Subscriber
<-----
data | | | | + +Figure 2.1.1/1: Transfer of updated subscription information to VLR or SGSN + +### 2.1.2 Invocation of Barring + +Barring of outgoing calls or mobile originated short messages is invoked in the VLR. If the VLR receives a request for subscription information for an outgoing call or mobile originated short message which is prohibited by Operator Determined Barring, the VLR will return a negative response to the request for subscription information, with an appropriate error indication. The MSC may relay this error indication via the BSS/RNS to the mobile station over the radio path, or (in the case of an outgoing call) may connect the mobile station to an address to be determined by the network operator. + +Barring of mobile originated short messages is invoked in the SGSN. If the SGSN receives a request for a mobile originated short message which is prohibited by Operator Determined Barring, the SGSN will return a negative response to the request with an appropriate error indication via the BSS/RNS to the mobile station over the radio path. + +Barring of all international calls, barring of all international calls except those directed to the home PLMN country, barring of all premium rate (information) calls or barring of all premium rate (entertainment) calls requires the VLR or the SGSN to analyse the called number to determine whether the requested call is barred. + +Barring of all outgoing calls when roaming outside the home PLMN country requires the HLR to determine whether a request for location updating originates from a PLMN outside the home PLMN country. If the request does originate from a PLMN outside the home PLMN country, the HLR will transfer subscription information to the requesting node to indicate that the mobile station is subject to barring of all outgoing calls. + +Operator Specific Barring may apply to outgoing or incoming calls, or mobile originated or mobile terminated short messages; if it applies to outgoing calls or mobile originated short messages, it is invoked in the VLR or the SGSN, as described above. If the barring applies to calls directed to a specific class of destination, the called number must be analysed to determine whether the requested call is barred. + +Indicative message flow diagrams for the handling of Operator Determined Barring of outgoing calls or mobile originated short messages are given in figures 2.1.2/1 and 2.1.2/2. For the case where the mobile station is connected to an address determined by the network operator, this address is assumed to be directly connected to the MSC, so that no inter-MSC signalling is required. + + + +| MS | | MSC | | VLR | | +|--------------------------------------------------------------|---------------|-----|--|-----|--| +| Outgoing call or MO SMS request barred because of ODB | | | | | | +| | O/G Request | | | | | +| | -----> | | | | | +| | Send Info for | | | | | +| | -----> | | | | | +| | O/G Call | | | | | +| | | | | | | +| | Reject | | | | | +| | <----- | | | | | +| | (cause) | | | | | +| Operator option: error indication returned to MS | | | | | | +| | | | | | | +| | Reject | | | | | +| | <----- | | | | | +| | (Cause) | | | | | + +Figure 2.1.2/1: Operator Determined Barring of Outgoing Calls or Mobile Originated Short Messages invocation in the VLR + + + +| MS | | SGSN | | +|--------------------------------------|---------------------|------|--| +| MO SMS request barred because of ODB | | | | +| | MO Short
Message | | | +| Error indication returned to MS | | | | +| | Reject
(cause) | | | + +Sequence diagram showing the interaction between MS and SGSN for Operator Determined Barring of Mobile Originated Short Messages. The MS sends an 'MO Short Message' to the SGSN, which is barred because of ODB. The SGSN returns an 'Error indication' (Reject with cause) to the MS. + +Figure 2.1.2/2: Operator Determined Barring of Mobile Originated Short Messages invocation in the SGSN + +## 2.2 Barring of Incoming Calls or Mobile Terminated Short Messages + +### 2.2.1 Application or Change of Barring in the HLR + +If barring of incoming calls or mobile terminated short messages is applied to a subscription (or existing barring of incoming calls or mobile terminated short messages is modified or removed) by administrative action in the HLR, the HLR will update the subscription information accordingly. It is not necessary to transfer the updated subscription information to the VLR or the SGSN. + +### 2.2.2 Invocation of Barring + +Barring of incoming calls is invoked in the HLR. If the HLR receives a request for routing information for a call directed to a mobile station which is subject to barring of incoming calls, the HLR will return a negative response to the request for routing information, with an appropriate error indication. The Gateway MSC may relay this error indication to the originating network using the appropriate telephony signalling system, or may connect the call to a recorded announcement to be determined by the network operator. + +Barring of mobile terminated short messages is invoked in the HLR. If the HLR receives a request for routing information for a short message directed to a mobile station which is subject to barring of incoming calls, the HLR will return a negative response to the request for routing information, with an appropriate error indication. This error indication will be relayed to the originating Short Message service centre by the Gateway MSC using the protocol defined in 3GPP TS 23.040. + +Operator Specific Barring may apply to outgoing or incoming calls, or mobile originated or mobile terminated short messages; if it applies to incoming calls or mobile terminated short messages, it is invoked in the HLR, as described above. + +An indicative message flow diagram for the handling of Operator Determined Barring of incoming calls is given in figure 2.2.2/1. For the case where the call is connected to an address determined by the network operator, this address is assumed to be directly connected to the GMSC, so that no inter-MSC signalling is required. + + + +**HLR** **GMSC** **N/W** + +Incoming call request barred because of ODB + +Incoming call + <----- + (address) + Send routing + <----- + info request + +Reject + -----> + (cause) + +Operator option: error indication returned to network + +Reject + -----> + (cause) + +Sequence diagram for Operator Determined Barring of Incoming Calls. Lifelines: HLR, GMSC, N/W. The diagram shows an incoming call request being processed by the HLR, which then sends a reject message to the GMSC with a cause code. An operator option for error indication is also shown. + +Figure 2.2.2/1: Operator Determined Barring of Incoming Calls + +An indicative message flow diagram for the handling of Operator Determined Barring of mobile terminated short messages is given in figure 2.2.2/2. + + + +**HLR** **SMS GMSC** **SMS SC** + +MT short message request barred because of ODB + +MT short + <----- + message + Send routing + info for SM + <----- + request + +Reject + -----> + (cause) + +Reject + -----> + (cause) + +Sequence diagram for Operator Determined Barring of Mobile Terminated Short Messages. Lifelines: HLR, SMS GMSC, SMS SC. The diagram shows an MT short message request being processed by the HLR, which then sends two reject messages to the SMS GMSC with cause codes. + +Figure 2.2.2/2: Operator Determined Barring of Mobile Terminated Short Messages + +## 2.3 Barring of Roaming + +### 2.3.1 Application or Change of Barring in the HLR/HSS/UDM + +If barring of roaming is applied to a subscription (or modified or removed) by administrative action in the HLR/HSS/UDM, the HLR/HSS/UDM shall update the subscription information accordingly. If the HLR/HSS/UDM determines from the identity of the VLR and/or the SGSN and/or MME and/or the AMF that the mobile subscriber is currently registered in a barred PLMN, the HLR/HSS/UDM shall put the barring into effect by using a Cancel Location operation to the VLR and/or the SGSN and/or to the MME when applied in HLR/HSS or a UECM Deregistration to AMF when applied in UDM, as shown in figure 2.3.1/1. In the 5G Core case, barring of roaming may be stored in UDR. Upon change of barring of roaming in UDR, UDM clears also user registration in UDR using Nudr\_DM\_Update operation and unsubscribes to changes on barring of roaming data using Nudr\_DM\_Unsubscribe operation. + +If the mobile subscriber is not currently registered in a barred PLMN, the HLR/HSS/UDM shall take no further action. + + + +| MS | MSC | VLR or SGSN or MME | HLR/HSS | +|-------------------------------|-----|------------------------------|---------| +| ODB of roaming applied | | | | +| | | Cancel
<-----
location | | + +Figure 2.3.1/1: Immediate Application of Barring of Roaming in HLR/HSS + + + +| UE | AMF | UDM | +|-------------------------------|-----|-----| +| ODB of roaming applied | | | +| UECM Deregistration
<----- | | | +| Deregistration
<----- | | | + +Figure 2.3.1/2: Immediate Application of Barring of Roaming in UDM + +### 2.3.2 Invocation of Barring + +Barring of roaming is invoked in the HLR/HSS/UDM. If the HLR receives a request from a VLR for location updating for a mobile which is attempting to roam to an area prohibited by Operator Determined Barring, the HLR shall reject the location updating request with an appropriate error indication and this error indication shall be relayed by the MSC and the BSS/RNS to the mobile station over the radio path. If the HLR receives a request from a SGSN for location updating for a mobile which is attempting to roam to an area prohibited by Operator Determined Barring, the HLR shall reject the location updating request with an appropriate error indication and this error indication shall be relayed by the SGSN and the BSS/RNS to the mobile station over the radio path. If the HSS receives a request from a MME for location updating for a mobile which is attempting to roam to an area prohibited by Operator Determined Barring, the HSS shall reject the location updating request with an appropriate error indication and this error indication shall be relayed by the MME to the mobile station over the radio path. If the UDM receives a request from an AMF for 5G registration for a user equipment who is attempting to roam to an area prohibited by Operator Determined Barring, the UDM shall reject the registration request with an appropriate error indication and this error indication shall be relayed by the AMF to the user equipment over the radio path. + +In the 5G Core case, barring of roaming can be optionally stored in UDR. Upon change of barring of roaming in UDR, UDM clears also user registration in UDR using Nudr\_DM\_Update operation and unsubscribes to changes on barring of roaming data using Nudr\_DM\_Unsubscribe operation. + +Indicative message flow diagrams for the handling of Operator Determined Barring of roaming are given in figures 2.3.2/1, 2.3.2/2, 2.3.2/3 and 2.3.2/4. + + + +Roaming barred because of ODB + +``` + +sequenceDiagram + participant MS + participant MSC + participant VLR + participant HLR + Note over MS, MSC: LR request + MS->>MSC: + Note over MS, MSC: Location update request + MS->>MSC: + Note over MSC, HLR: Update Location request + MSC->>HLR: + Note over HLR, MSC: Reject (cause) + HLR-->>MSC: + Note over MSC, MS: Reject (cause) + MSC-->>MS: + Note over MSC, MS: Reject (cause) + MSC-->>MS: + +``` + +Sequence diagram showing MS sending LR request and Location update request to MSC. MSC sends Update Location request to HLR. HLR returns Reject (cause) to MSC. MSC returns Reject (cause) to MS twice. + +**Figure 2.3.2/1: Operator Determined Barring of Roaming invocation in HLR. Roaming in a prohibited VLR** + + + +Roaming barred because of ODB + +``` + +sequenceDiagram + participant MS + participant SGSN + participant HLR + Note over MS, SGSN: LR request + MS->>SGSN: + Note over MS, SGSN: GPRS Update Location request + MS->>SGSN: + Note over SGSN, MS: Reject (cause) + SGSN-->>MS: + Note over SGSN, MS: Reject (cause) + SGSN-->>MS: + +``` + +Sequence diagram showing MS sending LR request and GPRS Update Location request to SGSN. SGSN returns Reject (cause) to MS twice. + +**Figure 2.3.2/2: Operator Determined Barring of Roaming invocation in HLR. Roaming in a prohibited SGSN** + + + +**MS** **MME** **HSS** + +Roaming barred because of ODB + +``` + +sequenceDiagram + participant MS + participant MME + participant HSS + Note left of MS: Roaming barred because of ODB + MS->>MME: LR request + MME->>HSS: Update Location request + HSS-->>MME: Reject (cause) + MME-->>MS: Reject (cause) + +``` + +Sequence diagram showing Operator Determined Barring of Roaming invocation in HSS. The MS sends an LR request to the MME, which then sends an Update Location request to the HSS. The HSS responds with a Reject (cause), which the MME then forwards to the MS as a Reject (cause). + +**Figure 2.3.2/3: Operator Determined Barring of Roaming invocation in HSS. Roaming in a prohibited MME** + + + +**UE** **AMF** **UDM** + +Roaming barred because of ODB + +``` + +sequenceDiagram + participant UE + participant AMF + participant UDM + Note left of UE: Roaming barred because of ODB + UE->>AMF: Registration request + AMF->>UDM: UECM Registration request + UDM-->>AMF: Reject (cause) + AMF-->>UE: Reject (cause) + +``` + +Sequence diagram showing Operator Determined Barring of Roaming invocation in UDM. The UE sends a Registration request to the AMF, which then sends a UECM Registration request to the UDM. The UDM responds with a Reject (cause), which the AMF then forwards to the UE as a Reject (cause). + +**Figure 2.3.2/4: Operator Determined Barring of Roaming invocation in UDM. Roaming in a prohibited AMF** + +## 2.4 Barring of Supplementary Services Access + +Barring of supplementary services access encompasses the general barring of supplementary services management category specified in 3GPP TS 22.041 [2] and the specific categories of barring of registration of a call forwarded-to number and barring of invocation of call transfer. + +### 2.4.1 Application or Change of Barring in the HLR + +If barring of supplementary services access is applied to a subscription (or existing barring of supplementary services access is modified or removed) by administrative action in the HLR, the HLR will update the subscription information accordingly, and, if necessary, transfer the updated subscription information to the VLR using one or more Insert Subscriber Data operations, as shown in figure 2.1.1/1. + +If the VPLMN does not support Operator Determined Barring of supplementary service access, the VLR shall indicate this in the acknowledgement to the Insert Subscriber Data message. The HLR shall then, as an operator option, apply barring of roaming as described in clause 2.3 or take any other action decided by the operator of the HPLMN. + +### 2.4.2 Invocation of Barring + +Barring of supplementary services access is invoked in the HLR or the VLR, depending on the supplementary service operation. + +Barring of access to the following supplementary service operations is invoked in the HLR: + +- registration; +- erasure; +- activation; +- deactivation; +- password registration; +- processing unstructured SS data. + +An indicative message flow diagram for the handling in the HLR of Operator Determined Barring of access to supplementary services is given in figure 2.4.2/1. + + + +| MS | MSC | VLR | HLR | +|--------------------------------------------------------|-----------------------|-----|-----------------------| +| Access to Supplementary Services barred because of ODB | | | | +| | SS request
-----> | | | +| | SS activity
-----> | | | +| | request | | | +| | | | SS activity
-----> | +| | | | request | +| | | | Reject
<----- | +| | | | (cause) | +| | Reject
<----- | | | +| | (cause) | | | +| | Reject
<----- | | | +| | (cause) | | | + +Figure 2.4.2/1: Operator Determined Barring of Access to Supplementary Services in the HLR + +NOTE 1: Although the HLR handles interrogation of some supplementary services, Operator Determined Barring of interrogation of all supplementary services is invoked in the VLR. This reduces the amount of analysis which the VLR must perform on supplementary service requests before deciding whether to relay a supplementary service request to the HLR or reject it because of Operator Determined Barring of access to supplementary services. Operator Determined Barring of control of PLMN specific supplementary services is invoked in the VLR for the same reason. + +NOTE 2: Although the VLR handles some processing of unstructured SS data, and therefore has to check for Operator Determined Barring of access to supplementary services, a check is also specified in the HLR to guard against the case where the VLR does not support Operator Determined Barring of access to supplementary services. + +Barring of access to the following supplementary service operations is invoked in the VLR: + +- interrogation; +- invocation; +- control of PLMN specific supplementary services; +- processing unstructured SS data. + +An indicative message flow diagram for the handling in the VLR of Operator Determined Barring of access to supplementary services is given in figure 2.4.2/2. + + + +| MS | | MSC | | VLR | | +|---------------------------------------------------------------|-------------|-----|--|-----|--| +| Access to Supplementary Services barred because of ODB | | | | | | +| | SS request | | | | | +| | -----> | | | | | +| | SS activity | | | | | +| | -----> | | | | | +| | request | | | | | +| | | | | | | +| | Reject | | | | | +| | <----- | | | | | +| | (cause) | | | | | +| | | | | | | +| | Reject | | | | | +| | <----- | | | | | +| | (Cause) | | | | | + +Figure 2.4.2/2: Operator Determined Barring of Access to Supplementary Services in the VLR + +### 2.4.3 Operator Determined Barring of access to supplementary service not supported in VLR + +If the VLR does not support Operator Determined Barring of access to supplementary services the HLR shall take the following actions: + +The VLR supports only phase 1: + +If the HLR receives a request which should normally be barred by the VLR the HLR shall reject the request with the appropriate phase 1 error (illegal SS operation or system failure). + +The VLR supports phase 2 but does not support this Operator Determined Barring category: + +If the HLR receives a request which should normally be barred by the VLR the HLR shall reject the request instead of the VLR. + +Note that requests handled locally by the VLR (e.g. interrogation) will not be barred. + +## 2.5 Barring of MS initiated PDP context activation + +Barring of MS initiated PDP context activation shall be performed based on the Operator Determined Barring for Packet Oriented Services defined in 3G TS 22.041 [2]. + +### 2.5.1 Application or Change of Barring in the HLR + +If barring of Packet Oriented Services is applied to a subscription (or existing barring of Packet Oriented Services is modified or removed) by administrative action in the HLR, the HLR will update the subscription information accordingly, and transfer the updated subscription information to the SGSN using one or more Insert Subscriber Data operations, as shown in figure 2.5.1/1. + +If the VPLMN does not support Operator Determined Barring of Packet Oriented Services, the SGSN shall indicate this in the acknowledgement of the Insert Subscriber Data message. The HLR shall then, as an operator option, apply barring of roaming as described in clause 2.3 or take any other action decided by the operator of the HPLMN. + + + +| MS | | SGSN | | HLR | | +|---------------------------------------------------------------------|-------------------------------|------|--|-----|--| +| ODB of Packet Oriented Services applied, modified or removed | | | | | | +| | Insert Subscriber <----- data | | | | | + +Figure 2.5.1/1: Transfer of updated subscription information to SGSN + +### 2.5.2 Invocation of Barring + +Barring of MS initiated PDP context activation is invoked in the SGSN. If the SGSN receives a request for an MS initiated PDP context activation which is prohibited by Operator Determined Barring, the SGSN will return a negative response to the request with an appropriate error indication via the BSS/RNS to the mobile station over the radio path. + +NOTE: Barring of MS initiated PDP context activation for Packet Oriented Services is not applicable for Local IP Access (LIPA). + +Barring of MS initiated PDP context activation is performed in the SGSN while the SGSN selects the APN and GGSN. The APN operator identifier, a part of selected APN is referred to make a judgement whether to be barred or not. The detail mechanism of the ODB judgement is specified in the 3G TS 23.060 [4]. + +Indicative message flow diagram for the handling of Operator Determined Barring of MS initiated PDP context activation is given in figures 2.5.2/1. + + + +| MS | | SGSN | | | | +|------------------------------------------------------------------|-------------------------------------|------|--|--|--| +| MS initiated PDP context activation barred because of ODB | | | | | | +| | Activate PDP context request -----> | | | | | +| | Reject <----- (cause) | | | | | + +Figure 2.5.2/1: Operator Determined Barring of MS initiated PDP context activation in the SGSN + +## 2.5A Barring of EPS Bearer context establishment + +Barring of EPS Bearer context establishment shall be performed based on the Operator Determined Barring for Packet Oriented Services defined in 3GPP TS 22.041 [2]. + +### 2.5A.1 Application or Change of Barring in the HSS + +If barring of Packet Oriented Services is applied to a subscription (or existing barring of Packet Oriented Services is modified or removed) by administrative action in the HSS, the HSS shall update the subscription information + +accordingly, and transfer the updated subscription information to the MME using one or more Insert Subscriber Data operations, as shown in figure 2.5A.1/1. + +If the VPLMN does not support Operator Determined Barring of Packet Oriented Services, the MME shall indicate this in the acknowledgement of the Insert Subscriber Data message. The HSS shall then, as an operator option, apply barring of roaming as described in clause 2.3 or take any other action decided by the operator of the HPLMN. + + + +| MS | | MME | | HSS | | +|--------------------------------------------------------------|--|----------------------------------------|--|-----|--| +| ODB of Packet Oriented Services applied, modified or removed | | | | | | +| | | Insert
Subscriber
<-----
data | | | | + +Figure 2.5A.1/1: Transfer of updated subscription information to MME + +### 2.5A.2 Invocation of Barring + +Barring of EPS Bearer context establishment is invoked in the MME. If the MME receives from an UE connected over E-UTRAN an attach or PDN connectivity request which is prohibited by Operator Determined Barring, the MME shall return a negative response to the request with an appropriate error indication to the UE over the E-UTRAN radio path. + +NOTE: Barring of EPS Bearer context establishment for Packet Oriented Services is not applicable for Local IP Access (LIPA). + +For subscribers completely barred from the Packet Oriented Services, the MME shall reject attach requests. + +Barring of EPS Bearer context establishment for other barring categories for the Packet Oriented Services requires the MME to select the APN and PDN-GW before it can determine whether a request for EPS Bearer context establishment shall be barred or not: + +- For "bar a subscriber from requesting Packet Oriented Services from access points that are within the HPLMN whilst the subscriber is roaming in a VPLMN", MME shall check whether or not the subscriber is located in the HPLMN. If it is not and the PDN-GW being accessed is located in HPLMN, then the MME shall reject the attach or PDN connectivity request, +- For "bar a subscriber from requesting Packet Oriented Services from access points that are within the roamed to VPLMN", MME shall check whether or not the subscriber is located in the HPLMN. If it is not and the PDN-GW being accessed is located in VPLMN, then the MME shall reject the attach or PDN connectivity request. + +Indicative message flow diagram for the handling of Operator Determined Barring of EPS Bearer context establishment is given in figures 2.5A.2/1. + + + +| UE | | MME | | +|------------------------------------------------|------------------------------------------------|-----|--| +| E-UTRAN PDN connectivity barred because of ODB | | | | +| | Attach Request, or
PDN Connectivity request | | | +| | -----> | | | +| | Reject | | | +| | <----- | | | +| | (cause) | | | + +Figure 2.5A.2/1: Operator Determined Barring of EPS Bearer Context Establishment in the MME + +## 2.5B Barring of PDU Session establishment + +Barring of PDU Session establishment shall be performed based on the Operator Determined Barring for Packet Oriented Services defined in 3GPP TS 22.041 [2]. + +### 2.5B.1 Application or Change of Barring in the UDM + +If barring of Packet Oriented Services is applied to a subscription (or existing barring of Packet Oriented Services is modified or removed) by administrative action in the UDM, the UDM shall update the subscription information accordingly, and transfer the updated subscription information to the AMF/SMF using Nudm\_SDM Notification operation, as shown in figure 2.5B.1/1. + + + +| MS | | AMF or SMF | | UDM | | +|--------------------------------------------------------------|--|--------------------------|--|-----|--| +| ODB of Packet Oriented Services applied, modified or removed | | | | | | +| | | Nudm_SDM
Notification | | | | +| | | <----- | | | | + +Figure 2.5B.1/1: Transfer of updated subscription information to AMF/SMF + +### 2.5B.2 Invocation of Barring + +Barring of PDU Session establishment is invoked in the SMF. If the SMF receives from an UE connected over 5GS a PDU Session connectivity request which is prohibited by Operator Determined Barring, the SMF shall return a negative response to the request with an appropriate error indication to the UE over the 5G radio path. + +NOTE: Barring of PDU Session establishment for Packet Oriented Services is not applicable for Local Access Data Network (LADN). + +For subscribers completely barred from the Packet Oriented Services, the AMF may reject the registration requests. + +Barring of PDU Session establishment for other barring categories for the Packet Oriented Services, SMF determines whether a request for PDU Session establishment shall be barred or not: + +- For "bar a subscriber from requesting Packet Oriented Services from access points that are within the HPLMN whilst the subscriber is roaming in a VPLMN", if the subscriber is not located in the HPLMN and the SMF being accessed is located in HPLMN, then the SMF shall reject the PDU connectivity request, +- For "bar a subscriber from requesting Packet Oriented Services from access points that are within the roamed to VPLMN", if the subscriber is not located in the HPLMN and the SMF being accessed is located in VPLMN, then the SMF shall reject the PDU connectivity request. + +Indicative message flow diagram for the handling of Operator Determined Barring of PDU Session establishment is given in figures 2.5B.2/1. + + + +The diagram is a sequence diagram with two lifelines: UE and SMF. The title is "5G PDU connectivity barred because of ODB". The sequence of messages is as follows: + + +- The UE sends a "PDU Connectivity request" to the SMF via a dashed arrow. +- The SMF responds with a "Reject" message (containing a cause) via a dashed arrow pointing back to the UE. + +Sequence diagram showing PDU Connectivity request and Reject message between UE and SMF. + +Figure 2.5B.2/1: Operator Determined Barring of PDU Session Establishment in the SMF + +## 2.6 Barring of Network initiated PDP context activation + +Barring of Network initiated PDP context activation shall be performed based on the Operator Determined Barring for Packet Oriented Services defined in 3G TS 22.041 [2]. + +### 2.6.1 Application or Change of Barring in the HLR + +If barring of Packet Oriented Services is applied to a subscription (or existing barring of Packet Oriented Services is modified or removed) by administrative action in the HLR, the HLR will update the subscription information accordingly. It is not necessary to transfer the updated subscription information to the SGSN. + +### 2.6.2 Invocation of Barring + +Barring of Network initiated PDP context activation is invoked in the HLR. If the HLR receives a request for routing information for a PDP context activation directed to a mobile station which is subject to barring of Packet Oriented Services, the HLR will return a negative response to the request for routing information, with an appropriate error indication. The GGSN may relay this error indication to the PDP PDU incoming network using the appropriate interworking. + +An indicative message flow diagram for the handling of Operator Determined Barring of Network initiated PDP context activation is given in figure 2.6.2/1. + + + +| HLR | | GGSN | | N/W | | +|-----------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------|------|--|-----|--| +| Network initiated PDP context activation barred because of ODB | | | | | | +| | Incoming PDP PDU
<-----
(address)
Send routing
<-----
info request
for GPRS
Reject
----->
(cause) | | | | | +| Operator option: error indication returned to network | | | | | | +| | Reject
----->
(cause) | | | | | + +Figure 2.6.2/1: Operator Determined Barring of Network initiated PDP context activation + +## 2.6A Barring of existing PDP contexts + +Barring of existing PDP contexts shall be performed based on the Operator Determined Barring for Packet Oriented Services defined in 3G TS 22.041 [2]. + +### 2.6A.1 Application or Change of Barring in the HLR + +If barring of Packet Oriented Services is applied to a subscription (or existing barring of Packet Oriented Services is modified or removed) by administrative action in the HLR, the HLR will update the subscription information accordingly, and transfer the updated subscription information to the SGSN using one or more Insert Subscriber Data operations, as shown in figure 2.6A.1/1. + +If the VPLMN does not support Operator Determined Barring of Packet Oriented Services, the SGSN shall indicate this in the acknowledgement of the Insert Subscriber Data message. The HLR shall then, as an operator option, apply barring of roaming as described in clause 2.3 or take any other action decided by the operator of the HPLMN. + + + +| MS | | SGSN | | HLR | | +|---------------------------------------------------------------------|----------------------------------------|------|--|-----|--| +| ODB of Packet Oriented Services applied, modified or removed | | | | | | +| | Insert
Subscriber
<-----
data | | | | | + +Figure 2.6A.1/1: Transfer of updated subscription information to SGSN + +### 2.6A.2 Invocation of Barring + +Barring of existing PDP contexts is invoked in the SGSN. If the SGSN receives Insert Subscriber Data message due to barring of Packet Oriented Services is applied to a subscription (or existing barring of Packet Oriented Services is modified or removed) by administrative action in the HLR, the SGSN shall take the following action depending on barring category when one or more PDP contexts exist in SGSN. + +- For "bar subscribers completely from the Packet Oriented Services", SGSN shall deactivate all existing PDP contexts. +- For "bar a subscriber from requesting Packet Oriented Services from access points that are within the HPLMN whilst the subscriber is roaming in a VPLMN", SGSN shall check whether or not the subscriber is located in the HPLMN. If it is not and the GGSN being accessed is located in HPLMN, then all associated PDP contexts with this path shall be deactivated.. +- For "bar a subscriber from requesting Packet Oriented Services from access points that are within the roamed to VPLMN", SGSN shall check whether or not the subscriber is located in the HPLMN. If it is not and the GGSN being accessed is located in VPLMN, then all associated PDP contexts with this path shall be deactivated. + +NOTE: Barring of existing PDP contexts for Packet Oriented Services is not applicable for Local IP Access (LIPA). + +## 2.6B Barring of existing EPS Bearer contexts + +Barring of existing EPS Bearer contexts shall be performed based on the Operator Determined Barring for Packet Oriented Services defined in 3GPP TS 22.041 [2]. + +### 2.6B.1 Application or Change of Barring in the HSS + +If barring of Packet Oriented Services is applied to a subscription (or existing barring of Packet Oriented Services is modified or removed) by administrative action in the HSS, the HSS shall update the subscription information accordingly, and transfer the updated subscription information to the MME using one or more Insert Subscriber Data operations, as shown in figure 2.6B.1/1. + +If the VPLMN does not support Operator Determined Barring of Packet Oriented Services, the MME shall indicate this in the acknowledgement of the Insert Subscriber Data message. The HSS shall then, as an operator option, apply barring of roaming as described in clause 2.3 or take any other action decided by the operator of the HPLMN. + + + +| UE | | MME | | HSS | | +|--------------------------------------------------------------|--|----------------------------------------|--|-----|--| +| ODB of Packet Oriented Services applied, modified or removed | | | | | | +| | | Insert
Subscriber
<-----
data | | | | + +Figure 2.6B.1/1: Transfer of updated subscription information to MME + +### 2.6B.2 Invocation of Barring + +Barring of existing EPS Bearer contexts is invoked in the MME. If the MME receives Insert Subscriber Data message due to barring of Packet Oriented Services being applied to a subscription (or existing barring of Packet Oriented Services is modified) by administrative action in the HSS, the MME shall take the following action depending on barring category when one or more EPS Bearer contexts exist in MME. + +- For "bar subscribers completely from the Packet Oriented Services", MME shall deactivate all existing EPS Bearer contexts. +- For "bar a subscriber from requesting Packet Oriented Services from access points that are within the HPLMN whilst the subscriber is roaming in a VPLMN", MME shall check whether or not the subscriber is located in the HPLMN. If it is not and the PDN-GW being accessed is located in HPLMN, then all associated EPS Bearer contexts with this path shall be deactivated. +- For "bar a subscriber from requesting Packet Oriented Services from access points that are within the roamed to VPLMN", MME shall check whether or not the subscriber is located in the HPLMN. If it is not and the PDN-GW being accessed is located in VPLMN, then all associated EPS Bearer contexts with this path shall be deactivated. + +NOTE: Barring of existing EPS Bearer contexts for Packet Oriented Services is not applicable for Local IP Access (LIPA). + +## 2.6C Barring of existing PDU Sessions + +Barring of existing PDU Sessions shall be performed based on the Operator Determined Barring for Packet Oriented Services defined in 3GPP TS 22.041 [2]. + +### 2.6C.1 Application or Change of Barring in the UDM + +If barring of Packet Oriented Services is applied to a subscription (or existing barring of Packet Oriented Services is modified or removed) by administrative action in the UDM, the UDM shall update the subscription information accordingly, and transfer the updated subscription information to the AMF using Nudm\_SDM Notification operation, as shown in figure 2.6C.1/1. + + + +| UE | AMF | UDM | +|--------------------------------------------------------------|---------------------------------|-----| +| ODB of Packet Oriented Services applied, modified or removed | | | +| | Nudm_SDM Notification
<----- | | + +Figure 2.6C.1/1: Transfer of updated subscription information to AMF + +### 2.6C.2 Invocation of Barring + +Barring of existing PDU Sessions is invoked in the AMF. If the AMF receives Nudm\_SDM Notification message due to barring of Packet Oriented Services being applied to a subscription (or existing barring of Packet Oriented Services is modified) by administrative action in the UDM, the AMF shall take the following action depending on barring category when one or more PDU Sessions exist in AMF. + +- For "bar subscribers completely from the Packet Oriented Services", AMF shall release all existing PDU Sessions. +- For "bar a subscriber from requesting Packet Oriented Services from access points that are within the HPLMN whilst the subscriber is roaming in a VPLMN", AMF shall check whether or not the subscriber is located in the HPLMN. If it is not and the SMF being accessed is located in HPLMN, then all associated PDU Sessions with this path shall be released. + +- For "bar a subscriber from requesting Packet Oriented Services from access points that are within the roamed to VPLMN", AMF shall check whether or not the subscriber is located in the HPLMN. If it is not and the SMF being accessed is located in VPLMN, then all associated PDU sessions with this path shall be released. + +NOTE: Barring of existing EPS Bearer contexts for Packet Oriented Services is not applicable for Local Access Data Network (LADN). + +## 2.7 Interactions of Operator Determined Barring with Supplementary Services + +The following interactions of Operator Determined Barring with supplementary services have been identified: + +### 2.7.1 Call Forwarding + +The interactions between Operator Determined Barring and Call Forwarding are specified in 3GPP TS 22.041 [2]. + +The interaction where Operator Determined Barring is applied when there is an existing Call Forwarding programme which is in contravention of the Operator Determined Barring programme is shown in the message flow diagram in figure 2.7.1/1. The HLR modifies the subscription information for the mobile subscriber to show that the contravening call forwarding programme is quiescent, and forwards the modified subscription information to the VLR. No indication is forwarded to the mobile station or the user. + + + +``` + +sequenceDiagram + participant MS + participant MSC + participant VLR + participant HLR + Note over MS, HLR: ODB applied when Call Forwarding programme contravenes ODB + HLR-->>VLR: Insert Subscriber data + +``` + +Sequence diagram showing HLR sending 'Insert Subscriber data' to VLR when ODB is applied due to a contravening Call Forwarding programme. + +**Figure 2.7.1/1: Effect of Operator Determined Barring on Call Forwarding programme** + +The interaction where the user attempts to activate or register a call forwarding programme which is in contravention of an operator determined barring category is shown in the message flow diagram in figure 2.7.1/2. + + + +| MS | | MSC | | VLR | | HLR | | +|---------------------------------------------------------------|------------------------------------------------------------------------------------------|-----|-------------------------------------|-----|--|-----|--| +| Request for Call Forwarding programme contravening ODB | | | | | | | | +| | SS request
(register or
----->
activate CF)
SS activity
----->
request | | | | | | | +| | | | SS
activity
----->
request | | | | | +| | | | Reject
<-----
(cause) | | | | | +| | Reject
<-----
(cause) | | | | | | | +| Operator option: error indication returned to MS | | | | | | | | +| | Reject
<-----
(cause) | | | | | | | + +Figure 2.7.1/2: Interaction between Operator Determined Barring and Call Forwarding + +### 2.7.2 Closed User Group + +The interaction between Operator Determined Barring and Closed User Group is specified in 3GPP TS 22.041 [2]. In order to meet the service requirement, the checks of a call request in the HLR (for incoming calls) or VLR (for outgoing calls) against the Operator Determined Barring programme shall be carried out before the checks for Closed User Group. + +### 2.7.3 Call Barring + +The interaction between Operator Determined Barring and the Call Barring supplementary service is specified in 3GPP TS 22.041 [2]. In order to meet the service requirement, the checks of a call request in the HLR (for incoming calls) or VLR (for outgoing calls) against the Operator Determined Barring programme shall be carried out before the checks for the Call Barring supplementary service. + +## 2.8 Barring of services in I-WLAN + +NOTE: The WLAN Network Selection and WLAN/3GPP Radio Interworking features supersede the I-WLAN feature from Rel-12 onwards, therefore all I-WLAN related requirements specified in the present Clause are no longer maintained. + +Barring of interworked services in I-WLAN upon the activation of W-APN shall be performed based on the Operator Determined Barring for Packet Oriented Services as defined in 3GPP TS 29.234 [5]. + +### 2.8.1 Change of Barring in the HSS + +If barring of Packet Oriented Services for I-WLAN is applied to a subscription (or existing barring of Packet Oriented Services is modified or removed) by administrative action in the HSS, the HSS shall update the subscription information accordingly. It is necessary to transfer the updated User Profile Data and subscription information to the 3GPP AAA Server if the subscriber is currently using interworked WLAN services. After downloading the update User Profile Data the 3GPP AAA Server shall initiate re-authorization of the W-APN if there is an existing connection established. The HSS initiated User Profile Data update indication followed by the 3GPP AAA Server download of the updated User Profile Data and re-authorization request is shown in the message flow diagram in Figure 2.8.1/1. + + + +| WLAN-UE | | (Visited/Home) PDG | | 3GPP AAA Server | | HSS | | +|---------------------------------------------------------------------|--|--------------------------------------------------------------------------------------------|--|---------------------------------------------|--|-----|--| +| ODB of Packet Oriented Services applied, modified or removed | | | | | | | | +| | | | | Update of
User Profile
<-----
data | | | | +| | | | | Download
User Profile
<----->
data | | | | +| | | Re-authorization Request
if there is existing W-APN
connection established
<----- | | | | | | + +Figure 2.8.1/1: Transfer of updated User profile Data to 3GPP AAA Server + +### 2.8.2 Barring of interworked packet services in I-WLAN + +The interactions between Operator Determined Barring and W-APN activation/authorization are specified in 3GPP TS 29.234 [5]. + +Barring of interworked WLAN packet services is invoked in the 3GPP AAA Server. If the 3GPP AAA Server receives a request for a W-APN activation/authorization which is prohibited by Operator Determined Barring, the 3GPP AAA Server shall return a negative response to the request with an appropriate error code. + +Indicative message flow diagram for the handling of Operator Determined Barring of interworked WLAN packet services is given in figure 2.8.2/1. + + + +| WLAN-UE | | (Visited/Home) PDG | | 3GPP AAA Server | | HSS | | +|------------------------------------------------------------------------|------------------------------------|--------------------|--|-----------------|--|-----|--| +| Activation of W-APN when interworked packet services are barred | | | | | | | | +| | W-APN (re-)authorization
-----> | | | | | | | +| | Authorization Reject
<----- | | | | | | | + +Figure 2.8.2/1: Authorization attempt of a interworked packet services when the WLAN-UE is connecting via a PDG located either in Visited or Home PLMN + +### 2.8.3 Barring of W-APN Activation in I-WLAN + +The interactions between Operator Determined Barring and W-APN activation/authorization are specified in 3GPP TS 29.234 [5]. + +Barring of specific W-APN is invoked in the 3GPP AAA Server. If the 3GPP AAA Server receives a request for a W-APN activation/authorization which is prohibited by Operator Determined Barring, the 3GPP AAA Server shall return a negative response to the request with an appropriate error code. + +Indicative message flow diagram for the handling of Operator Determined Barring of a specific W-APN is given in figure 2.8.3/1. + + + +| WLAN-EU | (Visited/Home) PDG | 3GPP AAA Server | HSS | +|----------------------------------------------------------|------------------------------------|-----------------|-----| +| Activation of W-APN when the said W-APN is barred | | | | +| | W-APN (re-)authorization
-----> | | | +| | Authorization Reject
<----- | | | + +**Figure 2.8.3/1: Authorization attempt of a W-APN when the WLAN-UE is connecting via a PDG located either in Visited or Home PLMN** + +### 2.8.4 Barring of public Internet access in I-WLAN + +The interactions between Operator Determined Barring and W-APN activation/authorization are specified in 3GPP TS 29.234 [5]. + +Barring of specific public Internet access through a specific W-APN is invoked in the 3GPP AAA Server. If the 3GPP AAA Server receives a request for a W-APN activation/authorization where public Internet access is prohibited by Operator Determined Barring, the 3GPP AAA Server shall return a positive response to the request with appropriate routing policies that allow the PDG filter IP traffic to or from public Internet. + +Indicative message flow diagram for the handling of Operator Determined Barring of a specific W-APN is given in figure 2.8.4/1. + + + +| WLAN-EU | (Visited/Home) PDG | 3GPP AAA Server | HSS | +|---------------------------------------------------------------------|---------------------------------------------------------------|-----------------|-----| +| Activation of W-APN when access to public Internet is barred | | | | +| | W-APN (re-)authorization
-----> | | | +| | Authorization Accept and
Routing Policy Download
<----- | | | + +**Figure 2.8.4/1: Authorization of a W-APN when public Internet access is barred** + +## 2.9 Barring of Access to All Except Some Specific DNNs/APNs + +### 2.9.1 General + +Barring of access to all except some specific DNNs/APNs shall be performed based on the Operator Determined Barring for Packet Oriented Services defined in 3GPP TS 22.041 [2]. + +### 2.9.2 Application or Change of Barring in the UDM/HSS/HLR + +When barring of access to all except some specific DNNs/APNs is invoked in the UDM/HSS/HLR, the UDM/HSS/HLR shall update the subscription profile to contain only the specific non barred DNNs/APNs as the subscribed DNNs/APNs and indicate the updated subscription information to the AMF, SMF, MME or the SGSN. + +If the existing default DNN/APN is barred, one of the specific non barred DNN/APNs shall be the new default DNN/APN. + +The UDM/HSS/HLR shall disable any other barring of Packet Oriented Services when this function is used. + +When barring of access to all except some specific DNNs/APNs is removed in the UDM/HSS/HLR, the UDM/HSS/HLR shall update the subscription profile to restore the originally subscribed DNNs/APNs, including the original default DNN/APN and indicate the updated subscription information to the AMF, the MME or the SGSN. + +### 2.9.3 Invocation of Barring + +When the AMF, the SMF, the MME or the SGSN updates the subscription, and if the subscriber has existing PDN connectivity for DNNs/APNs not in the received list of subscribed DNN/APN, the SMF, MME or the SGSN deactivates the PDU/PDN connectivity for these DNNs/APNs as specified in 3GPP TS 23.502 [7], 3GPP TS 23.401 [6] and 3GPP TS 23.060 [7]. + +To bar a subscriber from access to all except some specific DNNs/APNs, when the AMF, the MME or the SGSN receives PDU/PDN Connectivity Request message from the UE or the MS, the AMF, the MME or the SGSN shall check whether or not the requested DNN/APN is included in the list of subscribed DNNs/APNs for the subscriber. If included, then the AMF, the MME or the SGSN continues the Attach or UE-requested PDU/PDN connectivity or MS-requested PDP Context Activation procedures as specified in 3GPP TS 23.502 [7], 3GPP TS 23.401 [6] and 3GPP TS 23.060 [7]. If not included, then the AMF, the MME or the SGSN rejects the Attach or UE-requested PDU/PDN connectivity or MS-requested PDP Context Activation requests as specified in 3GPP TS 23.502 [7], 3GPP TS 23.401 [6] and 3GPP TS 23.060 [7]. + +# --- 3 Information stored in location registers + +## 3.1 Information stored in the HLR/HSS + +The HLR must store subscription information for each mobile subscriber to define which of the following categories of barring is to be applied, independently of each other: + +Barring of outgoing calls (including mobile originated short messages) - one of: + +- 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 calls when roaming outside 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. + +Barring of incoming calls (including mobile terminated short messages) - one of: + +- 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. + +Barring of roaming - one of: + +- Barring of roaming outside the home PLMN; +- Barring of roaming outside the home PLMN country. + +Barring of outgoing premium rate calls - one or both of: + +- Barring of outgoing premium rate (information) calls; +- Barring of outgoing premium rate (entertainment) calls. + +Barring specific to the home PLMN - when the mobile station is registered in its home PLMN, any one or more of: + +- Operator Specific Barring (Type 1); +- Operator Specific Barring (Type 2); +- Operator Specific Barring (Type 3); +- Operator Specific Barring (Type 4). + +Barring of Supplementary Services Management. + +Barring of registration of call forwarding - one of: + +- 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. + +Barring of invocation of call transfer: + +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, i.e. the call is either an outgoing international call or an incoming call when the served subscriber roams outside the HPLMN country; +- 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, i.e. the call is either an outgoing inter-zonal call or an incoming call when the served subscriber roams to a VPLMN in a different zone from the HPLMN; + +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. + +Barring of Packet Oriented Services - one of: + +- 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; +- Barring of access to all except some specific APNs. + +## 3.1A Information stored in the UDM/UDR + +Barring of roaming - one of: + +- Barring of roaming outside the home PLMN; +- Barring of roaming outside the home PLMN country. +- Barring of Packet Oriented Services - one of: +- 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; + +- Barring of access to all except some specific DNNs. + +## 3.2 Information stored in the VLR + +The VLR must store subscription information for each mobile subscriber to define which of the following categories of barring is to be applied, independently of each other: + +Barring of outgoing calls (including mobile originated short messages) - one of: + +- 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. + +Barring of outgoing premium rate calls - one or both of: + +- Barring of outgoing premium rate (information) calls; +- Barring of outgoing premium rate (entertainment) calls. + +Barring specific to the home PLMN - when the mobile station is registered in its home PLMN, any one or more of: + +- Operator Specific Barring (Type 1); +- Operator Specific Barring (Type 2); +- Operator Specific Barring (Type 3); +- Operator Specific Barring (Type 4). + +Barring of Supplementary Services Management. + +Barring of invocation of call transfer: + +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, i.e. the call is either an outgoing international call or an incoming call when the served subscriber roams outside the HPLMN country; +- 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, i.e. the call is either an outgoing inter-zonal call or an incoming call when the served subscriber roams to a VPLMN in a different zone from the HPLMN. + +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. + +## 3.3 Information stored in the SGSN + +The SGSN shall store subscription information for each mobile subscriber to define which of the following categories of barring is to be applied, independently of each other: + +Barring of mobile originated short messages - one of: + +- 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. + +Barring specific to the home PLMN of mobile originated short messages - when the mobile station is registered in its home PLMN, any one or more of: + +- Operator Specific Barring (Type 1); +- Operator Specific Barring (Type 2); +- Operator Specific Barring (Type 3); +- Operator Specific Barring (Type 4). + +Barring of Packet Oriented Services - one of: + +- 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. + +## 3.3A Information stored in the MME + +The MME shall store subscription information for each mobile subscriber to define which of the following categories of barring is to be applied, independently of each other: + +Barring of mobile originated short messages - one of: + +- 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. + +Barring specific to the home PLMN of mobile originated short messages - when the mobile station is registered in its home PLMN, any one or more of: + +- Operator Specific Barring (Type 1); +- Operator Specific Barring (Type 2); +- Operator Specific Barring (Type 3); + +- Operator Specific Barring (Type 4). + +Barring of Packet Oriented Services - one of: + +- 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. + +## 3.4 Transfer of Subscription Information from HLR to VLR + +The following subscription information for Operator Determined Barring must be transferred from the HLR to the VLR when a mobile station registers in a VLR: + +- Barring of outgoing calls; +- Barring of outgoing premium rate calls; +- Barring of supplementary services management; +- Barring of invocation of call transfer. + +In addition, when a mobile station registers in a VLR in its home PLMN the subscription information for Operator Determined Barring specific to the home PLMN must be transferred from the HLR to the VLR. + +## 3.5 Transfer of Subscription Information from HLR to SGSN + +The following subscription information for Operator Determined Barring shall be transferred from the HLR to the SGSN when a mobile station registers in a SGSN: + +- Barring of outgoing calls (which leads to barring of mobile originated short messages). + +The following subscription information for Operator Determined Barring for Packet Oriented Services shall be transferred from the HLR to the SGSN when a mobile station registers in a SGSN: + +- 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. + +In addition, when a mobile station registers in a SGSN in its home PLMN the subscription information for Operator Determined Barring specific to the home PLMN shall be transferred from the HLR to the SGSN. + +## 3.5A Transfer of Subscription Information from HSS to MME + +The following subscription information for Operator Determined Barring shall be transferred from the HLR to the MME when a mobile station registers in a MME: + +- Barring of outgoing calls (which leads to barring of mobile originated short messages). + +The following subscription information for Operator Determined Barring for Packet Oriented Services shall be transferred from the HSS to the MME when a mobile station registers in a MME: + +- 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. + +In addition, when a mobile station registers in an MME in its home PLMN the subscription information for Operator Determined Barring specific to the home PLMN shall be transferred from the HLR to the MME. + +## 3.6 I-WLAN Information stored in the HSS + +The HSS shall store subscription information for each I-WLAN subscriber to define which of the following categories of barring is to be applied, independently of each other. These barring categories are applied to WLAN 3GPP IP Access: + +- Barring of Interworking WLAN completely from the interworked service capabilities. +- Barring of a subscriber from requesting interworking through Packet Data Gateways that are within the HPLMN whilst the subscriber is WLAN connected via a VPLMN. +- Barring a subscriber from requesting packet-oriented services from Packet Data Gateways that are within the roamed to VPLMN. +- Barring of a subscriber from requesting direct Internet access from Packet Data Gateways that are within the I-WLAN. + +## 3.7 Transfer of User Profile Data from HSS to 3GPP AAA Server + +The following User Profile Data for Operator Determined Barring must be transferred from the HSS to the 3GPP AAA Server when a WLAN-UE authenticates to 3GPP AAA Server and the I-WLAN service: + +- Barring of Interworking WLAN completely from the interworked service capabilities +- Barring of a subscriber from requesting interworking through Packet Data Gateways that are within the HPLMN whilst the subscriber is WLAN connected via a VPLMN +- Barring a subscriber from requesting packet-oriented services from Packet Data Gateways that are within the roamed to VPLMN +- Barring of a subscriber from requesting direct Internet access from Packet Data Gateways that are within the I-WLAN + +## 3.8 Information stored in the AMF/SMF + +Barring of Packet Oriented Services - one of: + +- 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. + +## 3.9 Transfer of Subscription Information from UDM to AMF/SMF + +The following subscription information for Operator Determined Barring for Packet Oriented Services shall be transferred from the UDM to the AMF/SMF: + +- 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. + +In addition, when a mobile station registers in an AMF in its home PLMN the subscription information for Operator Determined Barring specific to the home PLMN shall be transferred from the UDM to the AMF/SMF. + +# Annex A: Change History + +| Change history | | | | | | | +|----------------|-----------|---------|--------|---------|-------------|---------------------------------------------------------------------------------------------| +| TSG CN# | Spec | Version | CR |
If the emergency indication includes the value for "test", mobile terminals which are not used for testing purpose silently discard the paging message and do not receive the corresponding CBS/warning message. | | + +## 8.2 Duplication Detection Function + +The MS/UE uses a common duplication detection function for all messages received in GSM, UMTS, E-UTRAN and NG-RAN. + +Upon reception of a new message, the MS/UE shall perform duplication detection on the messages. Those messages that are received from the same PLMN in the certain time period specified by the duplication detection time are subject to duplication detection. The MS/UE shall not perform duplication detection on messages whose duplication detection time has elapsed. The value of the duplication detection time to be used by the MS/UE shall be derived from the MCC of the current PLMN as follows: + +- If MCC = 440 or MCC = 441 (Japan), duplication detection time shall be 1 hour; +- For all other MCCs, duplication detection time shall be 24 hours. + +The MS/UE shall check: + +- 1) whether the Serial Number associated with the Message Identifier of the new message matches the Serial Number of any of those messages with the same Message Identifier that have been received and displayed to the subscriber and that are subject to the duplication detection. + +Additionally, the MS/UE may check: + +- 2) other criteria for detecting duplicates. An example of such a criterion is whether the actual contents of the two messages is the same. + +If criterion 1 is fulfilled and any implemented additional checks (as described in criterion 2) are also met, then the MS/UE shall consider the new message as duplicated and shall ignore it. If the Geographical Scope is not PLMN wide the validity of the Serial Number may be considered as described in sub clause 9.4.1.2.1. + +For ETWS, duplicate message detection shall be performed independently for primary and secondary notifications. + +## 8.3 ePWS functionality + +The ePWS functionality consists of the ePWS language-independent content functionality and the ePWS disaster characteristics functionality as follows: + +- 1) UEs with user interface which support the ePWS language-independent content functionality and which are capable of displaying text-based warning messages should be capable of displaying the language-independent content mapped to an event or a disaster (e.g. character such as Unicode based pictogram mapping to a disaster) that is part of user information contained in the content of a warning message transparently passed from CBC to UEs. + +NOTE 1: Language-independent contents mapped to disasters need to be formatted to be suitable to be included in a warning message. It could be unicode symbol or symbol based on GSM 7 bit default alphabet. It is desirable that standardised symbols mapped to disasters are applied in all countries that provide warning messages for public safety. This will make it possible for foreigners to intuitively understand the meaning of language-independent contents displayed to their devices. + +**Editor's note [WI: ePWS, CR#202]: FFS on what character(s) such as Unicode based pictogram(s) are the language-independent content mapped to an event or a disaster.** + +- 2) UEs with user interface which support the ePWS language-independent content functionality and which are incapable of displaying text-based warning messages should be capable of mapping message identifiers of received warning messages to language-independent contents stored in those UEs. When a warning message is received, such a UE should be capable of displaying of a language-independent content stored in the UE mapped from the message identifier of the received warning message. + +NOTE 2: This ePWS functionality is not applied for such UEs if they are not capable of storing any language-independent content. + +- 3) UEs with no user interface which support the ePWS disaster characteristics functionality should be capable of identifying the characteristics of a disaster derived from the message identifier of a received warning message in order to take appropriate action. + +# 9 Protocols and Protocol Architecture + +## 9.1 Requirements on Core Network and Radio Access Network + +### 9.1.1 GSM Radio Access Network + +Commands interpreted by the BSC will result in a sequence of 4 SMS BROADCAST REQUEST messages or 1 SMS BROADCAST COMMAND message being sent to a BTS, which in turn result in a sequence of 4 blocks each 22 octets long being transferred via the BTS-MS interface (see 3GPP TS 44.012 [7]). + +With the SMS BROADCAST REQUEST mode of operation, the 88 octet fixed length CBS page which is specified in subclause 9.3 is split into four 22 octet blocks which are carried in SMS BROADCAST REQUEST messages as follows: + +- octets 1-22 are transferred in the 1st SMS BROADCAST REQUEST +with a sequence number (see 3GPP TS 44.012 [7]) indicating first block; +- octets 23-44 are transferred in the 2nd SMS BROADCAST REQUEST +with a sequence number (see 3GPP TS 44.012 [7]) indicating second block; +- octets 45-66 are transferred in the 3rd SMS BROADCAST REQUEST +with a sequence number (see 3GPP TS 44.012 [7]) indicating third block; +- octets 67-88 are transferred in the 4th SMS BROADCAST REQUEST +with a sequence number (see 3GPP TS 44.012 [7]) indicating fourth block. + +Figure 3 illustrates the protocol architecture and the scope of the various GSM Specifications for the SMS BROADCAST REQUEST mode of operation. + + + +The diagram illustrates the protocol architecture for SMS BROADCAST REQUEST mode. It shows the following sequence of messages: + +- The CBC (Core Network) sends a **Write-Replace** message to the BSC (Base Station Controller). +- The BSC sends four **SMS BROADCAST REQUEST** messages (labeled 1, 2, 3, and 4) to the BTS (Base Transceiver Station). +- The BTS sends four corresponding blocks (labeled 1, 2, 3, and 4) to the MSs (Mobile Stations). +- The BSC sends a **Report-Success** message back to the CBC. + +The diagram is annotated with the following specifications: + +- TS 23.041 Section 9.2** (between CBC and BSC) +- TS 23.041 Section 9.4** (between BSC and BTS/MSs) +- TS 48.058** (between BSC and BTS) +- TS 44.012** (between BTS and MSs) + +Sequence diagram illustrating the protocol architecture for SMS BROADCAST REQUEST mode. The diagram shows interactions between CBC, BSC, BTS, and MSs. The CBC sends a Write-Replace message to the BSC. The BSC sends four SMS BROADCAST REQUEST messages (1-4) to the BTS. The BTS then sends four corresponding blocks (1-4) to the MSs. The BSC also sends a Report-Success message back to the CBC. The diagram is annotated with TS 23.041 Section 9.2, TS 23.041 Section 9.4, TS 48.058, and TS 44.012. + +Figure 3 + +With the SMS BROADCAST COMMAND mode of operation, the BSC sends to the BTS in one single message the 88 octet fixed length CBS page. The BTS then splits the page into four 22 octet blocks, adds the sequence number (see 3GPP TS 44.012 [7]) and transmits the four resulting blocks on the air. + +Figure 4 illustrates the protocol architecture and the scope of the various GSM Specifications for the SMS BROADCAST COMMAND mode of operation. + + + +``` +sequenceDiagram + participant CBC + participant BSC + participant BTS + participant MSs + + Note left of BSC: TS 23.041 Section 9.2 + Note right of BSC: TS 23.041 Section 9.4 + Note left of MSs: TS 48.058 + Note right of MSs: TS 44.012 + + CBC->>BSC: Write-Replace + BSC->>BTS: SMS BROADCAST COMMAND + Note right of BTS: 1 + BTS->>MSs: + Note right of BTS: 2 + BTS->>MSs: + Note right of BTS: 3 + BTS->>MSs: + Note right of BTS: 4 + BTS->>MSs: + BSC->>CBC: Report-Success +``` + +Sequence diagram showing the protocol architecture for SMS BROADCAST COMMAND mode. It involves four entities: CBC, BSC, BTS, and MSs. The diagram is divided into three sections based on 3GPP specifications: TS 23.041 Section 9.2 (between CBC and BSC), TS 23.041 Section 9.4 (between BSC and BTS), and TS 48.058 (between BSC and BTS). The sequence of messages is: 1. CBC sends 'Write-Replace' to BSC. 2. BSC sends 'SMS BROADCAST COMMAND' to BTS. 3. BTS transmits four blocks (labeled 1, 2, 3, 4) to MSs. 4. BSC sends 'Report-Success' back to CBC. + +Figure 4 + +### 9.1.2 UMTS Radio Access Network + +Commands interpreted by the RNC will result in one SMS BROADCAST COMMAND sent to the UE. The CBS messages are completely transparent to the Node B, i.e. no manipulation of the data like e.g. fragmentation is done at the Node B. + + + +``` + +sequenceDiagram + participant CBC + participant RNC + participant NODE-B + participant UEs + Note left of CBC: 3G TS 23.041 Section 9.2 + Note right of UEs: 3G TS 23.041 Section 9.4 + Note right of RNC: 3G TS 25.324 + CBC->>RNC: Write-Replace + RNC->>UEs: SMS BROADCAST COMMAND + UEs->>CBC: Report-Success + +``` + +Sequence diagram illustrating the Warning Message Delivery procedure. The diagram shows four lifelines: CBC, RNC, NODE-B, and UEs. The CBC sends a 'Write-Replace' message to the RNC. The RNC sends an 'SMS BROADCAST COMMAND' to the UEs. The UEs send a 'Report-Success' message back to the CBC. Above the diagram, three reference labels are shown with arrows pointing to specific parts of the sequence: '3G TS 23.041 Section 9.2' points to the Write-Replace message, '3G TS 23.041 Section 9.4' points to the SMS BROADCAST COMMAND message, and '3G TS 25.324' points to the Report-Success message. There is a red 'X' mark over the first reference label. + +Figure 4a + +### 9.1.3 Warning Message Delivery + +#### 9.1.3.1 General + +In GSM and UMTS, the cell broadcast service can be used to transfer CBS messages related to public warning. This requires reception of CBS messages to be permanently activated in the mobile terminal. + +Warning message delivery is similar to cell broadcast service. It permits a number of unacknowledged warning messages to be broadcast to MS/UEs within a particular area. Reception of warning messages is enabled as defined later on in this specification. + +3GPP TS 31.102 [18] defines a USIM data file for configuration of warning messages reception. In case of a non-existing or empty USIM data file, the MS/UE accepts all warning messages on all PLMNs. As specified in 3GPP TS 31.102 [18], the MS/UE can be configured to ignore all warning messages received in its HPLMN or in a PLMN equivalent to it. As specified in 3GPP TS 31.102 [18], the MS/UE can be configured to ignore all warning messages received in a VPLMN or in a PLMN equivalent to it. + +A UE in limited service state, and configured according to the USIM data file to display warning messages on that PLMN, shall display warning messages to the user. + +In GSM, an ETWS capable MS uses the procedure as outlined in subclause 9.1.3.2. See 3GPP TS 44.018 [26] and 3GPP TS 44.060 [27] for details on the radio interface. + +In UMTS, an ETWS capable UE uses the procedure as outlined in subclause 9.1.3.3. See 3GPP TS 25.331 [16] for details on the radio interface. + +In E-UTRAN, an ETWS capable UE or a CMAS capable UE uses the procedures as outlined in subclause 9.1.3.4. See 3GPP TS 36.331 [36] for details on the radio interface. + +In NG-RAN, an ETWS capable UE or a CMAS capable UE uses the procedures as outlined in subclause 9.1.3.5. See 3GPP TS 36.331 [36] and 3GPP TS 38.331 [48] for details on the radio interface. + +#### 9.1.3.2 Warning Message Delivery Procedure in GSM + +When a warning message is sent in GERAN, the following message flow applies. The warning message request from the CBE will trigger a broadcast of an ETWS emergency message (containing the ETWS Primary Notification) and/or a CBS message (constituting a Secondary Notification) on the radio interface. The ETWS emergency message is conveyed by the paging message which can invoke mobile terminals to start receiving CBS messages without MMI. Mobile stations invoked to start receiving CBS messages this way may stop receiving CBS messages (without MMI) after a predefined period of time. + + + +``` + +sequenceDiagram + participant MS + participant BSC as BSC / BTS + participant MS2 as MS + Note right of BSC: 1. Registration and Security procedures + MS->>BSC: 3. WRITE-REPLACE + BSC->>MS2: 4. PAGING + BSC->>MS2: 6. WRITE-REPLACE COMPLETE + MS2->>BSC: 7. ACK + +``` + +Sequence diagram illustrating the Warning message delivery procedure in GERAN. The diagram shows three lifelines: MS (Mobile Station), BSC / BTS (Base Station Controller / Base Transceiver Station), and MS (Mobile Station). The sequence starts with a registration and security procedure (1. Registration and Security procedures). The MS sends a WRITE-REPLACE message (3. WRITE-REPLACE) to the BSC / BTS. The BSC / BTS sends a PAGING message (4. PAGING) to the MS. The BSC / BTS sends a WRITE-REPLACE COMPLETE message (6. WRITE-REPLACE COMPLETE) to the MS. The MS sends a response (7. ACK) to the BSC / BTS. + +**Figure 9.1.3.2-1: Warning message delivery procedure in GERAN** + +1. Network registration and security procedures are performed. + +NOTE 1: This step is performed each time an MS is attached to a NW (e.g. after each power-on). + +2. CBE (e.g. Information Source such as PSAP or Regulator) sends emergency information ("warning type", "warning message", "impacted area", and "time period") to the CBC. The CBC shall authenticate this request. The "warning type" takes one of the following values: earthquake, tsunami, earthquake and tsunami, test, or other. + +3. Using the "impacted area information", the CBC identifies which BSCs need to be contacted and constructs the "Cell list" for the cells in which the information is to be broadcast. + +The CBC shall send a WRITE-REPLACE message to all the identified BSCs. If the emergency information received from the CBE contains warning information to be sent both in an ETWS emergency message and in a CBS message, then the CBC need to send this information in separate WRITE-REPLACE messages to the identified BSCs accordingly: + +7 - When containing an ETWS emergency message the WRITE-REPLACE message includes the "Paging ETWS Indicator" to differentiate it from a normal CBS message, as well as (among other parameters) the "Cell list", "warning type" (which constitutes a part of the ETWS Primary Notification message, see subclause 9.4.1.3), and the "warning period" parameter. + +8 - When containing a CBS message the WRITE-REPLACE message includes the "Channel Indicator" to differentiate it from an ETWS emergency message, as well as (among other parameters) the "Cell list", "Repetition Period", "No of Broadcasts Requested" and the "CBS Message Information" parameter(s). + +The CBC shall not include the "digital signature" or "timestamp" information. + +NOTE 2: Due to requirements in earlier versions of this document, it is possible for "digital signature" and "timestamp" information (included in the "Warning Security Information" parameter) to be transmitted within the WRITE-REPLACE message. + +4. The BSCs use the "Cell list" information to identify in which cells the warning message needs to be broadcasted. + +9 a) When the WRITE-REPLACE message contains an ETWS emergency message, the BSC/BTS: + +- 10 1) shall include the ETWS emergency message within the paging message and start sending the paging messages in all paging groups for the time duration requested by the CBC in the "warning period" parameter. The paging message contains the "ETWS indicator", based on the "Paging ETWS Indicator" received in the WRITE-REPLACE message, and the ETWS Primary Notification message as defined in subclause 9.4.1.3. When the "warning type" in the ETWS Primary Notification message is set to 'other', all of the warning information is included in the broadcasted CBS message. + - 11 2) may send the ETWS Primary Notification message in other messages (Application Information, see 3GPP TS 44.018 [26], and Packet Application Information, see 3GPP TS 44.060 [27]) in order to reach mobiles in connected mode. + - 12 b) When the WRITE-REPLACE message contains a CBS message the BSC/BTS shall start to broadcast the CBS message on the Cell Broadcast channel according to the "Repetition Period" and "No of Broadcasts Requested" requested by the CBC. +5. Upon reception of the paging message containing the ETWS Primary Notification message, if the MS is configured to accept warnings on that PLMN (see 3GPP TS 31.102 [18]) the ETWS capable MS alerts the user immediately as indicated by the "warning type" value, and starts reading the Cell Broadcast channel in order to acquire a possible broadcasted CBS message containing the Secondary Notification message. + +Upon reception of the CBS message containing the Secondary Notification message, the ETWS capable MS immediately indicates the contents of the Secondary Notification message to the user. + +NOTE 3: If the MS receives the same ETWS Primary Notification message more than once it silently discards the last received Primary Notification message. + +NOTE 4: When the "warning type" is set to 'test', the MS silently discards the ETWS Primary Notification message. The MS does not start reading the Cell Broadcast channel in this case. However, the MS specially designed for testing purposes can perform user alerting and proceed to the reception of the broadcasted CBS message as described above. + +NOTE 5: If the MS is configured to ignore warnings on that PLMN (see 3GPP TS 31.102 [18]), the MS does not try to acquire the broadcasted CBS message described above. + +The MS shall perform duplication detection of the received message as specified in subclause 8.2. + +The MS shall ignore the values of "digital signature" and "timestamp" if received in the "Warning Security Information" parameter. + +NOTE 2: Due to requirements in earlier versions of this document, it is possible for "digital signature" and "timestamp" information (included in the "Warning Security Information" parameter) to be transmitted within the WRITE-REPLACE message. + +6. The BSC sends a WRITE-REPLACE COMPLETE message to the CBC in response to the WRITE-REPLACE message. +7. CBC sends acknowledgement message to CBE. + +#### 9.1.3.3 Warning Message Delivery Procedure in UMTS + +When a warning message is sent in UTRAN, the following message flow applies. In this case, the paging message with a new emergency indication can invoke mobile terminals to start receiving CBS messages without MMI. Mobile stations invoked to start receiving CBS messages this way may stop receiving CBS messages (without MMI) after a period of time, which should not be less than 30 minutes in case DRX-Level-2 is used, and 2 minutes in case DRX-Level-1 is used. + + + +``` + +sequenceDiagram + participant CBE as CBE + participant SGSN as S G S N + participant RNC as R N C + participant NodeB as N o d e B + participant UE as U E + + Note over SGSN, RNC: 1. Registration and Security procedures + CBE->>RNC: 2. Write-Replace + RNC->>NodeB: 3. a. Broadcast information + NodeB->>UE: 3. b. Paging + NodeB->>RNC: 4. Report-Success + RNC->>CBE: 5. Ack + +``` + +Sequence diagram illustrating the Warning message delivery procedure in UTRAN. Lifelines: S G S N, R N C, N o d e B, U E. The sequence starts with '1. Registration and Security procedures' between S G S N and R N C. An arrow from the left (CBE) points to R N C with message '2. Write-Replace'. R N C sends '3. a. Broadcast information' to N o d e B, which then sends '3. b. Paging' to U E. N o d e B sends '4. Report-Success' back to R N C, which finally sends '5. Ack' back to the left. + +**Figure 9.1.3.3-1: Warning message delivery procedure in UTRAN** + +1. Network registration and security (e.g. mutual authentication) procedures are performed. + +NOTE 1: This step is performed each time a UE is attached to a network (e.g. after each power-on). + +2. CBE (e.g. Information Source such as PSAP or Regulator) sends emergency information ("warning type", "warning message", "impacted area", and "time period") to the CBC. The CBC shall authenticate this request. The "warning type" takes one of the following values: earthquake, tsunami, earthquake and tsunami, test, or other. + +3. Using the "impacted area information", the CBC identifies which RNCs need to be contacted and constructs the "Service Area ID list" for the cells in which the information is to be broadcast. + +The CBC shall send a WRITE-REPLACE message to all the identified RNCs. The message shall include an "emergency indication" to differentiate it from normal Cell Broadcast information, as well as the "Service Area ID list", "warning type", "warning message". + +The CBC shall not include the "digital signature" or "timestamp" information. + +NOTE 2: Due to requirements in earlier versions of this document, it is possible for "digital signature" and "timestamp" information to be transmitted within "warning message". + +4. The RNCs use the "Service Area ID list" information to identify which Node Bs they need to reach, and then, they relay information to them using the appropriate Iub interface message. + +5. The Node B receives the Iub message containing the emergency indication. As parallel actions, the RNC/Node B: + +13 a) shall start to broadcast the "warning message". This is broadcast by using a Cell Broadcast channel and modified System Information messages. This broadcast information is repeated continuously by the Node B for the "time period" requested by the CBE. + +14 b) shall use paging messages in every paging group to alert idle mode mobiles to receive the broadcast warning message. Typically these paging messages are repeated in all paging groups for several DRX periods. The paging message contains the "ETWS indication" based on the "warning type" information. When the "warning type" is set to 'other', all of the warning information is included in the broadcast "warning message". + +15 c) may send the "ETWS indication" in other messages (System Information Change Indication or ETWS Primary Notification With Security) in order to reach mobiles in connected mode. Inclusion of "ETWS indication" is the same as that of the paging message mentioned above. + +6. If the UE is configured to accept warnings on that PLMN (see 3GPP TS 31.102 [18]) the UE alerts the user immediately, using "warning type" value upon the reception of the "ETWS Indication". + +NOTE 3: If the UE received the "ETWS Indication" more than once it will silently discard the optional primary notification. + +NOTE 4: When the "warning type" is 'test', the UE silently discards the "ETWS Indication" and does not perform the reception of the broadcast message described below. However, the UE specially designed for testing purposes can perform user alerting described above and proceed to the reception of the broadcast message described below + +NOTE 5: If the UE is configured to ignore warnings on that PLMN (see 3GPP TS 31.102 [18]) the UE does not perform the reception of the broadcast message described below. + +Upon the reception of the "ETWS Indication", the UE activates the reception of the broadcast messages containing the "warning message" as the secondary notification. The UE indicates the contents of the "warning message" to the user. + +The UE shall perform duplication detection of the received message as specified in subclause 8.2. + +The UE shall ignore the values of "digital signature" and "timestamp" if received. + +NOTE 6: The "digital signature" and "timestamp" can be received due to requirements in earlier versions of this document. + +7. The RNC node sends a BMC REPORT-SUCCESS to the CBC in response to Write-Replace. +8. CBC sends acknowledgement message to CBE. + +#### 9.1.3.4 Warning Message Delivery Procedure in E-UTRAN + +##### 9.1.3.4.1 General + +The maximum size of the warning message for E-UTRAN is different from that for UTRAN/GERAN. + +When S1-flex is used, the eNodeB may receive duplicated warning messages. Duplicated messages can be detected by checking the message identifier and serial number fields and they shall not be transmitted on the radio interface. + +E-UTRA connected to both EPC and 5GCN (see 3GPP TS 36.300 [46]) may receive warning messages from both EPC and 5GCN. Duplicated messages can be detected by checking the message identifier and serial number fields and duplicate messages shall not be transmitted on the radio interface. + +##### 9.1.3.4.2 Warning Message Delivery Procedure + +The warning message to be broadcast is delivered via MMEs to multiple eNodeBs. The eNodeB(s) are responsible for scheduling the broadcast of the new message and the repetitions in each cell. + +The overall warning message delivery procedure is presented in figure 9.1.3.4.2-1: + + + +``` + +sequenceDiagram + participant CBE + participant CBC + participant MME + participant eNodeB + participant UE + + Note right of MME: 0. Registration procedures + CBE->>CBC: 1. Emergency Broadcast Request + CBC->>MME: 2. Write-Replace Warning Request + MME-->>CBC: 3. Write-Replace Warning Confirm + CBC-->>CBE: 4. Emergency Broadcast Response + MME->>eNodeB: 5. Write-Replace Warning Request + Note right of eNodeB: 6. Cell Broadcast delivery + eNodeB-->>MME: 6. Write-Replace Warning Response + Note right of UE: 7. User Alerting + MME-->>CBC: 8. Write-Replace Warning Indication + Note right of CBC: 9. Record success/failure of message delivery in trace record + +``` + +Sequence diagram of Warning message delivery procedure in E-UTRAN. Lifelines: CBE, CBC, MME, eNodeB, UE. The sequence starts with 0. Registration procedures (dashed box). 1. CBE sends Emergency Broadcast Request to CBC. 2. CBC sends Write-Replace Warning Request to MME. 3. MME sends Write-Replace Warning Confirm to CBC. 4. CBC sends Emergency Broadcast Response to CBE. 5. MME sends Write-Replace Warning Request to eNodeB. 6. eNodeB performs Cell Broadcast delivery (dashed box) and sends Write-Replace Warning Response to MME. 7. UE performs User Alerting (dashed box). 8. MME sends Write-Replace Warning Indication to CBC. 9. CBC records success/failure of message delivery in trace record (dashed box). + +**Figure 9.1.3.4.2-1: Warning message delivery procedure in E-UTRAN** + +0. Network registration and security (e.g. mutual authentication) procedures are performed. + +NOTE 1: This step is performed each time a UE is attached to a network (e.g. after each power on). + +1. CBE (e.g. Information Source such as PSAP or Regulator) sends emergency information (e.g. "warning type", "warning message", "impacted area", "time period") to the CBC. The CBC shall authenticate this request. + +NOTE 2: A warning message can include a language-independent content mapped to an event or a disaster that is compatible with texts used to describe user information contained in the content of a CBS-Message-Information-Page transparently passed from CBC to UEs if the ePWS language-independent content functionality (see subclause 8.3) is supported by CBE. + +2. Using the "impacted area" information, the CBC identifies which MMEs need to be contacted and determines the information to be place into the Warning Area List Information Element. The CBC sends a Write-Replace Warning Request message containing the warning message to be broadcast and the delivery attributes (Message identifier, Serial Number, list of TAIs, Warning Area List, OMC ID, CWM Indicator, Send Write-Replace-Warning-Indication, Global eNB ID, Warning Area Coordinates) to MMEs. + +The warning messages use the coding scheme for CBS data specified in 3GPP TS 23.038 [3]. + +The list of TAIs is only used by the MME. The MME uses it for selecting which eNodeBs to forward the Write-Replace Warning Request message to. + +If the Write-Replace Warning Request message is sent to reload cells served by an eNodeB, for which the CBC has previously received a Restart Indication (see subclause 15A.1 of TS 23.007 [38]), the CBC shall include the Global eNB ID IE with the identity of this eNodeB in the Write-Replace Warning Request message. + +The Warning Area List shall be a list of Cell IDs or a list of TAIs or one or more Emergency Area IDs. The Warning Area List is only used by the eNodeB. The eNodeB is configured with the TAI(s) and Cell ID(s) it serves and the Emergency Area ID(s) that it belongs to. The eNodeB checks for any match of the contents of the Warning Area List with these IDs to identify the cells where to distribute the warning message. The Warning Area List is an optional information element. If the Warning Area is absent, it shall be interpreted as "all cells on + +the eNodeB". The number of cell IDs will be limited by the message size on SBc and S1-MME. An Emergency Area ID is unique within the PLMN. + +The message may include an OMC ID. If present, it indicates the OMC to which the Trace record generated in step 9 is destined. Co-location of that OMC with the CBC is an operator option. + +CBC shall set the Concurrent Warning Message (CWM) indicator in all Write-Replace Warning Request messages, if the PLMN supports concurrent warning message broadcasts. + +The CBC shall not include the "digital signature" or "timestamp" information. + +CBC shall set the Send Write-Replace-Warning Indication element in case the MME is requested to forward the Broadcast Scheduled Area List in a Write-Replace Warning Indication for the warning message. + +NOTE 3: Due to requirements in earlier versions of the specification, it is possible that "digital signature" and "timestamp" information are transmitted within the "warning message". + +CBC includes the Warning Area Coordinates in the Write-Replace-Warning Request message based on operator policy. + +3. The MME sends a Write-Replace Warning Confirm message that indicates to the CBC that the MME has started to distribute the warning message to eNodeBs. + +The Write-Replace Warning Confirm message may contain the *Unknown Tracking Area List* IE. The *Unknown Tracking Area List* IE identifies the Tracking Areas that are unknown to the MME and where the Request cannot be delivered. + +If this message is not received by the CBC within an appropriate time period, the CBC can attempt to deliver the warning message via another MME in the same pool area. + +4. Upon reception of the Write-Replace Confirm messages from the MMEs, the CBC may confirm to the CBE that it has started to distribute the warning message. +5. The MME forwards Write-Replace Warning Message Request to eNodeBs. The MME shall use the list of TAIs to determine the eNodeBs in the delivery area. If the list of TAIs is not included and no Global eNB ID has been received from the CBC, the message is forwarded to all eNodeBs that are connected to the MME. If a Global eNB ID has been received from the CBC, the MME shall forward the message only to the eNodeB indicated by the Global eNB ID IE. +6. When S1-flex is used the eNodeB may receive same message from multiple MMEs. The eNodeB detects duplicate messages by checking the message identifier and serial number fields within the warning message. If any redundant messages are detected only the first one received will be broadcasted by the cells. The eNodeB shall use the Warning Area List information to determine the cell(s) in which the message is to be broadcast. The eNodeBs return a Distribute Warning Message Response to the MME, even if it was a duplicate. + +If there is a warning broadcast message already ongoing and the CWM Indicator is included in the Write-Replace Warning Message Request, the eNodeB does not stop existing broadcast message but start broadcasting the new message concurrently. Otherwise the eNodeB shall immediately replace the existing broadcast message with the newer one. + +NOTE 4: If concurrent warning messages are not supported, this requires the CBE/CBC to take care that 'lower' priority warnings are not sent while a higher priority warning is still being sent. + +The eNodeB broadcasts the message frequently according to the attributes set by the CBC that originated the warning message distribution. + +7. If the UE has been configured to receive warning messages, and the UE is configured to accept warnings on that PLMN (see 3GPP TS 31.102 [18]), then the UE proceeds as follows: + +The UE can use "warning type" values, 'earthquake', 'tsunami' or 'earthquake and tsunami', immediately to alert the user. When "warning type" is 'test', the UE silently discards the primary notification, but the UE specially designed for testing purposes may proceed with the following procedures. + +The UE activates reception of the broadcast messages containing the "warning message". + +If the Warning Area Coordinates are not present: + +☞16 The UE indicates the contents of the "warning message" to the user. + +If the Warning Area Coordinates are present, and if the UE is unable to determine its location: + +☞17 The UE indicates the contents of the "warning message" to the user. + +If the Warning Area Coordinates are present, and the UE determines it is inside the Warning Area Coordinates: + +☞18 The UE indicates the contents of the "warning message" to the user. + +If the Warning Area Coordinates are present, and the UE determines it is outside the Warning Area Coordinates: + +☞19 The UE does not indicate the contents of the "warning message" to the user. The UE shall store the "warning message" in the list of "warning messages" to be checked for geo-fencing during a UE implementation specific time which shall not be greater than 24 hours. Upon expiration of the UE implementation specific time, the UE shall remove the stored "warning message" from the list of "warning messages" to be checked for geo-fencing. + +If the "warning message" is a geo-fencing trigger message (see subclause 9.4.1.2.2), the UE shall, for each "warning message" stored at the UE in the list of "warning messages" to be checked for geo-fencing: + +☞20 - compare the Serial Number and Message Identifier combination of the stored "warning message" to the list of Serial Number and Message Identifier combinations included in the Warning Message Content IE (CB Data) of the geo-fencing trigger message and encoded as specified in ATIS-0700041 [47]; and + +☞21 - if: + +☞22 1) the Serial Number and Message Identifier combination of the stored "warning message" matches one of the Serial Number and Message Identifier combinations included in the geo-fencing trigger message; and + +☞23 2) the UE: + +☞24 a) is able to determine its location and determines it is inside the Warning Area Coordinates of the stored "warning message"; or + +☞25 b) is unable to determine its location, + +☞26 indicate the contents of the stored "warning message" to the user and remove the "warning message" from the list of "warning messages" to be checked for geo-fencing. + +If a language-independent content mapped to an event or a disaster (e.g. character such as Unicode based pictogram mapping to a disaster) is included as part of user information contained in the content of a CBS-Message-Information-Page transparently passed from CBC to UEs: + +☞27 - UEs with user interface which support the ePWS language-independent content functionality (see subclause 8.3) and which are capable of displaying text-based warning messages should be capable of displaying the entire warning message that they receive. + +**Editor's note [WI: ePWS, CR#203]: FFS on what character(s) such as Unicode based pictogram(s) are the language-independent content mapped to an event or a disaster.** + +8. If the Send Warning-Message-Indication parameter was present in the Write-Replace Warning Request and it is configured in the MME based on operator policy, the MME shall forward the Broadcast Scheduled Area Lists in a Write-Replace Warning Indication(s) to the CBC. The Broadcast Scheduled Area List shall contain the Broadcast Completed Area List the MME has received from the eNodeB. The MME may aggregate Broadcast Completed Area Lists it receives from eNodeBs. + +NOTE 5: Support for sending of Write-Replace Warning Indication(s) to the CBC is optional in the MME. + +9. From the Write-Replace Warning Response messages returned by eNodeB's the MME determines the success or failure of the delivery and creates a trace record. Any OMC ID received in step 2 is written to the trace record to permit the O&M system to deliver them to the desired destination. + +##### 9.1.3.4.3 Warning Message Cancel Procedure + +The cancel warning message delivery procedure takes place when CBE requests to stop the on-going broadcast of warning messages. + + + +``` + +sequenceDiagram + participant CBE + participant CBC + participant MME + participant eNodeB + participant UE + + Note right of MME: 8. Record success/failure of message delivery in trace record + Note right of eNodeB: 6. Stop Cell Broadcast delivery + + CBE->>CBC: 1. Stop Emergency Broadcast Request + CBC->>MME: 2. Stop Warning Request + MME->>CBC: 3. Stop Warning Confirm + CBC->>CBE: 4. Stop Emergency Broadcast Response + MME->>eNodeB: 5. Kill Request + eNodeB-->>UE: 6. Stop Cell Broadcast delivery + eNodeB->>MME: 6. Kill Response + MME->>CBC: 7. Stop Warning Indication + +``` + +Sequence diagram of the Warning message cancel procedure in E-UTRAN. The diagram shows five lifelines: CBE, CBC, MME, eNodeB, and UE. The sequence of messages is: 1. CBE sends Stop Emergency Broadcast Request to CBC; 2. CBC sends Stop Warning Request to MME; 3. MME sends Stop Warning Confirm to CBC; 4. CBC sends Stop Emergency Broadcast Response to CBE; 5. MME sends Kill Request to eNodeB; 6. eNodeB sends Stop Cell Broadcast delivery to UE (indicated by a dashed box); 6. eNodeB sends Kill Response to MME; 7. MME sends Stop Warning Indication to CBC; 8. MME records success/failure of message delivery in trace record (indicated by a dashed box). + +**Figure 9.1.3.4.3-1: Warning message cancel procedure in E-UTRAN** + +1. CBE initiates procedure by sending Stop Emergency Broadcast Request (e.g. "Message Identifier and Serial Number"), to the CBC. The CBC shall authenticate this request. +2. The CBC identifies which MMEs need to be contacted and determines the information to be place into the Warning Area Information Element. The CBC sends a Stop Warning Request message (Message Identifier, Serial Number, Tracking Area ID list, Warning Area, OMC ID, Send Stop Warning Indication) to MMEs. + +The message may include an OMC ID. If present, it indicates the OMC to which the Trace record generated in step 8 is destined. Co-location of that OMC with the CBC is an operator option. + +The CBC sets the Send Stop Warning Indication element in case the MME is requested to forward the Broadcast Completed Area List in a Stop Warning Indication for the warning message. + +3. The MME sends a Stop Warning Confirm message that indicates to the CBC that the MME has started to distribute the Kill Request message to eNodeBs. + +If this message is not received by the CBC within an appropriate time period, the CBC can attempt to send Stop Warning Request via another MME in the same pool area. + +4. Upon reception of the Stop Warning Confirm messages from the MMEs, the CBC may confirm to the CBE that it has initiated the Warning message cancel procedure. + +5. The MME forwards the request from the CBC by Kill Request to eNodeB's. The MME shall use the Tracking Area ID list to determine the eNodeBs that may have warning message broadcast ongoing. In case the Tracking Area ID list is not included the Kill Request is forwarded to all eNodeBs that are connected to the MME. + +6. The eNodeB shall stop broadcasting the warning message identified by the Message Identifier and Serial Number in the areas identified by Warning Area IDs. If the Warning Area is absent, it shall be interpreted as "all cells on the eNodeB"). + +When S1-Flex is used the eNodeB may receive same Kill Request from multiple MMEs, if any redundant Kill Requests are detected only the response to the first MME shall contain statistics related to the cancelled broadcast. + +7. If the Send Stop Warning Indication parameter was present in the Stop Warning Request and it is configured in the MME based on operator policy, the MME forwards the Broadcast Cancelled Area List it has received from the eNodeB in a Stop Warning Indication(s) to the CBC. The MME may aggregate Broadcast Cancelled Area Lists it receives from eNodeBs. + +If the CBC has requested the MME to send Stop Warning Indications, then the CBC releases the Serial Number of a message after it has stopped receiving the Stop Warning Indications for that message. + +NOTE: Support for Stop Warning Indication(s) is optional in the MME. + +8. From the Kill Response messages returned by eNodeB's the MME creates a trace record (e.g. number of times a particular message has been broadcasted in a given warning area) related to the cancelled message. Any OMC ID received in step 2 is written to the trace record to permit the O&M system to deliver them to the desired destination. + +#### 9.1.3.5 Warning Message Delivery Procedure in NG-RAN + +##### 9.1.3.5.1 General + +The maximum size of the warning message for NG-RAN is the same as the maximum size defined for E-UTRAN. + +When the CBCF sends warning messages to multiple AMFs for the same warning area, the gNodeB may receive duplicated warning messages. Duplicated messages can be detected by checking the message identifier and serial number fields and they shall not be transmitted on the radio interface. + +The Warning Message Delivery procedure messages and the Warning Message Cancel procedure messages are transported with the NonUeN2MessageTransfer service operation between CBCF and AMF (see clause 9A) and via N2 between AMF and NG-RAN. + +##### 9.1.3.5.2 Warning Message Delivery Procedure + +The warning message to be broadcast is delivered via AMFs to multiple NG-RAN nodes. The NG-RAN node(s) are responsible for scheduling the broadcast of the new message and the repetitions in each cell. + +The overall warning message delivery procedure is presented in figure 9.1.3.5.2-1: + + + +``` + +sequenceDiagram + participant CBE + participant CBCF/PWS-IWF + participant AMF + participant NG-RAN node + participant UE + + Note right of AMF: 0. Registration procedures + CBE->>CBCF/PWS-IWF: 1. Emergency Broadcast Request + CBCF/PWS-IWF->>AMF: 2. NonUeN2MessageTransfer (Write-Replace Warning Request NG-RAN) + AMF->>CBCF/PWS-IWF: 3. NonUeN2MessageTransfer (Write-Replace Warning Confirm NG-RAN) + CBCF/PWS-IWF->>CBE: 4. Emergency Broadcast Response + AMF->>NG-RAN node: 5. Write-Replace Warning Request + NG-RAN node->>AMF: 6. Write-Replace Warning Response + Note right of UE: 7. Cell Broadcast delivery + AMF->>CBCF/PWS-IWF: 8. NonUeN2InfoNotify (Write-Replace Warning Indication NG-RAN) + Note right of AMF: 9. Record success/failure of message delivery in trace record + +``` + +Sequence diagram of Warning message delivery procedure in NG-RAN. Lifelines: CBE, CBCF/PWS-IWF, AMF, NG-RAN node, UE. The sequence starts with 0. Registration procedures (dashed box). 1. CBE sends Emergency Broadcast Request to CBCF/PWS-IWF. 2. CBCF/PWS-IWF sends NonUeN2MessageTransfer (Write-Replace Warning Request NG-RAN) to AMF. 3. AMF sends NonUeN2MessageTransfer (Write-Replace Warning Confirm NG-RAN) back to CBCF/PWS-IWF. 4. CBCF/PWS-IWF sends Emergency Broadcast Response to CBE. 5. AMF sends Write-Replace Warning Request to NG-RAN node. 6. NG-RAN node sends Write-Replace Warning Response back to AMF. 7. NG-RAN node performs Cell Broadcast delivery to UE (dashed box). 8. AMF sends NonUeN2InfoNotify (Write-Replace Warning Indication NG-RAN) to CBCF/PWS-IWF. 9. AMF performs Record success/failure of message delivery in trace record (dashed box). + +**Figure 9.1.3.5.2-1: Warning message delivery procedure in NG-RAN** + +0. Network registration and security (e.g. mutual authentication) procedures are performed. + +NOTE 1: This step is performed each time a UE is attached to a network (e.g. after each power on). + +1. CBE (e.g. Information Source such as PSAP or Regulator) sends emergency information (e.g. "warning type", "warning message", "impacted area", "time period") to the CBC. The CBCF shall authenticate this request. + +NOTE 2: A warning message can include a language-independent content mapped to an event or a disaster that is compatible with texts used to describe user information contained in the content of a CBS-Message-Information-Page transparently passed from CBC to UEs if the ePWS language-independent content functionality (see subclause 8.3) is supported by CBE. + +2. Using the "impacted area" information, the CBCF identifies which AMFs need to be contacted and determines the information to be placed into the Warning Area List NG-RAN Information Element. The CBCF sends a Write-Replace Warning Request NG-RAN message containing the warning message to be broadcast and the delivery attributes (Message Identifier, Serial Number, list of NG-RAN TAIIs, Warning Area List NG-RAN, OMC ID, CWM Indicator, Send Write-Replace-Warning-Indication, Global RAN Node ID, Warning Area Coordinates) to AMFs. + +The warning messages use the coding scheme for CBS data specified in 3GPP TS 23.038 [3]. + +The list of NG-RAN TAIIs is only used by the AMF. The AMF uses it for selecting which NG-RAN node(s) to forward the Write-Replace Warning Request NG-RAN message to. + +If the Write-Replace Warning Request NG-RAN message is sent to reload cells served by a NG-RAN node, for which the CBCF has previously received a Restart Indication (see subclause 15A.1 of TS 23.007 [38]), the CBCF shall include the Global RAN Node ID IE with the identity of this NG-RAN node in the Write-Replace Warning Request NG-RAN message. + +The Warning Area List NG-RAN shall be a list of Cell IDs or a list of NG-RAN TAIIs or one or more Emergency Area IDs. The Warning Area List NG-RAN is only used by the NG-RAN node. The NG-RAN node + +is configured with the NG-RAN TAI(s) and Cell ID(s) it serves and the Emergency Area ID(s) that it belongs to. The NG-RAN node checks for any match of the contents of the Warning Area List NG-RAN with these IDs to identify the cells where to distribute the warning message. The Warning Area List NG-RAN is an optional information element. If the Warning Area List NG-RAN is absent, it shall be interpreted as "all cells on the NG-RAN node". The number of cell IDs will be limited by the message size on N50 and N2. An Emergency Area ID is unique within the PLMN. + +The message may include an OMC ID. If present, it indicates the OMC to which the Trace record generated in step 9 is destined. Co-location of that OMC with the CBCF is an operator option. + +The CBCF shall set the Concurrent Warning Message (CWM) indicator in all Write-Replace Warning Request NG-RAN messages, if the PLMN supports concurrent warning message broadcasts. + +The CBCF shall not include the "digital signature" or "timestamp" information. + +The CBCF shall set the Send Write-Replace-Warning Indication element in case the AMF is requested to forward the Broadcast Scheduled Area List in a Write-Replace Warning Indication NG-RAN for the warning message. + +The CBCF includes the Warning Area Coordinates in the Write-Replace-Warning-Request-NG-RAN message based on operator policy. + +3. The AMF sends a Write-Replace Warning Confirm NG-RAN message that indicates to the CBCF that the AMF has started to distribute the warning message to NG-RAN nodes. + +The Write-Replace Warning Confirm NG-RAN message may contain the *Unknown Tracking Area List* IE. The *Unknown Tracking Area List* IE identifies the Tracking Areas that are unknown to the AMF and where the Request cannot be delivered. + +If this message is not received by the CBCF within an appropriate time period, the CBCF can attempt to deliver the warning message via another AMF in the same AMF region. + +4. Upon reception of the Write-Replace Confirm NG-RAN messages from the AMFs, the CBCF may confirm to the CBE that it has started to distribute the warning message. +5. The AMF forwards Write-Replace Warning Message Request NG-RAN to NG-RAN nodes. The AMF shall use the list of NG-RAN TAIs to determine the NG-RAN nodes in the delivery area. If the list of NG-RAN TAIs is not included and no Global RAN Node ID has been received from the CBCF, the message is forwarded to all NG-RAN nodes that are connected to the AMF, subject to the RAT Selector NG-RAN. If a Global RAN Node ID has been received from the CBCF, the AMF shall forward the message only to the NG-RAN node indicated by the Global RAN Node ID IE. +6. When the CBCF sends warning messages to multiple AMFs for the same warning area, the NG-RAN node may receive the same message from multiple AMFs. The NG-RAN node detects duplicate messages by checking the message identifier and serial number fields within the warning message. If any redundant messages are detected only the first one received will be broadcasted by the cells. The NG-RAN node shall use the Warning Area List NG-RAN information to determine the cell(s) in which the message is to be broadcast. The NG-RAN nodes return a Write Replace Warning Message Response to the AMF, even if it was a duplicate. + +If there is a warning broadcast message already ongoing and the CWM Indicator is included in the Write-Replace Warning Request NG-RAN message, the NG-RAN node does not stop the existing broadcast message but starts broadcasting the new message concurrently. Otherwise the NG-RAN node shall immediately replace the existing broadcast message with the newer one. + +NOTE 3: If concurrent warning messages are not supported, this requires the CBE/CBCF to take care that 'lower' priority warnings are not sent while a higher priority warning is still being sent. + +The NG-RAN node broadcasts the message frequently according to the attributes set by the CBCF that originated the warning message distribution. + +7. If the UE has been configured to receive warning messages, and the UE is configured to accept warnings on that PLMN (see 3GPP TS 31.102 [18]), then the UE proceeds as follows: + +The UE can use "warning type" values, 'earthquake', 'tsunami' or 'earthquake and tsunami', immediately to alert the user. When "warning type" is 'test', the UE silently discards the primary notification, but the UE specially designed for testing purposes may proceed with the following procedures. + +The UE activates reception of the broadcast messages containing the "warning message". + +If the Warning Area Coordinates are not present: + +☞28 The UE indicates the contents of the "warning message" to the user. + +If the Warning Area Coordinates are present, and if the UE is unable to determine its location: + +☞29 The UE indicates the contents of the "warning message" to the user. + +If the Warning Area Coordinates are present, and the UE determines it is inside the Warning Area Coordinates: + +☞30 The UE indicates the contents of the "warning message" to the user. + +If the Warning Area Coordinates are present, and the UE determines it is outside the Warning Area Coordinates: + +☞31 The UE does not indicate the contents of the "warning message" to the user. The UE shall store the "warning message" in the list of "warning messages" to be checked for geo-fencing during a UE implementation specific time which shall not be greater than 24 hours. Upon expiration of the UE implementation specific time, the UE shall remove the stored "warning message" from the list of "warning messages" to be checked for geo-fencing. + +If the "warning message" is a geo-fencing trigger message (see subclause 9.4.1.2.2), the UE shall, for each "warning message" stored at the UE in the list of "warning messages" to be checked for geo-fencing: + +☞32 - compare the Serial Number and Message Identifier combination of the stored "warning message" to the list of Serial Number and Message Identifier combinations included in the Warning Message Content IE (CB Data) of the geo-fencing trigger message and encoded as specified in ATIS-0700041 [47]; and + +☞33 - if: + +☞34 1) the Serial Number and Message Identifier combination of the stored "warning message" matches one of the Serial Number and Message Identifier combinations included in the geo-fencing trigger message; and + +☞35 2) the UE: + +☞36 a) is able to determine its location and determines it is inside the Warning Area Coordinates of the stored "warning message"; or + +☞37 b) is unable to determine its location, + +☞38 indicate the contents of the stored "warning message" to the user and remove the "warning message" from the list of "warning messages" to be checked for geo-fencing. + +If a language-independent content mapped to an event or a disaster (e.g. character such as Unicode based pictogram mapping to a disaster) is included as part of user information contained in the content of a CBS-Message-Information-Page transparently passed from CBC to UEs: + +☞39 - UEs with user interface which support the ePWS language-independent content functionality (see subclause 8.3) and which are capable of displaying text-based warning messages should be capable of displaying the entire warning message that they receive. + +**Editor's note [WI: ePWS, CR#203]: FFS on what character(s) such as Unicode based pictogram(s) are the language-independent content mapped to an event or a disaster.** + +8. If the Send Warning-Message-Indication parameter was present in the Write-Replace Warning Request NG-RAN and it is configured in the AMF based on operator policy, the AMF shall forward the Broadcast Scheduled Area Lists in a Write-Replace Warning Indication(s) NG-RAN to the CBCF. The Broadcast Scheduled Area List shall contain the Broadcast Completed Area List the AMF has received from the NG-RAN node. The MME may aggregate Broadcast Completed Area Lists it receives from NG-RAN nodes. + +NOTE 4: Support for sending of Write-Replace Warning Indication(s) NG-RAN to the CBCF is optional in the AMF. + +9. From the Write-Replace Warning Response messages returned by NG-RAN nodes the AMF determines the success or failure of the delivery and creates a trace record. Any OMC ID received in step 2 is written to the trace record to permit the O&M system to deliver them to the desired destination. + +##### 9.1.3.5.3 Warning Message Cancel Procedure + +The cancel warning message delivery procedure takes place when CBE requests to stop the on-going broadcast of warning messages. + + + +``` + +sequenceDiagram + participant CBE + participant CBCF/PWS-IWF + participant AMF + participant NG-RAN node + participant UE + + Note right of AMF: 8. Record success/failure of message delivery in trace record + Note right of NG-RAN node: 6. Cancel Cell Broadcast delivery + + CBE->>CBCF/PWS-IWF: 1. Stop Emergency Broadcast Request + CBCF/PWS-IWF->>AMF: 2. NonUeN2MessageTransfer (Stop Warning Request NG-RAN) + AMF->>CBCF/PWS-IWF: 3. NonUeN2MessageTransfer (Stop Warning Confirm NG-RAN) + CBCF/PWS-IWF->>CBE: 4. Stop Emergency Broadcast Response + AMF->>NG-RAN node: 5. PWS Cancel Request + NG-RAN node->>UE: 6. Cancel Cell Broadcast delivery + NG-RAN node->>AMF: 6. PWS Cancel Response + AMF->>CBCF/PWS-IWF: 7. NonUeInfoNotify (Stop Warning Indication NG-RAN) + +``` + +Sequence diagram of the Warning message cancel procedure in NG-RAN. The diagram shows interactions between CBE, CBCF/PWS-IWF, AMF, NG-RAN node, and UE. The steps are: 1. CBE sends Stop Emergency Broadcast Request to CBCF/PWS-IWF; 2. CBCF/PWS-IWF sends NonUeN2MessageTransfer (Stop Warning Request NG-RAN) to AMF; 3. AMF sends NonUeN2MessageTransfer (Stop Warning Confirm NG-RAN) back to CBCF/PWS-IWF; 4. CBCF/PWS-IWF sends Stop Emergency Broadcast Response to CBE; 5. AMF sends PWS Cancel Request to NG-RAN node; 6. NG-RAN node sends Cancel Cell Broadcast delivery to UE (dashed box); 6. NG-RAN node sends PWS Cancel Response to AMF; 7. AMF sends NonUeInfoNotify (Stop Warning Indication NG-RAN) to CBCF/PWS-IWF; 8. AMF records success/failure of message delivery in trace record (dashed box). + +**Figure 9.1.3.5.3-1: Warning message cancel procedure in NG-RAN** + +1. CBE initiates procedure by sending Stop Emergency Broadcast Request (e.g. "Message Identifier and Serial Number"), to the CBCF. The CBCF shall authenticate this request. +2. The CBCF identifies which AMFs need to be contacted and determines the information to be placed into the Warning Area Information Element. The CBC sends a Stop Warning Request NG-RAN message (Message Identifier, Serial Number, Tracking Area ID list, Warning Area, OMC ID, Send Stop Warning Indication) to AMFs. + +The message may include an OMC ID. If present, it indicates the OMC to which the Trace record generated in step 8 is destined. Co-location of that OMC with the CBCF is an operator option. + +The CBCF sets the Send Stop Warning Indication element in case the AMF is requested to forward the Broadcast Completed Area List in a Stop Warning Indication NG-RAN for the warning message. + +3. The AMF sends a Stop Warning Confirm NG-RAN message that indicates to the CBCF that the AMF has started to distribute the Cancel Request message to NG-RAN nodes. + +If this message is not received by the CBCF within an appropriate time period, the CBCF can attempt to send Stop Warning Request NG-RAN via another AMF in the same AMF region. + +4. Upon reception of the Stop Warning Confirm NG-RAN messages from the AMFs, the CBCF may confirm to the CBE that it has initiated the Warning message cancel procedure. +5. The AMF forwards the request from the CBCF by a Cancel Request to NG-RAN nodes. The AMF shall use the Tracking Area ID list to determine the NG-RAN nodes that may have warning message broadcast ongoing. In case the Tracking Area ID list is not included the Cancel Request is forwarded to all NG-RAN nodes that are connected to the AMF, subject to the RAT Selector NG-RAN. +6. The NG-RAN node shall cancel broadcasting the warning message identified by the Message Identifier and Serial Number in the areas identified by Warning Area IDs. If the Warning Area is absent, it shall be interpreted as "all cells on the NG-RAN node". + +When the CBCF sends cancel messages to multiple AMFs for the same warning area, the NG-RAN node may receive same Cancel Request from multiple AMFs, if any redundant Cancel Requests are detected only the response to the first AMF shall contain statistics related to the cancelled broadcast. + +7. If the Send Stop Warning Indication parameter was present in the Stop Warning Request NG-RAN and it is configured in the AMF based on operator policy, the AMF forwards the Broadcast Cancelled Area List it has received from the NG-RAN node in a Stop Warning Indication(s) NG-RAN to the CBCF. The AMF may aggregate Broadcast Cancelled Area Lists it receives from NG-RAN nodes. + +If the CBCF has requested the AMF to send Stop Warning Indications NG-RAN, then the CBCF releases the Serial Number of a message after it has stopped receiving the Stop Warning Indications NG-RAN for that message. + +NOTE: Support for Stop Warning Indication(s) NG-RAN is optional in the AMF. + +8. From the Cancel Response messages returned by NG-RAN nodes the AMF creates a trace record (e.g. number of times a particular message has been broadcasted in a given warning area) related to the cancelled message. Any OMC ID received in step 2 is written to the trace record to permit the O&M system to deliver them to the desired destination. + +### 9.1.4 UMTS Protocol Overview + + + +The diagram illustrates the protocol stack for UMTS. It shows three columns representing different entities: UE (User Equipment), RNC (Radio Network Controller), and CBC (Core Network Controller). The UE column contains two boxes labeled 'CB Appl. 1' and 'CB Appl. 2'. The RNC column contains a box labeled 'CB Appl. 2/3' at the top, followed by a stack of four boxes labeled 'TCP/UDP', 'IP', 'L2', and 'L1' from top to bottom. The CBC column contains a box labeled 'CB Appl. 1' at the top, followed by a box labeled 'CB Appl. 3', and then a stack of three boxes labeled 'TCP/UDP', 'IP', 'L2', and 'L1' from top to bottom. Horizontal lines connect 'CB Appl. 1' in the UE to 'CB Appl. 1' in the CBC. Another horizontal line connects 'CB Appl. 2' in the UE to 'CB Appl. 2/3' in the RNC. A horizontal line connects 'CB Appl. 2/3' in the RNC to 'CB Appl. 3' in the CBC. A horizontal line labeled 'IuBC' connects the 'L1' box in the RNC to the 'L1' box in the CBC. + +Figure 5: UMTS Protocol Overview diagram showing the protocol stack for CB Appl. 1, CB Appl. 2, CB Appl. 3, and the RNC/CBC interface. + +Figure 5 + +### 9.1.5 E-UTRAN Protocol Overview + + + +The diagram illustrates the protocol stack for the CBC - eNodeB interface. It shows three main entities: eNodeB, MME, and CBC. The eNodeB stack consists of layers L1, L2, IP, SCTP, and S1-AP. The MME stack consists of layers L1, L2, IP, SCTP, and an 'Interworking' block containing S1-AP and SBc-AP. The CBC stack consists of layers L1, L2, IP, SCTP, and SBc-AP. Vertical lines connect the layers across entities: eNodeB S1-AP connects to MME S1-AP; MME SBc-AP connects to CBC SBc-AP. Horizontal lines connect the layers within each entity. Labels S1-MME, MME, SBc, and CBC are placed below the respective protocol stacks. + +Figure 9.1.5-1: CBC - eNodeB. Protocol stack diagram showing layers L1, L2, IP, SCTP, and S1-AP/SBc-AP between eNodeB, MME, and CBC. + +###### Legend: + +- SBc Application Protocol (SBc-AP): Application Layer Protocol between CBC and MME. This protocol supports transfer of warning messages. +- S1 Application Protocol (S1-AP): Application Layer Protocol between the eNodeB and the MME. +- SCTP for the control plane (SCTP): This protocol guarantees delivery of signalling messages between MME and eNodeB (S1). SCTP is defined in RFC 4960 [33]. + +Figure 9.1.5-1: CBC - eNodeB + +### 9.1.6 NG-RAN Protocol Overview + + + +The diagram illustrates the protocol stack for the CBCF - NG-RAN interface. It shows four main entities: NG-RAN, AMF, Namf, and CBCF. The NG-RAN stack consists of layers L1, L2, IP, SCTP, NG-AP, and NG-AP-CB (dashed box). The AMF stack consists of layers L1, L2, IP, SCTP, and a 'Relay' block containing NG-AP and HTTP/2. The Namf stack consists of layers L1, L2, IP, TCP, and HTTP/2. The CBCF stack consists of layers L1, L2, IP, TCP, and HTTP/2. Vertical lines connect the layers across entities: NG-RAN NG-AP connects to AMF NG-AP; AMF HTTP/2 connects to Namf HTTP/2; Namf HTTP/2 connects to CBCF HTTP/2. Horizontal lines connect the layers within each entity. Labels NG-RAN, N2, AMF, Namf, and CBCF are placed below the respective protocol stacks. + +Figure 9.1.6-1: CBCF - NG-RAN. Protocol stack diagram showing layers L1, L2, IP, SCTP, NG-AP/NG-AP-CB, HTTP/2, and TCP between NG-RAN, AMF, Namf, and CBCF. + +Figure 9.1.6-1: CBCF - NG-RAN + +###### Legend: + +- NG application protocol information for cell broadcast (NG-AP-CB): Subset of NG-AP information that the AMF relays between the AN and the CBCF. NG-AP-CB corresponds to a subset of NG-AP defined in 3GPP TS 38.413 [40]. +- NG application protocol (NGAP): Application layer protocol between the NG-RAN node and the AMF. The NGAP protocol is defined in 3GPP TS 38.413 [40]. +- SCTP for the control plane (SCTP): This protocol guarantees delivery of signalling messages between AMF and NG-RAN (N2). SCTP is defined in IETF RFC 4960 [33]. +- HTTP/2: Application layer protocol for Service based interface between AMF and CBCF. HTTP/2 is defined in IETF RFC 7540 [42]. + +NOTE: NG-RAN protocol stack for the case where AMF and CBC inter-connects via PWS-IWF is described in annex B.3. + +## 9.2 Requirements on the CBC-RAN, CBC-MME and CBCF-AMF interfaces + +### 9.2.0 General + +The requirements are described by primitives. The term primitive is used to indicate "an abstract, implementation independent interaction between a service user and a service provider" (see ITU-T Recommendation X.210 [12]). For the CBC-BSC/RNC/MME or CBCF-AMF interface, the service provider would be the protocol interconnecting the CBC and BSC/RNC/MME or the CBCF and AMF. A Primitive may therefore be viewed as an abstract, implementation independent request/indication or response/confirm interaction between the service user (CBC/CBCF or BSC/RNC/MME/AMF) and the service provider (protocol). A set of primitives for use between the CBC and BSC/RNC/MME and CBCF and AMF are specified appropriate to the functionality assigned to the CBC/CBCF and BSC/RNC/MME/AMF in clause 5 and clause 6. In order to allow future extensions to the primitives, where possible a primitive shall not be rejected because a parameter is not recognized; the recipient shall ignore the parameter in question and process the remainder of the primitive's parameters as usual. + +NOTE: The primitives for the CBCF-AMF interface are also applicable to the PWS-IWF – AMF interface, and the primitives for the CBC-MME interface are also applicable to the CBC-PWS-IWF interface. + +The following table gives an overview over the existing primitives: + +| Name | Originator | Type | Reference | +|-----------------------------------------|--------------|--------------------|-----------| +| WRITE-REPLACE | CBC | Request/Indication | 9.2.2 | +| KILL | CBC | Request/Indication | 9.2.3 | +| REPORT | BSC/RNC | Response/Confirm | 9.2.4 | +| STATUS-LOAD-QUERY | CBC | Request/Indication | 9.2.5 | +| STATUS-LOAD-QUERY | BSC/RNC | Response/Confirm | 9.2.6 | +| STATUS-MESSAGE-QUERY | CBC | Request/Indication | 9.2.7 | +| STATUS-MESSAGE-QUERY | BSC/RNC | Response/Confirm | 9.2.8 | +| REJECT | BSC/RNC | Response/Confirm | 9.2.9 | +| RESTART-INDICATION | BSC/RNC | Request/Indication | 9.2.10 | +| RESET | CBC | Request/Indication | 9.2.11 | +| FAILURE-INDICATION | BSC/RNC | Request/Indication | 9.2.12 | +| SET-DRX | CBC | Request/Indication | 9.2.13 | +| SET-DRX-REPORT | BSC | Response/Confirm | 9.2.14 | +| WRITE-REPLACE-WARNING-REQUEST | CBC | Request/Indication | 9.2.16 | +| WRITE-REPLACE-WARNING-CONFIRM | MME | Response/Confirm | 9.2.17 | +| STOP-WARNING-REQUEST | CBC | Request/Indication | 9.2.18 | +| STOP-WARNING-CONFIRM | MME | Response/Confirm | 9.2.19 | +| WRITE-REPLACE-WARNING-INDICATION | MME | Request/Indication | 9.2.20 | +| STOP-WARNING-INDICATION | MME | Request/Indication | 9.2.21 | +| RESTART-INDICATION-E-UTRAN | MME | Request/Indication | 9.2.22 | +| FAILURE-INDICATION-E-UTRAN | MME | Request/Indication | 9.2.23 | +| RESET-COMPLETE | BSC/RNC | Response/Confirm | 9.2.24 | +| RESET-FAILURE | BSC/RNC | Response/Confirm | 9.2.25 | +| WRITE-REPLACE-WARNING-REQUEST-NG-RAN | CBCF/PWS-IWF | Request/Indication | 9.2.26 | +| WRITE-REPLACE-WARNING-CONFIRM-NG-RAN | AMF | Response/Confirm | 9.2.27 | +| STOP-WARNING-REQUEST-NG-RAN | CBCF/PWS-IWF | Request/Indication | 9.2.28 | +| STOP-WARNING-CONFIRM-NG-RAN | AMF | Response/Confirm | 9.2.29 | +| WRITE-REPLACE-WARNING-INDICATION-NG-RAN | AMF | Request/Indication | 9.2.30 | +| STOP-WARNING-INDICATION-NG-RAN | AMF | Request/Indication | 9.2.31 | +| RESTART-INDICATION-NG-RAN | AMF | Request/Indication | 9.2.32 | +| FAILURE-INDICATION-NG-RAN | AMF | Request/Indication | 9.2.33 | + +In GSM the CBC is integrated into the Core Network. The protocol between the CBC and BSC is defined in 3GPP TS 48.049 [30]. + +In UMTS the CBC is integrated into the Core Network. The protocol between the CBC and RNC is defined in 3GPP TS 25.419 [29]. + +In E-UTRAN the CBC is integrated into the Core Network. The protocol between the CBC and MME is defined in 3GPP TS 29.168 [35]. + +In NG-RAN the CBCF/PWS-IWF is integrated into the Core Network. The protocol between the CBCF/PWS-IWF and AMF is defined in 3GPP TS 29.518 [41]. + +NOTE 1: The primitives used in NG-RAN are transported with the NonUeN2MessageTransfer and NonUeN2InfoNotfy service operations between CBCF and the AMF (see clause 9A) and via N2 from AMF to NG-RAN. + +NOTE 2: In the following definitions, M indicates "mandatory parameter", O indicates "optional parameter" and C indicates "conditional parameter". + +### 9.2.1 Identification of a CBS message + +In GSM within a CBC-BSC interface, a CBS message is uniquely identified by the quartet (Message Identifier, Serial Number, Cell Identifier, Channel Indicator). + +In UMTS within the CBC-RNC interface, in E-UTRAN within the CBC-MME interface, and in NG-RAN within the CBCF-AMF interface and CBC – PWS-IWF interface, a CBS message is uniquely identified by the triplet (Message Identifier, Serial Number, Cell Identifier). + +This means that even when two CBS messages have the same semantic contents (for example the same weather forecast) but in different languages or coding schemes, they are considered as different and must therefore be identified by a different quartet. + +The Serial Number (Old-Serial-Number or New-Serial-Number) is managed cyclically and therefore this does not prevent the re-use of the same quartet for a different CBS message when the serial number have been incremented a sufficient number of times. How to manage the ambiguity is described subsequently. + +This unique identification of a CBS message across the CBC-BSC interface is used in all the primitives defined hereafter. This means that the quartet/triplet will be implicitly or explicitly present in every interface primitive which applies to a given CBS message. + +This unique quartet/triplet will be referred in the rest of the document as the "message reference". + +### 9.2.2 WRITE-REPLACE Request/Indication + +| PARAMETER | REFERENCE | PRESENCE (UMTS/GSM) | +|--------------------------------------|-----------|---------------------| +| Message-Identifier | 9.3.1 | M/M | +| Old-Serial-Number | 9.3.2 | O/O | +| New-Serial-Number | 9.3.3 | M/M | +| Cell-List | 9.3.5.1 | M/M | +| GSM only [Channel Indicator | 9.3.6 | O] (note 1) | +| Category | 9.3.7 | O/C (note 2) | +| Repetition-Period | 9.3.8 | M/C (note 2) | +| No-of-Broadcasts-Requested | 9.3.9 | M/C (note 2) | +| Number-of-Pages | 9.3.4 | M/C (note 2) | +| Data Coding Scheme | 9.3.18 | M/C (note 2) | +| CBS-Message-Information-Page 1 | 9.3.19 | M/C (note 2) | +| CBS-Message-Information-Length 1 | 9.3.20 | M/C (note 2) | +| CBS-Message-Information-Page 2 | 9.3.19 | O/O | +| CBS-Message-Information-Length 2 | 9.3.20 | O/O | +| : | | : | +| CBS-Message-Information-Page n | 9.3.19 | O/O | +| CBS-Message-Information-Length n | 9.3.20 | O/O | +| Paging-ETWS-Indicator | 9.3.23 | O/O (note 1) | +| Warning-Type | 9.3.24 | O/C (note 3) | +| Warning-Security-Information | 9.3.25 | O/C (note 3) | +| GSM only [Warning Period | 9.3.26 | C] (note 3) | +| UMTS only [Broadcast Message Content | 9.3.48 | O] (note 4) | +| Validity Indicator | | | + +NOTE 1: Only one of these two optional parameters may be simultaneously present in the primitive. The *Channel Indicator* parameter is included if the primitive contains a CBS message. The *Paging-ETWS-Indicator* parameter is included if the primitive contains an ETWS emergency message. + +NOTE 2: In GSM this parameter is included if the *Channel Indicator* parameter is present in the primitive. + +NOTE 3: In GSM this parameter is included if the *Paging-ETWS-Indicator* parameter is present in the primitive. + +NOTE 4: In UMTS this parameter is included if the *Broadcast Message Content IE* present in the primitive *does not contain any valid information*. + +This primitive is sent by the CBC to the BSC/RNC. As this primitive can be used either to broadcast a new CBS message or replace a CBS message already broadcast, the CBC will use the presence and content of the Old-Serial-Number and New-Serial-Number fields in this primitive to instruct the BSC/RNC as follows: + +a) Old-Serial-Number not present/New-Serial-Number present: + +- ▣40 - This is a write request which will be interpreted by the BSC/RNC as an instruction to broadcast a new CBS message in all the cells of the Cell list. +- ▣41 - GSM only [The CBS message will be broadcasted on the channel derived by the Channel Indicator (see the clause on parameters that describes the implicit value of the Channel Indicator when not present in the CBS message)]. +- ▣42 The following table identifies the BSC/RNC's behaviour: + +| Success/Failure of write request | BSC/RNC behaviour | +|----------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Success | The BSC/RNC completes the following parameters to be returned in the Report PDU:
- • a '0' value is entered in the number of broadcasts completed list for the cell
- • no entry is made in the failure list for the cell
- • no entry is made in the number of broadcasts completed list for the cell
- • an entry is made in the failure list for the new CBS message identifying the failure cause for the cell
- • Write successful: the BSC/RNC completes the following parameters to be returned in the Report PDU:
- • An entry is made in the number of broadcasts completed list for the cell.
- • No entry is made in the failure list for the cell.
- • Write unsuccessful: the BSC/RNC completes the following parameters to be returned in the Report PDU:
- • An entry is made in the number of broadcasts completed list for the cell.
- • An entry is made in the failure list for the new CBS message identifying the failure cause for the cell.
- • no entry is made in the number of completed broadcasts list.
- • an entry is made for the old CBS message in the failure list identifying the failure cause for the cell.
octet 50 | + +Year (octet 1, bits 1-8): This field uses the same format as the Year field used in the TP-Service-Centre-Time-Stamp, which is defined in 3GPP TS 23.040 [4]. + +Month (octet 2, bits 1-8): This field uses the same format as the Month field used in the TP-Service-Centre-Time-Stamp, which is defined in 3GPP TS 23.040 [4]. + +Day (octet 3, bits 1-8): This field uses the same format as the Day field used in the TP-Service-Centre-Time-Stamp, which is defined in 3GPP TS 23.040 [4]. + +Hour (octet 4, bits 1-8): This field uses the same format as the Hour field used in the TP-Service-Centre-Time-Stamp, which is defined in 3GPP TS 23.040 [4]. + +Minute (octet 5, bits 1-8): This field uses the same format as the Minute field used in the TP-Service-Centre-Time-Stamp, which is defined in 3GPP TS 23.040 [4]. + +Second (octet 6, bits 1-8): This field uses the same format as the Second field used in the TP-Service-Centre-Time-Stamp, which is defined in 3GPP TS 23.040 [4]. + +Time Zone (octet 7, bits 1-8): This field uses the same format as the Time Zone field used in the TP-Service-Centre-Time-Stamp, which is defined in 3GPP TS 23.040 [4]. + +Digital Signature (octet 8 - 50, bits 1-8): This field contains the 43 byte digital signature. + +### 9.3.26 Warning Period + +This parameter indicates the length of the period during which the ETWS emergency message is to be broadcasted in the BSC. This parameter is applicable for GSM only. + +### 9.3.27 Broadcast Message Type + +This parameter is applicable for GSM only. + +It indicates if the primitive including this parameter is referring to: + +- CBS message broadcasting; or +- ETWS emergency message broadcasting. + +### 9.3.28 Message Type + +This parameter is applicable for E-UTRAN and NG-RAN only. + +The *Message Type* IE uniquely identifies the message being sent; see 3GPP TS 29.168 [35] for E-UTRAN and 3GPP TS 29.518 [41] for NG-RAN. + +### 9.3.29 List of TAs + +This parameter is applicable for E-UTRAN only. + +The *Tracking Area ID List* IE is used to uniquely identify a Tracking Area; see 3GPP TS 36.413 [36] for E-UTRAN. + +### 9.3.30 Warning Area List + +This parameter is applicable for E-UTRAN only. + +The *Warning Area List* IE indicates the areas where the warning message needs to be broadcast. The *Warning Area List* consists of a Cell ID list (see subclause 9.3.5) or a TAI list (see subclause 9.3.29) or an Emergency Area ID list; see subclause 9.3.47. + +### 9.3.31 OMC ID + +This parameter is applicable for E-UTRAN and NG-RAN only. + +The *OMC ID* IE indicates the identity of an Operation and Maintenance Centre to which Trace Records shall be sent. This element consists of a string of maximum 20 octets; see 3GPP TS 29.168 [35] for E-UTRAN and 3GPP TS 29.518 [41] for NG-RAN. + +### 9.3.32 Concurrent Warning Message Indicator + +This parameter is applicable for E-UTRAN and NG-RAN only. + +The *Concurrent Warning Message Indicator* IE indicates to eNB that the received warning message is a new message to be scheduled for concurrent broadcast with any other ongoing broadcast of warning messages. This element is an enumerated type; see 3GPP TS 36.413 [36] for E-UTRAN and 3GPP TS 38.413 [40] for NG-RAN. + +NOTE: The Concurrent Warning Message Indicator IE is always present for non-ETWS (eg. CMAS) messages. The Concurrent Warning Message Indicator is not applicable for ETWS. + +### 9.3.33 Cause-E-UTRAN + +This parameter is applicable for E-UTRAN only. + +The purpose of the *Cause E-UTRAN* IE is to indicate the reason for a particular event for the SBc-AP protocol. This element is an integer; see 3GPP TS 29.168 [35]. + +### 9.3.34 Criticality Diagnostics + +This parameter is applicable for E-UTRAN and NG-RAN only. + +The *Criticality Diagnostics* IE is sent by the MME/AMF when parts of a received message have not been comprehended or were missing, or if the message contained logical errors. When applicable, it contains information about which IEs were not comprehended or were missing; see 3GPP TS 29.168 [35] for E-UTRAN and 3GPP TS 29.518 [41] for NG-RAN. + +### 9.3.35 Warning Message Content E-UTRAN + +This parameter is applicable for E-UTRAN only. + +The *Warning Message Content E-UTRAN* IE contains user information, e.g., the message with warning contents, and will be broadcast over the radio interface. This element is a string of maximum 9600 octets; see 3GPP TS 36.413 [36]. + +NOTE: If the ePWS language-independent content functionality (see subclause 8.3) is supported by CBE, a user information can include a language-independent content mapped to an event or a disaster that is compatible with texts used to describe user information contained in the content of a CBS-Message-Information-Page transparently passed from CBC to UEs. + +The content of *Warning Message Content E-UTRAN* IE consists of the following parameters: + +| PARAMETER | REFERENCE | PRESENCE | +|----------------------------------|-----------|----------| +| Number-of-Pages | 9.3.4 | M | +| CBS-Message-Information-Page 1 | 9.3.19 | M | +| CBS-Message-Information-Length 1 | 9.3.20 | M | +| CBS-Message-Information-Page 2 | 9.3.19 | O | +| CBS-Message-Information-Length 2 | 9.3.20 | O | +| ... | | : | +| CBS-Message-Information-Page n | 9.3.19 | O | +| CBS-Message-Information-Length n | 9.3.20 | O | + +NOTE: n equal to or less than 15 + +### 9.3.36 Repetition-Period E-UTRAN + +This parameter is applicable for E-UTRAN only. + +The *Repetition Period E-UTRAN* IE indicates the periodicity in seconds of the warning message to be broadcast. This element is an integer with a value between 0 and 4095; see 3GPP TS 36.413 [36]. + +### 9.3.37 Extended Repetition-Period + +This parameter is applicable for E-UTRAN only. + +The *Extended Repetition-Period* IE indicates the periodicity in seconds of the warning message to be broadcast. This IE is used if the Repetition Period has a value larger than 4095 and is an integer between 4096 and $(2^{17}-1)$ ; see 3GPP TS 36.413 [36] for E-UTRAN. + +### 9.3.38 Unknown Tracking Area List + +This parameter is applicable for E-UTRAN and NG-RAN only. + +The *Unknown Tracking Area List* IE identifies the Tracking Areas that are unknown to the MME/AMF and where the Request cannot be delivered. This IE is of type List of TAI (see subclause 9.3.29). + +This IE shall not be included if the Cause IE indicates *Tracking area not valid*. The Cause IE indicating *Tracking area not valid* is used when all Tracking Areas in the Request are invalid. + +### 9.3.39 Send Write-Replace-Warning-Indication + +This parameter is applicable for E-UTRAN and NG-RAN only. + +For E-UTRAN: + +The *Send Write-Replace-Warning-Indication* IE indicates to the MME that the MME shall send the WRITE-REPLACE WARNING INDICATION to the CBC for the warning message. This element is an enumerated type; see 3GPP TS 29.168 [35]. + +For NG-RAN: + +The *Send Write-Replace-Warning-Indication* IE indicates to the AMF that the AMF shall send the WRITE-REPLACE WARNING INDICATION-NG-RAN to the CBCF for the warning message. This element is an enumerated type; see 3GPP TS 29.518 [41]. + +### 9.3.40 Broadcast Scheduled Area List + +This parameter is applicable for E-UTRAN and NG-RAN only. + +The *Broadcast Scheduled Area List* IE indicates the areas where initiation of a broadcast was performed successfully. A Broadcast Scheduled Area List is received by the MME/AMF from an eNodeB/NG-RAN node as Broadcast Completed Area List; see 3GPP TS 36.413 [36] for E-UTRAN and 3GPP TS 38.413 [40] for NG-RAN. + +### 9.3.41 Send Stop Warning Indication + +This parameter is applicable for E-UTRAN and NG-RAN only. + +For E-UTRAN: + +The *Send Stop Warning Indication* IE is an indication for the MME to send the STOP-WARNING-INDICATION to the CBC for the warning message. This element is an enumerated type; see 3GPP TS 29.168 [35]. + +For NG-RAN: + +The *Send Stop Warning Indication* IE is an indication for the AMF to send the STOP-WARNING-INDICATION-NG-RAN to the CBCF for the warning message. This element is an enumerated type; see 3GPP TS 29.518 [41]. + +### 9.3.42 Broadcast Cancelled Area List + +This parameter is applicable for E-UTRAN and NG-RAN only. + +The *Broadcast Cancelled Area List* IE indicates the areas where broadcast was stopped successfully; see 3GPP TS 36.413 [36] for E-UTRAN and 3GPP TS 38.413 [40] for NG-RAN. + +### 9.3.43 Stop-All Indicator + +This parameter is applicable for E-UTRAN and NG-RAN only. + +For E-UTRAN: + +The *Stop-All Indicator* IE in the STOP-WARNING-REQUEST is sent by the MME to the eNodeB in the Kill Request (see 3GPP TS 36.413 [36]). This is to indicate to the eNB that the *Message Identifier* IE and the *Serial Number* IE in the Kill Request shall be ignored and the request applies to all messages in the Warning Area. + +NOTE 1: The CBC may use the *Message Identifier* IE and/or the *Serial Number* IE to associate the STOP-WARNING-INDICATION and the STOP-WARNING-RESPONSE with the STOP-WARNING-REQUEST. + +The *Stop-All Indicator* IE is an enumerated type; see 3GPP TS 29.168 [35]. + +For NG-RAN: + +The *Stop-All Indicator* IE in the STOP-WARNING-REQUEST-NG-RAN is sent by the AMF to the NG-RAN node in the Cancel Request (see 3GPP TS 38.413 [40]). This is to indicate to the NG-RAN node that the *Message Identifier* IE and the *Serial Number* IE in the Cancel Request shall be ignored and the request applies to all messages in the Warning Area. + +NOTE 2: The CBCF may use the *Message Identifier* IE and/or the *Serial Number* IE to associate the STOP-WARNING-INDICATION-NG-RAN and the STOP-WARNING-RESPONSE-NG-RAN with the STOP-WARNING-REQUEST-NG-RAN. + +The *Stop-All Indicator* IE is an enumerated type; see 3GPP TS 29.518 [41]. + +### 9.3.44 Broadcast Empty Area List + +This parameter is applicable for E-UTRAN and NG-RAN only. + +For E-UTRAN: + +The *Broadcast Empty Area List* IE contains a list of the eNodeB IDs (see subclause 9.3.46) of eNodeBs that have responded to the the MME with a KILL RESPONSE message in which the *Broadcast Cancelled Area List* IE was not included (see 3GPP TS 36.413 [34]). The MME may aggregate eNodeB IDs into the Broadcast Empty Area List. + +For NG-RAN: + +The *Broadcast Empty Area List* IE contains a list of the RAN Node IDs (see subclause 9.3.53) of NG-RAN nodes that have responded to the the AMF with a CANCEL RESPONSE message in which the *Broadcast Cancelled Area List* IE + +was not included (see 3GPP TS 38.413 [40]). The AMF may aggregate NG-RAN node IDs into the Broadcast Empty Area List. + +### 9.3.45 Restarted-Cell-List + +This parameter is applicable for E-UTRAN and NG-RAN only. + +The *Restarted-Cell-List* IE lists the cells which have restarted and where warning messages have been stopped if any were ongoing. See 3GPP TS 36.413 [36] for E-UTRAN and 3GPP TS 38.413 [40] for NG-RAN. + +### 9.3.46 Global eNB ID + +This parameter is applicable for E-UTRAN only. + +The *Global eNB ID* IE is used to globally identify an eNB. See 3GPP TS 36.413 [36]. + +### 9.3.47 Emergency Area ID List + +This parameter is applicable for E-UTRAN and NG-RAN only. + +The *Emergency Area ID List* IE is used to indicate the area which has the emergency impact; see 3GPP TS 36.413 [36] for E-UTRAN and 3GPP TS 38.413 [40] for NG-RAN. + +### 9.3.48 Broadcast Message Content Validity Indicator + +This parameter is applicable for UMTS only. + +The *Broadcast Message Content Validity Indicator* IE if included in the WRITE-REPLACE message indicates that the Broadcast Message Content IE does not contain any valid information and is to be ignored. This element is an enumerated type; see 3GPP TS 25.419 [29]. + +### 9.3.49 Failed-Cell-List + +This parameter is applicable for E-UTRAN and NG-RAN only. + +The *Failed-Cell-List* IE lists the cells where ongoing PWS operation has failed. See 3GPP TS 36.413 [36] for E-UTRAN and 3GPP TS 38.413 [40] for NG-RAN. + +### 9.3.50 Cause-NG-RAN + +This parameter is applicable for NG-RAN only. + +The purpose of the *Cause-NG-RAN* IE is to indicate the reason for a particular event for the N50 protocol. This element is an integer; see 3GPP TS 29.518 [41]. + +### 9.3.51 Warning Message Content NG-RAN + +This parameter is applicable for NG-RAN only. + +The *Warning Message Content NG-RAN* IE contains user information, e.g., the message with warning contents, and will be broadcast over the radio interface. This element is a string of maximum 9600 octets; see 3GPP TS 38.413 [40]. + +NOTE: If the ePWS language-independent content functionality (clause 8.3) is supported by CBE, a user information can include a language-independent content mapped to an event or a disaster that is compatible with texts used to describe user information contained in the content of a CBS-Message-Information-Page transparently passed from CBC to UEs. + +The content of *Warning Message Content NG-RAN* IE consists of the following parameters: + +| PARAMETER | REFERENCE | PRESENCE | +|----------------------------------|-----------|----------| +| Number-of-Pages | 9.3.4 | M | +| CBS-Message-Information-Page 1 | 9.3.19 | M | +| CBS-Message-Information-Length 1 | 9.3.20 | M | +| CBS-Message-Information-Page 2 | 9.3.19 | O | +| CBS-Message-Information-Length 2 | 9.3.20 | O | +| ... | | : | +| CBS-Message-Information-Page n | 9.3.19 | O | +| CBS-Message-Information-Length n | 9.3.20 | O | + +NOTE: n equal to or less than 15 + +### 9.3.52 Repetition-Period NG-RAN + +This parameter is applicable for NG-RAN only. + +The *Repetition Period NG-RAN* IE indicates the periodicity in seconds of the warning message to be broadcast. This element is an integer with a value between 0 and $2^{17}-1$ ; see 3GPP TS 38.413 [40]. + +### 9.3.53 Global RAN Node ID + +This parameter is applicable for NG-RAN only. + +The *Global RAN Node ID* IE is used to globally identify a NG-RAN node (i.e. a Global gNB ID or a Global ng-eNB ID). See 3GPP TS 38.413 [40]. + +### 9.3.54 List of NG-RAN TAIIs + +This parameter is applicable for NG-RAN only. + +The *List of NG-RAN TAIIs* IE is used to uniquely identify NG-RAN Tracking Areas; see 3GPP TS 38.413 [40]. + +### 9.3.55 Warning Area List NG-RAN + +This parameter is applicable for NG-RAN only. + +The *Warning Area List NG-RAN* IE indicates the areas where the warning message needs to be broadcast. The *Warning Area List NG-RAN* consists of a Cell ID list (see subclause 9.3.5) or a NG-RAN TAI list (see subclause 9.3.54) or an Emergency Area ID list; see subclause 9.3.47. + +### 9.3.56 RAT Selector NG-RAN + +This parameter is applicable for NG-RAN only. + +The *RAT Selector NG-RAN* IE shall be present to indicate to the AMF if the request shall be distributed to attached ng-eNBs or to gNBs. See 3GPP TS 29.518 [41]. + +NOTE: The CBC and the AMF do not support handling of concurrent responses from ng-eNBs and gNBs for the same request. + +### 9.3.57 Unknown NG-RAN Tracking Area List + +This parameter is applicable for NG-RAN only. + +The *Unknown NG-RAN Tracking Area List* IE identifies the Tracking Areas that are unknown to the AMF and where the request cannot be delivered. This IE is of type List of NG-RAN TAIIs (see subclause 9.3.54). + +This IE shall not be included if the Cause IE indicates *Tracking area not valid*. The Cause IE indicating *Tracking area not valid* is used when all Tracking Areas in the request are invalid. + +### 9.3.58 Broadcast Scheduled Area List NG-RAN + +This parameter is applicable for NG-RAN only. + +The *Broadcast Scheduled Area List NG-RAN* IE indicates the areas where initiation of a broadcast was performed successfully. A Broadcast Scheduled Area List is received by the AMF from an NG-RAN Node as Broadcast Completed Area List. See 3GPP TS 38.413 [40]. + +### 9.3.59 Broadcast Cancelled Area List NG-RAN + +This parameter is applicable for NG-RAN only. + +The *Broadcast Cancelled Area List NG-RAN* IE indicates the areas where broadcast was stopped successfully; see 3GPP TS 38.413 [40]. + +### 9.3.60 Broadcast Empty Area List NG-RAN + +This parameter is applicable for NG-RAN only. + +The *Broadcast Empty Area List NG-RAN* IE contains a list of the Global RAN Node IDs (see subclause 9.3.53) of NG-RAN Nodes that have responded to the the AMF with a PWS CANCEL RESPONSE message in which the *Broadcast Cancelled Area List* IE was not included (see 3GPP TS 38.413 [40]). The AMF may aggregate NG-RAN Node IDs into the Broadcast Empty Area List NG-RAN. + +### 9.3.61 Restarted Cell List NG-RAN + +This parameter is applicable for NG-RAN only. + +The *Restarted Cell List NG-RAN* IE lists the cells which have restarted and where warning messages have been stopped if any were ongoing. See 3GPP TS 38.413 [40]. + +### 9.3.62 Failed Cell List NG-RAN + +This parameter is applicable for NG-RAN only. + +The *Failed Cell List NG-RAN* IE lists the cells where ongoing PWS operation has failed. See 3GPP TS 38.413 [40]. + +### 9.3.63 Warning Area Coordinates + +This parameter is applicable for E-UTRAN and NG-RAN only. + +The *Warning Area Coordinates* IE indicates alert area coordinates of a warning message. The eNB and NG-RAN node pass this information to the UE. The UE uses this information to conditionally display (see subclause 9.1.3.4.2 and subclause 9.1.3.5.2) the warning message contents. + +The *Warning Area Coordinates* IE is encoded as specified in ATIS-0700041 [47]. + +## 9.4 Message Format on the Radio Network – MS/UE Interface + +### 9.4.1 GSM + +The CBS messages which are transmitted by the BTS for the MS include the CBS Message (information for the user) and Schedule Message (schedule of CBS messages). + +The use and the formatting of the CBS messages, which contain information for the MS user, is described in this clause. + +The Schedule Message is broadcast to support CBS DRX mode for Mobile Stations. The Schedule Message is helpful in minimizing battery usage for Cell Broadcast in the Mobile Station, because it allows the MS to ignore transmissions of CBS messages the customer is not interested in. The use and formatting of the Schedule Message is described in 3GPP TS 44.012 [7]. + +The handling of the GSM only applicable ETWS Primary Notification messages differ from what is stated in this clause and is instead described in subclause 9.4.1.3. + +#### 9.4.1.1 General Description + +Each page of a CBS Message sent to the MS by the BTS is a fixed block of 88 octets as coded in 3GPP TS 44.012 [7]. This is sent on the channel allocated as CBCH by 3GPP TS 45.002 [8]. The 88 octets of the CBS Message are formatted as described in subclause 9.3.2. + +#### 9.4.1.2 Message Parameter + +| Octet Number(s) | Field | +|-----------------|--------------------| +| 1-2 | Serial Number | +| 3-4 | Message Identifier | +| 5 | Data Coding Scheme | +| 6 | Page Parameter | +| 7-88 | Content of Message | + +The octets in the above table are transmitted in order, starting with octet 1. The bits within these octets are numbered 0 to 7; bit 0 is the low order bit and is transmitted first. + +##### 9.4.1.2.1 Serial Number + +This parameter is a 16-bit integer which identifies a particular CBS message (which may be one to fifteen pages in length) from the source and type indicated by the Message Identifier and is altered every time the CBS message with a given Message Identifier is changed. + +The two octets of the Serial Number field are divided into a 2-bit Geographical Scope (GS) indicator, a 10-bit Message Code and a 4-bit Update Number as shown below: + +| Octet 1 | | | | | | | | Octet 2 | | | | | | | | +|---------|---|--------------|---|---|---|---|---|---------|---|---|---|---|---|---------------|---| +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | +| GS | | Message Code | | | | | | | | | | | | Update Number | | + +The most significant bit of the update number is octet 2 bit 3. The most significant bit of the Message Code is octet 1 bit 5 and the least significant bit of the Message Code is octet 2 bit 4. The most significant bit of the Geographical Scope is octet 1 bit 7. + +- Message Code: + +The Message Code differentiates between CBS messages from the same source and type (i.e. with the same Message Identifier). Message Codes are for allocation by PLMN operators. + +The Message Code identifies different message themes. For example, let the value for the Message Identifier be "Automotive Association" (= source), "Traffic Reports" (= type). Then "Crash on A1 J5" could be one value for the message code, "Cow on A32 J4" could be another, and "Slow vehicle on M3 J3" yet another. + +In the case of transmitting CBS messages for ETWS, i.e. the Message Identifier has a value for ETWS (see subclause 9.4.1.2.2), a part of Message Code can be used to command mobile terminals to activate emergency user alert and message popup in order to alert the users. Message Code format for this purpose is as follows: + +| 5 | 4 | 3 | 2 | 1 | 0 | 7 | 6 | 5 | 4 | +|----------------------|-------|---|---|---|---|---|---|---|---| +| Emergency User Alert | Popup | | | | | | | | | + +NOTE 1: The exact behaviour of the UE is specified in 3GPP TS 22.268 [28]. Whether the UE setting is overridden is subject to regulatory requirements. + +NOTE 2: Emergency user alert includes alerting tone and other user alerting means such as vibration, according to the UE's capability. The types of alert (e.g. the kind of tone, vibration, etc) are implementation dependent and may be subject to regulatory requirements. + +NOTE 3: The popup indication shall take precedence over the setting of the DCS Message class (see 3GPP TS 23.038 [3]), and the Geographical Scope with regard to Display Mode 'immediate'. + +The codings of the Emergency User Alert and Popup fields are shown below: + +| Field | Code | Instruction to Terminal | +|----------------------|------|--------------------------------------------| +| Emergency User Alert | 0 | No instruction as to emergency user alert. | +| | 1 | Activate emergency user alert. | +| Popup | 0 | No instruction as to popup. | +| | 1 | Activate popup on the display. | + +###### - Geographical Scope: + +The Geographical Scope (GS) indicates the geographical area over which the Message Code is unique, and the display mode. The CBS message is not necessarily broadcast by all cells within the geographical area. When two CBS messages are received with identical Serial Numbers/Message Identifiers in two different cells, the Geographical Scope may be used to determine if the CBS messages are indeed identical. + +In particular, the Geographical Scope tells the mobile if the CBS message is: + +- ☞47 - only cell wide (which means that if a message is displayed it is desirable that the message is removed from the screen when the UE selects the next cell and if any CBS message is received in the next cell it is to be regarded as "new"), or +- ☞48 - PLMN wide (which means that the Message Code and/or Update Number must change in the next cell, of the PLMN, for the CBS message to be "new". The CBS message is only relevant to the PLMN in which it is broadcast, so any change of PLMN (including a change to another PLMN which is an ePLMN) means the CBS message is "new"), or +- ☞49 - Location Area wide (in GSM) (which means that a CBS message with the same Message Code and Update Number may or may not be "new" in the next cell according to whether the next cell is in the same Location Area as the current cell), or +- ☞50 - Service Area wide (in UMTS) (which means that a CBS message with the same Message Code and Update Number may or may not be "new" in the next cell according to whether the next cell is in the same Service Area as the current cell), or + +NOTE 4: According to 3GPP TS 23.003 [2] a Service Area consists of one cell only. + +- ☞51 - Tracking Area wide (in E-UTRAN) (which means that a warning message with the same Message Code and Update Number may but need not be "new" in the next cell according to whether the next cell is in the same Tracking Area as the current cell), or +- ☞52 - Tracking Area wide (in NG-RAN) (which means that a warning message with the same Message Code and Update Number may but need not be "new" in the next cell according to whether the next cell is in the same Tracking Area as the current cell). + +The display mode indicates whether the CBS message is supposed to be on the display all the time ("immediate") or only when the user wants to see it ("normal"). In either case, the CBS message will be displayed only if its Message Identifier is contained within the "search list" of the mobile (see subclause 9.3.2). These display modes are indicative of intended use, without indicating a mandatory requirement or constraining the detailed implementation by mobile manufacturers. The user may be able to select activation of these different modes. + +The coding of the Geographical Scope field is shown below: + +| GS Code | Display Mode | Geographical Scope | +|---------|--------------|----------------------------------------------------------------------------------------------------------------------------| +| 00 | Immediate | Cell wide | +| 01 | Normal | PLMN wide | +| 10 | Normal | Location Area wide in GSM,
Service Area wide in UMTS,
Tracking Area wide in E-UTRAN,
Tracking Area wide in NG-RAN | +| 11 | Normal | Cell wide | + +Immediate = default direct display. + +Normal = default display under user interaction. + +Code 00 is intended for use by the network operators for base station IDs but this code can also be used for other applications. Use of GS=00 takes precedence over the setting of the DCS Message class (see 3GPP TS 23.038 [3]) + +- Update Number: + +The Update Number indicates a change of the message content of the same CBS message, i.e. the CBS message with the same Message Identifier, Geographical Scope, and Message Code. + +In other words, the Update Number will differentiate between older and newer versions of the same CBS message, within the indicated geographical area. A new CBS message may have Update Number 0000; however this number will increment by 1 for each update. + +##### 9.4.1.2.2 Message Identifier + +This parameter identifies the source and type of the CBS message. For example, "Automotive Association" (= source), "Traffic Reports" (= type) could correspond to one value. A number of CBS messages may originate from the same source and/or be of the same type. These will be distinguished by the Serial Number. The Message Identifier is coded in binary. + +The ME shall attempt to receive the CBS messages whose Message Identifiers are in the "search list". This "search list" shall contain the Message Identifiers stored in the EFCBMI, EFCBMID and EFCBMIR files on the SIM (see 3GPP TS 11.11) and any Message Identifiers stored in the ME in a "list of CBS messages to be received". If the ME has restricted capabilities with respect to the number of Message Identifiers it can search for, the Message Identifiers stored in the SIM shall take priority over any stored in the ME. + +The use/application of the Message Identifier is shown in the following table, with octet 3 of the Message Identifier in hex shown first, followed by octet 4. Thus "1234" (hex) represents octet 3 = 0001 0010 and octet 4 = 0011 0100. + +The MS shall discard a CBS message in Message Identifier value range "A000hex-AFFFhex" unless it is received from: + +- HPLMN; +- EHPLMN; or +- PLMN that is equivalent to either HPLMN or EHPLMN. + +Networks shall only use Message Identifiers from the range 4352 – 6399 (1100 hex – 18FF hex) for Public Warning System as defined in 3GPP TS 22.268 [28]. If a message Identifier from this range is in the "search list", the ME shall attempt to receive this CBS message. Processing of different language codes is specified in subclause 9.4.1.2.3 and subclause 9.4.2.2.4. + +| Decimal | Hex | Meaning | +|---------|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 – 999 | 0000 – 03E7 |
To be allocated by GSMA(see GSMA AD.26 [25]). If a Message Identifier from this range is in the "search list", the ME shall attempt to receive such CBS message.
This version of this document does not prohibit networks from using Message Identifiers in the range 0000 - 03E7 (hex) for Cell Broadcast Data Download to the SIM.
| + +| | | | +|--------------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1000 | 03E8 | LCS CBS Message Identifier for E-OTD Assistance Data message. | +| 1001 | 03E9 | LCS CBS Message Identifier for DGPS Correction Data message. | +| 1002 | 03EA | LCS CBS Message Identifier for GPS Ephemeris and Clock Correction Data message. | +| 1003 | 03EB | LCS CBS Message Identifier for GPS Almanac and Other Data message. | +| 1004 - 4095 | 03EC – 0FFF | Intended for standardization in future versions of this document. These values shall not be transmitted by networks that are compliant to this version of this document. If a Message Identifier from this range is in the "search list", the ME shall attempt to receive this CBS message. | +| 4096 - 4223 | 1000 – 107F | Networks shall only use Message Identifiers from this range for Cell Broadcast Data Download in "clear" (i.e. unsecured) to the SIM (see 3GPP TS 11.14). If a message Identifier from this range is in the "search list", the ME shall attempt to receive this CBS message.Not settable by MMI | +| 4224 - 4351 | 1080 – 10FF | Networks shall only use Message Identifiers from this range for Cell Broadcast Data Download secured according to 3GPP TS 23.048 [15] to the SIM (see 3GPP TS 11.14). If a message Identifier from this range is in the "search list", the ME shall attempt to receive this CBS message.
Not settable by MMI | +| 4352 | 1100 | ETWS CBS Message Identifier for earthquake warning message. | +| 4353 | 1101 | ETWS CBS Message Identifier for tsunami warning message. | +| 4354 | 1102 | ETWS CBS Message Identifier for earthquake and tsunami combined warning message. | +| 4355 | 1103 | ETWS CBS Message Identifier for test message.
The UE silently discards this message. A UE specially designed for testing purposes may display its contents. | +| 4356 | 1104 | ETWS CBS Message Identifier for messages related to other emergency types. | +| 4357 - 4359 | 1105 - 1107 | ETWS CBS Message Identifier for future extension. | +| 4360 - 4369 | 1108 - 1111 | Intended for standardization in future versions of this document. These values shall not be transmitted by networks that are compliant to this version this document. If a Message Identifier from this range is in the "search list", the ME shall attempt to receive this CBS message. | +| 4370 | 1112 | CMAS CBS Message Identifier for CMAS Presidential Level Alerts.
EU-Alert Level 1 Message Identifier for the local language as defined in ETSI TS 102 900 [32]. | + +| | | | +|-------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | Korean Public Alert System (KPAS) Class 0 Message Identifier.
Not settable by MMI. | +| 4371 | 1113 | CMAS CBS Message Identifier for CMAS Extreme Alerts with Severity of Extreme, Urgency of Immediate, and Certainty of Observed.
EU-Alert Level 2 Message Identifier for the local language as defined in ETSI TS 102 900 [32].
Korean Public Alert System (KPAS) Class 1 Message Identifier.
Settable by MMI
For subscriber opt-out requirements, see 3GPP TS 22.268 [28]. | +| 4372 | 1114 | CMAS CBS Message Identifier for CMAS Extreme Alerts with Severity of Extreme, Urgency of Immediate, and Certainty of Likely.
EU-Alert Level 2 Message Identifier for the local language as defined in ETSI TS 102 900 [32].
Korean Public Alert System (KPAS) Class 1 Message Identifier.
Settable by MMI
For subscriber opt-out requirements, see 3GPP TS 22.268 [28]. | +| 4373 | 1115 | CMAS CBS Message Identifier for CMAS Severe Alerts with Severity of Extreme, Urgency of Expected, and Certainty of Observed.
EU-Alert Level 3 Message Identifier for the local language as defined in ETSI TS 102 900 [32].
Korean Public Alert System (KPAS) Class 1 Message Identifier.
Settable by MMI
For subscriber opt-out requirements, see 3GPP TS 22.268 [28]. | +| 4374 | 1116 | CMAS CBS Message Identifier for CMAS Severe Alerts with Severity of Extreme, Urgency of Expected, and Certainty of Likely.
EU-Alert Level 3 Message Identifier for the local language as defined in ETSI TS 102 900 [32].
Korean Public Alert System (KPAS) Class 1 Message Identifier.
Settable by MMI
For subscriber opt-out requirements, see 3GPP TS 22.268 [28]. | +| 4375 | 1117 | CMAS CBS Message Identifier for CMAS Severe Alerts with Severity of Severe, Urgency of Immediate, and Certainty of Observed.
EU-Alert Level 3 Message Identifier for the local language as defined in ETSI TS 102 900 [32].
Korean Public Alert System (KPAS) Class 1 Message Identifier.
Settable by MMI | + +| | | | +|-------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | For subscriber opt-out requirements, see 3GPP TS 22.268 [28]. | +| 4376 | 1118 |
CMAS CBS Message Identifier for CMAS Severe Alerts with Severity of Severe, Urgency of Immediate, and Certainty of Likely.
EU-Alert Level 3 Message Identifier for the local language as defined in ETSI TS 102 900 [32].
Korean Public Alert System (KPAS) Class 1 Message Identifier.
Settable by MMI
For subscriber opt-out requirements, see 3GPP TS 22.268 [28].
| +| 4377 | 1119 |CMAS CBS Message Identifier for CMAS Severe Alerts with Severity of Severe, Urgency of Expected, and Certainty of Observed.
EU-Alert Level 3 Message Identifier for the local language as defined in ETSI TS 102 900 [32].
Korean Public Alert System (KPAS) Class 1 Message Identifier.
Settable by MMI
For subscriber opt-out requirements, see 3GPP TS 22.268 [28].
| +| 4378 | 111A |CMAS CBS Message Identifier for CMAS Severe Alerts with Severity of Severe, Urgency of Expected, and Certainty of Likely.
EU-Alert Level 3 Message Identifier for the local language as defined in ETSI TS 102 900 [32].
Korean Public Alert System (KPAS) Class 1 Message Identifier.
Settable by MMI
For subscriber opt-out requirements, see 3GPP TS 22.268 [28].
| +| 4379 | 111B |CMAS CBS Message Identifier for Child Abduction Emergency (or Amber Alert).
EU-Amber Message Identifier for the local language as defined in ETSI TS 102 900 [32].
Korean Public Alert System (KPAS) Class 1 Message Identifier.
Settable by MMI
For subscriber opt-out requirements, see 3GPP TS 22.268 [28].
| +| 4380 | 111C |CMAS CBS Message Identifier for the Required Monthly Test.
According to CMAS requirements (see 3GPP TS 22.268 [28]), if this Message Identifier is in the "search list", the ME shall attempt to receive this CBS message.
| +| 4381 | 111D |CMAS CBS Message Identifier for CMAS Exercise.
According to CMAS requirements (see 3GPP TS 22.268 [28]), if this Message Identifier is in the "search list", the ME shall attempt to receive this CBS message.
| +| 4382 | 111E | CMAS CBS Message Identifier for operator defined use. | + +| | | | +|-------------|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | According to CMAS requirements (see 3GPP TS 22.268 [28]), if this Message Identifier is in the "search list", the ME shall attempt to receive this CBS message. | +| 4383 | 111F |CMAS CBS Message Identifier for CMAS Presidential Level Alerts for additional languages.
EU-Alert Level 1 Message Identifier for additional languages as defined in ETSI TS 102 900 [32].
Korean Public Alert System (KPAS) Class 0 Message Identifier for additional languages.
Not settable by MMI.
The ME shall receive the messages dependent on the language indicated in the CBS message and the language indicator settings in the ME.
| +| 4384 | 1120 |CMAS CBS Message Identifier for CMAS Extreme Alerts with Severity of Extreme, Urgency of Immediate, and Certainty of Observed for additional languages.
EU-Alert Level 2 Message Identifier for additional languages as defined in ETSI TS 102 900 [32].
Korean Public Alert System (KPAS) Class 1 Message Identifier for additional languages.
Settable by MMI.
The ME shall receive the messages dependent on the language indicated in the CBS message and the language indicator settings in the ME.
For subscriber opt-out requirements, see 3GPP TS 22.268 [28].
| +| 4385 | 1121 |CMAS CBS Message Identifier for CMAS Extreme Alerts with Severity of Extreme, Urgency of Immediate, and Certainty of Likely for additional languages.
EU-Alert Level 2 Message Identifier for additional languages as defined in ETSI TS 102 900 [32].
Korean Public Alert System (KPAS) Class 1 Message Identifier for additional languages.
Settable by MMI.
The ME shall receive the messages dependent on the language indicated in the CBS message and the language indicator settings in the ME.
For subscriber opt-out requirements, see 3GPP TS 22.268 [28].
| +| 4386 | 1122 |CMAS CBS Message Identifier for CMAS Severe Alerts with Severity of Extreme, Urgency of Expected, and Certainty of Observed for additional languages.
EU-Alert Level 3 Message Identifier for additional languages as defined in ETSI TS 102 900 [32].
Korean Public Alert System (KPAS) Class 1 Message Identifier for additional languages.
| + +| | | | +|-------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | |Settable by MMI.
The ME shall receive the messages dependent on the language indicated in the CBS message and the language indicator settings in the ME.
For subscriber opt-out requirements, see 3GPP TS 22.268 [28].
| +| 4387 | 1123 |CMAS CBS Message Identifier for CMAS Severe Alerts with Severity of Extreme, Urgency of Expected, and Certainty of Likely for additional languages.
EU-Alert Level 3 Message Identifier for additional languages as defined in ETSI TS 102 900 [32].
Korean Public Alert System (KPAS) Class 1 Message Identifier for additional languages. Settable by MMI.
The ME shall receive the messages dependent on the language indicated in the CBS message and the language indicator settings in the ME.
For subscriber opt-out requirements, see 3GPP TS 22.268 [28].
| +| 4388 | 1124 |CMAS CBS Message for CMAS Severe Alerts with Severity of Severe, Urgency of Immediate, and Certainty of Observed for additional languages.
EU-Alert Level 3 Message Identifier for additional languages as defined in ETSI TS 102 900 [32].
Korean Public Alert System (KPAS) Class 1 Message Identifier for additional languages. Settable by MMI.
The ME shall receive the messages dependent on the language indicated in the CBS message and the language indicator settings in the ME.
For subscriber opt-out requirements, see 3GPP TS 22.268 [28].
| +| 4389 | 1125 |CMAS CBS Message for CMAS Severe Alerts with Severity of Severe, Urgency of Immediate, and Certainty of Likely for additional languages.
EU-Alert Level 3 Message Identifier for additional languages as defined in ETSI TS 102 900 [32].
Korean Public Alert System (KPAS) Class 1 Message Identifier for additional languages.
Settable by MMI.
The ME shall receive the messages dependent on the language indicated in the CBS message and the language indicator settings in the ME.
For subscriber opt-out requirements, see 3GPP TS 22.268 [28].
| +| 4390 | 1126 |CMAS CBS Message Identifier for CMAS Severe Alerts with Severity of Severe, Urgency of Expected, and Certainty of Observed for additional languages.
EU-Alert Level 3 Message Identifier for additional languages as defined in ETSI TS 102 900 [32].
Korean Public Alert System (KPAS) Class 1 Message Identifier
| + +| | | | +|-------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | |for additional languages.
Settable by MMI.
The ME shall receive the messages dependent on the language indicated in the CBS message and the language indicator settings in the ME.
For subscriber opt-out requirements, see 3GPP TS 22.268 [28].
| +| 4391 | 1127 |CMAS CBS Message Identifier for CMAS Severe Alerts with Severity of Severe, Urgency of Expected, and Certainty of Likely for additional languages.
EU-Alert Level 3 Message Identifier for additional languages as defined in ETSI TS 102 900 [32].
Korean Public Alert System (KPAS) Class 1 Message Identifier for additional languages.
Settable by MMI.
The ME shall receive the messages dependent on the language indicated in the CBS message and the language indicator settings in the ME.
For subscriber opt-out requirements, see 3GPP TS 22.268 [28].
| +| 4392 | 1128 |CMAS CBS Message Identifier for Child Abduction Emergency (or Amber Alert) for additional languages.
EU-Amber Message Identifier for additional languages as defined in ETSI TS 102 900 [32].
Korean Public Alert System (KPAS) Class 1 Message Identifier for additional languages.
Settable by MMI.
The ME shall receive the messages dependent on the language indicated in the CBS message and the language indicator settings in the ME.
For subscriber opt-out requirements, see 3GPP TS 22.268 [28].
| +| 4393 | 1129 |CMAS CBS Message Identifier for the Required Monthly Test for additional languages.
According to CMAS requirements (see 3GPP TS 22.268 [28]), if this Message Identifier is in the "search list", the ME shall attempt to receive this CBS message dependent on the language indicated in the CBS message and the language indicator settings in the ME.
| +| 4394 | 112A |CMAS CBS Message Identifier for CMAS Exercise for additional languages.
According to CMAS requirements (see 3GPP TS 22.268 [28]), if this Message Identifier is in the "search list", the ME shall attempt to receive this CBS message dependent on the language indicated in the CBS message and the language indicator settings in the ME.
| +| 4395 | 112B |CMAS CBS Message Identifier for operator defined use for additional languages.
| + +| | | | +|-------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | According to CMAS requirements (see 3GPP TS 22.268 [28]), if this Message Identifier is in the "search list", the ME shall attempt to receive this CBS message dependent on the language indicated in the CBS message and the language indicator settings in the ME. | +| 4396 | 112C | CMAS CBS Message Identifier for CMAS Public Safety Alerts.Settable by MMI.
For subscriber opt-out requirements, see 3GPP TS 22.268 [28]. | +| 4397 | 112D | CMAS CBS Message Identifier for CMAS Public Safety Alerts for additional languages.
Settable by MMI.
The ME shall receive the messages dependent on the language indicated in the CBS message and the language indicator settings in the ME.
For subscriber opt-out requirements, see 3GPP TS 22.268 [28]. | +| 4398 | 112E | CMAS CBS Message Identifier for CMAS State/Local WEA Test.
Settable by MMI.
For subscriber opt-out requirements, see 3GPP TS 22.268 [28]. | +| 4399 | 112F | CMAS CBS Message Identifier for CMAS State/Local WEA Test for additional languages.
Settable by MMI.
The ME shall receive the messages dependent on the language indicated in the CBS message and the language indicator settings in the ME.
For subscriber opt-out requirements, see 3GPP TS 22.268 [28]. | +| 4400 | 1130 | CMAS CBS Message Identifier for geo-fencing trigger messages. | +| 4401 | 1131 | Non-ETWS CBS Message Identifier for warning message dedicated to UEs with no user interface and with ePWS functionality.
Not applicable for US WEA | +| 4402 | 1132 | Non-ETWS CBS Message Identifier for warning message dedicated to UEs with no user interface and with ePWS functionality when an earthquake occurs.
Not applicable for US WEA | +| 4403 | 1133 | Non-ETWS CBS Message Identifier for warning message dedicated to UEs with no user interface and with ePWS functionality when a volcanic eruption occurs.
Not applicable for US WEA | +| 4404 | 1134 | Non-ETWS CBS Message Identifier for warning message dedicated to UEs with no user interface and with ePWS functionality when a disaster whose characteristic is water (e.g. flood, typhoon, hurricane or tsunami) occurs. | + +| | | | +|-------------|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | Not applicable for US WEA | +| 4405 | 1135 | Non-ETWS CBS Message Identifier for warning message dedicated to UEs with no user interface and with ePWS functionality when a disaster whose characteristic is fire (e.g. forest fire or building fire) occurs.
Not applicable for US WEA | +| 4406 | 1136 | Non-ETWS CBS Message Identifier for warning message dedicated to UEs with no user interface and with ePWS functionality when a disaster whose characteristic is pressure (e.g. landslide or avalanche) occurs.
Not applicable for US WEA | +| 4407 | 1137 | Non-ETWS CBS Message Identifier for warning message dedicated to UEs with no user interface and with ePWS functionality when a disaster whose characteristic is wind (e.g. tornado or gale) occurs.
Not applicable for US WEA | +| 4408 | 1138 | Non-ETWS CBS Message Identifier for warning message dedicated to UEs with no user interface and with ePWS functionality when a disaster whose characteristic is dust (e.g. yellow dust or sandstorm) occurs.
Not applicable for US WEA | +| 4409 | 1139 | Non-ETWS CBS Message Identifier for warning message dedicated to UEs with no user interface and with ePWS functionality when a disaster whose characteristic is chemical hazard (e.g. radiation leak or toxic substance leak) occurs.
Not applicable for US WEA | +| 4410 | 113A | Non-ETWS CBS Message Identifier for warning message dedicated to UEs with no user interface and with ePWS functionality when an epidemic occurs.
Not applicable for US WEA | +| 4411 | 113B | Non-ETWS CBS Message Identifier for test message dedicated to UEs with no user interface and with ePWS functionality.
Not applicable for US WEA | +| 4412 | 113C | ETWS CBS Message Identifier for warning message dedicated to UEs with no user interface and with ePWS functionality.
Not applicable for Japan ETWS | +| 4413 | 113D | ETWS CBS Message Identifier for warning message dedicated to UEs with no user interface and with ePWS functionality when an earthquake occurs.
Not applicable for Japan ETWS | +| 4414 | 113E | ETWS CBS Message Identifier for warning message dedicated to UEs with no user interface and with ePWS functionality when a volcanic eruption occurs.
Not applicable for Japan ETWS | + +| | | | +|---------------------|--------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 4415 | 113F | ETWS CBS Message Identifier for warning message dedicated to UEs with no user interface and with ePWS functionality when a disaster whose characteristic is water (e.g. flood, typhoon, hurricane or tsunami) occurs.
Not applicable for Japan ETWS | +| 4416 | 1140 | ETWS CBS Message Identifier for warning message dedicated to UEs with no user interface and with ePWS functionality when a disaster whose characteristic is fire (e.g. forest fire or building fire) occurs.
Not applicable for Japan ETWS | +| 4417 | 1141 | ETWS CBS Message Identifier for warning message dedicated to UEs with no user interface and with ePWS functionality when a disaster whose characteristic is pressure (e.g. landslide or avalanche) occurs.
Not applicable for Japan ETWS | +| 4418 | 1142 | ETWS CBS Message Identifier for warning message dedicated to UEs with no user interface and with ePWS functionality when a disaster whose characteristic is wind (e.g. tornado or gale) occurs.
Not applicable for Japan ETWS | +| 4419 | 1143 | ETWS CBS Message Identifier for warning message dedicated to UEs with no user interface and with ePWS functionality when a disaster whose characteristic is dust (e.g. yellow dust or sandstorm) occurs.
Not applicable for Japan ETWS | +| 4420 | 1144 | ETWS CBS Message Identifier for warning message dedicated to UEs with no user interface and with ePWS functionality when a disaster whose characteristic is chemical hazard (e.g. radiation leak or toxic substance leak) occurs.
Not applicable for Japan ETWS | +| 4421 | 1145 | ETWS CBS Message Identifier for warning message dedicated to UEs with no user interface and with ePWS functionality when an epidemic occurs.
Not applicable for Japan ETWS | +| 4422 | 1146 | ETWS CBS Message Identifier for test message dedicated to UEs with no user interface and with ePWS functionality.
Not applicable for Japan ETWS | +| 4423 - 6399 | 1147 – 18FF | Intended as PWS range in future versions of the present document.
These values shall not be transmitted by networks that are compliant to this version of this document. If a Message Identifier from this range is in the "search list", the ME shall attempt to receive this CBS message. | +| 6400 | 1900 | EU-Info Message Identifier for the local language as defined in ETSI TS 102 900 [32]. | +| 6401 – 40959 | 1901 – 9FFF | Intended for standardization in future versions of this document .
These values shall not be transmitted by networks that are | + +| | | | +|----------------------|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | compliant to this version of this document. If a Message Identifier from this range is in the "search list", the ME shall attempt to receive this CBS message. | +| 40960 - 45055 | A000 - AFFF | PLMN operator specific range. The type of information provided by PLMN operators using these Message Identifiers is not guaranteed to be the same across different PLMNs. If a Message Identifier from this range is in the "search list", the ME shall attempt to receive this CBS message. The MS shall discard messages in this MI value range unless received from HPLMN, EHPLMN or PLMN that is equivalent to HPLMN or EHPLMN. | +| 45056 - 61439 | B000 - EFFF | Intended as PLMN operator specific range in future versions of this document. These values shall not be transmitted by networks that are compliant to this version of this document. If a Message Identifier from this range is in the "search list", then the ME shall attempt to receive this CBS message. | +| 61440 - 65534 | F000 - FFFE | Intended as PLMN operator specific range in future versions of this document. These values shall not be transmitted by networks that are compliant to this version of this document. If a Message Identifier from this range is in the "search list", then the ME shall attempt to receive this CBS message.
Not settable by MMI. | +| 65535 | FFFF | Reserved, and should not be used for new services, as this value is used on the SIM to indicate that no Message Identifier is stored in those two octets of the SIM. If this Message Identifier is in the "search list", the ME shall attempt to receive this CBS message.
Not settable by MMI. | + +Generally, the MMI for entering any Message in the ME is left to the manufacturers' discretion. However, the codes allowed to be set by MMI in the table above shall be capable of being specified via their decimal representation i.e.: + +Octet 3 Octet 4. +0000 00000000 0000(decimal '000'). +0000 00000000 0001(decimal '001'). +0000 00000000 0010(decimal '002'). +0000 00000000 0011(decimal '003'). +: : : +0000 11111111 1111(decimal '4095'). + +0001 00010000 0000(decimal '4352'). +: : : +0001 00010001 0001(decimal '4369'). + +0001 00010001 0011(decimal '4371'). +: : : +0001 00010001 1110(decimal '4382'). + +0001 00010010 0000(decimal '4384'). +: : : +1110 11111111 1111(decimal '61439'). + +##### 9.4.1.2.3 Data Coding Scheme + +This parameter indicates the intended handling of the CBS message at the MS, the alphabet/coding, and the language (when applicable). This is defined in 3GPP TS 23.038 [3]. + +When the SIM indicates one or more language preferences, the ME shall, by default, use the language(s) stored in the SIM (in the EFPL file) to set any language filter mechanisms provided by the ME. + +Optionally, when allowed by language code processing specified below, the user can select the language(s) required by using an MMI, to determine whether a particular CBS message should be displayed. + +Where the message relates to a public warning system, the Message Identifier values 4370 through 4382, 4396 and 4398 relate to warning messages delivered in languages which are mandatory to receive. The ME shall not use any language filter mechanisms or use the language(s) selected through the MMI to determine whether a particular CBS message should be displayed for these Message Identifier values. This does not affect the ability to set a particular message identifier by MMI. + +Where the message relates to a public warning system, the Message Identifier values 4383 through 4395, 4397 and 4399 relate to warning messages delivered in languages which are optional to receive. For these values, the ME can use language filter mechanisms and the MS may use the language(s) selected through the MMI to determine whether a particular CBS message should be displayed. Even if the Message Identifier is not settable by MMI, the message shall still be discarded if the language is not set to be displayed. + +##### 9.4.1.2.4 Page Parameter + +This parameter is coded as two 4-bit fields. The first field (bits 0-3) indicates the binary value of the total number of pages in the CBS message and the second field (bits 4-7) indicates binary the page number within that sequence. The coding starts at 0001, with 0000 reserved. If a mobile receives the code 0000 in either the first field or the second field then it shall treat the CBS message exactly the same as a CBS message with page parameter 0001 0001 (i.e. a single page message). + +##### 9.4.1.2.5 Content of Message + +This parameter is a copy of the 'CBS-Message-Information-Page' as sent from the CBC to the BSC. + +#### 9.4.1.3 ETWS Primary Notification message + +##### 9.4.1.3.1 General Description + +The ETWS Primary Notification message is transmitted to a MS in idle mode and dedicated mode as described in 3GPP TS 44.018 [26], and to a MS in packet transfer mode as described in 3GPP TS 44.060 [27]. The ETWS Primary Notification message is structured as in the table in subclause 9.4.1.3.2. + +This message is only applicable in GSM. + +##### 9.4.1.3.2 Message Parameter + +| Octet Number(s) | Field | +|-----------------|------------------------------| +| 1-2 | Serial Number | +| 3-4 | Message Identifier | +| 5-6 | Warning Type | +| 7-56 | Warning Security Information | + +The octets in the above table are transmitted in order, starting with octet 1. The bits within these octets are numbered 0 to 7; bit 0 is the low order bit and is transmitted first. + +##### 9.4.1.3.3 Serial Number + +This parameter identifies a particular ETWS Primary Notification message from the source and type indicated by the Message Identifier and is altered every time the ETWS Primary Notification message with a given Message Identifier is changed. The coding of this parameter is same as that defined in subclause 9.4.1.2.1. + +##### 9.4.1.3.4 Message Identifier + +This parameter identifies the source and type of the ETWS Primary Notification message. The coding of this parameter is same as that defined in subclause 9.4.1.2.2. + +##### 9.4.1.3.5 Warning Type + +This parameter identifies the warning type of the ETWS Primary Notification message. It is identical with the Warning Type described in subclause 9.3.24 with respect to its structure and possible value range. + +##### 9.4.1.3.6 Warning Security Information + +This parameter identifies the warning security information of the ETWS Primary Notification message. The coding of this parameter is same as that defined in subclause 9.3.25. The UE shall ignore this parameter. + +NOTE: The Warning Security Information parameter is included due to requirements in earlier versions of this document. + +### 9.4.2 UMTS + +The CBS messages which are transmitted by the RNS to the UE include two types of messages: CBS Message (user information) and Schedule Message (schedule of CBS messages). + +The format of the CBS Message containing user information is described in this clause and in 3GPP TS 25.324 [19]. + +The format of the Schedule Message is described in 3GPP TS 25.324 [19]. + +#### 9.4.2.1 General Description + +The CBS message is transmitted as one unit over the radio interface. On layer two of the UMTS radio interface the logical channel CTCH is used. + +#### 9.4.2.2 Message Parameter + +| Octet Number(s) | Parameter | +|-----------------|--------------------| +| 1 | Message Type | +| 2 – 3 | Message ID | +| 4 – 5 | Serial Number | +| 6 | Data Coding Scheme | +| 7 – N | CB Data | + +The octets in the above table are transmitted in order, starting with octet 1. The bits within these octets are numbered 0 to 7; bit 0 is the low order bit and is transmitted first. + +For ETWS, the transmission order of the parameter is only applicable to the secondary notification. + +For value N in the above table see 3GPP TS 25.324 [19]. + +##### 9.4.2.2.1 Message Type + +This parameter indicates the type of a message, either a CBS message or a Schedule Message. The Coding of the Message Type is described in 3GPP TS 25.324 [19]. + +##### 9.4.2.2.2 Message ID + +This parameter identifies the source and type of the CBS Message (see also 3GPP TS 25.324 [19]). It is identical with the Message Identifier described in subclause 9.4.1.2.2 with respect to its structure and possible value range. Within a multi technology network of one operator, e.g. GSM combined with UMTS, the values identifying a given topic shall be identical for both the Message ID and the Message Identifier described in subclause 9.4.1.2.2. + +The UE shall attempt to receive the CBS messages whose Message ID's are in the "search list". This "search list" shall contain the Message IDs stored in the EFCBM1, EFCBMID and EFCBMIR files on the USIM (see 3GPP TS 31.102 [18]) and any Message Identifiers stored in the UE in a "list of CBS messages to be received". If the UE has restricted capabilities + +with respect to the number of Message ID's it can search for, the IDs stored in the USIM shall take priority over any stored in the UE. + +The MS shall discard a CBS message in Message Identifier value range "A000hex-AFFFhex" unless it is received from: + +- HPLMN; +- EHPLMN; or +- PLMN that is equivalent to either HPLMN or EHPLMN. + +##### 9.4.2.2.3 Serial Number + +This parameter identifies a particular CBS Message from the source and type indicated by the Message ID (see also 3GPP TS 25.324 [19]). It is identical with the Serial Number described in subclause 9.4.1.2.1 with respect to its structure and possible value range. + +##### 9.4.2.2.4 Data Coding Scheme + +This parameter identifies the the alphabet/coding and the language applied to a CBS Message as defined in 3GPP TS 23.038 [3]. + +When the USIM indicates one or more language preferences, the UE shall, by default, use the language(s) stored in the USIM (in the EFPL file) to set any language filter mechanisms provided by the UE. + +Optionally, when allowed by language code processing specified below, the user can select the language(s) required by using an MMI, to determine whether a particular CBS message should be displayed. + +Where the message relates to a public warning system, the Message Identifier values 4370 through 4382, 4396 and 4398, relate to warning messages delivered in languages which are mandatory to receive. The ME shall not use any language filter mechanisms or use the language(s) selected through the MMI to determine whether a particular CBS message should be displayed for these Message Identifier values. This does not affect the ability to set a particular message identifier by MMI. + +Where the message relates to a public warning system, the Message Identifier values 4383 through 4395, 4397 and 4399, relate to warning messages delivered in languages which are optional to receive. For these values, the ME can use language filter mechanisms and the MS/UE may use the language(s) selected through the MMI to determine whether a particular CBS message should be displayed. Even if the Message Identifier is not settable by MMI, the message shall still be discarded if the language is filtered or is not set to be displayed. + +##### 9.4.2.2.5 CB Data + +This parameter consists of the following WRITE-REPLACE primitive parameters as received from the CBC (see subclause 9.2.2): + +- Number-of-Pages; +- CBS-Message-Information-Page; +- CBS-Message-Information-Length. + +| Octet Number(s) | Parameter | +|----------------------------------|----------------------------------| +| 1 | Number-of-Pages | +| 2 – 83 | CBS-Message-Information-Page 1 | +| 84 | CBS-Message-Information-Length 1 | +| ... | ... | +| | CBS-Message-Information-Page n | +| | CBS-Message-Information-Length n | +| NOTE: n equal to or less than 15 | | + +The octets in the above table are transmitted in order, starting with octet 1. The bits within these octets are numbered 0 to 7; bit 0 is the low order bit and is transmitted first. + +### 9.4.3 E-UTRAN + +#### 9.4.3.1 General Description + +The warning message may be segmented within E-UTRAN for transmission over radio interface. + +#### 9.4.3.2 Message Parameter + +| Parameter | +|--------------------------------------------| +| Message Identifier | +| Serial Number | +| CB Data {Warning Message Content E-UTRAN}, | +| Data Coding Scheme | +| Warning Area Coordinates (O) | + +The table gives a high-level description of the warning message content. The format of the warning message is described in 3GPP TS 36.331 [36]. + +For ETWS, the description of the warning message content is only applicable for the secondary notification. Description of the ETWS Primary Notification message is specified in subclause 9.4.3.3. + +##### 9.4.3.2.1 Message Identifier + +This parameter identifies the source and type of the warning message. The contents of the parameter are specified in subclause 9.4.1.2.2 with respect to its structure and possible value range. + +##### 9.4.3.2.2 Serial Number + +This parameter identifies a particular warning message from the source and type indicated by the Message Identifier. The contents of the parameter are specified in subclause 9.4.1.2.1 with respect to its structure and possible value range. + +##### 9.4.3.2.3 Data Coding Scheme + +This parameter identifies the alphabet/coding and the language applied to the warning message as defined in 3GPP TS 23.038 [3]. The contents of the parameter are specified in subclause 9.4.2.2.4 with respect to its structure and possible value range. + +##### 9.4.3.2.4 CB Data + +This parameter contains the content of the warning message and is contained in the *Warning Message Content E-UTRAN* IE (see subclause 9.3.35) of the WRITE-REPLACE-WARNING-REQUEST Request message received from the CBC (see subclause 9.2.16). It is encoded as specified in subclause 9.4.2.2.5. + +##### 9.4.3.2.5 Warning Area Coordinates + +This parameter contains the coordinates of the warning area and is contained in the *Warning Area Coordinates* IE (see subclause 9.3.63) of the WRITE-REPLACE-WARNING-REQUEST Request message received from the CBC (see subclause 9.2.16) or WRITE-REPLACE-WARNING-REQUEST-NG-RAN request message received from the CBCF (see subclause 9.2.26). + +#### 9.4.3.3 ETWS Primary Notification message + +##### 9.4.3.3.1 General Description + +The ETWS Primary Notification message for E-UTRAN radio interface is described in 3GPP TS 36.331 [36]. The ETWS Primary Notification message is structured as in the table in subclause 9.4.3.3.2. + +##### 9.4.3.3.2 Message Parameter + +| Octet Number(s) | Parameter | +|-----------------|--------------------| +| 1-2 | Message Identifier | +| 3-4 | Serial Number | +| 5-6 | Warning Type | +| 7-56 | dummy | + +The octets in the above table are transmitted in order, starting with octet 1. The bits within these octets are numbered 0 to 7; bit 0 is the low order bit and is transmitted first. + +##### 9.4.3.3.3 Message Identifier + +This parameter identifies the source and type of the ETWS Primary Notification message. The contents of the parameter are specified in subclause 9.4.1.2.2 with respect to its structure and possible value range. + +##### 9.4.3.3.4 Serial Number + +This parameter identifies a particular ETWS Primary Notification message from the source and type indicated by the Message Identifier and is altered every time the ETWS Primary Notification message with a given Message Identifier is changed. The contents of the parameter are specified in subclause 9.4.1.2.1 with respect to its structure and possible value range. + +##### 9.4.3.3.5 Warning Type + +This parameter identifies the warning type of the ETWS Primary Notification message. It is identical with the Warning Type described in subclause 9.3.24 with respect to its structure and possible value range. + +##### 9.4.3.3.6 Dummy + +This parameter is not used in the specification. The UE shall ignore this parameter. + +### 9.4.4 NG-RAN + +The format of the CBS Message for NG-RAN is same as format of the CBS Message defined for E-UTRAN as described in subclause 9.4.3.2 and 3GPP TS 36.331 [36]. + +The format of the ETWS Primary Notification message is same as format of the ETWS Primary Notification message defined for E-UTRAN as described in subclause 9.4.3.3 and 3GPP TS 36.331 [36]. + +## 9.5 CBS Compression + +Cell Broadcast messages may be compressed in accordance with the compression algorithm described in 3GPP TS 23.042 [14]. + +The Data Coding Scheme parameter (see subclause 9.4.1.2.3) indicates whether or not a CBS Message is compressed. + +Compression and decompression may take place between a CBE and an MS/UE or between a CBC and an MS/UE. + +The compression applies only to user information sent between the CBC and the MS/UE i.e. excludes any padding octets. + +Padding in the case of CBS compression is defined as an integral number of octets where each padding octet has a value FF hexadecimal. The insertion of padding for different scenarios is described in the paragraphs below. + +The compression footer (see 3GPP TS 23.042 [14]) delimits the compressed user information bit stream at an octet boundary. The remainder of the 'CBS-Message-Information-Page' sent between the CBC and the BSC contains padding octets. The parameter 'CBS-Message-Information-Length' identifies the sum of the compressed octets, the compression header, and the compression footer (see 3GPP TS 23.042 [14]), but not any padding. + +Compression may apply to a single 'CBS-Message-Information-Page' or across multiple 'CBS-Message-Information-Page's. + +In the case where Compression applies only to a single 'CBS-Message-Information-Page', the compression header shall be the first octet in that 'CBS-Message-Information-Page' and the compression footer shall immediately follow the + +compressed data stream. Any remaining octets after the compression footer shall contain padding up to and including the 82nd octet position. However, if the 82nd octet position contains the compression footer then there is no padding. + +In the case where compression applies across multiple 'CBS-Message-Information-Page's, the compression header shall be present only in the first octet position of the first 'CBS-Message-Information-Page'. The compression footer shall immediately follow the compressed data stream which will terminate within the last 'CBS-Message-Information-Page'. Any remaining octets after the compression footer in the last 'CBS-Message-Information-Page' shall contain padding up to and including the 82nd octet position in the last 'CBS-Message-Information-Page'. However, if the 82nd octet position of the last 'CBS-Message-Information-Page' contains the compression footer then there is no padding. + +If it is required to convey different blocks of information which are to be treated by the MS/UE as though they were physically independent pages rather than concatenated information then page break characters (see 3GPP TS 23.038 [3]) may be inserted in the character stream prior to compression. The boundaries created by the page breaks will not normally align with the boundaries set by the page number parameters and so the page number parameters cannot be used to identify physically separate blocks of meaningful information. + +The decoding at the MS/UE may be achieved by first locating the compression footer octet by working back from the 82nd octet in the last 'CBS-Message-Information-Page'. If padding is present, the MS/UE must skip backwards over the padding until a non padding octet is found. By definition this octet must be the compression footer. The compression footer has a pre-defined bit combination which can never replicate a padding octet. If padding is not present in the 82nd octet position of the last 'CBS-Message-Information-Page', by definition the 82nd octet must be the compression footer. + +The compression footer defined in 3GPP TS 23.042 [14] indicates whether there are any compressed data bits contained within the compression footer octet and, if not, how many compressed data bits are contained within the octet immediately preceding the compression footer. In order to prevent possible replication of the padding octet value in the compression footer octet value, the compression mechanism must ensure that when bits 0, 1, 2 in the compression footer are all ones all other bits in the compression footer octet are set to 0. + +# 9A Service Based Interface for 5G System + +## 9A.1 Introduction + +Within the 5GCN, the AMF offers services to the CBCF via the Namf service-based interface (see 3GPP TS 23.501 [39] and 3GPP TS 23.502 [43]). + +Figure 9A.1-1 depicts the 5GS PWS system architecture, using the service-based interface representation showing how the network functions interact with each other. + + + +``` + +graph TD + CBCF[CBCF] --- N(( )) + PWS-IWF[PWS-IWF] --- N + N --- Namf[Namf] + Namf --- AMF[AMF] + +``` + +Diagram of 5GS PWS system architecture showing CBCF and PWS-IWF connected to a common horizontal line, which is connected to the AMF via the Namf service-based interface. + +Figure 9A.1-1: 5GS PWS system architecture – CBCF/PWS-IWF - AMF + +Service-based interface to support 5GS PWS: + +**Namf:** Service-based interface exhibited by AMF. + +**NOTE:** No services are provided by CBCF or PWS-IWF, thus no service-based interfaces are depicted for these NFs in the 5GS PWS system architecture. + +The table 9A.1-1 shows the AMF Service and Service Operations specific for PWS: + +Table 9A.1-1 AMF Service for PWS + +| Service Name | Service Operations | Operation Semantics | Consumer | +|--------------------|------------------------|---------------------|---------------| +| Namf_Communication | NonUeN2MessageTransfer | Request/Response | CBCF, PWS-IWF | + +| | | | +|------------------------|------------------|---------------| +| NonUeN2InfoSubscribe | Subscribe/Notify | CBCF, PWS-IWF | +| NonUeN2InfoUnSubscribe | Subscribe/Notify | CBCF, PWS-IWF | +| NonUeN2InfoNotify | Subscribe/Notify | CBCF, PWS-IWF | + +## 9A.2 Namf\_Communication Service + +### 9A.2.1 Service Description + +The Namf\_Communication service is specified in 3GPP TS 23.502 [43] subclause 5.2.2.2. + +### 9A.2.2 Service Operations + +#### 9A.2.2.1 Namf\_Communication\_NonUeN2MessageTransfer service operation + +The Namf\_Communication\_NonUeN2MessageTransfer service operation is specified in 3GPP TS 23.502 [43] subclause 5.2.2.2.17. + +The NonUeN2MessageTransfer service operation shall be invoked by the NF Service Consumer (e.g. CBCF or PWS-IWF) to initiate or stop broadcast in one or more cells as indicated in the *Warning Area* IE. The AMF shall accept the request and respond to the NF Service Consumer immediately. + +When NonUeN2MessageTransfer service operation is used for PWS services: + +- PWS Write-Replace-Warning Request message (see subclause 9.2.26) or the Stop-Warning Request message (see subclause 9.2.28) are transferred in an N2 Message Container via the NonUeN2MessageTransfer request operation (along with a number of IEs); + +The N2 Message Container contains all the available elements from the Write-Replace-Warning Request message or the Stop-Warning Request message with the exception of the *List of TAIs* IE and the *Send Write-Replace-Warning Indication* IE or the *Send Stop-Warning Indication* IE. The PWS message in the N2 Message Container is sent by the AMF via N2 to NG-RAN. + +- Write-Replace-Warning Confirm message (see subclause 9.2.27) or the Stop-Warning Confirm message (see subclause 9.2.29) returned to the NF Service Consumer via the NonUeN2MessageTransfer response operation; +- the *List of TAIs* IE shall be used by the AMF to determine to which NG-RAN nodes the N2 Message Container needs to be forwarded to. The *List of TAIs* IE is not included in the N2 Message Container. If the *List of TAIs* IE is not present then the message shall be forwarded to all NG-RAN nodes served by the AMF, subject to the RAT Selector NG-RAN; +- each NonUeN2MessageTransfer message is uniquely identified by the *Message Identifier* IE, the *Serial Number* IE and the *Message Type* IE. These IEs are also included in the N2 Message Container; +- if the *Send Write-Replace-Warning Indication* IE is present in the Write-Replace-Warning Request message then the AMF shall send the associated Write-Replace-Warning Indication message(s) to the NF Service Consumer as specified in subclause 9A.2.2.3. The *Send Write-Replace-Warning Indication* IE is not included in the N2 Message Container, and +- if the *Send Stop-Warning Indication* IE is present in the Stop-Warning Request message then the AMF shall send the associated Stop-Warning Indication message(s) to the NF Service Consumer as specified in subclause 9A.2.2.3. The *Send Stop-Warning Indication* IE is not included in the N2 Message Container. + +#### 9A.2.2.2 Namf\_Communication\_NonUeN2InfoSubscribe service operation + +The Namf\_Communication\_NonUeN2InfoSubscribe service operation is specified in 3GPP TS 23.502 [43] subclause 5.2.2.2.18. + +The NonUeN2InfoSubscribe service operation shall be invoked by the NF Service Consumer (e.g. CBCF or PWS-IWF) to subscribe to the delivery of non-UE specific PWS information from the NG-RAN node, e.g. for PWS events, sent via N2 to the AMF. + +When NonUeN2InfoSubscribe service operation is used for PWS services: + +- a) The NF Service Consumer ID is an identifier which is configured in the CBCF or PWS-IWF; +- b) The N2 information types are: + - WarningIndications; + - RestartFailure; +- c) if the N2 information type is WarningIndications then the NF Service Consumer subscribes to receiving Write-Replace-Warning Indication messages (see subclause 9.2.30) and Stop-Warning Indication messages (see subclause 9.2.31) from the AMF, and + +NOTE: If the Indication messages are actually sent to the NF Service Consumer depends on the presence of the *Send Write-Replace-Warning Indication* IE or the *Send Stop-Warning Indication* IE; see subclause 9A.2.2.1. + +- d) if the N2 information type is RestartFailure then the NF Service Consumer subscribes to receiving Restart Indications (see subclause 9.2.32) and Failure Indications (see subclause 9.2.33) from the NG-RAN node. + +#### 9A.2.2.2A Namf\_Communication\_NonUeN2InfoUnSubscribe service operation + +The Namf\_Communication\_NonUeN2InfoUnSubscribe service operation is specified in 3GPP TS 23.502 [43] subclause 5.2.2.2.19. + +The NonUeN2InfoUnSubscribe service operation shall be invoked by the NF Service Consumer (e.g. CBCF or PWS-IWF) to unsubscribe to stop notifying non-UE specific N2 information from the NG-RAN node, e.g. for PWS events. + +#### 9A.2.2.3 Namf\_Communication\_NonUeN2InfoNotify service operation + +The Namf\_Communication\_NonUeN2InfoNotify service operation is specified in 3GPP TS 23.502 [43] subclause 5.2.2.2.20. + +The NonUeN2InfoNotify service operation is used by AMF to notify a particular PWS event towards the NF Service Consumer (e.g. CBCF or PWS-IWF) that has subscribed for the specific information. The AMF receives messages for such PWS events from NG-RAN via N2. + +When NonUeN2InfoNotify service operation is used for PWS services, the N2 information consists of all (mandatory and optionally) available information provided via N2 in the Write-Replace Warning Indication (see subclause 9.2.30), a Stop Warning Indication (see subclause 9.2.31), a PWS Restart Indication (see subclause 9.2.32) or a PWS Failure Indication (see subclause 9.2.33). + +### 9A.2.3 Service operation message flows + +#### 9A.2.3.1 Service flow for message transfer + +Write-Replace-Warning Request messages and Stop-Warning-Request messages are transported with the NonUeMessageTransfer service operation. The procedure is shown in figure 9A.2.3-1. + + + +``` + +sequenceDiagram + participant (R)AN + participant AMF + participant CBCF/PWS-IWF + Note right of AMF: 1. Namf_Communication_NonUeInfoSubscribe() Request + AMF->>CBCF/PWS-IWF: 2a. Namf_Communication_NonUeN2MessageTransfer() Request + CBCF/PWS-IWF-->>AMF: 2b. Namf_Communication_NonUeN2MessageTransfer() Response + Note right of AMF: 3. RAN Nodes selection + Note right of AMF: 4. N2 message transfer + Note right of AMF: 5. Notifications aggregation + AMF->>CBCF/PWS-IWF: 6. Namf_Communications_NonUeInfoNotify() Notification + +``` + +Sequence diagram for Message transfer procedure (Figure 9A.2.3.1-1). Lifelines: (R)AN, AMF, CBCF/PWS-IWF. The sequence starts with the CBCF sending a Namf\_Communication\_NonUeInfoSubscribe() Request to the AMF. The AMF responds with a Namf\_Communication\_NonUeN2MessageTransfer() Request to the CBCF. The CBCF returns a response. The AMF then performs RAN Nodes selection and N2 message transfer (indicated by a dashed box). Finally, the AMF sends a Namf\_Communications\_NonUeInfoNotify() Notification to the CBCF. + +**Figure 9A.2.3.1-1: Message transfer procedure** + +- 1) If the CBCF supports reception of Write-Replace-Warning Notifications and Stop-Warning Notifications then the CBCF uses the Namf\_Communication\_NonUeInfoSubscribe service operation to subscribe to these notifications. +- 2a) The CBCF sends a Write-Replace-Warning Request message or a Stop-Warning-Request message to the AMF using the Namf\_Communication\_NonUeN2MessageTransfer service operation. +- 2b) The AMF returns a Namf\_Communication\_NonUeN2MessageTransfer response message. +- 3) The AMF determines from the List of TAIs IE to the NG-RAN nodes the N2 Message Container shall be forwarded to. +- 4) The AMF forwards the messages included in the N2 Message Container to the selected NG-RAN nodes via N2 and receives a response from the NG-RAN nodes. +- 5) The AMF may aggregate the responses it has received from the NG-RAN nodes. +- 6) The AMF forwards the (aggregated) response(s) as Write-Replace-Warning Notification(s) or Stop-Warning Notifications to the CBCF using the Namf\_Communication\_NonUeNotify service operation if the CBCF has subscribed to receiving these notifications in step 1. + +#### 9A.2.3.2 Service flow for Restart and Failure Indication messages + +Restart and Failure Indications are sent by NG-RAN nodes and are forwarded to the CBCF by the AMF if the CBCF has subscribed to receiving such indications. The procedure is shown in figure 9A.2.4-1. + + + +``` + +sequenceDiagram + participant (R)AN + participant AMF + participant CBCF/PWS-IWF + Note right of AMF: 1. Namf_Communication_NonUeInfoSubscribe() Request + Note right of AMF: 2. Indication message transfer + AMF->>CBCF/PWS-IWF: 3. Namf_Communication_NonUeInfoNotify() Notification + +``` + +Sequence diagram for Indication message transfer procedure (Figure 9A.2.3.2-1). Lifelines: (R)AN, AMF, CBCF/PWS-IWF. The sequence starts with the CBCF sending a Namf\_Communication\_NonUeInfoSubscribe() Request to the AMF. The AMF then receives an Indication message transfer from the (R)AN (indicated by a dashed box). Finally, the AMF sends a Namf\_Communication\_NonUeInfoNotify() Notification to the CBCF. + +**Figure 9A.2.3.2-1: Indication message transfer procedure** + +- 1) If the CBCF supports reception of Restart Indication messages and Failure Indication messages then the CBCF uses the Namf\_Communication\_NonUeInfoSubscribe service operation to subscribe to these notifications. +- 2) A RAN Node sends a Restart Indication or a Failure Indication to the AMF. + +- 3 The AMF forwards the Restart Indication or a Failure Indication to the CBCF using the Namf\_Communication\_NonUeInfoNotify service operation. + +# 10 CBS Index + +An index structure is defined in this clause. Index can be used by the operator to inform the end user about the type of CBS services available. Index has the structure of a tree. It can thus have sub parts which are called subindexes. A subindex can be embedded in the same index message as its parent ("embedded subindex") or it can physically be in a separate index message ("child subindex"). Every index message has a unique message identifier. They are always of the same type. Message Code 1010101010b shall be used to indicate this type. The root of the index structure shall be the index message with message identifier 0. Other index messages are linked to the root index with links. Definition of their message identifiers is left to the operator. + +A format ("enhanced format") for the index messages is described in this clause. If this enhanced format is used in the index message the MS/UE can present the index messages in its preferred format. + +Available CBS services are introduced in the index. This means that their message identifier and name are stated. Enhanced format includes a mechanism for separating a normal service introduction from embedded subindex introduction and child subindex introduction. The introduction of an embedded subindex specifies the "subindex-id" used for identifying services that belong to this subindex. Embedded subindexes can have subindexes embedded in them etc. If these "second level embedded subindexes" are introduced their subindex-id shall begin with the subindex-id of their parent. Same principle applies for subindexes in third, fourth etc. level. An example of an index structure is given in figure 6. + +Enhanced format includes a mechanism which allows the terminals to identify that the format of the index message is enhanced. The index-id -field and the above mentioned Message Code (1010101010b) constitute this mechanism: + +``` + +message-format = index-id index-element-intro+. + +index-id = "EI" version crlf. + +version = number+. + +number = "1" | "2" | "3" | "4" | "5" | "6" | "7" | "8" | "9" | "0". + +index-element-intro = subindex-intro | service-intro. + +subindex-intro = subindex-id " " subindex-name crlf. + +subindex-id = subindex-character+. + +subindex-character = "a" | "b" | ... | "z" | "A" | "B" | ... | "Z". + +subindex-name = name-character+. + +name-character =
rev1 | Rel-6 | 5.0.0 | 6.0.0 | Identification of a directory number in a CBS-Message-Information-Page | +| T#19 | TP-030038 | T2-030088 | 014 | Rel-6 | 6.0.0 | 6.1.0 | CB Data lenght | +| T#22 | TP-030267 | T2-030575 | 016 | Rel-6 | 6.1.0 | 6.2.0 | CB Data structure | +| CT#31 | CP-060126 | C1-060128 | 017r1 | Rel-7 | 6.2.0 | 7.0.0 | CBS – Reference correction | +| CT#41 | | | | | 7.0.0 | 8.0.0 | Upgrade to Rel-8 | +| CT#41 | CP-080535 | C1-083618 | 0019r
4 | Rel-8 | 7.0.0 | 8.0.0 | Additions to the protocol aspects of CBS for the realisation of ETWS | +| CT#41 | CP-080535 | C1-083620 | 0018r
5 | Rel-8 | 7.0.0 | 8.0.0 | Changes to CBS for the realisation of ETWS | +| CT#41 | CP-080535 | C1-083621 | 0020r
5 | Rel-8 | 7.0.0 | 8.0.0 | Changes to the radio message format aspect of CBS for the realisation of ETWS | +| CT#42 | CP-080836 | C1-085355 | 0021r
3 | Rel-8 | 8.0.0 | 8.1.0 | Clarification on EPS architecture and ETWS Instruction to terminal | +| CT#42 | CP-080836 | C1-085354 | 0022r
1 | Rel-8 | 8.0.0 | 8.1.0 | Addition of Warning Security Information | +| CT#42 | CP-080873 | C1-085129 | 0023 | Rel-8 | 8.0.0 | 8.1.0 | CBS Message ID table | +| CT#43 | CP-090149 | C1-091099 | 0026r
2 | Rel-8 | 8.1.0 | 8.2.0 | ETWS Duplication Detection | +| CT#43 | CP-090159 | C1-090442 | 0025r
1 | Rel-8 | 8.1.0 | 8.2.0 | Clarification of non settable Message ID's through MMI | +| CT#43 | | | | | 8.1.0 | 8.2.0 | Editorial cleanup by MCC | + +| | | | | | | | | +|-------|-----------|-----------|------------|--------|--------|--------|---------------------------------------------------------------------------------| +| CT#44 | CP-090320 | | 0027r
2 | Rel-8 | 8.2.0 | 8.3.0 | Definition of ETWS Primary Notification message format | +| CT#44 | CP-090434 | C1-092257 | 0028r
2 | Rel-9 | 8.3.0 | 9.0.0 | Message IDs for the U.S. Commercial Mobile Alert System (CMAS) | +| CT#45 | CP-090686 | C1-092466 | 0029 | Rel-9 | 9.0.0 | 9.1.0 | Message Identifiers for PWS | +| CT#45 | CP-090670 | C1-093124 | 0031r
1 | Rel-9 | 9.0.0 | 9.1.0 | CBS activation time for ETWS information | +| CT#45 | CP-090682 | C1-093812 | 0032r
1 | Rel-9 | 9.0.0 | 9.1.0 | Cell wide Geographical Scope (GS) code 00 | +| CT#45 | CP-090682 | C1-093249 | 0033 | Rel-9 | 9.0.0 | 9.1.0 | Updates on references | +| CT#45 | CP-090682 | C1-093813 | 0034r
1 | Rel-9 | 9.0.0 | 9.1.0 | Resolution of editor's note | +| CT#45 | CP-090682 | C1-093251 | 0035 | Rel-9 | 9.0.0 | 9.1.0 | Fixes for typographical errors | +| CT#45 | CP-090682 | C1-093252 | 0036r
1 | Rel-9 | 9.0.0 | 9.1.0 | Clarification on duplicate use of "immediate display" | +| CT#45 | CP-090686 | C1-093531 | 0037 | Rel-9 | 9.0.0 | 9.1.0 | Updating of references to stage 1 document | +| CT#46 | CP-090912 | C1-094929 | 0039 | Rel-9 | 9.1.0 | 9.2.0 | Additional ETWS requirements for the BSC - CBC Cell Broadcast protocol | +| CT#46 | CP-090912 | C1-095394 | 0041r
1 | Rel-9 | 9.1.0 | 9.2.0 | Clarification on ETWS secondary notification | +| CT#46 | CP-090912 | C1-095396 | 0043r
1 | Rel-9 | 9.1.0 | 9.2.0 | Correction of duplicate detection in the UE | +| CT#47 | CP-100152 | C1-101202 | 0044r
1 | Rel-9 | 9.2.0 | 9.3.0 | Corrections to the Cell Broadcast Service (CBS) for ETWS | +| CT#47 | CP-100135 | C1-100625 | 0045 | Rel-9 | 9.2.0 | 9.3.0 | Correction of figure 4b | +| CT#47 | CP-100152 | C1-101263 | 0046r
1 | Rel-9 | 9.2.0 | 9.3.0 | Addition of Broadcast Message Type | +| CT#48 | CP-100345 | C1-101950 | 0050r
1 | Rel-9 | 9.3.0 | 9.4.0 | PLMN handling for ETWS duplicate detection | +| CT#48 | CP-100345 | C1-101551 | 0052 | Rel-9 | 9.3.0 | 9.4.0 | Removal of editor's note for ETWS | +| CT#49 | CP-100501 | C1-102734 | 0053r
1 | Rel-9 | 9.4.0 | 9.5.0 | Clarification of precedence for immediate display | +| CT#49 | CP-100504 | C1-102216 | 0055 | Rel-9 | 9.4.0 | 9.5.0 | Removal of CMAS reference to a ETWS capability | +| CT#49 | CP-100520 | C1-102735 | 0054r
1 | Rel-10 | 9.5.0 | 10.0.0 | Clarification of Scope for CB in LTE | +| CT#49 | CP-100520 | C1-103152 | 0057 | Rel-10 | 9.5.0 | 10.0.0 | Clarification of definition of "PLMN Wide" in Geographical Scope (GS) indicator | +| CT#50 | CP-100744 | C1-105127 | 0058r
2 | Rel-10 | 10.0.0 | 10.1.0 | Correction to CMAS Alert levels | +| CT#50 | CP-100768 | C1-104243 | 0056r
3 | Rel-11 | 10.1.0 | 11.0.0 | Message Identifiers for EU-Alert | +| CT#50 | CP-100768 | C1-104483 | 0057 | Rel-11 | 10.1.0 | 11.0.0 | Message Identifier for EU-Info | +| CT#51 | CP-110876 | C1-114785 | 0065r
3 | Rel-11 | 11.0.0 | 11.1.0 | Correction on Message Identifier for Korean Public Alert System | +| CT#51 | CP-110882 | C1-114427 | 0066r
2 | Rel-11 | 11.0.0 | 11.1.0 | Coding of Geographical Scope parameter for E-UTRAN/LTE operation. | + +| | | | | | | | | +|-------|-----------|-----------|------------|--------|--------|--------|-------------------------------------------------------------------------------------------------| +| CT#51 | CP-110853 | C1-115046 | 0070r
3 | Rel-11 | 11.0.0 | 11.1.0 | Correction to UE warning message indication with regards to "digital signature" and "timestamp" | +| CT#51 | CP-110882 | C1-115255 | 0071r
2 | Rel-11 | 11.0.0 | 11.1.0 | Additional Message Identifiers for CMAS/EU-Alerts | +| CT#51 | CP-110882 | C1-114923 | 0072r
1 | Rel-11 | 11.0.0 | 11.1.0 | Update Number Processing | +| CT#51 | CP-110882 | C1-114975 | 0073r
1 | Rel-11 | 11.0.0 | 11.1.0 | Multiple languages used in CBS | +| CT#55 | CP-120125 | C1-120857 | 0083r
3 | Rel-11 | 11.1.0 | 11.2.0 | Sorting out inconsistency problem in ETWS/PWS specification | +| CT#55 | CP-120125 | C1-120285 | 0084 | Rel-11 | 11.1.0 | 11.2.0 | Correction of binary coding in clause 9.4.1.2.2 | +| CT#55 | CP-120091 | C1-120804 | 0077r
2 | Rel-11 | 11.1.0 | 11.2.0 | Redocumentation and alignment of the public warning system | +| CT#56 | CP-120309 | C1-122384 | 0081r
4 | Rel-11 | 11.2.0 | 11.3.0 | Alignment of clause 9 for PWS | +| CT#56 | CP-120309 | C1-121379 | 0091r
1 | Rel-11 | 11.2.0 | 11.3.0 | Correction to the duplication detection mechanism | +| CT#56 | CP-120285 | C1-121245 | 0092 | Rel-11 | 11.2.0 | 11.3.0 | Removal of security for ETWS/PWS over E-UTRAN | +| CT#56 | CP-120285 | C1-122295 | 0088r
3 | Rel-11 | 11.2.0 | 11.3.0 | Alignment and correction of aspects for public warning system for GERAN | +| CT#57 | CP-120573 | C1-123198 | 0094r
3 | Rel-11 | 11.3.0 | 11.4.0 | Correction to Figure 3.3-1 | +| CT#57 | CP-120567 | C1-123186 | 0103r
1 | Rel-11 | 11.3.0 | 11.4.0 | Correction of Warning Message Delivery Procedure in GSM | +| CT#57 | CP-120492 | - | 0098r
1 | Rel-11 | 11.3.0 | 11.4.0 | Correction of reference to GSMA document "Coding of Cell Broadcast Functions" | +| CT#58 | CP-120794 | C1-123955 | 0095r
2 | Rel-11 | 11.4.0 | 11.5.0 | Correction for Repetition Rates | +| CT#58 | CP-120794 | C1-123956 | 0107r
1 | Rel-11 | 11.4.0 | 11.5.0 | Correction of reference in Restart Indication Request | +| CT#58 | CP-120774 | C1-123875 | 0111r
1 | Rel-11 | 11.4.0 | 11.5.0 | Correcting handling of unused security parameters for warning messages | +| CT#58 | CP-120794 | C1-124990 | 0116r
2 | Rel-11 | 11.4.0 | 11.5.0 | Message IDs for Operator specific services | +| CT#58 | CP-120794 | C1-125024 | 0117r
2 | Rel-11 | 11.4.0 | 11.5.0 | USIM file usage for PWS message reception | +| CT#58 | CP-120819 | C1-124972 | 0097r
5 | Rel-12 | 11.5.0 | 12.0.0 | Report from MME on Warning Message Delivery | +| CT#58 | CP-120819 | C1-124971 | 0099r
4 | Rel-12 | 11.5.0 | 12.0.0 | Failure List in WRITE-REPLACE-WARNING-CONFIRM and STOP-WARNING-CONFIRM | +| CT#59 | CP-130115 | C1-130829 | 0120r
2 | Rel-12 | 12.0.0 | 12.1.0 | Correction for Warning Area List | +| CT#59 | CP-130129 | C1-130831 | 0123r
2 | Rel-12 | 12.0.0 | 12.1.0 | Clause 9.4.3 for E-UTRAN | +| CT#59 | CP-130115 | C1-130837 | 0124r
2 | Rel-12 | 12.0.0 | 12.1.0 | Warning message reception in Limited Service | +| CT#60 | CP-130264 | C1-132520 | 0125r
3 | Rel-12 | 12.1.0 | 12.2.0 | CB Message parameter format on the eUTRAN Radio Network – UE interface | + +| | | | | | | | | +|---------------|-----------|-----------|------------|--------|--------|--------|---------------------------------------------------------------------------------------------------| +| CT#60 | CP-130264 | C1-131445 | 0127r
1 | Rel-12 | 12.1.0 | 12.2.0 | CBS message parameter references correction | +| CT#60 | CP-130264 | C1-131446 | 0128r
1 | Rel-12 | 12.1.0 | 12.2.0 | Failure Indication and Restart Indication handling | +| CT#60 | CP-130264 | C1-131725 | 0129r
2 | Rel-12 | 12.1.0 | 12.2.0 | Clarification to data coding scheme usage for primary vs secondary notification | +| CT#61 | CP-130503 | C1-133320 | 0118r
3 | Rel-12 | 12.2.0 | 12.3.0 | Stop-all broadcasting of warning messages and report from MME on Stop Warning Messages in E-UTRAN | +| CT#61 | CP-130510 | C1-133206 | 0132r
1 | Rel-12 | 12.2.0 | 12.3.0 | CellID in E-UTRAN | +| CT#61 | CP-130510 | C1-133207 | 0133r
1 | Rel-12 | 12.2.0 | 12.3.0 | Clarification on Duplication Detection | +| CT#61 | CP-130510 | C1-133646 | 0134r
1 | Rel-12 | 12.2.0 | 12.3.0 | Clarification on PWS CB Data for the eUTRAN Radio interface | +| Post
CT#61 | | | | Rel-12 | 12.3.0 | 12.3.1 | Correction of typos | +| CT#62 | CP-130750 | C1-134137 | 0137r
2 | Rel-12 | 12.3.1 | 12.4.0 | eNodeB ID in Stop-Warning Indication | +| CT#62 | CP-130762 | C1-134530 | 0139 | Rel-12 | 12.3.1 | 12.4.0 | Removal of cells=all feature from RNC | +| CT#62 | CP-130751 | C1-134930 | 0140r
1 | Rel-12 | 12.3.1 | 12.4.0 | Stop all indicator clarification | +| CT#63 | CP-140140 | C1-140609 | 0135r
5 | Rel-12 | 12.4.0 | 12.5.0 | Restart Indication | +| CT#63 | CP-140144 | C1-140440 | 0141r
1 | Rel-12 | 12.4.0 | 12.5.0 | Capacity Indication Request not implemented | +| CT#64 | CP-140331 | C1-141098 | 0142 | Rel-12 | 12.5.0 | 12.6.0 | Available-Capacity not implemented | +| CT#64 | CP-140327 | C1-141642 | 0143r
1 | Rel-12 | 12.5.0 | 12.6.0 | Support of category indication for prioritization of emergency alerts | +| CT#66 | CP-140836 | C1-144414 | 0146 | Rel-12 | 12.6.0 | 12.7.0 | Removal of CAPACITY-INDICATION reference | +| CT#66 | CP-140858 | C1-144827 | 0147r
1 | Rel-13 | 12.7.0 | 13.0.0 | Missing Broadcast Message Content Validity Indicator IE | +| CT#68 | CP-150310 | C1-150914 | 0149 | Rel-13 | 13.0.0 | 13.1.0 | Correction for List of TAls | +| CT#68 | CP-150310 | C1-151465 | 0151r
1 | Rel-13 | 13.0.0 | 13.1.0 | Clarification on CBC Geo-redundancy support in LTE | +| CT#68 | CP-150329 | C1-151463 | 0152r
1 | Rel-13 | 13.0.0 | 13.1.0 | Serial Number handling for WRITE-REPLACE Request/Indication primitive | +| CT#68 | CP-150310 | C1-151830 | 0154 | Rel-13 | 13.0.0 | 13.1.0 | Warning message indication delivery for PWS reporting enhancement | +| CT#68 | CP-150329 | C1-151831 | 0155 | Rel-13 | 13.0.0 | 13.1.0 | ETWS Primary Notification message at E-UTRAN interface | +| CT#68 | CP-150329 | C1-152386 | 0156r
1 | Rel-13 | 13.0.0 | 13.1.0 | Reference corrections and editorial updates | +| CT#70 | CP-150700 | C1-154874 | 0157r
4 | Rel-13 | 13.1.0 | 13.2.0 | Failure Indication | +| CT#71 | CP-160086 | C1-160316 | 0159 | Rel-13 | 13.2.0 | 13.3.0 | Failed cell list parameter content correction | + +| Change history | | | | | | | | +|----------------|---------|-----------|------|-----|-----|------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2016-09 | CP-73 | CP-160519 | 0160 | 2 | F | RESET COMPLETE and RESET FAILURE Response messages missing | 14.0.0 | +| 2017-06 | CP-76 | CP-171092 | 0161 | 2 | C | Addition of new Message Identifiers for FCC mandated Wireless Emergency Alert (WEA, aka CMAS) enhancements | 14.1.0 | +| 2017-12 | CP-78 | CP-173067 | 0165 | 1 | F | Correction to the Data Coding Scheme clause in support of NA regulatory requirement | 14.2.0 | +| 2017-12 | CP-78 | CP-173069 | 0166 | 3 | B | Support of PWS in 5GS | 15.0.0 | +| 2018-03 | CP-79 | CP-180077 | 0167 | 2 | B | PWS message format for NG-RAN in 5G | 15.1.0 | +| 2018-03 | CP-79 | CP-180077 | 0168 | 3 | B | AMF to CBC inter-connectivity solution option with and without IWF | 15.1.0 | +| 2018-03 | CP-79 | CP-180077 | 0169 | 2 | B | PWS in NR – clause 9.1.3.5 | 15.1.0 | +| 2018-03 | CP-79 | CP-180077 | 0170 | 2 | B | PWS in NR – clause 9.2.0 | 15.1.0 | +| 2018-03 | CP-79 | CP-180077 | 0171 | 1 | B | PWS in NR – clause 9.2.x | 15.1.0 | +| 2018-03 | CP-79 | CP-180077 | 0172 | 3 | B | PWS in NR – clause 9.3.x | 15.1.0 | +| 2018-03 | CP-79 | CP-180077 | 0173 | 1 | B | AMF, CBC and CBCF functionalities for PWS in 5G | 15.1.0 | +| 2018-03 | CP-79 | CP-180077 | 0174 | | B | Service Based Interface for 5G System | 15.1.0 | +| 2018-06 | CP-80 | CP-181057 | 0175 | 1 | F | Corrections to table 6 and consistent use of terminology | 15.2.0 | +| 2018-06 | CP-80 | CP-181057 | 0176 | | F | Addition of reference to TS 23.502 | 15.2.0 | +| 2018-06 | CP-80 | CP-181057 | 0177 | 1 | B | Addition of entity functionality subclauses in annex B | 15.2.0 | +| 2018-06 | CP-80 | CP-181057 | 0178 | 1 | F | Correction for the use of NG-RAN node and other general corrections | 15.2.0 | +| 2018-06 | CP-80 | CP-181057 | 0180 | 3 | F | Addition of reference point between AMF and CBCF | 15.2.0 | +| 2018-06 | CP-80 | CP-181057 | 0181 | | F | Removal of Extended Repetition-Period IE for NG-RAN | 15.2.0 | +| 2018-06 | CP-80 | CP-181057 | 0182 | | F | Correction Warning message content and removal of editor's | 15.2.0 | +| 2018-06 | CP-80 | CP-181058 | 0183 | 2 | F | Clarification on no use of container for PWS messages via N2 | 15.2.0 | +| 2018-09 | CP-81 | CP-182128 | 0184 | 1 | B | Modifications needed to address NG-RAN over SBc | 15.3.0 | +| 2018-09 | CP-81 | CP-182128 | 0185 | 1 | F | Corrections to IE names for NG-RAN | 15.3.0 | +| 2018-09 | CP-81 | CP-182128 | 0186 | 1 | F | Solving Editor's notes for PWS | 15.3.0 | +| 2018-09 | CP-81 | CP-182158 | 0189 | 6 | B | Warning Area Coordinates in WRITE-REPLACE WARNING REQUEST | 15.3.0 | +| 2018-12 | CP-82 | CP-183030 | 0192 | 1 | F | Duplicate detection for EUTRA connected to both EPC and 5GCN | 15.4.0 | +| 2018-12 | CP-82 | CP-183030 | 0193 | | F | Resolving the EN for the PWS restoration procedure for NG-RAN | 15.4.0 | +| 2019-03 | CP-83 | CP-190100 | 0194 | 4 | F | Additional Message Identifier to direct UEs to perform geo-fencing of CMAS messages | 15.5.0 | +| 2019-03 | CP-83 | CP-190082 | 0195 | 1 | F | Corrections on Warning Area List and TAIs for NG-RAN | 15.5.0 | +| 2019-03 | CP-83 | CP-190082 | 0198 | 1 | F | Correction on applicability of List of TAIs | 15.5.0 | +| 2019-03 | CP-83 | CP-190064 | 0200 | | F | Incorrect reference | 16.0.0 | +| 2019-09 | CP-85 | CP-192071 | 0201 | | F | Missing references and some editorial cleanup | 16.1.0 | +| 2019-12 | CP-86 | CP-193105 | 0202 | 3 | B | Addition of the support of ePWS functionality via E-UTRAN and NG-RAN | 16.2.0 | +| 2019-12 | CP-86 | CP-193105 | 0203 | 3 | B | Support of language-independent content mapped to a disaster in a warning message | 16.2.0 | +| 2020-03 | CP-87e | CP-200128 | 0204 | | F | Misalignment of 23.041 with 23.007 and 23.527 | 16.3.0 | +| 2020-03 | CP-87e | CP-200110 | 0205 | | F | Procedures for an ETWS/CMAS-capable UE in NG-RAN | 16.3.0 | +| 2020-03 | CP-87e | CP-200118 | 0208 | 2 | B | Addition of message identifiers for UEs with no user interface | 16.3.0 | +| 2020-03 | CP-87e | CP-200118 | 0209 | 1 | B | Support of a stored language-independent content referenced by a warning message | 16.3.0 | +| 2020-06 | CP-88e | CP-201100 | 0207 | 2 | F | Removal of Duplicate Service Operation Details | 16.4.0 | +| 2020-06 | CP-88e | CP-201100 | 0212 | | F | Correction to figure | 16.4.0 | +| 2020-06 | CP-88e | CP-201100 | 0213 | | F | Corrections to references | 16.4.0 | +| 2020-06 | CP-88e | CP-201100 | 0214 | 1 | F | Subscription management in PWS-IWF | 16.4.0 | +| 2020-06 | CP-88e | CP-201131 | 0217 | 1 | F | Handling of Concurrent Warning Message Indicator | 16.4.0 | +| 2020-06 | CP-88e | CP-201115 | 0218 | | F | Deletion of Editor's note in the clause 9.3.24 Warning-Type for ETWS | 16.4.0 | \ No newline at end of file diff --git a/marked/Rel-16/23_series/23079/00504fc688ebcf131ccbeff94dfc9939_img.jpg b/marked/Rel-16/23_series/23079/00504fc688ebcf131ccbeff94dfc9939_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c74492bf139cd5bbcbcd4e919c279dc6c6259e74 --- /dev/null +++ b/marked/Rel-16/23_series/23079/00504fc688ebcf131ccbeff94dfc9939_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e32bb1614cf9d67f96679ee34da2221d916706923bebca2d2d3e0b0333f22691 +size 130426 diff --git a/marked/Rel-16/23_series/23079/053f1077d592e6622cd21dc4bb4cb366_img.jpg b/marked/Rel-16/23_series/23079/053f1077d592e6622cd21dc4bb4cb366_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..68d2426ab2035f55afbb6e177677545a99fc4c0a --- /dev/null +++ b/marked/Rel-16/23_series/23079/053f1077d592e6622cd21dc4bb4cb366_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:13d2d4b892e70683ca38a2864df5fa88335f98f393db363a12bce40a0bc9cfa0 +size 131896 diff --git a/marked/Rel-16/23_series/23079/0b87abe67b21a93777287649c33e755d_img.jpg b/marked/Rel-16/23_series/23079/0b87abe67b21a93777287649c33e755d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..669b57715d0b16293217ab2a9e5a8592e2b2fb49 --- /dev/null +++ b/marked/Rel-16/23_series/23079/0b87abe67b21a93777287649c33e755d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:123cc69c35a9f117494603dab782a57d6bb9a77fe0fc32bb173b01d48f24192e +size 76500 diff --git a/marked/Rel-16/23_series/23079/26d664119ad25250780f554633444e54_img.jpg b/marked/Rel-16/23_series/23079/26d664119ad25250780f554633444e54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0f7cf745fbe890b2355e350d882d4996caa293fd --- /dev/null +++ b/marked/Rel-16/23_series/23079/26d664119ad25250780f554633444e54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c86a1e06e5378ea81b5309bbc0d5d47d8bf74d182ca2d11b1bbcaef2504ad49b +size 101551 diff --git a/marked/Rel-16/23_series/23079/28d75f39a24203712ee907b32cf0bbe5_img.jpg b/marked/Rel-16/23_series/23079/28d75f39a24203712ee907b32cf0bbe5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a1c42920ab896366b841d0f4a61689fe5753580e --- /dev/null +++ b/marked/Rel-16/23_series/23079/28d75f39a24203712ee907b32cf0bbe5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:396959c6ed095b80dd68165e862b5197841e2e343251fd6160453c7e86061085 +size 81944 diff --git a/marked/Rel-16/23_series/23079/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg b/marked/Rel-16/23_series/23079/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..56fbd1747b395b8e3a736d3a8fe2fa78e3b5894e --- /dev/null +++ b/marked/Rel-16/23_series/23079/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:72ba06b1a5a4ed07ab3ecada3bf2582a13c2a31dfe4ad894ccf6cfacba426f97 +size 72384 diff --git a/marked/Rel-16/23_series/23079/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg b/marked/Rel-16/23_series/23079/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..42c9ee6cfdb656fb199bb10a201df4db0c5da9dc --- /dev/null +++ b/marked/Rel-16/23_series/23079/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:63f9607a2b26ac017dc6db59bd53e5c1dd6a08ed97c1221efb10fb5688f43c28 +size 113312 diff --git a/marked/Rel-16/23_series/23079/90ddb84c323b956e2d50a54d3f870566_img.jpg b/marked/Rel-16/23_series/23079/90ddb84c323b956e2d50a54d3f870566_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..065a2c6b9ca8335fcd5bca8106ba03eee03ea6a0 --- /dev/null +++ b/marked/Rel-16/23_series/23079/90ddb84c323b956e2d50a54d3f870566_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0284c350219a360b29d1c8c3a2ee2cb1dda4c9dc663ce14596003f25ba0d27c2 +size 100012 diff --git a/marked/Rel-16/23_series/23079/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/Rel-16/23_series/23079/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ae0e5c68555780067bddf4a3c12504abe3f8db17 --- /dev/null +++ b/marked/Rel-16/23_series/23079/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c254df4c362e7bb2ad0ce2c0813da4c0055d800771900b2e32d7948d69e9134b +size 81617 diff --git a/marked/Rel-16/23_series/23079/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg b/marked/Rel-16/23_series/23079/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f44beac8f28da52c79bbabbeb6afc3ad3b79b198 --- /dev/null +++ b/marked/Rel-16/23_series/23079/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a9bda85b7a2f4427bff77d993dcfae72d161e32cd2983a7da07500cd0e815ef6 +size 93233 diff --git a/marked/Rel-16/23_series/23079/b5335262987c819d7f71ce40f99cb71b_img.jpg b/marked/Rel-16/23_series/23079/b5335262987c819d7f71ce40f99cb71b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9e2e35cfb7682a00c30fe02e06690457cd879a2a --- /dev/null +++ b/marked/Rel-16/23_series/23079/b5335262987c819d7f71ce40f99cb71b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:95b38656ffbb267a911e86d44ae987e6a6729b0db18e22ec0bde44c1ba0f8314 +size 132294 diff --git a/marked/Rel-16/23_series/23079/d0abac95583b52a3b35f74a215567334_img.jpg b/marked/Rel-16/23_series/23079/d0abac95583b52a3b35f74a215567334_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2eb8fd53f939d151a1631ac27a46ae1365e872a2 --- /dev/null +++ b/marked/Rel-16/23_series/23079/d0abac95583b52a3b35f74a215567334_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e935cb3f7d7ad27638685d21064d8de2e9090921096d41e764c28ab3d58e4a56 +size 80096 diff --git a/marked/Rel-16/23_series/23079/dd5771673aececa53d42ece89218299d_img.jpg b/marked/Rel-16/23_series/23079/dd5771673aececa53d42ece89218299d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..25dcbc778647fc89fac502a126e830cbcc52acf4 --- /dev/null +++ b/marked/Rel-16/23_series/23079/dd5771673aececa53d42ece89218299d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e968f41f80d2c4efcd24f4a1113bbbaf0aa5e4ba7946642611b7c8a8a3c5ae7d +size 118809 diff --git a/marked/Rel-16/23_series/23079/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/marked/Rel-16/23_series/23079/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1e27fac1336895f0dc9cb3bf832ee4e7c7365e9a --- /dev/null +++ b/marked/Rel-16/23_series/23079/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:af7339b07e535aa066fdb106939c9fbe04d736f1868d81b5ac539a2ed58b2e2b +size 73044 diff --git a/marked/Rel-16/23_series/23079/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg b/marked/Rel-16/23_series/23079/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..042e8e5d1bb7d0611cf25453ca3d29578e129406 --- /dev/null +++ b/marked/Rel-16/23_series/23079/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:64839eff440d35844d1da3cb695f9551bc75ecfb8b944e92899f9c76587e4502 +size 131721 diff --git a/marked/Rel-16/23_series/23079/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/marked/Rel-16/23_series/23079/ff0952ef692c9d960ce5f6708bcc9711_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0751f98e28b6657e05e466023b7fd6addfe70bca --- /dev/null +++ b/marked/Rel-16/23_series/23079/ff0952ef692c9d960ce5f6708bcc9711_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:15cd1282572232863c3e9727d646a8bf9f93dfd8fbbe21a9777577b0fdc8e5d7 +size 70042 diff --git a/marked/Rel-16/23_series/23079/raw.md b/marked/Rel-16/23_series/23079/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..3a98149d57402e3dd5eec734db91d65222506464 --- /dev/null +++ b/marked/Rel-16/23_series/23079/raw.md @@ -0,0 +1,1283 @@ + + + + + + +# Contents + +| | | +|------------------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Definitions and abbreviations ..... | 6 | +| 3.1 Definitions..... | 6 | +| 3.2 Abbreviations ..... | 7 | +| 4 Architecture..... | 7 | +| 4.1 Optimal routeing for basic mobile-to-mobile calls ..... | 7 | +| 4.2 Optimal routeing for conditional call forwarding ..... | 9 | +| 5 Optimal routeing for basic mobile-to-mobile calls: message flows ..... | 10 | +| 5.1 Successful outcome..... | 11 | +| 5.2 Unsuccessful outcome..... | 12 | +| 5.2.1 B subscriber address not recognised as belonging to a UMTS or GSM PLMN ..... | 12 | +| 5.2.2 HLRB or VLRB does not support optimal routeing ..... | 12 | +| 5.2.3 OR charging requirements contravened..... | 12 | +| 6 Optimal routeing for conditional call forwarding: message flows ..... | 13 | +| 6.1 Early call forwarding..... | 13 | +| 6.1.1 Forwarding without interrogation of VLRB..... | 13 | +| 6.1.1.1 Successful outcome..... | 13 | +| 6.1.1.2 Unsuccessful outcome ..... | 14 | +| 6.1.2 Forwarding after interrogation of VLRB ..... | 14 | +| 6.1.2.1 Successful outcome..... | 14 | +| 6.1.2.2 Unsuccessful outcome ..... | 15 | +| 6.2 Late call forwarding ..... | 16 | +| 6.2.1 Successful outcome ..... | 17 | +| 6.2.2 Unsuccessful outcome..... | 17 | +| 6.2.2.1 GMSC does not support OR..... | 17 | +| 6.2.2.2 HLRB does not support OR..... | 17 | +| 6.2.2.3 VMSCB/VLRB does not support OR..... | 17 | +| 6.2.2.4 OR charging requirements contravened ..... | 17 | +| 7 Interactions between optimal routeing and supplementary services..... | 18 | +| 7.1 Call forwarding ..... | 18 | +| 7.2 Closed User Group (CUG)..... | 18 | +| 7.3 Advice of Charge ..... | 18 | +| 7.4 Call barring..... | 18 | +| 7.5 Other supplementary services ..... | 19 | +| 8 Interactions between optimal routeing and other network features ..... | 19 | +| 8.1 Operator determined barring ..... | 19 | +| 8.2 CAMEL..... | 19 | +| 9 Functional requirements of entities performing optimal routeing ..... | 20 | +| 9.1 Charging requirements for optimal routeing..... | 20 | +| 9.2 Functional behaviour of VMSCA ..... | 21 | +| 9.3 Functional behaviour of VLRA..... | 21 | +| 9.4 Functional behaviour of GMSC ..... | 21 | +| 9.4.1 Procedure OR_Set_ORA_Parameters..... | 21 | +| 9.4.2 Procedure OR_Handle_RCH..... | 21 | +| 9.4.3 Procedure Route_Permitted..... | 22 | +| 9.4.4 Procedure OR_Handle_SRI_Negative_Response..... | 22 | +| 9.5 Functional behaviour of HLR ..... | 28 | +| 9.5.1 Procedure OR_HLR_CF ..... | 29 | +| 9.5.2 Procedure OR_HLR_Interrogate_VLR..... | 29 | +| 9.6 Functional behaviour of VLRB..... | 33 | +| 9.6.1 Functional behaviour of VLRB for provision of subscriber information..... | 33 | + +| | | | +|-------------------------------|------------------------------------------------------------------|-----------| +| 9.6.2 | Functional behaviour of VLRB for roaming number allocation ..... | 33 | +| 9.6.3 | Functional behaviour of VLRB when handling an incoming call..... | 33 | +| 9.7 | Functional behaviour of VMSCB ..... | 33 | +| 9.7.1 | Procedure Handle_ORLCF_VMSC ..... | 33 | +| 10 | Contents of messages..... | 34 | +| 10.1 | Messages on the B interface (MSC-VLR) ..... | 35 | +| 10.1.1 | Send Info For Outgoing Call ..... | 35 | +| 10.1.2 | Send Info For Outgoing Call negative response..... | 35 | +| 10.1.3 | Send Info For Incoming Call..... | 35 | +| 10.1.4 | Send Info For Incoming Call ack ..... | 35 | +| 10.1.5 | Send Info For Incoming Call negative response ..... | 35 | +| 10.1.6 | Complete Call..... | 35 | +| 10.1.7 | Process Call Waiting ..... | 36 | +| 10.2 | Messages on the C interface (MSC-HLR) ..... | 36 | +| 10.2.1 | Send Routeing Info ..... | 36 | +| 10.2.2 | Send Routeing Info ack ..... | 37 | +| 10.2.3 | Send Routeing Info negative response ..... | 37 | +| 10.3 | Messages on the D interface (VLR-HLR)..... | 37 | +| 10.3.1 | Provide Roaming Number ..... | 37 | +| 10.3.2 | Provide Roaming Number ack ..... | 37 | +| 10.3.3 | Provide Roaming Number negative response ..... | 38 | +| 10.3.4 | Provide Subscriber Information ..... | 38 | +| 10.3.5 | Provide Subscriber Information ack ..... | 38 | +| 10.4 | Messages on the E interface (MSC-MSC) ..... | 38 | +| 10.4.1 | Resume Call Handling..... | 38 | +| 10.4.2 | Resume Call Handling ack ..... | 38 | +| 10.4.3 | Resume Call Handling negative response ..... | 39 | +| Annex A (informative): | Handling of an IAM at an MSC..... | 40 | +| Annex B (informative): | Change history..... | 41 | + +# --- Foreword + +This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). + +The present document specifies the technical realisation of the first phase of the network feature Support of Optimal Routeing (SOR) within the 3GPP system. + +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 technical realisation of the first phase of the network feature Support of Optimal Routeing (SOR). The first phase of SOR provides: + +- as a network operator option, a method to route a call from one mobile subscriber directly to another mobile subscriber who is in the same country as the calling mobile subscriber or in the called mobile subscriber's home country, without needing to connect the call via the HPLMN of the called subscriber, even though the called mobile subscriber has roamed outside his HPLMN; +- a method to forward calls when a called mobile subscriber who has roamed outside his home country is busy, or is not reachable, or does not reply, to a forwarded-to destination in the HPLMN country of the called subscriber or the VPLMN country of the called subscriber, without needing to connect the forwarded call via the VPLMN of the called subscriber; +- a method to combine the optimal routeing described in the first bullet point above with the optimal routeing described in the second bullet point above. + +OR of a call is permitted only if all entities involved in handling the call support OR. + +Other cases of optimal routeing (e.g. calls where the calling and called subscribers are in different countries, forwarding to a mobile subscriber or multiple forwarding) will be considered for inclusion in later phases. + +# --- 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] GSM 03.04: "Digital cellular telecommunications system (Phase 2+); Signalling requirements relating to routeing of calls to mobile subscribers". +- [2] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [3] 3GPP TS 22.079: "Support of Optimal Routeing (SOR); Service definition - Stage 1". +- [4] 3GPP TS 22.082: "Call Forwarding (CF) supplementary services - Stage 1". +- [5] 3GPP TS 23.003: "Numbering, addressing & identification". +- [6] 3GPP TS 23.018: "Basic call handling; Technical realization". +- [7] 3GPP TS 23.078: "Customized Applications for Mobile network Enhanced Logic (CAMEL) - Phase 3; Stage 2". +- [8] 3GPP TS 23.085: "Closed User Group (CUG) Supplementary Service - Stage 2". +- [9] 3GPP TS 23.087: "User-to-User Signalling (UUS) - Stage 2". +- [10] 3GPP TS 23.172: "Technical realization of Circuit Switched (CS) multimedia service; UDI/RDI fallback and service modification" + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the following terms and definitions apply. + +**A subscriber:** calling subscriber, who may be fixed or mobile + +**B subscriber:** mobile subscriber originally called by the A subscriber + +**C subscriber:** subscriber to whom the B subscriber has requested that calls be forwarded. The C subscriber may be fixed or mobile + +**Direct route:** call takes the direct route if the route from the serving PLMN of the A subscriber to the serving PLMN of the B subscriber is defined by the MSRN of the B subscriber rather than by the MSISDN of the B subscriber + +**Early call forwarding:** call forwarding from the IPLMN before the call has been extended to the VPLMN of the forwarding subscriber + +**HPLMN leg:** portion of the HPLMN route from the serving MSC of the A subscriber to an MSC in the HPLMN of the B subscriber + +**HPLMN route:** call takes the HPLMN route if the route from the serving MSC of the A subscriber to the serving MSC of the B subscriber is defined by the MSISDN of the called subscriber. This forces the call to be routed via the HPLMN of the B subscriber + +**Interrogating PLMN (IPLMN):** PLMN which interrogates the HPLMN of the B subscriber to obtain information to route the call to that subscriber or to the forwarded-to destination defined by the called mobile subscriber. The IPLMN is also the VPLMN of the A subscriber + +**Late call forwarding:** call forwarding after the call has been extended to the VPLMN of the forwarding subscriber. Late call forwarding may be invoked in the IPLMN or the VPLMN of the forwarding subscriber + +**Reference address:** address which defines the maximum charge which the A party is prepared to pay for the call leg which he originates + +**Routeing address:** address which the GMSC uses to route a call towards the B subscriber or the C subscriber + +## 3.2 Abbreviations + +Abbreviations used in the present document are listed in TS 21.905 [2]. + +For the purposes of the present document, the following abbreviations apply: + +| | | +|------------|---------------------------------------------------------------------------------| +| BOIZC | Barring of Outgoing InterZonal Calls | +| BOIZC-exHC | Barring of Outgoing InterZonal Calls except those directed to the HPLMN Country | +| CMN | CAMEL Modified Number | +| FTN | Forwarded-To Number | +| FTNW | Forwarded-To NetWork | +| GMSCA | The GMSC in the IPLMN, which may also be VMSCA | +| GMSCB | The GMSC in HPLMNB | +| GMSCC | The GMSC in HPLMNC | +| HLRB | The HLR of the B subscriber | +| HLRC | The HLR of the C subscriber | +| HPLMNB | The HPLMN of the B subscriber | +| HPLMNC | The HPLMN of the C subscriber | +| IAM | Initial Address Message | +| IPLMN | Interrogating PLMN | +| ORLCF | Optimal Routeing for Late Call Forwarding | +| PRN | Provide Roaming Number | +| PSI | Provide Subscriber Information | +| RCH | Resume Call Handling | +| SIFIC | Send Information For Incoming Call | +| SIFOC | Send Information For Outgoing Call | +| SRI(B) | Send Routeing Information (Basic call) | +| SRI(F) | Send Routeing Information (Forwarding information) | +| VLRA | The VLR of the A subscriber | +| VLRB | The VLR of the B subscriber | +| VMSCA | The VMSC of the A subscriber | +| VMSCB | The VMSC of the B subscriber | + +# --- 4 Architecture + +## 4.1 Optimal routeing for basic mobile-to-mobile calls + +It is a network operator option whether to implement optimal routeing for basic mobile-to-mobile calls. + +The existing UMTS and GSM architectures support the primary technical requirement of optimal routeing for mobile-to-mobile calls (basic OR): that a GMSC can interrogate an HLR in a different PLMN to obtain routeing information for a mobile terminated call (see GSM 03.04 [1]). Three logically distinct PLMNs are involved in the handling of an optimally routed mobile-to-mobile call: + +- the IPLMN, which is also the VPLMN of the calling mobile subscriber; +- the HPLMN of the called mobile subscriber (HPLMNB); +- the VPLMN of the called mobile subscriber (VPLMNB). + +Any two or all three of these PLMNs may be identical; in figure 1 they are shown as distinct. + +Figure 1 shows the communication between the IPLMN, HPLMNB and VPLMNB for an optimally routed mobile-to-mobile call. + + + +Figure 1: Architecture for optimal routing of basic mobile-to-mobile call. The diagram shows the signaling flow between various network elements. On the left, a box labeled IPLMN contains VMSCA, GMSCA, and gsmSSF. On the right, a box labeled VPLMNB contains VMSCB and VLRB. At the bottom left, a box labeled HPLMNA contains gsmSCF. At the bottom center, a box labeled HPLMNB contains HLRB. Solid arrows represent signaling paths: from VMSCA to GMSCA, from GMSCA to VMSCB (labeled IAM (ISUP)), from gsmSSF to gsmSCF (labeled Initial DP/ Connect), from gsmSCF to HLRB (labeled Send Routeing Info/ack), and from HLRB to VLRB (labeled Provide Roaming Number/ack). Dashed arrows represent data paths: from VMSCA to HLRB (labeled Send Routeing Info/ack) and from HLRB to GMSCA (labeled Provide Roaming Number/ack). + +**Figure 1: Architecture for optimal routing of basic mobile-to-mobile call** + +In figure 1 and throughout the present document, the term ISUP is used to denote the telephony signalling system used between exchanges. In this architecture the VMSC of the calling mobile subscriber (VMSCA) is integrated with the GMSC; communication between them is over an internal interface. A gsmSSF may also be associated with VMSCA, to support CAMEL functionality. This is one way to support optimal routing of mobile-to-mobile calls. Another way is to set up routing tables in GMSCA appropriately. + +If the originating subscriber has a CAMEL subscription, then when VMSCA receives the setup message it sends an Initial DP message, containing the address digits received in the setup message, via the gsmSSF to the gsmSCF. If the gsmSCF determines that the destination defined by the address digits belongs to a GSM or UMTS PLMN, it responds to the Initial DP with a Connect or Continue With Argument message to VMSCA containing an indication that the call is eligible for optimal routing. This causes VMSCA to route the call to the associated GMSC (GMSCA). + +If the GMSC is in the VPLMN of the calling mobile subscriber, is in a different PLMN from HLRB, it requests routing information from HLRB using the MAP protocol. If HLRB determines that the call can be routed directly from the GMSC to VMSCB without contravening the charging requirements for optimal routing given in subclause 9.1, it requests a roaming number from VLRB using the MAP protocol, and VLRB returns a roaming number in the Provide Roaming Number ack. HLRB returns the roaming number to the GMSC in the Send Routeing Info ack. The GMSC uses the roaming number to construct an ISUP IAM, which it sends to VMSCB. The call is then handled according to the procedures defined in 3GPP TS 23.018 [6], except that if the call is answered GMSCA relays the answer event to VMSCA and includes the destination address which it used to route the call, to allow VMSCA to generate the correct charging record. + +**NOTE:** If the GMSC relays an answer event to VMSCA before it has received an Answer message from the final destination (e.g. because of an interaction with a Specialised Resource Function) an incorrect destination address (or no destination address) can be sent to VMSCA, even though the call is eventually optimally routed. + +## 4.2 Optimal routing for conditional call forwarding + +Some cases of call forwarding on mobile subscriber not reachable (CFNRc) are handled in the IPLMN, without the call being extended to the VPLMN of the forwarding subscriber. For these cases, referred to in the present document as early call forwarding, the forwarding is already optimally routed. + +When a call has been extended from the GMSC to VMSCB, the procedures defined in 3GPP TS 23.018 [6] lead to any conditional call forwarding being routed from VMSCB to the forwarded-to destination; this is referred to in this specification as late call forwarding. Optimal routing for late call forwarding (ORLCF) allows VMSCB to return control of the call to the GMSC, which can then route the call to the forwarded-to destination. + +Figure 2 shows the architecture for ORLCF. Phase 1 of SOR does not include optimal routing of forwarding to a mobile subscriber, so optimal routing of the forwarding leg is not considered. + + + +``` + +graph TD + subgraph IPLMN + GMSC[GMSC] + end + subgraph VPLMNB + VMSCB[VMSCB] + end + subgraph Forwarded-to_Network [Forwarded-to Network] + LE[Forwarded-to LE] + end + subgraph HPLMNB + HLRB[(HLRB)] + end + + GMSC --> VMSCB : IAM (ISUP) + VMSCB --> GMSC : Resume Call Handling/ack (MAP) + VMSCB --> GMSC : Release (ISUP) + GMSC --> LE : IAM (ISUP) + VMSCB -.-> HLRB : Send Forwarding Info/ack (MAP) + +``` + +Figure 2: Architecture for optimal routing of late call forwarding. The diagram shows four network entities: IPLMN (containing GMSC), VPLMNB (containing VMSCB), Forwarded-to Network (containing Forwarded-to LE), and HPLMNB (containing HLRB). The flow is: 1. GMSC sends IAM (ISUP) to VMSCB. 2. VMSCB sends Resume Call Handling/ack (MAP) to GMSC. 3. VMSCB sends Release (ISUP) to GMSC. 4. GMSC sends IAM (ISUP) to Forwarded-to LE. 5. VMSCB sends Send Forwarding Info/ack (MAP) to HLRB. + +**Figure 2: Architecture for optimal routing of late call forwarding** + +After the call has been extended from the GMSC to VMSCB, if the VMSC/VLR determines that the call should be forwarded it requests the GMSC to resume call handling. The GMSC uses the forwarding information received in the request to resume call handling, or interrogates HLRB for forwarding information, depending on the indication received from the HLR with the roaming number. If the GMSC determines that the call can be routed directly to the forwarded-to destination without contravening the charging requirements for optimal routing given in subclause 9.1 it acknowledges the request, clears the traffic connection to VMSCB and sends an ISUP IAM to the forwarded-to local exchange. + +# 5 Optimal routing for basic mobile-to-mobile calls: message flows + +It is a network operator option whether to implement optimal routing for basic mobile-to-mobile calls. + +This clause does not consider the handling of calls to a fixed network B subscriber. + +The description in this clause of the handling of optimal routeing for basic mobile-to-mobile calls is informative, not normative. Further, the description does not consider the effects of other services or features, except where these are specifically mentioned. + +The message flow for an optimally routed call from one mobile subscriber to another mobile subscriber is shown in figure 3. For simplicity of description, it is assumed that forwarding of calls from the B subscriber is not required. Solid lines indicate circuit-associated signalling; dashed lines indicate connectionless signalling. + + + +``` + +sequenceDiagram + participant VMSCA as VMSCA/ GMSCA (IPLMN) + participant gsmSCF as gsmSCF (HPLMNA) + participant GMSCB as GMSCB (HPLMNB) + participant HLRB as HLRB (HPLMNB) + participant VLRB as VLRB (VPLMNB) + participant VMSCB as VMSCB (VPLMNB) + + Note left of VMSCA: Setup + VMSCA-->>gsmSCF: Initial DP + gsmSCF-->>VMSCA: Connect/ OR1:Y + VMSCA-->>gsmSCF: Continue with arg + VMSCA-->>HLRB: SRI(B) + Note right of HLRB: OR2:Y + Note right of HLRB: OR3:Y + HLRB-->>VLRB: PRN + VLRB-->>HLRB: PRN ack + Note right of HLRB: OR4:Y + HLRB-->>VMSCA: SRI ack + VMSCA->>VMSCB: IAM + + VMSCA-->>gsmSCF: Connect/ OR1:N + VMSCA-->>gsmSCF: Continue with arg + Note right of HLRB: OR3:N + HLRB-->>VLRB: PSI + VLRB-->>HLRB: PSI ack + HLRB-->>VLRB: PRN + VLRB-->>HLRB: PRN ack + Note right of HLRB: OR4:N + HLRB-->>VMSCA: SRI error + VMSCA->>GMSCB: IAM + GMSCB-->>HLRB: SRI(B) + HLRB-->>VLRB: PRN + VLRB-->>HLRB: PRN ack + HLRB-->>GMSCB: SRI ack + GMSCB->>VMSCB: IAM + +``` + +The diagram illustrates the message flow for an optimally routed call. It shows interactions between IPLMN (VMSCA/GMSCA), HPLMNA (gsmSCF), HPLMNB (GMSCB, HLRB), and VPLMNB (VLRB, VMSCB). The flow includes initial setup, CAMEL interaction (Initial DP, Connect), and Send Routing Information (SRI) procedures. It depicts different scenarios based on optimal routeing (OR) flags: OR1, OR2, OR3, and OR4. Solid lines represent circuit-associated signaling (IAM), while dashed lines represent connectionless signaling (MAP/CAP messages like SRI, PRN, PSI). + +Sequence diagram showing message flow for optimal routeing of basic mobile-to-mobile call between IPLMN, HPLMNA, HPLMNB, and VPLMNB. + +**Figure 3: Message flow for optimal routeing of basic mobile-to-mobile call** + +## 5.1 Successful outcome + +When VMSCA receives a Setup message from the MS, it sends a request for information to handle the outgoing call to VLRA, according to the procedures described in 3GPP TS 23.018 [6]. If VLRA determines that the MS is allowed + +service, it returns a positive acknowledgement, including an indication that the subscriber has a CAMEL subscription, so that VMSCA will request instructions via the gsmSSF (not shown in this diagram) from the gsmSCF. + +If the gsmSCF recognises the B subscriber address as belonging to a UMTS or GSM PLMN (decision OR1:Y), it sends a Connect message or a Continue With Argument message, containing an indication that the call is eligible for optimal routeing, to VMSCA. This causes VMSCA to route the call to the associated GMSC function (GMSCA). GMSCA checks the identity of HPLMNB. If GMSCA is in a different PLMN from HLRB, it then sends a request for routeing information (SRI(B)) to HLRB; this request contains an indication that it is an optimal routeing enquiry for information to route a basic call. If HLRB is prepared to accept an optimal routeing enquiry from GMSCA (decision OR2:Y), it checks whether at least one of the three conditions: + +- the GMSC is in the same country as VMSCB; +- the HLR is in the same country as VMSCB; +- the GMSC is in the same PLMN as the HLR; + +is met. If it is (decision OR3:Y), HLRB sends a request for a roaming number (PRN) to VLRB; the request contains an indication that it is for an optimally routed call. If VLRB supports optimal routeing (decision OR4:Y), it returns the roaming number in the PRN ack, and HLRB relays the roaming number in the SRI ack to GMSCA. GMSCA constructs an ISUP IAM using the roaming number, and sends it to VMSCB, which processes the incoming IAM according to the procedures described in 3GPP TS 23.018 [6]. + +## 5.2 Unsuccessful outcome + +Error situations which lead to failure of the call, rather than non-optimal routeing, are not described in this subclause. + +### 5.2.1 B subscriber address not recognised as belonging to a UMTS or GSM PLMN + +If the gsmSCF does not recognise the B subscriber address as belonging to a UMTS or GSM PLMN (decision OR1:N), it sends a Connect or Continue With Argument message, omitting the indication that the call is eligible for optimal routeing. VMSCA constructs an IAM using the B subscriber address and sends it to GMSCB in HPLMNB. GMSCB analyses the address received in the IAM, and sends a request for routeing information (SRI(B)) to HLRB; this request contains an indication that it is not an optimal routeing enquiry. Because GMSCB is in the same PLMN as HLRB, it will always be able to derive an HLR address. HLRB sends a request for a roaming number (PRN) to VLRB. VLRB returns the roaming number in the PRN ack, and HLRB relays the roaming number in the SRI ack to GMSCB. GMSCB constructs an ISUP IAM using the roaming number, and sends it to VMSCB, which processes the incoming IAM according to the procedures described in 3GPP TS 23.018 [6]. + +### 5.2.2 HLRB or VLRB does not support optimal routeing + +If HLRB is not prepared to accept an optimal routeing enquiry from GMSCA , because: + +- it does not support optimal routeing for basic mobile-to-mobile calls, or +- because there is no agreement for optimal routeing for basic mobile-to-mobile calls between the operators of GMSCA and HLRB, or +- because optimal routeing of basic mobile-to-mobile calls to the specific B subscriber is not allowed, + +(decision OR2:N), it returns an SRI negative response (shown in figure 3 as 'SRI error'). This causes GMSCA to construct an IAM using the B subscriber address and send it to GMSCB, as described in subclause 5.2.1. + +If VLRB does not support optimal routeing (decision OR4:N), it returns a PRN negative response (shown in figure 3 as 'PRN error'). This causes HLRB to return an SRI negative response (shown in figure 3 as 'SRI error'), which in turn causes GMSCA to construct an IAM using the B subscriber address and send it to GMSCB, as described in subclause 5.2.1. + +### 5.2.3 OR charging requirements contravened + +If HLRB determines that the call cannot be routed directly from GMSCA to VMSCB without contravening the charging requirements for optimal routeing given in subclause 9.1 (decision OR3:N) it sends a request for subscriber information + +(PSI) to VLRB. VLRB sends a response indicating whether the B subscriber is detached or in some other state. If the B subscriber is not detached, HLRB sends an SRI negative response (shown in figure 3 as 'SRI error') to GMSCA, which constructs an IAM using the B subscriber address and sends it to GMSCB, as described in subclause 5.2.1. + +# --- 6 Optimal routeing for conditional call forwarding: message flows + +The description in this clause of the handling of optimal routeing for conditional call forwarding is informative, not normative. Further, the description does not consider the effects of other services or features, except where these are specifically mentioned. + +Two cases of conditional call forwarding are described in this clause: + +- early call forwarding to a fixed destination; +- late call forwarding to a fixed destination. + +For phase 1 of SOR, no attempt is made to route a call directly from the GMSC to a forwarded-to mobile subscriber; if the forwarded-to subscriber is mobile, the call is routed from the GMSC to a GMSC in the HPLMN of the forwarded-to subscriber. + +## 6.1 Early call forwarding + +Early call forwarding is defined as call forwarding from the IPLMN **before** the call has been extended to the VPLMN of the forwarding subscriber. CFU and CFNRc when the forwarding mobile subscriber is IMSI detached are examples of early call forwarding. Early call forwarding is effectively optimally routed, because the call takes the most direct route possible from the IPLMN to the forwarded-to destination. + +The message flows for early call forwarding to a fixed destination are shown in figure 4a (forwarding without VLR interrogation) and figure 4b (forwarding after VLR interrogation). The IPLMN is shown as distinct from HPLMNB, on the assumption that the original call towards the B subscriber was optimally routed; however if optimal routeing of basic mobile-to-mobile calls is not implemented, the IPLMN will be the same as HPLMNB. Solid lines indicate circuit-associated signalling; dashed lines indicate connectionless signalling. + +### 6.1.1 Forwarding without interrogation of VLRB + +#### 6.1.1.1 Successful outcome + +GMSCA sends a request for routeing information (SRI(B)) to HLRB. If HLRB determines that the call is to be forwarded without needing to signal to VLRB then HLRB returns the forwarded-to number (FTN) in the SRI ack. + +If GMSCA determines that the call can be forwarded to LEC without contravening the charging requirements for Support of Optimal Routeing given in subclause 9.1 (decision OR:Y) it constructs an ISUP IAM using the FTN and sends it to LEC. + + + +``` + +sequenceDiagram + participant GMSGA as GMSGA + participant GMSCB as GMSCB + participant HLRB as HLRB + participant VLRB as VLRB + participant VMSCB as VMSCB + participant LEC as LEC + + Note left of GMSGA: OR:Y + GMSGA->>HLRB: SRI(B) + HLRB-->>GMSGA: SRI ack + GMSGA->>LEC: IAM + Note left of GMSGA: OR:N + GMSGA->>GMSCB: IAM + GMSCB->>HLRB: SRI(B) + HLRB-->>GMSCB: SRI ack + GMSCB->>LEC: IAM + +``` + +Sequence diagram for early call forwarding to a fixed destination without interrogation of VLRB. Lifelines: IPLMN (GMSGA), HPLMNB (GMSCB, HLRB), VPLMNB (VLRB, VMSCB), and FTNW (LEC). The diagram shows two paths: OR:Y (forwarding to LEC) and OR:N (forwarding via GMSCB). + +**Figure 4a: Message flow for early call forwarding to a fixed destination - forwarding without interrogation of VLRB** + +#### 6.1.1.2 Unsuccessful outcome + +Error situations which lead to failure of the call, rather than non-optimal routeing, are not described in this subclause. + +If GMSGA determines that the call cannot be forwarded to LEC without contravening the charging requirements for Support of Optimal Routeing given in subclause 9.1 (decision OR:N) it constructs an IAM using the B subscriber address and sends it to GMSCB. + +GMSCB sends a request for routeing information (SRI(B)) to HLRB. If HLRB determines that the call is to be forwarded, as described in subclause 6.1.1.1, it returns the FTN in the SRI ack. + +GMSCB constructs an IAM using the FTN and sends it to LEC. + +### 6.1.2 Forwarding after interrogation of VLRB + +#### 6.1.2.1 Successful outcome + +GMSGA sends a request for routeing information (SRI(B)) to HLRB. HLRB sends a request for the subscriber status (PSI) to VLRB. If the record in VLRB for the B subscriber shows that the B subscriber is IMSI detached, VLRB indicates this in the PSI ack. Alternatively, if HLRB determines that at least one of the three conditions: + +- the GMSC is in the same country as VMSCB; +- the HLR is in the same country as VMSCB; +- the GMSC is in the same PLMN as the HL; + +is met, it sends a request for a roaming number (PRN) to VLRB. If the record in VLRB for the B subscriber shows that the B subscriber is IMSI detached, VLRB indicates this in a PRN negative response. If HLRB determines that CFNRc should be invoked, it returns the forwarded-to number (FTN) in the SRI ack. + +If GMSGA determines that the call can be forwarded to LEC without contravening the charging requirements for Support of Optimal Routeing given in subclause 9.1 (decision OR:Y) it constructs an ISUP IAM using the FTN and sends it to LEC. + + + +``` + +sequenceDiagram + participant GMSCA as GMSCA + participant GMSCB as GMSCB + participant HLRB as HLRB + participant VLRB as VLRB + participant VMSCB as VMSCB + participant LEC as LEC + + Note left of GMSCA: OR:Y + GMSCA->>HLRB: SRI(B) + HLRB->>VLRB: PSI + VLRB->>HLRB: PSI ack + HLRB->>GMSCA: SRI ack + GMSCA->>LEC: IAM + + Note left of GMSCA: OR:N + GMSCA->>GMSCB: IAM + GMSCB->>HLRB: SRI(B) + HLRB->>VLRB: PRN + VLRB->>HLRB: PRN ack + HLRB->>GMSCB: SRI ack + GMSCB->>LEC: IAM + +``` + +Sequence diagram showing message flow for early call forwarding to a fixed destination. Lifelines: IPLMN (GMSCA), HPLMNB (GMSCB, HLRB), VPLMNB (VLRB, VMSCB), and FTNW (LEC). The diagram shows two call attempts: OR:Y and OR:N. In the OR:Y attempt, GMSCA sends SRI(B) to HLRB, HLRB sends PSI to VLRB, VLRB sends PSI ack to HLRB, HLRB sends SRI ack to GMSCA, and GMSCA sends IAM to LEC. In the OR:N attempt, GMSCA sends IAM to GMSCB, GMSCB sends SRI(B) to HLRB, HLRB sends PRN to VLRB, VLRB sends PRN ack to HLRB, HLRB sends SRI ack to GMSCB, and GMSCB sends IAM to LEC. + +NOTE: HLRB may send a PRN to VLRB, and receive a PRN negative response indicating absent subscriber, to determine that CFNRc should be invoked. + +**Figure 4b: Message flow for early call forwarding to a fixed destination - forwarding after interrogation of VLRB** + +#### 6.1.2.2 Unsuccessful outcome + +Error situations which lead to failure of the call, rather than non-optimal routeing, are not described in this subclause. + +If GMSCA determines that the call cannot be forwarded to LEC without contravening the charging requirements for Support of Optimal Routeing given in subclause 9.1 (decision OR:N), it constructs an ISUP IAM using the B subscriber address and sends it to GMSCB. + +GMSCB sends a request for routeing information (SRI(B)) to HLRB. HLRB sends a request for a roaming number (PRN) to VLRB. If the record in VLRB for the B subscriber shows that the B subscriber is IMSI detached, VLRB indicates this in the PRN ack. If HLRB determines that CFNRc should be invoked, it returns the forwarded-to number (FTN) in the SRI ack. + +GMSCB constructs an IAM using the FTN and sends it to LEC. + +## 6.2 Late call forwarding + +Late call forwarding is defined as call forwarding **after** the call has been extended to the VPLMN of the forwarding subscriber. CFB, CFNRc on no response to paging and CFNRy are examples of late call forwarding. In the absence of OR, late call forwarding occurs in the VPLMN of the forwarding party; if OR applies, late call forwarding occurs in the IPLMN. + +The message flow for optimal routeing of late call forwarding to a fixed destination is shown in figure 5. The IPLMN may be distinct from HPLMNB or the same as HPLMNB, depending on whether or not the original call to VPLMNB was optimally routed, but this description assumes that the original call to VPLMNB was optimally routed. For + +simplicity of description, the separation of VMSCA and GMSCA (described in clause 5 & subclause 6.1) is omitted. Solid lines indicate circuit-associated signalling; dashed lines indicate connectionless signalling. + + + +``` + +sequenceDiagram + participant GMSC as GMSC + participant HLRB as HLRB + participant VLRB as VLRB + participant VMSCB as VMSCB + participant LEC as LEC + + Note left of GMSC: FIR:Y + GMSC-->>HLRB: SRI(B) + HLRB-->>VLRB: PRN + VLRB-->>HLRB: PRN ack + HLRB-->>GMSC: SRI ack + GMSC->>VMSCB: IAM + VMSCB-->>VLRB: SIFIC + VLRB-->>VMSCB: SIFIC ack + VMSCB-->>GMSC: RCH + Note left of GMSC: FIR:N + GMSC-->>HLRB: SRI(F) + HLRB-->>GMSC: SRI ack + Note left of GMSC: OR:Y + GMSC-->>VMSCB: RCH ack + Note left of GMSC: FIR:N + GMSC->>VMSCB: Release + Note left of GMSC: FIR:N + GMSC->>LEC: IAM + Note left of GMSC: FIR:N + GMSC-->>VMSCB: RCH error + VMSCB->>LEC: IAM + +``` + +Sequence diagram showing message flow for optimal routing of late call forwarding to a fixed destination. Lifelines: IPLMN (GMSC), HPLMNB (HLRB), VPLMNB (VLRB, VMSCB), and FTNW (LEC). + +Figure 5: Message flow for optimal routing of late call forwarding to a fixed destination + +### 6.2.1 Successful outcome + +The GMSC obtains a roaming number from HLRB to route the call to VMSCB, as described in subclause 5.1. The SRI ack also includes an indication of whether the GMSC should interrogate the HLR for routing information for late call forwarding. The GMSC constructs an IAM using the roaming number, and sends it to VMSCB. When VMSCB receives the IAM, it requests subscriber information for the incoming call (SIFIC) from VLRB. If VLRB determines that the call should be forwarded, because the called mobile subscriber is busy, or is not reachable, or has not replied to the call before the no-reply call timer has expired, it returns a SIFIC ack containing the forwarded-to number, the forwarding reason, the GMSC address and the call reference number to VMSCB. VMSCB sends a request to resume call handling (RCH) to the GMSC; the RCH includes the forwarded-to number, the forwarding reason and the basic service information received in the SIFIC ack. + +If the HLR indicated in the SRI ack which contained the MSRN that the GMSC should interrogate the HLR for forwarding information (FIR:Y), the GMSC then sends a request for forwarding information (SRI(F)), containing the forwarding reason and the basic service group which applies for this call, to HLRB. HLRB responds with the appropriate forwarded-to number. + +If the HLR indicated in the SRI ack which contained the MSRN that the GMSC should not interrogate the HLR for forwarding information (FIR:N), the GMSC checks the forwarded-to number received in the RCH. + +If the GMSC determines that the call can be forwarded to the forwarded-to destination without contravening the charging requirements for Support of Optimal Routeing given in subclause 9.1 (decision OR:Y) it: + +- sends an RCH ack to VMSCB to indicate that control of the call has been accepted; +- sends an ISUP Release message indicating normal clearing to VMSCB to release the traffic circuit; +- constructs an IAM using the forwarded-to number, and sends it to LEC. + +### 6.2.2 Unsuccessful outcome + +Error situations which lead to failure of the call, rather than non-optimal routeing, are not described in this subclause. + +#### 6.2.2.1 GMSC does not support OR + +If the GMSC does not support OR, it omits the 'or-capability' information element from the SRI(B) request. The HLR then sends the 'OR not supported in GMSC' indicator in the PRN to VLRB. VMSCB will not send the RCH to the GMSC if the 'OR not supported in GMSC' indicator was received in the PRN. Instead, the call will be forwarded at VMSCB. + +#### 6.2.2.2 HLRB does not support OR + +If HLRB does not support OR, it does not relay the GMSC address and the call reference number which it received in the SRI(B), so VMSCB cannot send the RCH to the GMSC. Instead, the call will be forwarded at VMSCB. + +#### 6.2.2.3 VMSCB/VLRB does not support OR + +If VMSCB/VLRB does not support OR, VMSCB cannot send the RCH to the GMSC. Instead, the call will be forwarded at VMSCB. + +#### 6.2.2.4 OR charging requirements contravened + +If the original call to VMSCB was optimally routed, the GMSC can route the call to the forwarded-to destination only if the charge to do so is no more than the charge to route the call to HPLMNB. If this requirement, determined as described in subclause 9.1, is not met (decision OR:N) the GMSC returns an RCH negative response (shown in figure 5 as 'RCH error') to VMSCB, which then forwards the call. + +If the original call to VMSCB was not optimally routed, the GMSC can route the call directly to the forwarded-to destination only if the charge to do so is no more than the charge for the routeing to VMSCB. If this requirement, determined as described in subclause 9.1, is not met (decision OR:N) the GMSC returns an RCH negative response (shown in figure 5 as 'RCH error') to VMSCB, which then forwards the call. + +# --- 7 Interactions between optimal routeing and supplementary services + +## 7.1 Call forwarding + +If an optimally routed call encounters early call forwarding, GMSCA attempts to route the call to the forwarded-to destination. The forwarded-to destination is the C subscriber if the C subscriber is not a mobile subscriber, or the HPLMN of the C subscriber if the C subscriber is a mobile subscriber. If GMSCA cannot route the call to the forwarded-to destination without contravening the charging requirements for Support of Optimal Routeing given in subclause 9.1, the call is routed to a GMSC in the HPLMN of the B subscriber. + +If an optimally routed call encounters late call forwarding, GMSCA attempts to route the call to the forwarded-to destination. The forwarded-to destination is the C subscriber if the C subscriber is not a mobile subscriber, or the HPLMN of the C subscriber if the C subscriber is a mobile subscriber. If GMSCA cannot route the call to the forwarded-to destination without contravening the charging requirements for Support of Optimal Routeing given in subclause 9.1, the call is routed from VMSCB to the forwarded-to destination. + +The handling of call forwarding at HLRB for optimally routed calls is encapsulated in the procedures First\_Forwarding\_HLR, PRN\_Error\_HLR, Handle\_CFB, Handle\_CFNRC and Handle\_CFNRY, which are specified in 3GPP TS 23.018 [6]. + +## 7.2 Closed User Group (CUG) + +The handling of CUG checking for outgoing calls at VLRA is encapsulated in the process OCH\_VLR, which is specified in 3GPP TS 23.018 [6]. + +The handling of CUG checking at HLRB is encapsulated in the procedures Subscription\_Check\_HLR and Forward\_CUG\_Check, which are specified in 3GPP TS 23.018 [6]. + +## 7.3 Advice of Charge + +Advice of Charge (Information) and Advice of Charge (Charging) do not take account of whether a call has been optimally routed. + +## 7.4 Call barring + +It has been accepted in principle that all supplementary service call barring programmes except for BAIC are applied for cost control reasons, and that therefore barring should be applied on the basis of the cost of the actual route taken by the call. For phase 1 of Support of Optimal Routeing, this principle does not apply. Barring of outgoing calls is applied on the basis of the B subscriber number. Barring of all incoming calls will prevent a call to the served mobile subscriber, whether or not the call is optimally routed. If Barring of Incoming Calls when roaming outside the home PLMN country is active and operative it will prevent a call to the B subscriber even if the A subscriber pays to route the call to the VMSC of the B subscriber. + +The handling of barring of outgoing calls at VLRA is encapsulated in the process OCH\_VLR, which is specified in 3GPP TS 23.018 [6]. + +The handling of barring of incoming calls at HLRB is encapsulated in the procedure Subscription\_Check\_HLR, which is specified in 3GPP TS 23.018 [6]. + +The interactions between barring of outgoing calls and call forwarding for phase 1 of Support of Optimal Routeing are defined in 3GPP TS 22.082 [4]. + +The interactions between BIC-Roam and call forwarding for phase 1 of Support of Optimal Routeing are defined in 3GPP TS 22.082 [4]. + +## 7.5 Other supplementary services + +The effects of the following supplementary services on optimally routed calls are identical to their effects on non-optimally routed calls, so they are omitted from the present document: + +- CLIP, CLIR, COLP, COLR (3GPP TS 23.081); +- CW, HOLD (3GPP TS 23.083); +- MPTY (3GPP TS 23.084); +- ECT (3GPP TS 23.091). + +# 8 Interactions between optimal routeing and other network features + +## 8.1 Operator determined barring + +The principles for the interactions between operator determined barring and optimal routeing are the same as those for interactions between supplementary service barring and optimal routeing. + +## 8.2 CAMEL + +The principles for interactions between CAMEL services and optimal routeing are specified in this subclause. The interworking between CAMEL processing and optimal routeing in the GMSC and the terminating VMSC is specified in subclause 9.4 and 3GPP TS 23.018 [6]. + +If a mobile-originating CAMEL service modifies the number entered by the A subscriber, VMSCA treats the number returned by the gsmSCF in the same way as a number received in the SETUP message, i.e.: + +: + +- If the gsmSCF indicated that the call is eligible for optimal routeing, VMSCA sends a signal containing the modified number to the associated GMSC, which sends a request for routeing information to the appropriate HLR; +- If the gsmSCF did not indicate that the call is eligible for optimal routeing, VMSCA sends an IAM containing the modified number to a GMSC in HPLMNB, which sends a request for routeing information to the appropriate HLR. + +If a mobile-terminating CAMEL service modifies the number received by the GMSC, the GMSC treats the number returned by the CAMEL server in the same way as a forwarded-to number, i.e. it checks it against the optimal routeing criteria in subclause 9.1 but does not analyse it to find if it can derive an HLR address. If the number returned by the CAMEL server does not satisfy the optimal routeing criteria in subclause 9.1 and the GMSC is not in the same PLMN as HLRB, the GMSC will route the call to a GMSC in the same PLMN as HLRB. This will lead to a repetition of the mobile terminating CAMEL interaction. + +If the call is to be forwarded early at the GMSC (whether by a UMTS-standardised call forwarding service or by a CAMEL-based call forwarding service) and a mobile originating CAMEL service applies to the forwarding subscriber, the GMSC checks the number which results from the CAMEL service against the optimal routeing criteria in subclause 9.1. If the number returned by the CAMEL server does not satisfy the optimal routeing criteria in subclause 9.1, the GMSC will not route the call to the forwarded-to destination. The GMSC will route the call to a GMSC in the same PLMN as HLRB. This will lead to a repetition of the mobile originating CAMEL interaction. + +If the call is optimally routed back to the GMSC (optimal routeing of late call forwarding) and a mobile originating CAMEL service applies to the forwarding subscriber, then the GMSC does not check the number which results from the CAMEL service against the optimal routeing criteria in subclause 9.1. + +**NOTE:** Service Logic designers should be aware that Optimal Routeing of Late Call Forwarding (ORLCF) may be combined with Optimal Routeing of basic mobile to mobile calls (Basic Optimal Routeing - BOR) in a single call. The ORLCF handling in the GMSC may be subject to Mobile Terminating (MT) CAMEL handling and Mobile Forwarding (MF) CAMEL handling, as depicted in Procedure OR\_Handle\_RCH. Both the MT CAMEL Service and the MF CAMEL Service may provide a new destination for the forwarded leg. + +When BOR and ORLCF are combined within one call, and the MT CAMEL Service or the MF CAMEL Service provides a new destination for the forwarded leg, then these CAMEL Services should take particular care, if they need to ascertain whether this new destination complies with the optimal routeing criteria as specified in subclause 9.1. + +# 9 Functional requirements of entities performing optimal routeing + +## 9.1 Charging requirements for optimal routeing + +MoU have imposed two constraints for the charging of optimally routed calls: + +- No subscriber shall pay more for a call which has been optimally routed than he would do under the present routeing scheme described in GSM 03.04 [1] in the subclauses describing the call cases where the GMSC is in the same PLMN as the HLR. +- At least for the first phase of Support of Optimal Routeing, the charge for one leg of a call shall be paid for entirely by one subscriber. + +These constraints mean that the direct route for a call cannot always be used. For example, if the calling mobile subscriber (the A subscriber) is in Germany, and the B subscriber's HPLMN is in Switzerland but he has roamed to Finland, the charge payable by the A subscriber to route the call by the direct route to Finland would be greater than the charge payable to route the call to HPLMNB, so the HPLMN route must be used. + +In the first phase of Support of Optimal Routeing, it cannot be assumed that a GMSC is able to calculate the charge payable for the direct route and the charge payable for the HPLMN leg. The MoU requirements can be met by applying more stringent (but simpler) criteria for deciding whether the direct route may be used: + +- If the country code of the destination exchange and the country code of the GMSC are the same, then the direct route may be used. +- Otherwise, for a call leg which is chargeable to the A subscriber, if the country code of the destination exchange and the country code of HPLMNB are the same, then the direct route may be used. +- Otherwise, the HPLMN route shall be used. + +In certain cases, the second criterion above (equality of country codes for the HPLMN and the destination exchange) may not be enough to determine equality of the charges payable for the direct route and the HPLMN route. In these cases, analysis of the national destination code as well as the country code is required; however the principle is still that if the two numbers are the same to the depth of analysis required then the direct route may be used. + +For optimal routeing of late call forwarding, the constraints are satisfied if the following criteria are applied: + +- if the country code of the forwarded-to exchange and the country code of the GMSC are the same, then the forwarded call may be routed directly from the GMSC to the forwarded-to exchange; +- otherwise, if the country code of the forwarded-to exchange and the country code of HPLMNB are the same, then the forwarded call may be routed directly from the GMSC to the forwarded-to exchange; +- otherwise, if the country code of the forwarded-to exchange and the country code of VPLMNB are the same, then the forwarded call may be routed directly from the GMSC to the forwarded-to exchange; +- otherwise the forwarded call shall be routed through VPLMNB. + +## 9.2 Functional behaviour of VMSCA + +The functional behaviour of VMSCA is specified in 3GPP TS 23.018 [6]. The only functions specific to optimal routeing are: + +- Routeing the call to the associated GMSC function if the gsmSCF indicates that the call is eligible for optimal routeing; +- The transfer of the destination address, if it is received in the indication of the answer event, to the call data record, to allow the correct charge for the call to be made. This function is required only if VMSCA supports optimal routeing of mobile-to-mobile calls. + +## 9.3 Functional behaviour of VLRA + +The functional behaviour of VLRA is specified in 3GPP TS 23.018 [6]. + +## 9.4 Functional behaviour of GMSC + +When a call is being forwarded the forwarding leg is controlled by a process MT\_CF\_MSC which runs in the forwarding MSC (VMSC or GMSC). If CAMEL processing of the forwarding leg indicates that Basic Optimal Routeing of the forwarding leg should be attempted, the forwarding MSC may use the services of an associated GMSC for the forwarding leg, i.e. the associated GMSC requests routeing information from HLRC. In this case, the forwarding leg is processed in the same way as a mobile-originated call from mobile subscriber B. + +The functional behaviour of a GMSC is specified in 3GPP TS 23.018 [6]. The procedures specific to Support of Optimal Routeing are specified in this subclause. + +### 9.4.1 Procedure OR\_Set\_ORA\_Parameters + +### 9.4.2 Procedure OR\_Handle\_RCH + +Sheet 1: if the GMSC receives O-CSI or D-CSI in Resume Call Handling, then the GMSC shall verify whether it supports the CAMEL Phases indicated in O-CSI and D-CSI. If either or both of O-CSI and D-CSI indicates CAMEL Phase 4, then the GMSC shall also verify whether the Offered CAMEL4 CSIs of the GMSC includes support for O-CSI and D-CSI. If the required CAMEL Phases or the required CAMEL4 CSIs are not supported in the GMSC, then the GMSC disallows the Optimal Routeing request. Refer to 3GPP TS 23.078 [7] for a description of the Offered CAMEL4 CSIs. + +Sheet 1: if the GMSC interrogates the HLR for a Forwarded-to number, the Routeing address is the Forwarded-to number received in the Send Routeing Info ack; otherwise the Routeing address is the Forwarded-to number received in the Resume Call Handling. + +Sheet 1: the task "Destination address := FTN" is executed only if the GMSC supports optimal routeing of basic mobile-to-mobile calls. + +Sheet 1: the procedure Route\_permitted is called to verify the number received in Resume Call Handling or the number received from HLR. If the result is "False", then the GMSC disallows the Optimal Routeing. The call forwarding will now be done by the VMSC. + +**Note** When the procedure Route\_permitted returns result "False", then the gsmSCF is not informed about the forwarding and can therefore not provide an alternative destination address. Reason is that once the gsmSCF is informed about forwarding, the call forwarding can not be returned to the VMSC. + +Sheet 2: the procedure CAMEL\_MT\_GMSC\_Notify\_CF is specific to CAMEL phase 2 or higher; it is specified in 3GPP TS 23.078 [7]. If the GMSC does not support CAMEL phase 2 or higher, processing continues from the "Continue" exit of the test "Result". + +If the result of the procedure CAMEL\_MT\_GMSC\_Notify\_CF is "Fail" or "Release", then the call will be released. + +If the result of the procedure CAMEL\_MT\_GMSC\_Notify\_CF is "Reconnect", then the GMSC allows the Optimal Routeing. The GMSC will then start a call forwarding process. + +Sheet 2: when the procedure Route\_permitted on sheet 1 returns result "False", then the GMSC returns "OR not allowed" to the VMSC. The call forwarding will now be done by the VMSC. + +Sheet 3: the procedure Activate\_CF\_Process is specified in 3GPP TS 23.018 [6]. When procedure Activate\_CF\_Process returns result "Release" or "Fail", the call is released. + +If the result is "Pass", then the GMSC allows the Optimal Routeing. + +Sheet 3: the procedure UUS\_GMSC\_Check\_Forwarding is specific to UUS; it is specified in 3GPP TS 23.087 [9]. + +Sheet 3: the procedure CAMEL\_Store\_Destination\_Address is specific to CAMEL phase 3 or higher; it is specified in 3GPP TS 23.078 [7]. + +Sheet 3: the called party address sent in the IAM to the process MT\_CF\_MSC is the Forwarded-to number received in the Perform Call Forwarding ack. + +Sheet 3: the process MT\_CF\_MSC is specified in 3GPP TS 23.018 [6]. + +### 9.4.3 Procedure Route\_Permitted + +### 9.4.4 Procedure OR\_Handle\_SRI\_Negative\_Response + +'Non-fatal' error situations, which cause the call to be routed through a GMSC in the same PLMN as the HLR, are: + +- Send Routeing Info request rejected because the HLR does not support OR. +- Protocol error. +- System failure. +- Unexpected data value. +- Data missing. +- OR not allowed. + +'Fatal' negative responses, which cause the GMSC to return a 'fail' result, are: + +- Unknown subscriber. +- Number changed. +- Bearer service not provisioned. +- Teleservice not provisioned. +- Call barred. +- CUG reject. +- Forwarding violation. +- Facility not supported. +- Absent subscriber. + + + +Procedure OR\_Set\_ORA\_Parameters + +ORSORAP1(1) + +``` +graph TD; Note[Procedure in the GMSC to determine the OR input parameters for the call of Obtain_Routing_Address] --- C1(( )); C1 --> D1{IAM from same PLMN as GMSC?}; D1 -- Yes --> D2{HLR & GMSC in same PLMN?}; D1 -- No --> P1[OR:=False; Own PLMN:= True]; D2 -- Yes --> P2[OR:=False; Own PLMN:= True]; D2 -- No --> P3[OR:=True; Own PLMN:= False]; P1 --> P4[Allocate call reference number]; P2 --> P4; P3 --> P4; P4 --> P5[Reference address:= Called party address]; P5 --> C2(( )); +``` + +Flowchart for Procedure OR\_Set\_ORA\_Parameters. It starts with a note about the procedure's purpose, then a connector, followed by a decision 'IAM from same PLMN as GMSC?'. If 'Yes', it goes to another decision 'HLR & GMSC in same PLMN?'. If 'Yes' to the second decision, it sets OR:=False; Own PLMN:= True. If 'No', it sets OR:=True; Own PLMN:= False. If 'No' to the first decision, it also sets OR:=False; Own PLMN:= True. All three paths converge to 'Allocate call reference number', then 'Reference address:= Called party address', and finally an exit connector. + +Figure 6: Procedure OR\_Set\_ORA\_Parameters + + + +### Procedure OR\_Handle\_RCH + +H\_RCH1(3) + +Flowchart for Procedure OR\_Handle\_RCH (sheet 1). The process starts with a decision 'D-CSI or D-CSN included?'. If 'No', it goes to 'Forwarding interrogation required?'. If 'Yes', it checks if 'GMSC supports requested CAMEL Phases and requested CAMEL4 CSIs?'. If 'No', it sets a negative response 'OR not allowed', sends a 'Resume Call Handling negative response', and results in 'Result = Refused'. If 'Yes', it proceeds to 'Forwarding interrogation required?'. From 'Forwarding interrogation required?', if 'No', it goes to 'Send Routing Info (Forwarding Info)'. If 'Yes', it checks 'Forwarding reason = Call deflection?'. If 'Yes', it goes to 'Send Routing Info (Forwarding Info)'. If 'No', it goes to 'Send Routing Info (Forwarding Info)'. From 'Send Routing Info (Forwarding Info)', it goes to 'Wait\_For\_Forwarding\_Info'. From 'Wait\_For\_Forwarding\_Info', it branches into three paths: 1) 'Send Routing Info ack' (From HLR) leads to 'BOR:=OR', 'Destination address:= FTN', 'OR' decision. If 'True', it goes to 'Route\_Permitted (OR, FTN, Reference Address)' and then 'Route permitted' decision. If 'True', it ends at connector '1'. If 'False', it ends at connector '2'. If 'False' from 'OR', it goes to 'Reference address:= Routeing address', 'OR:=True', then to 'Route\_Permitted'. 2) 'Send Routing Info negative response' (From HLR) leads to 'Set negative response: Forwarding failed', 'Resume Call Handling negative response', 'Release', 'Release call resources', 'Result = Release', and ends at connector 'X'. 3) 'Release' leads to 'Set negative response: Forwarding failed', 'Resume Call Handling negative response', 'Release', 'Release call resources', 'Result = Fail', and ends at connector 'X'. Callouts include: 'Procedure in the GMSC to handle a Resume Call Handling Request' (top left), 'Signals to/from the left are to/from the originating exchange; signals to/from the right are to/from the destination exchange unless indicated otherwise' (top right), and 'To HLR' (middle left). + +Figure 7a: Procedure OR\_Handle\_RCH (sheet 1) + + + +### Procedure OR\_Handle\_RCH + +H\_RCH2(3) + +Procedure in the GMSC to handle a Resume Call Handling request + +Signals to/from the left are to/from the originating exchange; signals to/from the right are to/from the destination exchange unless indicated otherwise + +``` +sequenceDiagram + participant 1 + participant GMS_C as GMS_C Notify_CF + participant Result? as Result? + participant 2 + participant 3 + Note left of GMS_C: Procedure in the GMSC to handle a Resume Call Handling request + Note right of GMS_C: Signals to/from the left are to/from the originating exchange; signals to/from the right are to/from the destination exchange unless indicated otherwise + Note left of GMS_C: See TS 23.078 + + 1->>GMS_C: + GMS_C-->>Result?: + Result?-->>2: Reconnect + Result?-->>3: Fail + Result?-->>3: Release + Result?-->>3: Continue + + Note right of 2: Set negative response: OR not allowed + Note right of 2: Resume Call Handling negative response + Note right of 2: Result:= Refused + 2-->>X2((X)) + + Note right of 3: Set negative response: Forwarding failed + Note right of 3: Resume Call Handling negative response + Note right of 3: Release + Note right of 3: Release call resources + Note right of 3: Result:= Release + 3-->>X3((X)) + + Note right of Fail: Set negative response: Forwarding failed + Note right of Fail: Resume Call Handling negative response + Note right of Fail: Release + Note right of Fail: Release call resources + Note right of Fail: Result:= Fail + Fail-->>XFail((X)) +``` + +Sequence diagram for Procedure OR\_Handle\_RCH (sheet 2). The diagram starts at connector 1, proceeds to a GMS\_C Notify\_CF message, then a Result? decision. The decision has four branches: Reconnect, Fail, Release, and Continue. The Reconnect branch leads to connector 2. The Fail and Release branches lead to connector 3. The Continue branch also leads to connector 3. Connector 2 leads to a Set negative response: OR not allowed message, then a Resume Call Handling negative response message, then a Result:= Refused message, ending at a circle with an X. Connector 3 leads to a Set negative response: Forwarding failed message, then a Resume Call Handling negative response message, then a Release message, then a Release call resources message, then a Result:= Release message, ending at a circle with an X. The Fail branch also leads to a Set negative response: Forwarding failed message, then a Resume Call Handling negative response message, then a Release message, then a Release call resources message, then a Result:= Fail message, ending at a circle with an X. + +Figure 7b: Procedure OR\_Handle\_RCH (sheet 2) + + + +**Procedure OR\_Handle\_RCH** **H\_RCH3(3)** + +*Procedure in the GMSC to handle a Resume Call Handling request* + +*Signals to/from the left are to/from the originating exchange; signals to/from the right are to/from the destination exchange unless indicated otherwise* + +``` +graph TD; Start((3)) --> ActivateCF[Activate CF_Process]; Note1[See TS 23.018] -.-> ActivateCF; ActivateCF --> Result{Result?}; Result -- Release --> SetNeg1[Set negative response: Forwarding failed]; SetNeg1 --> ResNeg1[Resume Call Handling negative response]; ResNeg1 --> Release1[Release]; Release1 --> ReleaseRes1[Release call resources]; ReleaseRes1 --> ResultRelease[Result:= Release]; ResultRelease --> Exit1((X)); Result -- Pass --> ResumeAck[Resume Call Handling ack]; ResumeAck --> Release2[Release]; Release2 --> UUS[UUS_GMSC_Check_Forwarding]; Note2[See TS 23.087] -.-> UUS; UUS --> CAMEL[CAMEL_Store_Destination_Address (BOR True)]; Note3[See TS 23.078] -.-> CAMEL; CAMEL --> FTN[Initial Address (FTN)]; Note4[To Process MT_CF_MSC] -.-> FTN; FTN --> ResultPass[Result:=Pass]; ResultPass --> Exit2((X)); Result -- Fail --> SetNeg2[Set negative response: Forwarding failed]; SetNeg2 --> ResNeg2[Resume Call Handling negative response]; ResNeg2 --> Release3[Release]; Release3 --> ReleaseRes3[Release call resources]; ReleaseRes3 --> ResultFail[Result:= Fail]; ResultFail --> Exit3((X)); +``` + +Flowchart for Procedure OR\_Handle\_RCH. It starts with a connector '3', leading to 'Activate CF\_Process' (See TS 23.018). A decision 'Result?' follows. 'Release' leads to 'Set negative response: Forwarding failed', then 'Resume Call Handling negative response', 'Release', 'Release call resources', 'Result:= Release', and an exit circle. 'Pass' leads to 'Resume Call Handling ack', 'Release', 'UUS\_GMSC\_Check\_Forwarding' (See TS 23.087), 'CAMEL\_Store\_Destination\_Address (BOR True)' (See TS 23.078), 'Initial Address (FTN)' (To Process MT\_CF\_MSC), 'Result:=Pass', and an exit circle. 'Fail' leads to 'Set negative response: Forwarding failed', then 'Resume Call Handling negative response', 'Release', 'Release call resources', 'Result:= Fail', and an exit circle. + +Figure 7c: Procedure OR\_Handle\_RCH (sheet 3) + + + +### Procedure Route\_Permitted + +RP1(1) + +Procedure to check whether routing is permitted to the specified address + +Procedure Route\_Permitted +FPAR IN OR, Requested address, +Reference Address +IN/OUT Route permitted + +``` +graph TD; Start([ ]) --> OR{OR}; OR -- False --> RP1[Route permitted:= True]; OR -- True --> CC_Det{CC of requested address can be determined?}; CC_Det -- False --> CSI_Rec{O-CSI and/or D-CSI received in RCH?}; CC_Det -- True --> YesNo1{Yes/No}; YesNo1 -- Yes --> CC_GMSC[CC of requested address= CC of GMSC]; YesNo1 -- No --> YesNo2{Yes/No}; YesNo2 -- Yes --> CC_Ref[CC of requested address= CC of reference address]; YesNo2 -- No --> RP2[Route permitted:= False]; CSI_Rec -- Yes --> RP3[Route permitted:= True]; CSI_Rec -- No --> RP4[Route permitted:= False]; RP1 --> End1((X)); RP2 --> End2((X)); RP3 --> End3((X)); RP4 --> End4((X)); CC_GMSC --> RP1; CC_Ref --> RP1; +``` + +Flowchart for Procedure Route\_Permitted. It starts with an oval connector, leading to an 'OR' decision diamond. If 'False', it goes to 'Route permitted:= True'. If 'True', it goes to 'CC of requested address can be determined?' diamond. If 'False', it goes to 'O-CSI and/or D-CSI received in RCH?' diamond. If 'Yes', it goes to 'Route permitted:= True'. If 'No', it goes to 'Route permitted:= False'. If 'True' from the second diamond, it goes to a 'Yes'/'No' decision diamond. If 'Yes', it goes to 'CC of requested address= CC of GMSC' box, then to 'Route permitted:= True'. If 'No', it goes to another 'Yes'/'No' decision diamond. If 'Yes', it goes to 'CC of requested address= CC of reference address' box, then to 'Route permitted:= True'. If 'No', it goes to 'Route permitted:= False'. All 'Route permitted' boxes lead to circle-with-X connectors. + +Figure 8: Procedure Route\_Permitted + + + +Procedure OR\_Handle\_SRI\_Negative\_Response + +H\_SRINR1(1) + +``` +graph TD; Start([Start]) --> OwnPLMN{Own PLMN}; OwnPLMN -- True --> Join(( )); OwnPLMN -- False --> Repeat{Repeat interrogation?}; Repeat -- No --> Join; Repeat -- Yes --> RA[Routeing address := Reference address]; RA --> DA[Destination address := Reference address]; DA --> OR[OR := False]; OR --> Res[Result := Pass]; Res --> Join; Join --> Fail[Result := Fail]; Fail --> End(( )); +``` + +Procedure in the GMSC to handle a Send Routeing Info negative response for optimal routeing + +Flowchart for Procedure OR\_Handle\_SRI\_Negative\_Response. It starts with a note about handling negative responses in the GMSC. The flowchart includes a decision 'Own PLMN' (True/False), a decision 'Repeat interrogation?' (No/Yes), and several process steps including 'Routeing address := Reference address', 'Destination address := Reference address', 'OR := False', and final results 'Result := Fail' or 'Result := Pass'. + +Figure 9: Procedure OR\_Handle\_SRI\_Negative\_Response + +## 9.5 Functional behaviour of HLR + +The functional behaviour of an HLR is specified in 3GPP TS 23.018 [6]. The procedures specific to Support of Optimal Routeing are specified in this subclause. + +### 9.5.1 Procedure OR\_HLR\_CF + +Sheet 1: if the HLR does not support optimal routeing of basic mobile-to-mobile calls, the test "Optimal routeing allowed" takes the "No" exit. + +Sheet 2: the procedures Handle\_CFB, Handle\_CFNRc and Handle\_CFNRy are specified in 3GPP TS 23.018 [6]. + +### 9.5.2 Procedure OR\_HLR\_Interrogate\_VLR + +If the HLR does not support optimal routeing of basic mobile-to-mobile calls, this procedure will be executed only if the Send Routeing Info was from a GMSC in the same PLMN as the HLR, i.e. this was not an Optimal Routeing enquiry. + +The procedure Handle\_CFNRc is specified in 3GPP TS 23.018 [6]. + + + +### Procedure OR\_HLR\_CF + +ORHLRCF1(2) + +Procedure in the HLR to handle optimally routed call forwarding + +``` + +graph TD + Start([ ]) --> D1{Forwarding +enquiry?} + D1 -- Yes --> D2{Forwarding +interrogation +supported?} + D1 -- No --> D3{Optimal +Routeing +enquiry?} + + D2 -- Yes --> C2((2)) + D2 -- No --> P1[Set negative +response: +Facility not +supported] + + D3 -- No --> D4{Optimal +routeing +allowed?} + D3 -- Yes --> R1[Result:= +Continue] + + D4 -- No --> P2[Set negative +response: +OR not +allowed] + D4 -- Yes --> R1 + + P1 --> C1((1)) + P2 --> C1 + C1 --> R2[Result:= +Fail] + + R2 --> End1((X)) + R1 --> End2((X)) + +``` + +Flowchart for Procedure OR\_HLR\_CF (sheet 1) + +Figure 10a: Procedure OR\_HLR\_CF (sheet 1) + + + +### Procedure OR\_HLR\_CF + +ORHLRCF2(2) + +Procedure in the HLR to handle optimally routed call forwarding + +``` +graph TD; Start((2)) --> D1{ }; D1 -- No --> D2{ }; D1 -- Yes --> F1[Forwarding reason=busy?]; F1 --> H_CFB[Handle_CFB]; H_CFB --> R1[See TS 23.018]; D2 -- No --> H_CFNRY[Handle_CFNRY]; D2 -- Yes --> F2[Forwarding reason=not reachable?]; F2 --> H_CFNRC[Handle_CFNRC]; H_CFNRY --> R2[See TS 23.018]; H_CFNRC --> R3[See TS 23.018]; H_CFNRY --> D3{Result=Fail?}; D3 -- No --> D4{Result=Forward?}; D3 -- Yes --> N1[Set negative response: Forwarding violation]; N1 --> C1((1)); D4 -- No --> N2[Set negative response: No subscriber reply]; D4 -- Yes --> C3((3)); N2 --> C2((1)); H_CFNRC --> D5{Result=Fail?}; D5 -- No --> D6{Result=Forward?}; D5 -- Yes --> N3[Set negative response: Forwarding violation]; N3 --> C4((1)); D6 -- No --> N4[Set negative response: Absent Subscriber]; N4 --> C5((1)); D6 -- Yes --> R4[Result:=Forward]; R4 --> End((X)); R1 --> R4; R3 --> R4; C1 --> R4; C2 --> R4; C4 --> R4; C5 --> R4; C3 --> R4; +``` + +Flowchart for Procedure OR\_HLR\_CF. It starts at connector '2' and branches based on forwarding reasons: busy, not reachable, or neither. It includes sub-procedures Handle\_CFB, Handle\_CFNRY, and Handle\_CFNRC, with various decision points for Result=Fail? and Result=Forward? leading to negative responses or further forwarding steps. + +Figure 10b: Procedure OR\_HLR\_CF (sheet 2) + + + +**Procedure OR\_HLR\_Interrogate\_VLR** **HLRINTV1(1)** + +Procedure in the HLR to handle interrogation of the VLR for optimal routing + +Signals to/from the right are to/from the VLR + +``` + +graph TD + Start([Start]) --> OptimalRouteing{Optimal Routeing enquiry?} + OptimalRouteing -- No --> GMSCSupportsOR{GMSC supports OR?} + OptimalRouteing -- Yes --> CC_GMSC{CC of GMSC= CC of VMSC?} + CC_GMSC -- No --> CC_HLR{CC of HLR= CC of VMSC?} + CC_HLR -- Yes --> ProvideSubscriberInfo[Provide Subscriber Info] + CC_HLR -- No --> ProvideSubscriberInfo + ProvideSubscriberInfo --> WaitForSubscriberInfo[Wait For Subscriber Info] + WaitForSubscriberInfo --> ProvideSubscriberInfoAck[Provide Subscriber Info ack] + WaitForSubscriberInfo --> ProvideSubscriberInfoNegativeResponse[Provide Subscriber Info negative response] + ProvideSubscriberInfoAck --> StateNetworkDeterminedNotReachable{State=Network determined not reachable?} + StateNetworkDeterminedNotReachable -- Yes --> HandleCFNrc[Handle_CFNrc] + HandleCFNrc --> ResultFail{Result= Fail?} + ResultFail -- No --> ResultForward{Result= Forward?} + ResultForward -- Yes --> ResultForwardOut[Result:= Forward] + ResultForward -- No --> SetNegativeResponse1[Set negative response: Absent Subscriber] + SetNegativeResponse1 --> ResultFailOut[Result:= Fail] + ResultFail -- Yes --> SetNegativeResponse2[Set negative response: Forwarding violation] + SetNegativeResponse2 --> ResultFailOut + ProvideSubscriberInfoNegativeResponse --> SetNegativeResponse3[Set negative response: OR not allowed] + SetNegativeResponse3 --> ResultFailOut + GMSCSupportsOR -- No --> SetParameterForPRN1[Set parameter for PRN: OR not supported in GMSC] + GMSCSupportsOR -- Yes --> SetParametersForPRN1[Set parameters for PRN: GMSC address, call ref no] + SetParametersForPRN1 --> ResultContinueOut[Result:= Continue] + SetParameterForPRN1 --> ResultContinueOut + SetParametersForPRN1 --> SetParametersForPRN2[Set parameters for PRN: GMSC address, call ref no, OR] + SetParametersForPRN2 --> ResultContinueOut + +``` + +Flowchart for Procedure OR\_HLR\_Interrogate\_VLR (HLRINTV1(1)). The process starts with an 'Optimal Routeing enquiry?'. If 'No', it goes to 'GMSC supports OR?'. If 'Yes', it checks 'CC of GMSC= CC of VMSC?'. If 'No', it checks 'CC of HLR= CC of VMSC?'. If 'Yes', it sends 'Provide Subscriber Info' and waits for a response. If 'No', it sends 'Provide Subscriber Info' and waits for a response. The 'Wait For Subscriber Info' block leads to 'Provide Subscriber Info ack' or 'Provide Subscriber Info negative response'. The 'Provide Subscriber Info ack' leads to 'State=Network determined not reachable?'. If 'Yes', it calls 'Handle\_CFNrc' (See TS 23.018). If 'No', it checks 'Result= Fail?'. If 'Yes', it checks 'Result= Forward?'. If 'Yes', it sets 'Result:= Forward'. If 'No', it sets 'Result:= Fail'. The 'Provide Subscriber Info negative response' leads to 'Set negative response: Absent Subscriber', 'Set negative response: Forwarding violation', or 'Set negative response: OR not allowed', all leading to 'Result:= Fail'. The 'GMSC supports OR?' decision leads to 'Set parameter for PRN: OR not supported in GMSC', 'Set parameters for PRN: GMSC address, call ref no', or 'Set parameters for PRN: GMSC address, call ref no, OR', all leading to 'Result:= Continue'. + +Figure 11: Procedure OR\_HLR\_Interrogate\_VLR + +## 9.6 Functional behaviour of VLRB + +### 9.6.1 Functional behaviour of VLRB for provision of subscriber information + +The functional behaviour of VLRB for provision of subscriber information is specified in 3GPP TS 23.018 [6]. + +### 9.6.2 Functional behaviour of VLRB for roaming number allocation + +The functional behaviour of VLRB for roaming number allocation is specified in 3GPP TS 23.018 [6]. The only function specific to Support of Optimal Routeing is the storage of the OR indicator, the 'OR not supported in GMSC' indicator, the GMSC address and the call reference number if VLRB receives them in the Provide Roaming Number request. + +### 9.6.3 Functional behaviour of VLRB when handling an incoming call + +The functional behaviour of VLRB when handling a request for information to handle an incoming call is specified in 3GPP TS 23.018 [6]. The only functions specific to Support of Optimal Routeing are: + +- the inclusion in the Complete Call or Process Call Waiting, if the call is to be offered to the B subscriber, of the OR indicator and the GMSC address if VLRB received them in the Provide Roaming Number request; +- the inclusion in the Send Info For Incoming Call response, if the call is to be forwarded, of: + - the OR indicator, the 'OR not supported in GMSC' indicator, the GMSC address and the call reference number if VLRB received them in the Provide Roaming Number request; + - the basic service which applies for this call. + +## 9.7 Functional behaviour of VMSCB + +The functional behaviour of VMSCB when it handles an incoming call is described in 3GPP TS 23.018 [6]. The procedure specific to Support of Optimal Routeing is specified in this subclause. + +### 9.7.1 Procedure Handle\_ORLCF\_VMSC + +The procedure UUS\_ICH\_Handle\_LCF is specific to UUS; it is specified in 3GPP TS 23.087 [9]. + + + +**Procedure Handle\_ORLCF\_VMSC** **ORLCF\_M1(1)** + +*Procedure in the terminating VMSC to handle OR for late call forwarding* + +*Signals to/from the left are to/from the GMSC* + +``` + +graph TD + Start([Start]) --> NoGMSC{No GMSC address available?} + NoGMSC -- Yes --> Continue1[Result:= Continue] + NoGMSC -- No --> MTRetrySupp1{MT Roaming Retry Supported} + MTRetrySupp1 -- No --> MTRetry1{MT Roaming Retry} + MTRetry1 -- True --> SetMTRetryIE[set MT Roaming Retry IE] + MTRetry1 -- False --> ORNotSupported{OR not supported in GMSC} + ORNotSupported -- True --> Continue1 + ORNotSupported -- False --> UUS_ICH[UUS_ICH Handle_LCF] + SetMTRetryIE --> UUS_ICH + UUS_ICH --> ResumeCallHandling[Resume Call Handling] + ResumeCallHandling --> WaitForRCH[Wait_For_RCH_Result] + WaitForRCH --> FromGMSC[From GMSC] + FromGMSC --> Release[Release] + WaitForRCH --> ResumeCallHandlingNeg[Resume Call Handling negative response] + WaitForRCH --> ResumeCallHandlingAck[Resume Call Handling ack] + ResumeCallHandlingNeg --> MTRetrySupp2{MT Roaming Retry Supported} + MTRetrySupp2 -- No --> NegResponse{Negative response= Forwarding failure?} + NegResponse -- Yes --> ForwardingFailed[Result:= Forwarding Failed] + NegResponse -- No --> Continue2[Result:= Continue] + MTRetrySupp2 -- Yes --> MTRetry2{MT Roaming Retry} + MTRetry2 -- No --> Continue2 + MTRetry2 -- Yes --> Accepted[Result:= Accepted] + ResumeCallHandlingAck --> Accepted + Continue1 --> End1(( )) + ForwardingFailed --> End2(( )) + Continue2 --> End3(( )) + Accepted --> End4(( )) + +``` + +Flowchart for Procedure Handle\_ORLCF\_VMSC. The process starts with a decision 'No GMSC address available?'. If 'Yes', it goes to 'Result:= Continue'. If 'No', it checks 'MT Roaming Retry Supported'. If 'No', it checks 'MT Roaming Retry'. If 'True', it sets 'MT Roaming Retry IE' and then goes to 'UUS\_ICH Handle\_LCF'. If 'False', it checks 'OR not supported in GMSC'. If 'True', it goes to 'Result:= Continue'. If 'False', it goes to 'UUS\_ICH Handle\_LCF'. From 'UUS\_ICH Handle\_LCF', it goes to 'Resume Call Handling'. From 'Resume Call Handling', it goes to 'Wait\_For\_RCH\_Result'. From 'Wait\_For\_RCH\_Result', it branches into three paths: 'From GMSC' -> 'Release', 'Resume Call Handling negative response', and 'Resume Call Handling ack'. From 'Resume Call Handling negative response', it checks 'MT Roaming Retry Supported'. If 'No', it checks 'Negative response= Forwarding failure?'. If 'Yes', it goes to 'Result:= Forwarding Failed'. If 'No', it goes to 'Result:= Continue'. If 'Yes', it checks 'MT Roaming Retry'. If 'No', it goes to 'Result:= Continue'. If 'Yes', it goes to 'Result:= Accepted'. From 'Resume Call Handling ack', it goes to 'Result:= Accepted'. + +Figure 12: Procedure Handle\_ORLCF\_VMSC + +# 10 Contents of messages + +This clause specifies the changes to the content of each message shown in clauses 5, 6 and 9, including those messages which are already specified for UMTS but which require changes for Optimal Routeing. It should be read as a 'delta' on the corresponding clause of 3GPP TS 23.018 [6]; those information elements which are the same for SOR as for the basic call without OR are not specified in this clause. + +In the tables which follow, information elements are shown as mandatory (M) or conditional (C). A mandatory information element shall always be present. A conditional information element shall be present if certain conditions are fulfilled; if those conditions are not fulfilled it shall be absent. + +## 10.1 Messages on the B interface (MSC-VLR) + +### 10.1.1 Send Info For Outgoing Call + +This message is specified in 3GPP TS 23.018 [6]. + +### 10.1.2 Send Info For Outgoing Call negative response + +This message is specified in 3GPP TS 23.018 [6]. + +### 10.1.3 Send Info For Incoming Call + +This message is specified in 3GPP TS 23.018 [6]. + +### 10.1.4 Send Info For Incoming Call ack + +**This message is specified in 3GPP TS 23.018 [6]. The following additional information elements are required:** + +| Information element name | Required | Description | +|--------------------------|----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| OR indicator | C | Indicates whether the call has been routed directly from a GMSC not in the same PLMN as the HLR. Shall be present if it was received in the Provide Roaming Number, otherwise shall be absent. | +| GMSC address | C | E.164 address of the GMSC. Shall be present if it was received in the Provide Roaming Number, otherwise shall be absent. | +| Call reference number | C | Call reference number used by the GMSC for this call. Shall be present if it was received in the Provide Roaming Number, otherwise shall be absent. | +| OR not supported in GMSC | C | Indicates that the GMSC does not support Optimal Routeing. Shall be present if it was received in the Provide Roaming Number, otherwise shall be absent. | + +### 10.1.5 Send Info For Incoming Call negative response + +This message is specified in 3GPP TS 23.018 [6]. + +### 10.1.6 Complete Call + +**This message is specified in 3GPP TS 23.018 [6]. The following additional information elements are required:** + +| Information element name | Required | Description | +|--------------------------|----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| OR indicator | C | Indicates whether the call has been routed directly from a GMSC not in the same PLMN as the HLR. Shall be present if it was received in the Provide Roaming Number, otherwise shall be absent. | +| GMSC address | C | E.164 address of the GMSC. Shall be present if it was received in the Provide Roaming Number, otherwise shall be absent. | + +### 10.1.7 Process Call Waiting + +**This message is specified in 3GPP TS 23.018 [6]. The following additional information elements are required:** + +| Information element name | Required | Description | +|--------------------------|----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| OR indicator | C | Indicates whether the call has been routed directly from a GMSC not in the same PLMN as the HLR. Shall be present if it was received in the Provide Roaming Number, otherwise shall be absent. | +| GMSC address | C | E.164 address of the GMSC. Shall be present if it was received in the Provide Roaming Number, otherwise shall be absent. | + +## 10.2 Messages on the C interface (MSC-HLR) + +### 10.2.1 Send Routeing Info + +This message is specified in 3GPP TS 23.018 [6]. The following additional information elements are required: + +| Information element name | Required | Description | +|----------------------------|----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Interrogation type | M | Indicates the type of interrogation: basic(for routeing information for an MT call) or forwarding (when the GMSC has been asked to resume call handling for OR of late call forwarding). | +| OR interrogation indicator | C | Indicates that the interrogation is from a GMSC not in the same PLMN as the HLR. Shall be present if the interrogation is from a GMSC not in the same PLMN as the HLR, otherwise shall be absent. | +| OR capability | C | Indicates the phase of OR which the GMSC supports. Shall be present if the GMSC supports OR, otherwise shall be absent. | +| GMSC or gsmSCF address | M | E.164 address of the GMSC. | +| Call reference number | C | Call reference number used by the GMSC for this call. Shall be present if the interrogation type=basic call, otherwise shall be absent. | +| Forwarding reason | C | Indicates the reason for forwarding (on busy, on no subscriber reply, or on mobile subscriber not reachable). Shall be present if the Interrogation type=forwarding, otherwise shall be absent. | +| Basic service group | C | Basic service group which applies for this call. Shall be present if the Interrogation type=forwarding, otherwise shall be absent. | +| Basic service group 2 | C | Basic service group which applies for this call. Shall be present if the Interrogation type=forwarding and if the VMSC has determined that the forwarded call is to be treated as a SCUDIF call in accordance with the rules in 3GPP TS 23.172[10], otherwise shall be absent. | + +### 10.2.2 Send Routeing Info ack + +This message is specified in 3GPP TS 23.018 [6]. Two new information elements are required, and the condition for the presence of one existing information element is changed, as shown in the following table. + +| Information element name | Required | Description | +|-----------------------------------|----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Forwarding interrogation required | C | Indicates that the GMSC shall interrogate the HLR for routeing information for late call forwarding. Shall be present if the SRI ack contains an MSRN and GMSC has to interrogate the HLR for routeing information for late call forwarding, otherwise shall be absent. | +| VMSC address | C | E.164 address of the VMSC in whose area the B subscriber is currently registered. Shall be present in the Send Routeing Info ack if the OR interrogation indicator in the Send Routeing Info was present and the HLR supports optimal routeing of basic mobile-to-mobile calls and the HLR has not determined that the call is to be forwarded, otherwise shall be absent. | +| Roaming number | C | E.164 address required to route the call to the VMSC of the B party. Shall be present in the Send Routeing Info ack which is sent in response to a Send Routeing Info with Interrogation type=basic if the HLR has determined that the charging requirements for optimal routeing are not contravened and that the call is not to be forwarded, otherwise shall be absent. | + +### 10.2.3 Send Routeing Info negative response + +This message is specified in 3GPP TS 23.018 [6]. The negative response information element can take the following values in addition to those specified in 3GPP TS 23.018 [6]: + +- OR not allowed. +- Busy subscriber. +- No subscriber reply. + +## 10.3 Messages on the D interface (VLR-HLR) + +### 10.3.1 Provide Roaming Number + +This message is specified in 3GPP TS 23.018 [6]. The following additional information elements are required: + +| Information element name | Required | Description | +|----------------------------|----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| GMSC address | C | E.164 address of the GMSC. Shall be present if it was received by the HLR in the Send Routeing Info, otherwise shall be absent. | +| Call reference number | C | Call reference number used by the GMSC for this call. Shall be present if it was received by the HLR in the Send Routeing Info, otherwise shall be absent. | +| OR interrogation indicator | C | Indicates that the HLR received the corresponding Send Routeing Info from a GMSC not in the same PLMN as the HLR. Shall be present if the HLR received the Send Routeing Info from a GMSC not in the same PLMN as the HLR, otherwise shall be absent. | +| OR not supported in GMSC | C | Indicates that the GMSC does not support OR, and that RCH shall not be sent for optimal routing. Shall be present if the HLR received the Send Routeing Info from the GMSC without the OR-capability information Element, otherwise it shall be absent. | + +### 10.3.2 Provide Roaming Number ack + +This message is specified in 3GPP TS 23.018 [6]. + +### 10.3.3 Provide Roaming Number negative response + +This message is specified in 3GPP TS 23.018 [6]. + +### 10.3.4 Provide Subscriber Information + +This message is specified in 3GPP TS 23.018 [6]. + +### 10.3.5 Provide Subscriber Information ack + +This message is specified in 3GPP TS 23.018 [6]. + +## 10.4 Messages on the E interface (MSC-MSC) + +### 10.4.1 Resume Call Handling + +The following information elements are required: + +| Information element name | Required | Description | +|-------------------------------|----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Call reference number | M | Call reference number used by the GMSC for this call. | +| Forwarding reason | C | Indicates the reason for forwarding (on call deflection, on busy, on no subscriber reply, or on mobile subscriber not reachable). Shall be present if the call is forwarded other than for the MT roaming retry reason. | +| Basic service group | M | Basic service group which applies for this call. For SCUDIF calls, see 3GPP TS 23.172 [10] for the use of this information element. | +| IMSI | M | IMSI of the B subscriber. | +| Forwarded-to number | C | E.164 number of the C subscriber. Shall be present if the call is forwarded other than for the MT roaming retry reason. | +| Notification to calling party | C | Indication of whether the calling party is to be notified that the call has been forwarded. Shall be present if the call is forwarded other than for MT roaming retry reason. | +| Forwarded-to subaddress | C | Subaddress of the C subscriber (see 3GPP TS 23.003 [5]). Shall be present if a forwarded-to subaddress is stored in the VLR in association with the forwarded-to number; otherwise shall be absent. | +| Redirecting presentation | C | Indication of whether the MSISDN of the B subscriber shall be presented to the C subscriber. Shall be present if VMSCB supports the handling of the redirecting number, otherwise shall be absent. | +| MSISDN | C | E.164 number which identifies the B subscriber. It will be used to create the redirecting number presented to the C subscriber. Shall be present if VMSCB supports the handling of the redirecting number, otherwise shall be absent. | +| CUG interlock | C | For the definition of this IE, see 3GPP TS 23.085 [8]. Shall be present if the VLR has determined that the forwarded call is to be treated as a CUG call in accordance with the rules in 3GPP TS 23.085 [8], otherwise shall be absent. | +| CUG outgoing access | C | For the definition of this IE, see 3GPP TS 23.085 [8]. Shall be present if the VLR has determined that the forwarded call is to be treated as a CUG call with outgoing access in accordance with the rules in 3GPP TS 23.085 [8], otherwise shall be absent. | +| Basic service group 2 | C | For the definition of this IE, see 3GPP TS 23.172 [10]. Shall be present if the VMSC has determined that the forwarded call is to be treated as a SCUDIF call in accordance with the rules in 3GPP TS 23.172[10], otherwise shall be absent. | +| MT Roaming Retry | C | Indication that the call is forwarded for MT roaming retry. All other forwarding parameters are not relevant if this IE is present. | + +### 10.4.2 Resume Call Handling ack + +This message contains no information elements. + +### 10.4.3 Resume Call Handling negative response + +The negative response information element can take the following values: + +- OR not allowed. +- Forwarding failed. + +# --- Annex A (informative): Handling of an IAM at an MSC + +An MSC which receives an IAM from an originating exchange may react in three different ways: + +- It acts as a transit exchange, i.e. it relays the IAM to a destination exchange determined by analysis of the called party address, and thereafter relays other ISUP signalling between the originating and destination exchange until the connection is released. This behaviour is not specific to UMTS or GSM. +- It acts as a terminating exchange, i.e. it attempts to connect the call to an MS currently registered in the service area of the MSC. +- It acts as a GMSC, i.e. it interrogates an HLR for information to route the call. If the HLR returns routeing information, the MSC uses the routeing information from the HLR to construct an IAM, which it sends to a destination exchange determined by analysis of the routeing information from the HLR. + +The method which the MSC uses to determine how to handle the IAM is described in 3GPP TS 23.018 [6]. However, the number analysis required to derive the address of an HLR in a different PLMN from the MSC is much more extensive than that required to derive the address of an HLR in the same PLMN as the MSC - the MSC needs to be able to recognise the combination of country code and national destination code for every subscriber of every PLMN to which calls are to be optimally routed. In order to avoid the need to maintain the tables required to support this extensive number analysis, and the run-time processing load of performing the number analysis, optimal routeing of mobile-to-mobile calls is handled as a mobile originating CAMEL service; the gsmSCF analyses the destination address (after possible modification of the number by other MO CAMEL services) to determine whether the call is eligible for optimal routeing. If the call is eligible for optimal routeing, the gsmSCF indicates this to VMSCA, which routes the call to an associated GMSC function, which in turn sends a request for routeing information to the appropriate HLR. + +When a GMSC has interrogated an HLR and received an MSRN, the GMSC may need to route the call to the HPLMN of the called subscriber. If the call is routed through an MSC which has the capability to analyse an address to derive an HLR address, a method must be provided to prevent the transit MSC from performing a further interrogation of the HLR, using the MSRN as an MSISDN. The method used to prevent this further interrogation is a matter for the PLMN operator. + +# Annex B (informative): Change history + +| TSG CN# | Spec | CR |
79 | | | | Transferred to 3GPP CN1 | +| CN#03 | 23.079 | | R99 | 3.0.0 | Approved at CN#03 | +| CN#04 | 23.079 | | R99 | 3.1.0 | Notification of Call Forwarding to the gsmSCF | +| CN#05 | 23.079 | 001 | R99 | 3.2.0 | OR capability IE in PRN | +| | 23.079 | 003 | R99 | 3.2.0 | Removal of TDP Criteria from Resume Call Handling | +| | 23.079 | 005r1 | R99 | 3.2.0 | Separation of success & failure cases for OR of late call forwarding | +| | 23.079 | 006 | R99 | 3.2.0 | Notification of Call Forwarding to the gsmSCF before activating call forwarding process | +| | 23.079 | 007 | R99 | 3.2.0 | Handling of Release during forwarding interrogation | +| CN#06 | 23.079 | 008 | R99 | 3.3.0 | Introduction of CAMEL Phase 3 | +| CN#07 | 23.079 | 009 | R99 | 3.4.0 | Correction of CF Notification | +| | 23.079 | 010r1 | R99 | 3.4.0 | Replacement of references to GSM with references to UMTS | +| | 23.079 | 011 | R99 | 3.4.0 | Indication of OR capability of the GMSC to the destination MSC/VLR | +| CN#08 | 23.079 | 014 | R99 | 3.5.0 | Indication in PRN of support of Long FTNs | +| CN#09 | 23.079 | 015 | R99 | 3.6.0 | Sheet 1 of Procedure OR_HLR_CF | +| CN#11 | 23.079 | | Rel-4 | 4.0.0 | Release 4 after CN#11 | +| CN#15 | 23.079 | 016 | Rel-5 | 5.0.0 | Introduction of CAMEL Phase 4 | +| CN#16 | 23.079 | 019 | Rel-5 | 5.1.0 | Removal of unnecessary references to O-CSI | +| CN#18 | 23.079 | 020r1 | Rel-5 | 5.2.0 | Optimal routeing and CAMEL discrepancy | +| CN#18 | 23.079 | 024 | Rel-5 | 5.2.0 | Correction to figure 7a (handling of RCH in GMSC) | +| CN#21 | 23.079 | 025r4 | Rel-5 | 5.3.0 | Correction to interaction between ORLCF and forwarding notification | +| CN#21 | 23.079 | 026r1 | Rel-5 | 5.3.0 | Notification of the 2nd BSG in case of Late CF with OR | +| CN#22 | 23.079 | 027 | Rel-5 | 5.4.0 | Correction to MAP RCH – GMSC shall check Offered CAMEL4 CSIs | +| CN#24 | 23.079 | 080 | Rel-5 | 5.5.0 | Enhancement to Route_Permitted procedure to handle Short/ Long FTNs | +| CN#26 | 23.079 | | Rel-6 | 6.0.0 | Release 6 after CN#26 | +| CT#30 | 23.079 | 0083r2 | Rel-6 | 6.1.0 | Correction to relationship between the OR implementation and CAMEL | +| CT#36 | 23.079 | 0085 | Rel-7 | 7.0.0 | Mobile Termination whilst the MS is moving to another MSC | +| CT#42 | 23.079 | | Rel-8 | 8.0.0 | Upgraded unchanged from Rel-7 | +| CT#46 | 23.079 | - | Rel-9 | 9.0.0 | Update to Rel-9 version (MCC) | +| 2011-03 | 23.079 | - | Rel-10 | 10.0.0 | Update to Rel-10 version (MCC) | +| 2012-09 | 23.079 | - | Rel-11 | 11.0.0 | Update to Rel-11 version (MCC) | +| 2014-09 | 23.079 | - | Rel-12 | 12.0.0 | Update to Rel-12 version (MCC) | +| 2015-12 | 23.079 | - | Rel-13 | 13.0.0 | Update to Rel-13 version (MCC) | +| 2017-03 | 23.079 | - | Rel-14 | 14.0.0 | Update to Rel-14 version (MCC) | +| 2018-06 | 23.079 | - | Rel-15 | 15.0.0 | Update to Rel-15 version (MCC) | +| 2020-07 | 23.079 | - | 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/23083/00504fc688ebcf131ccbeff94dfc9939_img.jpg b/marked/Rel-16/23_series/23083/00504fc688ebcf131ccbeff94dfc9939_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..95e7d94fdb26d259da1b47035d78aaa5c7eab4e8 --- /dev/null +++ b/marked/Rel-16/23_series/23083/00504fc688ebcf131ccbeff94dfc9939_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dd82368193f1600f2599f5c84f4e84a624d2b2a2fbf944d55251be814dc174c3 +size 101909 diff --git a/marked/Rel-16/23_series/23083/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg b/marked/Rel-16/23_series/23083/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ba85294ef7a6b8e3c914ccac23141595d8f5c0f8 --- /dev/null +++ b/marked/Rel-16/23_series/23083/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e009d249f9118d05273d5b4aa3997e09111736e293f5e8afe7cba62a53e9e5e4 +size 44043 diff --git a/marked/Rel-16/23_series/23083/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/marked/Rel-16/23_series/23083/1a827b10290f33d4fec04d0e8ef7a897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d873c6d216e8fb1d12e921f874b8bb1495e25f9c --- /dev/null +++ b/marked/Rel-16/23_series/23083/1a827b10290f33d4fec04d0e8ef7a897_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:877d25f957e5fb8bb77f9cfa62969c47a1c8f6dbefddfc0223cf0b209568a986 +size 158146 diff --git a/marked/Rel-16/23_series/23083/26d664119ad25250780f554633444e54_img.jpg b/marked/Rel-16/23_series/23083/26d664119ad25250780f554633444e54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..42d22fb14ea451119ad9daa286502cf2c89257dd --- /dev/null +++ b/marked/Rel-16/23_series/23083/26d664119ad25250780f554633444e54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c4f814bac4c1b361db490dee265964a4b3d85b44739aff2e5537f33ba445cd1b +size 113353 diff --git a/marked/Rel-16/23_series/23083/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/Rel-16/23_series/23083/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9b22ce2a65c43a2f7f2067f5078a40fe3628b282 --- /dev/null +++ b/marked/Rel-16/23_series/23083/27b06ec9f42b5d727a2630f61a5f1861_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0bd8f57000fb05ed70be7f9830b416b373e52cb6b4a2c5750bd08d87e880464b +size 192411 diff --git a/marked/Rel-16/23_series/23083/2837ffdadcdb1e5bababa56b564e56ed_img.jpg b/marked/Rel-16/23_series/23083/2837ffdadcdb1e5bababa56b564e56ed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bcc4d3d32711b02dc61a1d05e566fd3ac3bafb28 --- /dev/null +++ b/marked/Rel-16/23_series/23083/2837ffdadcdb1e5bababa56b564e56ed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cf18210cd740898f3a15f019cbefb853f0ad3af5bf99d8aec037f81529124f14 +size 88914 diff --git a/marked/Rel-16/23_series/23083/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg b/marked/Rel-16/23_series/23083/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dc58bda8d860c251114ee11fdeef0309c732e4d9 --- /dev/null +++ b/marked/Rel-16/23_series/23083/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8c9814b29a0ed79adc38ba472d3d22b2f87b411a5f3412a25e54510769e8d467 +size 57839 diff --git a/marked/Rel-16/23_series/23083/4356776ca004ecba5d599667a155d7d4_img.jpg b/marked/Rel-16/23_series/23083/4356776ca004ecba5d599667a155d7d4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ccaaa8d823483f189167b774e87103331f3ee0b8 --- /dev/null +++ b/marked/Rel-16/23_series/23083/4356776ca004ecba5d599667a155d7d4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:194498b26bd5622c668f4448c87bd0304bce272ff1af48098ce75a9fbc67e856 +size 143433 diff --git a/marked/Rel-16/23_series/23083/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Rel-16/23_series/23083/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c2288c06e91b25438684e4ba8a20feec77fe0914 --- /dev/null +++ b/marked/Rel-16/23_series/23083/5a4e62bead259c258d069fd3663ea670_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a9418029f7148e9377329359c53f7680e5e7b881a88b569b31e4a0271c55cc06 +size 107725 diff --git a/marked/Rel-16/23_series/23083/6ca05954842b17f14dfd52f26b9d43d2_img.jpg b/marked/Rel-16/23_series/23083/6ca05954842b17f14dfd52f26b9d43d2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f757b8a26d9e23a12acf3a65b2e0e1b7eb161d52 --- /dev/null +++ b/marked/Rel-16/23_series/23083/6ca05954842b17f14dfd52f26b9d43d2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f5f2a50f3d38b6859a66c8cb114fd17f725710bc1a7d6b552cad2a6e8c20b078 +size 70908 diff --git a/marked/Rel-16/23_series/23083/6df5629bc2fc6d82f1a1edf9d7340113_img.jpg b/marked/Rel-16/23_series/23083/6df5629bc2fc6d82f1a1edf9d7340113_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a2d4d4175562ac8b67afdf28558227778ee96cfb --- /dev/null +++ b/marked/Rel-16/23_series/23083/6df5629bc2fc6d82f1a1edf9d7340113_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7313a3c9056688d8fcf533dc9a7f39eb9f18eea989eb75413777cae444877371 +size 32116 diff --git a/marked/Rel-16/23_series/23083/6e15fc9ea763541c5913d26f85072ae1_img.jpg b/marked/Rel-16/23_series/23083/6e15fc9ea763541c5913d26f85072ae1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cb41d0843ccdc819be1aec0d4dd8c3751dd35b56 --- /dev/null +++ b/marked/Rel-16/23_series/23083/6e15fc9ea763541c5913d26f85072ae1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:654f072164785d6215bb2181be200f33894e2ca27e09bfb8dcfe110183e37ecc +size 118502 diff --git a/marked/Rel-16/23_series/23083/79e1709a7317ead45379cbb8ff3ba802_img.jpg b/marked/Rel-16/23_series/23083/79e1709a7317ead45379cbb8ff3ba802_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1a9c0a7de07a13a81116a9c12939497f4364ec56 --- /dev/null +++ b/marked/Rel-16/23_series/23083/79e1709a7317ead45379cbb8ff3ba802_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7e482cec8df3c54a8c999d1e6852b21f617abcf22fd2bf85fd66ac3a75fe3091 +size 124279 diff --git a/marked/Rel-16/23_series/23083/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/marked/Rel-16/23_series/23083/7efae06af3af43ffe5d4b956a679cf54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b42363022fa19a563e4778f9bc312f2e0951d72a --- /dev/null +++ b/marked/Rel-16/23_series/23083/7efae06af3af43ffe5d4b956a679cf54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d9b1bce366be40bfeba3ff7febd7d328bdf4aefec69472a77c410e19fab64221 +size 126419 diff --git a/marked/Rel-16/23_series/23083/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg b/marked/Rel-16/23_series/23083/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b0217bbedee04758be6d175f2f6c089dd0b76d6d --- /dev/null +++ b/marked/Rel-16/23_series/23083/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7629b2c8e3cde18d669e0a6c02a980dbde0bc413832eecca0b6ee4e557d6c27c +size 121039 diff --git a/marked/Rel-16/23_series/23083/8307f6b04df072c9332f9987e034272c_img.jpg b/marked/Rel-16/23_series/23083/8307f6b04df072c9332f9987e034272c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..10b5d3c7f52ba6904ba61b8cc82d130453160512 --- /dev/null +++ b/marked/Rel-16/23_series/23083/8307f6b04df072c9332f9987e034272c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fbed8ea9dbf1ef1d8392dc5a9d9e66850a072c9527a5e01ddf2fd42b6569c0c5 +size 171754 diff --git a/marked/Rel-16/23_series/23083/8fa679f79a1bb1f527cba9f29e784e89_img.jpg b/marked/Rel-16/23_series/23083/8fa679f79a1bb1f527cba9f29e784e89_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0d31aa6197afcc4d00d649b8455ff3c873995b8f --- /dev/null +++ b/marked/Rel-16/23_series/23083/8fa679f79a1bb1f527cba9f29e784e89_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b394650a8f484b124838afa4008b3fd5d1908cf38f8e95c08d11946861de0fe4 +size 98118 diff --git a/marked/Rel-16/23_series/23083/90ddb84c323b956e2d50a54d3f870566_img.jpg b/marked/Rel-16/23_series/23083/90ddb84c323b956e2d50a54d3f870566_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..311526714857bff4c25f539438cf7ff2bd07a8b7 --- /dev/null +++ b/marked/Rel-16/23_series/23083/90ddb84c323b956e2d50a54d3f870566_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:00d5c2ef625736a15fdfdbd906a8df5c9bfa6e9b740ba40087c81afdacfa6119 +size 91234 diff --git a/marked/Rel-16/23_series/23083/9791722d75115ddcc599b07d7bc35d73_img.jpg b/marked/Rel-16/23_series/23083/9791722d75115ddcc599b07d7bc35d73_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..74e9d36d3c8f5d0af3dbd20f12d77ea419455457 --- /dev/null +++ b/marked/Rel-16/23_series/23083/9791722d75115ddcc599b07d7bc35d73_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f408f167de3923ac9c56d1df70fcf8f8d94e73ff5b3f98da7bc7452fbebd5acc +size 28793 diff --git a/marked/Rel-16/23_series/23083/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/Rel-16/23_series/23083/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..61df7a2079411772dba7daf1e3d1195b10632f5a --- /dev/null +++ b/marked/Rel-16/23_series/23083/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:145f25487e75385a32475439a535cce1eb56be908dd3351fe8853335279624d7 +size 97992 diff --git a/marked/Rel-16/23_series/23083/a4b963a07cc368283154762c4b156fe7_img.jpg b/marked/Rel-16/23_series/23083/a4b963a07cc368283154762c4b156fe7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eb9661474005cafb580df5153f8631550f6f00c2 --- /dev/null +++ b/marked/Rel-16/23_series/23083/a4b963a07cc368283154762c4b156fe7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:10abcc8f27ed129398eed9b7038c15a04caa54af1eec6c1e6acb6f4f32819678 +size 60217 diff --git a/marked/Rel-16/23_series/23083/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg b/marked/Rel-16/23_series/23083/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f80059ee0ad08505d4f7d1ba3f17a8f1b3cd0b54 --- /dev/null +++ b/marked/Rel-16/23_series/23083/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:481190608b329d7369108963fa5a69dfdc6ff40080bb04326698ea177da3aa1a +size 153020 diff --git a/marked/Rel-16/23_series/23083/b5335262987c819d7f71ce40f99cb71b_img.jpg b/marked/Rel-16/23_series/23083/b5335262987c819d7f71ce40f99cb71b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..731aa9bffd2cd98933b337bac70913af1440f4ad --- /dev/null +++ b/marked/Rel-16/23_series/23083/b5335262987c819d7f71ce40f99cb71b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1d9147bceff694e16ffd260b4040b79350df4a14fe7a7a10e14740f6d9d764d8 +size 136368 diff --git a/marked/Rel-16/23_series/23083/dd5771673aececa53d42ece89218299d_img.jpg b/marked/Rel-16/23_series/23083/dd5771673aececa53d42ece89218299d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dc7e5fa58b16876821720786ea4bc44a7e261bdd --- /dev/null +++ b/marked/Rel-16/23_series/23083/dd5771673aececa53d42ece89218299d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:223e9d45ecdd8f5c76c98b98fef3d66bce78ddc6d218429b4cf95a438d90034d +size 116010 diff --git a/marked/Rel-16/23_series/23083/e05b36c0d46549e681ce6581422c66b2_img.jpg b/marked/Rel-16/23_series/23083/e05b36c0d46549e681ce6581422c66b2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8e04c5601a55631296a5d3b2d3798a65aa5579ac --- /dev/null +++ b/marked/Rel-16/23_series/23083/e05b36c0d46549e681ce6581422c66b2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:98ebf5455e0884bfa21216feac3681010dac13d731ba1e5e63fff84134643d10 +size 118091 diff --git a/marked/Rel-16/23_series/23083/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/marked/Rel-16/23_series/23083/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6a5d2715f582a5704f008178caf4325e4f88173d --- /dev/null +++ b/marked/Rel-16/23_series/23083/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0e961330bbaeca21ee56f47fd8ab74ccabe1c19e019793e32130d22e4602ec5c +size 126718 diff --git a/marked/Rel-16/23_series/23083/e23c9577e177bf077bac8951a775dd90_img.jpg b/marked/Rel-16/23_series/23083/e23c9577e177bf077bac8951a775dd90_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..024aa3276bd160c3de042ed3fd5469d656c0b9d6 --- /dev/null +++ b/marked/Rel-16/23_series/23083/e23c9577e177bf077bac8951a775dd90_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:59308d2d6f07505a0c9c29804b979087e83245bea3a5b228f89580920ec073ab +size 33677 diff --git a/marked/Rel-16/23_series/23083/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/Rel-16/23_series/23083/e6df2733626a85205c1db682e6259c46_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8d9ea78a6421e045eb55adc163c12834e9c641d1 --- /dev/null +++ b/marked/Rel-16/23_series/23083/e6df2733626a85205c1db682e6259c46_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:66a1c9e5add118e9d128db53f8682b7f6bc7262613d8d9b0b6b75f75e4ae4a4c +size 87064 diff --git a/marked/Rel-16/23_series/23083/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg b/marked/Rel-16/23_series/23083/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..83ec122bd402314cd964732fad14d77746de612b --- /dev/null +++ b/marked/Rel-16/23_series/23083/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:12ec11161049abbca004647dc6c3e7b16680860d2f186ebd826086a47c7f46ac +size 112362 diff --git a/marked/Rel-16/23_series/23083/fb18a83d10ebdad8e3e5ea2e86b36136_img.jpg b/marked/Rel-16/23_series/23083/fb18a83d10ebdad8e3e5ea2e86b36136_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3511c16745e3f25f1129b55ef9b1abb1c3f843a7 --- /dev/null +++ b/marked/Rel-16/23_series/23083/fb18a83d10ebdad8e3e5ea2e86b36136_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e3072cac5a3e76c5b59c60ce27937a8dc22a97135183cfd98e7912b791577f61 +size 32553 diff --git a/marked/Rel-16/23_series/23083/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/marked/Rel-16/23_series/23083/ff0952ef692c9d960ce5f6708bcc9711_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..170b7dfd55e36df9db360a7343b320c6960b71cf --- /dev/null +++ b/marked/Rel-16/23_series/23083/ff0952ef692c9d960ce5f6708bcc9711_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cb77219935df702de3a3e3eeebe4124d5047e05c20c7cfed4858dd436c5ad492 +size 131822 diff --git a/marked/Rel-16/23_series/23083/raw.md b/marked/Rel-16/23_series/23083/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..fd0f40699b1508c0aeeebaa419bfddd152976cb8 --- /dev/null +++ b/marked/Rel-16/23_series/23083/raw.md @@ -0,0 +1,1450 @@ + + + + + + +# Contents + +| | | +|---------------------------------------------------|----| +| Foreword ..... | 4 | +| 0 Scope..... | 5 | +| 0.1 References ..... | 5 | +| 0.2 Abbreviations ..... | 5 | +| 1 Call waiting (CW)..... | 6 | +| 1.1 Handling of call waiting..... | 6 | +| 1.1.1 Activation ..... | 6 | +| 1.1.2 Deactivation..... | 6 | +| 1.1.3 Interrogation ..... | 7 | +| 1.2 Functions and information flows..... | 7 | +| 1.3 Information stored in the HLR ..... | 26 | +| 1.4 State transition model..... | 26 | +| 1.5 Transfer of information from HLR to VLR ..... | 27 | +| 1.6 Information stored in the VLR ..... | 27 | +| 1.7 Handover ..... | 27 | +| 2 Call hold (HOLD) ..... | 27 | +| 2.1 Functions and information flows..... | 27 | +| 2.2 Information stored in the HLR ..... | 36 | +| 2.3 State transition model..... | 37 | +| 2.4 Transfer of information from HLR to VLR ..... | 37 | +| 2.5 Information stored in the VLR ..... | 37 | +| 2.6 Handover ..... | 37 | +| Annex A: Change history ..... | 38 | + +# --- 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. + +# --- 0 Scope + +The present document gives the stage 2 description of the call completion supplementary services. + +The group of call completion supplementary services is divided into the following two supplementary services: + +- Call waiting (CW) (clause 1); +- Call hold (HOLD) (clause 2). + +## 0.1 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "3G Vocabulary". +- [2] 3GPP TS 22.082: "Call Forwarding (CF) Supplementary Services - Stage 1". +- [3] 3GPP TS 23.011: "Technical realization of supplementary services - General Aspects". +- [4] 3GPP TS 24.008: "Mobile radio interface layer 3 specification; Core Network Protocols - Stage3". +- [5] 3GPP TS 23.018: "Basic call handling". +- [6] 3GPP TS 23.078: "Customized Applications for Mobile network Enhanced Logic (CAMEL) - Phase 3; Stage 2". +- [7] 3GPP TS 23.135: "Multicall supplementary service; Technical Realisation; Stage 2". +- [8] 3GPP TS 23.087: "User-to-User Signalling (UUS) - Stage 2". +- [9] 3GPP TS 23.093: "Technical realisation of Completion of Calls to Busy Subscriber (CCBS) - Stage 2". +- [10] 3GPP TS 23.072: "Call Deflection (CD) supplementary service - Stage2". +- [11] 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)". + +## 0.2 Abbreviations + +In addition to those below, abbreviations used in the present document are listed in 3GPP TR 21.905. + +HTI: HoldTreatment Indicator + +# 1 Call waiting (CW) + +## 1.1 Handling of call waiting + +### 1.1.1 Activation + +The call waiting supplementary service is activated at the request of the user. The activation request indicates the basic services to which the activation request refers. + +The information flow for activation of call waiting is shown in figure 1.1. + + + +``` +sequenceDiagram + participant MS + participant MSC + participant VLR + participant HLR + Note right of HLR: HLRá + MS->>MSC: Activate CW + MSC->>VLR: Activate CW + VLR->>HLR: Activate CW + HLR-->>VLR: Acknowledge + VLR-->>MSC: Acknowledge + MSC-->>MS: Release Complete + Note left of MS: /Facility +``` + +Sequence diagram illustrating the activation of call waiting. The interaction involves four entities: MS (Mobile Station), MSC (Mobile Switching Center), VLR (Visitor Location Register), and HLR (Home Location Register, labeled HLRá). The sequence of messages is: 1. MS sends 'Activate CW' to MSC. 2. MSC sends 'Activate CW' to VLR. 3. VLR sends 'Activate CW' to HLR. 4. HLR sends 'Acknowledge' back to VLR. 5. VLR sends 'Acknowledge' back to MSC. 6. MSC sends 'Release Complete' back to MS, with a note '/Facility'. + +Sequence diagram for activation of call waiting + +Figure 1.1: Activation of call waiting + +### 1.1.2 Deactivation + +The call waiting supplementary service is deactivated at the request of the user. The deactivation request indicates the basic services to which the deactivation request refers. + +The information flow for deactivation of call waiting is shown in figure 1.2. + + + +``` +sequenceDiagram + participant MS + participant MSC + participant VLR + participant HLR + Note right of HLR: HLRá + MS->>MSC: Deactivate CW + MSC->>VLR: Deactivate CW + VLR->>HLR: Deactivate CW + HLR-->>VLR: Acknowledge + VLR-->>MSC: Acknowledge + MSC-->>MS: Release Complete + Note left of MS: /Facility +``` + +Sequence diagram illustrating the deactivation of call waiting. The interaction involves four entities: MS (Mobile Station), MSC (Mobile Switching Center), VLR (Visitor Location Register), and HLR (Home Location Register, labeled HLRá). The sequence of messages is: 1. MS sends 'Deactivate CW' to MSC. 2. MSC sends 'Deactivate CW' to VLR. 3. VLR sends 'Deactivate CW' to HLR. 4. HLR sends 'Acknowledge' back to VLR. 5. VLR sends 'Acknowledge' back to MSC. 6. MSC sends 'Release Complete' back to MS, with a note '/Facility'. + +Sequence diagram for deactivation of call waiting + +Figure 1.2: Deactivation of call waiting + +### 1.1.3 Interrogation + +#### Status check + +The status check procedure enables the mobile subscriber to obtain information about the status of the call waiting supplementary service with respect to subscribed basic service groups. + +The interrogation of call waiting is for all applicable basic services. + +The information flow for interrogation of call waiting is shown in figure 1.3. + + + +``` + +sequenceDiagram + participant MS + participant MSC + participant VLR + participant HLR + Note right of HLR: HLRá + MS->>MSC: Interrogate CW + MSC->>VLR: Interrogate CW + VLR-->>MSC: Acknowledge + MSC-->>MS: Release Complete / Facility + +``` + +Sequence diagram showing the interrogation of call waiting. The diagram involves four lifelines: MS (Mobile Station), MSC (Mobile Switching Center), VLR (Visitor Location Register), and HLR (Home Location Register). The sequence of messages is: 1. MS sends 'Interrogate CW' to MSC. 2. MSC sends 'Interrogate CW' to VLR. 3. VLR sends 'Acknowledge' back to MSC. 4. MSC sends 'Release Complete / Facility' back to MS. + +Figure 1.3: Interrogation of call waiting + +## 1.2 Functions and information flows + +TS 24.008 specifies the procedures for call control. These shall also be used for waiting calls when applicable. + +The following Mobile Additional Function has been identified for the call waiting service: + +### MAF013 + +Call waiting related authorizations examination + +The ability of a PLMN component to determine the authorizations relating to call waiting. See figure 1.4. + +Location: VLR + +Definitions: + +Subscriber B: + +The subscriber who is provided by the network with the call waiting supplementary service. The subscriber B is always a mobile subscriber. + +User B: + +The user who reacts to call waiting at subscriber B. The user B is always a mobile user. + +User C: + +The user who has originated a call to subscriber B which causes the call waiting supplementary service to be invoked. The user C may be a mobile user. + +User A: + +The user who is engaged in a call with user B. The user A may be a mobile user. + +Timer T1: + +This timer corresponds to T303 + T310 (as defined in TS 24.008). + +Timer T2: + +Call Waiting Timer. This shall limit the duration of the call in the waiting condition. + +Timer T3: + +No Reply Condition Timer (see TS 22.082). + +CFNRc: + +Call Forwarding on Not Reachable (see TS 22.082). + +CFNRy: + +Call Forwarding on No Reply (see TS 22.082). + +CW: + +Call Waiting. + +The procedure Process\_Call\_Waiting is shown in figure 1.5. + +Sheet 1: the procedure Set\_CLIP\_Info\_MSC is specific to CLIP; it is specified in 3GPP TS 23.018 [5]. + +Sheet 1: the VMSC derives the PLMN bearer capability required for the call according to the rules defined in 3GPP TS 29.007 [11]. + +Sheet 1: the VMSC and the MS may negotiate the bearer capability to be used for the call by the exchange of information in the Set-up and Call Confirmed messages. + +Sheet 1: the Call Confirmed message indicates "busy" for the successful case. + +Sheet 1: the procedure Establish\_Terminating\_TCH\_Multicall1 is specific to Multicall; it is specified in 3GPP TS 23.135 [7]. If the VMSC does not support Multicall, processing continues from the "Yes" exit of the test "Result=Pass?". + +Sheet 1: the procedure UUS\_ICH\_UUS1\_Implicit\_Active is specific to UUS; it is specified in 3GPP TS 23.087 [8]. + +Sheet 1: the procedure CCBS\_Report\_Not\_Idle is specific to CCBS; it is specified in 3GPP TS 23.093 [9]. + +Sheet 2, sheet 3, sheet 5: the procedure UUS\_ICH\_Check\_Support is specific to UUS; it is specified in 3GPP TS 23.087 [8]. If the VMSC does not support UUS, processing continues from the "Yes" exit of the test "Result=Pass?" where the test follows the procedure call. + +Sheet 2: the procedure CCBS\_ICH\_MSC\_Report\_Success is specific to CCBS; it is specified in 3GPP TS 23.093 [9]. + +Sheet 2: the task "UTU2Cnt:=0" is executed only if the VMSC supports UUS. + +Sheet 2: the procedure CAMEL\_Start\_TNRy is called if the VMSC supports CAMEL phase 3 or later; it is specified in 3GPP TS 23.078 [6]. + +Sheet 2: the procedure Send\_ACM\_If\_Required is specified in 3GPP TS 23.018 [5]. + +Sheet 2: The procedure CAMEL\_MT\_MSC\_ALERTING is specific to CAMEL phase 4 or later; it is specified in 3GPP TS 23.078 [6]. If the VMSC does not support CAMEL phase 4 or later, processing continues from the "Pass" exit of the test "Result?". + +Sheet 2, sheet 8: the processing in the branch starting with the input "CD Request" is specific to Call Deflection; if the VMSC does not support Call Deflection the input is discarded. + +Sheet 2, sheet 8: the procedure Handling\_CD\_MSC is specific to Call Deflection; it is specified in 3GPP TS 23.072 [10]. + +Sheet 2, sheet 3, sheet 6, sheet 7: the procedure CAMEL\_MT\_GMSC\_DISC4 is called if the VMSC supports CAMEL phase 3 or later; it is specified in 3GPP TS 23.078 [6]. If the VMSC does not support CAMEL phase 3 or later, processing continues from the "No" exit of the test "Result=Reconnect?". + +Sheet 2, sheet 3, sheet 4, sheet 8: the procedure CCBS\_ICH\_MSC\_Report\_Failure is specific to CCBS; it is specified in 3GPP TS 23.093 [9]. + +Sheet 3, sheet 7: the Release transaction (reject) message covers all unsuccessful cases not otherwise indicated. + +Sheet 4, sheet 7: the procedure UUS\_MSC\_Check\_UUS1\_UI is specific to UUS; it is specified in 3GPP TS 23.087 [8]. + +Sheet 4, sheet 8: the procedure CAMEL\_MT\_GMSC\_DISC6 is called if the VMSC supports CAMEL phase 3 or later; it is specified in 3GPP TS 23.078 [6]. + +Sheet 5: the procedure CAMEL\_Stop\_TNRy is called if the VMSC supports CAMEL phase 3 or later; it is specified in 3GPP TS 23.078 [6]. + +Sheet 5: the procedure Establish\_Terminating\_TCH\_If\_Required is specified in 3GPP TS 23.018 [5]. + +Sheet 5: the procedure Establish\_Terminating\_TCH\_Multicall is specific to Multicall; it is specified in 3GPP TS 23.135 [7]. + +Sheet 6: the procedure Handle\_AoC\_MT\_MSC is specific to AoC; it is specified in 3GPP TS 23.018 [5]. If the VMSC does not support AoC, processing continues from the "Yes" exit of the test "Result=Pass?". + +Sheet 6: the procedure CAMEL\_MT\_GMSC\_ANSWER is called if the VMSC supports CAMEL phase 3 or later; it is specified in 3GPP TS 23.078 [6]. If the VMSC does not support CAMEL phase 3 or later, processing continues from the "Pass" exit of the test "Result?" on sheet 6. + +Sheet 6: the procedure Set\_COL\_Presentation\_Indicator\_MSC is specific to COLP; it is specified in 3GPP TS 23.018 [5]. + +Sheet 6: the procedure Send\_Answer\_If\_Required is specified in 3GPP TS 23.018 [5]. + +Sheet 7: the input signal "CAMEL\_TNRy expired" will be received only if the VMSC supports CAMEL phase 3 or later. + +Sheet 7: the procedure CAMEL\_MT\_GMSC\_DISC5 is called if the VMSC supports CAMEL phase 3 or later; it is specified in 3GPP TS 23.078 [6]. If the VMSC does not support CAMEL phase 3 or later, processing continues from the "No" exit of the test "Result=Reconnect?". + +Sheet 7, sheet 8: the procedure UUS\_ICH\_Check\_Forwarding is specific to UUS; it is specified in 3GPP TS 23.087 [8]. If the VMSC does not support UUS, processing continues from the "Yes" exit of the test "Result=Pass?". + +Sheet 7, sheet 8, sheet 9: the procedure UUS\_MSC\_Check\_UUS1\_UI is specific to UUS; it is specified in 3GPP TS 23.087 [8]. + +Sheet 8: the procedures UUS\_MSC\_Check\_UUS2\_UI\_to\_MS and UUS\_MSC\_Check\_UUS2\_UI\_to\_NW are specific to UUS; they are specified in 3GPP TS 23.087 [8]. + +Sheet 8: the procedure CD\_UUS\_Interaction is specific to Call Deflection; it is specified in GSM 23.072 [10]. + +Sheet 9: the procedure CCBS\_ICH\_MSC\_Report\_Failure is specific to CCBS; it is specified in 23.093 [9]. + +Sheet 9: the procedure CAMEL\_MT\_GMSC\_DISC6 is specific to CAMEL; it is specified in 23.078 [6]. + +The information flows are shown in figure 1.6. In these flows it is assumed that user A and user C are fixed users and that user B is a mobile user. Functions to be performed by the fixed ISDN are not shown in the information flows. Only the functions to be performed by the PLMN are shown. + + + +### Process MAF013 + +383\_14(1) + +``` +graph TD; Start([ ]) --> Idle1([Idle]); Idle1 --> Init{initiate handling of CW}; Init --> CW_Activated{CW activated for the BS}; CW_Activated -- no --> Set_Not_Available[set indicator = 'CW not available']; CW_Activated -- yes --> CW_Applicable{CW applicable to BS}; CW_Applicable -- no --> Set_Not_Available; CW_Applicable -- yes --> Set_Available[set indicator = 'CW available']; Set_Available --> Process_Waiting{process call waiting}; Set_Not_Available --> Process_Waiting; Process_Waiting --> Idle2([Idle]); +``` + +Process in the VLR to check subscription for CW. + +Signals to/from the left are to/from the VLR. + +activation is checked for the basic service of the already active call. + +applicability is checked for the basic service of the already active call. + +Flowchart for Process MAF013: Call waiting related authorisations examination (VLR). The process starts at an 'Idle' state, proceeds to 'initiate handling of CW', then checks if 'CW activated for the BS'. If 'no', it goes to 'set indicator = 'CW not available''. If 'yes', it checks if 'CW applicable to BS'. If 'no', it goes to 'set indicator = 'CW not available''. If 'yes', it goes to 'set indicator = 'CW available''. Both indicator settings lead to 'process call waiting', which then returns to an 'Idle' state. Callouts indicate that the process in the VLR checks subscription for CW, and signals to/from the left are to/from the VLR. Other callouts explain that activation and applicability are checked for the basic service of the already active call. + +Figure 1.4: MAF013 Call waiting related authorisations examination (VLR) + + + +### Procedure Process\_Call\_Waiting + +PCW1(9) + +Procedure in the MSC to handle a Process Call Waiting request from the VLR + +Signals to/from the left are to/from the BSS; signals to/from the right are to/from the VLR unless marked otherwise + +``` +graph TD; Start([Start]) --> CW{CW Treatment indicator for existing call set to CW Allowed?}; CW -- No --> NDUB[Set negative response: Busy subscriber(NDUB)]; CW -- Yes --> CallUp{Call being set up}; CallUp -- Yes --> CallWaitingNeg[Process Call Waiting negative response]; CallUp -- No --> SetCLIP[Set_CLIP_Info_MSC]; SetCLIP --> DeriveBC[Derive required PLMN BC]; DeriveBC --> Setup{{Setup}}; Setup --> UUS[UUS_ICH_UUS1_Explicit_Active]; UUS --> CCBS[CCBS_Report_Not_Idle]; CCBS --> WaitSetup([Wait_For_Setup_Response]); WaitSetup --> CallConfirmed{{Call Confirmed}}; CallConfirmed --> EstablishTCH[Establish_Terminating_TCH_Multicall]; EstablishTCH --> ResultPass{Result=Pass?}; ResultPass -- Yes --> WaitAlert([Wait_For_Alerting]); ResultPass -- No --> ResultAborted{Result=Aborted?}; ResultAborted -- Yes --> 5((5)); ResultAborted -- No --> 4((4)); +``` + +Callouts: + +- See TS 23.018 +- See TS 29.007 +- See TS 23.087 +- See TS 23.093 +- See TS 23.135 + +Flowchart for Procedure Process\_Call\_Waiting. It starts with a decision 'CW Treatment indicator for existing call set to CW Allowed?'. If 'No', it goes to 'Set negative response: Busy subscriber(NDUB)'. If 'Yes', it goes to 'Call being set up'. If 'Yes' to 'Call being set up', it goes to 'Process Call Waiting negative response'. If 'No' to 'Call being set up', it goes to 'Set\_CLIP\_Info\_MSC', then 'Derive required PLMN BC', then 'Setup'. From 'Setup', it goes to 'UUS\_ICH\_UUS1\_Explicit\_Active', then 'CCBS\_Report\_Not\_Idle', then 'Wait\_For\_Setup\_Response', then 'Call Confirmed', then 'Establish\_Terminating\_TCH\_Multicall', then 'Result=Pass?'. If 'Yes' to 'Result=Pass?', it goes to 'Wait\_For\_Alerting'. If 'No' to 'Result=Pass?', it goes to 'Result=Aborted?'. If 'Yes' to 'Result=Aborted?', it goes to connector 5. If 'No' to 'Result=Aborted?', it goes to connector 4. Callouts include 'See TS 23.018', 'See TS 29.007', 'See TS 23.087', 'See TS 23.093', and 'See TS 23.135'. + +Figure 1.5 (sheet 1 of 9): Procedure Process\_Call\_Waiting + + + +## Procedure Process\_Call\_Waiting + +PCW2(9) + +Procedure in the MSC to handle a Process Call Waiting request from the VLR + +Signals to/from the left are to/from the BSS; signals to/from the right are to/from the VLR unless marked otherwise + +``` + + graph TD + Start([Wait_For_Alerting]) + Start --> Alerting[/Alerting/] + Start --> CD_Req[/CD Request/] + Start --> Alert_Fail[/Alerting failure/] + + %% Alerting Branch + Alerting --> UUS[UUS_ICH_Check_Support] + UUS --> TS_087[See TS 23.087] + UUS --> Res_Pass{Result=Pass?} + Res_Pass -- No --> Rel_Trans[Release transaction] + Rel_Trans --> Conn2((2)) + Res_Pass -- Yes --> CCBS_Succ1[CCBS_ICH_MSC_Report_Success] + CCBS_Succ1 --> TS_093a[See TS 23.093] + CCBS_Succ1 --> UTU2[UTU2Cnt:=0] + UTU2 --> Wait_Call[For waiting call] + UTU2 --> NRCT{NRCT provided?} + NRCT -- No --> Start_Acc[Start Acceptance timer] + NRCT -- Yes --> Start_NoRep[Start No Reply Call Timer] + Start_NoRep --> Start_Acc + Start_Acc --> CAMEL_TNRy[CAMEL_Start_TNRy] + CAMEL_TNRy --> TS_078a[See TS 23.078] + CAMEL_TNRy --> Send_ACM[Send_ACM_If_Required] + Send_ACM --> GMSC_Wait[To GMSC of waiting call] + Send_ACM --> CAMEL_Alert[CAMEL_MT_MSC_ALERTING] + CAMEL_Alert --> TS_078b[See TS 23.078] + CAMEL_Alert --> Res_Final{Result?} + + Res_Final -- Pass --> Wait_Acc([Wait_For_Acceptance]) + Wait_Acc --> ConnA((A)) + Res_Final -- Fail --> Rel_Fail[Release] + Rel_Fail --> GMSC_Wait2[To GMSC of waiting call] + Rel_Fail --> ConnA + Res_Final -- Answer --> ConnB((B)) + Res_Final -- Reconnect --> Res_Rec[Result:= Reconnect] + Res_Rec --> Term1((X)) + + %% CD Request Branch + CD_Req --> CCBS_Succ2[CCBS_ICH_MSC_Report_Success] + CCBS_Succ2 --> TS_093b[See TS 23.093] + CCBS_Succ2 --> Hand_CD[Handling_CD_MSC] + Hand_CD --> TS_072[See TS 23.072] + Hand_CD --> Neg_Resp[Process Call Waiting negative response] + Neg_Resp --> Res_Fail2[Result:= Fail] + Res_Fail2 --> Term2((X)) + + %% Alerting Failure Branch + Alert_Fail --> Set_Cause[Set cause] + Conn2 --> Set_Cause + Conn4((4)) --> Set_Cause + Set_Cause --> CAMEL_Disc[CAMEL_MT_GMSC_DISC4] + CAMEL_Disc --> TS_093c[See TS 23.093] + CAMEL_Disc --> Res_Rec2{Result=Reconnect?} + Res_Rec2 -- Yes --> Res_Rec3[Result:= Reconnect] + Res_Rec3 --> Term3((X)) + Res_Rec2 -- No --> CCBS_Fail[CCBS_ICH_MSC_Report_Failure] + CCBS_Fail --> TS_093d[See TS 23.093] + CCBS_Fail --> Rel_Abort[Release] + Rel_Abort --> GMSC_Wait3[To GMSC of waiting call] + Rel_Abort --> Abort[Abort] + Abort --> Res_Aborted[Result:= Aborted] + Res_Aborted --> Term4((X)) + +``` + +Flowchart of Procedure Process\_Call\_Waiting (sheet 2 of 9). The process begins at state 'Wait\_For\_Alerting'. It branches into 'Alerting', 'CD Request', and 'Alerting failure'. The 'Alerting' path checks UUS support, reports success, and starts timers. The 'CD Request' path handles call deflection. The 'Alerting failure' path sets causes and handles CAMEL disconnection. Various outcomes lead to connectors A, B, or termination points. + +**Figure 1.5 (sheet 2 of 9): Procedure Process\_Call\_Waiting** + + + +### Procedure Process\_Call\_Waiting + +PCW3(9) + +Procedure in the MSC to handle a Process Call Waiting request from the VLR + +Signals to/from the left are to/from the BSS; +signals to/from the right are to/from the VLR +unless marked otherwise + +``` +graph TD; Start([Wait_For_Setup_Response]) --> Branch1[Release transaction (reject)]; Start --> Branch2[Setup failure]; Start --> Branch3[Release transaction (UDUB)]; Start --> Branch4[Int_Release Call]; Branch4 --> gsmSSF[From gsmSSF]; Branch1 --> UUS1[UUS_ICH_Check_Support]; UUS1 --> CAMEL[CAMEL_MT_GMSC_DISC4]; CAMEL --> Decision{Result=Reconnect?}; Decision -- Yes --> ResultReconnect[Result:= Reconnect]; Decision -- No --> CCBS1[CCBS_ICH_MSC_Report_Failure]; CCBS1 --> Release[Release]; Release --> GMSC[To GMSC of waiting call]; Release --> Abort[Abort]; Abort --> ResultAborted[Result:= Aborted]; Branch2 --> Clear[Clear pending call]; Clear --> UUS1; Branch3 --> UUS2[UUS_ICH_Check_Support]; UUS2 --> SetNegative[Set negative response: Busy subscriber(UDUB)]; SetNegative --> ProcessNegative[Process Call Waiting negative response]; ProcessNegative --> CCBS2[CCBS_ICH_MSC_Report_Failure]; CCBS2 --> ResultFail[Result:= Fail]; +``` + +See TS 23.087 + +See TS 23.078 + +See TS 23.093 + +See TS 23.093 + +Flowchart for Procedure Process\_Call\_Waiting. It starts with 'Wait\_For\_Setup\_Response' and branches into four main paths: 'Release transaction (reject)', 'Setup failure', 'Release transaction (UDUB)', and 'Int\_Release Call'. The first three paths lead to 'UUS\_ICH\_Check\_Support' blocks, which then lead to a 'CAMEL\_MT\_GMSC\_DISC4' block. From there, a decision 'Result=Reconnect?' is made. If 'Yes', it leads to 'Result:= Reconnect'. If 'No', it leads to 'CCBS\_ICH\_MSC\_Report\_Failure', which then leads to a 'Release' block, then an 'Abort' block, and finally 'Result:= Aborted'. The 'Release' block also leads to 'To GMSC of waiting call'. The 'Int\_Release Call' path leads to 'From gsmSSF'. The 'Release transaction (UDUB)' path leads to 'UUS\_ICH\_Check\_Support', then 'Set negative response: Busy subscriber(UDUB)', then 'Process Call Waiting negative response', then 'CCBS\_ICH\_MSC\_Report\_Failure', and finally 'Result:= Fail'. Various 'See TS' references are included throughout the flow. + +Figure 1.5 (sheet 3 of 9): Procedure Process\_Call\_Waiting + + + +### Procedure Process\_Call\_Waiting + +PCW4(9) + +Procedure in the MSC to handle a Process Call Waiting request from the VLR + +Signals to/from the left are to/from the BSS; +signals to/from the right are to/from the VLR +unless marked otherwise + +``` +graph TD; Start(( )) --> Wait[Wait_For_Setup_Response, Wait_For_Alerting]; Wait --> Release[Release]; Release --> CCBS[CCBS_ICH_MSC_Report_Failure]; CCBS --> UUS[UUS_MSC_Check_UUS1_UI]; UUS --> ReleaseTrans[Release transaction]; ReleaseTrans --> CAMEL[CAMEL_MT_GMSC_DISC6]; CAMEL --> Abort[Abort]; Abort --> ReleaseRes[Release call resources]; ReleaseRes --> Result[Result:= Aborted]; Result --> End(((X)))); +``` + +The flowchart illustrates the 'Procedure Process\_Call\_Waiting' in an MSC. It begins with an initial state (oval) leading to a state 'Wait\_For\_Setup\_Response, Wait\_For\_Alerting'. A 'Release' signal (trapezoid) is received from the GMSC of the waiting call. This is followed by a 'CCBS\_ICH\_MSC\_Report\_Failure' signal (rectangle), which refers to TS 23.093. Next is a 'UUS\_MSC\_Check\_UUS1\_UI' signal (rectangle), referring to TS 23.087. A 'Release transaction' (diamond) is then performed for the waiting call. This is followed by a 'CAMEL\_MT\_GMSC\_DISC6' signal (rectangle), referring to TS 23.078. An 'Abort' (diamond) is then performed. 'Release call resources' (rectangle) are released for the waiting call. The procedure concludes with 'Result:= Aborted' (rectangle) and an end state (circle with an X). + +Flowchart for Procedure Process\_Call\_Waiting + +Figure 1.5 (sheet 4 of 9): Procedure Process\_Call\_Waiting + + + +### Procedure Process\_Call\_Waiting + +PCW5(9) + +Procedure in the MSC to handle a Process Call Waiting request from the VLR + +Signals to/from the left are to/from the BSS; signals to/from the right are to/from the VLR unless marked otherwise + +``` +graph TD; WFA([Wait_for_Acceptance]) --> C{Connect}; C --> STNRy[CAMEL Stop_TNRy]; STNRy --- STNRy_ref[See TS 23.078]; C --> UICH[UUS_ICH_Check_Support]; UICH --- UICH_ref[See TS 23.087]; UICH --> RP{Result=Pass?}; RP -- No --> R1{Release}; R1 --> GMSC1[To GMSC of waiting call]; GMSC1 --> C2((2)); RP -- Yes --> M{Multicall supported in MSC?}; M -- No --> ET[Establish_Terminating_TCH_If_Required]; ET --- ET_ref[See TS 23.018]; ET --> C3((3)); M -- Yes --> ETM[Establish_Terminating_TCH_Multicall]; ETM --- ETM_ref[See TS 23.135]; ETM --> C2; C --> B((B)); FGSF[From gsmSSF] --> IRC[Int_Release_Call]; IRC --> A{Abort}; A --> RT{Release transaction}; RT --> R2{Release}; R2 --> GMSC2[To GMSC of waiting call]; GMSC2 --> RA[Result:= Aborted]; RA --> CX((X)); +``` + +Flowchart for Procedure Process\_Call\_Waiting. It starts with 'Wait\_for\_Acceptance' leading to 'Connect'. 'Connect' leads to 'CAMEL Stop\_TNRy' (See TS 23.078) and 'UUS\_ICH\_Check\_Support' (See TS 23.087). A decision 'Result=Pass?' follows. If 'No', it goes to 'Release' (To GMSC of waiting call) and then to connector '2'. If 'Yes', it goes to a triangle labeled 'Multicall supported in MSC?'. If 'No', it goes to 'Establish\_Terminating\_TCH\_If\_Required' (See TS 23.018) and then to connector '3'. If 'Yes', it goes to 'Establish\_Terminating\_TCH\_Multicall' (See TS 23.135) and then to connector '2'. A connector 'B' is also shown. On the left side, 'From gsmSSF' leads to 'Int\_Release\_Call', which leads to 'Abort', 'Release transaction', 'Release' (To GMSC of waiting call), 'Result:= Aborted', and finally to connector 'X'. + +Figure 1.5 (sheet 5 of 9): Procedure Process\_Call\_Waiting + + + +### Procedure Process\_Call\_Waiting + +PCW6(9) + +Procedure in the MSC to handle a Process Call Waiting request from the VLR + +Signals to the right are to the VLR + +``` +graph TD + Start((3)) --> ResPass{Result= +Pass?} + ResPass -- Yes --> HandleAoC[Handle_AoC_ +MT_MSC] + ResPass -- No --> ResAborted{Result= +Aborted?} + + HandleAoC --> ResPass2{Result= +Pass?} + ResPass2 -- Yes --> ConnectAck[/Connect +ack/] + ResPass2 -- No --> ResAborted + + ConnectAck --> CAMELAnswer[[CAMEL_ +MT_GMSC_ +ANSWER]] + CAMELAnswer --> Res{Result?} + + Res -- Pass --> SetCOL[Set_COL_ +Presentation_ +Indicator_MSC] + SetCOL --> SendAnswer[Send_ +Answer_If_ +Required] + SendAnswer --> ProcessAck[/Process Call +Waiting ack/] + ProcessAck --> ResPassFinal[Result:= +Pass] + ResPassFinal --> EndPass(( )) + + Res -- Fail --> Abort1[/Abort/] + Abort1 --> ResAbortedFinal[Result:= +Aborted] + ResAbortedFinal --> EndAbort(( )) + + Res -- Release --> Release1[/Release/] + Release1 --> ToGMSC1[To GMSC of +waiting call] + Release1 --> Abort2[/Abort/] + Abort2 --> ResAbortedFinal + + Res -- Reconnect --> ResReconnect{Result= +Reconnect?} + ResReconnect -- Yes --> ResReconnectFinal[Result:= +Reconnect] + ResReconnectFinal --> EndReconnect(( )) + + ResReconnect -- No --> Release2[/Release/] + Release2 --> ToGMSC2[To GMSC of +waiting call] + Release2 --> Abort3[/Abort/] + Abort3 --> ResAbortedFinal + + ResAborted -- Yes --> End5((5)) + ResAborted -- No --> CAMELDisc4[[CAMEL_ +MT_GMSC_ +DISC4]] + + CAMELDisc4 --> ResReconnect2{Result= +Reconnect?} + ResReconnect2 -- Yes --> ResReconnectFinal + ResReconnect2 -- No --> Release3[/Release/] + Release3 --> ToGMSC3[To GMSC of +waiting call] + Release3 --> Abort4[/Abort/] + Abort4 --> ResAbortedFinal + + CAMELDisc4 --> CAMELDisc6[[CAMEL_ +MT_GMSC_ +DISC6]] + CAMELDisc6 --> Abort5[/Abort/] + Abort5 --> ReleaseCall[Release call +resources] + ReleaseCall --> ResAbortedFinal +``` + +*Annotations:* + +- See TS 23.018 (near Handle\_AoC\_MT\_MSC and Set\_COL\_Presentation\_Indicator\_MSC) +- See TS 23.078 (near CAMEL\_MT\_GMSC\_ANSWER, CAMEL\_MT\_GMSC\_DISC4, and CAMEL\_MT\_GMSC\_DISC6) +- See TS 23.018 (To GMSC of waiting call.) (near Send\_Answer\_If\_Required) + +**Figure 1.5 (sheet 6 of 9): Procedure Process\_Call\_Waiting** + + + +### Procedure Process\_Call\_Waiting + +PCW7(9) + +Procedure in the MSC to handle a Process Call Waiting request from the VLR + +Signals to/from the left are to/from the BSS; + signals to/from the right are to/from the VLR + unless marked otherwise + +``` + + graph TD + Start([Wait_for_Acceptance]) + + Start --- L1[ ] + style L1 width:0px, height:0px + + L1 --> RelBusy{Release +transaction +(busy)} + L1 --> RelReject{Release +transaction +(reject)} + L1 --> Conn1((1)) + L1 --> AccTimer{Acceptance +timer expired} + L1 --> CamelTNRy{CAMEL TNRy +expired} + L1 --> NoReply{No Reply +Call Timer +expired} + + %% Path: Release transaction (busy) + RelBusy --> UUS_ICH1[UUS_ICH_ +Check_ +Forwarding] + UUS_ICH1 --> Pass1{Result= +Pass?} + Pass1 -- No --> UUS_MSC[UUS_MSC_ +Check_ +UUS1_UUI] + UUS_MSC --> Conn2((2)) + Pass1 -- Yes --> SetNegBusy[Set negative +response: +Busy +subscriber(UDUB)] + SetNegBusy --> ProcNegBusy[Process +Call Waiting +negative +response] + ProcNegBusy --> ResFail1([Result:= +Fail]) + + %% Path: Release transaction (reject) + RelReject --> CamelDisc4[CAMEL_ +MT_GMSC_ +DISC4] + CamelDisc4 --> Reconn1{Result= +Reconnect?} + Reconn1 -- Yes --> Rel1[Release] + Rel1 --> ToGMSC[To GMSC of +waiting call] + Reconn1 -- No --> UUS_ICH2[UUS_ICH_ +Check_ +Forwarding] + UUS_ICH2 --> Abort1[Abort] + Abort1 --> ResAborted([Result:= +Aborted]) + + %% Path: Acceptance timer expired + Conn1 --> AccTimer + AccTimer --> RelTrans1[Release +transaction] + RelTrans1 --> CamelDisc5[CAMEL_ +MT_GMSC_ +DISC5] + CamelDisc5 --> ResReconn([Result:= +Reconnect]) + + %% Path: CAMEL TNRy expired + CamelTNRy --> See87_1[See TS 23.087] + + %% Path: No Reply Call Timer expired + NoReply --> UUS_ICH3[UUS_ICH_ +Check_ +Forwarding] + UUS_ICH3 --> Pass2{Result= +Pass?} + Pass2 -- No --> ResFail2([Result:= +Fail]) + Pass2 -- Yes --> SetNegNoRep[Set negative +response: +No subscriber +reply] + SetNegNoRep --> ProcNegNoRep[Process +Call Waiting +negative +response] + ProcNegNoRep --> RelTrans2[Release +transaction] + RelTrans2 --> ResFail2 + + %% Annotations + UUS_ICH1 --- See87_2[See TS 23.087] + CamelDisc4 --- See78_1[See TS 23.078] + UUS_ICH2 --- See87_3[See TS 23.087] + RelTrans1 --- ForWait1[For waiting call] + CamelDisc5 --- See78_2[See TS 23.078] + NoReply --- See87_4[See TS 23.087] + RelTrans2 --- ForWait2[For waiting call] + +``` + +**Figure 1.5 (sheet 7 of 9): Procedure Process\_Call\_Waiting** + + + +### Procedure Process\_Call\_Waiting + +PCW8(9) + +Procedure in the MSC to handle a Process Call Waiting request from the VLR + +Signals to/from the left are to/from the BSS; signals to/from the right are to/from the VLR unless marked otherwise + +``` +graph TD; Start([Wait_For_Acceptance]) --> Release{Release}; Start --> CD{CD Request}; Start --> U2U1{User To User}; Start --> U2U2{User To User}; Release --> R1[From GMSC of waiting call]; R1 --> R2[UUS_MSC_Check_UUS1_UI]; R2 --> R3[See TS 23.087]; R2 --> R4{Release transaction}; R4 --> R5[For waiting call]; R4 --> R6[See TS 23.072]; R4 --> R7[CAMEL_MT_GMSC_DISC6]; R7 --> R8[See TS 23.078]; R7 --> R9{Abort}; R9 --> R10[Release call resources]; R10 --> R11[For waiting call]; R10 --> R12[Result:= Aborted]; R12 --> R13((X)); CD --> CD1[UUS_ICH_Check_Forwarding]; CD1 --> CD2[See TS 23.087]; CD1 --> CD3{Result:= Pass?}; CD3 -- No --> CD4[CD_UUS_Interaction]; CD3 -- Yes --> CD5[Handling_CD_MSC]; CD5 --> CD6{Process Call Waiting negative response}; CD6 --> CD7[Result:= Fail]; CD7 --> CD8((X)); U2U1 --> U2U1_1[From GMSC of active call]; U2U1_1 --> U2U1_2[UUS_MSC_Check_UUS2_UI to NW]; U2U1_2 --> U2U1_3[See TS 23.087]; U2U1_2 --> U2U1_4[Wait_For_Acceptance]; U2U1_4 --> U2U1_5[See TS 23.087]; U2U2 --> U2U2_1[UUS_MSC_Check_UUS2_UI to MS]; U2U2_1 --> U2U2_2[See GSM 03.72]; U2U2_1 --> U2U2_3[Wait_For_Acceptance]; U2U2_3 --> U2U2_4[See TS 23.087]; U2U2_4 --> CD4; CD4 --> CD4_1[1]; +``` + +Flowchart for Procedure Process\_Call\_Waiting. It starts with 'Wait\_For\_Acceptance' and branches into four main paths: 'Release' (for waiting call), 'CD Request', 'User To User' (for active call), and another 'User To User' path. The 'Release' path leads to 'UUS\_MSC\_Check\_UUS1\_UI', 'Release transaction', 'CAMEL\_MT\_GMSC\_DISC6', 'Abort', 'Release call resources', and 'Result:= Aborted'. The 'CD Request' path leads to 'UUS\_ICH\_Check\_Forwarding', 'Result:= Pass?', 'Handling\_CD\_MSC', 'Process Call Waiting negative response', and 'Result:= Fail'. The 'User To User' paths lead to various 'UUS\_MSC' checks and eventually to 'Wait\_For\_Acceptance' or 'CD\_UUS\_Interaction'. The 'CD\_UUS\_Interaction' path leads to 'See GSM 03.72' and connector '1'. + +Figure 1.5 (sheet 8 of 9): Procedure Process\_Call\_Waiting + + + +### Procedure Process\_Call\_Waiting + +PCW9(9) + +Procedure in the MSC to handle a Process Call Waiting request from the VLR + +Signals to/from the left are to/from the BSS; signals to/from the right are to/from the VLR unless marked otherwise + +``` + +graph TD + Start([Wait_For_Setup_Response, +Wait_For_Alerting]) --> Release{Release} + Release -- "From GMSC of +waiting call" --> OCBS[CCBS_ICH_MSC_ +Report_Failure] + OCBS -. "See TS 23.093" .-> OCBS + OCBS --> UUS[UUS_MSC_ +Check_ +UUS1_UUI] + UUS -. "See TS 23.087" .-> UUS + UUS --> ReleaseTrans{Release +transaction} + ReleaseTrans -- "For waiting call" --> CAMEL[CAMEL_ +MT_GMSC_ +DISC6] + CAMEL -. "See TS 23.078" .-> CAMEL + CAMEL --> Abort{Abort} + Abort --> ReleaseRes[Release call +resources] + ReleaseRes -- "For waiting call" --> Result[Result:= +Aborted] + Result --> End(( )) + +``` + +The flowchart illustrates the final sheet of the 'Procedure Process\_Call\_Waiting'. It starts in the states **Wait\_For\_Setup\_Response** or **Wait\_For\_Alerting**. Upon receiving a **Release** signal from the GMSC of the waiting call, it proceeds through several sub-procedures: **CCBS\_ICH\_MSC\_Report\_Failure** (referencing *TS 23.093*), **UUS\_MSC\_Check\_UUS1\_UUI** (referencing *TS 23.087*), and **CAMEL\_MT\_GMSC\_DISC6** (referencing *TS 23.078*). The process involves releasing the transaction and call resources for the waiting call, ultimately resulting in **Result:= Aborted**. + +SDL Flowchart for Procedure Process\_Call\_Waiting sheet 9 of 9 + +**Figure 1.5 (sheet 9 of 9): Procedure Process\_Call\_Waiting** + + + +``` + +sequenceDiagram + participant TEa + participant LEa + participant TEC + participant LEC + participant VLR + participant MSC + participant MS + + Note left of TEa: CHANNEL NOT AVAILABLE +subscriber C wants to set up connection C-B + + TEC->>LEC: set-up + LEC->>TEC: interrogation + TEC->>LEC: acknowledge + LEC->>MSC: set-up + Note right of VLR: MAF013 + MSC->>VLR: info req + VLR->>MSC: info ack + MSC->>MS: set-up + Note right of MSC: start timer T1 + + Note left of TEa: WAITING ACKNOWLEDGMENT + + Note left of LEa: WAITING ACKNOWLEDGMENT +B being informed + + MS->>MSC: call-conf + Note right of MSC: stop timer T1 + MS->>MSC: alert + Note right of MSC: start timer T2 or T3 + LEC->>TEC: notify C (call waiting C-B) + Note left of TEa: CALL A-B ACTIVE/CALL C-B WAITING or +CALL A-B ACTIVE/CALL C-B WAITING/CALL D-B HELD or +CALL A-B HELD/CALL C-B WAITING + + Note left of TEa: WAITING ACKNOWLEDGMENT +timer T1 expires + + Note right of MSC: T1 expires + LEC->>TEC: disconnect demand (no user responding) + Note left of TEC: no user responding + TEC->>LEC: disconnect demand + Note left of TEa: CHANNEL NOT AVAILABLE + +``` + +Sequence diagram showing information flow for call waiting between TEa, LEa, TEC, LEC, VLR, MSC, and MS. The diagram is divided into three horizontal sections. The first section shows the initial setup where subscriber C wants to set up a connection C-B, but the channel is not available. The second section shows the waiting state where the user is informed and other call states are possible. The third section shows the expiration of timer T1 and the subsequent disconnect demand due to no user response. + +NOTE 1: info req: information request +info ack: information acknowledge + +**Figure 1.6 (sheet 1 of 7): Information flow for call waiting** + + + +**Section 1: Call A-B held, Call C-B waiting** + +- TEa: CALL A-B ACTIVE/CALL C-B WAITING/CALL D-B HELD or +- LEa: CALL A-B HELD/CALL C-B WAITING or +- TEC: CALL A-B ACTIVE/CALL C-B WAITING +- LEC: timer T2 expires +- LEC to TEC: disconnect demand +- TEC to LEC: user alerting, no answer +- LEC to VLR: disconnect demand +- VLR to MSC: disconnect demand (user alerting, no answer) +- MSC: T2 expires +- MSC to MS: disconnect demand (C-B) +- MS to MSC: (recovery after timer expiry) +- TEa: CHANNEL NOT AVAILABLE + +**Section 2: Call C-B waiting** + +- TEa: CALL C-B WAITING +- LEa: timer T2 expires +- LEC to VLR: disconnect demand +- VLR to MSC: disconnect demand (user alerting, no answer) +- MSC: T2 expires +- MSC to MS: disconnect demand (C-B) +- MS to MSC: (recovery after time expiry) +- TEa: IDLE + +**Section 3: Call A-B held, Call C-B rejected (busy)** + +- TEa: CALL A-B HELD/CALL C-B WAITING or +- LEa: CALL A-B ACTIVE/CALL C-B WAITING/CALL D-B HELD or +- TEC: CALL A-B ACTIVE/CALL C-B WAITING +- LEC: B rejects incoming call from C +- LEC to TEC: disconnect demand +- TEC to LEC: (user busy) +- LEC to VLR: disconnect demand +- VLR to MSC: disconnect demand (user busy) +- MSC: stop T2 or T3 (note 2) +- MSC to MS: connection reject +- MS to MSC: (user busy) +- TEa: CHANNEL NOT AVAILABLE + +Sequence diagrams showing information flow for call waiting between TEa, LEa, TEC, LEC, VLR, MSC, and MS. The diagram is divided into three horizontal sections. The first section shows a call from A to B being held while a call from C to B is waiting. The second section shows the waiting call from C to B expiring. The third section shows a call from A to B being held while a call from C to B is waiting, but the call from C to B is rejected because B is busy. + +NOTE 2: The call shall be forwarded on mobile subscriber busy at this stage if activated. + +Figure 1.6 (sheet 2 of 7): Information flow for call waiting + + + +The diagram consists of three sequence diagrams illustrating call waiting scenarios. The lifelines are TEa, LEa, TEC, LEC, VLR, MSC, and MS. + +**Scenario 1: C releases waiting call** + +- Initial states: + - TEa: CALL A-B HELD/CALL C-B WAITING or + - LEa: CALL A-B ACTIVE/CALL C-B WAITING/CALL D-B HELD or + - TEC: CALL A-B ACTIVE/CALL C-B WAITING +- C releases waiting call (from TEC to LEa). +- TEC sends a **disconnect demand** to LEC. +- LEC sends a **disconnect demand** to MSC. +- MSC sends a **disconnect demand** to MS. +- MS sends a **disconnect ack** to MSC. +- MSC sends a **disconnect acknowledge** to LEC. +- LEC sends a **disconnect ack** to TEC. +- Final state: CHANNEL NOT AVAILABLE (at TEa). + +**Scenario 2: B rejects incoming call from C** + +- Initial state: CALL C-B WAITING (at TEa). +- B rejects incoming call from C (from LEa to TEC). +- TEC sends a **disconnect demand** to LEC. +- LEC sends a **disconnect demand** to MSC. +- MSC sends a **connection reject (user busy)** to LEC. +- LEC sends a **disconnect ack (user busy)** to TEC. +- Final state: IDLE (at TEa). + +**Scenario 3: C releases waiting call (IDLE final state)** + +- Initial state: CALL C-B WAITING (at TEa). +- C releases waiting call (from TEC to LEa). +- TEC sends a **disconnect demand** to LEC. +- LEC sends a **disconnect demand** to MSC. +- MSC sends a **disconnect demand** to MS. +- MS sends a **disconnect ack** to MSC. +- MSC sends a **disconnect acknowledge** to LEC. +- LEC sends a **disconnect ack** to TEC. +- Final state: IDLE (at TEa). + +Sequence diagrams showing information flow for call waiting scenarios between TEa, LEa, TEC, LEC, VLR, MSC, and MS. + +NOTE 3: The call shall be forwarded on mobile subscriber busy at this stage if activated. + +**Figure 1.6 (sheet 3 of 7): Information flow for call waiting** + + + +**Top Sequence Diagram: CALL A-B ACTIVE/CALL C-B WAITING** + +Initial state: CALL A-B ACTIVE/CALL C-B WAITING + subscriber B wants to hold active call and connect the waiting call + +Sequence of messages: + +- LEa → TEa: notify A (call A-B held by B) +- TEa → LEa: call A-B held by B +- LEC → TEC: connection demand +- TEC → LEC: connection demand +- MSC → MS: hold A-B +- MSC → MS: connect waiting call +- MSC → MS: stop T2 or T3 +- MSC → MS: connection ack (C-B) + +Final state: CALL A-B HELD/CALL C-B ACTIVE + +**Bottom Sequence Diagram: CALL A-B HELD/CALL C-B WAITING or CALL A-B ACTIVE/CALL C-B WAITING** + +Initial state: CALL A-B HELD/CALL C-B WAITING or CALL A-B ACTIVE/CALL C-B WAITING + subscriber B wants to terminate active or held call and connect waiting call + +Sequence of messages: + +- LEa → TEa: disconnect demand (A-B) +- TEa → LEa: CONTINUE A-B AS NORMAL CALL CLEARING +- LEC → TEC: disconnect demand (A-B) +- TEC → LEC: connection demand +- MSC → MS: disconnect demand (A-B) +- MSC → MS: disconnect ack (A-B) +- MSC → MS: connection demand (C-B) +- MSC → MS: stop T2 or T3 (note 4) +- MSC → MS: connection ack (C-B) + +Final state: CALL C-B ACTIVE + +Sequence diagrams for call waiting information flow. The top diagram shows the flow for 'CALL A-B ACTIVE/CALL C-B WAITING' where subscriber B wants to hold the active call and connect the waiting call. The bottom diagram shows the flow for 'CALL A-B HELD/CALL C-B WAITING or CALL A-B ACTIVE/CALL C-B WAITING' where subscriber B wants to terminate the active or held call and connect the waiting call. Lifelines include TEa, LEa, TEC, LEC, VLR, MSC, and MS. + +NOTE 4: If T2 or if applicable T3 expires before reception of connection demand in the MSC then call c-b shall be released with cause no reply and if it was T3 which expired the waiting call from C shall be forwarded on no reply. + +Figure 1.6 (sheet 4 of 7): Information flow for call waiting + + + +The diagram illustrates the information flow for call waiting across three scenarios: + +- Scenario 1:** Initial state: CALL A-B HELD/CALL C-B WAITING or CALL A-B ACTIVE/CALL C-B WAITING. Subscriber A disconnects active or held call. TEa sends a disconnect demand to LEa. LEa sends a disconnect demand (A-B) to VLR. VLR sends a disconnect demand (A-B) to MSC. MSC sends a disconnect demand (A-B) to MS. MS sends a disconnect ack (A-B) to MSC. MSC sends a connection demand (C-B) to VLR. VLR sends a connection demand (C-B) to LEC. LEC sends a connection demand to TEC. TEC sends a connection demand to LEa. LEa sends a CONTINUE A-B AS NORMAL CALL CLEARING message to TEa. MSC also sends a stop T2 or T3 (note 5) message to VLR. MS sends a connection ack (C-B) to MSC. Final state: CALL C-B ACTIVE. +- Scenario 2:** Initial state: CALL A-B WAITING or CALL A-B ACTIVE/CALL C-B WAITING or CALL A-B HELD/CALL C-B WAITING or CALL A-B ACTIVE/CALL C-B WAITING/CALL D-B HELD. A timer T3 expires. TEC sends a disconnect demand to LEC. LEC sends a disconnect demand (user alerting, no answer) to VLR. VLR sends a disconnect demand to MSC. MSC sends a disconnect demand (C-B) to MS. MS sends a disconnect demand (C-B) to MSC. MSC sends a (recovery after timer expiry) message to VLR. Final state: CALL A-B HELD/CALL C-B WAITING. +- Scenario 3:** Initial state: CALL A-B HELD/CALL C-B WAITING. B wants to retrieve held call. MS sends a retrieve req (A-B) to MSC. MSC sends a retrieve ack (A-B) to MS. Final state: CALL A-B ACTIVE/CALL C-B WAITING. (Note: The diagram also shows a retrieve reject (A-B) message from MSC to MS, leading to a final state of CALL A-B HELD/CALL C-B WAITING). + +Sequence diagram showing information flow for call waiting between TEa, LEa, TEC, LEC, VLR, MSC, and MS. The diagram is divided into three horizontal sections. The first section shows a call disconnect and subsequent connection of a waiting call. The second section shows a call waiting scenario where a timer expires and a disconnect demand is sent. The third section shows a call retrieval scenario where a user wants to retrieve a held call. + +NOTE 5: The call shall be forwarded on mobile subscriber busy at this stage if activated. + +NOTE 6: The call shall be forwarded on no reply. + +**Figure 1.6 (sheet 5 of 7): Information flow for call waiting** + + + +**Sequence 1: Establishing a waiting call** + +Initial state: CALL A-B HELD/ CALL C-B WAITING +B wants to connect waiting call + +TEC sends a **connection demand** to LEC. LEC sends a **connection demand (C-B)** to MSC. MSC sends a **connection demand (C-B)** to MS. MS responds with **stop T2 or T3** to MSC. Final state: CALL A-B HELD/ CALL C-B ACTIVE + +**Sequence 2: Terminating the active call while waiting** + +Initial state: CALL A-B ACTIVE/ CALL C-B WAITING/ CALL D-B HELD +B wants to terminate active call + +LEa sends a **disconnect demand (A-B)** to MSC. MSC sends a **disconnect demand (A-B)** to MS. MS responds with **disconnect ack (A-B)** to MSC. Final state: CALL C-B WAITING/ CALL D-B HELD (note 7) + +**Sequence 3: Terminating the active call initiated by the caller** + +Initial state: CALL A-B ACTIVE/ CALL C-B WAITING/ CALL D-B HELD +A disconnects active call + +TEa sends a **disconnect demand** to LEa. LEa sends a **disconnect demand (A-B)** to MSC. MSC sends a **disconnect demand (A-B)** to MS. MS responds with **disconnect ack (A-B)** to MSC. Final state: CALL C-B WAITING/ CALL D-B HELD (note 7) + +Sequence diagrams showing information flow for call waiting between TEa, LEa, TEC, LEC, VLR, MSC, and MS. The diagram is divided into three parts: 1) Establishing a waiting call (CALL A-B HELD/ CALL C-B WAITING to CALL A-B HELD/ CALL C-B ACTIVE). 2) Terminating the active call while waiting (CALL A-B ACTIVE/ CALL C-B WAITING/ CALL D-B HELD to CALL C-B WAITING/ CALL D-B HELD). 3) Terminating the active call initiated by the caller (CALL A-B ACTIVE/ CALL C-B WAITING/ CALL D-B HELD to CALL C-B WAITING/ CALL D-B HELD). + +NOTE 7: This state can be treated as CALL C-B WAITING/ CALL A-B HELD. + +**Figure 1.6 (sheet 6 of 7): Information flow for call waiting** + + + +The diagram consists of two sequence diagrams illustrating the information flow for call waiting between a Mobile Station (MS) and network elements (LED, VLR, MSC). + +**Top Sequence Diagram:** + +- Initial State:** CALL A-B ACTIVE/CALL C-B WAITING/CALL D-B HELD +- Action:** B wants to terminate held call +- Message Flow:** + - MS → MSC: disconnect demand (D-B) + - MSC → VLR: disconnect demand (D-B) + - VLR → LED: disconnect demand +- Intermediate State:** CONTINUE D-B AS NORMAL CALL CLEARING +- Final State:** CALL A-B ACTIVE/CALL C-B WAITING + +**Bottom Sequence Diagram:** + +- Initial State:** CALL A-B ACTIVE/CALL C-B WAITING/CALL D-B HELD +- Action:** D wants to terminate held call +- Message Flow:** + - LED → MSC: disconnect demand + - MSC → MS: disconnect demand (D-B) +- Intermediate State:** CONTINUE D-B AS NORMAL CALL CLEARING +- Final State:** CALL A-B ACTIVE/CALL C-B WAITING + +Figure 1.6 (sheet 7 of 7): Information flow for call waiting. The diagram shows two sequence diagrams illustrating the interaction between a Mobile Station (MS) and network elements (LED, VLR, MSC) for call waiting. The top diagram shows a scenario where the Mobile Station (MS) sends a disconnect demand (D-B) to the MSC, which then forwards it to the VLR, which then forwards it to the LED. The bottom diagram shows a scenario where the LED sends a disconnect demand (D-B) to the MSC, which then forwards it to the MS. Both diagrams show the state transitions of the call waiting service. + +Figure 1.6 (sheet 7 of 7): Information flow for call waiting + +## 1.3 Information stored in the HLR + +Call waiting may have the following logical states (refer to TS 23.011 for an explanation of the notation): + +| Provisioning State | Registration State | Activation State | HLR Induction State | +|--------------------|--------------------|-----------------------|---------------------| +| (Not Provisioned, | Not Applicable, | Not Active, | Not Induced) | +| (Provisioned, | Not Applicable, | Not Active, | Not Induced) | +| (Provisioned, | Not Applicable, | Active and Operative, | Not Induced) | + +The activation state may be different for each applicable elementary basic service group. + +The provisioning state shall be on a per subscriber basis, and hence the same for all basic service groups. + +The HLR shall store the logical state of the call waiting service (which shall be one of the valid states listed above) on a per elementary basic service group. + +## 1.4 State transition model + +The following figure shows the successful cases of transition between the applicable logical states of call waiting. The state changes are either caused by actions of the service provider or the mobile user. + +Note that error cases are not shown in the diagram as they normally do not cause a state change. Additionally, some successful requests may not cause a state change. Hence they are not shown in the diagram. + +The diagram only shows operations on elementary basic service groups. + + + +``` + +stateDiagram-v2 + [*] --> (Not Provisioned, Not Applicable, Not Active, Not Induced) + (Not Provisioned, Not Applicable, Not Active, Not Induced) --> (Provisioned, Not Applicable, Not Active, Not Induced) : Provision + (Provisioned, Not Applicable, Not Active, Not Induced) --> (Not Provisioned, Not Applicable, Not Active, Not Induced) : Withdrawal + (Provisioned, Not Applicable, Active and Operative, Not Induced) --> (Provisioned, Not Applicable, Not Active, Not Induced) : Deactivation + (Provisioned, Not Applicable, Active and Operative, Not Induced) --> (Not Provisioned, Not Applicable, Not Active, Not Induced) : Withdrawal + (Provisioned, Not Applicable, Active and Operative, Not Induced) --> (Provisioned, Not Applicable, Not Active, Not Induced) : Activation + +``` + +State transition model for call waiting. The diagram shows three states represented by ovals. The top-left state is '(Not Provisioned, Not Applicable, Not Active, Not Induced)'. The top-right state is '(Provisioned, Not Applicable, Not Active, Not Induced)'. The bottom state is '(Provisioned, Not Applicable, Active and Operative, Not Induced)'. Transitions are: 'Provision' from top-left to top-right; 'Withdrawal' from top-right to top-left; 'Activation' from bottom to top-right; 'Deactivation' from top-right to bottom; 'Withdrawal' from bottom to top-left. + +Figure 1.7: State transition model for call waiting + +## 1.5 Transfer of information from HLR to VLR + +If the provisioning state for call waiting is "Provisioned" then, when the subscriber registers on a VLR, the HLR shall send that VLR information about the logical state of call waiting. + +If the logical state of call waiting is changed while a subscriber is registered on a VLR, then the HLR shall inform the VLR of the new logical state of call waiting. + +## 1.6 Information stored in the VLR + +For call waiting, the VLR shall store the service state information received from the HLR. + +## 1.7 Handover + +Handover will have no impact on the control procedures and the operation of the service. + +# 2 Call hold (HOLD) + +## 2.1 Functions and information flows + +The following Mobile Additional Function has been identified for the call hold service: + +### MAF024 + +Call hold related authorizations examination + +The ability of a PLMN component to determine the authorizations relating to call hold. See figure 2.1. + +Location: VLR + +The Indicator are shown in figures 2.2 a, 2.2b and 2.2c, respectively. + +Procedure Process\_Retrieve\_Request: the process Subs\_FSM is defined in 3GPP TS 23.018 [5]. + +Procedure Process\_Hold\_Request, procedure Process\_Retrieve\_Request: the variable On\_Hold is set in the process OCH\_MSC or the process ICH\_MSC. + +Procedure Handle\_Timed\_Call\_Swap: the macro Decrement\_Call\_Counter is defined in 3GPP TS 23.018 [5]. + +All procedures: to avoid having two calls on hold at the same time (except as a transient effect during the handling of retrieve), the reception of the retrieve request is supervised by a retrieve timer T (T = 5 s). + +All procedures: the network may receive hold and retrieve requests not included in this overall SDL. These requests will be rejected by the network. + +All procedures: the handling of requests other than hold and retrieve requests is defined in the appropriate supplementary service specification. + +The information flows are shown in figure 2.3. In these flows it is assumed that the served user is a mobile user and that other users are fixed network users. + + + +**Process MAF024** **383\_21(1)** + +Process in the VLR to check the subscription for HOLD. + +Signals to/from the left are to/from the MSC. + +``` +graph TD; Start([ ]) --> Idle1([Idle]); Idle1 --> CheckHOLD[/Check HOLD subscription/]; CheckHOLD --> Decision{HOLD activated}; Decision -- no --> SetIndicator1[set indicator = 'HOLD not activated']; Decision -- yes --> SetIndicator2[set indicator = 'HOLD activated']; SetIndicator1 --> ProcessCallHold[/Process call hold/]; SetIndicator2 --> ProcessCallHold; ProcessCallHold --> Idle2([Idle]); +``` + +Flowchart for Process MAF024: Call hold related authorisations examination (VLR). The flow starts at an oval, goes to an 'Idle' state, then 'Check HOLD subscription'. A decision 'HOLD activated' follows. If 'no', it goes to 'set indicator = 'HOLD not activated''. If 'yes', it goes to 'set indicator = 'HOLD activated''. Both paths lead to 'Process call hold', which then returns to an 'Idle' state. + +**Figure 2.1: MAF024 Call hold related authorisations examination (VLR)** + + + +### Procedure Process\_Hold\_Request + +PHR1(2) + +Procedure in the MSC to handle a HOLD request. + +Signals to/from the left are to/from the BSS; signals to/from the right are to/from MAF024 + +``` +graph TD; Start([ ]) --> On_Hold{On_Hold}; On_Hold -- True --> Hold_Reject{Hold reject}; On_Hold -- False --> Request_Speech{Request from a speech call?}; Request_Speech -- No --> Release[Release]; Request_Speech -- Yes --> HTI_Present{HTI Present in SI22?}; HTI_Present -- Yes --> HTI_Set{HTI Set to Reject Hold Requests?}; HTI_Present -- No --> Check_Hold[Check HOLD subscription]; HTI_Set -- Yes --> Hold_Reject; HTI_Set -- No --> Check_Hold; Check_Hold --> Wait_Status{Wait_For_Hold_Status_Reply}; Wait_Status --> Int_Release[Int_Release_Call]; Wait_Status --> Release; Wait_Status --> Release_Trans[Release transaction]; Wait_Status --> Process_Hold[Process call hold]; Int_Release --> gsmSSF[gsmSSF]; Release --> Distant[From distant exchange]; Release_Trans --> BSS[From BSS]; Process_Hold --> Hold_Activated{Hold Activated?}; Hold_Activated -- Yes --> Hold_Request{Hold request}; Hold_Request --> Subs_FSM[To Subs_FSM]; Subs_FSM --> Wait_Response{Wait_For_Response}; Hold_Activated -- No --> Hold_Reject; +``` + +Flowchart for Procedure Process\_Hold\_Request. The process starts with a connector, followed by a decision 'On\_Hold'. If 'True', it goes to a 'Hold reject' block. If 'False', it goes to 'Request from a speech call?'. If 'No', it goes to a 'Release' block. If 'Yes', it goes to 'HTI Present in SI22?'. If 'Yes', it goes to 'HTI Set to Reject Hold Requests?'. If 'No', it goes to 'Check HOLD subscription'. From 'Check HOLD subscription', it goes to 'Wait\_For\_Hold\_Status\_Reply'. From 'Wait\_For\_Hold\_Status\_Reply', it branches into four paths: 'Int\_Release\_Call' (to gsmSSF), 'Release' (to distant exchange), 'Release transaction' (to BSS), and 'Process call hold'. 'Process call hold' leads to 'Hold Activated?'. If 'Yes', it goes to 'Hold request' -> 'To Subs\_FSM' -> 'Wait\_For\_Response'. If 'No', it goes to 'Hold reject'. + +Figure 2.2a (sheet 1 of 2): Procedure Process\_Hold\_Request + + + +### Procedure Process\_Hold\_Request + +PHR2(2) + +Procedure in the MSC to handle a HOLD request. + +Signals to/from the left are to/from the BSS; +Signals to/from the right are to/from the Subs\_FSM (defined in TS 23.018) unless otherwise marked + +``` +stateDiagram-v2 + [*] --> Wait_For_Response + state "Wait_For_Response" as Wait_For_Response + state "Int_Release_Call" as Int_Release_Call + state "Release" as Release + state "Release transaction" as Release_transaction + state "Hold ack" as Hold_ack + state "Hold reject" as Hold_reject + state "Reserve Bm Channel" as Reserve_Bm_Channel + state "Hold ack" as Hold_ack_2 + state "Hold reject" as Hold_reject_2 + state "Hold status notification" as Hold_status_notification + state "On_Hold:= True" as On_Hold_True + + Wait_For_Response --> Int_Release_Call + Wait_For_Response --> Release + Wait_For_Response --> Release_transaction + Wait_For_Response --> Hold_ack + Wait_For_Response --> Hold_reject + + Int_Release_Call --> [*] + Release --> [*] + Release_transaction --> [*] + Hold_ack --> Reserve_Bm_Channel + Reserve_Bm_Channel --> Hold_ack_2 + Hold_ack_2 --> Hold_status_notification + Hold_status_notification --> On_Hold_True + On_Hold_True --> [*] + Hold_reject --> Hold_reject_2 + Hold_reject_2 --> [*] +``` + +State transition diagram for Procedure Process\_Hold\_Request. It starts with 'Wait\_For\_Response' leading to a horizontal line. From this line, five paths emerge: 1) 'Int\_Release\_Call' (from gsmSSF), 2) 'Release' (from distant exchange), 3) 'Release transaction' (from BSS), 4) 'Hold ack' (leading to 'Reserve Bm Channel' -> 'Hold ack' -> 'Hold status notification' (to originating/destination exchange) -> 'On\_Hold:= True'), and 5) 'Hold reject' (leading to 'Hold reject'). All five paths converge to a single circle with an 'X' at the bottom. + +Figure 2.2a (sheet 2 of 2): Procedure Process\_Hold\_Request + + + +### Procedure Process\_Retrieve\_Request + +PRR1(1) + +Procedure in MSC to check with the Subs FSM that the retrieve request is valid in the current call state. + +Signals to/from the left are to/from the BSS; +Signals to/from the right are to/from the Subs\_FSM (defined in TS 23.018) unless otherwise marked + +``` +graph TD; Start([ ]) --> On_Hold{On_Hold}; On_Hold -- False --> Reject1[Retrieve reject]; On_Hold -- True --> Request{Request from speech call?}; Request -- No --> Reject1; Request -- Yes --> RequestOut[Retrieve request]; RequestOut --> Wait[Wait_For_Reply]; Wait --> Int_Release[Int_Release_Call]; Int_Release --> gsmSSF[gsmSSF]; Wait --> Release[Release]; Release --> Distant[From distant exchange]; Wait --> Release_Trans[Release transaction]; Release_Trans --> BSS[BSS]; Wait --> Ack1[Retrieve ack]; Ack1 --> On_Hold_False[On_Hold:= False]; On_Hold_False --> Ack2[Retrieve ack]; Ack2 --> Hold_Notif[Hold status notification]; Hold_Notif --> OrigDest[To the originating or destination exchange]; Wait --> Reject2[Retrieve reject]; Int_Release --> End(( )); Release --> End; Release_Trans --> End; Ack2 --> End; Hold_Notif --> End; Reject2 --> End; +``` + +Flowchart for Procedure Process\_Retrieve\_Request. It starts with a connector, then a decision 'On\_Hold'. If 'False', it goes to a 'Retrieve reject' block. If 'True', it goes to a decision 'Request from speech call?'. If 'No', it goes to a 'Retrieve reject' block. If 'Yes', it goes to 'Retrieve request' -> 'Wait\_For\_Reply'. From 'Wait\_For\_Reply', it branches into five paths: 1) 'Int\_Release\_Call' (to gsmSSF), 2) 'Release' (to distant exchange), 3) 'Release transaction' (to BSS), 4) 'Retrieve ack' -> 'On\_Hold:= False' -> 'Retrieve ack' -> 'Hold status notification' (to originating/destination exchange), 5) 'Retrieve reject'. All five paths converge to a final connector. + +Figure 2.2b: Procedure Process\_Retrieve\_Request + + + +**Procedure Handle\_Timed\_Call\_Swap** **HTCS1(1)** + +Process in the originating MSC to handle a hold and retrieve. + +Signals to/from the left are to/from either process OCH\_MSC or process ICH\_MSC + +``` + +graph TD + Start([Start retrieve timer]) --> Wait1((Wait_For_Retrieve)) + Wait1 --> CallCleared1{Call cleared} + CallCleared1 -- From held call process --> CallCleared2{Call cleared} + CallCleared2 --> StopRetrieveTimer1[Stop retrieve timer] + StopRetrieveTimer1 --> SpeechCallCnt[Speech_Call_Cnt := Speech_Call_Cnt - 1] + SpeechCallCnt --> ResultHoldClr[Result := Hold_Clr] + ResultHoldClr --> Exit1(( )) + + RetrieveRequest{Retrieve request} --> StopRetrieveTimer2[Stop retrieve timer] + StopRetrieveTimer2 --> HoldAck{Hold ack} + HoldAck --> RetrieveAck{Retrieve ack} + RetrieveAck --> ResultRetrReq[Result := Retr_req] + ResultRetrReq --> Exit2(( )) + + TimerExpired{Timer expired} -- From internal process --> HoldReject{Hold reject} + HoldReject --> ResultTExpr[Result := T_Expr] + ResultTExpr --> Exit3(( )) + + CallCleared3{Call cleared} --> DecrementCallCounter[Decrement_Call_Counter] + DecrementCallCounter -- See 3G TS 23.018 --> Speech[Speech] + DecrementCallCounter -- Non_Speech --> NonSpeechCallOngoing{Non-speech call ongoing?} + + Speech --> StopRetrieveTimer3[Stop retrieve timer] + StopRetrieveTimer3 --> SpeechCallBNull[Speech_CallB := Null] + SpeechCallBNull --> ResultActiveClr[Result := Active_Clr] + ResultActiveClr --> Exit4(( )) + + NonSpeechCallOngoing -- Yes --> Wait1 + NonSpeechCallOngoing -- No --> NonSpeechCallsNull[Non_Speech_Calls := Null] + NonSpeechCallsNull --> Wait2((Wait_For_Retrieve)) + +``` + +Flowchart for Procedure Handle\_Timed\_Call\_Swap. The process starts with 'Start retrieve timer' and 'Wait\_For\_Retrieve'. It then branches into four main paths: 1) 'Call cleared' (from held call process) leads to 'Stop retrieve timer', 'Speech\_Call\_Cnt := Speech\_Call\_Cnt - 1', 'Result := Hold\_Clr', and an exit. 2) 'Retrieve request' leads to 'Stop retrieve timer', 'Hold ack', 'Retrieve ack', 'Result := Retr\_req', and an exit. 3) 'Timer expired' (from internal process) leads to 'Hold reject', 'Result := T\_Expr', and an exit. 4) 'Call cleared' (from originating process) leads to 'Decrement\_Call\_Counter' (with a note 'See 3G TS 23.018'). From 'Decrement\_Call\_Counter', a 'Speech' path leads to 'Stop retrieve timer', 'Speech\_CallB := Null', 'Result := Active\_Clr', and an exit. A 'Non\_Speech' path leads to a decision 'Non-speech call ongoing?'. If 'Yes', it loops back to 'Wait\_For\_Retrieve'. If 'No', it leads to 'Non\_Speech\_Calls := Null' and then to 'Wait\_For\_Retrieve'. + +Figure 2.2c: Procedure Handle\_Timed\_Call\_Swap + + + +``` + +sequenceDiagram + participant MSa + participant MSCa + participant LEb + participant TEb + participant VLRAaa + + Note left of MSa: A-B (active, idle) +user A wants to hold A-B + MSa->>MSCa: hold request + MSCa->>VLRAaa: information request + VLRAaa-->>LEb: information acknowledgement + Note left of MSCa: ORI=N + LEb-->>MSCa: + Note left of MSCa: ORI=Y + MSCa->>LEb: notification (hold) + LEb->>TEb: notification (hold) + Note left of MSa: A-B (active, idle) + MSCa-->>MSa: hold acknowledge + Note left of MSa: A-B (active, hold) + +``` + +Sequence diagram for call hold. Lifelines: MSa, MSCa, LEb, TEb, VLRAaa. The process involves a hold request from MSa to MSCa, an information request from MSCa to VLRAaa, an information acknowledgement from VLRAaa to LEb, and subsequent notifications to TEb. MSa receives hold reject or hold acknowledge from MSCa based on ORI settings. + +NOTE: ORI: call hold (Y: yes N: no) + + + +``` + +sequenceDiagram + participant MSa + participant MSCa + participant LEb + participant TEb + participant LEc + participant TEc + + Note left of MSa: A-B (active, hold) +user A wants to retrieve A-B + MSa->>MSCa: retrieve request + MSCa-->>MSa: retrieve reject + Note left of MSa: A-B (active, hold) + MSCa->>LEb: notification (retrieval) + LEb->>TEb: notification (retrieval) + Note left of MSa: A-B (active, idle) + MSCa-->>MSa: retrieve acknowledge + + Note left of MSa: A-B (active, held) +User A wants to setup new call A-C + MSa->>MSCa: call request A-C + Note left of MSCa: NORMAL CALL ESTABLISHMENT A-C + Note left of MSa: A-B (active, held) A-C (active, idle) + +``` + +Sequence diagram for call retrieval and new call setup. Lifelines: MSa, MSCa, LEb, TEb, LEc, TEc. The first part shows retrieval of call A-B from hold to active. The second part shows the setup of a new call A-C while A-B remains on hold. + +Figure 2.3 (sheet 1 of 3): Information flow for call hold + + + +The sequence diagram illustrates the interaction for call hold across three scenarios: + +- Top Section:** MSa sends a 'hold request A-C' to MSCa. MSCa starts timer T and sends 'notification (hold)' to LEc and TEc. MSa then sends 'retrieve request A-B' to MSCa. MSCa stops timer T and sends 'notification (retrieval)' to LEb and TEb. LEc and TEc receive 'notification (hold)' from LEb and TEb. The call state changes from 'A-B (active, held) A-C (active, idle)' to 'A-B (active, idle) A-C (active, held)'. +- Middle Section:** MSa sends a 'hold request A-C' to MSCa. MSCa starts timer T. After some time, timer T expires, and MSCa sends 'hold reject A-C' to MSa. The call state changes from 'A-B (active, held) A-C (active, hold req)' to 'A-B (active, held) A-C (active, idle)'. +- Bottom Section:** MSa sends a 'disconnect req A-B' to MSCa. MSCa performs 'NORMAL DISCONNECTION A-B' and stops timer T. MSCa then sends 'hold reject A-C' to MSa. The call state changes from 'A-B (active, held) A-C (active, hold req)' to 'A-B (null, idle) A-C (active, idle)'. + +Sequence diagram showing information flow for call hold between MSa, MSCa, LEb, TEb, LEc, and TEc lifelines. The diagram is divided into three sections. The first section shows a successful hold and retrieval. The second section shows a hold request that expires. The third section shows a disconnect and subsequent hold rejection. + +Figure 2.3 (sheet 2 of 3): Information flow for call hold + + + +The diagram illustrates the information flow for call hold across three scenarios: + +- Top Scenario:** MSCa sends a "disconnect req" to LEB, which is then forwarded to TEB. The call states transition from "A-B (active, held) A-C (active, hold req)" to "NORMAL DISCONNECTION A-B" and finally to "A-B (null, idle) A-C (active, idle)". A "hold reject A-C" message is received by MSCa from MSa, and a "stop T" message is sent from MSCa. +- Middle Scenario:** MSa sends a "disconnect req A-C" to MSCa. The call states transition from "A-B (active, held) A-C (active, hold req)" to "NORMAL DISCONNECTION A-C" and finally to "A-B (active, held) A-C (null, idle)". A "hold reject A-C" message is received by MSa from MSCa, and a "stop T" message is sent from MSCa. +- Bottom Scenario:** MSCa sends a "disconnect request" to LEc, which is then forwarded to TEc. The call states transition from "A-B (active, held) A-C (active, hold req)" to "NORMAL DISCONNECTION A-C" and finally to "A-B (active, held) A-C (null, idle)". A "hold reject A-C" message is received by MSCa from MSa, and a "stop T" message is sent from MSCa. + +Sequence diagrams showing information flow for call hold between MSa, MSCa, LEB, TEB, LEc, and TEc. The diagram is divided into three horizontal sections. The first section shows a disconnect request from MSCa to LEB and then to TEB. The second section shows a disconnect request from MSa to MSCa. The third section shows a disconnect request from MSCa to LEc and then to TEc. Each section includes state transitions for the calls between the entities. + +Figure 2.3 (sheet 3 of 3): Information flow for call hold + +## 2.2 Information stored in the HLR + +Call hold may have the following logical states (refer to TS 23.011 for an explanation of the notation): + +| Provisioning State | Registration State | Activation State | HLR Induction State | +|--------------------|--------------------|-----------------------|---------------------| +| (Not Provisioned, | Not Applicable, | Not Active, | Not Induced) | +| (Provisioned, | Not Applicable, | Active and Operative, | Not Induced) | + +The HLR shall store the logical state of the call hold service (which shall be one of the valid states listed above) on a per subscriber basis. + +## 2.3 State transition model + +The following figure shows the successful cases of transition between the applicable logical states of call hold. The state changes are caused by actions of the service provider. + +Note that error cases are not shown in the diagram as they normally do not cause a state change. Additionally, some successful requests may not cause a state change. Hence they are not shown in the diagram. + + + +``` +stateDiagram-v2 + state " (Not Provisioned, Not Applicable, Not Active, Not Induced) " as S1 + state " (Provisioned, Not Applicable, Active and Operative, Not Induced) " as S2 + S1 --> S2 : Provision + S2 --> S1 : Withdrawal +``` + +The diagram illustrates the state transition model for call hold. It consists of two states represented by ovals. The left state is labeled "(Not Provisioned, Not Applicable, Not Active, Not Induced)". The right state is labeled "(Provisioned, Not Applicable, Active and Operative, Not Induced)". A transition arrow labeled "Provision" points from the left state to the right state. A transition arrow labeled "Withdrawal" points from the right state to the left state. + +State transition model for call hold diagram + +Figure 2.4: State transition model for call hold + +## 2.4 Transfer of information from HLR to VLR + +If the provisioning state for call hold is "Provisioned" then, when the subscriber registers on a VLR, the HLR shall send that VLR information about the logical state of call hold. + +If the logical state of call hold is changed while a subscriber is registered on a VLR, then the HLR shall inform the VLR of the new logical state of call hold. + +## 2.5 Information stored in the VLR + +For call hold, the VLR shall store the service state information received from the HLR. + +## 2.6 Handover + +Handover will have no impact on the control procedures and the operation of the service. + +# Annex A: Change history + +| TSG CN# | Spec | CR | Rev | Phase | Cat | New Ver | Subject/Comment | +|---------|--------|-----|-----|--------|-----|---------|--------------------------------------------------------------------------------------| +| CN#09 | 23.083 | 004 | 1 | R99 | F | 3.2.0 | SDL refresh | +| CN#09 | 23.083 | 005 | 1 | Rel-4 | D | 4.0.0 | Inclusion of call hold in basic call handling | +| CN#11 | 23.083 | 006 | 3 | Rel-4 | C | 4.1.0 | Enhancement of procedures for Call Hold | +| CN#11 | 23.083 | 007 | 1 | Rel-4 | C | 4.2.0 | Enhancement of CW procedures (Missed CR added; TSG agreed 007r1 at CN#11 -> v.4.2.0) | +| CN#14 | 23.083 | 008 | | Rel-4 | F | 4.3.0 | Missing connector in procedure Process_Call_Waiting | +| CN#15 | 23.083 | 009 | 1 | Rel-5 | B | 5.0.0 | Introduction of CAMEL Phase 4 | +| CN#17 | 23.083 | 010 | | Rel-5 | F | 5.1.0 | Determining the basic service for MT calls | +| CN#26 | 23.083 | | | Rel-6 | | 6.0.0 | Release 6 after CN#26 | +| CT#36 | 23.083 | | | Rel-7 | | 7.0.0 | Upgraded unchanged from Rel-6 | +| CT#42 | 23.083 | | | Rel-8 | | 8.0.0 | Upgraded unchanged from Rel-7 | +| CT#46 | 23.083 | - | - | Rel-9 | | 9.0.0 | Update to Rel-9 version (MCC) | +| 2011-03 | 23.083 | - | - | Rel-10 | | 10.0.0 | Update to Rel-10 version (MCC) | +| 2012-09 | 23.083 | - | - | Rel-11 | | 11.0.0 | Update to Rel-11 version (MCC) | +| 2014-09 | 23.083 | - | - | Rel-12 | | 12.0.0 | Update to Rel-12 version (MCC) | +| 2015-12 | 23.083 | - | - | Rel-13 | | 13.0.0 | Update to Rel-13 version (MCC) | +| 2017-03 | 23.083 | - | - | Rel-14 | | 14.0.0 | Update to Rel-14 version (MCC) | +| 2018-06 | 23.083 | - | - | Rel-15 | - | 15.0.0 | Update to Rel-15 version (MCC) | +| 2020-07 | 23.083 | - | - | 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/23084/088921fa3f5a44c8551815122517eefd_img.jpg b/marked/Rel-16/23_series/23084/088921fa3f5a44c8551815122517eefd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..874cff998f5bf82bcb8f6b497a12495716617119 --- /dev/null +++ b/marked/Rel-16/23_series/23084/088921fa3f5a44c8551815122517eefd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e104acce66d50d8e6317051375fdea6605ae674d45a5167c86bec5f29b008b82 +size 119450 diff --git a/marked/Rel-16/23_series/23084/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/marked/Rel-16/23_series/23084/1a827b10290f33d4fec04d0e8ef7a897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..56b72f8c9cd564cac38aa9a1900848143c077c17 --- /dev/null +++ b/marked/Rel-16/23_series/23084/1a827b10290f33d4fec04d0e8ef7a897_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e527fd9895850ee0166838618edec785565c68c835a577c525d0baabaea717ef +size 111450 diff --git a/marked/Rel-16/23_series/23084/26d664119ad25250780f554633444e54_img.jpg b/marked/Rel-16/23_series/23084/26d664119ad25250780f554633444e54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..358778574584c84a82f3cec3ab2e9cdf29f58cec --- /dev/null +++ b/marked/Rel-16/23_series/23084/26d664119ad25250780f554633444e54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:77c28ed75b49f4752f73503222e9215932628be9106935936fdd928584191384 +size 124024 diff --git a/marked/Rel-16/23_series/23084/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/Rel-16/23_series/23084/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dc8e0acdcd683a2ba8603ededf0365a4afbcfa74 --- /dev/null +++ b/marked/Rel-16/23_series/23084/27b06ec9f42b5d727a2630f61a5f1861_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d7943a660648b17b8af016810304aa9d1e0cfe6280e0cdf920caba4905e08418 +size 109925 diff --git a/marked/Rel-16/23_series/23084/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg b/marked/Rel-16/23_series/23084/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..895b479c9f306da64df5733c46f292e71b4810f1 --- /dev/null +++ b/marked/Rel-16/23_series/23084/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7437f4969068cd8e5fe0e1514ac3ae7922fe3bc7fbfa08cd47268c770d78ccfd +size 70289 diff --git a/marked/Rel-16/23_series/23084/4356776ca004ecba5d599667a155d7d4_img.jpg b/marked/Rel-16/23_series/23084/4356776ca004ecba5d599667a155d7d4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b08451d67a6fbff2b435f06f31dd663e30abbcf8 --- /dev/null +++ b/marked/Rel-16/23_series/23084/4356776ca004ecba5d599667a155d7d4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e65e6fcb287c6b1582c29709b5bda1a73d718a7d70b963d453cfa84bbe4a6cea +size 117408 diff --git a/marked/Rel-16/23_series/23084/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Rel-16/23_series/23084/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f36e4bce1c0c34369106c435c578e0f08b0e443a --- /dev/null +++ b/marked/Rel-16/23_series/23084/5a4e62bead259c258d069fd3663ea670_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e5b91fe1a78e177260141d32625d2de0d81c3e3b182a93f7cc8917036cbd6122 +size 116360 diff --git a/marked/Rel-16/23_series/23084/79e1709a7317ead45379cbb8ff3ba802_img.jpg b/marked/Rel-16/23_series/23084/79e1709a7317ead45379cbb8ff3ba802_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..693115920392974f28790d9126bce8c682ae292a --- /dev/null +++ b/marked/Rel-16/23_series/23084/79e1709a7317ead45379cbb8ff3ba802_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fa5c8676a914428b154482fad8c797fa69c3a7e24d886c54bceb2f85f5cafd21 +size 90642 diff --git a/marked/Rel-16/23_series/23084/7a02de7ed198501f7a4f6ca37c3f28c5_img.jpg b/marked/Rel-16/23_series/23084/7a02de7ed198501f7a4f6ca37c3f28c5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..583b95da8a8862eaaabf737ad8166d674da3fc6e --- /dev/null +++ b/marked/Rel-16/23_series/23084/7a02de7ed198501f7a4f6ca37c3f28c5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fd6432292461c1f7609c3ab4df187ab785a3d7df6f83a1fdde1596ad713b7fb7 +size 31739 diff --git a/marked/Rel-16/23_series/23084/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/marked/Rel-16/23_series/23084/7efae06af3af43ffe5d4b956a679cf54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0fa2f3f35e4fb9fd04f06fb693923573df77ffad --- /dev/null +++ b/marked/Rel-16/23_series/23084/7efae06af3af43ffe5d4b956a679cf54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0ac1f8118faecbf194f276154774a6403c8076956cc33f5f021eb4eca2e57a24 +size 125620 diff --git a/marked/Rel-16/23_series/23084/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg b/marked/Rel-16/23_series/23084/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d86e796c63a9aa2b9384f0a4810155938283e05f --- /dev/null +++ b/marked/Rel-16/23_series/23084/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7f2b17da797db0f0014efe840ec8ad9841aa5253101c2a2d4cd59849a3ccee8e +size 112278 diff --git a/marked/Rel-16/23_series/23084/8307f6b04df072c9332f9987e034272c_img.jpg b/marked/Rel-16/23_series/23084/8307f6b04df072c9332f9987e034272c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6c9fc4d58cab4bea60f64470d59f41d925f14aca --- /dev/null +++ b/marked/Rel-16/23_series/23084/8307f6b04df072c9332f9987e034272c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:892cb002f60f8fd6e0e3f574f09411e05bb7e22192b4c263c9c3c3dbdd039768 +size 121385 diff --git a/marked/Rel-16/23_series/23084/8fa679f79a1bb1f527cba9f29e784e89_img.jpg b/marked/Rel-16/23_series/23084/8fa679f79a1bb1f527cba9f29e784e89_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1b5f33722153c0a67d5c02d749f67e370a91ec49 --- /dev/null +++ b/marked/Rel-16/23_series/23084/8fa679f79a1bb1f527cba9f29e784e89_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:82107ab016e5a190ce103fceaf96df0909ee5fc937cc60acf75138fc4ce50e8e +size 125567 diff --git a/marked/Rel-16/23_series/23084/90ddb84c323b956e2d50a54d3f870566_img.jpg b/marked/Rel-16/23_series/23084/90ddb84c323b956e2d50a54d3f870566_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..89a1a845ed213e2552f850ad9cc68932fffa0940 --- /dev/null +++ b/marked/Rel-16/23_series/23084/90ddb84c323b956e2d50a54d3f870566_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0da66cfdd3decb615724f7fd13bdf0f22c681937cbd1c02e5515ccdfdda2b070 +size 137256 diff --git a/marked/Rel-16/23_series/23084/997233d405f0d4b89ddeb7683e047f66_img.jpg b/marked/Rel-16/23_series/23084/997233d405f0d4b89ddeb7683e047f66_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bb1b06e90ac8c7d76f4e653b5385244543961ce2 --- /dev/null +++ b/marked/Rel-16/23_series/23084/997233d405f0d4b89ddeb7683e047f66_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d4087ddce1fb713256b2cd15768db2188dde1760f7f73ff6fdd86c6150a7907c +size 83694 diff --git a/marked/Rel-16/23_series/23084/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/Rel-16/23_series/23084/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..70c4afc512e1da9583da2e899cff5f2f6c122089 --- /dev/null +++ b/marked/Rel-16/23_series/23084/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:03363b222a3063df770e89fef79b7dcf550e6e20c780fd6d75f4d1818fdb6843 +size 118082 diff --git a/marked/Rel-16/23_series/23084/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg b/marked/Rel-16/23_series/23084/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..50d110a43d870cda8e33938d071600e147757387 --- /dev/null +++ b/marked/Rel-16/23_series/23084/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cc97014abad4448b58f94af707476280a51d4a1403cf43e0db49476121ba0b47 +size 133013 diff --git a/marked/Rel-16/23_series/23084/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg b/marked/Rel-16/23_series/23084/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..69c4f40dade183933d38b6864f16f33ba7982c28 --- /dev/null +++ b/marked/Rel-16/23_series/23084/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ccaa4104b58a605a92dbc37c32362f15a65b18a360c69a14770848dc9e60ea63 +size 131997 diff --git a/marked/Rel-16/23_series/23084/d0abac95583b52a3b35f74a215567334_img.jpg b/marked/Rel-16/23_series/23084/d0abac95583b52a3b35f74a215567334_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..19543c8c6ee4031b12accdf55ce980d90dbd39a4 --- /dev/null +++ b/marked/Rel-16/23_series/23084/d0abac95583b52a3b35f74a215567334_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6ec2fb7c1350b27dddc363fc8e4ba7c9cb40f064fbe28572401375aff489b666 +size 99944 diff --git a/marked/Rel-16/23_series/23084/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/marked/Rel-16/23_series/23084/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7d1f214cf987037df5e44dc7f21ff7ad5cd20632 --- /dev/null +++ b/marked/Rel-16/23_series/23084/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:317ee7c6b4702f4601401595f3bc0e5aa64ec00b81ccc22f0645521abc6bbcf5 +size 131789 diff --git a/marked/Rel-16/23_series/23084/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/Rel-16/23_series/23084/e6df2733626a85205c1db682e6259c46_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f1556c7f54812f2fd62bb35b9a2a2aa62fe152d1 --- /dev/null +++ b/marked/Rel-16/23_series/23084/e6df2733626a85205c1db682e6259c46_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bc0eb8a5c42c55f2fc29fd11385b4fcc433d99e03c27379b43b94c7cb80fefd9 +size 129582 diff --git a/marked/Rel-16/23_series/23084/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg b/marked/Rel-16/23_series/23084/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..be1369cf528227dce98dbdc7b871631e24a6afdf --- /dev/null +++ b/marked/Rel-16/23_series/23084/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ad5b8f76d18b6759396460c93be6861c976903052455174f96d2410c375d8203 +size 143283 diff --git a/marked/Rel-16/23_series/23084/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/marked/Rel-16/23_series/23084/ff0952ef692c9d960ce5f6708bcc9711_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..60c6531c1445d0384b58878860e177a6139d8213 --- /dev/null +++ b/marked/Rel-16/23_series/23084/ff0952ef692c9d960ce5f6708bcc9711_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bc46295f36671c6ba2836f93a60f6a09e57bcf681f687c3540f7a238bc1fbdff +size 106109 diff --git a/marked/Rel-16/23_series/23084/raw.md b/marked/Rel-16/23_series/23084/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..baee2d1929a15a4fa736908a0d8bb7191358ba45 --- /dev/null +++ b/marked/Rel-16/23_series/23084/raw.md @@ -0,0 +1,954 @@ + + + + + + +# Contents + +- Foreword .....4 +- 0 Scope.....5 +- 0.1 References.....5 +- 0.2 Abbreviations .....5 +- 1 Multi Party service (MPTY).....5 +- 1.1 Functions and information flows.....5 +- 1.2 Information stored in the HLR .....28 +- 1.3 State transition model.....28 +- 1.4 Transfer of information from HLR to VLR .....28 +- 1.5 Information stored in the VLR .....28 +- 1.6 Handover .....28 +- 1.7 Simultaneous use of Multi Party operations .....28 +- Annex A: Change history .....29 + +# --- 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. + +# --- 0 Scope + +The present document gives the stage 2 description of the multi party supplementary services. + +Only one multi party supplementary service has been defined, this is the Multi Party (MPTY) service, and is described in clause 1. + +## 0.1 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] 3GPP TR 21.905: "3G Vocabulary". +- [2] 3GPP TS 23.011: "Technical realization of supplementary services - General Aspects". +- [3] 3GPP TS 23.083: "Call Waiting (CW) and Call Hold (HOLD) supplementary services - Stage 2". +- [4] 3GPP TS 23.018: "Basic Call Handling" + +## 0.2 Abbreviations + +In addition to those below, abbreviations used in the present document are listed in 3GPP TR 21.905 [1]. + +| | | +|------|------------------------------------| +| SII2 | Service Interaction Indicators Two | +|------|------------------------------------| + +# --- 1 Multi Party service (MPTY) + +## 1.1 Functions and information flows + +The following Mobile Additional Function has been identified for the Multi Party service: + +###### MAF026 + +Multi Party service related authorizations examination + +The ability of a PLMN component to determine the authorizations relating to Multi Party service. See figure 2.1. + +Location: VLR + +The SDL diagrams for the Multi Party service are shown in figures 1.2 and 1.3. + +The procedure Handle\_MPTY shows the status of the service as perceived by the served mobile subscriber, as well as the status as perceived by any of the other parties. Beside this, the SDL diagrams show the actions to be taken by the network and the information provided by the network to the users. + +Figure 1.x: the procedure Update\_Non\_Speech\_Calls\_Status is defined in 3GPP TS 23.018 [4]. + +The information flow for the MPTY service is shown in figure 1.5. + +In the information flow it is assumed that the served subscriber is a mobile subscriber and that the other parties are all fixed ISDN subscribers. For the purposes of the information flow diagrams it is assumed that there are only two remote parties. Where there are more than two remote parties, signals to any party connected to the MPTY bridge shall be sent to all other parties connected to the MPTY bridge, except where a single remote party is to be selected for a private communication. + +As a consequence of this assumption, after the MPTY is split (to establish a private communication) it contains only one remote party. However, the end state for disconnection of or by that remaining remote party is shown as A-B ACTIVE / MPTY HELD. This is to indicate that the disconnection by a single remote party will not necessarily cause the MPTY call to be released. This will happen only when that remote party is the only remaining party in the MPTY call. + +Party A is the subscriber controlling the MPTY call (served mobile subscriber). Party B is the first remote party called. Party C is the second remote party called. + +Remote parties are disconnected by the generic disconnect/release procedure. Any scenario requiring disconnection of remote parties shown in the SDL diagrams but not explicitly shown in the flow diagrams shall follow the procedure shown in the flow diagrams for similar scenarios. + +Functions to be performed by the fixed ISDN (for example hold authorizations examination) are not shown in the information flow; only the functions to be performed by the PLMN are shown. + +It is assumed that the MPTY bridge is located in the MSC. + +To avoid having two calls on hold at the same time the reception of the retrieve request is supervised by a retriever timer T as defined in 3GPP TS 23.083 [3]. + +Note that while the MPTY is on hold, the remote parties can continue to communicate with each other. + + + +**Process MPTY\_MAF026** + +**384\_11(1)** + +Process in the VLR to check if MPTY is provisioned. + +Signals to/from the left are to/from the MSC. + +``` +graph TD; Start([ ]) --> Idle1([Idle]); Idle1 --> Check[Check MPTY subscription]; Check --> MPTY_Prov{MPTY provisioned}; MPTY_Prov -- No --> Indicator3[Indicator:= MPTY_not_available]; MPTY_Prov -- Yes --> SS_CSI_Prov{SS-CSI provisioned?}; SS_CSI_Prov -- No --> Indicator1[Indicator:= MPTY_available]; SS_CSI_Prov -- Yes --> MPTY_Marked{MPTY marked in CSI?}; MPTY_Marked -- No --> Indicator1; MPTY_Marked -- Yes --> Indicator2[Indicator:= MPTY_available + SS-CSI]; Indicator1 --> ProcessMPTY{Process MPTY}; Indicator2 --> ProcessMPTY; Indicator3 --> ProcessMPTY; ProcessMPTY --> Idle2([Idle]); +``` + +Flowchart for Process MPTY\_MAF026. It starts with an oval, followed by an 'Idle' state. Then a 'Check MPTY subscription' process. A decision 'MPTY provisioned' follows. If 'No', it goes to 'Indicator:= MPTY\_not\_available'. If 'Yes', it goes to another decision 'SS-CSI provisioned?'. If 'No', it goes to 'Indicator:= MPTY\_available'. If 'Yes', it goes to a decision 'MPTY marked in CSI?'. If 'No', it goes to 'Indicator:= MPTY\_available'. If 'Yes', it goes to 'Indicator:= MPTY\_available + SS-CSI'. All three indicator boxes lead to a 'Process MPTY' process, which then leads to an 'Idle' state. + +**Figure 1.1: MAF026 Multi Party service related authorisations examination (VLR)** + + + +### Procedure Handle\_MPTY + +MPTY\_1(16) + +Procedure in the serving MSC to handle an MPTY call. + +Signals to/from the left are to/from the controller (A party); signals to/from the right are to/from the B party unless otherwise stated. + +``` +graph TD; Start([ ]) --> Check_MPTY[Check_MPTY]; Check_MPTY -- Pass --> Connect[Connect A, B and C]; Check_MPTY -- Fail --> Reject{MPTY reject}; Connect --> SetVars["Speech_CallA:=MPTY
Speech_CallB:=Null
MPTY_Remote_Parties:=2"]; SetVars --> Retrieve[Retrieve indication]; Retrieve --> Ind1[Multi party indication]; Ind1 --> Ind2[Multi party indication]; Ind2 -- To C party --> ToC[To C party]; Ind2 --> Ack{MPTY ack}; Ack --> Decision{SS-CSI present?}; Decision -- Yes --> Active([Active_MPTY]); Decision -- No --> Notify[SS Invocation Notify]; Notify -- To gsmSCF --> ToGSM[To gsmSCF]; ToGSM --> Active; Reject --> Fail[Result:= Fail]; Fail --> End((X)) +``` + +Flowchart for Procedure Handle\_MPTY. The process starts with 'Check\_MPTY'. If 'Pass', it proceeds to 'Connect A, B and C', then sets variables (Speech\_CallA:=MPTY, Speech\_CallB:=Null, MPTY\_Remote\_Parties:=2), then 'Retrieve indication', 'Multi party indication', 'Multi party indication' (To C party), 'MPTY ack', and then a decision 'SS-CSI present?'. If 'Yes', it goes to 'Active\_MPTY'. If 'No', it goes to 'SS Invocation Notify' (To gsmSCF) and then to 'Active\_MPTY'. If 'Fail' from 'Check\_MPTY', it goes to 'MPTY reject', then 'Result:= Fail', and ends. + +Figure 1.2 (sheet 1 of 16): Procedure Handle\_MPTY + + + +### Procedure Handle\_MPTY + +MPTY\_2(16) + +Procedure in the serving MSC to handle an MPTY call. + +Signals to/from the left are to/from the controller (A party); +signals to/from the right are to/from all/any remote parties unless otherwise stated. + +``` +graph TD; Start([Active_MPTY]) --> Branch1[Disconnect MPTY]; Start --> Branch2[Disconnect one party e.g. C]; Start --> Branch3[Disconnect e.g. C]; Start --> Branch4[Private communication e.g. F]; Branch1 --> Action1[Disconnect MPTY]; Action1 --> State1["MPTY_Remote_Parties:=0 +Speech_CallA:=Null +Speech_Call_Cnt:=0"]; State1 --> Decision1{MPTY Disconnected}; Decision1 --> Result1[Result:= End]; Result1 --> End1(( )); Branch2 --> Action2[Disconnect C]; Action2 --> State2["MPTY_Remote_Parties:= +MPTY_Remote_Parties - 1"]; State2 --> Decision2{Call C disconnected}; Decision2 -- Yes --> Decision3{Any remaining parties in MPTY?}; Decision3 -- Yes --> Start; Decision3 -- No --> Result2[Result:= End]; Result2 --> End2(( )); Branch3 --> Action3[To all parties except F]; Action3 --> Decision4{Hold indication}; Decision4 --> Decision5{Private communication ack}; Decision5 --> End3([Held_MPTY_and_active_call]); Branch4 --> Action4[Hold MPTY and make specified call active]; Action4 --> State3["MPTY_Remote_Parties:= +MPTY_Remote_Parties - 1"]; State3 --> Action5[Speech_CallB:= Active]; Action5 --> Decision4; +``` + +Flowchart for Procedure Handle\_MPTY. It starts with 'Active\_MPTY' and branches into four options: 'Disconnect MPTY', 'Disconnect one party (e.g. C)', 'Disconnect (e.g. C)', and 'Private communication (e.g. F)'. Each branch leads to specific actions and state changes, eventually leading to 'Result:= End' or back to 'Active\_MPTY'. + +Figure 1.2 (sheet 2 of 16): Procedure Handle\_MPTY + + + +### Procedure Handle\_MPTY + +MPTY\_4(16) + +Procedure in the serving MSC to handle an MPTY call. + +Signals to/from the left are to/from the controller (A party); signals to/from the right are to/from all/any remote parties unless otherwise stated. + +``` +stateDiagram-v2 + [*] --> Held_MPTY + Held_MPTY --> Disconnect_MPTY : Disconnect MPTY + Held_MPTY --> Disconnect_one_party : Disconnect one party (e.g. C) + Held_MPTY --> Disconnect_C : Disconnect (e.g. C) + Held_MPTY --> Retrieve_MPTY : Retrieve MPTY + Held_MPTY --> Hold_indication : Hold indication + Held_MPTY --> Retrieve_indication : Retrieve indication + + Disconnect_MPTY --> Disconnect_MPTY_action : Disconnect MPTY + Disconnect_MPTY_action --> MPTY_Remote_Parties_0 : MPTY_Remote_Parties:=0 +Speech_CallA:=Null +Speech_Call_Cnt:=0 + MPTY_Remote_Parties_0 --> MPTY_Disconnected : MPTY Disconnected + MPTY_Disconnected --> Result_End : Result:= End + Result_End --> [*] + + Disconnect_one_party --> Disconnect_C_action : Disconnect C + Disconnect_C_action --> MPTY_Remote_Parties_minus_1 : MPTY_Remote_Parties:=MPTY_Remote_Parties - 1 + MPTY_Remote_Parties_minus_1 --> Call_C_disconnected : Call C disconnected + Call_C_disconnected --> Any_remaining_parties : Any remaining parties in MPTY? + Any_remaining_parties -- No --> Result_End + Any_remaining_parties -- Yes --> Held_MPTY + + Retrieve_MPTY --> Retrieve_held_MPTY : Retrieve held MPTY + Retrieve_held_MPTY --> Retrieve_indication_state : Retrieve indication + Retrieve_indication_state --> Retrieve_ack : Retrieve ack + Retrieve_ack --> Active_MPTY : Active_MPTY + + Hold_indication --> Hold_indication_state : Hold indication + Retrieve_indication --> Hold_indication_state + Hold_indication_state --> Held_MPTY +``` + +State transition diagram for Procedure Handle\_MPTY. It starts at 'Held\_MPTY' and branches into six paths based on input signals: 'Disconnect MPTY', 'Disconnect one party (e.g. C)', 'Disconnect (e.g. C)', 'Retrieve MPTY', 'Hold indication', and 'Retrieve indication'. The 'Disconnect MPTY' path leads to 'Disconnect MPTY' action, then a state where 'MPTY\_Remote\_Parties:=0', 'Speech\_CallA:=Null', and 'Speech\_Call\_Cnt:=0', then 'MPTY Disconnected' state, then 'Result:= End' action, and finally an end state. The 'Disconnect one party' path leads to 'Disconnect C' action, then a state where 'MPTY\_Remote\_Parties:=MPTY\_Remote\_Parties - 1', then 'Call C disconnected' state, then a decision 'Any remaining parties in MPTY?'. If 'No', it goes to 'Result:= End'. If 'Yes', it goes to 'Held\_MPTY' state. The 'Retrieve MPTY' path leads to 'Retrieve held MPTY' action, then 'Retrieve indication' state, then 'Retrieve ack' state, and finally 'Active\_MPTY' state. The 'Hold indication' and 'Retrieve indication' paths both lead to 'Hold indication' state, which then leads to 'Held\_MPTY' state. + +Figure 1.2 (sheet 4 of 16): Procedure Handle\_MPTY + + + +### Procedure Handle\_MPTY + +MPTY\_5(16) + +Procedure in the serving MSC to handle an MPTY call. + +Signals to/from the left are to/from the controller (A party); +Signals to/from the right are to/from either process OCH\_MSC or process ICH\_MSC. + +``` +graph TD; Held_MPTY([Held_MPTY]) --> Awaiting[Answer waiting call (e.g. F)]; Held_MPTY --> TCH[Speech TCH required]; Awaiting --> Decision{Is there a waiting call?}; Decision -- No --> Reject{Answer waiting call reject}; Reject --> Held_MPTY; Decision -- Yes --> ConnectF[Connect F]; ConnectF --> Cnt1[Speech_Call_Cnt := Speech_Call_Cnt + 1]; Cnt1 --> CallB1[Speech_CallB := Active]; CallB1 --> ActiveCall([Held_MPTY_Active_Call]); TCH --> CallB2[Speech_CallB := Setup]; CallB2 --> AllocateTCH[Allocate TCH]; AllocateTCH --> CallSetup([Held_MPTY_Call_Setup]); CallSetup --> CallEstablished[Call established]; CallSetup --> CallSetupFailed[Call setup failed]; CallEstablished --> Cnt2[Speech_Call_Cnt := Speech_Call_Cnt + 1]; Cnt2 --> CallB3[Speech_CallB := Active]; CallB3 --> ActiveCall; CallSetupFailed --> CallB4[Speech_CallB := Null]; CallB4 --> Held_MPTY; +``` + +Flowchart for Procedure Handle\_MPTY. It starts with 'Held\_MPTY' and branches into 'Answer waiting call (e.g. F)' and 'Speech TCH required'. The 'Answer waiting call' path leads to a decision 'Is there a waiting call?'. If 'No', it goes to 'Answer waiting call reject' and back to 'Held\_MPTY'. If 'Yes', it goes to 'Connect F', then 'Speech\_Call\_Cnt := Speech\_Call\_Cnt + 1', then 'Speech\_CallB := Active', and finally to 'Held\_MPTY\_Active\_Call'. The 'Speech TCH required' path leads to 'Speech\_CallB := Setup', then 'Allocate TCH', and finally to 'Held\_MPTY\_Call\_Setup'. From 'Held\_MPTY\_Call\_Setup', it branches into 'Call established' and 'Call setup failed'. The 'Call established' path leads to 'Speech\_Call\_Cnt := Speech\_Call\_Cnt + 1', then 'Speech\_CallB := Active', and finally to 'Held\_MPTY\_Active\_Call'. The 'Call setup failed' path leads to 'Speech\_CallB := Null' and finally back to 'Held\_MPTY'. + +Figure 1.2 (sheet 5 of 16): Procedure Handle\_MPTY + + + +### Procedure Handle\_MPTY + +MPTY\_6(16) + +Procedure in the serving MSC to handle an MPTY call. + +Signals to/from the left are to/from the controller (A party); +signals to/from the right are to/from all/any remote parties unless otherwise stated. + +``` +graph TD; Start([Held_MPTY_Active_Call]) --> Branch1[Disconnect MPTY]; Start --> Branch2[Disconnect one held party (e.g. C)]; Start --> Branch3[Disconnect active call (e.g. F)]; Branch1 --> D1[Disconnect MPTY]; D1 --> M1{MPTY disconnected}; M1 --> End1(( )); Branch2 --> D2[Disconnect C]; D2 --> M2{Call C disconnect}; M2 --> Calc1[MPTY_Remote_Parties := MPTY_Remote_Parties - 1]; Calc1 --> Decision1{Any remaining parties in MPTY?}; Decision1 -- No --> End1; Decision1 -- Yes --> End2([Held_MPTY_Active_Call]); Branch3 --> D3[Disconnect F]; D3 --> M3{Call F disconnected}; M3 --> Calc2[Speech_Call_Cnt := Speech_Call_Cnt - 1]; Calc2 --> Calc3[Speech_CallB := Null]; Calc3 --> End3([Held_MPTY]); End1 --> Calc4[MPTY_Remote_Parties := 0; Speech_CallA := Active; Speech_CallB := Null; Speech_Call_Cnt := 1]; Calc4 --> End4[Result := End_Active]; End4 --> End5(( )); +``` + +Flowchart for Procedure Handle\_MPTY. It starts with 'Held\_MPTY\_Active\_Call' and branches into three main paths: 1) Disconnect MPTY, 2) Disconnect one held party (e.g. C), and 3) Disconnect active call (e.g. F). Each path leads to specific disconnection steps and state updates, eventually returning to 'Held\_MPTY\_Active\_Call' or ending with 'End\_Active'. + +Figure 1.2 (sheet 6 of 16): Procedure Handle\_MPTY + + + +### Procedure Handle\_MPTY + +MPTY\_7(16) + +Procedure in the serving MSC to handle an MPTY call. + +Signals to/from the left are to/from the controller (A party); signals to/from the right are to/from all/any remote parties unless otherwise stated. + +``` +graph TD; Start([Held_MPTY_Active_Call]) --> AddParty[Add party (e.g. F)]; Start --> HoldInd[Hold indication]; Start --> RetInd[Retrieve indication]; Start --> HoldActive[Hold active call]; AddParty --> Decision{Another party permitted?}; Decision -- Yes --> ConnectF[Connect F to MPTY]; ConnectF --> MPTY_Remote_Parties["MPTY_Remote_Parties := MPTY_Remote_Parties + 1"]; MPTY_Remote_Parties --> Speech_CallB["Speech_CallB := Null"]; Speech_CallB --> MPTY_Indication[MPTY indication]; MPTY_Indication --> RetrieveIndication[Retrieve indication]; RetrieveIndication --> AddPartyAck[Add party ack]; AddPartyAck --> ActiveMPTY([Active_MPTY]); Decision -- No --> AddPartyReject[Add party reject]; AddPartyReject --> HeldMPTYActiveCall([Held_MPTY_Active_Call]); HoldInd --> HoldIndication[Hold indication]; HoldIndication --> RetrieveIndication; RetInd --> RetrieveIndication; HoldActive --> StartT[Start T]; StartT --> HeldMPTYActiveCallTimedSwap([Held_MPTY_Active_Call_Timed_Swap]); +``` + +Flowchart for Procedure Handle\_MPTY. It starts with Held\_MPTY\_Active\_Call. The first path (Add party) leads to a decision 'Another party permitted?'. If 'Yes', it proceeds through 'Connect F to MPTY', 'MPTY\_Remote\_Parties := MPTY\_Remote\_Parties + 1', 'Speech\_CallB := Null', 'MPTY indication', and 'Retrieve indication' (labeled 'To F party only') to 'Add party ack' and 'Active\_MPTY'. If 'No', it goes to 'Add party reject' and 'Held\_MPTY\_Active\_Call'. The second path (Hold indication) leads to 'Hold indication' and then to 'Retrieve indication'. The third path (Retrieve indication) leads directly to 'Retrieve indication'. The fourth path (Hold active call) leads to 'Start T' and 'Held\_MPTY\_Active\_Call\_Timed\_Swap'. + +Figure 1.2 (sheet 7 of 16): Procedure Handle\_MPTY + + + +### Procedure Handle\_MPTY + +MPTY\_8(16) + +Procedure in the serving MSC to handle an MPTY call. + +Signals to/from the left are to/from the controller (A party); +signals to/from the right are to/from all/any remote parties in the MPTY unless otherwise stated. + +``` +sequenceDiagram + participant T as T expires + participant R1 as Retrieve request + participant R2 as Retrieve request + Note left of T: Procedure in the serving MSC to handle an MPTY call. + Note right of R2: Signals to/from the left are to/from the controller (A party); signals to/from the right are to/from all/any remote parties in the MPTY unless otherwise stated. + + T-->R1: Internal signal + R1-->R2: For single call + R2-->R1: For MPTY + + T-->T: T expires + T-->H1: Hold reject + H1-->H1: Held_MPTY_Active_call + + R1-->S1: Stop T + S1-->H2: Hold reject + H2-->R3: Retrieve reject + R3-->H2: Held_MPTY_Active_Call + + R2-->S2: Stop T + S2-->H3: Hold single call + H3-->S3: Speech_CallB:=Held + S3-->H4: Hold indication + Note right of H4: To the single call only + H4-->H5: Hold ack + H5-->R4: Retrieve MPTY + R4-->H6: Retrieve indication + H6-->H7: Retrieve ack + H7-->H5: Active_MPTY_Held_call +``` + +Sequence diagram for Procedure Handle\_MPTY. The diagram shows three lifelines: T expires, Retrieve request, and Retrieve request. The first lifeline (T expires) leads to a 'Hold reject' and then to 'Held\_MPTY\_Active\_call'. The second lifeline (Retrieve request) is labeled 'For single call', leads to 'Stop T', then 'Hold reject', 'Retrieve reject', and finally 'Held\_MPTY\_Active\_Call'. The third lifeline (Retrieve request) is labeled 'For MPTY', leads to 'Stop T', 'Hold single call', 'Speech\_CallB:=Held', 'Hold indication' (labeled 'To the single call only'), 'Hold ack', 'Retrieve MPTY', 'Retrieve indication', 'Retrieve ack', and finally 'Active\_MPTY\_Held\_call'. A note at the top left explains the procedure is in the serving MSC. A note at the top right explains signal directions. + +Figure 1.2 (sheet 8 of 16): Procedure Handle\_MPTY + + + +### Procedure Handle\_MPTY + +MPTY\_9(16) + +Procedure in the serving MSC to handle an MPTY call. + +Signals to/from the left are to/from the controller (A party); +signals to/from the right are to/from all/any remote parties in the MPTY unless otherwise stated. + +``` +graph TD; Start([Held_MPTY_Active_Call_Timed_Swap]) --> Branch1(( )); Branch1 --> D1[Disconnect e.g. F]; D1 --> StopT1[Stop T]; StopT1 --> D2[Disconnect F]; D2 --> C1{Call F disconnected}; C1 --> S1[Speech_Call_Cnt := Speech_Call_Cnt - 1]; S1 --> S2[Speech_CallB := Null]; S2 --> H1{Hold reject}; H1 --> End1([Held_MPTY]); Branch1 --> D3[Disconnect e.g. C]; D3 --> D4[Disconnect C]; D4 --> M1[MPTY_Remote_Parties := MPTY_Remote_Parties - 1]; M1 --> C2{Call disconnected}; C2 --> Q1{Any remaining parties in MPTY?}; Q1 -- No --> StopT2[Stop T]; StopT2 --> H2{Hold reject}; H2 --> S3[Speech_CallA := Active +Speech_CallB := Null +Speech_Call_Cnt := 1]; S3 --> R1[Result := End_Active]; R1 --> End2((X)); Q1 -- Yes --> Branch1; +``` + +Flowchart for Procedure Handle\_MPTY. It starts with 'Held\_MPTY\_Active\_Call\_Timed\_Swap' and branches into two main paths. The left path is for a single call, involving disconnecting F, stopping timer T, disconnecting F, checking if F is disconnected, decrementing speech call count, nullifying speech call B, and holding reject. The right path is for multiple parties, involving disconnecting C, updating remote party count, checking if disconnected, then checking if any remaining parties exist. If no remaining parties, it stops timer T, holds reject, sets speech call A to active, B to null, and count to 1, then ends active. If remaining parties exist, it loops back to the start. Both paths end at 'Held\_MPTY' or 'Held\_MPTY\_Active\_Call\_Timed\_Swap'. + +Figure 1.2 (sheet 9 of 16): Procedure Handle\_MPTY + + + +### Procedure Handle\_MPTY + +MPTY\_10(16) + +Procedure in the serving MSC to handle an MPTY call. + +Signals to/from the left are to/from the controller (A party); signals to/from the right are to/from all/any remote parties unless otherwise stated. + +``` +graph TD; Start([Active_MPTY_Held_Call]) --> D1{Disconnect MPTY}; Start --> D2{Disconnect one party (e.g. C)}; Start --> D3{Disconnect (e.g. C)}; Start --> D4{Disconnect (e.g. F)}; Start --> D5{Disconnect single call (e.g. F)}; D1 --> DM1[Disconnect MPTY]; DM1 --> MD1{MPTY disconnected}; D2 --> DC1[Disconnect C]; DC1 --> CD1{Call C disconnected}; CD1 --> MR1[MPTY_Remote_Parties := MPTY_Remote_Parties - 1]; MR1 --> ARP{Any remaining parties in MPTY?}; ARP -- No --> J1(( )); ARP -- Yes --> AMHC1([Active_MPTY_Held_Call]); D3 --> J1; D4 --> FSC[From the single call]; D5 --> DF1[Disconnect F]; DF1 --> CF1{Call F disconnected}; CF1 --> SC1[Speech_Call_Cnt := Speech_Call_Cnt - 1]; SC1 --> SCB1[Speech_CallB := Null]; SCB1 --> AM1([Active_MPTY]); J1 --> J2[ ]; J2 --> MR2[MPTY_Remote_Parties:=0; Speech_CallA:=Held; Speech_CallB:=Null; Speech_Call_Cnt:=1]; MR2 --> J3[ ]; J3 --> RH1[Result:= End_Held]; RH1 --> End((X)); +``` + +Flowchart for Procedure Handle\_MPTY. It starts with 'Active\_MPTY\_Held\_Call' and branches into 'Disconnect MPTY', 'Disconnect one party (e.g. C)', 'Disconnect (e.g. C)', 'Disconnect (e.g. F)', and 'Disconnect single call (e.g. F)'. Each branch leads to specific disconnect actions and state updates, eventually leading to 'Result:= End\_Held' and an end connector. + +Figure 1.2 (sheet 10 of 16): Procedure Handle\_MPTY + + + +### Procedure Handle\_MPTY + +MPTY\_11(16) + +Procedure in the serving MSC to handle an MPTY call. + +Signals to/from the left are to/from the controller (A party); +signals to/from the right are to/from all/any remote parties unless otherwise stated. + +``` + + graph TD + State1([Active_MPTY_Held_Call]) + + %% Branch 1: Add Party + State1 --> In1[/Add party +(e.g. F)/] + In1 --> Dec1{Another party +permitted?} + Dec1 -- Yes --> Task1["MPTY_Remote_Parties := +MPTY_Remote_Parties + 1"] + Task1 --> Task2["Speech_CallB := +Null"] + Task2 --> Task3["Connect F + +``` + +*To F party only* + +SDL Flowchart for Procedure Handle\_MPTY starting from state Active\_MPTY\_Held\_Call. + +**Figure 1.2 (sheet 11 of 16): Procedure Handle\_MPTY** + + + +### Procedure Handle\_MPTY + +MPTY\_12(16) + +Procedure in the serving MSC to handle an MPTY call. + +Signals to/from the left are to/from the controller (A party); +signals to/from the right are to/from all/any remote parties in the MPTY unless otherwise stated. + +``` +graph TD; Start([Active_MPTY_Held_Call_Timed_Swap]) --> T_expire[T expires]; Start --> Req_MPTY[Retrieve request]; Start --> Req_Single[Retrieve request]; T_expire --> Internal[Internal signal]; Req_MPTY --> For_MPTY[For MPTY]; Req_Single --> For_Single[For single call]; T_expire --> Hold_Reject_1{Hold reject}; Req_MPTY --> Stop_T_1[Stop T]; Req_Single --> Stop_T_2[Stop T]; Stop_T_1 --> Hold_Reject_2{Hold reject}; Stop_T_2 --> Hold_MPTY[Hold MPTY]; Hold_Reject_1 --> End_1([Active_MPTY_Held_Call]); Hold_Reject_2 --> End_2([Active_MPTY_Held_Call]); Hold_MPTY --> Hold_Indication{Hold indication}; Hold_Indication --> Hold_Ack{Hold ack}; Hold_Ack --> Retrieve_Single[Retrieve single call]; Retrieve_Single --> Speech_CallB[Speech_CallB:=Active]; Speech_CallB --> Retrieve_Indication{Retrieve indication}; Retrieve_Indication --> To_Single[To the single call only]; Retrieve_Indication --> Retrieve_Ack{Retrieve ack}; Retrieve_Ack --> End_3([Held_MPTY_Active_Call]); +``` + +Flowchart for Procedure Handle\_MPTY. It starts with 'Active\_MPTY\_Held\_Call\_Timed\_Swap' and branches into three paths: 1) 'T expires' (internal signal) leading to 'Hold reject' and back to 'Active\_MPTY\_Held\_Call'; 2) 'Retrieve request' (for MPTY) leading to 'Stop T', 'Hold reject', and back to 'Active\_MPTY\_Held\_Call'; 3) 'Retrieve request' (for single call) leading to 'Stop T', 'Hold MPTY', 'Hold indication', 'Hold ack', 'Retrieve single call', 'Speech\_CallB:=Active', 'Retrieve indication' (to the single call only), 'Retrieve ack', and finally 'Held\_MPTY\_Active\_Call'. + +Figure 1.2 (sheet 12 of 16): Procedure Handle\_MPTY + + + +### Procedure Handle\_MPTY + +MPTY\_13(16) + +Procedure in the serving MSC to handle an MPTY call. + +Signals to/from the left are to/from the controller (A party); +signals to/from the right are to/from all/any remote parties in the MPTY unless otherwise stated. + +``` + + graph TD + Start([Active_MPTY_ +Held_Call_ +Timed_Swap]) + + %% Left Branch + Start --> In1{Disconnect +single call +(e.g. F)} + Note1[From the single call] -.-> In1 + In1 --> Task1[Stop T] + Task1 --> Task2[Disconnect +F] + Task2 --> In2{Call F +disconnected} + In2 --> Task3["Speech_Call_Cnt:= +Speech_Call_Cnt - 1"] + Task3 --> Task4["Speech_CallB:= +Null"] + Task4 --> In3{Hold +reject} + In3 --> EndState1([Active_MPTY]) + + %% Right Branch + Start --> In4{Disconnect +(e.g. C)} + In4 --> Task5[Disconnect +C] + Task5 --> Task6["MPTY_Remote_Parties:= +MPTY_Remote_Parties - 1"] + Task6 --> In5{Call +disconnected} + In5 --> Dec1{Any +remaining parties +in MPTY?} + + Dec1 -- Yes --> EndState2([Active_MPTY_ +Held_Call_ +Timed_Swap]) + Dec1 -- No --> Task7[Stop T] + Task7 --> In6{Hold +reject} + In6 --> Task8["Speech_CallA:=Held +Speech_CallB:=Null +Speech_Call_Cnt:=1"] + Task8 --> Task9["Result:= +End_Held"] + Task9 --> EndNode((X)) + +``` + +Flowchart of Procedure Handle\_MPTY sheet 13. It describes the logic for disconnecting calls during an active MPTY held call timed swap state. One path handles disconnecting the single call (F), leading to an Active\_MPTY state. The other path handles disconnecting a remote party (C), checking if any parties remain, and either returning to the initial state or ending the held state if no parties remain. + +**Figure 1.2 (sheet 13 of 16): Procedure Handle\_MPTY** + + + +### Macrodefinition Check\_MPTY + +Chk\_MPTY(1) + +``` +graph TD; Start([ ]) --> Cond1{Conditions met?}; Cond1 -- No --> Cond2{Conference Treatment Indicator set to reject conference request (for either ongoing call)?}; Cond2 -- Yes --> Fail((Fail)); Cond2 -- No --> Sub[Check MPTY subscription]; Cond1 -- Yes --> Cond3{Conference Treatment Indicator present in SII2 (for either ongoing call)?}; Cond3 -- No --> Sub; Sub --> Wait([Wait_For_MPTY_Status_Reply]); Wait --> Process[/Process MPTY/]; Process --> Cond4{MPTY active?}; Cond4 -- No --> Fail; Cond4 -- Yes --> Cond5{Request accepted?}; Cond5 -- No --> Fail; Cond5 -- Yes --> Pass((Pass)); Process --> IntRelease[/Int_Release_Call/]; IntRelease --> gsmSSF[gsmSSF]; Process --> Release[/Release/]; Release --> distant[distant exchange]; Process --> ReleaseTrans[/Release transaction/]; ReleaseTrans --> BSS[BSS]; +``` + +Macro in the serving MSC to check if an MPTY call can go ahead. + +Signals to/from the right are to/from the VLR. + +Conference Treatment Indicator present in SII2 (for either ongoing call)? + +Conference Treatment Indicator set to reject conference request (for either ongoing call)? + +Check MPTY subscription + +Wait\_For\_MPTY\_Status\_Reply + +Process MPTY + +Int\_Release\_Call + +Release + +Release transaction + +From gsmSSF + +From distant exchange + +From BSS + +Conditions met? + +MPTY active? + +Request accepted? + +Fail + +Pass + +Flowchart for Macro Check\_MPTY. It starts with a connector, then checks if conditions are met. If no, it checks if the Conference Treatment Indicator is set to reject. If yes, it fails. If no, it checks the MPTY subscription. If conditions are met, it checks if the Conference Treatment Indicator is present in SII2. If no, it checks the MPTY subscription. If yes, it processes MPTY, then checks if MPTY is active. If no, it fails. If yes, it checks if the request is accepted. If no, it fails. If yes, it passes. There are also release call options from gsmSSF, distant exchange, and BSS. + +Figure 1.3: Macro Check\_MPTY + + + +### Macrodefinition Setup\_New\_Data\_Call\_MPTY + +SNDC\_1(1) + +Macro to set up a new data call while a MPTY call is ongoing + +Signals to/from the left are to/from process ICH\_MSC or process OCH\_MSC + +``` + +graph TD + Start([ ]) --> Decision{Max number of data calls reached?} + Decision -- Yes --> TCH[TCH already allocated] + TCH --> Fail1((Fail)) + Decision -- No --> Allocate[Allocate TCH] + Allocate --> Setup[Non_Speech_Calls:=Setup] + Setup --> Pending(MPTY_Data_Call_Setup_Pending) + Pending --> CallEstablished{{Call established}} + Pending --> CallSetupFailed{{Call setup failed}} + CallEstablished --> Active[Non_Speech_Calls:=Active] + Active --> Cnt[Non_Speech_Call_Cnt:= +Non_Speech_Call_Cnt+1] + Cnt --> Pass((Pass)) + CallSetupFailed --> Update[[Update_Non_Speech_Calls_Status]] + Update -.- Note[See 3GPP TS 23.018] + Update --> Fail2((Fail)) + +``` + +Flowchart for Setup\_New\_Data\_Call\_MPTY macro. It starts with a decision 'Max number of data calls reached?'. If 'Yes', it goes to 'TCH already allocated' and then 'Fail'. If 'No', it goes to 'Allocate TCH', then 'Non\_Speech\_Calls:=Setup', then 'MPTY\_Data\_Call\_Setup\_Pending'. From there, it branches into 'Call established' (leading to 'Non\_Speech\_Calls:=Active', 'Non\_Speech\_Call\_Cnt:=Non\_Speech\_Call\_Cnt+1', and 'Pass') and 'Call setup failed' (leading to 'Update\_Non\_Speech\_Calls\_Status' with a note 'See 3GPP TS 23.018' and then 'Fail'). + +Figure 1.4: Setup\_New\_Data\_Call\_MPTY + + + +``` + +sequenceDiagram + participant MSa + participant MSCa + participant VLRa + participant HLRa + participant LEb + participant TEb + participant LEc + participant TEc + + Note over MSa, TEc: A-B HELD / A-C ACTIVE + Note right of MSa: Subscriber A wants to initiate a multi party conversation + MSa->>MSCa: build MPTY request + MSCa->>VLRa: info req + Note right of VLRa: MAF 026 + VLRa-->>MSCa: info ack + MSCa-->>MSa: OR1 :N build MPTY reject + + Note over MSa, TEc: A-B HELD / A-C ACTIVE + Note right of MSCa: OR1 :Y + MSCa->>VLRa: connect bridge + VLRa->>LEb: notification (retrieval) + LEb->>TEb: notification (retrieval) + VLRa->>LEb: notification (multi party) + LEb->>TEb: notification (multi party) + VLRa->>LEc: notification (multi party) + LEc->>TEc: notification (multi party) + MSa->>MSCa: build MPTY acknowledge + + Note over MSa, TEc: ACTIVE MULTI PARTY CONVERSATION + + Note over MSa, TEc: ACTIVE MULTI PARTY CONVERSATION + Note right of MSa: Subscriber A wants to terminate the multi party call + MSa->>MSCa: disconnect B + MSCa->>LEb: disconnect + LEb->>TEb: disconnect + MSa->>MSCa: disconnect C + TEb-->>LEb: release + LEb-->>VLRa: release confirmation + VLRa->>HLRa: disconnect + HLRa->>LEc: disconnect + LEc->>TEc: disconnect + MSa-->>MSCa: release B + TEc-->>LEc: release + LEc-->>HLRa: release confirmation + MSa-->>MSCa: release C + + Note over MSa, TEc: IDLE + +``` + +Sequence diagram showing information flow for Multi Party service. Lifelines: MSa, MSCa, VLRa, HLRa, LEb, TEb, LEc, TEc. + +OR1: Multi party call acceptable + Y: Yes N: No + +Figure 1.5 (sheet 1 of 7): Information flow for Multi Party service + + + +The diagram illustrates four scenarios of information flow for a Multi Party service across eight lifelines: MSa, MSCa, VLRA, HLRA, LEb, TEb, LEc, and TEc. Each scenario begins and ends with the state 'ACTIVE MULTI PARTY CONVERSATION'. + +- Scenario 1: Subscriber A wants to disconnect one remote party (e.g. C)** + - MSa sends a 'disconnect' message to MSCa. + - MSCa sends a 'disconnect' message to LEc. + - LEc sends a 'disconnect' message to TEc. + - TEc sends a 'release' message back to LEc. + - LEc sends a 'release confirmation' message back to HLRA. + - HLRA sends a 'release' message back to MSCa. + - MSCa sends a 'release' message back to MSa. +- Scenario 2: One remote party (e.g. C) wants to disconnect** + - LEc sends a 'disconnect' message to TEc. + - TEc sends a 'disconnect' message back to LEc. + - LEc sends a 'release' message to HLRA. + - HLRA sends a 'release confirmation' message back to MSCa. + - MSCa sends a 'release' message to MSa. + - MSa sends a 'disconnect' message back to MSCa. +- Scenario 3: One remote party (e.g. B) wants to hold** + - LEb sends a 'hold request' message to HLRA. + - HLRA sends a 'notification (hold)' message to MSCa. + - MSCa sends a 'notification (hold)' message back to MSa. + - HLRA sends a 'hold confirmation' message back to LEb. +- Scenario 4: One remote party (e.g. B) wants to retrieve the held call** + - LEb sends a 'retrieve request' message to HLRA. + - HLRA sends a 'notification (retrieval)' message to MSCa. + - MSCa sends a 'notification (retrieval)' message back to MSa. + - HLRA sends a 'retrieve confirmation' message back to LEb. + +Sequence diagrams showing information flow for Multi Party service. The diagram includes four scenarios: 1. Subscriber A wants to disconnect one remote party (e.g. C). 2. One remote party (e.g. C) wants to disconnect. 3. One remote party (e.g. B) wants to hold. 4. One remote party (e.g. B) wants to retrieve the held call. Lifelines involved are MSa, MSCa, VLRA, HLRA, LEb, TEb, LEc, and TEc. + +Figure 1.5 (sheet 2 of 7): Information flow for Multi Party service + + + +**ACTIVE MULTI PARTY CONVERSATION** + Subscriber A wants to hold entire multi party conversation + +MSa → MSCa: hold request + MSCa → MSa: hold bridge + MSCa → VLRA: notification (hold) + MSCa → HLRA: notification (hold) + MSCa → LEB: notification (hold) + MSCa → TEB: notification (hold) + MSCa → LEC: notification (hold) + MSCa → TEC: notification (hold) + +**HELD MULTI PARTY CONVERSATION** + +Subscriber A wants to retrieve the held multi party conversation + +MSa → MSCa: retrieve request + MSCa → MSa: retrieve bridge + MSCa → VLRA: notification (retrieval) + MSCa → HLRA: notification (retrieval) + MSCa → LEB: notification (retrieval) + MSCa → TEB: notification (retrieval) + MSCa → LEC: notification (retrieval) + MSCa → TEC: notification (retrieval) + +**ACTIVE MULTI PARTY CONVERSATION** + +Subscriber A wants to establish a private communication with one party (e.g. B) + +MSa → MSCa: PrivComm request + MSCa → MSa: hold bridge + MSCa → VLRA: notification (hold) + MSCa → HLRA: notification (hold) + MSCa → LEB: notification (hold) + MSCa → TEB: notification (hold) + MSCa → LEC: notification (hold) + MSCa → TEC: notification (hold) + +**A-B ACTIVE / MPTY HELD** + +Sequence diagrams showing information flow for Multi Party service. The diagram is divided into three parts: 1. Holding a conversation: Subscriber A sends a 'hold request' to MSCa, which responds with 'hold bridge'. MSCa then sends 'notification (hold)' to VLRA, HLRA, LEB, TEB, LEC, and TEC. 2. Retrieving a conversation: Subscriber A sends a 'retrieve request' to MSCa, which responds with 'retrieve bridge'. MSCa then sends 'notification (retrieval)' to VLRA, HLRA, LEB, TEB, LEC, and TEC. 3. Establishing a private communication: Subscriber A sends a 'PrivComm request' to MSCa, which responds with 'hold bridge'. MSCa then sends 'notification (hold)' to VLRA, HLRA, LEB, TEB, LEC, and TEC. The final state is 'A-B ACTIVE / MPTY HELD'. + +Figure 1.5 (sheet 3 of 7): Information flow for Multi Party service + + + +The diagram illustrates three scenarios for a Multi Party service using sequence diagrams. The lifelines involved are MSa, MSCa, VLRA, HLRA, LEb, TEb, LEc, and TEc. + +**Scenario 1: Subscriber A wants to disconnect entire multi party conversation** + +- The process starts in the **HELD MULTI PARTY CONVERSATION** state. +- MSa sends a **disconnect** message to MSCa. +- MSCa sends a **disconnect** message to VLRA. +- VLRA sends a **disconnect** message to HLRA. +- HLRA sends a **disconnect** message to LEb. +- LEb sends a **disconnect** message to TEb. +- TEb sends a **release** message to LEb. +- LEb sends a **release confirmation** message to HLRA. +- HLRA sends a **disconnect** message to LEc. +- LEc sends a **disconnect** message to TEc. +- TEc sends a **release** message to LEc. +- LEc sends a **release confirmation** message to HLRA. +- HLRA sends a **release bridge** message to MSCa. +- MSCa sends a **release C** message to MSa. +- The process ends in the **IDLE** state. + +**Scenario 2: One remote party (e.g. B) wants to disconnect** + +- The process starts in the **HELD MULTI PARTY CONVERSATION** state. +- LEb sends a **disconnect** message to TEb. +- TEb sends a **disconnect** message to LEb. +- LEb sends a **release** message to TEb. +- TEb sends a **release** message to LEb. +- LEb sends a **release confirmation** message to HLRA. +- HLRA sends a **disconnect** message to VLRA. +- VLRA sends a **disconnect** message to MSCa. +- MSCa sends a **disconnect** message to MSa. +- MSa sends a **release** message to MSCa. +- MSCa sends a **release** message to MSa. +- The process ends in the **HELD MULTI PARTY CONVERSATION** state. + +**Scenario 3: One remote party (e.g. B) wants to hold** + +- The process starts in the **HELD MULTI PARTY CONVERSATION** state. +- LEb sends a **hold request** message to TEb. +- TEb sends a **hold request** message to LEb. +- LEb sends a **hold confirmation** message to TEb. +- TEb sends a **hold confirmation** message to LEb. +- LEb sends a **notification** message to HLRA. +- HLRA sends a **notification** message to VLRA. +- VLRA sends a **notification** message to MSCa. +- MSCa sends a **notification** message to MSa. +- MSa sends a **(hold)** message to MSCa. +- MSCa sends a **(hold)** message to MSa. +- The process ends in the **HELD MULTI PARTY CONVERSATION** state. + +Sequence diagrams showing information flow for Multi Party service. The diagram is divided into three parts: 1. Subscriber A wants to disconnect entire multi party conversation. 2. One remote party (e.g. B) wants to disconnect. 3. One remote party (e.g. B) wants to hold. Lifelines include MSa, MSCa, VLRA, HLRA, LEb, TEb, LEc, and TEc. + +Figure 1.5 (sheet 4 of 7): Information flow for Multi Party service + + + +The diagram illustrates four sequence diagrams for Multi Party service information flow: + +- HELD MULTI PARTY CONVERSATION**: One remote party (e.g. B) wants to retrieve the held call. + - LEb sends a **retrieve request** to TEb. + - TEb sends a **retrieve** message to HLRA. + - HLRA sends a **notification (retrieval)** to MSCa. + - MSCa sends a **notification (retrieval)** to MSa. + - LEb receives a **confirmation** from TEb. +- A-B ACTIVE / MPTY HELD**: Subscriber A wants to terminate the multi party call. + - MSa sends a **disconnect** to MSCa. + - MSCa sends a **disconnect** to VLRA. + - VLRA sends a **release confirmation** to MSCa. + - MSCa sends a **release** to MSa. + - MSCa sends a **release bridge** to VLRA. + - VLRA sends a **disconnect** to LEc. + - LEc sends a **release** to TEc. +- A-B ACTIVE / MPTY HELD**: One remote party (e.g. C) wants to disconnect. + - LEc sends a **disconnect** to VLRA. + - VLRA sends a **disconnect** to MSCa. + - MSCa sends a **disconnect** to MSa. + - VLRA sends a **release confirmation** to MSCa. + - MSCa sends a **release** to MSa. + - VLRA sends a **release** to LEc. +- A-B ACTIVE / MPTY HELD**: Active remote party (B) wants to disconnect. + - LEb sends a **disconnect** to VLRA. + - VLRA sends a **disconnect** to MSCa. + - MSCa sends a **disconnect** to MSa. + - VLRA sends a **release confirmation** to LEb. + - LEb sends a **release** to TEb. + +Sequence diagrams showing information flow for Multi Party service. The diagram includes four scenarios: 1. Retrieval of a held call. 2. Termination of a multi-party call by the initiator. 3. Disconnection of a remote party. 4. Disconnection of an active remote party. Lifelines include MSa, MSCa, VLRA, HLRA, LEb, TEb, LEc, and TEc. + +Figure 1.5 (sheet 5 of 7): Information flow for Multi Party service + + + +``` + +sequenceDiagram + participant MSa + participant MSCa + participant VLRA + participant HLRA + participant LEb + participant TEb + participant LEc + participant TEc + + Note left of MSa: A-B ACTIVE / MPTY HELD +Subscriber A wants to add active call (A-B) to multi party call + MSa->>MSCa: build MPTY request + MSCa-->>MSa: build MPTY :N +reject + Note left of MSa: A-B ACTIVE / MPTY HELD + MSCa-->>VLRA: OR2 :Y +notification (multi party) + VLRA->>LEb: notification (multi party) + VLRA->>LEc: notification (retrieved) + VLRA->>LEc: notification (multi party) + Note left of MSa: build MPTY acknowledge + Note left of MSa: ACTIVE MULTI PARTY CONVERSATION + +``` + +Sequence diagram for adding an active call to a multi-party call. Lifelines: MSa, MSCa, VLRA, HLRA, LEb, TEb, LEc, TEc. The process involves MSa sending a build MPTY request to MSCa, MSCa checking OR2:N, and then sending notifications to VLRA, LEb, and LEc. VLRA sends notifications to TEb and TEc. The state transitions from A-B ACTIVE / MPTY HELD to ACTIVE MULTI PARTY CONVERSATION. + +OR2: Extra remote party allowed within maximum number? +Y: Yes N: No + +Figure 1.5 (sheet 6 of 7): Information flow for Multi Party service + + + +``` + +sequenceDiagram + participant MSa + participant MSCa + participant VLRA + participant HLRA + participant LEb + participant TEb + participant LEc + participant TEc + + Note left of MSa: A-B ACTIVE / MPTY HELD +One remote party (e.g. B) wants to hold + VLRA->>LEb: notification (hold) + LEb->>TEb: hold request + TEb-->>LEb: hold confirmation + Note left of MSa: A-B ACTIVE / MPTY HELD + + Note left of MSa: A-B ACTIVE / MPTY HELD +One remote party (e.g. B) wants to retrieve the held call + VLRA->>LEb: notification (retrieval) + LEb->>TEb: retrieve request + TEb-->>LEb: retrieve +confirmation + Note left of MSa: A-B ACTIVE / MPTY HELD + + Note left of MSa: A-B ACTIVE / MPTY HELD +Served mobile subscriber wishes to alternate between active call and held MPTY + MSa->>MSCa: hold request for B start T + Note left of MSa: A-B (ACTIVE, HOLD REQ) / MPTY HELD + MSa->>MSCa: retrieve req for MPTY stop T + MSCa-->>VLRA: notification (hold) + VLRA->>LEb: notification (hold) + VLRA->>LEc: notification (retrieval) + Note left of MSa: MPTY ACTIVE / A-B HELD + +``` + +Sequence diagram for holding and retrieving a remote party. Lifelines: MSa, MSCa, VLRA, HLRA, LEb, TEb, LEc, TEc. The diagram shows three scenarios: 1) A remote party (B) wants to hold, 2) A remote party (B) wants to retrieve the held call, 3) The served mobile subscriber wishes to alternate between active call and held MPTY. The state transitions from A-B ACTIVE / MPTY HELD to A-B (ACTIVE, HOLD REQ) / MPTY HELD and finally to MPTY ACTIVE / A-B HELD. + +Figure 1.5 (sheet 7 of 7): Information flow for Multi Party service + +## 1.2 Information stored in the HLR + +The following logical states are applicable for MPTY (refer to TS 23.011 for an explanation of the notation): + +| Provisioning State | Registration State | Activation State | HLR Induction State | +|---------------------------|---------------------------|-------------------------|----------------------------| +| (Not Provisioned, | Not Applicable, | Not Active, | Not Induced) | +| (Provisioned, | Not Applicable, | Active and Operative, | Not Induced) | + +The HLR shall store the logical state of MPTY (which shall be one of the valid states listed above) on a per subscriber basis. + +## 1.3 State transition model + +The following figure shows the successful cases of transition between the applicable logical states of MPTY. The state changes are caused by actions of the service provider. + +Note that error cases are not shown in the diagram as they normally do not cause a state change. Additionally, some successful requests may not cause a state change. Hence they are not shown in the diagram. + + + +``` + +stateDiagram-v2 + [*] --> State1 : (Not Provisioned, Not Applicable, Not Active, Not Induced) + State1 --> State2 : Provision + State2 --> State1 : Withdrawal + state " (Not Provisioned, Not Applicable, Not Active, Not Induced) " as State1 + state " (Provisioned, Not Applicable, Active and Operative, Not Induced) " as State2 + +``` + +The diagram illustrates the state transition model for MPTY. It consists of two states represented by ovals. The left state is labeled "(Not Provisioned, Not Applicable, Not Active, Not Induced)". The right state is labeled "(Provisioned, Not Applicable, Active and Operative, Not Induced)". A transition arrow labeled "Provision" points from the left state to the right state. A transition arrow labeled "Withdrawal" points from the right state back to the left state. + +State transition model for MPTY diagram showing two states and two transitions. + +**Figure 1.6: State transition model for MPTY** + +## 1.4 Transfer of information from HLR to VLR + +If the provisioning state for MPTY is "Provisioned" then, when the subscriber registers on a VLR, the HLR shall send that VLR information about the logical state of MPTY. + +If the logical state of MPTY is changed while a subscriber is registered on a VLR then the HLR shall inform the VLR of the new logical state of MPTY. + +## 1.5 Information stored in the VLR + +For MPTY the VLR shall store the service state information received from the HLR. + +## 1.6 Handover + +Handover will have no impact on the control procedures and the operation of the service. + +## 1.7 Simultaneous use of Multi Party operations + +The operations BuildMPTY, SplitMPTY, HoldMPTY and RetrieveMPTY interact with each other, and cannot be applied simultaneously. Once the mobile station has initiated one of these operations, it shall not initiate another Multi Party operation until the first operation has been acknowledged by the network, or the MS locally determines (due to timer expiry) that the first operation has failed. + +# Annex A: Change history + +| TSG CN# | Spec | CR | Rev | Phase | Cat | New Ver | Subject/Comment | +|----------|-----------|-----|-----|--------|-----|---------|--------------------------------------------------| +| Apr 1999 | GSM 03.84 | | | R97 | | | Transferred to 3GPP CN1 | +| CN#03 | 23.084 | | | R99 | | 3.0.0 | Approved at CN#03 | +| CN#06 | 23.084 | 001 | | R99 | | 3.1.0 | approved at CN#06 | +| CN#09 | 23.084 | 002 | 1 | R99 | F | 3.2.0 | SDL refresh | +| Cn#11 | | | | | | 4.0.0 | Version increased from R99 to Rel-4 after CN#11. | +| CN#11 | 23.084 | 003 | 1 | Rel-4 | C | 4.0.0 | Enhancement of MPTY SDLs and CAMEL functionality | +| CN#12 | 23.084 | 004 | 1 | Rel-5 | C | 5.0.0 | Handling of MultiCall in MPTY procedure | +| CN#26 | 23.084 | | | Rel-6 | | 6.0.0 | Release 6 after CN#26 | +| CT#36 | 23.084 | | | Rel-7 | | 7.0.0 | Upgraded unchanged from Rel-6 | +| CT#42 | 23.084 | | | Rel-8 | | 8.0.0 | Upgraded unchanged from Rel-7 | +| CT#46 | 23.084 | - | - | Rel-9 | | 9.0.0 | Update to Rel-9 version (MCC) | +| 2011-03 | 23.084 | - | - | Rel-10 | | 10.0.0 | Update to Rel-10 version (MCC) | +| 2012-09 | 23.084 | - | - | Rel-11 | | 11.0.0 | Update to Rel-11 version (MCC) | +| 2014-09 | 23.084 | - | - | Rel-12 | | 12.0.0 | Update to Rel-12 version (MCC) | +| 2015-12 | 23.084 | - | - | Rel-13 | - | 13.0.0 | Update to Rel-13 version (MCC) | +| 2017-03 | 23.084 | - | - | Rel-14 | | 14.0.0 | Update to Rel-14 version (MCC) | +| 2018-06 | 23.084 | - | - | Rel-15 | - | 15.0.0 | Update to Rel-15 version (MCC) | +| 2020-07 | 23.084 | - | - | 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/23135/07b17a620c75522d53916a11e12d1bff_img.jpg b/marked/Rel-16/23_series/23135/07b17a620c75522d53916a11e12d1bff_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..97bed1ae713efa9addfb10c65a1ac78c7ef652e1 --- /dev/null +++ b/marked/Rel-16/23_series/23135/07b17a620c75522d53916a11e12d1bff_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7b2806766172e58768b69e82f4724f4562dcdb77abd5f28f2dc94b9cb28a82dd +size 30654 diff --git a/marked/Rel-16/23_series/23135/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/marked/Rel-16/23_series/23135/1a827b10290f33d4fec04d0e8ef7a897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aff366c33cf31ba6aebabf23aa00365f088d42ea --- /dev/null +++ b/marked/Rel-16/23_series/23135/1a827b10290f33d4fec04d0e8ef7a897_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:402b69be606d9be76925198e43b69db0e5c22a076ecdaad9ce4d86fcb4ce6a7a +size 84674 diff --git a/marked/Rel-16/23_series/23135/303fadfb9def251d1575d6221199b158_img.jpg b/marked/Rel-16/23_series/23135/303fadfb9def251d1575d6221199b158_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cf6e87516aed71f2204067a57cd0babc92db92c4 --- /dev/null +++ b/marked/Rel-16/23_series/23135/303fadfb9def251d1575d6221199b158_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:990aa62f8efef6ca42981fa4e5d9435e7cb8380535fa3d00c26cd10d1e3fd66c +size 24290 diff --git a/marked/Rel-16/23_series/23135/5793a44ffdadd039928e2f9fe6daae06_img.jpg b/marked/Rel-16/23_series/23135/5793a44ffdadd039928e2f9fe6daae06_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8232da0b75c9c804fc1198562b8d8090e6be040f --- /dev/null +++ b/marked/Rel-16/23_series/23135/5793a44ffdadd039928e2f9fe6daae06_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:69590135e005acc3df0c4f8dfabaf482a10b1ef7db2914915c0b8f5a3648ebd6 +size 104515 diff --git a/marked/Rel-16/23_series/23135/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Rel-16/23_series/23135/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9a45d040620c58efff2421cf7d5442f0faa1df42 --- /dev/null +++ b/marked/Rel-16/23_series/23135/5a4e62bead259c258d069fd3663ea670_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:16a2c951dfcc552bac93c1a4e86c4fa67637013d60899aa91a1036a1ea592798 +size 63492 diff --git a/marked/Rel-16/23_series/23135/79e1709a7317ead45379cbb8ff3ba802_img.jpg b/marked/Rel-16/23_series/23135/79e1709a7317ead45379cbb8ff3ba802_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c8d5494aae50ac18bdae93fbe0ce1a4b94d2445b --- /dev/null +++ b/marked/Rel-16/23_series/23135/79e1709a7317ead45379cbb8ff3ba802_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c0492fce255d0c02376e7b93b9840440bb8d586fae2a9effdab432734fb2db35 +size 88581 diff --git a/marked/Rel-16/23_series/23135/7e670a2b556b53ea9002dfff3a420e08_img.jpg b/marked/Rel-16/23_series/23135/7e670a2b556b53ea9002dfff3a420e08_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d8ddb4b678234f3421c2961b706a8c83b55ef6df --- /dev/null +++ b/marked/Rel-16/23_series/23135/7e670a2b556b53ea9002dfff3a420e08_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9679fffdceaf56858d809e0f074128bfe181d19b0b4dcc65abe91976a4785b76 +size 66505 diff --git a/marked/Rel-16/23_series/23135/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg b/marked/Rel-16/23_series/23135/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a5b101411885ee4ab520245ae4526be0ca0eb465 --- /dev/null +++ b/marked/Rel-16/23_series/23135/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:769c131fddb2c5c71d96b559f61a3ccaba741c7e4a7d7ab649509e7228da1660 +size 119845 diff --git a/marked/Rel-16/23_series/23135/8307f6b04df072c9332f9987e034272c_img.jpg b/marked/Rel-16/23_series/23135/8307f6b04df072c9332f9987e034272c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..426caee01856dbb5a13dda72b22b5247552feaab --- /dev/null +++ b/marked/Rel-16/23_series/23135/8307f6b04df072c9332f9987e034272c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2cd45f6d620dc7a74e11429bc5ad726586bc45da7bd1869cb389bde94f97de2b +size 94903 diff --git a/marked/Rel-16/23_series/23135/8fa679f79a1bb1f527cba9f29e784e89_img.jpg b/marked/Rel-16/23_series/23135/8fa679f79a1bb1f527cba9f29e784e89_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1306f12cc8f67b72291635061dee39270be0fea8 --- /dev/null +++ b/marked/Rel-16/23_series/23135/8fa679f79a1bb1f527cba9f29e784e89_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e282ef381ea00430dfb20de4421db6178abde1656004207eaa187127036be994 +size 117184 diff --git a/marked/Rel-16/23_series/23135/997233d405f0d4b89ddeb7683e047f66_img.jpg b/marked/Rel-16/23_series/23135/997233d405f0d4b89ddeb7683e047f66_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..42c680ae9aa2d6c2efdbb201cd2d7d76bdc226f2 --- /dev/null +++ b/marked/Rel-16/23_series/23135/997233d405f0d4b89ddeb7683e047f66_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:28c0b135d67de7dd0f2c69dbe5276882cab9c7eebb39755af648d60033708f5f +size 92924 diff --git a/marked/Rel-16/23_series/23135/a9ed452e3e099e1505f7b9ad182a11e9_img.jpg b/marked/Rel-16/23_series/23135/a9ed452e3e099e1505f7b9ad182a11e9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7a4625681cb0409c8179769dac2f344f370704a6 --- /dev/null +++ b/marked/Rel-16/23_series/23135/a9ed452e3e099e1505f7b9ad182a11e9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:27a40e48c2cd5e85e8da032995da1252bd2541e2d19de661211466392523d39f +size 41741 diff --git a/marked/Rel-16/23_series/23135/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg b/marked/Rel-16/23_series/23135/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..09b7632c22b4609ce96b498ca1095d192ca682a7 --- /dev/null +++ b/marked/Rel-16/23_series/23135/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ab0eabe6fd09f22f02f22f9ed63d30e2b2cd13d415d63d4d28cce6bfec671998 +size 76429 diff --git a/marked/Rel-16/23_series/23135/c2fc2621e8206d24427b56bcb2398fc0_img.jpg b/marked/Rel-16/23_series/23135/c2fc2621e8206d24427b56bcb2398fc0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e9d3caf2404fe5d41e5512bb80086e1ba4257a79 --- /dev/null +++ b/marked/Rel-16/23_series/23135/c2fc2621e8206d24427b56bcb2398fc0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d400eed0971731670f1173217c40a6b3a6d530eaa7edd59dfa05070f978ff9d5 +size 65574 diff --git a/marked/Rel-16/23_series/23135/raw.md b/marked/Rel-16/23_series/23135/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..eb93d6a9feb4e4ebc3609026c362a8039db7bc35 --- /dev/null +++ b/marked/Rel-16/23_series/23135/raw.md @@ -0,0 +1,941 @@ + + + + + + +# Contents + +| | | +|-------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Definitions and abbreviations ..... | 6 | +| 3.1 Definitions..... | 6 | +| 3.2 Abbreviations ..... | 6 | +| 4 Descriptions ..... | 6 | +| 4.1 Handling of Multicall ..... | 6 | +| 4.1.1 Provision..... | 6 | +| 4.1.2 Withdrawal ..... | 6 | +| 4.1.3 Registration..... | 6 | +| 4.1.4 Erasure ..... | 7 | +| 4.1.5 Activation ..... | 8 | +| 4.1.6 Deactivation..... | 8 | +| 4.1.7 Interrogation ..... | 8 | +| 4.2 Call related procedures..... | 10 | +| 4.2.1 MO call..... | 10 | +| 4.2.2 MT call ..... | 10 | +| 4.3 Messages and their contents..... | 12 | +| 4.3.1 Messages between MS and MSC ..... | 12 | +| 4.3.2 Messages on B interface (MSC-VLR) ..... | 13 | +| 4.3.2.1 Send Info For Outgoing Call ..... | 13 | +| 4.3.2.2 Send Info For Outgoing Call negative response ..... | 13 | +| 4.3.2.3 Send Info For Incoming Call ..... | 13 | +| 4.3.2.4 Send Info For Incoming Call ack..... | 13 | +| 4.3.2.5 Send Info For Incoming Call negative response..... | 13 | +| 4.3.2.6 Complete Call ..... | 13 | +| 4.3.2.7 Complete Call ack..... | 13 | +| 4.3.2.8 Page MS..... | 13 | +| 4.3.2.9 Page MS negative response ..... | 14 | +| 4.3.2.10 Process Access Request..... | 14 | +| 4.3.2.11 Process Access Request ack ..... | 14 | +| 4.3.2.12 Process Access Request negative response ..... | 14 | +| 4.3.2.13 Search For MS ..... | 14 | +| 4.3.2.14 Search For MS ack..... | 14 | +| 4.3.2.15 Search For MS negative response..... | 14 | +| 5 Network entity functions..... | 15 | +| 5.1 General ..... | 15 | +| 5.2 MO call..... | 15 | +| 5.2.1 Functional requirements of serving MSC..... | 15 | +| 5.2.2 Functional requirements of VLR..... | 16 | +| 5.3 MT call..... | 18 | +| 5.3.1 Functional requirements of serving MSC..... | 18 | +| 5.3.2 Functional requirements of VLR..... | 22 | +| 6 Interaction with telecommunication services..... | 24 | +| 6.1 Speech ..... | 24 | +| 6.2 Short message service ..... | 24 | +| 6.3 Facsimile service..... | 24 | +| 6.4 Data circuit asynchronous ..... | 24 | +| 6.5 Data circuit synchronous..... | 24 | +| 6.6 Void..... | 24 | +| 6.7 GPRS..... | 24 | +| 7 Interaction with other supplementary services..... | 24 | +| 7.1 Line Identification services ..... | 24 | + +| | | | +|-------------------------------|-------------------------------------------------------------------------|-----------| +| 7.2 | Call forwarding unconditional (CFU) ..... | 24 | +| 7.3 | Call forward on busy (CFB)..... | 25 | +| 7.4 | Call forwarding on no reply (CFNRy) ..... | 25 | +| 7.5 | Call forwarding on MS not reachable (CFNRc) ..... | 25 | +| 7.6 | Call Hold (CH)..... | 25 | +| 7.7 | Call Waiting (CW) ..... | 25 | +| 7.8 | Multipart service (MPTY)..... | 25 | +| 7.9 | Closed user group (CUG)..... | 25 | +| 7.10 | Advice Of Charge (AoC) ..... | 25 | +| 7.11 | Call Barring services ..... | 25 | +| 7.12 | Explicit call transfer (ECT) ..... | 25 | +| 7.13 | Call Deflection (CD)..... | 25 | +| 7.14 | Completion of calls to busy subscriber (CCBS) ..... | 25 | +| 8 | Interaction with network features ..... | 26 | +| 8.1 | Customised Applications for Mobile network Enhanced Logic (CAMEL) ..... | 26 | +| 8.2 | Support of Optimal Routeing (SOR)..... | 26 | +| 8.3 | Operator Determined Barring (ODB) ..... | 26 | +| 9 | Information stored in the HLR..... | 26 | +| 10 | State transition model..... | 26 | +| 11 | Transfer of information from HLR to VLR..... | 27 | +| 12 | Information stored in VLR..... | 27 | +| 13 | Handover..... | 27 | +| Annex A (informative): | Examples ..... | 28 | +| Annex B (informative): | Change history..... | 32 | + +# --- Foreword + +This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). + +The present document gives the stage 2 description of the Multicall service within the 3GPP system. + +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 Multicall supplementary service. + +# --- 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. + +- [1] 3GPP TR 21.905: "3GPP Vocabulary". +- [2] 3GPP TS 22.100: "UMTS Phase 1". +- [3] 3GPP TS 22.105: "Services & Service capabilities". +- [4] 3GPP TS 22.135: "Multicall Stage 1". +- [5] 3GPP TS 23.009: "Handover procedures". +- [6] 3GPP TS 23.011: "Technical realisation of supplementary services". +- [7] 3GPP TS 23.018: "Basic call handling; Technical realization". +- [8] 3GPP TS 23.083: "Call Waiting (CW) and Call Hold (HOLD) Supplementary Service - Stage 2". +- [9] 3GPP TS 24.008: "Mobile radio interface layer 3 specification Core Network Protocol – Stage 3". + +# 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in TS 22.135 and the following apply. + +**Speech Call:** speech call means one of TS11 (Telephony), TS12 (Emergency call), TS61 (Alternate speech and facsimile group 3). + +## 3.2 Abbreviations + +Abbreviations used in the present document are listed in TR 21.905. + +# 4 Descriptions + +## 4.1 Handling of Multicall + +### 4.1.1 Provision + +No special signalling procedures apply. + +### 4.1.2 Withdrawal + +No special signalling procedures apply. + +### 4.1.3 Registration + +The information flow for registration is shown in figure 1. The registration process is shown in figure 2. + + + +``` +sequenceDiagram + participant MS + participant MSC + participant VLR + participant HLR + Note left of MS: MS + MS->>MSC: Register Multicall (Nbr_User) + MSC->>VLR: Register Multicall (Nbr_User) + VLR->>HLR: Register Multicall (Nbr_User) + HLR-->>VLR: ACK (SS-status, Nbr_User) + VLR-->>HLR: ISD (SS-Code = MC, Nbr_User) + VLR-->>MSC: ACK + MSC-->>MS: Release complete (SS-status, Nbr_User) +``` + +The diagram illustrates the sequence of messages for Multicall registration. It involves four entities: MS (Mobile Station), MSC (Mobile Switching Center), VLR (Visitor Location Register), and HLR (Home Location Register). The sequence of messages is as follows: 1. MS sends a 'Register Multicall' message with parameter (Nbr\_User) to MSC. 2. MSC sends a 'Register Multicall' message with parameter (Nbr\_User) to VLR. 3. VLR sends a 'Register Multicall' message with parameter (Nbr\_User) to HLR. 4. HLR responds with an 'ACK' message containing (SS-status, Nbr\_User) to VLR. 5. VLR sends an 'ISD' message containing (SS-Code = MC, Nbr\_User) to HLR. 6. VLR sends an 'ACK' message to MSC. 7. MSC sends a 'Release complete' message containing (SS-status, Nbr\_User) to MS. + +Sequence diagram showing the registration of Multicall between MS, MSC, VLR, and HLR. + +Figure 1: Registration of Multicall + + + +Process Register\_Multicall\_HLR + +RM\_HLR1(1) + +Multicall Registration +process in HLR + +``` + +graph TD + Start([ ]) --> Idle1([Idle]) + Idle1 --> Register[/Register +Multicall/] + Register --> Provisioned{Multicall +provisioned?} + Provisioned -- No --> Error1[Error: = +Service not provisioned] + Provisioned -- Yes --> Provided{Nbr_User +Provided?} + Provided -- No --> Error2[Error: = +Insufficient information] + Provided -- Yes --> Range{0 < Nbr_User +<= Nbr_SB?} + Range -- No --> Error3[Error: = +Nbr_User out of range] + Range -- Yes --> Set[Set new value +Nbr_User] + + Set --> Join(( )) + Error1 --> Join + Error2 --> Join + Error3 --> Join + + Join --> Ack[/Acknowledge +positive=Nbr_User +negative=Error/] + Ack --> Idle2([Idle]) + +``` + +Flowchart for Process Register\_Multicall\_HLR (RM\_HLR1(1)). The process starts at an Idle state, receives a Register Multicall request, and then checks if the service is provisioned. If not, it returns an error. If provisioned, it checks if Nbr\_User is provided. If not, it returns insufficient information. If provided, it checks if 0 < Nbr\_User <= Nbr\_SB. If not, it returns an error. If valid, it sets the new value for Nbr\_User and then sends an acknowledgment (positive or negative) before returning to the Idle state. + +**Figure 2: Process Register\_Multicall\_HLR** + +### 4.1.4 Erasure + +No special signalling procedures apply. + +### 4.1.5 Activation + +The service provider shall provide an initial value for $Nbr_{User}$ when activating the service. No special signalling procedures apply. + +### 4.1.6 Deactivation + +No special signalling procedures apply. + +### 4.1.7 Interrogation + +The information flow for interrogation is shown in figure 3. The interrogation process is shown in figure 4. + + + +``` +sequenceDiagram + participant MS + participant MSC + participant VLR + Note right of VLR: INTERROGATE_MULTICALL_VLR + MS->>MSC: Interrogate Multicall + MSC->>VLR: Interrogate Multicall + VLR-->>MSC: ACK (N_br_User, N_br_SB, N_br_SN) + MSC-->>MS: Release complete (N_br_User, N_br_SB, N_br_SN) +``` + +The diagram illustrates the interrogation process involving three entities: MS (Mobile Station), MSC (Mobile Switching Center), and VLR (Visitor Location Register). The sequence of messages is as follows: 1. The MS sends an 'Interrogate Multicall' message to the MSC. 2. The MSC then sends an 'Interrogate Multicall' message to the VLR. 3. The VLR responds with an 'ACK' message containing parameters (N\_br\_User, N\_br\_SB, N\_br\_SN). 4. Finally, the MSC sends a 'Release complete' message to the MS, also containing the parameters (N\_br\_User, N\_br\_SB, N\_br\_SN). A note on the VLR lifeline indicates the internal operation 'INTERROGATE\_MULTICALL\_VLR'. + +Sequence diagram of Interrogation of Multicall + +**Figure 3: Interrogation of Multicall** + + + +**Process Interrogate\_Multicall\_VLR** IM\_VLR1(1) + +Multicall Interrogation process + +``` +graph TD; Start([ ]) --> idle1([idle]); idle1 --> Interrogate{Interrogate Multicall}; Interrogate --> Decision{Multicall provisioned?}; Decision -- Yes --> Result[Result: = Nbr_SB, Nbr_User, Nbr_SN]; Result --> Acknowledge[Acknowledge positive=Result negative=Error]; Acknowledge --> idle2([idle]); Decision -- No --> Error[Error: =Service not provisioned]; Error --> Merge(( )); Merge --> Acknowledge; +``` + +Flowchart for Process Interrogate\_Multicall\_VLR. It starts with an initial state, goes to 'idle', then 'Interrogate Multicall'. A decision 'Multicall provisioned?' follows. If 'Yes', it calculates 'Result: = Nbr\_SB, Nbr\_User, Nbr\_SN', then sends an 'Acknowledge' (positive=Result, negative=Error), and returns to 'idle'. If 'No', it sets 'Error: =Service not provisioned' and returns to the merge point before the Acknowledge step. + +Figure 4: Process Interrogate\_Multicall\_VLR + +## 4.2 Call related procedures + +The procedures for basic call handling are specified in 3GPP TS 23.018. These shall also be used for Multicall. + +### 4.2.1 MO call + +Figure 5 shows the flow of information between network elements for an MO call: + + + +The diagram illustrates the sequence of messages for a mobile originating (MO) call. At the top, a large arrow labeled "Active Calls" spans across the four network elements: MS, MSC, VLR, and Destination NW. The sequence of messages is as follows: + +- The MS sends a **Setup (SI)** message to the MSC. +- The MSC sends a **SIFOC (Total Number of bearers in use)** message to the VLR. +- The VLR sends a **Complete Call** message back to the MSC. +- The MSC sends an **IAM** message to the Destination NW. +- The Destination NW sends an **ACM** message back to the MSC. +- The MSC sends an **ANM** message to the Destination NW. +- The MSC sends an **Alert** message to the MS. +- The MSC sends a **Connect** message to the MS. +- The MS sends a **Connect ack** message back to the MSC. +- A **TCH Allocation** message is shown as a dashed double-headed arrow between the MS and the MSC. + +Sequence diagram showing information flow for a mobile originating (MO) call between MS, MSC, VLR, and Destination NW. + +Figure 5: Information flow for mobile originating call + +### 4.2.2 MT call + +Figure 6 and Figure 7 show the flow of information between network elements for an MT call: + +- Case 1: When the MS requests a new bearer in call confirmed. (Figure 6). +- Case 2: When the MS requests a new bearer in Connect. (Figure 7). + + + +This sequence diagram illustrates the information flow for a mobile terminating call (Case1) involving four entities: MS (Mobile Station), MSC (Mobile Switching Center), VLR (Visitor Location Register), and GMSC (Gateway Mobile Switching Center). A large arrow at the top labeled "Active Calls" spans across the diagram. The sequence of messages is as follows: 1. IAM (Initial Address Message) from GMSC to MSC. 2. SIFIC (Subsequent Information) from MSC to VLR. 3. Page MS (Nbr User) from MSC to VLR. 4. Process access req from VLR to MSC. 5. Process access req ack from MSC to VLR. 6. Complete Call from MSC to VLR. 7. Setup from MSC to MS. 8. Call Confirmed (SI) from MS to MSC. 9. TCH Allocation (dashed line) between MS and MSC. 10. Alert from MSC to MS. 11. ACM (Address Complete Message) from GMSC to MSC. 12. Connect from MS to MSC. 13. ANM (Answer Message) from GMSC to MSC. 14. Connect ack from MSC to MS. 15. Complete Call ack from MSC to VLR. + +Sequence diagram for mobile terminating call (Case1) showing information flow between MS, MSC, VLR, and GMSC. + +Figure 6: Information flow for mobile terminating call (Case1) + + + +This sequence diagram illustrates the information flow for a mobile terminating call (Case2) involving four entities: MS (Mobile Station), MSC (Mobile Switching Center), VLR (Visitor Location Register), and GMSC (Gateway Mobile Switching Center). A large arrow at the top labeled "Active Calls" spans across the diagram. The sequence of messages is as follows: 1. IAM (Initial Address Message) from GMSC to MSC. 2. SIFIC (Subsequent Information) from MSC to VLR. 3. Page MS (Nbr User) from MSC to VLR. 4. Process access req from VLR to MSC. 5. Process access req ack from MSC to VLR. 6. Complete Call from MSC to VLR. 7. Setup from MSC to MS. 8. Call Confirmed (SI="No Bearer") from MS to MSC. 9. Alert from MSC to MS. 10. ACM (Address Complete Message) from GMSC to MSC. 11. Connect (SI) from MS to MSC. 12. ANM (Answer Message) from GMSC to MSC. 13. TCH Allocation (dashed line) between MS and MSC. 14. Connect ack from MSC to MS. 15. Complete Call ack from MSC to VLR. + +Sequence diagram for mobile terminating call (Case2) showing information flow between MS, MSC, VLR, and GMSC. + +Figure 7: Information flow for mobile terminating call (Case2) + +## 4.3 Messages and their contents + +This clause contains the detailed description of the information flows used by Multicall. + +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. + +### 4.3.1 Messages between MS and MSC + +Table 1 indicates messages between the MS and the MSC for mobile originating calls and mobile terminating calls. (Refer to TS 24.008). + +The MS shall indicate the maximum number of bearers supported by the MS in the CC capabilities IE. The MS shall also indicate the maximum number of simultaneous speech bearers supported by the MS for future compatibility. For Release 99, the maximum number of simultaneous speech bearers is 1. If the MS does not indicate the maximum number of bearers the network shall assume it does not support Multicall. + +The network supporting Multicall shall indicate the capability in the NW CC capabilities IE. If the NW CC capabilities IE is not sent from the network, the MS supporting Multicall shall assume that the network doesn't support Multicall. If an MS initiating an emergency call is located in a network that does not support Multicall, the MS shall release one or more existing call to ensure that the emergency call can be established. + +**Table 1: Messages between MS and MSC** + +| Message | Message sender | Information element name | Information element Required | Information element description | +|-----------------|----------------|--------------------------|------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Setup (MO) | MS | Stream Identifier | M | This information element indicates which bearer (new or existing) shall be used for the call. | +| | | CC Capabilities | C | For the first call, this information element shall be included to indicate the maximum number of bearers supported by the MS. | +| Emergency Setup | MS | Stream Identifier | M | This information element indicates which bearer (new or existing) shall be used for the call. | +| Call Confirmed | MS | Stream Identifier | M | This information element indicates whether a new bearer is requested, i.e. SI=value which is not used by any of the existing bearers , or no bearer is requested at that point in time, i.e. SI="no bearer". | +| | | CC Capabilities | C | For the first call, this information element shall be included to indicate the maximum number of bearers supported by the MS. | +| Connect (MT) | MS | Stream Identifier | C | This IE shall be present in the Connect message if the SI contained "No bearer" in the Call Confirmed message, otherwise shall be absent. | +| Setup (MT) | NW | NW CC Capabilities | C | This information element shall be present for the first call. | +| Call Proceeding | NW | NW CC Capabilities | C | | + +### 4.3.2 Messages on B interface (MSC-VLR) + +#### 4.3.2.1 Send Info For Outgoing Call + +**This message is specified in 3GPP TS 23.018. The following additional information element is required:** + +| Information element name | Required | Description | +|--------------------------------|----------|-----------------------------------------------------------------| +| Total number of bearers in use | M | Total number includes the new bearer if requested for the call. | + +#### 4.3.2.2 Send Info For Outgoing Call negative response + +**This message is specified in 3GPP TS 23.018. The following additional information element is required:** + +| Information element name | Required | Description | +|---------------------------------------|----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Negative response information element | M |
If the VLR detects that the OG call can not be permitted because Multicall limit set by the user is exceeded, it shall indicate " Nbr_User is exceeded" as the negative response information element value.
If the VLR detects that the OG call can not be permitted because the user is not provisioned with Multicall, it shall indicate "Multicall not provisioned" as the negative response information element value.
| + +#### 4.3.2.3 Send Info For Incoming Call + +This message is specified in TS 23.018. + +#### 4.3.2.4 Send Info For Incoming Call ack + +This message is specified in TS 23.018. + +#### 4.3.2.5 Send Info For Incoming Call negative response + +This message is specified in TS 23.018. + +#### 4.3.2.6 Complete Call + +This message is specified in TS 23.018. + +#### 4.3.2.7 Complete Call ack + +This message is specified in TS 23.018. + +#### 4.3.2.8 Page MS + +**This message is specified in 3GPP TS 23.018. The following additional information element is required:** + +| Information element name | Required | Description | +|--------------------------|----------|-------------------------------------------------------------------| +| N br _User | M | Shall be present if the subscriber is provisioned with Multicall. | + +#### 4.3.2.9 Page MS negative response + +This message is specified in 3GPP TS 23.018. The following additional information element is required: + +| Information element name | Required | Description | +|--------------------------|----------|------------------------------------------------------------------------------------------------------------------| +| Basic service list | C | If the MSC detects subscriber busy (More Calls Possible), the Basic service list shall be included, see Table 2. | + +Table 2: Basic Service List setting + +| Condition | | Setting | +|-----------------------------------------|--------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| The terminating call type is speech | There exists an active or held speech call | Basic service of active call via the same bearer as the existing speech call. If an active call does not exist via the same bearer as the existing speech call "speech" shall be indicated. | +| | There exists no speech call | All basic services of ongoing calls | +| The terminating call type is not speech | | All basic services of ongoing calls | + +#### 4.3.2.10 Process Access Request + +This message is specified in TS 23.018. + +#### 4.3.2.11 Process Access Request ack + +This message is specified in TS 23.018. + +#### 4.3.2.12 Process Access Request negative response + +This message is specified in TS 23.018. + +#### 4.3.2.13 Search For MS + +This message is specified in 3GPP TS 23.018. The following additional information element is required: + +| Information element name | Required | Description | +|--------------------------|----------|-------------------------------------------------------------------| +| Nbr_User | M | Shall be present if the subscriber is provisioned with Multicall. | + +#### 4.3.2.14 Search For MS ack + +This message is specified in 3GPP TS 23.018. + +#### 4.3.2.15 Search For MS negative response + +This message is specified in 3GPP TS 23.018. The following additional information element is required: + +| Information element name | Required | Description | +|--------------------------|----------|------------------------------------------------------------------------------------------------------------------| +| Basic service list | C | If the MSC detects subscriber busy (More Calls Possible), the Basic service list shall be included, see Table 2. | + +# --- 5 Network entity functions + +The following SDL diagrams describe the procedures within individual network entities for handling Multicall. + +## 5.1 General + +The MSC shall check whether the maximum number of bearers has been reached for both MO and MT call. In counting of the current number of bearers for the target subscriber, the following situations are counted as an active bearer. + +- Call in set-up. +- Established call. +- Call on hold. +- Call on hold and established call on the same bearer. +- Call on hold and MO call in Setup on the same bearer. + +## 5.2 MO call + +### 5.2.1 Functional requirements of serving MSC + +Figure 8: Procedure Check\_OG\_Multicall\_MSC. + +This procedure is called when the MSC receives a Setup message from the MS. After handover procedure completion to another MSC, $N_{br\_SN}$ as defined for the target MSC shall overwrite the previous $N_{br\_SN}$ . + + + +Procedure Check\_OG\_Multicall\_MSC + +COM\_MSC1(1) + +``` + +graph TD + Start([ ]) --> D1{Is a new bearer requested?} + D1 -- Yes --> D2{Current number of bearers in use < Nbr_SN} + D1 -- No --> D3{Is there an active call on the bearer?} + + D2 -- Yes --> R1[Result := Pass] + D2 -- No --> M[Multicall indicator := Nbr_SN exceeded] + M --> R2[Result := Rejected] + + D3 -- Yes --> R3[Result := Rejected] + D3 -- No --> R4[Result := Pass] + + R1 --> End1((X)) + R2 --> End2((X)) + R3 --> End3((X)) + R4 --> End4((X)) + +``` + +Procedure to check Multicall limitation by serving MSC + +Flowchart for Procedure Check\_OG\_Multicall\_MSC. It starts with a connector, then a decision 'Is a new bearer requested?'. If 'Yes', it goes to another decision 'Current number of bearers in use < Nbr\_SN'. If 'Yes', 'Result := Pass'; if 'No', 'Multicall indicator := Nbr\_SN exceeded' then 'Result := Rejected'. If 'No' to the first decision, it goes to 'Is there an active call on the bearer?'. If 'Yes', 'Result := Rejected'; if 'No', 'Result := Pass'. All results lead to an exit connector marked with an X. + +**Figure 8: Procedure Check\_OG\_Multicall\_MSC** + +### 5.2.2 Functional requirements of VLR + +Figure 9: Procedure Check\_OG\_Multicall\_VLR. + +This procedure is called when the VLR receives a Send Info For Outgoing Call message from the MSC. + + + +**Procedure Check\_OG\_Multicall\_VLR** COM\_VLR1(1) + +Procedure to check Multicall subscription limitation + +``` +graph TD; Start([ ]) --> D1{Multicall provisioned?}; D1 -- No --> D2{Total number of bearer in use > 1}; D1 -- Yes --> D3{Total number of bearers in use <= Nbr_User}; D2 -- Yes --> NR1[Negative response: = Multicall not provisioned]; D2 -- No --> R1[Result:= Pass]; NR1 --> R2[Result: =Fail]; D3 -- Yes --> R3[Result:= Pass]; D3 -- No --> NR2[Negative response: = Nbr_User exceeded]; NR2 --> R2; R1 --> End1(( )); R2 --> End2(( )); R3 --> End3(( )); +``` + +Flowchart for Procedure Check\_OG\_Multicall\_VLR. It starts with a connector, then a decision 'Multicall provisioned?'. If 'No', it goes to 'Total number of bearer in use > 1'. If 'Yes', it goes to 'Total number of bearers in use <= Nbr\_User'. From 'Total number of bearer in use > 1', if 'Yes', it leads to 'Negative response: = Multicall not provisioned', which then leads to 'Result: =Fail'. If 'No', it leads to 'Result:= Pass'. From 'Total number of bearers in use <= Nbr\_User', if 'Yes', it leads to 'Result:= Pass'. If 'No', it leads to 'Negative response: = Nbr\_User exceeded', which then leads to 'Result: =Fail'. All three result boxes lead to connectors. + +Figure 9: Procedure Check\_OG\_Multicall\_VLR + +## 5.3 MT call + +### 5.3.1 Functional requirements of serving MSC + +Figure 10: Procedure Check\_MT\_Multicall\_MSC. + +This procedure is called when the MSC receives a Page MS message or a Search For MS message from the VLR. The maximum number of bearers ( $N_{br}$ ) indicates the minimum value of $N_{br\_User}$ , $N_{br\_SN}$ and $N_{br\_UE}$ . After handover to another MSC is completed, $N_{br\_SN}$ , as defined for the target MSC, shall overwrite the previous $N_{br\_SN}$ . + +"Call in Setup" means that the MS is engaged in at least one call that has not reached the established phase (called party answer). + +The test "Call waiting" takes the "Yes" exit if a waiting call has been offered to the subscriber but the outcome of offering the call has not been determined. + +Figure 11: Procedure Establish\_Terminating\_TCH\_Multicall. + +This procedure is called when the MSC receives a Call Confirmed or a Connect message from the MS. If the MS indicates "No bearer" as the value of the Stream Identifier in the Call Confirmed message the test "Bearer allocation pending" takes the "Yes" exit. + +Figure 12: Procedure MC\_TCH\_Check + +This procedure is called when the MSC needs to establish a terminating TCH. + + + +### Procedure Check\_MT\_Multicall\_MSC + +CMM\_MSC1(1) + +Procedure to determine + the way to offer the call + and whether the MS is NDUB + + + +``` + +graph TD + Start([ ]) --> D1{Nbr_User indicated?} + D1 -- No --> R1[Result := Not provisioned] + R1 --> X1((X)) + D1 -- Yes --> D2{Current number of terminating calls < Ncs_MT} + D2 -- No --> R2[Result := NDUB] + R2 --> X2((X)) + D2 -- Yes --> D3{New call is speech?} + D3 -- No --> D4{Speech call exists?} + D3 -- Yes --> D4 + D4 -- No --> D7{Current number of bearers in use < Nbr} + D4 -- Yes --> D5{Speech call is in Setup?} + D5 -- Yes --> R3[Result := NDUB] + R3 --> X3((X)) + D5 -- No --> D6{Waiting call exists?} + D6 -- Yes --> D5 + D6 -- No --> R4[Result := More calls possible] + R4 --> X4((X)) + D7 -- Yes --> R5[Result := Offered] + R5 --> X5((X)) + D7 -- No --> D8{All calls are in Setup?} + D8 -- Yes --> R6[Result := NDUB] + R6 --> X6((X)) + D8 -- No --> R5 + +``` + +NOTE: Each call in set-up is counted as one bearer. + +Flowchart for Procedure Check\_MT\_Multicall\_MSC. It starts with a start symbol and proceeds through decision diamonds for 'Nbr\_User indicated?', 'Current number of terminating calls < Ncs\_MT', 'New call is speech?', 'Speech call exists?', 'Speech call is in Setup?', 'Waiting call exists?', 'All calls are in Setup?', and 'Current number of bearers in use < Nbr'. It ends with result boxes: 'Result := NDUB', 'Result := More calls possible', 'Result := NDUB', and 'Result := Offered'. + +**Figure 10: Procedure Check\_MT\_Multicall\_MSC** + + + +### Procedure Establish\_Terminating\_TCH\_Multicall + +ETTM1(1) + +Procedure to allocate a TCH after checking Multicall limitation + +``` +graph TD; Start([ ]) --> BearerPending{Bearer allocation pending?}; BearerPending -- Yes --> ResultPass1[Result:= Pass]; BearerPending -- No --> MC_TCH_Check[MC_TCH_Check]; MC_TCH_Check --> Result{Result}; Result -- Reject --> ResultRejected[Result:= Rejected]; Result -- Allocate --> AllocateChannel{Allocate channel}; AllocateChannel --> WaitForComplete([Wait_For_Allocation_Complete]); WaitForComplete --> ReleaseTransaction1{Release transaction}; ReleaseTransaction1 --> ResultFail1[Result:= Fail]; WaitForComplete --> AllocationComplete{Allocation complete}; AllocationComplete --> ResultPass2[Result:= Pass]; Result -- Fail --> ResultFail2[Result:= Fail]; Result -- Aborted --> ResultAborted1[Result:= Aborted]; Result -- Pass --> ResultPass3[Result:= Pass]; ResultAborted1 --> Release{Release}; Release --> ReleaseTransaction2{Release transaction}; ReleaseTransaction2 --> ResultAborted2[Result:= Aborted]; ResultPass1 --> End(( )); ResultRejected --> End; ResultFail1 --> End; ResultPass2 --> End; ResultFail2 --> End; ResultAborted2 --> End; ResultPass3 --> End; +``` + +Flowchart for Procedure Establish\_Terminating\_TCH\_Multicall. It starts with a connector, checks if bearer allocation is pending. If yes, it goes to 'Result:= Pass'. If no, it performs 'MC\_TCH\_Check'. The 'Result' from the check can be 'Reject', 'Allocate', 'Fail', 'Aborted', or 'Pass'. 'Reject' leads to 'Result:= Rejected'. 'Allocate' leads to 'Allocate channel' -> 'Wait\_For\_Allocation\_Complete' -> 'Release transaction' -> 'Result:= Fail' or 'Allocation complete' -> 'Result:= Pass'. 'Fail' leads to 'Result:= Fail'. 'Aborted' leads to 'Result:= Aborted'. 'Pass' leads to 'Result:= Pass'. All final results converge to a connector. + +Figure 11: Procedure Establish\_Terminating\_TCH\_Multicall + + + +### Procedure MC\_TCH\_Check + +MTC1(1) + +Procedure to allocate TCH after checking Multicall limitation + +``` +graph TD; Start([ ]) --> Q1{New bearer requested?}; Q1 -- No --> Junction(( )); Q1 -- Yes --> Q2{Nbr reached?}; Q2 -- Yes --> R1[Result:= Reject]; Q2 -- No --> P1[TCH_Check]; P1 --- Note[See TS 23.018]; P1 --> Q3{Result}; Q3 -- Reject --> R1; Q3 -- Aborted --> R2[Result:= Aborted]; Q3 -- Fail --> R3[Result:= Fail]; Q3 -- Allocate --> R4[Result:= Allocate]; Q3 -- Use existing --> R5[Result:= Pass]; R1 --> End((X)); R2 --> End; R3 --> End; R4 --> End; R5 --> End; +``` + +Flowchart for Procedure MC\_TCH\_Check. It starts with an oval connector, followed by a decision 'New bearer requested?'. If 'No', it goes to a junction. If 'Yes', it goes to another decision 'Nbr reached?'. If 'Yes' to 'Nbr reached?', it goes to a 'Reject' result box. If 'No' to 'Nbr reached?', it goes to a 'TCH\_Check' process box (referencing TS 23.018). From 'TCH\_Check', it goes to a 'Result' decision. The 'Result' decision has five outcomes: 'Reject' (Result:= Reject), 'Aborted' (Result:= Aborted), 'Fail' (Result:= Fail), 'Allocate' (Result:= Allocate), and 'Use existing' (Result:= Pass). All five result boxes lead to a final circular connector with an 'X'. + +Figure 12: Procedure MC\_TCH\_Check + +### 5.3.2 Functional requirements of VLR + +Figure 13: Procedure Get\_CW\_Subscription\_Info\_Multicall\_VLR. + +This procedure is called when the VLR receives a Page MS negative response message or a Search For MS negative response message with the negative response IE set to "Busy (More Calls Possible)". + + + +**Procedure Get\_CW\_Subscription\_Info\_Multicall\_VLR** CWIM\_VLR1(1) + +Procedure in the VLR to retrieve subscription information for the Call Waiting service + +Signals to/from the right are to/from the process MAF013 (TS 23.083) + +``` +graph TD; Start([ ]) --> BS1[BS := first BS]; BS1 --> Init{initiate handling of CW}; Init --> Wait([Wait_For_CW_Info]); Wait --> FromMSC[From MSC]; Wait --> Process[Process call waiting]; FromMSC --> Abort[/Abort/]; Process --> IndicatorCW{Indicator = CW available?}; IndicatorCW -- Yes --> IndicatorAvailable[Indicator := CW available]; IndicatorAvailable --> End1((X)); IndicatorCW -- No --> NextBS{Next BS exists?}; NextBS -- Yes --> BSNext[BS := next BS]; BSNext --> BS1; NextBS -- No --> IndicatorNotAvailable[Indicator := CW not available]; IndicatorNotAvailable --> End2((X)); +``` + +Flowchart for Procedure Get\_CW\_Subscription\_Info\_Multicall\_VLR. The process starts with BS := first BS, then initiate handling of CW, then Wait\_For\_CW\_Info. From Wait\_For\_CW\_Info, it branches to 'From MSC' -> 'Abort' and 'Process call waiting'. 'Process call waiting' leads to a decision 'Indicator = CW available?'. If 'Yes', it sets 'Indicator := CW available' and ends. If 'No', it leads to 'Next BS exists?'. If 'Yes', it sets 'BS := next BS' and loops back to 'initiate handling of CW'. If 'No', it sets 'Indicator := CW not available' and ends. + +Figure 13: Procedure Get\_CW\_Subscription\_Info\_Multicall\_VLR + +# --- 6 Interaction with telecommunication services + +## 6.1 Speech + +The Multicall supplementary service does not provide multiple traffic channels for speech calls. Refer to Procedure Check\_OG\_Multicall\_MSC and Procedure Check\_MT\_Multicall\_MSC. + +If $N_{br\_UE}$ is greater than $N_{br\_SN}$ , the mobile station may initiate an Emergency call even if $N_{br\_SN}$ has been reached. When the network receives an Emergency call Setup message from the mobile station: + +- if $N_{br\_SN}$ has not been reached, the network shall accept it regardless of $N_{br\_SB}$ or $N_{br\_User}$ ; +- if $N_{br\_SN}$ has been reached, the network shall reject the emergency call setup attempt. The MS shall release one or more existing calls and it shall re-initiate an Emergency call. + +The MS shall ensure that an emergency call Setup request is acceptable to a serving network which does not support multicall, if necessary by releasing one or more existing calls. + +## 6.2 Short message service + +No impact. + +## 6.3 Facsimile service + +The Multicall supplementary service provides multiple traffic channels for facsimile service except for alternate speech and facsimile group 3. + +## 6.4 Data circuit asynchronous + +The Multicall supplementary service provides multiple traffic channels for data circuit asynchronous. + +## 6.5 Data circuit synchronous + +The Multicall supplementary service provides multiple traffic channels for data circuit synchronous. + +## 6.6 Void + +## 6.7 GPRS + +No impact. + +# --- 7 Interaction with other supplementary services + +## 7.1 Line Identification services + +No impact. + +## 7.2 Call forwarding unconditional (CFU) + +No impact. + +## 7.3 Call forward on busy (CFB) + +The condition NDUB occurs in accordance with the definition for multicall. (See TS 22.135). + +## 7.4 Call forwarding on no reply (CFNRy) + +No impact. + +## 7.5 Call forwarding on MS not reachable (CFNRc) + +No impact. + +## 7.6 Call Hold (CH) + +No impact. + +## 7.7 Call Waiting (CW) + +Call Waiting SS will be invoked under the conditions described in TS 22.135. + +## 7.8 Multiparty service (MPTY) + +No impact. + +## 7.9 Closed user group (CUG) + +No impact. + +## 7.10 Advice Of Charge (AoC) + +No impact. + +## 7.11 Call Barring services + +No impact. + +## 7.12 Explicit call transfer (ECT) + +No impact. + +## 7.13 Call Deflection (CD) + +No impact. + +## 7.14 Completion of calls to busy subscriber (CCBS) + +The NDUB condition occurs in accordance with the definition for multicall. (See 3GPP TS 22.135). + +A subscriber provisioned with multicall is in the idle state when the subscriber has no ongoing (active or held) calls. CCBS requests in the destination B CCBS queue shall be processed if destination B is idle. + +# --- 8 Interaction with network features + +## 8.1 Customised Applications for Mobile network Enhanced Logic (CAMEL) + +No impact. + +## 8.2 Support of Optimal Routeing (SOR) + +No impact. + +## 8.3 Operator Determined Barring (ODB) + +No impact. + +# 9 Information stored in the HLR + +The following logical states are applicable for Multicall (refer to TS 23.011 for an explanation of the notation): + +| Provisioning State | Registration State | Activation State | HLR Induction State | +|--------------------|--------------------|-----------------------|---------------------| +| (Not Provisioned, | Not Applicable, | Not Active, | Not Induced) | +| (Provisioned, | Registered, | Active and Operative, | Not Induced) | + +The HLR shall store: + +- The state of Multicall (which shall be one of the valid states listed above) per subscriber. +- The subscription option "maximum number of bearers Nbr\_SB" per subscriber: + - This subscription option takes a value in the range (2 – 7). +- The subscription option "maximum number of bearers Nbr\_User" per subscriber: + - This subscription option takes a value in the range (1 – Nbr\_SB). + +# 10 State transition model + +Figure 14 shows the successful cases of transition between the applicable logical states of Multicall. The state changes are caused by actions of the service provider. + +Note that error cases are not shown in the diagram, as they normally do not cause a state change. Additionally, some successful requests may not cause a state change. Hence they are not shown in the diagram. + + + +``` + +stateDiagram-v2 + [*] --> Not Provisioned + state "Not Provisioned, Not Applicable, Not Active, Not induced" as Not Provisioned + state "Provisioned, Registered, Active and Operative, Not induced" as Provisioned + Not Provisioned --> Provisioned : Provision + Provisioned --> Not Provisioned : Withdrawal + +``` + +The diagram illustrates the state transition model for Multicall. It consists of two states represented by ovals. The top state is labeled "Not Provisioned, Not Applicable, Not Active, Not induced". The bottom state is labeled "Provisioned, Registered, Active and Operative, Not induced". A downward arrow from the top state to the bottom state is labeled "Provision". An upward arrow from the bottom state to the top state is labeled "Withdrawal". + +State transition model for Multicall diagram showing two states and their transitions. + +Figure 14: State transition model for Multicall + +# 11 Transfer of information from HLR to VLR + +If the provisioning state for Multicall is "Provisioned" then when the subscriber registers on a VLR the HLR shall send that VLR information about the logical state of Multicall, Nbr\_User and Nbr\_SB. + +If the logical state of Multicall, the subscription options Nbr\_SB or Nbr\_User are changed while a subscriber is registered on a VLR then the HLR shall inform the VLR of the new logical state of Multicall, the new Nbr\_User or the new Nbr\_SB. + +# 12 Information stored in VLR + +The VLR shall store the service state information, Nbr\_SB and Nbr\_User as received from the HLR. + +# --- 13 Handover + +In the case that the network supports Multicall, it shall be possible to handover multiple bearers (See TS 23.009). + +# Annex A (informative): Examples + +The following table shows some examples: + +## 1 Mobile Originating Call (MO call). + +As an example: $N_{br}=2$ . + +| Current Status | | | | Additional MO call | | +|----------------|------------------------------------------------------------------------|-------------------|-----------------|---------------------------------------------------------------------------------|---------------------------------------------------------------------------------| +| No | Status | Number of bearers | Number of calls | Speech | Data | +| 1 | None | 0 | 0 | Acceptable | Acceptable | +| 2 | 1 Speech call(active) | 1 | 1 | Rejected | Acceptable | +| 3 | 1 Speech call(on hold) | 1 | 1 | Acceptable(with same SI)
Rejected
(with another SI) | Acceptable | +| 4 | 1 Data call(active) | 1 | 1 | Acceptable | Acceptable | +| 5 | 1 Speech call(on hold)
1 Speech call(active) | 1 | 2 | Rejected | Acceptable | +| 6 | 1 Speech call(on hold)
1 Data call(active) | 1 | 2 | Rejected | Acceptable | +| 7 | Multiparty
(2-5 remote parties:
active) | 1 | 2 - 5 | Rejected | Acceptable | +| 8 | Multiparty
(2-5 remote parties: on
hold) | 1 | 2 - 5 | Acceptable
(with same SI)
Rejected
(with another SI) | Acceptable | +| 9 | 1 Speech call(active)
1 Data call(active) | 2 | 2 | Rejected | Rejected | +| 10 | 1 Speech call(on hold)
1 Data call(active) | 2 | 2 | Acceptable
(with same SI as
speech call)
Rejected
(with another SI) | Acceptable
(with same SI as
speech call)
Rejected
(with another SI) | +| 11 | 1 Speech call(on hold)
1 Speech call(active)
1 Data call(active) | 2 | 3 | Rejected | Rejected | +| 12 | 2 Data call(active) | 2 | 2 | Rejected | Rejected | +| 13 | 1 Speech call(on hold)
2 Data call(active) | 2 | 3 | Rejected | Rejected | +| 14 | Multiparty
(2-5 remote parties:
active)
1 Data call(active) | 2 | 3 - 6 | Rejected | Rejected | +| 15 | Multiparty
(2-5 remote parties: on
hold)
1 Data call(active) | 2 | 3 - 6 | Acceptable
(with same SI as
speech call)
Rejected
(with another SI) | Acceptable
(with same SI as
speech call)
Rejected
(with another SI) | + +## 2 Mobile Terminated Call (MT call). + +As an example: $N_{br}=2$ (CW is not active). + +| No | Current Status | | | Additional MT call | | +|----|------------------------------------------------------------------------|-------------------|-----------------|--------------------|---------| +| | Status | Number of bearers | Number of calls | Speech | Data | +| 1 | None | 0 | 0 | Offered | Offered | +| 2 | 1 Speech call(active) | 1 | 1 | Busy | Offered | +| 3 | 1 Speech call(on hold) | 1 | 1 | Busy | Offered | +| 4 | 1 Data call(active) | 1 | 1 | Offered | Offered | +| 5 | 1 Speech call(on hold)
1 Speech call(active) | 1 | 2 | Busy | Offered | +| 6 | 1 Speech call(on hold)
1 Data call(active) | 1 | 2 | Busy | Offered | +| 7 | Multiparty
(2-5 remote parties:
active) | 1 | 2 - 5 | Busy | Offered | +| 8 | Multiparty
(2-5 remote parties: on
hold) | 1 | 2 - 5 | Busy | Offered | +| 9 | 1 Speech call(active)
1 Data call(active) | 2 | 2 | Busy | Busy | +| 10 | 1 Speech call(on hold)
1 Data call(active) | 2 | 2 | Busy | Busy | +| 11 | 1 Speech call(on hold)
1 Speech call(active)
1 Data call(active) | 2 | 3 | Busy | Busy | +| 12 | 2 Data call(active) | 2 | 2 | Busy | Busy | +| 13 | 1 Speech call(on hold)
2 Data call(active) | 2 | 3 | Busy | Busy | +| 14 | Multiparty
(2-5 remote parties:
active)
1 Data call(active) | 2 | 3 - 6 | Busy | Busy | +| 15 | Multiparty
(2-5 remote parties: on
hold)
1 Data call(active) | 2 | 3 - 6 | Busy | Busy | + +## 3 Call Waiting (CW). + +As an example: $N_{br}=2$ (CW is provisioned). + +| No | Current Status | | | | Additional MT call | | +|----|-------------------------------------------------------|----------------------|--------------------|------------|--------------------|--| +| | Status | CW status for speech | CW status for data | Speech | Data | | +| 1 | None | - | - | - | - | | +| 2 | 1 Speech call(active) | active | - | CW offered | MT offered | | +| | | Not active | - | busy | MT offered | | +| 3 | 1 Speech call(on hold) | active | - | CW offered | MT offered | | +| | | Not active | - | busy | MT offered | | +| 4 | 1 Data call(active) | - | active | MT offered | MT offered | | +| | | | Not active | MT offered | MT offered | | +| 5 | 1 Speech call(on hold) via bearer A | active | active | CW offered | MT offered | | +| | | active | Not active | CW offered | MT offered | | +| | 1 Speech call(active) via bearer A | Not active | active | busy | MT offered | | +| | | Not active | Not active | busy | MT offered | | +| 6 | 1 Speech call(on hold) via bearer A | active | active | CW offered | MT offered | | +| | | active | Not active | busy | MT offered | | +| | 1 Data call(active) via bearer A | Not active | active | CW offered | MT offered | | +| | | Not active | Not active | busy | MT offered | | +| 7 | Multiparty via bearer A (2-5 remote parties: active) | active | - | CW offered | MT offered | | +| | | Not active | - | Busy | MT offered | | +| 8 | Multiparty via bearer A (2-5 remote parties: on hold) | active | - | CW offered | MT offered | | +| | | Not active | - | busy | MT offered | | +| 9 | 1 Speech call(active) via bearer A | active | active | CW offered | CW offered | | +| | | active | Not active | CW offered | CW offered | | +| | 1 Data call(active) via bearer B | Not active | active | busy | CW offered | | +| | | Not active | Not active | busy | busy | | +| 10 | 1 Speech call(on hold) via bearer A | active | active | CW offered | CW offered | | +| | | active | Not active | CW offered | CW offered | | +| | 1 Data call(active) via bearer B | Not active | active | busy | CW offered | | +| | | Not active | Not active | busy | busy | | +| 11 | 1 Speech call(on hold) via bearer A | active | active | CW offered | CW offered | | +| | | active | Not active | CW offered | CW offered | | +| | 1 Speech call(active) via bearer A | Not active | active | busy | CW offered | | +| | | Not active | Not active | busy | busy | | +| 12 | 2 Data call(active) | - | active | CW offered | CW offered | | +| | | - | Not active | busy | busy | | + +| Current Status | | | | Additional MT call | | +|-----------------------|-------------------------------------------------------|-----------------------------|---------------------------|---------------------------|-------------| +| No | Status | CW status for speech | CW status for data | Speech | Data | +| 13 | 1 Speech call(on hold) via bearer A | - | active | CW offered | CW offered | +| | 2 Data call(active) via bearer A and B | - | Not active | Busy | Busy | +| 14 | Multiparty via bearer A (2-5 remote parties: active) | active | active | CW offered | CW offered | +| | | active | Not active | CW offered | CW offered | +| | 1 Data call(active) via bearer B | Not active | active | busy | CW offered | +| | | Not active | Not active | busy | busy | +| 15 | Multiparty via bearer A (2-5 remote parties: on hold) | active | active | CW offered | CW offered | +| | | active | Not active | CW offered | CW offered | +| | 1 Data call(active) via bearer B | Not active | active | busy | CW offered | +| | | Not active | Not active | busy | busy | + +# Annex B (informative): Change history + +| TSG CN# | Spec | CR |
PS if the emergency session contains only media other than voice. | PS if first attempt in CS
CS if first attempt in PS - NOTE 7) | +| C | N | Y | Y or N | N | PS if ESFB is "Y" (NOTE 5).
Else CS or PS for another 3GPP RAT with EMS or ESFB set to "Y" if available and supported and if the emergency session includes at least voice.
Else PS for another 3GPP RAT with EMS or ESFB set to "Y" if available and supported if the emergency session contains only media other than voice. | PS if first attempt in CS
CS if first attempt in PS - NOTE 7) | +| D | Y | N | Y or N | Y or N | CS if the emergency session includes at least voice.
PS if available and EMS or ESFB is "Y" and emergency session contains only media other than voice. | PS if available and EMS or ESFB is "Y" | +| E | Y | Y | Y | Y | If the emergency session includes at least voice, follow rules in TS 22.101 [8] which say to use the same domain as for a non-EMC (NOTE 2)
PS if the emergency session contains only media other than voice. | PS if first attempt in CS
CS if first attempt in PS | +| F | Y | Y | Y or N | N | PS if ESFB is "Y" (NOTE 5).
Else PS for another 3GPP RAT with EMS if available and supported or CS, if the emergency session includes at least voice. | CS if first attempt in PS
PS for another 3GPP RAT if available and supported and EMS or ESFB is "Y" if first attempt in CS. | + +| G | Y | Y | N | Y | CS if the emergency session includes at least voice.
PS if the emergency session contains only media other than voice. | PS | +|---------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|-------------------------------------------------------------------------------------------------------------------------------|----| +| EMC = | Emergency Session. EMC includes also normal calls initiated in the CS domain that are treated by the CS CN as emergency calls. | | | | | | +| VoIMS = | Voice over IMS over PS sessions support as indicated by IMS Voice over PS session supported indication as defined in TS 23.401 [28], TS 23.060 [2] and TS 23.502 [49]. | | | | | | +| EMS = | IMS Emergency Services supported as indicated by Emergency Service Support indicator as defined in TS 23.401 [28], TS 23.060 [2], TS 23.501 [48] and TS 23.502 [49]. | | | | | | +| ESFB = | Emergency Services Fallback for 5GS as defined in TS 23.501 [48] and TS 23.502 [49]. | | | | | | +| NOTE 1: | If the UE selects the CS domain and initiates a normal call using the dialled local emergency number (see clause 7.1.2), and the UE enters limited service state (e.g. due to a Location Registration failing), then the UE camps on an acceptable cell (see TS 23.122 [41]) and may proceed with the EMC by initiating an emergency call in limited service state. | | | | | | +| NOTE 2: | Use of the same domain as for a non-EMC is restricted to UTRAN, E-UTRAN and NG-RAN access (e.g. excludes WLAN). | | | | | | +| NOTE 3: | This NOTE applies to a UE in dual registration mode as defined in TS 23.501 [48]. A dual registration mode UE that is registered to both EPC and 5GC assumes attachment, for the purpose of the "PS Attached" column, to whichever of EPC or 5GC indicates EMS as "Y". When both EPC and 5GC indicate EMS as "Y", the UE shall assume attachment to either EPC or 5GC based on implementation. A UE that is registered to both EPC and 5GC does not use emergency services fallback and ignores the ESFB condition when performing domain selection. | | | | | | +| NOTE 4: | The other 3GPP RAT for row C and row F can be any of UTRA, E-UTRAN connected to EPC, E-UTRA connected to 5GC or NR connected to 5GC that is supported by the UE and differs from the RAT to which the UE is currently attached in the PS domain (or is assumed to be attached based on NOTE 3). | | | | | | +| NOTE 5: | The condition 'ESFB is "Y"' only applies for a UE that is camped on or connected to 5GS via NR or via E-UTRA and that supports Emergency Services Fallback. In that case the emergency call will be provided over E-UTRAN or E-UTRA connected to 5GC as defined in procedures in TS 23.502 [49]. The condition 'ESFB is "Y"' is taken into consideration by the UE only when the network has indicated EMS = "N" for the RAT on which the UE is camping or connected. | | | | | | +| NOTE 6: | For 5GS, the value of the column "EMS" is for the RAT that UE is camped on or is connected to. | | | | | | +| NOTE 7: | As an implementation option, when the first attempt uses PS and fails for reasons other than related to IMS, the second attempt may use PS with a different 3GPP RAT. In this case the UE, can make a third attempt using CS. | | | | | | + +## H.6 eCall over IMS + +This clause details the domain priority and selection (see clause 7.3) for a UE that attempts to make an eCall over IMS session using E-UTRAN or NG-RAN radio access networks based on the availability of the CS or PS domains and the network support for IMS emergency, eCall over IMS and IMS voice over PS. + +The following table (Table H.2) defines these rules based on the UE (last 2 columns) for different initial conditions (first 4 columns) when an eCall over IMS session is initiated and when the UE is not in limited service state. + +**Table H.2: Domain Selection Rules for eCall over IMS session attempts for E-UTRAN or NG-RAN radio access networks** + +| | PS Available | VoIMS | EMS | ECL | First eCall Attempt | Second eCall Attempt | +|----------|--------------|--------|-----|-----|-----------------------|---------------------------------------------------------------------------| +| A | Y | Y | Y | Y | PS | PS on another PS RAT if available with EMS=Y and ECL=Y or CS if available | +| B | Y | Y | Y | N | CS if available | PS (UE establishes IMS emergency session) | +| C | Y | Y or N | N | N | CS if available | PS on another PS RAT if available with EMS=Y or EMS unknown | +| D | Y | N | Y | Y | PS or CS if available | CS if first attempt in PS
PS if first attempt in CS | +| E | Y | N | Y | N | CS if available | PS (UE establishes IMS emergency session) | +| F | N | | - | - | CS if available | | + +VoIMS = Voice over IMS over PS sessions support as indicated by IMS Voice over PS session supported indication as defined in TS 23.401 [28] and TS 23.502 [49]. +EMS = IMS Emergency Services supported as indicated by Emergency Service Support indicator as defined in TS 23.401 [28] and TS 23.501 [48] and TS 23.502 [49]. +ECL = eCall Over IMS support as indicated by the eCall support indicator defined in TS 23.401 [28] and TS 23.501 [48]. + +NOTE: If the E-UTRAN and NG-RAN cells available to the UE have different settings, the UE assumes "PS Available" and "ECL" apply to whichever cell is indicated (as defined in TS 23.401 [28] and TS 23.501 [48]) as providing eCall over IMS support. When support by more than one cell is indicated, a UE may select any cell according to the UE implementation. + +# --- Annex I (normative): IMS Emergency Services Using HRPD/EPC Network + +## I.1 cdma2000 HRPD/EPC Options + +The following options from the normative clauses of this TS are applicable in cdma2000 HRPD systems with an EPC core network: + +- 1) Clause 7.1.1, step 4 "The IP-CAN may support a UE indication that this request is for an emergency service". + +The following options from the normative clauses of this TS are not applicable in cdma2000 HRPD/EPC systems: + +- 1) Clause 4.1 "The P-CSCF serving the emergency call is the IMS network entity which may retrieve the location identifier from the IP-CAN". + +## --- I.2 Requirements on the HRPD/EPC Network as an IP-CAN + +For an emergency call over HRPD/EPC, the requirements on the IP CAN are specified in 3GPP2 X.S0057-A [39]. + +## --- I.3 Information Flows + +The informational flows for emergency calls over HRPD are provided in 3GPP2 X.S0057-A [39]. + +# --- Annex J (normative): IMS emergency services using WLAN access to EPC + +## J.1 General + +This annex includes additional clarifications when the IP-CAN corresponds to a WLAN access to EPC. + +Both trusted WLAN access (S2a) and Untrusted WLAN access (S2b) to EPC for emergency sessions are supported. + +NOTE: This annex only applies to EPC access using S2a or S2b. + +The UE may issue an Emergency session over WLAN access to EPC only when 3GPP access for emergency call is not possible or available (e.g. no 3GPP coverage). + +Further details on the procedures defined for WLAN access to EPC support of support emergency sessions are defined in TS 23.402 [29]. + +## --- J.2 UE specific behaviour + +Procedure for determining the list of emergency numbers: + +- In addition to the emergency numbers and associated types stored either on the USIM or on the user equipment specified in clause 10.1.1 of TS 22.101 [8], the UE shall use the stored Local Emergency Numbers List received from the 3GPP network to detect that the number dialled is an emergency number. +- If a UE has a SIM/USIM and has received a list of emergency numbers, and associated types via mobility management procedures as described in TS 24.301 [33] or TS 24.008 [13] when connected to the PLMN using GERAN, UTRAN, E-UTRAN or TS 24.501 [52] when connected to NG-RAN or non-3GPP access connected to 5GC, or, for a UE supporting access to 5GC using non-3GPP access, as specified in Annex L, the UE shall use this list to determine if the dialled digits correspond to an emergency call as long as the UE has determined that the list is valid (see clause 4.1). +- The UE may also determine that the dialled digits and associated types or URN information correspond to an emergency call based on the list of emergency numbers retrieved by one of the following means: + +NOTE: How the UE uses two lists (a list of emergency numbers and associated types or URN information received via mobility management procedures and a list of emergency numbers and associated types or URN information retrieved via the WLAN) is a stage 3 decision. + +- a) via Access Network Query Protocol (ANQP) procedures defined in IEEE Std 802.11 2012 [47] from the associated WLAN AP upon completing authentication with the trusted WLAN access to EPC, with management frame protection enabled. + - b) via a previous query to a DNS only when that DNS is in the same country as the UE and is an internal DNS server in the 3GPP network whose address is acquired from the ePDG; or + - c) via IKEv2 procedures from ePDG. +- The list of downloaded emergency numbers shall be deleted at country change or, if the particular list is only valid for a PLMN, see clause 10.4.1 of TS 22.101 [8]), at successful registration with a different PLMN. + +For the specific case where the UE has selected to make an emergency call over WLAN access to EPC (hence the UE has detected that the target URI or dialled digits correspond to an emergency sessions), the UE shall use the following procedures: + +- The UE shall establish an emergency PDN connection over WLAN and shall perform an IMS emergency registration before sending an IMS emergency session request. + +- The UE shall include any available location information in the IMS emergency session request. This is further detailed in TS 23.228 [1]. +- For the media supported during IMS emergency sessions, media codec and format support is specified in TS 26.114 [34]. +- For the support of DRVCC on emergency call on WLAN, see TS 23.237 [32]. + +A UE shall not establish an emergency PDN connection over WLAN if the UE initiated a normal (i.e. non-emergency) session and is subsequently informed by the network that the ongoing session is accepted by the network even though it is an emergency session. + +## J.3 High Level Procedures for IMS emergency calls + +For the high level procedures (as described in clause 7.1.1) the following statements apply for UE detected emergency calls when EPC access over WLAN is used: + +- the IP-CAN bearer resource is a PDN connection dedicated for emergency services. The TS 23.402 [29] describes how to indicate that a PDN connection request is for emergency; +- For registration requests received from an emergency PDN connection, the P-CSCF shall reject any IMS registration which is not for the emergency purpose. + +NOTE 1: When the IMS network detects that the UE is establishing an emergency session over WLAN access to EPC while the UE is not in its Home country, local policies in the Home IMS network may determine whether to nevertheless handle the emergency session + +For the high level procedures (as described in clause 7.1.2) the following statements apply for Non UE detectable emergency calls when WLAN access to EPC is used: + +- The P-CSCF may reject the session initiation request with an indication that this is an emergency session or may allow the session initiation request to continue. + +The following flow contains a high level description of the emergency service procedures performed over WLAN access to EPC when the UE can detect that an emergency PDN connection is being needed. This flow provides details (or references) related with WLAN access to EPC on top of the general procedure described in clause 7.1. + + + +``` + +sequenceDiagram + participant UE + participant IP-CAN + participant IMS + participant EC as Emergency Center or PSAP + + Note left of UE: 1. Detect Emergency session request + UE->>IP-CAN: + Note left of UE: 2. Release any PDN connection over SWu + UE->>IP-CAN: + Note left of UE: 3. & 4. Set up of an emergency PDN connection + UE->>IP-CAN: + Note left of UE: 5. P-CSCF Discovery + UE->>IMS: + Note left of UE: 6. IMS Registration + UE->>IMS: + Note left of UE: 7. Establish Emergency Session (and Bearer Resources) + UE->>EC: + +``` + +Sequence diagram for Terminal Detected Emergency Calls (WLAN access to EPC). The diagram shows the interaction between UE, IP-CAN, IMS, and Emergency Center or PSAP. The steps are: 1. Detect Emergency session request (UE to IP-CAN); 2. Release any PDN connection over SWu (UE to IP-CAN, dashed box); 3. & 4. Set up of an emergency PDN connection (UE to IP-CAN); 5. P-CSCF Discovery (UE to IMS); 6. IMS Registration (UE to IMS); 7. Establish Emergency Session (and Bearer Resources) (UE to Emergency Center or PSAP). + +Figure J.3: Terminal Detected Emergency Calls (WLAN access to EPC) + +The following steps are performed: + +1. Same as step 1 of Figure 7.1. +2. The UE releases any PDN connection it may have over untrusted access to EPC. +3. Void. +4. As described in TS 23.402 [29]: + - in the case of untrusted access, the UE selects an ePDG for emergency services and sets-up a PDN connection for emergency services; + - in the case of trusted access, the UE sets-up a PDN connection for emergency services. + +The UE is assigned an IP address at this stage. + +NOTE 2: No specific WLAN AP selection is carried out to support emergency services. + +5. Same as step 5 of Figure 7.1. +6. Same as step 6 of Figure 7.1. +7. Same as step 7 of Figure 7.1. + +## --- J.4 Location handling + +When a UE performs an emergency registration or initiates an emergency session over WLAN access to EPC the UE provides location information that is further defined in TS 23.228 [1]. + +If the operator policy requires network provided location using PCC-based solutions for the UE location, the P-CSCF may retrieve location information from the access network as defined in TS 23.203 [20] and includes it in the emergency session request, as described in TS 23.228 [1]. + +# --- Annex K (normative): Support of IMS emergency sessions for roaming users in deployments without IMS-level roaming interfaces + +## K.1 General + +This annex includes network impact and call flows for support of IMS emergency sessions for roaming users in deployments without IMS-level roaming interface between the P-CSCF in the VPLMN and the S-CSCF in the HPLMN. This annex is only applicable to UTRAN, E-UTRAN and NG-RAN access networks. + +IMS authentication is performed by linking the IMS registration to user's EPS or 5GS authentication based on the user's IP address and IMSI. This mechanism is similar to GIBA (GPRS-IMS bundled authentication) specified in TS 33.203 [44]. The P-CSCF performs the GIBA procedure over Gm with the UE as defined in TS 24.229 [19]. If this procedure is not supported, UE may perform anonymous emergency session. A callback number for the user may also be retrieved via the PCRF or PCF. + +## --- K.2 Functional description + +### K.2.1 General + +This clause lists the additional functionality in the network that is required to support IMS emergency sessions for roaming users in network deployments where there are no IMS-level roaming interfaces between the serving IMS network and the home IMS network. + +### K.2.2 P-CSCF + +In addition to the functionality described in clause 6.2.1, the P-CSCF supports the functionality listed below: + +- P-CSCF shall be able to retrieve the UE/user's IMSI, IMEI and MSISDN (if available) from the PCRF/PCF. +- P-CSCF may support the GIBA procedure over Gm as defined in TS 24.229 [19]. +- P-CSCF may verify the IMSI/IMEI provided in the SIP REGISTER message against the IMSI/IMEI provided by the PCRF or PCF. + +### K.2.3 PCRF or PCF + +- PCRF or PCF shall be able to provide the IMSI, the ME Identity (IMEISV), and MSISDN (if available) over Rx to the P-CSCF. + +### K.2.4 PGW or SMF/UPF + +- PGW or SMF/UPF shall be able to prevent "source IP address spoofing" for IMS emergency PDN connections if GIBA authentication, defined in TS 33.203 [44], is used as part of emergency IMS registration. + +### K.2.4 HSS or UDM + +- The EPS user subscription at the HSS should contain exactly one MSISDN which should be the same as that in the IMS profile. +- The 5GS user subscription at the UDM should contain exactly one MSISDN based GPSI which should be the same as that in the IMS profile. + +## K.3 IMS Emergency Registration and Session Establishment + +The call flow for support of IMS emergency sessions for roaming users in deployments without IMS-level roaming interfaces for UTRAN, E-UTRAN or NG-RAN access networks is described in Figure K.3-1. + + + +``` + +sequenceDiagram + participant UE + participant AMF as MME/SGSN (AMF) + participant SMF as SGW/PGW (SMF) + participant PCRF as PCRF (PCF) + participant P-CSCF + participant HSS as HSS (UDM) + + Note over VPLMN: VPLMN + Note over HPLMN: HPLMN + + UE->>AMF: 1. Attach request (Em) or PDN Connectivity Req (Em) +(PDU Session Establishment Request (Em)) + AMF->>HSS: 2. Retrieve IMSI/SUPI, IMEI/PEI, MSISDN + HSS-->>AMF: + AMF->>SMF: 3. Create Session (Em, IMSI, IMEI, MSISDN) +(Nsmf_PDUSession_CreateSMContextRequest (Em, SUPI, PEI, GPSI)) + SMF->>PCRF: 4. IP-CAN session establishment. IMSI/SUPI, IMEI/ +PEI, MSISDN/GPSI passed on to PCRF or PCF + PCRF-->>SMF: + SMF-->>AMF: 5. Completion of Attach or UE requested PDN connectivity procedure +(Completion of PDU Session Establishment procedure) + AMF-->>UE: + UE->>P-CSCF: 6. SIP REGISTER (UserID-1) + P-CSCF->>PCRF: 7. P-CSCF retrieves IMSI, IMEI, MSISDN from the PCRF or +PCF upon Rx or Npcf_PolicyAuthorization session est. + PCRF-->>P-CSCF: + P-CSCF-->>UE: 8. 420 (unsupported-header; sec-agree) or rejection + Note right of UE: A. + UE->>P-CSCF: 9. SIP REGISTER (UserID-2; no Auth header) + P-CSCF-->>UE: 10. OK + UE->>P-CSCF: 11. SIP INVITE (UserID-3) + P-CSCF->>HSS: 12. SIP INVITE (userID-3, CallbackPar) + Note right of UE: B. + UE->>P-CSCF: 13. SIP INVITE (anonymous) + P-CSCF->>PCRF: 14. P-CSCF retrieves IMSI/SUPI, IMEI/PEI, +MSISDN from the PCRF/PCF upon Rx session est. + PCRF-->>P-CSCF: + P-CSCF->>HSS: 15. SIP INVITE (userID-4, CallbackPar) + Note right of UE: C. + UE: 16. UE attempts an emergency call in CS domain + +``` + +Sequence diagram showing IMS Emergency Session Establishment between UE, AMF, SMF, PCRF/PCF, P-CSCF, and HSS/UDM across VPLMN and HPLMN domains. + +Figure K.3-1: IMS Emergency Session Establishment in deployments without IMS roaming interface between VPLMN and HPLMN + +1. UE establishes a PDN connection (for EPC) or PDU session (for 5GC) for IMS emergency services. +2. For EPC, IMSI and IMEI(SV) are retrieved from the UE. The MSISDN (if available) is provided by the HSS. + +For 5GC, the SUPI and PEI are retrieved from the UE context stored in the AMF; the SUPI needs to contain an IMSI and the PEI needs to contain an IMEI(SV). The GPSI (if available) is provided by the UDM; the GPSI needs to contain an MSISDN. + +3. For EPC: MME/SGSN sends a Create Session Request towards the PGW including the IMSI, the IMEI(SV) and the MSISDN (if available) as specified in TS 23.401 [28]. + +For 5GS: AMF sends a Nsmf\_PDUSession\_CreateSMContextRequest towards the SMF/UPF including the SUPI, the PEI and the GPSI (if available) as specified in TS 23.502 [49]. + +4. For EPC, PGW establishes an IP-CAN session with the PCRF as described in TS 23.401 [28] and TS 23.203 [20]. The IP-CAN session is identified with UE's IPv4 address or IPv6 prefix associated with the PDN connection for IMS emergency services. The IMSI, the IMEI(SV) and the MSISDN (if available) are passed to the PCRF as part of the IP-CAN session establishment. + +For 5GC, SMF establishes an SM Policy Association with the PCF as described in TS 23.502 [49] and TS 23.503 [51]. The PDU session is identified with UE's IPv4 address or IPv6 prefix. The SUPI, PEI, GPSI (if available) and emergency DNN are passed to the PCF. + +5. The Attach or UE requested PDN connection procedure (for EPC) or the PDU Session Establishment procedure (for 5GC) is being completed. + +Steps 6-12 apply if the UE performs IMS Emergency Registration, based on conditions specified in clause 4.1 e.g. UE is aware that it has sufficient IMS authentication material. + +6. UE initiates IMS emergency registration by sending a SIP REGISTER (UserID-1) message. The UserID-1 parameter is an IMPI and optionally an IMPU. +- 7a. Upon reception of the SIP REGISTER message the P-CSCF determines that there is no IMS NNI to the user's HPLMN. The P-CSCF requests the PCRF or PCF for EPS-level identities (e.g. IMSI, IMEI(SV), MSISDN) in the Rx session establishment request. For 5GC, P-CSCF may use the Npcf\_PolicyAuthorization service as described in TS 23.502 [49] and TS 23.503 [51] instead of the Rx interface. +- 7b. For EPC, the PCRF performs session binding based on the UE's IP address/prefix (as defined in clause 6.1.1.2 of TS 23.203 [20]) and provides one or more EPS-level identities and the MSISDN (if available) to the P-CSCF. + +For 5GC, the PCF performs session binding based on the UE's IP address/prefix (as defined in TS 23.503 [51]). If the Rx interface is used, the PCF extracts IMSI, IMEI(SV), and if available MSISDN from SUPI, PEI, and GPSI, respectively and provides the former identities to the P-CSCF. If the Npcf\_PolicyAuthorization service is used, the PCF provides SUPI, PEI, and if available GPSI, and the P-CSCF extracts IMSI, IMEI(SV), and if available MSISDN from those identities. + +8. Based on operator configuration and if the network supports the GIBA procedure over Gm as defined in TS 24.229 [19], the P-CSCF responds with a 420 response with sec-agree value listed in the unsupported header field. Otherwise it rejects the IMS registration request with SIP 403 (Forbidden) as defined in TS 24.229 [19]. If the network supports anonymous IMS emergency sessions, P-CSCF may add an indication whether it supports anonymous IMS emergency sessions to the 403 or 420 response. + +Steps 9-12 apply if the P-CSCF has responded with a 420 response in step 8 and if the UE supports GIBA procedure as part of emergency IMS registration (irrespective of whether indication of anonymous IMS emergency session support was included in step 8). + +9. UE according to TS 24.229 [19], performs a new initial registration by sending a SIP REGISTER (UserID-2, IMEI) message and without inclusion of the Authorization header field. UserID-2 is an a public user identity derived from IMSI. P-CSCF may verify the IMSI/IMEI provided by the PCRF or PCF in step 7b against the IMSI/IMEI derived from the public user identity provided by the UE, prior to accepting the SIP REGISTER message. +10. P-CSCF accepts the registration with 200 OK and provides a tel-URI based on the MSISDN (if available) received from PCRF in step 7b to the UE. From the UE point of view, the procedure is the same as specified for GIBA (GPRS-IMS bundled authentication) procedures in TS 24.229 [19]. + +11. UE then attempts an IMS emergency session by sending a SIP INVITE (UserID-3) message. UserID-3 is set to UE's public identity (i.e. MSISDN as Tel-URI received in step 10). +12. The P-CSCF verifies whether the UserID-3 indicated in the SIP INVITE message complies with the tel-URI that was provided to the UE. If compliant, P-CSCF forwards the SIP INVITE towards the PSAP including a callback parameter (CallBackPar) in the form of TEL-URI derived from the MSISDN received in step 7. The procedure stops here. + +Steps 13-15 apply if the UE attempts anonymous IMS emergency session, e.g. the P-CSCF has responded in step 8 with a 403 (Forbidden) response, or the P-CSCF has responded in step 8 with 420 response and the UE does not support GIBA as part of emergency IMS registration, or if the UE skipped IMS emergency registration: + +13. The UE may attempt an unauthenticated IMS emergency session including an "anonymous user" parameter in the SIP INVITE message. +14. Upon reception of the SIP INVITE the P-CSCF either internally retrieves the one or more EPS-level identities and the MSISDN (if available) that were received in step 7b, or performs step 7 again. +15. The P-CSCF forwards the SIP INVITE (UserID-4, CallBackPar) towards the PSAP. UserID-4 is derived from one of the EPS-level identities received in step 7b. CallBackPar in the form of TEL-URI is derived from the MSISDN received in step 7b. The procedure stops here. + +Step 16 applies if the UE attempts an emergency call in the CS domain as specified in clause 4.1: + +16. Subsequent to the IMS registration failure in step 8 or subsequent to an anonymous SIP INVITE attempt the UE may attempt an emergency call in the CS domain. + +## --- K.4 Non UE detectable Emergency Session + +In addition to clause 7.1.2, the following is applicable for this scenario: + +- It is recommended that local emergency call numbers are provided to the UE according to the procedures specified in TS 24.501 [52], TS 24.301 [33], TS 24.008 [13] or Annex J.2. This helps to reduce the number of non-UE detected emergency numbers even for those PLMNs where only a subset of the local emergency numbers can be downloaded to the UEs. +- When the UE registers in the IMS, the P-CSCF may retrieve the VPLMN-ID of the UE as described in clause W.3 of TS 23.228 [1] and may access a database to obtain a list of all local emergency numbers for the visited PLMN, if not already available in the P-CSCF. These numbers are used for detection of non UE detectable emergency calls during IMS session setup. The database of PLMN- specific emergency numbers and its interface with the P-CSCF are not specified by 3GPP. + +# --- Annex L (normative): IMS emergency services using non-3GPP access to 5GC + +## L.1 General + +This annex includes additional clarifications when the IP-CAN corresponds to a non-3GPP access to 5GC. + +Trusted and untrusted non-3GPP access to 5GC for emergency sessions are supported. + +The UE may issue an Emergency session over non-3GPP access to 5GC only when 3GPP access for emergency call is not possible or available (e.g. no 3GPP coverage). + +Further details on the procedures defined for non-3GPP access to 5GC support of support emergency sessions are defined in TS 23.502 [49]. + +## --- L.2 UE specific behaviour + +Procedure for determining the list of emergency numbers: + +- In addition to the emergency numbers and associated types stored either on the USIM or on the user equipment specified in clause 10.1.1 of TS 22.101 [8], the UE shall use the stored Local Emergency Numbers List received from the 3GPP network to detect that the number dialled is an emergency number. +- If a UE has a SIM/USIM and has received a list of emergency numbers and associated types or URN information via mobility management procedures as described in TS 24.301 [33] and TS 24.008 [13] when connected to the PLMN using GERAN, UTRAN, E-UTRAN, or TS 24.501 [52] when connected to NG-RAN or non-3GPP access connected to 5GC, or, for a UE supporting access to EPC via WLAN, as specified in Annex J, the UE shall use this list to determine if the dialled digits correspond to an emergency call as long as the UE has determined that the list is valid (see clause 4.1). + +NOTE: How the UE uses two lists (a list of emergency numbers and associated types or URN information received via mobility management procedures and , for a UE supporting access to EPC via WLAN, a list as specified in Annex J) is a stage 3 decision. + +- The list of downloaded emergency numbers shall be deleted at country change or, if the particular list is only valid for a PLMN (see clause 10.4.1 of TS 22.101 [8]), at successful registration with a different PLMN. + +For the specific case where the UE has selected to make an emergency call over non-3GPP access to 5GC (hence the UE has detected that the target URI or dialled digits correspond to an emergency sessions), the UE shall use the following procedures: + +- The UE shall establish an emergency PDU session over non-3GPP and shall perform an IMS emergency registration before sending an IMS emergency session request. +- The UE shall include any available location information in the IMS emergency session request. This is further detailed in TS 23.228 [1]. +- For the media supported during IMS emergency sessions, media codec and format support is specified in TS 26.114 [34]. + +A UE shall not establish an emergency PDU session over non-3GPP access if the UE initiated a normal (i.e. non-emergency) session and is subsequently informed by the network that the ongoing session is accepted by the network even though it is an emergency session. + +## L.3 High Level Procedures for IMS emergency calls + +For the high-level procedures (as described in clause 7.1.1) the following statements apply for UE detected emergency calls when 5GC access over non-3GPP access is used: + +- the IP-CAN bearer resource is a PDU session dedicated for emergency services. TS 23.502 [49] describes how to indicate that a PDU Session Request is for emergency. +- For registration requests received from an emergency PDU session, the P-CSCF shall reject any IMS registration which is not for the emergency purpose. + +NOTE 1: When the IMS network detects that the UE is establishing an emergency session over non-3GPP access to 5GC while the UE is not in its Home country, local policies in the Home IMS network may determine whether to nevertheless handle the emergency session. + +For the high-level procedures (as described in clause 7.1.2) the following statements apply for Non UE detectable emergency calls when non-3GPP access to 5GC is used: + +- The P-CSCF may reject the session initiation request with an indication that this is an emergency session or may allow the session initiation request to continue. + +The following flow contains a high-level description of the emergency service procedures performed over non-3GPP access to 5GC when the UE can detect that an emergency PDU session is being needed. This flow provides details (or references) related with non-3GPP access to 5GC on top of the general procedure described in clause 7.1. + + + +``` + +sequenceDiagram + participant UE + participant IP-CAN + participant IMS + participant PSAP as Emergency Center or PSAP + + Note over UE: 1. Detect Emergency session request + rect rgb(200, 200, 200) + Note over UE, IP-CAN: 2. Release any PDU session over non-3GPP access + end + Note over UE, IP-CAN: 3. & 4. Set up of an emergency PDU session + Note over UE, IP-CAN: 5. P-CSCF Discovery + Note over UE, IMS: 6. IMS Registration + Note over UE, PSAP: 7. Establish Emergency Session (and PDU session Resources) + +``` + +Sequence diagram for Terminal Detected Emergency Calls (non-3GPP access to 5GC). The diagram shows interactions between UE, IP-CAN, IMS, and Emergency Center or PSAP. The steps are: 1. Detect Emergency session request; 2. Release any PDU session over non-3GPP access; 3. & 4. Set up of an emergency PDU session; 5. P-CSCF Discovery; 6. IMS Registration; 7. Establish Emergency Session (and PDU session Resources). + +**Figure L.3: Terminal Detected Emergency Calls (non-3GPP access to 5GC)** + +The following steps (numbering being the same as in figure 7.1) are performed: + +1. Same as step 1 of Figure 7.1. +2. In some exceptional cases (e.g. in congestion situation), the UE may release some PDU session it may have over non-3GPP access to 5GC. +3. Void (no "bearer registration" as described in step 3 of Figure 7.1). +4. As described in TS 23.502 [49]: + - in the case of untrusted access, the UE selects an N3IWF as for accessing regular services and sets-up a PDU session for emergency services; + +- in the case of trusted access, the UE sets-up a PDU session for emergency services. + +The UE is assigned an IP address at this stage. + +NOTE 2: When non-3GPP access is WLAN, no specific WLAN AP selection is carried out to support emergency services. + +5. Same as step 5 of Figure 7.1. +6. Same as step 6 of Figure 7.1. +7. Same as step 7 of Figure 7.1, except that eCall is not supported via untrusted non-3GPP access. + +## --- L.4 Location handling + +When a UE performs an emergency registration or initiates an IMS emergency session over untrusted non-3GPP access to EPC the UE provides location information that is further defined in TS 23.228 [1]. + +For untrusted non-3GPP access to 5GC, provided location information can only correspond to the UE IP address seen by the N3IWF and used for traffic destined towards the UE. + +# Annex M (informative): Change history + +| Change history | | | | | | | | | +|----------------|---------|-----------|------|-----|-----|-----------------------------------------------------------------------------------------------------------------------------|---------------|--| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | | +| 2010-12 | SA#50 | SP-100694 | 0182 | 3 | B | Retrieval of reference location for emergency session routed via the S-CSCF | 11.0.0 | | +| 2011-01 | - | - | - | - | - | Update of LTE logo to LTE-Advanced logo | 11.0.1 | | +| 2011-03 | SA#51 | SP-110063 | 0186 | 1 | A | PSAP call back handling in S-CSCF | 11.1.0 | | +| 2011-09 | SA#53 | SP-110455 | 0189 | 1 | A | Correction of emergency procedures | 11.2.0 | | +| 2011-09 | SA#53 | SP-110469 | 0190 | 1 | C | Emergency location information for fixed broadband access | 11.2.0 | | +| 2011-12 | SA#54 | SP-110740 | 0192 | 1 | F | Media support during an IMS emergency session | 11.3.0 | | +| 2011-12 | SA#54 | SP-110730 | 0197 | 1 | A | Correction of Emergency procedures | 11.3.0 | | +| 2011-12 | SA#54 | SP-110737 | 0201 | 1 | A | Clarification on S-CSCF handling when receiving emergency session from AS. | 11.3.0 | | +| 2011-12 | SA#54 | SP-110869 | 0204 | 5 | A | Clarifications on non UE detectable emergency call | 11.3.0 | | +| 2011-12 | SA#54 | SP-110740 | 0205 | 2 | B | Media support on PSAP callback | 11.3.0 | | +| 2012-03 | SA#55 | SP-120080 | 0207 | 1 | B | Codecs supported for IMS emergency sessions | 11.4.0 | | +| 2012-03 | SA#55 | SP-120081 | 0208 | 1 | B | Support of Network-provided Location for IMS functionality | 11.4.0 | | +| 2012-03 | SA#55 | SP-120080 | 0212 | 3 | B | Domain Selection Rules for IMSESOM with E-UTRAN and UTRAN Access | 11.4.0 | | +| 2012-06 | SA#56 | SP-120250 | 0215 | 1 | F | Handling of Emergency Registrations at Home IMS | 11.5.0 | | +| 2012-06 | SA#56 | SP-120250 | 0216 | 1 | F | S-CSCF and AS in Emergency Calls | 11.5.0 | | +| 2012-12 | SA#58 | SP-120250 | 0220 | 1 | A | Defining S-CSCF procedures for registration and emergency registration relationships | 11.6.0 | | +| 2013-06 | SA#60 | SP-130309 | 0223 | 1 | F | Domain selection before UE detectable emergency session | 11.7.0 | | +| 2013-06 | SA#60 | SP-130309 | 0226 | 2 | F | Domain selection in the event emergency bearer services are not supported | 11.7.0 | | +| 2013-09 | SA#61 | SP-130367 | 0232 | 2 | A | Requirement Alignment for emergency registration and call back | 11.8.0 | | +| 2013-09 | SA#61 | SP-130376 | 0234 | 1 | C | Requirement Alignment for call back | 11.8.0 | | +| 2013-12 | SA#62 | SP-130518 | 0251 | 1 | A | Treatment of a 380 Response for an undetected IMS Emergency Call | 11.9.0 | | +| 2014-03 | SA#63 | SP-140097 | 0259 | 1 | A | Non UE detected emergency call correction when the retry attempt is made in CS domain | 11.10.0 | | +| 2014-03 | SA#63 | SP-140098 | 0261 | - | A | Clarification when using a private network for emergency calls | 11.10.0 | | +| 2014-06 | SA#64 | SP-140247 | 0264 | 3 | A | 380 - Emergency call clarification | 11.11.0 | | +| 2014-09 | SA#65 | - | - | - | - | Update to Rel-12 version (MCC) | 12.0.0 | | +| 2015-03 | SA#67 | SP-150109 | 0275 | 1 | F | Correction to support of I-WLAN in TS 23.167 | 12.1.0 | | +| 2015-09 | SA#69 | SP-150503 | 0279 | 2 | B | Location to Support Emergency services over WLAN access to EPC | 13.0.0 | | +| 2015-09 | SA#69 | SP-150503 | 0280 | 2 | B | Introduction of the Support of Emergency services over WLAN access to EPC | 13.0.0 | | +| 2015-12 | SA#70 | SP-150614 | 0281 | - | F | Clarification on the UE behavior when initiates the emergency call | 13.1.0 | | +| 2016-03 | SA#71 | SP-160162 | 0283 | - | F | Correction of 3GPP2 specification reference | 13.2.0 | | +| 2016-06 | SA#72 | SP-160299 | 0284 | 9 | B | eCall over IMS - Initial MSD | 14.0.0 | | +| 2016-06 | SA#72 | SP-160299 | 0286 | 5 | B | Domain Selection for eCall Over IMS | 14.0.0 | | +| 2016-06 | SA#72 | SP-160299 | 0287 | 2 | B | Transfer of Updated MSD for eCall Over IMS | 14.0.0 | | +| 2016-06 | SA#72 | SP-160302 | 0289 | 2 | B | Support for Sh in LRF for NPLI, and Support for UE updated Location mid-emergency session over emergency signalling channel | 14.0.0 | | +| 2016-06 | SA#72 | SP-160302 | 0292 | 3 | B | WLAN to CS session continuity for Emergency call over WLAN | 14.0.0 | | +| 2016-06 | SA#72 | SP-160302 | 0294 | 3 | B | Determine of Emergency number for call over WLAN | 14.0.0 | | +| 2016-06 | SA#72 | SP-160304 | 0295 | 3 | C | Support of IMS emergency sessions for roaming users in deployments without IMS-level roaming interfaces | 14.0.0 | | +| 2016-09 | SA#73 | SP-160659 | 0282 | 4 | B | Providing subscriber ID in case of anonymous emergency calls | 14.1.0 | | +| 2016-09 | SA#73 | SP-160652 | 0296 | 2 | B | Support for dispatchable civic location for indoor environments for North American. | 14.1.0 | | +| 2016-09 | SA#73 | SP-160647 | 0297 | 1 | F | Editorial change to Transfer of Updated MSD for eCall Over IMS call flow | 14.1.0 | | +| 2016-09 | SA#73 | SP-160658 | 0299 | 1 | B | Indication for support of anonymous IMS emergency sessions | 14.1.0 | | +| 2016-09 | SA#73 | SP-160651 | 0300 | 3 | C | Capturing solution for non UE detectable emergency call for S8 Home routing | 14.1.0 | | +| 2016-09 | SA#73 | SP-160647 | 0301 | 2 | F | Clarifications when inband is used by a UE to convey MSD | 14.1.0 | | +| 2016-09 | SA#73 | SP-160647 | 0302 | - | F | Definition for eCall Over IMS | 14.1.0 | | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|-------------------------------------------------------------------------------------------------------------|---------------| +| 2016-09 | SA#73 | SP-160654 | 0303 | 2 | B | Allowing ICS MSC to interact with IMS for IMS emergency call handling. | 14.1.0 | +| 2016-12 | SA#74 | SP-160817 | 0305 | 3 | F | Update with SEW2 capabilities | 14.2.0 | +| 2016-12 | SA#74 | SP-160816 | 0306 | 1 | F | Correction from IMPI to IMPU | 14.2.0 | +| 2016-12 | SA#74 | SP-160817 | 0311 | 3 | F | Correction to emergency number determination for call over WLAN | 14.2.0 | +| 2016-12 | SA#74 | SP-160817 | 0312 | - | F | Enable use of SUPL to locate a UE with WLAN Access | 14.2.0 | +| 2016-12 | SA#74 | SP-160817 | 0313 | 2 | F | Unsolicited Provision of UPLI by a UE for WLAN Access | 14.2.0 | +| 2017-03 | SA#75 | SP-170053 | 0314 | 2 | F | Clarification of functionality for interconnection of emergency call over II-NNI | 14.3.0 | +| 2017-03 | SA#75 | SP-170079 | 0315 | 1 | F | Alignment of emergency procedures | 14.3.0 | +| 2017-06 | SA#76 | SP-170367 | 0316 | 1 | F | Downloading emerg number from ePDG | 14.4.0 | +| 2017-09 | SA#77 | SP-170723 | 0318 | - | F | Clarification for voice domain selection rules applicability in Annex H | 14.5.0 | +| 2017-12 | SA#78 | SP-170919 | 0319 | 2 | B | Support of IMS Emergency Calls for NG-RAN access to 5GS | 15.0.0 | +| 2018-03 | SA#79 | SP-180094 | 0320 | 3 | F | Emergency services over 5GC via untrusted non-3GPP access | 15.1.0 | +| 2018-03 | SA#79 | SP-180094 | 0321 | 2 | F | Handling of emergency sessions over untrusted N3GPP access in 5GS | 15.1.0 | +| 2018-03 | SA#79 | SP-180094 | 0324 | 1 | F | Delivery of local emergency numbers in NAS | 15.1.0 | +| 2018-03 | SA#79 | SP-180094 | 0325 | 2 | F | Addition of Emergency Services Support using Fallback to Domain Selection Rules | 15.1.0 | +| 2018-06 | SA#80 | SP-180479 | 0326 | 1 | F | Clarification on Domain Selection for Emergency Service. | 15.2.0 | +| 2018-06 | SA#80 | SP-180475 | 0327 | 1 | F | Domain selection for eCall over IMS | 15.2.0 | +| 2018-06 | SA#80 | SP-180475 | 0329 | - | F | Correction on domain selection for eCall over IMS | 15.2.0 | +| 2018-06 | SA#80 | SP-180475 | 0330 | 2 | F | Correction to NOTE 5 in domain selection for Emergency services | 15.2.0 | +| 2018-09 | SA#81 | SP-180712 | 0331 | 2 | F | Update on Domain Selection Rules for emergency session attempts | 15.3.0 | +| 2018-09 | SA#81 | SP-180712 | 0332 | - | F | UE handling of emergency numbers list when using untrusted non-3GPP access to 5GC | 15.3.0 | +| 2018-09 | SA#81 | SP-180711 | 0334 | - | A | Correct conditions for using valid local emergency number list | 15.3.0 | +| 2018-09 | SA#81 | SP-180712 | 0335 | - | F | Domain selection for dual registration mode UE | 15.3.0 | +| 2018-09 | SA#81 | SP-180712 | 0336 | 2 | F | Support of eCall and emergency call when eUTRAN is connected to 5GS and EPS | 15.3.0 | +| 2018-12 | SA#82 | SP-181083 | 0337 | 1 | F | Correct procedures for obtaining local emergency number list | 15.4.0 | +| 2018-12 | SA#82 | SP-181083 | 0338 | 1 | F | Correct validity of local emergency number list | 15.4.0 | +| 2018-12 | SA#82 | SP-181083 | 0339 | 1 | F | Correcting usage of emergency service indication and emergency session indication | 15.4.0 | +| 2018-12 | SA#82 | SP-181083 | 0341 | - | C | More Flexible Domain selection for Emergency Calls using the PS Domain | 15.4.0 | +| 2019-09 | SA#85 | SP-190604 | 0346 | 2 | F | Correcting principle stating that procedures for untrusted access are to be used even over trusted WLAN | 15.5.0 | +| 2019-09 | SA#85 | SP-190609 | 0344 | 1 | F | Enabling emergency call using trusted non-3GPP access to 5GC | 16.0.0 | +| 2019-12 | SA#86 | SP-191089 | 0350 | 3 | F | Support of IMS emergency sessions for roaming users in 5GS deployments without IMS-level roaming interfaces | 16.1.0 | +| 2020-07 | SA#87 | SP-200420 | 0355 | - | A | Correction for IMS Emergency Registration and Session Establishment | 16.2.0 | +| 2020-07 | SA#87 | SP-200552 | 0357 | 1 | C | Domain selection for support of NG-eCall over NR | 16.2.0 | +| 2020-12 | SA#90E | SP-200959 | 0358 | 1 | F | Correction of reference for Sh interface | 16.3.0 | +| 2021-06 | SA#92E | SP-210332 | 0362 | 1 | F | NG eCall domain selection corrections | 16.4.0 | \ No newline at end of file diff --git a/marked/Rel-16/23_series/23172/00504fc688ebcf131ccbeff94dfc9939_img.jpg b/marked/Rel-16/23_series/23172/00504fc688ebcf131ccbeff94dfc9939_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b8ba0ed78cbf715f4706b1c21c9efd729285870d --- /dev/null +++ b/marked/Rel-16/23_series/23172/00504fc688ebcf131ccbeff94dfc9939_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:605cdfb36c8b6c9e983d0bcf92fffbabdf1ea523502d1c85d4e4ba995f35e26e +size 66029 diff --git a/marked/Rel-16/23_series/23172/00942e7d6db56fd4fbd5f45bdbad7fdb_img.jpg b/marked/Rel-16/23_series/23172/00942e7d6db56fd4fbd5f45bdbad7fdb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..98bc72e5591a1df7611ef046771adeb62b85990c --- /dev/null +++ b/marked/Rel-16/23_series/23172/00942e7d6db56fd4fbd5f45bdbad7fdb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aa2a3b764864a412c8997a2a07f405d7b8f8c72bf1a6ca91383ff263470a5e0e +size 17110 diff --git a/marked/Rel-16/23_series/23172/06da11ab76cacc38bbcd714e437797ea_img.jpg b/marked/Rel-16/23_series/23172/06da11ab76cacc38bbcd714e437797ea_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5d1edaf95fafa30a12dca36b31c754ce62fcecca --- /dev/null +++ b/marked/Rel-16/23_series/23172/06da11ab76cacc38bbcd714e437797ea_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:20a8b675e7cacb689b8c4b8c7e2f1d9f2650c132ee052fe23f7e0a65f09d42aa +size 9833 diff --git a/marked/Rel-16/23_series/23172/0a73b03fba21af142d619a9a662e6490_img.jpg b/marked/Rel-16/23_series/23172/0a73b03fba21af142d619a9a662e6490_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3ab41090bfcf8c12f5df726b305421b31d685a71 --- /dev/null +++ b/marked/Rel-16/23_series/23172/0a73b03fba21af142d619a9a662e6490_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6b56fbcc1734716a88c87e031d0c74fe35401257324d4d55e2394eaf56925def +size 142258 diff --git a/marked/Rel-16/23_series/23172/144e1d61e8738b22dcf4a683f869ac6f_img.jpg b/marked/Rel-16/23_series/23172/144e1d61e8738b22dcf4a683f869ac6f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c97e7098a1caba85acd1026ab0dd44ea7cc2c85b --- /dev/null +++ b/marked/Rel-16/23_series/23172/144e1d61e8738b22dcf4a683f869ac6f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9c130bef6bf871012e695e198ff377f5e15e71c530a2cc2465a0562a2bcddce1 +size 16830 diff --git a/marked/Rel-16/23_series/23172/187d05bf7ead21e1394b61320d8b3632_img.jpg b/marked/Rel-16/23_series/23172/187d05bf7ead21e1394b61320d8b3632_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0c2cd1657689cfa8fe0fe6599c05ab9e916792ee --- /dev/null +++ b/marked/Rel-16/23_series/23172/187d05bf7ead21e1394b61320d8b3632_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:168206fd862299f513b8e7abb346247565efe9d921f9b384b2988ce6bc1ac61f +size 152590 diff --git a/marked/Rel-16/23_series/23172/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/marked/Rel-16/23_series/23172/1a827b10290f33d4fec04d0e8ef7a897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5e20fb5340b7c633ebab929cd0f731e4dc3d8a98 --- /dev/null +++ b/marked/Rel-16/23_series/23172/1a827b10290f33d4fec04d0e8ef7a897_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c21fbfaf6d9e3f513f33c088dac636d0353480f7547761141a00d9bf52472c36 +size 67226 diff --git a/marked/Rel-16/23_series/23172/21ad58fee90f2be50708ff541d225507_img.jpg b/marked/Rel-16/23_series/23172/21ad58fee90f2be50708ff541d225507_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ac77f09cd96c3564a827bd476e72de0c96b3f435 --- /dev/null +++ b/marked/Rel-16/23_series/23172/21ad58fee90f2be50708ff541d225507_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d6b4f38cedc93cb9c2e83d61bfe75288bc69c284a0a65992365d575219a6a05e +size 74758 diff --git a/marked/Rel-16/23_series/23172/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/Rel-16/23_series/23172/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8f16d05690c93ca286c75c4a4bd1d384f230378a --- /dev/null +++ b/marked/Rel-16/23_series/23172/27b06ec9f42b5d727a2630f61a5f1861_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1b2c8f65143b277ae6efd6c4bf601b5d83cd67f481b4ac0318feb89d55cbf6a3 +size 23486 diff --git a/marked/Rel-16/23_series/23172/28d75f39a24203712ee907b32cf0bbe5_img.jpg b/marked/Rel-16/23_series/23172/28d75f39a24203712ee907b32cf0bbe5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d99e044ce89c22e93f488dfad949a69cef504569 --- /dev/null +++ b/marked/Rel-16/23_series/23172/28d75f39a24203712ee907b32cf0bbe5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:67e61ca07f8fb4875e89bc681353da76a9fcc755bd2aa0a3112a40dce26c7651 +size 69715 diff --git a/marked/Rel-16/23_series/23172/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg b/marked/Rel-16/23_series/23172/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..99f9ae0911a018bd5242dc78ca650283cde57ecd --- /dev/null +++ b/marked/Rel-16/23_series/23172/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:43f3c1165e241514542bf6931a8ad3e7bf59824ebdc202766c1538a78c61bc25 +size 59884 diff --git a/marked/Rel-16/23_series/23172/2ba086df3506f81bae3a9b53725dcfea_img.jpg b/marked/Rel-16/23_series/23172/2ba086df3506f81bae3a9b53725dcfea_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..93c615bb541f36b3a513faaf218a0f1e0e9febd8 --- /dev/null +++ b/marked/Rel-16/23_series/23172/2ba086df3506f81bae3a9b53725dcfea_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5d531d62514cdcee3543496538f1a177a1422debc8f138d640484600dc94c58d +size 9258 diff --git a/marked/Rel-16/23_series/23172/315bdbeafb39026e19b77c26b19d9d1f_img.jpg b/marked/Rel-16/23_series/23172/315bdbeafb39026e19b77c26b19d9d1f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ce27accd85a48c2a56e6a13bc97f92cf11b1e05a --- /dev/null +++ b/marked/Rel-16/23_series/23172/315bdbeafb39026e19b77c26b19d9d1f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6877f8779a5df06f8aaa19f1485b2b3c35475e3a2f456f7833ada68edb4bdea7 +size 15417 diff --git a/marked/Rel-16/23_series/23172/32ff77da4286b58c4778033acaa10836_img.jpg b/marked/Rel-16/23_series/23172/32ff77da4286b58c4778033acaa10836_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..35e08dfadf72d783d3bcf801cfbb08d7eb8038cb --- /dev/null +++ b/marked/Rel-16/23_series/23172/32ff77da4286b58c4778033acaa10836_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4022e11ca9a4f726038c1e55cce52e879c3cb9fbb718aa10c7b8b3570bd53d43 +size 125347 diff --git a/marked/Rel-16/23_series/23172/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg b/marked/Rel-16/23_series/23172/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..89baf12ccb0edc3f269be376ef84e7f9774206e4 --- /dev/null +++ b/marked/Rel-16/23_series/23172/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a309a508ace77508ee9f25c3eb02af3d1426db1d32f578e8f28a8b891a900cde +size 102522 diff --git a/marked/Rel-16/23_series/23172/34f788b0e5bc8af774fa5561c22e6d01_img.jpg b/marked/Rel-16/23_series/23172/34f788b0e5bc8af774fa5561c22e6d01_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1d173fdda17bd648cf5669b91e4e32544a4a59dd --- /dev/null +++ b/marked/Rel-16/23_series/23172/34f788b0e5bc8af774fa5561c22e6d01_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f10d8baee8598beb35bb90f331cc1924d84e13ec487cacf30df8c0a005c45440 +size 9590 diff --git a/marked/Rel-16/23_series/23172/3db5d62ad46e33647ec2b1ad6d2703bb_img.jpg b/marked/Rel-16/23_series/23172/3db5d62ad46e33647ec2b1ad6d2703bb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c7d223b240065f50947322511c3dd0d7dde25ee3 --- /dev/null +++ b/marked/Rel-16/23_series/23172/3db5d62ad46e33647ec2b1ad6d2703bb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:22b2fa6b4024cf759b7416b7f8ed9478f343637c00682c2aed9a4f081b2adfc7 +size 15157 diff --git a/marked/Rel-16/23_series/23172/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg b/marked/Rel-16/23_series/23172/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3537883bb8fc38a1da633be5b77b735f4e929f16 --- /dev/null +++ b/marked/Rel-16/23_series/23172/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:807c92c45ee9ccdac7f67eb339b0845341cd412c4794d4af5015de861fecaedf +size 184861 diff --git a/marked/Rel-16/23_series/23172/4356776ca004ecba5d599667a155d7d4_img.jpg b/marked/Rel-16/23_series/23172/4356776ca004ecba5d599667a155d7d4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..10a2c19de28d4ccc395d3fefd23f3a2b9a1e834a --- /dev/null +++ b/marked/Rel-16/23_series/23172/4356776ca004ecba5d599667a155d7d4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9d194b8c24c44274008d9a094f7e703f274cd90ecfd2d12bdcc1d4dc01822b92 +size 74317 diff --git a/marked/Rel-16/23_series/23172/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg b/marked/Rel-16/23_series/23172/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f36ff4eb148d0d873dc9fc1b90958da1aca9059e --- /dev/null +++ b/marked/Rel-16/23_series/23172/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:34171261547b0529d4916fc07bd12808f5c484ee77d24c1c41f2fa70da3c2780 +size 100616 diff --git a/marked/Rel-16/23_series/23172/5a24ac755b962fd5f0183f13de0726de_img.jpg b/marked/Rel-16/23_series/23172/5a24ac755b962fd5f0183f13de0726de_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fbf54cfe89af8b466824b4aaa7f7ab3047427130 --- /dev/null +++ b/marked/Rel-16/23_series/23172/5a24ac755b962fd5f0183f13de0726de_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:03ff39b66efb6caa9f2eb92ecc80583cadd89cc4ffaf69bf895c99f22f2c2869 +size 8822 diff --git a/marked/Rel-16/23_series/23172/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Rel-16/23_series/23172/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..197308e1fb58933366e7f88f90da4e40e21b7f7b --- /dev/null +++ b/marked/Rel-16/23_series/23172/5a4e62bead259c258d069fd3663ea670_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a55a118bd03ee74306ee368eaf3205a6a23f0248ff5040071ad86952d958b3dd +size 14077 diff --git a/marked/Rel-16/23_series/23172/5a9282ac54ca7bc50f1d2ab6cfb376ba_img.jpg b/marked/Rel-16/23_series/23172/5a9282ac54ca7bc50f1d2ab6cfb376ba_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f67bb988e2212410f008988357c162cf75dd2418 --- /dev/null +++ b/marked/Rel-16/23_series/23172/5a9282ac54ca7bc50f1d2ab6cfb376ba_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9c7060ddf9184fea92295ff89573dd3b48c911e9693907471b2209f3ed04e4c7 +size 35584 diff --git a/marked/Rel-16/23_series/23172/5a95b187de0044da69b7322e04761b86_img.jpg b/marked/Rel-16/23_series/23172/5a95b187de0044da69b7322e04761b86_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..09f60f69c427f7e1b2ed3ac9aa3e41dfe6bff3e6 --- /dev/null +++ b/marked/Rel-16/23_series/23172/5a95b187de0044da69b7322e04761b86_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:db0e480745a9afa64bf63f60038fe2f387043f1d1c8900eb9a50f9243a9b2c06 +size 36528 diff --git a/marked/Rel-16/23_series/23172/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg b/marked/Rel-16/23_series/23172/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6fa5d624180af9f2dc0c2b7ae2a90b5602c63934 --- /dev/null +++ b/marked/Rel-16/23_series/23172/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8fb095a06ee6d1f5ec5f5db098991134179410308bee0a48fc9497191f33b646 +size 18678 diff --git a/marked/Rel-16/23_series/23172/6e15fc9ea763541c5913d26f85072ae1_img.jpg b/marked/Rel-16/23_series/23172/6e15fc9ea763541c5913d26f85072ae1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..810db6d536ffec4341b93ac129d2e409ca4040b9 --- /dev/null +++ b/marked/Rel-16/23_series/23172/6e15fc9ea763541c5913d26f85072ae1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b1568d22faa9b5d04e6a6b115cff7e3fff511dcc45a3e0eda170c22705e61677 +size 71932 diff --git a/marked/Rel-16/23_series/23172/6f31cdb576d2f15c35c3f266e5f59211_img.jpg b/marked/Rel-16/23_series/23172/6f31cdb576d2f15c35c3f266e5f59211_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c21ab65e40c5e64975c24a06fba7f2abe48b5327 --- /dev/null +++ b/marked/Rel-16/23_series/23172/6f31cdb576d2f15c35c3f266e5f59211_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:74dc6088aa9bf190e8d08716669b06fba46fc17673c485a501613257eacb20fb +size 15907 diff --git a/marked/Rel-16/23_series/23172/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg b/marked/Rel-16/23_series/23172/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..19057be2f0feaa4461390394d9d748f46d2ab556 --- /dev/null +++ b/marked/Rel-16/23_series/23172/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c23d71c920cd5e818f47cf2429b24367f5464b54659fef1d1d0f503f98655779 +size 17455 diff --git a/marked/Rel-16/23_series/23172/79e1709a7317ead45379cbb8ff3ba802_img.jpg b/marked/Rel-16/23_series/23172/79e1709a7317ead45379cbb8ff3ba802_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4be626f1ebfc41f737732318f1ec9573304271eb --- /dev/null +++ b/marked/Rel-16/23_series/23172/79e1709a7317ead45379cbb8ff3ba802_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a26118da941442616c85224c89117dd1f76487f4ed955c8e6e03d61bd18a1eed +size 125477 diff --git a/marked/Rel-16/23_series/23172/7e670a2b556b53ea9002dfff3a420e08_img.jpg b/marked/Rel-16/23_series/23172/7e670a2b556b53ea9002dfff3a420e08_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..edd229af8c3b26c7d1aea7e4446dbcf442739897 --- /dev/null +++ b/marked/Rel-16/23_series/23172/7e670a2b556b53ea9002dfff3a420e08_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:41d67e204de6c66eafaf1d4a207309728822c7dcfa1dc36cb771bd72b660ed90 +size 25569 diff --git a/marked/Rel-16/23_series/23172/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/marked/Rel-16/23_series/23172/7efae06af3af43ffe5d4b956a679cf54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b7d95d747e6109560e6c23be1ababaa2ca19dc0c --- /dev/null +++ b/marked/Rel-16/23_series/23172/7efae06af3af43ffe5d4b956a679cf54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:51687293c087e37e18fd630a12ca8c6155f36c8d7e24bda0377380b80d876c7b +size 41130 diff --git a/marked/Rel-16/23_series/23172/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg b/marked/Rel-16/23_series/23172/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f27dffa61ae5ab04793851c859455ab195505115 --- /dev/null +++ b/marked/Rel-16/23_series/23172/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:104b962e4e4bc257dd954a4f69cb1005992f06f83103bc2eadaabfc745f95526 +size 124696 diff --git a/marked/Rel-16/23_series/23172/8269648391c59363ea61243864a2adf7_img.jpg b/marked/Rel-16/23_series/23172/8269648391c59363ea61243864a2adf7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d49bc6df9e614366f4e414b1bb8d7388abe0df62 --- /dev/null +++ b/marked/Rel-16/23_series/23172/8269648391c59363ea61243864a2adf7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:77975550bb5f2fbd92b70d396bfea1aefbc00b26a35fdc7d19b53ffbd8891e6a +size 182644 diff --git a/marked/Rel-16/23_series/23172/844077b3034f0030b404207db0ad76b4_img.jpg b/marked/Rel-16/23_series/23172/844077b3034f0030b404207db0ad76b4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aba60e6fd5eee4de1bc61d066a1510697bd76da3 --- /dev/null +++ b/marked/Rel-16/23_series/23172/844077b3034f0030b404207db0ad76b4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7b85d9c8305e4b67dbc0df948000955e0e09c840bd78326d264fc5c15613500b +size 17493 diff --git a/marked/Rel-16/23_series/23172/8d66c9c295023a1380f9986d3663bb1e_img.jpg b/marked/Rel-16/23_series/23172/8d66c9c295023a1380f9986d3663bb1e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..03a103323858b77950fa851f2083adcabd0f6249 --- /dev/null +++ b/marked/Rel-16/23_series/23172/8d66c9c295023a1380f9986d3663bb1e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:47f4036d6a66eaecece6936128169837684388435481994952963a4301aec209 +size 186382 diff --git a/marked/Rel-16/23_series/23172/8e14350b4b669119a3bdfca7869110ca_img.jpg b/marked/Rel-16/23_series/23172/8e14350b4b669119a3bdfca7869110ca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a23344e0bcc74774237ad345cec07e08c31a201f --- /dev/null +++ b/marked/Rel-16/23_series/23172/8e14350b4b669119a3bdfca7869110ca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1efcb6afd8e871e546ef5090646e1ba99ed7d09c1cd418676edda87d72b77196 +size 30455 diff --git a/marked/Rel-16/23_series/23172/8e80de0cac529b2c3775d677c5203133_img.jpg b/marked/Rel-16/23_series/23172/8e80de0cac529b2c3775d677c5203133_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f1bcaa09d309dd132da928b1dc6f8abce5ef60df --- /dev/null +++ b/marked/Rel-16/23_series/23172/8e80de0cac529b2c3775d677c5203133_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:26df27e585097a61e001e7921e30418631ea60b0af5523803d716a6be76c349f +size 180953 diff --git a/marked/Rel-16/23_series/23172/8fa679f79a1bb1f527cba9f29e784e89_img.jpg b/marked/Rel-16/23_series/23172/8fa679f79a1bb1f527cba9f29e784e89_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..be215ded5544420458bba5a7c3c0fdfdcf08a776 --- /dev/null +++ b/marked/Rel-16/23_series/23172/8fa679f79a1bb1f527cba9f29e784e89_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c2aeb8f4030e4af2059dd98f28687ef658d92828327e80a52c3ffe639d4dbd92 +size 107907 diff --git a/marked/Rel-16/23_series/23172/90ddb84c323b956e2d50a54d3f870566_img.jpg b/marked/Rel-16/23_series/23172/90ddb84c323b956e2d50a54d3f870566_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..259d1905198bbe734ef99ce112f73b26e1ff9dc8 --- /dev/null +++ b/marked/Rel-16/23_series/23172/90ddb84c323b956e2d50a54d3f870566_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c16898f0ccf19d4d6725782debdfe5279bee8237d602c4a6bdc8dd69cf05fdb9 +size 69865 diff --git a/marked/Rel-16/23_series/23172/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg b/marked/Rel-16/23_series/23172/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..11e0cbe21f15241c2e28d83d2ee7fbb7b3e58efa --- /dev/null +++ b/marked/Rel-16/23_series/23172/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fb3d59d0db998d089eccd207aee1026684bb8fd7dd32e2edcc9968d49ea67a56 +size 105180 diff --git a/marked/Rel-16/23_series/23172/99bae07626f60f9ede10e2e387ef7051_img.jpg b/marked/Rel-16/23_series/23172/99bae07626f60f9ede10e2e387ef7051_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..90851615c3fcd53eae942e789a97f8aae7b2cad1 --- /dev/null +++ b/marked/Rel-16/23_series/23172/99bae07626f60f9ede10e2e387ef7051_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:224ded9ce6d89fae021a0beff27cd145d9cbc40e2a0e9d435c518dd3d7effbfc +size 10662 diff --git a/marked/Rel-16/23_series/23172/9c1d3678db4a12d5864cb2a4def1135d_img.jpg b/marked/Rel-16/23_series/23172/9c1d3678db4a12d5864cb2a4def1135d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..72a5b58fc9fc46d06d763448df33a6be494fa859 --- /dev/null +++ b/marked/Rel-16/23_series/23172/9c1d3678db4a12d5864cb2a4def1135d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7fd9bcfb5c66f7b96c948e610277ba48c9d06e80fe95047d854ca5e23aecb0c9 +size 65203 diff --git a/marked/Rel-16/23_series/23172/9cd90f495b95ad2116ff780248c26d95_img.jpg b/marked/Rel-16/23_series/23172/9cd90f495b95ad2116ff780248c26d95_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e2dee310ac2f63d3abf667149069f5dfdefe6860 --- /dev/null +++ b/marked/Rel-16/23_series/23172/9cd90f495b95ad2116ff780248c26d95_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ab610681e3838ed368d354b78cfc4436cf46cf195253b487cc27e45cec184b8b +size 81693 diff --git a/marked/Rel-16/23_series/23172/9f6dec4d4e9fde40bce018861ef1278e_img.jpg b/marked/Rel-16/23_series/23172/9f6dec4d4e9fde40bce018861ef1278e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..61d81d90319115b8fa9025b1dfd6767b35f1d03c --- /dev/null +++ b/marked/Rel-16/23_series/23172/9f6dec4d4e9fde40bce018861ef1278e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:03c65d775a715125c8a62ff8d7e30cb1ee3d8fe3b3a085109dffb86cde22f569 +size 22189 diff --git a/marked/Rel-16/23_series/23172/9ff1b32449ea068bba9647d71904bd59_img.jpg b/marked/Rel-16/23_series/23172/9ff1b32449ea068bba9647d71904bd59_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..327c178d9e98ede2cca86efc392e9c5e14afc211 --- /dev/null +++ b/marked/Rel-16/23_series/23172/9ff1b32449ea068bba9647d71904bd59_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:273546b7f5b32cd96aff8e8c8fa0d72c9122b1169b0284fa48b471ecc8c7631d +size 18371 diff --git a/marked/Rel-16/23_series/23172/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg b/marked/Rel-16/23_series/23172/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e9e3018009573e28bc8d5f1bd5d40484e22662fb --- /dev/null +++ b/marked/Rel-16/23_series/23172/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ecf524728b916f1c2833ee48ae8b73532288979f642afd50c95ff7f71205cfac +size 144652 diff --git a/marked/Rel-16/23_series/23172/a0e8fe7862a6d7341faf5dac275277cc_img.jpg b/marked/Rel-16/23_series/23172/a0e8fe7862a6d7341faf5dac275277cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..158f6ef3cd35121ff2b75d0e853fe04176f5bb2b --- /dev/null +++ b/marked/Rel-16/23_series/23172/a0e8fe7862a6d7341faf5dac275277cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c7b7e68dec97b4286bab9970df73917e545e54604fa521974a72c1747b12b760 +size 38766 diff --git a/marked/Rel-16/23_series/23172/a1890b9a9b85f13e67ed59bbad623659_img.jpg b/marked/Rel-16/23_series/23172/a1890b9a9b85f13e67ed59bbad623659_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..77756eddd1f6e896db7a824ac72eba53b87cdf54 --- /dev/null +++ b/marked/Rel-16/23_series/23172/a1890b9a9b85f13e67ed59bbad623659_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3a9f034ba778630e14dfd47facd12d1ce63452de322854f7b78244469c5136dd +size 72765 diff --git a/marked/Rel-16/23_series/23172/a234352dfaccdc24745c88eef7724cc6_img.jpg b/marked/Rel-16/23_series/23172/a234352dfaccdc24745c88eef7724cc6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..84af3fa65d2ddf12ca1a85b262fd6d00b0d8c607 --- /dev/null +++ b/marked/Rel-16/23_series/23172/a234352dfaccdc24745c88eef7724cc6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5448693cecbd3c9fa3b03ee04b9cf2078401aa91903a6a9f117863e92ee54433 +size 8274 diff --git a/marked/Rel-16/23_series/23172/a24e89a6fe9bb70c83f8bf5202baba95_img.jpg b/marked/Rel-16/23_series/23172/a24e89a6fe9bb70c83f8bf5202baba95_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c267d8a294555c9c44fe1b6ad29db12a1202c616 --- /dev/null +++ b/marked/Rel-16/23_series/23172/a24e89a6fe9bb70c83f8bf5202baba95_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:435cd9e66cedf55d2046d047c84aacb87657beb1c804c47b641ca5902b90647c +size 26605 diff --git a/marked/Rel-16/23_series/23172/a26e142d3df5bef41a84a9dd099d7825_img.jpg b/marked/Rel-16/23_series/23172/a26e142d3df5bef41a84a9dd099d7825_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..005b70b90961aabedeb4c3bf9830d133586f0a05 --- /dev/null +++ b/marked/Rel-16/23_series/23172/a26e142d3df5bef41a84a9dd099d7825_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c7f7574146611ec0d9879fc5c5375d5a0c16937925b96b619f55b46df23ef385 +size 38604 diff --git a/marked/Rel-16/23_series/23172/b5335262987c819d7f71ce40f99cb71b_img.jpg b/marked/Rel-16/23_series/23172/b5335262987c819d7f71ce40f99cb71b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..32c0914fca09475c015a721d616c698db4ce6e87 --- /dev/null +++ b/marked/Rel-16/23_series/23172/b5335262987c819d7f71ce40f99cb71b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:af6c990df0bc5118c684bb7ef6d1bdeb8f02d942527ade19d27703b51e79fc80 +size 71763 diff --git a/marked/Rel-16/23_series/23172/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg b/marked/Rel-16/23_series/23172/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..498512e572386691fe10ddfe4e69554e55def9dd --- /dev/null +++ b/marked/Rel-16/23_series/23172/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cbc1c0c50d578f50f3898d620800aec098da1e5f370d252e44422f3fd3d1316e +size 204127 diff --git a/marked/Rel-16/23_series/23172/c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg b/marked/Rel-16/23_series/23172/c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8f6ff4a54a6882494ada57dea46f81add4ee11c0 --- /dev/null +++ b/marked/Rel-16/23_series/23172/c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:19a3fee7a41e97c673d18ab97d2eee1088958a0e04aefee6225a4662e71a0372 +size 19569 diff --git a/marked/Rel-16/23_series/23172/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg b/marked/Rel-16/23_series/23172/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e1f1b03d70a7dfa8fc95e0bc1ef0e40b9fc3e0e6 --- /dev/null +++ b/marked/Rel-16/23_series/23172/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8f4328828b912de2adf61092ff075fca0b1c9f47e549c97d48a1e344d45d9434 +size 179563 diff --git a/marked/Rel-16/23_series/23172/d0abac95583b52a3b35f74a215567334_img.jpg b/marked/Rel-16/23_series/23172/d0abac95583b52a3b35f74a215567334_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ecf25571b8031285bd75c3dc92c4c463060e3d40 --- /dev/null +++ b/marked/Rel-16/23_series/23172/d0abac95583b52a3b35f74a215567334_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2b89d9dc393208d04aa191082d94d3294647b66a686ce47bd29e67494adf76dc +size 11541 diff --git a/marked/Rel-16/23_series/23172/dd5771673aececa53d42ece89218299d_img.jpg b/marked/Rel-16/23_series/23172/dd5771673aececa53d42ece89218299d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..250bb59a9c09a51f770008e7fefebee5ff8cac88 --- /dev/null +++ b/marked/Rel-16/23_series/23172/dd5771673aececa53d42ece89218299d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d33e248f5db98559522acf921974b0a77cc709d93721b9c518e0bd0feb208a7c +size 93316 diff --git a/marked/Rel-16/23_series/23172/df1966d80c74bc127f159a48f38b13ee_img.jpg b/marked/Rel-16/23_series/23172/df1966d80c74bc127f159a48f38b13ee_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4e3bb31f862ac48da41e93f5a57d88fa05ddbb67 --- /dev/null +++ b/marked/Rel-16/23_series/23172/df1966d80c74bc127f159a48f38b13ee_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0aad715667c001c0a2c1f6509b0056ced30043179123882efbdce118c8928ae7 +size 135161 diff --git a/marked/Rel-16/23_series/23172/e05b36c0d46549e681ce6581422c66b2_img.jpg b/marked/Rel-16/23_series/23172/e05b36c0d46549e681ce6581422c66b2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a05a2fc47f2508497485b737ddc5282439ed6754 --- /dev/null +++ b/marked/Rel-16/23_series/23172/e05b36c0d46549e681ce6581422c66b2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bb0bc27bd0330f8f23458dbc20ed887fa12e2da1569cbd7a2bc7442b90cbaca7 +size 70946 diff --git a/marked/Rel-16/23_series/23172/e354b57563dae469c00b412b2abdf765_img.jpg b/marked/Rel-16/23_series/23172/e354b57563dae469c00b412b2abdf765_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..07a934b4f660c71b83c251c15777327b40f8be0b --- /dev/null +++ b/marked/Rel-16/23_series/23172/e354b57563dae469c00b412b2abdf765_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2d2b71c1d9c8916d6083ba6504f4d41581cd391e20026487e5f09872732570d6 +size 71338 diff --git a/marked/Rel-16/23_series/23172/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/Rel-16/23_series/23172/e6df2733626a85205c1db682e6259c46_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cea8141c08ba8c3cfd4b18cb01c2bbacb55e4065 --- /dev/null +++ b/marked/Rel-16/23_series/23172/e6df2733626a85205c1db682e6259c46_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:62434e266826029539f71e39d4a7b8524385411e1cecbc3c85b2cad0443bd870 +size 21555 diff --git a/marked/Rel-16/23_series/23172/f1091147d93cee4dfa88498610e395a7_img.jpg b/marked/Rel-16/23_series/23172/f1091147d93cee4dfa88498610e395a7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7416f6ac37c0e4459c6869e0c0e7957d8bbda674 --- /dev/null +++ b/marked/Rel-16/23_series/23172/f1091147d93cee4dfa88498610e395a7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:859f4968c4cc440a2a91f8d4198dccf497b306c0e1ce9e818ae29390705fc78e +size 19110 diff --git a/marked/Rel-16/23_series/23172/f6e8acf9f931452d01688d311b5c0364_img.jpg b/marked/Rel-16/23_series/23172/f6e8acf9f931452d01688d311b5c0364_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4b9063c9e3bbdbe3aaf905cc0d129bf6e609673b --- /dev/null +++ b/marked/Rel-16/23_series/23172/f6e8acf9f931452d01688d311b5c0364_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e0b438a52a0709689844b2bd1bef1ae3e323cf4def694244595a8786a537a8d9 +size 23351 diff --git a/marked/Rel-16/23_series/23172/fb18a83d10ebdad8e3e5ea2e86b36136_img.jpg b/marked/Rel-16/23_series/23172/fb18a83d10ebdad8e3e5ea2e86b36136_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7adb7ea23918875f78c26c4f9eed70924b3997b6 --- /dev/null +++ b/marked/Rel-16/23_series/23172/fb18a83d10ebdad8e3e5ea2e86b36136_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:54da711bd3387b34eec91b307fc757c576e03b4f5d417c5a173c61fe1a7a8f6d +size 16022 diff --git a/marked/Rel-16/23_series/23172/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/marked/Rel-16/23_series/23172/ff0952ef692c9d960ce5f6708bcc9711_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f7b0b353242ddb1f50f21f0f3376a70139dd22d4 --- /dev/null +++ b/marked/Rel-16/23_series/23172/ff0952ef692c9d960ce5f6708bcc9711_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9d5fdf5583b1634fdcb12284fd63e1a25ac1efda555ee22c2f7af5383822687e +size 35500 diff --git a/marked/Rel-16/23_series/23172/raw.md b/marked/Rel-16/23_series/23172/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..ea96df74e927cd80f880c1ffb9eb69677fab5d79 --- /dev/null +++ b/marked/Rel-16/23_series/23172/raw.md @@ -0,0 +1,2248 @@ + + + + + + +# Contents + +| | | +|--------------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions and abbreviations ..... | 7 | +| 3.1 Definitions..... | 7 | +| 3.2 Abbreviations ..... | 7 | +| 4 Service change and fallback for UDI/RDI multimedia..... | 7 | +| 4.1 General Requirements ..... | 7 | +| 4.2 Access Call Control Signalling ..... | 8 | +| 4.2.1 Mobile originating side - initiation of call setup ..... | 8 | +| 4.2.1.1 Subscription checking..... | 9 | +| 4.2.1.1.1 Send Info For Outgoing Call..... | 9 | +| 4.2.1.1.2 Complete Call..... | 10 | +| 4.2.2 Mobile terminating side..... | 10 | +| 4.2.2.1 Subscription checking..... | 11 | +| 4.2.2.1.1 Send Info For Incoming Call..... | 11 | +| 4.2.2.1.2 Complete Call..... | 12 | +| 4.2.3 Mobile originating side - completion of call setup..... | 12 | +| 4.2.4 User-initiated Service change in the active state ..... | 13 | +| 4.2.5 Network-initiated Service change in the active state..... | 14 | +| 4.2.5.1 Network-initiated Service change in the active state starting with multimedia in Iu mode ..... | 16 | +| 4.2.5.2 Network-initiated Service change in the active state starting with speech in Iu mode..... | 17 | +| 4.3 Core Network procedures..... | 22 | +| 4.3.1 Multimedia codec ..... | 23 | +| 4.3.2 Originating side - initiation of call setup ..... | 23 | +| 4.3.2.1 Originating MSC Handling..... | 23 | +| 4.3.2.2 VMSC Handling at Originating Side..... | 24 | +| 4.3.3 Terminating side ..... | 24 | +| 4.3.3.1 HLR Interrogation..... | 24 | +| 4.3.3.1.1 Send Routing Info ..... | 25 | +| 4.3.3.1.2 Send Routing Info Ack..... | 25 | +| 4.3.3.1.3 Handling of mobile terminating calls in the HLR..... | 26 | +| 4.3.3.1.4 Handling of mobile terminating calls in the GMSC ..... | 33 | +| 4.3.3.1a GMSC Handling at Terminating Side ..... | 36 | +| 4.3.3.2 Terminating MSC Handling ..... | 36 | +| 4.3.4 Originating side - completion of call setup ..... | 39 | +| 4.3.5 Service change during the active state..... | 40 | +| 4.3.5.1 Mid-Call Codec Modification Procedure For Service Change..... | 41 | +| 4.3.5.2 Unsuccessful Service Change..... | 51 | +| 4.3.6 Interaction with supplementary services ..... | 55 | +| 4.3.6.1 Call forwarding and Call deflection..... | 55 | +| 4.3.6.2 Closed User Group (CUG) ..... | 56 | +| 4.3.6.3 Call barring ..... | 56 | +| 4.3.7 Interactions with CAMEL ..... | 56 | +| 4.3.7.1 Interaction at call setup..... | 56 | +| 4.3.7.2 Interaction at call answer..... | 56 | +| 4.3.7.3 Interaction with Call Party Handling..... | 56 | +| 4.3.7.4 Interaction with CAMEL in-band information and user interaction ..... | 57 | +| 4.3.7.5 Interaction during service change..... | 57 | +| 4.3.8 Interworking with external networks..... | 57 | +| 4.3.9 User interaction and in-band information..... | 57 | +| 5 Lawful Interception..... | 58 | +| Annex A (informative): Change history..... | 59 | + +# --- 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 Service Change and UDI Fallback (SCUDIF) feature. This service is available to UDI/RDI multimedia calls and allows users to achieve successful call establishment when end to end circuit-switched (CS) multimedia is not possible (fallback to speech) or when signalling of the feature is not possible in the network (fallback to preferred service or speech). Furthermore, it allows the users to swap between a multimedia service and basic speech during an established call. + +NOTE: In the present document, the term "multimedia" refers to UDI/RDI multimedia unless specifically stated. + +# --- 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 and/or edition number or version number) 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.153: "Out of Band Transcoder Control; Stage 2". +- [3] 3GPP TS 24.008: "Mobile Radio Interface Layer 3 specification; Core network protocols; Stage 3". +- [4] 3GPP TS 26.103: "Speech Codec List for GSM and UMTS". +- [5] 3GPP TS 27.001: "General on Terminal Adaptation Functions (TAF) for Mobile Stations (MS)". +- [6] 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)". +- [7] 3GPP TS 29.205: "Application of Q.1900 series to bearer-independent circuit-switched core network architecture; Stage 3". +- [8] 3GPP TS 22.101: "Service aspects; Service principles". +- [9] 3GPP TS 33.106: "3GPP Security; Lawful Interception Requirements". +- [10] 3GPP TS 23.018: "Basic Call Handling; Technical realization". +- [11] 3GPP TS 23.003: "Numbering, addressing and identification". +- [12] 3GPP TS 29.232: "Media Gateway Controller (MGC) – Media Gateway (MGW) Interface; Stage 3". +- [13] 3GPP TS 26.102: "Mandatory Speech Codec; AMR Speech Codec; Interface to Iu, Uu, Nb". +- [14] 3GPP TS 23.078: "Customised Applications for Mobile network Enhanced Logic (CAMEL) ; Stage 2". +- [15] 3GPP TS 23.082: "Call Forwarding (CF) supplementary services, Stage 2". +- [16] 3GPP TS 22.078: "Customised Applications for Mobile network Enhanced Logic (CAMEL); Service description, Stage 1". + +- [17] 3GPP TS 25.413: "UTRAN Iu interface RANAP signalling". +- [18] IETF RFC 4040: "RTP Payload Format for a 64 kbit/s Transparent Call" + +# --- 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: + +**fallback:** when two services (multimedia and speech) are proposed but only one of them is available or wanted, only the service available (preferred or less preferred) is selected, and the other one is discarded + +**service change:** when two services (multimedia and speech) are available during the active state of a call, users may request a service change to switch between the two services + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply: + +| | | +|--------|----------------------------------------------------------------| +| BC | Bearer Capability | +| BC1 | First Bearer Capability in a message (preferred service) | +| BC2 | Second Bearer Capability in a message (less preferred service) | +| BCa | Bearer Capability of the currently selected service | +| BCb | Bearer Capability of the service to switch to | +| BCmm | Bearer Capability multimedia | +| BCSM | Basic Call State Model | +| BCsp | Bearer Capability speech | +| CAMEL | Customised Applications for Mobile network Enhanced Logic | +| DP | Detection Point | +| IE | Information Element | +| MMI | Man-Machine Interface | +| O-MSC | Originating MSC | +| OoBTC | Out-of-Band Transcoder Control | +| O-UE | Originating UE | +| RI | Repeat Indicator | +| SCUDIF | Service Change and UDI/RDI Fallback | +| T-MSC | Terminating MSC | +| T-UE | Terminating UE | + +# --- 4 Service change and fallback for UDI/RDI multimedia + +## 4.1 General Requirements + +The Service Change and UDI Fallback (SCUDIF) is a function which applies to UDI/RDI multimedia calls (see 3GPP TS 22.101 [8], clause 7.2.1), and shall support the following: + +- Fallback to speech during call setup: allow a user to attempt to set up a multimedia call, and try a speech connection if the former doesn't succeed; +- Fallback to the less preferred service (speech or multimedia) during call setup: allow the terminating side via specific settings for this service in the terminal to accept or reject a multimedia call, without interrupting the call setup; +- Fallback to the preferred service (speech or multimedia) or speech during call setup: allow the call setup to proceed with a single service if the transit network does not support the signalling of this functionality; +- BC negotiation at the terminating side: allow the terminating side via specific settings for this service in the terminal to turn a speech call (with service change) into a multimedia call and vice-versa; + +- e) Service change: allow a speech call to be turned to multimedia by either of parties, and back to speech, through a successful in call modification procedure; +- f) Allow any of the users to reject a multimedia request from the other party while in speech mode. +- g) Network-initiated service change: The network shall initiate a service-change from multimedia to speech during the active call if a multimedia call can no longer be supported. If a multimedia call can again be supported at a later point in time, the network may initiate a service change from speech to multimedia. + +To fulfil: + +- service request signalling between the UE and the MSC; +- service request signalling across the Core Network. + +This functionality is not supported for multimedia with Fixed Network User Rate set to 32 kbit/s. In this case, the MSC shall revert to a multimedia only call. + +## 4.2 Access Call Control Signalling + +Using the repeat indicator value "support of service change and fallback", as described in 3GPP TS 24.008 [3], clause 5.3.6, together with two BC-IEs, a multimedia and a speech, it is possible to request a service change and fallback functionality, while still maintaining the backwards compatibility with non-supporting terminals. + +### 4.2.1 Mobile originating side - initiation of call setup + +By sending a SETUP message with a Repeat Indicator set to "support of service change and fallback", a multimedia BC-IE, and a speech BC-IE (see figure 4.1), a terminal may request a call to be set with the capability to fallback to either a speech only, a multimedia only call or to use service change later during the active state of the call (the first BC-IE indicates the preferred service). If the terminal supports Network-initiated service upgrade to multimedia, then it shall also indicate this in the SETUP message with the "Enhanced Network-initiated ICM" (ENICM) Capability (see 3GPP TS 24.008[3]). + +After checking the provisioning (see subclause 4.2.1.1), and verifying that the functionality is supported, the MSC replies in the CALL PROCEEDING message with either the two BCs in the same order (to indicate that it accepts the proposed settings - see figure 4.2), or with a single BC (multimedia or speech - see figure 4.3) unless the CALL PROCEEDING is delayed until the response from the terminating user and then it may also be sent with the BCs in reverse order (see clause 4.2.3). + +In the case the MSC ignores the SETUP message if the presence of a reserved value for the Repeat Indicator is set, it sends a STATUS message back to the UE (see figure 4.4), with the Cause Value set to #100, "Conditional IE error" (see 3GPP TS 24.008 [3], clause 8.7.2). The UE then reacts as described in 3GPP TS 24.008 [3], clause 5.5.3.2.2, and may resend a new SETUP message with a single BC, or perform any appropriate action according to its implementation. This also applies in case the MSC returns instead a RELEASE COMPLETE message. + + + +``` +sequenceDiagram + participant O-UE + participant O-MSC + Note left of O-UE: + O-UE->>O-MSC: SETUP (RI, BC1, BC2, [ENICM]) + Note right of O-MSC: + activate O-MSC + Note right of O-MSC: + deactivate O-MSC +``` + +Sequence diagram showing the SETUP message from O-UE to O-MSC. + +Figure 4.1: SETUP message towards the originating MSC + + + +``` +sequenceDiagram + participant O-UE + participant O-MSC + Note left of O-UE: + activate O-MSC + Note right of O-MSC: + O-MSC->>O-UE: CALL PROCEEDING (RI, BC1, BC2) + Note left of O-UE: + deactivate O-MSC +``` + +Sequence diagram showing the CALL PROCEEDING message from O-MSC to O-UE. + +Figure 4.2: Normal case + + + +``` + +sequenceDiagram + participant O-UE + participant O-MSC + Note left of O-UE: + O-UE->>O-MSC: CALL PROCEEDING (BC1 or BC2) + Note right of O-UE: + +``` + +Sequence diagram for Figure 4.3: Fallback case. It shows a message 'CALL PROCEEDING (BC1 or BC2)' being sent from the O-UE to the O-MSC. + +Figure 4.3: Fallback case + + + +``` + +sequenceDiagram + participant O-UE + participant O-MSC + Note right of O-UE: + O-UE->>O-MSC: STATUS (Cause:#100) + Note right of O-UE: NOTE + Note left of O-UE: + O-UE->>O-MSC: SETUP (BC1 or BC2) + Note left of O-UE: NOTE + Note right of O-UE: + O-UE->>O-MSC: CALL PROCEEDING (BC) + Note right of O-UE: + +``` + +Sequence diagram for Figure 4.4: MSC not supporting the RI value. It shows three messages: 1. STATUS (Cause:#100) from O-UE to O-MSC with a NOTE on the O-MSC side. 2. SETUP (BC1 or BC2) from O-UE to O-MSC with a NOTE on the O-UE side. 3. CALL PROCEEDING (BC) from O-UE to O-MSC. + +NOTE: The sending of the STATUS message from the MSC and the second SETUP message from the UE are implementation dependent. + +Figure 4.4: MSC not supporting the RI value + +#### 4.2.1.1 Subscription checking + +The functional behaviour of the originating MSC and VLR is specified in 3GPP TS 23.018 [10]. The procedure specific to SCUDIF is specified in this subclause: + +For mobile originated SCUDIF calls, the MSC shall convert both PLMN bearer capability 1 and PLMN bearer capability 2 to two individual Basic Service codes and send them in Send Info For Outgoing Call. The VLR shall check the subscription for those basic services, then indicates the availability of each basic service to the MSC by Complete Call. If both services are not provisioned, the VLR shall send Send Info For Outgoing Call negative response to the MSC. The MSC shall fall back to the allowed service if the availability of only one service is indicated. The MSC shall continue as a SCUDIF call if the availability of both services is indicated. + +##### 4.2.1.1.1 Send Info For Outgoing Call + +Send Info For Outgoing Call contains the following SCUDIF specific information elements: + +| Information element name | Status | Description | +|--------------------------|--------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Bearer service2 | C | Bearer service 2 required for the MO call, derived from the PLMN bearer capability 2 information received in the set-up request from the MS. For a SCUDIF call, one of bearer service 2 or teleservice 2 shall be present. | +| Teleservice2 | C | Teleservice 2 required for the MO call, derived from the PLMN bearer capability 2 information received in the set-up request from the MS. For a SCUDIF call, one of bearer service 2 or teleservice 2 shall be present. | + +##### 4.2.1.1.2 Complete Call + +Complete Call contains the following SCUDIF specific information elements: + +| Information element name | Status | Description | +|-----------------------------|--------|-----------------------------------------------------------------------------------------------------------------------| +| First service availability | C | Shall be present for a MO SCUDIF call if the Bearer service or Teleservice is allowed; otherwise shall be absent. | +| Second service availability | C | Shall be present for a MO SCUDIF call if the Bearer service 2 or Teleservice 2 is allowed; otherwise shall be absent. | + +### 4.2.2 Mobile terminating side + +When the terminating MSC receives a request for a multimedia call, it shall check if the called user is provisioned for the service (see subclause 4.2.2.1). + +The terminating MSC shall include in the SETUP message towards the UE both BC-IEs in the same order as indicated by the incoming request together with the Repeat Indicator set to "service change and fallback in order to invoke the SCUDIF functionality in the called terminal (see figure 4.5). + +The terminating UE, based on its capabilities and internal settings, may return the two BC-IEs in the same order (to indicate that it accepts the proposed settings - see figure 4.6), reversed order (see figure 4.7), or just one BC-IE (either speech or multimedia - see figure 4.8) to the terminating MSC in the CALL CONFIRMED message. If the terminal supports Network-initiated service upgrade to multimedia, then it shall also indicate this in the CALL CONFIRMED message with the "Enhanced Network-initiated ICM" (ENICM) Capability (see 3GPP TS 24.008[3]). + +In the case the UE ignores the SETUP message due to the presence of a reserved value for the Repeat Indicator, it sends a STATUS message back to the terminating MSC (see figure 4.9), with the Cause Value set to #100, "Conditional IE error" (see 3GPP TS 24.008 [3], clause 8.7.2). The terminating MSC shall then react according to 3GPP TS 24.008 [3], clause 5.5.3.2.2 and it shall send a new SETUP message with a single BC, either the preferred service BC-IE or the speech BC-IE (fallback to speech), depending on configuration. The call setup then proceeds accordingly. + + + +``` +sequenceDiagram + participant T-MSC + participant T-UE + Note left of T-MSC: T-MSC + Note right of T-UE: T-UE + T-MSC->>T-UE: SETUP (RI, BC1, BC2) +``` + +Sequence diagram showing the SETUP message from T-MSC to T-UE. + +**Figure 4.5: SETUP message towards the terminating UE** + + + +``` +sequenceDiagram + participant T-MSC + participant T-UE + Note left of T-MSC: T-MSC + Note right of T-UE: T-UE + T-UE->>T-MSC: CALL CONFIRMED (RI, BC1, BC2, [ENICM]) +``` + +Sequence diagram showing the CALL CONFIRMED message from T-UE to T-MSC in the normal case. + +**Figure 4.6: Normal case** + + + +``` +sequenceDiagram + participant T-MSC + participant T-UE + Note left of T-MSC: T-MSC + Note right of T-UE: T-UE + T-UE->>T-MSC: CALL CONFIRMED (RI, BC2, BC1) +``` + +Sequence diagram showing the CALL CONFIRMED message from T-UE to T-MSC in the reversed call setup case. + +**Figure 4.7: Reversed call setup** + + + +``` +sequenceDiagram + participant T-MSC + participant T-UE + Note left of T-MSC: T-MSC + Note right of T-UE: T-UE + T-UE->>T-MSC: CALL CONFIRMED (BC1 or BC2) +``` + +Sequence diagram showing the CALL CONFIRMED message from T-UE to T-MSC in the fallback case. + +**Figure 4.8: Fallback case** + + + +``` + +sequenceDiagram + participant T-UE + participant T-MSC + Note left of T-UE: + T-UE->>T-MSC: STATUS (Cause: #100) + Note right of T-MSC: + T-MSC->>T-UE: SETUP (BC1 or BC2) + Note left of T-UE: + T-UE->>T-MSC: CALL CONFIRMED (BC ) + +``` + +Sequence diagram showing the interaction between T-MSC and T-UE. The sequence is: 1. T-UE sends STATUS (Cause: #100) to T-MSC. 2. T-MSC sends SETUP (BC1 or BC2) to T-UE. 3. T-UE sends CALL CONFIRMED (BC ) to T-MSC. + +**Figure 4.9: UE not supporting the RI value** + +#### 4.2.2.1 Subscription checking + +The functional behaviour of the terminating MSC and VLR is specified in 3GPP TS 23.018 [10]. The procedure specific to SCUDIF calls is specified in this subclause. + +For mobile terminating SCUDIF calls, the MSC shall convert the services received in the incoming request to two individual Basic Service codes, and include them in Send Info For Incoming Call. The VLR shall check the subscription for those basic services, then indicate the availability of each basic service to the MSC by Complete Call. If both services are not provisioned, the VLR shall send Send Info for Incoming Call negative response to the MSC. The MSC shall fall back to the allowed service if the availability of only one service is indicated. The MSC shall continue as a SCUDIF call if the availability of both services is indicated. + +##### 4.2.2.1.1 Send Info For Incoming Call + +Send Info For Incoming Call contains the following SCUDIF specific information elements: + +| Information element name | Required | Description | +|--------------------------|----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Bearer Service 2 | C | Bearer Service 2 required for the MT call, derived from the less preferred service indicated in the incoming IAM of a SCUDIF call. For a SCUDIF call, one of Bearer service 2 or Teleservice 2 shall be present. | +| Teleservice 2 | C | Teleservice 2 required for the MT call, derived from the less preferred service indicated in the incoming IAM of a SCUDIF call. For a SCUDIF call, one of Bearer service 2 or Teleservice 2 shall be present. | + +##### 4.2.2.1.2 Complete Call + +The parameters described in subclause 4.2.1.1.2 "Complete Call" for the mobile originating MSC are also applicable to the mobile terminating MSC. + +### 4.2.3 Mobile originating side - completion of call setup + +If the preferred mode, that is the first BC-IE indicated by the originating UE, was selected as the result of negotiations, the call shall be set up normally towards the originating UE. + +If the negotiation resulted in a change of the selected mode, i.e. the call was set up as "multimedia first" and changed during the negotiation to a speech call, or vice-versa, because of either fallback or change of selected mode and the Call Proceeding message has been sent then an In-Call Modification procedure (see 3GPP TS 24.008 [3], clause 5.3.4.3) shall be initiated towards the originating UE after the call control entity has entered the active state, i.e. the CONNECT message has been sent. + + + +``` +sequenceDiagram + participant O-UE + participant O-MSC + Note left of O-UE: Preferred mode selected + O-UE->>O-MSC: CONNECT + O-MSC-->>O-UE: CONNECT ACKNOWLEDGE +``` + +Sequence diagram for Figure 4.10: Preferred mode selected. It shows two lifelines: O-UE and O-MSC. The O-UE sends a CONNECT message to the O-MSC. The O-MSC responds with a CONNECT ACKNOWLEDGE message back to the O-UE. + +**Figure 4.10: Preferred mode selected** + + + +``` +sequenceDiagram + participant O-UE + participant O-MSC + Note left of O-UE: Less preferred mode selected, accepted + O-UE->>O-MSC: CONNECT + O-MSC-->>O-UE: CONNECT ACKNOWLEDGE + O-UE->>O-MSC: MODIFY (BC2) + O-MSC-->>O-UE: MODIFY COMPLETE (BC2) +``` + +Sequence diagram for Figure 4.11: Less preferred mode selected, accepted. It shows two lifelines: O-UE and O-MSC. The O-UE sends a CONNECT message to the O-MSC. The O-MSC responds with a CONNECT ACKNOWLEDGE message. The O-UE then sends a MODIFY (BC2) message to the O-MSC. The O-MSC responds with a MODIFY COMPLETE (BC2) message. + +**Figure 4.11: Less preferred mode selected, accepted** + + + +``` +sequenceDiagram + participant O-UE + participant O-MSC + Note left of O-UE: Less preferred mode selected, rejected + O-UE->>O-MSC: CONNECT + O-MSC-->>O-UE: CONNECT ACKNOWLEDGE + O-UE->>O-MSC: MODIFY (BC2) + O-MSC-->>O-UE: MODIFY REJECT (BC1) + O-UE->>O-MSC: RELEASE COMPLETE +``` + +Sequence diagram for Figure 4.12: Less preferred mode selected, rejected. It shows two lifelines: O-UE and O-MSC. The O-UE sends a CONNECT message to the O-MSC. The O-MSC responds with a CONNECT ACKNOWLEDGE message. The O-UE then sends a MODIFY (BC2) message to the O-MSC. The O-MSC responds with a MODIFY REJECT (BC1) message. Finally, the O-UE sends a RELEASE COMPLETE message to the O-MSC. + +**Figure 4.12: Less preferred mode selected, rejected** + +If the Call Proceeding message is delayed until response from the terminating side then it may include one or both BCs either in the order requested from the Originating UE or the order of the BCs may be reversed, depending on the result from the negotiation or (single BC) due to fallback. See Figure 4.12a. + + + +``` + +sequenceDiagram + participant O-UE + participant O-MSC + Note right of O-MSC: (select = x, avail = x, y, z, mm) + O-MSC->>O-UE: CALL PROCEEDING (RI, BC2, BC1) + O-UE->>O-MSC: CONNECT + O-MSC->>O-UE: CONNECT ACKNOWLEDGE + +``` + +Sequence diagram for Figure 4.12a: Call Proceeding Delayed. It shows the interaction between O-UE and O-MSC. The O-MSC sends a message '(select = x, avail = x, y, z, mm)' to the O-UE. The O-UE then sends 'CALL PROCEEDING (RI, BC2, BC1)' to the O-MSC. The O-MSC responds with 'CONNECT', and the O-UE replies with 'CONNECT ACKNOWLEDGE'. + +Figure 4.12a: Call Proceeding Delayed + +### 4.2.4 User-initiated Service change in the active state + +At any given time, if either of the call parties wants to change from the current active mode to the other mode via MMI, the terminal shall activate an In-Call Modification procedure. Using this procedure, described in 3GPP TS 24.008 [3], clause 5.3.4.3, the UE shall send a MODIFY message containing the BC-IE to change to. This BC-IE shall be one of those already negotiated at call setup. + +As a result, the MSC shall then invoke the service change procedure (see clause 4.3.5). If the request is accepted, the originating MSC sends a MODIFY COMPLETE message to the UE including the BC-IE of the mode to switch to (see figure 4.13). If the request is rejected, the MSC sends a MODIFY REJECT message to the UE including the BC-IE from the current active mode (see figure 4.14). + +In the case the MSC has determined that the other mode is unavailable (e.g. a fallback to either mode has occurred), it shall reject the MODIFY request at once by replying with a MODIFY REJECT message. + +On the remote side, the MSC shall initiate an In-Call Modification procedure towards the terminal using the MODIFY message. For a service change from speech to multimedia, the terminal shall request confirmation from the user unless configured differently. For a service change from multimedia to speech, the terminal shall accept the request without requesting confirmation from the user. If the change is accepted, the UE shall reply to the MSC with a MODIFY COMPLETE message, whereas a MODIFY REJECT message shall be sent if the change is rejected. + +NOTE: Privacy concerns strongly advise that any change to multimedia mode, unless explicitly allowed by the user in the terminal configuration settings, triggers a question to the user in order to confirm or decline the change. The details on how to provide the user interaction are left for implementation. + +When receiving a MODIFY message, a terminal shall not interrupt the data traffic and shall continue to send and receive data in the old mode, even after the terminal accepts the modification with a MODIFY COMPLETE message. The radio bearer will then be reconfigured by the network. After the radio bearer has been reconfigured, the terminal shall send and receive data in the new mode. + + + +``` + +sequenceDiagram + participant UE A + participant MSC A + participant MSC B + participant UE B + UE A->>MSC A: MODIFY (BCb) + Note right of MSC A: Core Network Procedure + MSC A->>MSC B: MODIFY (BCb) + MSC B->>UE B: MODIFY COMPLETE (BCb) + Note right of UE B: Core Network Procedure + UE B->>MSC A: MODIFY COMPLETE (BCb) + MSC A->>UE A: MODIFY COMPLETE (BCb) + +``` + +Sequence diagram for Figure 4.13: Service change requested, accepted. It shows the interaction between UE A, MSC A, MSC B, and UE B. UE A sends a 'MODIFY (BCb)' message to MSC A. MSC A performs a 'Core Network Procedure' and sends a 'MODIFY (BCb)' message to MSC B. MSC B sends a 'MODIFY COMPLETE (BCb)' message to UE B. UE B performs a 'Core Network Procedure' and sends a 'MODIFY COMPLETE (BCb)' message to MSC A. MSC A then sends a 'MODIFY COMPLETE (BCb)' message to UE A. + +Figure 4.13: Service change requested, accepted + + + +Sequence diagram for Figure 4.14: Service change requested, rejected. The diagram shows four lifelines: UE A, MSC A, MSC B, and UE B. UE A sends a MODIFY (BCb) message to MSC A. MSC A performs a 'Core Network Procedure' (dotted line) to MSC B. MSC B sends a MODIFY (BCb) message to UE B. UE B responds with a MODIFY REJECT (BCa) message to MSC B. MSC B performs another 'Core Network Procedure' (dotted line) back to MSC A. Finally, MSC A sends a MODIFY REJECT (BCa) message to UE A. + +**Figure 4.14: Service change requested, rejected** + +### 4.2.5 Network-initiated Service change in the active state + +When the visited MSC of either party can no longer support an ongoing multimedia call, for example due to degraded coverage conditions (including UTRAN to GERAN only transitions), the visited MSC of this party shall initiate a service-change from multimedia to speech, following the procedures described below. + +If the visited MSC is again able to support the multimedia at a later point in time while the speech call is still ongoing, the same visited MSC may initiate a service change from speech to multimedia as stated in TS 22.101 [8]. The details for the service change from speech to multimedia are described in section 4.2.5.2. + +For a downgrade from multimedia to speech the visited MSC shall initiate an In-Call Modification procedure towards the terminal it serves using the MODIFY message. The visited MSC shall also invoke the service change procedure (see clause 4.3.5) towards the remote side. The terminals on both sides will react as described in Clause 4.2.4. + +The Visited MSC shall only initiate a Network Initiated Service Upgrade from speech to multimedia if the terminal has indicated support for Network Initiated Service Upgrade Capability during the call establishment phase, as detailed in 3GPP TS 24.008 [3]. When sending the Modify request to the local terminal the MSC shall include the Network-initiated Service Upgrade indicator. A visited MSC receiving an incoming Network Initiated Service Upgrade procedure from the core network shall also include the Network-initiated Service Upgrade indicator within the MODIFY request to the local terminal. + +**NOTE:** If the visited MSC initiating the Network Initiated Service Upgrade uses the 3G-324.M codec in the core network signalling due to operator's policy, the visited MSC receiving the incoming Service Upgrade procedure from the core network will not recognise that this procedure is network-initiated and thus will not include the Network-initiated Service Upgrade indicator within the MODIFY request to the local terminal. + + + +Sequence diagram for Figure 4.14a: Network-Initiated Service change from multimedia to speech requested, accepted. The diagram shows four lifelines: UE A, MSC A, MSC B, and UE B. MSC A sends a MODIFY (BCb) message to UE A. UE A responds with a MODIFY COMPLETE (BCb) message to MSC A. MSC A performs a 'Core Network Procedure' (dotted line) to MSC B. MSC B sends a MODIFY (BCb) message to UE B. UE B responds with a MODIFY COMPLETE (BCb) message to MSC B. MSC B performs another 'Core Network Procedure' (dotted line) back to MSC A. + +**Figure 4.14a: Network-Initiated Service change from multimedia to speech requested, accepted** + +Figure 4.14b: void + +Figure 4.14c: void + + + +This sequence diagram illustrates a successful network-initiated service change from speech to multimedia. It involves four participants: UE A, MSC A, MSC B, and UE B. The process begins with MSC A sending a MODIFY (BCb, NISUid) message to UE A. UE A responds with a MODIFY COMPLETE (BCb) message. MSC A then initiates a 'Core Network Procedure' (represented by a series of five dots) to MSC B. MSC B sends a MODIFY (BCb, NISUid) message to UE B. UE B responds with a MODIFY COMPLETE (BCb) message. Finally, MSC B completes its 'Core Network Procedure' back to MSC A. + +Sequence diagram for Figure 4.14c1 showing a successful network-initiated service change from speech to multimedia. + +Figure 4.14c1: Network-Initiated Service change from speech to multimedia requested, accepted + +If the served terminal rejects the service change from speech to multimedia, the initiating MSC shall maintain the original service. If the remote side rejects the service change from speech to multimedia, the initiating MSC shall initiate a service change procedure towards the served terminal to revert to the original service. + + + +This sequence diagram illustrates a service change request that is rejected by UE A. It involves four participants: UE A, MSC A, MSC B, and UE B. The process begins with MSC A sending a MODIFY (BCb, NISUid) message to UE A. UE A responds with a MODIFY REJECT (BCa) message. The diagram does not show any further messages to or from MSC B or UE B. + +Sequence diagram for Figure 4.14c2 showing a service change request rejected by UE A. + +Figure 4.14c2: Network-Initiated Service change from speech to multimedia requested, rejected by user A + + + +Sequence diagram for Figure 4.14c3: Network-Initiated Service change from speech to multimedia requested, rejected by user B. The diagram shows four lifelines: UE A, MSC A, MSC B, and UE B. UE A sends a MODIFY (BCb, NISUid) message to MSC A. MSC A responds with MODIFY COMPLETE (BCb). MSC A then initiates a 'Core Network Procedure' (indicated by a series of dots) towards MSC B. MSC B sends a MODIFY (BCb, NISUid) message to UE B. UE B responds with MODIFY REJECT (BCa). MSC B initiates another 'Core Network Procedure' towards MSC A. MSC A sends a MODIFY (BCa) message to UE A. UE A responds with MODIFY COMPLETE (BCa). + +**Figure 4.14c3: Network-Initiated Service change from speech to multimedia requested, rejected by user B** + +#### 4.2.5.1 Network-initiated Service change in the active state starting with multimedia in Iu mode + +For a network initiated service change from multimedia in Iu mode to speech, the visited MSC shall use the following procedure. + +In order to request a notification from the RNC when it detects a lack of sufficient resources or radio signal degradation, the visited MSC shall include an Alternative RAB Parameters IE in the RANAP RAB Assignment Request or RANAP Relocation Request message indicating the RAB configuration for speech in addition to the RAB configuration for multimedia, when it establishes or modifies the radio access bearer for multimedia at the Iu interface. + +When the radio access network detects a lack of sufficient resources to sustain the multimedia RAB configuration, it shall inform the visited MSC by sending a RANAP Modify Request message (see 3GPP TS 25.413 [17]) to the visited MSC. The visited MSC shall then: + +- initiate an In-Call Modification procedure to speech towards the terminal it serves using the MODIFY message; and +- invoke the service change procedure (see clause 4.3.5) towards the remote side, +- trigger the RAB modification by sending a RANAP RAB Assignment with the RAB requested to be Modified to the RNC. + + + +``` + +sequenceDiagram + participant UE A + participant RNC A + participant MSC A + participant MSC B + participant UE B + + MSC A->>RNC A: RANAP RAB Assignment +(configuration1, configuration 2) + Note over RNC A, MSC A: ● ● ● ● ● ● ● ● + RNC A->>MSC A: RANAP Modify Request +(alternate configuration requested) + MSC A->>UE A: MODIFY +(BCspeech) + UE A->>MSC A: MODIFY COMPLETE +(BCspeech) + Note over MSC A, MSC B: Core Network +Procedure + MSC B->>UE B: MODIFY +(BCspeech) + UE B->>MSC B: MODIFY COMPLETE +(BCspeech) + Note over MSC A, MSC B: ● ● ● ● ● ● ● ● + MSC A->>RNC A: RAB Assignment Modify +(Configuration 2, Configuration1) + +``` + +Sequence diagram illustrating a Network-Initiated Service change from UTRAN multimedia to speech requested, accepted. + +**Figure 4.14d: Network-Initiated Service change from UTRAN multimedia to speech requested, accepted** + +#### 4.2.5.2 Network-initiated Service change in the active state starting with speech in Iu mode + +The network initiated service change from speech to multimedia in Iu mode is an optional feature. If supported the MSC initiating the service upgrade to multimedia shall use the following procedure. However a service change from speech to multimedia should not be initiated unless a network initiated service change from multimedia to speech had previously taken place during the same user session. Furthermore a network initiated service upgrade to multimedia shall not be performed unless the terminal has indicated that it supports it by including the Enhanced Network-initiated ICM (ENICM) Capability at call establishment. If the 3G-324.M2 was not received in the available codec list, depending on operator policy, the visited MSC may or may not perform a Network-initiated Service change procedure from speech to multimedia. + +NOTE: The 3G-324.M2 codec in the available codec list indicates that all nodes in the call support incoming request for the network initiated service change from speech to multimedia and thus collect charging information indicating that a network-initiated service change was performed. An operator could choose to perform a network-initiated service change even if the 3G-324.M2 codec was not received in the available codec list, for example if the operator applies a billing scheme where the initiator of the multimedia call pays for the call and mutual agreements with the peer's operator allow this policy. + +In order to request a notification about sufficient resources to sustain again the multimedia RAB configuration from the radio access network , the visited MSC shall include an Alternative RAB Parameters IE in the RANAP RAB Assignment Request or RANAP Relocation Request message indicating the RAB configuration for multimedia in addition to the RAB configuration for speech, when it establishes or modifies the radio access bearer for speech at the Iu interface during or after a network-initiated service change from multimedia to speech. In order to request a notification about sufficient resources from a target RNC after a subsequent relocation, the MSC shall pass the Alternative RAB Parameters IE in the RELOCATION REQUEST message to the target RNC. + +NOTE: If the non-anchor RNC is a pre-Release 6 node then no notification about sufficient resources can be received and therefore the MSC cannot assume that it will receive the notification for upgrade if it did not receive a previous notification for downgrade from that RNC. + +When the radio access network later detects that there are sufficient resources to sustain again the multimedia RAB configuration, it shall indicate the possibility of a service change to the alternative multimedia RAB configuration by sending a RANAP Modify Request message (see 3GPP TS 25.413 [17]) to the MSC. The MSC may then: + +- initiate an In-Call Modification procedure to multimedia towards the terminal it serves using the MODIFY message. The visited MSC shall include the NISUId information element in the MODIFY message. The MSC + +initiating the service change shall not interrupt the user plane until the terminal accepts the modification with a MODIFY COMPLETE message. When the MODIFY COMPLETE message is received from the served terminal, the initiating MSC shall then: + +- invoke the service change procedure (see clause 4.3.5) towards the remote side. The initiating MSC shall then; +- reconfigure the RAB to the multimedia bearer at the latest when receiving a confirmation about the successful service change procedure from the remote side. + +When receiving a MODIFY message, a terminal shall not interrupt the data traffic and shall continue to send and receive data in the old mode, even after the terminal accepts the modification with a MODIFY COMPLETE message. After the radio bearer has been reconfigured by the network, the terminal shall send and receive data in the new mode. + + + +The sequence diagram shows the interaction between UE A, RNC A, MSC A, MSC B, and UE B. The process starts with MSC A sending a RANAP RAB Assignment Modify (configuration2, configuration1) to RNC A. RNC A responds with a RANAP Modify Request (alternate configuration requested) to MSC A. MSC A then sends a MODIFY (Bcmultimedia, NISUid) to UE A. UE A responds with a MODIFY COMPLETE (BCmultimedia) to MSC A. MSC A then initiates a Core Network Procedure with MSC B, sending a MODIFY (BCmultimedia, NISUid) to UE B. UE B responds with a MODIFY COMPLETE (BCmultimedia) to MSC B. MSC B then sends a RANAP RAB Assignment Modify (Multimedia, Altern. RAB Param. = speech) to RNC A. RNC A responds with a RANAP RAB Assignment Response (Successful) to MSC A. + +Sequence diagram illustrating the Network-Initiated Service change from UTRAN speech to multimedia requested, accepted in case the RAB is modified on the initiating side after receiving the response to the service change request from the remote side. + +**Figure 4.2.5.2/1: Network-Initiated Service change from UTRAN speech to multimedia requested, accepted in case the RAB is modified on the initiating side after receiving the response to the service change request from the remote side** + + + +This sequence diagram illustrates a network-initiated service change from UTRAN speech to multimedia. The participants are UE A, RNC A, MSC A, MSC B, and UE B. The process begins with RNC A sending a RANAP RAB Assignment Modify (configuration2, configuration1) to MSC A. MSC A responds with a RANAP Modify Request (alternate configuration requested). RNC A then sends a MODIFY (BCmultimedia, NISUid) to UE A. UE A responds with a MODIFY COMPLETE (BCmultimedia). MSC A then sends a RANAP RAB Assignment Modify (Multimedia, Altern. RAB Param. = speech) to RNC A. RNC A responds with a RANAP RAB Assignment Response (Successful). A 'Core Network Procedure' is indicated between MSC A and MSC B. MSC B sends a MODIFY (BCmultimedia, NISUid) to UE B. UE B responds with a MODIFY COMPLETE (BCmultimedia). + +``` + +sequenceDiagram + participant UE A + participant RNC A + participant MSC A + participant MSC B + participant UE B + Note right of RNC A: RANAP RAB Assignment Modify (configuration2, configuration1) + RNC A->>MSC A: RANAP Modify Request (alternate configuration requested) + Note right of MSC A: ● ● ● ● ● ● ● ● + MSC A->>RNC A: MODIFY (BCmultimedia, NISUid) + RNC A->>UE A: MODIFY COMPLETE (BCmultimedia) + Note right of RNC A: RANAP RAB Assignment Modify (Multimedia, Altern. RAB Param. = speech) + RNC A->>MSC A: RANAP RAB Assignment Response (Successful) + Note right of MSC A: ● ● ● ● ● ● ● ● + Note right of MSC A: Core Network Procedure + MSC B->>UE B: MODIFY (BCmultimedia, NISUid) + UE B->>MSC B: MODIFY COMPLETE (BCmultimedia) + +``` + +Sequence diagram for Figure 4.2.5.2/2: Network-Initiated Service change from UTRAN speech to multimedia requested, accepted in case the RAB is modified on the initiating side before receiving the response to the service change request from the remote side. + +**Figure 4.2.5.2/2: Network-Initiated Service change from UTRAN speech to multimedia requested, accepted in case the RAB is modified on the initiating side before receiving the response to the service change request from the remote side** + + + +This sequence diagram illustrates a network-initiated service change from UTRAN speech to multimedia, where RNC B fails. The participants are UE A, RNC A, MSC A, MSC B, RNC B, and UE B. The process begins with RNC A sending a RANAP Modify Request (alternate configuration requested) to MSC A. MSC A responds with a MODIFY (BCmultimedia, NISUid) to UE A. UE A responds with a MODIFY COMPLETE (BCmultimedia). A 'Core Network Procedure' is indicated between MSC A and MSC B. MSC B sends a MODIFY (BCmultimedia, NISUid) to UE B. UE B responds with a MODIFY COMPLETE (BCmultimedia). MSC B then sends a RANAP RAB Assignment Request (BCmultimedia) to RNC B. RNC B responds with a RANAP RAB Assignment Response (failure). MSC B then sends a MODIFY (BCspeech) to UE B. UE B responds with a MODIFY COMPLETE (BCspeech). MSC B then sends a MODIFY (BCspeech) to MSC A. MSC A responds with a MODIFY COMPLETE (BCspeech). + +``` + +sequenceDiagram + participant UE A + participant RNC A + participant MSC A + participant MSC B + participant RNC B + participant UE B + Note right of RNC A: RANAP Modify Request (alternate configuration requested) + RNC A->>MSC A: MODIFY (BCmultimedia, NISUid) + MSC A->>UE A: MODIFY COMPLETE (BCmultimedia) + Note right of MSC A: ● ● ● ● ● ● ● ● + Note right of MSC A: Core Network Procedure + MSC B->>UE B: MODIFY (BCmultimedia, NISUid) + UE B->>MSC B: MODIFY COMPLETE (BCmultimedia) + MSC B->>RNC B: RANAP RAB Assignment Request (BCmultimedia) + RNC B->>MSC B: RANAP RAB Assignment Response (failure) + Note right of MSC B: ● ● ● ● ● ● ● ● + MSC B->>UE B: MODIFY (BCspeech) + UE B->>MSC B: MODIFY COMPLETE (BCspeech) + MSC B->>MSC A: MODIFY (BCspeech) + MSC A->>UE A: MODIFY COMPLETE (BCspeech) + +``` + +Sequence diagram for Figure 4.2.5.2/3: Network-Initiated Service change from UTRAN speech to multimedia, RNC B failure in case the RAB on the initiating side is not modified before receiving the response to the service change request from the remote side. + +**Figure 4.2.5.2/3: Network-Initiated Service change from UTRAN speech to multimedia, RNC B failure in case the RAB on the initiating side is not modified before receiving the response to the service change request from the remote side** + + + +The sequence diagram illustrates the interaction between UE A, RNC A, MSC A, MSC B, RNC B, and UE B. The process begins with RNC A sending a RANAP Modify Request (alternate configuration requested) to MSC A. MSC A responds with MODIFY (BCmultimedia, NISUid) to RNC A, which then sends MODIFY COMPLETE (Bcmultimedia) to UE A. Simultaneously, RNC A sends a RANAP RAB Assignment Modify (Multimedia, Altern. RAB Param. = speech) to MSC A, which responds with RANAP RAB Assignment Response (Successful). A 'Core Network Procedure' is indicated between MSC A and MSC B. MSC B sends MODIFY (BCmultimedia, NISUid) to UE B, which responds with MODIFY COMPLETE (BCmultimedia). MSC B then sends a RANAP RAB Assignment Request(BCmultimedia) to RNC B, which fails and responds with RANAP RAB Assignment Response(failure). RNC B then sends MODIFY (BCspeech) to UE B, which responds with MODIFY COMPLETE (BCspeech). Finally, RNC A sends a RANAP RAB Assignment Modify (Speech) to MSC A, which responds with RANAP RAB Assignment Response (Successful). + +``` +sequenceDiagram + participant UE A + participant RNC A + participant MSC A + participant MSC B + participant RNC B + participant UE B + + Note right of MSC A: Core Network Procedure + + RNC A->>MSC A: RANAP Modify Request (alternate configuration requested) + MSC A->>RNC A: MODIFY (BCmultimedia, NISUid) + RNC A->>UE A: MODIFY COMPLETE (Bcmultimedia) + RNC A->>MSC A: RANAP RAB Assignment Modify (Multimedia, Altern. RAB Param. = speech) + MSC A->>RNC A: RANAP RAB Assignment Response (Successful) + MSC A->>MSC B: + MSC B->>UE B: MODIFY (BCmultimedia, NISUid) + UE B->>MSC B: MODIFY COMPLETE (BCmultimedia) + MSC B->>RNC B: RANAP RAB Assignment Request(BCmultimedia) + RNC B-->>MSC B: RANAP RAB Assignment Response(failure) + RNC B->>UE B: MODIFY (BCspeech) + UE B->>MSC B: MODIFY COMPLETE (BCspeech) + RNC A->>MSC A: RANAP RAB Assignment Modify (Speech) + MSC A->>RNC A: RANAP RAB Assignment Response (Successful) +``` + +Sequence diagram showing a network-initiated service change from UTRAN speech to multimedia, with RNC B failure. + +**Figure 4.2.5.2/4: Network-Initiated Service change from UTRAN speech to multimedia, RNC B failure in case the RAB is modified on the initiating side before receiving the response to the service change request from the remote side** + + + +``` + +sequenceDiagram + participant UE A + participant RNC A + participant MSC + participant MSC B + participant RNC B + participant UE B + + Note over RNC A, MSC: RANAP Modify Request +(alternate configuration requested =Multimedia) + MSC->>UE A: MODIFY (BCmultimedia, NISUId) + UE A->>MSC: MODIFY COMPLETE +(BCmultimedia) + + Note over MSC, MSC B: Core Network +Procedure + + MSC B->>UE B: MODIFY (BCmultimedia, +NISUId) + UE B->>MSC B: MODIFY COMPLETE +(BCmultimedia) + + MSC B->>RNC B: RANAP RAB Assignment Modify +(Multimedia, Altern. RAB Param= Speech) + RNC B->>MSC B: RANAP RAB Assignment Response +(Multimedia, Successful) + + Note over MSC, MSC B: Core Network +Procedure + + MSC B->>RNC A: RANAP RAB Assignment Modify +(Multimedia, Altern. RAB Param. = speech) + RNC A->>MSC: RANAP RAB Assignment +Response (failure) + + MSC->>UE A: MODIFY +(BCspeech) + UE A->>MSC: MODIFY COMPLETE +(BCspeech) + + Note over MSC, MSC B: Core Network +Procedure + + MSC->>UE B: MODIFY +(BCspeech) + UE B->>MSC B: MODIFY COMPLETE +(BCspeech) + + MSC B->>RNC B: RANAP RAB Assignment Modify +(Speech) + RNC B->>MSC B: RANAP RAB Assignment +Response (Speech) + + Note over MSC, MSC B: Core Network +Procedure + +``` + +Sequence diagram illustrating a network-initiated service change from UTRAN speech to multimedia requested, with a failure in RNC A. + +**Figure 4.2.5.2/5: Network-Initiated Service change from UTRAN speech to multimedia requested, RNC A failure in case the RAB is modified on the initiating side after receiving the response to the service change request from the remote side** + + + +``` + +sequenceDiagram + participant UE A + participant RNC A + participant MSC + participant MSC B + participant RNC B + participant UE B + + RNC A->>MSC: RANAP Modify Request +(alternate configuration requested =Multimedia) + MSC->>RNC A: MODIFY +(Bcmultimedia, NISUId) + RNC A->>UE A: MODIFY COMPLETE +(BCmultimedia) + Note over MSC, MSC B: Core Network Procedure + MSC->>MSC B: MODIFY +(BCmultimedia) + MSC B->>UE B: MODIFY COMPLETE +(BCmultimedia) + MSC->>RNC A: RANAP RAB Assignment Modify +(Multimedia, Altern. RAB Param. = speech) + RNC A->>MSC: RANAP RAB Assignment +Response (failure) + MSC B->>RNC B: RANAP RAB Assignment Modify +(Multimedia, Altern. RAB Param= Speech) + RNC B->>MSC B: RANAP RAB Assignment Response +(Multimedia, Successful) + MSC->>RNC A: MODIFY +(BCspeech) + RNC A->>UE A: MODIFY COMPLETE +(BCspeech) + Note over MSC, MSC B: Core Network Procedure + MSC->>MSC B: MODIFY +(BCspeech) + MSC B->>UE B: MODIFY COMPLETE +(BCspeech) + MSC B->>RNC B: RANAP RAB Assignment Modify +(Speech) + RNC B->>MSC B: RANAP RAB Assignment +Response (Speech) + Note over MSC, MSC B: Core Network Procedure + +``` + +Sequence diagram for Figure 4.2.5.2/6: Network-Initiated Service change from UTRAN speech to multimedia requested, RNC A failure in case the RAB is modified on the initiating side before receiving the response to the service change request from the remote side + +**Figure 4.2.5.2/6: Network-Initiated Service change from UTRAN speech to multimedia requested, RNC A failure in case the RAB is modified on the initiating side before receiving the response to the service change request from the remote side** + + + +``` + +sequenceDiagram + participant RNC 1 + participant MSC + participant RNC 2 + RNC 1->>MSC: RANAP Relocation Required + MSC->>RNC 2: RANAP Relocation Request (Alternative +RAB Parameters Value IE) + RNC 2->>MSC: RANAP Relocation Request Acknowledge + +``` + +Sequence diagram for Figure 4.2.5.2/7: Alternative RAB Parameters delivery during the relocation. + +**Figure 4.2.5.2/7: Alternative RAB Parameters delivery during the relocation** + +## 4.3 Core Network procedures + +In order to provide the capability in the network to transmit the request for service change (upgrade to multi-media and fallback to speech) both at call setup and during the active state of a call, the normal Out-of-Band Transcoder Control procedures, described in 3GPP TS 23.153 [2] shall be used. The following text describes the codec type to be used, the mapping between the terminal interface described above, and the different IEs to be used for the codec negotiation procedures at both the originating and the terminating MSC. + +### 4.3.1 Multimedia codec + +The codec negotiation procedures transmit an ordered list of preferred codecs from the originating to the terminating MSC. A node that requires interaction with the user plane will remove the codecs it does not support. The terminating MSC shall select the codec to use ("selected codec") from the list of available codecs for the call. This selection shall be based on the received list of codecs and on the information given by the terminating UE in the CALL CONFIRMED message. + +A dummy codec (defined in 3GPP TS 26.103 [4] for a BICC based CS core network and in 3GPP TS 29.007 [6] as dedicated RTP payload types for a SIP-I based CS core network) is included in the codec list to indicate that a multimedia call is requested. Two dummy codecs are defined: + +- Dummy codec 1 shall be used for a terminal-initiated service change from speech to multimedia. Based on the operator policy the dummy codec 1 may be used for the network-initiated service change from speech to multimedia, if one of the MSCs has not included the dummy codec 2 to the available codec list during the call setup phase. This dummy codec 1 is in the present document referred to as the 3G-324.M codec. It shall be supported by any SCUDIF compliant MSC. +- Dummy codec 2 shall be used for a network-initiated service change from speech to multimedia, if all the MSCs in the call have indicated the dummy codec 2 in the available codec list during the call setup phase. This codec is in the present document referred to as the 3G-324.M2 codec. The 3G-324.M2 codec is identical to the 3G-324.M codec except for the CoID. It shall be supported by any SCUDIF compliant MSC that supports a network-initiated service change from speech to multimedia. + +NOTE: An Rel-5 MSC does not support the 3G-324.M2 codec. A Rel-6 MSC not supporting the optional network-initiated service change procedures could also not support the 3G-324.M2 codec. + +These codec are in the present document referred to as the 3G-324.M codec. + +This codec is only used by the Core Network and shall not be sent from the terminal in the Supported Codec List IE. + +For a BICC based CS core network, the 3G-324.M codec shall be indicated to the MGW as codec media stream property in accordance with the 3GPP TS 29.232 [12]. The 3G-324.M codec shall be indicated to the MGW also if the 3G-324.M2 codec is selected in Out-of-Band Transcoder Control procedures. The MGW shall treat the User Plane configuration (SDU Format) of the 3G-324.M codec as for PCM, as defined in 3GPP TS 26.102 [13]. + +For a SIP-I based CS core network, instead of the 3G-324.M or 3G-324.M2 codecs, the CLEARMODE RTP payload type (see IETF RFC 4040 [18]) shall be indicated to the MGW as media type in accordance with the 3GPP TS 29.232 [12]. The MGW will treat the user plane for the Clearmode RTP payload type as defined in 3GPP TS 29.007 [6]. + +### 4.3.2 Originating side - initiation of call setup + +#### 4.3.2.1 Originating MSC Handling + +The originating MSC has a list of supported codec types, listed in order of preference. + +If the SETUP message received from the UE contains a Repeat Indicator with a value of "service change and fallback", in addition to a multimedia BC-IE and a speech BC-IE, the MSC shall include a 3G-324.M codec in the list of supported codec types according to the following rule: + +- If the multimedia BC-IE is listed first, then the 3G-324.M codec shall be the first codec in the list (see figure 4.15) If the originating MSC supports a network-initiated service change from speech to multimedia, it shall include the 3G-324.M2 codec as second codec in the list. +- If the speech BC-IE is listed first, then the 3G-324.M codec shall be the last codec in the list (see figure 4.16) sent by a originating MSC not supporting a network-initiated service change from speech to multimedia. If the originating MSC supports a network-initiated service change from speech to multimedia, the 3G-324.M codec shall be the last but one codec in the list and the 3G-324.M2 codec shall be the last codec in the list.. In the case that the maximum number of codecs is already reached before insertion of the 3G-324.M and possibly 3G-324.M2 codec(s), the optional speech codec(s) with the least preference shall be replaced by those codec(s). + +The list shall then be sent according to the Out-of-Band Transcoder Control codec negotiation procedures. The TMR field, although mandatory BICC/ISUP parameter, has no meaning when using OoBTC/BICC codec negotiation (the link characteristics and QoS are determined from the codec type and signalled to any intermediate switches via the + +bearer control protocol) and thus shall be set arbitrarily to "speech". A transit node that requires interaction with the user plane will remove from the list the codecs it does not support. If the 3G-324.M codec is not supported, and thus removed, the call shall be turned into a normal speech call (fallback to speech) and follow the normal call setup procedures. + + + +``` + +sequenceDiagram + participant O-UE + participant O-MSC + participant T-MSC + O-UE->>O-MSC: SETUP (RI, BCmm, BCsp) + O-MSC->>T-MSC: (List of Codecs = mm, x, y, z) + +``` + +Sequence diagram for Figure 4.15: Multimedia BC as first BC. It shows three entities: O-UE, O-MSC, and T-MSC. The O-UE sends a SETUP message to the O-MSC with parameters RI, BCmm, and BCsp. The O-MSC then sends a message to the T-MSC with a 'List of Codecs' containing 'mm, x, y, z', where 'mm' is the first codec listed. + +x, y, z: speech codecs. + mm: dummy multimedia codec 3G-324.M. + +NOTE: If the originating MSC supports incoming requests for a network-initiated service change from speech to multimedia, it shall include the 3G-324.M2 codec as second codec in the list after 3G-324.M. This is not depicted in the figure. + +**Figure 4.15: Multimedia BC as first BC** + + + +``` + +sequenceDiagram + participant O-UE + participant O-MSC + participant T-MSC + O-UE->>O-MSC: SETUP (RI, BCsp, BCmm) + O-MSC->>T-MSC: (List of Codecs = x, y, z, mm) + +``` + +Sequence diagram for Figure 4.16: Speech BC as first BC. It shows three entities: O-UE, O-MSC, and T-MSC. The O-UE sends a SETUP message to the O-MSC with parameters RI, BCsp, and BCmm. The O-MSC then sends a message to the T-MSC with a 'List of Codecs' containing 'x, y, z, mm', where 'mm' is the last codec listed. + +NOTE: If the originating MSC supports incoming requests for a network-initiated service change from speech to multimedia, it shall include the 3G-324.M2 codec as last codec in the list after 3G-324.M. This is not depicted in the figure. + +**Figure 4.16: Speech BC as first BC** + +#### 4.3.2.2 VMSC Handling at Originating Side + +Depending on operator policy, the VMSC may remove the 3G-324.M2 codec from the list of supported codec types if the call is routed to selected other PLMNs. + +NOTE: This enables the operator to block a network initiated upgrade if inter-operator accounting agreements do not allow this functionality, e.g. because billing schemes are not compatible for the network-initiated upgrade. + +### 4.3.3 Terminating side + +#### 4.3.3.1 HLR Interrogation + +The GMSC sends the Send Routing Information request with both the Network Signal Information and Network Signal Information 2 parameters. The Network Signal Information shall include the ISDN BC IE for the preferred service, and the Network Signal Information 2 includes the ISDN BC IE for the less preferred service. + +The functional behaviour of the HLR is described in 3GPP TS 23.018 [10]. The procedures specific to SCUDIF calls are specified in the subclause 4.3.3.1.3 for the HLR and 4.3.3.1.4 for the GMSC. The information elements specific to SCUDIF between the GMSC and the HLR are specified in subclauses 4.3.3.1.1 and 4.3.3.1.2. + +##### 4.3.3.1.1 Send Routing Info + +The following element specific to SCUDIF calls is defined for Send Routing Info: + +| Information element name | Required | Description | +|--------------------------|----------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| ISDN BC 2 | C | ISDN bearer capability 2. Shall be present for a SCUDIF call to indicate the less preferred service. | +| ISDN LLC 2 | C | ISDN lower layer compatibility 2. Shall be present for a SCUDIF call if necessary for the less preferred service, otherwise shall be absent. | +| ISDN HLC 2 | C | ISDN higher layer compatibility 2. Shall be present for a SCUDIF call if necessary for the less preferred service, otherwise shall be absent. | + +##### 4.3.3.1.2 Send Routing Info Ack + +The following elements specific to SCUDIF calls are defined for Send Routing Info Ack: + +| Information element name | Required | Description | +|---------------------------------|----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Roaming number 2 | C | E.164 number required to route the call to VMSCB (see 3GPP TS 23.003 [11]) for the less preferred service of a SCUDIF call. Shall be present for a SCUDIF call if the preferred service is not forwarded (i.e. either Roaming Number is present or the preferred service is not allowed) and the less preferred service is allowed and not forwarded, otherwise shall be absent. | +| Forwarded-to number 2 | C | E.164 number of the C subscriber for the less preferred service of a SCUDIF call. Shall be present if the HLR has determined that the less preferred service of a SCUDIF call is to be forwarded, otherwise shall be absent. | +| Long forwarded-to number 2 | C | Number of the C subscriber (see 3GPP TS 23.082 [15]) for the less preferred service of a SCUDIF call. Shall be present if the HLR has determined that the less preferred service of a SCUDIF call is to be forwarded, and GMSC and HLR support Long Forwarded-to Numbers, otherwise shall be absent. | +| Forwarded-to subaddress 2 | C | Subaddress of the C subscriber (see 3GPP TS 23.003 [11]) for the less preferred service of a SCUDIF call. Shall be present if the HLR has determined that the less preferred service of a SCUDIF call is to be forwarded and a forwarded-to subaddress is stored in the HLR in association with the forwarded-to number 2, otherwise shall be absent. | +| Notification to calling party 2 | C | Indication of whether the calling party is to be notified that the call has been forwarded if the less preferred service of a SCUDIF call is kept. Shall be present if the HLR has determined that the less preferred service of a SCUDIF call is to be forwarded, otherwise shall be absent. | +| Forwarding reason 2 | C | Indication of why the call has been forwarded (unconditionally or on mobile subscriber not reachable) for the less preferred service of a SCUDIF call. Shall be present if the HLR has determined that the less preferred service of a SCUDIF call is to be forwarded, otherwise shall be absent. | +| SS-List 2 | C | List of SS-codes for the less preferred service of a SCUDIF call. Shall be present if the HLR has determined that the less preferred service of a SCUDIF call is allowed, otherwise shall be absent. | +| Basic Service Code 2 | C | Indicates the type of the basic service for the less preferred service, i.e. teleservice or bearer service. | +| Allowed Services | C | Shall be present for SCUDIF calls. Indicates which services are available for that call. | +| Unavailability Cause | C | Indicates the reason for which one of the services of a SCUDIF call is not available. Shall be present for SCUDIF calls if one service is not available. | + +##### 4.3.3.1.3 Handling of mobile terminating calls in the HLR + +The procedures specific to SCUDIF calls in the HLR are specified within this subclause: + +- Procedure SCUDIF\_Subscription\_Check\_HLR +- Procedure SCUDIF\_CAMEL\_CSI\_Check\_HLR +- Procedure SCUDIF\_Set\_Second\_Service\_when\_Forwarded + +- Procedure SCUDIF\_Set\_Correct\_PLMN\_BC +- Procedure SCUDIF\_Check\_Second\_Service\_before\_Negative\_Response +- Procedure SCUDIF\_Check\_Second\_Service\_after\_PRN +- Procedure SCUDIF\_Check\_Second\_Service\_when\_Forwarded + + + +**procedure SCUDIF\_Subscription\_Check\_HLR** SCSC\_HLR1(2) + +Procedure in the HLR to check the subscription for the second service and store the unavailability cause if one of the services is not available + +``` +graph TD; Start([ ]) --> D1{Second Network Signal Info Present?}; D1 -- no --> Error((X)); D1 -- Yes --> P1[Store Result for first service]; P1 --> D2{result=fail?}; D2 -- no --> P2[Allowed Services := both]; D2 -- yes --> D3{service related negative response?}; D3 -- no --> Error; D3 -- yes --> P3[Unavailability Cause := negative response]; P3 --> P4[Allowed Services := second Service]; P4 --> P5[requested service := Network Signal Info 2]; P5 --> End1([1]); P2 --> End2([1]); +``` + +Flowchart for procedure SCUDIF\_Subscription\_Check\_HLR. It starts with a connector, followed by a decision 'Second Network Signal Info Present?'. If 'no', it goes to an error connector. If 'Yes', it goes to 'Store Result for first service', then 'result=fail?'. If 'no', it goes to 'Allowed Services := both', then connector '1'. If 'yes', it goes to 'service related negative response?'. If 'no', it goes to the error connector. If 'yes', it goes to 'Unavailability Cause := negative response', then 'Allowed Services := second Service', then 'requested service := Network Signal Info 2', then connector '1'. + +Figure 4.16A: Procedure SCUDIF\_Subscription\_Check\_HLR (sheet 1) + + + +**procedure SCUDIF\_Subscription\_Check\_HLR** SCSC\_HLR2(2) + +Procedure in the HLR to check the subscription for the second service and store the unavailability cause if one of the services is not available + +``` +graph TD; 1((1)) --> SC[Subscription_Check_HLR]; SC -.-> SC_desc[for second service]; SC --> R1{result=fail?}; R1 -- no --> R2{result for first service =fail?}; R1 -- yes --> Exit((X)); R2 -- yes --> NR[negative response := negative response for first service]; R2 -- no --> UC[Unavailability Cause := negative response]; UC --> AS[Allowed Services := first Service]; AS --> RP[result := pass]; NR --> Exit; RP --> Exit; +``` + +Flowchart for procedure SCUDIF\_Subscription\_Check\_HLR. It starts at connector 1, goes to Subscription\_Check\_HLR (for second service), then checks if result=fail?. If no, it checks if result for first service =fail?. If yes, negative response := negative response for first service. If no, Unavailability Cause := negative response, Allowed Services := first Service, result := pass. Both result=fail? (yes) and result := pass lead to the exit connector. + +Figure 4.16B: Procedure SCUDIF\_Subscription\_Check\_HLR (sheet 2) + + + +**procedure SCUDIF\_CAMEL\_CSI\_Check\_HLR** 1(1) + +Procedure in the HLR to check the CAMEL data for the second service to know if CAMEL is active for that call + +``` +graph TD; Start([Start]) --> D1{Network Signal Info 2 present?}; D1 -- no --> Join(( )); D1 -- yes --> D2{Interrogation on second service?}; D2 -- yes --> Join; D2 -- no --> D3{result = CSI active?}; D3 -- yes --> Join; D3 -- no --> P1[CAMEL_CSI Subscription_Check]; P1 -.-> Note[for second service]; P1 --> Join; +``` + +Flowchart for procedure SCUDIF\_CAMEL\_CSI\_Check\_HLR. It starts with a start symbol, followed by a decision 'Network Signal Info 2 present?'. If 'no', it goes to a join symbol. If 'yes', it goes to 'Interrogation on second service?'. If 'yes', it goes to a join symbol. If 'no', it goes to 'result = CSI active?'. If 'yes', it goes to a join symbol. If 'no', it goes to 'CAMEL\_CSI Subscription\_Check' which is linked to a note 'for second service'. All paths lead to a join symbol at the bottom. + +Figure 4.16C: Procedure SCUDIF\_CAMEL\_CSI\_Check\_HLR + + + +procedure SCUDIF\_Set\_Second\_Service\_when\_forwarded 1(1) + +Procedure in the HLR to set the forwarding information to the correct service for SCUDIF + +``` +graph TD; Start([ ]) --> D1{Network Signal Info 2 present?}; D1 -- no --> R2[result := continue]; D1 -- yes --> D2{Interrogation on second service?}; D2 -- no --> S1[Store Forwarding Information for first Service]; D2 -- yes --> S2[Store Forwarding Information for second Service]; S1 --> D3{first service allowed?}; S2 --> D3; D3 -- no --> R2; D3 -- yes --> R1[result := SRI_Ack]; R1 --> End((X)); R2 --> End; +``` + +Flowchart for procedure SCUDIF\_Set\_Second\_Service\_when\_forwarded. It starts with a connector, followed by a decision 'Network Signal Info 2 present?'. If 'no', it goes to 'result := continue'. If 'yes', it goes to 'Interrogation on second service?'. If 'no', it goes to 'Store Forwarding Information for first Service'. If 'yes', it goes to 'Store Forwarding Information for second Service'. Both store blocks lead to 'first service allowed?'. If 'no', it goes to 'result := continue'. If 'yes', it goes to 'result := SRI\_Ack'. Both result blocks lead to an exit connector. + +Figure 4.16D: Procedure SCUDIF\_Set\_Second\_Service\_when\_Forwarded + + + +procedure SCUDIF\_Set\_Correct\_PLMN\_BC 1(1) + +Procedure in the HLR to always set the speech PLMN BC for SCUDIF calls + +``` + +graph TD + Start([ ]) --> D1{Network Signal Info 2 +present?} + D1 -- no --> R3[result := +set_PLMN_BC] + D1 -- yes --> D2{Both services +allowed?} + D2 -- no --> P1[PLMN BC := +BC for +allowed service] + D2 -- yes --> D3{Interrogation +on the first +service?} + D3 -- yes --> P2[PLMN BC := +BC for +speech service] + D3 -- no --> D4{Routing address +of first service +is MSRN?} + D4 -- no --> R1[result := SRI_Ack] + D4 -- yes --> P3[Copy MSRN for first +service to MSRN for +second service] + P3 --> R1 + P1 --> R2[result := +continue] + P2 --> R2 + R1 --> End(( )) + R2 --> End + R3 --> End + +``` + +Flowchart for procedure SCUDIF\_Set\_Correct\_PLMN\_BC. The process starts and checks if 'Network Signal Info 2' is present. If no, it sets result to 'set\_PLMN\_BC'. If yes, it checks if 'Both services' are allowed. If no, it sets 'PLMN BC' for the allowed service and continues. If yes, it checks if 'Interrogation' is on the first service. If yes, it sets 'PLMN BC' for speech service and continues. If no, it checks if the 'Routing address' is MSRN. If no, result is 'SRI\_Ack'. If yes, it copies MSRN and then result is 'SRI\_Ack'. All paths lead to an end terminal. + +Figure 4.16E: Procedure SCUDIF\_Set\_Correct\_PLMN\_BC + + + +**procedure SCUDIF\_Check\_second\_service\_before\_Negative\_response** 1(1) + +Procedure in the HLR to check the second service before sending a SRI negative response back to the GMSC + +``` +graph TD; Start([ ]) --> D1{Second Network Signal info present?}; D1 -- no --> R1[result := fail]; D1 -- yes --> D2{Interrogation on second service?}; D2 -- no --> D3{Service related negative response?}; D3 -- yes --> P1[requested service := second signal network info]; P1 --> P2[unavailability cause := negative response]; P2 --> P3[allowed services := second service]; P3 --> R2[result := second interrogation]; D3 -- no --> R3[result := fail]; D2 -- yes --> D4{Interrogation on first service failed?}; D4 -- no --> P4[restore routing information for first service]; P4 --> P5[unavailability cause := negative response]; P5 --> P6[allowed services := first service]; P6 --> R4[result := pass]; D4 -- yes --> P7[negative response := negative response for first service]; P7 --> R5[result := fail]; R1 --> End(( )); R2 --> End; R3 --> End; R4 --> End; R5 --> End; +``` + +Flowchart for procedure SCUDIF\_Check\_second\_service\_before\_Negative\_response. It starts with a connector, checks if second network signal info is present. If no, result is fail. If yes, it checks if interrogation on second service is present. If no, it checks if service related negative response is present. If yes, it sets requested service, unavailability cause, and allowed services to second service, then result is second interrogation. If no, result is fail. If interrogation on second service is present, it checks if interrogation on first service failed. If no, it restores routing information, sets unavailability cause and allowed services to first service, then result is pass. If yes, it sets negative response for first service and result is fail. All results converge to an exit connector. + +Figure 4.16F: Procedure SCUDIF\_Check\_Second\_Service\_before\_Negative\_Response + + + +procedure SCUDIF\_Check\_Second\_Service\_after\_PRN 1(1) + +Procedure in the HLR to check the second service after PRN response has been received + +``` +graph TD; Start([ ]) --> D1{Network Signal Info 2 present?}; D1 -- no --> R1[result := continue]; D1 -- yes --> D2{Interrogation on second service?}; D2 -- yes --> S2[Store routeing information for the second service]; D2 -- no --> S1[Store routeing information for the first service]; S1 --> Q[requested service := second network signal info]; S2 --> Q; Q --> R2[result := second interrogation]; R1 --> End(( )); R2 --> End +``` + +Flowchart for procedure SCUDIF\_Check\_Second\_Service\_after\_PRN. It starts with a connector, followed by a decision 'Network Signal Info 2 present?'. If 'no', it goes to 'result := continue'. If 'yes', it goes to another decision 'Interrogation on second service?'. If 'yes', it goes to 'Store routeing information for the second service'. If 'no', it goes to 'Store routeing information for the first service'. Both store blocks lead to 'requested service := second network signal info', which then leads to 'result := second interrogation'. Both 'result := continue' and 'result := second interrogation' lead to an exit connector. + +Figure 4.16G: Procedure SCUDIF\_Check\_Second\_Service\_after\_PRN + + + +procedure SCUDIF\_Check\_Second\_Service\_when\_forwarded 1(1) + +Procedure in the HLR to check the second service when a service is forwarded + +``` +graph TD; Start([ ]) --> D1{Network Signal Info 2 present?}; D1 -- no --> R1[result := continue]; D1 -- yes --> D2{CSI active?}; D2 -- yes --> R1; D2 -- no --> D3{Interrogation on second service?}; D3 -- yes --> S2[Store routing information for the second service]; D3 -- no --> S1[Store routing information for the first service]; S1 --> Q[requested service := Network Signal Info 2]; S2 --> Q; Q --> R2[result := second interrogation]; R2 --> End((X)); R1 --> End; +``` + +Flowchart for procedure SCUDIF\_Check\_Second\_Service\_when\_forwarded. The flow starts with a start symbol, followed by a decision 'Network Signal Info 2 present?'. If 'no', it goes to 'result := continue'. If 'yes', it goes to 'CSI active?'. If 'yes', it goes to 'result := continue'. If 'no', it goes to 'Interrogation on second service?'. If 'yes', it goes to 'Store routing information for the second service'. If 'no', it goes to 'Store routing information for the first service'. Both store blocks lead to 'requested service := Network Signal Info 2'. This leads to 'result := second interrogation', which then leads to an end symbol. + +**Figure 4.16H: Procedure SCUDIF\_Check\_Second\_Service\_when\_Forwarded** + +##### 4.3.3.1.4 Handling of mobile terminating calls in the GMSC + +The procedures specific to SCUDIF calls in the GMSC are specified within this subclause: + +- Procedure SCUDIF\_Negative\_SRI\_Response\_Handling +- Procedure SCUDIF\_Check\_Service\_Availability +- Procedure SCUDIF\_Check\_Service\_Compatibility + + + +**procedure SCUDIF\_Negative\_SRI\_Response\_Handling** SC\_SRI1(1) + +Procedure in the GMSC to handle a second interrogation for SCUDIF call when a negative response is received + +``` +graph TD; Start([ ]) --> SCUDIF{SCUDIF call?}; SCUDIF -- no --> Fail1[result := fail]; SCUDIF -- yes --> Second{second interrogation?}; Second -- no --> Service{service related error?}; Service -- no --> Fail2[result := fail]; Service -- yes --> Fallback[Fallback to the less preferred service]; Fallback --> Retry[result := retry]; Second -- yes --> First{first interrogation successful?}; First -- no --> Fail3[result := fail]; First -- yes --> Retrieve[retrieve SRI result from first interrogation]; Retrieve --> Pass[result := pass]; Fail1 --> End(( )); Fail2 --> End; Fail3 --> End; Pass --> End; Retry --> End; +``` + +Flowchart for procedure SCUDIF\_Negative\_SRI\_Response\_Handling. It starts with a start node, followed by a decision 'SCUDIF call?'. If 'no', it goes to 'result := fail'. If 'yes', it goes to 'second interrogation?'. If 'no', it goes to 'service related error?'. If 'no', it goes to 'result := fail'. If 'yes', it goes to 'Fallback to the less preferred service', then 'result := retry'. If 'yes' from 'second interrogation?', it goes to 'first interrogation successful?'. If 'no', it goes to 'result := fail'. If 'yes', it goes to 'retrieve SRI result from first interrogation', then 'result := pass'. All 'result' nodes converge to an end node. + +Figure 4.16I: Procedure SCUDIF\_Negative\_SRI\_Response\_Handling + +###### procedure SCUDIF\_Check\_Service\_Availability + +SC\_S\_A1(1) + +Procedure in the GMSC to fallback to a single service if one of the services of a SCUDIF call is unavailable + + + +``` +graph TD; Start([ ]) --> SCUDIF{SCUDIF call?}; SCUDIF -- no --> result1[result := continue]; SCUDIF -- yes --> Indicator{Allowed services indicator present?}; Indicator -- no --> Second{second interrogation?}; Second -- yes --> Result[Result is for the less preferred service]; Result --> result2[result := continue]; Second -- no --> MSRN{MSRN included?}; MSRN -- yes --> First[first service]; MSRN -- no --> Store[Store SRI for preferred service]; Store --> result3[result := second_SRI]; Indicator -- yes --> Value{Value of Allowed services indicator ?}; Value -- both --> Fallback1[Fallback to the less preferred service]; Value -- second service --> Fallback2[Fallback to the preferred service]; Fallback1 --> Merge(( )); Fallback2 --> Merge; Merge --> result4[result := continue]; result1 --> End(( )); result2 --> End; result3 --> End; result4 --> End; +``` + +Flowchart for procedure SCUDIF\_Check\_Service\_Availability. It starts with a connector, followed by a decision 'SCUDIF call?'. If 'no', it goes to a 'result := continue' block. If 'yes', it checks 'Allowed services indicator present?'. If 'no', it checks 'second interrogation?'. If 'yes', it goes to 'Result is for the less preferred service' then to 'result := continue'. If 'no', it checks 'MSRN included?'. If 'yes', it goes to 'first service' path. If 'no', it goes to 'Store SRI for preferred service' then to 'result := second\_SRI'. If 'Allowed services indicator present?' is 'yes', it checks 'Value of Allowed services indicator ?'. If 'both', it goes to 'Fallback to the less preferred service'. If 'second service', it goes to 'Fallback to the preferred service'. Both lead to a merge point before 'result := continue'. All three 'result' blocks lead to an exit connector. + +Figure 4.16J: Procedure SCUDIF\_Check\_Service\_Availability + + + +procedure SCUDIF\_Check\_Service\_Compatibility SC\_S\_C1(1) + +Procedure in the GMSC to fallback to a single service if the services of a SCUDIF call have different destination + +``` + +graph TD + Start([ ]) --> SCUDIF{SCUDIF call?} + SCUDIF -- no --> Exit(( )) + SCUDIF -- yes --> MSRN{MSRN provided for preferred service?} + MSRN -- yes --> FwdData{Forwarding data provided for less preferred service?} + MSRN -- no --> Identical{Forwarded number identical for both services?} + FwdData -- yes --> Fallback[Fallback to the preferred service] + FwdData -- no --> Identical + Identical -- yes --> Fallback + Identical -- no --> Exit + Fallback --> Exit + +``` + +Flowchart for procedure SCUDIF\_Check\_Service\_Compatibility. It starts with a connector symbol, followed by a decision 'SCUDIF call?'. If 'no', it goes to an exit symbol. If 'yes', it goes to 'MSRN provided for preferred service?'. If 'yes', it goes to 'Forwarding data provided for less preferred service?'. If 'no', it goes to 'Forwarded number identical for both services?'. If 'yes' to 'Forwarding data provided for less preferred service?' or 'Forwarded number identical for both services?', it goes to 'Fallback to the preferred service'. If 'no' to 'Forwarded number identical for both services?', it goes to the exit symbol. The 'Fallback to the preferred service' block leads to the exit symbol. + +**Figure 4.16K: Procedure SCUDIF\_Check\_Service\_Compatibility** + +#### 4.3.3.1a GMSC Handling at Terminating Side + +Depending on operator policy, the GMSC may remove the 3G-324.M2 codec from the list of supported codec types if the call is received from selected other PLMNs. + +**NOTE:** This enables the operator to block a network initiated upgrade if inter-operator accounting agreements do not allow this functionality, e.g. because billing schemes are not compatible for the network-initiated upgrade. + +#### 4.3.3.2 Terminating MSC Handling + +The terminating MSC receives the list of supported codec types, including the 3G-324.M codec and possibly the 3G-324.M2 codec. It shall then send a SETUP message towards the terminating UE including a Repeat Indicator with the value "service change and fallback" and two BC-IEs, according to the following rule: + +- if the 3G-324.M codec is the first (preferred) codec in the list of supported codecs, then the first BC-IE in the SETUP message is the multimedia BC-IE, and the second BC-IE is the speech BC-IE (see figure 4.17); +- if the 3G-324.M codec is in the list of supported codec types, but not in the first position, then the first BC-IE in the SETUP message is the speech BC-IE, and the second BC-IE is the multimedia BC-IE (see figure 4.18). + +The terminating UE answers according to its capabilities in the CALL CONFIRMED message. The terminating MSC shall determine the Selected Codec and construct the list of available codecs according to the following rules: + +- If no Repeat Indicator is included, and only a speech BC-IE is received, the MSC shall choose a speech codec as the Selected Codec according to the normal mechanism, and no 3G-324.M codec shall be inserted in the list of available codecs (see figure 4.19). +- If no Repeat Indicator is included, and only a multimedia BC-IE is received, the MSC shall choose the 3G-324.M codec as the Selected Codec, and only the 3G-324.M codec shall be inserted in the list of available codecs (see figure 4.20). +- If the Repeat Indicator is included, and the speech BC\_IE is the first BC-IE and the multimedia BC-IE is the second BC-IE, the MSC shall choose a speech codec as the Selected Codec according to the normal mechanism, and both the 3G-324.M codec and speech codecs shall be inserted in the list of available codecs (see figure 4.21). If the terminating MSC supports incoming requests for a network-initiated service change from speech to multimedia and was offered the 3G-324.M2 codec and the terminal had indicated in the CALL CONFIRMED message with the "Enhanced Network-initiated ICM" (ENICM) Capability for the support of Network-initiated service upgrade to multimedia, the 3G-324.M codec shall be the last but one codec in the list and the 3G-324.M2 codec shall be the last codec in the list. +- If the Repeat Indicator is included, and the multimedia BC-IE is the first BC-IE and the speech BC-IE is the second BC-IE, the Selected Codec shall be the 3G-324.M codec, and both the 3G-324.M codec and speech codecs shall be inserted in the list of available codecs (see figure 4.22). If the terminating MSC supports incoming requests for a network-initiated service change from speech to multimedia and was offered the 3G-324.M2 codec and the terminal had indicated in the CALL CONFIRMED message with the "Enhanced Network-initiated ICM" (ENICM) Capability for the support of Network-initiated service upgrade to multimedia, the terminating MSC it shall include the 3G-324.M2 codec as second codec in the list of available codecs. + +The Selected Codec and the list of available codecs shall be sent back to the originating MSC according to the normal codec negotiation procedure. + + + +``` + +sequenceDiagram + participant O-MSC + participant T-MSC + participant T-UE + O-MSC->>T-MSC: (List of Codecs = mm, x, y, z) + T-MSC->>T-UE: SETUP (RI, BCmm, BCsp) + +``` + +Sequence diagram for Figure 4.17: 3G-324M codec first. It shows three lifelines: O-MSC, T-MSC, and T-UE. O-MSC sends a message '(List of Codecs = mm, x, y, z)' to T-MSC. T-MSC then sends a 'SETUP (RI, BCmm, BCsp)' message to T-UE. + +NOTE: The 3G-324.M2 codec may be included the list in addition to 3G-324.M. This is not depicted in the figure. + +**Figure 4.17: 3G-324M codec first** + + + +``` + +sequenceDiagram + participant O-MSC + participant T-MSC + participant T-UE + O-MSC->>T-MSC: (List of Codecs = x, y, z, mm) + T-MSC->>T-UE: SETUP (RI, BCsp, BCmm) + +``` + +Sequence diagram for Figure 4.18: Speech codec first. It shows three lifelines: O-MSC, T-MSC, and T-UE. O-MSC sends a message '(List of Codecs = x, y, z, mm)' to T-MSC. T-MSC then sends a 'SETUP (RI, BCsp, BCmm)' message to T-UE. + +NOTE: The 3G-324.M2 codec may be included the list in addition to 3G-324.M. This is not depicted in the figure. + +**Figure 4.18: Speech codec first** + + + +``` +sequenceDiagram + participant O-MSK + participant T-MSK + participant T-UE + Note right of T-UE: NOTE + T-UE->>T-MSK: CALL CONFIRMED (BCsp) + T-MSK->>O-MSK: (select = x, avail = x, y, z) +``` + +Sequence diagram for Figure 4.19: Speech only. Lifelines: O-MSK, T-MSK, T-UE. T-UE sends CALL CONFIRMED (BCsp) to T-MSK. T-MSK sends (select = x, avail = x, y, z) to O-MSK. A NOTE is present on the T-UE lifeline. + +NOTE: The actual speech codec is selected according to OoBTC procedures. + +**Figure 4.19: Speech only** + + + +``` +sequenceDiagram + participant O-MSK + participant T-MSK + participant T-UE + T-UE->>T-MSK: CALL CONFIRMED (BCmm) + T-MSK->>O-MSK: (select = mm, avail = mm) +``` + +Sequence diagram for Figure 4.20: Multimedia only. Lifelines: O-MSK, T-MSK, T-UE. T-UE sends CALL CONFIRMED (BCmm) to T-MSK. T-MSK sends (select = mm, avail = mm) to O-MSK. + +NOTE: The 3G-324.M2 codec may be included in the list of available codecs after the 3G-324.M codec. This is not depicted in the figure. + +**Figure 4.20: Multimedia only** + + + +``` +sequenceDiagram + participant O-MSK + participant T-MSK + participant T-UE + Note right of T-UE: NOTE + T-UE->>T-MSK: CALL CONFIRMED (RI, BCsp, BCmm) + T-MSK->>O-MSK: (select = x, avail = x, y, z, mm) +``` + +Sequence diagram for Figure 4.21: Speech preferred. Lifelines: O-MSK, T-MSK, T-UE. T-UE sends CALL CONFIRMED (RI, BCsp, BCmm) to T-MSK. T-MSK sends (select = x, avail = x, y, z, mm) to O-MSK. A NOTE is present on the T-UE lifeline. + +NOTE 1: The actual speech codec is selected according to OoBTC procedures. + +NOTE 2: If the terminating MSC supports incoming requests for a network-initiated service change from speech to multimedia and was offered the 3G-324.M2 codec and the terminal had indicated in the CALL CONFIRMED message with the "Enhanced Network-initiated ICM" (ENICM) Capability for the support of Network-initiated service upgrade to multimedia, the terminating MSC shall include the 3G-324.M2 codec as last codec in the list of available codecs after 3G-324.M. This is not depicted in the figure. + +**Figure 4.21: Speech preferred** + + + +``` + +sequenceDiagram + participant O-MSC + participant T-MSC + participant T-UE + T-UE->>T-MSC: CALL CONFIRMED (RI, BCmm, BCsp) + Note right of T-UE: NOTE + T-MSC->>O-MSC: (select = mm, avail = mm, x, y, z) + +``` + +Sequence diagram for Figure 4.22: Multimedia preferred. The diagram shows three lifelines: O-MSC, T-MSC, and T-UE. A message 'CALL CONFIRMED (RI, BCmm, BCsp)' is sent from T-UE to T-MSC. A return message '(select = mm, avail = mm, x, y, z)' is sent from T-MSC to O-MSC. A 'NOTE' is indicated on the T-UE lifeline. + +NOTE 1: The actual list of speech codecs is built according to OoBTC procedures. + +NOTE 2: If the terminating MSC supports incoming requests for a network-initiated service change from speech to multimedia and was offered the 3G-324.M2 codec and the terminal had indicated in the CALL CONFIRMED message with the "Enhanced Network-initiated ICM" (ENICM) Capability for the support of Network-initiated service upgrade to multimedia, the terminating MSC shall include the 3G-324.M2 codec as second codec in the list of available codecs after 3G-324.M. This is not depicted in the figure. + +**Figure 4.22: Multimedia preferred** + +### 4.3.4 Originating side - completion of call setup + +The originating MSC receives the Selected Codec and the list of available codecs, and, depending on the active mode, shall do the following: + +The call was set up with a multimedia BC-IE first: + +- if the Selected Codec is the 3G-324.M codec, no In-Call Modification procedure is necessary (see figure 4.23). If no speech codecs are included in the list of available codecs, all In-Call Modification procedures initiated by the UE using the speech BC-IE shall be rejected with a MODIFY REJECT message; +- if the Selected Codec is a speech codec, an In-Call Modification procedure to change to speech mode shall take place (see figure 4.24). If the 3G-324.M codec is not included in the list of available codecs, all In-Call Modification procedures initiated by the UE using the multimedia BC-IE shall be rejected with a MODIFY REJECT message. + +The call was set up with a speech BC-IE first: + +- if the Selected Codec is the 3G-324.M codec, an In-Call Modification procedure to change to multimedia mode shall take place (see figure 4.25). If no speech codecs are included in the list of available codecs, all In-Call Modification procedures initiated by the UE using the speech BC-IE shall be rejected with a MODIFY REJECT message; +- if the Selected Codec is a speech codec, no In-Call Modification procedure is necessary (see figure 4.26). If the 3G-324.M codec is not included in the list of available codecs, all In-Call Modification procedures initiated by the UE using the multimedia BC-IE shall be rejected with a MODIFY REJECT message. + + + +``` + +sequenceDiagram + participant O-UE + participant O-MSC + participant T-MSC + T-MSC->>O-MSC: (select = mm, avail = mm, x, y, z) + Note right of T-MSC: NOTE 1, +NOTE 2 + O-MSC->>O-UE: CONNECT + +``` + +Sequence diagram for Figure 4.23: Multimedia preferred, selected. The diagram shows three lifelines: O-UE, O-MSC, and T-MSC. A message '(select = mm, avail = mm, x, y, z)' is sent from T-MSC to O-MSC. A 'CONNECT' message is sent from O-MSC to O-UE. 'NOTE 1, NOTE 2' are indicated on the T-MSC lifeline. + +NOTE 1: Speech codecs (x, y, z) may or may not be present. If they are not present, subsequent MODIFY requests from the UE are rejected. + +NOTE 2: The 3G-324.M2 codec may be included in the list of available codecs after the 3G-324.M codec. This is not depicted in the figure. + +**Figure 4.23: Multimedia preferred, selected** + + + +``` + +sequenceDiagram + participant O-UE + participant O-MSC + participant T-MSC + T-MSC->>O-MSC: (select = x, avail = x, y, z, mm) + Note right of T-MSC: NOTE 1, +NOTE 3 + O-MSC->>O-UE: CONNECT + O-UE->>O-MSC: MODIFY (BCsp) + Note right of T-MSC: NOTE 2 + +``` + +Sequence diagram for Figure 4.24: Multimedia preferred, speech selected. The diagram shows three lifelines: O-UE, O-MSC, and T-MSC. T-MSC sends a message to O-MSC with parameters (select = x, avail = x, y, z, mm). O-MSC sends a CONNECT message to O-UE. O-UE sends a MODIFY (BCsp) message to O-MSC. + +NOTE 1: The multimedia codec (mm) may or may not be present. If it is not present, subsequent MODIFY requests from the UE are rejected. + +NOTE 2: see clause 4.2.3 for the In-Call Modification signalling. + +NOTE 3: The 3G-324.M2 codec may be included in the list of available codecs after the 3G-324.M codec. This is not depicted in the figure. + +**Figure 4.24: Multimedia preferred, speech selected** + + + +``` + +sequenceDiagram + participant O-UE + participant O-MSC + participant T-MSC + T-MSC->>O-MSC: (select = mm, avail = mm, x, y, z) + Note right of T-MSC: NOTE 1, +NOTE 3 + O-MSC->>O-UE: CONNECT + O-UE->>O-MSC: MODIFY (BCmm) + Note right of T-MSC: NOTE 2 + +``` + +Sequence diagram for Figure 4.25: Speech preferred, multimedia selected. The diagram shows three lifelines: O-UE, O-MSC, and T-MSC. T-MSC sends a message to O-MSC with parameters (select = mm, avail = mm, x, y, z). O-MSC sends a CONNECT message to O-UE. O-UE sends a MODIFY (BCmm) message to O-MSC. + +NOTE 1: Speech codecs (x, y, z) may or may not be present. If they are not present, subsequent MODIFY requests from the UE are rejected. + +NOTE 2: see clause 4.2.3 for the In-Call Modification signalling. + +NOTE 3: The 3G-324.M2 codec may be included in the list of available codecs after the 3G-324.M codec. This is not depicted in the figure. + +**Figure 4.25: Speech preferred, multimedia selected** + + + +``` + +sequenceDiagram + participant O-UE + participant O-MSC + participant T-MSC + T-MSC->>O-MSC: (select = x, avail = x, y, z, mm) + Note right of T-MSC: NOTE 1, +NOTE 2 + O-MSC->>O-UE: CONNECT + +``` + +Sequence diagram for Figure 4.26: Speech preferred, selected. The diagram shows three lifelines: O-UE, O-MSC, and T-MSC. T-MSC sends a message to O-MSC with parameters (select = x, avail = x, y, z, mm). O-MSC sends a CONNECT message to O-UE. + +NOTE 1: The multimedia codec (mm) may or may not be present. If it is not present, subsequent MODIFY requests from the UE are rejected. + +NOTE 2: The 3G-324.M2 codec may be included in the list of available codecs after the 3G-324.M codec. This is not depicted in the figure. + +**Figure 4.26: Speech preferred, selected** + +### 4.3.5 Service change during the active state + +Whenever an In-Call Modification procedure is invoked by a terminal, unless it is not allowed as determined at call setup, the following shall take place: + +- if the current mode is the speech mode and the MODIFY message contains a multimedia BC-IE, the normal Out-of-Band Transcoder Control procedures shall be invoked in order to change the Selected Codec to the 3G-324.M/3G-324.M2 codec; + +- if the current mode is the multimedia mode and the MODIFY message contains a speech BC-IE, the normal Out-of-Band Transcoder Control procedures shall be invoked in order to change the Selected Codec to the preferred speech codec. + +When a visited MSC invokes Network-initiated Service change in the active state (see Clause 4.2.5), this visited MSC shall also invoke the normal Out-of-Band Transcoder Control procedures in order to change the Selected Codec to speech or to the 3G-324.M/3G-324.M2 codec, respectively. + +For a User-initiated service change from speech to multimedia, the visited MSC shall use the 3G-324.M codec as Selected Codec. + +If the visited MSC received the 3G-324.M2 codec in the available codec list, the visited MSC shall use the 3G-324.M2 codec as Selected Codec for a Network-initiated Service change procedure from speech to multimedia. + +If the visited MSC did not receive the 3G-324.M2 codec in the available codec list, depending on operator policy, the visited MSC may either use the 3G-324.M codec as Selected Codec for a Network-initiated Service change procedure from speech to multimedia, or the visited MSC may not perform a Network-initiated Service change procedure from speech to multimedia. + +NOTE: The the 3G-324.M2 codec in the available codec list indicates that all nodes in the call support collecting appropriate charging records for the network initiated service change from speech to multimedia. + +If the 3G-324.M2 codec is used as Selected Codec in BICC signalling, the 3G-324.M codec shall be signalled instead to the MGW. + +NOTE: This avoids that MGWs need to support the 3G-324.M2 codec. + +The Codec Modification procedure shall be supported for service change. The use of mid-call codec negotiation procedure is optional for service change. + +When a MSC detects through an Out-of-Band Transcoder Control procedure that the selected codec has changed from a speech codec to the 3G-324.M codec, or vice-versa, it shall initiate an In-Call Modification procedure towards the UE with a MODIFY message containing the multimedia BC-IE (or the speech BC-IE), unless the new mode has been denied at call setup (see clause 4.2.4). + +#### 4.3.5.1 Mid-Call Codec Modification Procedure For Service Change + +The Codec Modification procedures as defined in 3GPP TS 23.153 [2] shall be applied with the following specific additional rules for the Service Change procedure. + +In order to prevent the MGW generating an error or seizing resources during the interim period, when its terminations are being altered and it may have a speech codec on one side of the context and the 3G-324M codec on the other side the Server shall modify the Stream-mode of the affected terminations to inactive during the Service change and shall restore the stream mode to active – (send/receive – bothway) on completion of the service change procedure. In order to restore the stream mode to active, the MSC servers shall use the “Modify Bearer Characteristics” procedure for Iu terminations and for Nb terminations towards the succeeding node with respect to the “Modify Codec” message. The MSC servers shall use the “Confirm Bearer Characteristics” procedure for Nb terminations towards the preceding node with respect to the “Modify Codec” message. + +If the affected termination's stream mode is inactive a MGW shall not reject a “Modify Bearer Characteristics” or a “Reserve Bearer Characteristics” procedure because the multimedia codec and a speech codec are interconnected simultaneously in the same context. + +For a service change where the CN shall initiate the IuUP on the Nb interface, the MSC server terminating the service change shall trigger the IuUP initialisation towards the core network by setting the IuUP initialisation direction to “out” in the “Confirm Bearer Characteristics” procedure for the corresponding termination towards the core network. + +Example call flows are shown in Figure 4.3.5.1/1 to 4.3.5.1/10. + + + +``` + +sequenceDiagram + participant RNC-A + participant MSC-A + participant MGW-A + participant Server B + participant MGW-B + participant MSC-C + participant MGW-C + participant RNC C + + RNC-A->>MSC-A: Direct Transfer [Modify (MuMe)] + MSC-A->>MGW-A: Modify Bearer Characteristics (Stream Mode=INACTIVE, New Codec = MuMe, 3GUP mode=transparent) + MGW-A-->>MSC-A: + MSC-A->>RNC-A: RAB Assign Modify (MuMe RAB parameters) + Note over MSC-A, MGW-A: Optionally to increase bandwidth + MSC-A->>MGW-A: Modify Bearer Request + MGW-A->>MSC-A: Modify Bearer Ack + RNC-A->>MSC-A: RAB Assign Modify Rsp + MSC-A->>MGW-A: Modify Bearer Characteristics (Stream Mode=INACTIVE, New Codec = MuMe, Dir=IN) + MGW-A-->>MSC-A: + MSC-A->>Server B: Modify Codec (Selected Codec = MuMe) + Server B->>MGW-B: Reserve Bearer Characteristics (Stream Mode=INACTIVE, New Codec = MuMe, Dir=IN) + MGW-B-->>Server B: + Note over Server B, MGW-B: Optionally to increase bandwidth + Server B->>MGW-B: Modify Bearer Request + MGW-B->>Server B: Modify Bearer Ack + Server B->>MGW-B: BNC Modified + MGW-B-->>Server B: + Server B->>MGW-B: Modify Bearer Characteristics (Stream Mode=INACTIVE, New Codec = MuMe, Dir=IN) + MGW-B-->>Server B: + Server B->>MGW-B: Modify Codec (Selected Codec = MuMe) + MGW-B-->>Server B: + Server B->>MSC-C: Reserve Bearer Char (Stream Mode=INACTIVE, New Codec = MuMe) + MSC-C->>MGW-C: + Note over MSC-C, MGW-C: Optionally to increase bandwidth + MSC-C->>MGW-C: Modify Bearer Request + MGW-C->>MSC-C: Modify Bearer Ack + MSC-C->>MGW-C: BNC Modified + MGW-C-->>MSC-C: + MSC-C->>RNC C: Direct Transfer [Modify (MuMe)] + RNC C->>MSC-C: Direct Transfer [Modify Complete(MuMe)] + MSC-C->>MGW-C: Modify Bearer Characteristics (Stream Mode=INACTIVE, codec = MuMe, mode=transparent) + MGW-C-->>MSC-C: + MSC-C->>RNC C: RAB Assign Modify (MuMe RAB parameters) + Note over MSC-C, RNC C: Optionally to increase bandwidth + RNC C->>MSC-C: Modify Bearer request + MSC-C->>RNC C: Modify Bearer Ack + RNC C->>MSC-C: RAB Assign Modify Rsp + +``` + +Sequence diagram for service change speech to MuMe. Lifelines: RNC-A, MSC-A, MGW-A, Server B, MGW-B, MSC-C, MGW-C, RNC C. The diagram shows a series of messages for modifying bearers and RABs across these components, with optional bandwidth increase steps at various points. + +**Figure 4.3.5.1/1: Service change speech to MuMe** + + + +``` + +sequenceDiagram + participant RNC-A + participant MSC-A + participant Server B + participant MSC-C + participant RNC C + + Note right of MSC-A: MGW-A + Note right of Server B: MGW-B + Note right of MSC-C: MGW-C + + MSC-C->>MGW-C: Modify Bearer Characteristics (Stream Mode=ACTIVE, codec = MuMe) + MGW-C-->>MSC-C: Confirm Bearer Char (Stream Mode=ACTIVE, Codec = MuMe, Dir=OUT) + MSC-C->>Server B: Iu FP Init + Server B-->>MSC-C: Iu FP Init Ack + Server B->>MGW-B: Successful Codec Modification + Server B->>MGW-B: Modify Bearer Characteristics (Stream Mode=ACTIVE, codec = MuMe) + MGW-B-->>Server B: Confirm Bearer Char (Stream Mode=ACTIVE, Codec = MuMe) + Server B->>MSC-A: Successful Codec Modification + MSC-A->>MGW-A: Modify Bearer Characteristics (Stream Mode=ACTIVE, codec = MuMe) + MGW-A-->>MSC-A: + MSC-A->>MGW-A: Modify Bearer Characteristics (Stream Mode=ACTIVE, codec = MuMe) + MGW-A-->>MSC-A: + MSC-A->>RNC-A: Direct Transfer [Modify_Complete (MuMe)] + +``` + +Sequence diagram showing service change speech to MuMe. Lifelines: RNC-A, MSC-A (with MGW-A), Server B (with MGW-B), MSC-C (with MGW-C), RNC C. The diagram shows messages for Iu FP Init, Successful Codec Modification, and Modify Bearer Characteristics with parameters like Stream Mode=ACTIVE and codec=MuMe. + +Figure 4.3.5.1/2: Service change speech to MuMe (continued) + + + +``` + +sequenceDiagram + participant RNC-A + participant MSC-A + participant MGW-A + participant Server B + participant MGW-B + participant MSC-C + participant MGW-C + participant RNC C + + Note right of MGW-A: Optionally to decrease bandwidth + Note right of MGW-B: Optionally to decrease bandwidth + Note right of RNC-A: Optionally for RFCI value correction + + RNC-A->>MSC-A: Direct Transfer [Modify (speech)] + MSC-A->>MGW-A: Modify Bearer Characteristics (Stream Mode=INACTIVE, New Codec = AMR, Dir=OUT, ) + MSC-A->>RNC-A: RAB Assign Modify (AMR RAB parameters) + RNC-A->>MSC-A: Iu FP Init + MSC-A->>RNC-A: Iu FP Init Ack + MSC-A->>MGW-A: Modify Bearer Request + MGW-A->>MSC-A: Modify Bearer Ack + MSC-A->>RNC-A: RAB Assign Modify Rsp + MSC-A->>MGW-A: Modify Bearer Characteristics (Stream Mode=INACTIVE, New Codec = AMR) + MGW-A->>Server B: Modify Codec (Selected Codec = AMR) + Server B->>MGW-B: Reserve Bearer Characteristics (Stream Mode=INACTIVE, New Codec = AMR, 3GUP Dir=IN, ) + MGW-B->>Server B: BNC Modified + Server B->>MGW-B: Modify Bearer Characteristics (Stream Mode=INACTIVE, New Codec = AMR, 3GUP Dir=IN, ) + MGW-B->>Server B: Modify Codec (Selected Codec= AMR) + Server B->>MGW-C: Reserve Bearer Char (Stream Mode=INACTIVE, New Codec = AMR, 3GUP Dir=IN, ) + MGW-C->>Server B: BNC Modified + Server B->>MGW-C: Modify Bearer Characteristics (Stream Mode=INACTIVE, codec = AMR, 3GUP Dir=IN, ) + MGW-C->>RNC C: Direct Transfer [Modify (AMR)] + MGW-C->>RNC C: Direct Transfer [Modify Complete(AMR)] + RNC C->>MGW-C: RAB Assign Modify (AMR RAB parameters) + RNC C->>MSC-C: Iu FP Init + MSC-C->>RNC C: Iu FP Init Ack + RNC C->>MGW-C: Modify Bearer request + MGW-C->>RNC C: Modify Bearer Ack + RNC C->>MSC-C: RAB Assign Modify Rsp + MGW-C->>Server B: Iu FP Init + Server B->>MGW-C: Iu FP Init Ack + MGW-A->>Server B: Iu FP Init + Server B->>MGW-A: Iu FP Init Ack + RNC-A->>MSC-A: Iu FP Init + MSC-A->>RNC-A: Iu FP Init Ack + +``` + +Sequence diagram for Service change MuMe to AMR. Lifelines: RNC-A, MSC-A, MGW-A, Server B, MGW-B, MSC-C, MGW-C, RNC C. The diagram shows the interaction for changing a service from MuMe to AMR, including bearer modification, RAB assignment, and Iu FP initialization across multiple network elements. + +Figure 4.3.5.1/3: Service change MuMe to AMR + + + +``` + +sequenceDiagram + participant RNC-A + participant MSC-A + participant Server B + participant MSC-C + participant RNC C + + Note right of MSC-A: Optionally to decrease bandwidth + MSC-C->>RNC C: Modify Bearer Characteristics (Stream Mode=ACTIVE, codec = AMR) + RNC C-->>MSC-C: Confirm Bearer Char (Stream Mode=ACTIVE, New Codec = AMR) + MSC-C->>Server B: Modify Bearer Request + Server B-->>MSC-C: Modify Bearer Ack + Note right of Server B: Successfully Codec Modification + Server B->>MSC-A: Modify Bearer Characteristics (Stream Mode=ACTIVE, codec = AMR) + MSC-A-->>Server B: Confirm Bearer Char (Stream Mode=ACTIVE, New Codec = AMR) + Note right of MSC-C: Optionally to decrease bandwidth + MSC-A->>Server B: Modify Bearer Request + Server B-->>MSC-A: Modify Bearer Ack + Note right of Server B: Successfully Codec Modification + MSC-A->>RNC-A: Modify Bearer Characteristics (Stream Mode=ACTIVE, codec = AMR) + RNC-A-->>MSC-A: + MSC-A->>RNC-A: Modify Bearer Characteristics (Stream Mode=ACTIVE, codec = AMR) + RNC-A-->>MSC-A: + MSC-A->>RNC-A: Direct Transfer (Modify_Complete (speech)) + +``` + +Sequence diagram for service change MuMe to AMR. Lifelines: RNC-A, MSC-A (with MGW-A), Server B (with MGW-B), MSC-C (with MGW-C), RNC C. The diagram shows a series of messages for bearer modification and codec change, including 'Modify Bearer Characteristics', 'Confirm Bearer Char', 'Modify Bearer Request', 'Modify Bearer Ack', and 'Successful Codec Modification'. There are optional bandwidth decrease steps and direct transfer messages at the end. + +Figure 4.3.5.1/4: Service change MuMe to AMR (continued) + +![Sequence diagram showing service change from MuMe to PCM(G.711) between RNC-A, MSC-A, Server B, MSC-C, and RNC C. The diagram includes lifelines for RNC-A, MSC-A (with MGW-A), Server B (with MGW-B), MSC-C (with MGW-C), and RNC C. The process involves Direct Transfer, Modify Bearer Characteristics, RAB Assign Modify, Iu FP Init/Ack, Modify Bearer Request/Ack, Modify Codec, Reserve Bearer Characteristics, BNC Modified, and Direct Transfer [Modify (AMR)] messages. Annotations include 'Optionally to decrease bandwidth' and specific parameter values like Stream Mode=INACTIVE, New Codec = AMR, Dir=OUT, and 3GUP Dir=IN.](8e80de0cac529b2c3775d677c5203133_img.jpg) + +The sequence diagram illustrates the interaction for a service change from MuMe to PCM(G.711). The lifelines are RNC-A, MSC-A (containing MGW-A), Server B (containing MGW-B), MSC-C (containing MGW-C), and RNC C. The sequence of messages is as follows: + + +- RNC-A sends a Direct Transfer [Modify (speech)] to MSC-A. +- MSC-A sends a Modify Bearer Characteristics (Stream Mode=INACTIVE, New Codec = AMR, Dir=OUT,) to Server B. +- MSC-A sends a RAB Assign Modify (AMR RAB parameters) to RNC-A. +- RNC-A sends an Iu FP Init to MSC-A. +- MSC-A sends an Iu FP Init Ack to RNC-A. +- MSC-A sends a Modify Bearer Request to Server B. +- Server B sends a Modify Bearer Ack to MSC-A. +- MSC-A sends a RAB Assign Modify Rsp to RNC-A. +- MSC-A sends a Modify Bearer Characteristics (Stream Mode=INACTIVE, New Codec = G.711) to Server B. +- MSC-A sends a Modify Codec (Selected Codec = G.711) to Server B. +- Server B sends a Reserve Bearer Characteristics (Stream Mode=INACTIVE, New Codec = G.711 3GUP Dir=IN) to MGW-B. +- MGW-B sends a BNC Modified to Server B. +- Server B sends a Modify Bearer Characteristics (Stream Mode=INACTIVE, New Codec = G.711 3GUP Dir=IN,) to MGW-B. +- Server B sends a Modify Codec (Selected Codec= G.711) to MGW-C. +- MGW-C sends a Reserve Bearer Char (Stream Mode=INACTIVE, New Codec = G.711,) to MGW-B. +- MGW-B sends a BNC Modified to MGW-C. +- MGW-C sends a Modify Bearer Characteristics (Stream Mode=INACTIVE, codec = AMR, 3GUP Dir=IN) to MSC-C. +- MSC-C sends a Direct Transfer [Modify (AMR)] to RNC C. +- MSC-C sends a Direct Transfer [Modify Complete(AMR)] to RNC C. +- MSC-C sends a RAB Assign Modify (AMR RAB parameters) to RNC C. +- RNC C sends an Iu FP Init to MSC-C. +- MSC-C sends an Iu FP Init Ack to RNC C. +- MSC-C sends a Modify Bearer request to RNC C. +- RNC C sends a Modify Bearer Ack to MSC-C. +- MSC-C sends a RAB Assign Modify Rsp to RNC C. +- MSC-C sends a Modify Bearer Characteristics (Stream Mode=ACTIVE, codec = AMR) to RNC C. + + There are two annotations labeled 'Optionally to decrease bandwidth': one between MSC-A and Server B, and another between MSC-C and RNC C. + +Sequence diagram showing service change from MuMe to PCM(G.711) between RNC-A, MSC-A, Server B, MSC-C, and RNC C. The diagram includes lifelines for RNC-A, MSC-A (with MGW-A), Server B (with MGW-B), MSC-C (with MGW-C), and RNC C. The process involves Direct Transfer, Modify Bearer Characteristics, RAB Assign Modify, Iu FP Init/Ack, Modify Bearer Request/Ack, Modify Codec, Reserve Bearer Characteristics, BNC Modified, and Direct Transfer [Modify (AMR)] messages. Annotations include 'Optionally to decrease bandwidth' and specific parameter values like Stream Mode=INACTIVE, New Codec = AMR, Dir=OUT, and 3GUP Dir=IN. + +Figure 4.3.5.1/5: Service change MuMe to PCM(G.711) + + + +``` +sequenceDiagram + participant RNC-A + participant MSC-A + participant Server B + participant MSC-C + participant RNC C + + Note right of MSC-A: MGW-A + Note right of Server B: MGW-B + Note right of MSC-C: MGW-C + + MSC-C->>MGW-C: Confirm Bearer Char (Stream Mode=ACTIVE, New Codec = G.711, 3GUP Dir=Out) + MGW-C->>MSC-C: Iu FP Init + MSC-C->>MGW-B: Iu FP Init + MGW-B->>MSC-C: Iu FP Init Ack + MGW-B->>Server B: Successful Codec Modification + Server B->>MGW-B: Modify Bearer Characteristics (Stream Mode=ACTIVE, codec = G.711) + MGW-B->>Server B: Confirm Bearer Char (Stream Mode=ACTIVE, New Codec = G.711) + Server B->>MSC-A: Successful Codec Modification + Server B->>MGW-A: Modify Bearer Characteristics (Stream Mode=ACTIVE, codec = G.711) + MGW-A->>Server B: + Server B->>MGW-A: Modify Bearer Characteristics (Stream Mode=ACTIVE, codec = AMR) + MGW-A->>Server B: + MSC-A->>RNC-A: Direct Transfer (Modify_Complete (speech)) +``` + +Sequence diagram for service change MuMe to PCM(G.711) (continued). Lifelines: RNC-A, MSC-A (with MGW-A), Server B (with MGW-B), MSC-C (with MGW-C), RNC C. The diagram shows a series of messages for codec modification and bearer characteristic updates between the RNCs and the MGWs, with Server B acting as a central controller. + +Figure 4.3.5.1/6: Service change MuMe to PCM(G.711) (continued) + +![Sequence diagram for network-initiated service change from MuMe to speech. Lifelines: RNC-A, MSC-A, MGW-A, Server B, MGW-B, MSC-C, MGW-C, RNC C. The diagram shows the flow of messages for modifying bearers and codecs across different network elements. Key messages include RAB Modify Request (Speech), Modify Bearer Characteristics, Direct Transfer [Modify (Speech)], RAB Assign Modify, Iu FP Init, and Iu FP Init Ack. Annotations highlight optional steps for decreasing bandwidth and RFCI value correction.](be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg) + +The sequence diagram illustrates the network-initiated service change from MuMe to speech. The interaction involves the following components and steps: + +- RNC-A** sends a **RAB Modify Request (Speech)** to **MSC-A**. +- MSC-A** sends a **Modify Bearer Characteristics (Stream Mode=INACTIVE, New Codec = AMR, Dir=OUT, )** to **MGW-A**. +- MGW-A** sends a **Direct Transfer [Modify (Speech)]** to **RNC-A**. +- MSC-A** sends a **Modify Bearer Characteristics (Stream Mode=INACTIVE, New Codec = AMR or G.711, Dir=IN)** to **MGW-A**. +- MGW-A** sends a **Modify Codec (Selected Codec = AMR or G.711)** to **Server B**. +- Server B** sends a **Direct Transfer [Modify Complete (Speech)]** to **MGW-A**. +- MGW-A** sends a **Reserve Bearer Characteristics (Stream Mode=INACTIVE, New Codec = AMR or G.711 3GUP Dir=IN )** to **Server B**. +- Server B** sends a **BNC Modified** message to **MGW-A**. +- MGW-A** sends a **Modify Bearer Characteristics (Stream Mode=INACTIVE, New Codec = AMR or G.711 3GUP Dir=IN, )** to **Server B**. +- Server B** sends a **Modify Codec (Selected Codec= AMR or G.711)** to **MGW-A**. +- MGW-A** sends a **Direct Transfer [Modify Complete (Speech)]** to **MSC-A**. +- MSC-A** sends a **RAB Assign Modify ( RAB parameters)** to **RNC-A**. +- RNC-A** sends an **Iu FP Init** message to **MSC-A**. +- MSC-A** sends an **Iu FP Init Ack** message to **RNC-A**. +- MSC-A** sends a **Modify Bearer Request** to **MGW-A**. +- MGW-A** sends a **Modify Bearer Ack** message to **MSC-A**. +- MSC-A** sends a **RAB Assign Modify Rsp** message to **RNC-A**. +- MSC-A** sends a **Modify Bearer Characteristics (Stream Mode=INACTIVE, New Codec = AMR or G.711, If codec is AMR: 3GUP Dir=IN)** to **MGW-A**. +- MGW-A** sends a **BNC Modified** message to **MSC-A**. +- MSC-A** sends a **Modify Bearer Characteristics (Stream Mode=INACTIVE, codec = AMR, 3GUP Dir=IN)** to **MGW-A**. +- MGW-A** sends a **Direct Transfer [Modify (Speech)]** to **MSC-A**. +- MSC-A** sends a **Direct Transfer [Modify Complete (Speech)]** to **MGW-A**. +- MGW-A** sends a **RAB Assign Modify (RAB parameters)** to **MSC-A**. +- MSC-A** sends an **Iu FP Init** message to **MGW-A**. +- MGW-A** sends an **Iu FP Init Ack** message to **MSC-A**. +- MSC-A** sends an **Iu FP Init** message to **Server B**. +- Server B** sends an **Iu FP Init Ack** message to **MSC-A**. +- MSC-A** sends an **Iu FP Init** message to **MGW-A**. +- MGW-A** sends an **Iu FP Init Ack** message to **MSC-A**. +- MSC-A** sends an **Iu FP Init** message to **RNC-A**. +- RNC-A** sends an **Iu FP Init Ack** message to **MSC-A**. +- MSC-A** sends a **Modify Bearer request** to **MGW-A**. +- MGW-A** sends a **Modify Bearer Ack** message to **MSC-A**. +- MGW-A** sends a **RAB Assign Modify Rsp** message to **MSC-A**. + +Annotations in the diagram: + +- Optionally to decrease bandwidth**: A bracket grouping the messages between **MSC-A** and **MGW-A** (Modify Bearer Request, Modify Bearer Ack, RAB Assign Modify Rsp). +- Optionally for RFCI value correction**: A bracket grouping the dashed Iu FP Init and Iu FP Init Ack messages between **MSC-A** and **Server B**. +- Conditionally, if selected codec in core network is AMR**: A bracket grouping the messages between **MSC-A** and **MGW-A** (Modify Bearer Characteristics, BNC Modified, Modify Bearer Characteristics). +- Optionally to decrease bandwidth**: A bracket grouping the messages between **MGW-A** and **MSC-A** (Modify Bearer request, Modify Bearer Ack, RAB Assign Modify Rsp). + +Sequence diagram for network-initiated service change from MuMe to speech. Lifelines: RNC-A, MSC-A, MGW-A, Server B, MGW-B, MSC-C, MGW-C, RNC C. The diagram shows the flow of messages for modifying bearers and codecs across different network elements. Key messages include RAB Modify Request (Speech), Modify Bearer Characteristics, Direct Transfer [Modify (Speech)], RAB Assign Modify, Iu FP Init, and Iu FP Init Ack. Annotations highlight optional steps for decreasing bandwidth and RFCI value correction. + +Figure 4.3.5.1/7: Network-initiated service change from MuMe to speech + + + +The sequence diagram illustrates the interaction for a network-initiated service change from MuMe to speech. The lifelines are RNC-A, MSC-A, MGW-A, Server B, MGW-B, MSC-C, MGW-C, and RNC C. + +Key message exchanges include: + +- Modify Bearer Characteristics** (*Stream Mode=ACTIVE, codec = AMR*): Sent from MGW-C to MGW-B. +- Confirm Bearer Char** (*Stream Mode=ACTIVE, New Codec = AMR or G.711*), if codec = G.711, 3GUP Dir =Out: Sent from MGW-B to MGW-C. +- Modify Bearer Request** and **Modify Bearer Ack**: Exchanged between MGW-B and MGW-C. +- Optionally to decrease bandwidth if selected codec is AMR**: A note associated with the MGW-B/MGW-C interaction. +- Iu FP Init** and **Iu FP Init Ack**: Exchanged between MGW-B and MGW-C (dashed lines). +- Successful Codec Modification**: Sent from MGW-B to Server B. +- Modify Bearer Characteristics** (*Stream Mode=ACTIVE, codec = AMR*): Sent from Server B to MGW-B. +- Confirm Bearer Char** (*Stream Mode=ACTIVE, New Codec = AMR*): Sent from MGW-B to Server B. +- Modify Bearer Request** and **Modify Bearer Ack**: Exchanged between MGW-B and MGW-A. +- Optionally to decrease bandwidth, if selected codec =AMR.**: A note associated with the MGW-B/MGW-A interaction. +- Successful Codec Modification**: Sent from MGW-A to Server B. +- Modify Bearer Characteristics** (*Stream Mode=ACTIVE, codec = AMR*): Sent from Server B to MGW-A. +- Modify Bearer Characteristics** (*Stream Mode=ACTIVE, codec = AMR*): Sent from MGW-A to MSC-A. +- Conditionally, if the selected codec in core network is G.711**: A note associated with the MGW-A/MGW-B interaction. +- Iu FP Init** and **Iu FP Init Ack**: Exchanged between MGW-A and MGW-B (dashed lines). + +Sequence diagram showing network-initiated service change from MuMe to speech. Lifelines: RNC-A, MSC-A, MGW-A, Server B, MGW-B, MSC-C, MGW-C, RNC C. The diagram shows a series of messages for bearer modification and codec selection between the RNC and the core network (MSC/MGW) and Server B. + +**Figure 4.3.5.1/8: Network-initiated service change from MuMe to speech (continue)** + + + +``` + +sequenceDiagram + participant RNC-A + participant MSC-A + participant MGW-A + participant Server B + participant MGW-B + participant MSC-C + participant MGW-C + participant RNC C + + RNC-A->>MSC-A: RAB Modify Request (MuMe) + MSC-A->>RNC-A: Direct Transfer [Modify (MuMe, NISUId)] + RNC-A->>MSC-A: Direct Transfer [Modify Complete (MuMe)] + MSC-A->>MGW-A: Modify Bearer Characteristics (Stream Mode=INACTIVE, New Codec = MuMe, 3GUP mode=transparent) + MGW-A-->>MSC-A: + MSC-A->>MGW-A: Modify Bearer Characteristics (Stream Mode=INACTIVE, New Codec = MuMe, Dir=IN) + MGW-A-->>MSC-A: + MSC-A->>Server B: Modify Codec (Selected Codec = MuMe2) + Server B->>MGW-B: Reserve Bearer Characteristics (Stream Mode=INACTIVE, New Codec = MuMe, Dir=IN) + MGW-B-->>Server B: + Note over Server B, MGW-B: Optionally to increase bandwidth + Server B->>MGW-B: Modify Bearer Request + MGW-B-->>Server B: Modify Bearer Ack + Server B->>MGW-B: BNC Modified + MGW-B-->>Server B: + Server B->>MGW-B: Modify Bearer Characteristics (Stream Mode=INACTIVE, New Codec = MuMe, Dir=IN) + MGW-B-->>Server B: + Server B->>MGW-B: Modify Codec (Selected Codec = MuMe2) + MGW-B->>MSC-C: Reserve Bearer Char (Stream Mode=INACTIVE, New Codec = MuMe) + MSC-C-->>MGW-B: + Note over MSC-C, MGW-C: Optionally to increase bandwidth + MSC-C->>MGW-C: Modify Bearer Request + MGW-C-->>MSC-C: Modify Bearer Ack + MSC-C->>MGW-C: BNC Modified + MGW-C-->>MSC-C: + MSC-C->>RNC C: Direct Transfer [Modify (MuMe)] + RNC C->>MSC-C: Direct Transfer [Modify Complete(MuMe)] + MSC-C->>MGW-C: Modify Bearer Characteristics (Stream Mode=INACTIVE, codec = MuMe, mode=transparent) + MGW-C-->>MSC-C: + MSC-C->>RNC C: RAB Assign Modify (MuMe RAB parameters) + Note over MSC-C, MGW-C: Optionally to increase bandwidth + MSC-C->>MGW-C: Modify Bearer request + MGW-C-->>MSC-C: Modify Bearer Ack + RNC C->>MSC-C: RAB Assign Modify Rsp + MSC-C->>MGW-C: Modify Bearer Characteristics (Stream Mode=ACTIVE, codec = MuMe) + MGW-C-->>MSC-C: + MSC-C->>MGW-C: Confirm Bearer Char (Stream Mode=ACTIVE, Codec = MuMe, Dir=OUT) + MGW-C-->>MSC-C: + +``` + +Sequence diagram for network-initiated service change speech to MuMe. Lifelines: RNC-A, MSC-A, MGW-A, Server B, MGW-B, MSC-C, MGW-C, RNC C. The process involves RAB Modify Request, Direct Transfer messages, Modify Bearer Characteristics, Modify Codec, Reserve Bearer Characteristics, BNC Modified, and RAB Assign/Modify messages. Includes optional bandwidth increase blocks. + +Figure 4.3.5.1/9: Network-initiated service change speech to MuMe + + + +``` + +sequenceDiagram + participant RNC-A + participant MSC-A + participant Server B + participant MSC-C + participant RNC C + participant MGW-A + participant MGW-B + participant MGW-C + + Note right of MGW-A: Iu FP Init + MGW-A->>Server B: Iu FP Init + Note right of Server B: Iu FP Init Ack + Server B->>MGW-A: Iu FP Init Ack + Note right of MGW-B: Iu FP Init + MGW-B->>Server B: Iu FP Init + Note right of Server B: Iu FP Init Ack + Server B->>MGW-B: Iu FP Init Ack + Note right of MGW-C: Iu FP Init + MGW-C->>Server B: Iu FP Init + Note right of Server B: Iu FP Init Ack + Server B->>MGW-C: Iu FP Init Ack + + Note right of Server B: Successful Codec Modification + Server B->>MGW-B: Successful Codec Modification + Note right of MGW-B: Modify Bearer Characteristics (Stream Mode=ACTIVE, codec = MuMe) + MGW-B->>Server B: Modify Bearer Characteristics (Stream Mode=ACTIVE, codec = MuMe) + Note right of Server B: Confirm Bearer Char (Stream Mode=ACTIVE, Codec = MuMe) + Server B->>MGW-B: Confirm Bearer Char (Stream Mode=ACTIVE, Codec = MuMe) + + Note right of MGW-A: Successful Codec Modification + MGW-A->>Server B: Successful Codec Modification + Note right of Server B: Modify Bearer Characteristics (Stream Mode=ACTIVE, codec = MuMe) + Server B->>MGW-A: Modify Bearer Characteristics (Stream Mode=ACTIVE, codec = MuMe) + + Note right of MSC-A: RAB Assign Modify (MuMe RAB parameters) + MSC-A->>RNC-A: RAB Assign Modify (MuMe RAB parameters) + Note right of RNC-A: Modify Bearer Request + RNC-A->>MSC-A: Modify Bearer Request + Note right of MSC-A: Modify Bearer Ack + MSC-A->>RNC-A: Modify Bearer Ack + Note right of RNC-A: RAB Assign Modify Rsp + RNC-A->>MSC-A: RAB Assign Modify Rsp + + Note right of MSC-A: Modify Bearer Characteristics (Stream Mode=ACTIVE, codec = MuMe) + MSC-A->>MGW-A: Modify Bearer Characteristics (Stream Mode=ACTIVE, codec = MuMe) + + Note right of MGW-A: Optionally to increase bandwidth + Note right of MGW-B: Optionally to increase bandwidth + Note right of MGW-C: Optionally to increase bandwidth + +``` + +Sequence diagram for network-initiated service change speech to MuMe (continued). + +NOTE: The RAB Assign Modify sent towards RNC-A may also be sent by MSC-A before receiving the Successful Codec Modification Message. + +**Figure 4.3.5.1/10: Network-initiated service change speech to MuMe (continued)** + +#### 4.3.5.2 Unsuccessful Service Change + +In the case the service change is denied by the UE at the terminating side, the procedures for the unsuccessful Codec Modification as defined in [2] shall be applied to revert to the old medium (speech or multimedia). + +The through-connection of terminations shall be performed as described in Subclause 4.3.5.1. The "Codec Modification Failure" message shall interact with the "Modify Bearer Characteristics" procedure and the "Confirm Bearer Characteristics" procedure in the same way as the "Successful Codec Modification" message. + +An example sequence is shown in Figure 4.3.5.2/1 to 4.3.5.2/5. + + + +``` + +sequenceDiagram + participant RNC-A + participant MSC-A + participant MGW-A + participant Server B + participant MGW-B + participant MSC-C + participant MGW-C + participant RNC C + + RNC-A->>MSC-A: Direct Transfer [Modify (MuMe)] + MSC-A->>MGW-A: Modify Bearer Characteristics (Stream Mode=INACTIVE, New Codec = MuMe mode=transparent) + MSC-A->>RNC-A: RAB Assign Modify (MuMe RAB parameters) + + rect rgb(255, 255, 255) + Note right of MSC-A: Optionally to increase bandwidth + MSC-A->>MGW-A: Modify Bearer Request + MGW-A->>MSC-A: Modify Bearer Ack + end + + RNC-A->>MSC-A: RAB Assign Modify Rsp + MSC-A->>Server B: Modify Bearer Characteristics (Stream Mode=INACTIVE, New Codec = MuMe Dir=IN, ) + MSC-A->>Server B: Modify Codec (Selected Codec = MuMe) + MSC-A->>MGW-B: Reserve Bearer Characteristics (Stream Mode=INACTIVE, New Codec = MuMe Dir=IN, ) + + rect rgb(255, 255, 255) + Note right of Server B: Optionally to increase bandwidth- Note: note needed if changing from PCM + Server B->>MGW-B: Modify Bearer Request + MGW-B->>Server B: Modify Bearer Ack + end + + MGW-B->>Server B: BNC Modified + MSC-A->>Server B: Modify Bearer Characteristics (Stream Mode=INACTIVE, New Codec = MuMe Dir=IN, ) + MSC-A->>Server B: Modify Codec (Selected Codec= MuMe) + MSC-A->>MSC-C: Reserve Bearer Char (Stream Mode=INACTIVE, New Codec = MuMe, Dir=IN, ) + + rect rgb(255, 255, 255) + Note right of MSC-C: Optionally to increase bandwidth – Note: note needed if changing from PCM + MSC-C->>MGW-C: Modify Bearer Request + MGW-C->>MSC-C: Modify Bearer Ack + end + + MGW-C->>MSC-C: BNC Modified + MSC-A->>MSC-C: Direct Transfer [Modify (MuMe)] + MSC-C->>RNC C: Direct Transfer [Modify Reject (Speech)] + +``` + +Sequence diagram for Service Change Rejected procedure involving RNC-A, MSC-A, MGW-A, Server B, MGW-B, MSC-C, MGW-C, and RNC C. + +**Figure 4.3.5.2/1: Service Change Rejected** + + + +``` + +sequenceDiagram + participant RNC-A + participant MSC-A + participant Server B + participant MSC-C + participant RNC-C + Note right of MSC-A: MGW-A + Note right of Server B: MGW-B + Note right of MSC-C: MGW-C + + Note right of MGW-C: Confirm Bearer Char (Stream Mode=ACTIVE, New Codec = Old Codec (G711 or AMR)) + MGW-C->>MGW-B: Confirm Bearer Char (Stream Mode=ACTIVE, New Codec = Old Codec (G711 or AMR)) + MGW-B->>MGW-C: Modify Bearer Request + MGW-C->>MGW-B: Modify Bearer Ack + MGW-B->>MGW-C: BNC Modified + Note right of MGW-C: Codec Modification Failure + MGW-C->>MGW-B: Codec Modification Failure + MGW-B->>MGW-C: Modify Bearer Characteristics (Stream Mode=ACTIVE, codec = Old Codec (G711 or AMR)) + MGW-C->>MGW-B: Confirm Bearer Char (Stream Mode=ACTIVE, Codec = Old Codec (G711 or AMR)) + + Note right of MGW-B: Optionally to decrease bandwidth – Note: Not need if change from PCM + MGW-B->>MGW-A: Modify Bearer Request + MGW-A->>MGW-B: Modify Bearer Ack + MGW-B->>MGW-A: BNC modified + Note right of MGW-A: Codec Modification Failure + MGW-A->>MGW-B: Codec Modification Failure + MGW-B->>MGW-A: Modify Bearer Characteristics (Stream Mode=ACTIVE, codec = Old Codec(G711 or AMR) ) + MGW-A->>MGW-B: Modify Bearer Characteristics (Stream Mode=ACTIVE, Codec = AMR 3GUP Dir=OUT, mode=support ) + + Note right of MGW-A: RAB Assign Modify (AMR RAB parameters) + MGW-A->>RNC-A: RAB Assign Modify (AMR RAB parameters) + RNC-A->>MGW-A: Iu FP Init + MGW-A->>RNC-A: Iu FP Init Ack + MGW-A->>MGW-B: Modify Bearer Request + MGW-B->>MGW-A: Modify Bearer Ack + RNC-A->>MGW-A: Iu FP Init + MGW-A->>RNC-A: Iu FP Init Ack + MGW-A->>MGW-B: RAB Assign Modify Rsp + MGW-B->>MGW-A: Direct Transfer (Modify Reject (speech)) + MGW-A->>RNC-A: Direct Transfer (Modify Reject (speech)) + +``` + +The sequence diagram illustrates the interaction between RNC-A, MSC-A, Server B, MSC-C, and RNC-C for a service change rejection. The process involves several steps: + + +- MSC-C (via MGW-C) sends a **Confirm Bearer Char** message to MGW-B with **Stream Mode=ACTIVE** and **New Codec = Old Codec (G711 or AMR)**. +- MGW-B responds with **Modify Bearer Request**, which MGW-C answers with **Modify Bearer Ack** and **BNC Modified**. +- MGW-C then reports a **Codec Modification Failure** to MGW-B. +- MGW-B sends **Modify Bearer Characteristics** to MGW-C with **Stream Mode=ACTIVE** and **codec = Old Codec (G711 or AMR)**, which MGW-C confirms. +- A note indicates that decreasing bandwidth is optional and not needed if the change is from PCM. +- MGW-B sends **Modify Bearer Request** to MGW-A, which MGW-A answers with **Modify Bearer Ack** and **BNC modified**. +- MGW-A reports a **Codec Modification Failure** to MGW-B. +- MGW-B sends **Modify Bearer Characteristics** to MGW-A with **Stream Mode=ACTIVE** and **codec = Old Codec(G711 or AMR)**. +- MGW-A responds with **Modify Bearer Characteristics** with **Stream Mode=ACTIVE**, **Codec = AMR 3GUP Dir=OUT**, and **mode=support**. +- MGW-A sends **RAB Assign Modify (AMR RAB parameters)** to RNC-A. +- RNC-A and MGW-A exchange **Iu FP Init** and **Iu FP Init Ack** messages. +- MGW-A sends **Modify Bearer Request** to MGW-B, which MGW-B answers with **Modify Bearer Ack**. +- RNC-A and MGW-A exchange another **Iu FP Init** and **Iu FP Init Ack** messages. +- MGW-A sends **RAB Assign Modify Rsp** to MGW-B. +- MGW-B sends **Direct Transfer (Modify Reject (speech))** to MGW-A, which MGW-A then forwards to RNC-A. + + Additional notes indicate that decreasing bandwidth is optional and that RFCI value correction is not performed if PCM is in the core. + +Sequence diagram for Service Change Rejected (Continued) + +Figure 4.3.5.2/2:Service Change Rejected (Continued) + +![Sequence diagram for Figure 4.3.5.2/3 showing a network-initiated service change from speech to MuMe initiated by MSS A, rejected by user A. Lifelines: RNC-A, MSC-A, MGW-A, Server B, MGW-B, MSC-C, MGW-C, RNC C. The sequence starts with RNC-A sending a RAB Modify Request (MuMe) to MSC-A. MSC-A sends a Direct Transfer [Modify] (MuMe, NISUId) to RNC-A. RNC-A responds with a Direct Transfer [Modify Reject] (Speech) to MSC-A.](a0e8fe7862a6d7341faf5dac275277cc_img.jpg) + +Sequence diagram for Figure 4.3.5.2/3 showing a network-initiated service change from speech to MuMe initiated by MSS A, rejected by user A. Lifelines: RNC-A, MSC-A, MGW-A, Server B, MGW-B, MSC-C, MGW-C, RNC C. The sequence starts with RNC-A sending a RAB Modify Request (MuMe) to MSC-A. MSC-A sends a Direct Transfer [Modify] (MuMe, NISUId) to RNC-A. RNC-A responds with a Direct Transfer [Modify Reject] (Speech) to MSC-A. + +Figure 4.3.5.2/3: Network-initiated service change from speech to MuMe initiated by MSS A, rejected by user A + +![Sequence diagram for Figure 4.3.5.2/4 showing a network-initiated service change from speech to MuMe initiated by MSS A, rejected by user B. Lifelines: RNC-A, MSC-A, MGW-A, Server B, MGW-B, MSC-C, MGW-C, RNC C. The sequence starts with RNC-A sending a RAB Modify Request (MuMe) to MSC-A. MSC-A sends a Direct Transfer [Modify] (MuMe, NISUId) to RNC-A. RNC-A responds with a Direct Transfer [Modify Complete] (MuMe) to MSC-A. MSC-A then sends a Modify Bearer Characteristics (Stream Mode=INACTIVE, New Codec = MuMe, 3GUP mode=transparent) to MGW-A. MGW-A sends a Modify Bearer Characteristics (Stream Mode=INACTIVE, New Codec = MuMe, Dir=IN) to Server B. Server B sends a Modify Codec (Selected Codec = MuMe2) to MGW-B. MGW-B sends a Reserve Bearer Characteristics (Stream Mode=INACTIVE, New Codec = MuMe, Dir=IN) to MSC-C. MSC-C sends a Modify Bearer Request to MGW-C. MGW-C sends a Modify Bearer Ack to MSC-C. MSC-C sends a BNC Modified to Server B. Server B sends a Modify Bearer Characteristics (Stream Mode=INACTIVE, New Codec = MuMe, Dir=IN) to MGW-B. MGW-B sends a Modify Codec (Selected Codec= MuMe2) to MSC-C. MSC-C sends a Reserve Bearer Char (Stream Mode=INACTIVE, New Codec = MuMe) to MGW-C. MGW-C sends a Modify Bearer Request to MSC-C. MSC-C sends a Modify Bearer Ack to MGW-C. MGW-C sends a BNC Modified to MSC-C. MSC-C sends a Direct Transfer [Modify] (MuMe) to RNC C. RNC C responds with a Direct Transfer [Modify Reject] (Speech) to MSC-C. Two callouts indicate 'Optionally to increase bandwidth - Note: needed if changing from PCM' and 'Optionally to increase bandwidth'.](df1966d80c74bc127f159a48f38b13ee_img.jpg) + +Sequence diagram for Figure 4.3.5.2/4 showing a network-initiated service change from speech to MuMe initiated by MSS A, rejected by user B. Lifelines: RNC-A, MSC-A, MGW-A, Server B, MGW-B, MSC-C, MGW-C, RNC C. The sequence starts with RNC-A sending a RAB Modify Request (MuMe) to MSC-A. MSC-A sends a Direct Transfer [Modify] (MuMe, NISUId) to RNC-A. RNC-A responds with a Direct Transfer [Modify Complete] (MuMe) to MSC-A. MSC-A then sends a Modify Bearer Characteristics (Stream Mode=INACTIVE, New Codec = MuMe, 3GUP mode=transparent) to MGW-A. MGW-A sends a Modify Bearer Characteristics (Stream Mode=INACTIVE, New Codec = MuMe, Dir=IN) to Server B. Server B sends a Modify Codec (Selected Codec = MuMe2) to MGW-B. MGW-B sends a Reserve Bearer Characteristics (Stream Mode=INACTIVE, New Codec = MuMe, Dir=IN) to MSC-C. MSC-C sends a Modify Bearer Request to MGW-C. MGW-C sends a Modify Bearer Ack to MSC-C. MSC-C sends a BNC Modified to Server B. Server B sends a Modify Bearer Characteristics (Stream Mode=INACTIVE, New Codec = MuMe, Dir=IN) to MGW-B. MGW-B sends a Modify Codec (Selected Codec= MuMe2) to MSC-C. MSC-C sends a Reserve Bearer Char (Stream Mode=INACTIVE, New Codec = MuMe) to MGW-C. MGW-C sends a Modify Bearer Request to MSC-C. MSC-C sends a Modify Bearer Ack to MGW-C. MGW-C sends a BNC Modified to MSC-C. MSC-C sends a Direct Transfer [Modify] (MuMe) to RNC C. RNC C responds with a Direct Transfer [Modify Reject] (Speech) to MSC-C. Two callouts indicate 'Optionally to increase bandwidth - Note: needed if changing from PCM' and 'Optionally to increase bandwidth'. + +Figure 4.3.5.2/4: Network-initiated service change from speech to MuMe initiated by MSS A, rejected by user B + + + +The sequence diagram illustrates the interaction between RNC-A, MSC-A (with MGW-A), Server B (with MGW-B), MSC-C (with MGW-C), and RNC C. The process involves bearer modification requests and responses between the network elements and the user equipment (UE). + +Key messages and interactions shown: + +- MSC-C to MGW-C:** Confirm Bearer Char (Stream Mode=ACTIVE, New Codec = Old Codec (G711 or AMR)) +- MGW-C to MSC-C:** Modify Bearer Request, Modify Bearer Ack, BNC Modified +- Server B to MGW-B:** Codec Modification Failure +- Server B to MGW-B:** Modify Bearer Characteristics (Stream Mode=ACTIVE, codec = Old Codec (G711 or AMR)) +- MGW-B to Server B:** Confirm Bearer Char (Stream Mode=ACTIVE, Codec = Old Codec (G711 or AMR)) +- Server B to MGW-A:** Modify Bearer Request, Modify Bearer Ack, BNC modified +- MGW-A to Server B:** Codec Modification Failure +- Server B to MGW-A:** Modify Bearer Characteristics (Stream Mode=ACTIVE, codec = Old Codec (G711 or AMR)) +- Server B to MGW-A:** Modify Bearer Characteristics (Stream Mode=ACTIVE, Codec = AMR, 3GUP Dir=OUT, mode=support) +- MGW-A to RNC-A:** Direct Transfer (Modify (speech)) +- RNC-A to MGW-A:** Direct Transfer (Modify Complete (speech)) + +Two optional notes indicate that decreasing bandwidth is not needed if the change is from PCM: + +- Optionally to decrease bandwidth – Note: Not needed if change from PCM (associated with MGW-C) +- Optionally to decrease bandwidth – Note: not needed if change from PCM (associated with MGW-A) + +Sequence diagram for network-initiated service change from speech to MuMe initiated by MSS A, rejected by user B (continued). + +**Figure 4.3.5.2/5: Network-initiated service change from speech to MuMe initiated by MSS A, rejected by user B (continued)** + +### 4.3.6 Interaction with supplementary services + +#### 4.3.6.1 Call forwarding and Call deflection + +If CFB(UDUB), CFNRy, or Call Deflection is invoked in a SCUDIF call, and both basic services are provisioned, the HLR (for early call forwarding) or VLR (for late call forwarding) shall check the handling of the call should continue with the active service negotiated between the called UE and the network. + +If call forwarding except CFB(UDUB) and CFNRy is invoked in a SCUDIF call, and both basic services are provisioned, the HLR (for early call forwarding) or VLR (for late call forwarding) shall check the service for both the preferred service and the less preferred service. + +Then, the SCUDIF call interacting with call forwarding shall be handled according to the following rules: + +- If the call forwarding is active only for the less preferred service, the preferred service shall be selected and the call setup shall continue with a single service without invoking call forwarding. + +- If the call forwarding is active only for the preferred service, the preferred service shall be selected and call forwarding shall continue with a single service to the destination indicated by the forwarded to number. +- If the call forwarding is active for both services and the forwarded to number for the preferred service is same as for the less preferred service, the call shall continue as a SCUDIF call to the destination indicated by the forwarded to number. +- If the call forwarding is active for both services and the forwarded to number for the preferred service is different from that for the less preferred service, the preferred service shall be selected and call forwarding shall continue with a single service to the destination indicated by the forwarded to number for the preferred service. +- If the call forwarding is active for both services and CF type for the preferred service is different from that of less preferred service, the call shall continue as a SCUDIF call to the destination indicated by the forwarded to number, and the forwarding reason for the preferred service shall be indicated. + +NOTE: For Late call forwarding or Call Deflection with Optimal Routing, the second basic service group code shall be generated in VMSC and sent in Resume Call Handling and may be sent in the following Send Routing Information. The preferred service is set as basic service group IE, and the less preferred service is set as basic service group 2 IE. + +#### 4.3.6.2 Closed User Group (CUG) + +If a SCUDIF call interacts with CUG and both basic services are provisioned, the service state shall be checked for both the preferred service and the less preferred service. If one service is not allowed, then the call shall fall back to the allowed service. + +#### 4.3.6.3 Call barring + +If a SCUDIF call interacts with call barring and both basic services are provisioned, the service state shall be checked for both the preferred service and the less preferred service. If one service is barred, then the call shall fall back to the allowed service. + +### 4.3.7 Interactions with CAMEL + +#### 4.3.7.1 Interaction at call setup + +When a SCUDIF call activates a CAMEL dialogue for the originating or the terminating subscriber, both basic services shall be indicated to the gsmSCF in the InitialDP message (see 3GPP TS 23.078 [14]) : + +- the bearer capability IE and the ext-basic service code IE shall indicate the preferred service (*i.e.* 3G-324.M if the 3G-324.M codec is the first codec in the list of supported codecs ; speech otherwise), +- the bearer capability 2 IE and the ext-basic service code 2 IE shall indicate the other, less preferred service (*i.e.* resp. speech or 3G-324.M). + +#### 4.3.7.2 Interaction at call answer + +When the Answer DP is triggered according to the BCSM (see 3GPP TS 23.078 [14]), the event report sent to the gsmSCF shall indicate the result from the OoBTC codec negotiation procedure according to the following : + +- the ext-basic service code IE is included, and represents the selected service (indicated by the selected codec) ; +- the ext-basic service code 2 IE is included if the list of available codecs contains codecs both for speech and 3G-324.M, and represents the other service (*i.e.* speech if the selected service is 3G-324.M, and vice-versa). + +#### 4.3.7.3 Interaction with Call Party Handling + +Interaction with Call Party Handling is allowed, when the call is a speech call and it cannot become a multimedia call. + +See 3GPP TS 22.078 [16] clause 21. + +#### 4.3.7.4 Interaction with CAMEL in-band information and user interaction + +Interaction with Camel in-band information and user interaction is allowed, when the call is a speech call and it cannot become a multimedia call. + +See 3GPP TS 22.078 [16] clause 21. + +#### 4.3.7.5 Interaction during service change + +When a service change is successfully completed (*i.e.* the codec modification or mid-call codec negotiation reply message indicates a successful codec modification), and the O\_Service\_Change DP or the T\_Service\_Change DP is armed, then the relevant detection point is triggered (see 3GPP TS 23.078 [14]). + +When a service change is rejected (*i.e.* the codec modification or mid-call codec negotiation reply message indicates a failure), then the previously selected service is kept, and no event report shall be sent to the gsmSCF for the O\_Service\_Change DP and the T\_Service\_Change DP. + +### 4.3.8 Interworking with external networks + +If the 3G-324.M codec is included in the list of supported codec types received by a Gateway MSC, and the external network does not support BICC or does not support Codec Negotiation, the Gateway MSC shall terminate the codec negotiation and fallback to a single service. + +NOTE 1: If the route is known not to support the SCUDIF functionality, the Gateway MSC may decide by configuration to terminate the codec negotiation and follow the procedure described in this clause. + +In the case where the 3G-324.M codec is the first in the list, the network decides by configuration to fallback either to a UDI multimedia-only call or to speech. In the case where the 3G-324.M codec is not the first on the list, the call shall fallback to speech only. + +If fallback to multimedia occurs, the call control parameters sent towards the external network shall be set according to the setting for multimedia calls, and TMR is set to "64 kbit/s unrestricted". The 3G-324.M codec shall be returned to the originating MSC server as the selected codec and be the only member of the available codec list. + +NOTE 2: For multimedia calls, 3GPP TS 27.001 [5], annex B, and 3GPP TS 29.007 [6], table 7A, describe the setting and validity of the PLMN BC-IE as well as the comparable settings of parameters in the PLMN and ISDN BC-IEs. As the ISDN BC-IE parameter values used for UDI/RDI multimedia calls are identical to the BICC USI IE parameter values (see 3GPP TS 29.205 [7]), the setting of call control parameters sent towards the external network in case of fallback to multimedia can be derived straightforward. + +If fallback to speech occurs, the call control parameters shall be set according to the setting for speech calls, and TMR is set to "speech". The 3G-324.M codec shall be removed from the available codec list. Speech codec selection shall be made according to normal OoBTC procedures for interworking to external networks, and the selected codec and available codec list returned to the originating MSC server. + +### 4.3.9 User interaction and in-band information + +The MSC provided announcements and tones do not work, if the negotiated BC is a multimedia BC. Most often the in-band information is connected to the originating UE but the same rules apply for the terminating UE. The following rules apply: + +- 1) Before sending the CONNECT message the originating MSC may insert in-band information if CALL PROCEEDING message indicates speech as the selected or preferred service. When fallback to multimedia occurs after CALL PROCEEDING but before CONNECT, the MSC may insert in-band information. +- 2) Before sending the CONNECT message the originating MSC shall not insert in-band information, if CALL PROCEEDING message indicates multimedia as the selected or preferred service. When fallback to speech occurs after CALL PROCEEDING but before CONNECT, the MSC shall not insert in-band information. +- 3) After the CONNECT message to/from the UE the originating/terminating MSC may insert in-band information, if the selected service is speech. Otherwise, the MSC shall not insert any in-band information. As an option, if the call is to be cleared, the MSC may perform an in-call modification to speech prior to the insertion of the in-band information. +- 4) During the call setup phase the terminating MSC, transit MSC and GMSC may insert in-band information, if the selected/preferred service received from the originating switch is speech. Otherwise the terminating MSC, transit MSC and GMSC shall not insert any in-band information during the call setup phase. + +- 5) In the active phase of the call the terminating MSC, transit MSC and GMSC may insert in-band information, if the selected service is speech. Otherwise the terminating MSC, transit MSC and GMSC shall not insert any in-band information. As an option, if the call is to be cleared, the terminating MSC, transit MSC or GMSC may perform an in-call modification to speech prior to insertion of the in-band information. + +# --- 5 Lawful Interception + +SCUDIF calls shall be monitored as for normal Circuit Switched data calls, for detailed requirements see 3GPP TS 33.106 [9]. + +# Annex A (informative): Change history + +| Change history | | | | | | | | | +|-----------------------|--------------|-----------------|-----------|------------|----------------------------------------------------------------------------------|-----------------------------------------|------------|------------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | | Old | New | +| 2004-03 | NP#23 | NP-040147 | 025 | 3 | Network-Initiated Service Change | | 5.4.0 | 6.0.0 | +| 2004-09 | NP#25 | NP-040366 | 027 | - | Interaction of CAMEL with Service Change | | 6.0.0 | 6.1.0 | +| 2005-03 | NP#27 | NP-050100 | 031 | - | Inclusion of Missing HLR Interrogation Parameter for SCUDIF | | 6.1.0 | 6.2.0 | +| 2005-03 | NP#27 | NP-050101 | 029 | - | Correction to Network-initiated SCUDIF | | 6.1.0 | 6.2.0 | +| 2005-06 | CP#28 | CP-050033 | 036 | 1 | Correction to figure 4.3.5.2/1, wrong Bearer Capability in MODIFY REJECT-message | | 6.2.0 | 6.3.0 | +| 2005-06 | CP#28 | CP-050035 | 038 | 1 | Network-initiated downgrade, signaling flows | | 6.2.0 | 6.3.0 | +| 2005-06 | CP#28 | CP-050036 | 040 | 4 | Network-Initiated upgrade procedure for SCUDIF | | 6.2.0 | 6.3.0 | +| 2006-03 | CP#31 | CP-060050 | 043 | 1 | Indication of Network-Initiated Service Change | | 6.3.0 | 6.4.0 | +| 2007-06 | CT#36 | | | | Upgraded to v7.0.0 | | 6.4.0 | 7.0.0 | +| 2008-12 | CT#42 | CP-080754 | 045 | 1 | Multimedia Dummy Codec for SIP-I | | 7.0.0 | 8.0.0 | +| 2009-12 | CT#46 | | | | Automatic upgrade from previous Release | | 8.0.0 | 9.0.0 | +| 2011-03 | CT#51 | | | | Automatic upgrade from previous Release version 9.0.0 | | 9.0.0 | 10.0.0 | +| 2011-03 | CT#51 | | | | Correction of heading and numbering made by MCC | | 10.0.0 | 10.0.1 | +| 2012-09 | 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 | CT#80 | | | | | Automatic upgrade from previous Release | 15.0.0 | | +| 2020-06 | CT#88e | | | | | Automatic upgrade from previous Release | 16.0.0 | | \ No newline at end of file diff --git a/marked/Rel-16/23_series/23216/0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg b/marked/Rel-16/23_series/23216/0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..07661f4f7e5b2f320036a5cf1077d3e9288654cd --- /dev/null +++ b/marked/Rel-16/23_series/23216/0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4a1c1dd7663961c588b37cd3eb68d4852cd38ef8a9e8b5736bcb9c691ed3e51c +size 76976 diff --git a/marked/Rel-16/23_series/23216/19a59d6b53059ebd27b13c98793f88e0_img.jpg b/marked/Rel-16/23_series/23216/19a59d6b53059ebd27b13c98793f88e0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..31cdabc53ccd80377780a5a0e40aa20928ea73ba --- /dev/null +++ b/marked/Rel-16/23_series/23216/19a59d6b53059ebd27b13c98793f88e0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2c2c92a08e96683ee0ee30bca16f9d5a53fca6d6db463e9ea044ba99cdb92e7d +size 57602 diff --git a/marked/Rel-16/23_series/23216/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/marked/Rel-16/23_series/23216/1a827b10290f33d4fec04d0e8ef7a897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7a78c1ea90e013cdb4fa53c410d10b69ad3aa7e6 --- /dev/null +++ b/marked/Rel-16/23_series/23216/1a827b10290f33d4fec04d0e8ef7a897_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:37f8e14bdb8e24c3f340cbbbe808a935fa9bf7d8aad006328f081e52c4bfe9b2 +size 71694 diff --git a/marked/Rel-16/23_series/23216/1ce027dfd26183da52137cf990213724_img.jpg b/marked/Rel-16/23_series/23216/1ce027dfd26183da52137cf990213724_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b9ef3bbb6814ebf752aed7a2564fbf92a33e9f92 --- /dev/null +++ b/marked/Rel-16/23_series/23216/1ce027dfd26183da52137cf990213724_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1a499c2133d525931ca8c4c64a8e7138e836d2c0ea13ff492594d319bceaed21 +size 182547 diff --git a/marked/Rel-16/23_series/23216/212c50c4e3d043c989037a01e13c1a98_img.jpg b/marked/Rel-16/23_series/23216/212c50c4e3d043c989037a01e13c1a98_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3cdd5efbed53e8abea221105d4c21406536c6ebe --- /dev/null +++ b/marked/Rel-16/23_series/23216/212c50c4e3d043c989037a01e13c1a98_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e106e5909418eff39f839dae68d68bd9a6e8eded8a363daed426224493c79801 +size 98604 diff --git a/marked/Rel-16/23_series/23216/21d8ca19de468e733e521605b1890767_img.jpg b/marked/Rel-16/23_series/23216/21d8ca19de468e733e521605b1890767_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ad2ee3ab1f88f4b9883e0a11f5352d880e8dff66 --- /dev/null +++ b/marked/Rel-16/23_series/23216/21d8ca19de468e733e521605b1890767_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5c8a1931686a921f796698514987fe9a1cf272c9e8c18d329c439382bcef9c37 +size 54814 diff --git a/marked/Rel-16/23_series/23216/26d664119ad25250780f554633444e54_img.jpg b/marked/Rel-16/23_series/23216/26d664119ad25250780f554633444e54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4a6e70021f6761dd0f382fa27c62a7db073d6920 --- /dev/null +++ b/marked/Rel-16/23_series/23216/26d664119ad25250780f554633444e54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ef232d45c3d81011ccb1a157d3a663bb6c5ef44773bc5a06b66fd19cdc38ccdf +size 60875 diff --git a/marked/Rel-16/23_series/23216/3337af75dfee8af7687b4f49914d6c93_img.jpg b/marked/Rel-16/23_series/23216/3337af75dfee8af7687b4f49914d6c93_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4a464dbd5274c8a78ea03247cd9068c560e0d087 --- /dev/null +++ b/marked/Rel-16/23_series/23216/3337af75dfee8af7687b4f49914d6c93_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c316d18f79cb8a2e4486c7a67445214a64b803d8cbbe2bc782a3c2803d63a72c +size 121885 diff --git a/marked/Rel-16/23_series/23216/4356776ca004ecba5d599667a155d7d4_img.jpg b/marked/Rel-16/23_series/23216/4356776ca004ecba5d599667a155d7d4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..877e8461f4d0b70c72223797e307e1a3dbd10655 --- /dev/null +++ b/marked/Rel-16/23_series/23216/4356776ca004ecba5d599667a155d7d4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:adc81dc987d5e5e06f268933a2c81d6db8b48863f623843c7da2a8e16ef50790 +size 109373 diff --git a/marked/Rel-16/23_series/23216/4b398c5e8c4fd656d5b7a61806400650_img.jpg b/marked/Rel-16/23_series/23216/4b398c5e8c4fd656d5b7a61806400650_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3bbf956ce99ea3feccf7b94571d896ead9f8351b --- /dev/null +++ b/marked/Rel-16/23_series/23216/4b398c5e8c4fd656d5b7a61806400650_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7e49bb3bf4414190cc87ddbe679a6ea306e59160d6ae926da22b3234939ca84a +size 33320 diff --git a/marked/Rel-16/23_series/23216/5132b3a97ac70fe4765c1e07e66b72b3_img.jpg b/marked/Rel-16/23_series/23216/5132b3a97ac70fe4765c1e07e66b72b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..df7c7424d612df50f57dd92ae678b77f2b922598 --- /dev/null +++ b/marked/Rel-16/23_series/23216/5132b3a97ac70fe4765c1e07e66b72b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4292e1312329667fb3f19821811e9801e967a58c1cf73d44064fc934f3bf00da +size 43461 diff --git a/marked/Rel-16/23_series/23216/552ca016af3d6240648ab5a2cad97f60_img.jpg b/marked/Rel-16/23_series/23216/552ca016af3d6240648ab5a2cad97f60_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6dc46ef871eb479123a8c558059c0598b9a0c230 --- /dev/null +++ b/marked/Rel-16/23_series/23216/552ca016af3d6240648ab5a2cad97f60_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cc16543d14a3926412d446d794a5b70ba5b1ede91d4a0a3c7a584cc5a1fbd6ac +size 66228 diff --git a/marked/Rel-16/23_series/23216/5a9282ac54ca7bc50f1d2ab6cfb376ba_img.jpg b/marked/Rel-16/23_series/23216/5a9282ac54ca7bc50f1d2ab6cfb376ba_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c46f23ee7639534d8f6f69a19df6aebd481c70cf --- /dev/null +++ b/marked/Rel-16/23_series/23216/5a9282ac54ca7bc50f1d2ab6cfb376ba_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:14577a97e0a837e91fde0582fd1f91915154fcbf12bd204867c91dcb193e314d +size 65794 diff --git a/marked/Rel-16/23_series/23216/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-16/23_series/23216/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..76c44754b1d65c46e865b8c783a48347a0ddd3ae --- /dev/null +++ b/marked/Rel-16/23_series/23216/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f0c16685059f0c918b82a124aa56dcf1ee2c4660d3ffe93bc42d2c53de4be09e +size 8603 diff --git a/marked/Rel-16/23_series/23216/5fbb4f0de01736f1293333e599410c99_img.jpg b/marked/Rel-16/23_series/23216/5fbb4f0de01736f1293333e599410c99_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..51ff45009f0330bdf31ce696e5278a80b392bd89 --- /dev/null +++ b/marked/Rel-16/23_series/23216/5fbb4f0de01736f1293333e599410c99_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0a120d64fd7fd008a55c129653c5e61682bc435d7d4ff868b0b9fd561637c237 +size 87399 diff --git a/marked/Rel-16/23_series/23216/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-16/23_series/23216/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fccfdf9ae763904d41d8bdb08b07bff4b0e3cf20 --- /dev/null +++ b/marked/Rel-16/23_series/23216/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:511a6aedab6818b7fb6bb55e368e31bab3ae09b68770ebf35d3c795bce1df6b1 +size 4968 diff --git a/marked/Rel-16/23_series/23216/742a5484e7dd016256ab99921bbd635d_img.jpg b/marked/Rel-16/23_series/23216/742a5484e7dd016256ab99921bbd635d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f8ca0bb047b316c28726f7424cfa211ba8010c23 --- /dev/null +++ b/marked/Rel-16/23_series/23216/742a5484e7dd016256ab99921bbd635d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6bcda68069b02a2cb5b0ffe30f93d92b02f4e787dd3eeda8c4c606229b588595 +size 157630 diff --git a/marked/Rel-16/23_series/23216/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg b/marked/Rel-16/23_series/23216/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6bb878e65695c34c8962a400b0d8a874bd503374 --- /dev/null +++ b/marked/Rel-16/23_series/23216/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b637225e23c720601623e4cb84d7ada1ad5c2bb809143b810adc7b92844e9e2e +size 41504 diff --git a/marked/Rel-16/23_series/23216/8307f6b04df072c9332f9987e034272c_img.jpg b/marked/Rel-16/23_series/23216/8307f6b04df072c9332f9987e034272c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64d1a14a8afbcf7e09b634563531ddd1a290b769 --- /dev/null +++ b/marked/Rel-16/23_series/23216/8307f6b04df072c9332f9987e034272c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:175d9b02e22db749e36aa74e6e1dfde67f84d9b866e4c0f8e0290312395d5cf1 +size 91706 diff --git a/marked/Rel-16/23_series/23216/854cb86f664ff62fd23e7607cfeb5727_img.jpg b/marked/Rel-16/23_series/23216/854cb86f664ff62fd23e7607cfeb5727_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3392b67e6c88b786a651dbe7c97969194a0c36b1 --- /dev/null +++ b/marked/Rel-16/23_series/23216/854cb86f664ff62fd23e7607cfeb5727_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4058cfa3e19c2f29770b993420f579396064e2d799bdead41657d28c04576b65 +size 23945 diff --git a/marked/Rel-16/23_series/23216/8e80de0cac529b2c3775d677c5203133_img.jpg b/marked/Rel-16/23_series/23216/8e80de0cac529b2c3775d677c5203133_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d37785048a59729cc0df0d02fbb95a7a4ca7983d --- /dev/null +++ b/marked/Rel-16/23_series/23216/8e80de0cac529b2c3775d677c5203133_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bbd62955763061a3a65111a808316c7a4f918b7ee5bf260f4f7fe5d0214550c1 +size 124688 diff --git a/marked/Rel-16/23_series/23216/8ed7f57cc317f6574bec781d01ae6ad2_img.jpg b/marked/Rel-16/23_series/23216/8ed7f57cc317f6574bec781d01ae6ad2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4bb7cb86f3f57cc05cac518878e3d25338600530 --- /dev/null +++ b/marked/Rel-16/23_series/23216/8ed7f57cc317f6574bec781d01ae6ad2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:252c047785f620efb14bd8d47e9d7ea54edf63b7d1c9ebefa9b65460393b8d1d +size 72342 diff --git a/marked/Rel-16/23_series/23216/90ddb84c323b956e2d50a54d3f870566_img.jpg b/marked/Rel-16/23_series/23216/90ddb84c323b956e2d50a54d3f870566_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2215006bb38ab654d94089d8cae665b09c830625 --- /dev/null +++ b/marked/Rel-16/23_series/23216/90ddb84c323b956e2d50a54d3f870566_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:830293916a95c5f83d587ae16b661b1bd9646bdb63f0f90c273b0f7457c025ad +size 43132 diff --git a/marked/Rel-16/23_series/23216/9e4f582a5d5f6742d1372956db0f8f0b_img.jpg b/marked/Rel-16/23_series/23216/9e4f582a5d5f6742d1372956db0f8f0b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7ed6f66af2f49ec1e41ce56b630b02aed9b219fc --- /dev/null +++ b/marked/Rel-16/23_series/23216/9e4f582a5d5f6742d1372956db0f8f0b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f5f2fc2b927adf1b9f414535f48a8ce536881340b4d2d3a030862ce127c2662a +size 115321 diff --git a/marked/Rel-16/23_series/23216/9ff1b32449ea068bba9647d71904bd59_img.jpg b/marked/Rel-16/23_series/23216/9ff1b32449ea068bba9647d71904bd59_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e76bbc6e6bf85c26cd2baa335c13fb63557f7248 --- /dev/null +++ b/marked/Rel-16/23_series/23216/9ff1b32449ea068bba9647d71904bd59_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2635cfb40ba90580a50a11506cdbd73dd79b30a2aa8c72d383bbb0545cf3a1d2 +size 129239 diff --git a/marked/Rel-16/23_series/23216/bffdddb47fced140f8d17fdc2a29f592_img.jpg b/marked/Rel-16/23_series/23216/bffdddb47fced140f8d17fdc2a29f592_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4e01c9d6d15b64c5f8bb34d75826d05f87a660ca --- /dev/null +++ b/marked/Rel-16/23_series/23216/bffdddb47fced140f8d17fdc2a29f592_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bc263f7cf9183cc43a2b46fd8331f9edfd49b543f04ca2a0c785f2eb4cc4f031 +size 74275 diff --git a/marked/Rel-16/23_series/23216/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg b/marked/Rel-16/23_series/23216/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..71d50aa4697364cecbac83c66b41c33ddf161bcb --- /dev/null +++ b/marked/Rel-16/23_series/23216/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9edff9bcb19ea7fea38e00ffb1c9081837efe59911f28dd1c4bb58171df2d4ca +size 127657 diff --git a/marked/Rel-16/23_series/23216/db39acbd11df5eb7e79ab84562fb8f74_img.jpg b/marked/Rel-16/23_series/23216/db39acbd11df5eb7e79ab84562fb8f74_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..316cfcee238f0f63c736ed5911f2a86f383bdf76 --- /dev/null +++ b/marked/Rel-16/23_series/23216/db39acbd11df5eb7e79ab84562fb8f74_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c96bbe293c7acc65d7cd40dc66f2d341f9d3a55408d0b8137892fb46152cf084 +size 65721 diff --git a/marked/Rel-16/23_series/23216/dd380ccd5aca1151074fede04826f1a4_img.jpg b/marked/Rel-16/23_series/23216/dd380ccd5aca1151074fede04826f1a4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e5ff36aff7f171cac18e6b7a54904a09c4026653 --- /dev/null +++ b/marked/Rel-16/23_series/23216/dd380ccd5aca1151074fede04826f1a4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:098973d584c122288fe5b701da298c65ee1c7cf10befa8c2e26784670c307dc0 +size 40690 diff --git a/marked/Rel-16/23_series/23216/e2c120be98ede6deb60dd341f5a9803b_img.jpg b/marked/Rel-16/23_series/23216/e2c120be98ede6deb60dd341f5a9803b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7f282c3ad77b991efa86c129dff2ab29ed7e3989 --- /dev/null +++ b/marked/Rel-16/23_series/23216/e2c120be98ede6deb60dd341f5a9803b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2d51a0c2a9e332b32ffd3b0a499ed14e915b66cbce0adcec8e4d4a0c1dcc9fc6 +size 71938 diff --git a/marked/Rel-16/23_series/23216/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg b/marked/Rel-16/23_series/23216/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8de532fbbf06bb2653c550fc7e89c205c9531065 --- /dev/null +++ b/marked/Rel-16/23_series/23216/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eabec5d5b18ba03bd35d499a82266827e8ec2ff226c5a662fdd1b405d7ccd4f1 +size 58925 diff --git a/marked/Rel-16/23_series/23216/f388cbdae6f0ef3aeb96fdf9984d1284_img.jpg b/marked/Rel-16/23_series/23216/f388cbdae6f0ef3aeb96fdf9984d1284_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fba82bae9253f000b3b94f12315ce72f2fd4da2d --- /dev/null +++ b/marked/Rel-16/23_series/23216/f388cbdae6f0ef3aeb96fdf9984d1284_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:056f7de6d82f885be35334173c47f9033386910fd6a8c3905f796c345d0554e7 +size 81815 diff --git a/marked/Rel-16/23_series/23216/f6e8acf9f931452d01688d311b5c0364_img.jpg b/marked/Rel-16/23_series/23216/f6e8acf9f931452d01688d311b5c0364_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f1bf1c105bb252247def1ffa2ea35cb2733bfdf0 --- /dev/null +++ b/marked/Rel-16/23_series/23216/f6e8acf9f931452d01688d311b5c0364_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3db84b8ca1606a428f0d990707ffb716973a37ad1f950eec72ef8c7619c00304 +size 71461 diff --git a/marked/Rel-16/23_series/23216/ff7977984f2552f326b2089d7595fff3_img.jpg b/marked/Rel-16/23_series/23216/ff7977984f2552f326b2089d7595fff3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..02c2d45e2046ffdefcc21495d10c48f196f59214 --- /dev/null +++ b/marked/Rel-16/23_series/23216/ff7977984f2552f326b2089d7595fff3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:098fb1f953cfe540220e83e49ccf99e8ab3e47785a1bbb9f3d966d974034f595 +size 21958 diff --git a/marked/Rel-16/23_series/23216/raw.md b/marked/Rel-16/23_series/23216/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..6371b274fb31eaf4cd81030cef5f2b34e9455af9 --- /dev/null +++ b/marked/Rel-16/23_series/23216/raw.md @@ -0,0 +1,2799 @@ + + +# 3GPP TS 23.216 V16.7.0 (2022-06) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Single Radio Voice Call Continuity (SRVCC); Stage 2 (Release 16)** + + + +The 5G logo, featuring 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 + + + +The 3GPP logo, featuring the text "3GPP" in a stylized, bold, black font. Below the "P" is a red signal icon consisting of three curved lines. 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 + +--- + +
Additional clause on OSA API added. | | | | +| 22/11/00 | | N1-001386 | | | V 0.2.0 created based on discussion in CN1#14. The clause on scope modified. | | | | +| 28/11/00 | | N1-001448 | | | V 0.3.0 created based on discussion in CN1/SA2 joint meeting. The title modified. | | | | +| Jan 2001 | | N1-010069
NJ-010102 | | | V0.3.1 created. Specification number TS 23.218 allocated to TS 23.cde. | | | | +| 16/1/01 | | NJ-010106 | | | V0.4.0 created. Clause 8 on OSA API updated to include the proposal in NJ-010104 agreed at joint CN1/2/4 meeting on 23.218. | | | | +| Mar 2001 | | N1-010762 | | | V0.5.0 created. Clause 6.5 updated to include the proposal in NJ-010117 agreed at the joint CN1/2/3/4 Feb meeting in Sophia. Reference to Visited Network updated. | | | | +| Jun 2001 | | N1-010981 | | | V0.5.1 created. Informative Annex B created containing N1-010749 agreed at Joint CN1/2/3/4 meeting in Puerto Rico. | | | | +| Aug 2001 | | N1-011090 | | | V0.5.2 created. Section 5 updated to include the proposals in N1-010982, N1-011013 and N1-011043; Section 6 updated to include the proposals in N1-011044 and N1-011045, agreed at CN1#18 and joint CN1/2/3/4 meetings in Dresden. | | | | +| Sep 2001 | | N1-011365 | | | V0.6.0 created. Document layout reorganized and content updated to conform to proposal in N1-011277; Section 6 and Section 9 updated to include the proposals in N1-011342, agreed at CN1#19 meeting in Helsinki. | | | | +| Oct 2001 | | N1-011522 | | | V0.7.0 created. Appendix B.1 added based on N1-011423 agreed at CN1#19bis meeting in Sophia Antipolis | | | | +| Oct 2001 | | N1-011707 | | | V0.8.0 created using Tdocs:
N1-011596, N1-011597, N1-011599, N1-011600 | 0.7.0 | 0.8.0 | | +| Nov 2001 | | N1-011867 | | | V0.9.0 created using Tdocs:
N1-011751, N1-011778 | 0.8.0 | 0.9.0 | | +| Dec 2001 | | NP-010640
N1-020033 | | | V1.0.0 created using Tdocs:
N1-011999, N1-012051 agreed at CN#21 in Cancun. To be presented for information at CN#14 | 0.9.0 | 1.0.0 | | +| Jan 2002 | | N1-020343 | | | V1.1.0 created using Tdocs:
N1-020035, N1-020036, N1-020069, N1-020071 N1-020072, N1-020107, N1-020109, N1-020110, N1-020114, N1-020115 N1-020116, N1-020119 N1-020137, N1-020153, N1-020156, N1-020164 agreed at CN1 SIP Adhoc 0102 in Phoenix. | 1.0.0 | 1.1.0 | | +| Feb 2002 | | N1-020552 | | | V1.2.0 created using Tdocs:
N1-020231, N1-020385, N1-020387, N1-020392, N1-020393, N1-020448, N1-020450, N1-020451, N1-020452, N1-020453 agreed at CN1#22 in Sophia Antipolis, and corrected implementation error of N1-020156. | 1.1.0 | 1.2.0 | | +| Feb 2002 | | | | | V2.0.0 created using Tdocs:
N1-020607, N1-020620, N1-020633, N1-020634, N1-020637, N1-020653, N1-020661, N1-020662, N1-020667 agreed at CN1#22 bis in Oulu. | 1.2.0 | 2.0.0 | | +| Mar 2002 | | | | | Editorial clean-up by ETSI/MCC. | 2.0.0 | 2.0.1 | | +| Mar 2002 | TSG
CN#1
5 | NP-020047 | | | The draft was approved and decided to be 'frozen', and 3GPP TS 23.218 was then to be issued in Rel-5 with the needed new RFC numbers allocated in NP-020134 incorporated. | 2.0.1 | 5.0.0 | | +| Jun 2002 | NP-16 | NP-020226 | 002 | 3 | HSS providing to the S-CSCF the subset of the relevant end user profile | 5.0.0 | 5.1.0 | N1-020972 | +| Jun 2002 | NP-16 | NP-020226 | 003 | 10 | Clarification on SPI related text | 5.0.0 | 5.1.0 | N1-021405 | +| Jun 2002 | NP-16 | NP-020226 | 004 | 4 | Passing charging correlation information | 5.0.0 | 5.1.0 | N1-021423 | +| Jun 2002 | NP-16 | NP-020226 | 006 | 1 | Correction of terminology in 23.218 regarding Offer-counter offer answer | 5.0.0 | 5.1.0 | N1-020951 | +| Jun 2002 | NP-16 | NP-020226 | 012 | 5 | Update of the S-CSCF AS relationship, for REGISTER | 5.0.0 | 5.1.0 | N1-021425 | +| Jun 2002 | NP-16 | NP-020226 | 014 | 1 | User profile filter criteria updates | 5.0.0 | 5.1.0 | N1-021384 | +| Jun 2002 | NP-16 | NP-020226 | 015 | 1 | Add references for Sh and Si interfaces | 5.0.0 | 5.1.0 | N1-021385 | +| Jun 2002 | NP-16 | NP-020226 | 016 | 1 | SIP Application Server acting as a Gateway to an external Application Server; and OSA API usage. | 5.0.0 | 5.1.0 | N1-021404 | +| Jun 2002 | NP-16 | NP-020226 | 017 | 1 | Clarification to Handling of IP multimedia registration for barred public user identities | 5.0.0 | 5.1.0 | N1-021424 | +| Jun 2002 | NP-16 | NP-020226 | 019 | | Correction of COMET to UPDATE in 23.218 | 5.0.0 | 5.1.0 | N1-021252 | + +| | | | | | | | | | +|-----------|-------|-----------|------|---|--------------------------------------------------------------------------------------------------------------|-------|-------|-----------| +| Sep 2002 | NP-17 | NP-020373 | 021 | 1 | Service profiles and implicitly registered public user identities | 5.1.0 | 5.2.0 | N1-021828 | +| Sep 2002 | NP-17 | NP-020373 | 022 | 2 | Clarification on specialized charging server | 5.1.0 | 5.2.0 | N1-021859 | +| Sep 2002 | NP-17 | NP-020373 | 025 | 1 | Clarification on location information for IMS | 5.1.0 | 5.2.0 | N1-021829 | +| Sep 2002 | NP-17 | NP-020373 | 026 | 1 | Proposed change of term SPI to SPT | 5.1.0 | 5.2.0 | N1-021830 | +| Sep 2002 | NP-17 | NP-020373 | 027 | 1 | Support of originating requests from Application Servers | 5.1.0 | 5.2.0 | N1-021831 | +| Dec. 2002 | NP-18 | NP-020552 | 029 | 1 | Clarification on CCF/ECF addresses | 5.2.0 | 5.3.0 | N1-022142 | +| Dec. 2002 | NP-18 | NP-020553 | 030 | 3 | Clarification on MRFP reference point | 5.2.0 | 5.3.0 | N1-022468 | +| Dec. 2002 | NP-18 | NP-020552 | 031 | 1 | Support of originating requests from Application Servers | 5.2.0 | 5.3.0 | N1-022144 | +| Dec. 2002 | NP-18 | NP-020552 | 033 | | Addition of Request-URI as SPT | 5.2.0 | 5.3.0 | N1-022297 | +| Dec. 2002 | NP-18 | NP-020552 | 034 | 1 | Clarifications on Annex C (Informative) | 5.2.0 | 5.3.0 | N1-022469 | +| Dec. 2002 | NP-18 | NP-020552 | 038 | 1 | Clarification to use of Service Information | 5.2.0 | 5.3.0 | N1-022475 | +| Mar 2003 | NP-19 | NP-030045 | 040 | 2 | Clarification on Sh interface for charging purposes | 5.3.0 | 5.4.0 | N1-030309 | +| Mar 2003 | NP-19 | NP-030046 | 042 | | Correction related to implicit public user identities in third party REGISTER | 5.3.0 | 5.4.0 | N1-030197 | +| Jun 2003 | NP-20 | NP-030272 | 043 | 5 | Correction on Handling of MO request | 5.4.0 | 5.5.0 | N1-030943 | +| Jun 2003 | NP-20 | NP-030272 | 044 | 1 | Corrections regarding SPTs and Filter Criteria handling on REGISTER request | 5.4.0 | 5.5.0 | N1-030516 | +| Jun 2003 | NP-20 | NP-030272 | 046 | 1 | Clarifications on SPT. | 5.4.0 | 5.5.0 | N1-030517 | +| Jun 2003 | NP-20 | NP-030272 | 048 | | Service Key Clarification | 5.4.0 | 5.5.0 | N1-030663 | +| Jun 2003 | NP-20 | NP-030272 | 051 | 1 | S-CSCF behavior correction to enable call forwarding | 5.4.0 | 5.5.0 | N1-030855 | +| Jun 2003 | NP-20 | NP-030272 | 055 | 1 | Filtering of unknown header fields and header parameters | 5.4.0 | 5.5.0 | N1-030924 | +| Sept 2003 | NP-21 | NP-030411 | 057 | | Removal of Incorrect Information | 5.5.0 | 5.6.0 | N1-031070 | +| Dec 2003 | NP-22 | NP-030475 | 053 | 3 | Flow number corrections in Annex B | 5.6.0 | 5.7.0 | N1-031630 | +| Dec 2003 | NP-22 | NP-030482 | 059 | | Corrections on charging specification number | 5.7.0 | 6.0.0 | N1-031468 | +| Mar 2004 | NP-23 | NP-040032 | 064 | 1 | Dh interface | 6.0.0 | 6.1.0 | N1-040158 | +| Mar 2004 | NP-23 | NP-040032 | 066 | 2 | Initiating Back to Back User Agent | 6.0.0 | 6.1.0 | N1-040472 | +| Sep 2004 | NP-25 | NP-040384 | 69 | | IFC process termination at R-URI change | 6.1.0 | 6.2.0 | N1-041440 | +| Sep 2004 | NP-25 | NP-040384 | 70 | 1 | Third party registration optimization | 6.1.0 | 6.2.0 | N1-041562 | +| Mar 2005 | NP-27 | NP-050069 | 76 | | Filter criteria matching and generation of third-party REGISTER request for network-initiated deregistration | 6.2.0 | 6.3.0 | N1-050223 | +| Mar 2005 | NP-27 | NP-050073 | 072 | | Resolution of references to 24.228 | 6.2.0 | 6.3.0 | N1-050061 | +| Mar 2005 | NP-27 | NP-050073 | 074 | 1 | Default handling | 6.2.0 | 6.3.0 | N1-050288 | +| Dec 2005 | CT-30 | CP-050550 | 079 | | Mobile originated request unregistered | 6.3.0 | 7.0.0 | C1-051428 | +| Mar 2006 | CT-31 | CP-060160 | 0080 | 2 | Change of originating and terminating terminal terminology | 7.0.0 | 7.1.0 | | +| Mar 2006 | CT-31 | CP-060124 | 0081 | 1 | Editorial corrections | 7.0.0 | 7.1.0 | C1-060122 | +| Mar 2006 | CT-31 | CP-060124 | 0082 | - | Correction for the description of the contents of the clauses | 7.0.0 | 7.1.0 | C1-060409 | +| Jun 2006 | CT-32 | CP-060274 | 0086 | 1 | Amend the playing announcement call flow | 7.1.0 | 7.2.0 | C1-061081 | +| Jun 2006 | CT-32 | CP-060262 | 0085 | 1 | 3Rd party registratin clarification | 7.1.0 | 7.2.0 | C1-061005 | +| Sept 2006 | CT-33 | CP-060466 | 0089 | 2 | Impact of GRUU on Service Control in 23.218 | 7.2.0 | 7.3.0 | C1-061364 | +| Sept 2006 | CT-33 | CP-060468 | 0090 | 1 | Clarification of Cases of Downloading iFC to S-CSCF | 7.2.0 | 7.3.0 | C1-061704 | +| Sept 2006 | CT-33 | CP-060468 | 0091 | 1 | S-CSCF handling of terminations when AS modifies the Req-URI | 7.2.0 | 7.3.0 | C1-061760 | +| Oct 2006 | | | | | Version 7.3.1 created by MCC to correct styles | 7.3.0 | 7.3.1 | | +| Nov 2006 | | CP-060660 | 0092 | 3 | Introduction of communication service concept in TS 23218 | 7.3.1 | 7.4.0 | C1-062521 | +| Mar 2007 | CT-35 | CP-070153 | 0094 | 1 | The IMS Communication service identifier can be included in the SIP response message | 7.4.0 | 7.5.0 | C1-070559 | +| Jun 2007 | CT-36 | CP-070383 | 0095 | 6 | IMS Communication Service ID | 7.5.0 | 7.6.0 | C1-071477 | +| Jun 2007 | CT-36 | CP-070387 | 0097 | 1 | Dynamic Service Activation Info | 7.5.0 | 7.6.0 | C1-070977 | +| Sep 2007 | CT-37 | CP-070586 | 0100 | 2 | Additions in TS 23.218 due to ICSI/IARI | 7.6.0 | 7.7.0 | C1-072182 | +| Sep 2007 | CT-37 | CP-070586 | 0101 | 2 | Completing 23.218 ICSI procedures | 7.6.0 | 7.7.0 | C1-072160 | +| Sep 2007 | | | | | Correction in History table (new version column) done by MCC | 7.7.0 | 7.7.1 | | +| Dec 2007 | CT-38 | CP-070806 | 0104 | 3 | Completing 23.218 ICSI text | 7.7.1 | 7.8.0 | C1-073100 | +| Dec 2007 | CT-38 | CP-070810 | 0103 | 1 | Correction of request handling in terminating unregistered case | 7.8.0 | 8.0.0 | C1-072664 | +| Dec 2007 | CT-38 | CP-070810 | 0102 | 1 | Enabling service triggering after call forwarding | 7.8.0 | 8.0.0 | C1-072662 | +| Mar 2008 | CT-39 | CP-080140 | 0105 | 2 | Addition of other access network types. | 8.0.0 | 8.1.0 | C1-080415 | +| Jun 2008 | CT-40 | CP-080418 | 0108 | 3 | B2BUA AS influence of filter criteria evaluation | 8.1.0 | 8.2.0 | C1-082032 | +| Jun 2008 | CT-40 | CP-080365 | 0111 | 1 | Cr interface description | 8.1.0 | 8.2.0 | C1-081341 | +| Jun 2008 | CT-40 | CP-080354 | 0113 | 1 | Editorial changes to subclauses 6.4 and 6.5 | 8.1.0 | 8.2.0 | C1-082026 | +| Jun 2008 | CT-40 | CP-080344 | 0116 | - | Correction of GRUU references | 8.1.0 | 8.2.0 | C1-081797 | +| Sep 2008 | CT-41 | CP-080536 | 0117 | 2 | Enhancement of Filter Criteria to Include Incoming Register in Third Party Register | 8.2.0 | 8.3.0 | C1-083098 | +| Sep 2008 | CT-41 | CP-080537 | 0118 | 1 | MRB | 8.2.0 | 8.3.0 | C1-083361 | +| Dec 2008 | CT-42 | CP-080854 | 0120 | | Cr interface addition to architecture diagram | 8.3.0 | 8.4.0 | C1-084751 | +| Dec 2008 | CT-42 | CP-080854 | 0121 | | Media example fixes | 8.3.0 | 8.4.0 | C1-084753 | +| Dec 2008 | CT-42 | CP-080873 | 0122 | | Enhancement of Filter Criteria to include final response to Incoming Register in Third Party Register | 8.3.0 | 8.4.0 | C1-085056 | +| Dec 2008 | CT-42 | | | | Editorial cleanup by MCC | 8.3.0 | 8.4.0 | | + +| | | | | | | | | | +|----------|-------|-----------|------|---|-----------------------------------------------------------------------------------------------|--------|--------|-----------| +| Dec 2009 | CT-46 | CP-090894 | 0127 | | Updating of GRUU references | 8.4.0 | 8.5.0 | C1-094829 | +| Dec 2009 | CT-46 | CP-090923 | 0124 | 2 | Allowing direct routing between AS and MRFC | 8.5.0 | 9.0.0 | C1-094735 | +| Dec 2009 | CT-46 | CP-090936 | 0125 | | Registration of IMS media plane security capabilities | 8.5.0 | 9.0.0 | C1-094418 | +| Mar 2010 | CT-47 | CP-100110 | 0129 | | Resolve EN on terminating request handling | 9.0.0 | 9.1.0 | C1-100467 | +| Jun 2010 | CT-48 | CP-100366 | 0130 | | Updating references to OMA specifications | 9.1.0 | 9.2.0 | C1-101714 | +| Mar 2011 | CT-51 | | | | Upgrade to Rel-10 | 9.2.0 | 10.0.0 | | +| Sep 2011 | CT-53 | CP-110693 | 0132 | 2 | Identifying Application Server capabilities on the signaling route | 10.0.0 | 11.0.0 | C1-113592 | +| Sep 2011 | CT-53 | CP-110688 | 0133 | 2 | Adding MRB between AS and MRFC | 10.0.0 | 11.0.0 | C1-113725 | +| Dec 2011 | CT-54 | CP-110889 | 0137 | 1 | Border control elements and the MRB | 11.0.0 | 11.1.0 | C1-115156 | +| Dec 2011 | CT-54 | CP-110889 | 0138 | | MRB interfaces | 11.0.0 | 11.1.0 | C1-114812 | +| Mar 2012 | CT-55 | CP-120119 | 0136 | 3 | AS selection of MRF resources | 11.1.0 | 11.2.0 | C1-120753 | +| Mar 2012 | CT-55 | CP-120119 | 0139 | 1 | Revisions to Rc interface | 11.1.0 | 11.2.0 | C1-120754 | +| Jun 2012 | CT-56 | CP-120320 | 0141 | | Editorial correction in border control concepts | 11.2.0 | 11.3.0 | C1-120991 | +| Jun 2012 | CT-56 | CP-120307 | 0143 | | Correction of reference to TS 33.328 | 11.2.0 | 11.3.0 | C1-121958 | +| Jun 2012 | CT-56 | CP-120320 | 0144 | 1 | Access to MRB and to MRF resources by entities other than an application server | 11.2.0 | 11.3.0 | C1-122241 | +| Jun 2012 | CT-56 | CP-120316 | 0145 | 3 | Creation of a new functional entity to support application servers in the enterprise | 11.2.0 | 11.3.0 | C1-122479 | +| Jun 2012 | CT-56 | CP-120320 | 0146 | 1 | Correction of MRF and MRB related interfaces | 11.2.0 | 11.3.0 | C1-122242 | +| Jun 2012 | CT-56 | CP-120320 | 0147 | | MRB to MRB operation | 11.2.0 | 11.3.0 | C1-122140 | +| Sep 2012 | CT-57 | CP-120597 | 0148 | 1 | Usage of visited network MRB address when allocating MRF resources | 11.3.0 | 11.4.0 | C1-123276 | +| Sep 2012 | CT-57 | CP-120591 | 0149 | | Addressing an editor's note relating to interface naming | 11.3.0 | 11.4.0 | C1-122926 | +| Sep 2012 | CT-57 | CP-120591 | 0150 | 1 | Addressing an editor's note supported functionality for the ISC gateway function | 11.3.0 | 11.4.0 | C1-123268 | +| Sep 2012 | CT-57 | CP-120597 | 0152 | | Addressing an editor's note relating to resources in multiple VPLMNs | 11.3.0 | 11.4.0 | C1-122934 | +| Sep 2012 | CT-57 | CP-120597 | 0153 | 1 | Addressing an editor's note relating to border control functions on Mr, Mr' and Cr interfaces | 11.3.0 | 11.4.0 | C1-123278 | +| Sep 2012 | CT-57 | CP-120597 | 0154 | | Addressing an editor's note relating to border control concepts for the Rc interface | 11.3.0 | 11.4.0 | C1-122936 | +| Sep 2012 | CT-57 | CP-120597 | 0155 | | Addressing an editor's note relating to IBCF usage on media resource allocation architecture | 11.3.0 | 11.4.0 | C1-122970 | +| Sep 2012 | CT-57 | CP-120591 | 0157 | 1 | Functionalities of the IBCF on the ISC interface | 11.3.0 | 11.4.0 | C1-123269 | +| Dec 2012 | CT-58 | CP-120804 | 0158 | 1 | Recover screened information | 11.4.0 | 11.5.0 | C1-124096 | +| Dec 2012 | CT-58 | CP-120809 | 0160 | 2 | Transit Function – ISC alternative | 11.4.0 | 11.5.0 | C1-124938 | +| Dec 2012 | CT-58 | CP-120818 | 0162 | 1 | Transferring IMS CAMEL Data with Sh Protocol | 11.5.0 | 12.0.0 | C1-124878 | +| Mar 2013 | CT-59 | CP-130127 | 0168 | 1 | Interface IM-SSF / HSS with Diameter | 12.0.0 | 12.1.0 | C1-130505 | +| Jun 2013 | CT-60 | CP-130249 | 0170 | 1 | Renaming the Mz reference point to be Mf | 12.1.0 | 12.2.0 | C1-131618 | +| Sep 2013 | CT-61 | CP-130513 | 0171 | 1 | Updating TS 23.218 to RFC 6665 | 12.2.0 | 12.3.0 | C1-133235 | +| Mar 2015 | CT-67 | CP-150082 | 0175 | 1 | Correction of Mf reference point name in figure | 12.3.0 | 13.0.0 | C1-150598 | + +| Change history | | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------|--|---------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | | New version | +| 2017-03 | CT-75 | | | | | Upgrade to Rel-14 | | 14.0.0 | +| 2018-06 | SA-80 | - | - | - | | Update to Rel-15 version (MCC) | | 15.0.0 | +| 2020-07 | SA-88e | - | - | - | | Update to Rel-16 version (MCC) | | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/23_series/23280/02dfdcd208dbdc8fa4f645885e59dd17_img.jpg b/marked/Rel-16/23_series/23280/02dfdcd208dbdc8fa4f645885e59dd17_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bc47188cc1c50ad9dda9339edfded407ae27092f --- /dev/null +++ b/marked/Rel-16/23_series/23280/02dfdcd208dbdc8fa4f645885e59dd17_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5190b7bd6d4a33c9cb698fbe41f5731add69a3c5a270e7dfaf88941b8d958ff1 +size 17869 diff --git a/marked/Rel-16/23_series/23280/036ceaf207a7b289ca76e160892eb724_img.jpg b/marked/Rel-16/23_series/23280/036ceaf207a7b289ca76e160892eb724_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..38e992dd2ea66cd8d4567e45d446dce029fe95f3 --- /dev/null +++ b/marked/Rel-16/23_series/23280/036ceaf207a7b289ca76e160892eb724_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0c16bcc94f101379f184858857d932e9e2218cc7aba35e9ff33fcd7c5cacec3f +size 71974 diff --git a/marked/Rel-16/23_series/23280/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg b/marked/Rel-16/23_series/23280/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0b5883d37db63eb1218c2d478013b2d470820e53 --- /dev/null +++ b/marked/Rel-16/23_series/23280/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4d903e1a265bcad3aa9fcb995374044c6b3e05910399a4b501f9fea5534ef62e +size 112855 diff --git a/marked/Rel-16/23_series/23280/0a73b03fba21af142d619a9a662e6490_img.jpg b/marked/Rel-16/23_series/23280/0a73b03fba21af142d619a9a662e6490_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b667ee8d423fe7c761b4b1f0c281493b2461201e --- /dev/null +++ b/marked/Rel-16/23_series/23280/0a73b03fba21af142d619a9a662e6490_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d23d63d644220390678e2848cdc39c47b0a69ea94298f21125548fd8ea95e077 +size 42566 diff --git a/marked/Rel-16/23_series/23280/0d9b44054c70dcda35129f11b97a912f_img.jpg b/marked/Rel-16/23_series/23280/0d9b44054c70dcda35129f11b97a912f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e7b715301ddb43d6f1468a015815719768793bb1 --- /dev/null +++ b/marked/Rel-16/23_series/23280/0d9b44054c70dcda35129f11b97a912f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3333f3c74c80917965d0f6d84738d37ef7d5e0c9494285590aba0d20e5e7bf46 +size 12376 diff --git a/marked/Rel-16/23_series/23280/0dfdff10c725fe9c332b07ade9d23a5e_img.jpg b/marked/Rel-16/23_series/23280/0dfdff10c725fe9c332b07ade9d23a5e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ce9becf0bb42b61403ddffa55f8e065ad51b94b1 --- /dev/null +++ b/marked/Rel-16/23_series/23280/0dfdff10c725fe9c332b07ade9d23a5e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8d001affc8c7e81a1031953f3e1e4a6dd6619baa5538e11119a5a50d3de523c5 +size 69259 diff --git a/marked/Rel-16/23_series/23280/0e252770f8f0573617e0112b36a93d2f_img.jpg b/marked/Rel-16/23_series/23280/0e252770f8f0573617e0112b36a93d2f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..99cac6ad2fb9234db6d8b67d9d538a471911a3eb --- /dev/null +++ b/marked/Rel-16/23_series/23280/0e252770f8f0573617e0112b36a93d2f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8e7863b67443e99e9e0504ead176da5a9615bc455b8873e5dd247a47119265a0 +size 31016 diff --git a/marked/Rel-16/23_series/23280/0ea87c5f55e5857d0969bc5ca36dccba_img.jpg b/marked/Rel-16/23_series/23280/0ea87c5f55e5857d0969bc5ca36dccba_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c4d89430e31021d1519dd0c27fba1c9f129a251b --- /dev/null +++ b/marked/Rel-16/23_series/23280/0ea87c5f55e5857d0969bc5ca36dccba_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0d9ce003648fcc7c0810958f7fa02cb13190556fa8052290a896216f055ab900 +size 29761 diff --git a/marked/Rel-16/23_series/23280/132cff7e872feb31f629703959beddd7_img.jpg b/marked/Rel-16/23_series/23280/132cff7e872feb31f629703959beddd7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..38a10ad70dafb4fe1f5b4de05c0fb99ad0c96935 --- /dev/null +++ b/marked/Rel-16/23_series/23280/132cff7e872feb31f629703959beddd7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7e5f6ffd95d1ca33faa052114ea7d9d3b9eccc46f589dd38f70531fe56c9455d +size 45984 diff --git a/marked/Rel-16/23_series/23280/15906392337ec83a921988b52f102a44_img.jpg b/marked/Rel-16/23_series/23280/15906392337ec83a921988b52f102a44_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cf88a920c57f6907c1b3f3ab1170f3e14de8a148 --- /dev/null +++ b/marked/Rel-16/23_series/23280/15906392337ec83a921988b52f102a44_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:01721daaafe7884b2090e62cc0460555c1910bad2b5e63be2efcfc7f27664014 +size 15092 diff --git a/marked/Rel-16/23_series/23280/17431d8b59408f09df7552d8bdbaa015_img.jpg b/marked/Rel-16/23_series/23280/17431d8b59408f09df7552d8bdbaa015_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b1633860aeaf28d6b2188b83ad9ed065ab8d70a5 --- /dev/null +++ b/marked/Rel-16/23_series/23280/17431d8b59408f09df7552d8bdbaa015_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:47cbed7629592c4ec6229e92d58cc7e8bd489df4bdd28ab0d2f38c03bad77864 +size 111108 diff --git a/marked/Rel-16/23_series/23280/18003425d0e8638dde4acc9c5c468c5c_img.jpg b/marked/Rel-16/23_series/23280/18003425d0e8638dde4acc9c5c468c5c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2bda6f1e45f9709bc3352893e8d6fd78821c8945 --- /dev/null +++ b/marked/Rel-16/23_series/23280/18003425d0e8638dde4acc9c5c468c5c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:11a54cf124553aa04808a470dae5d63b799a88df4dcc81e0775f88c305c9743c +size 51772 diff --git a/marked/Rel-16/23_series/23280/187bba66c887c745c512add37a577c5e_img.jpg b/marked/Rel-16/23_series/23280/187bba66c887c745c512add37a577c5e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..18b2b6009d96397c6c17822119de982d3d99aac4 --- /dev/null +++ b/marked/Rel-16/23_series/23280/187bba66c887c745c512add37a577c5e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e126f0a5069613da23d6b2cfaaa7cdc9ea4e051a555206c39b76ddc0cdf78bf9 +size 28936 diff --git a/marked/Rel-16/23_series/23280/187d05bf7ead21e1394b61320d8b3632_img.jpg b/marked/Rel-16/23_series/23280/187d05bf7ead21e1394b61320d8b3632_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7b50cc161e54da12ad6354465bc7570a7bc420b1 --- /dev/null +++ b/marked/Rel-16/23_series/23280/187d05bf7ead21e1394b61320d8b3632_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5708dbe385ac83a96e7dac8e1db2c0a2939846f98f0c068972e0fde31bd1b8e1 +size 49753 diff --git a/marked/Rel-16/23_series/23280/195611c20b2dc7ed0fa3033392e22908_img.jpg b/marked/Rel-16/23_series/23280/195611c20b2dc7ed0fa3033392e22908_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..137280ee9e3d76a5ba4f7475c73fdeccad910776 --- /dev/null +++ b/marked/Rel-16/23_series/23280/195611c20b2dc7ed0fa3033392e22908_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:17b7b5e9ca3d9e91760178e31ac6707fb04e2c4fd0cd04f24cc3c22b62bbb331 +size 69465 diff --git a/marked/Rel-16/23_series/23280/1ea7909aea2fb749a6fe98fbdb8cacae_img.jpg b/marked/Rel-16/23_series/23280/1ea7909aea2fb749a6fe98fbdb8cacae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6fd03d20b78fd1a7dcf2abcbe3151cf1f18ec34e --- /dev/null +++ b/marked/Rel-16/23_series/23280/1ea7909aea2fb749a6fe98fbdb8cacae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c7af490005684ed949e1bdb8981244bd238dd2f6fb3c109e1a0d791c75c229de +size 22315 diff --git a/marked/Rel-16/23_series/23280/20809e79dee38f3d6e03e1ad565a9cf5_img.jpg b/marked/Rel-16/23_series/23280/20809e79dee38f3d6e03e1ad565a9cf5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2f0a6b97df4483fe8c076dce7d52417576a465e0 --- /dev/null +++ b/marked/Rel-16/23_series/23280/20809e79dee38f3d6e03e1ad565a9cf5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5123cc6a790599171c50a23f9f4f4ac8c5f75084d41764ad7061503ca26694f3 +size 57573 diff --git a/marked/Rel-16/23_series/23280/2119293733c74fc64de88aefd597f4bb_img.jpg b/marked/Rel-16/23_series/23280/2119293733c74fc64de88aefd597f4bb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9a5a68a760d77da90b0f7c9449ac1cbd1574b657 --- /dev/null +++ b/marked/Rel-16/23_series/23280/2119293733c74fc64de88aefd597f4bb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:83cf85fd830139da6f3a9e4165657fd543404ddc2c70f4c0b56bbf67297b69da +size 78236 diff --git a/marked/Rel-16/23_series/23280/21327313f7b18a481da0c87a6472a80d_img.jpg b/marked/Rel-16/23_series/23280/21327313f7b18a481da0c87a6472a80d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..15b9eeb30920aa9f9ae724e39ba9bf6962ab4fbb --- /dev/null +++ b/marked/Rel-16/23_series/23280/21327313f7b18a481da0c87a6472a80d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9d7f84064ec2ca092651dbd6553f1890b718c2570bb4243690a9bd5893b21f3e +size 42867 diff --git a/marked/Rel-16/23_series/23280/236f674770a03c918c0375a74fe950db_img.jpg b/marked/Rel-16/23_series/23280/236f674770a03c918c0375a74fe950db_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..009127e17aa5dd72eea9bc33c1db068f048973dd --- /dev/null +++ b/marked/Rel-16/23_series/23280/236f674770a03c918c0375a74fe950db_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a07e3c3ff84789f6e3b5130ad52810f33c0b755956d8616461dc6340d99b848c +size 60012 diff --git a/marked/Rel-16/23_series/23280/26d664119ad25250780f554633444e54_img.jpg b/marked/Rel-16/23_series/23280/26d664119ad25250780f554633444e54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ea4e49a26dd4c13cd29e6ab07e0517dda3a15f28 --- /dev/null +++ b/marked/Rel-16/23_series/23280/26d664119ad25250780f554633444e54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6cc8e4fc37cb0ddfed95ff0677ef6d1f37fa3af6e7dfab00e035e52a2e9c870b +size 20304 diff --git a/marked/Rel-16/23_series/23280/28d75f39a24203712ee907b32cf0bbe5_img.jpg b/marked/Rel-16/23_series/23280/28d75f39a24203712ee907b32cf0bbe5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b7b9bfb230cea6420ebd505b77d87a339e1b8fca --- /dev/null +++ b/marked/Rel-16/23_series/23280/28d75f39a24203712ee907b32cf0bbe5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1a01067c6a54093395cc4da996b2243dd06976b8dfd7785d9fa6ec105d2c7190 +size 32678 diff --git a/marked/Rel-16/23_series/23280/2a476a0b3dbc3429436246db4784ff9f_img.jpg b/marked/Rel-16/23_series/23280/2a476a0b3dbc3429436246db4784ff9f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f86e475c6b8d986a95a6383213c01b54f01f7751 --- /dev/null +++ b/marked/Rel-16/23_series/23280/2a476a0b3dbc3429436246db4784ff9f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c440dbb6f83f4f43352c6d5ea5ae4786fb2568d94bd75510562385519240aaac +size 27442 diff --git a/marked/Rel-16/23_series/23280/2df09d249c38abee55dbf0526dd6da0a_img.jpg b/marked/Rel-16/23_series/23280/2df09d249c38abee55dbf0526dd6da0a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..04840cfd8a5ea2bf190630c1b8e2395eefb31935 --- /dev/null +++ b/marked/Rel-16/23_series/23280/2df09d249c38abee55dbf0526dd6da0a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f2c767b39f1cef79c528573aea66484adf7e33fdf22c3fc7632eb7ad1a288da6 +size 48853 diff --git a/marked/Rel-16/23_series/23280/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg b/marked/Rel-16/23_series/23280/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a6f5bc3a0fce1a191e7d9d8f1701eb5f482701f9 --- /dev/null +++ b/marked/Rel-16/23_series/23280/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e9cedaac8391fe52e56ec292d9d15d3cced467f9992f7c44bff2b9f79e5765d2 +size 22823 diff --git a/marked/Rel-16/23_series/23280/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg b/marked/Rel-16/23_series/23280/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..95f1d22edf893530f0aad5adb68d0c61768a9c68 --- /dev/null +++ b/marked/Rel-16/23_series/23280/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c8c37942ac44deb80012d0966f80530a191261b000d7d2c4ebc134986be4e132 +size 29415 diff --git a/marked/Rel-16/23_series/23280/347010b7ac06d3ae97927fde0f784d7c_img.jpg b/marked/Rel-16/23_series/23280/347010b7ac06d3ae97927fde0f784d7c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..00e1930d7de52f56ee558fc071e9188d1dc2a270 --- /dev/null +++ b/marked/Rel-16/23_series/23280/347010b7ac06d3ae97927fde0f784d7c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d0bc65eee787dd82e963c0656ec602a3732407538b27ad48f1a51c639e2984f9 +size 65806 diff --git a/marked/Rel-16/23_series/23280/367926125450c2bc3f4bdca9d59a62ba_img.jpg b/marked/Rel-16/23_series/23280/367926125450c2bc3f4bdca9d59a62ba_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f76a4025193419060bd5dfe4d98d7755e47456fc --- /dev/null +++ b/marked/Rel-16/23_series/23280/367926125450c2bc3f4bdca9d59a62ba_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:67824bbea665e0b4d79bca43315b8f0ede3ed0af5bb4f53ad0088db45e0195ee +size 21946 diff --git a/marked/Rel-16/23_series/23280/39536a630fa74c3bcfd1670ee2152809_img.jpg b/marked/Rel-16/23_series/23280/39536a630fa74c3bcfd1670ee2152809_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7cd11d073298b48bcc6786137cee6de094b143ec --- /dev/null +++ b/marked/Rel-16/23_series/23280/39536a630fa74c3bcfd1670ee2152809_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:82476896cbfe925fb22cb3cd379d7e83461497da2dfd61a2c52519b182d8e04d +size 89500 diff --git a/marked/Rel-16/23_series/23280/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg b/marked/Rel-16/23_series/23280/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..47afd0c1e562bd89c5cbad2827b819a0238dc41d --- /dev/null +++ b/marked/Rel-16/23_series/23280/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f792bb79c559904023b1723ae1630e6ece1eb639840aca78ecb9099564fb0d17 +size 63768 diff --git a/marked/Rel-16/23_series/23280/4390b89fdb95cba102ee1f88e218b07b_img.jpg b/marked/Rel-16/23_series/23280/4390b89fdb95cba102ee1f88e218b07b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..71fe4224855739a2999fccfdecd63041fa6d4e98 --- /dev/null +++ b/marked/Rel-16/23_series/23280/4390b89fdb95cba102ee1f88e218b07b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e00d7eba38312cb352138b5af6c52d2860f55590a38cdc77f285b5bae90360ac +size 114178 diff --git a/marked/Rel-16/23_series/23280/468be155058fd5d2862919eb8ec35496_img.jpg b/marked/Rel-16/23_series/23280/468be155058fd5d2862919eb8ec35496_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4162c19a9b46eee1cb79358e5825cbf3482b9ddf --- /dev/null +++ b/marked/Rel-16/23_series/23280/468be155058fd5d2862919eb8ec35496_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b5237aae1225fe1e633cb398b5ddcb26863f1d3d244ef9be0ae4d9264bb71676 +size 30184 diff --git a/marked/Rel-16/23_series/23280/4792a2ccd62226861fadc22117edb7b1_img.jpg b/marked/Rel-16/23_series/23280/4792a2ccd62226861fadc22117edb7b1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e0f62b724437c947b6da5463b170b0e602fcedc1 --- /dev/null +++ b/marked/Rel-16/23_series/23280/4792a2ccd62226861fadc22117edb7b1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:08e47c10cd05e1faaf8f1b0b68ea7ff946534c6e014d351564f0c359d1325a5d +size 46456 diff --git a/marked/Rel-16/23_series/23280/4806f9f95fff13a30d6523bd6ffeac63_img.jpg b/marked/Rel-16/23_series/23280/4806f9f95fff13a30d6523bd6ffeac63_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c43fa16ac5c478b03f61c0effaf9f7eff1d653fc --- /dev/null +++ b/marked/Rel-16/23_series/23280/4806f9f95fff13a30d6523bd6ffeac63_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9dd4a71a92acd0738cb097dbe955c9bf7434a06b509b93dfbbe269ff72231760 +size 34964 diff --git a/marked/Rel-16/23_series/23280/4b398c5e8c4fd656d5b7a61806400650_img.jpg b/marked/Rel-16/23_series/23280/4b398c5e8c4fd656d5b7a61806400650_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..21dc04af9137fcdf8a876e95706685a6b89dfeba --- /dev/null +++ b/marked/Rel-16/23_series/23280/4b398c5e8c4fd656d5b7a61806400650_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2d0799e4b84e5d09d79ea575a37e4c1cead6d7da534956a20b905ffd34752592 +size 100620 diff --git a/marked/Rel-16/23_series/23280/4ca4ef49a4f79d5621932651f7ae3f5e_img.jpg b/marked/Rel-16/23_series/23280/4ca4ef49a4f79d5621932651f7ae3f5e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1b3f3a21f34e4aeba73dbcbe24c4d4ab71397b1c --- /dev/null +++ b/marked/Rel-16/23_series/23280/4ca4ef49a4f79d5621932651f7ae3f5e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:49b2da311a6ef13c9dc7f02c939fcd1bde4802e45b7e4c001e7721333190d2dd +size 43909 diff --git a/marked/Rel-16/23_series/23280/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg b/marked/Rel-16/23_series/23280/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7bfbbb128ba4655bfb04538fd5fc9a7ae3ff458c --- /dev/null +++ b/marked/Rel-16/23_series/23280/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ffcdbeaeecdcb9f28c7b591c8d0fde432854f8f14c9d3a27a987378c8f35b779 +size 57761 diff --git a/marked/Rel-16/23_series/23280/4f95964fc4eb05cd5cf7294114d77528_img.jpg b/marked/Rel-16/23_series/23280/4f95964fc4eb05cd5cf7294114d77528_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f33f7fd54f87bcb20b5eb6b8b81c081a2dfadc7f --- /dev/null +++ b/marked/Rel-16/23_series/23280/4f95964fc4eb05cd5cf7294114d77528_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bb8a6dbbde60ad5c32aaa978e4afc43317d72585ac5e702cdfcfe399a4284ad6 +size 18304 diff --git a/marked/Rel-16/23_series/23280/503e868b4dc4a68f02e22d83251f2b0f_img.jpg b/marked/Rel-16/23_series/23280/503e868b4dc4a68f02e22d83251f2b0f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..45c7a38064ac4da2be3e857985eec0f59a447a7d --- /dev/null +++ b/marked/Rel-16/23_series/23280/503e868b4dc4a68f02e22d83251f2b0f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e2f2901449109d94c780df20ae1145db96f655a1a50e8f201660877422c954bb +size 23359 diff --git a/marked/Rel-16/23_series/23280/521e2e9d53a2d9c4b3e22d151d46ee23_img.jpg b/marked/Rel-16/23_series/23280/521e2e9d53a2d9c4b3e22d151d46ee23_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..293e46639eab1139271f756ff4d7571a154ecf3a --- /dev/null +++ b/marked/Rel-16/23_series/23280/521e2e9d53a2d9c4b3e22d151d46ee23_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:04eb41ceae1ab9d02860f1cbb343c0032b1a2d689442214039689d50e6167bdb +size 70633 diff --git a/marked/Rel-16/23_series/23280/552ca016af3d6240648ab5a2cad97f60_img.jpg b/marked/Rel-16/23_series/23280/552ca016af3d6240648ab5a2cad97f60_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5ce999f27d4e58714fd79e1ff2f2a2dd22db174f --- /dev/null +++ b/marked/Rel-16/23_series/23280/552ca016af3d6240648ab5a2cad97f60_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e46ac6c7d767ec48bb9724e735961a7827c1cb58df55bf34485e469f5df44bc8 +size 34643 diff --git a/marked/Rel-16/23_series/23280/55736d2180d01f631782ce0784caafa3_img.jpg b/marked/Rel-16/23_series/23280/55736d2180d01f631782ce0784caafa3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e6217c7c1519382380a9e506da41ee0d03ba2911 --- /dev/null +++ b/marked/Rel-16/23_series/23280/55736d2180d01f631782ce0784caafa3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1e9e03355124797217d205d1b933c91e4da607d607d7f7ede34c5a6f9f4234e6 +size 66094 diff --git a/marked/Rel-16/23_series/23280/572cf014db14c8234f91c07d5a5a28c6_img.jpg b/marked/Rel-16/23_series/23280/572cf014db14c8234f91c07d5a5a28c6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a15aebae05fde652c35bf16c69011d108e4bf44c --- /dev/null +++ b/marked/Rel-16/23_series/23280/572cf014db14c8234f91c07d5a5a28c6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1bac5546b73de307adba496b79830e452a0c96565eb7a291e9b4012858d26832 +size 22972 diff --git a/marked/Rel-16/23_series/23280/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Rel-16/23_series/23280/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1ec39cad64e8ed11e0e6b30f4408108c446a385d --- /dev/null +++ b/marked/Rel-16/23_series/23280/5a4e62bead259c258d069fd3663ea670_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6f8ce580d45696a757734ee783b072b44d12852d4826d14332f91832be3adc6b +size 40369 diff --git a/marked/Rel-16/23_series/23280/5bba23cc120ad806779f82df1c01bebf_img.jpg b/marked/Rel-16/23_series/23280/5bba23cc120ad806779f82df1c01bebf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..67fdbf8bbf1c91263c028f350a3e023e98f0e1fe --- /dev/null +++ b/marked/Rel-16/23_series/23280/5bba23cc120ad806779f82df1c01bebf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6bc7c64df2738829692a8b1d7795e66726e5a4a0bfe608f4c5e6559c3b49ed4f +size 30878 diff --git a/marked/Rel-16/23_series/23280/5e815f5cc63672bd3b17d9b79eb78784_img.jpg b/marked/Rel-16/23_series/23280/5e815f5cc63672bd3b17d9b79eb78784_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d7dc25fec88c20e54c6a889672f7e172b804de03 --- /dev/null +++ b/marked/Rel-16/23_series/23280/5e815f5cc63672bd3b17d9b79eb78784_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d97b075e506395780d171935bb0b4499713b61faa8ba85974b2dcc6678e7da46 +size 9523 diff --git a/marked/Rel-16/23_series/23280/5e9af8986a5845504f251d3079da8078_img.jpg b/marked/Rel-16/23_series/23280/5e9af8986a5845504f251d3079da8078_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f6119a201eb4ed1075db7a41cf82c27c690ba51e --- /dev/null +++ b/marked/Rel-16/23_series/23280/5e9af8986a5845504f251d3079da8078_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:21f901100510f90b53c7632fbf0013fc30d5a062f2b062b35716265272e44ee0 +size 24908 diff --git a/marked/Rel-16/23_series/23280/61a7f401eb46fe99a71f27bc37493f04_img.jpg b/marked/Rel-16/23_series/23280/61a7f401eb46fe99a71f27bc37493f04_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..504664d20234606d6eb9a5f676c2ca07aa46e2d7 --- /dev/null +++ b/marked/Rel-16/23_series/23280/61a7f401eb46fe99a71f27bc37493f04_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9a68562abd9866f72c71d79e8bb5124b00bd45864ee2c96e402ee36fba11643d +size 30716 diff --git a/marked/Rel-16/23_series/23280/64544fbada794f3cdf4f78f5d83613e4_img.jpg b/marked/Rel-16/23_series/23280/64544fbada794f3cdf4f78f5d83613e4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..06dc3d2a3622b38f436ec76517e3cc9470fbf483 --- /dev/null +++ b/marked/Rel-16/23_series/23280/64544fbada794f3cdf4f78f5d83613e4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4012f07fe8db867d6e408f7e01c4542099156cd0d89f491ca0a2705f0a0d7722 +size 53198 diff --git a/marked/Rel-16/23_series/23280/677bcb564410628b8b966ad87b394888_img.jpg b/marked/Rel-16/23_series/23280/677bcb564410628b8b966ad87b394888_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..81bc6b5d054955e5339f0e1aee2e9d085f3037f0 --- /dev/null +++ b/marked/Rel-16/23_series/23280/677bcb564410628b8b966ad87b394888_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e5f9e095debf860688f46c2113a6dae217561b0982e4acf00b57e3ab96364fa5 +size 25937 diff --git a/marked/Rel-16/23_series/23280/67c232883c119b120d2fb337bf588e05_img.jpg b/marked/Rel-16/23_series/23280/67c232883c119b120d2fb337bf588e05_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e84bd66b7306a894dfe9b3dc8c34471ff850d26e --- /dev/null +++ b/marked/Rel-16/23_series/23280/67c232883c119b120d2fb337bf588e05_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b9aa64e2410af6e33df05f876c45599b26544000e57bb4e7fe0217f32f123365 +size 17416 diff --git a/marked/Rel-16/23_series/23280/6a993bfdf2e00cfad01c4d2188a75d86_img.jpg b/marked/Rel-16/23_series/23280/6a993bfdf2e00cfad01c4d2188a75d86_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6a108a33148dfba9560e2e17d87d7f4e3b280850 --- /dev/null +++ b/marked/Rel-16/23_series/23280/6a993bfdf2e00cfad01c4d2188a75d86_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a230f00628822686ab383d0dce13374b322594c3f2b70b6b3f789f67d9e833b0 +size 52907 diff --git a/marked/Rel-16/23_series/23280/6e0ac4070edc6a056713e6f0a3222db5_img.jpg b/marked/Rel-16/23_series/23280/6e0ac4070edc6a056713e6f0a3222db5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dbc3e57dad8ff0bf44fbf77bf2abb03bd3044c5c --- /dev/null +++ b/marked/Rel-16/23_series/23280/6e0ac4070edc6a056713e6f0a3222db5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d16fa9d70b263b7e77bccb012d16dbe2bd5ef18adbf6af571425bc9f208e9634 +size 21269 diff --git a/marked/Rel-16/23_series/23280/6e612452d995bb03cc3f3d004493f7bf_img.jpg b/marked/Rel-16/23_series/23280/6e612452d995bb03cc3f3d004493f7bf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a1a7b3d20cbce0e72c41c7a95021aed6d39aa7f9 --- /dev/null +++ b/marked/Rel-16/23_series/23280/6e612452d995bb03cc3f3d004493f7bf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:44d2e775a38bfabf71f68d2fa1a0950f323aff398bd5f05d2279c9c531f197b1 +size 46969 diff --git a/marked/Rel-16/23_series/23280/708e4c9a044ef61f586126676eb2eeb8_img.jpg b/marked/Rel-16/23_series/23280/708e4c9a044ef61f586126676eb2eeb8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..11b2a5e0c3e9cad5faf75465f4da241ca285a0fc --- /dev/null +++ b/marked/Rel-16/23_series/23280/708e4c9a044ef61f586126676eb2eeb8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3aa339d4dc95b647076f03b2e995bf07037f4537a9d226290f625790b7766e22 +size 52849 diff --git a/marked/Rel-16/23_series/23280/719ef0f734259484038b2434e5dc3f24_img.jpg b/marked/Rel-16/23_series/23280/719ef0f734259484038b2434e5dc3f24_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..af3ded0d392369cc52069aa45f68a8e0b0a42197 --- /dev/null +++ b/marked/Rel-16/23_series/23280/719ef0f734259484038b2434e5dc3f24_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:53747bce2b207c555bab44a40f4560aeb920f302f9624e6b7110942910064d71 +size 48407 diff --git a/marked/Rel-16/23_series/23280/73dff6b45b2b9ffd384bab3235f869af_img.jpg b/marked/Rel-16/23_series/23280/73dff6b45b2b9ffd384bab3235f869af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..332887a10a3a1fb72f0448a361d325e00382b2cc --- /dev/null +++ b/marked/Rel-16/23_series/23280/73dff6b45b2b9ffd384bab3235f869af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b3ce235bae7079fe24e942b4fc22604518b322442db39917cecf7d06d26931ed +size 49158 diff --git a/marked/Rel-16/23_series/23280/753e6cc5dcad1a478caa2c7ec3a6c0a3_img.jpg b/marked/Rel-16/23_series/23280/753e6cc5dcad1a478caa2c7ec3a6c0a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9944b90ffd538fc06e7cca108cd270c01432b008 --- /dev/null +++ b/marked/Rel-16/23_series/23280/753e6cc5dcad1a478caa2c7ec3a6c0a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6b7ddf45d0e1e62df514237e0037336a05b992af4240cff54ee5ecc8fd1c92e8 +size 40582 diff --git a/marked/Rel-16/23_series/23280/7722d62e33dcc894cc8555e9474c5606_img.jpg b/marked/Rel-16/23_series/23280/7722d62e33dcc894cc8555e9474c5606_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c3f0b1af17eef920bd1ae267940a3d2dd6c266fe --- /dev/null +++ b/marked/Rel-16/23_series/23280/7722d62e33dcc894cc8555e9474c5606_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:03ba3ffac9cb630b0b44f408a3ea59905e4fa92a466504094cb8b10355ffabc9 +size 41203 diff --git a/marked/Rel-16/23_series/23280/7c92fa3f1d1b465cc1d3c48a1a8728ff_img.jpg b/marked/Rel-16/23_series/23280/7c92fa3f1d1b465cc1d3c48a1a8728ff_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9e34afd84ef9e84ffbc2f0517491fd239bc535ba --- /dev/null +++ b/marked/Rel-16/23_series/23280/7c92fa3f1d1b465cc1d3c48a1a8728ff_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/23280/7ed5d5770331f31ade15439a21c31425_img.jpg b/marked/Rel-16/23_series/23280/7ed5d5770331f31ade15439a21c31425_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f3f862b7743effff0c4f5485821eaef6c867eb9a --- /dev/null +++ b/marked/Rel-16/23_series/23280/7ed5d5770331f31ade15439a21c31425_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:10ec071758cf62494deb775f9f59355cc2de074bed7cde19751945c35b98a059 +size 56947 diff --git a/marked/Rel-16/23_series/23280/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg b/marked/Rel-16/23_series/23280/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4d4d9f7363ad5e82e491494d640b005799e7bb2c --- /dev/null +++ b/marked/Rel-16/23_series/23280/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:40cff87b756b159d97fdd58b6343943e1ba6e83b2f3c947bd62c0e36ec40852a +size 74372 diff --git a/marked/Rel-16/23_series/23280/886963464425186f4a465fa8155d2a3c_img.jpg b/marked/Rel-16/23_series/23280/886963464425186f4a465fa8155d2a3c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bac746e00d5d0608d8d2274c6f1098cf32743ee3 --- /dev/null +++ b/marked/Rel-16/23_series/23280/886963464425186f4a465fa8155d2a3c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8823751aceaf71413fa77d5e7c37a67198a8183d2e08916f80c48d4328bf5d57 +size 63142 diff --git a/marked/Rel-16/23_series/23280/8d66c9c295023a1380f9986d3663bb1e_img.jpg b/marked/Rel-16/23_series/23280/8d66c9c295023a1380f9986d3663bb1e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f3677b89f9e2c017962063cfc913a18b6169713b --- /dev/null +++ b/marked/Rel-16/23_series/23280/8d66c9c295023a1380f9986d3663bb1e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:02534bc591c9b1d8fea1ecbbccfc292d26b7a39a7b114ab4ee3b6ff2561d7c71 +size 114215 diff --git a/marked/Rel-16/23_series/23280/8e80de0cac529b2c3775d677c5203133_img.jpg b/marked/Rel-16/23_series/23280/8e80de0cac529b2c3775d677c5203133_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6521fd4a73db26da10b582b36488b176bc2888f8 --- /dev/null +++ b/marked/Rel-16/23_series/23280/8e80de0cac529b2c3775d677c5203133_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d378f19b8bee4c6ae2158c6c050cf340e839ef487c56bad100ed13726f0691ba +size 27957 diff --git a/marked/Rel-16/23_series/23280/90df9788d66ecf65abf861caf76be5ca_img.jpg b/marked/Rel-16/23_series/23280/90df9788d66ecf65abf861caf76be5ca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f8e1e659410e7faf10c74ecf54387b6c9fce5b3e --- /dev/null +++ b/marked/Rel-16/23_series/23280/90df9788d66ecf65abf861caf76be5ca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c2814fbc5bebbaeb44ac0c895cb0b6b30b462a96249e97998fdc4c091e2f794b +size 15558 diff --git a/marked/Rel-16/23_series/23280/98e54d5540b2efe3e24af3cf936bc4ea_img.jpg b/marked/Rel-16/23_series/23280/98e54d5540b2efe3e24af3cf936bc4ea_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..600f4ea6a214e6e7a1c27dd35ddd5f448c5e8364 --- /dev/null +++ b/marked/Rel-16/23_series/23280/98e54d5540b2efe3e24af3cf936bc4ea_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a263c7e552c5ac7ab6124595e8a986e130d93b6c6e0b746c7c0b6086026ffc1b +size 62378 diff --git a/marked/Rel-16/23_series/23280/997233d405f0d4b89ddeb7683e047f66_img.jpg b/marked/Rel-16/23_series/23280/997233d405f0d4b89ddeb7683e047f66_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e1d6ed041237012e0ae0dfbb28d59ce6c237354b --- /dev/null +++ b/marked/Rel-16/23_series/23280/997233d405f0d4b89ddeb7683e047f66_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/23280/9b686adccf125267a013fa25721231a3_img.jpg b/marked/Rel-16/23_series/23280/9b686adccf125267a013fa25721231a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3894e5999a283a07da1006ec6a0a5f2c8fbdb1a2 --- /dev/null +++ b/marked/Rel-16/23_series/23280/9b686adccf125267a013fa25721231a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fc914991ce1c77d4b74666beb6b3c769d5159adec3e238adf877bf47cdd28c57 +size 77763 diff --git a/marked/Rel-16/23_series/23280/9c05ae298f897f405d4f0c72d98cb2c7_img.jpg b/marked/Rel-16/23_series/23280/9c05ae298f897f405d4f0c72d98cb2c7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..af80d3e800acd1e0d3bdbfba3aeb2c78a3253169 --- /dev/null +++ b/marked/Rel-16/23_series/23280/9c05ae298f897f405d4f0c72d98cb2c7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c896f70b219db23ff315324ee266e7fecc8f7d405e2f0ff73d282342891e1e34 +size 45906 diff --git a/marked/Rel-16/23_series/23280/9c1d3678db4a12d5864cb2a4def1135d_img.jpg b/marked/Rel-16/23_series/23280/9c1d3678db4a12d5864cb2a4def1135d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..df010b6f3836661f219e3a1f1a0ad7549307b79a --- /dev/null +++ b/marked/Rel-16/23_series/23280/9c1d3678db4a12d5864cb2a4def1135d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:27ea70b30634e51046c5d3f352b1bd292a1be49743bfbc5ea1f468e44daf5ebc +size 58136 diff --git a/marked/Rel-16/23_series/23280/9e8ebf03cae78f4f81b697548c2d7250_img.jpg b/marked/Rel-16/23_series/23280/9e8ebf03cae78f4f81b697548c2d7250_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c45904b681204b9cbe27840813a865ee9c3fc162 --- /dev/null +++ b/marked/Rel-16/23_series/23280/9e8ebf03cae78f4f81b697548c2d7250_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:68d31fbc7f61724534388d5f2c9ee1e859abdcfff1e18aab699b2e929982e6a0 +size 49180 diff --git a/marked/Rel-16/23_series/23280/9ed248b025d766251d58be10b01a1cc0_img.jpg b/marked/Rel-16/23_series/23280/9ed248b025d766251d58be10b01a1cc0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..00f889f62ddcdedc1e5b11d26ae799a0a04333d7 --- /dev/null +++ b/marked/Rel-16/23_series/23280/9ed248b025d766251d58be10b01a1cc0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:49fb28c2cf520faf9588fd67f0af759b9eb52bb18c0f63142b4fe3a82cda39b2 +size 43224 diff --git a/marked/Rel-16/23_series/23280/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg b/marked/Rel-16/23_series/23280/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..18da385d596fb5c2d366b21fa84a32ed97b00649 --- /dev/null +++ b/marked/Rel-16/23_series/23280/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:991166fea7eb2e64e79726f7ef8f155f306d7c16e9b998c88ef7786f9e2ee88a +size 45142 diff --git a/marked/Rel-16/23_series/23280/a0e8fe7862a6d7341faf5dac275277cc_img.jpg b/marked/Rel-16/23_series/23280/a0e8fe7862a6d7341faf5dac275277cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..89fec854aeaab60434d9bd3c262e35949201fed7 --- /dev/null +++ b/marked/Rel-16/23_series/23280/a0e8fe7862a6d7341faf5dac275277cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:503b384e7065cffa3c151d6e5146259898b4d75a982a87fefab073961a21929b +size 56021 diff --git a/marked/Rel-16/23_series/23280/a234352dfaccdc24745c88eef7724cc6_img.jpg b/marked/Rel-16/23_series/23280/a234352dfaccdc24745c88eef7724cc6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a15ff1907cafc8626176a5123178f8e2c7993154 --- /dev/null +++ b/marked/Rel-16/23_series/23280/a234352dfaccdc24745c88eef7724cc6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cdaf0c90a01184a3e53e029e21e969942236ad426ed6f26083a44fb0408815fe +size 21262 diff --git a/marked/Rel-16/23_series/23280/a27134bc3a3c899782febdd02b502240_img.jpg b/marked/Rel-16/23_series/23280/a27134bc3a3c899782febdd02b502240_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..58a32b7a7b89198d409b859ea90214cb8e683fa7 --- /dev/null +++ b/marked/Rel-16/23_series/23280/a27134bc3a3c899782febdd02b502240_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b99976a3be08994df49f4f4ac95edac1b440a3eebcb3ff044cd0606b79900009 +size 20169 diff --git a/marked/Rel-16/23_series/23280/a320e67b369bfde4a5fa360b100da55c_img.jpg b/marked/Rel-16/23_series/23280/a320e67b369bfde4a5fa360b100da55c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5e879c50a366f84fda579b4cf046ee0ce2ab1e59 --- /dev/null +++ b/marked/Rel-16/23_series/23280/a320e67b369bfde4a5fa360b100da55c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:958c5f42cf88987dca467d55062750569fd7662946dbf25707ae1c36dcfe7eb2 +size 61527 diff --git a/marked/Rel-16/23_series/23280/a623046e0b145f14b961518396f7c43e_img.jpg b/marked/Rel-16/23_series/23280/a623046e0b145f14b961518396f7c43e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e31d67c149bc7809f72f9bfb10fc86b6f7836431 --- /dev/null +++ b/marked/Rel-16/23_series/23280/a623046e0b145f14b961518396f7c43e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4d940f7ac23221eaeed24cae9d0603450a09541fa5573663ff99e7b011f96d83 +size 52190 diff --git a/marked/Rel-16/23_series/23280/a7721892ae499a78173ff3dfdc4e65a9_img.jpg b/marked/Rel-16/23_series/23280/a7721892ae499a78173ff3dfdc4e65a9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4c8488fa2fbf369c85c9848f33be977597ce2623 --- /dev/null +++ b/marked/Rel-16/23_series/23280/a7721892ae499a78173ff3dfdc4e65a9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f4e0a1cd2befe396f5e8648f82edf6b2dbcd19a9c04c8210356c1822c0091be5 +size 32313 diff --git a/marked/Rel-16/23_series/23280/a963ca41bde1669b18a4b783616f228b_img.jpg b/marked/Rel-16/23_series/23280/a963ca41bde1669b18a4b783616f228b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..49886f0335645c74f2366cd6e7e582f14c3e92be --- /dev/null +++ b/marked/Rel-16/23_series/23280/a963ca41bde1669b18a4b783616f228b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:98abec9cc83584626c1bcade4e32069d0edb4d1e872d8f778f886c27014381e4 +size 104932 diff --git a/marked/Rel-16/23_series/23280/ac31fdfebb9751f7f10416dfe33bc872_img.jpg b/marked/Rel-16/23_series/23280/ac31fdfebb9751f7f10416dfe33bc872_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a6bb839c249c0d22d0f8db3abfbb7084d5bdec06 --- /dev/null +++ b/marked/Rel-16/23_series/23280/ac31fdfebb9751f7f10416dfe33bc872_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:32f8963133f2dd10ef1a55b72093395a941872a2bdd50e327083916968ba4f7f +size 70792 diff --git a/marked/Rel-16/23_series/23280/ae0dd5533e0b7fd2db452b5e2fdf8e5b_img.jpg b/marked/Rel-16/23_series/23280/ae0dd5533e0b7fd2db452b5e2fdf8e5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b1a7ec3c13f9a805666d62fec1d33367f1287ce4 --- /dev/null +++ b/marked/Rel-16/23_series/23280/ae0dd5533e0b7fd2db452b5e2fdf8e5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a8c944d0ba3a102ad51c8c0b65ca0f4cdcd098ad11f032da5511e745477075ec +size 32314 diff --git a/marked/Rel-16/23_series/23280/b0666d7acc98c96f24d88c97bbd7cae7_img.jpg b/marked/Rel-16/23_series/23280/b0666d7acc98c96f24d88c97bbd7cae7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..00ba98e14d77783d7ed3bd183bf83033d9177d2a --- /dev/null +++ b/marked/Rel-16/23_series/23280/b0666d7acc98c96f24d88c97bbd7cae7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aec6cde8a6f6a2bd30cb7b8a12d0c6811002bcde5415250bc100210ada4f2563 +size 14884 diff --git a/marked/Rel-16/23_series/23280/b06a4c871dfd0ce034cf801519d0039a_img.jpg b/marked/Rel-16/23_series/23280/b06a4c871dfd0ce034cf801519d0039a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..02549a5051350f37e9821d2684de1aa1f0159fd6 --- /dev/null +++ b/marked/Rel-16/23_series/23280/b06a4c871dfd0ce034cf801519d0039a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0c3c027567b6f6e749377f78d85c2ba1419f59e09c3b809a50c0bb848bad434f +size 77332 diff --git a/marked/Rel-16/23_series/23280/b2ea162a0f53d5e0504b7d28346e0754_img.jpg b/marked/Rel-16/23_series/23280/b2ea162a0f53d5e0504b7d28346e0754_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..16493e48632df932941301aa975f82f41abea7bb --- /dev/null +++ b/marked/Rel-16/23_series/23280/b2ea162a0f53d5e0504b7d28346e0754_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b865e01d7364ebfc21df72bbf6b91c9d74b7e463392ac780ed99972760278124 +size 51807 diff --git a/marked/Rel-16/23_series/23280/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg b/marked/Rel-16/23_series/23280/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b1fb7a9464cface32f15562bf210601cce3d2033 --- /dev/null +++ b/marked/Rel-16/23_series/23280/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9511411902bcb084a41d164f804268bf287cffe33f30d646cd48ce5eb6a314db +size 85049 diff --git a/marked/Rel-16/23_series/23280/b4a7906eddfd40aaa750e19e56c94a8b_img.jpg b/marked/Rel-16/23_series/23280/b4a7906eddfd40aaa750e19e56c94a8b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..533cf80fcc46e00be3793423a729e22aa0ed9e1a --- /dev/null +++ b/marked/Rel-16/23_series/23280/b4a7906eddfd40aaa750e19e56c94a8b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0d7bb8b7716529121d27a4e59a1052e70ee8230a3acc2810fd24624fb3e6c558 +size 46376 diff --git a/marked/Rel-16/23_series/23280/b560268ea8f6526970f23f0da225b099_img.jpg b/marked/Rel-16/23_series/23280/b560268ea8f6526970f23f0da225b099_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8a053844094bf5bc3f621d865f5e7a025d380dac --- /dev/null +++ b/marked/Rel-16/23_series/23280/b560268ea8f6526970f23f0da225b099_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ab0e33a3b27d2b82a81d6cbdc6fadda47787c2c01db5516970917bd71c90692b +size 35715 diff --git a/marked/Rel-16/23_series/23280/b82b870697ef3993804c839b298c0f4f_img.jpg b/marked/Rel-16/23_series/23280/b82b870697ef3993804c839b298c0f4f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ac56be2d85b98a004484003ce1dcfd9a9fafb515 --- /dev/null +++ b/marked/Rel-16/23_series/23280/b82b870697ef3993804c839b298c0f4f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8678b062730ab8faa3cb2ca8f68a7b6b0a86d7b29e98e4809286caaed592a7e3 +size 39893 diff --git a/marked/Rel-16/23_series/23280/bb3063a33c89b248574f64b6d8dfc404_img.jpg b/marked/Rel-16/23_series/23280/bb3063a33c89b248574f64b6d8dfc404_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f00e1b3deeb23143dcd3840562900d22d550d9ec --- /dev/null +++ b/marked/Rel-16/23_series/23280/bb3063a33c89b248574f64b6d8dfc404_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2d628423f2df1174b64a00d48aa4562889c1a2f836fbd37838a27a107f5bf3bd +size 61630 diff --git a/marked/Rel-16/23_series/23280/bb3354f497635d15bef873577125c48d_img.jpg b/marked/Rel-16/23_series/23280/bb3354f497635d15bef873577125c48d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c9d7a41753ef1530951731b7cf5bfb4367ec3f9a --- /dev/null +++ b/marked/Rel-16/23_series/23280/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/23280/bccc028d0e75bc30c41528056f581545_img.jpg b/marked/Rel-16/23_series/23280/bccc028d0e75bc30c41528056f581545_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dce7b4c9cdfe3a3d969d893c144b56b937d2949a --- /dev/null +++ b/marked/Rel-16/23_series/23280/bccc028d0e75bc30c41528056f581545_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7865fce8a0d495d2904d86d17e7fc5b900dca2a82801c39d4d943b7a29154e7a +size 47195 diff --git a/marked/Rel-16/23_series/23280/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg b/marked/Rel-16/23_series/23280/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..93c72b91263675543c055230799dc81e51b6d748 --- /dev/null +++ b/marked/Rel-16/23_series/23280/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:51af32df56717253f82bc5a35b6ccae02b3fe244797b657b296aa6d71c5ed5c3 +size 75984 diff --git a/marked/Rel-16/23_series/23280/c07e21a8d65991db04263322f859c94f_img.jpg b/marked/Rel-16/23_series/23280/c07e21a8d65991db04263322f859c94f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64dba417d55247931ebc598529777d31a4131989 --- /dev/null +++ b/marked/Rel-16/23_series/23280/c07e21a8d65991db04263322f859c94f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3ce4b658ec74f87501cf084bb08d578051d57e44d971589872a21d24552a04df +size 77208 diff --git a/marked/Rel-16/23_series/23280/c0ca823603794512478906b302176bca_img.jpg b/marked/Rel-16/23_series/23280/c0ca823603794512478906b302176bca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6283e06731ac219acad6f5d64c86f98bee278ee5 --- /dev/null +++ b/marked/Rel-16/23_series/23280/c0ca823603794512478906b302176bca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8aacf62db5dc2f13b2aad8c741c8c86d4e514d30ebee92421eb6df6c79e7a224 +size 48987 diff --git a/marked/Rel-16/23_series/23280/c67407c82ad10179bcb338347ded4245_img.jpg b/marked/Rel-16/23_series/23280/c67407c82ad10179bcb338347ded4245_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bcb0d83cc1a110fcdad8ed4ffbc0017c47dc07b8 --- /dev/null +++ b/marked/Rel-16/23_series/23280/c67407c82ad10179bcb338347ded4245_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6edf80c18f34ca3249b7835f42440601969858577efd6d57d4f64143e7a9395b +size 29123 diff --git a/marked/Rel-16/23_series/23280/c8a01394092e8f1fbaf91c81d752d401_img.jpg b/marked/Rel-16/23_series/23280/c8a01394092e8f1fbaf91c81d752d401_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c7f771feb047d082204504b1cac83f1a38fbb196 --- /dev/null +++ b/marked/Rel-16/23_series/23280/c8a01394092e8f1fbaf91c81d752d401_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:36919c5435c8e0e081db85c154c2e58dd86df1660639c30545381c61673a94e7 +size 50370 diff --git a/marked/Rel-16/23_series/23280/cad89c017c9e7c1785bcd104fde4e737_img.jpg b/marked/Rel-16/23_series/23280/cad89c017c9e7c1785bcd104fde4e737_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ba57fc1fa842e380f663f8d52fac8fe8cec30cdc --- /dev/null +++ b/marked/Rel-16/23_series/23280/cad89c017c9e7c1785bcd104fde4e737_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c33eb6d0b672c6e37e96030ad8a48414bf612ef3dc8cec16e1fdefc9e17cbb30 +size 39827 diff --git a/marked/Rel-16/23_series/23280/cdc21bbfcba380e98ece42e5b8da50bb_img.jpg b/marked/Rel-16/23_series/23280/cdc21bbfcba380e98ece42e5b8da50bb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d96e9cfad1601d84ecca29c2848ed5515c6424d2 --- /dev/null +++ b/marked/Rel-16/23_series/23280/cdc21bbfcba380e98ece42e5b8da50bb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1df4e9b4878b9c640dc1ef7473500c571c33fcaabd72175d3174c85a547fe026 +size 17812 diff --git a/marked/Rel-16/23_series/23280/d0abac95583b52a3b35f74a215567334_img.jpg b/marked/Rel-16/23_series/23280/d0abac95583b52a3b35f74a215567334_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..424513831333a6484e3275ea31b0ce459e1f0c49 --- /dev/null +++ b/marked/Rel-16/23_series/23280/d0abac95583b52a3b35f74a215567334_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3c7cb8eea8227c5233eea326222c0827e1064137989fdb287b16878afc8cadfb +size 52360 diff --git a/marked/Rel-16/23_series/23280/d2417b04116c354deccb25d98a84a0fb_img.jpg b/marked/Rel-16/23_series/23280/d2417b04116c354deccb25d98a84a0fb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b2c643976294f371f9ad95aa232169af8cff48aa --- /dev/null +++ b/marked/Rel-16/23_series/23280/d2417b04116c354deccb25d98a84a0fb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3b69ce4adc8b1c398af77424f34fc3a00ce95c90a6afb23c15ad90d27887f349 +size 60132 diff --git a/marked/Rel-16/23_series/23280/d6c377ae3e619ff992bd3647dbf43593_img.jpg b/marked/Rel-16/23_series/23280/d6c377ae3e619ff992bd3647dbf43593_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d96cf59d3b0af813b9e0c14097b78f0c2f40eeed --- /dev/null +++ b/marked/Rel-16/23_series/23280/d6c377ae3e619ff992bd3647dbf43593_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4f0755c3e343c3b1e8e6b9a85bd03da2f9508b5b40013f09e3aec53cf89885ab +size 73051 diff --git a/marked/Rel-16/23_series/23280/db39acbd11df5eb7e79ab84562fb8f74_img.jpg b/marked/Rel-16/23_series/23280/db39acbd11df5eb7e79ab84562fb8f74_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fbb69036aed2224f64fae144446b2a20dca13284 --- /dev/null +++ b/marked/Rel-16/23_series/23280/db39acbd11df5eb7e79ab84562fb8f74_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c037423379d8687cca585465512f8584e3fcfb030104030ec14f9892377c5e7d +size 24143 diff --git a/marked/Rel-16/23_series/23280/dcc3de7b5b2ad8fbacf8f3c7b5b08aa3_img.jpg b/marked/Rel-16/23_series/23280/dcc3de7b5b2ad8fbacf8f3c7b5b08aa3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a9218ab68e4b58baf62d8e4e35ef7f326da9c99f --- /dev/null +++ b/marked/Rel-16/23_series/23280/dcc3de7b5b2ad8fbacf8f3c7b5b08aa3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b020c0ead3647302084655a94d4c754e5442df80baad777491d51530a52d852e +size 18106 diff --git a/marked/Rel-16/23_series/23280/dd5771673aececa53d42ece89218299d_img.jpg b/marked/Rel-16/23_series/23280/dd5771673aececa53d42ece89218299d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..be06e45b78f78a46807b3edd61d31570ba5715cb --- /dev/null +++ b/marked/Rel-16/23_series/23280/dd5771673aececa53d42ece89218299d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dad4dca1e8c5580f33daeb76bf488f06558463bfdcab012d98f91bc5d616e448 +size 152594 diff --git a/marked/Rel-16/23_series/23280/e05b36c0d46549e681ce6581422c66b2_img.jpg b/marked/Rel-16/23_series/23280/e05b36c0d46549e681ce6581422c66b2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..384db88321b02f996f716033ac4525a3ad825370 --- /dev/null +++ b/marked/Rel-16/23_series/23280/e05b36c0d46549e681ce6581422c66b2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1a7b0b26cc8c39bbe03f6996da09f314e5947c84ce4b9f92c529f5e4d5533c47 +size 96550 diff --git a/marked/Rel-16/23_series/23280/e16bfa31d748f4d99ec4ae3d16656926_img.jpg b/marked/Rel-16/23_series/23280/e16bfa31d748f4d99ec4ae3d16656926_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..87f88a1a1daece552902983e27257f8261a3dac2 --- /dev/null +++ b/marked/Rel-16/23_series/23280/e16bfa31d748f4d99ec4ae3d16656926_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:742018988a259c6d452c77918347f4bc2595777b3bb44a59cf5d139cf1ee834e +size 55934 diff --git a/marked/Rel-16/23_series/23280/e5293502d8d5885d71defe1150aa12fc_img.jpg b/marked/Rel-16/23_series/23280/e5293502d8d5885d71defe1150aa12fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..57398a2b86a24ba6d978162daebd4be549ce80e4 --- /dev/null +++ b/marked/Rel-16/23_series/23280/e5293502d8d5885d71defe1150aa12fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:19c1b082ae32c14dc46bda27334630398d1d35f16e004d5ce46143045fc75fda +size 51652 diff --git a/marked/Rel-16/23_series/23280/e672f1afe3bbf9f8344379c41ec08bd6_img.jpg b/marked/Rel-16/23_series/23280/e672f1afe3bbf9f8344379c41ec08bd6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9d0eed2f8e3de0a7db3db87a9492402f286b2610 --- /dev/null +++ b/marked/Rel-16/23_series/23280/e672f1afe3bbf9f8344379c41ec08bd6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c5f41447a184f18671c91bff250b3dce109fe3b774b609a4db1467870a882c8e +size 17710 diff --git a/marked/Rel-16/23_series/23280/e7010c66da16316c2935dfbbef5056b3_img.jpg b/marked/Rel-16/23_series/23280/e7010c66da16316c2935dfbbef5056b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fb2fcc11e67ea16968c9fedf1cab2e7273647d8e --- /dev/null +++ b/marked/Rel-16/23_series/23280/e7010c66da16316c2935dfbbef5056b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d6dbaa9a0695033ead9085be55a52a6d1b4ae900efcac0448ab70801c74fc872 +size 47084 diff --git a/marked/Rel-16/23_series/23280/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg b/marked/Rel-16/23_series/23280/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a568c4d2750d9e58f5e9239d453c760a27d6a167 --- /dev/null +++ b/marked/Rel-16/23_series/23280/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:535e10d90f0f9e2aa3ff4b02ee80202b9949c3ffdd1ee7634a4b0926c6f14599 +size 48799 diff --git a/marked/Rel-16/23_series/23280/e928f4874ed492d3ad4c6fa2d29aedbc_img.jpg b/marked/Rel-16/23_series/23280/e928f4874ed492d3ad4c6fa2d29aedbc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2246f80608dc0e824ccf63dfc3ac2f116c13494a --- /dev/null +++ b/marked/Rel-16/23_series/23280/e928f4874ed492d3ad4c6fa2d29aedbc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1420a346d9c74026134fc57073389af9f3f9486d33e1ef9be9d67ec4fb01dd17 +size 82881 diff --git a/marked/Rel-16/23_series/23280/ebbf932a7c39555fbb003c4502fb90ed_img.jpg b/marked/Rel-16/23_series/23280/ebbf932a7c39555fbb003c4502fb90ed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f2fe2e73d985cbb3a70732c763e139236e32d410 --- /dev/null +++ b/marked/Rel-16/23_series/23280/ebbf932a7c39555fbb003c4502fb90ed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ba69f222a752bfaf307bc1ea9162e7d32287451912ea601fcc4cb428acd3e767 +size 24196 diff --git a/marked/Rel-16/23_series/23280/ee26f1d7de8a2de730e2e81a30b819a7_img.jpg b/marked/Rel-16/23_series/23280/ee26f1d7de8a2de730e2e81a30b819a7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..edff4aad80f063cd4f2552afe596faae3dc8ab04 --- /dev/null +++ b/marked/Rel-16/23_series/23280/ee26f1d7de8a2de730e2e81a30b819a7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0f68d0b681ef8c073db6e43315a765d66789aceb91272b2060ffd3f1983d0547 +size 19728 diff --git a/marked/Rel-16/23_series/23280/ef5f5c6665b6ae13660ede412333ba45_img.jpg b/marked/Rel-16/23_series/23280/ef5f5c6665b6ae13660ede412333ba45_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d9d02238d34d24da4ef06e7460adb153edbedca0 --- /dev/null +++ b/marked/Rel-16/23_series/23280/ef5f5c6665b6ae13660ede412333ba45_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1737eb43e97dd8678fd8d4573b9cd16d5daa90d908bf8577c4030f2c0d5f1c8c +size 38039 diff --git a/marked/Rel-16/23_series/23280/f0bae10b54c4f3cf8d0e33f5e2fb7cfa_img.jpg b/marked/Rel-16/23_series/23280/f0bae10b54c4f3cf8d0e33f5e2fb7cfa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0a8a7f247247afc3b631bd19f43621fb9abd16fc --- /dev/null +++ b/marked/Rel-16/23_series/23280/f0bae10b54c4f3cf8d0e33f5e2fb7cfa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5eb249d75a5e08efba6530edb11c8a27bee042e08837830a3a922b2ad1f99710 +size 28689 diff --git a/marked/Rel-16/23_series/23280/f2ea0f64a770b22b902820457d262265_img.jpg b/marked/Rel-16/23_series/23280/f2ea0f64a770b22b902820457d262265_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..39d24597295791f219de6c63e674fb8de825fdf4 --- /dev/null +++ b/marked/Rel-16/23_series/23280/f2ea0f64a770b22b902820457d262265_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d6e63ab4fe487525fd27a82e18b7e955ba5b61022a10cf08e5c3be830ae0989f +size 51539 diff --git a/marked/Rel-16/23_series/23280/f5d4c136ae38b454ba9212fa9b37193c_img.jpg b/marked/Rel-16/23_series/23280/f5d4c136ae38b454ba9212fa9b37193c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dcd04d39eebcbf38f211972370c41bef4aa4563b --- /dev/null +++ b/marked/Rel-16/23_series/23280/f5d4c136ae38b454ba9212fa9b37193c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:65db1fc1c623063a68b8371d3075cd533d8515664487f09d4ab60ca30b8eb34f +size 53217 diff --git a/marked/Rel-16/23_series/23280/f5e131a3fffe09aa98db055df84e4378_img.jpg b/marked/Rel-16/23_series/23280/f5e131a3fffe09aa98db055df84e4378_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e23d253b019c845ba67a2f93cb4fa5f3bba9a77c --- /dev/null +++ b/marked/Rel-16/23_series/23280/f5e131a3fffe09aa98db055df84e4378_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8dd87d3f38dc6c420a142b75d9b2cb89d576c215ec70e6f8b74163e14cfcdb50 +size 26138 diff --git a/marked/Rel-16/23_series/23280/fc3e2b49a9f850951570e502393b697f_img.jpg b/marked/Rel-16/23_series/23280/fc3e2b49a9f850951570e502393b697f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..26836bc9c8314086cad5535623ddc1a2dbf4fb0b --- /dev/null +++ b/marked/Rel-16/23_series/23280/fc3e2b49a9f850951570e502393b697f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9719f5492ea5777510e4008c4b46069af964b9d52c8e0ca0e31f7f388be41572 +size 33303 diff --git a/marked/Rel-16/23_series/23280/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/marked/Rel-16/23_series/23280/ff0952ef692c9d960ce5f6708bcc9711_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..625be32a14698e50b30de0bd998767bd082ce917 --- /dev/null +++ b/marked/Rel-16/23_series/23280/ff0952ef692c9d960ce5f6708bcc9711_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a9f05d152e0b0dd0175e9753727def82d0d935fd691389784d9e6120e8110c66 +size 88774 diff --git a/marked/Rel-16/23_series/23280/ff3417b75213b8688e6504a21220b430_img.jpg b/marked/Rel-16/23_series/23280/ff3417b75213b8688e6504a21220b430_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b174b4df0ede33d35768adbf0b3a3d7105bfdf9e --- /dev/null +++ b/marked/Rel-16/23_series/23280/ff3417b75213b8688e6504a21220b430_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e99cc2d86eaa889aa1a1fd1e69be92872d8f8bcfd4d4b363d7e1c4b21d4310f4 +size 89089 diff --git a/marked/Rel-16/23_series/23280/raw.md b/marked/Rel-16/23_series/23280/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..f737e8e8be71cb6b146ab1178ced4812e84880b6 --- /dev/null +++ b/marked/Rel-16/23_series/23280/raw.md @@ -0,0 +1,8819 @@ +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..... | 19 | +| 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..... | 21 | +| 5.2.7.0 General..... | 21 | +| 5.2.7.1 MBMS bearer management ..... | 21 | +| 5.2.7.2 EPS bearer considerations ..... | 22 | +| 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 ..... | 24 | +| 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 (CMS) ..... | 32 | +| 7.4.2.2.3 Group management client ..... | 32 | +| 7.4.2.2.4 Group management server (GMS) ..... | 32 | +| 7.4.2.2.5 Identity management client..... | 32 | +| 7.4.2.2.6 Identity management server (IdMS) ..... | 32 | +| 7.4.2.2.7 Key management client..... | 33 | + +| | | | +|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------|----| +| 7.4.2.2.8 | Key management server (KMS)..... | 33 | +| 7.4.2.2.9 | Location management client ..... | 33 | +| 7.4.2.2.10 | Location management server (LMS)..... | 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..... | 34 | +| 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 ..... | 36 | +| 7.4.3.2.1 | General ..... | 36 | +| 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..... | 38 | +| 7.5.2.1 | General..... | 38 | +| 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) ..... | 39 | +| 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) ..... | 40 | +| 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) ..... | 41 | +| 7.5.2.19 | Reference point MCX-1 (between MC service servers)..... | 42 | +| 7.5.2.20 | Reference point CSC-19 (between group management server and MC gateway server) ..... | 42 | +| 7.5.2.21 | Reference point CSC-20 (between configuration management server and MC gateway server) ..... | 42 | +| 7.5.2.22 | Reference point CSC-21 (between MC gateway servers in different MC systems)..... | 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)..... | 43 | +| 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)..... | 44 | +| 7.5.3.9 | Reference point AAA-2 (between the SIP core and Diameter proxy)..... | 44 | +| 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)..... | 45 | +| 8.1.3.1 | General..... | 45 | +| 8.1.3.2 | MC service group ID management (off-network operation)..... | 45 | +| 8.1.4 | MC system identity (MC system ID)..... | 46 | +| 8.2 | SIP signalling control plane..... | 46 | +| 8.3 | Relationship between identities in different planes..... | 47 | +| 8.3.1 | Relationship between MC service ID and public user identity..... | 47 | +| 8.3.2 | Relationship between MC service group ID and public service identity..... | 47 | +| 9 | Application of functional model to deployments..... | 48 | +| 9.1 | General..... | 48 | +| 9.2 | Architecture model and deployment scenarios for on-network operations..... | 48 | +| 9.2.1 | On-network architectural model..... | 48 | +| 9.2.1.1 | On-network architectural model diagram..... | 48 | +| 9.2.1.2 | Application services layer..... | 49 | +| 9.2.1.2.1 | Overview..... | 49 | +| 9.2.1.2.2 | Common services core..... | 49 | +| 9.2.1.2.3 | MC services..... | 49 | +| 9.2.1.3 | SIP core..... | 50 | +| 9.2.1.4 | EPS..... | 50 | +| 9.2.1.5 | UE 1..... | 50 | +| 9.2.1.6 | UE 2..... | 50 | +| 9.2.2 | Deployment scenarios..... | 50 | +| 9.2.2.1 | Administration of MC service, SIP core and EPS..... | 50 | +| 9.2.2.1.1 | General..... | 50 | +| 9.2.2.1.2 | Common administration of all planes..... | 50 | +| 9.2.2.1.3 | MC service provider separate from SIP core and EPS..... | 51 | +| 9.2.2.1.4 | MC service provider administers SIP core, separate from EPS..... | 52 | +| 9.2.2.1.5 | SIP core partially administered by both PLMN operator and MC service provider..... | 52 | +| 9.2.2.1.6 | PLMN operator administers SIP core with SIP identities administered by MC service provider..... | 53 | +| 9.2.2.2 | MC service user database, SIP database and HSS..... | 54 | +| 9.2.2.3 | Control of bearers by SIP core and MC service server..... | 57 | +| 9.2.2.3.1 | General..... | 57 | +| 9.2.2.3.2 | Control of bearers by SIP core..... | 57 | +| 9.2.2.3.3 | Control of bearers by MC service server..... | 57 | +| 9.3 | Architecture model for off-network operations..... | 58 | +| 9.3.1 | Off-network architectural model diagram..... | 58 | +| 9.3.2 | UE 3..... | 58 | +| 9.3.3 | UE 4..... | 59 | +| 9.3.4 | Offline common services server..... | 59 | +| 9.4 | Architecture model for roaming..... | 59 | +| 10 | Procedures and information flows..... | 59 | +| 10.1 | MC service configuration..... | 59 | +| 10.1.1 | General..... | 59 | +| 10.1.1.1 | MC service configuration on primary MC system..... | 59 | +| 10.1.1.2 | MC service configuration for migration to partner MC system..... | 61 | + +| | | | +|--------------|---------------------------------------------------------------------------------------------------|----| +| 10.1.2 | Information flows for MC service configuration ..... | 62 | +| 10.1.2.1 | Store group configuration request..... | 62 | +| 10.1.2.2 | Store group configuration response ..... | 62 | +| 10.1.2.3 | Get group configuration request ..... | 62 | +| 10.1.2.4 | Get group configuration response..... | 63 | +| 10.1.2.5 | Subscribe group configuration request ..... | 63 | +| 10.1.2.6 | Subscribe group configuration response..... | 63 | +| 10.1.2.7 | Notify group configuration request..... | 63 | +| 10.1.2.8 | Notify group configuration response ..... | 64 | +| 10.1.2.9 | Get functional alias configuration request ..... | 64 | +| 10.1.2.10 | Get functional alias configuration response..... | 64 | +| 10.1.2.11 | Subscribe functional alias configuration request ..... | 64 | +| 10.1.2.12 | Subscribe functional alias configuration response..... | 65 | +| 10.1.2.13 | Notify functional alias configuration request ..... | 65 | +| 10.1.2.14 | Notify functional alias configuration response ..... | 65 | +| 10.1.2.15 | MC service emergency alert request..... | 65 | +| 10.1.2.16 | MC service emergency alert response ..... | 66 | +| 10.1.2.17 | MC service emergency alert cancel request ..... | 66 | +| 10.1.2.18 | MC service emergency alert cancel response ..... | 67 | +| 10.1.2.19 | MC service emergency alert area notification ..... | 67 | +| 10.1.2.20 | MC service emergency alert announcement..... | 67 | +| 10.1.2.21 | MC service emergency alert cancel announcement..... | 68 | +| 10.1.3 | MC service UE configuration data ..... | 68 | +| 10.1.3.1 | General..... | 68 | +| 10.1.3.2 | Procedures..... | 68 | +| 10.1.3.3 | Structure of UE configuration data ..... | 69 | +| 10.1.4 | MC service user profile ..... | 69 | +| 10.1.4.1 | General..... | 69 | +| 10.1.4.2 | Information flows for MC service user profile ..... | 70 | +| 10.1.4.2.1 | Get MC service user profile request..... | 70 | +| 10.1.4.2.2 | Get MC service user profile response ..... | 70 | +| 10.1.4.2.3 | Notification for MC service user profile data update..... | 70 | +| 10.1.4.2.4 | Get updated MC service user profile data request ..... | 71 | +| 10.1.4.2.5 | Get updated MC service user profile data response ..... | 71 | +| 10.1.4.2.6 | Update MC service user profile data request ..... | 71 | +| 10.1.4.2.7 | Update MC service user profile data response..... | 71 | +| 10.1.4.2.8 | Update pre-selected MC service user profile request..... | 71 | +| 10.1.4.2.9 | Update pre-selected MC service user profile response ..... | 72 | +| 10.1.4.2.10 | Update selected MC service user profile request..... | 72 | +| 10.1.4.2.11 | Update selected MC service user profile response..... | 72 | +| 10.1.4.3 | MC service user obtains the MC service user profile(s) from the network ..... | 73 | +| 10.1.4.3.1 | MC service user receiving MC service in primary MC system ..... | 73 | +| 10.1.4.3.2 | MC service user receiving MC service from a partner MC system ..... | 73 | +| 10.1.4.4 | MC service user receives updated MC service user profile data from the network ..... | 75 | +| 10.1.4.5 | MC service user updates MC service user profile data to the network ..... | 75 | +| 10.1.4.6 | Updating the pre-selected MC service user profile ..... | 76 | +| 10.1.4.7 | Updating the selected MC service user profile for an MC service ..... | 77 | +| 10.1.5 | MC service group configuration management ..... | 79 | +| 10.1.5.1 | Store group configurations at the group management server ..... | 79 | +| 10.1.5.2 | Retrieve group configurations at the group management client ..... | 79 | +| 10.1.5.3 | Subscription and notification for group configuration data ..... | 80 | +| 10.1.5.4 | Structure of group configuration data ..... | 81 | +| 10.1.5.5 | Dynamic data associated with a group ..... | 81 | +| 10.1.5.5.1 | Dynamic data associated with a group in MC service server ..... | 81 | +| 10.1.5.5.2 | Affiliation status in group management server ..... | 82 | +| 10.1.5.6 | Subscription and notification for dynamic data associated with a group ..... | 82 | +| 10.1.5.6.1 | Information flows for subscription and notification for dynamic data associated with a group..... | 82 | +| 10.1.5.6.1.1 | Subscribe group dynamic data request..... | 82 | +| 10.1.5.6.1.2 | Subscribe group dynamic data response..... | 82 | +| 10.1.5.6.1.3 | Notify group dynamic data request ..... | 83 | +| 10.1.5.6.1.4 | Notify group dynamic data response..... | 83 | +| 10.1.5.6.2 | Procedure for subscription and notification for dynamic data associated with a group ..... | 83 | + +| | | | +|------------|---------------------------------------------------------------------------------------------------------------------------------|-----| +| 10.1.5.6.3 | Procedure for subscription and notification for affiliation status associated with a group by the group management server ..... | 84 | +| 10.1.6 | MC service UE migration..... | 85 | +| 10.1.6.1 | MC service UE obtains migration connectivity information of partner MC system..... | 85 | +| 10.1.6.2 | Signalling plane registration for the MC service UE between the primary and the partner MC systems..... | 85 | +| 10.1.7 | Functional alias configuration management..... | 87 | +| 10.1.7.1 | Retrieve functional alias configurations from the functional alias management server ..... | 87 | +| 10.1.7.2 | Subscription and notification for functional alias configuration data..... | 88 | +| 10.2 | Group management (on-network) ..... | 89 | +| 10.2.1 | General ..... | 89 | +| 10.2.2 | Information flows for group management..... | 89 | +| 10.2.2.1 | Group creation request..... | 89 | +| 10.2.2.2 | Group creation response ..... | 89 | +| 10.2.2.3 | Group regroup request (group management client – group management server) ..... | 90 | +| 10.2.2.4 | Group regroup response (group management server – group management client)..... | 90 | +| 10.2.2.5 | Group regroup teardown request ..... | 90 | +| 10.2.2.6 | Group regroup teardown response..... | 90 | +| 10.2.2.7 | Group creation notify ..... | 91 | +| 10.2.2.8 | Group regroup notify ..... | 91 | +| 10.2.2.9 | Group regroup teardown notify ..... | 91 | +| 10.2.2.10 | Group regroup teardown notification ..... | 91 | +| 10.2.2.11 | Group regroup teardown notification response ..... | 91 | +| 10.2.2.12 | Group regroup request (group management server – group management server) ..... | 92 | +| 10.2.2.13 | Group regroup response (group management server – group management server)..... | 92 | +| 10.2.2.14 | Group regroup notification ..... | 92 | +| 10.2.2.15 | Group regroup notification response ..... | 92 | +| 10.2.2.16 | Group information query request..... | 93 | +| 10.2.2.17 | Group information query response ..... | 93 | +| 10.2.2.18 | Group membership update request ..... | 93 | +| 10.2.2.19 | Group membership update response..... | 93 | +| 10.2.2.20 | Group membership notification ..... | 94 | +| 10.2.2.21 | Group deletion request..... | 94 | +| 10.2.2.22 | Group deletion response ..... | 94 | +| 10.2.2.23 | Group deletion notification..... | 94 | +| 10.2.2.24 | Group information provision request..... | 95 | +| 10.2.2.25 | Group information provision response ..... | 95 | +| 10.2.2.26 | Group information request..... | 95 | +| 10.2.2.27 | Group information response ..... | 95 | +| 10.2.2.28 | Group information subscribe request..... | 96 | +| 10.2.2.29 | Group information subscribe response ..... | 96 | +| 10.2.2.30 | Group information notify request ..... | 96 | +| 10.2.2.31 | Group information notify response..... | 96 | +| 10.2.3 | Group creation ..... | 97 | +| 10.2.4 | Group regrouping ..... | 98 | +| 10.2.4.1 | Temporary group formation - group regrouping within an MC system ..... | 98 | +| 10.2.4.2 | Temporary group formation involving multiple MC systems ..... | 100 | +| 10.2.4.3 | Temporary group tear down involving multiple group host servers ..... | 102 | +| 10.2.4.4 | Group regroup rules ..... | 103 | +| 10.2.5 | Membership and affiliation list query ..... | 104 | +| 10.2.5.1 | General..... | 104 | +| 10.2.5.2 | Procedure ..... | 104 | +| 10.2.6 | Group membership ..... | 104 | +| 10.2.6.1 | Group membership notification ..... | 104 | +| 10.2.6.2 | Group membership update by authorized user ..... | 105 | +| 10.2.7 | Group configuration for interconnection..... | 106 | +| 10.2.7.1 | Overview..... | 106 | +| 10.2.7.2 | Primary MC system provides group configuration to the partner MC system..... | 107 | +| 10.2.7.3 | Partner MC system requests group configuration from the primary MC system..... | 108 | +| 10.2.7.4 | Partner MC system subscribes to group configuration..... | 109 | +| 10.2.7.5 | Primary MC system notifies group configuration ..... | 110 | +| 10.2.8 | Group deletion ..... | 111 | + +| | | | +|--------------|---------------------------------------------------------------------|-----| +| 10.3 | Pre-established session (on-network)..... | 112 | +| 10.3.1 | General ..... | 112 | +| 10.3.2 | Procedures ..... | 112 | +| 10.3.2.1 | General..... | 112 | +| 10.3.2.2 | Pre-established session establishment ..... | 112 | +| 10.3.2.3 | Pre-established session modification ..... | 113 | +| 10.3.2.4 | Pre-established session release ..... | 115 | +| 10.4 | Simultaneous session (on-network) ..... | 116 | +| 10.4.1 | General ..... | 116 | +| 10.5 | Use of UE-to-network relay ..... | 116 | +| 10.5.1 | UE-to-network relay service authorization..... | 116 | +| 10.5.2 | UE-to-network relay MC service ..... | 116 | +| 10.6 | General user authentication and authorization for MC services ..... | 116 | +| 10.6.1 | Primary MC system..... | 116 | +| 10.6.2 | Interconnection partner MC system ..... | 117 | +| 10.6.3 | Migration to partner MC system ..... | 117 | +| 10.6.3.1 | General..... | 117 | +| 10.6.3.2 | Information flows for migrated service authorization ..... | 118 | +| 10.6.3.2.1 | Migration service authorization request..... | 118 | +| 10.6.3.2.2 | Migration service authorization response ..... | 118 | +| 10.6.3.3 | Procedure ..... | 118 | +| 10.7 | Use of MBMS transmission..... | 120 | +| 10.7.1 | General ..... | 120 | +| 10.7.2 | Information flows for MBMS transmission ..... | 120 | +| 10.7.2.1 | MBMS bearer announcement ..... | 120 | +| 10.7.2.2 | MBMS listening status report..... | 121 | +| 10.7.2.3 | MBMS suspension reporting instruction ..... | 121 | +| 10.7.2.4 | Discover bearer request ..... | 122 | +| 10.7.2.5 | Discover bearer response ..... | 122 | +| 10.7.2.6 | Media distribution request ..... | 122 | +| 10.7.2.7 | Media distribution request response ..... | 123 | +| 10.7.2.8 | Identify multicast participants request..... | 123 | +| 10.7.2.9 | Remove call from bearer request..... | 123 | +| 10.7.2.10 | Media distribution release..... | 123 | +| 10.7.2.11 | Media broadcasting notification ..... | 123 | +| 10.7.2.12 | Group status notification..... | 123 | +| 10.7.3 | Procedures for MBMS usage..... | 124 | +| 10.7.3.1 | Use of pre-established MBMS bearers ..... | 124 | +| 10.7.3.1.1 | General ..... | 124 | +| 10.7.3.1.2 | Procedure..... | 124 | +| 10.7.3.2 | Use of dynamic MBMS bearer establishment ..... | 126 | +| 10.7.3.3 | Switching from MBMS bearer to unicast bearer ..... | 127 | +| 10.7.3.4 | Use of MBMS bearer for application level control signalling..... | 128 | +| 10.7.3.4.1 | Description ..... | 128 | +| 10.7.3.4.2 | Procedure..... | 128 | +| 10.7.3.5 | MBMS bearer announcement over MBMS bearer ..... | 129 | +| 10.7.3.5.1 | Description ..... | 129 | +| 10.7.3.5.2 | Procedure..... | 129 | +| 10.7.3.6 | MBMS bearer quality detection..... | 131 | +| 10.7.3.6.1 | Description ..... | 131 | +| 10.7.3.6.2 | Procedure..... | 131 | +| 10.7.3.7 | Service continuity in MBMS scenarios ..... | 132 | +| 10.7.3.7.1 | General ..... | 132 | +| 10.7.3.7.2 | Service continuity when moving from one MBSFN to another..... | 132 | +| 10.7.3.7.3 | Service continuity with a UE-to-Network relay..... | 135 | +| 10.7.3.8 | MBMS suspension notification ..... | 137 | +| 10.7.3.8.1 | Description ..... | 137 | +| 10.7.3.8.2 | Procedure..... | 137 | +| 10.7.3.9 | Multi-server bearer coordination ..... | 138 | +| 10.7.3.9.1 | General ..... | 138 | +| 10.7.3.9.2 | Procedures ..... | 138 | +| 10.7.3.9.2.1 | MBMS bearer coordination independent on broadcasted media..... | 138 | + +| | | | +|--------------|--------------------------------------------------------------------------------------------------------------------------------------------------|-----| +| 10.7.3.9.2.2 | MBMS bearer coordination within one group call..... | 140 | +| 10.7.3.10 | MBMS bearer event notification ..... | 142 | +| 10.7.3.10.1 | General ..... | 142 | +| 10.7.3.10.2 | Procedure..... | 143 | +| 10.7.3.11 | Use of FEC to protect MBMS transmissions..... | 144 | +| 10.7.3.11.1 | General ..... | 144 | +| 10.7.3.11.2 | FEC encoding by the BM-SC..... | 144 | +| 10.7.3.11.3 | FEC encoding by the MC service server..... | 145 | +| 10.7.3.12 | Header compression over MBMS with ROHC ..... | 146 | +| 10.7.3.12.1 | General ..... | 146 | +| 10.7.3.12.2 | Header compression by the MC service server..... | 146 | +| 10.7.3.12.3 | Header compression by the BM-SC..... | 147 | +| 10.7.3.13 | Use of MBMS bearer for group status ..... | 148 | +| 10.8 | Affiliation and de-affiliation to/from MC service group(s) ..... | 150 | +| 10.8.1 | General ..... | 150 | +| 10.8.2 | Information flows ..... | 150 | +| 10.8.2.1 | MC service group affiliation request..... | 150 | +| 10.8.2.2 | MC service group affiliation request (MC service server – MC service server)..... | 150 | +| 10.8.2.3 | MC service group affiliation response..... | 150 | +| 10.8.2.4 | MC service group affiliation response (MC service server – MC service server) ..... | 151 | +| 10.8.2.5 | Void ..... | 151 | +| 10.8.2.6 | MC service group de-affiliation request..... | 151 | +| 10.8.2.7 | MC service group de-affiliation request (MC service server – MC service server)..... | 151 | +| 10.8.2.8 | MC service group de-affiliation response..... | 151 | +| 10.8.2.9 | MC service group de-affiliation response (MC service server – MC service server) ..... | 152 | +| 10.8.2.10 | Void ..... | 152 | +| 10.8.2.11 | MC service group affiliation change request..... | 152 | +| 10.8.2.12 | MC service group affiliation change response ..... | 152 | +| 10.8.2.13 | MC service group de-affiliation notification ..... | 153 | +| 10.8.2.14 | Notify group dynamic data request..... | 153 | +| 10.8.3 | Affiliation ..... | 153 | +| 10.8.3.1 | MC service group affiliation procedure..... | 153 | +| 10.8.3.2 | Affiliation to MC service group(s) defined in partner MC system without topology hiding ..... | 154 | +| 10.8.3.2.1 | Functional description..... | 154 | +| 10.8.3.2.2 | Procedure..... | 155 | +| 10.8.3.2a | Affiliation to MC service group(s) defined in partner MC system using topology hiding ..... | 156 | +| 10.8.3.2a.1 | Functional description..... | 156 | +| 10.8.3.2a.2 | Procedure..... | 156 | +| 10.8.4 | De-affiliation from MC service group(s)..... | 158 | +| 10.8.4.1 | General ..... | 158 | +| 10.8.4.2 | MC service group de-affiliation procedure..... | 158 | +| 10.8.4.3 | De-affiliation from MC service group(s) defined in partner MC service system..... | 159 | +| 10.8.4.4 | MC server initiated group de-affiliation procedure ..... | 160 | +| 10.8.4.5 | MC server initiated group de-affiliation from group defined in partner MC service system..... | 161 | +| 10.8.5 | Remote change of affiliation ..... | 163 | +| 10.8.5.1 | Remote change of affiliation for groups defined in primary MC system..... | 163 | +| 10.8.5.1.1 | Authorized user remotely changes another MC service user's affiliated MC service group(s) –
mandatory mode..... | 163 | +| 10.8.5.1.2 | Authorized user remotely changes another MC service user's affiliated MC service group(s) –
negotiated mode ..... | 164 | +| 10.8.5.2 | Remote change of affiliation for groups defined in partner MC system ..... | 166 | +| 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 ..... | 166 | +| 10.9 | Location management (on-network) ..... | 168 | +| 10.9.1 | General ..... | 168 | +| 10.9.2 | Information flows for location information ..... | 168 | +| 10.9.2.1 | Location reporting configuration ..... | 168 | +| 10.9.2.2 | Location information report..... | 168 | +| 10.9.2.3 | Location information request..... | 169 | +| 10.9.2.4 | Location reporting trigger ..... | 169 | +| 10.9.2.5 | Location information subscription request ..... | 169 | +| 10.9.2.6 | Location information subscription response..... | 170 | + +| | | | +|-------------|-------------------------------------------------------------------------------|-----| +| 10.9.2.7 | Location information notification..... | 170 | +| 10.9.2.10 | Location report response..... | 171 | +| 10.9.3 | Procedure ..... | 171 | +| 10.9.3.1 | Event-triggered location reporting procedure..... | 171 | +| 10.9.3.2 | On-demand location reporting procedure ..... | 172 | +| 10.9.3.3 | Client-triggered location reporting procedure ..... | 173 | +| 10.9.3.4 | Location reporting cancel procedure ..... | 173 | +| 10.9.3.5 | Location information subscription procedure..... | 174 | +| 10.9.3.6 | Usage of location information procedure ..... | 174 | +| 10.9.3.6.1 | Event-trigger location information notification procedure ..... | 174 | +| 10.9.3.6.2 | On-demand usage of location information procedure..... | 175 | +| 10.9.3.8 | Location management using functional alias..... | 176 | +| 10.9.3.8.1 | Client-triggered one-time location information report..... | 176 | +| 10.9.3.8.2 | Client-triggered periodic location information report..... | 177 | +| 10.10 | Emergency Alert ..... | 179 | +| 10.10.1 | On-network emergency alert ..... | 179 | +| 10.10.1.1 | General ..... | 179 | +| 10.10.1.2 | MC service emergency alert ..... | 179 | +| 10.10.1.2.1 | MC service emergency alert initiation ..... | 179 | +| 10.10.1.2.2 | MC service emergency alert cancel ..... | 181 | +| 10.10.1.2.3 | Entering MC service emergency alert area ..... | 182 | +| 10.10.1.2.4 | Leaving MC service emergency alert area..... | 183 | +| 10.10.2 | Off-network emergency alert..... | 184 | +| 10.10.2.1 | General..... | 184 | +| 10.10.2.2 | MC service emergency alert ..... | 185 | +| 10.10.2.2.1 | Emergency alert initiation ..... | 185 | +| 10.10.2.2.2 | Emergency alert cancel ..... | 186 | +| 10.11 | MC service resource management (on-network) ..... | 187 | +| 10.11.1 | General ..... | 187 | +| 10.11.2 | Request for unicast resources at session establishment..... | 187 | +| 10.11.3 | Request for modification of unicast resources ..... | 188 | +| 10.11.4 | Management of multicast media bearers ..... | 189 | +| 10.11.5 | Request for resources with shared priority ..... | 190 | +| 10.11.5.1 | General ..... | 190 | +| 10.11.5.2 | Procedure ..... | 190 | +| 10.11.6 | Request for media resources from MC service server..... | 191 | +| 10.11.6.1 | General..... | 191 | +| 10.11.6.2 | Procedure ..... | 191 | +| 10.12 | Priority Management..... | 192 | +| 10.12.1 | General ..... | 192 | +| 10.12.2 | Information flows ..... | 193 | +| 10.12.2.1 | MC priority request..... | 193 | +| 10.12.3 | Procedure for priority coordination between multiple MC service servers ..... | 193 | +| 10.13 | Functional alias management (on-network)..... | 195 | +| 10.13.1 | General ..... | 195 | +| 10.13.2 | Information flows for functional alias management..... | 195 | +| 10.13.2.1 | Active functional alias information user query request..... | 195 | +| 10.13.2.1a | Active functional alias information usage query request..... | 195 | +| 10.13.2.2 | Active functional alias information user query response..... | 195 | +| 10.13.2.2a | Active functional alias information usage query response ..... | 196 | +| 10.13.2.3 | Functional alias activation request..... | 196 | +| 10.13.2.4 | Functional alias activation response ..... | 196 | +| 10.13.2.5 | Functional alias de-activation request..... | 197 | +| 10.13.2.6 | Functional alias de-activation response ..... | 197 | +| 10.13.2.7 | Functional alias status notification ..... | 197 | +| 10.13.2.8 | Functional alias take over request..... | 197 | +| 10.13.2.9 | Functional alias take over response ..... | 198 | +| 10.13.2.10 | Functional alias revoke notification..... | 198 | +| 10.13.2.11 | Subscribe functional alias request..... | 198 | +| 10.13.2.12 | Subscribe functional alias response ..... | 198 | +| 10.13.2.13 | Notify functional alias request..... | 199 | +| 10.13.2.14 | Notify functional alias response ..... | 199 | + +| | | | +|-----------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------|------------| +| 10.13.2.15 | Unsubscribe functional alias request ..... | 199 | +| 10.13.2.16 | Unsubscribe functional alias response ..... | 199 | +| 10.13.3 | Authorised MC service user retrieves active functional alias(es) for certain MC service user(s) ..... | 199 | +| 10.13.4 | MC service user activates functional alias(es) within an MC system ..... | 200 | +| 10.13.5 | MC service user de-activates functional alias(es) within an MC system ..... | 201 | +| 10.13.6 | Authorised MC service user takes over functional alias(es) within an MC system ..... | 202 | +| 10.13.7 | Authorised MC service user retrieves MC service user(s) for certain active functional alias(es) ..... | 203 | +| 10.13.10 | Subscription and notification for functional alias ..... | 206 | +| 10.13.10.1 | General ..... | 206 | +| 10.14 | Generic procedures for interconnection ..... | 208 | +| 10.14.1 | General ..... | 208 | +| 10.14.2 | Generic call procedure with topology hiding ..... | 208 | +| 10.14.2.1 | General ..... | 208 | +| 10.14.2.2 | Procedure for calls with topology hiding ..... | 208 | +| 10.14.3 | Generic call procedure for enforcement of local MC service group configuration ..... | 210 | +| 10.14.3.1 | General ..... | 210 | +| 10.14.3.2 | MC service group call initiated in the partner MC system of the MC service group ..... | 210 | +| 10.14.3.3 | MC service group call request received from the primary MC system of the MC service group ..... | 211 | +| 10.14.4 | Generic call procedure for media replication in participating MC system in MC service group calls ..... | 212 | +| 10.14.4.1 | General ..... | 212 | +| 10.14.4.2 | Media replication in the partner MC system of the MC service group ..... | 212 | +| Annex A (normative): Configuration data for MC services ..... | | 214 | +| A.1 | General ..... | 214 | +| A.2 | MC service UE configuration data ..... | 215 | +| A.3 | MC service user profile configuration data ..... | 215 | +| A.4 | Group configuration data ..... | 215 | +| A.5 | MC service configuration data ..... | 219 | +| A.6 | Initial MC service UE configuration data ..... | 219 | +| Annex B (informative): Service continuity for MC service ..... | | 221 | +| B.1 | Service continuity between on-network MC service and UE-to-network relay MC service ..... | 221 | +| Annex C (informative): Change history ..... | | 224 | + +--- + +## 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 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". +- [29] 3GPP TS 23.271: "Functional stage 2 description of Location Services (LCS)". + +--- + +## 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). + +**LCS network:** The 3GPP network that provides location service as defined in 3GPP TS 23.271 [29]. + +**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 | +| CMS | Configuration Management Server | +| 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 | +| GMS | Group Management Server | +| 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 | +| IdMS | Identity Management Server | +| IM CN | IP Multimedia Core Network | +| IMPI | IP Multimedia Private Identity | +| IMPU | IP Multimedia PUblic identity | +| IMS | IP Multimedia Subsystem | +| KMS | Key Management Server | +| LCS | Location Services | +| LMS | Location Management Server | +| 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 + +**MCData** +**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: + +- a) 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. + +- b) The MC service architecture should enable an application plane and signalling control plane split for the provisioning of the MC service. +- c) 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;). +- d) 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 1:** 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. When the MC service user is logged off from the MC service, all affiliations shall be revoked in the MC service server even if no explicit de-affiliation signalling is sent. + +Editor's note: The interaction of logoff and de-affiliation when moving to off network case is FFS. + +Editor's note: The consideration for revoking affiliations of a user logged on to multiple devices on the MC service server is FFS. + +Editor's note: The MC service server may track logoff state independent of affiliation and is FFS. + +NOTE 2: When the MC service user next performs successful service authorization, re-affiliation occurs in the MC service server without explicit affiliation signalling for all MC service groups that are configured for implicit affiliation after service authorization. + +NOTE 3: The MC service client may also store MC service groups to which the MC service user was affiliated prior to that user logging off, and may re-affiliate through an explicit affiliation to these groups following the next service authorization. Such a function is outside the scope of the present document. + +## 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: + + + +Figure 5.2.6-1: MC service on-network architecture showing MBMS. The diagram illustrates the architecture where a UE (User Equipment) containing an MC service client is connected to an E-UTRAN. The E-UTRAN is connected to an MC service server (shown bundled with GCS AS) via two paths: a Unicast path (labeled Rx) and an MBMS path (labeled MB2-C and MB2-U). The UE is also connected to the MC service server via a GC1 interface. The E-UTRAN is connected to the MC service server via an SGi interface. + +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 APNs 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 QCIs 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 APNs 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 APNs 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 APNs specified in subclause 5.2.7 that identify the PDNs of the partner MC system. + +NOTE 3: Provisioning of APNs 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. + + + +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. + + + +``` + +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: + +- a) use of identities. Each plane is therefore responsible for the privacy of that plane's own identities; and +- b) 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: + +- a) 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 +- b) 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. + + + +The diagram illustrates the functional model for the application plane of an MC system. It is organized into three main vertical sections: External Systems (left), Common Services Core (middle), and MC Service UE (right), separated by the EPS (Evolved Packet System). + +- External Systems (Left):** + - Other MC system:** Contains an **MC gateway server** connected to the EPS via reference point **MCX-1**. + - Other MC service server:** Connected to the EPS via reference point **MCX-1**. + - MC gateway server:** Connected to the EPS via reference point **CSC-21**. + - MC service user database(s):** Connected to the EPS via reference point **CSC-20**. + - Other group management server:** Connected to the EPS via reference point **CSC-19**. + - Group management server:** Connected to the EPS via reference point **CSC-16**. + - Configuration management server:** Connected to the EPS via reference point **CSC-17**. + - Migration management server:** Connected to the EPS via reference point **CSC-18**. +- Common Services Core (Middle):** A dashed box containing shared functions: + - MC service server(s):** Connected to the EPS via reference points **CSC-3** and **CSC-5**. + - Group management server:** Connected to the EPS via reference point **CSC-2**. + - Configuration management server:** Connected to the EPS via reference point **CSC-4**. + - Migration management server:** Connected to the EPS via reference point **CSC-10**. + - Identity management server:** Connected to the EPS via reference point **CSC-1**. + - Key management server:** Connected to the EPS via reference point **CSC-8**. + - Location management server:** Connected to the EPS via reference point **CSC-14**. +- MC Service UE (Right):** Contains client functions connected to the EPS: + - MC service client(s):** Connected to the EPS via reference point **CSC-3**. + - Group management client:** Connected to the EPS via reference point **CSC-2**. + - Configuration management client:** Connected to the EPS via reference point **CSC-4**. + - Identity management client:** Connected to the EPS via reference point **CSC-1**. + - Key management client:** Connected to the EPS via reference point **CSC-8**. + - Location management client:** Connected to the EPS via reference point **CSC-14**. + +The EPS is represented by a vertical double line separating the Common Services Core from the MC Service UE. Reference points **CSC-7** and **CSC-9** are also indicated within the Common Services Core area. + +Functional model for application plane for an MC system diagram + +**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. + +Figure 7.3.1-2 shows the functional model for the signalling control plane. + + + +The diagram illustrates the functional model for the signalling control plane. It features several interconnected components: + +- Other MC system:** Contains a **SIP core** and an **HTTP proxy**. + - The **SIP core** connects to the **Registrar finder/I-CSCF** via **SIP-3**. + - The **HTTP proxy** connects to the central **HTTP Proxy** via **HTTP-3**. +- SIP database:** Connects to the **Registrar finder/I-CSCF** via **AAA-1**. +- 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** and to the **Registrar-AS selection/S-CSCF** via **AAA-2**. + - The **HTTP server** connects to the central **HTTP Proxy** via **HTTP-2**. + - The **HTTP client** connects to the central **HTTP Proxy** via **HTTP-1**. +- Common services core:** Contains a **SIP AS**, an **HTTP server**, an **HTTP client**, and a **Diameter proxy**. + - The **SIP AS** connects to the central **HTTP Proxy** via **HTTP-2**. + - The **HTTP server** connects to the central **HTTP Proxy** via **HTTP-2**. + - The **HTTP client** connects to the central **HTTP Proxy** via **HTTP-1**. + - The **Diameter proxy** connects to the **Registrar-AS selection/S-CSCF**. +- SIP core (Central):** Contains a **Registrar finder/I-CSCF** and a **Registrar-AS selection/S-CSCF**. + - The **Registrar finder/I-CSCF** connects to a **Local proxy/P-CSCF**. + - The **Registrar-AS selection/S-CSCF** connects to the **Local proxy/P-CSCF** via **SIP-1** and to the **MC service UE** via **Rx**. + - Both components have an outgoing connection labeled **SIP-3** "To other SIP core". +- Local proxy/P-CSCF:** Connects to the **MC service UE** via **SIP-1**. +- MC service UE:** Contains a **Signalling user agent** and an **HTTP client**. + - The **Signalling user agent** connects to the **Local proxy/P-CSCF** via **SIP-1**. + - The **HTTP client** connects to the central **HTTP Proxy** via **HTTP-1**. +- Central HTTP Proxy:** Connects to the **Other MC system HTTP proxy** via **HTTP-3** and to "other HTTP Proxy" via **HTTP-3**. +- EPS:** A vertical bar representing the Evolved Packet System, situated between the **Local proxy/P-CSCF** and the **MC service UE**. + +Functional model for signalling control plane diagram showing various network components and their interconnections. + +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. + + + +The diagram illustrates the interconnections between MC service application plane components and signalling control planes. It features two main sections of servers on the left and clients on the right, both interfacing with central SIP cores. + +- Top Section:** + - An **MC service server** connects to an **SIP core** via **SIP-2**. It also has internal reference points **HTTP-1**, **HTTP-2**, and **CSC-3**. + - A **Group management server** connects to the same **SIP core** via **SIP-2**. + - A **Migration management server** connects to the **SIP core** via **SIP-3**. It is associated with **AAA-2** and **CSC-18**. +- Bottom Section:** + - An **MC service server** connects to a second **SIP core** via **SIP-2**. It includes reference points **HTTP-1**, **HTTP-2**, **CSC-3**, and **CSC-5**. + - A **Group management server** connects to the second **SIP core** via **SIP-2**. It includes reference points **HTTP-1**, **HTTP-2**, **HTTP-3**, **CSC-7**, and **CSC-10**. + - A **Configuration management server** connects to the second **SIP core** via **SIP-2**. It includes reference points **HTTP-1**, **CSC-9**, and **CSC-15**. + - A **Key management server** connects to the second **SIP core** via **SIP-2**. It includes reference points **HTTP-1**, **HTTP-2**, **CSC-9**, and **CSC-15**. + - A **Location management server** connects to the second **SIP core** via **SIP-2**. It includes reference points **HTTP-1**, **HTTP-2**, **CSC-15**, and **CSC-18**. + - A second **Migration management server** connects to the second **SIP core** via **SIP-3**. It is associated with **AAA-2** and **CSC-18**. +- Clients on the Right:** + - An **MC service client** connects to the second **SIP core** via **SIP-1**. + - A **Group management client** connects to the second **SIP core** via **SIP-1**. It is associated with **CSC-2**. + - A **Configuration management client** connects to the second **SIP core** via **SIP-1**. It is associated with **CSC-4**. + - A **Key management client** connects to the second **SIP core** via **SIP-1**. It is associated with **CSC-8**. + - A **Location management client** connects to the second **SIP core** via **SIP-1**. It is associated with **CSC-14**. +- Internal Connections:** Various **HTTP-1**, **HTTP-2**, and **HTTP-3** reference points are shown between servers and the SIP cores, indicating internal signalling paths. + +A complex architectural diagram showing relationships between 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) through 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'. + +**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 (CMS) + +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 (GMS) + +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 (IdMS) + +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 (KMS) + +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 (LMS) + +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 (e.g. LCS network). + +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, take over and interrogation. 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 different MC service servers are contained in 3GPP TS 23.379 [16], 3GPP TS 23.281 [12] and 3GPP TS 23.282 [13]. + +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 the same security domain. 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. + +The CSC-16 reference point uses the HTTP-1, HTTP-2 and HTTP-3 reference points for transport and routing of non-subscription/notification related signalling. + +#### 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. + +The CSC-17 reference point uses the HTTP-1, HTTP-2 and HTTP-3 reference points for transport and routing of non-subscription/notification related signalling. + +#### 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.2.20 Reference point CSC-19 (between group management server and MC gateway server) + +The CSC-19 reference point, which exists between the group management server and MC gateway server is used by the group management server for subscription and notification signalling related to group configuration information that is shared between MC systems to permit interconnection of MC service group calls. + +The CSC-19 reference point uses the SIP-2 and SIP-3 reference points for transport and routing of subscription/notification related signalling. + +#### 7.5.2.21 Reference point CSC-20 (between configuration management server and MC gateway server) + +The CSC-20 reference point, which exists between configuration management server and MC gateway server is used by the configuration management server for subscription and notification signalling related to user configuration information that is shared between MC systems to permit migration between MC systems. + +The CSC-20 reference point uses the SIP-2 and SIP-3 reference points for transport and routing of subscription/notification related signalling. + +### 7.5.2.22 Reference point CSC-21 (between MC gateway servers in different MC systems) + +The CSC-21 reference point, which exists between MC gateway servers in different MC systems in different security domains, is used to share subscription and notification related signalling for group configuration and user configuration management to permit interconnection and migration between MC systems. + +The CSC-21 reference point uses the SIP-3 reference point for transport and routing of subscription/notification related signalling. + +## 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 GC1 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 MCVideo group 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 illustrating MC service group ID management in off-network operation. A central box 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 box, the text 'Pre-defined and associated' is present, with three arrows pointing from it to each of the three sections. + +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.1.5 Functional Alias + +Functional alias provides a complementary, role-based user identification scheme which can be used by MC service users for operational purposes in the form of meaningful elements such as the function, the order number or vehicle identifications that can be used within any form of MC service communication. Functional alias takes a form of a URI. The application addressing remains in its form and forms the foundation for the association with the corresponding functional alias. An MC service user can simultaneously activate several functional aliases but only one can be associated to a certain communication. + +Each functional alias is subject to the uniqueness principle within an organization and can be shared simultaneously by several MC service users, depending on the assignment. In this case, all assigned MC service users sharing a functional alias can be included in a communication. + +An MC service user can simultaneously use different functional aliases from multiple service organizations to allow the MC service user to be reachable by different organizations. + +## 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. + + + +``` +graph LR; subgraph Example1; ID1_1[MC service group ID 1] --> PSI1_1[Public service identity 1]; ID2_1[MC service group ID 2] --> PSI1_1; PSI1_1 --> Server1_1[MC service server 1]; end; subgraph Example2; ID1_2[MC service group ID 1] --> PSI1_2[Public service identity 1]; ID2_2[MC service group ID 2] --> PSI2_2[Public service identity 2]; PSI1_2 --> Server1_2[MC service server 1]; PSI2_2 --> Server1_2; end; subgraph Example3; ID1_3[MC service group ID 1] --> PSI1_3[Public service identity 1]; ID1_3 --> PSI2_3[Public service identity 2]; ID1_3 --> PSI3_3[Public service identity 3]; PSI1_3 --> Server1_3[MC service server 1]; PSI2_3 --> Server2_3[MC service server 2]; PSI3_3 --> Server3_3[MC service server 3]; end; +``` + +Diagram showing the relationship between MC service group IDs, Public service identities (PSIs), and MC service servers. It consists of three separate examples. In the first, MC service group IDs 1 and 2 both point to Public service identity 1, which points to MC service server 1. In the second, MC service group ID 1 points to Public service identity 1 and MC service group ID 2 points to Public service identity 2, both of which point to MC service server 1. In the third, MC service group ID 1 points to three different Public service identities (1, 2, and 3), which in turn point to MC service servers 1, 2, and 3 respectively. + +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. + + + +Figure 9.2.1.1-1: On-network architectural model diagram. The diagram shows a vertical stack of functional blocks: 'Application services layer' at the top, followed by 'SIP core' (offset to the right), 'EPS', 'UE 1', and 'UE 2' at the bottom. A dashed blue line separates 'UE 1' and 'UE 2'. Green lines represent 'Media' paths, and red lines represent 'Signalling' paths. The 'Application services layer' connects to 'EPS' via one green and two red lines. The 'SIP core' connects to 'EPS' via one red line and to 'Application services layer' via one red line. 'EPS' connects to 'UE 1' via one green and one red line. 'UE 1' connects to 'UE 2' via one green and one red line. A legend box on the right shows a green line for 'Media' and a red line for 'Signalling'. The text 'UE-to-network relay MC service' is located to the right of 'UE 2'. + +**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. + + + +The diagram illustrates a scenario where a single operator manages all network layers. A dashed rectangular box labeled "All services administered by same operator" encloses a vertical stack of components. From top to bottom, they are: "Application services layer", "SIP core", "EPS", "SIP client", "MC service client", and "MC service UE". + +Diagram showing a single operator administering all services. A dashed box labeled 'All services administered by same operator' contains the following stack: Application services layer, SIP core, EPS, SIP client, MC service client, and MC service UE. + +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. + + + +This diagram shows a separation of administrative domains. It consists of three stacked dashed boxes. The top box, labeled "MC service provider administered", contains the "Application services layer". The middle box, labeled "PLMN operator administered", contains the "SIP core", "EPS", and "SIP client". The bottom box, also labeled "MC service provider administered", contains the "MC service client" and "MC service UE". Vertical lines connect the components across these boundaries, showing the flow of communication despite the administrative separation. + +Diagram showing separate administration of services. It is divided into three dashed boxes: 'MC service provider administered' (top, containing Application services layer), 'PLMN operator administered' (middle, containing SIP core, EPS, and SIP client), and 'MC service provider administered' (bottom, containing MC service client and MC service UE). + +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. + + + +The diagram illustrates three stacked domains separated by dashed lines. The top domain is labeled 'MC service provider administered' and contains 'Application services layer' and 'SIP core'. The middle domain is labeled 'PLMN operator administered' and contains 'EPS'. The bottom domain is labeled 'MC service provider administered' and contains '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', the 'EPS' to the 'SIP client', and the 'SIP client' to the 'MC service client'. + +Diagram illustrating the MC service provider provision of SIP core, separate domain from EPS. The diagram shows three stacked domains: MC service provider administered (top), PLMN operator administered (middle), and MC service provider administered (bottom). + +**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. + + + +The diagram illustrates a layered architecture for MC services. It consists of three main administrative domains, each enclosed in a dashed box: + +- MC service provider administered (top):** Contains the **Application services layer** and the **SIP core**. +- PLMN operator administered (middle):** Contains the **EPS**. +- MC service provider administered (bottom):** Contains the **SIP client** and the **MC service client**, which are part of the **MC service UE**. + +Vertical connections between layers are as follows: + +- The **Application services layer** connects to the **SIP core**. +- The **SIP core** connects to the **EPS**. +- The **EPS** connects to the **SIP client**. +- The **SIP client** connects to the **MC service 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. + + + +``` + +graph TD + subgraph MC_service_provider_administered [MC service provider administered] + ASL[Application services layer] + SD[SIP database] + end + subgraph PLMN_operator_administered [PLMN operator administered] + SC[SIP core] + end + subgraph Application_service_provider_administered [Application service provider administered] + subgraph MC_service_UE [MC service UE] + MSC[MC service client] + SCli[SIP client] + end + end + EPS[EPS] + + ASL --- SD + ASL --- EPS + SD --- SC + SC --- EPS + MSC --- EPS + SCli --- SC + +``` + +Diagram illustrating the network architecture for MC service provider providing identities to PLMN operator SIP core. The diagram is divided into three main administrative domains: MC service provider administered (top left), PLMN operator administered (top right), and Application service provider administered (bottom). The MC service provider domain contains an Application services layer and a SIP database. The PLMN operator domain contains a SIP core. Both domains connect to a central EPS (Evolved Packet System) block. The Application service provider domain contains an MC service UE, which includes an MC service client and a SIP client. The MC service client connects to the EPS, and the SIP client connects to the SIP core. The SIP core also connects to the EPS. + +**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 showing the collocation of MC service user database and SIP database with HSS. On the left, a large box labeled 'HSS' contains three stacked boxes: 'MC service user database', 'SIP database', and 'HLR'. On the right, three stacked boxes are labeled 'MC service server', 'SIP core', and 'EPS'. Horizontal lines connect the HSS components to the right-side components: 'MC service user database' to 'MC service server' (labeled 'MC service defined interface'), 'SIP database' to 'SIP core' (labeled 'AAA-1'), and 'HLR' to 'EPS' (labeled 'S6a'). + +**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 showing a shared PLMN operator and MC service provider based deployment. On the left, a box labeled 'MCS user database' is above a large box labeled 'HSS'. The 'HSS' box contains two stacked boxes: 'SIP database' and 'HLR'. On the right, three stacked boxes are labeled 'MCX server', 'SIP core', and 'EPS'. Horizontal lines connect the 'MCS user database' to 'MCX server' (labeled 'MCS user database defined interface'), the 'SIP database' to 'SIP core' (labeled 'AAA-1'), and the 'HLR' to 'EPS' (labeled 'S6a'). + +**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 boxes on the left and a stack of three boxes on the right. The top-left box contains 'MC service user database' and 'SIP database'. The middle-left box contains 'HLR'. The bottom-left box is labeled 'HSS'. The top-right box is 'MC service server'. The middle-right box is 'SIP core'. The bottom-right box is 'EPS'. Connections: 'MC service defined interface' between MC service user database and MC service server; 'AAA-1' between SIP database and SIP core; '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 boxes on the left and a stack of three boxes on the right. The top-left box is 'MC service user database'. The middle-left box is 'SIP database'. The bottom-left box contains 'HLR' and is labeled 'HSS'. The top-right box is 'MC service server'. The middle-right box is 'SIP core'. The bottom-right box is 'EPS'. Connections: 'MC service defined interface' between MC service user database and MC service server; 'AAA-1' between SIP database and SIP core; '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. + + + +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. The SIP core is connected to the EPS via an Rx interface. The EPS is connected to the MC service UE. A red line labeled 'SIP signalling' is shown to the right of the SIP core, indicating the control path. + +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. + + + +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. The SIP core is connected to the EPS via an Rx interface. The EPS is connected to the MC service UE. A red line labeled 'SIP signalling' is shown to the right of the SIP core, indicating the control path. Additionally, a line from the MC service server connects to the EPS, bypassing the SIP core, which represents the bearer control path. + +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'. + +**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. 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. + + + +``` + +graph TD + Bootstrap[Bootstrap] --> Auth["MC service user authentication and MC service authorisation"] + Auth --> Ops["MC service operation(s) (e.g., Affiliation, Call establishment, Ongoing call, Call release)"] + Ops --> Logoff[MC service log-off] + Ops --> Ops + + IUC[Initial UE configuration] -.-> Bootstrap + UC[UE configuration] -.-> Auth + MUPC[MC service user profile configuration] -.-> Auth + GC[Group configuration] -.-> Auth + U[Updates to: UE configuration, MC service user profile configuration, group configuration] -.-> Ops + +``` + +Flowchart of MC service UE configuration time sequence. The sequence starts with 'Bootstrap', followed by 'MC service user authentication and MC service authorisation', then '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 the transitions between these 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 Operations; 'Updates to: UE configuration, MC service user profile configuration, group configuration' points to the transition between Operations and Log-off. There is also a feedback loop from the Operations box back to itself. + +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 after 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:** The extent of MC services available to an MC service UE with an unauthenticated MC user or unauthorized MC service user is described as 'limited services' in 3GPP TS 33.180 and is FFS. + +**Editor's note:** The decision by the MC service UE to continue use of initial configuration data after MC service authorisation or discontinue its use in favour of configuration data obtained after MC service authorisation 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. + + + +``` + +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] -.-> G + K[Group configuration for partner MC system] -.-> G + 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 finally 'MC service log-off'. Dashed boxes indicate optional or supplementary information: 'Security parameters to enable migration' (pointing to the transition between steps 1 and 2), 'MC service user profile configuration by partner MC system' and 'Group configuration for partner MC system' (pointing to the transition between steps 6 and 7), and 'Updates to: MC service user profile configuration by partner MC system, group configuration for partner MC system' (pointing to the transition between steps 7 and 8). + +**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]. At this point, the MC UE is configured sufficiently for the partner system so that the MC service user is capable of utilizing "limited services" as described 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 (see NOTE) | O | Reference to information stored relating to the MC service group | +| Group related key material (see 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.2.15 MC service emergency alert request + +Table 10.1.2.15-1 describes the information flow MC service emergency alert request from the MC service client to the MC service server. + +**Table 10.1.2.15-1 MC service emergency alert request information elements** + +| Information Element | Status | Description | +|---------------------|--------|------------------------------------------------------------| +| MC service ID | M | The identity of the alerting party | +| Functional alias | O | The functional alias of the alerting party | +| MC service group ID | M | The MC service group ID with which the alert is associated | +| Location | O | The alerting MC service client's location | + +Table 10.1.2.15-2 describes the information flow MC service emergency alert request from the MC service server to the MC service client. + +**Table 10.1.2.15-2 MC service emergency alert request information elements** + +| Information Element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------| +| MC service ID | M | The identity of the alerting party | +| Functional alias | O | The functional alias of the alerting party | +| MC service group ID | M | The MC service group ID with which the alert is associated | +| Organization name | M | The alerting MC service user's mission critical organization name | +| Location | O | The alerting MC service client's location | + +### 10.1.2.16 MC service emergency alert response + +Table 10.1.2.16-1 describes the information flow MC service emergency alert response from the MC service client to the MC service server and from the MC service server to the MC service client. + +**Table 10.1.2.16-1 MC service emergency alert response information elements** + +| Information Element | Status | Description | +|---------------------|--------|------------------------------------------------------------| +| MC service ID | M | The identity of the alerting party | +| MC service group ID | M | The MC service group ID with which the alert is associated | + +### 10.1.2.17 MC service emergency alert cancel request + +Table 10.1.2.17-1 describes the information flow MC service emergency alert cancel request from the MC service client to the MC service server and from the MC service server to the MC service client. + +**Table 10.1.2.17-1 MC service emergency alert cancel request information elements** + +| Information Element | Status | Description | +|----------------------------------------------------|--------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MC service ID | M | MC service user identity of the cancelling party | +| MC service ID (NOTE) | O | MC service user identity whose emergency alert is to be cancelled | +| MC service group ID | M | The MC service 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 MC service user's alert. If not present, then the alert of the MC service ID of the cancelling party is being cancelled | + +### 10.1.2.18 MC service emergency alert cancel response + +Table 10.1.2.18-1 describes the information flow MC service emergency alert cancel response from the MC service client to the MC service server and from the MC service server to the MC service client. + +**Table 10.1.2.18-1 MC service emergency alert cancel response information elements** + +| Information Element | Status | Description | +|---------------------|--------|------------------------------------------------------------| +| MC service ID | M | The identity of the cancelling party | +| MC service group ID | M | The MC service group ID with which the alert is associated | + +### 10.1.2.19 MC service emergency alert area notification + +Table 10.1.2.19-1 describes the information flow MC service emergency alert area notification from the MC service server to the MC service client. + +**Table 10.1.2.19-1 MC service emergency alert area notification information elements** + +| Information Element | Status | Description | +|--------------------------------|--------|--------------------------------------------------------------------------------------------------------| +| MC service ID | M | MC service user identity of the party to be notified | +| Emergency Alert Area Indicator | M | An indicator that the MC service 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 MC service alert area notification is not the same. + +### 10.1.2.20 MC service emergency alert announcement + +Table 10.1.2.20-1 describes the information flow for the MC service emergency alert announcement from the MC service client to the other MC service clients. + +**Table 10.1.2.20-1: MC service emergency alert announcement information elements** + +| Information Element | Status | Description | +|---------------------|--------|------------------------------------------------------------| +| MC service ID | M | The identity of the alerting MC service user | +| MC service group ID | M | The MC service 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.1.2.21 MC service emergency alert cancel announcement + +Table 10.1.2.21-1 describes the information flow for the MC service emergency alert cancel announcement from the MC service client to other MC service clients. + +**Table 10.1.2.21-1: MC service emergency alert cancel announcement information elements** + +| Information Element | Status | Description | +|---------------------|--------|------------------------------------------------------------| +| MC service ID | M | The identity of the cancelling MC service user | +| MC service group ID | M | The MC service group ID with which the alert is associated | + +## 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. + + + +``` + +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. A 'Configuration management client' sends a '1. Get MC service UE configuration request' to a 'Configuration management server', which responds with '2. 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. + + + +``` +graph LR; MC_user["MC service user (MC ID)"] --- MC_ID_X["MC service ID X (corresponding to MC service A)"]; MC_user --- MC_ID_Y["MC service ID Y (corresponding to MC service B)"]; MC_ID_X --- UP_X1["MC service user profile (Index 1)"]; MC_ID_X --- UP_X2["MC service user profile (Index 2)"]; MC_ID_X --- UP_Xn["MC service user profile (Index n)"]; MC_ID_Y --- UP_Y1["MC service user profile (Index 1)"]; MC_ID_Y --- UP_Y2["MC service user profile (Index 2)"]; MC_ID_Y --- UP_Yn["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, MC service user profiles, and MC services. + +**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. This information flow is sent individually addressed on unicast or multicast. + +**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. + + + +``` +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' (message 1) to the server. The server then performs an internal step labeled '2. Obtain MC service user profile' and sends a 'Get MC service user profile response' (message 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. + + + +``` + +sequenceDiagram + participant MC service UE + participant Partner MC system of user + participant Primary MC system of user + + Note left of MC service UE: Configuration management client + Note right of Partner MC system of user: Configuration management server, MC service user database + Note right of Primary MC system of user: Configuration management server, MC service user database + + MC service UE->>Partner MC system of user: 1. Get MC service user profile for migration request + Partner MC system of user->>Primary MC system of user: 2. Get migrated MC service user profile request + Primary MC system of user->>Primary MC system of user: 3. Retrieve user profile for migration + Primary MC system of user->>Partner MC system of user: 4. Get migrated MC service user profile response + Partner MC system of user->>Partner MC system of user: 5. Modify user profile according to partner MC system policy and store + Partner MC system of user->>Primary MC system of user: 6. Validate modified MC service user profile request + Primary MC system of user->>Primary MC system of user: 7. Validate modified user profile for migration + Primary MC system of user->>Partner MC system of user: 8. Validate modified MC service user profile response + Partner MC system of user->>MC service UE: 9. Get MC service user profile for migration response + +``` + +Sequence diagram titled 'Retrieval of user profile in partner MC system'. It shows interactions between three main entities: MC service UE, Partner MC system of user, and Primary MC system of user. The MC service UE contains a 'Configuration management client'. The Partner MC system contains a 'Configuration management server' and an 'MC service user database'. The Primary MC system contains a 'Configuration management server' and an 'MC service user database'. The sequence of messages is: 1. Client to Partner Server: Get MC service user profile for migration request. 2. Partner Server to Primary Server: Get migrated MC service user profile request. 3. Primary Server to Primary DB: Retrieve user profile for migration. 4. Primary DB to Partner Server: Get migrated MC service user profile response. 5. Partner Server to Partner DB: Modify user profile according to partner MC system policy and store. 6. Partner Server to Primary Server: Validate modified MC service user profile request. 7. Primary Server to Primary DB: Validate modified user profile for migration. 8. Primary DB to Partner Server: Validate modified MC service user profile response. 9. Partner Server to Client: Get MC service user profile for migration response. + +**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. + + + +``` +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 (internal to the server), 2. Notification for MC service user profile data update (server to client), 3. Get updated MC service user profile data request (client to server), 4. Get updated MC service user profile data response (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. + + + +``` +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. + + + +``` + +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 showing the interaction between a Configuration management client and a Configuration management server for updating a pre-selected MC service user profile. The client sends a request (1. Update pre-selected MCPTT user profile request) to the server. The server performs an authorization check (2. Authorization check) and stores the selection (3. Store MCPTT user profile selection). Finally, the server sends a response (4. Update pre-selected MCPTT user profile response) back to the 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. + + + +``` +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; + + + +``` + +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 + +``` + +Sequence diagram showing the interaction between a Group management client (Authorized user) and a Group management server. The steps are: 1. Receive group configurations (internal to client), 2. Store group configuration request (client to server), 3. Validate group configurations (internal to server, dashed box), 4. Store group configurations (internal to server), 5. Store group configuration response (server to client). + +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. + + + +``` +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 retrieving group configurations. Lifelines: Group management client and Group management server. The client sends a '1. Get group configuration request' to the server. The server responds with '2. Get group configuration response'. The client then performs an internal action '3. Store group configuration data'. + +**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. + + + +``` +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 subscription. Lifelines: Group management client and Group management server. The client sends a '1. Subscribe group configuration request' to the server. The server responds with '2. Subscribe group configuration response'. + +**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. + + + +``` + +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 + +##### 10.1.5.5.1 Dynamic data associated with a group in MC service server + +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-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. | +| Regroup status of group where regrouping using a preconfigured group is used, e.g. whether group is regrouped, MC service group identity of regroup group. | + +##### 10.1.5.5.2 Affiliation status in group management server + +The affiliation status in the form of a list of MC service IDs of affiliated group members corresponding to the MC service for that group is available in group management server. The group management server can subscribe to this + +information from the MC service server in Table 10.1.5.5.1-1. Table 10.1.5.5.2-1 describes the affiliation status contained in the group management server. + +**Table 10.1.5.5.2-1: Affiliation status in group management server** + +| Parameter description | +|----------------------------------| +| MC service group ID | +| List of affiliated group members | +| > MCPTT | +| >> MCPTT ID | +| > MCVideo | +| >> MCVideo ID | +| > MCData | +| >> MCData ID | + +**Editor's note:** The support for affiliation status in the group management server of an MC service user logged into multiple UEs is FFS. + +## 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.1. + +The group management server can subscribe for affiliation status associated with a group at the MC service server. The affiliation status in the group management server is described in subclause 10.1.5.5.2. + +### 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 and from the group management server 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 and from the MC service server to the group management server. This information flow from the MC service server to the MC service client is sent individually addressed on unicast or multicast. + +**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 and from the MC service server to the group management server. This information flow from the + +MC service server to the MC service client may be sent individually addressed or group addressed on unicast or multicast (see subclause 10.7.3.4.1). + +**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 and from the group management server 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. + + + +``` + +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 + +``` + +Sequence diagram showing the subscription process for group dynamic data between an MC service client and an MC service server. + +**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. + + + +``` +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 +``` + +A sequence diagram showing the interaction between an MC service client and an MC service server. The MC service server sends a '1. Notify group dynamic data request' to the MC service client, and the MC service client responds with '2. Notify group dynamic data response'. + +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.5.6.3 Procedure for subscription and notification for affiliation status associated with a group by the group management server + +The procedure for subscription for affiliation status associated with an MC service group by the group management server is described in figure 10.1.5.6.3-1 and is used by the group management server to obtain the affiliation status (implicit and explicit) from the MC service server. + +Pre-conditions: + +- The MC service server is the MC service server within the MC system where the group is defined. + + + +``` +sequenceDiagram + participant Group management server + participant MC service server + Group management server->>MC service server: 1. Subscribe group dynamic data request + MC service server-->>Group management server: 2. Subscribe group dynamic data response +``` + +A sequence diagram showing the interaction between a Group management server and an MC service server. The Group management server sends a '1. Subscribe group dynamic data request' to the MC service server, and the MC service server responds with '2. Subscribe group dynamic data response'. + +Sequence diagram for Subscription for group affiliation status + +**Figure 10.1.5.6.3-1: Subscription for group affiliation status** + +1. The group management server subscribes to the group affiliation status stored in the MC service server using the subscribe group dynamic data request. +2. The MC service server provides a subscribe group dynamic data response to the group management server indicating success or failure of the request. + +The procedure for notification of group affiliation status as shown in figure 10.1.5.6.3-2 is used by the MC service server to inform the group management server about the updates to the group affiliation status. + +Pre-conditions: + +- The group management server has subscribed to the affiliation status in the MC service server. +- The affiliation status associated with a group subscribed to by the group management server has been updated at the MC service server. + + + +``` +sequenceDiagram + participant Group management server + participant MC service server + MC service server->>Group management server: 1. Notify group dynamic data request + Group management server-->>MC service server: 2. Notify group dynamic data response +``` + +A sequence diagram showing the interaction between a Group management server and an MC service server. The MC service server sends a '1. Notify group dynamic data request' to the Group management server, and the Group management server responds with '2. Notify group dynamic data response'. + +Sequence diagram for Notification of group affiliation status + +**Figure 10.1.5.6.3-2: Notification of group affiliation status** + +1. The MC service server provides the affiliation status via a notification to the group management server which has subscribed for the group affiliation status. +2. The group management server 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 + +Connectivity information for the partner MC system, including MC system identification and access information, is contained in the on-network user profiles for MCPTT in 3GPP TS 23.379 [16], for MCVideio in 3GPP TS 23.281 [12] and for MCData in 3GPP TS 23.282 [13]. + +### 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. + + + +``` + +sequenceDiagram + participant MC_service_UE as MC service UE + participant Partner_MC_system as Partner MC system + participant Primary_MC_system as Primary MC system + + Note left of MC_service_UE: Signalling user agent + Note right of Partner_MC_system: SIP core, Migration management server + Note right of Primary_MC_system: Migration management server, SIP core + + MC_service_UE->>Partner_MC_system: 1. SIP registration request + Partner_MC_system->>Partner_MC_system: 2. Get SIP authentication information request + Partner_MC_system->>Partner_MC_system: 3. Map SIP identities + Partner_MC_system->>Primary_MC_system: 4. Get SIP authentication information request + Primary_MC_system->>Primary_MC_system: 5. Get SIP authentication information request + Primary_MC_system->>Primary_MC_system: 6. Get SIP authentication information response + Primary_MC_system->>Partner_MC_system: 7. Get SIP authentication information response + Partner_MC_system->>Partner_MC_system: 8. Map SIP identities + Partner_MC_system->>Partner_MC_system: 9. Get SIP authentication information response + Note left of MC_service_UE: 10. SIP Authentication procedure + MC_service_UE->>Partner_MC_system: 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 a Signalling user agent), Partner MC system (with a SIP core and a Migration management server), and Primary MC system (with a Migration management server and a SIP core). The sequence of messages is: 1. SIP registration request from Signalling user agent to SIP core; 2. Get SIP authentication information request from SIP core to Migration management server; 3. Map SIP identities (internal); 4. Get SIP authentication information request from Migration management server to Primary MC system's Migration management server; 5. Get SIP authentication information request from Primary MC system's Migration management server to its SIP core; 6. Get SIP authentication information response from Primary MC system's SIP core to its Migration management server; 7. Get SIP authentication information response from Primary MC system's Migration management server to Partner MC system's Migration management server; 8. Map SIP identities (internal); 9. Get SIP authentication information response from Partner MC system's Migration management server to its SIP core; 10. SIP Authentication procedure (internal to Signalling user agent); 11. SIP registration response from SIP core to Signalling user agent. + +**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. + + + +``` +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 showing the interaction between a Functional alias management client and a Functional alias management server. The client sends a '1. Get functional alias configuration request' to the server. The server responds with '2. Get functional alias configuration response'. The client then performs '3. Store functional alias configuration data'. + +**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. + + + +``` +sequenceDiagram + participant Client as Functional alias management client + participant Server as Functional alias management server + Note left of Client: + Client->>Server: 1. Subscribe functional alias configuration request + Server-->>Client: 2. Subscribe functional alias configuration response +``` + +A sequence diagram showing the interaction between a 'Functional alias management client' and a 'Functional alias management server'. The client sends a '1. Subscribe functional alias configuration request' to the server, and the server responds with a '2. Subscribe functional alias configuration response'. + +Sequence diagram for subscription + +**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. + + + +``` +sequenceDiagram + participant Client as Functional alias management client + participant Server as Functional alias management server + Note right of Server: + Server->>Client: 1. Notify functional alias configuration request + Client-->>Server: 2. Notify functional alias configuration response +``` + +A sequence diagram showing the interaction between a 'Functional alias management client' and a 'Functional alias management server'. The server sends a '1. Notify functional alias configuration request' to the client, and the client responds with a '2. Notify functional alias configuration response'. + +Sequence diagram for notification + +**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 (see NOTE 1) | +| MC service list (see NOTE 2) | O | List of MC services whose service communications are to be enabled on the group. | +| Proposed MC service group ID | O | MC service group ID proposed for the requested group | +| MC service group configuration data | O | Configuration data for the requested group (see NOTE 3) | +| NOTE 1: The MC service ID list can be an empty list.
NOTE 2: This information element shall be included in the message for creating a group configured for multiple MC services.
NOTE 3: If the MC service group configuration data is not present it can be provided later using the "Store group configuration request" (see subclause 10.1.2.1). | | | + +#### 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 (see NOTE) | MC service group ID of the group | +| Result | M | Indicates success or reason for failure | +| 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 | +| Broadcast regroup | O | Indicates that only an authorized MC service user can transmit on this temporary 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 (see 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. | +| Broadcast regroup | O | Indicates that only an authorized MC service user can transmit 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 and from the group management server to the group management client. + +**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 and from the group management client to the group management server. + +**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 and from the group management server to the group management client. + +**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 | +| Broadcast regroup | O | Indicates that only an authorized MC service user can transmit on this 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 and from the group management client to the group management server. + +**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 | +| Broadcast regroup | O | Indicates that only an authorized MC service user can transmit on this 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 flow 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
(see NOTE 1) | Configuration information for the MC service group | +| Failure reason | O
(see 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. + + + +``` + +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 creation request + Note right of Server: 2a. Check acceptability of any proposed MC service group ID or modify or generate the MC service group ID + Note right of Server: 2b. Create and store the group related information + Server-->>MCServer: 3. Group creation notify + Note right of Server: 4. Notify the users + Server-->>Client1: 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 starts with a '1. Group creation request' from the first client to the server. The server performs internal steps '2a. Check acceptability of any proposed MC service group ID or modify or generate the MC service group ID' and '2b. Create and store the group related information'. Then, a dashed arrow '3. Group creation notify' goes from the server to the MC service server. A box '4. Notify the users' is shown between the server and the second client. Finally, a '5. Group creation response' is sent from the server back to the first 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. + +NOTE 1: The administrator/dispatcher/authorized MC service user can include a proposed MC service group ID in the group creation request. The proposed MC service group ID can be derived from a set of rules previously agreed between the administrator/dispatcher/authorized MC service user and the group management server. The method by which the the administrator/dispatcher/authorized MC service user obtains the set of rules is outside the scope of the present document. + +NOTE 2: The administrator/dispatcher/authorized MC service user can include include configuration data for the requested group. The method by which the administrator/dispatcher/authorized MC service user prepares the configuration data for the requested group is outside the scope of the present document, but it could, for example, be derived from pre-prepared templates available to the administrator/dispatcher/authorized MC service user. + +- 2a. If the proposed MC service group ID information element is not present in the group creation request, the group management server generates the MC service group ID. If the proposed MC service group ID information element is present and acceptable to the group management server, the group management server uses the proposed MC service group ID for the new group. If the proposed MC service group ID information element is present but not acceptable to the group management server, the group management server modifies proposed MC servicegroup ID or generates the MC service group ID or rejects the group creation request. +- 2b. During the group creation, the group management server stores or 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 (if any). 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 (if any) 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. The result information element indicates: + - success (using proposed MC service group ID); or + - success (MC service group ID provided by the group management server); or + - failure (proposed MC service group ID not acceptable); or + - failure for other reason. + +## 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. + +The temporary group created can be a broadcast group or a non-broadcast group. The broadcast 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 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.180 [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]. + +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. + + + +``` + +sequenceDiagram + participant G1 as Group management client + participant GMS as Group management server + participant G2 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 + Note right of GMS: 8.Retrieve group configuration, as described in clause 10.1.5.2 + + G1->>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->>G2: 5.Group regroup notification + G2->>GMS: 6.Group regroup notification response + GMS->>G1: 7.Group regroup response + GMS->>GMS: 8.Retrieve group configuration, as described in clause 10.1.5.2 + +``` + +Sequence diagram for Group regroup within the same MC system. Lifelines: Group management client, Group management server, Group management client (MC service group members), and MC service server. The process involves a request, authorization check, group creation, notification to the server, notification to members, responses from members, a response to the client, and configuration retrieval. + +**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. The group management client indicates whether the temporary group is a broadcast regroup. +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, the security level of the temporary group, and whether the temporary group is a broadcast regroup. 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 by sending group regroup notification messages. +6. The affiliated MC service group members of the constituent MC service groups send individual group regroup notification response messages. +7. 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. + +8. The affiliated MC service group members of the constituent MC service groups individually request group configuration data from the group management server for the temporary group, as described in clause 10.1.5.2. The group configuration data includes security, priority, and other parameters. + +### 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. + + + +``` + +sequenceDiagram + participant GMC as Group management client + participant GMS1 as Group management server 1 + participant GMS1_PGM as Group management client (Primary group members) + participant MSS1 as MC service server (Primary) + participant GMS2 as Group management server 2 + participant GMS2_PGM as Group management client (Partner group members) + participant MSS2 as MC service server (Partner) + + GMC->>GMS1: 1.Group regroup request + Note over GMS1: 2.Authorization check based on group policy and check whether group1 is a temporary group + GMS1->>GMS2: 3.Group regroup request + Note over GMS2: 4.Check whether group2 is a temporary group + GMS2->>GMS1: 5.Group regroup response + Note over GMS1: 6.Create and store temporary group related information + GMS1->>GMS2: 7.Group regroup notification + GMS2->>GMS1: 8.Group regroup notification response + GMS2->>MSS2: 9.Group regroup notify + MSS2->>GMS2: 10.Group regroup notify response + GMS2->>GMS2_PGM: 11.Group regroup notification + GMS2_PGM->>GMS2: 12.Group regroup notification response + GMS2->>MSS1: 13.Group regroup notify + MSS1->>GMS1: 14.Group regroup notification response + GMS1->>GMS1_PGM: 15.Group regroup notification + GMS1_PGM->>GMS1: 16.Group regroup notification response + GMS1->>GMC: 17.Group regroup response + Note over GMS1_PGM: 18.Retrieve group configuration, as described in clause 10.1.5.2 + Note over GMS2_PGM: 18.Retrieve group configuration, as described in clause 10.1.5.2 + +``` + +Sequence diagram for Temporary group formation - group regrouping involving multiple MC systems. + +**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. The group management client indicates whether the temporary group is a broadcast regroup. + +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, the security level of the temporary group, and whether the temporary group is a broadcast regroup. 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 affiliated MC service group members of the constituent MC service groups of the group management server 2 send individual group regroup notification responses to the group management server 2. +13. 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. +14. Primary MC service server acknowledges the notification from the group management server 1. +15. The group management server 1 notifies the affiliated MC service group members of the constituent MC service groups of the group management server 1 by sending group regroup notification messages. +16. The affiliated MC service group members of the constituent MC service groups of group management server 1 send individual group regroup notification responses to the group management server 1. + +17. The group management server 1 provides a group regroup response to the group management client of the authorized MC service user (e.g. dispatcher). +18. The affiliated MC service group members of the constituent MC service groups of the group management servers individually request group configuration data from the group management servers for the temporary group, as described in clause 10.1.5.2. The group configuration data includes security, priority, and other parameters. + +### 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. + + + +``` + +sequenceDiagram + participant Client as Group management client + participant Server1 as Group management server 1 + participant PrimaryMembers as Group management client (Primary group members) + participant PrimaryServer as MC service server (Primary) + participant Server2 as Group management server 2 + participant PartnerMembers as Group management client (Partner group members) + participant PartnerServer 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->>PrimaryServer: 5.Group regroup teardown notify + Note right of PrimaryServer: 6.Notify the affiliated users of the group + PrimaryServer->>Server2: 7a.Group regroup teardown notification + Server2->>PrimaryServer: 7b.Group regroup teardown notification + Server2->>PartnerServer: 8.Group regroup teardown notify + Note right of PartnerServer: 9.Notify the affiliated users of the group + Server1->>Client: 10.Group regroup teardown response + +``` + +Sequence diagram for Temporary group tear down involving multiple group host servers. 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 authorization checks, completion of active calls, and tear down of the temporary group. Notifications are then sent to the primary server, server 2, and the partner server, with a final 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: + +- Group regroup in either single MC system or multiple MC systems can 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 + - If the policy of the MC system does not allow a temporary group to include groups that are currently in emergency state, then regrouping of groups can take place if none of the groups to be regrouped are in emergency state. +- If the policy of the MC system allows a temporary group to include groups from other MC systems, group regrouping containing groups with multiple MC systems can take place if: + - the MC service server (controlling role) for the regrouped group is the MC service server (controlling role) for all MC service groups involved in the regrouping; or + - the MC service server (controlling role) for the regrouped group is an MC service server (controlling role) for at least one of the MC service groups involved in the regrouping; or + - the MC service server (controlling role) for the regrouped group is an MC service server homed by at least one of the MC service groups and the MC system of any involved 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 the 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 take place if: + - the MC service server (controlling role) for the regrouped group is the MC service server (controlling role) for all MC service groups involved in the regrouping; or + - the MC service server (controlling role) for the regrouped group is an MC service server (controlling role) for at least one of the MC service groups involved in the regrouping, and the MC service servers with the controlling roles for all of the groups that are regrouped are within the same MC system. + +## 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. + + + +``` +sequenceDiagram + participant GMC as Group management client + participant GMS as Group management server + Note right of GMS: 2. Authorization check and retrieve according to the conditions + GMC->>GMS: 1. Group information query request + GMS-->>GMC: 3. Group information query response +``` + +The diagram is a sequence diagram showing the interaction between a Group management client and a Group management server. The client sends a '1. Group information query request' to the server. The server performs an '2. Authorization check and retrieve according to the conditions' (shown in a box) and then sends a '3. Group information query response' back to the client. + +Sequence diagram for membership or affiliation list query + +**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. + + + +``` +sequenceDiagram + participant GMS as Group management server + participant GMC as Group management client + participant MSS as MC service server + Note right of GMS: 1. Group membership changed + GMS->>MSS: 2. Group membership notification + GMS->>GMC: 3. Group membership notification + Note left of GMS: 4. Retrieve group configuration +``` + +The diagram is a sequence diagram illustrating the group membership notification process. It features three lifelines: Group management client, Group management server, and MC service server. The sequence of messages is as follows: 1. A self-message on the Group management server labeled '1. Group membership changed'. 2. A message from the Group management server to the MC service server labeled '2. Group membership notification'. 3. A message from the Group management server to the Group management client labeled '3. Group membership notification'. 4. A dashed box labeled '4. Retrieve group configuration' indicating a request from the Group management client to the Group management server. + +Sequence diagram for group membership notification + +**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. + + + +``` +sequenceDiagram + participant G1 as Group management client (Administrator/authorized user/dispatcher) + participant GMS as Group management server + participant G2 as Group management client (MC service group members) + participant MSS as MC service server + + Note right of GMS: 2. Group membership update + Note right of G2: 4. Notify the users + + G1->>GMS: 1. Group membership update request + GMS->>GMS: 2. Group membership update + GMS->>MSS: 3. Group membership notification + GMS->>G2: 4. Notify the users + GMS->>G1: 5. Group membership update response +``` + +The diagram is a sequence diagram illustrating the interaction for a group membership update. It features four 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. A request from the first client to the server. 2. An internal update on the server. 3. A notification from the server to the MC service server. 4. A notification from the server to the second client. 5. A response from the server back to the first client. + +Sequence diagram for Group membership update by authorized user + +**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. + + + +``` +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 + 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-->>Partner MC system of group: 4. Notify group information + Partner MC system of group-->>Primary MC system of group: 5. Group information provision response +``` + +Sequence diagram showing the Primary MC system providing group configuration to the Partner MC system. The diagram involves two lifelines: 'Primary MC system of group' (containing a 'Group management server') and 'Partner MC system of group' (containing a 'Group management server' and an 'MC service server'). The sequence of messages is: 1. Group information provision request from Primary 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 Partner MSS; 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. + + + +``` + +sequenceDiagram + participant MC_server as 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_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_server: 6. Group information response + +``` + +Sequence diagram showing the interaction between an MC service server, a group management server in the partner MC system, and a group management server in the primary MC system. The sequence includes: 1. Group information request from MC service server to partner GMS; 2. Group information request from partner GMS to primary GMS; 3. Group information response from primary GMS to partner GMS; 4. Modify group configuration according to partner MC system policy (internal step); 5. Store group configuration information (internal step); 6. Group information response from partner GMS to MC service server. + +**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. + + + +``` +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 Group management servers. On the left, the 'Partner MC system of MC service group' contains a 'Group management server'. On the right, the 'Primary MC system of MC service group' contains another 'Group management server'. A solid arrow labeled '1. Group information subscribe request' points from the partner's server to the primary's server. A return arrow labeled '2. Group information subscribe response' points from the primary's server back to the partner's server. + +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. + + + +``` +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 Group management servers. On the left, the 'Partner MC system of MC service group' contains a 'Group management server'. On the right, the 'Primary MC system of MC service group' contains another 'Group management server'. A solid arrow labeled '1. Group information notify request' points from the primary's server to the partner's server. A return arrow labeled '2. Group information notify response' points from the partner's server back to the primary's server. + +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. + + + +``` + +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 + GMC->>GMS: 1. 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 procedure. Lifelines: Group management client (originator), Group management server, MC service server, Group management clients (group members). Steps: 1. Group deletion request (client to server), 2. Authorize group deletion request (internal server action), 3. Group deletion notification (server to MC service server), 4. Group deletion notification (server to group members), 5. Group deletion response (server to client). + +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. + + + +``` +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 interaction for pre-established session establishment. 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. A 'Create pre-established session response' is sent back to the client. 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. + + + +``` +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 the interaction between an MC service client and an MC service server for a pre-established session modification. The sequence of steps is as follows: 1. The MC service client gathers ICE candidates (shown in a dashed box). 2. The client sends a 'Modify pre-established session request' to the server. 3. The server performs service control, obtains media parameters, and gathers ICE candidates (shown in a solid box). 4. The server sends a 'Modify pre-established session response' back to the client. 5. ICE candidate pair checks are performed (shown in a dashed box). 6. The client sends another 'Modify pre-established session request' to the server. 7. The server sends a final 'Modify pre-established session response' to the client. + +Sequence diagram for Pre-established session modification + +**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. + + + +``` +sequenceDiagram + participant MC service client + participant MC service server + Note right of MC service server: 3. Release resources + MC service client->>MC service server: 1. Release pre-established session request + MC service server-->>MC service client: 2. Release pre-established session response +``` + +A sequence diagram showing the interaction between an MC service client and an MC service server. The client sends a 'Release pre-established session request' to the server. The server responds with a 'Release pre-established session response'. Simultaneously, a note on the server side indicates 'Release resources'. + +Sequence diagram for MC service client initiated pre-established session release + +**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. + + + +``` +sequenceDiagram + participant MC service client + participant MC service server + Note right of MC service server: 3. Release resources + MC service server->>MC service client: 1. Release pre-established session request + MC service client-->>MC service server: 2. Release pre-established session response +``` + +A sequence diagram showing the interaction between an MC service client and an MC service server. The server sends a 'Release pre-established session request' to the client. The client responds with a 'Release pre-established session response'. Simultaneously, a note on the server side indicates 'Release resources'. + +Sequence diagram for MC service server initiated pre-established session release + +**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. + + + +``` + +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** + +| Information element | Status | Description | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|-----------------------------------------------------------------------------------------------------| +| 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. This information flow is sent individually addressed on unicast or multicast. + +**Table 10.6.3.2.2-1: Migration service authorization response** + +| Information element | Status | Description | +|--------------------------------------------------------------------------------------------------------------------|--------|-----------------------------------------------------------------------------------------------------| +| 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. + + + +``` + +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 titled '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. The process involves a migration service authorization request from the client to the partner server, an initial authorization check, forwarding of the request through gateway servers to the primary server, a final authorization check and marking of migration in the primary system, and a return response through the gateway servers back to the 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. | +| MBMS reception quality level | O | The reception quality level per TMGI (see NOTE) | +| Unicast listening status | O | The unicast listening status. | +| NOTE: | The set of quality levels helps service continuity in MBMS scenarios. A reception quality level may help to make an efficient switching decision to another bearer. How these levels are used is implementation specific. | | + +#### 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 MBMS 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 MBMS broadcast area. | +| Bandwidth | M | Maximum bandwidth required | +| QCI | O | Desired QCI | + +#### 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 | +|----------------------------------|--------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TMGIs | M | List of TMGIs and related information | +| List of service area identifiers | M | A list of service area identifiers for the applicable MBMS broadcast areas, corresponding to the listed TMGIs, over which the request was successful. | +| Frequency | O | Identification of the frequency if multi-carrier support is provided | +| 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 a remote UE over PC5. | + +#### 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 | +|------------------------|--------|----------------------------------------------------------------------------------------------------------------------| +| TMGI | M | TMGI 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) | +| QCI | O | Desired QCI | +| 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 | +|------------------------------|--------|----------------------------------------------------------------------------------------------------------------------| +| TMGI | M | TMGI 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) | +| QCI | O | Actual QCI | +| Media stream identifier | O | This element identifies the media stream of the SDP used for the group call (e.g. MBMS 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 | +|---------------------|--------|-------------------------------------------------------------------------| +| TMGI | M | TMGI 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.2.12 Group status notification + +Table 10.7.2.12-1 describes the information flow for the group status notification from MC service server to MC service client. + +**Table 10.7.2.12-1: Group status notification** + +| Information element | Status | Description | +|---------------------|--------|---------------------------------------------| +| MCPTT group ID | M | The MCPTT group ID of the group | +| Status of the group | M | Indicate the group has on-going call or not | + +### 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 need 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. + + + +``` +sequenceDiagram + participant MC service client + participant MC service server + Note right of MC service server: 1a. Activate MBMS bearers + Note right of MC service server: 1b. Activate MBMS bearers for application level control signalling + MC service server-->>MC service client: 2a. MBMS bearer announcement + MC service server-->>MC service client: 2b. MBMS bearer announcement ( For control signalling ) + Note left of MC service 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). + MC service client->>MC service server: 4. MBMS listening status report + Note right of MC service server: 5. Procedure of MC communication session setup and media delivery using MBMS + Note left of MC service client: 6. DL media over MBMS +``` + +The diagram is a sequence diagram showing the interaction between an MC service client and an MC service server. The sequence of steps is as follows: 1. The MC service server activates MBMS bearers (1a) and optionally activates MBMS bearers for application level control signalling (1b). 2. The MC service server sends MBMS bearer announcements to the MC service client (2a and 2b). 3. The MC service client stores TMGI(s), service area and other info about the MBMS bearer(s), and the MC service UE starts to monitor the TMGI(s). 4. The MC service client sends an MBMS listening status report to the MC service server. 5. The MC service server performs the procedure of MC communication session setup and media delivery using MBMS. 6. The MC service server sends DL media over MBMS to the MC service client. + +Sequence diagram illustrating the use of pre-established MBMS bearers for MC group communication. + +**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. + + + +``` + +sequenceDiagram + participant UE + participant MC service server + Note over UE, MC service server: 1. Procedure of MC communication session setup + MC service server->>UE: 2. DL media over unicast + Note right of MC service server: 3. Establish MBMS bearers + MC service server->>UE: 4. MBMS bearer announcement + 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 + UE->>MC service server: 7. MBMS bearer listening status report + Note over UE, MC service server: 8. Group communication session via dynamic MBMS bearer(s) is established + MC service server->>UE: 9. DL media over MBMS + +``` + +The diagram shows a sequence of interactions between a User Equipment (UE) and an MC service server. It begins with a session setup procedure. The server initially sends downlink media via unicast. Simultaneously, it establishes MBMS bearers and announces them to the UE. The UE then monitors for the MBMS bearer associated with a specific TMGI and confirms its ability to receive it. A listening status report is sent from the UE to the server. Upon receiving this, a group communication session is established via dynamic MBMS bearers, and the server switches to sending downlink media over MBMS. + +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 the MBMS listening status associated to the monitored TMGI, (e.g. that it is successfully receiving the TMGI). The MC service client may also notify the MBMS reception quality level of the TMGI. MC service server stops sending media data over unicast way to the MC service client. +- NOTE 2: The MBMS reception quality level may be used by the MC service server to make an efficient decision to switch again to a unicast transmission or to take measures to prepare such a switch (e.g. when the quality level indicates that the reception quality of the MBMS bearer is decreasing or reaching an insufficient quality level for the reception of MC services). +8. An MC service group communication session via dynamic MBMS bearer(s) is established. +- NOTE 3: 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. + + + +``` + +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 + +``` + +The diagram illustrates the interaction between a User Equipment (UE) and an MC Service Server for switching from MBMS to unicast delivery. The sequence starts with the UE detecting a bad MBMS bearer condition (Step 1). It then sends an MBMS listening status report to the MC Service Server (Step 2). The server responds with downlink data over a unicast bearer (Step 3). During this transition, the UE simultaneously receives data over both unicast and MBMS bearers (Step 4, shown in a dashed box). Finally, the UE stops receiving MBMS and continues receiving traffic only over the unicast bearer (Step 5). + +Sequence diagram showing the switching from MBMS delivery to unicast delivery between a UE and an MC Service Server. + +**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. + +NOTE 1: To efficiently notify the MC service server, e.g., when the MC service client detects that the reception quality of the MBMS bearer is decreasing or reaching an insufficient quality level for the reception of MC services, the MC service client proactively may send to the MC service server a MBMS listening status report including the MBMS reception quality level. + +3. The MC service server sends the downlink data by unicast delivery to the MC service client. + +NOTE 2: 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. + +The MC service client shall not send responses to group-addressed application level control signalling unless instructed or configured to respond. + +##### 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. + + + +``` +sequenceDiagram + participant MC service client + participant MC service server + Note right of MC service server: 1. Activate MBMS bearer for application control message + MC service server->>MC service client: 2. MBMS bearer announcement + Note left of MC service 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. + MC service client->>MC service server: 4. MBMS listening status report + Note right of MC service server: 5. Application control messages + MC service server-->>MC service client: 5. Application control messages +``` + +The diagram is a sequence diagram with two lifelines: 'MC service client' on the left and 'MC service server' on the right. The interaction consists of five steps: 1. The MC service server sends a message to activate an MBMS bearer for application control messages. 2. The MC service server sends an 'MBMS bearer announcement' to the MC service client. 3. The MC service client stores the TMGI, service area, and other information about the MBMS bearer, and the MC service UE starts to monitor the TMGI. 4. The MC service client sends an 'MBMS listening status report' to the MC service server. 5. The MC service server sends 'Application control messages' to the MC service client, represented by a large blue arrow. + +Sequence diagram illustrating the use of 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. The MC service client may also indicate at which MBMS reception quality level it has received the MC service media on the MBMS bearer. Hence, 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. + + + +``` +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 + MC service client-->>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 +``` + +The diagram is a sequence diagram showing the interaction between an MC service client and an MC service server. The sequence of steps is as follows: 1. The MC service client monitors an existing MBMS bearer for application control messages. 2. The MC service server activates a new MBMS bearer. 3. The MC service server decides to announce this new bearer. 4. The server sends an 'MBMS bearer announcement' message to the client. 5. The client monitors the newly announced bearer. 6. The client sends an 'MBMS bearer acknowledgement' message back to the server. 7. The server decides to de-announce the bearer. 8. The server sends an 'MBMS bearer de-announcement' message to the client. 9. The client stops monitoring the de-announced bearer. + +Sequence diagram illustrating the MBMS bearer announcement procedure between an MC service client and an MC service server. + +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. Furthermore, based on the received quality, the MC service client may notify the MC service server at which MBMS reception quality level it has received the MC service media on the MBMS bearer. + +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 can be 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 + + + +``` + +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 + +``` + +The diagram shows a sequence of three messages between an MC service client and an MC service server. + 1. The MC service client performs an internal 'MBMS bearer quality determination'. + 2. It then sends a solid arrow message labeled '2. MBMS listening status report' to the MC service server. + 3. The MC service server responds with a dashed arrow message labeled '3. MBMS bearer announcement' back to the client. + +Sequence diagram illustrating MBMS bearer quality detection between an MC service client and an MC service server. + +**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 can 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. The MC service client may also map the determined MBMS bearer quality to a MBMS reception quality level. The MBMS reception quality level indicates at which specific MBMS bearer quality level the MC service media has been received. Based on the MBMS reception quality level, the MC service server may efficiently decide to switch to another bearer or to take measures to prepare such a switch. + +**Editor's note:** The set of MBMS reception quality levels and the mapping of the determined MBMS bearer quality to those levels are FFS. + +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 is used to define the MBMS listening status, which indicates if the MBMS bearer quality has been acceptable or not to receive a specific MC service media. If the MBMS bearer quality is mapped to a different MBMS reception quality level, the MC service client may send an MBMS listening status report including the MBMS reception quality level. + +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 showing two overlapping MBSFN areas, MBSFN 1 and MBSFN 2. MBSFN 1 is associated with TMGI 1 and MBSFN 2 with TMGI 2. The overlapping region contains cells that belong to both areas. Mobile stations (UEs) are shown moving from MBSFN 1 into the overlapping area and then into MBSFN 2. + +Figure 10.7.3.7.2-1: Two MBMS bearer using overlapping MBSFN areas + +The procedural steps will work as follows: + + + +Sequence diagram showing the interaction between an MC service client (UE) and an MC Service Server. The steps are: 1. UE is located in MBSFN area 1 and receives MC service media over TMGI 1; 2. MBMS listening status report; 3. UE moves to overlapping area between MBSFN 1 and MBSFN 2; 4. Location information report; 5. MBMS bearer announcement; 6. MBMS listening status report; 7. Simultaneous MC service media over both MBMS bearers (TMGI 1 and TMGI 2); 8. UE moves into a new cell only in MBSFN area 2; 9. MBMS listening status report; 10. MC service media received only over TMGI 2. + +Figure 10.7.3.7.2-2: Service continuity when moving from one MBSFN to another + +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 MC service client notifies the MC service server that it is successfully receiving the MC service media over TMGI 1. The MC service client may also notify the MBMS reception quality level of TMGI 1. + +NOTE: The MBMS reception quality level may be used by the MC service server to make an efficient decision to switch to another MBMS bearer or to a unicast bearer, or to take measures to prepare such a switch (e.g. when the quality level indicates that the reception quality of the MBMS bearer is decreasing or reaching an insufficient quality level for the reception of MC services). + +3. 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. +4. The MC service client sends a location information report to the MC service server. For that, the UE uses the SAI information found in the system information block (SIB) transmitted by the radio cells. +5. The MC service server sends to the MC service client a MBMS bearer announcement with information related to TMGI 2 (if the MC service server had not done it before). Hence, the MC service client knows that TMGI 2 transmits the same MC service media. +6. The MC service client notifies the MC service server that it is successfully receiving TMGI 1 and TMGI 2. The MC service client may also notify the MBMS reception quality level per TMGI. +7. The MC service client may receive the MC service media over both MBMS bearers, i.e. TMGI 1 and TMGI 2. The MC service client may also verify that it is the same content sent on both bearers. The duplicated packets may also be used to perform error corrections. +8. The UE moves into a new cell in MBSFN area 2, where only TMGI 2 is active. +9. The MC service client notifies the MC service server that it is successfully receiving the MC service media over TMGI 2. The MC service client may also notify the MBMS reception quality level of TMGI 2. +10. The MC service client receives the MC service media only over TMGI 2. + +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), as described in steps 4-6 above. To send the location report and the MBMS listening report by the MC service client to the MC service server 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-3. 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 MBMS bearers (TMGI 1 and TMGI 2) using overlapping MBSFN areas (MBSFN 1 and MBSFN 2) with a separate MC application signalling bearer (TMGI 9). The diagram shows a grid of hexagonal cells. Cells on the left are blue and labeled 'TMGI 1 MBSFN 1'. Cells on the right are orange and labeled 'TMGI 2 MBSFN 2'. A central vertical strip of cells is shaded with a blue grid pattern and labeled 'TMGI 9 MBSFN 1+2'. Three mobile device icons are shown: one in a blue cell, one in a grid cell, and one in an orange cell, with arrows pointing to each. + +**Figure 10.7.3.7.2-3: 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. + + + +The diagram illustrates a mobile network scenario. A large circle represents the overall network coverage, with an inner dashed circle representing the MBMS coverage area. Outside the dashed circle but inside the outer circle is a region labeled 'Unicast coverage'. Inside the dashed circle are four base station icons. UE A is shown at three positions: first, inside the dashed circle; second, in the unicast coverage area; and third, outside the outer circle. A red double-headed arrow connects the first UE A position to a UE-R (User Equipment Relay) icon. Another red double-headed arrow connects the UE-R icon to the second UE A position. A black arrow points from the second UE A position to the third UE A position, indicating movement. + +Diagram showing UE A moving from MBMS coverage to outside the network coverage, passing through a unicast-only area with UE-R relays. + +**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. + + + +The sequence diagram shows the interaction between three entities: MC service client, UE-R, and MC service server. + 1. The MC service client performs an 'Estimation of the MBMS bearer quality'. + 2. The MC service client sends a message 'Discovery and connection to UE-R' to the UE-R. + 3. A horizontal bar spanning all three entities represents the 'Normal service continuity procedure'. + 4. The MC service client sends a message 'Inform the UE-R about the reception of media over MBMS bearer.' to the UE-R. + 5. A horizontal bar spanning all three entities represents 'UE-R relay the media received over MBMS bearer.' + +Sequence diagram showing service continuity over MBMS bearer using UE-to-network relay with steps: 1. Estimation of MBMS bearer quality, 2. Discovery and connection to UE-R, 3. Normal service continuity procedure, 4. Inform UE-R about media reception, 5. UE-R relay media. + +**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 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 + + + +``` +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 + MC service client->>MC service server: 3. MBMS suspension indication + MC service client->>MC service server: 4. MBMS suspension report +``` + +The diagram is a sequence diagram with three lifelines: MC service client, Radio access network, and MC service server. The sequence of messages is as follows: 1. MC service server sends an arrow labeled '1. MBMS suspension reporting instruction' to the MC service client. 2. A self-message on the Radio access network lifeline is labeled '2. RAN suspend MBMS'. 3. The MC service client sends an arrow labeled '3. MBMS suspension indication' to the MC service server. 4. The MC service client sends an arrow labeled '4. MBMS suspension report' to the MC service server. + +Sequence diagram for MBMS suspension notification from MC service client + +**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. + + + +``` + +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 + + 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 + MC service server 1->>MC service server 2: 5. Media distribution request + MC service server 2-->>MC service server 1: 6. Media distribution request response + Note over all participants: 7. Group communication session via the bearer is established + MC service client 2->>MC service server 1: 8. Uplink media + MC service server 1->>MC service client 1: 9. Media + MC service server 1->>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), and MC service client 2. The process involves evaluating multicast applicability, discovering bearers, announcing bearers, establishing a group communication session, and distributing media via uplink and downlink. + +**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. + + + +``` + +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 right of 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 server 2->>MC service client 2: 6b. Media distribution request + MC service client 2-->>MC service server 2: 7b. Media distribution request response + + Note right of MC service server 1: 8a. Media + Note right of MC service server 2: 8b. Media + MC service server 1->>MC service server 2: 9. Media to be broadcasted + MC service server 2->>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, broadcasting 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. + + + +``` + +sequenceDiagram + participant MC service client + participant EPS (BM-SC) + participant MC service server + + Note right of EPS: 3. MBMS session setup procedures and MBMS resources allocation in RAN + + MC service server->>EPS: 1. Activate MBMS bearer request + EPS-->>MC service server: 2. Activate MBMS bearer response + EPS->>MC service server: 4. MBMS bearer event notification + Note over MC service client, MC service server: 5. MC service server starts to use the MBMS bearer + Note right of EPS: 6. Event received from RAN related to the MBMS session + EPS->>MC service server: 7. MBMS bearer event notification + Note over MC service client, 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]. + + + +``` + +sequenceDiagram + participant MC service client + participant BM-SC + participant MC service server + Note left of MC service client: Pre-condition: MBMS Bearer activated + MC service server->>BM-SC: 1. Setup FEC request + BM-SC-->>MC service server: 2. Setup FEC response + BM-SC->>MC service client: 3. MBMS Bearer announcement + MC service server->>MC service client: 4. Signaling group communication session over the MBMS bearer + MC service server->>BM-SC: 5. DL payload media + BM-SC->>MC service client: 6. DL payload media with FEC + 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 messages 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 MC service server 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 from 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 medias 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. + +**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. + + + +``` + +sequenceDiagram + participant MC service client + participant MC service server + Note right of MC service server: 2. Media distribution + Note right of MC service server: 3. FEC encoding of media + MC service server->>MC service client: 1. MBMS bearer announcement + MC service server->>MC service client: 4. DL Media with FEC + Note left of MC service client: 5. FEC decoding of media + +``` + +Sequence diagram showing the application of FEC by the MC service server. The diagram involves two main participants: MC service client and MC service server. The sequence of steps is: 1. MBMS bearer announcement from server to client; 2. Media distribution from server; 3. FEC encoding of media from server; 4. DL Media with FEC from server to client (indicated by a large arrow); 5. FEC decoding of media at the client. + +**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. + + + +``` + +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 left of Client: 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 is: 1. MBMS Bearer announcement (Server to Client), 2. Signaling group communication session over the MBMS bearer (Server to Client), 3. Media distribution (Server internal), 4. Header compression (Server internal), 5. DL Media (Server to Client), 6. Header decompression (Client internal). + +**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]. + + + +``` + +sequenceDiagram + participant MCSC as MC service client + participant BMSC as BM-SC + participant MSS as MC service server + Note left of MCSC: 7. Header decompression + MSS->>BMSC: 1. Setup ROHC request + BMSC-->>MSS: 2. Setup ROHC response + MSS->>MCSC: 3. MBMS Bearer announcement + MSS->>MCSC: 4. Signaling group communication session over the MBMS bearer + Note right of MCSC: 5. DL media + Note left of MCSC: 6. DL header compressed media + MSS->>MCSC: 5. DL media + MSS->>MCSC: 6. DL header compressed media + +``` + +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 messages 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 MC service client; 6. DL header compressed media from MC service server to MC service client; 7. Header decompression performed by 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. + +#### 10.7.3.13 Use of MBMS bearer for group status + +The MCPTT server may use the MBMS bearer to inform the status of a group (indicating the group call is on-going or not) when the group call is set up on unicast bearers. The affiliated clients that will perform late entry chat group calls or rejoin calls may use this group status information to decide whether to join the calls. The information flows for group status notification is specified in subclause 10.7.2.12. + +## 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. This information flow is sent individually addressed on unicast or multicast. + +**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 Void + +#### 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. This information flow is sent individually addressed on unicast or multicast. + +**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 Void + +#### 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. This information flow is sent individually addressed on unicast or multicast. + +**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. This information flow is sent individually addressed on unicast or multicast. + +**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.2.14 Notify group dynamic data request + +Table 10.8.2.14-1 describes the information flow notify group dynamic data request from the MC service server to the group management server. + +**Table 10.8.2.14-1: Notify group dynamic data request** + +| Information element | Status | Description | +|--------------------------------------|--------|--------------------------------------------------------------------------------------------------------------------------| +| MC service group ID | M | The MC service group ID to which the GMS has subscribed and for which the group dynamic data needs to be updated. | +| MC service ID | M | The MC service ID for which the group dynamic data (e.g. affiliation status, de-affiliation status) needs to be updated. | +| Affiliation or de-affiliation status | M | Indicates the affiliation status or de-affiliation status for the MC service group ID. | + +### 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 group(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; and +5. The group management server has subscribed to the MC service server within the MC system where the group is defined for affiliation status updates. + + + +``` + +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.Notify group dynamic data request + +``` + +Sequence diagram illustrating the MC service group 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 group affiliation request from client to server; 2a. Subscribe group policy from server to group management server; 2b. Notify group policy from group management server to server; 3. Authorization check based on group policy, user subscription and N2 limit check (internal to server); 4. Store group affiliation status (internal to server); 5a. MC service group affiliation response from server to client; 5b. Notify group dynamic data request from server to 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; and +6. The group management server has subscribed to the MC service server within the MC system where the group is defined for affiliation status updates. + + + +``` + +sequenceDiagram + participant Client as MC service Client + participant PrimaryServer as Primary MC service server + participant PartnerServer as Partner MC service server + participant GroupManagementServer 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->>GroupManagementServer: 4a.Subscribe group policy + GroupManagementServer-->>PartnerServer: 4b.Notify group policy + PartnerServer->>PrimaryServer: 7a.MC service group affiliation response + PrimaryServer->>GroupManagementServer: 7b.Notify group dynamic data request + PrimaryServer->>Client: 9.MC service group affiliation response + +``` + +Sequence diagram showing the affiliation process for an MC service group. Lifelines: MC service Client, Primary MC service server, Partner MC service server, Group management server. The process involves a request from the client to the primary server, an authorization check, a request from the primary server to the partner server, a policy subscription and notification between the partner server and the group management server, an authorization check and status storage on the partner server, a response from the partner server to the primary server, a status storage on the primary server, and a final response from the primary server to the client. + +**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. + + + +``` + +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 system gateway 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 home MC system gateway 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 host MC service 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 illustrating Group affiliation to an MC service group defined in partner MC system using topology hiding. The diagram shows interactions between MC service client 1, Serving MC service server, Serving MC system gateway server, Group home MC system gateway server, and Group host MC service server across two systems: Serving MC system of MC service client 1 and Group home system of MC service group. + +**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. The group host MC service server shall update the GMS with the affiliation status of the user for the requested MC service group by sending the notify group dynamic data request (not shown in the figure). + 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; and + +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. + +3. The group management server has subscribed to the MC service server within the MC system where the group is defined for affiliation status updates. + + + +``` + +sequenceDiagram + participant Client as MC service client + participant Server as MC service server + participant GMS as Group management server + + Client->>Server: 1. MC service group de-affiliation request + Note over Server: 2. Authorization check based on group policy and user subscription + Note over Server: 3. Remove the MC service group affiliation status + Server-->>Client: 4a. MC service group de-affiliation response + Server->>GMS: 4b. Notify group dynamic data request + +``` + +The diagram illustrates the MC service group de-affiliation procedure. It involves three main entities: MC service client, MC service server, and Group management server. The sequence of interactions is as follows: 1. The MC service client sends a 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. 4. The MC service server provides a de-affiliation response (4a) to the client and sends a notification (4b) to the group management server. Steps 4a and 4b can occur in any order or in parallel. + +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; and +2. The group management server has subscribed to the MC service server within the MC system where the group is defined for affiliation status updates. + + + +``` + +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. Notify group dynamic data request + 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. Lifelines: MC service client, Primary MC service server, Partner MC service server, Group management server. The process involves a request from the client to the primary server, authorization checks at both primary and partner servers, removal of affiliation at the partner server, and a final response back to the client. A notification to the group management server occurs in parallel with the response from the partner server. + +**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; and +3. The group management server has subscribed to the MC service server within the MC system where the group is defined for affiliation status updates. + + + +``` +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. Notify group dynamic data request + 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. Notify group dynamic data request (MC service server to Group management server); 4. MC service group de-affiliation notification (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; and + +4. The group management server has subscribed to the MC service server within the MC system where the group is defined for affiliation status updates. + + + +``` + +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. Notify group dynamic data request + 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 illustrating the MC service server initiated group de-affiliation from group in partner system procedure. The diagram shows interactions between MC service client, Primary MC service server, Partner MC service server, and Group management server. + +**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: + +1. 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; +2. 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; and +3. The group management server has subscribed to the MC service server within the MC system where the group is defined for affiliation status updates. + + + +``` + +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. Notify group dynamic data request + 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 illustrating the procedure for remotely changing MC service group affiliation in mandatory 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); 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 (internal to server); 5. Store group affiliation status (internal to server); 6. Notify group dynamic data request 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. + + + +``` + +sequenceDiagram + participant C1 as MC service client 1 +(Authorized user 1) + participant PS as Primary MC service server + participant GMS as Group management server + participant C2 as MC service client 2 +(Target user 2) + + C1->>PS: 1. MC service group affiliation change request + Note over PS: 2. Authorization check based on user subscription +and limit check + PS->>C2: 3. MC service group affiliation change request + Note over C2: 4. Notify group affiliation change to +MC service user and get agreement +from the user + C2-->>PS: 5. MC service group affiliation change response + PS-->>C1: 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). + +**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: + +1. 1. 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; +2. 2. 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; +3. 3. The partner MC service server may have retrieved the group related information from the group management server; +4. 4. 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; and +5. 5. The partner group management server has subscribed to the MC service server within the MC system where the group is defined for affiliation status updates. + + + +``` + +sequenceDiagram + participant C1 as MC service client 1 (Authorized user 1) + participant PS as Primary MC service server + participant PS2 as Partner MC service server 2 (Group host server) + participant GMS as Partner Group management server + participant C2 as MC service client 2 (Target MCPTT user 2) + + C1->>PS: 1. MC service group affiliation change request + Note over PS: 2. Authorization check based on subscription and limit check + PS->>PS2: 3. MC service group affiliation change request + PS2->>GMS: 4a. Subscribe group policy + GMS-->>PS2: 4b. Notify group policy + Note over PS2: 5. Authorization check based on group policy + Note over PS2: 6. Update group affiliation status + PS2->>PS: 7. MC service group affiliation change response + PS2->>GMS: 8. Notify group dynamic data request + Note over PS: 9. Update group affiliation status + PS->>C2: 10a. MC service group affiliation change request + C2-->>PS: 10b. MC service group affiliation change response + PS->>C1: 11. MC service group affiliation change response + +``` + +Sequence diagram for Figure 10.8.5.2.1-1: Remote change MC service group affiliation defined in partner MC system – mandatory mode. The diagram shows the interaction between five entities: 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 sends the MC service group affiliation change response to the primary MC service server. + 8. 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). +- 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. This information flow may be sent individually addressed or group addressed on unicast or multicast (see subclause 10.7.3.4.1). + +**Table 10.9.2.1-1: Location reporting configuration** + +| Information element | Status | Description | +|----------------------------------------------|-------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------| +| MC service ID or MC service group ID | M | Identity of the MC service user or MC service group to which the location reporting configuration is targeted. | +| Requested non-emergency location information | O (see NOTE) | Identifies what location information is requested, except for emergency or imminent peril calls or emergency alerts | +| Requested emergency location information | O (see NOTE) | Identifies what location information is requested, for emergency or imminent peril calls or emergency alerts | +| Triggering criteria in non-emergency cases | O (see NOTE) | Identifies when the location management client will send the location report in non-emergency cases | +| Minimum time between consecutive reports | O (see NOTE) | Defaults to 0 if absent and 0 for emergency calls, imminent peril calls and emergency alerts | +| Triggering criteria in emergency cases | O (see NOTE) | Identifies when the location management client will send the location report in emergency cases | +| 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) | +| Functional alias(es) (see NOTE) | O | Functional alias that corresponds to the MC service ID. | +| Triggering event | M | Identity of the event that triggered the sending of the report | +| Location Information | M | Location information of the individual MC service user | +| NOTE: | Each functional alias corresponds to an individual MC service ID. | | + +#### 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 | +| Functional alias(es) | O | Requested functional alias(es) of the MC service users. | + +#### 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
(see NOTE 1) | Identity of the requesting authorized MC service user (e.g. MCPTT ID, MCVideo ID, MCData ID) | +| MC service ID | O
(see NOTE 1)
(see NOTE 3) | Identity of the requested MC service user (e.g. MCPTT ID, MCVideo ID, MCData ID) | +| Functional alias | O
(see NOTE 3) | Functional alias that corresponds to the requested MC service user (e.g. MCPTT ID, MCVideo ID, MCData ID). | +| Immediate Report Indicator | O
(see NOTE 2) | Indicates whether an immediate location report is required | +| Requested non-emergency location information | O
(see NOTE 2) | Identifies what location information is requested, except for emergency or imminent peril calls or emergency alerts | +| Requested emergency location information | O
(see NOTE 2) | Identifies what location information is requested, for emergency or imminent peril calls or emergency alerts | +| Triggering criteria in non-emergency cases | O
(see NOTE 2) | Identifies when the client will send the location report in non-emergency cases | +| Triggering criteria in emergency cases | O
(see NOTE 2) | Identifies when the client will send the location report in emergency cases | +| Minimum time between consecutive reports | O
(see 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. | | | +| NOTE 3: Either the MC service ID or the functional alias must 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 or location management client 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 (see NOTE) | Indicates the interval time between consecutive reports | +| NOTE: If the interval time has a value of zero then the location management server will send the Location information notification immediately the location information report is received from the MC service user in the MC service ID list. | | | + +#### 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 | 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 IDs (e.g. MCPTT ID, MCData ID, MCVideo ID) 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 information of another MC service user (see 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 when the location management server sends location information notification to the MC service user who has subscribed the location information. | | | + +#### 10.9.2.8 Location information cancel subscription request + +Table 10.9.2.8-1 describes the information flow from the MC service server or location management client to the location management server for location information cancel subscription request. + +**Table 10.9.2.8-1: Location information cancel 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 IDs (e.g. MCPTT ID, MCData ID, MCVideo ID) of the MC service users for whom location information is no longer required. | + +#### 10.9.2.9 Location information cancel subscription response + +Table 10.9.2.9-1 describes the information flow from the location management server or the location management client to the MC service server for location information cancel subscription response. + +**Table 10.9.2.9-1: Location information cancel subscription response** + +| Information element | Status | Description | +|---------------------|--------|--------------------------------------------| +| MC service ID | M | Identity of the requesting MC service user | +| Subscription status | M | Indicates the subscription result | + +#### 10.9.2.10 Location report response + +Table 10.9.2.10-1 describes the information flow from the location management server to the requesting location management client for the location information reporting when using functional alias. This information flow combines individually recorded location information reports of the all involved location management clients. + +**Table 10.9.2.10-1: Location report response** + +| Information element | Status | Description | +|-----------------------------------------------------------------------------------------------------------------------------------|--------|----------------------------------------------------------------------------------------------| +| Combined set of MC service IDs | M | List of identities of the reporting MC service users (e.g. MCPTT ID, MCVideo ID, MCData ID). | +| Functional alias | O | Functional alias that corresponds to the MC service IDs. | +| Triggering event | M | Identity of the event that triggered the sending of the report. | +| Set of Location Information (see NOTE) | M | List of location information for the corresponding functional alias and its MC service ID. | +| NOTE: This is the location information corresponding to the MC service and the respective associated functional alias if present. | | | + +### 10.9.3 Procedure + +#### 10.9.3.1 Event-triggered location reporting procedure + +NOTE 1: This procedure is valid for single MC system operation only. + +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. The conditions could include, for example, 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 SAIs, geographic coordinates and other location information. + + + +``` + +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' back to the server. 3. Location management client sends 'Location Information Report' to the 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 2: 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 3: 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 + +NOTE: This procedure is valid for single MC system operation only. + +The location management server can request MC service 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. + + + +``` +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 +``` + +The diagram shows a sequence of interactions between a 'Location management Server' and a 'Location management client'. The process starts with the server deciding to initiate a location request (Step 1). It then sends a 'Location Information Request' to the client (Step 2). The client notifies the user and asks for permission to share location (Step 3). The client responds with a 'Location Information Report' (Step 4). Finally, the server updates the location information (Step 5). + +Sequence diagram illustrating 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 immediate request of location information to be sent 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 for permission to share location information. 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, the location management server just stores the reporting location information for that location management client. + +#### 10.9.3.3 Client-triggered location reporting procedure + +NOTE: This procedure is valid for single MC system operation only. + +Figure 10.9.3.3-1 illustrates the high level procedure of client-triggered location reporting. + + + +``` +sequenceDiagram + participant Client2 as Location management client 2 + participant Server as Location management server + participant Client1 as Location management client 1 + Note right of Server: 2. Event-triggered location reporting procedure or on-demand location reporting procedure + Client2->>Server: 1. Location reporting trigger + Note right of Server: 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 horizontal arrow labeled '1. Location reporting trigger' points from Client 2 to the Server. Below the Server lifeline, a rectangular box contains the text '2. Event-triggered location reporting procedure or on-demand location reporting procedure', indicating the server's subsequent action. + +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 + +NOTE: This procedure is valid for single MC system operation only. + +The location reporting cancel procedure reuses the information flow of location reporting configuration. + +Pre-conditions: + +- The location management client has been provided with location reporting configuration information. + + + +``` +sequenceDiagram + participant Server as Location management server + participant Client as Location management client + Note right of Client: 2. stop location report + Server->>Client: 1. Location Reporting Configuration + Note right of Client: 2. stop location report +``` + +The diagram illustrates the location reporting cancel procedure. It features two lifelines: 'Location management server' and 'Location management client'. A horizontal arrow labeled '1. Location Reporting Configuration' points from the Server to the Client. Below the Client lifeline, a rectangular box contains the text '2. stop location report', indicating the client's subsequent action. + +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 + +NOTE: This procedure is valid for single MC system operation only. + +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. + + + +``` + +sequenceDiagram + participant Client as MC service server or Location management client + participant Server as Location management server + Note right of Server: 2. Authorization check + Client->>Server: 1. Location information subscription request + Server-->>Client: 3. Location information subscription response + +``` + +Sequence diagram for Figure 10.9.3.5-1: Location information subscription request procedure. It shows three steps: 1. MC service server or Location management client sends a request to the Location management server; 2. The server performs an authorization check; 3. The server sends a response back to the requester. + +Figure 10.9.3.5-1: Location information subscription request procedure + +1. MC service server or location management client 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 checks 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 + +NOTE 1: This procedure is valid for single MC system operation only. + +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. + + + +``` + +sequenceDiagram + participant Server as Location management server + participant Client as MC service server or Location management client + Note left of Server: 1. Based on configurations and subscription to report location information + Server->>Client: 2. Location information notification + +``` + +Sequence diagram for Figure 10.9.3.6.1-1: Event-trigger usage of location information procedure. It shows two steps: 1. The Location management server triggers a report based on configurations and subscription; 2. The server sends a location information notification to the MC service server or Location management client. + +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 sends the location information report including the latest location information of one or more MC service users to the MC service server or location management client. The latest location information is derived from the location report procedure as described in clause 10.9.3.1, or from PLMN operator (e.g. LCS network). + +NOTE 2: For other entities, the step 3 can be skipped if not needed. + +##### 10.9.3.6.2 On-demand usage of location information procedure + +NOTE: This procedure is valid for single MC system operation only. + +The MC service server or the location management client can request location information at any time by sending a location information request to the location management server, which may trigger location management server to send the location information report immediately. + +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 other entities that would like to subscribe to location information at the location management server of an MC service user. + + + +``` +sequenceDiagram + participant Client as MC service server or Location management client + participant Server as Location management server + Note right of Server: 2. Authorization check + Note right of Server: 3. Get the latest location information + Client->>Server: 1. Location Information request + Server-->>Client: 4. Location Information report +``` + +Sequence diagram illustrating the on-demand usage of location information procedure. The diagram shows two lifelines: 'MC service server or Location management client' on the left and 'Location management server' on the right. The sequence of messages is: 1. Location Information request (from left to right), 2. Authorization check (internal to the right lifeline), 3. Get the latest location information (internal to the right lifeline), and 4. Location Information report (from right to left). + +**Figure 10.9.3.6.2-1: On-demand usage of location information procedure** + +1. MC service server or location management client sends a location information request to the location management server. +2. The location management server checks if the MC service server or location management client is authorized to request the location information. +3. The location management server acquires the latest location of the MC service clients being requested, by triggering an on-demand location report procedure as described in clause 10.9.3.2, or from PLMN operator (e.g. LCS network). +4. Then, location management server immediately sends the location information report including the latest location information acquired of one or more MC service users. + +#### 10.9.3.7 Location information cancel subscription procedure + +NOTE: This procedure is valid for single MC system operation only. + +Figure 10.9.3.7-1 illustrates the high level procedure of location information cancel subscription request. The same procedure can be applied for location management client and other entities that would like to cancel their subscription to MC service user location information. + + + +``` + +sequenceDiagram + participant A as MC service server or Location management client + participant B as Location management server + Note left of A: Error! No text of specified style in + A->>B: 1. Location information cancel subscription request + B-->>A: 2. Location Information cancel subscription response + +``` + +Sequence diagram for Figure 10.9.3.7-1 showing the location information cancel subscription request procedure between an MC service server/location management client and a location management server. + +**Figure 10.9.3.7-1: Location information cancel subscription request procedure** + +1. MC service server or location management client sends a location information cancel subscription request to the location management server to cancel the subscription for location information of one or more MC service users. +2. The location management server replies with a location information cancel subscription response indicating the cancel subscription status. + +#### **10.9.3.8 Location management using functional alias** + +##### **10.9.3.8.1 Client-triggered one-time location information report** + +Figure 10.9.3.8.1-1 illustrates the procedure when a location management client requests one-time location information from other location management clients for location information reporting using functional alias, which can be shared between several MC service users. Under this condition, the actual location of all MC service users sharing the same functional alias are contained in the one-time location report. + +Pre-conditions: + +1. MC service client 2 and MC service client 3 share the same functional alias. +2. MC service client 2 and MC service client 3 activated the functional alias. +3. MC service client 1 may have an activated functional alias. +4. The MC service server has subscribed to the functional alias controlling MC service server within the MC system for functional alias activation/de-activation updates. + + + +``` + +sequenceDiagram + participant A as Location management client 1 + participant B as Location management server + participant C as Location management client 2 + participant D as Location management client 3 + Note left of A: Error! No text of specified style in + A->>B: 1. Location reporting trigger + B->>C: 2. Authorization check + Note right of B: 3a. On-demand location reporting procedure + Note right of B: 3b. On-demand location report + +``` + +Sequence diagram for Figure 10.9.3.8.1-1 showing the one-time location information report procedure for a shared functional alias among three clients and a server. + +**Figure 10.9.3.8.1-1: One-time location information report for shared functional alias** + +1. Location management client 1 sends a location reporting trigger, limited to one MC service at the time, to the location management server to activate a one-time location report procedure which shall retrieve the location information of the MC service users that may share the contained functional alias. Location management client 1 may include its own activated functional alias. +2. Location management server checks whether location management client 1 is authorized to send a location reporting trigger. +3. The location management server uses on-demand location reporting procedures. The location information request contains the functional alias used by the location management client 1 to address location management client 2 and location management client 3. +4. Upon receiving the report, the location management server updates location of the reporting location management clients. If the location management server does not have location information of a reporting location management client before, then just stores the reporting location information for that location management client. +5. The location management server sends a location report response to location management client 1 containing the provided location information from location management client 2 and location management client 3. If not all location management clients immediately respond to the location management server, i.e. others report some time later, subsequent location reporting responses may be sent. + +##### 10.9.3.8.2 Client-triggered periodic location information report + +Figure 10.9.3.8.2-1 illustrates the procedure when a location management client requests periodic location information from other location management clients for location information reporting using functional aliases which may be shared between several MC service users. Under this condition, the actual location of all MC service users sharing the same functional alias are contained in the periodic location report. + +Pre-conditions: + +1. MC service client 2 and MC service client 3 share the same functional alias. +2. MC service client 2 and MC service client 3 activated the functional alias. +3. MC service client 1 may have an activated functional alias. +4. The MC service server has subscribed to the functional alias controlling MC service server within the MC system for functional alias activation/de-activation updates. + + + +``` + +sequenceDiagram + participant Client1 as Location management client 1 + participant Server as Location management server + participant Client2 as Location management client 2 + Note left of Client1: Pre-conditions + Client1->>Server: 1. Location reporting trigger + Note right of Server: 2. Authorization check + Note right of Server: 3a. Event triggered location reporting procedure + Note right of Server: 3b. Event triggered location report + +``` + +Sequence diagram showing the interaction between Location management client 1, Location management server, and Location management client 2. The steps are: 1. Location reporting trigger from client 1 to server; 2. Authorization check by server; 3a. Event triggered location reporting procedure; 3b. Event triggered location report. + +Figure 10.9.3.8.2-1: Periodic location information report for shared functional alias + +1. Location management client 1 sends a location reporting trigger, limited to one MC service at the time, to the location management server to activate a periodic location reporting procedure which shall retrieve the location information of the MC service users sharing the contained functional alias. Location management client 1 may include its own activated functional alias. +2. Location management server checks whether location management client 1 is authorized to send a location reporting trigger. +3. Depending on the information given by the location reporting trigger, the location management server uses event-triggered location information procedure and immediately send location information request to the location management clients that contains the functional alias requested by the location management client 1. +4. Upon receiving the reports, the location management server updates location of the reporting location management clients. +5. Based on the received location information reports, the location management server will periodically issue a location report response encompassing the MC service IDs, the associated functional aliases and the individual location information of the addressed MC service IDs. + +NOTE 1: If a functional alias is deactivated for an MC service client, the corresponding location management client stops sending periodic location information reports. + +NOTE 2: If a functional alias has been newly activated for an MC service client, the location management server activates location information reporting for this location management client. + +NOTE 3: If a functional alias is simultaneously shared between several MC service IDs, all location management clients with the associated MC service IDs will send the location report until the functional alias status change, e.g. take-over, for the individual MC service ID. + +## 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 to be used for emergency communications by MC service client 1 is previously defined on the group management server and MC service client 2 and MC service client 3 are affiliated to that MC service group. + +NOTE 2: Alternatively, the client could have been provisioned for emergency behaviour on the currently selected 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 may not have carried out an explicit affiliation procedure with the MC service group designated as the MC service 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. + + + +``` + +sequenceDiagram + participant Client1 as MC service client 1 + participant Server as MC service server + participant GroupMgmt 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 + Client1->>Server: 2. MC service emergency alert request + Note right of Server: 3. Check alert authorization + Note right of Server: 4. Resolve group ID + Server-->>Client1: 5. MC service emergency alert response + Note right of Server: 6. MC service emergency alert request + Note right of Client2: 7. Notify emergency alert + Note right of Client3: 7. Notify emergency alert + Client2-->>Server: 8. MC service emergency alert response + Client3-->>Server: 8. MC service emergency alert response + Note right of 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, and subsequent alert requests to clients 2 and 3. A dashed box labeled '9. Affiliate to group' is shown between the server and group management server. + +**Figure 10.10.1.2.1-1 MC service emergency alert** + +1. The MC service 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 user at MC service client 1 may select a functional alias used for the call. The MC service emergency state is retained by the MC service client 1 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. The MC service server checks whether the provided functional alias, if present, can be used and has been activated for the user. +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 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 user profile configuration) and the MC service user's mission critical organization name. If in step 2, the MC service client 1 does not include the location information in the MC service emergency alert request to the MC service server, the MC service server acquires the location information of the MC service user at the MC service client 1 from the location management server. If the location information is included in step 2, then the MC service server uses the location information from MC service client 1. +7. MC service users are notified of the MC service emergency alert. The functional alias of the group call initiating MC service user may be displayed. +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. + +NOTE 6: It is configured whether MC service client 1 automatically triggers a subsequent 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. + + + +``` + +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 + rect rgb(255, 255, 255) + Server->>GroupServer: 3. Resolve group ID + GroupServer-->>Server: + end + 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 alert cancel + Note right of Client3: 6. Notify emergency alert 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 sending an 'initiate emergency alert cancel' message to the server. The server responds with 'MC service emergency alert cancel request' to the group management server, which returns 'Resolve group ID'. The server then sends 'MC service emergency alert cancel response' to client 1. Next, the server sends 'MC service emergency alert cancel request' to clients 2 and 3. Clients 2 and 3 respond with 'Notify emergency alert cancel'. Finally, the server sends 'MC service emergency alert cancel response' to clients 2 and 3. + +**Figure 10.10.1.2.2-1 MC service emergency alert cancel** + +1. The MC service 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. For a unicast MC service emergency alert cancel, 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 MC service emergency alert cancel, these acknowledgements are not sent unless the MC service clients have been configured to do so. + +##### 10.10.1.2.3 Entering MC service emergency alert area + +**Editor's Note:** MC service emergency alert triggered by MC service client locally which stores the pre-defined 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 MC service emergency alert to be triggered when an MC service UE moves into a pre-defined area. 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.3-1 are the signalling control plane procedures for the MC service server triggering 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. 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. + +NOTE: 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 service system. +3. An area in which the MC service client should send emergency alert is pre-defined in MC service server. + + + +``` + +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 right of MC service server: 1. Acquire latest location information of user at MC service client 1 + MC service server->>MC service server: 2. Check whether MC service client 1 has moved into a predefined area + Note right of MC service server: 3. MC service emergency alert area notification + MC service server->>MC service client 1: 3. MC service emergency alert area notification + Note left of MC service client 1: 4. Notify user + Note over MC service client 1, MC service server, Group management server, MC service client 2, MC service client 3: 5. MC service emergency alert initiation procedure + +``` + +Sequence diagram illustrating the procedure for entering an MC service emergency alert area. The diagram shows interactions between MC service client 1, MC service server, Group management server, MC service client 2, and MC service client 3. The steps are: 1. MC service server acquires location info from Group management server; 2. MC service server checks if client 1 is in a predefined area; 3. MC service server sends an emergency alert area notification to client 1; 4. client 1 notifies its user; 5. client 1 initiates the emergency alert procedure. + +Figure 10.10.1.2.3-1 Entering MC service emergency alert area + +1. MC service server acquires the latest location information of user at MC service client 1 from location management server as described in 10.9.3.6. +2. MC service server checks whether MC service client 1 has moved into a pre-defined area. +3. If so, MC service server sends an MC service emergency alert area notification to MC service client 1 to notify that it has moved into the area in potential danger. +4. MC service client 1 notifies the MC service user about the MC service emergency alert area. +5. MC service client 1 initiates MC service emergency alert procedure as described in 10.10.1.2.1. + +##### 10.10.1.2.4 Leaving MC service emergency alert area + +This procedure focuses on the case where a notification is sent when an MC service UE moves out of a pre-defined area. This procedure will notify the MC service client that it is now out of the pre-defined emergency alert area. It is up to the MC service user at that MC service client to determine if the emergency state is to be cleared or not. + +Procedures in figure 10.10.1.2.4-1 are the signalling control plane procedures for the MC service server sends an MC service emergency alert area notification. It is optional if the MC service user wants to initiate the MC service emergency alert cancel procedure to inform the members in the MC service group that **its emergency condition is over**. + +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 MCPTT client 3 affiliated to that MC service group. This MC service group has been pre-defined for communicating the emergency alert in the user profile. +2. All members of the MC service group belong to the same MC service system. +3. An area in which the **emergency alert for the** MC service client should remain active is pre-defined in MC service server. + + + +``` +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 right of MC service server: 1. Acquire latest location information of user at MC service client 1 + Note right of MC service server: 2. Check whether MC service client 1 has moved out a predefined area + MC service server->>MC service client 1: 3. MC service emergency alert area notification + Note left of MC service client 1: 4. Notify user + Note right of MC service client 3: 5. MC service emergency alert cancel procedure +``` + +Sequence diagram illustrating the process of leaving an MC service emergency alert area. The diagram shows interactions between MC service client 1, MC service server, Group management server, MC service client 2, and MC service client 3. The process involves acquiring location information, checking if the user has moved out of a predefined area, sending a notification, notifying the user, and optionally initiating a cancel procedure. + +**Figure 10.10.1.2.4-1 Leaving MC service emergency alert area** + +1. MC service server acquires the latest location information of user at MC service client 1 from location management server as described in subclause 10.9.3.6. +2. MC service server checks whether MC service client 1 has moved out a pre-defined area. +3. If so, MC service server sends an MC service emergency alert area notification to MC service client 1 to notify that it has moved out of the area in potential danger. +4. MC service client 1 notifies the MC service user about the MC service emergency alert area cancel. It is up to the MC service user at the MC service client 1 to determine if the emergency state is clear. +5. Optionally, the MC service user of MC service client 1 initiates MC service emergency alert cancel procedure as described in 10.10.1.2.2. + +NOTE 2: It is up to the MC service user to clear the local emergency state on the client after the MC service UE has moved out of the emergency alert area, the MC service server cannot clear the client's local emergency state. + +### 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 clients 2 and 3 belong to and are ready for off-network communications on the MC service group. + + + +``` +sequenceDiagram + participant Client1 as MC service client 1 (Originator) + participant Client2 as MC service client 2 + participant Client3 as MC service client 3 + + Note left of Client1: 1. User initiates MC service emergency alert + Client1->>Client2: 2. MC service emergency alert announcement + Client1->>Client3: 2. MC service emergency alert announcement + Note right of Client2: 3. Notify MC service emergency alert + Note right of Client3: 3. Notify MC service emergency alert + Client2->>Client1: 4. Response + Client3->>Client1: 4. Response + Note left of Client1: 5. Check participants +``` + +The diagram is a sequence diagram showing the interaction between three MC service clients: MC service client 1 (Originator), MC service client 2, and MC service client 3. The process starts with a note on the left lifeline: "1. User initiates MC service emergency alert". An arrow labeled "2. MC service emergency alert announcement" goes from Client 1 to both Client 2 and Client 3. On the right lifelines, there are notes: "3. Notify MC service emergency alert". Arrows labeled "4. Response" go from Client 2 and Client 3 back to Client 1. Finally, a note on the left lifeline says "5. Check participants". + +Sequence diagram illustrating the emergency alert initiation process between three MC service clients. + +Figure 10.10.2.2.1-1: Emergency alert initiation + +1. 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. + +2. MC service client 1 sends an MC service emergency alert announcement to the other participants on the MC service emergency group. 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. + +3. MC service users are notified of the MC service emergency state of the originating MC service user. + +4. 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 needs 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. + +NOTE 5: It is configured if MC service client 1 will automatically trigger a subsequent MC service emergency group call. + +5. 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. The initiating MC service client 1 and MC service clients 2 and 3 are still in off-network contact via the MC service group provisioned to MC service client 1 as for the MC service emergency group. + + + +``` + +sequenceDiagram + participant Client1 as MC service client 1 (Originator) + participant Client2 as MC service client 2 + participant Client3 as MC service client 3 + Note left of Client1: 1. User initiates MC service emergency alert cancel + Client1->>Client2: 2. MC service emergency alert cancel announcement + Client1->>Client3: 2. MC service emergency alert cancel announcement + Note right of Client2: 3. Notify MC service emergency alert cancel + Note right of Client3: 3. Notify MC service emergency alert cancel + Client2->>Client1: 4. Response + Client3->>Client1: 5. Response + +``` + +Sequence diagram for Emergency alert cancel. Lifelines: MC service client 1 (Originator), MC service client 2, and MC service client 3. The process involves: 1. User initiates MC service emergency alert cancel; 2. MC service emergency alert cancel announcement from client 1 to clients 2 and 3; 3. Notify MC service emergency alert cancel from clients 2 and 3; 4. Response from client 2 to client 1; 5. Response from client 3 to client 1. + +**Figure 10.10.2.2.2-1 Emergency alert cancel** + +1. The user at the MC service client 1 initiates an MC service emergency alert cancel. +2. 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. +3. MC service users are notified of the MC service emergency alert cancellation by MC service client 1. +4. 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 1: A group call can consist of both unicast and multicast bearers which can all need modification due to the same event. + +NOTE 2: The MC service server can retry the establishment of a media bearer upon failure based on information received, or other conditions. + +### 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 illustrating the resource request at session establishment. The diagram shows four lifelines: MC service client, EPS (PCRF), SIP core, and MC service server. The sequence of messages is: 1. Session establishment (MC service client to MC service server); 2. MC service server evaluates need for network resources and media sharing (internal to MC service server); 3. Session progress - request for resources (MC service server to SIP core); 4. PCC procedures (as defined in 3GPP TS 23.203 [4]) (SIP core to EPS (PCRF)); 5. Session progress (EPS (PCRF) to MC service client); 6. ok (MC service client to SIP core); 7. ok (SIP core to MC service server); 8. MC service call/session using unicast bearer established (SIP core to MC service client).](bb3063a33c89b248574f64b6d8dfc404_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 + MC service client->>MC service server: 1. Session establishment + MC service server->>SIP core: 3. Session progress - request for resources + SIP core->>EPS (PCRF): 4. PCC procedures (as defined in 3GPP TS 23.203 [4]) + EPS (PCRF)->>MC service client: 5. Session progress + MC service client->>SIP core: 6. ok + SIP core->>MC service server: 7. ok + Note left of MC service client: 8. MC service call/session using unicast bearer established + +``` + +Sequence diagram illustrating the resource request at session establishment. The diagram shows four lifelines: MC service client, EPS (PCRF), SIP core, and MC service server. The sequence of messages is: 1. Session establishment (MC service client to MC service server); 2. MC service server evaluates need for network resources and media sharing (internal to MC service server); 3. Session progress - request for resources (MC service server to SIP core); 4. PCC procedures (as defined in 3GPP TS 23.203 [4]) (SIP core to EPS (PCRF)); 5. Session progress (EPS (PCRF) to MC service client); 6. ok (MC service client to SIP core); 7. ok (SIP core to MC service server); 8. MC service call/session using unicast bearer established (SIP core to MC service client). + +**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; + + + +``` + +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 + + Note right of MC service server: 1. Media bearer modification decision + MC service server->>SIP core: 2. Session update – Resource modification request + Note over EPS (PCRF), SIP core: 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 showing interactions between MC service client, EPS (PCRF), SIP core, and MC service server. + +**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. + + + +``` + +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 (internal to MC service server), 2. Call control Bearer modification request (MC service server to SIP core), 3. PCC Bearer modification (SIP core to EPS (PCRF)), 4. OK (EPS (PCRF) to SIP core), 5. PCC updates the priority for the bearer (internal to EPS (PCRF)), 6. Call control Bearer modification request (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 + + + +``` + +sequenceDiagram + participant MC service client + participant EPS (PCRF) + participant SIP core + participant MC service server + + Note left of MC service client: 1. Group affiliation request + MC service client->>MC service server: 1. Group affiliation request + Note left of MC service client: 2. Session Establishment + MC service client->>SIP core: 2. Session Establishment + Note right of SIP core: 3. Session establishment + SIP core->>MC service server: 3. Session establishment + Note left of SIP core: 4. Request for resource for transmission control + SIP core->>EPS (PCRF): 4. Request for resource for transmission control + Note left of MC service client: 5. Session establishment + SIP core->>MC service client: 5. Session establishment + Note left of MC service client: 6. Call setup + MC service client->>MC service server: 6. Call setup + Note left of MC service server: 7. Request for resources for media bearers + MC service server->>EPS (PCRF): 7. Request for resources for media bearers + Note center: 8. Group call ongoing + Note left of MC service server: 9. Release of resources for media bearers + 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. + + + +``` + +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 C as MC service clients + + Note left of S1: 1. Need for elevated MC priority level identified + S1->>S2: 2. MC priority request + Note right of S2: 3. Priority decision based on requested priority + S2->>S1: 4. MC priority granted + S2->>S3: 5. MC Priority taken + Note left of S1: 6. MC service communication with elevated priority + S1->>C: 7c. Elevated priority notification + S2->>C: 7a. Elevated priority notification + S3->>C: 7b. Elevated priority notification + Note left of 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 the interaction between 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 the arbitrator, receiving a grant, notifying server 3, communicating with elevated priority, and finally releasing the priority when the need ceases. + +**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 Active functional alias information user query request + +Table 10.13.2.1-1 describes the information flow for the active functional alias information user query request from the MC service client to the MC service server. + +**Table 10.13.2.1-1: Active functional alias information user query request** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------------------| +| MC service ID | M | The identity of the MC service user who performs the query. | +| MC service ID(s) | M | The identity of the MC service user(s) to be queried. | + +#### 10.13.2.1a Active functional alias information usage query request + +Table 10.13.2.1a-1 describes the information flow for the active functional alias information usage query request from the MC service client to the MC service server. + +**Table 10.13.2.1a-1: Active functional alias information usage query request** + +| Information element | Status | Description | +|----------------------|--------|-------------------------------------------------------------| +| MC service ID | M | The identity of the MC service user who performs the query. | +| Functional alias(es) | M | A list of functional alias(es) to be queried. | + +#### 10.13.2.2 Active functional alias information user query response + +Table 10.13.2.2-1 describes the information flow for the active functional alias information user query response from the MC service server to the MC service client. This information flow is sent individually addressed on unicast or multicast. + +**Table 10.13.2.2-1: Active functional alias information user query response** + +| Information element | Status | Description | +|---------------------|--------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MC service ID | M | The identity of the MC service user who performs the query. | +| MC service ID(s) | M | The identity of the MC service user(s) to be queried. | +| Query result | M | The active functional alias information retrieved from the MC service server for each of the MC service user(s) queried; or Null if no functional alias is active for the MC service user. | + +##### 10.13.2.2a Active functional alias information usage query response + +Table 10.13.2.2a-1 describes the information flow for the active functional alias information usage query response from the MC service server to the MC service client. This information flow is sent individually addressed on unicast or multicast. + +**Table 10.13.2.2a-1: Active functional alias information usage query response** + +| Information element | Status | Description | +|----------------------|--------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MC service ID | M | The identity of the MC service user who performs the query. | +| Functional alias(es) | M | The functional alias(es) to be queried. | +| Query result | M | The list of MC service ID(s) of the MC service user(s) who have activated the functional alias being queried; or Null if this functional alias is not active for any 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. This information flow is sent individually addressed on unicast or multicast. + +**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. This information flow is sent individually addressed on unicast or multicast. + +**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. This information flow may be sent individually addressed or group addressed on unicast or multicast (see subclause 10.7.3.4.1). + +**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. This information flow is sent individually addressed on unicast or multicast. + +**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. This information flow is sent individually addressed on unicast or multicast. + +**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.2.11 Subscribe functional alias request + +Table 10.13.2.11-1 describes the information flow subscribe functional alias request from the MC service server to the functional alias controlling MC service server, and from the location management server to the functional alias controlling MC service server. + +**Table 10.13.2.11-1: Subscribe functional alias request** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------------------| +| Functional alias | M | The functional alias for which subscription is requested. | +| Subscription type | M | Indicates the subscription is for one-time notification or continuous notification. | + +#### 10.13.2.12 Subscribe functional alias response + +Table 10.13.2.12-1 describes the information flow subscribe functional alias response from the functional alias controlling MC service server to the MC service server, and from the functional alias controlling MC service server to the location management server. + +**Table 10.13.2.12-1: Subscribe functional alias response** + +| Information element | Status | Description | +|---------------------|--------|-----------------------------------------------------------| +| Functional alias | M | The functional alias for which subscription is requested. | +| Status | M | Success or failure of the request | + +#### 10.13.2.13 Notify functional alias request + +Table 10.13.2.13-1 describes the information flow notify functional alias request from the functional alias controlling MC service server to the MC service server, and from the functional alias controlling MC service server to the location management server. + +**Table 10.13.2.13-1: Notify functional alias request** + +| Information element | Status | Description | +|----------------------------------------------------|--------|-----------------------------------------------------------------------| +| Functional alias | M | The functional alias for which subscription is requested. | +| List of MC service IDs (see NOTE) | M | The list of MC service IDs that is activated for the functional alias | +| NOTE: The MC service ID list can be an empty list. | | | + +#### 10.13.2.14 Notify functional alias response + +Table 10.13.2.14-1 describes the information flow notify functional alias response from the MC service server to the functional alias controlling MC service server, and from the location management server to the functional alias controlling MC service server. + +**Table 10.13.2.14-1: Notify functional alias response** + +| Information element | Status | Description | +|---------------------|--------|-----------------------------------------------------------------------------------------------------------| +| Functional alias | M | The functional alias for which a list of MC service users who activate the functional alias is requested. | + +#### 10.13.2.15 Unsubscribe functional alias request + +Table 10.13.2.15-1 describes the information flow unsubscribe functional alias request from the MC service server to the functional alias controlling MC service server, and from the location management server to the functional alias controlling MC service server. + +**Table 10.13.2.15-1: Unsubscribe functional alias request** + +| Information element | Status | Description | +|---------------------|--------|---------------------------------------------------------------------------| +| Functional alias | M | The functional alias for which subscription is requested to be cancelled. | + +#### 10.13.2.16 Unsubscribe functional alias response + +Table 10.13.2.16-1 describes the information flow unsubscribe functional alias response from the functional alias controlling MC service server to the MC service server, and from the functional alias controlling MC service server to the location management server. + +**Table 10.13.2.16-1: Unsubscribe functional alias response** + +| Information element | Status | Description | +|---------------------|--------|---------------------------------------------------------------------------| +| Functional alias | M | The functional alias for which subscription is requested to be cancelled. | +| Status | M | Success or failure of the request | + +### 10.13.3 Authorised MC service user retrieves active functional alias(es) for certain MC service user(s) + +An authorised MC service user can request the active functional alias(es) for one or more MC service users. + +Figure 10.13.3-1 below illustrates the active functional alias list query for the MC service user(s). + + + +``` + +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. Active function alias information user query request + MC service server-->>MC service client: 3. Active function alias information user query response + +``` + +Sequence diagram showing the active functional alias list query process between an MC service client and an MC service server. + +**Figure 10.13.3-1: Active functional alias list query for the user** + +1. The MC service client of the MC service user requests the list(s) of active functional aliases for each MC service user(s) from the MC service server by sending an active functional alias information user query request. The MC service ID(s) to be queried 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(s). +3. The MC service server sends an active functional alias information user query response including the 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. + + + +``` + +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 to MC service server); 3. Store functional alias(es) status (internal to 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. + +NOTE 1: If the MC service server is not the one that performs the functional alias controlling role, the MC service server will forward the request to the MC service server that performs the functional alias controlling role. + +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). + +NOTE 2: The functional alias status is notified to other servers (e.g. MC service servers) within the MC system that have subscribed to functional alias status. + +- 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. + + + +``` + +sequenceDiagram + participant Client as MC service client + participant Server as MC service server + participant OtherClients as Other MC service client(s) + Note right of Server: 2. Authorization check based on functional alias(es) policy, user subscription etc. + Note right of Server: 3. Store functional alias(es) status + Client->>Server: 1. Functional alias(es) de-activation request + Server-->>Client: 4. Functional alias(es) de-activation response + Server->>OtherClients: 5. Functional alias(es) status notification + +``` + +Sequence diagram showing the functional alias de-activation procedure. Lifelines: MC service client, MC service server, and Other MC service client(s). The process involves: 1. Request from client to server, 2. Internal authorization check, 3. Internal status store, 4. Response from server to client, 5. Notification from server to other clients. + +**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. + +NOTE 1: If the MC service server is not the one that performs the functional alias controlling role, the MC service server will forward the request to the MC service server that performs the functional alias controlling role. + +- 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. + +NOTE 2: The functional alias status is notified to other servers (e.g. MC service servers) within the MC system that have subscribed to functional alias status. + +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. + + + +``` + +sequenceDiagram + participant C1 as MC service client 1 + participant S as MC service server + participant C2 as MC service client 2 + participant OC as Other MC service client(s) + + C1->>S: 1. Functional alias take over request + Note over S: 2. Authorization check based on functional alias(es) policy, user subscription etc. + S->>C2: 3. Functional alias revoke notification + Note over S: 4. Store functional alias(es) status + S->>C1: 5. Functional alias take over response + S->>OC: 6. Functional alias(es) status notification + +``` + +Sequence diagram showing the functional alias take over procedure. 1. MC service client 1 sends a 'Functional alias take over request' to the MC service server. 2. The server performs an 'Authorization check based on functional alias(es) policy, user subscription etc.' 3. The server sends a 'Functional alias revoke notification' to MC service client 2. 4. The server performs 'Store functional alias(es) status'. 5. The server sends a 'Functional alias take over response' back to MC service client 1. 6. The server sends a 'Functional alias(es) status notification' to 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. + +NOTE 1: If the MC service server is not the one that performs the functional alias controlling role, the MC service server will forward the request to the MC service server that performs the functional alias controlling role. + +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. + +NOTE 2: The functional alias status is notified to other servers (e.g. MC service servers) within the MC system that have subscribed to functional alias status. + +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.13.7 Authorised MC service user retrieves MC service user(s) for certain active functional alias(es) + +An authorised MC service user can request the MC service user(s) who have activated the functional alias being queried, for one or more functional aliases. + +Figure 10.13.7-1 below illustrates the query of usage of the active functional alias(es) procedure. + + + +``` + +sequenceDiagram + participant Client as MC service client + participant Server as MC service server + Note right of Server: 2. Authorization check and retrieve according to the conditions + Client->>Server: 1. Active function alias information usage query request + Server-->>Client: 3. Active function alias information usage query response + +``` + +Sequence diagram showing the interaction between an MC service client and an MC service server. The client sends a request, the server performs an authorization check and retrieval, and then sends a response. + +**Figure 10.13.7-1: Query of usage of the active functional alias(es)** + +1. The MC service client of the MC service user requests the list(s) of MC service user(s) who have activated the functional alias being queried, by sending an active functional alias information usage query request. The functional alias(es) to be queried are 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 MC service user(s) information for those MC service users who have activated the functional alias being queried. +3. The MC service server sends an active functional alias information usage query response including the MC service user information to the MC service client. + +### 10.13.8 Automatic activation of functional alias(es) within an MC system + +The MC Service Server can automatically activate functional aliases that can be specified by internal or external triggers such as location dependency, schedule, or timer. + +The procedure for automatic activation of functional alias(es) within an MC system is illustrated in figure 10.13.8-1. The MC service client(s) get(s) notified by the MC service server at the time when a functional alias has been activated by the MC service server. + +Pre-conditions: + +1. MC service server may have retrieved the MC service user subscription and functional alias policy, for example, which MC service user(s) are authorized to activate which functional alias(es), to use corresponding priorities and other configuration data associated with the functional alias. +2. MC service server has already been provisioned with the functional alias(es) information that the MC service client is allowed to activate. + + + +``` + +sequenceDiagram + participant MC service client + participant MC service server + participant Other MC service client(s) + + Note right of MC service server: 1. Internal or external trigger condition e.g. timer or location of the MC service user is met + Note right of MC service server: 2. Checks conflicts with any activated functional alias(es) + MC service server->>MC service client: 3. Functional alias(es) activation notification + Note right of MC service server: 4. Store functional alias(es) status + MC service server->>Other MC service client(s): 5. Functional alias(es) status notification + +``` + +Sequence diagram illustrating automatic functional alias activation within an MC system. The diagram shows three lifelines: MC service client, MC service server, and Other MC service client(s). The process starts with a trigger on the server, followed by a conflict check, a notification to the client, a status store, and a final notification to other clients. + +**Figure 10.13.8-1: Automatic functional alias activation within an MC system** + +1. The condition e.g. timer or current location of the MC service user for automatic functional alias(es) activation is met. +2. The MC service server checks if there are any conflicts with current active functional alias(es). + - a.) If a certain functional alias(es) can be simultaneously active for multiple MC service users and the upper limit of simultaneous MC service users is not reached, the MC service server shall activate the functional alias(es) for the corresponding MC service user and inform all other MC service user(s) that are sharing the same functional alias(es) (step 5). + - b.) If the limit of simultaneous MC service users is reached or the functional alias is not allowed to be shared then the MC service server does not proceed with the functional alias(es) activation procedure or the MC service server can reassign the functional alias, i.e. takeover, from the MC service user currently using the functional alias(es) to the new MC service client. +3. MC service server notifies the MC service client about the activation of the functional alias(es). +4. The MC service server stores the functional alias(es) status for the functional alias(es), including date and time of activation. +5. The MC service server informs all other MC service user(s) sharing the same functional alias(es). + +### 10.13.9 Automatic deactivation of functional alias(es) within an MC system + +The MC Service Server can automatically activate functional aliases that can be specified by internal or external triggers such as location dependency, schedule, or timer. + +The procedure for automatic deactivation of functional alias(es) within an MC system is illustrated in figure 10.13.9-1. The MC service client(s) get(s) notified by the MC service server at the time when a functional alias has been deactivated by the MC service server. + +Pre-conditions: + +1. MC service server has already retrieved the relevant functional alias(es) information from the configuration (functional alias) management server and has stored the data of the concerning functional alias(es) a MC service user has activated. + + + +``` + +sequenceDiagram + participant MC service client + participant MC service server + participant Other MC service client(s) + Note right of MC service server: 1. Internal or external trigger condition e.g. timer or location of the MC service user is met + MC service server->>MC service client: 2. Functional alias(es) deactivation notification + Note right of MC service server: 3. Store functional alias(es) status + MC service server->>Other MC service client(s): 4. Functional alias(es) status notification + +``` + +Sequence diagram for automatic functional alias deactivation within an MC system. Lifelines: MC service client, MC service server, Other MC service client(s). Steps: 1. Internal or external trigger condition e.g. timer or location of the MC service user is met (on MC service server); 2. Functional alias(es) deactivation notification (from MC service server to MC service client); 3. Store functional alias(es) status (on MC service server); 4. Functional alias(es) status notification (from MC service server to Other MC service client(s)). + +**Figure 10.13.9-1: Automatic functional alias deactivation within an MC system** + +1. The condition e.g. timer or current location of the MC service user for automatic functional alias(es) deactivation is met. The trigger for deactivation may be done by the MC system or by an authorized external system attached to the MC system. +2. MC service server notifies the MC service client about the deactivation of the functional alias(es). +3. The MC service server stores the status, e.g. deactivated, of the concerned functional alias(es) and the corresponding MC service ID(s). +4. The MC service server informs all other MC service user(s) sharing the same functional alias(es). + +### 10.13.10 Subscription and notification for functional alias + +#### 10.13.10.1 General + +The MC service server obtains the list of MC service users who have activated a functional alias from the functional alias controlling MC service server via subscription and notification mechanisms. + +The procedures in this subclause are also applicable for the location management server to subscribe a functional alias from the functional alias controlling server to obtain the list of MC service users who have activated the functional alias. + +#### 10.13.10.2 Subscription for functional alias procedure + +The procedure for subscription for functional alias is described in figure 10.13.10.2-1. + +Pre-conditions: + +- The functional alias controlling MC service server holds a list of MC service users who has activated the functional alias. + + + +``` + +sequenceDiagram + participant MC service server + participant (Functional alias controlling) MC service server + MC service server->>(Functional alias controlling) MC service server: 1. Subscribe functional alias request + (Functional alias controlling) MC service server-->>MC service server: 2. Subscribe functional alias response + +``` + +Sequence diagram for subscription for functional alias. Lifelines: MC service server, (Functional alias controlling) MC service server. Steps: 1. Subscribe functional alias request (from MC service server to (Functional alias controlling) MC service server); 2. Subscribe functional alias response (from (Functional alias controlling) MC service server to MC service server). + +**Figure 10.13.10.2-1: Subscription for functional alias** + +1. The MC service server sends a subscribe functional alias request to the functional alias controlling MC service server in order to receive notifications about the list of MC service users who has activated the function alias. +2. The functional alias controlling MC service server provides a subscribe functional alias response to the MC service server indicating success or failure of the request. + +#### 10.13.10.3 Notification for functional alias procedure + +The procedure for notification for functional alias as shown in figure 10.13.10.3-1 is used by the functional alias controlling MC service server to inform the MC service server about MC service users who activate of the functional alias. + +Pre-conditions: + +- The MC service server has subscribed to the functional alias +- The list of MC service users who has activated the functional alias is changed at functional alias controlling MC service server due to activation, deactivation or taken over. + + + +``` +sequenceDiagram + participant MC service server + participant (Functional alias controlling) MC service server + Note left of MC service server: + MC service server->>(Functional alias controlling) MC service server: 1. Notify functional alias request + (Functional alias controlling) MC service server-->>MC service server: 2. Notify functional alias response +``` + +The diagram shows a sequence of two messages between the MC service server and the (Functional alias controlling) MC service server. The first message, '1. Notify functional alias request', is sent from the (Functional alias controlling) MC service server to the MC service server. The second message, '2. Notify functional alias response', is sent from the MC service server to the (Functional alias controlling) MC service server. + +Sequence diagram for Notification for functional alias procedure + +**Figure 10.13.10.3-1: Notification for the functional alias** + +1. The functional alias controlling MC service server provides the list of MC service users who has activated the functional alias in the notify functional alias request to the MC service server. +2. The MC service server provides a notify functional alias response to the functional alias controlling MC service server. + +#### 10.13.10.4 Unsubscription for functional alias procedure + +The procedure for unsubscription for functional alias is described in figure 10.13.10.4-1. + +Pre-conditions: + +- The functional alias controlling MC service server holds a list of MC service users who has activated the functional alias. + + + +``` +sequenceDiagram + participant MC service server + participant (Functional alias controlling) MC service server + MC service server->>(Functional alias controlling) MC service server: 1. Unsubscribe functional alias request + (Functional alias controlling) MC service server-->>MC service server: 2. Unsubscribe functional alias response +``` + +The diagram shows a sequence of two messages between the MC service server and the (Functional alias controlling) MC service server. The first message, '1. Unsubscribe functional alias request', is sent from the MC service server to the (Functional alias controlling) MC service server. The second message, '2. Unsubscribe functional alias response', is sent from the (Functional alias controlling) MC service server to the MC service server. + +Sequence diagram for Unsubscription for functional alias procedure + +**Figure 10.13.10.4-1: Unsubscription for functional alias** + +1. The MC service server sends a unsubscribe functional alias request to the functional alias controlling MC service server in order to stop receiving notifications about the list of MC service IDs who has activated the function alias. +2. The functional alias controlling MC service server provides a subscribe functional alias response to the MC service server indicating success or failure of the request. + +## 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 'Serving MC system of MC service client 1' and 'Partner MC system'. Lifelines include MC service client 1, Serving MC service server, Serving MC system MC gateway server, Partner MC system MC gateway server, Partner MC service server, and MC service client 2. The sequence of messages is: 1. Call request (client 1 to serving server), 2. Determine target MC service server (internal to serving system), 3. Call request (serving server to serving gateway), 4. Determine partner MC system for target for call (internal to serving gateway), 5. Call request (serving gateway to partner gateway), 6. Determine partner MC service server (internal to partner gateway), 7. Call request (partner gateway to partner server), 8. Authorization check (internal to partner system), 9. Call request (partner server to client 2), 10. Call response (client 2 to partner server), 11. Call response (partner server to partner gateway), 12. Call response (partner gateway to serving gateway), 13. Call response (serving gateway to serving server), 14. Call response (serving server to client 1). A final bar labeled '15. Establish floor/transmission control and media paths' spans across all lifelines. + +**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. + +2. MC service client 1 has affiliated to the MC service group. + + + +``` + +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 + Note right of Serving MC service server: 2. Authorize group call request using local configuration + Serving MC service server->>Group host MC service server: 3. Group call request + Note right of Group host MC service server: 4. Authorize group call request using group configuration + Group host MC service server->>Serving MC service server: 5. Group call response + Serving MC service server->>MC service client 1: 6. Group call response + 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 an 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** + +1. 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. +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 forwards the group call request to the group host MC service server in the primary MC system of the MC service group. +4. 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. +5. 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. +6. The serving MC service server sends the MC service group call response to MC service client 1. +7. 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: + +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: 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. + + + +``` + +sequenceDiagram + participant Group host MC service server as Group host MC service server + participant Serving MC service server as Serving MC service server + participant MC service client 1 as MC service client 1 + Note right of Serving MC service server: 2. Authorize group call request using local configuration + Group host MC service server->>Serving MC service server: 1. Group call request + Serving MC service server->>MC service client 1: 3. Group call request + MC service client 1-->>Serving MC service server: 4. Group call response + Serving MC service server-->>Group host MC service server: 5. Group call response + Note left of Group host MC service server: 6. Establish floor/transmission control and media paths + +``` + +Sequence diagram illustrating the enforcement of local configuration for a group call request. The diagram shows three lifelines: 'Primary MC system of MC service group' (containing 'Group host MC service server'), 'Serving MC system of MC service client 1' (containing '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 message 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 message to Group host MC service server). + +**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. + + + +``` + +sequenceDiagram + participant MC client 1 as MC service client 1 + participant Group host server as Group host MC service server + participant Serving server as Serving MC service server + participant MC client 2 as MC service client 2 + participant MC client 3 as MC service client 3 + participant MC client n as MC service client n + + Note over MC client 1, MC client n: 1. Group call setup and floor/transmission control and media paths established + MC client 1->>Group host server: 2. Floor grant + MC client 1->>Group host server: 3a. Media flow + Group host server->>Serving server: 3b. Media flow + Note over MC client 2, MC client n: 3c. Media flow + +``` + +Sequence diagram illustrating media replication in a partner MC system. The diagram shows two systems: 'Primary MC system of MC service group' and 'Partner MC system of MC service group'. In the primary system, MC service client 1 sends a request to the Group host MC service server. The server responds with a floor grant. The client then sends a media flow to the server. The server replicates this media flow to the Serving MC service server in the partner system. Finally, the serving server distributes the media flow to MC service clients 2, 3, and n in the partner system. + +**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],
[R-6.4.3-001],
[R-6.4.3-002],
[R-6.9-004] and
[R-5.1.3-002] of
3GPP TS 22.280 [3] | MC service group ID | Y | Y | Y | +| [R-5.17-004],
[R-6.4.3-001],
[R-6.4.3-002] and
[R-6.9-004] of
3GPP TS 22.280 [3] | Group Alias (Contact URIs) | Y | Y | Y | +| | List of group members (see NOTE 1)
(see NOTE 8) | | | | +| [R-5.1.3-001],
[R-5.1.5-001],
[R-6.4.5-005] and
[R-6.4.5-006] of
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
[R-7.6-007] of
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 | +| [R-5.1.3-001],
[R-5.1.5-001],
[R-6.4.5-005] and
[R-6.4.5-006] of
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
[R-7.6-007] of
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 | +| [R-5.1.3-001],
[R-5.1.5-001],
[R-6.4.5-005] and
[R-6.4.5-006] of
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
[R-7.6-007] of
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 | +| [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 | +| Subclause 10.6.2.9 of 3GPP TS 23.379 [16] | Group is a preconfigured regroup group | Y | Y | Y | +| [R-5.2.1-002] of 3GPP TS 22.280 [3] | Group is a broadcast group | Y | 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 (also known as KMSUri for security domain managed by KMS) | +| | > Indication of whether the UE shall use IPv4 or IPv6 for on-network MCPTT | +| | > MCPTT Server | +| | >> Server URI | +| | > Indication of whether the UE shall use IPv4 or IPv6 for on-network MCData | +| | > MCData Server | +| | >> Server URI | +| | > Indication of whether the UE shall use IPv4 or IPv6 for on-network MCVideo | +| | > MCVideo Server | +| | >> Server URI | +| | > Location management server | +| | >> Server URI | + +# 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. + + + +The diagram illustrates the network architecture for service continuity. A yellow box represents the core network containing the MME, PCRF, SGW/PGW, MBMS GW, and BM-SC. The MME is connected to the eNB via S1-MME, to the PCRF via S11, and to the SGW/PGW via S1-U. The PCRF is connected to the SGW/PGW via Gx. The SGW/PGW is connected to the SIP core via SGi. The MBMS GW is connected to the eNB via M1 and to the BM-SC via SG-imb and SG-mb. The eNB is connected to the UE-1 (MCPTT client) via Uu. The SIP core is connected to the MCPTT AS and the SCC AS. The SCC AS is connected to the MCPTT AS. The diagram shows two states: the initial state where UE-1 is connected directly to the network (solid lines) and the state after a handover where UE-1 is connected via a UE-R (dashed lines). The handover is indicated by a downward arrow next to the UE-1. + +Figure B.1-1: Service continuity from on-network to UE-to-network relay. The diagram shows a network architecture with a UE-1 (MCPTT client) connected to an eNB, which is part of a core network containing MME, PCRF, SGW/PGW, MBMS GW, and BM-SC. The eNB is connected to a SIP core, which is connected to an MCPTT AS and an SCC AS. The diagram illustrates two states: the initial state where UE-1 is connected directly to the network (solid lines) and the state after a handover where UE-1 is connected via a UE-R (dashed lines). + +**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. + + + +``` + +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 + SCC->>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; 3. UE-1 registers with the SIP core; 4. UE-1 transfers media streams; 5. UE-1 engaged in UE-to-Network Relay service. Lifelines include 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 + +| 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:
CR0057(S6-160312), CR0063(S6-160189),
CR0065(S6-160362),CR0068(S6-160348),
CR0069(S6-160313), CR0070(S6-160280),
CR0071(S6-160199), CR0079(S6-160360),
CR0080(S6-160297), CR0085(S6-160361),
CR0092(S6-160345), CR0095(S6-160339),
CR0099(S6-160342) | | 0.1.0 | +| 2016-06 | | | | | | Implemented the following pCRs approved in SA6#11:
S6-160378, S6-160489, S6-160492, S6-160504,
S6-160524, S6-160528, S6-160560, S6-160561,
S6-160570, S6-160578, S6-160579, S6-160583,
S6-160600, S6-160601
Also implemented the Rapporteur actions from SA6#11:
1. Removed all colour coding from the TS
2. Fixed the subclauses numbering in the entire TS.
3. Generalized the text as per agreed terminology.
4. Added references for TS 23.303 and TS 23.237 | | 0.2.0 | +| 2016-08 | | | | | | Implemented the following pCRs approved in SA6#12:
S6-160794, S6-160795, S6-160796, S6-160797,
S6-160798, S6-160799, S6-160880, S6-160888,
S6-160919, S6-160920 | | 0.3.0 | +| 2016-09 | | | | | | Implemented the pCR S6-160822 which was approved in SA6#12
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 | +| 2018-09 | SA#81 | SP-180676 | 0151 | 2 | C | Multicast application level control signal clarification | 16.0.0 | +| 2018-12 | SA#82 | SP-181171 | 0153 | 2 | A | Editorial correction of figure in TS 23.280 | 16.1.0 | +| 2018-12 | SA#82 | SP-181172 | 0162 | 1 | A | Removal of notes for FEC and ROHC | 16.1.0 | +| 2018-12 | SA#82 | SP-181177 | 0165 | 4 | C | Proposal for affiliation status information in group management server | 16.1.0 | +| 2018-12 | SA#82 | SP-181177 | 0167 | | C | Spelling of ProSe | 16.1.0 | +| 2018-12 | SA#82 | SP-181177 | 0169 | 2 | F | Align UE configuration with TS 33.180 | 16.1.0 | +| 2018-12 | SA#82 | SP-181177 | 0171 | 1 | B | Regroup group configuration | 16.1.0 | +| 2018-12 | SA#82 | SP-181174 | 0172 | | A | Correcting title of a functional alias management subclause | 16.1.0 | +| 2019-03 | SA#83 | SP-190073 | 0173 | 3 | C | Improvement of the group creation request | 16.2.0 | +| 2019-03 | SA#83 | SP-190073 | 0174 | 2 | B | Broadcast group regroup | 16.2.0 | +| 2019-03 | SA#83 | SP-190073 | 0178 | 1 | B | Group status notification over MBMS | 16.2.0 | +| 2019-03 | SA#83 | SP-190075 | 0179 | 1 | F | Migration connectivity information | 16.2.0 | +| 2019-03 | SA#83 | SP-190071 | 0180 | - | A | Correction of emergency location triggering criteria | 16.2.0 | +| 2019-03 | SA#83 | SP-190073 | 0181 | 4 | B | MBMS listening status report | 16.2.0 | +| 2019-06 | SA#84 | SP-190482 | 0184 | 1 | A | Clarifications on functional alias controlling role | 16.3.0 | +| 2019-06 | SA#84 | SP-190488 | 0185 | 3 | B | Functional alias information query | 16.3.0 | +| 2019-06 | SA#84 | SP-190484 | 0186 | 1 | F | Add location management server URI to initial MC service UE configuration | 16.3.0 | +| 2019-06 | SA#84 | SP-190488 | 0187 | 4 | F | Functional alias alternative addressing for MCX services | 16.3.0 | +| 2019-06 | SA#84 | SP-190488 | 0188 | 1 | B | Implicit functional alias management | 16.3.0 | +| 2019-06 | SA#84 | SP-190484 | 0190 | | F | Corrections to affiliation procedures | 16.3.0 | +| 2019-06 | SA#84 | SP-190484 | 0191 | 3 | F | Affiliation clarifications | 16.3.0 | +| 2019-06 | SA#84 | SP-190484 | 0192 | 1 | C | Preconfigured regroup information in dynamic data | 16.3.0 | +| 2019-06 | SA#84 | SP-190484 | 0194 | 2 | F | Remove the duplicated Key Management Server URI definition | 16.3.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|---|-----------------------------------------------------------------------|--------| +| 2019-06 | SA#84 | SP-190484 | 0196 | 3 | B | Change to Location Subscription for notification immediate | 16.3.0 | +| 2019-06 | SA#84 | SP-190488 | 0201 | 2 | B | Functional alias subscription and notification | 16.3.0 | +| 2019-06 | SA#84 | SP-190488 | 0203 | 3 | B | Location information reporting based on functional alias | 16.3.0 | +| 2019-06 | SA#84 | SP-190488 | 0204 | 2 | F | Functional alias clarifications | 16.3.0 | +| 2019-06 | SA#84 | SP-190484 | 0205 | 2 | F | Abbreviations | 16.3.0 | +| 2019-06 | SA#84 | SP-190484 | 0206 | 2 | F | Clarifications for group regroup rules | 16.3.0 | +| 2019-09 | SA#85 | SP-190731 | 0182 | 4 | C | Configuration of the user notification in temporary group formation | 16.4.0 | +| 2019-09 | SA#85 | SP-190731 | 0210 | 5 | F | Corrections to the emergency alert procedures | 16.4.0 | +| 2019-09 | SA#85 | SP-190731 | 0211 | 3 | F | Corrections to clauses in 10.9 Location Management (on-network) | 16.4.0 | +| 2019-09 | SA#85 | SP-190730 | 0220 | 2 | F | Functional model update for interconnection and migration | 16.4.0 | +| 2019-10 | | | | | | Editorial corrections by MCC | 16.4.1 | +| 2019-12 | SA#86 | SP-191109 | 0227 | 2 | F | Clarifications for location management | 16.5.0 | +| 2021-09 | SA#93 | SP-210960 | 0294 | 3 | F | Clarification of MC service server retry for dedicated bearer request | 16.6.0 | \ No newline at end of file diff --git a/marked/Rel-16/23_series/23281/00504fc688ebcf131ccbeff94dfc9939_img.jpg b/marked/Rel-16/23_series/23281/00504fc688ebcf131ccbeff94dfc9939_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..40bb6ba9a99a5e8120ccfdeccaa744a4ce3e5673 --- /dev/null +++ b/marked/Rel-16/23_series/23281/00504fc688ebcf131ccbeff94dfc9939_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1a20080b9bcf517c48b395851030382d489a8f5835087eae6380bdc77a8567ba +size 88501 diff --git a/marked/Rel-16/23_series/23281/062ad684575a714449a7e040c0e1ec00_img.jpg b/marked/Rel-16/23_series/23281/062ad684575a714449a7e040c0e1ec00_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bd89d532a86220c10a28ed5af5856e5020ecc9d7 --- /dev/null +++ b/marked/Rel-16/23_series/23281/062ad684575a714449a7e040c0e1ec00_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cdc0519b23546787041066f3eebdc7e937213649026f245a0b1bddc61a453136 +size 44127 diff --git a/marked/Rel-16/23_series/23281/0ff19975027a3c5177519975f9af055f_img.jpg b/marked/Rel-16/23_series/23281/0ff19975027a3c5177519975f9af055f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c795e193794518b6e8a7b9cd8ee1a0ae53441b66 --- /dev/null +++ b/marked/Rel-16/23_series/23281/0ff19975027a3c5177519975f9af055f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9f7d7edcb3a7a82ddfdfa72059ac12fe769f8caacaba3d054aa91bff11dc9338 +size 46056 diff --git a/marked/Rel-16/23_series/23281/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/marked/Rel-16/23_series/23281/1a827b10290f33d4fec04d0e8ef7a897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e50c000413740e5fbda05444fe763eff5bedeac1 --- /dev/null +++ b/marked/Rel-16/23_series/23281/1a827b10290f33d4fec04d0e8ef7a897_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8c786dbdc148b56b182fc6137d2fdbfbc76bf9f6430822bedeb9391340684414 +size 82919 diff --git a/marked/Rel-16/23_series/23281/212c50c4e3d043c989037a01e13c1a98_img.jpg b/marked/Rel-16/23_series/23281/212c50c4e3d043c989037a01e13c1a98_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..03ad85c810fb27b22610285ab35f9999a1c8b4d1 --- /dev/null +++ b/marked/Rel-16/23_series/23281/212c50c4e3d043c989037a01e13c1a98_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1df23c44e5cb5608e95f2b31b487db0b824da3608c4a0b2d403aff5b43859729 +size 40897 diff --git a/marked/Rel-16/23_series/23281/2837ffdadcdb1e5bababa56b564e56ed_img.jpg b/marked/Rel-16/23_series/23281/2837ffdadcdb1e5bababa56b564e56ed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6c054beec22a60032a702aef70275fc102f6b941 --- /dev/null +++ b/marked/Rel-16/23_series/23281/2837ffdadcdb1e5bababa56b564e56ed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e58f91a93dae98b411bc29171232a73a99599921140db1d8e09ec3984f80792f +size 77312 diff --git a/marked/Rel-16/23_series/23281/28d75f39a24203712ee907b32cf0bbe5_img.jpg b/marked/Rel-16/23_series/23281/28d75f39a24203712ee907b32cf0bbe5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3f0af90cfb308a65aec1d0cc25839567e7bbe374 --- /dev/null +++ b/marked/Rel-16/23_series/23281/28d75f39a24203712ee907b32cf0bbe5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:933c5a0da911d86b17d54f2bb51062bbc5b91448c9b1def7a0bec3bf487facf8 +size 38788 diff --git a/marked/Rel-16/23_series/23281/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg b/marked/Rel-16/23_series/23281/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ffc5d959836a31c79d70c604fd2e8200710fcb44 --- /dev/null +++ b/marked/Rel-16/23_series/23281/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:32dd5d9f5fb5b8d58518100307d1616de5340f177bbb3e6425c38214fb48bb6a +size 50058 diff --git a/marked/Rel-16/23_series/23281/2f587210e4f97c32758c5972e2e83d20_img.jpg b/marked/Rel-16/23_series/23281/2f587210e4f97c32758c5972e2e83d20_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7af59bb8c8385818d58c4e3b755fc8f0b4e591ca --- /dev/null +++ b/marked/Rel-16/23_series/23281/2f587210e4f97c32758c5972e2e83d20_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/23281/3337af75dfee8af7687b4f49914d6c93_img.jpg b/marked/Rel-16/23_series/23281/3337af75dfee8af7687b4f49914d6c93_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5cebde99f52799feefa77f081d62b0ea93cc55c1 --- /dev/null +++ b/marked/Rel-16/23_series/23281/3337af75dfee8af7687b4f49914d6c93_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2f170c805d8b346a686a140dfe68b02d7ce7099e575ee6269416e9762de0c282 +size 59968 diff --git a/marked/Rel-16/23_series/23281/396197257cf9437b526bb6585b6a9c8a_img.jpg b/marked/Rel-16/23_series/23281/396197257cf9437b526bb6585b6a9c8a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..47d063c07dd896575942f2f5422f83af18de60f5 --- /dev/null +++ b/marked/Rel-16/23_series/23281/396197257cf9437b526bb6585b6a9c8a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7bf2ae3ac8f84de719d1f146023a7fbc49c8944b75ddab30150e68f2052a5677 +size 73400 diff --git a/marked/Rel-16/23_series/23281/3e8e3bdb3d90f0856266d4eaf36abba1_img.jpg b/marked/Rel-16/23_series/23281/3e8e3bdb3d90f0856266d4eaf36abba1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7292656b98464be489cae62cb6068e13db463750 --- /dev/null +++ b/marked/Rel-16/23_series/23281/3e8e3bdb3d90f0856266d4eaf36abba1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f68c9174dc109f6de4eb67ec057f59b393df5a98d825d1059841502cd4c05be8 +size 27512 diff --git a/marked/Rel-16/23_series/23281/5c6787bac31274e2dc992efeca74b303_img.jpg b/marked/Rel-16/23_series/23281/5c6787bac31274e2dc992efeca74b303_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a366d083b45e812aa0fdd5a1284975c4e60be6e4 --- /dev/null +++ b/marked/Rel-16/23_series/23281/5c6787bac31274e2dc992efeca74b303_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ff794c7c7ec6c8699617e6e23d23bb8d4f34b92e2ab8dbf0e92572b2612e0a31 +size 39085 diff --git a/marked/Rel-16/23_series/23281/608f1b5ef8f3dc0723f2b4ea1fb72be2_img.jpg b/marked/Rel-16/23_series/23281/608f1b5ef8f3dc0723f2b4ea1fb72be2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..362b19b8c16ca0317b92ee54155c416470560534 --- /dev/null +++ b/marked/Rel-16/23_series/23281/608f1b5ef8f3dc0723f2b4ea1fb72be2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:064d90fe3fc2ad0b86921836288cca26496f5a63b0a6af036c9a45f56dc6053d +size 32176 diff --git a/marked/Rel-16/23_series/23281/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg b/marked/Rel-16/23_series/23281/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aa2d63a54dac6a48331c14c67080e3b4c6edd5c0 --- /dev/null +++ b/marked/Rel-16/23_series/23281/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0c5d0cc9fc254b7153ad1d92a55a8887ced71fa4e0a283174e4afe646667b6b8 +size 75942 diff --git a/marked/Rel-16/23_series/23281/6984a27b2b89e0995d5216ec29b41d1c_img.jpg b/marked/Rel-16/23_series/23281/6984a27b2b89e0995d5216ec29b41d1c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..42bbde08284d590951d86ff2fcd220e29dff8405 --- /dev/null +++ b/marked/Rel-16/23_series/23281/6984a27b2b89e0995d5216ec29b41d1c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:35b81563d6373e051900db7a3b790039fe70d08350428b5fa1497a4586ffb649 +size 63041 diff --git a/marked/Rel-16/23_series/23281/6e15fc9ea763541c5913d26f85072ae1_img.jpg b/marked/Rel-16/23_series/23281/6e15fc9ea763541c5913d26f85072ae1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9ffdd9c683d776447a94c4ae95517ddbc414cc9f --- /dev/null +++ b/marked/Rel-16/23_series/23281/6e15fc9ea763541c5913d26f85072ae1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8e6585b9c75ba3a4a0e9028270bff22a2b1647ef3eea5c46f0b832b2f94b435b +size 55257 diff --git a/marked/Rel-16/23_series/23281/719ef0f734259484038b2434e5dc3f24_img.jpg b/marked/Rel-16/23_series/23281/719ef0f734259484038b2434e5dc3f24_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..638e52ac5c7490f553de187438c95cff6bb3aee9 --- /dev/null +++ b/marked/Rel-16/23_series/23281/719ef0f734259484038b2434e5dc3f24_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eabf553e284fa327db85dbc7f382973952bf385c4ab10e2cc1e8a9c7b4707c0c +size 81930 diff --git a/marked/Rel-16/23_series/23281/772cc583a60eeb058cc19de48269ad22_img.jpg b/marked/Rel-16/23_series/23281/772cc583a60eeb058cc19de48269ad22_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..664597de1f58c93756860d832f0401a60a53d1f3 --- /dev/null +++ b/marked/Rel-16/23_series/23281/772cc583a60eeb058cc19de48269ad22_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/23281/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg b/marked/Rel-16/23_series/23281/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a9b7d1855f49db69c6b760913c91236612834f63 --- /dev/null +++ b/marked/Rel-16/23_series/23281/78ff716475b2f65bf01c3a4d02d89fc4_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/23281/7d3d5fb5d09c0cd35a9d637be241651e_img.jpg b/marked/Rel-16/23_series/23281/7d3d5fb5d09c0cd35a9d637be241651e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b4c9e7aa0c97980d1cd3bb63d278fc0a6e9f1ceb --- /dev/null +++ b/marked/Rel-16/23_series/23281/7d3d5fb5d09c0cd35a9d637be241651e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d56fe4af8da6ea898f605250fe6bedd390b2006d9c431fe2300957a412ceb077 +size 28802 diff --git a/marked/Rel-16/23_series/23281/7ed5d5770331f31ade15439a21c31425_img.jpg b/marked/Rel-16/23_series/23281/7ed5d5770331f31ade15439a21c31425_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c01def21953980f745e1386fe306a08e57e642ea --- /dev/null +++ b/marked/Rel-16/23_series/23281/7ed5d5770331f31ade15439a21c31425_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/23281/8a94796989f4fcba2688c4faa7991538_img.jpg b/marked/Rel-16/23_series/23281/8a94796989f4fcba2688c4faa7991538_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fdf78f6e8605b00d3bdeb08e89bce6dfebb1a4a4 --- /dev/null +++ b/marked/Rel-16/23_series/23281/8a94796989f4fcba2688c4faa7991538_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6c1512429ef02d3ab24c67e8cd057c80d515d7c022cd5049b22654133a07d7ef +size 53421 diff --git a/marked/Rel-16/23_series/23281/8e80de0cac529b2c3775d677c5203133_img.jpg b/marked/Rel-16/23_series/23281/8e80de0cac529b2c3775d677c5203133_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..59928756266cdff6c4d1aca5ca9ae0663e2399c4 --- /dev/null +++ b/marked/Rel-16/23_series/23281/8e80de0cac529b2c3775d677c5203133_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:19382faed6aca406469ad2ad69bfc200699cf0f708bf29827151427a84a28639 +size 88761 diff --git a/marked/Rel-16/23_series/23281/90ddb84c323b956e2d50a54d3f870566_img.jpg b/marked/Rel-16/23_series/23281/90ddb84c323b956e2d50a54d3f870566_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..681967a38ba21c1e39ec9363592b60902c2b12a1 --- /dev/null +++ b/marked/Rel-16/23_series/23281/90ddb84c323b956e2d50a54d3f870566_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:240b005ba70fe47448ba010bee27b9033f14b16c424a0ef3c1f23304591db75e +size 49838 diff --git a/marked/Rel-16/23_series/23281/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg b/marked/Rel-16/23_series/23281/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6ec63a35f6a3650e5c8b85d233da9ea6c257462e --- /dev/null +++ b/marked/Rel-16/23_series/23281/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2b2d21ef870e4f78bde8c80616e313aa47d81b4b7340c45753c33504df16bcc9 +size 67159 diff --git a/marked/Rel-16/23_series/23281/9c1d3678db4a12d5864cb2a4def1135d_img.jpg b/marked/Rel-16/23_series/23281/9c1d3678db4a12d5864cb2a4def1135d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dbc158013c57fdb23b8f03afde9bf752199ae1aa --- /dev/null +++ b/marked/Rel-16/23_series/23281/9c1d3678db4a12d5864cb2a4def1135d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dde78a8f6a996546dc6c5044e473b78cb19847466fdc913fd4f8a1d4291e3025 +size 41443 diff --git a/marked/Rel-16/23_series/23281/9e8ebf03cae78f4f81b697548c2d7250_img.jpg b/marked/Rel-16/23_series/23281/9e8ebf03cae78f4f81b697548c2d7250_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5a335287e3868dc13bfb69030212f5d78f712fcf --- /dev/null +++ b/marked/Rel-16/23_series/23281/9e8ebf03cae78f4f81b697548c2d7250_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:869b82e9c93a59ebb3d68cd603d849d1cdfee8fbc833cd87685638ef5fada508 +size 52564 diff --git a/marked/Rel-16/23_series/23281/b774dfc5023e15e9c352b97ca25a56d4_img.jpg b/marked/Rel-16/23_series/23281/b774dfc5023e15e9c352b97ca25a56d4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0599c2e30b147fee6a8dc24e1b2bdcfb9b352a06 --- /dev/null +++ b/marked/Rel-16/23_series/23281/b774dfc5023e15e9c352b97ca25a56d4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dac2b1d52b82c652ff40ea824c05ca20ab18c242aafb3728fdd63611eda8ca6b +size 41929 diff --git a/marked/Rel-16/23_series/23281/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg b/marked/Rel-16/23_series/23281/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f701e9f8f6e6002d8471000b84519e7f3bb0b912 --- /dev/null +++ b/marked/Rel-16/23_series/23281/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dbacbb24113155eab75751ec6ca2cd8a0fd8d6a00dcfb145205f7522977855e5 +size 41463 diff --git a/marked/Rel-16/23_series/23281/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg b/marked/Rel-16/23_series/23281/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1826b4811ef8a16e7ca27830db982a5dd5f41b3e --- /dev/null +++ b/marked/Rel-16/23_series/23281/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:daf514e53e9e3e19cae7fb37124efce7c7d6cdf09202a389c83200c440973953 +size 64749 diff --git a/marked/Rel-16/23_series/23281/d78e519e9186d30807342196675fd440_img.jpg b/marked/Rel-16/23_series/23281/d78e519e9186d30807342196675fd440_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5c5841267dfd4bb0fe0f4866df8667aa7e781746 --- /dev/null +++ b/marked/Rel-16/23_series/23281/d78e519e9186d30807342196675fd440_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f5c84bcfdda9edad914d02bfeedc83e95858fb06729a8f0c16da66eaf319889d +size 37095 diff --git a/marked/Rel-16/23_series/23281/d8698aacaeead6dfed9a1e448670a2e4_img.jpg b/marked/Rel-16/23_series/23281/d8698aacaeead6dfed9a1e448670a2e4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..58e70fb1439c2876a8411065973ee3a7b752551f --- /dev/null +++ b/marked/Rel-16/23_series/23281/d8698aacaeead6dfed9a1e448670a2e4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0f20ef206b731ea0106e6a685fd0cebd16815c44aaf00791ce814978ae62db24 +size 52040 diff --git a/marked/Rel-16/23_series/23281/db39acbd11df5eb7e79ab84562fb8f74_img.jpg b/marked/Rel-16/23_series/23281/db39acbd11df5eb7e79ab84562fb8f74_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c5a8059639987d068484d42d559d38e4e6018287 --- /dev/null +++ b/marked/Rel-16/23_series/23281/db39acbd11df5eb7e79ab84562fb8f74_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:73d93771595d8e45679882fdc615860ddba9b1707848d68a2ad6700b8437263b +size 54900 diff --git a/marked/Rel-16/23_series/23281/e05122559f56af5699789b7118d8fe87_img.jpg b/marked/Rel-16/23_series/23281/e05122559f56af5699789b7118d8fe87_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cf5082e7f9aa97a4381ae81875117d9b2a37e5b8 --- /dev/null +++ b/marked/Rel-16/23_series/23281/e05122559f56af5699789b7118d8fe87_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:48f22229fed64f2d56640c0c8780b01dc0d8dec14c15e34939e7f55c2c8fd8cd +size 79759 diff --git a/marked/Rel-16/23_series/23281/f14f0843f9944e61124817d06809d7ad_img.jpg b/marked/Rel-16/23_series/23281/f14f0843f9944e61124817d06809d7ad_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7643a8a4b80c68641d4f2fc2925fb285cc999d6b --- /dev/null +++ b/marked/Rel-16/23_series/23281/f14f0843f9944e61124817d06809d7ad_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7f7efd8790af7a5f54217f270934f54409d9934d9290c68f1e7b5e2e8fddbc71 +size 43224 diff --git a/marked/Rel-16/23_series/23281/raw.md b/marked/Rel-16/23_series/23281/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..adda5f3ee98ec27d26b0c525384bfd55f203b395 --- /dev/null +++ b/marked/Rel-16/23_series/23281/raw.md @@ -0,0 +1,7185 @@ +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 ..... | 17 | +| 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 ..... | 18 | +| 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) ..... | 19 | +| 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)..... | 20 | +| 6.3.8 Reference point MCVideo-10 (between the MC gateway server and the MC gateway server in a different MCVideo system)..... | 20 | + +| | | | +|-------------|---------------------------------------------------------------------|----| +| 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 join request (MCVideo client – MCVideo server)..... | 23 | +| 7.1.2.2.11 | Group 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.12a | Group call leave request (MCVideo client – MCVideo server)..... | 24 | +| 7.1.2.2.13 | Group call leave response (MCVideo client – MCVideo server)..... | 24 | +| 7.1.2.2.13a | Group call leave response (MCVideo server – MCVideo client)..... | 25 | +| 7.1.2.2.14 | MCVideo emergency alert request..... | 25 | +| 7.1.2.2.15 | MCVideo emergency alert response ..... | 25 | +| 7.1.2.2.16 | MCVideo emergency alert cancel request ..... | 26 | +| 7.1.2.2.17 | MCVideo emergency alert cancel response..... | 26 | +| 7.1.2.2.18 | MCVideo emergency group call request..... | 26 | +| 7.1.2.2.19 | MCVideo emergency group call response ..... | 27 | +| 7.1.2.2.20 | MCVideo in-progress emergency group state cancel request..... | 27 | +| 7.1.2.2.21 | MCVideo in-progress emergency group state cancel response ..... | 28 | +| 7.1.2.2.22 | MCVideo imminent peril group call request..... | 28 | +| 7.1.2.2.23 | MCVideo imminent peril group call response..... | 28 | +| 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..... | 29 | +| 7.1.2.3 | Group call within one MC system ..... | 29 | +| 7.1.2.3.1 | Group call models ..... | 29 | +| 7.1.2.3.1.1 | Pre-arranged group call ..... | 29 | +| 7.1.2.3.1.2 | Chat group call ..... | 34 | +| 7.1.2.3.2 | Exiting group call due to de-affiliation ..... | 40 | +| 7.1.2.3.3 | MCVideo user leaving a group call..... | 41 | +| 7.1.2.4 | Broadcast group call ..... | 41 | +| 7.1.2.4.1 | General ..... | 41 | +| 7.1.2.4.2 | Common broadcast group call procedure..... | 42 | +| 7.1.2.5 | Emergency and imminent peril procedures ..... | 42 | +| 7.1.2.5.1 | MCVideo emergency group call ..... | 42 | +| 7.1.2.5.1.1 | MCVideo emergency group call commencement ..... | 42 | +| 7.1.2.5.1.2 | MCVideo group call upgraded to an MCVideo emergency group call..... | 44 | +| 7.1.2.5.1.3 | MCVideo in-progress emergency group state cancel..... | 46 | +| 7.1.2.5.2 | MCVideo imminent peril group call ..... | 48 | +| 7.1.2.5.2.1 | MCVideo imminent peril group call commencement ..... | 48 | +| 7.1.2.5.2.2 | Imminent peril group call upgrade ..... | 50 | +| 7.1.2.5.2.3 | MCVideo imminent peril group call cancel ..... | 52 | +| 7.1.2.6 | MCVideo emergency alert..... | 53 | +| 7.1.2.6.1 | General ..... | 53 | +| 7.1.3 | Off-network group communications ..... | 53 | +| 7.1.3.1 | General..... | 53 | +| 7.1.3.2 | Information flows for off-network group communications ..... | 53 | +| 7.1.3.2.1 | Group communication announcement ..... | 53 | +| 7.1.3.2.2 | Group communication answer response ..... | 54 | + +| | | | +|-------------|---------------------------------------------------------------------------------|----| +| 7.1.3.2.3 | MCVideo upgrade to emergency group communication ..... | 54 | +| 7.1.3.2.4 | MCVideo emergency group communication cancel..... | 55 | +| 7.1.3.2.5 | MCVideo upgrade to imminent peril group communication ..... | 55 | +| 7.1.3.2.6 | MCVideo imminent peril group communication cancel..... | 55 | +| 7.1.3.2.7 | MCVideo emergency alert announcement..... | 55 | +| 7.1.3.2.8 | MCVideo emergency alert cancel announcement..... | 56 | +| 7.1.3.3 | Group communication setup ..... | 56 | +| 7.1.3.3.1 | General ..... | 56 | +| 7.1.3.3.2 | Procedure..... | 56 | +| 7.1.3.4 | Passive join to group communication..... | 58 | +| 7.1.3.4.1 | General ..... | 58 | +| 7.1.3.4.2 | Procedure..... | 58 | +| 7.1.3.5 | Active join to group communication ..... | 59 | +| 7.1.3.5.1 | General ..... | 59 | +| 7.1.3.5.2 | Procedure..... | 59 | +| 7.1.3.6 | Broadcast group communication ..... | 60 | +| 7.1.3.7 | Group communication release due to inactivity ..... | 61 | +| 7.1.3.8 | Emergency and imminent peril procedures ..... | 61 | +| 7.1.3.8.1 | Emergency group communication ..... | 61 | +| 7.1.3.8.2 | MCVideo imminent peril ..... | 62 | +| 7.1.3.9 | MCVideo emergency alert..... | 63 | +| 7.1.3.9.1 | General ..... | 63 | +| 7.2 | Private call..... | 63 | +| 7.2.1 | General ..... | 63 | +| 7.2.2 | Private call on-network..... | 63 | +| 7.2.2.1 | General..... | 63 | +| 7.2.2.2 | Information flows for private call in on-network ..... | 63 | +| 7.2.2.2.1 | MCVideo private call request (MCVideo client – MCVideo server) ..... | 63 | +| 7.2.2.2.2 | MCVideo private call request (MCVideo server – MCVideo client) ..... | 64 | +| 7.2.2.2.3 | MCVideo private call response (MCVideo client – MCVideo server)..... | 64 | +| 7.2.2.2.4 | MCVideo private call response (MCVideo server – MCVideo client)..... | 65 | +| 7.2.2.2.5 | MCVideo call end request..... | 65 | +| 7.2.2.2.6 | MCVideo emergency private call request (MCVideo client to MCVideo server) ..... | 65 | +| 7.2.2.2.7 | MCVideo emergency private call request (MCVideo server to MCVideo client) ..... | 66 | +| 7.2.2.2.8 | Emergency MCVideo private call response (MCVideo client – MCVideo server) ..... | 66 | +| 7.2.2.2.9 | Emergency MCVideo private call response (MCVideo server – MCVideo client) ..... | 67 | +| 7.2.2.3 | Private call within one MC system..... | 67 | +| 7.2.2.3.1 | Private call setup in automatic commencement mode ..... | 67 | +| 7.2.2.3.2 | Private call setup in manual commencement mode ..... | 69 | +| 7.2.2.3.2.1 | Description ..... | 69 | +| 7.2.2.3.2.2 | Procedure ..... | 69 | +| 7.2.2.3.3 | Private call release..... | 71 | +| 7.2.2.3.3.1 | Client initiated ..... | 71 | +| 7.2.2.3.3.2 | Server initiated..... | 72 | +| 7.2.2.4 | MCVideo emergency private call..... | 73 | +| 7.2.2.4.1 | MCVideo emergency private call commencement ..... | 73 | +| 7.2.2.4.2 | MCVideo private call emergency upgrade..... | 74 | +| 7.2.3 | Off-network private communications..... | 75 | +| 7.2.3.1 | General..... | 75 | +| 7.2.3.2 | Information flows for off-network private communications ..... | 76 | +| 7.2.3.2.1 | Private communication request..... | 76 | +| 7.2.3.2.2 | Private communication answer response ..... | 76 | +| 7.2.3.2.3 | Private communication release request..... | 76 | +| 7.2.3.2.4 | Private communication release response..... | 77 | +| 7.2.3.3 | Use of ProSe for off-network private communications ..... | 77 | +| 7.2.3.4 | Automatic commencement private communication ..... | 77 | +| 7.2.3.4.1 | General ..... | 77 | +| 7.2.3.4.2 | Procedure..... | 78 | +| 7.2.3.5 | Manual commencement private communication..... | 79 | +| 7.2.3.5.1 | General ..... | 79 | +| 7.2.3.5.2 | Procedure – Communication accepted..... | 79 | +| 7.2.3.5.3 | Procedure – Communication rejected/ignored..... | 81 | + +| | | | +|-----------|-------------------------------------------------------------------------------|-----| +| 7.2.3.6 | Private communication release ..... | 82 | +| 7.2.3.6.1 | General ..... | 82 | +| 7.2.3.6.2 | Procedure..... | 82 | +| 7.3 | Video pull..... | 83 | +| 7.3.1 | General ..... | 83 | +| 7.3.2 | On-network video pull..... | 83 | +| 7.3.2.1 | General..... | 83 | +| 7.3.2.2 | Information flows for on-network video pull ..... | 83 | +| 7.3.2.2.1 | MCVideo pull from server request..... | 84 | +| 7.3.2.2.2 | MCVideo pull from server response ..... | 84 | +| 7.3.2.2.3 | MCVideo pull from server complete request..... | 84 | +| 7.3.2.2.4 | MCVideo pull from server complete response ..... | 84 | +| 7.3.2.3 | One-to-one video pull ..... | 85 | +| 7.3.2.3.1 | General ..... | 85 | +| 7.3.2.3.2 | One-to-one video pull – call setup ..... | 85 | +| 7.3.2.3.3 | One-to-one video pull – call release..... | 86 | +| 7.3.2.4 | One-from-server video pull ..... | 86 | +| 7.3.2.4.1 | General ..... | 86 | +| 7.3.2.4.2 | Procedure..... | 86 | +| 7.3.3 | Off-network video pull ..... | 87 | +| 7.3.3.1 | General..... | 87 | +| 7.3.3.2 | Information flows for off-network video pull..... | 88 | +| 7.3.3.3 | Video pull to self..... | 88 | +| 7.3.3.3.1 | General ..... | 88 | +| 7.3.3.3.2 | Procedure..... | 88 | +| 7.4 | Video push..... | 90 | +| 7.4.1 | General ..... | 90 | +| 7.4.2 | On-network video push ..... | 90 | +| 7.4.2.1 | General..... | 90 | +| 7.4.2.2 | Information flows for on-network video push ..... | 90 | +| 7.4.2.2.1 | Remote video push request ..... | 90 | +| 7.4.2.2.2 | Remote video push response ..... | 91 | +| 7.4.2.2.3 | Remote video push release request ..... | 91 | +| 7.4.2.2.4 | MCVideo push to server request..... | 92 | +| 7.4.2.2.5 | MCVideo push to server response ..... | 92 | +| 7.4.2.2.6 | MCVideo push to server complete request ..... | 92 | +| 7.4.2.2.7 | MCVideo push to server complete response..... | 93 | +| 7.4.2.3 | One-to-one video push..... | 93 | +| 7.4.2.3.1 | General ..... | 93 | +| 7.4.2.3.2 | One-to-one video push – call setup..... | 93 | +| 7.4.2.3.3 | One-to-one video push – call release ..... | 94 | +| 7.4.2.4 | One-to-server video push..... | 94 | +| 7.4.2.4.1 | General ..... | 94 | +| 7.4.2.4.2 | Procedure..... | 94 | +| 7.4.2.5 | Remotely initiated video push ..... | 96 | +| 7.4.2.5.1 | General ..... | 96 | +| 7.4.2.5.2 | Remotely initiated video push – call setup..... | 96 | +| 7.4.2.5.3 | Remotely initiated video push – call release by authorized user ..... | 97 | +| 7.4.2.6 | Remotely initiated video push to group ..... | 98 | +| 7.4.2.6.1 | General ..... | 98 | +| 7.4.2.6.2 | Remotely initiated video push to group – call setup ..... | 98 | +| 7.4.2.6.3 | Remotely initiated video push to group – call release by authorized user..... | 99 | +| 7.4.3 | Off-network video push..... | 100 | +| 7.4.3.1 | General..... | 100 | +| 7.4.3.2 | Information flows for off-network video push ..... | 100 | +| 7.4.3.2.1 | Remote video push request ..... | 100 | +| 7.4.3.2.2 | Video push trying response ..... | 100 | +| 7.4.3.2.3 | Notification of video push..... | 100 | +| 7.4.3.3 | Video push to another MCVideo user ..... | 101 | +| 7.4.3.3.1 | General ..... | 101 | +| 7.4.3.3.2 | Procedure..... | 101 | +| 7.4.3.4 | Remotely initiated video push ..... | 102 | + +| | | | +|-----------|--------------------------------------------------------------------------|-----| +| 7.4.3.4.1 | General ..... | 102 | +| 7.4.3.4.2 | Procedure..... | 102 | +| 7.4.3.5 | Remotely initiated video push to a group ..... | 104 | +| 7.4.3.5.1 | General ..... | 104 | +| 7.4.3.5.2 | Procedure..... | 104 | +| 7.5 | Capability information sharing..... | 105 | +| 7.5.1 | General ..... | 105 | +| 7.5.2 | On-network capability information sharing ..... | 105 | +| 7.5.2.1 | General..... | 105 | +| 7.5.2.2 | Information flows for on-network capability information sharing..... | 105 | +| 7.5.2.2.1 | Update MCVideo capabilities info request ..... | 105 | +| 7.5.2.2.2 | Update MCVideo capabilities info response..... | 106 | +| 7.5.2.2.3 | Get MCVideo capabilities info request..... | 106 | +| 7.5.2.2.4 | Get MCVideo capabilities info response ..... | 106 | +| 7.5.2.2.5 | Subscribe MCVideo capabilities info request..... | 106 | +| 7.5.2.2.6 | Subscribe MCVideo capabilities info response ..... | 107 | +| 7.5.2.2.7 | Notify MCVideo capabilities info request ..... | 107 | +| 7.5.2.2.8 | Notify MCVideo capabilities info response..... | 107 | +| 7.5.2.3 | Update MCVideo capabilities information at the MCVideo server ..... | 107 | +| 7.5.2.4 | Retrieve MCVideo capabilities information by the MCVideo client ..... | 108 | +| 7.5.2.5 | Subscription and notification for MCVideo capabilities information ..... | 108 | +| 7.5.3 | Off-network capability information sharing..... | 109 | +| 7.5.3.1 | General..... | 109 | +| 7.5.3.2 | Information flows for Off-network capability information sharing ..... | 110 | +| 7.5.3.2.1 | Capability request..... | 110 | +| 7.5.3.2.2 | Capability announcement..... | 110 | +| 7.5.3.2.3 | Activity status request..... | 110 | +| 7.5.3.2.4 | Activity status announcement ..... | 111 | +| 7.5.3.3 | Periodic capability announcements ..... | 111 | +| 7.5.3.3.1 | General ..... | 111 | +| 7.5.3.3.2 | Procedure..... | 111 | +| 7.5.3.4 | Request capabilities from client(s) ..... | 112 | +| 7.5.3.4.1 | General ..... | 112 | +| 7.5.3.4.2 | Request clients with particular capabilities..... | 112 | +| 7.5.3.4.3 | Request capabilities from a particular client ..... | 113 | +| 7.5.3.5 | Request activity status from client(s)..... | 114 | +| 7.5.3.5.1 | General ..... | 114 | +| 7.5.3.5.2 | Request activity status of group members..... | 114 | +| 7.5.3.5.3 | Request activity status from a particular client ..... | 115 | +| 7.6 | Ambient viewing call ..... | 116 | +| 7.6.1 | General ..... | 116 | +| 7.6.2 | Information flows for ambient viewing call ..... | 116 | +| 7.6.2.1 | Ambient viewing call request ..... | 116 | +| 7.6.2.2 | Ambient viewing call response..... | 117 | +| 7.6.2.3 | Ambient viewing call release request..... | 117 | +| 7.6.2.4 | Ambient viewing call release response..... | 117 | +| 7.6.2.5 | Ambient viewing call release notification ..... | 118 | +| 7.6.3 | Procedures ..... | 118 | +| 7.6.3.1 | Remotely initiated ambient viewing call setup procedure..... | 118 | +| 7.6.3.2 | Locally initiated ambient viewing call setup procedure ..... | 119 | +| 7.6.3.3 | Ambient viewing call release – server initiated..... | 120 | +| 7.6.3.4 | Ambient viewing call release – "viewing" user initiated..... | 121 | +| 7.6.3.5 | Ambient viewing call release – "viewed to" user initiated..... | 122 | +| 7.7 | Transmission control..... | 123 | +| 7.7.1 | Transmission control for on-network MCVideo service..... | 123 | +| 7.7.1.1 | General..... | 123 | +| 7.7.1.2 | Information flows for transmission control for on-network ..... | 123 | +| 7.7.1.2.1 | General ..... | 123 | +| 7.7.1.2.2 | Transmit media request..... | 123 | +| 7.7.1.2.3 | Transmit media granted..... | 124 | +| 7.7.1.2.4 | Transmit media rejected..... | 124 | +| 7.7.1.2.5 | Media transmission notification..... | 124 | + +| | | | +|-------------|-----------------------------------------------------------------------------------------------|-----| +| 7.7.1.2.6 | Receive media request..... | 124 | +| 7.7.1.2.7 | Receive media response ..... | 125 | +| 7.7.1.2.8 | Media reception notification ..... | 125 | +| 7.7.1.2.9 | Queue position info ..... | 125 | +| 7.7.1.2.10 | Transmission revoked ..... | 125 | +| 7.7.1.2.11 | Queue position request..... | 126 | +| 7.7.1.2.12 | Transmit media cancel request..... | 126 | +| 7.7.1.2.13 | Transmit media cancel response ..... | 126 | +| 7.7.1.2.14 | Transmit media cancel request notify ..... | 126 | +| 7.7.1.2.15 | Transmit media end request ..... | 127 | +| 7.7.1.2.16 | Transmit media end response..... | 127 | +| 7.7.1.2.17 | Remote transmit media request..... | 127 | +| 7.7.1.2.18 | Remote transmit media response..... | 127 | +| 7.7.1.2.19 | Remote transmit media end request..... | 128 | +| 7.7.1.2.20 | Remote transmit media cancel response ..... | 128 | +| 7.7.1.2.21 | Media reception end request ..... | 128 | +| 7.7.1.2.22 | Media reception end response..... | 128 | +| 7.7.1.2.23 | Media reception override notification..... | 129 | +| 7.7.1.2.24 | Transmit media end notify ..... | 129 | +| 7.7.1.3 | Transmission control within one MC system for MCVideo service ..... | 129 | +| 7.7.1.3.1 | Transmission control during an MCVideo session ..... | 129 | +| 7.7.1.3.2 | Reception control during an MCVideo session..... | 130 | +| 7.7.1.3.2A | End media reception – receiving user initiated ..... | 132 | +| 7.7.1.3.2B | End media reception – transmission control server initiated ..... | 132 | +| 7.7.1.3.2C | Reception control on overridden – mandatory mode..... | 133 | +| 7.7.1.3.2D | Reception control on overridden – negotiated mode ..... | 134 | +| 7.7.1.3.3 | Transmission revoke during an MCVideo session..... | 135 | +| 7.7.1.3.4 | Queue position during an MCVideo session..... | 136 | +| 7.7.1.3.5 | Transmit media request cancellation from the video transmission queue ..... | 137 | +| 7.7.1.3.5.1 | Transmit media request cancellation from the queue – MCVideo user initiated ..... | 137 | +| 7.7.1.3.5.2 | Transmit media request cancellation from the queue - transmission control server initiated .. | 138 | +| 7.7.1.3.6 | End a media transmission during an MCVideo session..... | 139 | +| 7.7.1.3.6.1 | End a media transmission – MCVideo user initiated ..... | 139 | +| 7.7.1.3.6.2 | End a media transmission – transmission control server initiated..... | 140 | +| 7.7.1.3.6.3 | End a media transmission – remote MCVideo user initiated ..... | 141 | +| 7.7.1.3.7 | Remotely initiated media transmission during an MCVideo session ..... | 142 | +| 7.7.2 | Off-network transmission control..... | 143 | +| 7.7.2.1 | General..... | 143 | +| 7.7.2.2 | Information flows for off-network transmission control ..... | 143 | +| 7.7.2.2.1 | Transmission request..... | 143 | +| 7.7.2.2.2 | Transmission granted ..... | 144 | +| 7.7.2.2.3 | Transmission release ..... | 144 | +| 7.7.2.2.4 | Transmission rejected..... | 144 | +| 7.7.2.2.5 | Transmission revoked ..... | 144 | +| 7.7.2.2.6 | Transmission arbitration taken..... | 145 | +| 7.7.2.2.7 | Transmission arbitration release..... | 145 | +| 7.7.2.3 | Initializing transmission control – single arbitrator approach ..... | 145 | +| 7.7.2.3A | Initializing transmission control – self arbitration approach ..... | 146 | +| 7.7.2.4 | Transmission permission granted ..... | 147 | +| 7.7.2.5 | Transmission permission rejected..... | 148 | +| 7.7.2.6 | Releasing transmission permission..... | 149 | +| 7.7.2.7 | Transmission override..... | 150 | +| 7.7.2.8 | Transmission override (revoke self) ..... | 151 | +| 7.7.2.9 | Transmission arbitration release ..... | 153 | +| 7.7.2.9.1 | Transmission arbitration release..... | 153 | +| 7.7.2.9.2 | Transmission arbitration release with delegation..... | 153 | +| 7.7.2.10 | Simultaneous transmission requests ..... | 154 | +| 7.8 | MCVideo service configuration..... | 155 | +| 7.9 | Affiliation and de-affiliation to/from MCVideo group(s)..... | 155 | +| 7.9a | Functional alias management..... | 156 | +| - | The MC service ID is the MCVideo ID.7.10 Use of MBMS transmission (on-network) ..... | 156 | +| 7.10.1 | Information flows for MBMS Transmission..... | 156 | + +| | | | +|----------------------------------------------------------------------|------------------------------------------------------------------------------------------------|------------| +| 7.10.1.1 | General..... | 156 | +| 7.10.1.2 | MapGroupToBearer..... | 156 | +| 7.10.1.3 | UnmapGroupFromBearer ..... | 157 | +| 7.10.2 | Use of pre-established MBMS bearers..... | 157 | +| 7.10.3 | Use of dynamic MBMS bearer establishment..... | 157 | +| 7.10.4 | Video call connect and disconnect over MBMS ..... | 158 | +| 7.10.4.1 | General..... | 158 | +| 7.10.4.2 | Procedure ..... | 158 | +| 7.10.4.2.1 | Call connect over MBMS..... | 158 | +| 7.10.4.2.2 | Call disconnect over MBMS..... | 159 | +| 7.10.5 | Switching from MBMS bearer to unicast bearer..... | 160 | +| 7.11 | Simultaneous session for MCVideo calls (on-network) ..... | 160 | +| 7.12 | User authentication and authorization for MCVideo service..... | 160 | +| 7.13 | Support for multiple devices ..... | 161 | +| 7.14 | Location information (on-network)..... | 161 | +| 7.15 | MCVideo resource management (on-network)..... | 161 | +| 7.16 | MCVideo client query..... | 162 | +| 7.16.1 | General ..... | 162 | +| 7.16.2 | Information flows for MCVideo client query ..... | 162 | +| 7.16.2.1 | MCVideo client query request..... | 162 | +| 7.16.2.2 | MCVideo client query response ..... | 162 | +| 7.16.3 | MCVideo client query procedure ..... | 162 | +| 7.17 | MCVideo adaptation during MCVideo communication..... | 163 | +| 7.17.1 | General ..... | 163 | +| 7.17.2 | Information flows for MCVideo adaptation..... | 163 | +| 7.17.2.1 | MCVideo communication parameter update request ..... | 163 | +| 7.17.2.2 | MCVideo communication parameter update response..... | 164 | +| 7.17.3 | MCVideo adaptation procedure ..... | 164 | +| 7.17.3.1 | MCVideo adaptation during group communication procedure – transmitting client triggered ..... | 164 | +| 7.17.3.2 | MCVideo adaptation during group communication procedure – receiving user triggered ..... | 165 | +| 7.17.3.3 | MCVideo adaptation during private communication procedure – transmitting client triggered..... | 166 | +| 7.17.3.4 | MCVideo adaptation during group communication procedure – receiving user triggered ..... | 167 | +| Annex A (normative): MCVideo related configuration data ..... | | 169 | +| A.1 | General..... | 169 | +| A.2 | MCVideo UE configuration data ..... | 170 | +| A.3 | MCVideo user profile configuration data ..... | 170 | +| A.4 | MCVideo related Group configuration data ..... | 177 | +| A.5 | MCVideo service configuration data ..... | 179 | +| Annex B (informative): Change history..... | | 181 | + +--- + +## 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 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. It is recommended that the dedicated bearer(s) for video media and control of the video media (i.e. MCVideo-4 and MCVideo-7) utilise the QCI values depending on the MCVideo mode of the MCVideo call/session, as per table 5.5.3-1. For transmission and reception control signalling, the QCI value of 69 is recommended as specified in 3GPP TS 23.203 [11]. 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
(as specified in 3GPP
TS 23.203 [11]) | +|---------------------------|----------------------------------------------------------------| +| Urgent real-time mode | 67 | +| Non-urgent real-time mode | 67 | +| Non real-time mode | 4 | + +The MCVideo audio media and video media may transmit over separate EPS bearers, in which case the priority for each bearer is determined by the operator policy. Depending on operator policy, the MCVideo 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. + +NOTE: Operator policy takes into account regional/national requirements. + +When MCVideo audio media and video media are multiplexed into one EPS bearer, then different QCI and/or ARP values are not possible for video and audio media. + +### 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. + + + +The diagram illustrates the functional model for the application plane of MCVideo service. On the left, three external entities are shown: 'Other MCVideo server', 'MCVideo user database', and 'MC gateway server'. The 'Other MCVideo server' connects to the 'MCVideo server' via interface 'MCVideo-3'. The 'MCVideo user database' connects to the 'MCVideo server' via interface 'MCVideo-2'. The 'MC gateway server' connects to the 'MCVideo server' via interface 'MCVideo-3' and to an 'Other MCVideo system' (represented by a dashed box) via interface 'MCVideo-10'. The 'MCVideo server' is a central component containing two sub-functions: 'Media distribution function' and 'Transmission control server'. The 'Media distribution function' has multiple interfaces: 'MCVideo-5' (Rx) and 'MCVideo-6' (MB2C) connecting to the 'MCVideo client' inside the 'MCVideo UE'; 'MCVideo-7' connecting to the 'Media mixer' inside the 'MCVideo UE'; and 'MCVideo-8' connecting to the 'Transmission control participant' inside the 'MCVideo UE'. The 'Transmission control server' has interfaces 'MCVideo-1' and 'MCVideo-4' connecting to the 'Transmission control participant' inside the 'MCVideo UE', and 'MCVideo-9' connecting to the 'Transmission control participant' inside the 'MCVideo UE'. All these internal interfaces pass through a vertical bar labeled 'EPS' (Evolved Packet System). The 'MCVideo UE' is shown on the right, containing the 'MCVideo client', 'Media mixer', and 'Transmission control participant'. + +Functional model diagram for application plane of MCVideo service. It shows various components connected via interfaces labeled MCVideo-1 through MCVideo-10. Components include Other MCVideo server, MCVideo user database, MC gateway server, MCVideo server (containing Media distribution function and Transmission control server), EPS, and MCVideo UE (containing MCVideo client, Media mixer, and Transmission control participant). + +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. + + + +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, Group management client), and an MCVideo client (Media mixer, Transmission control participant, 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. + +The MCVideo 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 MCVideo user. + +The controlling roles for group call, private call and functional alias are independent with each other. + +#### 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 | +| Functional alias | O | The functional alias 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 | +| Requested priority | O | Application priority level requested for this 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 | +| Functional alias | O | The functional alias 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 | +| Functional alias | O | The functional alias 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 | +| Requested priority | O | Application priority level requested for this call | + +#### 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 join request (MCVideo client – MCVideo server) + +Table 7.1.2.2.10-1 describes the information flow group join request from the MCVideo client to the MCVideo server. + +**Table 7.1.2.2.10-1: Group 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 | +| Implicit transmit media request | O | An indication that the user is also requesting the permission to transmit video | +| Requested priority | O | Application priority level requested for this call | + +#### 7.1.2.2.11 Group join response (MCVideo server – MCVideo client) + +Table 7.1.2.2.11-1 describes the information flow group join response from the MCVideo server to the MCVideo client. + +**Table 7.1.2.2.11-1: Group 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.12a Group call leave request (MCVideo client – MCVideo server) + +Table 7.1.2.2.12a-1 describes the information flow group call leave request from the MCVideo client to the MCVideo server. + +**Table 7.1.2.2.12a-1: Group call leave request (MCVideo client – MCVideo server)** + +| Information Element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------| +| MCVideo ID | M | The MCVideo ID of the MCVideo group member leaving the group call | +| 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.13a Group call leave response (MCVideo server – MCVideo client) + +Table 7.1.2.2.13a-1 describes the information flow group call leave response from the MCVideo server to the MCVideo client. + +**Table 7.1.2.2.13a-1: Group call leave response (MCVideo server – MCVideo client)** + +| Information Element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------| +| MCVideo ID | M | The MCVideo ID of the MCVideo group member leaving the group call | +| 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 | +| Functional alias | O | The functional alias 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 | +| Functional alias | O | The functional alias 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 (see NOTE) | O | Requests cancellation of the emergency alert of the cancelling party | +| Group in-progress emergency state cancel request (see 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 | +| Functional alias | O | The functional alias 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 (see 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 | +| Functional alias | O | The functional alias 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 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. + +###### 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. +3. Optionally, the MCVideo client 1 may have an activated functional alias to be used. +4. The MCVideo server may have subscribed to the MCVideo functional alias controlling server within the MC system for functional alias activation/de-activation updates. + + + +``` + +sequenceDiagram + participant C1 as MCVideo client 1 + participant S as MCVideo server + participant GMS as Group management server + participant C2 as MCVideo client 2 + participant C3 as MCVideo client 3 + + Note over C1: 1. Initiate group call + C1->>S: 2. Group call request + Note over S, GMS: 3. Resolve group id + S->>C2: 4a. Group call request + Note over C2: 4a. Notify group call + S->>C3: 4b. Group call request + Note over C3: 4b. Notify group call + C2->>S: 5a. Group call response + C3->>S: 5b. Group call response + S->>C1: 6. Group call response + S-->>C1: 7. Group call notify + Note over C1, C3: 8. Media plane and transmission control establishment + +``` + +Sequence diagram for Pre-arranged group call setup involving MCVideo client 1, MCVideo server, Group management server, MCVideo client 2, and MCVideo client 3. + +**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). The MCVideo user at MCVideo client 1 may include a functional alias used within the MCVideo group call. + +**NOTE 1:** The selected functional alias is not changed during the group call, i.e. a MCVideo client uses the same functional alias until the group call is released or the MCVideo client has left the group call. + +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 the MC service user of MCVideo client 1 has selected a functional alias, then the group call request contains that functional alias. 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 a functional alias is present, the MCVideo server checks whether it is allowed to be used and if it has been activated for the user. 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 2: 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 and, if present, the functional alias of the initiating MC service user is displayed. 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 3: 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. + +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. + + + +``` + +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. +3. Optionally, the MCVideo client 1 may have activated functional alias to be used. +4. The MCVideo server may have subscribed to the MCVideo functional alias controlling server within the MC system for functional alias activation/de-activation updates. + + + +``` + +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 + Note left of MCVideo client 1: 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 at client 1; 4. Group call response from client 1 to server; 5. MCVideo client 1 is added to ongoing group call (indicated by a bar across all lifelines); 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 client1. + +**Editor's Note: Checking of functional alias of MCVideo client 1 by the MCVideo server is FFS.** + +#### 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: + +- 1 It is assumed that MCVideo users on MCVideo client 2 to MCVideo client n are on an ongoing call. + +2. Optionally, the MCVideo client 1 may have activated functional alias to be used. +3. The MCVideo server may have subscribed to the MCVideo functional alias controlling server within the MC system for functional alias activation/de-activation updates. + + + +``` + +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. Group call rejoin request from client 1 to server; 2. Authorize from server; 3. Group call rejoin response from server to client 1; 4. Client 1 added to ongoing group call (indicated by a bar across all lifelines); 5. Notification of video transmissions in the group call from server 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. The MCVideo user at MCVideo client 1 may include a functional alias used within the MCVideo rejoin request. +2. MCVideo server checks whether the MCVideo client 1 can rejoin the ongoing call (e.g. based upon affiliation status) and checks the functional alias, if present. +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 and the functional alias of MCVideo client 1 may be displayed. +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 (restricted) call model, the MCVideo user individually joins a group call without being explicitly invited by the MCVideo server. The establishment of a chat group (restricted) 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 (restricted) call model. The chat group (restricted) call model can be used to realize the video conferencing service where only users that have been configured as participants for the video conferencing group are allowed to join the group communications for the given group. + +Chat group join mechanism: + +- Each MCVideo client sends a group 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 join request may include a transmit media request. It is assumed that the group join request will be delivered from MCVideo client to MCVideo server using SIP. +- The group 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 join request shall 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 join request contains the information needed to negotiate media parameters (on demand) or to associate a pre-established session between MCVideo server and MCVideo 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 MCVideo client during the whole participation within a chat group call, i.e. a MCVideo client uses the same functional alias selected when joining the chat group call until the chat group call is released or the MCVideo client leaves the chat group call. + +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, and the time out between transmission control exchanges has expired) 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 other joined users of the group using the chat model, then the MCVideo client shall use 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. + +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. + +#### 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. 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. +2. MCVideo client 1, MCVideo client 2 and MCVideo 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. +3. The MCVideo server may have subscribed to the MCVideo functional alias controlling server within the MC system for functional alias activation/de-activation updates. + + + +``` + +sequenceDiagram + participant MCVideo client 1 + participant MCVideo server + participant MCVideo client 2 + participant MCVideo client 3 + + Note right of MCVideo server: 1b. MCVideo server receives the group call join request. + + MCVideo client 1->>MCVideo server: 1a. Group join request + Note right of MCVideo server: 1b. MCVideo server receives the group call join request. + MCVideo server-->>MCVideo client 1: 1c. Group join response + + Note over MCVideo client 1, MCVideo client 3: 2. MCVideo user 1 requests to transmit video causing the media plane to be established (if not pre-established). + + Note over MCVideo client 1, MCVideo client 3: 3. Media plane signaling using transmission control + +``` + +Sequence diagram for MCVideo chat group call. Lifelines: MCVideo client 1, MCVideo server, MCVideo client 2, MCVideo client 3. Steps: 1a. Group join request from client 1 to server; 1b. Server receives request; 1c. Server responds; 2. Client 1 requests to transmit video; 3. Media plane signaling across all participants. + +**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 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. The MCVideo user at MCVideo client 1 may include a functional alias used within the MCVideo group join request. If there is a request for media transmission, then the group join request contains an indication of an implicit transmit media request. + - 1b. The MCVideo server receives the group 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. If a functional alias is present, the MCVideo server checks whether it is allowed to be used and if it has been activated for the user. + - 1c. The MCVideo server replies with a group join response indicating the acceptance of the group join request and also returns the MCVideo server selected media parameters for the group call in the group 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. .If present, the functional alias of MCVideo client 1, MCVideo client 2 and MCVideo client 3 are displayed where appropriate. + +#### 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 + + + +``` + +sequenceDiagram + participant MCVideo server + participant MCVideo client 1 + 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 + Note left of MCVideo client 1: 4a. Notify user + MCVideo server->>MCVideo client 2: 3b. Group call release request + Note right of MCVideo client 2: 4b. Notify user + MCVideo server->>MCVideo client 3: 3c. Group call release request + Note right of MCVideo client 3: 4c. Notify user + MCVideo client 1-->>MCVideo server: 5a. Group call release response + MCVideo client 2-->>MCVideo server: 5b. Group call release response + MCVideo client 3-->>MCVideo server: 5c. Group call release response + Note bottom: 6. Release transmission control and media plane resources associated with the group call + +``` + +Sequence diagram for 'Release chat group call' showing interactions between MCVideo client 1, MCVideo server, MCVideo client 2, and MCVideo client 3. The process involves the server initiating a release, determining participants, sending requests to clients, notifying users, receiving optional responses, and finally releasing resources. + +**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 void + +7.1.2.3.1.2.5 Late entry chat group call, newly joined group member + +Procedures in figure 7.1.2.3.1.2.5-1 are those for a group member entering an ongoing MCVideo group call, i.e. performing a late entry. + +Pre-conditions: + +1. MCVideo user 2 and MCVideo user 3 have previously joined to the group. 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. +2. MCVideo user 1 indicates to join the group communication for the group. +3. MCVideo users using MCVideo client 1 to MCVideo client n may have activated functional alias(es) configured to be used during the group call communication. +- 4 The MCVideo server may have subscribed to the MCVideo functional alias controlling server within the MC system for functional alias activation/de-activation updates. + + + +``` + +sequenceDiagram + participant MCVideo client 1 + participant MCVideo server + participant MCVideo client 2 + participant MCVideo client 3 + + Note right of MCVideo server: 2. Perform implicit affiliation and check user authorization + + MCVideo client 1->>MCVideo server: 1.Group join request + MCVideo server-->>MCVideo client 1: 3.Group join response + Note left of MCVideo server: 4. Media plane establishment + Note right of MCVideo server: 5. Notify users + Note left of MCVideo server: 6a. Media transmission notification or +6b. Transmit media granted or +6c. Transmit media rejected or +6d. Queue position info + MCVideo server-->>MCVideo client 1: 6a. Media transmission notification or +6b. Transmit media granted or +6c. Transmit media rejected or +6d. Queue position info + Note right of MCVideo client 3: 7. Media plane signaling using transmission control + +``` + +Sequence diagram showing the interaction for late entry of a newly joined group member. Lifelines: MCVideo client 1, MCVideo server, MCVideo client 2, MCVideo client 3. Steps: 1. Group join request from client 1 to server; 2. Perform implicit affiliation and check user authorization (server internal); 3. Group join response from server to client 1; 4. Media plane establishment between client 1 and server; 5. Notify users (client 2 and 3); 6a-d. Media transmission notification or Transmit media granted or Transmit media rejected or Queue position info from server to client 1; 7. Media plane signaling using transmission control between client 1 and clients 2/3. + +Figure 7.1.2.3.1.2.5-1: Late entry of a newly joined group member + +1. MCVideo client 1 sends a group 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. The MCVideo user at MCVideo client 1 may include a functional alias used within the MCVideo group join request. If there is a request to transmit, then the group join request contains an indication of an implicit transmit media request. +2. The MCVideo server receives the group 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. If a functional alias is present, the MCVideo server checks whether it is allowed to be used and if it has been activated for the user. +3. The MCVideo server replies with a group join response indicating the acceptance of the group join request. +4. Media plane between MCVideo client 1 and MCVideo server is established using media plane control signalling. +5. MCVideo users at MCVideo client 2 and MCVideo client 3 may be notified about the MCVideo client 1 joining the group call, and the functional alias of MCVideo client 1 may be displayed. + +6. The MCVideo server may send (6a) Media transmission notification to MCVideo client 1, indicating the current transmitter. Alternatively the MCVideo server may send (6b) Transmit media granted, (6b) Transmit media rejected or (6d) Queue position info. +7. Transmission control will continue to be used by the transmission control participants associated with MCVideo client 1, MCVideo client 2 and MCVideo client 3. If present, the functional alias of MCVideo client 1, MCVideo client 2 and MCVideo client 3 are displayed where appropriate. + +#### 7.1.2.3.1.2.6 Late entry chat group call, MCVideo client coming back from out of coverage + +Procedures in figure 7.1.2.3.1.2.6-1 are those for an MCVideo client coming back from out of coverage during an ongoing MCVideo group call. + +Pre-conditions: + +1. MCVideo users using MCVideo client 1, MCVideo client 2 and MCVideo client 3 are in an ongoing group call when MCVideo client1 goes out of radio coverage. +2. MCVideo client1 returns from out of coverage while the group call is still ongoing. +3. MCVideo users using MCVideo client 1 to MCVideo client n may have activated functional alias(es) configured to be used during the group call communication. +4. The MCVideo server may have subscribed to the MCVideo functional alias controlling server within the MC system for functional alias activation/de-activation updates. + + + +``` + +sequenceDiagram + participant MCVideo client 1 + participant MCVideo server + participant MCVideo client 2 + participant MCVideo client 3 + + Note over MCVideo client 1, MCVideo server: 1. MCVideo client 1 returns from out of coverage + Note over MCVideo client 1, MCVideo server: 2. Re-establish media plane + MCVideo server->>MCVideo client 1: 3a. Media transmission notification or +3b. Transmit media granted or +3c. Transmit media rejected or +3d. Queue position info + Note over MCVideo server, MCVideo client 3: 4. Notify users + Note over MCVideo client 1, MCVideo client 3: 5. Media plane signaling using Transmission control + +``` + +Sequence diagram illustrating the late entry of an MCVideo client returning from out of coverage. 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 1 returns from out of coverage; 2. Re-establish media plane; 3a-d. MCVideo server sends notification/grant/reject/info to client 1; 4. Notify users (dashed box); 5. Media plane signaling using Transmission control (wide arrow). + +**Figure 7.1.2.3.1.2.6-1: Late entry of an MCVideo client returning from out of coverage** + +1. MCVideo client 1 or MCVideo server detects that MCVideo client 1 has returned from out of coverage. + +NOTE 1: How the MCVideo client or MCVideo server detects that the client has returned from out of coverage is out of scope of the present document. + +2. Media plane between MCVideo client 1 and MCVideo server is re-established using media plane control signalling. + +NOTE 2: Depending on how long MCVideo client 1 was out of coverage, this step can include signalling from MCVideo client 1 to rejoin the chat group. + +3. The MCVideo server may send (3a) Media transmission notification to MCVideo client 1, indicating the current transmitter. Alternatively the MCVideo server may send (3b) Transmit media granted, (3c) Transmit media rejected or (3d) Queue position info. + +4. MCVideo users at MCVideo client 2 and MCVideo client 3 may be notified about the MCVideo client 1 returning to the group call, and the functional alias of MCVideo client 1 may be displayed. +5. Transmission control will continue to be used by the transmission control participants associated with MCVideo client 1, MCVideo client 2 and MCVideo client 3. If present, the functional alias of MCVideo client 1, MCVideo client 2 and MCVideo client 3 are displayed where appropriate. + +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. + + + +``` + +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 has been de-affiliated from the MCVideo group + MCVideo server->>MCVideo client 1: 2. Group call leave request + MCVideo client 1->>MCVideo server: 3. Notify user + MCVideo client 1->>MCVideo server: 4. Group call leave response + Note right of MCVideo client n: 5. MCVideo client 1 is removed from the ongoing group call + +``` + +Sequence diagram showing the interaction between MCVideo client 1, MCVideo server, MCVideo client 2, and MCVideo client n. The process starts with a note that MCVideo client 1 has been de-affiliated. The server sends a 'Group call leave request' to client 1. Client 1 then notifies its user and sends a 'Group call leave response' back to the server. Finally, a note indicates that 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.3.3 MCVideo user leaving a group call + +Procedures in figure 7.1.2.3.3-1 are the signalling control plane procedures for the MCVideo user leaving 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 user 1 indicates to leave the group call + + + +``` + +sequenceDiagram + participant MCVideo client 1 + participant MCVideo server + participant MCVideo client 2 + participant MCVideo client n + Note left of MCVideo client 1: 3. Release media plane + MCVideo client 1->>MCVideo server: 1. Group call leave request + MCVideo server-->>MCVideo client 1: 2. Group call leave response + Note right of MCVideo server: 4. Notify users + MCVideo server-->>MCVideo client 2: + MCVideo server-->>MCVideo client n: + +``` + +Sequence diagram showing a user leaving a group call. Lifelines: MCVideo client 1, MCVideo server, MCVideo client 2, MCVideo client n. Steps: 1. Group call leave request from client 1 to server; 2. Group call leave response from server to client 1; 3. Release media plane (internal to client 1); 4. Notify users (dashed line from server to clients 2 and n). + +**Figure 7.1.2.3.3-1: MCVideo user leaving a group call** + +1. MCVideo client 1 sends a group call leave request to the MCVideo server. +2. MCVideo server sends a group call leave response to MCVideo client 1. +3. Release of transmission control and media plane resources associated with the group call for MCVideo client 1. + +NOTE 1: MCVideo server checks if group call termination conditions are met, e.g. last participant leaving, second last participant leaving, initiator leaving, minimum number of affiliated MCVideo group members are not present . If at least one of the group call termination conditions is met, the MCVideo server releases the group call for all participants (see subclauses 7.1.2.3.1.1.3 Release pre-arranged group call and 7.1.2.3.1.2.3 Release chat group call). + +4. MCVideo users at MCVideo client 2 to MCVideo client n may be notified that the MCVideo user of client 1 has left the group call. + +NOTE 2: The MCVideo server does not perform late entry for MCVideo users that have 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. + + + +``` + +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 + MCVideo client 1->>MCVideo server: 2. Video transmission + MCVideo client 1->>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 server and client 2 to client 1). + +**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. +4. MCVideo client 1, MCVideo client 2 and MCVideo client 3 may have an activated functional alias to be used during the emergency group communication. + +5. The MCVideo server may have subscribed to the MCVideo 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. + + + +``` + +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 client 3->>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 shows the initiation of an emergency call, server-side processing (affiliation, group ID resolution, bearer configuration), and subsequent notification and response to clients. + +**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 emergency group call request towards the MCVideo server. The MCVideo user at MCVideo client 1 may include a functional alias used within the MCVideo emergency group call request. 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 provided functional alias is allowed to be used and has been activated for the MCVideo user, and 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, and, if available, the functional alias of the initiating user is displayed. +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. + + + +``` + +sequenceDiagram + participant Client1 as MCVideo client 1 + participant Server as MCVideo server + participant GMS as Group management server + participant Client2 as MCVideo client 2 + participant Client3 as MCVideo client 3 + + Note over Client1, Client3: Group call already in progress + + Client1->>Client1: 1. Initiate group emergency + Client1->>Server: 2. MCVideo emergency group call request + Note over Server: 3. Bearer priority adjustment + Server->>Client2: 4. MCVideo emergency group call request + Server->>Client3: 4. MCVideo emergency group call request + Note over Client2: 5. Notify group emergency status + Note over Client3: 5. Notify group emergency status + Client2->>Server: 6. MCVideo emergency group call response + Client3->>Server: 6. MCVideo emergency group call response + Server->>Client1: 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 back 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. + + + +``` + +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. +4. MCVideo client 1, MCVideo client 2 and MCVideo client 3 may have an activated functional alias to be used during the emergency group communication. +5. The MCVideo server may have subscribed to the MCVideo functional alias controlling server within the MC system for functional alias activation/de-activation updates. + +NOTE 1: Alternatively, the client could have been provisioned for imminent peril behaviour on the selected group. + + + +``` + +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 the user. 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 MCVideo user at MCVideo client 1 may include a functional alias used within the MCVideo imminent peril group call request. 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 provided functional alias is allowed to be used and has been activated for the MCVideo user, and 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, and, if available, the functional alias of the initiating user is displayed. +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. + + + +``` + +sequenceDiagram + participant Client1 as MCVideo client 1 + participant Server as MCVideo server + participant GMS as Group management server + participant Client2 as MCVideo client 2 + participant Client3 as MCVideo client 3 + + Note over Client1, Client3: Group call already in progress + + Note left of Client1: 1. User initiates imminent peril call + Client1->>Server: 2. MCVideo imminent peril group call request + Note right of Server: 3. Bearer priority adjustment + Server->>Client2: 4. MCVideo imminent peril group call request + Server->>Client3: 4. MCVideo imminent peril group call request + Note right of Client2: 5. Notify imminent peril status + Note right of Client3: 5. Notify imminent peril status + Client2-->>Server: 6. MCVideo imminent peril group call response + Client3-->>Server: 6. MCVideo imminent peril group call response + Server->>Client1: 7. MCVideo imminent peril group call response + +``` + +Sequence diagram showing the upgrade of an MCVideo group call 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 from the server to the user. + +**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. + + + +``` + +sequenceDiagram + participant C1 as MCVideo client 1 + participant S as MCVideo server + participant GMS as Group management server + participant C2 as MCVideo client 2 + participant C3 as MCVideo client 3 + + Note over C1: 1. initiate imminent peril cancel + C1->>S: 2. MCVideo imminent peril group call cancel request + Note over S: 3. Bearer priority adjustment + Note over S: 4. Resolve group id + S->>C2: 5. MCVideo imminent peril group call cancel request + S->>C3: 5. MCVideo imminent peril group call cancel request + Note over C2: 6. Notify Imminent peril cancel + Note over C3: 6. Notify Imminent peril cancel + C2-->>S: 7. MCVideo imminent peril group call cancel response + C3-->>S: 7. MCVideo imminent peril group call cancel response + S->>C1: 8. MCVideo imminent peril group call cancel response + +``` + +Sequence diagram for MCVideo imminent peril group call cancel + +**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** + +| Information Element | Status | Description | +|------------------------------------|---------------|--------------------------------------------------------------------------------------------------------------| +| 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** + +| Information Element | Status | Description | +|----------------------------|---------------|------------------------------------------------------------------| +| 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** + +| Information Element | Status | Description | +|---------------------|--------|--------------------------------------------------------------| +| 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** + +| Information Element | Status | Description | +|---------------------|--------|---------------------------------------------------------| +| 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** + +| Information Element | Status | Description | +|---------------------|--------|--------------------------------------------------------------| +| 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** + +| Information Element | Status | Description | +|---------------------|--------|---------------------------------------------------------| +| 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. + + + +``` + +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. + + + +``` +sequenceDiagram + participant MCVideo client 1 + participant MCVideo client N + participant MCVideo client X + Note right of MCVideo client X: 1. MCVideo client enters in communication range + MCVideo client N->>MCVideo client 1: 2. Periodic group communication announcement + Note right of MCVideo client X: 3. Set parameters for media plane + MCVideo client X-->>MCVideo client 1: 4. Group communication answer response + Note over MCVideo client 1, MCVideo client N: 5. MCVideo group communication with periodic group communication announcements +``` + +Sequence diagram illustrating the passive join procedure to an MCVideo group communication. The diagram shows three lifelines: MCVideo client 1, MCVideo client N, and MCVideo client X. The sequence of events is: 1. MCVideo client X enters the communication range (dashed line from X to N). 2. MCVideo client N sends a periodic group communication announcement (solid line from N to 1). 3. MCVideo client X sets parameters for the media plane (solid line from X to N). 4. MCVideo client X sends a group communication answer response (dashed line from X to 1). 5. MCVideo group communication with periodic group communication announcements (solid line from N to 1). + +**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. + + + +``` +sequenceDiagram + participant MCVideo client 1 + participant MCVideo client N + participant MCVideo client X + Note right of MCVideo client X: 3. Set parameters for media plane + MCVideo client X->>MCVideo client N: 1. Group communication announcement + MCVideo client N->>MCVideo client X: 2. Group communication announcement + MCVideo client X-->>MCVideo client N: 3. Group communication answer response + Note bottom: 5. MCVideo group communication with periodic group communication announcements +``` + +Sequence diagram illustrating the active join procedure to an MCVideo group communication. The diagram shows three lifelines: MCVideo client 1, MCVideo client N, and MCVideo client X. The sequence of messages is: 1. MCVideo client X sends a 'Group communication announcement' to MCVideo client N. 2. MCVideo client N sends a 'Group communication announcement' to MCVideo client X. 3. MCVideo client X sends a 'Set parameters for media plane' message to itself. 4. MCVideo client X sends a 'Group communication answer response' to MCVideo client N. 5. A box at the bottom indicates 'MCVideo group communication with periodic group communication announcements' involving all three clients. + +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 new MCVideo 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. + + + +``` +sequenceDiagram + participant Client1 as MCVideo client 1 (Originator) + participant Client2 as MCVideo client 2 + participant Client3 as MCVideo client 3 + Note over Client1, Client2, Client3: 1. Group communication setup + Note over Client1, Client2, Client3: 2. Video transmission + Note over Client1, Client2, Client3: 3. Group communication release +``` + +Sequence diagram for Broadcast group communication showing three clients: 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)** + +| Information Element | Status | Description | +|-----------------------------------|--------|-----------------------------------------------------------------------------------------| +| MCVideo ID | M | The MCVideo ID of the calling party | +| Functional alias | O | The functional alias 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 | +| Requested priority | O | Application priority level requested for this 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)** + +| Information Element | Status | Description | +|-----------------------------------|--------|-----------------------------------------------------------------------------------------| +| MCVideo ID | M | The MCVideo ID of the calling party | +| Functional alias | O | The functional alias 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 | +| Functional alias | O | The functional alias 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 | +| Functional alias | O | The functional alias 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. +4. Optionally, the MCVideo client 1 may have a functional alias activated to be used. +5. The MCVideo server may have subscribed to the MCVideo functional alias controlling server within the MC system for functional alias activation/de-activation updates. + + + +``` + +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 + MCVideo server->>MCVideo client 1: 4. MCVideo progress indication + Note right of MCVideo server: 3. Authorize request + MCVideo server->>MCVideo client 2: 5. MCVideo private call request + Note right of MCVideo client 2: 6. Notify call + MCVideo client 2->>MCVideo server: 7. MCVideo private call response + MCVideo server->>MCVideo client 1: 8. MCVideo private call response + Note bottom: 9. Media plane and transmission control is established + +``` + +Sequence diagram illustrating the private call setup in automatic commencement mode between two MCVideo clients and an MCVideo server. + +**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. The MCVideo user at MCVideo client 1 may include a functional alias used within the MCVideo private call. + 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. MCVideo server verifies whether the provided functional alias, if present, can be used and has been activated for the user. 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 and, if available the functional alias 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. If the functional alias of the calling user is included it is displayed. + 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. +4. Optionally, the MCVideo client 1 may have a functional alias activated to be used. +5. The MCVideo server may have subscribed to the MCVideo functional alias controlling server within the MC system for functional alias activation/de-activation updates. + + + +``` + +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 server->>MCVideo client 2: 6a. MCVideo ringing + MCVideo client 2-->>MCVideo server: 7. User is notified and accepts the call + MCVideo server->>MCVideo client 1: 9. MCVideo private call response + Note right of MCVideo server: 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 call initiation, request routing, authorization check, ringing, acceptance, 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. The MCVideo user at MCVideo client 1 may include a functional alias used within the MCVideo private call. +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. MCVideo server verifies whether the provided functional alias, if present, can be used and has been activated for the user. 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, and, if available the functional alias 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. If the functional alias of the calling user is included it is displayed. +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. + + + +``` +sequenceDiagram + participant MCVideo client 1 + participant MCVideo server + participant MCVideo client 2 + Note left of MCVideo client 1: 1. Release private call + MCVideo client 1->>MCVideo server: 2. MCVideo call end request + MCVideo server->>MCVideo client 2: 3. MCVideo call end request + Note right of MCVideo client 2: 4. Notify call termination + MCVideo client 2->>MCVideo server: 5. MCVideo call end response + MCVideo server->>MCVideo client 1: 6. MCVideo call end response + Note bottom: 7. Media plane and transmission control resources are released +``` + +The diagram is a sequence diagram illustrating the 'Private call release – client initiated' procedure. It features three lifelines: 'MCVideo client 1', 'MCVideo server', and 'MCVideo client 2'. The sequence of messages is as follows: 1. A self-message on MCVideo client 1 labeled '1. Release private call'. 2. A message from MCVideo client 1 to MCVideo server labeled '2. MCVideo call end request'. 3. A message from MCVideo server to MCVideo client 2 labeled '3. MCVideo call end request'. 4. A self-message on MCVideo client 2 labeled '4. Notify call termination'. 5. A message from MCVideo client 2 to MCVideo server labeled '5. MCVideo call end response'. 6. A message from MCVideo server to MCVideo client 1 labeled '6. MCVideo call end response'. 7. A final message spanning all three lifelines labeled '7. Media plane and transmission control resources are released'. + +Sequence diagram for Private call release – client initiated + +**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. + + + +``` + +sequenceDiagram + participant MCVideo client 1 + participant MCVideo server + participant MCVideo client 2 + Note right of MCVideo server: 1. Conditions to trigger terminate private call + MCVideo server->>MCVideo client 1: 2. MCVideo call end request + MCVideo server->>MCVideo client 2: 2. MCVideo call end request + Note left of MCVideo client 1: 3. Notify call termination + Note right of MCVideo client 2: 3. Notify call termination + MCVideo client 1->>MCVideo server: 4. MCVideo call end response + MCVideo client 2->>MCVideo server: 4. MCVideo call end response + Note bottom: 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. The process involves conditions to trigger termination, sending call end requests, notifying call termination, sending call end responses, and finally releasing media plane and transmission control resources. + +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. +- 3. Optionally, the MCVideo client 1 may have a functional alias activated to be used. +- 4. The MCVideo server may have subscribed to the MCVideo functional alias controlling server within the MC system for functional alias activation/de-activation updates. + + + +``` + +sequenceDiagram + participant C1 as MCVideo client 1 + participant S as MCVideo server + participant C2 as MCVideo client 2 + Note over C1: 1. initiate emergency call + C1->>S: 2. MCVideo emergency private call request + S->>C2: 3. MCVideo emergency private call request + Note over C2: 4. Notify emergency call + C2->>S: 5. MCVideo emergency private call response + Note over S: 6. Bearer priority adjustment + S->>C1: 7. MCVideo emergency private call response + Note over C1,C2: 8. Media plane and transmission control establishment + +``` + +Sequence diagram for MCVideo emergency private call. The diagram shows three vertical lifelines: MCVideo client 1, MCVideo server, and MCVideo client 2. 1. An internal box at MCVideo client 1 labeled '1. initiate emergency call'. 2. An arrow from MCVideo client 1 to MCVideo server labeled '2. MCVideo emergency private call request'. 3. An arrow from MCVideo server to MCVideo client 2 labeled '3. MCVideo emergency private call request'. 4. An internal box at MCVideo client 2 labeled '4. Notify emergency call'. 5. An arrow from MCVideo client 2 back to MCVideo server labeled '5. MCVideo emergency private call response'. 6. An internal box at MCVideo server labeled '6. Bearer priority adjustment'. 7. An arrow from MCVideo server back to MCVideo client 1 labeled '7. MCVideo emergency private call response'. 8. A wide horizontal box spanning all three lifelines at the bottom labeled '8. Media plane and transmission control establishment'. + +**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 user at MCVideo client 1 may include a functional alias used within the MCVideo emergency private call. The MCVideo server verifies whether the provided functional alias can be used. 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. If available the request contains the functional alias of the calling MCVideo user 1. +4. The MCVideo user on MCVideo client 2 is notified of the incoming MCVideo emergency private call. If the functional alias of the calling user is included it is displayed. +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. + + + +``` + +sequenceDiagram + participant MCVideo client 1 + participant MCVideo server + participant MCVideo client 2 + Note over all: 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 over all: 8. Private call continues as a private emergency call + +``` + +Sequence diagram illustrating the MCVideo private call upgrade process. The diagram shows three lifelines: MCVideo client 1, MCVideo server, and MCVideo client 2. The process starts with a 'Private call already in progress' state. Step 1: User initiates emergency at MCVideo client 1. Step 2: MCVideo client 1 sends an 'MCVideo emergency private call request' to the MCVideo server. Step 3: MCVideo server sends the request to MCVideo client 2. Step 4: MCVideo client 2 notifies the user of the emergency status. Step 5: MCVideo client 2 sends an 'MCVideo emergency private call response' to the MCVideo server. Step 6: MCVideo server performs 'Bearer priority adjustment'. Step 7: MCVideo server sends the response to MCVideo client 1. Step 8: The private call continues as a private emergency call. + +**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.** + + + +``` +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 + Note over MCVideo client A, MCVideo client B: 5. Video Transmission from MCVideo client A to MCVideo client B + + MCVideo client A->>MCVideo client B: 1. Private communication request + MCVideo client B->>MCVideo client A: 3a. Private communication answer response +``` + +The diagram is a sequence diagram showing the interaction between MCVideo client A and MCVideo client B. The sequence of messages is as follows: 1. MCVideo client A sends a 'Private communication request' to MCVideo client B. 2. MCVideo client B performs an internal check to determine if it is the designated client. 3a. MCVideo client B sends a 'Private communication answer response' back to MCVideo client A. 3b. MCVideo client B sends a notification to its associated MCVideo user. 4. Both clients proceed to 'Establish media plane'. 5. Finally, 'Video Transmission from MCVideo client A to MCVideo client B' occurs. + +Sequence diagram illustrating the off-network automatic commencement private communication procedure 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.** + + + +``` + +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 + +``` + +The diagram shows a sequence of 8 steps for establishing a private communication between MCVideo client A and MCVideo client B. It starts with a request from A to B. B performs internal checks and presents the request to the user while sending a ringing response back to A. A notifies its user. Once the user at B answers, an answer response is sent to A. Both clients then establish a media plane, followed by video transmission from A to B. + +Sequence diagram for off-network manual commencement private communication – Accepted + +**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.** + + + +``` + +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 rejects or ignores + B-->>A: 6. Private communication reject response + Note left of A: 7. Notify MCVideo user that the request is rejected or ignored + +``` + +The sequence diagram illustrates the interaction between MCVideo client A and MCVideo client B for a rejected or ignored private communication. + 1. MCVideo client A sends a 'Private communication request' to MCVideo client B. + 2. MCVideo client B checks if it is the designated client. + 3a. MCVideo client B presents the incoming communication request to the user. + 3b. MCVideo client B sends a 'Private communication ringing response' back to client A. + 4. MCVideo client A notifies its user that the request is presented. + 5. The user at MCVideo client B rejects or ignores the request. + 6. MCVideo client B sends a 'Private communication reject response' to client A. + 7. MCVideo client A notifies its user that the request is rejected or ignored. + +Sequence diagram illustrating the procedure for off-network manual commencement private communication that is rejected or ignored. + +**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. + + + +``` + +sequenceDiagram + participant A as MCVideo client A + participant B as MCVideo client B + participant U as MCVideo user + A->>B: 1. Private communication release request + B-->>A: 2a. Private communication release response + B->>U: 2b. Notify MCVideo user + Note over A,B: 3. Release media plane + +``` + +Sequence diagram for Off-network Private communication release. The diagram shows three lifelines: MCVideo client A, MCVideo client B, and MCVideo user. Step 1: MCVideo client A sends a 'Private communication release request' to MCVideo client B. Step 2a: MCVideo client B sends a 'Private communication release response' back to MCVideo client A. Step 2b: MCVideo client B sends a 'Notify MCVideo user' message to the MCVideo user lifeline. Step 3: A 'Release media plane' message is shown as a horizontal bar across the bottom of the diagram, indicating a common 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 | +| Requested priority | O | Application priority level requested for this call | + +#### 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. + +Pre-conditions: + +1. Optionally, MCVideo client 1 may have a functional alias activated to be used. +2. The MCVideo server may have subscribed to the MCVideo functional alias controlling server within the MC system for functional alias activation/de-activation updates. + + + +``` + +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 bottom: 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 (all three). + +**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. The MCVideo user at MCVideo client 1 may include a functional alias used within the MCVideo private call request. +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. MCVideo server verifies whether the provided functional alias, if present, can be used and has been activated for the user. +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, and, if available the functional alias 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. If a functional alias of the calling user is included it is displayed. + +NOTE 1: Step 3 can occur at any time following step 4, and prior to step 6. + +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 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. + + + +``` + +sequenceDiagram + participant MCVideo client 1 + participant MCVideo server + Note right of MCVideo server: 2. Authorization check + Note over MCVideo client 1, MCVideo server: 4. Media plane and transmission control established + MCVideo client 1->>MCVideo server: 1. MCVideo push to server request + MCVideo server-->>MCVideo client 1: 3. MCVideo push to server response + Note right of 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 + +``` + +Sequence diagram for One-from-server video pull. Lifelines: MCVideo client 1 and MCVideo server. The sequence starts with MCVideo client 1 sending a '1. MCVideo push to server request' to MCVideo server. MCVideo server performs an '2. Authorization check' and sends a '3. MCVideo push to server response' back. A box labeled '4. Media plane and transmission control established' spans both lifelines. Then, a '5. Video stream from MCVideo client 1' is shown as a large arrow from server to client. MCVideo client 1 sends a '6. MCVideo push to server complete request' to MCVideo server, which responds with '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. + + + +``` + +sequenceDiagram + participant MCVideo client A + participant MCVideo client B + Note right of MCVideo client B: 2a. MCVideo Pull notification to the MCVideo user + MCVideo client A->>MCVideo client B: 1. Private communication request (Video Pull ) + MCVideo client B-->>MCVideo client A: 2b. Private communication answer response (Video Pull ) + Note left of MCVideo client A: 3. Notify response to MCVideo user + Note over MCVideo client A, MCVideo client B: 4. Establish media plane + Note left of MCVideo client A: 5. Video from MCVideo client B to MCVideo client A + +``` + +Sequence diagram showing the procedure for an off-network video pull to self between MCVideo client A and MCVideo client B. The steps are: 1. Private communication request (Video Pull) from client A to client B; 2a. MCVideo Pull notification to the MCVideo user at client B; 2b. Private communication answer response (Video Pull) from client B to client A; 3. Notify response to MCVideo user at client A; 4. Establish media plane between clients; 5. 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 | +| Functional alias | O | The functional alias of the 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 | +| Requested priority | O | Application priority level requested for this call | +| 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 | +| Requested priority | O | Application priority level requested for this call | + +#### 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: + +1. 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. +2. Optionally, MCVideo client 1 may have a functional alias activated to be used. +3. The MCVideo server may have subscribed to the MCVideo functional alias controlling server within the MC system for functional alias activation/de-activation updates. + + + +``` + +sequenceDiagram + participant M1 as MCVideoclient 1 + participant S as MCVideoserver + participant M2 as MCVideoclient 2 + Note right of M2: Error! No text of specified style in + M1->>S: 1. Private call request + S->>S: 2. Authorization check + S-->>M1: 3. Private call progress indication + S->>M2: 4. Private call request + M2->>M2: 5. Notify user + M2->>S: 6. Private call response + S->>M1: 7. Private call response + Note over M1, S, M2: 8. Media plane and transmission control established + +``` + +Sequence diagram for One-to-one video push. Lifelines: MCVideoclient 1, MCVideoserver, and MCVideoclient 2. The sequence of messages is: 1. Private call request (M1 to S), 2. Authorization check (S to S), 3. Private call progress indication (S to M1), 4. Private call request (S to M2), 5. Notify user (M2 to M2), 6. Private call response (M2 to S), 7. Private call response (S to M1), and 8. Media plane and transmission control established (M1, S, and M2). + +**Figure 7.4.2.3.2-1: One-to-one video push** + +1. MCVideoclient 1 initiates push video to MCVideoclient 2, and sends a private call request to the MCVideoserver using a service identifier as defined in 3GPP TS 23.228 [5] for MCVideoclient, for establishing a private call with the chosen MCVideoclient user for video push. The MCVideoclient private call request contains MCVideoclient 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. The MCVideoclient user at MCVideoclient 1 may include a functional alias used within the MCVideoclient private call request. +2. MCVideoserver checks whether the MCVideoclient user at MCVideoclient 1 is authorized to initiate the private call for video push, and that MCVideoclient user at MCVideoclient 2 is authorized to receive the private call for video push. MCVideoserver verifies whether the provided functional alias, if present, can be used and has been activated for the user. +3. MCVideoserver may provide a progress indication to MCVideoclient 1 to indicate progress in the call setup process. +4. If authorized, MCVideoserver includes information that it communicates using MCVideoclient 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 MCVideoclient and sends the corresponding MCVideoclient private call request towards the MCVideoclient 2, including the MCVideoclient ID and, if available the functional alias of the calling MCVideoclient user 1. If the called MCVideoclient user has registered to the MCVideoclient service with multiple MCVideoclient UEs and has designated the MCVideoclient UE for receiving the private calls, then the incoming MCVideoclient private call request is delivered only to the designated MCVideoclient UE. +5. The MCVideoclient 2 notifies the user about the incoming private call for video push. If the functional alias of the calling user is included it is displayed. +6. The MCVideoclient 2 accepts the private call for video push, and sends an MCVideoclient private call response to the MCVideoserver. +7. Upon receiving the MCVideoclient private call response from MCVideoclient 2 accepting the private call request for video push, the MCVideoserver informs the MCVideoclient 1 about successful call establishment via a private call response message. +8. MCVideoclient 1 and MCVideoclient 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. + + + +``` + +sequenceDiagram + participant MCVideo client 1 + participant MCVideo server + Note right of MCVideo server: 2. Authorization check + Note left of MCVideo client 1: 4. Media plane and transmission control established + MCVideo client 1->>MCVideo server: 1. MCVideo push to server request + MCVideo server-->>MCVideo client 1: 3. MCVideo push to server response + 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 + +``` + +Sequence diagram showing the one-to-server video push procedure between MCVideo client 1 and MCVideo server. 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.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. + + + +``` + +sequenceDiagram + participant Client3 as MCVideo client 3 + participant Server as MCVideo server + participant Client1 as MCVideo client 1 + participant Client2 as MCVideo client 2 + + Note right of Server: 2. Check for authorization and whether any on-going private call between source user and destination user + + Client3->>Server: 1. Remote video push request + Server->>Client1: 3. Remote video push request + Note over Client1, Client2: 4. Establish one-to-one video push call between MCVideo client 1 and MCVideo client 2 + Client1->>Server: 5. Remote video push response + Server->>Client3: 6. Remote video push response + +``` + +Sequence diagram for remotely initiated video push call setup. Lifelines: MCVideo client 1, MCVideo server, MCVideo client 2, MCVideo client 3. The sequence starts with a '1. Remote video push request' from client 3 to the server. The server performs a '2. Check for authorization and whether any on-going private call between source user and destination user'. It then sends a '3. Remote video push request' to client 1. A box labeled '4. Establish one-to-one video push call between MCVideo client 1 and MCVideo client 2' spans between client 1 and client 2. Client 1 sends a '5. Remote video push response' to the server, which in turn sends a '6. Remote video push response' to 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. + + + +``` + +sequenceDiagram + participant C1 as MCVideo client 1 + participant S as MCVideo server + participant C2 as MCVideo client 2 + participant C3 as MCVideo client 3 + + C3->>S: 1. Remote video push release request + Note over S: 2. Check for authorization and +whether any on-going private call +between source user and +destination user + S->>C1: 3. Remote video push release request + Note over C1,C2: 4. Release the one-to-one video push call between MCVideo client 1 and MCVideo client 2 + C1->>S: 5. Remote video push release response + S->>C3: 6. Remote video push release response + +``` + +Sequence diagram showing the call release procedure between MCVideo client 1, MCVideo server, MCVideo client 2, and MCVideo client 3. The steps are: 1. MCVideo client 3 sends a 'Remote video push release 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 release request' to MCVideo client 1. 4. MCVideo client 1 performs the release procedure for the call with MCVideo client 2. 5. MCVideo client 1 sends a 'Remote video push release response' to the MCVideo server. 6. The MCVideo server sends a 'Remote video push release response' to MCVideo 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. + + + +``` + +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 + activate MCVideo client 2 + Note over MCVideo client 2: 4. Broadcast group call initiated by MCVideo client 2 + deactivate 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 for 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: A 'Broadcast group call initiated by MCVideo client 2' is shown as a wide activation bar. 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. + + + +``` + +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 left of MCVideo client 1: 6. Broadcast group call release by remote user + +``` + +Sequence diagram showing the interaction between MCVideo client 1, MCVideo server, and MCVideo client 2 for a remote video push release request. The steps are: 1. Remote video push release request from client 1 to server; 2. Check for user authorization and whether there is a on-going video pull to group call (internal server step); 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 (action 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. + + + +``` + +sequenceDiagram + participant A as MCVideo client A + participant B as MCVideo client B + participant C as MCVideo client C + + B->>C: 1. Private communication request (Video push) + Note right of C: 2a. Notify MCVideo Push request + C-->>B: 2b. Private communication answer response (Video push) + B->>A: 3a. Notification of video push to MCVideo client C + Note left of A: 3b. Notify MCVideo user + rect rgb(240, 240, 240) + Note over B,C: 4. Establish media plane + end + B->>C: 5. Video from MCVideo client B to MCVideo client C + +``` + +Sequence diagram for Off-network Video push to another MCVideo user. Lifelines: MCVideo client A, MCVideo client B, MCVideo client C. Steps: 1. Private communication request (Video push) from B to C; 2a. Notify MCVideo Push request from C; 2b. Private communication answer response (Video push) from C to B; 3a. Notification of video push to MCVideo client C from B to A; 3b. Notify MCVideo user at A; 4. Establish media plane between B and C; 5. Video from MCVideo client B to MCVideo 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. + + + +``` + +sequenceDiagram + participant A as MCVideo client A + participant B as MCVideo client B + participant C as MCVideo client C + Note left of A: 6. Notify MCVideo user + Note right of C: 4b. Notify connection request to MCVideo user + + A->>B: 1. Remote video push request + Note right of B: 2a. MCVideo client B discovers MCVideo client C + Note right of B: 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) + B-->>A: 5. Notification of video push to MCVideo client C + Note right of B: 7. Establish media plane + B->>C: 8. Video from MCVideo client B to MCVideo client C + +``` + +Sequence diagram illustrating the remotely initiated off-network video push process between MCVideo client A, MCVideo client B, and MCVideo client C. + +**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. + + + +``` + +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 + Note right of MCVideo group G: 3. Group communication + +``` + +Sequence diagram for Remotely initiated video push to a group. The diagram shows three lifelines: MCVideo Client B, MCVideo Client A, and MCVideo group G. Step 1: MCVideo Client A sends a 'Remote video push request' to both MCVideo Client B and MCVideo group G. Step 2: MCVideo Client B sends a 'Notify remote push request' to MCVideo group G. Step 3: A 'Group communication' phase occurs between MCVideo Client B and MCVideo group G. + +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 (see NOTE) | O | List of Identities of the target MCVideo users | +| MCVideo group ID list (see 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 (see NOTE) | M | Identity of the MCVideo user whose MCVideo capabilities are requested | +| MCVideo capabilities (see 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. + + + +``` + +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 + +``` + +Sequence diagram for Update MCVideo capabilities information at the MCVideo server. The diagram shows two lifelines: MCVideo client and MCVideo server. The client sends a '1. Update MCVideo capabilities info request' to the server. The server performs an internal '2. Update MCVideo capabilities information' process. Finally, the server sends a '3. Update MCVideo capabilities info response' back to the client. + +**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. + + + +``` + +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 + +``` + +Sequence diagram for Retrieve MCVideo capabilities information by the MCVideo client. The diagram shows two lifelines: MCVideo client and MCVideo server. The client sends a '1. Get MCVideo capabilities info request' to the server. The server performs an internal '2. Authorization check' process. Finally, the server sends a '3. Get MCVideo capabilities info response' back to the 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. + + + +``` + +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 + +``` + +Sequence diagram showing a subscription flow. The MCVideo client sends a 'Subscribe MCVideo capabilities info request' (message 1) to the MCVideo server. The MCVideo server then sends a 'Subscribe MCVideo capabilities info response' (message 2) back to the MCVideo client. + +**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. + + + +``` + +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 + +``` + +Sequence diagram showing a notification flow. The MCVideo server sends a 'Notify MCVideo capabilities info request' (message 1) to the MCVideo client. The MCVideo client then sends a 'Notify MCVideo capabilities info response' (message 2) back to the MCVideo server. + +**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: + +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. + + + +``` + +sequenceDiagram + participant MCVideo client 1 + participant MCVideo client 2 + participant MCVideo client N + Note left of MCVideo client 1: + MCVideo client 1->>MCVideo client 2: 1. Capability announcement + MCVideo client 1->>MCVideo client N: 1. Capability announcement + Note right of MCVideo client 2: 2. Cache MCVideo client 1's presence and capabilities + Note right of MCVideo client N: 2. Cache MCVideo client 1's presence and capabilities + +``` + +Sequence diagram showing periodic capability announcements between MCVideo client 1, client 2, and client N. Step 1: MCVideo client 1 sends a 'Capability announcement' to clients 2 and N. Step 2: Clients 2 and N perform '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. + + + +``` + +sequenceDiagram + participant MCVideo client 1 + participant MCVideo client 2 + participant MCVideo client N + Note right of MCVideo client N: 3. Cache presence and capabilities of other MCVideo clients + MCVideo client 1->>MCVideo client 2: 1. Capability request + MCVideo client 2->>MCVideo client 1: 2. Capability announcement + MCVideo client N->>MCVideo client 1: 2. Capability announcement + +``` + +The diagram shows three MCVideo clients: client 1, client 2, and client N. Client 1 sends a '1. Capability request' message to clients 2 and N. Clients 2 and N respond with '2. Capability announcement' messages back to client 1. A box at the bottom indicates that client 1 will '3. Cache presence and capabilities of other MCVideo clients'. + +Sequence diagram illustrating the request and response process for video capabilities among MCVideo clients. + +**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. + + + +``` +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 +``` + +The diagram illustrates a sequence of interactions between two MCVideo clients. MCVideo client 1 sends a '1. Capability request' message to MCVideo client 2. MCVideo client 2 responds with a '2. Capability announcement' message. Upon receiving the announcement, MCVideo client 1 performs a local action labeled '3. Cache presence and capabilities of the MCVideo client 2'. + +Sequence diagram showing the interaction between MCVideo client 1 and MCVideo client 2 for requesting and caching capabilities. + +**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 criterions, 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. + + + +``` +sequenceDiagram + participant MCVideo client 1 + participant MCVideo client 2 + participant MCVideo client N + Note right of MCVideo client N: Cache presence and activity status of other MCVideo clients + MCVideo client 1->>MCVideo client 2: 1. Activity status request + MCVideo client 1->>MCVideo client N: 1. Activity status request + MCVideo client 2->>MCVideo client 1: 2. Activity status announcement + MCVideo client N->>MCVideo client 1: 2. Activity status announcement + Note left of MCVideo client 1: 3. Cache presence and activity status of other MCVideo clients +``` + +Sequence diagram showing the request activity status of group members. MCVideo client 1 sends an activity status request to MCVideo client 2 and MCVideo client N. MCVideo client 2 and MCVideo client N respond with activity status announcements. MCVideo client 1 then caches the presence and activity status of other MCVideo clients. + +**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. + + + +``` +sequenceDiagram + participant MCVideo client 1 + participant MCVideo client 2 + Note left of MCVideo client 1: 3. Cache presence and activity status of the MCVideo client 2 + MCVideo client 1->>MCVideo client 2: 1. Activity status request + MCVideo client 2-->>MCVideo client 1: 2. Activity status announcement +``` + +The diagram illustrates a sequence of three steps between two MCVideo clients. MCVideo client 1 sends a message labeled '1. Activity status request' to MCVideo client 2. MCVideo client 2 responds with a message labeled '2. Activity status announcement' back to MCVideo client 1. Finally, a note on the left side of MCVideo client 1 indicates '3. Cache presence and activity status of the MCVideo client 2'. + +Sequence diagram showing the interaction between MCVideo client 1 and MCVideo client 2 to request activity status. + +**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 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** + +| Information Element | Status | Description | +|----------------------------|---------------|-----------------------------------------------------------------------------------------------------------------------| +| 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** + +| Information Element | Status | Description | +|----------------------------|---------------|-----------------------------------------------------------------------------------------------------------------------| +| 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** + +| Information Element | Status | Description | +|----------------------|--------|-----------------------------------------------------------------------------------------------------------------------| +| 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. + + + +``` + +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 1: 5.Ambient viewing call response + MCVideo server->>MCVideo client 2: 6. Transmit media granted + Note left of MCVideo client 1: 7. Media transmission + Note right of MCVideo client 2: 7. Media transmission + MCVideo client 2->>MCVideo client 1: 7. Media transmission + +``` + +Sequence diagram for Figure 7.6.3.1-1: Remotely initiated ambient viewing call setup. Lifelines: MCVideo client 1, MCVideo server, MCVideo client 2. Steps: 1. Ambient viewing call request (client 1 to server), 2. Authorize ambient viewing call request (server internal), 3. Ambient viewing call request (server to client 2), 4. Ambient viewing call response (client 2 to server), 5. Ambient viewing call response (server to client 1), 6. Transmit media granted (server to client 2), 7. Media transmission (client 2 to client 1). + +**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. + + + +``` +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 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 right of MCVideo server: 2.Authorize ambient viewing call request + MCVideo client 1->>MCVideo server: 7. Video transmission + MCVideo client 2->>MCVideo server: 7. Video transmission +``` + +Sequence diagram for Figure 7.6.3.2-1: Locally initiated ambient viewing call setup. The diagram shows three lifelines: MCVideo client 1, MCVideo server, and MCVideo client 2. The sequence of messages is: 1. MCVideo client 2 sends an 'Ambient viewing call request' to the MCVideo server. 2. The MCVideo server performs an 'Authorize ambient viewing call request' check. 3. The MCVideo server sends an 'Ambient viewing call request' to MCVideo client 1. 4. MCVideo client 1 returns an 'Ambient viewing call response' to the MCVideo server. 5. The MCVideo server sends an 'Ambient viewing call response' to MCVideo client 2. 6. The MCVideo server sends a 'Transmit media granted' message to MCVideo client 2. 7. MCVideo client 1 and MCVideo client 2 both perform 'Video transmission'. + +**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. + + + +``` + +sequenceDiagram + participant C1 as MCVideo client 1 + participant S as MCVideo server + participant C2 as MCVideo client 2 + Note over S: 1.Ambient viewing call +release is triggered + 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 +notification + Note over C1: 6.Notify user + +``` + +Sequence diagram for Ambient viewing call release – server initiated. Lifelines: MCVideo client 1, MCVideo server, MCVideo 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 to client 1, and finally notifying the user. + +**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. + + + +``` + +sequenceDiagram + participant MCVideo client 1 + participant MCVideo server + participant MCVideo client 2 + Note right of MCVideo client 2: Stop transmitting media + MCVideo client 1->>MCVideo server: 1.Ambient viewing call release request + MCVideo server->>MCVideo client 2: 2.Ambient viewing call release request + MCVideo client 2->>MCVideo server: 4.Ambient viewing call release response + MCVideo server->>MCVideo client 1: 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. + + + +``` + +sequenceDiagram + participant MCVideo client 1 + participant MCVideo server + participant MCVideo client 2 + Note left of MCVideo client 1: Notify user + Note right of MCVideo client 2: Stop transmitting media + MCVideo client 2->>MCVideo server: 1.Ambient viewing call release request + MCVideo server->>MCVideo client 1: 2.Ambient viewing call release request + MCVideo client 1->>MCVideo server: 4.Ambient viewing call release response + MCVideo server->>MCVideo client 2: 5.Ambient viewing call release response + +``` + +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 NOTE 1) | Position of the queued transmit media request in the queue | +| Media identifier | O
(see NOTE 2) | 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 | +| NOTE 1: If revoke reason is queuing, then queue position info is included.
NOTE 2: 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. + + + +``` + +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. + + + +``` + +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 left 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 configuration-based mode decision, media transmission notification, user intent, media request, availability check, media response, video transmission, and optional media reception notification. + +**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 'End media reception – receiving user initiated'. Lifelines: Transmission control participant A, Transmission control server, and Transmission control participant B. The sequence starts with a user action '1. User determines to end receiving the video stream.' from participant B. This is followed by a '2. Media reception end request' message from participant B to the server. The server responds with '3. Media reception end response' to participant B. The server then performs '4. stop sending downlink video stream selected to be ended by user'. Finally, a dashed box indicates an optional step: '5. Optionally, transmission control server initiated end media transmission procedure as described in subclause 7.7.1.3.6.2.' + +**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. + + + +``` + +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), stopping the stream (5), and optionally initiating an end procedure (6). + +**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 participants 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 participants 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. + + + +``` + +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 of steps is: 1. Maximum number of simultaneous receiving streams detect (at server), 2. Media reception override notification (server to B), 3. Notify user the override (B), 4. Transmission control server initiated media reception end procedure as described in subclause 7.7.1.3.2.B, 5. Normal reception control procedure as described in subclause 7.7.1.3.2. + +**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. + + + +``` + +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 transmission notification + Note right of B: 3. Notify user and the user determines to reject or override. + Note right of B: 4. User initiated media reception end procedure as described in subclause 7.7.1.3.2A. + Note right of B: 5. Request to receive newly video stream as described in subclause 7.7.1.3.2. + +``` + +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 messages is: 1. Maximum number of simultaneous receiving streams detect (from server to participant B); 2. Media transmission notification (from server to participant B); 3. Notify user and the user determines to reject or override (from participant B to server); 4. User initiated media reception end procedure as described in subclause 7.7.1.3.2A (from participant B to participant A); 5. Request to receive newly video stream as described in subclause 7.7.1.3.2 (from participant B to 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. + + + +``` + +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. + + + +``` + +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 + Note right of S: 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. + + + +``` + +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 right of A: 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. The diagram shows four lifelines: Transmission control participant A, Transmission control server, Transmission control participant B, and Transmission control participant C. A pre-condition box states that transmission control is established, participant B has permission to transmit, and participants A and C are in the video transmission queue. The sequence of messages is: 1. User wants to cancel a transmit media request from the video transmission queue (internal to A); 2. Transmit media cancel request (A to Server); 3. Authorization check, and remove transmit media request from the video transmission queue (internal to Server); 4. Transmit media cancel request notify (Server to C); 5. Transmit media cancel response (Server to A). + +**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 showing transmit media request cancellation. Lifelines: Transmission control participant A, Transmission control server, Transmission control participant C. A box at the top states: '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.' The sequence of messages is: 1. Remove the transmit request from the video transmission queue based on policy (from server to itself); 2. Transmit media cancel request notify (from server to participant A); 3. Queue position info (from server 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. + + + +``` + +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. + + + +``` + +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. + + + +``` + +sequenceDiagram + participant A as Transmission control participant A + participant S as Transmission control server + participant B as Transmission control participant B + A->>S: 1. Remote transmit media end request + Note over S: 2. Authorization check for remote termination of the on-going media transmission from transmission control participant B + Note over S: 3. Terminate the on-going media transmission from transmission control participant B + S->>A: 4. Remote transmit media end response + +``` + +Sequence diagram showing the procedure for ending a media transmission by a remote MCVideo user. The diagram involves 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 + + + +``` + +sequenceDiagram + participant A as Transmission control participant A + participant S as Transmission control server + participant B as Transmission control participant B + A->>S: 1. Remote transmit media request + Note over S: 2. Authorization check for remotely +initiating media transmission from +transmission control participant B. +Check for maximum simultaneous +media transmissions limit + 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. Lifelines: Transmission control participant A, Transmission control server, and Transmission control participant B. The sequence is: 1. Remote transmit media request from A to server; 2. Authorization check for remotely initiating media transmission from participant B (including check for maximum simultaneous media transmissions limit) within the 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 flows 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 flows 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. + + + +``` +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: 3a. Transmission arbitration taken + C1->>C2: 3a. Transmission arbitration taken + C1->>C3: 3a. Transmission arbitration taken + C1->>CN: 3a. Transmission arbitration taken + Note left of C1: 4. Media Flow + C1->>C2: 4. Media Flow + C1->>C3: 4. Media Flow + C1->>CN: 4. Media Flow +``` + +Sequence diagram illustrating the initialization of transmission control for a single arbitrator case. The diagram shows four MCVideo clients (client 1, client 2, client 3, and client N). Client 1 sends a 'Transmission request' to the other clients. After a 'No response detected' period, client 1 sends a 'Transmission arbitration taken' message. A dashed box indicates a 'Notify user' step. Finally, a thick arrow labeled 'Media Flow' shows video being transmitted from client 1 to the other clients. + +**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. + + + +``` +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 the other clients. + +**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. + + + +``` +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 granted + TA->>C3: 3. Transmission granted + TA->>CN: 3. Transmission granted + 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 (client 2 to others), 2. Check if limit is reached (client 1), 3. Transmission granted (client 1 to others), 4. Notify user (client 2), 5. Media Flow (client 2 to others). + +**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. + + + +``` +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 rejected + Note right of C2: 4. Notify user +``` + +Sequence diagram illustrating the procedure for requesting transmission permission. 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 rejected from client 1 to clients 2, 3, and N. 4. Notify user (internal to client 2). + +**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. + + + +``` +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 +``` + +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. + +**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. + + + +``` + +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. + + + +``` + +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 + Note left of C1: 4. Revoke transmission + Note left of C1: 7. Release transmission arbitration + + C2->>C1: 1. Transmission request + C1->>C2: 3. Transmission revoked + C1->>C3: 3. Transmission revoked + C1->>CN: 3. Transmission revoked + C1->>C2: 5. Transmission granted (including new arbitrator) + C2->>C1: 6a. Transmission arbitration taken + C2-->>C2: 6b. Notify user + C1->>C2: 7. Release transmission arbitration + Note right of C2: 8. Media Flow + C2->>C3: 8. Media Flow + C2->>CN: 8. Media Flow + +``` + +Sequence diagram titled 'Transmission override' showing the interaction between four MCVideo clients (1 (TA), 2, 3, and N). The sequence starts with client 2 sending a 'Transmission request' to client 1. Client 1 checks its override policy and sends a 'Transmission revoked' message to all clients. Client 1 then sends a 'Transmission granted (including new arbitrator)' message to client 2. Client 2 sends a 'Transmission arbitration taken' message to all clients. Client 1 sends a 'Release transmission arbitration' message. Client 2 may notify its user. Finally, client 2 starts the 'Media Flow' to all clients. + +**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. + + + +``` +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): 2. Release + MCVideo client 1 (TA)->>MCVideo client 2: 1. Transmission arbitration release + Note right of MCVideo client 2: + Note right of MCVideo client 3: + Note right of MCVideo client N: +``` + +Sequence diagram illustrating transmission arbitration release without delegation. Four MCVideo clients are shown: client 1 (TA), client 2, client 3, and client N. Client 1 sends a 'Transmission arbitration release' message to the group. 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. + + + +``` + +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: 1. Stop media transmission + TA->>C2: 2. Transmission arbitration release (delegated to MCVideo client 2) + Note left of TA: 3. No response detected + TA->>C3: 4. Transmission arbitration release (delegated to MCVideo client 3) + Note right of C3: 5. Transmission arbitration taken + C3->>TA: + Note left of TA: 6. Release transmission arbitration + +``` + +Sequence diagram illustrating Transmission arbitration release with delegation. Lifelines: MCVideo client 1 (TA), MCVideo client 2, MCVideo client 3, MCVideo client N. Steps: 1. Stop media transmission; 2. Transmission arbitration release (delegated to MCVideo client 2); 3. No response detected; 4. Transmission arbitration release (delegated to MCVideo client 3); 5. Transmission arbitration taken; 6. Release transmission arbitration. + +**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. + + + +``` + +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: 1a. Transmission request + Client1->>Client3: + Note left of Client2: 1b. Transmission request + Client2->>Client3: + Note left of Client1: 2. Compare priority + Note left of Client2: 2. Compare priority + Note left of Client1: 3. Transmission arbitration taken + Client1->>Client3: + Note left of Client1: 4. Notify user + +``` + +The diagram shows four lifelines: MCVideo client 1, MCVideo client 2, MCVideo client 3, and MCVideo client N. + Step 1a: MCVideo client 1 sends a 'Transmission request' message to the group (indicated by an arrow to MCVideo client 3). + Step 1b: MCVideo client 2 sends a 'Transmission request' message to the group (indicated by an arrow to MCVideo client 3). + Step 2: Both MCVideo client 1 and MCVideo client 2 have a 'Compare priority' block. + Step 3: MCVideo client 1 sends a 'Transmission arbitration taken' message to the group (indicated by an arrow to MCVideo client 3). + Step 4: MCVideo client 1 has a 'Notify user' block, represented by a dashed box. + +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.9a Functional alias management + +The MCVideo service shall support the functional alias activation, de-activation, taken over, subscription and notification and functional alias to group binding procedures and related information flows as specified in subclause 10.13 of 3GPP TS 23.280 [6]. + +- The MC service client is the MCVideo client; +- The MC service server is the MCVideo server; + +###### - The MC service ID is the MCVideo ID. 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 (see 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. + + + +``` + +sequenceDiagram + participant MCVideo client 1 + participant MCVideo server + participant MCVideo Client 2 + participant MCVideo Client 3 + + Note right of MCVideo server: 1. Activation and announcement of MBMS bearer + MCVideo client 1->>MCVideo server: 2. Initial transmit media request + MCVideo server->>MCVideo Client 2: 3. MapGroupToBearer + MCVideo server->>MCVideo Client 3: 3. MapGroupToBearer + MCVideo server->>MCVideo client 1: 4. Transmit media granted + MCVideo server->>MCVideo Client 2: 5. Media transmission notification + MCVideo server->>MCVideo Client 3: 5. Media transmission notification + Note right of MCVideo Client 2: 6. Notify + Note right of MCVideo Client 3: 6. Notify + MCVideo Client 2-->>MCVideo server: 7. Receive media request + MCVideo Client 3-->>MCVideo server: 7. Receive media request + MCVideo Client 2-->>MCVideo server: 8. Receive media response + MCVideo Client 3-->>MCVideo server: 8. Receive media response + Note right of MCVideo client 1: 9. Media flow (uplink unicast) + Note right of MCVideo server: 9. Media flow (downlink MBMS) + +``` + +Sequence diagram showing the procedure for a chat group call connect on an MBMS bearer. The diagram involves four lifelines: MCVideo client 1, MCVideo server, MCVideo Client 2, and MCVideo Client 3. The sequence starts with an activation and announcement of the MBMS bearer from the server. Client 1 sends an initial transmit media request to the server. The server responds with MapGroupToBearer to clients 2 and 3. The server then grants media transmission to client 1 and notifies clients 2 and 3. Clients 2 and 3 send receive media request and receive media response messages to the server. Finally, a media flow (uplink unicast) is established from client 1 to the server, and a media flow (downlink MBMS) is established from the server 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. + + + +``` + +sequenceDiagram + participant C1 as MCVideo client 1 + participant S as MCVideo server + participant C2 as MCVideo client 2 + participant C3 as MCVideo client 3 + + Note over C1, S: 1. Media flow (uplink, unicast) + C1->>S: Media flow + Note over S, C3: 1. Media flow + S->>C2: Media flow + S->>C3: Media flow + + Note over S: 2. Decision to disconnect the call +or dissociate from the MBMS +bearer + + S->>C2: 3. Disconnect / UnmapGroupFromBearer + S->>C3: 3. Disconnect / UnmapGroupFromBearer + +``` + +Sequence diagram showing call disconnect over MBMS. MCVideo client 1 sends media flow (uplink, unicast) to MCVideo server. MCVideo server forwards media flow to MCVideo client 2 and 3. MCVideo server then makes a decision to disconnect or dissociate. Finally, MCVideo server sends Disconnect / UnmapGroupFromBearer to MCVideo client 2 and 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 for MCVideo user authentication and registration, single domain. The diagram shows interactions between MCVideo client, Identity management client, Signalling user agent, SIP core, Identity management server, and MCVideo 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]. Step 2: The MCVideo client performs the service authorization with the MCVideo server.](db39acbd11df5eb7e79ab84562fb8f74_img.jpg) + +``` + +sequenceDiagram + participant MCVideo client + participant Identity management client + participant Signalling user agent + participant SIP core + participant Identity management server + participant MCVideo server + + Note right of Identity management client: 1. User Authentication is based on the procedure – “General user authentication and authorization for MC services” specified in 3GPP TS 23.280[18]. + Note right of MCVideo client: 2. The MCVideo client performs the service authorization with the MCVideo server. + +``` + +Sequence diagram for MCVideo user authentication and registration, single domain. The diagram shows interactions between MCVideo client, Identity management client, Signalling user agent, SIP core, Identity management server, and MCVideo 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]. Step 2: The MCVideo client performs the 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. + + + +``` + +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. The diagram shows two lifelines: MCVideo client A and MCVideo server. The sequence of messages is: 1. MCVideo client query request from client to server; 2. Authorization check and retrieve MCVideo clients (internal server process); 3. MCVideo client query response from server to 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 fulfils 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. + + + +``` + +sequenceDiagram + participant C1 as MCVideo client 1 + participant S as MCVideo server + participant C2 as MCVideo client 2 + Note over C1, C2: 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 MCVideo adaptation procedure. Lifelines: MCVideo client 1, MCVideo server, and MCVideo client 2. The process starts with client 1 transmitting video to the group. Then, client 1 sends a parameter update request to the server. The server performs an authorization check. Upon authorization, the server sends a parameter update request to client 2. Client 2 notifies its user. Client 2 sends a response to the server, which then sends a 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. + + + +``` + +sequenceDiagram + participant C1 as MCVideo client 1 + participant S as MCVideo server + participant C2 as MCVideo client 2 + Note over C1, C2: Client 1 is receiving video from Client 2 within the group communication + C1->>S: 1. MCVideo communication parameter update request + Note over 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 + Note right of C1: 4b. Notify user + Note left of C2: 4a. Notify user + C1->>S: 5b. MCVideo communication parameter update response + C2->>S: 5a. MCVideo communication parameter update response + Note over C1, C2: 6. The MCVideo group communication applies new parameters + +``` + +Sequence diagram showing MCVideo adaptation. MCVideo client 1 sends a parameter update request to the MCVideo server. The server determines to update parameters and sends update requests to both client 1 and client 2. Both clients notify their users and send back update responses. Finally, the group communication applies the new parameters. + +**Figure 7.17.3.2-1: Receiving user triggered MCVideo 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 MCVideo 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. + + + +``` + +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 showing MCVideo client 1, MCVideo server, and MCVideo client 2. The process involves a parameter update request from client 1 to the server, an authorization check, a request from the server to client 2, a user notification, responses from client 2 and the server, and finally the application of 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. + + + +``` + +sequenceDiagram + participant MCVideo client 1 + participant MCVideo server + participant MCVideo client 2 + Note right of MCVideo client 1: MCVideo client 1 is receiving video from MCVideo client 2 + MCVideo client 1->>MCVideo server: 1. MCVideo communication parameter update notification + MCVideo server->>MCVideo server: 2. Determine to update the MCVideo communication parameters + 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 bottom: 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. The process starts with MCVideo client 1 receiving video from MCVideo client 2. Then, MCVideo client 1 sends a parameter update notification to the server. The server determines to update parameters and sends a request to MCVideo client 2. MCVideo client 2 notifies its user and sends a response to the server. The server then sends a response to MCVideo client 1. Finally, the MCVideo communication applies the new parameters. + +**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]) | +| 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-013] of 3GPP TS 22.280 [17] | Automatically trigger a MCVideo emergency communication after initiating the 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 used on initiation of an MCVideo emergency group call (see NOTE 5) | 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 [17] | Recipient for an emergency private MCVideo call (see NOTE 5) | | | | | +| | > MCVideo ID | Y | Y | Y | Y | +| 3GPP TS 33.180 [19] | > KMSUri for security domain of MCVideo ID (see NOTE 1) | 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-6.7.3-007] of 3GPP TS 22.280 [2] | Authorised to make a private video call towards users not included in "list of user(s) who can be called in MCVideo private call" | Y | Y | Y | Y | +| [R-5.1.10.2-002] of 3GPP TS 22.281 [3] | List of category tags | | | | | +| | > Video category tag | 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 | | | | | +| | > Video category tag for query | 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 | | | | | +| | > Geography area to query | 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. +- NOTE 5: 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 MCVideo user's currently selected group will be used. + +**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],
[R-5.1.5-002],
[R-5.10-001],
[R-6.4.7-002],
[R-6.8.1-008],
[R-6.7.4-002] of
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 | Y | Y | Y | +| | > Application plane server identity information of identity management server which provides authorization for group (see NOTE 1) | | | | | +| | >> Server URI | Y | Y | 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
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
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],
[R-6.4.6.1-003] of
3GPP TS 22.280 [2] | 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 [2] | 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 [2] | Authorisation to perform regrouping | Y | Y | Y | Y | +| [R-6.7.2-001] of
3GPP TS 22.280 [2] | 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 [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],
[R-6.8.7.4.2-002] of
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
3GPP TS 22.280 [2] | Authorisation for an MCVideo user to enable/disable an MCVideo 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 [2] | Authorisation for an MCVideo 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 (Nc2) | N | Y | Y | Y | +| [R-6.4.6.1-001],
[R-6.4.6.1-004] of
3GPP TS 22.280 [2] | List of MCVideo users whose selected groups are authorized to be remotely changed | | | | | + +| | | | | | | +|--------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------|---|---|---|---| +| | > MCVideo ID | 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 | +| [R-6.7.3-007a] of
3GPP TS 22.280 [2] | List of user(s) from which MCVideo private calls can be received | | | | | +| | > MCVideo ID | Y | Y | Y | Y | +| | > Presentation priority relative to other users and groups | Y | Y | Y | Y | +| 3GPP TS 33.180 [18] | > KMSUri for security domain of MCVideo ID | Y | Y | Y | Y | +| [R-5.9a-012] of
3GPP TS 22.280 [2]
[R-5.9a-013] of
3GPP TS 22.280 [2] | Authorised to request association between active functional alias(es) and MCVideo ID(s) | | 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 | +| [R-6.6.4.2-002a] and
[R-6.6.4.2-002b] of
3GPP TS 22.280 [2] | List of groups the client affiliates/de-affiliates when criteria is met | | | | | +| | > MCVideo Group ID | Y | Y | Y | Y | +| | >> Criteria for affiliation (see NOTE 7) | Y | Y | Y | Y | +| | >> Criteria for de-affiliation (see NOTE 7) | 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 [2] | List of groups the client affiliates after receiving an emergency alert | | | | | +| | > MCVideo 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.9a-012] of 3GPP TS 22.280 [2] | Authorised to take over a functional alias from another MCVideo user | N | Y | Y | Y | +| | List of functional alias(es) of the MCVideo user | | | | | +| [R-5.9a-005] of 3GPP TS 22.280 [2] | > Functional alias | Y | Y | Y | Y | +| [R-5.9a-018] of 3GPP TS 22.280 [2] | >> MCVideo server trigger criteria for activation (see NOTE 6) | N | Y | Y | Y | +| [R-5.9a-017], [R-5.9a-018] of 3GPP TS 22.280 [2] | >> MCVideo server trigger criteria for de-activation (see NOTE 6) | N | Y | Y | Y | +| [R-5.9a-019] of 3GPP TS 22.280 [16] | >> MCVideo client trigger criteria for activation (see NOTE 6) | Y | Y | Y | Y | +| [R-5.9a-019] of 3GPP TS 22.280 [16] | >> MCVideo client trigger criteria for de-activation (see NOTE 6) | Y | Y | Y | Y | +| | >> Manual de-activation is not allowed if the criteria are met (see NOTE 6) | Y | 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 [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] | | | | | | +| NOTE 6: The criteria may consist of conditions like the location of the MCVideo user, local time etc. | | | | | | +| NOTE 7: The criteria may consist of conditions such as the location of the MCVideo user or the active functional alias of the MCVideo user. | | | | | | + +**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 | +| [R-5.10-001a] of 3GPP TS 22.280 [2] | Maximum number of successful simultaneous service authorizations of clients from a user | N | Y | Y | +| | List of functional alias identities | | | | +| [R-5.9a-005] of 3GPP TS 22.280 [2] | > Functional alias | N | Y | Y | +| [R-5.9a-005] of 3GPP TS 22.280 [2] | > Limit number of simultaneous activations | N | Y | Y | +| [R-5.9a-005] of 3GPP TS 22.280 [2] | > This functional alias can be taken over | N | Y | Y | +| | > List of user who can activate this functional alias | | | | +| [R-5.9a-005] of 3GPP TS 22.280 [2] | >> MCVideo ID | 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 ProSe Per-Packet priority (as specified in 3GPP TS 23.303 [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:
S6-160535, S6-160536, S6-160589
Title aligned with the title in MCVideo WID. | 0.1.0 | +| 2016-08 | | | | | | Implemented the following pCRs approved in SA6#12:
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 | +| 2018-12 | SA#82 | SP-181170 | 0111 | 2 | A | MCVideo QCI update | 15.5.0 | +| 2018-12 | SA#82 | SP-181180 | 0109 | | D | Spelling of ProSe | 16.0.0 | +| 2019-03 | SA#83 | SP-190070 | 0114 | 1 | A | Corrections to MCVideo Group join information flows and procedure | 16.1.0 | +| 2019-03 | SA#83 | SP-190073 | 0116 | 1 | F | Corrections to 'general' subclause for pre-arranged and chat group calls | 16.1.0 | +| 2019-03 | SA#83 | SP-190073 | 0117 | 1 | B | Late entry for MCVideo chat group call | 16.1.0 | +| 2019-03 | SA#83 | SP-190073 | 0118 | 1 | B | Procedure for MCVideo user leaving a group call | 16.1.0 | +| 2019-06 | SA#84 | SP-190488 | 0119 | 1 | B | Restricting incoming private communications | 16.2.0 | +| 2019-06 | SA#84 | SP-190488 | 0120 | 2 | B | User configuration for functional alias information query for MCVideo | 16.2.0 | +| 2019-06 | SA#84 | SP-190488 | 0121 | 1 | B | User requested priority in 23.281 | 16.2.0 | +| 2019-06 | SA#84 | SP-190488 | 0122 | 2 | B | MCVideo configuration for functional alias | 16.2.0 | +| 2019-06 | SA#84 | SP-190488 | 0123 | 3 | B | Criteria based automatic group affiliation and deaffiliation | 16.2.0 | +| 2019-06 | SA#84 | SP-190488 | 0124 | 1 | B | Add configuration data to support functional alias in MCVideo | 16.2.0 | +| 2019-06 | SA#84 | SP-190488 | 0125 | 3 | B | Add functional alias to MCVideo for video pull and push operations | 16.2.0 | +| 2019-06 | SA#84 | SP-190488 | 0126 | 3 | B | Add functional alias to MCVideo private calls | 16.2.0 | +| 2019-06 | SA#84 | SP-190488 | 0127 | 4 | B | Add functional alias to MCVideo group calls | 16.2.0 | +| 2019-06 | SA#84 | SP-190484 | 0129 | 2 | F | Remove the duplicated MCVideo server URI in UE configuration table | 16.2.0 | +| 2019-06 | SA#84 | SP-190489 | 0130 | 2 | F | Fix the missing parameters in the user profile configuration table | 16.2.0 | +| 2019-06 | SA#84 | SP-190488 | 0131 | | B | MCVideo server limits the number of simultaneous successful service authorisations | 16.2.0 | +| 2019-06 | SA#84 | SP-190488 | 0132 | | B | MCVideo client performs automatic activation and deactivation of functional aliases based on location | 16.2.0 | +| 2019-09 | SA#85 | SP-190731 | 0133 | 3 | F | Correct the configuration parameters for the MCVideo emergency alert procedures | 16.3.0 | +| 2019-09 | SA#85 | SP-190732 | 0136 | 1 | F | Fixing the user profile configuration data for criteria triggered functional alias activation and de-activation | 16.3.0 | +| 2020-12 | SA#90-e | SP-200990 | 0154 | 1 | F | FA controlling role description in MCVideo | 16.4.0 | + +| | | | | | | | | +|---------|---------|-----------|------|--|---|------------------------------------|--------| +| 2020-12 | SA#90-e | SP-200990 | 0156 | | F | FA management procedure in MCVideo | 16.4.0 | +|---------|---------|-----------|------|--|---|------------------------------------|--------| \ No newline at end of file diff --git a/marked/Rel-16/23_series/23287/0f1767577a073167eb9628d72034e083_img.jpg b/marked/Rel-16/23_series/23287/0f1767577a073167eb9628d72034e083_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4e76034daec2fe2f4d88d71b32415794096015d1 --- /dev/null +++ b/marked/Rel-16/23_series/23287/0f1767577a073167eb9628d72034e083_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:126edab6c242819cc1f8e4c5b2e2bba076313a090f4804ca370d1d37df6e0aef +size 19399 diff --git a/marked/Rel-16/23_series/23287/18e519d1f91133e080347562f681dfb5_img.jpg b/marked/Rel-16/23_series/23287/18e519d1f91133e080347562f681dfb5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..40aebd53f011f6ee9e284d2bdab304f77bef39f4 --- /dev/null +++ b/marked/Rel-16/23_series/23287/18e519d1f91133e080347562f681dfb5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8af1e8b93358cba2e2d582947d4f210819b2943b26ff2fbaccd38c3074925cd1 +size 25275 diff --git a/marked/Rel-16/23_series/23287/28d75f39a24203712ee907b32cf0bbe5_img.jpg b/marked/Rel-16/23_series/23287/28d75f39a24203712ee907b32cf0bbe5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8a78b726df665dc2bf025bf4e423481e301d84f2 --- /dev/null +++ b/marked/Rel-16/23_series/23287/28d75f39a24203712ee907b32cf0bbe5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c01cf2eedc203e2d7951719cba305b067a704f021b0228732a41576a6b2b1fe8 +size 80034 diff --git a/marked/Rel-16/23_series/23287/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg b/marked/Rel-16/23_series/23287/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0bf843a1958c4a6a321e4121412a7eeca611cab7 --- /dev/null +++ b/marked/Rel-16/23_series/23287/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e3f386e84306ebd3b89f9005d838f95f09fc654a2dfbc483f623608f7365a18c +size 64628 diff --git a/marked/Rel-16/23_series/23287/4dadfd8b8240e9d83f974e3f0fdd18df_img.jpg b/marked/Rel-16/23_series/23287/4dadfd8b8240e9d83f974e3f0fdd18df_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5b98d6d3fc04d4add6540ee43af01169a950b504 --- /dev/null +++ b/marked/Rel-16/23_series/23287/4dadfd8b8240e9d83f974e3f0fdd18df_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:885017b95f3412b5e269a9e304e225eb6f9459faff7e088ac4bcc654f8ba6bd4 +size 68551 diff --git a/marked/Rel-16/23_series/23287/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-16/23_series/23287/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8dd96c65562e547f6670d9fe26a3261df0a0cebe --- /dev/null +++ b/marked/Rel-16/23_series/23287/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8cf5cc9b32e0e6e2cc1eb017de6b46c2ba9b3b32f4f029f3e41c000ae82be0d2 +size 7622 diff --git a/marked/Rel-16/23_series/23287/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-16/23_series/23287/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..760ae62d7e7e916527b54305c86a3a90f835e2a8 --- /dev/null +++ b/marked/Rel-16/23_series/23287/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:844037de4133f66d5f5cc13bc2b069145fddd210fc7c0bfe20f79b2222d9b5a0 +size 5745 diff --git a/marked/Rel-16/23_series/23287/659a041a7997f9eea79f4e2f3ba265a5_img.jpg b/marked/Rel-16/23_series/23287/659a041a7997f9eea79f4e2f3ba265a5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..92a8b6dcf2c337e573181fcc8898f71dbfa856b2 --- /dev/null +++ b/marked/Rel-16/23_series/23287/659a041a7997f9eea79f4e2f3ba265a5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c99dbff83182748142bdb4268c0cf46857c3d6570067c7be22e16ecef2d27a00 +size 17481 diff --git a/marked/Rel-16/23_series/23287/71b0a68b4dd64961465d2b0e790538de_img.jpg b/marked/Rel-16/23_series/23287/71b0a68b4dd64961465d2b0e790538de_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2ced9cc91a6b2700e1cff8ec2c40013716676aac --- /dev/null +++ b/marked/Rel-16/23_series/23287/71b0a68b4dd64961465d2b0e790538de_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8e8894c94cb9db7e195a12da19cb6256978daefab4cb020d54366ee1c5d3894e +size 28539 diff --git a/marked/Rel-16/23_series/23287/7e670a2b556b53ea9002dfff3a420e08_img.jpg b/marked/Rel-16/23_series/23287/7e670a2b556b53ea9002dfff3a420e08_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4e86827a7d264066e9353224157dbd6d305d6816 --- /dev/null +++ b/marked/Rel-16/23_series/23287/7e670a2b556b53ea9002dfff3a420e08_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2f15f1f54655148f56afddb4a6bbdcc3603c187dcd57888b963ed83045dad536 +size 74814 diff --git a/marked/Rel-16/23_series/23287/7fe5741e83bc9702d1b1d7585ddf66bd_img.jpg b/marked/Rel-16/23_series/23287/7fe5741e83bc9702d1b1d7585ddf66bd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6fbb1f2145f37061fde29097599a3500a137ab16 --- /dev/null +++ b/marked/Rel-16/23_series/23287/7fe5741e83bc9702d1b1d7585ddf66bd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d4c9b5962ee27332d4c0a209afd2728cfe931f06a0d0e0ca5986fd3942cf03dd +size 19923 diff --git a/marked/Rel-16/23_series/23287/838c31609fac483fa2c01c7896a2fd6d_img.jpg b/marked/Rel-16/23_series/23287/838c31609fac483fa2c01c7896a2fd6d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9a479e079aee5c71c5ae7d5de69060d6c1d26a50 --- /dev/null +++ b/marked/Rel-16/23_series/23287/838c31609fac483fa2c01c7896a2fd6d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1f039d3977a7df2fbc232d7d75d5042b23b52d08c1bc2eccc392726f59cde4e3 +size 82870 diff --git a/marked/Rel-16/23_series/23287/853f59c89931a666c07903b31d098277_img.jpg b/marked/Rel-16/23_series/23287/853f59c89931a666c07903b31d098277_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..994b954d3e8d7618c3060de91c80dda06dc9dadc --- /dev/null +++ b/marked/Rel-16/23_series/23287/853f59c89931a666c07903b31d098277_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d1e1e97cad902332e818ccf94245868458170fc064f55f0a498b47b68d2db44a +size 34710 diff --git a/marked/Rel-16/23_series/23287/896e86ed12aff206d302c64f2e3091fa_img.jpg b/marked/Rel-16/23_series/23287/896e86ed12aff206d302c64f2e3091fa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..175dd2ceb6f58ccadf2973a81420ae527671faed --- /dev/null +++ b/marked/Rel-16/23_series/23287/896e86ed12aff206d302c64f2e3091fa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9b07d219e6302db81c481ece208999fa5d8068af9eb98799c5f21b7d6701ca36 +size 32906 diff --git a/marked/Rel-16/23_series/23287/8e14350b4b669119a3bdfca7869110ca_img.jpg b/marked/Rel-16/23_series/23287/8e14350b4b669119a3bdfca7869110ca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..91e34dadcf19e05789200f5894581651134e6e2a --- /dev/null +++ b/marked/Rel-16/23_series/23287/8e14350b4b669119a3bdfca7869110ca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5a27df24364e026ebe397681d24801c383c42f9418b18eb1e3dc04c7ecc93f96 +size 71929 diff --git a/marked/Rel-16/23_series/23287/90ddb84c323b956e2d50a54d3f870566_img.jpg b/marked/Rel-16/23_series/23287/90ddb84c323b956e2d50a54d3f870566_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bc44581833763cd77872f57393ad236e28f4f503 --- /dev/null +++ b/marked/Rel-16/23_series/23287/90ddb84c323b956e2d50a54d3f870566_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bdc6d268e88b2e3b87752be2706b00db6f0b2bd4cd6a0ba0c13870f7db08aef8 +size 76368 diff --git a/marked/Rel-16/23_series/23287/9f6dec4d4e9fde40bce018861ef1278e_img.jpg b/marked/Rel-16/23_series/23287/9f6dec4d4e9fde40bce018861ef1278e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0de7613c0f61edfde6213ad2432d948388e0b298 --- /dev/null +++ b/marked/Rel-16/23_series/23287/9f6dec4d4e9fde40bce018861ef1278e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1963a84c54ca51f9e2dcce445bb102f04cdc6083d410d0aa66841f5655701c31 +size 41667 diff --git a/marked/Rel-16/23_series/23287/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/Rel-16/23_series/23287/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fa508f5fc768972d6c3e3e6f472879b6494b5b41 --- /dev/null +++ b/marked/Rel-16/23_series/23287/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:122ebeadba8be85fa03c2c761314a6161662e681d06bd6c6ee3223aede2db34a +size 102599 diff --git a/marked/Rel-16/23_series/23287/c1278da91cbcabe32628e589ebc47418_img.jpg b/marked/Rel-16/23_series/23287/c1278da91cbcabe32628e589ebc47418_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..77dc20c33fc62f9ac6c2a6697a56499992ee2b00 --- /dev/null +++ b/marked/Rel-16/23_series/23287/c1278da91cbcabe32628e589ebc47418_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bce3d93eefc5d0c78f45d8f24f8edf43121a7e93c22ea5680168092e434f239b +size 35942 diff --git a/marked/Rel-16/23_series/23287/c468d53e877568cd7d8c5ba1632c2e65_img.jpg b/marked/Rel-16/23_series/23287/c468d53e877568cd7d8c5ba1632c2e65_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dda2eb03e75ea503f399bda962bfc695f8aa69a5 --- /dev/null +++ b/marked/Rel-16/23_series/23287/c468d53e877568cd7d8c5ba1632c2e65_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e1f53d64f8886d267de28338319589b5ad314bcdebeb2bf4e996a59e7bd89d09 +size 38940 diff --git a/marked/Rel-16/23_series/23287/ddee3e67e0dfc22e25188fa635a19558_img.jpg b/marked/Rel-16/23_series/23287/ddee3e67e0dfc22e25188fa635a19558_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6d871536f2932c2cdd7bdd14385568b9d2945025 --- /dev/null +++ b/marked/Rel-16/23_series/23287/ddee3e67e0dfc22e25188fa635a19558_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7290b93ab112f9552104db17da31bbe754d7b79ae06688fcddb00794c36939e5 +size 129822 diff --git a/marked/Rel-16/23_series/23287/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/marked/Rel-16/23_series/23287/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0c4e9a31ec03445c9c2ce999374b99684c9108dc --- /dev/null +++ b/marked/Rel-16/23_series/23287/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5f3b211ad9fe67bd73570cf4252cf10ae5440c6930854dcc797582767fe4a42b +size 70763 diff --git a/marked/Rel-16/23_series/23287/e94cbc0895c6914a2bb53f150ab7495e_img.jpg b/marked/Rel-16/23_series/23287/e94cbc0895c6914a2bb53f150ab7495e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eb9e41ce6aaf2ea0c673e50630021eace9d681cf --- /dev/null +++ b/marked/Rel-16/23_series/23287/e94cbc0895c6914a2bb53f150ab7495e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7625b10d04fd57479a93430ccf3556039b3d4e875cc807ec3315b52e223aa972 +size 69389 diff --git a/marked/Rel-16/23_series/23287/raw.md b/marked/Rel-16/23_series/23287/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..ad73a02511ffbfd6f63898ba485cb4568bdaca68 --- /dev/null +++ b/marked/Rel-16/23_series/23287/raw.md @@ -0,0 +1,2063 @@ + + +# 3GPP TS 23.287 V16.7.0 (2022-06) + +Technical Specification + +## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Architecture enhancements for 5G System (5GS) to support Vehicle-to-Everything (V2X) services (Release 16)** + + + +The 5G logo, consisting of the text "5G" in a bold, black, sans-serif font. Above the "5G" text is a green graphic element consisting of three curved lines, resembling a signal strength indicator or a stylized wave. + +5G logo + + + +The 3GPP logo, featuring the letters "3GPP" in a stylized, bold, black font. The "3" and "G" are connected at the top by a single horizontal line. The "P" and "P" are also connected at the top by a single horizontal line. Below the "G" and "P" is a red graphic element consisting of three curved lines, resembling a signal strength indicator or a stylized wave. + +3GPP logo + +A GLOBAL INITIATIVE + +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 + +--- + +
(NOTE 1) | 3 | 20 ms | $10^{-4}$ | N/A | 2000 ms | Platooning between UEs – Higher degree of automation; Platooning between UE and RSU – Higher degree of automation | +| 22 | | 4 | 50 ms | $10^{-2}$ | N/A | 2000 ms | Sensor sharing – higher degree of automation | +| 23 | | 3 | 100 ms | $10^{-4}$ | N/A | 2000 ms | Information sharing for automated driving – between UEs or UE and RSU - higher degree of automation | +| 55 | Non-GBR | 3 | 10 ms | $10^{-4}$ | N/A | N/A | Cooperative lane change – higher degree of automation | +| 56 | | 6 | 20 ms | $10^{-1}$ | N/A | N/A | Platooning informative exchange – low degree of automation; Platooning – information sharing with RSU | +| 57 | | 5 | 25 ms | $10^{-1}$ | N/A | N/A | Cooperative lane change – lower degree of automation | +| 58 | | 4 | 100 ms | $10^{-2}$ | N/A | N/A | Sensor information sharing – lower degree of automation | +| 59 | | 6 | 500 ms | $10^{-1}$ | N/A | N/A | Platooning – reporting to an RSU | +| 90 | Delay Critical GBR
(NOTE 1) | 3 | 10 ms | $10^{-4}$ | 2000 bytes | 2000 ms | Cooperative collision avoidance; Sensor sharing – Higher degree of automation; Video sharing – higher degree of automation | +| 91 | | 2 | 3 ms | $10^{-5}$ | 2000 bytes | 2000 ms | Emergency trajectory alignment; Sensor sharing – Higher degree of automation | + +NOTE 1: GBR and Delay Critical GBR PQIs can only be used for unicast PC5 communications. + +NOTE 1: For Standardized PQI to QoS characteristics mapping, the table will be extended/updated to support service requirements for other identified V2X services. + +NOTE 2: The PQIs may be used for other services than V2X. + +NOTE 3: A PQI may be used together with an application indicated priority, which overrides the Default Priority Level of the PQI. + +### 5.4.5 QoS handling for V2X communication over Uu reference point + +#### 5.4.5.1 General + +The V2X service data can be delivered via Non-GBR QoS Flow as well as GBR QoS Flow (i.e. using the GBR resource type or the Delay-critical GBR resource type) as specified in TS 23.501 [6]. + +#### 5.4.5.2 Notification on QoS Sustainability Analytics to the V2X Application Server + +##### 5.4.5.2.1 General + +A V2X Application Server may request notifications on QoS Sustainability Analytics for an indicated geographic area and time interval in order to adjust the application behaviour in advance with potential QoS change. The V2X Application Server may also request past statistical information for the purposes of adjustment of the application, how V2X Application Server makes use of such data is outside of 3GPP scope. Clause 6.4.1 describes the procedure for such notification from 5GS. + +##### 5.4.5.2.2 Functional description + +The potential QoS change to assist application adjustment is based on the notification of QoS Sustainability Analytics defined in clause 6.9 of TS 23.288 [20]. The V2X Application Server acting as an Application Function communicates with the NEF which corresponds to the NF consumer in clause 6.9.4 of TS 23.288 [20]. + +The V2X Application Server can either subscribe to notifications from the NEF (i.e., a Subscribe-Notify model) or request a single notification from the NEF (i.e. a Request-Response model). The V2X Application Server request contains the following parameters: + +- Analytics ID = "QoS Sustainability"; +- Target of Analytics Reporting: "any UE"; +- Analytics Filter Information: + - Optional maximum number of objects; + - QoS requirements: + - 5QI (standardized or pre-configured), and applicable additional QoS parameters and the corresponding values (conditional, i.e., it is needed for GBR 5QIs to know the GFBR); or + - the QoS Characteristics attributes including Resource Type, PDB and PER and their values; + +NOTE: The V2X Application Server could provide the 5QIs as input based on SLA with the operator which authorizes the V2X Application Server to use certain 5QIs and to use the QoS Sustainability Analytics only for them. + +- Location information (the details are specified in TS 23.288 [20] clause 6.9.1); +- S-NSSAI (optional, if available in the V2X Application Server). +- Analytics target period (the details are specified in TS 23.288 [20] clause 6.9.1); +- Reporting Threshold(s) (the details are specified in TS 23.288 [20] clause 6.9.1); +- In a subscription, the Notification Correlation Id and the Notification Target Address. + +#### 5.4.5.3 QoS Change based on Extended NG-RAN Notification to support Alternative Service Requirements + +To support V2X applications that can operate with different configurations (e.g. different bitrates or delay requirements), the V2X Application Server (V2X AS), acting as the Application Function, can provide, in addition to the requested level of service requirements, Alternative Service Requirements to the 5GS. This enables the 5GS to act + +on the Alternative Service Requirements and apply them for the extended NG-RAN notification, as described in TS 23.501 [6] and TS 23.503 [16]. + +The V2X AS can use the related procedures specified in clause 4.15.6.6 of TS 23.502 [7] to influence the QoS provided to the V2X service. If so, the V2X AS includes Alternative Service Requirements as specified in clause 6.1.3.22 of TS 23.503 [16] when providing service information to the PCF. + +The QoS change based on extended NG-RAN notification operates within the 5GS QoS model as specified in TS 23.501 [6] and TS 23.503 [16]. + +## 5.5 Subscription to V2X services + +The user's profile in the UDM contains the subscription information to give the user permission to use V2X services. + +At any time, the operator can remove the UE subscription rights for V2X services from user's profile in the UDM, and revoke the user's permission to use V2X services. + +The following subscription information is defined for V2X services: + +- a) whether the UE is authorized to perform V2X communication over PC5 reference point as Vehicle UE, Pedestrian UE, or both, including for LTE PC5 and for NR PC5. +- b) UE-PC5-AMBR per PC5 RAT, including UE-PC5-AMBR for LTE PC5 and UE-PC5-AMBR for NR PC5. +- c) the list of the PLMNs where the UE is authorized to perform V2X communication over PC5 reference point. For each PLMN in the list, the RAT(s) over which the UE is authorized to perform V2X communications over PC5 reference point. +- d) PC5 QoS parameters as defined in clause 5.4.2 used by NG-RAN. + +The UDM may retrieve a) and b) from the UDR. a) and b) are provided by the UDM to the AMF during UE Registration procedure as defined in clause 4.2.2.2 of TS 23.502 [7] using Nudm\_SDM service for Subscription data type "V2X Subscription data" and the AMF provides a) and b) to NG-RAN as part of the UE context information. + +c) and d) are provided by the UDR to the PCF during the UE Policy Association Establishment procedure as defined in clause 4.16.11 of TS 23.502 [7] and UE Policy Association Modification procedure as defined in clause 4.16.12 of TS 23.502 [7] using Nudr service for Data Set "Policy Data" and Data Subset "Policy Set Entry". If the subscription information provided to the PCF from UDR is changed (e.g., PC5 QoS related parameters, the list of PLMNs where the UE is authorized to perform V2X communication over PC5 reference point), the PCF initiates the UE Configuration Update procedure as specified in clause 6.2.2. + +## 5.6 Identifiers + +### 5.6.1 Identifiers for V2X communication over PC5 reference point + +#### 5.6.1.1 General + +Each UE has one or more Layer-2 IDs for V2X communication over PC5 reference point, consisting of: + +- Source Layer-2 ID(s); and +- Destination Layer-2 ID(s). + +Source and destination Layer-2 IDs are included in layer-2 frames sent on the layer-2 link of the PC5 reference point identifying the layer-2 source and destination of these frames. Source Layer-2 IDs are always self-assigned by the UE originating the corresponding layer-2 frames. + +The selection of the source and destination Layer-2 ID(s) by a UE depends on the communication mode of V2X communication over PC5 reference point for this layer-2 link, as described in clauses 5.6.1.2, 5.6.1.3, and 5.6.1.4. The source Layer-2 IDs may differ between different communication modes. + +When IP-based V2X communication is supported for broadcast and groupcast modes of V2X communication over PC5 reference point, the source IP address is allocated as described in clause 5.2.1.5. + +If the UE has an active V2X application that requires privacy support in the current Geographical Area, as identified by configuration described in clause 5.1.2.1, in order to ensure that a source UE (e.g. vehicle) cannot be tracked or identified by any other UEs (e.g. vehicles) beyond a certain short time-period required by the application, the source Layer-2 ID shall be changed over time and shall be randomized. For IP-based V2X communication over PC5 reference point, the source IP address shall also be changed over time and shall be randomized. The change of the identifiers of a source UE must be synchronized across layers used for PC5, (e.g. when the Application Layer ID changes, the source Layer-2 ID and the source IP address need to be changed). + +#### 5.6.1.2 Identifiers for broadcast mode V2X communication over PC5 reference point + +For broadcast mode of V2X communication over PC5 reference point, the UE is configured with the destination Layer-2 ID(s) to be used for V2X services. The destination Layer-2 ID for a V2X communication is selected based on the configuration as described in clause 5.1.2.1. + +The UE self-selects a source Layer-2 ID. The UE may use different source Layer-2 IDs for different types of PC5 reference points, i.e. LTE based PC5 and NR based PC5. + +#### 5.6.1.3 Identifiers for groupcast mode V2X communication over PC5 reference point + +For groupcast mode of V2X communication over PC5 reference point, the V2X application layer may provide group identifier information. When the group identifier information is provided by the V2X application layer, the UE converts the provided group identifier into a destination Layer-2 ID. When the group identifier information is not provided by the V2X application layer, the UE determines the destination Layer-2 ID based on configuration of the mapping between V2X service type and Layer-2 ID, as specified in clause 5.1.2.1. + +NOTE: The mechanism for converting the V2X application layer provided group identifier to the destination Layer-2 ID is defined in Stage 3. + +The UE self-selects a source Layer-2 ID. + +#### 5.6.1.4 Identifiers for unicast mode V2X communication over PC5 reference point + +For unicast mode of V2X communication over PC5 reference point, the destination Layer-2 ID used depends on the communication peer. The Layer-2 ID of the communication peer, identified by the Application Layer ID, may be discovered during the establishment of the PC5 unicast link, or known to the UE via prior V2X communications, e.g. existing or prior unicast link to the same Application Layer ID, or obtained from application layer service announcements. The initial signalling for the establishment of the PC5 unicast link may use the known Layer-2 ID of the communication peer, or a default destination Layer-2 ID associated with the V2X service type configured for PC5 unicast link establishment, as specified in clause 5.1.2.1. During the PC5 unicast link establishment procedure, Layer-2 IDs are exchanged, and should be used for future communication between the two UEs, as specified in clause 6.3.3.1. + +The Application Layer ID is associated with one or more V2X applications within the UE. If UE has more than one Application Layer IDs, each Application Layer ID of the same UE may be seen as different UE's Application Layer ID from the peer UE's perspective. + +The UE maintains a mapping between the Application Layer IDs and the source Layer-2 IDs used for the PC5 unicast links, as the V2X application layer does not use the Layer-2 IDs. This allows the change of source Layer-2 ID without interrupting the V2X applications. + +When Application Layer IDs change, the source Layer-2 ID(s) of the PC5 unicast link(s) shall be changed if the link(s) was used for V2X communication with the changed Application Layer IDs. + +Based on privacy configuration as specified in clause 5.1.2.1, the update of the new identifiers of a source UE to the peer UE for the established unicast link may cause the peer UE to change its Layer-2 ID and optionally IP address/prefix if IP communication is used as defined in clause 6.3.3.2. + +A UE may establish multiple PC5 unicast links with a peer UE and use the same or different source Layer-2 IDs for these PC5 unicast links. + +## 5.7 Support for V2X communication for UEs in limited service state + +For UE in limited service state, as defined in TS 23.122 [13], V2X communication is only allowed over PC5 reference point. + +UEs that are authorized to use V2X communication over PC5 reference point shall be able to use V2X communication over PC5 reference point when in limited service state following the principles defined in clause 5.1.2.2 for V2X communication over PC5 reference point when the UE enters in limited service state in 5GS: + +- because UE cannot find a suitable cell of the selected PLMN as described in TS 23.122 [13]; or +- as the result of receiving one of the following reject reasons defined in TS 23.122 [13]: + - a "PLMN not allowed" response to a registration request or; + - a "5GS services not allowed" response to a registration request or service request. + +A UE in limited service state shall only use the radio resources and procedure available in CM-IDLE mode for V2X communication over PC5 reference point, for details see TS 36.300 [9] and TS 38.300 [11]. + +UEs shall not use V2X communication over PC5 reference point using the "operator-managed" radio resources, as specified in clause 5.1.2.1, if the UE has entered in limited service state due to all other situations (e.g. no SIM in the MS, an "illegal MS" or "illegal ME" response to a registration request, or an "IMSI unknown in HLR" response to a registration request) defined in TS 23.122 [13], where the UE is unable to obtain normal service from a PLMN. The UEs may use V2X communication over PC5 reference point using the "non-operator-managed" radio resources, as specified in clause 5.1.2.1, according to the principles defined in clause 5.1.2.2. + +## 5.8 Interworking between EPS V2X and 5GS V2X + +### 5.8.1 V2X Policy and parameter provisioning + +When the UE is in 5GS or EPS, the UE shall use the valid V2X policy and parameters provisioned by the PCF in 5GC or by the V2X Control Function in EPC for V2X communication. The V2X related parameters for EPS defined in TS 23.285 [8] can be either provided by the PCF or by the V2X Control Function, while the V2X policy and parameters involving 5GS are provided by the PCF only. If the UE does not have valid V2X policy and parameters, the UE shall request the network to provision the V2X policy and parameters. + +### 5.8.2 PC5 Operation + +PC5 communication can be supported with proper UE configurations by taking into account e.g. regional regulations, deployments, and UE support for LTE PC5 and/or NR PC5 RATs. + +V2X communication over NR PC5 reference point in network scheduled operation mode is supported in EPS (i.e. EN-DC architecture defined in TS 37.340 [25]) as defined in TS 23.285 [8] and TS 36.331 [14]. + +### 5.8.3 Mobility between EPS and 5GS over Uu + +Interworking specified in clause 5.17 of TS 23.501 [6] and clause 4.11 of TS 23.502 [7] is applied to mobility between EPS and 5GS over Uu reference point with the following additions: + +- For N26 based handover, V2X related data including the "V2X services authorized" indication per PC5 RAT, UE-PC5-AMBR per PC5 RAT, and PC5 QoS parameters are transferred between AMF and MME, and are included in Handover Request message sent to the target RAN node. + +Any Unstructured type PDU Session established in 5GC based on the UE configuration as described in clause 5.1.3.1 is allowed to be transferred to EPC as non-IP PDN connection when non-IP PDN type is supported by UE and EPC as specified in clause 5.17.2.1 of TS 23.501 [6]. + +# 6 Functional description and information flows + +## 6.1 Control and user plane stacks + +### 6.1.1 User plane for NR PC5 reference point supporting V2X services + +Figure 6.1.1-1 depicts a user plane for NR PC5 reference point, i.e. PC5 User Plane Protocol stack. + + + +The diagram illustrates the User Plane (UP) protocol stack for two User Equipment (UE) units, UE A and UE B, connected via the PC5-U reference point. Both UE A and UE B have identical protocol stacks. From top to bottom, the layers are: V2X App, IP, Non-IP, SDAP, PDCP, RLC, MAC, and PHY. Horizontal double-headed arrows connect corresponding layers between UE A and UE B, indicating bidirectional data flow. The entire stack for each UE is enclosed in a dashed box, and the connection between the two boxes is labeled PC5-U. + +Diagram of the User Plane for NR PC5 reference point showing the protocol stacks for UE A and UE B. Both stacks consist of V2X App, IP, Non-IP, SDAP, PDCP, RLC, MAC, and PHY layers. The stacks are connected via the PC5-U interface. + +###### Legend: + +- **PC5-U:** The SDAP/PDCP/RLC/MAC/PHY functionality is specified in TS 38.300 [11]. +- For PDCP SDU type "Non-IP", a "Non-IP Type" header included in the SDU by upper layer to indicate the type of non-IP messages carried will be specified in stage 3 specification. + +**Figure 6.1.1-1: User Plane for NR PC5 reference point** + +IP and Non-IP PDCP SDU types are supported for the V2X communication over PC5 reference point. + +For IP PDCP SDU type, only IPv6 is supported. The IP address allocation and configuration are as defined in clause 5.6.1.1. + +The Non-IP PDCP SDU contains a Non-IP Type header, which indicates the V2X message family used by the application layer, e.g. IEEE 1609 family's WSMP [18], ISO defined FNTP [19], CCSA defined DSMP [27]. + +NOTE: The Non-IP Type header and allowed values are defined in TS 24.587 [24]. + +The packets from V2X application layer are handled by the V2X layer before transmitting them to the AS layer, e.g. V2X layer maps the IP/Non IP packets to PC5 QoS Flow and marks the corresponding PFI. + +### 6.1.2 Control plane for NR PC5 reference point supporting V2X services + +Figure 6.1.2-1 depicts a control plane for NR PC5 reference point, i.e. PC5 Signalling Protocol stack. + + + +Diagram of the Control Plane for NR PC5 reference point showing two User Equipment (UE) stacks, UE A and UE B, connected via a PC5-S reference point. Each stack contains five layers: PC5 Signalling Protocol, PDCP, RLC, MAC, and PHY. The PC5 Signalling Protocol layers are connected to each other, and the PDCP, RLC, MAC, and PHY layers are connected to each other within each UE. The PDCP, RLC, MAC, and PHY layers of UE A are connected to the corresponding layers of UE B via the PC5-S reference point. + +###### Legend: + +- PC5-S Protocol: The protocol used for the control plane signalling over the PC5 reference point for the secure layer-2 link as specified in clause 6.3.3. +- The PDCP/RLC/MAC/PHY functionality is specified in TS 38.300 [11]. + +**Figure 6.1.2-1: Control Plane for NR PC5 reference point** + +## 6.2 Procedures for Service Authorization and Provisioning to UE + +### 6.2.1 General + +The procedures for service authorization and provisioning to UE may be initiated by the PCF (as described in clause 6.2.2), by the UE (as described in clause 6.2.4), or by the AF (as described in clause 6.2.5). + +### 6.2.2 PCF based Service Authorization and Provisioning to UE + +For PCF based Service Authorization and Provisioning to UE, the Registration procedures as defined in clause 4.2.2.2 of TS 23.502 [7], UE Policy Association Establishment procedure as defined in clause 4.16.11 of TS 23.502 [7] and UE Policy Association Modification procedure as defined in clause 4.16.12 of TS 23.502 [7] apply with the following additions: + +- If the UE indicates V2X capability in the Registration Request message and if the UE is authorized to use V2X service based on subscription data, the AMF selects the PCF which supports V2X Policy/Parameter provisioning as described in clause 6.2.3 and establishes a UE policy association with the PCF for V2X Policy/Parameter delivery. +- If the AMF receives the PC5 capability for V2X in the Registration Request message from UE, the AMF further reports the PC5 capability for V2X to the selected PCF. The PCF may determine the V2X Policy/Parameter for specific PC5 RAT based on the received UE's PC5 capability for V2X. + +The PCF may update the V2X Policy/parameters to the UE in following conditions: + +- UE Mobility, e.g. UE moves from one PLMN to another PLMN. This is achieved by using the procedure of UE Policy Association Modification initiated by the AMF, as defined in clause 4.16.12.1 of TS 23.502 [7]. +- When there is a subscription change in the list of PLMNs where the UE is authorized to perform V2X communication over PC5 reference point. This is achieved by using UE Policy Association Modification initiated by the PCF procedure as defined in clause 4.16.12.2 of TS 23.502 [7]. +- When there is a change of service specific parameter as described in clause 4.15.6.7 of TS 23.502 [7]. + +If the serving PLMN is removed from the list of PLMNs in the service authorization parameters, the service authorization is revoked in the UE. + +When the UE is roaming, the change of subscription resulting in updates of the service authorization parameters are transferred to the UE by H-PCF via V-PCF. + +The UE may perform UE triggered V2X Policy Provisioning procedure to the PCF, after Registration procedure has been completed, as specified in clause 6.2.4 when the UE determines the V2X Policy/Parameter is invalid (e.g. Policy/Parameter is outdated, missing or invalid). + +### 6.2.3 PCF discovery + +PCF discovery and selection mechanism defined in clause 6.3.7.1 of TS 23.501 [6] applies with the following addition to enable a PCF instance is selected for V2X service and for UE: + +- Based on the indication from the UE and/or UE subscription data during the Registration procedure as specified in clause 6.2.2, the AMF may include the V2X capability indication in the Nnrf\_NFDiscovery\_Request message as the optional input parameter. If provided, the NRF takes the information into account for discovering the PCF instance. + +### 6.2.4 Procedure for UE triggered V2X Policy provisioning + +The UE triggered Policy Provisioning procedure is initiated by the UE to request V2X Policy/Parameter from the PCF when UE determines the V2X Policy/Parameter is invalid in the following cases: + +- if the validity timer indicated in the V2X Policy/Parameter expires; +- if there are no valid parameters, e.g. for the V2X service type a UE wants to use, for current area, or due to abnormal situation. + + + +``` + +sequenceDiagram + participant UE + participant (R)AN + participant AMF + participant PCF + Note left of UE: 1. UE Policy provisioning request + UE->>AMF: 1. UE Policy provisioning request + Note right of AMF: 2. Namf_Communication_N1MessageNotify + AMF->>PCF: 2. Namf_Communication_N1MessageNotify + Note over UE, (R)AN, AMF, PCF: 3. UE Policy delivery procedure defined in clause 4.2.4.3 of 23.502 + +``` + +Sequence diagram of UE triggered V2X Policy provisioning procedure. The diagram shows four lifelines: UE, (R)AN, AMF, and PCF. Step 1: UE sends 'UE Policy provisioning request' to AMF. Step 2: AMF sends 'Namf\_Communication\_N1MessageNotify' to PCF. Step 3: A box labeled 'UE Policy delivery procedure defined in clause 4.2.4.3 of 23.502' spans across all lifelines, indicating a procedure involving all four entities. + +**Figure 6.2.4-1: UE triggered V2X Policy provisioning procedure** + +1. The UE sends UL NAS TRANSPORT message carrying the UE Policy Container (UE V2X Policy Provisioning Request to request V2X policies) to the AMF. +2. The AMF sends the Namf\_Communication\_N1MessageNotify request to the PCF including the UE Policy Container received from UE. +3. The PCF receives UE Policy Container which indicates UE Policy Provisioning Request to request V2X policies. If the V2X policies are authorized based on AMF input as specified in clause 6.2.2, the PCF performs the UE Policy delivery procedure defined in clause 4.2.4.3 of TS 23.502 [7]. + +### 6.2.5 AF-based service parameter provisioning for V2X communications over control plane + +The V2X Application Server can provision the 5GC with V2X service parameters via NEF as depicted in clause 4.2.2. For V2X service parameter provisioning, the procedure defined in clause 4.15.6.7 of TS 23.502 [7] is performed with the following considerations: + +- The AF in TS 23.502 [7] is considered as V2X Application Server in this specification. + +- Service Description indicates V2X service domain information. +- Service Parameters include policy/provisioning parameters for V2X communications over Uu and PC5. The detailed information on the parameters is described in clause 5.1. + +NOTE: It is assumed that the V2X service domain information is set based on the Service Level Agreement with the operator. + +## 6.3 Procedures for V2X communication over PC5 reference point + +### 6.3.1 Broadcast mode V2X communication over PC5 reference point + +To perform V2X communication over PC5 reference point in broadcast mode operation, the UE is configured with the related information as described in clause 5.1.2. + +Figure 6.3.1-1 shows the procedure for broadcast mode of V2X communication over PC5 reference point. + + + +``` + +sequenceDiagram + participant Tx UE-1 + participant Rx UE-1 + participant Rx UE-2 + participant Rx UE-n + + Note right of Rx UE-1: 1. UE-1 determines destination Layer-2 ID for reception. + Note right of Rx UE-2: 1. UE-2 determines destination Layer-2 ID for reception. + Note right of Rx UE-n: 1. UE-n determines destination Layer-2 ID for reception. + + Note left of Tx UE-1: 2. V2X application layer provides data unit and optional Qos requirements to V2X layer. + Note left of Tx UE-1: 3. Tx UE determines source and destination Layer-2 ID + + Tx UE-1->>Rx UE-1: 4. V2X Service (Broadcast) + Tx UE-1->>Rx UE-2: 4. V2X Service (Broadcast) + Tx UE-1->>Rx UE-n: 4. V2X Service (Broadcast) + +``` + +Sequence diagram illustrating the procedure for broadcast mode of V2X communication over PC5 reference point. The diagram shows a transmitting UE (Tx UE-1) and multiple receiving UEs (Rx UE-1, Rx UE-2, Rx UE-n). The process involves: 1. Receiving UEs determining destination Layer-2 IDs; 2. Transmitting UE's application layer providing data and QoS requirements; 3. Transmitting UE determining source and destination Layer-2 IDs; 4. Broadcasting the V2X service. + +**Figure 6.3.1-1: Procedure for Broadcast mode of V2X communication over PC5 reference point** + +1. The receiving UE(s) determine the destination Layer-2 ID for broadcast reception as specified in clause 5.6.1.2. The destination Layer-2 ID is passed down to the AS layer of receiving UE(s) for the reception. +2. The transmitting UE V2X application layer provides data unit and may provide V2X Application Requirements specified in clause 5.4.1.2 to V2X layer. +3. The transmitting UE determines the destination Layer-2 ID for broadcast as specified in clause 5.6.1.2. The transmitting UE self-assigns the source Layer-2 ID as specified in clause 5.6.1.1. + +The transmitting UE determines the PC5 QoS parameters for this broadcast V2X service as specified in clauses 5.4.1.1 and 5.4.1.2. + +4. The transmitting UE sends the V2X service data using the source Layer-2 ID and the destination Layer-2 ID. + +NOTE: In step 4, there is only one broadcast message from the transmitting UE. + +### 6.3.2 Groupcast mode V2X communication over PC5 reference point + +To perform groupcast mode of V2X communication over PC5 reference point, the UE is configured with the related information as described in clause 5.1.2.1. + +Figure 6.3.2-1 shows the procedure for groupcast mode of V2X communication over PC5 reference point. + + + +``` + +sequenceDiagram + participant Tx UE + participant Rx UE-1 + participant Rx UE-n + Note over Tx UE, Rx UE-1, Rx UE-n: 1. Group management is carried out in V2X application layer + Note left of Tx UE: 2. V2X application layer may provide application layer information for PC5 groupcast mode communication. + Note right of Rx UE-1: 2. V2X application layer may provide application layer information for PC5 groupcast mode communication. + Note right of Rx UE-n: 2. V2X application layer may provide application layer information for PC5 groupcast mode communication. + Note left of Tx UE: 3. Tx UE determines source/destination Layer-2 IDs. + Note right of Rx UE-1: 3. Rx UE determines destination Layer-2 ID. + Note right of Rx UE-n: 3. Rx UE determines destination Layer-2 ID. + Note over Tx UE, Rx UE-1, Rx UE-n: 4. V2X Service (Groupcast) + Tx UE->>Rx UE-1: + Tx UE->>Rx UE-n: + +``` + +Figure 6.3.2-1: Procedure for groupcast mode of V2X communication over PC5 reference point. The diagram shows a sequence of steps between a Transmitting UE (Tx UE) and multiple Receiving UEs (Rx UE-1 to Rx UE-n). Step 1: Group management is carried out in the V2X application layer. Step 2: The V2X application layer may provide application layer information for PC5 groupcast mode communication. Step 3: The Tx UE determines source/destination Layer-2 IDs, while the Rx UEs determine the destination Layer-2 ID. Step 4: The V2X Service (Groupcast) is transmitted from the Tx UE to the Rx UEs. + +**Figure 6.3.2-1: Procedure for groupcast mode of V2X communication over PC5 reference point** + +1. V2X group management is carried out by the V2X application layer and is out of scope of this specification. +2. The V2X application layer may provide group identifier information (i.e. an Application-layer V2X Group identifier) as specified in clause 5.6.1.3. + +The V2X application layer may provide V2X Application Requirements for this communication. + +If the V2X application layer does not provide V2X Application Requirements, the V2X layer determines the PC5 QoS parameters based on the mapping of V2X service type to PC5 QoS parameters as defined in clause 5.1.2.1. + +The V2X application layer may provide a group size and a member ID as specified in clause 5.2.1.3. + +3. Transmitting UE determines a source Layer-2 ID and a destination Layer-2 ID and Receiving UE(s) determine destination Layer-2 ID, as specified in clauses 5.6.1.1 and 5.6.1.3. + +The destination Layer-2 ID is passed down to the AS layer of Receiving UE(s) for the groupcast mode communication reception. + +Transmitting UE determines the PC5 QoS parameters for this groupcast mode communication as specified in clauses 5.4.1.1 and 5.4.1.3. + +If the group size and the member ID for Application Layer managed group are provided by the V2X application layer, the V2X layer passes them to the AS layer as described in clause 5.2.1.3. + +4. Transmitting UE has a V2X service associated with this groupcast mode communication. + +Transmitting UE sends the V2X service data using the source Layer-2 ID and the destination Layer-2 ID. + +NOTE: In step 4, there is only one groupcast message from the transmitting UE. + +### 6.3.3 Unicast mode V2X communication over PC5 reference point + +#### 6.3.3.1 Layer-2 link establishment over PC5 reference point + +To perform unicast mode of V2X communication over PC5 reference point, the UE is configured with the related information as described in clause 5.1.2.1. + +Figure 6.3.3.1-1 shows the layer-2 link establishment procedure for unicast mode of V2X communication over PC5 reference point. + + + +``` + +sequenceDiagram + participant UE-1 + participant UE-2 + participant UE-3 + participant UE-4 + + Note right of UE-1: 2. V2X application layer provides application information for PC5 unicast communication. + Note right of UE-2: 1. UE-2 determines the destination Layer-2 ID for signalling reception. + Note right of UE-3: 1. UE-3 determines the destination Layer-2 ID for signalling reception. + Note right of UE-4: 1. UE-4 determines the destination Layer-2 ID for signalling reception. + + UE-1->>UE-2: 3. Direct Communication Request (Broadcast or Unicast) + UE-1->>UE-3: 3. Direct Communication Request (Broadcast or Unicast) + UE-1->>UE-4: 3. Direct Communication Request (Broadcast or Unicast) + + subgraph A) UE oriented Layer-2 link establishment + UE-1->>UE-2: 4a. Security Establishment + UE-2->>UE-1: 5a. Direct Communication Accept (Unicast) + UE-1->>UE-2: 6. V2X service data over unicast link + end + + subgraph B) V2X Service oriented Layer-2 link establishment + UE-1->>UE-2: 4b. Security Establishment + UE-2->>UE-1: 5b. Direct Communication Accept (Unicast) + UE-1->>UE-4: 4b. Security Establishment + UE-4->>UE-1: 5b. Direct Communication Accept (Unicast) + UE-1->>UE-2: 6. V2X service data over unicast link + UE-1->>UE-4: 6. V2X service data over unicast link + end + +``` + +Sequence diagram illustrating the layer-2 link establishment procedure for unicast mode of V2X communication over PC5 reference point. The diagram shows four User Equipment (UE) entities: UE-1, UE-2, UE-3, and UE-4. The process starts with UE-1 providing application information for PC5 unicast communication. UE-2, UE-3, and UE-4 determine the destination Layer-2 ID for signalling reception. UE-1 sends a Direct Communication Request (Broadcast or Unicast) to the other UEs. The procedure then branches into two options: A) UE oriented Layer-2 link establishment and B) V2X Service oriented Layer-2 link establishment. Both options involve Security Establishment, Direct Communication Accept (Unicast), and V2X service data over unicast link. + +**Figure 6.3.3.1-1: Layer-2 link establishment procedure** + +1. The UE(s) determine the destination Layer-2 ID for signalling reception for PC5 unicast link establishment as specified in clause 5.6.1.4. The destination Layer-2 ID is configured with the UE(s) as specified in clause 5.1.2.1. +2. The V2X application layer in UE-1 provides application information for PC5 unicast communication. The application information includes the V2X service type(s) and the initiating UE's Application Layer ID. The target UE's Application Layer ID may be included in the application information. + +The V2X application layer in UE-1 may provide V2X Application Requirements for this unicast communication. UE-1 determines the PC5 QoS parameters and PFI as specified in clause 5.4.1.4. + +If UE-1 decides to reuse the existing PC5 unicast link as specified in clause 5.2.1.4, the UE triggers Layer-2 link modification procedure as specified in clause 6.3.3.4. + +3. UE-1 sends a Direct Communication Request message to initiate the unicast layer-2 link establishment procedure. The Direct Communication Request message includes: + - Source User Info: the initiating UE's Application Layer ID (i.e. UE-1's Application Layer ID). + - If the V2X application layer provided the target UE's Application Layer ID in step 2, the following information is included: + - Target User Info: the target UE's Application Layer ID (i.e. UE-2's Application Layer ID). + - V2X Service Info: the information about V2X service type(s) requesting Layer-2 link establishment. + - Security Information: the information for the establishment of security. + +NOTE 1: The Security Information and the necessary protection of the Source User Info and Target User Info are defined in TS 33.536 [26]. + +The source Layer-2 ID and destination Layer-2 ID used to send the Direct Communication Request message are determined as specified in clauses 5.6.1.1 and 5.6.1.4. The destination Layer-2 ID may be broadcast or unicast Layer-2 ID. When unicast Layer-2 ID is used, the Target User Info shall be included in the Direct Communication Request message. + +UE-1 sends the Direct Communication Request message via PC5 broadcast or unicast using the source Layer-2 ID and the destination Layer-2 ID. + +4. Security with UE-1 is established as below: + - 4a. If the Target User Info is included in the Direct Communication Request message, the target UE, i.e. UE-2, responds by establishing the security with UE-1. + - 4b. If the Target User Info is not included in the Direct Communication Request message, the UEs that are interested in using the announced V2X service type(s) over a PC5 unicast link with UE-1 responds by establishing the security with UE-1. + +NOTE 2: The signalling for the Security Procedure is defined in TS 33.536 [26]. + +When the security protection is enabled, UE-1 sends the following information to the target UE: + +- If IP communication is used: + - IP Address Configuration: For IP communication, IP address configuration is required for this link and indicates one of the following values: + - "IPv6 Router" if IPv6 address allocation mechanism is supported by the initiating UE, i.e., acting as an IPv6 Router; or + - "IPv6 address allocation not supported" if IPv6 address allocation mechanism is not supported by the initiating UE. + - Link Local IPv6 Address: a link-local IPv6 address formed locally based on RFC 4862 [21] if UE-1 does not support the IPv6 IP address allocation mechanism, i.e. the IP Address Configuration indicates "IPv6 address allocation not supported". + - QoS Info: the information about PC5 QoS Flow(s) to be added. For each PC5 QoS Flow, the PFI, the corresponding PC5 QoS parameters (i.e. PQI and conditionally other parameters such as MFBR/GFBR, etc.) and the associated V2X service type(s). + +The source Layer-2 ID used for the security establishment procedure is determined as specified in clauses 5.6.1.1 and 5.6.1.4. The destination Layer-2 ID is set to the source Layer-2 ID of the received Direct Communication Request message. + +Upon receiving the security establishment procedure messages, UE-1 obtains the peer UE's Layer-2 ID for future communication, for signalling and data traffic for this unicast link. + +5. A Direct Communication Accept message is sent to UE-1 by the target UE(s) that has successfully established security with UE-1: + +- 5a. (UE oriented Layer-2 link establishment) If the Target User Info is included in the Direct Communication Request message, the target UE, i.e. UE-2 responds with a Direct Communication Accept message if the Application Layer ID for UE-2 matches. +- 5b. (V2X Service oriented Layer-2 link establishment) If the Target User Info is not included in the Direct Communication Request message, the UEs that are interested in using the announced V2X Service(s) respond to the request by sending a Direct Communication Accept message (UE-2 and UE-4 in Figure 6.3.3.1-1). + +The Direct Communication Accept message includes: + +- Source User Info: Application Layer ID of the UE sending the Direct Communication Accept message. +- QoS Info: the information about PC5 QoS Flow(s) requested by UE-1. For each PC5 QoS Flow, the PFI, the corresponding PC5 QoS parameters (i.e. PQI and conditionally other parameters such as MFBR/GFBR, etc.) and the associated V2X service type(s). +- If IP communication is used: + - IP Address Configuration: For IP communication, IP address configuration is required for this link and indicates one of the following values: + - "IPv6 Router" if IPv6 address allocation mechanism is supported by the target UE, i.e., acting as an IPv6 Router; or + - "IPv6 address allocation not supported" if IPv6 address allocation mechanism is not supported by the target UE. + - Link Local IPv6 Address: a link-local IPv6 address formed locally based on RFC 4862 [21] if the target UE does not support the IPv6 IP address allocation mechanism, i.e. the IP Address Configuration indicates "IPv6 address allocation not supported", and UE-1 included a link-local IPv6 address in the Direct Communication Request message. The target UE shall include a non-conflicting link-local IPv6 address. + +If both UEs (i.e. the initiating UE and the target UE) selected to use link-local IPv6 address, they shall disable the duplicate address detection defined in RFC 4862 [21]. + +NOTE 3: When either the initiating UE or the target UE indicates the support of IPv6 router, corresponding address configuration procedure would be carried out after the establishment of the layer 2 link, and the link-local IPv6 addresses are ignored. + +The V2X layer of the UE that established PC5 unicast link passes the PC5 Link Identifier assigned for the unicast link and the PC5 unicast link related information down to the AS layer. The PC5 unicast link related information includes Layer-2 ID information (i.e. source Layer-2 ID and destination Layer-2 ID) and the corresponding PC5 QoS parameters. This enables the AS layer to maintain the PC5 Link Identifier together with the PC5 unicast link related information. + +6. V2X service data is transmitted over the established unicast link as below: + +The PC5 Link Identifier, and PFI are provided to the AS layer, together with the V2X service data. + +Optionally in addition, the Layer-2 ID information (i.e. source Layer-2 ID and destination Layer-2 ID) is provided to the AS layer. + +NOTE 4: It is up to UE implementation to provide the Layer-2 ID information to the AS layer. + +UE-1 sends the V2X service data using the source Layer-2 ID (i.e. UE-1's Layer-2 ID for this unicast link) and the destination Layer-2 ID (i.e. the peer UE's Layer-2 ID for this unicast link). + +NOTE 5: PC5 unicast link is bi-directional, therefore the peer UE of UE-1 can send the V2X service data to UE-1 over the unicast link with UE-1. + +#### 6.3.3.2 Link identifier update for a unicast link + +Figure 6.3.3.2-1 shows the link identifier update procedure for a unicast link. When privacy requirements is configured for a V2X service type associated with the unicast link, identifiers used for unicast mode of V2X communication over PC5 reference point (e.g. Application Layer ID, Source Layer-2 ID and IP address/prefix) shall be changed over time as specified in clauses 5.6.1.1 and 5.6.1.4. A UE may decide to change the identifiers for other reasons, e.g. application layer requirement. This procedure is used to update and exchange new identifiers between the source and the peer UEs for a unicast link before using the new identifiers, to prevent service interruptions. When there are privacy requirements as indicated above, this procedure is executed over a security protected unicast link. + +If a UE has multiple unicast links using the same Application Layer IDs or Layer-2 IDs, the UE needs to perform the link identifier update procedure over each of the unicast link. + + + +``` + +sequenceDiagram + participant UE-1 + participant UE-2 + Note left of UE-1: 0. Unicast link + UE-1->>UE-2: 1. Link Identifier Update Request + UE-2-->>UE-1: 2. Link Identifier Update Response + UE-1->>UE-2: 3. Link Identifier Update Ack + Note left of UE-1: 4. Start using each UE's new identifiers + Note right of UE-2: 5. Start using each UE's new identifiers + +``` + +Sequence diagram illustrating the link identifier update procedure between UE-1 and UE-2. The diagram shows five steps: 0. Unicast link establishment; 1. Link Identifier Update Request from UE-1 to UE-2; 2. Link Identifier Update Response from UE-2 to UE-1; 3. Link Identifier Update Ack from UE-1 to UE-2; 4. Start using each UE's new identifiers at UE-1; 5. Start using each UE's new identifiers at UE-2. + +**Figure 6.3.3.2-1: Link identifier update procedure** + +0. UE-1 and UE-2 have a unicast link established as described in clause 6.3.3.1. +1. UE-1 decides to change its identifier(s), e.g. due to the Application Layer ID change or upon expiry of a timer. UE-1 generates its new Layer-2 ID and sends a Link Identifier Update Request message to UE-2 using the old identifiers. + +The Link Identifier Update Request message includes the new identifier(s) to use (including the new Layer-2 ID, Security Information, optionally the new Application Layer ID and optionally new IP address/prefix if IP communication is used). The new identifier(s) shall be cyphered to protect privacy if security is configured for the unicast link. After sending the Link Identifier Update Request message, if the UE-1 has data to send, UE-1 keeps sending data traffic to UE-2 with the old identifiers until UE-1 sends the Link Identifier Update Ack message to UE-2. + +NOTE 1: The timer is running on per Source Layer-2 ID. + +NOTE 2: When one of the two UEs acts as IPv6 router as described in clause 5.2.1.5 and IP address/prefix also needs to be changed, corresponding address configuration procedure would be carried out after the Link Identifier update procedure. + +2. Upon reception of the Link Identifier Update Request message, UE-2 changes its identifier(s). UE-2 responds with a Link Identifier Update Response message which includes the new identifier(s) to use (including the new Layer-2 ID, Security Information, optionally the new Application Layer ID, and optionally a new IP address/prefix if IP communication is used). The new identifier(s) shall be cyphered to protect privacy if security is configured for the unicast link. The Link Identifier Update Response message is sent using the old identifiers. UE-2 continues to receive traffic with the old Layer-2 ID from UE-1 until UE-2 receives traffic with the new Layer-2 ID from UE-1. After sending the Link Identifier Update Response message, UE-2 keeps sending data traffic to UE-1 with the old identifiers, if UE-2 has data to send, until UE-2 receives the Link Identifier Update Ack message from UE-1. +3. Upon reception of the Link Identifier Update Response message, UE-1 responds with a Link Identifier Update Ack message. The Link Identifier Update Ack message includes the new identifier(s) from UE-2, as received on + +the Link Identifier Update Response message. The Link Identifier Update Ack message is sent using the old identifiers. UE-1 continues to receive traffic with the old Layer-2 ID from UE-2 until UE-1 receives traffic with the new Layer-2 ID from UE-2. + +4. The V2X layer of UE-1 passes the PC5 Link Identifier for the unicast link and the updated Layer-2 IDs (i.e. new Layer-2 ID for UE-1 for the source and new Layer-2 ID of UE-2 for the destination) down to the AS layer. This enables the AS layer to update the provided Layer-2 IDs for the unicast link. + +UE-1 starts using its new identifiers and UE-2's new identifiers for this unicast link. + +5. Upon reception of the Link Identifier Update Ack message, the V2X layer of UE-2 passes the PC5 Link Identifier for the unicast link and the updated Layer-2 IDs (i.e. new Layer-2 ID of UE-2 for the source and new Layer-2 ID for UE-1 for the destination) down to the AS layer. This enables the AS layer to update the provided Layer-2 IDs for the unicast link. + +UE-2 starts using its new identifiers and UE-1's new identifiers for this unicast link. + +NOTE 3: The Security Information in the above messages also needs to be updated at the same time as the Layer-2 IDs. This is defined in TS 33.536 [26]. + +#### 6.3.3.3 Layer-2 link release over PC5 reference point + +Figure 6.3.3.3-1 shows the layer-2 link release procedure over PC5 reference point. + + + +``` + +sequenceDiagram + participant UE-1 + participant UE-2 + Note left of UE-1: 0. Unicast link + UE-1->>UE-2: 1. Disconnect Request + UE-2-->>UE-1: 2. Disconnect Response + +``` + +Sequence diagram illustrating the Layer-2 link release procedure between UE-1 and UE-2. The diagram shows three steps: 0. Unicast link (established), 1. Disconnect Request (sent from UE-1 to UE-2), and 2. Disconnect Response (sent from UE-2 to UE-1). + +Figure 6.3.3.3-1: Layer-2 link release procedure + +0. UE-1 and UE-2 have a unicast link established as described in clause 6.3.3.1. +1. UE-1 sends a Disconnect Request message to UE-2 in order to release the layer-2 link and deletes all context data associated with the layer-2 link. The Disconnect Request message includes Security Information. +2. Upon reception of the Disconnect Request message UE-2 may respond with a Disconnect Response message and deletes all context data associated with the layer-2 link. The Disconnect Response message includes Security Information. + +The V2X layer of each UE informs the AS layer that the unicast link has been released. The V2X layer uses PC5 Link Identifier to indicate the released unicast link. This enables the AS layer to delete the context related to the released unicast link. + +NOTE: The Security Information in the above messages is defined in TS 33.536 [26]. + +#### 6.3.3.4 Layer-2 link modification for a unicast link + +Figure 6.3.3.4-1 shows the layer-2 link modification procedure for a unicast link. This procedure is used to: + +- add new PC5 QoS Flow(s) in the existing PC5 unicast link. + - This covers the case for adding new PC5 QoS Flow(s) to the existing V2X service(s) as well as the case for adding new PC5 QoS Flow(s) to new V2X service(s). +- modify existing PC5 QoS Flow(s) in the existing PC5 unicast link. + +- This covers the case for modifying the PC5 QoS parameters for existing PC5 QoS Flow(s). +- This also covers the case for removing the associated V2X service(s) from existing PC5 QoS Flow(s) as well as the case for associating new V2X service(s) with existing PC5 QoS Flow(s). +- remove existing PC5 QoS Flow(s) in the existing PC5 unicast link. + + + +``` + +sequenceDiagram + participant UE-1 + participant UE-2 + Note right of UE-1: 0. Unicast link + UE-1->>UE-2: 1. Link Modification Request + UE-2-->>UE-1: 2. Link Modification Accept + +``` + +Sequence diagram illustrating the Layer-2 link modification procedure between UE-1 and UE-2. The diagram shows three steps: 0. Unicast link (established), 1. Link Modification Request (sent from UE-1 to UE-2), and 2. Link Modification Accept (sent from UE-2 to UE-1). + +**Figure 6.3.3.4-1: Layer-2 link modification procedure** + +0. UE-1 and UE-2 have a unicast link established as described in clause 6.3.3.1. +1. The V2X application layer in UE-1 provides application information for PC5 unicast communication. The application information includes the V2X service type(s) and the initiating UE's Application Layer ID. The target UE's Application Layer ID may be included in the application information. If UE-1 decides to reuse the existing PC5 unicast link as specified in clause 5.2.1.4, so decides to modify the unicast link established with UE-2, UE-1 sends a Link Modification Request to UE-2. + +The Link Modification Request message includes: + +- To add new PC5 QoS Flow(s) in the existing PC5 unicast link: + - QoS Info: the information about PC5 QoS Flow(s) to be added. For each PC5 QoS Flow, the PFI, the corresponding PC5 QoS parameters (i.e. PQI and conditionally other parameters such as MFBR/GFBR, etc.) and the associated V2X service type(s). +- To modify PC5 QoS Flow(s) in the existing PC5 unicast link: + - QoS Info: the information about PC5 QoS Flow(s) to be modified. For each PC5 QoS Flow, the PFI, the corresponding PC5 QoS parameters (i.e. PQI and conditionally other parameters such as MFBR/GFBR, etc.) and the associated V2X service type(s). +- To remove PC5 QoS Flow(s) in the existing PC5 unicast link: + - PFI(s). + +2. UE-2 responds with a Link Modification Accept message. + +The Link Modification Accept message includes: + +- For case a) and case b) described in step 1: + - QoS Info: the information about PC5 QoS Flow(s) requested by UE-1. For each PC5 QoS Flow, the PFI, the corresponding PC5 QoS parameters (i.e. PQI and conditionally other parameters such as MFBR/GFBR, etc.) and the associated V2X service type(s). + +The V2X layer of each UE provides information about the unicast link modification to the AS layer. This enables the AS layer to update the context related to the modified unicast link. + +#### 6.3.3.5 Layer-2 link maintenance over PC5 reference point + +The PC5 Signalling Protocol shall support keep-alive functionality that is used to detect if a particular PC5 unicast link is still valid. Either side of the PC5 unicast link can initiate the layer-2 link maintenance procedure (i.e. keep-alive + +procedure), based on for example triggers from the AS layer or internal timers. The UEs shall minimize the keep-alive signalling, e.g. cancel the procedure if data are successfully received over the PC5 unicast link. + + + +The diagram shows a sequence of interactions between two User Equipment (UE) blocks, UE-1 and UE-2. At the top, a double-lined arrow between them is labeled '0. Unicast link', indicating an established connection. Below this, a single arrow points from UE-1 to UE-2, labeled '1. Keep-alive'. Finally, a single arrow points from UE-2 back to UE-1, labeled '2. Keep-alive Ack'. + +Sequence diagram illustrating the Layer-2 link maintenance procedure between UE-1 and UE-2. + +**Figure 6.3.3.5-1: Layer-2 link maintenance procedure** + +0. UE-1 and UE-2 have a unicast link established as described in clause 6.3.3.1. +1. Based on trigger conditions, UE-1 sends a Keep-alive message to UE-2 in order to determine the status of the PC5 unicast link. + +NOTE 1: It is left to Stage 3 to determine the exact triggers for the keep-alive messages. For example, the trigger can be based on a timer associated with the Layer-2 link. The timer can be reset with a successful reception event defined by TS 38.300 [11]. + +2. Upon reception of the Keep-alive message, UE-2 responds with a Keep-alive Ack message. + +The UE initiating the keep-alive procedure shall determine the follow up actions based on the result of the signalling, e.g. proceed with implicit layer-2 link release. + +NOTE 2: It is left to Stage 3 to determine the follow up actions. For example, a successful reception event can also cancel the layer-2 link release if received in time. + +## 6.4 Procedures for V2X communication over Uu reference point + +### 6.4.1 Procedure for notification on QoS Sustainability Analytics to the V2X Application Server + +Figure 6.4.1-1 depicts a procedure for notification on QoS Sustainability Analytics to the V2X Application Server. + +![Sequence diagram showing the notification on QoS Sustainability Analytics to the V2X Application Server. The diagram involves five lifelines: UE, OAM, NWDAF, NEF, and V2X Application Server. The sequence of messages is: 1. V2X Application Server derives information (optional UE involvement); 2. V2X Application Server sends Nnef_AnalyticsExposure_Subscribe/Nnef_AnalyticsExposure_Fetch to NEF; 3. NEF interacts with NWDAF (TS 23.288 [20] clause 6.9.4); 4. NEF sends Nnef_AnalyticsExposure_Notify/Nnef_AnalyticsExposure_Fetch response to V2X Application Server; 5. V2X Application Adjustment.](3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg) + +``` + +sequenceDiagram + participant UE + participant OAM + participant NWDAF + participant NEF + participant V2X Application Server + + Note right of V2X Application Server: 1. V2X Application Server derives information. UE involvement is optional. + Note right of NEF: 3. TS 23.288 [20] clause 6.9.4 (QoS Sustainability analytics) + + V2X Application Server->>NEF: 2. Nnef_AnalyticsExposure_Subscribe/ +Nnef_AnalyticsExposure_Fetch + NEF->>NWDAF: + NWDAF-->>NEF: + NEF->>V2X Application Server: 4. Nnef_AnalyticsExposure_Notify/ +Nnef_AnalyticsExposure_Fetch response + Note right of V2X Application Server: 5. V2X Application Adjustment + +``` + +Sequence diagram showing the notification on QoS Sustainability Analytics to the V2X Application Server. The diagram involves five lifelines: UE, OAM, NWDAF, NEF, and V2X Application Server. The sequence of messages is: 1. V2X Application Server derives information (optional UE involvement); 2. V2X Application Server sends Nnef\_AnalyticsExposure\_Subscribe/Nnef\_AnalyticsExposure\_Fetch to NEF; 3. NEF interacts with NWDAF (TS 23.288 [20] clause 6.9.4); 4. NEF sends Nnef\_AnalyticsExposure\_Notify/Nnef\_AnalyticsExposure\_Fetch response to V2X Application Server; 5. V2X Application Adjustment. + +**Figure 6.4.1-1: Notification on QoS Sustainability Analytics to the V2X Application Server** + +1. The V2X Application Server derives information on V2X service, location information (an area or path of interest), QoS requirements and reporting threshold(s). The location information can be in the form of geographic coordinates to reflect a list of waypoints. + +NOTE 1: Step 1 is outside 3GPP scope. The V2X Application Server can derive this, for example, based on information provided by the UE(s) or the V2X Application Server uses locally configured information. + +2. The V2X Application Server subscribes to or requests notification on QoS Sustainability Analytics provided by NWDAF via NEF by invoking Nnef\_AnalyticsExposure\_Subscribe service operation as defined in clause 6.1.1.2 of TS 23.288 [20] or Nnef\_AnalyticsExposure\_Fetch service operation as defined in clause 6.1.2.2 of TS 23.288 [20]. The parameters included in the request are described in clause 5.4.5.2.2. + +The V2X Application Server may include multiple sets of parameters in order to provide different combinations of "Location information" and "Analytics Target Period" when requesting notification on QoS Sustainability Analytics. + +NOTE 2: The V2X Application Server needs to set the "Time when analytics information is needed" parameter (see TS 23.288 [20]) appropriately, e.g. large enough, to perform the V2X application adjustment before the potential QoS change happens. + +NOTE 3: The request made by the V2X Application Server does not have to be per UE. In order to make a request for multiple UEs, the V2X Application Server can perform mapping between individual UE path requests and subscription to notification per path/road segment. Whether a request is generated for a UE or multiple UEs, and how to set the parameters included in the request and triggers for such request are up to the V2X Application Server implementation and outside of the scope of 3GPP. + +3. When the NEF receives the request from the V2X Application Server, the NEF interacts with the NWDAF as described in the procedure in clause 6.9.4 of TS 23.288 [20]. The NEF shall map the QoS Characteristics attributes including Resource Type, PDB and PER received from the V2X Application Server to the most appropriate 5QI that is supported by the network if the V2X application server does not provide 5QI. If 5QI is provided by the V2X Application Server, NEF does not perform such mapping. The NEF may map other parameters included in the request from the V2X Application Server to information used by the 3GPP system. + +4. If the NEF receives the response from the NWDAF, the NEF notifies the V2X Application Server with the analytics information on QoS Sustainability Analytics by invoking Nnef\_AnalyticsExposure\_Notify service operation for a Subscribe-Notify model as defined in clause 6.1.1.2 of TS 23.288 [20] or Nnef\_AnalyticsExposure\_Fetch service operation for a Request-Response model as defined in clause 6.1.2.2 of TS 23.288 [20]. + +5. V2X application adjustment may take place. + +NOTE 4: Step 5 is outside 3GPP scope. V2X application adjustment can take place at UE and/or V2X Application Server, e.g. adjust inter-vehicle gap, change video codec parameters, etc. For the case that the V2X Application Server uses the request for multiple UEs in step 2, the V2X Application Server can perform the V2X application adjustment for every UE corresponding to the request. + +For a Subscribe-Notify model, when the V2X Application Server wants to cancel subscription to analytics information, it invokes the Nnef\_AnalyticsExposure\_Unsubscribe service operation as defined in clause 6.1.1.2 of TS 23.288 [20]. + +## 6.5 Procedures for Service Authorization to NG-RAN for V2X communications over PC5 reference point + +### 6.5.1 General + +In order to enable PC5 radio resource control in NG-RAN, per PC5 RAT V2X service authorization information and PC5 QoS parameters need to be made available in NG-RAN, this clause describes the corresponding procedures and aspects. + +### 6.5.2 Registration procedure + +The Registration procedure for UE is performed as defined in TS 23.502 [7] with the following additions: + +- The UE includes the PC5 Capability for V2X (i.e. LTE PC5 only, NR PC5 only, both LTE and NR PC5) as part of the "5GMM capability" in the Registration Request message. The AMF stores this information for V2X operation. The PC5 Capability for V2X indicates whether the UE is capable of V2X communication over PC5 reference point and which specific PC5 RAT(s) it supports. +- The AMF obtains the V2X Subscription data as part of the user subscription data from UDM during UE Registration procedure using Nudm\_SDM service as defined in clause 4.2.2.2.2 of TS 23.502 [7]. +- The AMF determines whether the UE is authorized to use V2X communication over PC5 reference point based on UE's PC5 Capability for V2X and the subscription data related to V2X service authorization information (i.e. "V2X services authorized" indication, UE-PC5-AMBR per PC5 RAT and cross-RAT PC5 control authorization if applicable) received from UDM, and stores the V2X service authorization information as part of the UE context. +- The PCF provides the PC5 QoS parameters to AMF, and the AMF stores them in the UE context. +- If the UE is PC5 capable for V2X, and the UE is authorized to use V2X communication over PC5 reference point based on the subscription data, then the AMF shall include the following information in the NGAP message sent to NG-RAN: + - a "V2X services authorized" indication, indicating the UE is authorized to use V2X communication over PC5 reference point as Vehicle UE, Pedestrian UE or both. + - UE-PC5-AMBR per PC5 RAT and cross-RAT PC5 control authorization (if applicable), used by NG-RAN for the resource management of UE's PC5 transmission for V2X services in network scheduled mode. + - the PC5 QoS parameters used by the NG-RAN for the resource management of UE's PC5 transmission for V2X services in network scheduled mode. +- If the UE is authorized to use V2X communication over PC5 reference point, then the AMF should not initiate the release of the signalling connection after the completion of the Registration procedure. The release of the NAS signalling relies on the decision of NG-RAN, as specified in TS 23.502 [7]. + +### 6.5.3 Service Request procedure + +The Service Request procedure for UE in CM-IDLE state is performed as defined in TS 23.502 [7] with the following additions: + +- If the UE is PC5 capable for V2X, and the UE is authorized to use V2X communication over PC5 reference point, then the AMF shall include a "V2X services authorized" indication in the NGAP message, indicating the UE is authorized to use V2X communication over PC5 reference point as Vehicle UE, Pedestrian UE or both. +- The AMF includes the UE-PC5-AMBR, and cross-RAT PC5 control authorization in the NGAP message to the NG-RAN as part of the UE context and NG-RAN may use in resource management of UE's PC5 transmission for V2X services in network scheduled mode. +- The AMF sends the PC5 QoS parameters to NG-RAN via N2 signalling. The PC5 QoS parameters may be stored in the UE context after the registration procedure. If the UE is authorized to use V2X communication over PC5 reference point but AMF does not have PC5 QoS parameters available, the AMF fetches the PC5 QoS parameters from the PCF. + +### 6.5.4 N2 Handover procedure + +The N2 based handover or the Inter-RAT to NG-RAN handover procedures for UE are performed as defined in TS 23.502 [7] with the following additions: + +- If the UE is PC5 capable for V2X, and the UE is authorized to use V2X communication over PC5 reference point, then the target AMF shall send the "V2X services authorized" indication, UE-PC5-AMBR, cross-RAT PC5 control authorization, and PC5 QoS parameters to the target NG-RAN as follows: + - For the intra AMF handover, the "V2X services authorized" indication, UE-PC5-AMBR, cross-RAT PC5 control authorization, and PC5 QoS parameters are included in the NGAP Handover Request message. + - For the inter AMF handover or Inter-RAT handover to NG-RAN, the "V2X services authorized" indication, UE-PC5-AMBR, cross-RAT PC5 control authorization, and PC5 QoS parameters are included in the NGAP Handover Request message sent to the target NG-RAN. + +### 6.5.5 Xn Handover procedure + +The Xn based handover procedures for UE are performed as defined in TS 23.502 [7] with the following additions: + +- If the "V2X services authorized" indication is included in the UE context (as described in TS 38.423 [23]), then the source NG-RAN shall include a "V2X services authorized" indication, UE-PC5-AMBR, cross-RAT PC5 control authorization and PC5 QoS parameters in the XnAP Handover Request message to the target NG-RAN. +- If the UE is PC5 capable for V2X, and the UE is authorized to use V2X communication over PC5 reference point, then the AMF shall send the "V2X services authorized" indication, the UE-PC5-AMBR, cross-RAT PC5 control authorization, and PC5 QoS parameters to the target NG-RAN in the Path Switch Request Acknowledge message + +### 6.5.6 Subscriber Data Update Notification to AMF + +The procedure of Subscriber Data Update Notification to AMF is performed as defined in TS 23.502 [7] with the following additions: + +- The Nudm\_SDM\_Notification service operation may contain the "V2X services authorized" indication or the UE-PC5-AMBR, or cross-RAT PC5 control authorization or any combination; +- The AMF updates the UE Context with the above new V2X subscription data. +- When the AMF updates UE context stored at NG-RAN, the UE context contains the V2X subscription data. + +### 6.5.7 Delivery of PC5 QoS parameters to NG-RAN + +The UE Policy Association Establishment procedure and UE Policy Association Modification procedure, as defined in TS 23.502 [7], is used to provide to the AMF PC5 QoS parameters used by NG-RAN. When receiving Npcf\_UEPolicyControl\_Create Request from the AMF which includes the PC5 capability for V2X or when receiving the updated subscription data from UDR, the PCF generates the PC5 QoS parameters used by NG-RAN corresponding to a UE as defined in clause 5.4.2. + +The (V-)PCF provides the information to the AMF as follows: + +- In the roaming case, the H-PCF includes the PC5 QoS parameters used by NG-RAN in the Npcf\_UEPolicyControl\_Create Response message or Npcf\_UEPolicyControl\_UpdateNotify Request message sent to V-PCF in an N2 PC5 policy container, and V-PCF relays this N2 PC5 policy container as the N2 container in the Namf\_Communication\_N1N2MessageTransfer message sent to AMF. +- In the non-roaming case, the PCF includes the PC5 QoS parameters used by NG-RAN in an N2 container in Namf\_Communication\_N1N2MessageTransfer message sent to AMF. + +When the AMF determines that the N2 PC5 policy container comes from (V-)PCF, the AMF stores such information as part of the UE context. + +In the UE Configuration Update procedure triggered by UE Policy Association Establishment or UE Policy Association Modification, the AMF: + +- The AMF forwards the PC5 QoS parameters in the NGAP message to the NG-RAN if a N2 PC5 policy container is received in the Namf\_Communication\_N1N2MessageTransfer message. +- The AMF forwards the PC5 QoS parameters in the NAS message to UE by using the UE Configuration Update procedure for transparent UE Policy delivery procedure defined in clause 4.2.4.3 of TS 23.502 [7] if a UE Policy Container is received in the Namf\_Communication\_N1N2MessageTransfer message. + +NOTE 1: If the PC5 QoS parameters are provided to both NG-RAN and UE, both the N2 PC5 Policy Container and the UE Policy Container are included in the Namf\_Communication\_N1N2MessageTransfer message. + +NOTE 2: Non-UE specific PC5 QoS parameters, e.g. default PC5 QoS parameters, can also be locally configured in NG-RAN. How such configuration is performed is out of scope of this specification. + +### 6.5.8 PC5 Capability for V2X indication and V2X related information per PC5 RAT + +A UE may support multiple PC5 RATs (i.e. LTE PC5 and NR PC5). For such UE, the PC5 Capability for V2X indication and V2X related information can be per PC5 RAT as described in clause 6.5.2. + +The cross-RAT PC5 control authorization indicates whether LTE Uu controls LTE PC5 and/or NR PC5 from the cellular network, and whether NR Uu controls LTE PC5 and/or NR PC5 from the cellular network. + +NOTE: Stage 3 does not define an explicit cross-RAT PC5 control authorization IE and it is indicated in an implicit manner as specified in TS 38.413 [22] and TS 38.423 [23]. + +# --- Annex A (informative): Application Function influence based edge computing for V2X services + +To route V2X messages or any traffic for V2X purposes to/from V2X Application Server(s) in a local Data Network (DN) close to NG-RAN, V2X Application Server operated by e.g. operators, OEMs, road authorities, can use the Application Function (AF) influence on traffic routing feature defined in clause 5.6.7 of TS 23.501 [6]. + +The V2X Application Server that sends the AF request for AF influence based edge computing for V2X services can be the same V2X Application Server to/from which the traffic is routed. + +When Application Function influence on traffic routing is applied, a local UPF can be selected to route the traffic to the local V2X Application Server. + +Usage of Application Function (AF) influence on traffic routing feature and its application for SMF to control UPF data forwarding are defined in clause 5.6.7 and clause 5.8.2 of TS 23.501 [6]. + +# Annex B (informative): Road Side Unit (RSU) implementation options + +This Annex presents examples how RSU can be implemented in 5GS, as shown in TS 23.285 [8]. Figure B-1 shows a UE-type RSU, which combines a UE with the V2X application logic. + + + +The diagram illustrates a UE-type RSU implementation. On the left, a 'Vehicle' (UE A) contains a 'V2X Application'. On the right, a 'Stationary' (UE B) is enclosed in a dashed box labeled 'RSU' and also contains a 'V2X Application'. A dashed line labeled 'V5' connects the two V2X Applications. A solid line labeled 'NR-PC5' connects UE A and UE B. + +Diagram of UE-type RSU implementation + +**Figure B-1: RSU includes a UE and the V2X application logic** + +Figure B-2 shows one example of gNB-type RSUs. In this example, the RSU comprises a gNB, a collocated UPF, and a V2X Application Server. + + + +The diagram illustrates a gNB-type RSU implementation. On the left, a 'Vehicle' (UE A) contains a 'V2X Application'. On the right, a dashed box labeled 'RSU' contains a 'V2X Application Server', a 'UPF', and a 'gNB'. A dashed line labeled 'V1' connects the V2X Application in UE A to the V2X Application Server in the RSU. A solid line labeled 'NR-Uu' connects UE A to the gNB in the RSU. + +Diagram of gNB-type RSU implementation + +**Figure B-2: RSU includes a gNB, collocated UPF and a V2X Application Server** + +# --- Annex C (informative): Change history + +| Change history | | | | | | | | +|----------------|---------|-----------|------|-----|-----|------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2019-09 | SP#85 | - | - | - | - | MCC Editorial update for publication after TSG SA#85 approval | 16.0.0 | +| 2019-12 | SP#86 | SP-191083 | 0008 | 2 | F | Clarification on QoS handling | 16.1.0 | +| 2019-12 | SP#86 | SP-191083 | 0009 | 1 | F | Update on Architecture and Functional Entities | 16.1.0 | +| 2019-12 | SP#86 | SP-191083 | 0015 | 3 | F | Terminology correction: Replace service type by V2X services | 16.1.0 | +| 2019-12 | SP#86 | SP-191083 | 0018 | 1 | F | Corrections of QoS Sustainability Analytics | 16.1.0 | +| 2019-12 | SP#86 | SP-191083 | 0019 | 2 | F | Supplement for address resolution and clarification for Localized V2X Application Server discovery and routing | 16.1.0 | +| 2019-12 | SP#86 | SP-191083 | 0021 | 3 | F | Resolve editor's note on PC5 Link-AMBR | 16.1.0 | +| 2019-12 | SP#86 | SP-191083 | 0023 | 3 | F | Application classifier at Rx UE | 16.1.0 | +| 2019-12 | SP#86 | SP-191083 | 0024 | 7 | F | Update to delivery of PC5 QoS parameters to NG-RAN | 16.1.0 | +| 2019-12 | SP#86 | SP-191083 | 0025 | 3 | F | Correction to V2X Policy update due to UE PLMN change | 16.1.0 | +| 2019-12 | SP#86 | SP-191083 | 0027 | 2 | F | Correction what a V2X service is | 16.1.0 | +| 2019-12 | SP#86 | SP-191083 | 0028 | 3 | F | V2X Policy and Parameter Provisioning for EPS and 5GS Interworking | 16.1.0 | +| 2019-12 | SP#86 | SP-191083 | 0030 | 2 | F | Clarification on IP address allocation for groupcast and multicast modes of V2X communication over PC5 reference point | 16.1.0 | +| 2019-12 | SP#86 | SP-191083 | 0033 | 2 | F | Group information to AS layer for groupcast control | 16.1.0 | +| 2019-12 | SP#86 | SP-191083 | 0034 | 3 | F | Clarification on precedence of parameters | 16.1.0 | +| 2019-12 | SP#86 | SP-191083 | 0036 | 1 | F | Removing ENs on identifiers for groupcast and unicast | 16.1.0 | +| 2019-12 | SP#86 | SP-191083 | 0037 | - | F | Resolving ENs on NR PC5 QoS | 16.1.0 | +| 2019-12 | SP#86 | SP-191083 | 0039 | 1 | F | Clarification on Range parameter | 16.1.0 | +| 2019-12 | SP#86 | SP-191083 | 0040 | 2 | F | Removing EN related to groupcast security | 16.1.0 | +| 2019-12 | SP#86 | SP-191083 | 0041 | 1 | F | Use of unicast L2 ID for unicast link establishment | 16.1.0 | +| 2019-12 | SP#86 | SP-191083 | 0042 | 1 | F | Updated of PC5 RQIs | 16.1.0 | +| 2019-12 | SP#86 | SP-191083 | 0043 | 2 | F | Miscellaneous corrections to TS 23.287 | 16.1.0 | +| 2019-12 | SP#86 | SP-191083 | 0044 | 2 | F | unicast overview modification | 16.1.0 | +| 2019-12 | SP#86 | SP-191083 | 0045 | 1 | F | PC5 control plane protocol stack | 16.1.0 | +| 2019-12 | SP#86 | SP-191083 | 0047 | 1 | F | PC5 PQI and Priority level and PDB in PPPP | 16.1.0 | +| 2019-12 | SP#86 | SP-191083 | 0048 | 2 | F | Miscellaneous V2X corrections | 16.1.0 | +| 2019-12 | SP#86 | SP-191083 | 0049 | 3 | F | Clarification on V2X UE context delivery in Xn Handover procedure | 16.1.0 | +| 2019-12 | SP#86 | SP-191083 | 0053 | 2 | F | ENs resolution about PC5 operation in EPS/5GS IWK | 16.1.0 | +| 2019-12 | SP#86 | SP-191083 | 0059 | 2 | F | Update of unicast link establishment for security protection | 16.1.0 | +| 2020-03 | SP#87E | SP-200073 | 0061 | 2 | F | Correction on the QoS handling for groupcast | 16.2.0 | +| 2020-03 | SP#87E | SP-200073 | 0063 | 2 | F | Updates to the PC5 unicast link modification | 16.2.0 | +| 2020-03 | SP#87E | SP-200073 | 0066 | 1 | F | PC5 PDB Clarification | 16.2.0 | +| 2020-03 | SP#87E | SP-200073 | 0068 | - | F | PC5 unicast link handling regarding RLF | 16.2.0 | +| 2020-03 | SP#87E | SP-200073 | 0069 | - | F | Clarification on QoS related information to AS layer for unicast | 16.2.0 | +| 2020-03 | SP#87E | SP-200073 | 0070 | - | F | Clarification on unicast link release | 16.2.0 | +| 2020-03 | SP#87E | SP-200073 | 0073 | 2 | F | Correction of NR PC5 user plane protocol stack | 16.2.0 | +| 2020-03 | SP#87E | SP-200073 | 0075 | 2 | F | Update of PC5 Link Identifier description | 16.2.0 | +| 2020-03 | SP#87E | SP-200073 | 0076 | 1 | F | Correction of set of configuration parameters in the precedence of the V2X configuration parameters | 16.2.0 | +| 2020-03 | SP#87E | SP-200073 | 0077 | 2 | F | Support of keep-alive signalling for unicast layer-2 link | 16.2.0 | +| 2020-03 | SP#87E | SP-200073 | 0078 | - | F | Clarification on the L2 ID used for the security establishment procedures | 16.2.0 | +| 2020-03 | SP#87E | SP-200073 | 0084 | 2 | F | PC5 QoS handling for network scheduled operation mode | 16.2.0 | +| 2020-03 | SP#87E | SP-200073 | 0086 | 1 | F | Update of Link identifier update for unicast link procedure | 16.2.0 | +| 2020-03 | SP#87E | SP-200073 | 0087 | 1 | F | Miscellaneous Corrections | 16.2.0 | +| 2020-03 | SP#87E | SP-200073 | 0089 | 1 | F | Correction of QoS sustainability analytics | 16.2.0 | +| 2020-03 | SP#87E | SP-200073 | 0091 | 1 | F | served by and not served by clarification | 16.2.0 | +| 2020-03 | SP#87E | SP-200073 | 092 | - | F | V2X application server clarification | 16.2.0 | +| 2020-03 | SP#87E | SP-200073 | 0094 | - | F | Clarification on V2X services communication | 16.2.0 | +| 2020-03 | SP#87E | SP-200073 | 0096 | 1 | F | Clarification on V2X Policy and Parameter Provisioning related aspects | 16.2.0 | +| 2020-03 | SP#87E | SP-200073 | 0097 | 1 | F | Clarification on V2X groupcast and broadcast security | 16.2.0 | +| 2020-03 | SP#87E | SP-200073 | 0098 | 1 | F | Resolve the EN on PC5 QoS | 16.2.0 | +| 2020-03 | SP#87E | SP-200073 | 0101 | 1 | F | Clarification of PDB | 16.2.0 | +| 2020-03 | SP#87E | SP-200073 | 0102 | - | D | Correction to Handling of PC5 QoS Flows based on PC5 QoS Rules | 16.2.0 | +| 2020-03 | SP#87E | SP-200073 | 0103 | 1 | F | V2X Subscription Data | 16.2.0 | +| 2020-03 | SP#87E | SP-200073 | 0104 | 1 | F | EPC interworking for V2X support | 16.2.0 | +| 2020-03 | SP#87E | SP-200073 | 0106 | 1 | F | Correction to Procedure for QoS Sustainability Notification | 16.2.0 | +| 2020-07 | SP#88E | SP-200434 | 0108 | 1 | F | Miscellaneous corrections | 16.3.0 | +| 2020-07 | SP#88E | SP-200434 | 0109 | 1 | F | Correction of PC5 RAT selection handling | 16.3.0 | +| 2020-07 | SP#88E | SP-200434 | 0110 | 1 | F | Correction of PC5 cast type handling | 16.3.0 | +| 2020-07 | SP#88E | SP-200434 | 0112 | 1 | F | Clarification on the mode of communication for PC5 | 16.3.0 | +| 2020-07 | SP#88E | SP-200434 | 0113 | 1 | F | Correction on V2X Policy and Parameters for PC5 | 16.3.0 | +| 2020-07 | SP#88E | SP-200434 | 0114 | 1 | F | Correction on V2X Subscription data | 16.3.0 | +| 2020-07 | SP#88E | SP-200434 | 0117 | 1 | F | Modify Description of N1 Reference Point | 16.3.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|-----------------------------------------------------------------------------------------------|--------| +| 2020-07 | SP#88E | SP-200434 | 0119 | - | F | Introduction of missing definitions for Tx Profile and Mode of communication | 16.3.0 | +| 2020-07 | SP#88E | SP-200434 | 0120 | - | F | Clarification on groupcast mode communication | 16.3.0 | +| 2020-07 | SP#88E | SP-200434 | 0121 | 1 | F | V2X Service Type | 16.3.0 | +| 2020-07 | SP#88E | SP-200434 | 0122 | - | F | Clarification of Service Data for PC5 | 16.3.0 | +| 2020-07 | SP#88E | SP-200434 | 0124 | 1 | F | V2X service type provisioning | 16.3.0 | +| 2020-07 | SP#88E | SP-200434 | 0127 | 1 | F | RSU Implementation Options and Deployment Use Case | 16.3.0 | +| 2020-07 | SP#88E | SP-200434 | 0128 | - | F | Clean-ups including removing EN not implemented from the approved CR | 16.3.0 | +| 2020-07 | SP#88E | SP-200434 | 0129 | - | F | Clarification on PC5 PDB | 16.3.0 | +| 2020-07 | SP#88E | SP-200434 | 0130 | 1 | C | Clarification on mapping relationship between V2X Service and PFI for a PC5 unicast link | 16.3.0 | +| 2020-07 | SP#88E | SP-200434 | 0132 | - | F | Correction of the SIB number for V2X communication | 16.3.0 | +| 2020-07 | SP#88E | SP-200434 | 0134 | 1 | F | Clarification on QoS Sustainability Analytics and Alignment with TS 23.288 | 16.3.0 | +| 2020-07 | SP#88E | SP-200434 | 0135 | - | D | Editorial fix in 6.3.2 | 16.3.0 | +| 2020-07 | SP#88E | SP-200434 | 0137 | - | F | Addition of Keep Alive in the list of PC5-S messages | 16.3.0 | +| 2020-07 | SP#88E | SP-200434 | 0139 | 1 | F | General corrections | 16.3.0 | +| 2020-09 | SP#89E | SP-200682 | 0141 | - | F | Clarification on V2X Packet Filter Set | 16.4.0 | +| 2020-09 | SP#89E | SP-200682 | 0144 | 1 | F | Introducing new V2X service type | 16.4.0 | +| 2020-09 | SP#89E | SP-200682 | 0145 | 1 | F | Clarification of QoS info in accept message | 16.4.0 | +| 2020-09 | SP#89E | SP-200682 | 0146 | 1 | F | Clarification on SMF Configuration to UPF | 16.4.0 | +| 2020-09 | SP#89E | SP-200682 | 0147 | 1 | F | Clarification on QoS Sustainability | 16.4.0 | +| 2020-09 | SP#89E | SP-200682 | 0148 | 1 | F | Correction on PC5 RAT selection | 16.4.0 | +| 2020-09 | SP#89E | SP-200682 | 0149 | 1 | F | Correct the triggering conditions for the link identifier update procedure | 16.4.0 | +| 2020-09 | SP#89E | SP-200682 | 0150 | 1 | F | Update to Link Release Procedure | 16.4.0 | +| 2020-09 | SP#89E | SP-200682 | 0151 | 1 | F | Corrections to Link Identifier Update Procedure | 16.4.0 | +| 2020-12 | SP#90E | SP-200950 | 0152 | - | F | Cleanup about V2X service type | 16.5.0 | +| 2020-12 | SP#90E | SP-200950 | 0153 | - | F | Removal of Tx Profile for NR PC5 | 16.5.0 | +| 2021-12 | SP#94E | SP-211277 | 0171 | - | F | Correction to UE triggered Policy provisioning Procedure | 16.6.0 | +| 2022-06 | SP#96 | SP-220390 | 0180 | 1 | F | Removal of the UE Policy Provisioning Request indication for V2XP in the Registration Request | 16.7.0 | \ No newline at end of file diff --git a/marked/Rel-16/23_series/23527/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/marked/Rel-16/23_series/23527/1a827b10290f33d4fec04d0e8ef7a897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dc04257ad3234376bd9d3b3dbee87a8055c0d873 --- /dev/null +++ b/marked/Rel-16/23_series/23527/1a827b10290f33d4fec04d0e8ef7a897_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1cee9a5b45d34def676b104ba7c2eaed809e61110d8a83a97c6e156bc1d8d990 +size 46336 diff --git a/marked/Rel-16/23_series/23527/33a8f3f01dfa8bce75d23017855a13c5_img.jpg b/marked/Rel-16/23_series/23527/33a8f3f01dfa8bce75d23017855a13c5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c35fd0ec8744b3832dd8b2e6e14f938ef7461e8d --- /dev/null +++ b/marked/Rel-16/23_series/23527/33a8f3f01dfa8bce75d23017855a13c5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:83e6c061f9d3e494d1c734775a4ed0fee370b17551dc662d39b8637161071e4e +size 59116 diff --git a/marked/Rel-16/23_series/23527/410562339ce067fdc6fa41940c118658_img.jpg b/marked/Rel-16/23_series/23527/410562339ce067fdc6fa41940c118658_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8d6d2cea598921d57d32f77f1cc916dd32eb314f --- /dev/null +++ b/marked/Rel-16/23_series/23527/410562339ce067fdc6fa41940c118658_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9ba6d92a2b133b1884397765f47b1b6d14e71b17d8f2b1ed4b4362db8457098c +size 40709 diff --git a/marked/Rel-16/23_series/23527/54fabc351eda5228d2fa28cd9ba07971_img.jpg b/marked/Rel-16/23_series/23527/54fabc351eda5228d2fa28cd9ba07971_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dd475ca64016abfc4e66711f1a07619c75577e3b --- /dev/null +++ b/marked/Rel-16/23_series/23527/54fabc351eda5228d2fa28cd9ba07971_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0473353a590608433532aaae4fe274ace74c2f2f1dee6c15849c6071be5f7781 +size 86251 diff --git a/marked/Rel-16/23_series/23527/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-16/23_series/23527/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..35d9cefcd5a7ebda08c3bf6db749cfe4bd5158b2 --- /dev/null +++ b/marked/Rel-16/23_series/23527/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3df8e0cebe93ccffe4cd33a2d6f307ff245c2f6f2599ab45a651cc067ed58e8b +size 9510 diff --git a/marked/Rel-16/23_series/23527/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-16/23_series/23527/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..26fd53abef53f6006c18b37e7980ad7d9fc921af --- /dev/null +++ b/marked/Rel-16/23_series/23527/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6c809a272a0875e9ab4896d0496e46dd775d4ff800da817a9e1c51203f5d3c05 +size 5792 diff --git a/marked/Rel-16/23_series/23527/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/marked/Rel-16/23_series/23527/7efae06af3af43ffe5d4b956a679cf54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6464bc969b3be7cb906e2cee6830b79e54f089ab --- /dev/null +++ b/marked/Rel-16/23_series/23527/7efae06af3af43ffe5d4b956a679cf54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:67438e391d6346c140d5d0d10b73eea3e77d11efcf6ae414b062f1c111286369 +size 46518 diff --git a/marked/Rel-16/23_series/23527/8fa679f79a1bb1f527cba9f29e784e89_img.jpg b/marked/Rel-16/23_series/23527/8fa679f79a1bb1f527cba9f29e784e89_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..df39e79f170c342c8b6a0f6f151e06b7449c62e1 --- /dev/null +++ b/marked/Rel-16/23_series/23527/8fa679f79a1bb1f527cba9f29e784e89_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:27437533ceab987a9b892ef67e98c077a9368866ff4a77a76b4543676b380648 +size 73210 diff --git a/marked/Rel-16/23_series/23527/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/Rel-16/23_series/23527/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ab003e962fee01e563cb58b75400fd2f7e60af2f --- /dev/null +++ b/marked/Rel-16/23_series/23527/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:93a3d6c91fb6e8cfe195ffd7bbe04b7a5b2f753dca4ecaa53edf33ea9aa84017 +size 41122 diff --git a/marked/Rel-16/23_series/23527/raw.md b/marked/Rel-16/23_series/23527/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..a1d23511a68d6810810c9d7dd8e32dcaee4c5893 --- /dev/null +++ b/marked/Rel-16/23_series/23527/raw.md @@ -0,0 +1,876 @@ + + +# 3GPP TS 23.527 V16.7.0 (2022-06) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 5G System; Restoration Procedures (Release 16)** + + + +The 5G logo, consisting of the text "5G" in a bold, black, sans-serif font. Above the "5G" text are three green curved lines representing signal waves. + +5G logo + + + +The 3GPP logo, featuring the letters "3GPP" in a stylized, bold, black font. Below the "3GPP" text is a red signal icon consisting of three curved lines. Below the icon, 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 + +--- + +
Implementation of C4-185409, C4-185410, C4-185411, C4-185412, C4-185413, C4-185414, C4-185527 | | 0.1.0 | +| 2018-08 | CT4#86 | C4-186509 | | | | Implementation of C4-186233, C4-186406, C4-186408, C4-186413, C4-186488 | | 0.2.0 | +| 2018-09 | CT#81 | CP-182082 | | | | Presented for Information and approval | | 1.0.0 | +| 2018-09 | CT#81 | | | | | Approved in CT#81 | | 15.0.0 | +| 2018-12 | CT#82 | CP-183021 | 0003 | - | F | GTP-U Error Indication received from 5G-AN | | 15.1.0 | +| 2018-12 | CT#82 | CP-183021 | 0004 | 4 | F | NF service restart detection by direct signalling between NFs | | 15.1.0 | +| 2018-12 | CT#82 | CP-183021 | 0006 | 1 | F | Restoration Procedure for Intermediate UPF Restart | | 15.1.0 | +| 2018-12 | CT#82 | CP-183021 | 0007 | 1 | F | Restart detection by direct signalling between NFs | | 15.1.0 | +| 2018-12 | CT#82 | CP-183021 | 0008 | | F | PWS restoration procedures | | 15.1.0 | +| 2018-12 | CT#82 | CP-183021 | 0009 | 1 | F | NF Service Instance Reselection | | 15.1.0 | +| 2019-03 | CT#83 | CP-190026 | 0010 | - | F | NF Restart detection | | 15.2.0 | +| 2019-06 | CT#84 | CP-191038 | 0011 | 1 | F | Corrections to Restoration procedures | | 15.3.0 | +| 2019-06 | CT#84 | CP-191044 | 0012 | 2 | F | Clarifications on UPF restoration procedure | | 16.0.0 | +| 2019-06 | CT#84 | CP-191044 | 0013 | 1 | F | Clarifications on GTP-U Error Indication received by 5G-AN | | 16.0.0 | +| 2019-09 | CT#85 | CP-192124 | 0014 | - | F | Regulation of contexts restoration by NFs | | 16.1.0 | +| 2019-12 | CT#86 | CP-193045 | 0017 | 1 | F | PFCP Association Setup Request with same Node ID | | 16.2.0 | +| 2019-12 | CT#86 | CP-193045 | 0018 | 2 | F | Reestablishment of PFCP sessions after a UP function restart | | 16.2.0 | +| 2020-06 | CT#88e | CP-201030 | 0019 | 2 | B | Populating Recovery Information via Direct signalling from a Service Producer | | 16.3.0 | +| 2020-06 | CT#88e | CP-201030 | 0021 | 2 | B | Populating Recovery Information of NF (Service) Set via NRF | | 16.3.0 | +| 2020-06 | CT#88e | CP-201030 | 0020 | 2 | B | Populating Recovery Information via Direct signalling from a Service Consumer | | 16.3.0 | +| 2020-06 | CT#88e | CP-201030 | 0023 | - | F | NF Service Instance Reselection | | 16.3.0 | +| 2020-09 | CT#89e | CP-202119 | 0024 | 1 | F | Reselection when the Routing Binding Indication unavailable | | 16.4.0 | +| 2020-12 | CT90e | CP-203054 | 0025 | 1 | F | NF reselection by the SCP without Routing Binding Indication | | 16.5.0 | +| 2021-06 | CT#92e | CP-211059 | 0032 | 1 | F | Clarifications to NF service producer reselection procedure (w/o binding support) | | 16.6.0 | +| 2022-06 | CT#96 | CP-221061 | 0057 | 1 | F | Restoration procedures for Home Routed PDU Sessions or PDU sessions with an I-SMF | | 16.7.0 | \ No newline at end of file diff --git a/marked/Rel-16/23_series/23715/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/marked/Rel-16/23_series/23715/1a827b10290f33d4fec04d0e8ef7a897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a982a897336c5268128701af0317a2e611c30377 --- /dev/null +++ b/marked/Rel-16/23_series/23715/1a827b10290f33d4fec04d0e8ef7a897_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:38d6bf4b0d8cba588317d90e98cc720949a81f124ccdeb2bcfe09e6a528dadf7 +size 277568 diff --git a/marked/Rel-16/23_series/23715/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg b/marked/Rel-16/23_series/23715/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..33ab911d53aed368581d84ce6b6a421111603811 --- /dev/null +++ b/marked/Rel-16/23_series/23715/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:56ebb932a5ce5dd74c0489c91266029b52b5e590a84c5ea00d9cbb9a825de492 +size 52964 diff --git a/marked/Rel-16/23_series/23715/7d3d5fb5d09c0cd35a9d637be241651e_img.jpg b/marked/Rel-16/23_series/23715/7d3d5fb5d09c0cd35a9d637be241651e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..439cebcacb6310c4473aab5a982259301c228901 --- /dev/null +++ b/marked/Rel-16/23_series/23715/7d3d5fb5d09c0cd35a9d637be241651e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1623460202264f07b7b4506b99485fe823462e68ce4ef16eab7f5a85db666f0a +size 89775 diff --git a/marked/Rel-16/23_series/23715/8e14350b4b669119a3bdfca7869110ca_img.jpg b/marked/Rel-16/23_series/23715/8e14350b4b669119a3bdfca7869110ca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..95264f281b69bca24e86cfb4af64524e035b0604 --- /dev/null +++ b/marked/Rel-16/23_series/23715/8e14350b4b669119a3bdfca7869110ca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1482ff0841a89b45f5c1eaa5d812f8d418ef56553acf272ece331e305f0a901d +size 47938 diff --git a/marked/Rel-16/23_series/23715/90ddb84c323b956e2d50a54d3f870566_img.jpg b/marked/Rel-16/23_series/23715/90ddb84c323b956e2d50a54d3f870566_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9bc5acbc09026f2de030cb822b7222cb071d138b --- /dev/null +++ b/marked/Rel-16/23_series/23715/90ddb84c323b956e2d50a54d3f870566_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4ec714edf19b30120d8ce56edbf4172ca83e751ec9d5fdc3ab7d9acb50f7b542 +size 59328 diff --git a/marked/Rel-16/23_series/23715/a7585024ebe2bba8ac0757150a12759a_img.jpg b/marked/Rel-16/23_series/23715/a7585024ebe2bba8ac0757150a12759a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e93c2033765f24b3b03fdcf9cf72461aaca48133 --- /dev/null +++ b/marked/Rel-16/23_series/23715/a7585024ebe2bba8ac0757150a12759a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aea7a09e0a1651ff3a541ba836d550b74c1eb9cca2d159371e8877bab1d4b342 +size 33032 diff --git a/marked/Rel-16/23_series/23715/bdfe4e1058d1a0e14bb838771b57254c_img.jpg b/marked/Rel-16/23_series/23715/bdfe4e1058d1a0e14bb838771b57254c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..21481a04440a9ef684a791c79e27ac91bbdee083 --- /dev/null +++ b/marked/Rel-16/23_series/23715/bdfe4e1058d1a0e14bb838771b57254c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4c65e09dc0067ade3ed5c472f9a690676965303cad1f32687a048ffdc7379cd9 +size 56397 diff --git a/marked/Rel-16/23_series/23715/e636d7ccca0ad14c6b95201404324823_img.jpg b/marked/Rel-16/23_series/23715/e636d7ccca0ad14c6b95201404324823_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c50d8bc03249d567e4689d62f349ef14dd5a7e23 --- /dev/null +++ b/marked/Rel-16/23_series/23715/e636d7ccca0ad14c6b95201404324823_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a42e4bbe05df89e8e27a9a66164ca0acaf310392f448355c9d19c87ed7399b58 +size 37778 diff --git a/marked/Rel-16/23_series/23715/raw.md b/marked/Rel-16/23_series/23715/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..8771c1896fe12a5a87515fbebe97c126f2d22168 --- /dev/null +++ b/marked/Rel-16/23_series/23715/raw.md @@ -0,0 +1,1200 @@ + + +# **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on system enhancements for provision of access to restricted local operator services by an unauthenticated User Equipment (UE) (Release 16)** --- + +## --- **Keywords** + +--- + +3GPP, access, authentication, enhancements, +services + +## **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** + +--- + +
Network indicating support for Restricted Local Operator Services and related UE behaviour | Description | Advantages | Drawbacks | +|-----------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------| +| Solution #1 | 1) A new SIB provided by E-UTRAN indicates that the PLMN is configured to supports Restricted Local Operator Services.
2) The PLMNs where RLOS is supported may be stored in UICC (or ME).
3) Whether automatic PLMN selection needs to be supported for RLOS will be confirmed by CT WG1. | 1) It is the only way to prevent UEs to even send a message.
2) In line with SA WG1. | None | +| Solution #9 | 1) New SIB: same as solution #1
2) PLMN selection by user or configured in ME. | 1) Same. | 1) None for new SIB.
2) PLMN selection configured in ME would require more specification work. | + +Table 8-2 + +| Key Issue #EPC-2: RLOS request indication | Description | Advantages | Drawbacks | +|-------------------------------------------|----------------------------------------|-----------------------------------|--------------| +| Solution #2 | RLOS indication in Attach (UE-CN). | For entering RLOS EPC procedures. | None. | +| Solution #4 | RLOS indication in Attach (UE-CN). | For entering RLOS EPC procedures. | None. | +| Solution #9 | RLOS RRC establishment cause (UE-RAN). | For admission control in RAN. | RAN impacts. | + +Table 8-3 + +| Key Issue #EPC-3:
Support of
unauthenticated UEs
access to RLOS
(congestion issue) | Description | Advantages | Drawbacks | +|------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------| +| Solution #1 | An operator may decide to unset the SIB indicator e.g. using OAM to prevent access attempts from UEs for RLOS e.g. in case of network congestion. | No impacts to the specs. | 1) RLOS for all UEs or no UEs.
2) Slow mechanism.
3) Cannot be extended to CN congestion situations. | +| Solution #9 | The E-UTRAN may reject the RRC connection establishment with extended wait timer for RLOS attempts. | 1) Per UE mechanism.
2) Fast and proportional to the level of congestion.
3) Can also apply before congestion.
4) Can be extended to CN overload by adding S1 overload message. | RAN impacts | + +Table 8-4 + +| Key Issue #EPC-3:
Support of
unauthenticated UEs
access to RLOS (EPC
access issue) | Description | Advantages | Drawbacks | +|------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------| +| Solution #6 |
Partial solution:
Enabling VoLTE calls after initial attachment:
- - First option: the RLOS APN can lead to a portal that guides the user to various services. Alternatively, if the UE attached to RLOS APN can be IMS authenticated, the UE can use IMS APN to re-(register) in IMS.
- - In the second option, the RLOS APN may lead directly to the IMS network to initiate the requested RLOS VoLTE service.
- - SIP signalling may not acquire the QCI 5 that would typically be associated with an APN dedicated for IMS.
Not a full solution.
Apart from non-roamers UEs in limited service state, UEs cannot be authenticated. So, text is incorrect.
| +| Solution #2 | RLOS attach with RLOS indication, no authentication, configured APN for RLOS, P-CSCF address in PCO, PGW shall block any traffic that is not from or to addresses of network entities (e.g. P-CSCF, captive portal), UE and Network shall implicitly detach without NAS signalling transactions. | Basic solution. | Some aspects are missing. | +| Solution #4 | Same as solution #2 plus charging, location services, mobility aspects. Difference is that authentication is performed for non-roaming UEs in limited service state in order to use credentials (see key issue EPC-4). | Charging aspects, ARP aspects, PCC deployments considerations. | None. | + +Table 8-5 + +| Key Issue #EPC-4:Support of authenticated
UEs access to RLOS | Description | Advantages | Drawbacks | +|---------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------|--------------------------------------------------------------------| +| Solution #2 | UE requesting RLOS is authenticated but in limited state: MME skips the authentication. | Simple; authentication is always skipped when RLOS indication is present. | No integrity protection nor ciphering for control and user planes. | +| Solution #4 | UE requesting RLOS is authenticated and non-roamer but in limited state: MME performs the authentication to get credentials. | It allows to integrity protect and cipher control and user planes. | More complex than solution #2. | + +Table 8-6 + +| Key Issue #EPC-6:
Collection of charging
information | Description | Advantages | Drawbacks | +|------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------|-----------| +| Solution #4 | Charging of RLOS PDN connections can be performed by OFCS and OCS as for regular PDN connections. The rating group provided by PCRF should just be a RLOS specific rating group. | No changes. Only configuration for RLOS. | None. | + +Table 8-7 + +| Key Issue #EPC-7: Level
of security | Description | Advantages | Drawbacks | +|----------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Solution #2 | Mimics emergency calls for unauthenticated UEs per 23.617 annex K.3.
Treats all RLOS requests as for unauthenticated UEs. | The solution supports the requirement "Level of security should not be less than that which is currently applied to existing equivalent network access methods (e.g., unauthenticated emergency calling)". | Does not protect customer from false base station attacks. | +| Solution #4 | Mimics emergency calls for unauthenticated UEs per 23.617 annex K.3.
In addition, for UEs in limited service state for which subscribers belong to the local PLMN, integrity protection is ensured for signalling and ciphering is possible for control and user plane. | The solution supports the requirement "Level of security should not be less than that which is currently applied to existing equivalent network access methods (e.g., unauthenticated emergency calling)".
For UEs of the local PLMN (but which are in limited service state) it allows to integrity protect control plane and cipher the control and user planes. | Does not protect customer from false base station attacks. | +| Solution #11 | In order to reduce the fraud risks associated with RLOS, the UE shall not offer RLOS services to the user unless the serving cell has a Mobile Country Code from the set {310, ..., 316}. | Simple additional mechanism only impacting the ME to protect customer from false base station attacks. | List needs to be extended if other countries require to use RLOS. UEs need to be updated (e.g. via over the air updates).
Does not protect against fraud risks when MCC = {310, ..., 316}
It relies on the UE to locate itself at "country level" that can only rely on implementation dependant methods. | + +Table 8-8 + +| Key Issues #IMS-1:
Support for unauthenticated and authenticated user
#IMS-2: Identification of Restricted Local Operator Services at IMS layer
#IMS-3: Handling IMS session for Restricted Local Operator Services | Description | Advantages | Drawbacks | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Solution #3 | RLOS indication in SIP REGISTER. In line with S8HR emergency calls specified in TS 23.167 [8] clause K.3. No authentication at IMS layer since TS 23.167 [8] clause K.3 is for unauthenticated UEs. | Minimal changes if TS 23.167 [8] clause K.3 is reused as is. | No integrity protection nor ciphering for non-roaming UEs in limited service state. | +| Solution #5 | Same as solution #3 but where the non-roaming UEs in limited service state are authenticated only to retrieve credentials. | It allows to integrity protect and cipher control and user planes. | More complex than solution #3 | +| Solution #7 | In the first scenario (unauthenticated UEs), RLOS UEs are allowed to make VoLTE calls even if their IMS registration cannot be successful.
In the second scenario (authenticated UEs), RLOS UEs are registered in IMS with identities specially assigned for RLOS that allow them to make VoLTE calls. | To capture: based on operator policy, be configured with a limited set of destinations. | No clear description. Looks like solution #5 but does not state whether TS 23.167 [8] is reused or if it rely on new procedures (which would have more impacts). | +| Solution #10 | Skipping IMS registration as for emergency calls. | | Not in line with S8HR emergency calls specified in TS 23.167 [8], clause K.3. | + +Table 8-9 + +| Key issue #IMS-4:
Support of emergency services by UEs attached for RLOS | Description | Advantages | Drawbacks | +|-------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------| +| Solution #3 | Not described. | | | +| Solution #5 | UE does not detach to initiate an emergency call: the P-CSCF will route the emergency call to E-CSCF. | No need to detach from RLOS APN to obtain emergency call. Minimal changes to P-CSCF. | None. | +| Solution #8 | The UE may detach from RLOS and then do emergency Attach, or the UE may decide to stay RLOS attached and to establish an emergency PDN connectivity towards the emergency APN. | | Not clear which procedure is intended. Complexity / more impacts if we have to implement both. | + +# 9 Conclusions + +For Key Issue EPC-1 (Network indicating support for Restricted Local Operator Services and related UE behaviour), it is agreed that: + +- A new SIB provided by E-UTRAN indicates that the PLMN is configured to supports Restricted Local Operator Services. +- The PLMNs where RLOS is supported may be stored in UICC (or ME). +- In automatic PLMN selection, if registration cannot be achieved on any PLMN and at least one PLMN offering restricted local operator services has been found, the UE shall behave as stated in TS 22.011 [10] clause 3.2.2.2. + +For Key Issue EPC-2 (RLOS request indication), it is agreed that: + +- The UE shall indicate in the Attach Request that the attachment is for RLOS. +- During the RRC connection establishment procedure, the UE indicates in the RRC signalling that the RRC connection is for RLOS access, using RLOS RRC establishment cause, per solution #9. + +For Key Issues EPC-3 (Support of unauthenticated UEs access to RLOS) and EPC-4 (Support of authenticated UEs access to RLOS), it is agreed that: + +- For congestion issue, solution #9 is adopted. +- For EPC access issue, solution #4 is adopted with the following clarifications: + - Authentication for EPC access for roaming UEs in limited state may be performed based on local operator policy; + - MME initiated detach based on RRC release or implicit detach timer is excluded; + - Handling related to End of RLOS session is excluded (as "End of RLOS session" is not defined); + - The following PGW function proposed in solution #2 is adopted: duration of PDN connection for RLOS is controlled through local policies in PGW; +- For configuring access to IMS after initial attachment to EPC, solution #6 is adopted. + +For Key Issue EPC-6 (collection of charging information), it is agreed that: + +- Solution #4 is adopted. + +For Key Issues IMS-1 (Support for unauthenticated and authenticated user), IMS-2 (Identification of Restricted Local Operator Services at IMS layer) and IMS-3 (Handling IMS session for Restricted Local Operator Service), it is agreed that: + +- For UEs unauthenticated at IMS layer (manual roamers) and for UEs whose IMSI belongs to the local operator, the solution 7 is adopted, complemented with the solution 5 optional capabilities for security checks (to be tuned during normative phase), with the following clarification: + - Whether the P-CSCF may be configured to consider UEs whose IMSI belongs to the local operator as unauthenticated UEs will be decided by SA WG3. + +For Key Issue IMS-4 (Support of emergency services by UEs attached for RLOS), it is agreed that: + +- Solution in clause 7.8.2.1 "UE performs detach from RLOS and then do emergency Attach" is adopted to support emergency service for a RLOS attached UE. + +For key issue EPC-7: + +- In order to avoid MitM attacks, TLS can be used for any server that provides PaRLOS service e.g. using HTTPS or SIPS. How the Server authentication is performed e.g. using the server certificates and authorized trust anchor root CA certificates, procedures for validation of the server certificate, etc. will be studied in SA WG3. +- For operators that do not require support for PaRLOS they can indicate that in their terminal requirements so that PaRLOS can be by default "disabled" and enabled only after user's consent. + +Overall security impacts will be further studied and concluded by SA WG3/TSG SA. + +# --- Annex : Change history + +| Change history | | | | | | | | +|----------------|---------|-----------|----|-----|-----|-------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2018-09 | SP#81 | SP-180742 | - | - | - | MCC editorial update for presentation to TSG SA#81 for approval | 1.0.0 | +| 2018-09 | SP#81 | SP-180742 | - | - | - | MCC editorial update for publication after TSG SA#81 approval
(correction to title to add User Equipment (UE)) | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/23_series/23724/036ceaf207a7b289ca76e160892eb724_img.jpg b/marked/Rel-16/23_series/23724/036ceaf207a7b289ca76e160892eb724_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b717debebfd36f24d61a5fab7c1b07eb5116f50e --- /dev/null +++ b/marked/Rel-16/23_series/23724/036ceaf207a7b289ca76e160892eb724_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:03b76ebeb2a0ed075fd434abae3ac0b39ff971cd553bf8a019f6fc609fdf2056 +size 33614 diff --git a/marked/Rel-16/23_series/23724/03d9aaba6c1af8bfd8e42c1d2422ae5c_img.jpg b/marked/Rel-16/23_series/23724/03d9aaba6c1af8bfd8e42c1d2422ae5c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2add9d3a5ca5cc36facde1804aa7fe4cf2a3002a --- /dev/null +++ b/marked/Rel-16/23_series/23724/03d9aaba6c1af8bfd8e42c1d2422ae5c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:04a5adc3c4381296a279bd1824b4e61770d52894f12287e8b35aa793ec2bf595 +size 62898 diff --git a/marked/Rel-16/23_series/23724/03eae103d1ac14e9b07ed21a3c091d48_img.jpg b/marked/Rel-16/23_series/23724/03eae103d1ac14e9b07ed21a3c091d48_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..437e5f7179e49e002267ee287a78a48574e1edb3 --- /dev/null +++ b/marked/Rel-16/23_series/23724/03eae103d1ac14e9b07ed21a3c091d48_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:48ec1ae0154a78c875d4a7c8f3eae22b841805cdf155e5897d5a9e36cdce4cdd +size 82109 diff --git a/marked/Rel-16/23_series/23724/0856d34939157228ac3a54a59882fb10_img.jpg b/marked/Rel-16/23_series/23724/0856d34939157228ac3a54a59882fb10_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..375eb8fad0f94317c2addf30e77b618013b2d1d3 --- /dev/null +++ b/marked/Rel-16/23_series/23724/0856d34939157228ac3a54a59882fb10_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ffcd3b53b78774334b967c9a8d55137c50ba90b566aa4650a5a5eda9b8ee2c3b +size 89245 diff --git a/marked/Rel-16/23_series/23724/0a3ab80d35c138cc4038b5758f6ff34d_img.jpg b/marked/Rel-16/23_series/23724/0a3ab80d35c138cc4038b5758f6ff34d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..93c5fe22bccab9f5d51d71d45498fe31aabd42e3 --- /dev/null +++ b/marked/Rel-16/23_series/23724/0a3ab80d35c138cc4038b5758f6ff34d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4d4387f49e16c5868cf13248aba3978ff893a9f907a9cf466302eb3bd1c7ba54 +size 95808 diff --git a/marked/Rel-16/23_series/23724/0a73b03fba21af142d619a9a662e6490_img.jpg b/marked/Rel-16/23_series/23724/0a73b03fba21af142d619a9a662e6490_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..be745dcfb1df47e3fa839afeaed8d0de08941d96 --- /dev/null +++ b/marked/Rel-16/23_series/23724/0a73b03fba21af142d619a9a662e6490_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fc24738d4de7dcd36a03081bf9fe1bf77a7e44355937171832eae6f6cc2f009f +size 12431 diff --git a/marked/Rel-16/23_series/23724/0adcd19063a66145a465add40bf956e6_img.jpg b/marked/Rel-16/23_series/23724/0adcd19063a66145a465add40bf956e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..69ee2d9bde8f8170ec63a4bc015ce6b6501a1eb7 --- /dev/null +++ b/marked/Rel-16/23_series/23724/0adcd19063a66145a465add40bf956e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e8438a7900666ec306c8fdeb006d87293632807e2acb2e758562413ac2df6ef2 +size 79112 diff --git a/marked/Rel-16/23_series/23724/0c80c383f76034e117adf5e5eaadaaf3_img.jpg b/marked/Rel-16/23_series/23724/0c80c383f76034e117adf5e5eaadaaf3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f932381ebb77b28a58b1565436e7724e616cb106 --- /dev/null +++ b/marked/Rel-16/23_series/23724/0c80c383f76034e117adf5e5eaadaaf3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a20875a4711eef9eea687a3823b8675c553b9fc7627bbe6ae22b252e4badfe77 +size 27827 diff --git a/marked/Rel-16/23_series/23724/0de91e9b714369b312bf3ab1853301ac_img.jpg b/marked/Rel-16/23_series/23724/0de91e9b714369b312bf3ab1853301ac_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..22b504eaccec91932052f0ebc3164ecdce77456d --- /dev/null +++ b/marked/Rel-16/23_series/23724/0de91e9b714369b312bf3ab1853301ac_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9064e9c337ba13e16c82ea925eb12f7339b13c11fe1b51b3b73e98cdeb27bed9 +size 47586 diff --git a/marked/Rel-16/23_series/23724/0dfdff10c725fe9c332b07ade9d23a5e_img.jpg b/marked/Rel-16/23_series/23724/0dfdff10c725fe9c332b07ade9d23a5e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6c44001e5a57a6ec350d144185610c9b329e1a67 --- /dev/null +++ b/marked/Rel-16/23_series/23724/0dfdff10c725fe9c332b07ade9d23a5e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c1286eeb96509bccb3ed1b037000bc77720664eb32106b0c4c2dc0c512d10b29 +size 67790 diff --git a/marked/Rel-16/23_series/23724/0f1767577a073167eb9628d72034e083_img.jpg b/marked/Rel-16/23_series/23724/0f1767577a073167eb9628d72034e083_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..90f850b3ea67d23328ffdddde4e3719ef92246ff --- /dev/null +++ b/marked/Rel-16/23_series/23724/0f1767577a073167eb9628d72034e083_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3d5a357700a0e488e73c7286e05340ad3cbbd1fd883f62dfed1f24ea760c8e44 +size 31253 diff --git a/marked/Rel-16/23_series/23724/0f26e70157bd4c45f825795cdcd20fbd_img.jpg b/marked/Rel-16/23_series/23724/0f26e70157bd4c45f825795cdcd20fbd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b826864bd6fccaa63e5e4ae28e43eaa9ffefd5ce --- /dev/null +++ b/marked/Rel-16/23_series/23724/0f26e70157bd4c45f825795cdcd20fbd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b64a4b38d1969d2f602cc1364972f78d2c51dd3eb1ab35ecb2bdf599b22c7dc5 +size 73611 diff --git a/marked/Rel-16/23_series/23724/0f7871077bba48a2c97f7859a5edda0d_img.jpg b/marked/Rel-16/23_series/23724/0f7871077bba48a2c97f7859a5edda0d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f1286e6a013430615e17de1bd8fa0f646fcfa860 --- /dev/null +++ b/marked/Rel-16/23_series/23724/0f7871077bba48a2c97f7859a5edda0d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9d4a04be14dafa499904d2b52f76734c55e92d3eb802e7bab6f31cbaf67c208c +size 119421 diff --git a/marked/Rel-16/23_series/23724/1033dc9fde75540d224c907681b1b7aa_img.jpg b/marked/Rel-16/23_series/23724/1033dc9fde75540d224c907681b1b7aa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9a8c1fd4e5e28f6b2a0477d5b6ba06ddba9cdff1 --- /dev/null +++ b/marked/Rel-16/23_series/23724/1033dc9fde75540d224c907681b1b7aa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8aeaaa5ef140262dee4537721ef10d5be3c896606122162f43e5370582823d87 +size 60197 diff --git a/marked/Rel-16/23_series/23724/107cbeda15ddd53da92c2f677b441c93_img.jpg b/marked/Rel-16/23_series/23724/107cbeda15ddd53da92c2f677b441c93_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..04effac10a019fd8f335128695022a03a31e6743 --- /dev/null +++ b/marked/Rel-16/23_series/23724/107cbeda15ddd53da92c2f677b441c93_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b26f143369f81f729de68d84e59aa197c72fa1fa518fc7f7e917b7be8943ae0b +size 39665 diff --git a/marked/Rel-16/23_series/23724/11f18bf0233d812ad2604f88f3385d60_img.jpg b/marked/Rel-16/23_series/23724/11f18bf0233d812ad2604f88f3385d60_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fd1c1ebf2f9724b07aeab173141b8ba4cfa69b05 --- /dev/null +++ b/marked/Rel-16/23_series/23724/11f18bf0233d812ad2604f88f3385d60_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:20d58236c9fd8c92c84b648439c841d3f7f870071fc40e221fde9fd6c03fa73b +size 107289 diff --git a/marked/Rel-16/23_series/23724/13fde41de77bf026013a0b81684d1fc9_img.jpg b/marked/Rel-16/23_series/23724/13fde41de77bf026013a0b81684d1fc9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ff5f333a04ca61f47694ae9c5420b091beeb20dc --- /dev/null +++ b/marked/Rel-16/23_series/23724/13fde41de77bf026013a0b81684d1fc9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:34a19a75132a92ea0bf97cdeb002fe76c13cc9209dd2201308956f7c231b7baa +size 144705 diff --git a/marked/Rel-16/23_series/23724/164d1b48231be457522b31965610ea3b_img.jpg b/marked/Rel-16/23_series/23724/164d1b48231be457522b31965610ea3b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fe63510a49905ed7f749fb45b3219263247aadca --- /dev/null +++ b/marked/Rel-16/23_series/23724/164d1b48231be457522b31965610ea3b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b810cc1f65709397bee20e472ca9ecb93839dbe9469cffb2214ee0841895a771 +size 94091 diff --git a/marked/Rel-16/23_series/23724/17431d8b59408f09df7552d8bdbaa015_img.jpg b/marked/Rel-16/23_series/23724/17431d8b59408f09df7552d8bdbaa015_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3b9166789f7f9a0ac774f26cb4ec21d31a828580 --- /dev/null +++ b/marked/Rel-16/23_series/23724/17431d8b59408f09df7552d8bdbaa015_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:67c72730f7369542ee847a86aae55a4b05ff8ca994c94794d583bc5c63ce71ae +size 49113 diff --git a/marked/Rel-16/23_series/23724/187d05bf7ead21e1394b61320d8b3632_img.jpg b/marked/Rel-16/23_series/23724/187d05bf7ead21e1394b61320d8b3632_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bddadf3158daf6213c990ed38a9dc9fad562e070 --- /dev/null +++ b/marked/Rel-16/23_series/23724/187d05bf7ead21e1394b61320d8b3632_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3001b98fb997e8c479ad2c0789d4737a9207b36e84136aa266ece49bb2746467 +size 30560 diff --git a/marked/Rel-16/23_series/23724/1a1484a99fee36bd3ca4e40fe1538bf8_img.jpg b/marked/Rel-16/23_series/23724/1a1484a99fee36bd3ca4e40fe1538bf8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..74524cd74a3f78546b5f7d5e93f5e9ef880cfb0c --- /dev/null +++ b/marked/Rel-16/23_series/23724/1a1484a99fee36bd3ca4e40fe1538bf8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f4c818362a5bf5af43469b9bc31e139e41f301c8ee4ef079a5d17b61330de1e7 +size 37209 diff --git a/marked/Rel-16/23_series/23724/1bc1746388cb64bf23b356ce2365dfc2_img.jpg b/marked/Rel-16/23_series/23724/1bc1746388cb64bf23b356ce2365dfc2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8031c4cb353d129c9798523319167e99e6be865e --- /dev/null +++ b/marked/Rel-16/23_series/23724/1bc1746388cb64bf23b356ce2365dfc2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:402f8e84586358f220620a2abc3a9896d9e0fb41f26646dffb0b5076a8a778f2 +size 27514 diff --git a/marked/Rel-16/23_series/23724/1e8c50ad4fca7f315a407347dd5091cc_img.jpg b/marked/Rel-16/23_series/23724/1e8c50ad4fca7f315a407347dd5091cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..42317632d0a1ac81818cc51d516a91f4b9522c33 --- /dev/null +++ b/marked/Rel-16/23_series/23724/1e8c50ad4fca7f315a407347dd5091cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dd98226541379723fdcafcbf60412a952c4b59be461ad9b5e33f9170b997c14b +size 75520 diff --git a/marked/Rel-16/23_series/23724/1eadbbe42cfcac5c0023577110aec5e3_img.jpg b/marked/Rel-16/23_series/23724/1eadbbe42cfcac5c0023577110aec5e3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eb95190fa43628df8390ce645354839911c90fb2 --- /dev/null +++ b/marked/Rel-16/23_series/23724/1eadbbe42cfcac5c0023577110aec5e3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:18fa9d073af40dc2e0ed9c2105f7d7d416f43fd74ff0d46d8e625facdf974151 +size 37356 diff --git a/marked/Rel-16/23_series/23724/2226ff0a3945d72d56b5150c5618e71c_img.jpg b/marked/Rel-16/23_series/23724/2226ff0a3945d72d56b5150c5618e71c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a6f6d5b368308207e4d05bc584c77b757bc44d16 --- /dev/null +++ b/marked/Rel-16/23_series/23724/2226ff0a3945d72d56b5150c5618e71c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:90186d9d4a99e23a2d41acfde93c70d464b67ac61f96e68a9e7080293568032d +size 76628 diff --git a/marked/Rel-16/23_series/23724/223c6f5bda05ffdd254a828a148b53f1_img.jpg b/marked/Rel-16/23_series/23724/223c6f5bda05ffdd254a828a148b53f1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..155808471217abd6504e5cab8f6827760170e522 --- /dev/null +++ b/marked/Rel-16/23_series/23724/223c6f5bda05ffdd254a828a148b53f1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:527d3356f096b53959c2290814845f21982216b440e6db3d68e36af1623b7c78 +size 25026 diff --git a/marked/Rel-16/23_series/23724/24ee23a8f3995ecfd3aae31a37a1d40c_img.jpg b/marked/Rel-16/23_series/23724/24ee23a8f3995ecfd3aae31a37a1d40c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a7969f67658457350218bad57200b43ae551512c --- /dev/null +++ b/marked/Rel-16/23_series/23724/24ee23a8f3995ecfd3aae31a37a1d40c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0dacfb442455d520f613d0007c104645269a4f062548db4212238b76c569ad83 +size 40180 diff --git a/marked/Rel-16/23_series/23724/26d0c0482ad7f4f026a58ecc0b468980_img.jpg b/marked/Rel-16/23_series/23724/26d0c0482ad7f4f026a58ecc0b468980_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e93797e8a2957a3db6b0dd1afea7b72c47a6ea1e --- /dev/null +++ b/marked/Rel-16/23_series/23724/26d0c0482ad7f4f026a58ecc0b468980_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:91c12fb09c27488dc5fcc346f9fb2edddfeefe01c39ba4edcf935706f04f9ecb +size 39988 diff --git a/marked/Rel-16/23_series/23724/26d664119ad25250780f554633444e54_img.jpg b/marked/Rel-16/23_series/23724/26d664119ad25250780f554633444e54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..064c67663787d2fc542226c1b7aae1b0cd28f92c --- /dev/null +++ b/marked/Rel-16/23_series/23724/26d664119ad25250780f554633444e54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:63d8e2d5e5e0591f394e26c958b425c66b4464bb46cf2baa1040991f82d3f59a +size 71131 diff --git a/marked/Rel-16/23_series/23724/2837ffdadcdb1e5bababa56b564e56ed_img.jpg b/marked/Rel-16/23_series/23724/2837ffdadcdb1e5bababa56b564e56ed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..347ea4a7fd7f325a6720965ddbe6ab36ebee2a83 --- /dev/null +++ b/marked/Rel-16/23_series/23724/2837ffdadcdb1e5bababa56b564e56ed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4f4ce66588b3d8961f52d2795e16b809d361e2bc797be2710e7749b4cab01187 +size 173017 diff --git a/marked/Rel-16/23_series/23724/2957154f4dc666a6cafb7b4d2d882910_img.jpg b/marked/Rel-16/23_series/23724/2957154f4dc666a6cafb7b4d2d882910_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..797d890d21af583ee2792ab4d1a0a671b54bf8b3 --- /dev/null +++ b/marked/Rel-16/23_series/23724/2957154f4dc666a6cafb7b4d2d882910_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:47595773faab3950cd01066a7338fef159261866bc620f555f4779fef1e65588 +size 49224 diff --git a/marked/Rel-16/23_series/23724/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg b/marked/Rel-16/23_series/23724/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a0a5167fb021bb7191380e112bfdbccf0432211a --- /dev/null +++ b/marked/Rel-16/23_series/23724/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:59335aa5f6b5b76f013c313c7b3de0a0a5778255131d84cc70b40503465e6b4c +size 65586 diff --git a/marked/Rel-16/23_series/23724/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg b/marked/Rel-16/23_series/23724/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6675871940d544628113999139028c429a201055 --- /dev/null +++ b/marked/Rel-16/23_series/23724/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:771b8320036b0ac8143d487f28de86755b59b03530b1b625a603649c2b435dbf +size 80378 diff --git a/marked/Rel-16/23_series/23724/34b381406f073080ef510a32772b2612_img.jpg b/marked/Rel-16/23_series/23724/34b381406f073080ef510a32772b2612_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..00f5bb35608553bd04ca525ccbf44151a55bec32 --- /dev/null +++ b/marked/Rel-16/23_series/23724/34b381406f073080ef510a32772b2612_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6e715b8286dce8de47287f88a37e3c9babac84f99e12ce44f25b715373b51f65 +size 216681 diff --git a/marked/Rel-16/23_series/23724/384ca4ed072674dbb16642cd334b1c15_img.jpg b/marked/Rel-16/23_series/23724/384ca4ed072674dbb16642cd334b1c15_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ed04c3a0e56d13a0208fd781ba1394c3b42009eb --- /dev/null +++ b/marked/Rel-16/23_series/23724/384ca4ed072674dbb16642cd334b1c15_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:669a1a48722b1d912559176ed43d7e3c6747c03471cc29401dd42792f7385901 +size 59554 diff --git a/marked/Rel-16/23_series/23724/38a51baf4d5b8857d162e5d9a0645269_img.jpg b/marked/Rel-16/23_series/23724/38a51baf4d5b8857d162e5d9a0645269_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..513851a4d9463392cc3cd79fa006f666435b9926 --- /dev/null +++ b/marked/Rel-16/23_series/23724/38a51baf4d5b8857d162e5d9a0645269_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fb943323a3f7761abed8b2339bd319927436aa407c6ce6c188ae86fd18be978b +size 47860 diff --git a/marked/Rel-16/23_series/23724/390bcf4191c1553e62cb740c6d6d6ff3_img.jpg b/marked/Rel-16/23_series/23724/390bcf4191c1553e62cb740c6d6d6ff3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c06d2c364410b263951f4a9895c30688d9b67a52 --- /dev/null +++ b/marked/Rel-16/23_series/23724/390bcf4191c1553e62cb740c6d6d6ff3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d54fa98b3520039a890af54722f0e2221df11987d0abe562d8e1bc787007a404 +size 58844 diff --git a/marked/Rel-16/23_series/23724/39536a630fa74c3bcfd1670ee2152809_img.jpg b/marked/Rel-16/23_series/23724/39536a630fa74c3bcfd1670ee2152809_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..068406ff925a94d083ed88816d0c1d553218cd6c --- /dev/null +++ b/marked/Rel-16/23_series/23724/39536a630fa74c3bcfd1670ee2152809_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5e89da411e8c72e4958b04eb3e78a9f5c8cb6b64f5592e142a5e2bfadb41b1a7 +size 69314 diff --git a/marked/Rel-16/23_series/23724/4260aa4a7ece77c411597094c9d197bd_img.jpg b/marked/Rel-16/23_series/23724/4260aa4a7ece77c411597094c9d197bd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f39fc733d86015ffd3249b22d30f963f4b8da3b2 --- /dev/null +++ b/marked/Rel-16/23_series/23724/4260aa4a7ece77c411597094c9d197bd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:734eb5f7aa98c582299f0f86c0b3f1d1597f2daed7666bfdab266b5476a73815 +size 21801 diff --git a/marked/Rel-16/23_series/23724/4514db66fce4bb74f66cea56d5106b62_img.jpg b/marked/Rel-16/23_series/23724/4514db66fce4bb74f66cea56d5106b62_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3a35be0d4966a3f6933e9aedf1ac4a4ba593c6a6 --- /dev/null +++ b/marked/Rel-16/23_series/23724/4514db66fce4bb74f66cea56d5106b62_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:483d89e6cb797b803138bafc5452fe3a8bb886ad31697f19c818d453c9a87988 +size 33875 diff --git a/marked/Rel-16/23_series/23724/48f209b7c0c1f91af40cfc3466dbd534_img.jpg b/marked/Rel-16/23_series/23724/48f209b7c0c1f91af40cfc3466dbd534_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..27b83ee1e3cadb57dd164da2697deaf8bf270819 --- /dev/null +++ b/marked/Rel-16/23_series/23724/48f209b7c0c1f91af40cfc3466dbd534_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6a90c9c6b31d6625d5529443ca25b2ba9f404f9e7bdad9de285dbf9ef903b9ac +size 38799 diff --git a/marked/Rel-16/23_series/23724/4cd9eeaee1deb05bf88a8abf02ff7d7f_img.jpg b/marked/Rel-16/23_series/23724/4cd9eeaee1deb05bf88a8abf02ff7d7f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..915b0bd0a1394858f8a668294b23e17d1637d579 --- /dev/null +++ b/marked/Rel-16/23_series/23724/4cd9eeaee1deb05bf88a8abf02ff7d7f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6606652706149c4c5437ecf7e1ad664c7222c689790df4be2328f87cec8b29a8 +size 213255 diff --git a/marked/Rel-16/23_series/23724/4dd5f00d74e7db5bbb2d011609bcc43d_img.jpg b/marked/Rel-16/23_series/23724/4dd5f00d74e7db5bbb2d011609bcc43d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..07574f842ad5a74faf575e7b165c2ad39a73e52f --- /dev/null +++ b/marked/Rel-16/23_series/23724/4dd5f00d74e7db5bbb2d011609bcc43d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fdb52e63d227dcda0e668a8dfa28f1855ce657cda9cbf703267f614cedd8b2c3 +size 24211 diff --git a/marked/Rel-16/23_series/23724/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg b/marked/Rel-16/23_series/23724/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..174bad783c0d4534f07af507b16a1a215dfff125 --- /dev/null +++ b/marked/Rel-16/23_series/23724/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aa51b88b3d4c4e3148480b96f187a3256008d898fa65cad8f17a333f38348fbe +size 45013 diff --git a/marked/Rel-16/23_series/23724/508bc574df81fa8d3027a374f6d155fc_img.jpg b/marked/Rel-16/23_series/23724/508bc574df81fa8d3027a374f6d155fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..72b45d94b1a7dc51f7cba85f1e0a280ac06e0ce4 --- /dev/null +++ b/marked/Rel-16/23_series/23724/508bc574df81fa8d3027a374f6d155fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bd94ac2df47bf7d66a3192b82b21e844270f4c4b2bf982593b07b3bc96d11aec +size 72283 diff --git a/marked/Rel-16/23_series/23724/51167ecef86d85cdc6dde05a3afb74b8_img.jpg b/marked/Rel-16/23_series/23724/51167ecef86d85cdc6dde05a3afb74b8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4b83020ff3f612b37e8c42707e8e8f31c4cb44ed --- /dev/null +++ b/marked/Rel-16/23_series/23724/51167ecef86d85cdc6dde05a3afb74b8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:daad3e4c0386a5b8229154f70c7f4a46b105f0168a044f6599fa7f4a28f14c17 +size 40931 diff --git a/marked/Rel-16/23_series/23724/52e112d1ba42a3c660bf62a0fea927d3_img.jpg b/marked/Rel-16/23_series/23724/52e112d1ba42a3c660bf62a0fea927d3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..20b2f66c4db8d46d649841705c75532d3f579e4f --- /dev/null +++ b/marked/Rel-16/23_series/23724/52e112d1ba42a3c660bf62a0fea927d3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6416174111db1c5d2166dafc19331361e8e944187254bb2a96a899df44fc19c0 +size 49138 diff --git a/marked/Rel-16/23_series/23724/54bf8ae3f6e425085a2ce5fbb2c56267_img.jpg b/marked/Rel-16/23_series/23724/54bf8ae3f6e425085a2ce5fbb2c56267_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bc0fdabdf145663b2643324c81e3cf6329fb4a5f --- /dev/null +++ b/marked/Rel-16/23_series/23724/54bf8ae3f6e425085a2ce5fbb2c56267_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f84f31d865e1ee4bbe0c1f8d402678885b8915249691089bd56cfa5e7ac12a57 +size 80708 diff --git a/marked/Rel-16/23_series/23724/55736d2180d01f631782ce0784caafa3_img.jpg b/marked/Rel-16/23_series/23724/55736d2180d01f631782ce0784caafa3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4023fb85711b04d28a6ea9c2b91f5ea31550885c --- /dev/null +++ b/marked/Rel-16/23_series/23724/55736d2180d01f631782ce0784caafa3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:54c046b1f2b96b51dc7d20ec77a86d7117466145059ed073eaeb922e78be6c32 +size 67621 diff --git a/marked/Rel-16/23_series/23724/57134800ac3a97b6212b27b93aa196ac_img.jpg b/marked/Rel-16/23_series/23724/57134800ac3a97b6212b27b93aa196ac_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..11f0977ad094f036dc53ef3f35fa9b2dfc7ad7f3 --- /dev/null +++ b/marked/Rel-16/23_series/23724/57134800ac3a97b6212b27b93aa196ac_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1453ca3976eff1baa70f34d45a4540b51c167b5b151a887d34e8f00c99cb609f +size 73114 diff --git a/marked/Rel-16/23_series/23724/5801c19431e76330430e92a598cc7a16_img.jpg b/marked/Rel-16/23_series/23724/5801c19431e76330430e92a598cc7a16_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0a1db84aeb26f9717d646486d1a4b5635df838f6 --- /dev/null +++ b/marked/Rel-16/23_series/23724/5801c19431e76330430e92a598cc7a16_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:493d35481e61b2a633b95e4efb4bf60827dfd6f370cef3bb87d40966d10767f7 +size 76730 diff --git a/marked/Rel-16/23_series/23724/591746e6f224b8d929697a200e87e976_img.jpg b/marked/Rel-16/23_series/23724/591746e6f224b8d929697a200e87e976_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d9d6cc9d5a69c5dc02991b5c714c0bb8d349b671 --- /dev/null +++ b/marked/Rel-16/23_series/23724/591746e6f224b8d929697a200e87e976_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:004d6179df2e3c737b3414e0e3d020bf549320e91d5cdb355c631fa9438c45fd +size 78549 diff --git a/marked/Rel-16/23_series/23724/5a01395925fc88802da68fb5ac0f31ff_img.jpg b/marked/Rel-16/23_series/23724/5a01395925fc88802da68fb5ac0f31ff_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aa1294f769d6aff8ea3a149f958cc0810a867933 --- /dev/null +++ b/marked/Rel-16/23_series/23724/5a01395925fc88802da68fb5ac0f31ff_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ea0605f59a0213a2df5499da022f6b7f3bb74013adce9e933a4f7e397845ed9c +size 51197 diff --git a/marked/Rel-16/23_series/23724/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Rel-16/23_series/23724/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..813e7ae869333b131e0d9a35765feec4bb0c2afd --- /dev/null +++ b/marked/Rel-16/23_series/23724/5a4e62bead259c258d069fd3663ea670_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2205086548122c1ee14851769f0b306151f46a6e0b68fddbcd2e90701ba2c4cd +size 95820 diff --git a/marked/Rel-16/23_series/23724/64bec4cd45e47e1976245711f702aca2_img.jpg b/marked/Rel-16/23_series/23724/64bec4cd45e47e1976245711f702aca2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6f5df743cce75000335b6d842580a2b5aa745502 --- /dev/null +++ b/marked/Rel-16/23_series/23724/64bec4cd45e47e1976245711f702aca2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:843f794a63c987b2d2e77888b7eea46dab3a3b4be9212b058a5ae787e4965bab +size 87443 diff --git a/marked/Rel-16/23_series/23724/65d47e1d0e5982c00e9bd116b89e2b6a_img.jpg b/marked/Rel-16/23_series/23724/65d47e1d0e5982c00e9bd116b89e2b6a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8ea31cf1be0057cd0cf2ed0b464443e7af40f070 --- /dev/null +++ b/marked/Rel-16/23_series/23724/65d47e1d0e5982c00e9bd116b89e2b6a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c3bc80c1098d76127ad2aba2fcdadb6fb490efeea3910be2d261631ff37314d9 +size 42247 diff --git a/marked/Rel-16/23_series/23724/65e8c0628536d6d4245e9ab46ba070c3_img.jpg b/marked/Rel-16/23_series/23724/65e8c0628536d6d4245e9ab46ba070c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..61d238da68a82ea507246f4037b4886e1e085d4c --- /dev/null +++ b/marked/Rel-16/23_series/23724/65e8c0628536d6d4245e9ab46ba070c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ee1cb56598970eb91a964c2665756acd812852c489d3a4ad7881707bcf98a77c +size 21991 diff --git a/marked/Rel-16/23_series/23724/68d50e85fb8de4fae0e0eafaf20e63c0_img.jpg b/marked/Rel-16/23_series/23724/68d50e85fb8de4fae0e0eafaf20e63c0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..35512a2cd35560509edf694aeb3de50b278512c5 --- /dev/null +++ b/marked/Rel-16/23_series/23724/68d50e85fb8de4fae0e0eafaf20e63c0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e20899fc68d18b15f702004180a9f6f587908b188892b9c9fee779331a6e99a0 +size 46262 diff --git a/marked/Rel-16/23_series/23724/69467ece0a576b4c2ec3e0c89ba61527_img.jpg b/marked/Rel-16/23_series/23724/69467ece0a576b4c2ec3e0c89ba61527_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b72229f709922212db38f7fdcacb1aaeed119ac9 --- /dev/null +++ b/marked/Rel-16/23_series/23724/69467ece0a576b4c2ec3e0c89ba61527_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ca48e19e6201bcf42fb682fed6ac7a702e3c454a5475990d54d0eecfc3c1af51 +size 136576 diff --git a/marked/Rel-16/23_series/23724/69e5f1993021af230d08c08aac97d9df_img.jpg b/marked/Rel-16/23_series/23724/69e5f1993021af230d08c08aac97d9df_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a18cf42aa39ca7aa3ed270162c9b2cede4b8306c --- /dev/null +++ b/marked/Rel-16/23_series/23724/69e5f1993021af230d08c08aac97d9df_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e4cafdb2e5a8dd76d481e4fe2e3521f59d444ce9a2a08273e465bd22f34e6c4f +size 46732 diff --git a/marked/Rel-16/23_series/23724/6a993bfdf2e00cfad01c4d2188a75d86_img.jpg b/marked/Rel-16/23_series/23724/6a993bfdf2e00cfad01c4d2188a75d86_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b456bc3dd107bc021911a4fb965f6b62e6d6d794 --- /dev/null +++ b/marked/Rel-16/23_series/23724/6a993bfdf2e00cfad01c4d2188a75d86_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7ff0d61d7e89177191d5486f6c4150884ace4a133c4cacc750a507c6a6406ad8 +size 50885 diff --git a/marked/Rel-16/23_series/23724/6ba310120ebcd99661c4ee1c58a1586c_img.jpg b/marked/Rel-16/23_series/23724/6ba310120ebcd99661c4ee1c58a1586c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e81156f904407e43a34af0f0a61802383c5e4d4c --- /dev/null +++ b/marked/Rel-16/23_series/23724/6ba310120ebcd99661c4ee1c58a1586c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e9529ff0dd43655f949b92d2fd9c88015d94a3b2708ebaf5a01290f8833bcca5 +size 90695 diff --git a/marked/Rel-16/23_series/23724/6e0ac4070edc6a056713e6f0a3222db5_img.jpg b/marked/Rel-16/23_series/23724/6e0ac4070edc6a056713e6f0a3222db5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3cb3e88dbb5e6692ce7925a42ea51a57336ea149 --- /dev/null +++ b/marked/Rel-16/23_series/23724/6e0ac4070edc6a056713e6f0a3222db5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8490955f20eee0909c3a2534cb103ae1b48e20f6cd655853853e028ab2be5e08 +size 48325 diff --git a/marked/Rel-16/23_series/23724/73b28b0f5e3be628bb5a3d6bd1d79d21_img.jpg b/marked/Rel-16/23_series/23724/73b28b0f5e3be628bb5a3d6bd1d79d21_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3f43e36876e41a70112027ad463794d88c94ab85 --- /dev/null +++ b/marked/Rel-16/23_series/23724/73b28b0f5e3be628bb5a3d6bd1d79d21_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e5bf8045248a7d6ec34de0a0e900515b2103bc0ac4c9e9cf2a1631ebffac6992 +size 38962 diff --git a/marked/Rel-16/23_series/23724/7472c67897a35ed6b67fcb47ea4c6b6c_img.jpg b/marked/Rel-16/23_series/23724/7472c67897a35ed6b67fcb47ea4c6b6c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6946c3544bd41bc1de13cb7e91c7dccd5904d7f4 --- /dev/null +++ b/marked/Rel-16/23_series/23724/7472c67897a35ed6b67fcb47ea4c6b6c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ee6a237a03b28c830d3ecacfbcc6365ad17e867d15515b59dad8cddb5f28c5d2 +size 51370 diff --git a/marked/Rel-16/23_series/23724/753e6cc5dcad1a478caa2c7ec3a6c0a3_img.jpg b/marked/Rel-16/23_series/23724/753e6cc5dcad1a478caa2c7ec3a6c0a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d5639feb083621825914517be88510a715a359a4 --- /dev/null +++ b/marked/Rel-16/23_series/23724/753e6cc5dcad1a478caa2c7ec3a6c0a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:56c2a1c6a2907a4a265535202a645342eff99f44103a0b7fb4c1cffdb231c51e +size 34021 diff --git a/marked/Rel-16/23_series/23724/7722d62e33dcc894cc8555e9474c5606_img.jpg b/marked/Rel-16/23_series/23724/7722d62e33dcc894cc8555e9474c5606_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e9fe0d5269ea000ef35ee1e6ef6b50cd0cd11cb7 --- /dev/null +++ b/marked/Rel-16/23_series/23724/7722d62e33dcc894cc8555e9474c5606_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e31a94654f6364f5d38bab6b647a32328476703a69df1d24fbe278c7074b217a +size 12248 diff --git a/marked/Rel-16/23_series/23724/77464a47f104d0d647b2414591137b64_img.jpg b/marked/Rel-16/23_series/23724/77464a47f104d0d647b2414591137b64_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6651d79c8cbff193a1c7964187a3caef644d2662 --- /dev/null +++ b/marked/Rel-16/23_series/23724/77464a47f104d0d647b2414591137b64_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:99124d9a44a44646c2fa4644deb098ab3f9887f8fd9b467c2bd7bf4ef147c607 +size 84335 diff --git a/marked/Rel-16/23_series/23724/8269648391c59363ea61243864a2adf7_img.jpg b/marked/Rel-16/23_series/23724/8269648391c59363ea61243864a2adf7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d6d064dfd2e8181498d2af8bfd29fe2cc789c1e7 --- /dev/null +++ b/marked/Rel-16/23_series/23724/8269648391c59363ea61243864a2adf7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:49913a1f9eb11b5edb0c36f1380319b15b2fa18a422b19ea3ca9b90cb5bb0c17 +size 215113 diff --git a/marked/Rel-16/23_series/23724/863f4c0af0db9c27290338ff76162c06_img.jpg b/marked/Rel-16/23_series/23724/863f4c0af0db9c27290338ff76162c06_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1d3244c803ba0bcfa97caf36a2e8a327228ab966 --- /dev/null +++ b/marked/Rel-16/23_series/23724/863f4c0af0db9c27290338ff76162c06_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3fe519351f956bfd704103be3d8b92f9a738082121e7ebd51f1693ca2533d98f +size 77785 diff --git a/marked/Rel-16/23_series/23724/86bd357c573c9696393f5bde4d4cce4f_img.jpg b/marked/Rel-16/23_series/23724/86bd357c573c9696393f5bde4d4cce4f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..376ec195fc4924120c48cbe2682b44d5f2683a24 --- /dev/null +++ b/marked/Rel-16/23_series/23724/86bd357c573c9696393f5bde4d4cce4f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:78d6ceeafd34e3d2dfe2d740f08452dc370f6372337ffecbf11adcc95841ac79 +size 17975 diff --git a/marked/Rel-16/23_series/23724/879d68959f0c0ba370ef82447298ba17_img.jpg b/marked/Rel-16/23_series/23724/879d68959f0c0ba370ef82447298ba17_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9d5c12c3d322985d7abed27825896652cb900e82 --- /dev/null +++ b/marked/Rel-16/23_series/23724/879d68959f0c0ba370ef82447298ba17_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dcae3e86fc28c50a567790244474e55ac203208512356739808fa3ecaf84d39f +size 44250 diff --git a/marked/Rel-16/23_series/23724/88b0f3f4393228e9ea4d6542aef7c399_img.jpg b/marked/Rel-16/23_series/23724/88b0f3f4393228e9ea4d6542aef7c399_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dc9036176993bc42067dcc0b9400aef5320b5ced --- /dev/null +++ b/marked/Rel-16/23_series/23724/88b0f3f4393228e9ea4d6542aef7c399_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6779b8e277c4cd46597a3f44255f83a274397049ec4a6ac84b9a044de10e75a8 +size 61205 diff --git a/marked/Rel-16/23_series/23724/8afb16b644b2fe89d5c34251c3e6bf0c_img.jpg b/marked/Rel-16/23_series/23724/8afb16b644b2fe89d5c34251c3e6bf0c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6c89e1c48f355e34dcb3e111b86c7107d5f48e0d --- /dev/null +++ b/marked/Rel-16/23_series/23724/8afb16b644b2fe89d5c34251c3e6bf0c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:effdf6a15a47bd4003e150c96d44e024fa73abb497308a425576d19a2a6b28eb +size 109682 diff --git a/marked/Rel-16/23_series/23724/906c1ba8ae95f501d4cd79eb08485307_img.jpg b/marked/Rel-16/23_series/23724/906c1ba8ae95f501d4cd79eb08485307_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3196f07a5529cab45348389f4aca9a94d872c125 --- /dev/null +++ b/marked/Rel-16/23_series/23724/906c1ba8ae95f501d4cd79eb08485307_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f4054b13f9a2fa46492bba2b6ef3985004804ca27a2d43c4480be73261489c37 +size 30750 diff --git a/marked/Rel-16/23_series/23724/90ddb84c323b956e2d50a54d3f870566_img.jpg b/marked/Rel-16/23_series/23724/90ddb84c323b956e2d50a54d3f870566_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..80f5450d836b62ad6af78fbd50241ada27efca23 --- /dev/null +++ b/marked/Rel-16/23_series/23724/90ddb84c323b956e2d50a54d3f870566_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:734d0254997aef085e3a35ebbe1e92a125f1fd1ec0c482dc873d37df3b7baa35 +size 43451 diff --git a/marked/Rel-16/23_series/23724/90ee16ccc0ad16aeca48087797d7b07f_img.jpg b/marked/Rel-16/23_series/23724/90ee16ccc0ad16aeca48087797d7b07f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f4110f086a51a180124ceeecf6c9bd5a050af1e4 --- /dev/null +++ b/marked/Rel-16/23_series/23724/90ee16ccc0ad16aeca48087797d7b07f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1b6326a9a0f8ae13043ff9689ad34393c0a4c0d4c26f80353cf242a5d7e4641e +size 66005 diff --git a/marked/Rel-16/23_series/23724/921458d4fc1b778c2450592ac9745b48_img.jpg b/marked/Rel-16/23_series/23724/921458d4fc1b778c2450592ac9745b48_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..87485ed0afe08f765c4ad4f7d00b447feb9f92fb --- /dev/null +++ b/marked/Rel-16/23_series/23724/921458d4fc1b778c2450592ac9745b48_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a0f775dc3227b6cd3507252c0bc87a8852a884d706fd961ae702d2cac09a695e +size 35154 diff --git a/marked/Rel-16/23_series/23724/921f8fa0f7ce2c9956f20d33162c13a2_img.jpg b/marked/Rel-16/23_series/23724/921f8fa0f7ce2c9956f20d33162c13a2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2a004f7783fcccefbf9273e0d5a13c901da7f5c3 --- /dev/null +++ b/marked/Rel-16/23_series/23724/921f8fa0f7ce2c9956f20d33162c13a2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d14e20d1f1188321f10fd50794173a974dfab74e4b4996b107afdfe5af3e8234 +size 95277 diff --git a/marked/Rel-16/23_series/23724/9694add1e3183133a9ddb9f41c48d00e_img.jpg b/marked/Rel-16/23_series/23724/9694add1e3183133a9ddb9f41c48d00e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1bda3c8f47514a5c67534921732669f557933e77 --- /dev/null +++ b/marked/Rel-16/23_series/23724/9694add1e3183133a9ddb9f41c48d00e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b6c3c268c18ded10f720e864c255560c47197f4dbca029e10c0d414a51d69056 +size 86699 diff --git a/marked/Rel-16/23_series/23724/96b0240f56d14453b5da05ec30fd5c6e_img.jpg b/marked/Rel-16/23_series/23724/96b0240f56d14453b5da05ec30fd5c6e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..75f381a88e930b9086ac62fbcb6f9a91c91ecded --- /dev/null +++ b/marked/Rel-16/23_series/23724/96b0240f56d14453b5da05ec30fd5c6e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:deeef3fc07a72c0e938e48000de42ac94c8defe3596c55fb0d8418dedd661700 +size 45189 diff --git a/marked/Rel-16/23_series/23724/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg b/marked/Rel-16/23_series/23724/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3a6faab95b05985a6f2492107b851ee1fb679f43 --- /dev/null +++ b/marked/Rel-16/23_series/23724/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:366600e871beaee0f2b060a8a14b3da643a7e3cd936de2b7d674cac2e392c4eb +size 85433 diff --git a/marked/Rel-16/23_series/23724/9e3c3a68ea23d6b0c0243f2baa1cb99f_img.jpg b/marked/Rel-16/23_series/23724/9e3c3a68ea23d6b0c0243f2baa1cb99f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b9155f48b6c751a35e1026dd56772a53acce6033 --- /dev/null +++ b/marked/Rel-16/23_series/23724/9e3c3a68ea23d6b0c0243f2baa1cb99f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9ac9b51ffb22109ce92b101b84db40a81051054136357743497aea85258a8446 +size 64373 diff --git a/marked/Rel-16/23_series/23724/9e4f582a5d5f6742d1372956db0f8f0b_img.jpg b/marked/Rel-16/23_series/23724/9e4f582a5d5f6742d1372956db0f8f0b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5114ab5fd440567a47223cccfb31d141d7a2f6c5 --- /dev/null +++ b/marked/Rel-16/23_series/23724/9e4f582a5d5f6742d1372956db0f8f0b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:04657674035d2274cd07e69b4a83f8d9a21df4eb1a12aedb48c08cf1591d9ae6 +size 23072 diff --git a/marked/Rel-16/23_series/23724/9e8ebf03cae78f4f81b697548c2d7250_img.jpg b/marked/Rel-16/23_series/23724/9e8ebf03cae78f4f81b697548c2d7250_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5806b92e53fd9ef48f11af516d7c2a9405540dda --- /dev/null +++ b/marked/Rel-16/23_series/23724/9e8ebf03cae78f4f81b697548c2d7250_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3a36ecb43f1eb4a0a8074057c62a47b50796c49fb7cbe759729baf87b57a3cc1 +size 21327 diff --git a/marked/Rel-16/23_series/23724/9ff1b32449ea068bba9647d71904bd59_img.jpg b/marked/Rel-16/23_series/23724/9ff1b32449ea068bba9647d71904bd59_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..27b0b8318b8c0377fad6f7f188222a971921e9d2 --- /dev/null +++ b/marked/Rel-16/23_series/23724/9ff1b32449ea068bba9647d71904bd59_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:54c9efcb459726e5fd81523a753212c51528cbdacd0d39b1c37fed3a5e73c8c7 +size 69909 diff --git a/marked/Rel-16/23_series/23724/a0b72ad654428ce2b44766f24928643e_img.jpg b/marked/Rel-16/23_series/23724/a0b72ad654428ce2b44766f24928643e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..983f8e5257c226b1b233d67a93de4076ff365a40 --- /dev/null +++ b/marked/Rel-16/23_series/23724/a0b72ad654428ce2b44766f24928643e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d6f2d4e663d70be8d6c81da29ef3b28f0db431150d1eb6cd1add716c5aadbac6 +size 23397 diff --git a/marked/Rel-16/23_series/23724/a0e8fe7862a6d7341faf5dac275277cc_img.jpg b/marked/Rel-16/23_series/23724/a0e8fe7862a6d7341faf5dac275277cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..438faccd9f38ab24861bd6186977b3a577901137 --- /dev/null +++ b/marked/Rel-16/23_series/23724/a0e8fe7862a6d7341faf5dac275277cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f1d1051b023f4452c344ab9ae20575791ab0446dca51e80304298e5da02be884 +size 67336 diff --git a/marked/Rel-16/23_series/23724/a1890b9a9b85f13e67ed59bbad623659_img.jpg b/marked/Rel-16/23_series/23724/a1890b9a9b85f13e67ed59bbad623659_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7aa52f2eac55e715f5a1141e446c9f91112ca9a4 --- /dev/null +++ b/marked/Rel-16/23_series/23724/a1890b9a9b85f13e67ed59bbad623659_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1a3efc8bf3f03d56bad465c27dc6ea03aad0d4eddf0a5429aae910e4ea926a3e +size 39066 diff --git a/marked/Rel-16/23_series/23724/a26e142d3df5bef41a84a9dd099d7825_img.jpg b/marked/Rel-16/23_series/23724/a26e142d3df5bef41a84a9dd099d7825_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a09cff2e509683eafb9f85cd67f66f690ceabba6 --- /dev/null +++ b/marked/Rel-16/23_series/23724/a26e142d3df5bef41a84a9dd099d7825_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dccecacf5c196b8d7992d29bbd503cb1d000a0dc9c92e89accbaa81e4dbc7943 +size 93959 diff --git a/marked/Rel-16/23_series/23724/a3083eec2a883ee8327b3c24174df6a9_img.jpg b/marked/Rel-16/23_series/23724/a3083eec2a883ee8327b3c24174df6a9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3f90d574a6db86a4201e933259558ae7577fb88e --- /dev/null +++ b/marked/Rel-16/23_series/23724/a3083eec2a883ee8327b3c24174df6a9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2d25ce01093d7bdb65c36033012c996b451b1b044c10a0921206267c4ad2dfcc +size 51508 diff --git a/marked/Rel-16/23_series/23724/a3c1310e720178d2450a3748c7c75422_img.jpg b/marked/Rel-16/23_series/23724/a3c1310e720178d2450a3748c7c75422_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..59b8190461f6c35016fa53edef06348575ad6f97 --- /dev/null +++ b/marked/Rel-16/23_series/23724/a3c1310e720178d2450a3748c7c75422_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:30eaf08ab0bceddebb69fc377cb8fc574eb2c5fb2ecf1d6b86e53b499ac2430e +size 78031 diff --git a/marked/Rel-16/23_series/23724/a3f61f2e4a173b16257cd80e83d41d38_img.jpg b/marked/Rel-16/23_series/23724/a3f61f2e4a173b16257cd80e83d41d38_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..48e926c1431732ea3f221b3d7ebc96fb045c3863 --- /dev/null +++ b/marked/Rel-16/23_series/23724/a3f61f2e4a173b16257cd80e83d41d38_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0eaf9e72e820a7ad28cf0b1e9788d92bb4f64fa287cb1b36c248db9585ec1090 +size 78041 diff --git a/marked/Rel-16/23_series/23724/a4eb9fe011f0e6dc8405f777c5f3f766_img.jpg b/marked/Rel-16/23_series/23724/a4eb9fe011f0e6dc8405f777c5f3f766_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2af1b334c083e13ca506e1ed069de49309de854b --- /dev/null +++ b/marked/Rel-16/23_series/23724/a4eb9fe011f0e6dc8405f777c5f3f766_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b9235dd61cd47d486985ae23928b31ae103aa426d2d7746b0687410a7e8e43d6 +size 62667 diff --git a/marked/Rel-16/23_series/23724/a634891d16b60b21df90a35c2af72c67_img.jpg b/marked/Rel-16/23_series/23724/a634891d16b60b21df90a35c2af72c67_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c8e55f40222a8d7f060e59a68165837693865471 --- /dev/null +++ b/marked/Rel-16/23_series/23724/a634891d16b60b21df90a35c2af72c67_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:61bce42117783bf6bd473172f6cdde9065cb85eeb302dd5d3dfd4c2f49737a58 +size 83241 diff --git a/marked/Rel-16/23_series/23724/a78db21022e0687c18d97ed547dd7ecb_img.jpg b/marked/Rel-16/23_series/23724/a78db21022e0687c18d97ed547dd7ecb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..272515b6a1db6e6c1b21c4dfa539fd90d2cd1ce1 --- /dev/null +++ b/marked/Rel-16/23_series/23724/a78db21022e0687c18d97ed547dd7ecb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dda0bce94f9caf60c63a155c9fa69f9f94b58538bc8d24574e5443083acc9ba7 +size 27227 diff --git a/marked/Rel-16/23_series/23724/a963ca41bde1669b18a4b783616f228b_img.jpg b/marked/Rel-16/23_series/23724/a963ca41bde1669b18a4b783616f228b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2b836a918819f508111dd2d823c382256414abc5 --- /dev/null +++ b/marked/Rel-16/23_series/23724/a963ca41bde1669b18a4b783616f228b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0c8dea37ec4a113ea744d2a6d469d5acaf9dd2a077e897d51abe65989aa86e65 +size 49029 diff --git a/marked/Rel-16/23_series/23724/ac42de838505beb048fb1267c46de428_img.jpg b/marked/Rel-16/23_series/23724/ac42de838505beb048fb1267c46de428_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b1b0d3e56b662b917077ccf729b5034de1fb9782 --- /dev/null +++ b/marked/Rel-16/23_series/23724/ac42de838505beb048fb1267c46de428_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:baf6563be1831fa41bf4c9d542b9af00e6642918391702b1565949055120fcc0 +size 49898 diff --git a/marked/Rel-16/23_series/23724/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg b/marked/Rel-16/23_series/23724/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0eebec01491daebe22231b5a27853bb2ff6e6643 --- /dev/null +++ b/marked/Rel-16/23_series/23724/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3b2294afd95f8f1b4dba47cdbf79fa8c817845a8d7fbb03d8b04d8c0ec5e495a +size 59941 diff --git a/marked/Rel-16/23_series/23724/af6be343f0c0a8f155f965dcf337b8af_img.jpg b/marked/Rel-16/23_series/23724/af6be343f0c0a8f155f965dcf337b8af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..77b0231848add819416ae7873cacf186009b7ea6 --- /dev/null +++ b/marked/Rel-16/23_series/23724/af6be343f0c0a8f155f965dcf337b8af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:88772ccfe2f5c661b282cc5c10e5b0ab396406183205a463646461d9379a0779 +size 63513 diff --git a/marked/Rel-16/23_series/23724/b0988cfd9f60f2cd1916e3c2f9cae3da_img.jpg b/marked/Rel-16/23_series/23724/b0988cfd9f60f2cd1916e3c2f9cae3da_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..95bf9cbce5041de40d8fbee0c09306cc135c59a9 --- /dev/null +++ b/marked/Rel-16/23_series/23724/b0988cfd9f60f2cd1916e3c2f9cae3da_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ade5028939bb7a7a8503d628e0b0e1197c8b9651877e185ab93aec9c36dbd96e +size 102917 diff --git a/marked/Rel-16/23_series/23724/b13465efdac63129aef9b6f1787d0d00_img.jpg b/marked/Rel-16/23_series/23724/b13465efdac63129aef9b6f1787d0d00_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1e87ba53a78e71926cd1cf8132e3d2bb0b164d67 --- /dev/null +++ b/marked/Rel-16/23_series/23724/b13465efdac63129aef9b6f1787d0d00_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5adcbd85fe9cd03be5db1e61961a9a2da336e69bee8c36f9b2936fe0c6ee579a +size 81676 diff --git a/marked/Rel-16/23_series/23724/b153a1dd70177f3ad028ab64756eec09_img.jpg b/marked/Rel-16/23_series/23724/b153a1dd70177f3ad028ab64756eec09_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..415f78560b98b486f05d79e43657f68d91023f01 --- /dev/null +++ b/marked/Rel-16/23_series/23724/b153a1dd70177f3ad028ab64756eec09_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:869a0a70ef46bcf391bfc00a6f9de7704ff38399ae9fca8919af98993943cfea +size 61047 diff --git a/marked/Rel-16/23_series/23724/b2a75beaa7e485cd651c2a83b30a4adc_img.jpg b/marked/Rel-16/23_series/23724/b2a75beaa7e485cd651c2a83b30a4adc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8ad4f73dc80fb17eec07f7c9632241662ab2e755 --- /dev/null +++ b/marked/Rel-16/23_series/23724/b2a75beaa7e485cd651c2a83b30a4adc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7dc062bad1c1d0b5ed9234a5eeaaf84e7419fd2ed9f6025457add3974d94088a +size 26123 diff --git a/marked/Rel-16/23_series/23724/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg b/marked/Rel-16/23_series/23724/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7dc72ac3cacfa68126999f4b43f6d5af567f9084 --- /dev/null +++ b/marked/Rel-16/23_series/23724/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ace515ea6bdeeda1f6423d589ef82334b0245be757b6996a80275eb0d4295bad +size 30836 diff --git a/marked/Rel-16/23_series/23724/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg b/marked/Rel-16/23_series/23724/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b1f15962f3b348690cf4af5b04d1ab06bf345977 --- /dev/null +++ b/marked/Rel-16/23_series/23724/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c634487e331513f858ce9836a6c112b6983222b43bcc5ab211ef051a441ce518 +size 91109 diff --git a/marked/Rel-16/23_series/23724/b4e9fc9d087037ebe92a54050272e7d6_img.jpg b/marked/Rel-16/23_series/23724/b4e9fc9d087037ebe92a54050272e7d6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..632d9f1f116e709cd55d64cf9087022669800431 --- /dev/null +++ b/marked/Rel-16/23_series/23724/b4e9fc9d087037ebe92a54050272e7d6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:57616c8559dd7fb2449b522a8bda68bc9a0097709d04de55e7e154965eb02a9a +size 35743 diff --git a/marked/Rel-16/23_series/23724/b51423b6c049f5b5fcde42e50b58f18b_img.jpg b/marked/Rel-16/23_series/23724/b51423b6c049f5b5fcde42e50b58f18b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1cb0e5f50ad5c207d0aecc6faa8065e5bfc5fdae --- /dev/null +++ b/marked/Rel-16/23_series/23724/b51423b6c049f5b5fcde42e50b58f18b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8843abe4c246db07bcf6131d8345ed10245472b954cf62e2548678d4b8e75fc8 +size 43408 diff --git a/marked/Rel-16/23_series/23724/b58cedaf15ad4f0edee5621820865ccc_img.jpg b/marked/Rel-16/23_series/23724/b58cedaf15ad4f0edee5621820865ccc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fbd58c8379d3f98f51a9ff8dfc308b3b8120c5ce --- /dev/null +++ b/marked/Rel-16/23_series/23724/b58cedaf15ad4f0edee5621820865ccc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a2a0baf2e511b1d4cb6f317d292c34d729bde5b1dd8a7b3127e43f90371d9379 +size 144319 diff --git a/marked/Rel-16/23_series/23724/c1278da91cbcabe32628e589ebc47418_img.jpg b/marked/Rel-16/23_series/23724/c1278da91cbcabe32628e589ebc47418_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..615df5df1ab0e7b5465716100e22f2656d116685 --- /dev/null +++ b/marked/Rel-16/23_series/23724/c1278da91cbcabe32628e589ebc47418_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bf711bed2bc7613cfe81bf13f65e51740ff3a512cb2a8e54455eff7801523988 +size 36060 diff --git a/marked/Rel-16/23_series/23724/c14d36776b70c47a6bad152b3a8a5ec6_img.jpg b/marked/Rel-16/23_series/23724/c14d36776b70c47a6bad152b3a8a5ec6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..52f990fc1df6414fdc92801ae6b9c80c7844b2d5 --- /dev/null +++ b/marked/Rel-16/23_series/23724/c14d36776b70c47a6bad152b3a8a5ec6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5974b37d007e6c685360495620d7b739640f7ccd8f0e56573de278f8f9cceb25 +size 27636 diff --git a/marked/Rel-16/23_series/23724/c2f5e14ca0ed0f7944c7606451f67d85_img.jpg b/marked/Rel-16/23_series/23724/c2f5e14ca0ed0f7944c7606451f67d85_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..18ecd290a951b22ca411591e975ca5bd25ceb9f4 --- /dev/null +++ b/marked/Rel-16/23_series/23724/c2f5e14ca0ed0f7944c7606451f67d85_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:62b039ae20c78f7bd5c5d5c0071d0418189757601f598e708ecf19791996522e +size 55380 diff --git a/marked/Rel-16/23_series/23724/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg b/marked/Rel-16/23_series/23724/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64fecf943eb971ed73a9712358bb304a3f1dad38 --- /dev/null +++ b/marked/Rel-16/23_series/23724/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a298b8228a737585ac4d697b2681aa1ac42f1dcc028f72b5f40012c2ecf14660 +size 25605 diff --git a/marked/Rel-16/23_series/23724/cc6f9dbfc36aa5821d9749ca84861f93_img.jpg b/marked/Rel-16/23_series/23724/cc6f9dbfc36aa5821d9749ca84861f93_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3cb6b9fc8412671ec7e4925549ab31816289ac09 --- /dev/null +++ b/marked/Rel-16/23_series/23724/cc6f9dbfc36aa5821d9749ca84861f93_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:209bca2a97216999fb29794dc6f7a6ab437dd7ddaf32d43d79305b696e40ca02 +size 87144 diff --git a/marked/Rel-16/23_series/23724/d9cf65b94921cc4457be18d794ac0624_img.jpg b/marked/Rel-16/23_series/23724/d9cf65b94921cc4457be18d794ac0624_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7f6e01272e461ee53f953bc9834047f7c2ef2e16 --- /dev/null +++ b/marked/Rel-16/23_series/23724/d9cf65b94921cc4457be18d794ac0624_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:137248b8821f8e7a6d4ae29a80f1983fa7a63fdbda553e439aaaf456c7d259b5 +size 29455 diff --git a/marked/Rel-16/23_series/23724/d9cfc30025244dcd75766061f27ee09f_img.jpg b/marked/Rel-16/23_series/23724/d9cfc30025244dcd75766061f27ee09f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7e5e1baf4d4873a889685e937a845a17b945425e --- /dev/null +++ b/marked/Rel-16/23_series/23724/d9cfc30025244dcd75766061f27ee09f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:89766a06e3f2fcc1ee890bdce49c387a9743bbb30d2817dc5bf42b2d553adaa7 +size 104334 diff --git a/marked/Rel-16/23_series/23724/db7a693cf26f527ac6c0d4d41da20858_img.jpg b/marked/Rel-16/23_series/23724/db7a693cf26f527ac6c0d4d41da20858_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..476780022809c3c90dcdfe6437df9d7f29e72f6f --- /dev/null +++ b/marked/Rel-16/23_series/23724/db7a693cf26f527ac6c0d4d41da20858_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9f4dc8bb784092c9b3df8e7cd0990e741ba7267ecc975df1af9f37e2b13de8d0 +size 72329 diff --git a/marked/Rel-16/23_series/23724/dbd4bab54b57e8d1abf80e3de6471130_img.jpg b/marked/Rel-16/23_series/23724/dbd4bab54b57e8d1abf80e3de6471130_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2d177e4e5e8528256c82dc510e5f2be63de69aa1 --- /dev/null +++ b/marked/Rel-16/23_series/23724/dbd4bab54b57e8d1abf80e3de6471130_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:67c8005b8de61fe6f446cc508fc830ce2600dcd764f522988948ad33ca184221 +size 45563 diff --git a/marked/Rel-16/23_series/23724/de63e4b6d8b0aa76b85e1fe3236eac27_img.jpg b/marked/Rel-16/23_series/23724/de63e4b6d8b0aa76b85e1fe3236eac27_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b74c6b4d87b598afedd811d9a8dcc44164f4e914 --- /dev/null +++ b/marked/Rel-16/23_series/23724/de63e4b6d8b0aa76b85e1fe3236eac27_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:09de163facd5aced03c17a2299e737e92f782201e210ad9552d3e06bc367f7cd +size 65503 diff --git a/marked/Rel-16/23_series/23724/dfe74512a9c9fb620f72c9dbc22874aa_img.jpg b/marked/Rel-16/23_series/23724/dfe74512a9c9fb620f72c9dbc22874aa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7f0e7a629f6a92da2730319d2b630770c26345b5 --- /dev/null +++ b/marked/Rel-16/23_series/23724/dfe74512a9c9fb620f72c9dbc22874aa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dfd1fc7da488d6a4fe4f096b6fc726b87725f451debb2f5cc6bd750b94fbe50e +size 37519 diff --git a/marked/Rel-16/23_series/23724/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/marked/Rel-16/23_series/23724/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..257c6cc40732ea11832311ffee6707b4e6a0f12e --- /dev/null +++ b/marked/Rel-16/23_series/23724/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6097b2cd5c9cd5b54fbe2e2d3bc578b4f72c17e98df8f31f1b230036bda07961 +size 105132 diff --git a/marked/Rel-16/23_series/23724/e2180bd000d9ae6dea6b38d1cc79755b_img.jpg b/marked/Rel-16/23_series/23724/e2180bd000d9ae6dea6b38d1cc79755b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9d8c1becd1194afec4bdbe80d76800ca4f936738 --- /dev/null +++ b/marked/Rel-16/23_series/23724/e2180bd000d9ae6dea6b38d1cc79755b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:67f8f6e2d27f8b863aadbc8812c342c766244d434c54909a1e54bb132147b034 +size 104608 diff --git a/marked/Rel-16/23_series/23724/e2c120be98ede6deb60dd341f5a9803b_img.jpg b/marked/Rel-16/23_series/23724/e2c120be98ede6deb60dd341f5a9803b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..369654baafe51aa4677cb09a6dc08638874eaea9 --- /dev/null +++ b/marked/Rel-16/23_series/23724/e2c120be98ede6deb60dd341f5a9803b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:206f7adce7f4952fe9bb8cf3d28801532d25a506969a8123aaaa6b963b3b169e +size 60922 diff --git a/marked/Rel-16/23_series/23724/e7010c66da16316c2935dfbbef5056b3_img.jpg b/marked/Rel-16/23_series/23724/e7010c66da16316c2935dfbbef5056b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f67db68d9c860a5c76c279025875dc1296453c00 --- /dev/null +++ b/marked/Rel-16/23_series/23724/e7010c66da16316c2935dfbbef5056b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aa7c4fa5b740bf92f4b74986bb93d670ceb899886ae6f46b26b197c2f82ff92f +size 53237 diff --git a/marked/Rel-16/23_series/23724/e8f5277dca9bb75e7ba79d96c568db4b_img.jpg b/marked/Rel-16/23_series/23724/e8f5277dca9bb75e7ba79d96c568db4b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9217232abfd41c2c723add4b620ca5a9b6e45625 --- /dev/null +++ b/marked/Rel-16/23_series/23724/e8f5277dca9bb75e7ba79d96c568db4b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b0e9ae2b66771aab5b9114b87c0d982daa4416a0da1d67bb9d8b9cc3b3c44387 +size 98339 diff --git a/marked/Rel-16/23_series/23724/ed29f40262b821f88760fe2539d31090_img.jpg b/marked/Rel-16/23_series/23724/ed29f40262b821f88760fe2539d31090_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f4d898bce058c3fba8919d73944f6c3be5656185 --- /dev/null +++ b/marked/Rel-16/23_series/23724/ed29f40262b821f88760fe2539d31090_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:554c206cbed02907ee133385e5748d59ca6eaa602f3fe42256ceedfd44cb77a7 +size 85192 diff --git a/marked/Rel-16/23_series/23724/eea0bd1826a6e1bdcadff03936a7b20a_img.jpg b/marked/Rel-16/23_series/23724/eea0bd1826a6e1bdcadff03936a7b20a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b0a9168bbce1676e8566a29841cee7229957215c --- /dev/null +++ b/marked/Rel-16/23_series/23724/eea0bd1826a6e1bdcadff03936a7b20a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:815ecb589417091fcf9ebc6d337c31f9af3c7e75d50c82db529858ea6d153b78 +size 192717 diff --git a/marked/Rel-16/23_series/23724/f087d3f5d298b3b1634d13ff17879e41_img.jpg b/marked/Rel-16/23_series/23724/f087d3f5d298b3b1634d13ff17879e41_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..132a697ccf42da4889dfec7b31c28bf3aa97954a --- /dev/null +++ b/marked/Rel-16/23_series/23724/f087d3f5d298b3b1634d13ff17879e41_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9365924099e736105a7f88a2834a66604d21fdc56486e853cee69a6350a02d86 +size 75991 diff --git a/marked/Rel-16/23_series/23724/f142b022cfc716cd967297f027efe647_img.jpg b/marked/Rel-16/23_series/23724/f142b022cfc716cd967297f027efe647_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e021a2944e9c9ae48c72e683d9a5e7e08e9e9ac4 --- /dev/null +++ b/marked/Rel-16/23_series/23724/f142b022cfc716cd967297f027efe647_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:af81e43d1a7b7c71f183dfaae2f8b1dac82ed97971ac11eea4b625646283123e +size 42712 diff --git a/marked/Rel-16/23_series/23724/f246294bf54daf21d334d732c4b76d88_img.jpg b/marked/Rel-16/23_series/23724/f246294bf54daf21d334d732c4b76d88_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..06577966260870de2093b883ca3f0fbb948783ab --- /dev/null +++ b/marked/Rel-16/23_series/23724/f246294bf54daf21d334d732c4b76d88_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:deb1323974c5ec95f6893b69e0c647de5388965c9497fc16a5dac4e423e470c4 +size 98418 diff --git a/marked/Rel-16/23_series/23724/f4e5a86da5c799372a7c1ea2397dedb7_img.jpg b/marked/Rel-16/23_series/23724/f4e5a86da5c799372a7c1ea2397dedb7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c8e560ff605f9b27d392d5091d9f00268d8f5008 --- /dev/null +++ b/marked/Rel-16/23_series/23724/f4e5a86da5c799372a7c1ea2397dedb7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:512514b78c3cf52546080256d8624453b56e493e164cf05fb4803f5b5098c907 +size 68623 diff --git a/marked/Rel-16/23_series/23724/fb4274c4b7882a4059103f1dbca9b111_img.jpg b/marked/Rel-16/23_series/23724/fb4274c4b7882a4059103f1dbca9b111_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..38464167cdf00b172df82439e4209de6080735eb --- /dev/null +++ b/marked/Rel-16/23_series/23724/fb4274c4b7882a4059103f1dbca9b111_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:50401d19eee3cc6a3b9525d15b097ececc55b2aab9833c9ea9a757fdb19b7b54 +size 39317 diff --git a/marked/Rel-16/23_series/23724/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/marked/Rel-16/23_series/23724/ff0952ef692c9d960ce5f6708bcc9711_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9399327e887c5697b517219626e12c9f591e3f0c --- /dev/null +++ b/marked/Rel-16/23_series/23724/ff0952ef692c9d960ce5f6708bcc9711_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:43d8ec6c430024b36baa0668bba46ae206de0bfba7daee28c903d4c55c6ffb31 +size 66800 diff --git a/marked/Rel-16/23_series/23724/raw.md b/marked/Rel-16/23_series/23724/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..1e4a02ba74304efd7be0ddd0962c6b141ff23ad6 --- /dev/null +++ b/marked/Rel-16/23_series/23724/raw.md @@ -0,0 +1,11180 @@ +# Contents + +| | | +|------------------------------------------------------------------------------------|----| +| Foreword ..... | 15 | +| 1 Scope..... | 16 | +| 2 References..... | 17 | +| 3 Definitions, symbols and abbreviations ..... | 18 | +| 3.1 Definitions..... | 18 | +| 3.2 Symbols..... | 18 | +| 3.3 Abbreviations ..... | 18 | +| 4 Architectural Assumptions and Principles..... | 18 | +| 5 Key Issues ..... | 19 | +| 5.1 Key Issue 1: Support for infrequent small data transmission..... | 19 | +| 5.1.1 Description ..... | 19 | +| 5.1.2 Architectural requirements ..... | 19 | +| 5.1.3 Architectural baseline..... | 19 | +| 5.1.4 Open issues..... | 20 | +| 5.2 Key Issue 2: Frequent small data communication ..... | 20 | +| 5.2.1 Description ..... | 20 | +| 5.2.2 Architectural requirements ..... | 20 | +| 5.2.3 Architectural baseline..... | 21 | +| 5.2.4 Open issues..... | 21 | +| 5.3 Key Issue 3: High latency communication ..... | 21 | +| 5.3.1 Description ..... | 21 | +| 5.3.2 Architectural requirements ..... | 21 | +| 5.3.3 Architectural baseline..... | 21 | +| 5.3.4 Open issues..... | 22 | +| 5.4 Key Issue 4: Power Saving Functions..... | 22 | +| 5.4.1 Description ..... | 22 | +| 5.4.2 Architectural requirements ..... | 23 | +| 5.4.3 Architectural baseline..... | 23 | +| 5.4.4 Open issues..... | 23 | +| 5.5 Key Issue 5: UE TX Power Saving Functions ..... | 23 | +| 5.5.1 Description ..... | 23 | +| 5.5.2 Architectural requirements ..... | 24 | +| 5.5.3 Architectural baseline..... | 24 | +| 5.5.4 Open issues..... | 24 | +| 5.6 Key Issue 6: Management of Enhanced Coverage..... | 24 | +| 5.6.1 Description ..... | 24 | +| 5.6.2 Architectural requirements ..... | 24 | +| 5.6.3 Architectural baseline..... | 24 | +| 5.6.4 Open issues..... | 25 | +| 5.7 Key Issue 7: Overload Control for small data..... | 25 | +| 5.7.1 Description ..... | 25 | +| 5.7.2 Architectural requirements ..... | 25 | +| 5.7.3 Architectural baseline..... | 25 | +| 5.7.4 Open issues..... | 25 | +| 5.8 Key Issue 8: Support of the Reliable Data Service ..... | 26 | +| 5.8.1 Description ..... | 26 | +| 5.8.2 Architectural requirements ..... | 26 | +| 5.8.3 Architectural baseline..... | 26 | +| 5.8.4 Open issues..... | 26 | +| 5.9 Key Issue 9: Support of common north-bound APIs for EPC-5GC Interworking ..... | 26 | +| 5.9.1 Description ..... | 26 | +| 5.9.2 Architectural requirements ..... | 27 | +| 5.9.3 Architectural baseline..... | 27 | +| 5.9.4 Open issues..... | 27 | +| 5.10 Key Issue 10: Network Parameter Configuration API via NEF ..... | 27 | + +| | | | +|-----------|---------------------------------------------------------------------------------------------------------|----| +| 5.10.1 | Description ..... | 27 | +| 5.10.2 | Architectural requirements ..... | 27 | +| 5.10.3 | Architectural baseline ..... | 28 | +| 5.10.4 | Open issues ..... | 28 | +| 5.11 | Key Issue 11: Monitoring ..... | 28 | +| 5.11.1 | Description ..... | 28 | +| 5.11.2 | Architectural requirements ..... | 29 | +| 5.11.3 | Architectural baseline ..... | 29 | +| 5.11.4 | Open issues ..... | 29 | +| 5.12 | Key Issue 12: Inter-RAT mobility support to/from NB-IoT ..... | 29 | +| 5.12.1 | Description ..... | 29 | +| 5.12.2 | Architectural requirements ..... | 29 | +| 5.12.3 | Architectural baseline ..... | 29 | +| 5.12.4 | Open issues ..... | 30 | +| 5.13 | Key Issue 13: Support for Expected UE Behaviour ..... | 30 | +| 5.13.1 | Description ..... | 30 | +| 5.13.2 | Architectural requirements ..... | 30 | +| 5.13.3 | Architectural baseline ..... | 30 | +| 5.13.4 | Open issues ..... | 30 | +| 5.14 | Key Issue 14: QoS Support for NB-IoT ..... | 31 | +| 5.14.1 | Description ..... | 31 | +| 5.14.2 | Architectural requirements ..... | 31 | +| 5.14.3 | Architectural baseline ..... | 31 | +| 5.14.4 | Open issues ..... | 31 | +| 5.15 | Key Issue 15: Core Network selection for Cellular IoT ..... | 31 | +| 5.15.1 | Description ..... | 31 | +| 5.15.2 | Architectural requirements ..... | 32 | +| 5.15.3 | Architectural baseline ..... | 32 | +| 5.15.4 | Open issues ..... | 32 | +| 5.16 | Key Issue 16: Support of Group communication and messaging ..... | 32 | +| 5.16.1 | Description ..... | 32 | +| 5.16.2 | Architectural requirements ..... | 33 | +| 5.16.3 | Architectural baseline ..... | 33 | +| 5.16.4 | Open issues ..... | 33 | +| 5.17 | Key Issue 17: MSISDN-less MO SMS ..... | 33 | +| 5.17.1 | Description ..... | 33 | +| 5.17.2 | Architectural requirements ..... | 33 | +| 5.17.3 | Architectural baseline ..... | 33 | +| 5.17.4 | Open issues ..... | 34 | +| 6 | Solutions ..... | 34 | +| 6.1 | Solution 1: Infrequent small data transfer via NAS-SM and N6 ..... | 34 | +| 6.1.1 | Introduction ..... | 34 | +| 6.1.1.1 | General ..... | 34 | +| 6.1.1.2 | Architecture reference models ..... | 34 | +| 6.1.1.2.0 | General ..... | 34 | +| 6.1.1.2.1 | Non-roaming reference architectures ..... | 35 | +| 6.2.1.2.2 | Roaming reference architectures ..... | 35 | +| 6.1.2 | Functional Description ..... | 36 | +| 6.1.3 | Support of EPC interworking ..... | 38 | +| 6.1.4 | Procedures ..... | 39 | +| 6.1.4.0 | General ..... | 39 | +| 6.1.4.1 | PDU Session Establishment ..... | 39 | +| 6.1.4.2 | Mobile Originated Data Transport via NAS-SM and N6 ..... | 40 | +| 6.1.4.3 | Mobile Terminated Data Transport via NAS-SM and N6 ..... | 42 | +| 6.1.5 | Impacts on existing entities and interfaces ..... | 43 | +| 6.1.6 | Evaluation ..... | 44 | +| 6.2 | Solution 2: Infrequent small data transfer through NAS and a direct interface between AMF and UPF ..... | 45 | +| 6.2.1 | Introduction ..... | 45 | +| 6.2.2 | Functional Description ..... | 45 | +| 6.2.3 | Support of EPC interworking ..... | 46 | +| 6.2.4 | Procedures ..... | 46 | + +| | | | +|------------|----------------------------------------------------------------------------------------|----| +| 6.2.4.1 | Nx tunnel setup..... | 46 | +| 6.2.4.2 | Nx tunnel release ..... | 47 | +| 6.2.4.3 | MO data transport..... | 48 | +| 6.2.4.4 | MT data transport ..... | 49 | +| 6.2.4.5 | NIDD support ..... | 49 | +| 6.2.5 | Impacts on existing entities and interfaces..... | 50 | +| 6.2.6 | Evaluation..... | 51 | +| 6.3 | Solution 3: Infrequent small data transmission with no PDU session available..... | 51 | +| 6.3.1 | Introduction ..... | 51 | +| 6.3.2 | Functional Description ..... | 51 | +| 6.3.3 | Support of EPC interworking ..... | 51 | +| 6.3.4 | Procedures ..... | 51 | +| 6.3.4.1 | Registration Procedure..... | 51 | +| 6.3.4.2 | MO NSDD procedure ..... | 52 | +| 6.3.4.3 | MT Small data transmission procedure ..... | 54 | +| 6.3.5 | Impacts on existing entities and interfaces..... | 54 | +| 6.3.6 | Evaluation..... | 55 | +| 6.4 | Solution 4: Reliable Data Service Support..... | 55 | +| 6.4.1 | Introduction ..... | 55 | +| 6.4.2 | Functional Description ..... | 55 | +| 6.4.2.1 | Support of Reliable Data Service..... | 55 | +| 6.4.2.2 | Architecture to support RDS over 5GC ..... | 55 | +| 6.4.3 | Support of EPC interworking ..... | 57 | +| 6.4.4 | Procedures ..... | 58 | +| 6.4.4.1 | Registration procedure supporting reliable small data delivery over NAS ..... | 58 | +| 6.4.4.2 | RDS Configuration procedure between NEF and AF/AS ..... | 59 | +| 6.4.4.3 | MO reliable small data delivery procedure..... | 60 | +| 6.4.4.4 | MT reliable small data delivery procedure ..... | 61 | +| 6.4.5 | Impacts on existing entities and interfaces..... | 61 | +| 6.4.6 | Evaluation..... | 62 | +| 6.5 | Solution 5: Small Data Fast Path communication..... | 62 | +| 6.5.1 | Introduction ..... | 62 | +| 6.5.2 | Functional Description ..... | 62 | +| 6.5.2.1 | General..... | 62 | +| 6.5.2.2 | Mobility ..... | 63 | +| 6.5.2.3 | Security ..... | 63 | +| 6.5.2.4 | UPF and PDU Session information in the UE..... | 63 | +| 6.5.3 | Support of EPC interworking ..... | 64 | +| 6.5.4 | Procedures ..... | 65 | +| 6.5.4.1 | UE requested SDFP PDU session establishment..... | 65 | +| 6.5.4.2 | SDFP transfer initiated by UL data..... | 66 | +| 6.5.4.3 | Alternative 1: SDFP transfer initiated by DL data ..... | 67 | +| 6.5.4.3a | Alternative 2: SDFP transfer initiated by DL data ..... | 69 | +| 6.5.5 | Impacts on existing entities and interfaces..... | 70 | +| 6.5.6 | Evaluation..... | 70 | +| 6.6 | Solution 6: Small Data Communication based on Data PDU routed over the User Plane..... | 70 | +| 6.6.1 | Introduction ..... | 70 | +| 6.6.1.1 | General..... | 70 | +| 6.6.1.2 | Protocol stack for User data..... | 70 | +| 6.6.1.3 | Architecture reference models ..... | 71 | +| 6.6.2 | Functional Description ..... | 71 | +| 6.6.3 | Support of EPC interworking ..... | 72 | +| 6.6.4 | Procedures ..... | 73 | +| 6.6.4.1 | Small Data via UPF ..... | 73 | +| 6.6.4.1.1 | General ..... | 73 | +| 6.6.4.1.2 | Assumptions ..... | 73 | +| 6.6.4.1.3 | PDU Session Establishment..... | 74 | +| 6.6.4.1.4 | Mobile Originated Data Transport..... | 75 | +| 6.6.4.1.4b | Mobile Originated Data Transport, using EDT and AS based RAI..... | 76 | +| 6.6.4.1.5 | Mobile Terminated Data Transport..... | 77 | +| 6.6.4.2 | NIDD via NEF specific procedures ..... | 78 | +| 6.6.4.2.1 | General ..... | 78 | + +| | | | +|-----------|-----------------------------------------------------------------------------------|----| +| 6.6.4.2.2 | Nx Session Establishment..... | 78 | +| 6.6.4.2.3 | Mobile Terminated NIDD procedure..... | 79 | +| 6.6.4.2.4 | Mobile Originated NIDD procedure ..... | 80 | +| 6.6.5 | Impacts on existing entities and interfaces..... | 81 | +| 6.6.6 | Evaluation..... | 81 | +| 6.7 | Solution 7: Small data frequent communication ..... | 82 | +| 6.7.1 | Introduction ..... | 82 | +| 6.7.2 | Functional Description ..... | 82 | +| 6.7.3 | Support of EPC interworking ..... | 82 | +| 6.7.4 | Procedures ..... | 83 | +| 6.7.4.1 | MO transmissions ..... | 83 | +| 6.7.4.1.0 | General ..... | 83 | +| 6.7.4.1.1 | MO transmission with RRC Inactive ..... | 83 | +| 6.7.4.1.2 | MO transmission with Early Data Transmission and RRC Inactive..... | 84 | +| 6.7.4.2 | MT transmissions..... | 86 | +| 6.7.4.2.0 | General ..... | 86 | +| 6.7.4.2.1 | MT transmission with CN extended buffering at RRC Inactive..... | 86 | +| 6.7.4.2.2 | MT transmission with RAN buffering at RRC Inactive ..... | 87 | +| 6.7.5 | Impacts on existing entities and interfaces..... | 87 | +| 6.7.6 | Evaluation..... | 88 | +| 6.8 | Solution 8: Enhancing MICO for Mobile terminated data/signaling..... | 88 | +| 6.8.1 | Introduction ..... | 88 | +| 6.8.1.1 | General..... | 88 | +| 6.8.2 | Functional Description ..... | 88 | +| 6.8.3 | Support of EPC interworking ..... | 89 | +| 6.8.4 | Procedures ..... | 89 | +| 6.8.5 | Impacts on existing entities and interfaces..... | 89 | +| 6.8.6 | Evaluation..... | 89 | +| 6.9 | Solution 9: Enhanced MICO mode with Active Time..... | 90 | +| 6.9.1 | Introduction ..... | 90 | +| 6.9.2 | Functional Description ..... | 90 | +| 6.9.3 | Support of interworking ..... | 91 | +| 6.9.4 | Procedures ..... | 91 | +| 6.9.5 | Impacts on existing entities and interfaces..... | 91 | +| 6.9.6 | Evaluation..... | 92 | +| 6.10 | Solution 10: Solution for supporting High Latency Communication ..... | 92 | +| 6.10.1 | Introduction ..... | 92 | +| 6.10.2 | Functional Description ..... | 92 | +| 6.10.3 | Support of interworking ..... | 92 | +| 6.10.4 | Procedures ..... | 92 | +| 6.10.4.1 | Support for UE Reachability Notification for Mobile Terminated Communication..... | 92 | +| 6.10.4.2 | Support for UE Availability Notification Procedure after DDN Failure ..... | 93 | +| 6.10.5 | Impacts on existing entities and interfaces..... | 94 | +| 6.10.6 | Evaluation..... | 95 | +| 6.11 | Solution 11: Extended buffering in SMF and NEF ..... | 95 | +| 6.11.1 | Introduction ..... | 95 | +| 6.11.2 | Functional Description ..... | 95 | +| 6.11.3 | Support of interworking ..... | 95 | +| 6.11.4 | Procedures ..... | 95 | +| 6.11.4.1 | Data Transfer via N6 interface..... | 95 | +| 6.11.4.2 | Data Transfer via API..... | 96 | +| 6.11.5 | Impacts on existing entities and interfaces..... | 97 | +| 6.11.6 | Evaluation..... | 97 | +| 6.12 | Solution 12: Solution for Management of Enhanced Coverage for 5GC ..... | 97 | +| 6.12.1 | Introduction ..... | 97 | +| 6.12.2 | Functional Description ..... | 97 | +| 6.12.2.1 | Support of Enhanced Coverage ..... | 97 | +| 6.12.2.2 | Support of restriction of use of Enhanced Coverage ..... | 97 | +| 6.12.3 | Support of EPC interworking ..... | 98 | +| 6.12.3.1 | IDLE Mode aspects ..... | 98 | +| 6.12.3.2 | CONNECTED Mode aspects ..... | 98 | +| 6.12.4 | Procedures ..... | 98 | + +| | | | +|------------|-------------------------------------------------------------------------------|-----| +| 6.12.4.1 | Procedure for restriction of use of Enhanced Coverage ..... | 98 | +| 6.12.4.2 | Enhanced Coverage Restriction Control and via NEF ..... | 99 | +| 6.12.5 | Impacts on existing entities and interfaces ..... | 100 | +| 6.12.6 | Evaluation ..... | 101 | +| 6.13 | Solution 13: SCEF+NEF Node ..... | 101 | +| 6.13.1 | Introduction ..... | 101 | +| 6.13.2 | Functional Description ..... | 102 | +| 6.13.3 | Support of EPC interworking ..... | 103 | +| 6.13.4 | Procedures ..... | 103 | +| 6.13.5 | Impacts on existing entities and interfaces ..... | 103 | +| 6.13.6 | Evaluation ..... | 103 | +| 6.14 | Solution 14: APISupportCapability service ..... | 103 | +| 6.14.1 | Introduction ..... | 103 | +| 6.14.2 | Functional Description ..... | 103 | +| 6.14.3 | Support of EPC interworking ..... | 105 | +| 6.14.4 | Procedures ..... | 105 | +| 6.14.4.1 | Subscribe and Notify service operations information flow ..... | 105 | +| 6.14.4.2 | Unsubscribe service operation information flow ..... | 106 | +| 6.14.4.3 | Query service operation information flow ..... | 107 | +| 6.14.5 | Impacts on existing entities and interfaces ..... | 108 | +| 6.14.6 | Evaluation ..... | 108 | +| 6.15 | Solution 15: External parameter provisioning in the 5GC ..... | 109 | +| 6.15.1 | Introduction ..... | 109 | +| 6.15.2 | Functional Description ..... | 109 | +| 6.15.3 | Support of EPC interworking ..... | 109 | +| 6.15.4 | Procedures ..... | 110 | +| 6.15.5 | Impacts on existing entities and interfaces ..... | 111 | +| 6.15.6 | Evaluation ..... | 112 | +| 6.16 | Solution 16: UE assisted Inter-UE QoS Support for Data over NAS ..... | 112 | +| 6.16.1 | Introduction ..... | 112 | +| 6.16.2 | Functional Description ..... | 112 | +| 6.16.3 | Support of EPC interworking ..... | 113 | +| 6.16.4 | Procedures ..... | 113 | +| 6.16.4.1 | QoS Index configuration during Registration Procedure ..... | 113 | +| 6.16.4.2 | Using QoS index in MO Data over NAS ..... | 113 | +| 6.16.5 | Impacts on existing entities and interfaces ..... | 114 | +| 6.16.6 | Evaluation ..... | 115 | +| 6.17 | Solution 17: UE-Driven Packet Classification ..... | 115 | +| 6.17.1 | Introduction ..... | 115 | +| 6.17.2 | Functional Description ..... | 115 | +| 6.17.3 | Support of EPC interworking ..... | 115 | +| 6.17.4 | Procedures ..... | 116 | +| 6.17.5 | Impacts on existing entities and interfaces ..... | 117 | +| 6.17.6 | Evaluation ..... | 117 | +| 6.18 | Solution 18: QoS control for unstructured PDU sessions ..... | 118 | +| 6.18.1 | Introduction ..... | 118 | +| 6.18.2 | Functional Description ..... | 118 | +| 6.18.2.1 | QoS Flow mapping for unstructured PDU Session ..... | 118 | +| 6.18.2.2 | QoS Rule for Unstructured PDU Session ..... | 119 | +| 6.18.2.2.1 | Achieving Reflective QoS ..... | 119 | +| 6.18.2.3 | Field position based Packet Filters ..... | 119 | +| 6.18.3 | Support of EPC interworking ..... | 120 | +| 6.18.4 | Procedures ..... | 120 | +| 6.18.5 | Impacts on existing entities and interfaces ..... | 122 | +| 6.18.6 | Evaluation ..... | 122 | +| 6.19 | Solution 19: 5GS UP Optimization for Infrequent Small Data Transmission ..... | 122 | +| 6.19.1 | Introduction ..... | 122 | +| 6.19.2 | Functional Description ..... | 124 | +| 6.19.2.1 | General ..... | 124 | +| 6.19.2.2 | Mobility ..... | 124 | +| 6.19.2.3 | Security ..... | 124 | +| 6.19.3 | Support of EPC Interworking ..... | 124 | + +| | | | +|------------|-----------------------------------------------------------------------------------------------|-----| +| 6.19.4 | Procedures ..... | 125 | +| 6.19.4.1 | PDU Session Establishment..... | 125 | +| 6.19.4.2 | UL data transmission from CM-IDLE..... | 126 | +| 6.19.4.2b | UL data transmission from CM-IDLE with Early Data Transmission..... | 127 | +| 6.19.4.3 | DL data transmission..... | 128 | +| 6.19.4.4 | Connection Suspend procedure ..... | 130 | +| 6.19.4.5 | CN-initiated UP Deactivation procedure..... | 130 | +| 6.19.5 | Impacts on existing entities and interfaces..... | 132 | +| 6.19.6 | Evaluation..... | 132 | +| 6.20 | Solution 20: NIDD API support by SMF for infrequent small data transfer via NAS-SM ..... | 133 | +| 6.20.1 | Introduction ..... | 133 | +| 6.20.1.1 | General..... | 133 | +| 6.20.1.2 | Architecture reference models..... | 133 | +| 6.20.1.2.1 | General ..... | 133 | +| 6.20.1.2.2 | Non-roaming reference architecture..... | 133 | +| 6.20.1.2.3 | Roaming reference architectures..... | 133 | +| 6.20.2 | Functional Description ..... | 134 | +| 6.20.3 | Support of EPC interworking ..... | 134 | +| 6.20.4 | Procedures ..... | 135 | +| 6.20.4.1 | PDU Session Establishment (non-roaming) ..... | 135 | +| 6.20.4.2 | PDU Session Establishment (home-routed roaming) ..... | 136 | +| 6.20.4.3 | Mobile Originated Data Transport via NAS-SM and NIDD API ..... | 137 | +| 6.20.4.4 | Mobile Terminated Data Transport via NAS-SM and NIDD API ..... | 138 | +| 6.20.4.5 | NIDD configuration procedure ..... | 140 | +| 6.20.5 | Impacts on existing entities and interfaces..... | 142 | +| 6.20.6 | Evaluation..... | 142 | +| 6.21 | Solution 21: NIDD service activation ..... | 142 | +| 6.21.1 | Introduction ..... | 142 | +| 6.21.2 | Functional Description ..... | 143 | +| 6.21.2.1 | General..... | 143 | +| 6.21.2.2 | Mobility ..... | 143 | +| 6.21.3 | Support of EPC Interworking ..... | 143 | +| 6.21.4 | Procedures ..... | 143 | +| 6.21.4.1 | NIDD service activation for AMF based solution..... | 143 | +| 6.21.4.2 | NIDD service activation for SMF based solution..... | 145 | +| 6.21.4.3 | Bulk subscription of NIDD service activation..... | 146 | +| 6.21.5 | Impacts on existing entities and interfaces..... | 147 | +| 6.21.6 | Evaluation..... | 147 | +| 6.22 | Solution 22: eDRX for CM-IDLE state in 5GS ..... | 147 | +| 6.22.1 | Introduction ..... | 147 | +| 6.22.2 | Functional Description ..... | 147 | +| 6.22.3 | Support of EPC interworking ..... | 148 | +| 6.22.4 | Procedures ..... | 148 | +| 6.22.5 | Impacts on existing entities and interfaces..... | 148 | +| 6.22.6 | Evaluation..... | 148 | +| 6.23 | Solution 23: MICO Mode Management for Expected Application Behaviour ..... | 148 | +| 6.23.1 | Introduction ..... | 148 | +| 6.23.2 | Functional Description ..... | 149 | +| 6.23.3 | Support of interworking ..... | 149 | +| 6.23.4 | Procedures ..... | 149 | +| 6.23.5 | Impacts on existing entities and interfaces..... | 150 | +| 6.23.6 | Evaluation..... | 150 | +| 6.24 | Solution 24: High latency communication with extended buffering and event notifications ..... | 151 | +| 6.24.1 | Introduction ..... | 151 | +| 6.24.2 | Functional Description ..... | 151 | +| 6.24.3 | Support of EPC interworking ..... | 152 | +| 6.24.4 | Procedures ..... | 152 | +| 6.24.4.1 | Extended buffering ..... | 152 | +| 6.24.4.1.1 | General ..... | 152 | +| 6.24.4.1.2 | DL data in CM-IDLE mode ..... | 152 | +| 6.24.4.1.3 | DL data in CM-CONNECTED mode without CN extended buffering ..... | 154 | +| 6.24.4.1.4 | DL data in CM-CONNECTED mode with CN Extended buffering ..... | 154 | + +| | | | +|------------|-------------------------------------------------------------------------------|-----| +| 6.24.4.2 | Notification procedures..... | 156 | +| 6.24.4.2.1 | General ..... | 156 | +| 6.24.4.2.2 | Event Subscription and Notification of UE reachability..... | 156 | +| 6.24.4.2.3 | Notification of Availability after DDN failure..... | 157 | +| 6.24.4.2.4 | Configuration for notification related approaches ..... | 160 | +| 6.24.4.3 | Notification of Availability after MT control plane signalling..... | 161 | +| 6.24.5 | Impacts on existing entities and interfaces..... | 163 | +| 6.24.6 | Evaluation..... | 164 | +| 6.25 | Solution 25: HLCom buffering and event notification support for CM-IDLE ..... | 165 | +| 6.25.1 | Introduction ..... | 165 | +| 6.25.2 | Functional Description ..... | 165 | +| 6.25.3 | Support of EPC interworking ..... | 165 | +| 6.25.4 | Procedures ..... | 165 | +| 6.25.4.1 | Extended data buffering at UPF ..... | 165 | +| 6.25.4.1A | Extended data buffering at NEF ..... | 167 | +| 6.25.4.2 | AF notification from AMF ..... | 167 | +| 6.25.4.2.1 | General ..... | 167 | +| 6.25.4.2.2 | Event Subscription of UE reachability..... | 167 | +| 6.25.4.2.3 | MT data transfer with Notification of UE availability ..... | 167 | +| 6.25.4.2.4 | Event Subscription of "Availability Notification after DDN Failure" ..... | 168 | +| 6.25.4.2.5 | Notification about "Availability Notification after DDN Failure" ..... | 168 | +| 6.25.4.3 | AF notification from SMF ..... | 168 | +| 6.25.4.3.1 | Application Notification overall procedure..... | 168 | +| 6.25.4.3.2 | Event subscription for data delivery status ..... | 169 | +| 6.25.4.3.3 | Monitoring report procedure for data delivery status..... | 170 | +| 6.25.5 | Impacts on existing entities and interfaces..... | 172 | +| 6.25.6 | Evaluation..... | 172 | +| 6.26 | Solution 26: Expected UE Behaviour provisioning for CIoT ..... | 172 | +| 6.26.1 | Introduction ..... | 172 | +| 6.26.2 | Functional Description ..... | 173 | +| 6.26.3 | Support of EPC interworking ..... | 174 | +| 6.26.4 | Procedures ..... | 174 | +| 6.26.5 | Impacts on existing entities and interfaces..... | 174 | +| 6.26.6 | Evaluation..... | 175 | +| 6.27 | Solution 27: Reuse of EPS Overload Control Mechanisms ..... | 175 | +| 6.27.1 | Introduction ..... | 175 | +| 6.27.2 | Functional Description ..... | 175 | +| 6.27.2.1 | Small Data Rate Control..... | 175 | +| 6.27.2.2 | Service Gap Control..... | 175 | +| 6.27.2.3 | AMF and SMF Overload..... | 175 | +| 6.27.2.4 | Control plane data back-off timer..... | 176 | +| 6.27.2.5 | Low Access Priority..... | 176 | +| 6.27.3 | Support of EPC interworking ..... | 176 | +| 6.27.4 | Procedures ..... | 176 | +| 6.27.4.1 | Small Data Rate Control ..... | 176 | +| 6.27.4.1.1 | General ..... | 176 | +| 6.27.4.2 | Service Gap Control..... | 177 | +| 6.27.4.2.1 | General ..... | 177 | +| 6.27.4.3 | Overload procedure..... | 177 | +| 6.27.4.3.1 | General ..... | 177 | +| 6.27.4.4 | Low access priority ..... | 177 | +| 6.27.4.3.1 | General ..... | 177 | +| 6.27.4.5 | Control plane data back-off timer procedure ..... | 177 | +| 6.27.5 | Impacts on existing entities and interfaces..... | 177 | +| 6.27.6 | Evaluation..... | 178 | +| 6.28 | Solution 28: SMF assisted NG-RAN information ..... | 178 | +| 6.28.1 | Introduction ..... | 178 | +| 6.28.2 | Functional Description ..... | 178 | +| 6.28.3 | Support of EPC interworking ..... | 179 | +| 6.28.4 | Procedures ..... | 179 | +| 6.28.5 | Impacts on existing entities and interfaces..... | 181 | +| 6.28.6 | Evaluation..... | 182 | + +| | | | +|------------|----------------------------------------------------------------------------------------------|-----| +| 6.29 | Solution 29: User Plane data transmission with ConnectionLess signalling ..... | 182 | +| 6.29.1 | Introduction ..... | 182 | +| 6.29.2 | Functional Description ..... | 182 | +| 6.29.3 | Support of EPC interworking ..... | 186 | +| 6.29.4 | Procedures ..... | 186 | +| 6.29.4.1 | Identities..... | 186 | +| 6.29.4.1.1 | UPF CL SERVICE Id (UCLSI) ..... | 186 | +| 6.29.4.2 | Assumptions..... | 186 | +| 6.29.4.3 | Procedures..... | 186 | +| 6.29.4.3.1 | Set-up of a PDU sessions with Connectionless mode data transfer on the RAN-Core interface .. | 186 | +| 6.29.4.3.2 | UE connectionless uplink data transfer..... | 189 | +| 6.29.4.3.3 | UE connectionless downlink data transfer..... | 190 | +| 6.29.4.3.4 | Paging for UE connectionless downlink data transfer ..... | 192 | +| 6.29.4.3.5 | Mobility support..... | 193 | +| 6.29.4.4.6 | UPF Triggered Release and Redirection During UE Connectionless Active Mode..... | 193 | +| 6.29.5 | Impacts on existing entities and interfaces..... | 194 | +| 6.29.5.1 | Impact on interfaces..... | 194 | +| 6.29.5.2 | Impact on entities..... | 194 | +| 6.29.6 | Evaluation..... | 194 | +| 6.30 | Solution 30: NEF based infrequent small data transfer via NAS-SM..... | 194 | +| 6.30.1 | Introduction ..... | 194 | +| 6.30.1.1 | General..... | 194 | +| 6.30.1.2 | Architecture reference models ..... | 195 | +| 6.30.1.2.0 | General ..... | 195 | +| 6.30.1.2.1 | Non-roaming reference architectures ..... | 195 | +| 6.30.1.2.2 | Roaming reference architectures..... | 196 | +| 6.30.2 | Functional Description ..... | 196 | +| 6.30.3 | Support of EPC interworking ..... | 196 | +| 6.30.4 | Procedures ..... | 197 | +| 6.30.4.1 | PDU Session Establishment (non-roaming) ..... | 197 | +| 6.30.4.2 | PDU Session Establishment (home-routed roaming) ..... | 198 | +| 6.30.4.3 | Mobile Originated Data Transport via NAS-SM and N6 (NEF Anchored)..... | 200 | +| 6.30.4.4 | Mobile Terminated Data Transport via NAS-SM and N6 (NEF Anchored)..... | 200 | +| 6.30.4.5 | NIDD Configuration for Data Transport via NAS-SM ..... | 200 | +| 6.30.4.6 | SMF-NEF Connection ..... | 200 | +| 6.30.4.7 | NIDD Configuration by NEF ..... | 201 | +| 6.30.5 | Impacts on existing entities and interfaces..... | 202 | +| 6.30.6 | Evaluation..... | 202 | +| 6.31 | Solution 31: Deferring of Periodic Registration Update ..... | 202 | +| 6.31.1 | Introduction ..... | 202 | +| 6.31.2 | Functional Description ..... | 202 | +| 6.31.3 | Support of interworking ..... | 203 | +| 6.31.4 | Procedures ..... | 203 | +| 6.31.5 | Impacts on existing entities and interfaces..... | 203 | +| 6.31.6 | Evaluation..... | 204 | +| 6.32 | Solution 32: MO Data Buffering in the UE ..... | 204 | +| 6.32.1 | Introduction ..... | 204 | +| 6.32.2 | Functional Description ..... | 204 | +| 6.32.3 | Support of EPC interworking ..... | 204 | +| 6.32.4 | Procedures ..... | 204 | +| 6.32.5 | Impacts on existing entities and interfaces..... | 205 | +| 6.32.6 | Evaluation..... | 205 | +| 6.33 | Solution 33: Delayed Paging Response ..... | 205 | +| 6.33.1 | Introduction ..... | 205 | +| 6.33.2 | Functional Description ..... | 206 | +| 6.33.3 | Support of EPC interworking ..... | 206 | +| 6.33.4 | Procedures ..... | 206 | +| 6.33.5 | Impacts on existing entities and interfaces..... | 207 | +| 6.33.6 | Evaluation..... | 208 | +| 6.34 | Solution 34: Provisioning of UE TX power saving parameters..... | 208 | +| 6.34.1 | Introduction ..... | 208 | +| 6.34.2 | Functional Description ..... | 208 | + +| | | | +|------------|---------------------------------------------------------------------------------------------|-----| +| 6.34.3 | Support of EPC interworking ..... | 209 | +| 6.34.4 | Procedures ..... | 209 | +| 6.34.5 | Impacts on existing entities and interfaces ..... | 209 | +| 6.34.6 | Evaluation ..... | 209 | +| 6.35 | Solution 35: Small data delivery ..... | 209 | +| 6.35.1 | Introduction ..... | 209 | +| 6.35.2 | Functional Description ..... | 209 | +| 6.35.2.1 | Architecture ..... | 209 | +| 6.35.2.2 | Small data delivery ..... | 211 | +| 6.35.3 | Support of EPC interworking ..... | 212 | +| 6.35.4 | Procedures ..... | 212 | +| 6.35.4.1 | Connection establishment for UPF and NEF ..... | 212 | +| 6.35.4.2 | MO small data transfer ..... | 214 | +| 6.35.5 | Impacts on existing entities and interfaces ..... | 215 | +| 6.35.6 | Evaluation ..... | 215 | +| 6.36 | Solution 36: CM-CONNECTED with RRC Inactive state for frequent small data transmission..... | 215 | +| 6.36.1 | Introduction ..... | 215 | +| 6.36.2 | Functional Description ..... | 215 | +| 6.36.3 | Support of EPC interworking ..... | 216 | +| 6.36.4 | Procedures ..... | 216 | +| 6.36.4.1 | Connection Inactive procedure ..... | 216 | +| 6.36.4.2 | Connection Resume procedure ..... | 216 | +| 6.36.4.3 | CN-initiated deactivation of UP connection when the UE is in RRC inactive state ..... | 217 | +| 6.36.5 | Impacts on existing entities and interfaces ..... | 219 | +| 6.36.6 | Evaluation ..... | 219 | +| 6.37 | Solution 37: Monitoring ..... | 219 | +| 6.37.1 | Introduction ..... | 219 | +| 6.37.2 | Functional Description ..... | 219 | +| 6.37.3 | Support of EPC interworking ..... | 220 | +| 6.37.3.1 | General ..... | 220 | +| 6.37.3.2 | Interworking with N26 interface ..... | 220 | +| 6.37.3.3 | Interworking without N26 interface ..... | 220 | +| 6.37.4 | Procedures ..... | 220 | +| 6.37.4.1 | Monitoring events at AMF ..... | 220 | +| 6.37.4.2 | Monitoring events at UDM ..... | 220 | +| 6.37.4.3 | Monitoring events at PCF ..... | 220 | +| 6.37.4.3.1 | General ..... | 220 | +| 6.37.4.3.2 | PCF service operations information flow ..... | 221 | +| 6.37.5 | Impacts on existing entities and interfaces ..... | 222 | +| 6.37.6 | Evaluation ..... | 222 | +| 6.38 | Solution 38: eDRX RRC_INACTIVE STATE in 5GS ..... | 222 | +| 6.38.1 | Introduction ..... | 222 | +| 6.38.2 | Functional Description ..... | 222 | +| 6.38.3 | Support of EPC interworking ..... | 223 | +| 6.38.4 | Procedures ..... | 223 | +| 6.38.5 | Impacts on existing entities and interfaces ..... | 223 | +| 6.38.6 | Evaluation ..... | 224 | +| 6.39 | Solution 39: UE availability after DDN failure for multiple AFs ..... | 224 | +| 6.39.1 | Introduction ..... | 224 | +| 6.39.2 | Functional Description ..... | 224 | +| 6.39.3 | Support of EPC interworking ..... | 224 | +| 6.39.4 | Procedures ..... | 225 | +| 6.39.4.1 | Event Configuration ..... | 225 | +| 6.39.4.2 | Notification ..... | 226 | +| 6.39.5 | Impacts on existing entities and interfaces ..... | 227 | +| 6.39.6 | Evaluation ..... | 227 | +| 6.40 | Solution 40: Infrequent small data transmission with temporary PDU session ..... | 228 | +| 6.40.1 | Introduction ..... | 228 | +| 6.40.2 | Functional Description ..... | 228 | +| 6.40.3 | Support of EPC interworking ..... | 228 | +| 6.40.4 | Procedures ..... | 229 | +| 6.40.5 | Impacts on existing entities and interfaces ..... | 230 | + +| | | | +|------------|-----------------------------------------------------------------------------------------------------|-----| +| 6.40.6 | Evaluation..... | 230 | +| 6.41 | Solution 41: Combining RRC-INACTIVE and 5G UP optimization..... | 231 | +| 6.41.1 | Introduction ..... | 231 | +| 6.41.2 | Functional Description ..... | 231 | +| 6.41.3 | Support of EPC interworking ..... | 232 | +| 6.41.4 | Procedures ..... | 232 | +| 6.41.5 | Impacts on existing entities and interfaces..... | 232 | +| 6.41.6 | Evaluation..... | 232 | +| 6.42 | Solution 42: NAS based Redirection between Core Networks..... | 232 | +| 6.42.1 | Introduction ..... | 232 | +| 6.42.2 | Functional Description ..... | 232 | +| 6.42.3 | Support of EPC interworking ..... | 232 | +| 6.42.4 | Procedures ..... | 233 | +| 6.42.4.1 | Redirection using NAS indication ..... | 233 | +| 6.42.4.1.1 | General ..... | 233 | +| 6.42.4.1.2 | Redirection from EPC to 5GC network ..... | 233 | +| 6.42.4.1.3 | Redirection from 5GC to EPC network ..... | 234 | +| 6.42.4.1.4 | Interaction with Steering of Roaming ..... | 234 | +| 6.42.5 | Impacts on existing entities and interfaces..... | 234 | +| 6.42.6 | Evaluation..... | 235 | +| 6.43 | Solution 43: RRC based Redirection between Core networks..... | 235 | +| 6.43.1 | Introduction ..... | 235 | +| 6.43.2 | Functional Description ..... | 235 | +| 6.43.3 | Support of EPC interworking ..... | 235 | +| 6.43.4 | Procedures ..... | 235 | +| 6.43.4.1 | Redirection using RRC indication ..... | 235 | +| 6.43.4.1.1 | General ..... | 235 | +| 6.43.4.1.2 | Redirection from EPC to 5GC network ..... | 236 | +| 6.43.4.1.3 | Redirection from 5GC to EPC network ..... | 237 | +| 6.43.5 | Impacts on existing entities and interfaces..... | 237 | +| 6.43.6 | Evaluation..... | 238 | +| 6.44 | Solution 44: C-IoT UE Core Network selection based on S-NSSAIs ..... | 238 | +| 6.44.1 | Introduction ..... | 238 | +| 6.44.2 | Functional Description ..... | 238 | +| 6.44.2.1 | General..... | 238 | +| 6.44.2.2 | 5G Cellular IoT support information based on S-NSSAIs ..... | 239 | +| 6.44.3 | Support of EPC interworking ..... | 239 | +| 6.44.4 | Procedures ..... | 239 | +| 6.44.5 | Impacts on existing entities and interfaces..... | 241 | +| 6.44.6 | Evaluation..... | 241 | +| 6.45 | Solution 45: Core Network Type and Node Selection for CIoT UE Using Explicit Indications ..... | 241 | +| 6.45.1 | Introduction ..... | 241 | +| 6.45.2 | Functional Description ..... | 241 | +| 6.45.3 | Support of EPC interworking ..... | 241 | +| 6.45.4 | Procedures ..... | 241 | +| 6.45.4.1 | Registration Procedure..... | 241 | +| 6.45.4.2 | Core network type selection at UE and AMF selection at RAN ..... | 242 | +| 6.45.5 | Impacts on existing entities and interfaces..... | 242 | +| 6.45.6 | Evaluation..... | 243 | +| 6.46 | Solution 46: Network controlled UL data transmission delay ..... | 243 | +| 6.46.1 | Introduction ..... | 243 | +| 6.46.2 | Functional Description ..... | 243 | +| 6.46.3 | Support of EPC interworking ..... | 243 | +| 6.46.4 | Procedures ..... | 243 | +| 6.46.5 | Impacts on existing entities and interfaces..... | 244 | +| 6.46.6 | Evaluation..... | 245 | +| 6.47 | Solution 47: Improved Signalling/Data plane separation for Data over NAS small data solutions ..... | 245 | +| 6.47.1 | Introduction ..... | 245 | +| 6.47.2 | Functional Description ..... | 245 | +| 6.47.3 | Support of EPC interworking ..... | 245 | +| 6.47.4 | Procedures ..... | 245 | +| 6.47.5 | Impacts on existing entities and interfaces..... | 246 | + +| | | | +|----------|----------------------------------------------------------------------------------------------------|-----| +| 6.47.6 | Evaluation..... | 246 | +| 6.48 | Solution 48: NB-IoT idle mode inter-RAT mobility reusing EPS features ..... | 247 | +| 6.48.1 | Introduction ..... | 247 | +| 6.48.2 | Functional Description ..... | 247 | +| 6.48.2.1 | General..... | 247 | +| 6.48.2.2 | UE Radio Capability Handling ..... | 247 | +| 6.48.2.3 | PDU Session Handling ..... | 247 | +| 6.48.2.4 | Determining RAT Type Change..... | 247 | +| 6.48.3 | Support of EPC interworking ..... | 248 | +| 6.48.4 | Procedures ..... | 248 | +| 6.48.4.1 | RAT change with mobility between 5GC and EPC with N26 ..... | 248 | +| 6.48.4.2 | RAT change with mobility between 5GC and EPC without N26 ..... | 248 | +| 6.48.4.3 | RAT change without mobility between 5GC and EPC ..... | 249 | +| 6.48.4.4 | Determining RAT Type Change..... | 249 | +| 6.48.5 | Impacts on existing entities and interfaces..... | 249 | +| 6.48.6 | Evaluation..... | 249 | +| 6.49 | Solution 49: Support for RDS with infrequent small data transmission solutions #1, 2, 3..... | 250 | +| 6.49.1 | Introduction ..... | 250 | +| 6.49.2 | Functional Description ..... | 250 | +| 6.49.3 | Support of EPC interworking ..... | 251 | +| 6.49.4 | Procedures ..... | 252 | +| 6.49.5 | Impacts on existing entities and interfaces..... | 252 | +| 6.49.6 | Evaluation..... | 252 | +| 6.50 | Solution 50: AF Notifications after DDN failure ..... | 252 | +| 6.50.1 | Introduction ..... | 252 | +| 6.50.2 | Functional Description ..... | 252 | +| 6.50.3 | Support of EPC interworking ..... | 253 | +| 6.50.4 | Procedures ..... | 253 | +| 6.50.4.1 | Event Configuration..... | 253 | +| 6.50.4.2 | Notification ..... | 254 | +| 6.50.5 | Impacts on existing entities and interfaces..... | 255 | +| 6.50.6 | Evaluation..... | 256 | +| 6.51 | Solution 51: Core Network steering via CN type selection rules configuration/reconfiguration ..... | 256 | +| 6.51.1 | Introduction ..... | 256 | +| 6.51.2 | Functional Description ..... | 256 | +| 6.51.3 | Support of EPC interworking ..... | 258 | +| 6.51.4 | Procedures ..... | 258 | +| 6.51.5 | Impacts on existing entities and interfaces..... | 258 | +| 6.51.6 | Evaluation..... | 258 | +| 6.52 | Solution 52: Inter-UE QoS differentiation based on retrieval of UE Context ..... | 258 | +| 6.52.1 | Introduction ..... | 258 | +| 6.52.2 | Functional Description ..... | 259 | +| 6.52.3 | Support of EPC interworking ..... | 259 | +| 6.52.4 | Procedures ..... | 259 | +| 6.52.4.1 | Provision of UE Context to AMF ..... | 259 | +| 6.52.4.2 | Retrieval of UE Context from AMF and Inter-UE QoS differentiation ..... | 260 | +| 6.52.5 | Impacts on existing entities and interfaces..... | 261 | +| 6.52.6 | Evaluation..... | 261 | +| 7 | Evaluation ..... | 261 | +| 7.1 | Key Issue 1: Support for infrequent small data transmission..... | 261 | +| 7.2 | Key Issue 2: Frequent small data communication ..... | 263 | +| 7.2.1 | Overview ..... | 263 | +| 7.2.2 | Enhancements of existing procedures ..... | 264 | +| 7.2.3 | Optimised UP data solutions ..... | 264 | +| 7.2.4 | UPF-NEF interface ..... | 264 | +| 7.3 | Key Issue 3: High latency communication ..... | 264 | +| 7.4 | Key Issue 4: Power Saving Functions..... | 266 | +| 7.5 | Key Issue 5: UE TX Power Saving Functions ..... | 266 | +| 7.6 | Key Issue 6: Management of Enhanced Coverage..... | 267 | +| 7.7 | Key Issue 7: Overload Control for small data..... | 267 | +| 7.8 | Key Issue 8: Support of the Reliable Data Service ..... | 267 | + +| | | | +|----------|--------------------------------------------------------------------------------|-----| +| 7.9 | Key Issue 9: Support of common north-bound APIs for EPC-5GC Interworking ..... | 267 | +| 7.10 | Key Issue 10: Network Parameter Configuration API via NEF ..... | 267 | +| 7.10.1 | Overview ..... | 267 | +| 7.10.2 | Evaluation Relative to Key Issue 3 (High Latency Communication) ..... | 268 | +| 7.10.3 | Evaluation Relative to Key Issue 4 (Power Savings Functions) ..... | 268 | +| 7.11 | Key Issue 11: Monitoring..... | 268 | +| 7.12 | Key Issue 12: Inter-RAT mobility support to/from NB-IoT ..... | 268 | +| 7.13 | Key Issue 13: Support for Expected UE Behaviour..... | 268 | +| 7.14 | Key Issue 14: QoS Support for NB-IoT ..... | 269 | +| 7.15 | Key Issue 15: Core Network selection for Cellular IoT ..... | 269 | +| 7.16 | Key Issue 16: Support of Group communication and messaging ..... | 270 | +| 7.17 | Key Issue 17: MSISDN-less MO SMS..... | 270 | +| 8 | Conclusions..... | 270 | +| 8.1 | Key Issue 1: Support for infrequent small data transmission..... | 270 | +| 8.2 | Key Issue 2: Frequent small data communication ..... | 270 | +| 8.3 | Key Issue 3: High latency communication ..... | 270 | +| 8.4 | Key Issue 4: Power Saving Functions..... | 271 | +| 8.5 | Key Issue 5: UE TX Power Saving Functions ..... | 271 | +| 8.6 | Key Issue 6: Management of Enhanced Coverage..... | 271 | +| 8.7 | Key Issue 7: Overload Control for small data..... | 271 | +| 8.8 | Key Issue 8: Support of the Reliable Data Service ..... | 272 | +| 8.9 | Key Issue 9: Support of common north-bound APIs for EPC-5GC Interworking ..... | 272 | +| 8.10 | Key Issue 10: Network Parameter Configuration API via NEF ..... | 272 | +| 8.11 | Key Issue 11: Monitoring..... | 272 | +| 8.12 | Key Issue 12: Inter-RAT mobility support to/from NB-IoT ..... | 272 | +| 8.13 | Key Issue 13: Support for Expected UE Behaviour..... | 272 | +| 8.14 | Key Issue 14: QoS Support for NB-IoT ..... | 273 | +| 8.15 | Key Issue 15: Core Network selection for Cellular IoT ..... | 273 | +| 8.16 | Key Issue 16: Support of Group communication and messaging ..... | 273 | +| 8.17 | Key Issue 17: MSISDN-less MO SMS..... | 273 | +| Annex A: | Change history ..... | 274 | + +--- + +## 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 + +This technical report studies and evaluates architecture enhancements to address the following objectives: + +## **Objective I: Enable CIoT/MTC functionalities in 5G CN.** + +The objective is to study how to support identified CioT/MTC functionalities in 5G CN with potential connectivity to WB-EUTRA (eMTC) and/or NB-IoT for 5GS capable devices. + +The following CIoT/MTC functionalities need to be evaluated and studied how to enable them in 5G CN, if needed: + +- Equivalent overall functionalities as provided by SCEF for CIoT/MTC. +- Monitoring. +- Small data transmission (infrequent and frequent small data transmission including frequent small data transmission from tracking devices). +- Additional power saving functions unless those are supported for 5G system in Rel-15. +- Non-IP Data Delivery. +- Overload control (as relevant in 5G CN). +- Support of Coverage enhancement including adaptations in 5G CN required to support latencies. +- Equivalent to Group communication and messaging. +- Reliable communication via functionality equivalent to SCEF. +- Inter-RAT mobility support to/from NB-IoT. +- High latency communication. +- Include location services procedures for IoT in 5G location services. + +NOTE: Attach without PDN connection and non-IP PDN Connection type is already supported in 5G CN (TS 23.501 [5]). + +Ensure that regulatory requirements can be fulfilled at the same level as in EPC. + +## **Objective II: Co-existence and migration from EPC based eMTC/NB-IoT to 5GCN.** + +Study solutions for coexistence and migration from EPC towards 5G CN for eMTC/NB-IoT. + +This objective will study solutions where the same service is offered to some UEs connected to EPC and some UEs connected to 5G CN e.g. using SCEF and equivalent functionalities in 5GCN. Solutions that assume that 5G CN needs to support EPC NAS signaling for legacy IoT devices access are not considered. + +Any modifications in the EPC-5GC interworking "baseline" specific to CIOT will also be discussed as part of Objective II. + +## **Objective III: 5G System enhancements to address 5G service requirements (based on TS 22.261 [2] and TR 38.913 [3]).** + +To study system architecture enhancements to address related service requirements defined in TS 22.261 [2] and RAN requirements defined in TR 38.913 [3] and how to enable them in 5G CN, if needed. At least the following service requirements have been identified: + +- Enable the change of association between subscription and address/number of an IoT device within same operator and in between different operators. +- Restricted Registration procedure to allow IoT device provisioning. + +Any system implications for the RAN will be coordinated with RAN WGs. + +This study is not going to study enhancements to EPC. + +## 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.261: "Service requirements for next generation new services and markets". +- [3] 3GPP TR 38.913: "Study on scenarios and requirements for next generation access technologies". +- [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.501: "System Architecture for the 5G System". +- [6] 3GPP TS 23.682: "Architecture enhancements to facilitate communications with packet data networks and applications". +- [7] 3GPP TS 23.502: "Procedures for the 5G System". +- [8] 3GPP TS 24.250: "Protocol for Reliable Data Service between UE and SCEF; Stage 3". +- [9] 3GPP TS 29.122: "T8 reference point for northbound Application Programming Interfaces (APIs)". +- [10] 3GPP TS 24.501: "Non-Access-Stratum (NAS) protocol for 5G System (5GS)". +- [11] Void. +- [12] Open Mobile Alliance: "Lightweight Machine to Machine Requirements, V1.0". +- [13] MQTT For Sensor Networks, (MQTT-SN): [www.mqtt.org](http://www.mqtt.org). +- [14] IETF RFC 6347: "Rescorla et al.: Datagram Transport Layer Security", IETF, January 2012. +- [15] 3GPP TR 38.804: "Study on New Radio Access Technology; Radio Interface Protocol Aspects". +- [16] 3GPP TS 29.244: "Interface between the Control Plane and the User Plane nodes". +- [17] 3GPP TS 29.303: "Domain Name System Procedures; Stage 3". +- [18] 3GPP TS 29.510: "5G System; Network function repository services; Stage 3". +- [19] 3GPP TS 38.300: "NR; NR and NG-RAN Overall Description; Stage 2". +- [20] 3GPP TS 23.222: "Functional architecture and information flows to support Common API Framework for 3GPP Northbound APIs". +- [21] 3GPP TS 23.122: "Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode". +- [22] 3GPP TS 36.413: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP)". +- [23] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification". + +- [24] 3GPP TS 33.401: "3GPP System Architecture Evolution (SAE); Security architecture". +- [25] 3GPP TS 33.501: "Security architecture and procedures for 5G System". +- [26] 3GPP TS 29.502: "Session Management Services; Stage 3". +- [27] 3GPP TS 36.321: "Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification". + +--- + +## 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] 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 Symbols + +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.3 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [1] apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1]. + +--- + +## 4 Architectural Assumptions and Principles + +The following architecture assumptions and principles apply: + +- The assumption is that WB-E-UTRA and NB-IoT are connected to 5GC via N2/N3. +- Regulatory requirements (e.g. LI) shall be fulfilled at the same level as in EPC. +- No architectural enhancements made to EPC. +- APIs for CIoT related services provided to the SCS/AS shall be common for UEs connected to EPS and 5GS and accessed via the HPLMN. + +NOTE 1: The level of support of the API may differ between EPS and 5GS. + +- Notifications and data from NFs in the VPLMN to the NEF can be routed through an IWK-NEF, similar to the IWK-SCEF in EPC. + +NOTE 2: Some solutions documented in this TR may not necessarily show the IWK-NEF. It is however assumed that IWK-NEF support will be added during the normative phase. + +- Support for small data delivery using IP data and Unstructured (Non-IP). +- At least equivalent level of security for UEs used for CIoT in 5GS system as in EPS. + +NOTE 3: Security may need to be investigated by SA WG3. + +- Equivalent or reduced level of power consumption for UEs used for CIoT in 5GS system to that in EPS shall be supported. +- UEs used for CIoT can be mobile or nomadic/static, and resource efficiency should be considered for both for relevant optimization(s). +- The 5GS system is assumed to operate with a large number of UEs used for CIoT in the system and be able to appropriately handle overload and congestion situations. +- External exposure of network capabilities towards SCS/AS or AF is supported via NEF. + +- UEs used for CIoT can simultaneously connect to one or multiple SCSs/ASs or AFs. + +--- + +## 5 Key Issues + +### 5.1 Key Issue 1: Support for infrequent small data transmission + +#### 5.1.1 Description + +This key issue aims to provide solutions to support efficient infrequent small data transmissions for at least low complexity, power constrained, and low data-rate CIoT UEs. In some of the usage scenarios the devices (e.g., utility meters) may not be mobile throughout their lifetime. It is expected that the number of CIoT devices will increase exponentially but the data size per device will remain small. + +#### 5.1.2 Architectural requirements + +This key issue addresses infrequently sending and receiving small data with the following architectural requirements: + +- Resource efficient system signalling load (especially over the Radio interface); +- An at least equivalent level of security mechanisms for CIoT in 5G system as in EPS; +- Equivalent or reduced level of power consumption for UEs used for CIoT in 5GS system as in EPS; +- Minimal Access Stratum changes required for NB-IoT/eMTC UEs to connect to 5GS; +- Support for the following small data transmissions: + - single packet transmission (UL or DL); + - dual packet transmission (UL with subsequent DL, or DL with subsequent UL); + - multiple packet transmission (one or a few UL and/or one or a few DL (in any combination or order)); +- Support for delivery of IP data and Unstructured (Non-IP) data; +- Support for charging, roaming and policy control; +- Support API(s) for infrequent small data transmission and capability exposure to AF. +- Support of Exception Report for NB-IoT in 5G system as in EPS. + +#### 5.1.3 Architectural baseline + +The following architectural baseline assumptions should be considered: + +- Small data can be exchanged using either the northbound API interface between 5GC and AF or the N6 interface between UPF and AF. +- The 5GS network function terminating the northbound API is assumed to support message based charging. + +#### 5.1.4 Open issues + +The following open issues remains to be studied: + +- Efficient handling of nomadic/static and mobile usage scenarios. +- Whether and how small infrequent User Data delivery via Control Plane and/or User Plane in the 5GS is supported. + - Assumptions on UE indication of preferred and supported network behaviour (see TS 23.401 [4], clause 4.3.5.10) may be required: A UE includes in a Preferred Network Behaviour indication the Network Behaviour the UE can support and what it would prefer to use. +- Whether PDU sessions need to be established to exchange infrequent small data. + +- Identify whether specific AMF/SMF selection for CIoT devices is needed. +- How to support Exception Report in the manner of infrequent small data transmission. + +NOTE: This key issue may have some dependencies to the key issues for High Latency Communications. + +## 5.2 Key Issue 2: Frequent small data communication + +### 5.2.1 Description + +This key issue aims at providing a solution to support efficient frequent small data transmissions for CIoT, e.g. tracking devices for both Mobile Originated (MO) and Mobile Terminated (MT) use cases. It is expected that the number of such devices can increase exponentially, but the data size per device will remain small. Traffic characteristics for UEs used for CIoT using frequent small data transmissions may lead to inefficient use of resources in the 3GPP system and high UE power consumption without use of appropriate optimization. + +Frequent small data communication targets optimizations that can meet both architecture requirements on UE power consumption and resource efficient system signalling in a balanced way. A traffic pattern is assumed where small data transmissions may occur from a few small data transmissions per hour to multiple small data transmissions per minute. + +The objective of this key issue is to ensure optimized transmission with IP based and non-IP based protocols. Failure to do so may lead to sub-optimal transmission characteristics with increased signalling and UE power consumption. + +### 5.2.2 Architectural requirements + +In addition to the common requirements in clause 4, the following architecture requirements shall be supported in 5GS: + +- It shall be possible to transmit frequent small data with consideration of resource-efficiency and UE power efficiency; +- Minimal Access Stratum changes required for NB-IoT UEs to connect to 5GS; +- Support for delivery of IP data and Unstructured (Non-IP) data; +- Support for the following small data transmissions: + - single packet transmission (UL or DL); + - dual packet transmission (UL with subsequent DL, or DL with subsequent UL); + - multiple packet transmission (one or a few UL and/or one or a few DL (in any combination or order)); +- An at least equivalent level of security mechanisms for CIoT in 5G system as in EPS; +- Equivalent or reduced level of power consumption for UEs used for CIoT in 5GS system as in EPS; +- Support for charging, roaming, policy control; +- Support of Exception Report for NB-IoT in 5G system as in EPS. + +### 5.2.3 Architectural baseline + +The following are considered architecture baselines for this key issue: + +- The 5GS network function terminating the T8 NIDD API is assumed to support message based charging. +- The AF (i.e. SCS/AS) shall be able to access frequent small data service via an API equivalent to T8 NIDD API. +- The AF (i.e. SCS/AS) shall be able to access frequent small data communication over N6. + +### 5.2.4 Open issues + +The following open issues for supporting key issue Small data frequent communication: + +- How to enable frequent small data transmissions (see clause 5.2.1) in a resource-efficient and UE power efficient way in 5GS; + +- Whether and how to support Exception Report in the manner of frequent small data transmission. + +## 5.3 Key Issue 3: High latency communication + +### 5.3.1 Description + +Functions for high latency communication may be used to handle Mobile Terminated (MT) communication with UEs being unreachable while using power saving functions (see key issue on power saving functions) and for coordinating the maximum latency between the application, the UE and the network. "High latency" refers to the initial response time before normal exchange of packets is performed and may be further classified into shorter and longer latencies. That is, the time it takes before a UE has woken up from its power saving state and responded to the initial downlink packet(s). + +In EPC (see TS 23.682 [6]) high latency communication is handled by the following two mechanisms: + +- Extended buffering of downlink data in the network: The data is buffered until the UE wakes up from its power saving state and moves to ECM-CONNECTED state, when the buffered downlink data is conveyed to the UE. +- Notification procedures: An AF (i.e. SCS/AS) may request notification when a UE wakes up or is expected to wake up from its power saving state, to send the downlink data to the UE when the UE becomes reachable. + +Similar approaches may be considered for 5GC. Extended buffering is not recommended for UEs using very long sleep durations. + +### 5.3.2 Architectural requirements + +In addition to the common requirements in clause 4, the following architecture requirements shall be supported for high latency communication in the 5G system: + +- Send DL data to UEs at the earliest possible opportunity when the UEs are applying power saving functions, followed by subsequent return to power saving state when the data has been delivered. +- Coordination of the UE sleep duration between the Application, the UE and the network. +- Provide the AF (i.e. SCS/AS) with UE status information (e.g. reachability notification or the time when the UE is expected to be reachable). + +### 5.3.3 Architectural baseline + +- 5GS enhanced with resource efficient buffering until UE wakes up from its power saving state; +- The buffered downlink data can be forwarded, if needed, between the network function instances that provide the buffering to avoid packet loss. +- Support for UE status information related to power saving functions (e.g. UE reachability) reporting to SCS/AS . +- The 5GS may receive parameters related to reachability and buffering via the Network Parameter Configuration API. + +### 5.3.4 Open issues + +The following issues shall be considered: + +- Study how to support high latency communication when power saving solutions are used in 5GS; +- Study where downlink data can be buffered; +- Study which monitoring events can be generated; +- Study whether the 5G system should support obtaining Maximum Latency parameters from the UE via NAS signalling. + +NOTE: This key issue may have some dependencies to the key issues for Power saving functions, Infrequent small data communication, Frequent small data communication and Network Parameter Configuration API via NEF. + +## 5.4 Key Issue 4: Power Saving Functions + +### 5.4.1 Description + +EPC supports Power Saving Mode (PSM) and Extended Idle Mode DRX (eDRX). This key issue addresses how equivalent EPS power saving functions and 5G enhancements will be supported in the 5G system allowing connectivity between 5GC and WB-EUTRA (eMTC) and/or NB-IoT devices. + +E-UTRAN (both WB-E-UTRAN and NB-IoT) already supports extended idle mode DRX functionality and the same is assumed to be available when E-UTRAN is connected to 5GC: operators have begun deploying eDRX support for NB-IoT/eMTC and are expecting continued support of eDRX regardless of whether E-UTRAN is connected to EPC or 5GC. Therefore, this key issue aims at supporting eDRX in 5GC. + +Furthermore, as already studied for EPC, extended idle mode DRX has a limitation in the amount of time the UE can be in deep sleep (~45 minutes for WB-E-UTRAN and ~3hs for NB-IoT). Therefore, a NAS based approach should be adopted as well to support sleep cycles similar to the ones supported by PSM in EPC. + +Therefore two tracks of this key issue should be studied: + +- Track 1: 5G NAS/5GC support of extended idle mode DRX: + - Reuse as is the RAN aspects of extended idle mode DRX already supported in WB-E-UTRAN and NB-IoT. + - Include NAS, N2, subscription and CN handling aspects of extended idle mode DRX feature. +- Track 2: NAS based approach addressing very long delay tolerance for MT data, i.e. sleep cycles similar in duration as supported by PSM in EPC. + - NAS based solution with no/minimal RAN impact that allows for sleep periods of up to similar duration as in EPC PSM. + +NOTE 1: How the SCS/AS influences the configuration of the power savings functions will be impacted by the conclusion of the "Network Parameter Configuration API via NEF" key issue. + +NOTE 2: Reachability and buffering aspects will be addressed in the key issue on high latency communication. + +### 5.4.2 Architectural requirements + +Architecture goals for UE power consumption optimizations include: + +- Solutions shall enable UE power savings while also supporting mobile terminating communications with a delay governed by the duration of the UE's sleep cycles. +- Solutions shall enable UE power savings while also supporting delay-sensitive mobile terminating communications triggered by mobile originated communications. +- Solutions shall optimize UE power savings according to expected and desired UE and application behaviour (e.g. communication pattern) if such information is available. +- Sleep cycle durations supported by 5GC should be the same as supported by eDRX and PSM in EPC. + +### 5.4.3 Architectural baseline + +**Track 1:** 5G NAS/CN will be updated to support extended idle mode DRX for sleep cycles up to ~45 minutes for WB-E-UTRAN and ~3hs for NB-IoT as follows: + +- 5G NAS to support eDRX sleep cycle negotiation during registration/registration update, etc. +- Subscription information to be enhanced by extended idle mode DRX parameters. +- AMF to support Hyper SFN, Paging Hyperframe and Paging Time Window length as described in TS 23.682 [6] for paging the UE. + +**Editor's note:** Support for eDRX functionality by E-UTRA connected to 5GC as described above to be confirmed by RAN groups. + +**Track 2:** NAS based approach addressing very long delay tolerance for MT data, i.e. for sleep cycles similar in duration as supported by PSM in EPC. + +- Power Saving Function (e.g. the MICO mode, PSM), enabling sleep periods similar in duration to those supported by PSM in EPC is negotiated at NAS. + +#### 5.4.4 Open issues + +- No open issues for Track 1, translation of signalling to 5G CN should be straightforward. +- For Track 2, how to ensure that pending downlink data can be delivered to the UE when the UE wakes up from a sleep cycle. +- For 5GS enhancements how 5GS is configured with the UE's and application's expected and desired behaviour and how the 5GS fulfils those requirements. +- Support for eDRX in RRC\_Inactive is FFS. + +NOTE: This key issue may have some dependencies and relations to other key issues including high latency communication, etc. + +### 5.5 Key Issue 5: UE TX Power Saving Functions + +#### 5.5.1 Description + +It is observed that when UE communicates with network, the TX power consumption of each data transmission is more than ten times of the RX power consumption and the TX power consumption contributes much to the UE whole power consumption. So, optimizing the TX power consumption is an effective way to improve UE power saving. + +This key issue aims to optimize UE TX power consumption under certain conditions, e.g. in weak coverage, with high latency application, or other any conditions under which UE TX power consumption can be improved. + +NOTE: In this key issue UE TX power consumption optimization should be considered only at system level. + +#### 5.5.2 Architectural requirements + +The following architecture requirement shall be supported: + +- It shall be possible to optimize UE TX power consumption under the identified conditions. +- Optimizing UE TX power consumption shall reduce overall UE power consumption. + +#### 5.5.3 Architectural baseline + +#### 5.5.4 Open issues + +- To identify the conditions under which UE TX power consumption can be improved. + +### 5.6 Key Issue 6: Management of Enhanced Coverage + +#### 5.6.1 Description + +Both NB-IoT and WB-E-UTRA, with enhancements for MTC radio access technologies are expected to be used in 5G to provide radio access support for massive IoT. Both these RATs support Enhanced Coverage (EC) based on radio signal repetitions. Radio signal repetition is costly and therefore management of the feature is important from overall system cost perspective. + +#### 5.6.2 Architectural requirements + +The following functionality should be supported: + +- Enable an Application Server/Function to query the status of the enhanced coverage restriction for a UE; +- Means for the 5GC to restrict UE usage of the EC feature; +- Enable an Application Server/Function to enable, or to disable the EC restriction for a particular UE; and +- Temporary storage of RAN parameters in 5GC, related to the EC feature. +- Indication of UE capability of CE mode B support to the 5GC. +- Storage of restriction of use of EC as part of subscription parameter in UDM. + +### 5.6.3 Architectural baseline + +Baseline for EC support for 5G, is the T8 API towards the AF/AS and the 5GS architecture. + +5GC already support monitoring/exposure function of certain UE aspects, see TS 23.502 [7] clause 4.15. The exposure functionality already specified should be considered when enabling an Application Server/Function to query the status of the enhanced coverage restriction for a UE. + +The AMF receives, at N2 release, RAN parameters, important for paging a UE in EC. The AMF shall store the parameters during the time the UE is in CM-IDLE and return the parameters to RAN in a subsequent paging message unless the UE is restricted from using EC. Same or similar IE as the Information Element *UEPagingCoverageInformation* is used for this purpose in 5GS. + +Use of Enhanced Coverage can be restricted per subscriber per PLMN in the UDM. If the Enhanced Coverage is restricted as per subscription or based on local configuration then the AMF informs: + +- the UE as part of the Registration procedure; +- the RAN whenever the UE context is established or modified in the RAN. + +### 5.6.4 Open issues + +Compared to EPC there are a few new aspects in 5GS that should be studied and considered in proposed solutions: + +- OI1: Impacts to the Enhanced Coverage feature due to MICO mode and any other power save solutions proposed and studied for 5GS. +- OI2: Impacts, if any, to the Enhanced Coverage feature due to RRC\_Inactive feature. +- OI3: Signalling details for status query of Enhanced Coverage restriction and enabling/disabling Enhanced coverage restriction by Application Server/Function. + +## 5.7 Key Issue 7: Overload Control for small data + +### 5.7.1 Description + +In EPC two solutions are provided for small data communication a.k.a. CIoT optimizations: User Plan CIoT EPS optimization and Control Plane CIoT EPS optimization. For the Control Plane CIoT EPS optimization overload control mechanism is defined in EPC to protect the MME and the Signalling Radio Bearers (SRBs) in the E-UTRAN from the load generated by NAS Data PDUs. This key issue aims to study whether and how equivalent overload control mechanism can apply for NB-IoT and WB-E-UTRA connected to 5GC. + +NOTE: The Overload control for 5G IoT depends on the selected solution for small data communication. + +### 5.7.2 Architectural requirements + +The following architecture requirement shall be supported: + +- The system should support procedures to handle the overload from data transmission via the control plane (if data transmission via control plane is agreed as a feature in 5GS). +- The system should allow Exception Report during overload control. + +### 5.7.3 Architectural baseline + +Depending on the selected solution for small data communication in 5GS, similar functionality e.g. control plane data back-off timer, control plane overload start indication and service gap as applied in the EPC can be applied to protect the 5GS control plane from overload when used to transport user data packets. + +### 5.7.4 Open issues + +The following open issues remains to be studied. + +- In what network function(s) can the overload conditions occur, and where should the overload control be executed? +- What are the function and procedures required to handle overload? +- How to allow Exception Report when network function is in overload condition? +- Whether and how to handle UEs configured for Low Priority and Overriding of Low priority in 5G System? + +## 5.8 Key Issue 8: Support of the Reliable Data Service + +### 5.8.1 Description + +This key issue will address how to enable the Reliable Data Service for unstructured PDU sessions and functionality equivalent to the Reliable Data Service. + +NOTE: Solutions to this key issue will likely depend on solutions to several other key issues (e.g. Frequent and Infrequent Small Data key issues). + +### 5.8.2 Architectural requirements + +- In an unstructured PDU session type, it shall optionally be possible to provide for reliability and the detection and elimination of duplicate packets between the UE and the PDU session termination point. +- AF's shall be able to send and receive data via a set of exposed APIs. +- When an AF uses an exposed API to send and receive data: + - It shall optionally be possible for the sender to indicate whether or not the data needs to be sent with reliability or not. + - It shall optionally be possible to identify the sending and receiving application. +- UE and Network shall be able to indicate its support for reliable communication. + +### 5.8.3 Architectural baseline + +- It shall be an option to use the Reliable Data Service protocol (defined in TS 24.250 [8]) to provide for reliability and the detection and elimination of duplicate packets between the UE and the unstructured PDU session termination point as well as a means for identifying the sending and the receiving application. +- The APIs that are exposed to the AF will support the functionality and features that are exposed on the T8 interface by the Non-IP Data Delivery APIs that are defined in TS 29.122 [9] so that the T8 APIs may be re-used in 5GC. + +### 5.8.4 Open issues + +- What NF is used as the PDU session termination point (UPF, NEF, etc.) will be decided as part of other key issues (e.g. Frequent and Infrequent Small Data key issues). +- How reliable communication is enabled and disabled (e.g. based on static DNN configuration, or using dynamic mechanism). + +## 5.9 Key Issue 9: Support of common north-bound APIs for EPC-5GC Interworking + +### 5.9.1 Description + +An IoT UE can possibly switch between EPC and 5GC. An authorized third party service provider should be able to get access to authorized and available services when the UE is either on EPC or on 5GC. This key issue will address architectural issues that may arise when a UE switches between being served between EPC and 5GC. + +NOTE: Evaluation of solutions to this key issue should consider whether there are any CAPIF impacts. + +### 5.9.2 Architectural requirements + +- An authorized third party service provider should be able to get access to authorized and available services when the UE is either on EPC or on 5GC. + +### 5.9.3 Architectural baseline + +### 5.9.4 Open issues + +- With respect to the UE's movement between EPC and 5GC: + - Whether this will cause the API termination point(s) associated with the UE to change. + - How does the AF become aware of the availability or of the expected level of support of a given service? +- Whether it is possible for the exposure function (e.g. SCEF or NEF) serving a UE to change. + - If so, then how the AF determines what node to direct API requests towards. + - If so, then how the new node gets the UE's context (i.e. NIDD Configuration, Monitoring Event Configurations, etc.). + +## 5.10 Key Issue 10: Network Parameter Configuration API via NEF + +### 5.10.1 Description + +This key issue addresses how the Network Parameter Configuration API may be implemented the Nnef interface. + +TS 23.682 [6] defines a Network Parameter Configuration procedure on the T8 interface. The procedure is used by the SCS/AS to provide the EPS with suggested parameter values for Maximum Latency, Maximum Response Time and Suggested Number of Downlink Packets. + +In the EPS, these values are used to influence the UE's PSM, extended idle mode DRX, and extended buffering configurations. However, the SCS/AS is largely unaware of the details of the power savings techniques that are used by the network (e.g. PSM and eDRX). From the SCS/AS point of view, the UE is essentially reachable or unreachable. + +The SCS/AS provides Maximum Latency as a guide for the maximum amount of time between UE reachability events. + +The SCS/AS provides Maximum Response as a guide for how much time the SCS/AS needs to begin sending data to the UE after receiving a reachability notification. + +The SCS/AS provides the Suggested Number of Downlink Packets parameters to configure how many packets should be buffered by the network when the UE is not reachable. + +This key issue will examine how, in 5GS, the AF (i.e. SCS/AS) may provide Maximum Latency, Maximum Response, and Suggested Number of Downlink Packets to the 5GS and expect network behaviour similar to EPS. + +## 5.10.2 Architectural requirements + +- The Nnef interface should allow the AF to provide a Maximum latency parameter as a guide for the maximum amount of time between UE reachability events. +- The Nnef interface should allow the AF to provide a Maximum Response parameter as a guide for how much time the AF needs to begin sending data to the UE after receiving a reachability notification. +- The Nnef interface should allow the AF to provide a Suggested Number of Downlink Packets parameter to configure how many packets should be buffered by the network when the UE is not reachable. + +## 5.10.3 Architectural baseline + +- As is done on T8, the AF will use the Network Parameter Configuration API to provide the NEF with Maximum Latency, Maximum Response Time, and Suggested Number of Downlink Packets. +- The NEF will provide the Maximum Latency, Maximum Response Time, and Suggested Number of Downlink Packets parameters to the UDM or UDR and the values will be added to the UE's subscription information. + +NOTE 1: Whether UDM or UDR is used depends on whether it is concluded that per subscriber authorisation and/or data validation is required. + +- The UDM/UDR will provide the Maximum Latency, Maximum Response Time, and the Suggested Number of Downlink packets to the NFs that use them. +- An NF that buffers downlink data may use the Suggested Number of Downlink Packets parameter as a guide for configuring whether or not buffering should be enabled and the amount of data to be buffered. + +NOTE 2: This key issue is dependent on and should adapt to the outcome of other key issues (e.g. power saving, high latency, etc.). + +## 5.10.4 Open issues + +- How and whether Maximum Response Time is used to configure power saving functions and impact a UE's reachability for downlink data. +- How the 5GS uses the Maximum Response Time parameter to determine when to send reachability notifications to the AF. +- How and whether Maximum Latency is used to configure power saving functions and impact a UE's reachability for downlink data. +- How and whether the Suggested Number of Downlink Packets parameter impacts buffering. +- How the UDM knows what NF to provide the Suggested Number of Downlink Packets to (i.e. what PDU session the setting applies to). +- Whether the NEF adds parameters to the UE's subscription information via the UDM or directly to the UDR (i.e. do parameter updates need to be authorised per subscriber and/or is any data validation is required prior to storage). +- It is FFS how the Network Parameter Configuration API and the Maximum Response, Maximum Latency, and Suggested Number of Downlink Packets parameters are used may be impacted by solutions/conclusions to other key issues within this study (e.g. 5GS small data, high latency communication, and power saving functions solution(s)). + +NOTE: Where buffering occurs will be decided as part of the High Latency Communication key issue. + +- It is FFS whether other parameters may be need to configure power saving functions and buffering in 5GS. + +## 5.11 Key Issue 11: Monitoring + +### 5.11.1 Description + +Rel-15 5GC supports event monitoring for many of the same or similar events as EPC. This key issue will address how to add support to 5GC for any monitoring features that are supported in EPC but not 5GC. The key issue shall also make an assessment of the relevance for any identified features in 5GC. This key issue will also address how monitoring event configurations are handled when the UE moves between EPC and 5GC. + +### 5.11.2 Architectural requirements + +- Monitoring Events that are available via the T8 interface in EPC should also be available in 5GC. + +### 5.11.3 Architectural baseline + +- The Monitoring Events that are already available in Rel-15 5GC are assumed to be reused as much as possible. + +### 5.11.4 Open issues + +- Identify missing monitoring events, assess their relevance in 5GC, and study how to add any identified relevant events in 5GC. +- How is Monitoring Event Configuration information handled or transferred when a UE moves from EPC to 5GC. +- Depending on solutions to the Interworking KI, does the node that is supposed to receive the report (NEF or SCEF) change when a UE moves between EPC and 5GC. + +## 5.12 Key Issue 12: Inter-RAT mobility support to/from NB-IoT + +### 5.12.1 Description + +In Rel-14, inter-RAT mobility to/from NB-IoT without the need to detach/reattach was introduced with a CN only approach with three aspects: + +- Force TAU triggering UE via different TAs for different RAT types WB-E-UTRAN and NB-IoT. +- Maintaining two separate UE radio capabilities in the CN (MME) depending on whether they were received when the UE was camping on WB-E-UTRAN or NB-IoT. +- PDN connection handling based on subscription. + +### 5.12.2 Architectural requirements + +The architectural requirements are: + +- Intra-PLMN idle mode inter-RAT mobility to and from NB-IoT should be supported in a radio, core network and battery efficient manner. The other RAT to be supported are NR, WB-E-UTRAN. + +**Editor's note:** Additional considerations for GERAN/UTRAN are FFS. + +- The solution should enable data sent on different RATs to be correctly recorded on CDRs. +- The HPLMN should be able to influence which DNNs/S-NSSAIs are maintained, reconnected or disconnected at inter-RAT idle mode mobility to/from NB-IoT. + +### 5.12.3 Architectural baseline + +The architecture baseline uses the EPC solution as baseline for the core network aspects. + +- It is assumed that the UE radio capabilities provided by the UE in NB-IoT are different from the UE radio capabilities provided by the UE in WB-E-UTRAN and NR. +- Therefore two sets of capabilities are maintained by the AMF: + - UE radio capabilities provided while UE is camping on NB-IoT are stored in AMF and provided to the RAN only when the UE is camping on NB-IoT. + - UE radio capabilities provided while UE is camping on WB-E-UTRAN or NR are stored in AMF and provided to the RAN only when the UE is camping on WB-E-UTRAN or NR. +- When the UE performs inter-RAT idle mode mobility to/from NB-IoT, the SMF decides, based on policies received from UDM or based on local policy, whether to maintain, reconnect or release a PDU session based on the DNN/S-NSSAI information. + +## 5.12.4 Open issues + +- How to handle established PDU Session for following idle mode mobility scenarios: + - Between NB-IoT connected to 5GC and WB-EUTRAN connected to 5GC; + - Between NB-IoT connected to 5GC and WB-EUTRAN connected to EPC; + - Between NB-IoT connected to 5GC and NR connected to 5GC. + +# 5.13 Key Issue 13: Support for Expected UE Behaviour + +## 5.13.1 Description + +The procedure for External Parameter Provisioning is supported in Rel-15 5GC, and the Expected UE Behaviour parameters can be provided by the 3rd party via this procedure (see TS 23.502 [7], clause 4.15.6). The Expected UE Behaviour is regarded as a kind of 3rd party provided parameters set, which should also include the Communication Pattern parameters (see TS 23.682 [6], clause 5.10) which were defined for EPC mainly to optimize resource utilization for CIoT. + +This key issue investigates: + +- Which parameters are necessary to be indicated to the 5GC in order to allow the 5GC to operate as effectively as EPC for devices with communication patterns and how they are provided to the AMF and to the SMF; +- Investigate the relevance of parameters in Communication Pattern list for the procedures and features in 5GC. + +NOTE: Other key issues, such as Power Saving Functions, Network Parameter Configuration API via NEF, and High Latency Communication are affected by this Key Issue. + +## 5.13.2 Architectural requirements + +- Communication Pattern parameters and new parameters which may be used by 5GC to optimize network resource usage should also be part of the Expected UE Behaviour parameters. +- The 5GC authorises whether the AF is allowed to provide the parameters and checks that they are within the range allowed by the operator. + +## 5.13.3 Architectural baseline + +The architectural baseline for supporting the Expected UE Behaviour provisioning for 5G is the T8 API towards the AF/AS and the 5GS architecture. + +- The External Parameter Provisioning procedure is already available in Rel-15 5GC and is assumed to be reused and extended to support the provisioning of Communication Pattern parameters. + +## 5.13.4 Open issues + +The following open issues remains to be studied: + +- Which existing Communication Pattern parameters and new parameters (e.g. mobility related parameters) are necessary for 5GC. +- Which parameters are provided to AMF and to SMF. +- Whether and how the parameters provided to the 5GC are provided to the RAN. + +NOTE: Potential impacts on RAN and whether these parameters are provided to RAN will be coordinated with the relevant RAN WGs. + +## 5.14 Key Issue 14: QoS Support for NB-IoT + +### 5.14.1 Description + +This key issue aims at studying QoS differentiation for NB-IoT. If relevant end-user use cases can be identified, the study should include the required level of QoS differentiation, if any (e.g., QoS differentiation across different UEs, QoS differentiation across PDU sessions of the same UE, QoS differentiation for different traffic flows within a PDU session of the same UE). Consideration should be given for PDU Session types used by NB-IoT (i.e. IPv6, IPv4, and Unstructured) and that dedicated bearers are not supported in NB-IoT. + +The key issue should assume traffic models used by NB-IoT devices, e.g., consideration of relevance for QoS differentiation of traffic flows of small data transmission. + +The key issue should include and assume exception reporting would be present for NB-IoT in 5G. + +### 5.14.2 Architectural requirements + +Study whether and how to introduce support for QoS differentiation for NB-IoT. + +### 5.14.3 Architectural baseline + +The baseline includes: + +- PDU session types can be IPv4, IPv6, or Unstructured. + +### 5.14.4 Open issues + +If relevant end-user use cases can be identified, the open issues include: + +1. The required level of QoS differentiation, if any (e.g. QoS differentiation across different UEs, QoS differentiation across PDU sessions of the same UE, QoS differentiation for different traffic flows within a PDU session of the same UE). + +## 5.15 Key Issue 15: Core Network selection for Cellular IoT + +### 5.15.1 Description + +Rel-15 provides a mechanism to indicate over E-UTRA whether connectivity to 5GC is available, and a mechanism for the UE to indicate whether it has selected EPC or 5GC in RRC signaling. + +A UE that supports EPS CIoT features and 5GS CIoT features as well as a UE that only supports 5GS CIoT features needs to additionally be made aware whether CIoT features are available in EPC and/or 5GC when selecting the core network to connect to via an NB-IoT/WB-E-UTRA cell. + +In the networks that support CIoT features in both EPC and 5GC, the operator may steer the UEs to a specific CN type due to operator policy, e.g., due to roaming agreements, UE's Preferred and Supported Network Behaviour, load redistribution, etc. This key issue aims at studying how to inform the UE whether and which 5GS CIoT features are available in 5GC, and how to steer the UE to EPC or 5GC based on operator policies if the CIoT features required by the UE are supported in both EPC in 5GC. + +NOTE: Steering of UEs to the other CN type is not assumed to be performed for frequent load re-distribution. Operator policies in EPC and 5GC, respectively, are assumed to avoid steering UEs back and forth between EPC and 5GC. + +## 5.15.2 Architectural requirements + +The architectural requirements are as follows: + +- It shall be possible for a UE supporting CIoT features to discover whether 5G CIoT feature(s) are supported in 5GC via NB-IoT/WB-E-UTRA access, and to perform core network selection between EPC and 5GC based on such discovery. +- It shall be possible for the RAN to take into account CIoT feature indication(s) from the UE to perform AMF selection.-Upon UE selecting 5GC, it shall be possible for the 5GC, based on e.g. operator policy, to redirect the UE to EPC, and vice versa. +- Upon redirecting the UE to EPC, it shall be possible for the EPC to prevent idle and connected mode mobility to 5GC, and vice versa. + +## 5.15.3 Architectural baseline + +The architectural baseline is as follows: + +- A UE supporting 5G CIoT feature(s), discovers whether 5G CIoT feature(s) are supported in 5GC. +- A UE supporting 5G CIoT feature(s) and EPC CIoT optimizations performs CN type selection (EPC vs 5GC) based on the information about the features available for EPS (i.e. CP and/or UP optimizations) and 5GC. +- A UE selecting 5GC may also request 5G CIoT feature(s) during RRC connection establishment procedure. +- If the UE has requested 5G CIoT feature(s), the RAN takes that into account for AMF selection. +- If the UE has selected 5GC, the 5GC can based on e.g. operator policy, redirect the UE to EPC, and vice versa. +- If the 5GC has redirected the UE to EPC, the EPC indicates the idle mode camping policy and connected mode mobility restrictions to RAN to prevent mobility to 5GC, and vice versa. + +## 5.15.4 Open issues + +The open issues for this key issue are the following: + +- The granularity of CIoT features to be discovered and to be taken into account, i.e. which solution or set of solutions constitute a 5GS CIoT(s) features to be taken into account during CN selection. +- How the network determines the UE(s) need to be moved to the other system (i.e. EPC to 5GC or vice versa) +- Whether and how the 5GS C-IoT feature(s) are indicated to UE in broadcast or by any other means. +- How the 5GS CIoT feature(s) are indicated in RRC by UE. + +**Editor's note:** The previous two aspects require coordination with RAN WGs. + +- How potential solutions relate to network slicing. +- How the potential solutions for Core Network selection can be generalized and applied also to other than CIoT UEs. + +# 5.16 Key Issue 16: Support of Group communication and messaging + +## 5.16.1 Description + +In order for 5GS to support similar group communication and messaging as in EPC, the following aspects should be studied: + +- Mechanisms for efficient delivery of group messages. +- A service interface provided to application servers to send group messages intended to a group of devices. + +- Depending on solutions, a mechanism might be needed for synchronized wake up for group messages reception by UEs in a group that are using power saving functions. + +**Editor's note:** Depending on RAN WGs progress, this Key Issue may be moved to another Study Item. + +## 5.16.2 Architectural requirements + +The following architecture requirement shall be supported: + +- The system shall support efficient delivery of a group message to a group of devices. +- The system shall support the negotiation of group message delivery between application server and network. +- The system shall (depending on selected solution) support to synchronised wake up for a group of UEs that are using power saving functions. + +## 5.16.3 Architectural baseline + +The following are considered architecture baselines for this key issue: + +- A group message may be sent to a group of devices via unicast Mobile Terminated data delivery procedure. +- The AF (i.e. SCS/AS) may be able to access group messaging service via an API equivalent to T8 group message delivery API. + +## 5.16.4 Open issues + +The following issues shall be considered: + +- Pending RAN decisions on multicast/broadcast, study how to support efficient a group message to a group of devices. + +NOTE 1: This key issue may have some dependencies to the key issues for Power saving functions and Infrequent small data communication. + +NOTE 2: Work on multicast/broadcast will not be started until RAN related decisions. Multicast over UP in the CN is not precluded. + +# 5.17 Key Issue 17: MSISDN-less MO SMS + +## 5.17.1 Description + +This key issue addresses how the MSISDN-less MO SMS API may be implemented on the Nnef interface. + +TS 23.682 [6] defines a procedure for sending MSISDN-less MO SMS via the T8 interface. The procedure is used by the network to send MO SMS to the SCS/AS. + +## 5.17.2 Architectural requirements + +- The Nnef interface should allow the NEF to forward MO SMS to an AF. + +## 5.17.3 Architectural baseline + +- MO SMS between the UE and SMS-SC is unchanged. The service centre address points to the SMS-SC which can route the MO SMS to the AF, the destination SME address is set to short/long code of the AF, and Application Port ID element of the TP-User-Data field is set to an appropriate value. +- The SMS-SC uses the destination SME address (long/short code of the AF) to identify the corresponding NEF based on a pre-configured mapping table. SMS-SC extracts the SMS payload, Application port ID, and IMSI of the UE and delivers them to NEF via a T4 Interface along with the destination SME address (long/short code of the SCS/AS). The NEF acts as an MTC-IWF on the T4 interface. +- The NEF identifies the AF with the destination SME address (long/short code of the SCS/AS) received from the SMS-SC. + +- As is done on T8, the NEF will use the MSISDN-less MO SMS API to send MO SMS to the AF via the Nnef interface. + +## 5.17.4 Open issues + +None. + +# 6 Solutions + +## 6.1 Solution 1: Infrequent small data transfer via NAS-SM and N6 + +### 6.1.1 Introduction + +#### 6.1.1.1 General + +This solution applies to Key issue 1 (support for infrequent small data transmission). The key idea of the solution is to convey small data inside NAS PDUs between UE and SMF for PDU session types IPv4, IPv6, unstructured. + +Operators are not required to upgrade all SMFs to support small data transfer via NAS as the AMF is assumed to be able to select an SMF capable of small data transfer via NAS. This enables isolation from SMFs handling non-CIoT related sessions but also allows for separate scaling of SMFs supporting small data via NAS-SM. + +Support for Reliable Data Service (RDS) is provided as described in Solution [49]. + +Further details related to infrequent data transfer via API(s)/NEF are described in clause 6.30 (Solution 30). + +#### 6.1.1.2 Architecture reference models + +##### 6.1.1.2.0 General + +This clause shows the architecture reference models for the cases where a NAS Small Data Delivery PDU Session terminates at a UPF and architecture reference models that support API usage in the cases where a NAS Small Data Delivery PDU Session terminates at a NEF. + +This solution presents no Roaming Reference Architecture for the Local Breakout case when the PDU session terminates at an NEF because a Small Data API service will not be exposed by the visited network. This is in line with the architecture principle from TS 23.501 [5] which states *"For external exposure of services related to specific UE(s), the NEF resides in the HPLMN. Depending on operator agreements, the NEF in the HPLMN may have interface(s) with NF(s) in the VPLMN."* + +APIs are exposed to the AF via the N33/Nnef reference point. + +The N29 reference point will be used to send and receive small data packets via the NEF. + +##### 6.1.1.2.1 Non-roaming reference architectures + + + +``` + +graph TD + UE[UE] -- N1 --> RAN[RAN] + RAN -- N2 --> AMF[AMF] + AMF -- N12 --> AUSF[AUSF] + AMF -- N8 --> UDM[UDM] + AMF -- N11 --> SMF[SMF] + AUSF -- N13 --> UDM + UDM -- N10 --> SMF + SMF -- N4 --> UPF[UPF] + UPF -- N6 --> DN[DN] + SMF -- N29 --> NEF[NEF] + NEF -- N33 --> AF[AF] + +``` + +Figure 6.1.1.2.1-1: Architecture for small data delivery via NAS and N6 or N33 (non-roaming). The diagram shows a network architecture with the following components and interfaces: UE (User Equipment) connected to RAN (Radio Access Network) via N1; RAN connected to AMF (Access and Management Function) via N2; AMF connected to AUSF (Authentication Server Function) via N12; AMF connected to UDM (Unified Data Management) via N8; AMF connected to SMF (Session Management Function) via N11; AUSF connected to UDM via N13; UDM connected to SMF via N10; SMF connected to UPF (UPF) via N4; UPF connected to DN (Data Network) via N6; NEF (Network Exposure Function) connected to SMF via N29; NEF connected to AF (Application Function) via N33. + +Figure 6.1.1.2.1-1: Architecture for small data delivery via NAS and N6 or N33 (non-roaming) + +### 6.2.1.2.2 Roaming reference architectures + + + +This diagram illustrates the network architecture for home-routed roaming. It is divided into two main sections by a vertical dashed line: the Visited PLMN (VPLMN) on the left and the Home PLMN (HPLMN) on the right. In the VPLMN, a User Equipment (UE) is connected to a Radio Access Network (RAN), which in turn connects to an Access and Management Function (AMF). The AMF is connected to a UPF via the N2 interface. The AMF also connects to a V-SMF via the N11 interface. The V-SMF is connected to the UPF via the N4 interface. The AMF also has connections to the AUSF via the N12 interface and to the UDM via the N8 interface. In the HPLMN, the AMF connects to the AUSF via the N12 interface. The AUSF connects to the UDM via the N13 interface. The UDM connects to the H-SMF via the N10 interface. The H-SMF connects to the UPF via the N4 interface. The H-SMF also connects to the NEF via the N29 interface. The NEF connects to the AF via the N33 interface. The UPF in the HPLMN connects to the DN (Data Network) via the N6 interface. The UPF in the VPLMN connects to the H-SMF via the N16 interface. The H-SMF connects to the DN via the N9 interface. + +Architecture diagram for small data delivery via NAS and N6 or N33 (home-routed roaming). + +Figure 6.1.1.2.2-1: Architecture for small data delivery via NAS and N6 or N33 (home-routed roaming) + + + +This diagram illustrates the network architecture for roaming with local break-out. It is divided into two main sections by a vertical dashed line: the VPLMN on the left and the HPLMN on the right. In the VPLMN, a UE is connected to a RAN, which connects to an AMF. The AMF is connected to a SMF via the N11 interface. The SMF is connected to a UPF via the N4 interface. The UPF connects to the DN via the N6 interface. The AMF also has connections to the AUSF via the N12 interface, to the UDM via the N8 interface, and to the SMF via the N10 interface. In the HPLMN, the AMF connects to the AUSF via the N12 interface. The AUSF connects to the UDM via the N13 interface. The UDM connects to the SMF via the N10 interface. + +Architecture diagram for small data delivery via NAS and N6 (roaming with local break-out). + +Figure 6.1.1.2.2-2: Architecture for small data delivery via NAS and N6 (roaming with local break-out) + +### 6.1.2 Functional Description + +The following principles apply: + +- Small data transfer via NAS-SM: + - Small data is exchanged between the UE and SMF as payload of SM data transfer message in both uplink and downlink direction. + +NOTE 1: It is assumed that the PDU Session ID in the SM data transfer message is not sent in the SM data transfer message but is instead provided separately by the AMF to the SMF. Whether or not other IEs in the SM header can be omitted is left for Stage 3. + +- AMF transparently forwards downlink SM data transfer messages between UE and SMF. +- NAS transport messages are used to transfer SM data transfer messages between UE and AMF. + - The payload container type used for the downlink/uplink NAS transport message carrying SM data transfer message is a new container type "SM data transfer". This allows the AMF to differentiate between regular SM signaling and SM data transfer and apply overload control accordingly. + - For uplink NAS transport, the PDU session ID allows the AMF to route the SM data transfer message to the correct SMF as stored in the UE context. +- SM data transfer messages are associated with a PDU session. +- For a UE in CM Idle mode, it should be possible to send an initial NAS transport message with the SM data transfer message as payload. + +NOTE 2: It is currently not possible to send NAS transport message as defined in TS 24.501 [10] as Initial NAS message (the UE needs to perform service request or registration procedure first to establish a secure NAS connection between UE and AMF). It is up to CT WG1 to decide whether a new NAS message needs to be defined, NAS transport message is extended or service request is extended to transport SM data transfer message. + +- Supported PDU session types: + - Small data transfer supports IP and unstructured data. +- Integrity protection, ciphering and header compression: + - Integrity protection and ciphering for small data are performed by AMF (existing NAS PDU integrity protection and ciphering functionality are re-used as is). + - UE and SMF may perform header compression for IP data. +- AMF selection: + +NOTE 3: AMF selection is part of Key Issue 15 (Core Network selection for Cellular IoT) and the selected solution for Key Issue 15 is used.- SMF selection. + +- During the PDU session establishment procedure the AMF takes the UE request into account to select an SMF that supports Data Transfer over NAS-SM. +- PDU Session Anchor (NEF or UPF) Selection: + - When the PDU Session is established, as described in clause 6.1.4.1, PDU Session Anchor (NEF or UPF) selection is performed in step 5 as follows: + - If the PDU Session type is unstructured, the SMF uses the DNN and/or the S-NSSAI to check the UE's subscription. The UE's subscription may include an "Invoke NEF Selection" flag for the DNN/S-NSSAI combination. + - When the "Invoke NEF Selection" flag is present, the subscription information will also include the NEF Identity that should be used to anchor the PDU Session. + - When the "Invoke NEF Selection" flag is not present, the SMF will perform UPF selection to select a UPF to anchor the PDU Session as described in Solution 1. +- Further details on the support of APIs for infrequent small data transmission are described in Solution 30. +- Releasing the UE based on Release Assistance Indication provided by the UE. Two options have been discussed: + - Option 1 (Release Assistance Indication in NAS-MM - NAS RAI): + - The UE sends the NAS Release Assistance Indication (NAS RAI) to the AMF inside the NAS PDU, i.e. outside the SM data transfer message embedded in the NAS PDU. + - The AMF handles the NAS RAI as follows: + +- if the NAS RAI indicates that no further uplink or downlink data transmissions are expected and unless the AMF is aware of other pending MT traffic, the AMF requests NG-RAN to release the UE context; +- if the NAS RAI indicates that only a single downlink data transmission subsequent to this uplink data transmission is expected, then the AMF requests NG-RAN to release the UE context once the AMF has forwarded the next downlink NAS transport message with container type "SM data transfer" to the UE unless the AMF is aware of other pending MT traffic. +- Option 2 (Release Assistance Indication in AS - AS RAI plus N2 RAI): + - The UE sends AS Release Assistance Indication (AS RAI) to the NG-RAN. The AS RAI indicates whether no further uplink/downlink transmissions or only a single downlink transmission is expected. + +NOTE 4: This differs from the AS RAI defined in Rel-14 EPS (see TS 36.321 [27], TS 36.331 [23]). + +- When NG-RAN receives the AS RAI from the UE, NG-RAN shall maintain the UE's RRC connection in case RRC connection establishment procedure was executed, and include an N2 RAI indication (no further uplink/downlink transmissions or only a single downlink transmission) in the Initial UE message, in the next Uplink NAS transport message or in an RAI specific NGAP indication; +- The AMF evaluates the N2 RAI as follows: + - If the N2 RAI indicates no further uplink/downlink transmissions and the AMF is not aware of any pending DL data for the UE (e.g. a pending SMS or pending DL data buffered e.g. in SMF/UPF as part of extended buffering), the AMF sends the N2 UE Context Release Command to NG-RAN as per the AN Release procedure (TS 23.502 [7], clause 4.2.6). + - If the N2 RAI indicates only a single downlink transmission is expected, the AMF sends the N2 UE Context Release Command to NG-RAN as per the AN Release procedure (TS 23.502 [7], clause 4.2.6) once the AMF has forwarded the next downlink NAS transport message with container type "SM data transfer" to the UE and unless the AMF is aware of other pending MT traffic. + +NOTE 5: The Release Assistance Indication in AS can also support UP-based data delivery. In this case the RAN is expected to send the N2 UE Context Release Request including the N2 RAI to the AMF. The AMF sends the N2 UE Context Release Command to NG-RAN unless the AMF is aware of other pending MT traffic. The RAN releases the UE once it has received the N2 UE Context Release Command from the AMF and once an outstanding UP downlink transmission has been received (if applicable). + +The UE may choose which option to use, allowing it to take advantage of the different optimisation that each option brings and how the UL traffic the RAI is associated with is being transferred. The UE should not use NAS RAI when the last UL traffic is via DRBs or data via AMF is not being used as in these cases any efficiencies will be lost. The UE may use AS RAI at any time. + +NOTE 6: The details of Option 2 are to be defined by RAN WGs. + +NOTE 7: The AS RAI and related N2 RAI apply only to Higher Layer PDUs (i.e. NAS PDU, NAS Signalling, UP Data, but not RLC signalling). + +NOTE 8: See Solution 30 for further details on NEF based data transfer. + +- Early Data Transmission may be initiated by the UE for mobile originated small data over NAS-SM. + +### 6.1.3 Support of EPC interworking + +EPC interworking for small data transfer via NAS-SM uses the architecture for EPC-5GC interworking with N26 as specified in TS 23.501 [5] clauses 4.3.1 and 4.3.2 as a baseline. + +The following principles apply: + +- Idle-mode mobility from 5GS to EPS is performed as per the procedure described in TS 23.502 [7] clause 4.11.1.3.2 with the following differences: + +- Step 5b: When the SMF returns the mapped EPS bearer contexts to the AMF the SMF sets the Control Plane Only PDN Connection Indication for Data over NAS-SM PDU sessions. +- Idle-mode mobility from EPS to 5GS is performed as per the procedure described in TS 23.502 [7] clause 4.11.1.3.3 with the following differences: + - AMF indicates support of CIoT Optimizations when requesting the UE context from the MME via N26; + - for a PDN connection for which Control Plane Only PDN Connection Indication is set, + - in case of home-routed roaming, + - Step 14: the AMF selects a V-SMF supporting small data over NAS-SM; + - Step 14: the V-SMF configures the UPF for data transfer via N4; +- When the "Invoke NEF Selection" flag is present in the UE's subscription information for the PDU Session, the identified NEF will point to an SCEF+NEF if EPC Interworking is supported. +- When the "Invoke NEF Selection" flag is not present in the UE's subscription information for the PDU Session, the identified SMF will select a PGW+UPF as the PDU Session anchor. + +## 6.1.4 Procedures + +### 6.1.4.0 General + +This clause describes the procedures for the case where the PDU Session is terminated at a UPF. Refer to Solution 30 for the case where the PDU session anchor is an NEF. + +#### 6.1.4.1 PDU Session Establishment + +This procedure takes the PDU Session Establishment procedure as described in TS 23.502 [7], clause 4.3.2.2.1 as the baseline. + + + +Sequence diagram for PDU Session Establishment enabling Data over NAS-SM. The diagram shows the interaction between UE, NG-RAN, AMF, (V-)SMF, UPF, PCF, and UDM. The steps are: 1. UE sends a PDU Session Establishment Request (DNN, S-NSSAI, 'Data over NAS-SM' requested) to NG-RAN. 2. NG-RAN sends an SMF selection message to AMF. 3. AMF sends an Nsmf\_PDU Session\_Create SMContext Request/Response to (V-)SMF. 4. (V-)SMF sends a Session Management Policy Establishment or Modification message to PCF. 5. (V-)SMF sends a UPF selection message to UPF. 6. (V-)SMF sends an N4 Session Establishment/Modification message to UPF, providing N4 data transfer info. 7. (V-)SMF sends an N1N2MessageTransfer message to AMF. 8. AMF sends a NAS transport message (PDU session ID, SM: PDU session establishment response) to NG-RAN, which is then received by the UE. + +**Figure 6.1.4.2-1: PDU Session Establishment enabling Data over NAS-SM** + +1. The UE sends a PDU session establishment request message as SM payload of a NAS transport message. The NAS transport message contains PDU session ID along with other regular information e.g. DNN, S-NSSAI, etc. if applicable. +2. The AMF determines if the PDU Session uses NAS-SM to transfer PDUs. If the PDU Session will use NAS-SM to transfer PDUs, the AMF selects an SMF that supports Data over NAS-SM if available for the requested DNN, + +and S-NSSAI. The AMF stores the association of the PDU Session ID and the selected SMF ID in the UE context. The network chooses to transfer data to the DN via N6. + +NOTE 1: How the AMF determines if the PDU Session uses NAS-SM to transfer PDUs will be determined as part of the Key Issue 15 conclusion. + +NOTE 2: As captured in clause 4, it is assumed that the exposure of network capabilities towards the SCS/AS is done via NEF. In addition, as captured in clause 8.9, *when a UE is capable of switching between EPC and 5GC, it shall only be associated with combined SCEF+NEF node(s) for Service Capability Exposure.* Consequently, data towards SCS/AS can be routed via a NEF+SCEF combined node. See also Solution 30. + +3. The AMF invokes Nsmf\_PDUSession\_CreateSMContext request including DNN, S-NSSAI and PDU Session ID. The AMF also indicates to the SMF if the PDU Session uses NAS-SM to transfer PDUs. The SMF replies with an Nsmf\_PDUSession\_CreateSMContext Response. +4. The SMF may perform a Session Management Policy Establishment procedure. +5. The SMF selects a UPF. +6. The SMF configures the UPF for data transfer via N4. +7. The SMF sends a PDU Session Establishment Accept providing indication that Data Over NAS-SM is enabled for this PDU session without including the N2 SM container. +8. The AMF forwards the NAS message to the UE. + +### 6.1.4.2 Mobile Originated Data Transport via NAS-SM and N6 + + + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant AMF + participant SMF as (V-)SMF + participant UPF + + Note left of UE: 0. UE is in CM-IDLE + UE->>NG-RAN: 1. RRC Connection establishment Or RRC early data request (NAS transport(SM data transfer, PDU session ID)) + NG-RAN->>AMF: 2. Initial UE message (NAS transport(SM data transfer, PDU session ID)) + AMF->>AMF: 3. Check integrity and decrypt data + AMF->>NG-RAN: 3a. DL N2 message + Note left of NG-RAN: 3b. RRC Early Data Complete or RRC connection establishment + AMF->>SMF: 4. N11 message (SM data transfer, PDU session ID) + SMF->>UPF: 5. Forward data (UL data) + Note right of UPF: DL data available at UPF + UPF->>SMF: 6. Forward data (DL data) + SMF->>AMF: 7. Namf_Communication_N1N2MessageTransfer (SM data transfer, PDU session ID) + Note left of AMF: 8. Data encryption and integrity protection + AMF->>NG-RAN: 9. Downlink NAS transport (NAS transport(SM data transfer, PDU session ID)) + Note left of NG-RAN: 10. RRC DL message (NAS transport(SM data transfer, PDU session ID)) + Note left of NG-RAN: 11. No further activity detected. + Note right of AMF: 12. AN release procedure (see TS 23.502 clause 4.2.6) + +``` + +Sequence diagram for Mobile Originated Data Transport via NAS-SM and N6. Lifelines: UE, NG-RAN, AMF, (V-)SMF, UPF. The process starts with the UE in CM-IDLE, followed by RRC connection establishment or early data request. The NG-RAN forwards the initial UE message to the AMF, which checks integrity and decrypts the data. The AMF then sends an N11 message to the (V-)SMF, which forwards the uplink data to the UPF. A dotted box indicates the period when DL data is available at the UPF. The (V-)SMF sends a Namf\_Communication\_N1N2MessageTransfer to the AMF, which performs data encryption and integrity protection. The AMF then sends a downlink NAS transport message to the NG-RAN, which sends an RRC DL message to the UE. Finally, if no further activity is detected, an AN release procedure is initiated. + +**Figure 6.1.4.2-1: Mobile Originated Data Transport via NAS-SM** + +0. The UE is in CM-IDLE. +1. The UE establishes an RRC connection or sends the RRCEarlyDataRequest message and sends a NAS PDU as part of this. The NAS PDU carries encrypted uplink data as payload of an SM data transfer message and a PDU session ID. +2. NG-RAN forwards the NAS PDU to the AMF. If RRCEarlyDataRequest message was received in step 1, the NG-RAN includes "EDT Session" indication in the N2 Initial UE message. For Option 2, the NG-RAN further indicates request to release RRC connection in N2 Initial UE message. +3. AMF checks the integrity of the incoming NAS PDU and decrypts the data it contains. + +- 3a. If the AMF received "EDT Session" indication from the NG-RAN in step 2, the AMF sends an N2 message to the NG-RAN. +- a) If the Release Assistance Information was received from UE in Option 1 with Uplink data and it indicated that Downlink data was not expected or if the AMF received a request to release RRC connection in N2 Initial UE message for Option 2, and the AMF does not expect any other signalling with the UE, the AMF should: +- either send a NAS service accept in the N2 Downlink NAS message and include End Indication to indicate that no further data or signalling is expected with the UE; or, + - alternatively, instead of a NAS service accept, the AMF sends an N2 Connection Establishment Indication message including End Indication to indicate that no further data or signalling is expected with the UE. +- b) If the AMF determines more data or signalling may be pending, the AMF sends an N2 connection establishment indication message without End Indication. +- 3b. In case 3a was executed, the NG-RAN completes the RRC early data procedure as follows. +- a) For the case of 3a.a) the NG-RAN proceeds with RRCEarlyDataComplete message. The procedure is completed in Step 5. +- b) For the case of 3a.b) the NG-RAN proceeds with RRC connection establishment procedure. In that case all steps up to step 12 apply, +4. AMF forwards the data to the (V-)SMF handling the PDU session identified by the PDU session ID contained in the NAS transport message. +- NOTE 1: Whether a new or an existing service operation of SMF should be invoked in this step is to be decided during normative phase. +5. The (V-)SMF decompresses the header if header compression applies to the PDU session. The V-SMF forwards the data to the UPF. (In the home-routed roaming case, the UPF may forward the data to a different UPF in the HPLMN via N9.) The UPF forwards the data to the DN, In case of unstructured data, tunneling may be applied according to clause 5.6.10.3 in TS 23.501 [5]. +6. [Conditional] The UPF forwards available downlink data to the (V-)SMF, +7. [Conditional] The (V-)SMF compresses the header if header compression applies to the PDU session and encapsulates the downlink data as payload in an SM data transfer message. The (V-)SMF forwards the SM data transfer message and the PDU session ID to the AMF using the Namf\_Communication\_N1N2MessageTransfer service operation. +8. [Conditional] The AMF creates a DL NAS transport message with the received PDU session ID and the SM data transfer message (container type is set to SM data transfer). The AMF ciphers and integrity protects the NAS transport message. +9. [Conditional] The AMF sends the DL NAS transport message to NG-RAN. +10. [Conditional] NG-RAN delivers the NAS payload over RRC to the UE. +11. [Conditional] If no further NAS PDU activity is detected by NG-RAN, then NG-RAN triggers the AN release procedure. +12. The UE's logical NG-AP signaling connection and RRC signaling connection are released as per TS 23.502 [7] clause 4.2.6. +- NOTE 2: How the UE is released based on Release Assistance Information is covered in clause 6.1.2. +- NOTE 3: The details of the NGAP messages to be used for this procedure are to be decided by RAN WG3. + +### 6.1.4.3 Mobile Terminated Data Transport via NAS-SM and N6 + + + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant AMF + participant SMF as (V-)SMF + participant UPF + + Note right of UPF: 1. Forward data (DL data) + UPF->>SMF: 1. Forward data (DL data) + Note right of SMF: 2. Namf_Communication_N1N2MessageTransfer (PDU Session ID, SM data transfer) + SMF->>AMF: 2. Namf_Communication_N1N2MessageTransfer (PDU Session ID, SM data transfer) + + Note left of AMF: If UE in CM Idle + Note right of AMF: 3. Paging + AMF->>NG-RAN: 3. Paging + Note left of NG-RAN: 4. Paging + NG-RAN->>UE: 4. Paging + + Note left of UE: 5. Service Request + UE->>NG-RAN: 5. Service Request + Note right of NG-RAN: 6. Service Request + NG-RAN->>AMF: 6. Service Request + + Note right of AMF: 7. Data encryption and integrity protection + Note right of AMF: 8. Downlink NAS transport (NAS transport(SM data transfer, PDU session ID)) + AMF->>NG-RAN: 8. Downlink NAS transport (NAS transport(SM data transfer, PDU session ID)) + Note left of NG-RAN: 9. RRC DL message (NAS transport(PDU session ID, SM data transfer)) + NG-RAN->>UE: 9. RRC DL message (NAS transport(PDU session ID, SM data transfer)) + + Note left of UE: UL data available + Note left of UE: 10. RRC UL message (NAS transport(PDU session ID, SM data transfer)) + UE->>NG-RAN: 10. RRC UL message (NAS transport(PDU session ID, SM data transfer)) + Note right of NG-RAN: 11. Uplink NAS transport (NAS transport(SM data transfer, PDU session ID)) + NG-RAN->>AMF: 11. Uplink NAS transport (NAS transport(SM data transfer, PDU session ID)) + + Note right of AMF: 12. Check integrity and decrypt data + Note right of AMF: 13. N11 message (SM data transfer, PDU session ID) + AMF->>SMF: 13. N11 message (SM data transfer, PDU session ID) + Note right of SMF: 14. Forward data (UL data) + SMF->>UPF: 14. Forward data (UL data) + + Note left of NG-RAN: 15. No further activity detected. + + Note bottom: 16. AN release procedure (see TS 23.502 clause 4.2.6) + Note bottom: 16. AN release procedure (see TS 23.502 clause 4.2.6) + +``` + +Sequence diagram for Mobile Terminated Data Transport via NAS-SM and N6. Lifelines: UE, NG-RAN, AMF, (V-)SMF, UPF. The process involves data forwarding from UPF to SMF, then to AMF, followed by paging if the UE is idle, then service request and data transport via RRC and NAS messages, with encryption/decryption steps. It ends with an AN release procedure. + +**Figure 6.1.4.3-1: Mobile Terminated Data Transport via NAS-SM** + +1. The UPF forwards a downlink data packet to the SMF. +2. The (V-)SMF compresses the header if header compression applies to the PDU session and encapsulates the downlink data as payload in an SM data transfer message. The (V-)SMF forwards the SM data transfer message and the PDU session ID to the AMF using the Namf\_Communication\_N1N2MessageTransfer service operation. +3. [Conditional] If the UE is in CM Idle, the AMF sends a paging message to NG-RAN. +4. [Conditional] If NG-RAN received a paging message from AMF, NG-RAN perform paging. + +5. [Conditional ] If the UE receives paging message, it responds with service request. +7. The AMF creates a DL NAS transport message with the received PDU session ID and the SM data transfer message (container type is set to SM data transfer). The AMF ciphers and integrity protects the NAS transport message. +8. The AMF sends the DL NAS transport message to NG-RAN. +9. NG-RAN delivers the NAS payload over RRC to the UE. +10. While the RRC connection is established further uplink and downlink data can be exchanged. In order to send uplink data, the UE sends an integrity protected NAS PDU as RRC uplink data. The NAS PDU carries encrypted uplink data as payload of an SM data transfer message and a PDU session ID. +11. NG-RAN forwards the NAS PDU to the AMF. +12. AMF checks the integrity of the incoming NAS PDU and decrypts the data it contains. +13. AMF forwards the data to the (V-)SMF handling the PDU session identified by the PDU session ID contained in the NAS transport message. + +NOTE 1: Whether a new or an existing service operation of SMF should be invoked in this step is to be decided during normative phase. + +14. The (V-)SMF decompresses the header if header compression applies to the PDU session. The V-SMF forwards the data to the UPF. (In the home-routed roaming case, the UPF may forward the data to a different UPF in the HPLMN via N9.) The UPF forwards the data to the DN, In case of unstructured data, tunneling may be applied according to clause 5.6.10.3 in TS 23.501 [5]. +15. [Conditional] If no further NAS PDU activity is detected by NG-RAN, then NG-RAN triggers the AN release procedure. +16. The UE's logical NG-AP signaling connection and RRC signaling connection are released according to TS 23.502 [7] clause 4.2.6. + +NOTE 2: How the UE is released based on Release Assistance Information is covered in clause 6.1.2. + +NOTE 3: The details of the NGAP messages to be used for this procedure are to be decided by RAN WG3. + +## 6.1.5 Impacts on existing entities and interfaces + +### AMF: + +- Support of new payload container type for SM data transfer. +- Support for initial NAS transport message with the SM data transfer message as payload. +- Support for selecting SMF capable of Data over NAS. +- Support of release assistance indication handling. + +### SMF: + +- Supports and Sending and Receiving PDUs via NAS-SM. +- Support of new payload container type and SM data transfer message. +- Header compression for IP data. +- Receives the "Invoke NEF Selection" and "NEF ID" during PDU Session Establishment. +- Support for a N4-like services on the N29 interface with the NEF for Unstructured PDU Session. +- Supports exchange of Small Data PDUs with the UPF on the N4 interface. + +### UPF: + +- Support for extended buffering. +- Supports exchange of Small Data PDUs with the SMF on the N4 interface. + +## UE: + +- Supports and Sending and Receiving PDUs via NAS-SM. +- Support of new payload container type and SM data transfer message. +- Support for initial NAS transport message with the SM data transfer message as payload. +- Support of release assistance indication handling. + +## UDM/UDR: + +- Support for the NIDD Configuration, MT NIDD, and MO NIDD APIs as described in TS 29.122 [9] and TS 23.682 [6]. +- Support for the authorisation during the NIDD Configuration procedure. + +## NG-RAN: + +- Release Assistance Indication in AS (if chosen as the way forward). + +## 6.1.6 Evaluation + +This solution proposes to convey small data inside NAS-SM between UE and SMF for PDU session types IPv4, IPv6 and unstructured. The AMF transparently forwards small data inside NAS-SM between UE and SMF. Integrity protection and ciphering for small data are performed by AMF, and the UE and SMF may perform header compression for IP data. This solution supports also infrequent data transfer via API(s)/NEF (see clause 6.30 - in particular conclusions in clause 6.30.6 - for more details). Solution 1 supports early data and reuses EPC interworking as defined in Rel-15, i.e. relies on mapping PDU sessions to PDN connections. + +## Pros: + +- No need to establish user plane PDU session to transfer data. +- UE's application functionality are not affected. +- Limited or no impact on RAN (depending on RAI conclusions). +- Easy interworking with EPC based CIoT. Solution 1 follows the same concept as EPS CP optimization. This enables low complexity IoT devices that support both EPC and 5GC connectivity to send small data over NAS (i.e. without having to support a user-plane stack, AS security, etc.) regardless of the core network those devices are connected to. + +## Cons: + +- The solution(s) for Overload Control for small data (see KI 7 and related solutions) are required to help manage any additional load on the AMF and/or SMF. +- Impact on AMF and SMF to transfer small data. +- Whether to send the existing SM header or a shortened SM header with the small data is up to CT WG1. + +This solution successfully addresses Key Issues 1 (Support for infrequent small data transmission). + +## 6.2 Solution 2: Infrequent small data transfer through NAS and a direct interface between AMF and UPF + +### 6.2.1 Introduction + +This solution applies to Key Issue 1 - Support for infrequent small data transmission. + +## 6.2.2 Functional Description + +This solution introduces a user plane interface between AMF and UPF. We call it Nx interface here which is a user plane tunnel. Packets are transferred from UE to AMF through NAS and from AMF to UPF through the Nx tunnel. To support NIDD, packets can be transferred from UE to AMF through NAS and from AMF to NEF. It's shown in the Figure 6.2.2-1. + + + +``` + +graph TD + NEF[NEF] --- Nnef((Nnef)) + UDM[UDM] --- Nudm((Nudm)) + AF[AF] --- Naf((Naf)) + Nnef --- SBI[Service Based Interface] + Nudm --- SBI + Naf --- SBI + SBI --- Namf((Namf)) + SBI --- Nsmf((Nsmf)) + Namf --- AMF[AMF] + Nsmf --- SMF[SMF] + AMF --- N1((N1)) + AMF --- N2((N2)) + AMF --- Nx((Nx)) + N1 --- UE[UE] + N2 --- AN[AN] + Nx --- UPF[UPF] + SMF --- N4((N4)) + N4 --- UPF + UPF --- N6((N6)) + N6 --- DN[DN] + +``` + +Figure 6.2.2-1: Architecture for infrequent small data transfer through NAS and a direct interface between AMF and UPF. The diagram shows a central Service Based Interface (SBI) connecting various network functions. Above the SBI are NEF, UDM, and AF, connected via Nnef, Nudm, and Naf interfaces respectively. Below the SBI are AMF and SMF, connected via Namf and Nsmf interfaces. The AMF is connected to the UE via N1, to the AN via N2, and to the UPF via the Nx interface. The SMF is connected to the UPF via N4. The UPF is connected to the DN via N6. + +**Figure 6.2.2-1: Architecture for infrequent small data transfer through NAS and a direct interface between AMF and UPF** + +The assumption is UE has registered with network and has negotiated with the network of control plane small data transfer capabilities. + +During the UE requested PDU session establishment procedure, a session level Nx user plane tunnel is established between AMF and UPF. N11 and N4 signalling is used to control the Nx tunnel setup. E.g. exchanges the tunnel info between AMF and UPF. + +For MO data transfer, When AMF receives the NAS data PDU including the PDU session ID from UE, AMF identifies the related Nx tunnel based on the PDU session ID and transfers the received data PDU to UPF through the Nx tunnel. The UPF forwards the data to the DN. If the Nx tunnel is not established, N11 and N4 signalling is used to control the Nx tunnel setup. + +For MT data, after receiving DL data from DN, UPF buffers the DL data and sends Data Notification to SMF, and SMF sends the Data Notification to AMF. AMF paging UE in case the UE is in CM-IDLE state. Upon reception of paging indication, the UE sends a UE triggered Service Request NAS message to AMF, the Nx tunnel is established after the N11 and N4 signalling interaction. UPF forwards the DL data to AMF through the Nx tunnel. AMF sends the DL data as NAS data PDU to UE. + +For IP data, the UE and AMF may perform header compression. For uplink IP data, UE implements the compressor, and AMF implements the decompressor. For downlink IP data, AMF implements the compressor, and UE implements the decompressor. The header compression is supported at AMF. The NAS data PDU is sent using NAS MM message. + +For NIDD support, AMF determines whether or not the NIDD via NEF shall be used for a PDU session based on subscription information and the DNN/S-NSSAI received from UE. The subscription information includes NEF ID for the DNN/S-NSSAI. To setup the Session between AMF and NEF, AMF sends NEF id, the C-Plane address of AMF and the Create NEF Session Request to SMF, SMF forwards the received information to NEF and gets the Create NEF Session Response and the NEF C-Plane address. SMF provides the Create NEF Session Response and the NEF C-Plane address to AMF, thus the Session between AMF and NEF are setup. NEF supports infrequent small data transmission and capability exposure to AF is similar to the SCEF as described in TS 23.682 [6] + +## 6.2.3 Support of EPC interworking + +The existing EPS-5GS interworking principles are used with the differences that the UE should support for small data over NAS in both in 4G and 5G network. Idle-mode mobility from 5GS to EPS and Idle-mode mobility from to EPS to 5GS are supported as the procedures described in TS 23.502 [7], clause 4.11.1.3. + +## 6.2.4 Procedures + +### 6.2.4.1 Nx tunnel setup + +The Nx tunnel is setup during the PDU session establishment procedure. Figure 6.2.4.1-1 depicts how to setup an Nx tunnel between AMF and UPF. + + + +``` +sequenceDiagram + participant UE + participant AN + participant AMF + participant UPF + participant SMF + Note left of UE: 1.PDU Session Establishment Request + UE->>AMF: 1.PDU Session Establishment Request + Note right of AMF: 2.Nsmf_PDUSession_CreateSMContext Request + AMF->>SMF: 2.Nsmf_PDUSession_CreateSMContext Request + Note right of SMF: 3.Nsmf_PDUSession_CreateSMContext Response + SMF->>AMF: 3.Nsmf_PDUSession_CreateSMContext Response + Note right of AMF: 4.N4 Session Establishment Request + AMF->>UPF: 4.N4 Session Establishment Request + Note right of UPF: 5.N4 Session Establishment Response + UPF->>SMF: 5.N4 Session Establishment Response + Note right of SMF: 6.Namf_Communication_N1N2MessageTransfer + SMF->>AMF: 6.Namf_Communication_N1N2MessageTransfer + Note left of UE: 7.PDU Session Establishment Accept + AMF->>UE: 7.PDU Session Establishment Accept +``` + +Sequence diagram for Nx tunnel setup showing interactions between UE, AN, AMF, UPF, and SMF. + +Figure 6.2.4.1-1: Nx tunnel setup + +1. The PDU Session Establishment Request NAS message is received from UE. +2. If this PDU Session is used for control plane small data transfer and AMF decides to setup Nx tunnel for the data transfer between AMF and UPF, AMF allocates the its Nx tunnel info used for DL data forwarding from UPF. AMF includes its Nx tunnel info in the Nsmf\_PDUSession\_CreateSMContext Request from AMF to SMF. +3. The Nsmf\_PDUSession\_CreateSMContext Response is provided from SMF to AMF. +4. The SMF sends an N4 Session Establishment Request to the UPF including the Nx tunnel info of AMF. If the Nx Tunnel Info of UPF is allocated by the SMF, the Nx Tunnel Info of UPF is provided to UPF in this step. +5. The UPF acknowledges by sending an N4 Session Establishment Response. If UPF is responsible for allocating its Nx Tunnel Info, the Nx Tunnel Info of UPF is provided to SMF in this step. +6. SMF sends the Nx Tunnel Info of UPF to AMF using the Namf\_Communication\_N1N2MessageTransfer operation. The Nx tunnel is setup between AMF and UPF. PDU Session Establishment Accept message is carried in the N1 SM container. +7. The PDU Session Establishment Accept NAS message is sent to UE. + +### 6.2.4.2 Nx tunnel release + +The Nx tunnel could be released during the AN release procedure as depicted in Figure 6.2.4.2-1 or during the CN-initiated selective deactivation of UP connection of an existing PDU Session procedure as depicted in Figure 6.2.4.2-2. + + + +``` + +sequenceDiagram + participant UE + participant AN + participant AMF + participant UPF + participant SMF + AMF->>AN: 1.N2 UE Context Release Command + AN-->>UE: 2.RAN connection release + AN->>AMF: 3.N2 UE Context Release Complete + AMF->>SMF: 4.Nsmf_PDU Session_UpdateSMContext + SMF->>UPF: 5.N4 Session Modification Request + UPF-->>SMF: 6.N4 Session Modification Response + SMF->>AMF: 7.Nsmf_PDU Session_UpdateSMContext Ack + +``` + +Sequence diagram for Nx tunnel release due to AN release. Lifelines: UE, AN, AMF, UPF, SMF. 1. AMF sends N2 UE Context Release Command to AN. 2. AN sends RAN connection release to UE. 3. AN sends N2 UE Context Release Complete to AMF. 4. AMF sends Nsmf\_PDU Session\_UpdateSMContext to SMF. 5. SMF sends N4 Session Modification Request to UPF. 6. UPF sends N4 Session Modification Response to SMF. 7. SMF sends Nsmf\_PDU Session\_UpdateSMContext Ack to AMF. + +**Figure 6.2.4.2-1: Nx tunnel release due to AN release** + +1. AMF may decide to perform AN release based on local reason or the request received from AN. the AMF sends an N2 UE Context Release Command to the (R)AN. +2. If the (R)AN connection with the UE is not already released, the (R)AN requests the UE to release the (R)AN connection. +3. The (R)AN confirms the N2 Release by returning an N2 UE Context Release Complete message to the AMF. The N2 signalling connection between the AMF and the (R)AN for that UE is released. +4. If there are active Nx tunnels between AMF and UPF for the UE, for each active Nx tunnel, the AMF invokes Nsmf\_PDU Session\_UpdateSMContext Request to deactivate the Nx tunnel for the PDU Session. +5. SMF sends the N4 Session Modification Request to UPF to remove the Nx tunnel info. +6. UPF sends the N4 Session Modification Response acknowledging the SMF request. +7. SMF sends Nsmf\_PDU Session\_UpdateSMContext Ack to AMF to confirm the Nx tunnel is released. + + + +``` + +sequenceDiagram + participant UE + participant AN + participant AMF + participant UPF + participant SMF + SMF->>UPF: 1.N4 Session Modification Request + UPF-->>SMF: 2.N4 Session Modification Response + SMF->>AMF: 3.Namf_Communication_N1N2MessageTransfer + AMF->>SMF: 4.Nsmf_PDU Session_UpdateSMContext + +``` + +Sequence diagram for Nx tunnel release due to selective PDU session deactivation. Lifelines: UE, AN, AMF, UPF, SMF. 1. SMF sends N4 Session Modification Request to UPF. 2. UPF sends N4 Session Modification Response to SMF. 3. SMF sends Namf\_Communication\_N1N2MessageTransfer to AMF. 4. AMF sends Nsmf\_PDU Session\_UpdateSMContext to SMF. + +**Figure 6.2.4.2-2: Nx tunnel release due to selective PDU session deactivation** + +1. When SMF determines to deactivate a PDU session and the PDU Session is used for control plane small data transfer, the SMF sends N4 Session Modification Request to remove the Nx tunnel of the corresponding PDU Session. +2. UPF sends the N4 Session Modification Response acknowledging the SMF request. +3. The SMF invokes the Namf\_Communication\_N1N2MessageTransfer service operation to indicate AMF to release the Nx tunnel. AMF removes the related Nx tunnel info. +4. The AMF invokes the Nsmf\_PDU Session\_UpdateSMContext service operation to acknowledge the Namf service received in step 3. + +### 6.2.4.3 MO data transport + + + +``` + +sequenceDiagram + participant UE + participant AN + participant AMF + participant UPF + participant SMF + Note left of UE: 1.NAS data PDU + UE->>AMF: 1.NAS data PDU + AMF->>SMF: 2.Nsmf_PDUSession_UpdateSMContext + SMF->>UPF: 3.N4 Session Modification + UPF->>SMF: 4.Namf_Communication_N1N2MessageTransfer + SMF->>AMF: 5.data PDU over Nx tunnel + +``` + +Sequence diagram for MO data transport showing interactions between UE, AN, AMF, UPF, and SMF. + +**Figure 6.2.4.3-1: MO data transfer** + +1. UE transfers the data to AMF as the NAS data PDU. The PDU session ID is included in the NAS data PDU. +2. When AMF receives the NAS data PDU including the PDU session ID from UE, The AMF decompresses the IP header if header compression applies to the PDU session. AMF identifies the related Nx tunnel based on the PDU session ID. If the Nx tunnel is not established, AMF includes its Nx tunnel info in the Nsmf\_PDUSession\_UpdateSMContext from AMF to SMF. +3. The SMF sends the Nx tunnel info of AMF to UPF, and the Nx tunnel info of UPF is determined at this step. +4. SMF sends the Nx Tunnel Info of UPF to AMF. The Nx tunnel is setup between AMF and UPF. +5. AMF transfers the received data PDU to UPF through the Nx tunnel. The UPF forwards the data to the DN. + +### 6.2.4.4 MT data transport + + + +``` + +sequenceDiagram + participant UE + participant AN + participant AMF + participant UPF + participant SMF + Note right of UPF: 1.Data Notification + UPF->>SMF: 1.Data Notification + SMF->>AMF: 2. Namf_Communication_N1N2MessageTransfer + AMF->>AN: 3.paging + AN->>UE: 3.paging + UE->>AMF: 4.Service Request + AMF->>SMF: 5.Nsmf_PDUSession_UpdateSMContext + SMF->>UPF: 6.N4 Session Modification + UPF->>SMF: 7.Namf_Communication_N1N2MessageTransfer + SMF->>AMF: 8. downlink data over Nx tunnel + AMF->>UE: 9.NAS data PDU + +``` + +Sequence diagram for MT data transport showing interactions between UE, AN, AMF, UPF, and SMF. + +**Figure 6.2.4.4-1: MT data transfer** + +1. When UPF receives downlink data of a PDU session, and the Nx tunnel is not established, the UPF buffers the downlink data. UPF sends Data Notification message to the SMF. +2. The SMF invokes the Namf\_Communication\_N1N2MessageTransfer to the AMF. +3. If the UE is in CM-IDLE state, AMF performs paging for the UE. +4. Upon reception of paging indication, the UE sends a UE triggered Service Request NAS message to AMF. +5. AMF includes its Nx tunnel info in the Nsmf\_PDUSession\_UpdateSMContext from AMF to SMF. + +6. The SMF sends the Nx tunnel info of AMF to UPF, and the Nx tunnel info of UPF is determined at this step. +7. SMF sends the Nx Tunnel Info of UPF to AMF. The Nx tunnel is setup between AMF and UPF. +8. UPF forwards the downlink data to the AMF through the Nx tunnel. +9. The AMF compresses the header if header compression applies to the PDU session and encapsulates the downlink data into the NAS message. AMF sends the DL data as NAS data PDU to UE over NAS signalling. + +### 6.2.4.5 NIDD support + +The procedure for PDU Session Establishment enabling Data over NAS and NEF is as following: + + + +``` + +sequenceDiagram + participant UE + participant AN + participant AMF + participant SMF + participant NEF + Note left of UE: 1.PDU Session Establishment Request + UE->>AMF: 1.PDU Session Establishment Request + Note right of AMF: 2.Nsmf_PDUSession_CreateSMContext Request + AMF->>SMF: 2.Nsmf_PDUSession_CreateSMContext Request + Note right of SMF: 3.Nsmf_PDUSession_CreateSMContext Response + SMF->>AMF: 3.Nsmf_PDUSession_CreateSMContext Response + Note right of SMF: 4. Connection setup request + SMF->>NEF: 4. Connection setup request + Note right of NEF: 5. Connection setup response + NEF->>SMF: 5. Connection setup response + Note right of SMF: 6.Namf_Communication_N1N2MessageTransfer + SMF->>AMF: 6.Namf_Communication_N1N2MessageTransfer + Note left of UE: 7.PDU Session Establishment Accept + AMF->>UE: 7.PDU Session Establishment Accept + +``` + +Sequence diagram for PDU Session Establishment enabling Data over NAS and NEF. The diagram shows interactions between UE, AN, AMF, SMF, and NEF. The steps are: 1. UE sends PDU Session Establishment Request to AMF; 2. AMF sends Nsmf\_PDUSession\_CreateSMContext Request to SMF; 3. SMF sends Nsmf\_PDUSession\_CreateSMContext Response to AMF; 4. SMF sends Connection setup request to NEF; 5. NEF sends Connection setup response to SMF; 6. SMF sends Namf\_Communication\_N1N2MessageTransfer to AMF; 7. AMF sends PDU Session Establishment Accept to UE. + +**Figure 6.2.4.5-1: PDU Session Establishment enabling Data over NAS and NEF** + +1. The PDU Session Establishment Request is carried in a NAS message. The session ID and DNN, S-NSSAI, etc. if applicable are also contained in this NAS message. +2. If this PDU Session is used for control plane small data transfer, and the subscription information includes NEF ID for the corresponding DNN/S-NSSAI, the AMF determines to setup the connection between AMF and NEF, AMF includes NEF id, the C-Plane address of AMF and the Create NEF Session Request (the UE ID, session ID and DNN, S-NSSAI, etc.) with the N1 SM container (PDU Session Establishment Request) in the Nsmf\_PDUSession\_CreateSMContext Request from AMF to SMF. +3. The SMF replies with an Nsmf\_PDUSession\_CreateSMContext Response. +4. The SMF sends the connection setup request to NEF including the NEF id, the C-Plane address of AMF and the Create NEF Session Request (the UE ID, session ID and DNN, S-NSSAI, etc.). The rate control information may also be included in this message based on the SMF local configuration or interaction with PCF. +5. If an SCS/AS has performed the NIDD Configuration procedure (similar procedure as described in TS 23.682 [6] clause 5.13) , the NEF associates the NIDD connection with the PDU Session. Otherwise, the NEF rejects the procedure. NEF provides connection setup response to SMF including the C-Plane address of NEF and the Create NEF Session Response. +6. The SMF sends the Namf\_Communication\_N1N2MessageTransfer to AMF including PDU Session Establishment Accept message and the received C-Plane address of NEF and the Create NEF Session Response. + +7. After receiving the C-Plane address of NEF and the Create NEF Session Response, the connection between AMF and NEF are setup. The PDU Session Establishment Accept NAS message is sent to UE. + +## 6.2.5 Impacts on existing entities and interfaces + +The following nodes are impacted: + +AMF: + +- support the user plane Nx tunnel between AMF and UPF including Nx tunnel info allocation. +- support the header compression function. + +SMF: + +- support the the Nx tunnel info transfer between AMF and UPF. + +## 6.2.6 Evaluation + +**Editor's note:** This clause provides an evaluation of the solution. + +# 6.3 Solution 3: Infrequent small data transmission with no PDU session available + +## 6.3.1 Introduction + +This solution applies to address the Key Issue 1: Support for infrequent small data transmission. + +The solution assumes that the UE does not establish a PDU session before sending small data packet and addresses. This solution is only used for non-IP data delivery. + +## 6.3.2 Functional Description + +**Editor's note:** This clause outlines solution principles and documents any assumptions made. + +The infrequent small data transmission procedure for a scenario where the user data is forwarded to application server via control plane is illustrated in Figure 6.4-1. + +## 6.3.3 Support of EPC interworking + +**Editor's note:** This clause describes if and how EPC-5GC interworking is supported by this solution. + +The solution 3 does not support EPC-5GC interworking. This solution is only used for the UEs which only support 5GC-NAS. + +## 6.3.4 Procedures + +### 6.3.4.1 Registration Procedure + +During the Registration procedure, the AMF determines whether the user data are allowed to be delivered without PDU session. + + + +``` + +sequenceDiagram + participant UE + participant RAN as (R)AN + participant AMF + participant SMF + participant NEF + participant UDM + + Note left of UE: 1. Registration Request (Non Session Data delivery) + UE->>AMF: 1. Registration Request (Non Session Data delivery) + Note over UE, RAN, AMF, SMF, NEF, UDM: 2. Authentication/Security + Note right of AMF: 3. Nudm_SDM_Get + AMF->>UDM: 3. Nudm_SDM_Get + Note left of SMF: 4a. NSDD Context Create Request + AMF-->>SMF: 4a. NSDD Context Create Request + Note right of SMF: 4b. UPF selection and N4 session establishment + SMF->>SMF: 4b. UPF selection and N4 session establishment + Note left of NEF: 4c. NSDD Context Create Request + AMF-->>NEF: 4c. NSDD Context Create Request + Note left of UE: 5. Registration Request (Non Session Data delivery Activated) + AMF->>UE: 5. Registration Request (Non Session Data delivery Activated) + +``` + +Sequence diagram of the Small data transmission procedure (Non Session Data delivery). The diagram shows interactions between UE, (R)AN, AMF, SMF, NEF, and UDM. Step 1: UE sends a Registration Request (Non Session Data delivery) to AMF. Step 2: Authentication/Security procedure. Step 3: AMF sends Nudm\_SDM\_Get to UDM. Step 4: AMF sends NSDD Context Create Request to SMF (4a), which triggers UPF selection and N4 session establishment (4b), and then AMF sends NSDD Context Create Request to NEF (4c). Step 5: AMF sends Registration Request (Non Session Data delivery Activated) to UE. + +**Figure 6.3.4.1-1: Small data transmission procedure** + +1. The UE provides Non Session Data Delivery (NSDD) indication in the Registration Request message. The UE provides NSDD indication only for non IP data delivery. +2. Authentication/Security procedure is performed. +3. The AMF retrieves the UE subscription from the UDM; the UE subscription data may indicate whether the NSDD is allowed or not for the UE; The AMF determines whether the NSDD is activated for the UE according to UE subscription; +4. The AMF request NEF (as described in sub-clause 6.4.2) or SMF to create NSDD context for the UE, which may include UE ID, AMF ID, DNN etc.; The RDS Configuration procedure as described in sub-clause 6.4.4.2 between NEF and AF/AS may also be performed. + +If the NSDD Context is established at the SMF, the SMF selects UPF and initiates N4 session establishment procedure; the UPF establishes a point-to-point tunnelling via the N6 between the UPF and the SCS/AS The tunnel parameters are determined based on pre-configuration and/or the NSDD context. + +If the NSDD Context is established at the NEF, the NEF determines what SCS/AS is associated with the context based on the user identity and the DDN. + +5. The AMF indicates the UE that NSDD is activated in Registration Accept message. + +### 6.3.4.2 MO NSDD procedure + +If the NSDD is activated, the UE may send small data via NAS without PDU session establishment. + + + +``` + +sequenceDiagram + participant UE + participant AMF + participant SMF + participant UPF + participant SCS/AS + + Note right of AMF: 2. Check Integrity and decrypts data + + Note right of AMF: 7. Data encryption and Integrity protection + + UE->>AMF: 1. Data Transport(NAS Data PDU) + AMF->>SMF: 3. N11 Message (User Data) + SMF->>UPF: 4. N4 Message (User Data) + Note right of UPF: User Data in tunnel + UPF-->>SMF: 5. N4 Message (User Data) + SMF->>AMF: 6. N11 Message (User Data) + AMF->>UE: 8. Data Transport(NAS Data PDU) + +``` + +Sequence diagram for MO NSDD showing interactions between UE, AMF, SMF, UPF, and SCS/AS. The process involves data transport from UE to AMF, integrity checking, N11 and N4 message exchanges between AMF, SMF, and UPF, and final data transport from AMF to UE. + +**Figure 6.3.4-1: MO NSDD** + +0. The UE was in CM-IDLE state. +1. The UE transmits the NAS Data PDU to the AMF. +2. The AMF checks the integrity of the incoming NAS PDU and decrypts the user data it contains. + + +If the NSDD Context is established at SMF, step 3 to step 6 are performed. If the NSDD Context is established at NEF then MO delivery mechanism described in sub-clause 6.4.4.3 is used and step 3 to step 6 are skipped. +3. The AMF determines the SMF based on the NSDD context for the UE and forwards the user data to the SMF with the UE identity via N11 message. +4. The SMF determines the corresponding N4 session for the user data based on the UE identity received in step 3, then the SMF forwards the user data to the UPF via N4 message. +5. The UPF receives the DL user data and forwards the user data to the SMF based on the local association information between N4 session and point-to-point tunnelling in N6. +6. The SMF receives the DL user data and forwards the user data to the AMF based on the local association information between the N4 session and NSDD context. +7. If downlink data is received, the AMF encrypts and integrity protects the NAS transport message with downlink user data. +8. The AMF transmits the DL NAS Data PDU to the UE. + +### 6.3.4.3 MT Small data transmission procedure + + + +``` + +sequenceDiagram + participant UE + participant AME + participant SMF + participant UPF + participant SCS/AS + Note right of SCS/AS: User Data in tunnel + SCS/AS->>UPF: 1. N4 Message (User Data) + UPF->>SMF: 2. N11 Message (User Data) + SMF->>AME: 3. Data delivery via NAS + +``` + +Sequence diagram of the MT NSDD procedure. Lifelines: UE, AME, SMF, UPF, SCS/AS. The sequence starts with 'User Data in tunnel' from SCS/AS to UPF. Step 1: '1. N4 Message (User Data)' from UPF to SMF. Step 2: '2. N11 Message (User Data)' from SMF to AME. Step 3: '3. Data delivery via NAS' from AME to UE. + +**Figure 6.3.4.3-1: MT NSDD procedure** + +If the NSDD Context is established at SMF, step 1 to step 3 are performed; if the NSDD Context is established at NEF, the MT delivery mechanism described in clause 6.4.4.4 is used and step 1, step 2 are skipped. + +1. Upon receiving DL data from the N6 tunnel, the UPF forwards the DL data to the SMF; +2. The SMF forwards the user data to the AMF with the UE identity via N11 message. +3. The AMF forwards the user data container to the UE via NAS message. + +### 6.3.5 Impacts on existing entities and interfaces + +UE: + +- Non Session Data Delivery negotiation with the AMF during the Registration procedure; +- Support sending/receiving small data via NAS message without PDU session available. + +AMF: + +- Establish NSDD context with SMF/NEF for the UE if NSDD is enabled; +- Forwarding small data between the SMF/NEF and the UE. + +SMF: + +- Establish NSDD context and corresponding N4 session; +- Forwarding small data between the UPF and AMF. + +NEF: + +- Establish NSDD context with AMF; +- Forwarding small data between the SCS/AS and AMF. + +### 6.3.6 Evaluation + +The solution proposes the small data are delivered via NAS message without available PDU sessions. The proposed NSDD procedure is based on the same principles as the PDN Connection to the SCEF in EPC and addresses the NSDD + +context is established in the core network for small data delivery and the UE sends/receives small data via NAS message to/from the AMF without PDU session establishment procedure. + +In this solution, 5GC stores NSDD context for the small data delivery. There is not any PDU session context stored in the UE side and there is no PDU session establishment procedure performed by the UE, therefore, this solution can save the storage and power for the CIoT equipment. + +## 6.4 Solution 4: Reliable Data Service Support + +### 6.4.1 Introduction + +This solution addresses the Key Issue 1 - "Support for infrequent small data transmission" and Key Issue 8 - "Support of the Reliable Data Service". + +### 6.4.2 Functional Description + +#### 6.4.2.1 Support of Reliable Data Service + +The Reliable Data Service is used by the UE and NEF for reliable small data delivery of unstructured PDU. The service provides a mechanism for the NEF to determine if the data was successfully delivered to the UE and for UE to determine if the data was successfully delivered to the NEF. When a requested acknowledgement is not received, the Reliable Data Service retransmits the packet. Support for Reliable Data Service (RDS) incurs the following functionality: + +- Use of NAS transport between UE and AMF for small data delivery. This applies to both 3GPP and non-3GPP accesses. +- Support for AMF determining the NEF for a given UE. +- Support for subscription checking and actual transmission of MO/MT small data delivery by the NEF to the AF/UE. +- Support for MO/MT small data delivery for both roaming and non-roaming scenarios. +- Support for unstructured PDU. +- Support for API exposure for Reliable Data Service towards 3rd party application provider. + +During registration procedure, a UE that wants to use RDS provides "RDS supported" indication over NAS signalling indicating the UE's capability for support of RDS. "RDS supported" indication indicates whether UE can support reliable small data delivery over NAS via 3GPP access or via both 3GPP and non-3GPP access. If the core network supports RDS functionality, the AMF includes "RDS supported" indication to the UE, and whether RDS delivery over NAS via 3GPP access or via both the 3GPP and non-3GPP access is accepted by the network. + +RDS packets are transmitted over NAS without the need to establish data radio bearers, via NAS transport message, which can carry RDS payload. PDU session establishment is not needed. UE and Network supports RDS protocol as specified in TS 24.250 [8]. When the RDS is enabled, a protocol is used between the end-points, i.e. between UE and NEF. The protocol uses a RDS header to identify if the packet requires no acknowledgement, requires an acknowledgement, or is an acknowledgment and to allow detection and elimination of duplicate PDUs at the receiving endpoint. Also Port Numbers in the header are used to identify the application on the originator and to identify the application on the receiver. This solution supports RDS over unstructured PDU only. + +#### 6.4.2.2 Architecture to support RDS over 5GC + +Figure 6.4.2.2-1 shows the non-roaming architecture to support RDS using the Service-based interfaces within the Control Plane. + + + +Figure 6.4.2.2-1: Non-roaming System Architecture for RDS. This diagram shows a UE connected to an AMF via the N1 interface. The AMF is connected to a Service Based Interface (SBI) via the Namf interface. On the SBI, three network functions are connected: AF (via Naf), NEF (via Nnef), and UDM (via Nudm). + +**Figure 6.4.2.2-1: Non-roaming System Architecture for RDS** + +Figure 6.4.2.2-2 shows the non-roaming architecture to support RDS using the reference point representation. + + + +Figure 6.4.2.2-2: Non-roaming System Architecture for RDS in reference point representation. This diagram shows a UE connected to an AMF via the N1 interface. The AMF is connected to a NEF via the Nxx interface. The AMF is also connected to a UDM via the N8 interface. The UDM is connected to the NEF via the Nyy interface. The NEF is connected to an AF/AS via the N33 interface. + +**Figure 6.4.2.2-2: Non-roaming System Architecture for RDS in reference point representation** + +Figure 6.4.2.2-3 shows the roaming architecture (Home Routed scenario) to support RDS using the Service-based interfaces within the Control Plane. + + + +Figure 6.4.2.2-3: Roaming architecture for RDS over NAS - Home Routed scenario in service-based interface representation. This diagram is split by a dashed vertical line into two domains: VPLMN (Visited PLMN) and HPLMN (Home PLMN). In the VPLMN, a UE is connected to an AMF via the N1 interface. The AMF is connected to an NEF via the Namf interface. The NEF is connected to the SBI via the Nnef interface. In the HPLMN, the SBI contains an NEF (connected via Nnef), a UDM (connected via Nudm), and an AF (connected via Naf). + +**Figure 6.4.2.2-3: Roaming architecture for RDS over NAS - Home Routed scenario in service-based interface representation** + +Figure 6.4.2.2-4 shows the roaming architecture for NEF using the reference point representation. + + + +``` +graph TD; subgraph VPLMN; IWK-NEF[IWK-NEF] --- VPLMN_NF[VPLMN NF]; end; subgraph HPLMN; hNEF[hNEF] --- HPLMN_NF[HPLMN NF]; end; IWK-NEF --- hNEF; +``` + +Diagram of Roaming architecture for NEF in reference point representation. It shows two network domains, VPLMN and HPLMN, separated by a dashed vertical line. In the VPLMN domain, there is an IWK-NEF box connected to a VPLMN NF box below it. In the HPLMN domain, there is an hNEF box connected to an HPLMN NF box below it. A horizontal line connects the IWK-NEF box to the hNEF box, crossing the dashed line. + +**Figure 6.4.2.2-4: Roaming architecture for NEF in reference point representation** + +NOTE 1: For the sake of clarity, SEPPs are not depicted in the roaming figures 6.4.2.2-3, and 6.4.2.2-4. + +NOTE 2: IWK-NEF is located in the VPLMN for inter-connection with the NEF of the HPLMN. IWK-NEF (similar to IWK-SCEF in EPC) relays data between AMF in VPLMN to NEF in HPLMN for home routed scenario. + +### 6.4.3 Support of EPC interworking + +The principles of Solution 13 are followed for interworking with EPC. The S-NSSAI and DNN are used to determine if the Reliable Data Service is used. When interworking with EPC is required, the RDS endpoint is an SCEF+NEF. When the UE moves between EPC and 5GC, RDS state is recreated. When the UE moves from EPC to 5GC and PDN Connections with RDS are active, the PDN connections are released by the UE and the UE will configure the RDS between the UE and NEF as described in the Registration Procedure in clause 6.4.2.1. In EPC, RDS state is maintained for the lifetime of the PDN Connection to the SCEF. In 5GC, RDS state is maintained for the lifetime of the UE Registration or NIDD Configuration. + +When RDS PDUs are sent via NAS, Serving PLMN rate control will apply. Since RDS PDUs are not sent over a connection, APN rate control need not apply. + +## 6.4.4 Procedures + +### 6.4.4.1 Registration procedure supporting reliable small data delivery over NAS + + + +``` + +sequenceDiagram + participant UE + participant AMF + participant NEF + participant UDM/UDR + + Note left of UE: 1. Registration Request + UE->>AMF: 1. Registration Request + Note right of AMF: 2. Step 4 to step 14 of Registration procedure in Figure 4.2.2.2.2-1 of TS 23.502 + AMF->>NEF: 3. NEF selection + Note right of AMF: 4. Step 15 to step 20 of Registration procedure in Figure 4.2.2.2.2-1 of TS 23.502 + AMF->>NEF: 5.Nnef_RDS_Activate_Request + Note right of NEF: 6. UDR discovery + NEF->>UDM/UDR: 7a. Nudr_UDM_notify + UDM/UDR-->>NEF: 7b. Nudr_UDM_Query + NEF->>AMF: 8. Nnef_RDS_Activate Response + AMF->>UE: 9. Registration Accept + +``` + +Sequence diagram of the registration procedure supporting reliable small data delivery over NAS. The diagram shows interactions between UE, AMF, NEF, and UDM/UDR. The process starts with a Registration Request from UE to AMF. This is followed by steps 4 to 14 of the registration procedure (shown as a block). Then, NEF selection occurs. This is followed by steps 15 to 20 of the registration procedure (shown as a block). Next, the AMF sends an Nnef\_RDS\_Activate\_Request to the NEF. The NEF performs UDR discovery. Then, the NEF sends Nudr\_UDM\_notify and Nudr\_UDM\_Query to the UDM/UDR. The UDM/UDR responds with Nnef\_RDS\_Activate Response to the NEF. Finally, the AMF sends a Registration Accept to the UE. + +**Figure 6.4.4.1-1: Registration procedure supporting reliable small data delivery over NAS** + +1. During Registration procedure in 5GS defined in Figure 4.2.2.2.2-1 of TS 23.502 [7], to enable reliable small data delivery, the UE includes an "RDS supported" indication in Registration Request in step 1-3 indicating the UE's capability for RDS. The "RDS supported" indication indicates whether the UE supports reliable small data delivery over NAS via current access. +2. Step 4 to step 14 of the Registration procedure in Figure 4.2.2.2.2-1 of TS 23.502 [7] are performed. When AMF relocation happens during the Registration procedure, the old AMF transfers NEF address to the new AMF as part of UE context in step 5 of Figure 4.2.2.2.2-1. +3. If the "RDS supported" indication is included in the Registration Request, the AMF checks subscription from the UDM for the UE on whether the RDS service is allowed to the UE. If yes and the UE context doesn't include an available NEF of the serving PLMN, the AMF discovers and selects an NEF to serve the UE. The NEF discovery is based on the following methods: + - NEF address preconfigured in the AMF (i.e. NEF FQDN); or + - NEF address received from the UDM; or + - The AMF invokes Nnrf\_NFDiscovery service operation from NRF to discover the NEF address as described in clause 5.2.7.3.2 of TS 23.502 [7]. + +For roaming scenario, the AMF discovers and selects an NEF in VPLMN. + +4. Step 15 to step 20 of the Registration procedure in Figure 4.2.2.2.2-1 of TS 23.502 [7] are performed. +5. The AMF invokes Nnef\_RDS\_Activate service operation from the NEF. The invocation includes AMF address, Access Type, GPSI (if available) and SUPI. AMF uses the NEF address derived from step 3. +6. The NEF discovers a UDR as described in TS 23.501 [5], clause 6.3.9. +- 7a-7b. If the UE context already exists in the NEF, the NEF shall replace the old AMF address with the new AMF address. Otherwise NEF retrieves RDS related subscription data using Nudm\_UDM\_Query and subscribes to be notified using Nudr\_UDM\_Notify when the RDS related subscription data is modified. + +NEF also creates an UE context to store the RDS subscription information and the AMF address that is serving this UE. + +8. The NEF responds back to the AMF with Nnef\_RDS\_Activate service operation response message. The AMF stores the NEF address received as part of the UE context. +9. The AMF includes the "RDS supported" indication to the UE in the Registration Accept message of step 21 of Figure 4.2.2.2.2-1 of TS 23.502 [7] only after step 8 in which the AMF has received a positive indication from the selected NEF. + +The "RDS supported" indication in the Registration Accept message indicates to the UE whether the network allows the reliable small message delivery over NAS via 3GPP access or via both the 3GPP and non-3GPP access. + +#### 6.4.4.2 RDS Configuration procedure between NEF and AF/AS + +Figure 6.4.4.2-1 illustrates the procedure of configuring necessary information at the NEF and UDR. + +In order to avoid MO reliable small data delivery failure, the RDS configuration procedure should be performed by the AF/AS prior to the UE requesting send MO reliable small data delivery. + + + +``` + +sequenceDiagram + participant UDR + participant NEF + participant AF/AS + AF/AS->>NEF: 1. Nnef_RDSConfig Request + NEF->>UDR: 3. Nudr_UDM-Query Request + UDR->>NEF: 5. Nudr_UDM_Query Response + NEF->>AF/AS: 6. Nnef_RDSConfig Response + +``` + +Sequence diagram illustrating the RDS Configuration procedure between NEF and AF/AS. The diagram shows three lifelines: UDR, NEF, and AF/AS. The sequence of messages is: 1. AF/AS sends Nnef\_RDSConfig Request to NEF; 3. NEF sends Nudr\_UDM-Query Request to UDR; 5. UDR sends Nudr\_UDM\_Query Response to NEF; 6. NEF sends Nnef\_RDSConfig Response to AF/AS. + +**Figure 6.4.4.2-1: RDS Configuration procedure between NEF and AF/AS** + +1. The AF/AS used Nnef\_RDS\_Config\_Request service operation to establish routing information in UE context at NEF. AF/AS provides external identifier for UE message and reliable data service configuration information (e.g. application port number) to the NEF. +3. The NEF used Nudr\_UDM-Query\_Request service operation to check if RDS configuration request for the received External Identifier is authorized, and to receive necessary information for RDS, if required. +4. The UDR examines the Nudr\_UDM-Query\_Request, e.g. with regard to the existence of External Identifier and maps the external identifier to SUPI. The UDR sends Nudr\_UDM\_Query\_Response (SUPI, Result) to the NEF to acknowledge acceptance of the RDS Authorization. + +6. The NEF uses Nnef\_RDS\_Config\_Response service operation to acknowledge acceptance of the RDS Configuration Request to the AF/AS. If the RDS Configuration was accepted, the NEF will create an association between the External Identifier and SUPI in UE context. In the MT reliable small data delivery procedure, the NEF will use External Identifier to determine the SUPI and receiver port number. In the MO reliable small data delivery procedure, the NEF will use the SUPI, to determine AS/AF address and application port number from the UE context. + +#### 6.4.4.3 MO reliable small data delivery procedure + + + +``` +sequenceDiagram + participant UE + participant AN + participant AMF + participant NEF + participant AF/AS + + Note right of AMF: 2. Check integrity and decrypts data + + UE->>AMF: 1. Initial NAS Message (NAS PDU (RDS PDU)) + AMF->>NEF: 3. Namf_RDSTransfer (RDS PDU) + NEF->>AF/AS: 4. Nnef_DataTransfer (Data PDU) + NEF->>AMF: 5. Namf_Communication_N1N2_message_Transfer (RDS ACK PDU) + AMF->>UE: 6. DL NAS Message (NAS PDU (RDS ACK PDU)) +``` + +Sequence diagram of the MO reliable small data delivery procedure. Lifelines: UE, AN, AMF, NEF, AF/AS. The sequence starts with the UE sending an Initial NAS Message (NAS PDU (RDS PDU)) to the AMF. The AMF then checks integrity and decrypts the data. Next, the AMF sends a Namf\_RDSTransfer (RDS PDU) to the NEF. The NEF sends a Nnef\_DataTransfer (Data PDU) to the AF/AS. The NEF then sends a Namf\_Communication\_N1N2\_message\_Transfer (RDS ACK PDU) back to the AMF. Finally, the AMF sends a DL NAS Message (NAS PDU (RDS ACK PDU)) to the UE via the AN node. + +Figure 6.4.4.3-1: MO reliable small data delivery procedure + +It is assumed that the UE is registered with the network. + +1. The UE sends an integrity protected NAS PDU to the AMF via AN node. The NAS PDU carries the UL RDS PDU data and indication for reliable small data delivery. +2. The AMF checks the integrity of the incoming NAS PDU and decrypts the PDU data. +3. The AMF determines the NEF based on the UE context and Namf\_RDSTransfer service operation to send RDS PDU to NEF along with UE identity (e.g. SUPI). +4. The NEF sends the data PDU to the AF/AS according to UE context using Nnef\_DataTransfer service operation. +5. The NEF sends RDS acknowledgement to AMF using Namf\_Communication\_N1N2\_message\_transfer service operation. +6. The AMF encrypts the RDS Acknowledgement PDU and send to UE in DL NAS message. + +#### 6.4.4.4 MT reliable small data delivery procedure + + + +``` + +sequenceDiagram + participant AF/AS + participant NEF + participant AMF + participant AN + participant UE + + Note right of AMF: 5. Encryption and integrity protection + + AF/AS->>NEF: 1. Nnef_DataTransfer (data PDU) + NEF->>AMF: 2. Namf_Communication_N1N2MessageTransfer (RDS PDU) + AMF-->>AN: 3. PAGING + AN-->>UE: 3. PAGING + UE-->>AN: 4. Initial NAS Message + AN-->>AMF: 4. Initial NAS Message + Note right of AMF: 5. Encryption and integrity protection + AMF-->>AN: 6. DL NAS Message (NAS PDU(RDS PDU)) + AN-->>UE: 6. DL NAS Message (NAS PDU(RDS PDU)) + +``` + +Sequence diagram of MT reliable small data delivery procedure. Lifelines: UE, AN, AMF, NEF, AF/AS. The sequence starts with AF/AS sending Nnef\_DataTransfer (data PDU) to NEF. NEF sends Namf\_Communication\_N1N2MessageTransfer (RDS PDU) to AMF. AMF sends PAGING to AN, which then sends PAGING to UE. UE responds with Initial NAS Message to AN, which is forwarded to AMF. AMF performs encryption and integrity protection. Finally, AMF sends DL NAS Message (NAS PDU(RDS PDU)) to AN, which is received by UE. + +**Figure 6.4.4.4-1: MT reliable small data delivery procedure** + +It is assumed that the AF/AS has performed RDS configuration procedure. + +1. The AF/AS request reliable small data delivery using Nnef\_dataTransfer service operation. AS/AF provides External Identifier, DL data PDU, and Reliable Data Configuration. +2. The NEF based on UE context derive determines UE identity from UE's External identifier. NEF determines if AF/AS requested reliable small data delivery and adds RDS header to data PDU. NEF sends RDS PDU to AMF using Namf\_Communication\_N1N2\_message\_transfer service operation. +3. If the UE is in CM-IDLE, the AMF will buffer the RDS PDU and sends paging message to AN nodes. Then the UE is paged by the AN nodes. Otherwise, step 3 and step 4 are skipped. +4. UE responds to paging with initial NAS message. +5. The AMF performs integrity protection and encryption to the RDS PDU. +6. The AMF sends encrypted NAS PDU with RDS PDU to the AN node in DL NAS message. + +#### 6.4.5 Impacts on existing entities and interfaces + +UE: + +- Support the RDS protocol as defined in TS 24.250 [8]. + +AMF: + +- Support of initial NAS message to carry NAS payload (if not supported in Rel-15). +- Support of service operation with NEF for MO/MT data transfer. Re-use of existing services provided by AMF may be possible. + +NEF: + +- Support the RDS protocol as defined in TS 24.250 [8]. +- Support of service operation with AMF for MO/MT data transfer. Re-use of existing services provided by AMF may be possible. +- Support of service operation with AS/AF for MO/MT data transfer. Re-use of existing services provided by NEF may be possible. +- Support of service operation with UDM/UDR for RDS configuration. + +AS/AF: + +- Support of service operation with NEF for MO/MT data transfer and RDS configuration. + +## 6.4.6 Evaluation + +This solution relies on use of the RDS protocol (already defined for EPS) for reliable delivery of small data unstructured PDUs. It does not require establishment of a PDU session as the RDS header contains the routing information for the small data transfer between UE and AF. This solution transmit small data over NAS-MM between UE and AMF and then from AMF to NEF directly. + +# 6.5 Solution 5: Small Data Fast Path communication + +## 6.5.1 Introduction + +This solution addresses the Key Issue 1: Support for infrequent small data transmission. + +The Small Data Fast Path (SDFP) solution targets to optimize small data transmission for CIoT UEs in CM-IDLE mode. It describes how small data can be passed in a fast path of the user plane without the overhead amount of signalling caused by CM-IDLE / CM-CONNECTED mode transitions. + +The SDFP solution has the following specifics: + +- UP security is between UE and UPF. The security information is configured by AMF during UE registration or PDU session setup. +- The UE passes information required for the RAN to forward the small data to the UPF in the RRC message. The RAN derives the UPF information from the information provided by the UE. The UPF information should be abstract and hide the internal network architecture. +- One or several QoS flows can be enabled for SDFP. UE will indicate QoS information of the packet over radio interface, the RAN will forward the QoS information for verification by the UPF (i.e. that the UE is authorized to use a certain QoS flow). +- The solution support DL data using CN paging. (e)DRX parameters etc. is configured during UE registration. The solution can also support PSM if defined. +- Uses a UP connected to NEF, e.g. according to solution 35, to support NIDD API(s) to AF/SCS/AS for the Indirect Model of communication. + +## 6.5.2 Functional Description + +### 6.5.2.1 General + +The Small data fast path is intended as an add-on function handled in a separate PDU session. It does not replace any existing system function, but it can be used if both the network and UE support it. This should also keep the impact on the system lower and simplify the introduction in Low Power Wide Area Networks (LPWAN). + + + +``` + +graph LR + UE[UE] -- "(encrypted small data)" --> RAN[RAN] + RAN -- "N3 (encrypted small data)" --> UPF[UPF] + UPF -- "N6" --> PDN((PDN)) + +``` + +Diagram of E2E SDFP transmission showing data flow from UE to RAN, then to UPF via N3, and finally to PDN via N6. The data is labeled as '(encrypted small data)'. + +**Figure 6.5.2.1-1: E2E SDFP transmission** + +The SDFP is realized by providing relevant UPF or PDU session related information to the UE from the network, which the UE would later provide to the RAN. The UPF or PDU session relevant information enables the RAN to derive the path over N3 to the UPF. At UL data arrival the UE passes the data together with the UPF or PDU session relevant information to the RAN. The RAN forwards the data on the N3 interface. Since info required to determine the forwarding of the data is received from the UE, the RAN does not need to signal to the AMF or have any UE context information stored. + +The UPF or PDU session relevant information is provided to the UE as part of the Session Management (SM) procedures or UE Registration procedures. The SMF may enable one (or more) of the QoS flows for SDFP. + +The AMF derives SDFP security information and provides it to the SMF. The SMF stores the SDFP security information for the PDU session, enables indicated QoS flows and acknowledges to the AMF that they have been SDFP enabled. + +Header compression is supported in the UE and the UPF. + +## 6.5.2.2 Mobility + +Mobility is supported as for normal UEs in IDLE mode. When the UE enters a new TA currently not part of the UE registration area, the UE will initiate a registration update. During the UE registration update, the AMF notifies the SMF about the UE location and the SMF may decide to relocate the UPF. When UPF is to be relocated, the SMF activates the PDU session so UPF N3 UL TEID is sent to RAN. The RAN then updates the new UPF index and the UPF N3 UL TEID to UE. SSC mode 2 mobility is probably appropriate for infrequent small data. + +The solution assumes the Rel-15 5G baseline that the SMF can be used throughout the PLMN (e.g. a specific CIoT slice may be used), but UPF can be changed as of above if needed. + +In roaming cases, a UPF in the VPLMN is used for SDFP support. + +## 6.5.2.3 Security + +In the SDFP the UE sends traffic without having set up the regular AS security. + +In the described solution the security protection is done by security contexts in the UE and the AMF/SMF/UPF. These are established as part of existing signalling, hence keeping the signalling overhead for small data to a minimum. The SDFP security information is stored in the SMF, UPF and the UE as part of the PDU Session Resource Request information. It is kept regardless if the SDFP is active or not, i.e. the security information is kept as long as the SDFP remains enabled. When the SDFP security information is updated for the UE, the AMF also updates the SMF/UPF with new SDFP security information. + +If AMF is changed e.g. due to mobility, a new SDFP security information is established by AMF during the Registration Update procedure and provided to the SMF/UPF and to the UE. + +The security protocol between the UE and the UPF consists of the same or similar protocols to the E-UTRA PDCP layer, i.e. with integrity protection and ciphering functionality. + +**Editor's note:** The security aspects of the solution need to be checked by SA WG3. + +## 6.5.2.4 UPF and PDU Session information in the UE + +The UPF information provided to the UE should not disclose the internal network architecture and addressing. RAN therefore has a list of UPFs that support SDFP, with an index and an IP address for each UPF in the list. The list of UPFs supporting SDFP is preconfigured in the RAN and each RAN node in the same UPF service area has the same information. + +When a PDU Session is created for SDFP, or activated by SMF, RAN receives from the AMF/SMF a UPF Tunnel information and a SDFP indication. Based on the IP address in the UPF Tunnel information and the RAN list of UPFs with SDFP support, RAN determines the UPF index. RAN sends the UPF index and the UPF N3 UL TEID to UE. + +### 6.5.3 Support of EPC interworking + +#### **Mobility from EPC to 5GC:** + +At mobility from EPC to 5GC, the PDU Session needs to be activated and the UPF information is provided to the UE by RAN as part of the registration procedure. + +#### **CIoT support capability detection:** + +During mobility through N26 interface, the source AMF(SMF)/MME detects the target side CIoT support capability through DNS/NRF query or location configuration. See TS 29.303 [17] and TS 29.510 [18]. Based on the CIoT support capabilities, source side determines if CIoT related PDU sessions or PDN connections shall be transferred. + +During Idle mobility through N26 interface, the new AMF(SMF)/MME indicates CIoT support capability at the new side. Based on the capability at the new side, the old AMF(SMF)/MME determines if CIoT related PDU sessions or PDN connections shall be transferred. + +#### **Unstructured PDU type vs Non-IP PDN type:** + +For PDU session with unstructured PDU type, SMF shall set the PDN type to Non-IP during transfer to EPC. When Non-IP PDN type PDN connection is received from EPC side, SMF shall set the PDU session type to Unstructured. This is specified in TS 23.502 [7], clause 4.11 (Rel-15). + +#### **Selection of control plane or user plane CIoT optimization:** + +When SDFP PDU session is transferred to EPS side, it can either use the control plane CIoT optimization or user plane CIoT optimization based on preferred and supported network behaviour between UE and EPC. + +## 6.5.4 Procedures + +### 6.5.4.1 UE requested SDFP PDU session establishment + + + +``` + +sequenceDiagram + participant UE + participant (R)AN + participant AMF + participant UPF + participant SMF + participant PCF + participant UDM + participant DN + + UE->>AMF: 1. PDU Session Establishment Request + Note over AMF: 2. SMF selection + AMF->>SMF: 3a. Namf_PDUSession_CreateSMContext Request + SMF->>UDM: 4a-4b. Registration/ Subscription retrieval/ +Subscription for updates + UDM-->>SMF: + SMF->>AMF: 5. Namf_PDUSession_CreateSMContext Response + rect rgb(255, 255, 255) + Note over UE, DN: 6. PDU Session authentication/authorization + end + Note over SMF: 7a. PCF selection + SMF->>PCF: 7b. Session Management Policy Establishment or Modification + PCF-->>SMF: + Note over SMF: 8. UPF selection + SMF->>PCF: 9. Session Management Policy Modification + PCF-->>SMF: + SMF->>UPF: 10a. N4 Session Establishment/Modification Request + UPF-->>SMF: 10b. N4 Session Establishment/Modification Response + SMF->>AMF: 11. Namf_Communication_N1N2MessageTransfer + AMF->>(R)AN: 12. N2 PDU Session Request (NAS msg) + (R)AN->>UE: 13. AN-specific resource setup (PDU Session Establishment Accept) + (R)AN->>AMF: 14. N2 PDU Session Request Ack + Note over UE, UPF: First Uplink Data + AMF->>SMF: 15. Nsmf_PDUSession_UpdateSMContext Request + SMF->>UPF: 16a. N4 Session Modification Request + UPF-->>SMF: 16b. N4 Session Modification Response + SMF->>AMF: 17. Nsmf_PDUSession_UpdateSMContext Response + SMF-->>AMF: 18. Nsmf_PDUSession_SMContextStatusNotify + SMF-->>UE: 19. IPv6 Address Configuration + Note over UE, UPF: First Downlink Data + Note over SMF, UDM: 20. Unsubscription / Deregistration + SMF-->>UDM: + +``` + +Sequence diagram for UE-requested PDU Session Establishment for SDFP. Lifelines: UE, (R)AN, AMF, UPF, SMF, PCF, UDM, DN. The process involves 20 steps including PDU Session Establishment Request, SMF selection, Nsmf\_PDUSession\_CreateSMContext Request, PDU Session authentication/authorization, PCF selection, Session Management Policy Establishment or Modification, UPF selection, Session Management Policy Modification, N4 Session Establishment/Modification Request/Response, N2 PDU Session Request (NAS msg), AN-specific resource setup, N2 PDU Session Request Ack, Nsmf\_PDUSession\_UpdateSMContext Request, N4 Session Modification Request/Response, Nsmf\_PDUSession\_UpdateSMContext Response, Nsmf\_PDUSession\_SMContextStatusNotify, IPv6 Address Configuration, and Unsubscription / Deregistration. + +**Figure 6.5.4.1-1: UE-requested PDU Session Establishment for SDFP** + +The procedure assumes that the UE has already registered on the AMF. Below are some modifications for SDFP compared to the existing PDU Session Establishment procedure. The SDFP information is kept in the UE for the duration of the PDU Session. The SDFP information can be updated as part of the registration update procedure, e.g. to reflect UPF changes. + +1. UE provides an indication it wants to establish a SDFP PDU session. Additionally, the UE could provide NSSAI indicating a specific network slice for SDFP which could be used by the RAN to select an AMF that supports SDFP. +2. AMF selects an SMF that supports SDFP. +3. The AMF generates SDFP security information with same or similar information as normally is provided to RAN for PDCP when SDFP is not used. The SDFP security information is forwarded to the SMF/UPF (and to RAN/UE in step 12-13). + +**Editor's note:** SA WG3 should check if the SDFP security information could be derived in the RAN based on the existing AS security information available in the RAN (might avoid change to step 12). + +... + +8. SMF selects a UPF that supports SDFP. + +... + +10. SMF performs N4 Session Establishment including setting up the SDFP security context in the UPF. During this procedure the UE UPF and PDU Session information will be generated. + +12. The SDFP security information is sent to the RAN. + +13. RAN determines the UPF index based on the UPF Tunnel information received in step 12. RAN sends the UPF index, the UPF UL TEID and the SDFP security information to the UE. + +- 15-16a. The SDFP security information is sent to the SMF/UPF. + +#### 6.5.4.2 SDFP transfer initiated by UL data + +The following figure shows an example of how MO small data packet is passed from the UE in UL. The term "SDFP session" is used in the text below meaning the time from a fast path is established (e.g. DRB is created) until it is released (e.g. inactivity timeout). + + + +``` + +sequenceDiagram + participant UE + participant RAN + participant AMF + participant UPF + + Note left of RAN: 8. UP Act. Timeout + Note right of UPF: 8. UP Act. Timeout + + UE->>RAN: 1. RRC for SDFP + RAN-->>AMF: 1a. Paging + RAN-->>AMF: 1b. N2 connection establishment + UE->>RAN: 2. UL small data + RAN->>AMF: 3. UL small data + AMF->>UPF: 4. UL small data + UPF-->>AMF: 5. DL small data + AMF-->>RAN: 6. DL small data + RAN-->>UE: 7. DL small data + UE->>RAN: 9. RRC Release + +``` + +Sequence diagram illustrating SDFP transfer initiated by UL data. The diagram shows interactions between UE, RAN, AMF, and UPF. The sequence starts with the UE sending an RRC for SDFP to the RAN. The RAN then sends a Paging message to the AMF (1a) and an N2 connection establishment message to the AMF (1b). The UE sends UL small data to the RAN (2), which is forwarded to the AMF (3) and then to the UPF (4). The UPF sends DL small data to the AMF (5), which is forwarded to the RAN (6) and then to the UE (7). The RAN and UPF both have an inactivity timeout (8). Finally, the UE sends an RRC Release message to the RAN (9). + +**Figure 6.5.4.2-1: SDFP transfer initiated by UL data** + +1. The UE establishes an RRC for SDFP transfer. Parameters for selection of UPF for the PDU Session for the UE are passed to the RAN i.e. the UPF index and the UPF UL TEID. + +**Editor's note:** The detailed solution for this part should be discussed in RAN WGs. An alternative would be to transfer the parameters as part of the UL data PDU. + +1a/b. In case AMF trigger paging towards RAN (e.g. due to N1 CP signalling) during an ongoing "SDFP transfer initiated by UL data", RAN may set up N2 UE association using the 5G S-TMSI received in step 1 and provide the AMF with NGAP RAN UE ID. AMF replies with NGAP AMF UE ID. + +NOTE: This step may be performed at any time between step 1 and 6. + +2. The UE encrypts, and integrity protects an UL data PDU and sends it to RAN. + +3. RAN forwards the UL data PDU on the N3 tunnel to the selected UPF. RAN selects the UPF and the N3 tunnel based on the SDFP information provided by the UE (i.e. UPF index and the UPF UL TEID) and the RAN preconfigured list of UPFs supporting SDFP. RAN will also provide the UPF with RAN N3 DL Tunnel Info for the SDFP session. + +4. The UPF checks integrity protection and decrypts the UL data PDU. If passed the check, the UPF forwards the UL data on the N6/N9 interface. In addition, the UPF enables subsequent DL data transmissions to the RAN node it received the UP data PDU from N6/N9 interface. + +5. A DL data packet may arrive on N6/N9 shortly after, e.g. an acknowledgement. + +6. The UPF encrypt and integrity protects the DL data PDU and passes it to the RAN node, which was enabled in step 3-4. + +7. RAN forwards the DL data PDU to the UE. + +8-9. Based on a UP Activity Timeout timer in RAN and UPF the SDFP information context in RAN is released and DL data transmission in the UPF is disabled by setting the SDFP in a non-active state. RAN releases the RRC connection. + +### 6.5.4.3 Alternative 1: SDFP transfer initiated by DL data + +Small data initiated in DL on a QoS flow where fast path is enabled but not active (i.e. the RAN N3 DL TEID is unknown or expired), is handled as described in the figure below. It should be noted that compared to when small data is initiated UL, an additional paging of the UE is required. + + + +``` + +sequenceDiagram + participant UE + participant RAN + participant AMF + participant SMF + participant UPF + + Note right of UPF: 1. DL Data + UPF->>SMF: 2. DL Data Notification + SMF->>AMF: 3. Namf_MT_EnableUEReachability ( FP ind ) + AMF->>RAN: 4. Paging (FP ind) + RAN->>UE: 5. Paging (FP ind) + UE->>RAN: 6. RRC Establishment (NAS: SR, UPF Index & TEID, PDU Session ID) + RAN->>AMF: 7. N2 message (NAS: SR, RAN N3 TEID, PDU Session ID) + AMF->>SMF: 8. Nsmf_PDUSession_UpdateSMContext Request (RAN N3 TEID, PDU Session ID) + SMF->>UPF: 9. N4 Session Modification Req/Resp (RAN N3 TEID) + SMF->>AMF: 10. Nsmf_PDUSession_UpdateSMContext Response + AMF->>RAN: 11. DL Data + RAN->>UE: 12. DL Data + Note right of RAN: 14. UP Act. Timeout + Note right of UPF: 14. UP Act. Timeout + UE->>RAN: 15. RRC Release + +``` + +Sequence diagram for SDFP transfer initiated by DL data. The diagram shows interactions between UE, RAN, AMF, SMF, and UPF. The process starts with DL Data arriving at the UPF, followed by notifications and context updates through the SMF and AMF to the RAN, which then pages the UE. After RRC establishment and N2 message exchange, the UPF is updated with RAN N3 TEID. DL data is then transferred, followed by a timeout and RRC release. + +Figure 6.5.4.3-1: SDFP transfer initiated by DL data + +1. DL data arrives in the UPF for a PDU Session that is SDFP enabled but not currently active (i.e. the RAN N3 DL TEID is unknown or expired). +- 2-5. The PDU Session is in CM\_IDLE and the UPF notifies the SMF about DL data. SMF notifies the AMF using the Namf\_MT\_EnableUEReachability service including a Fast Path indicator for DL SDFP transfer. The AMF sends a paging message to the RAN with a Fast Path indicator included. The RAN pages the UE with a FP indicator included. +6. UE responds to the paging with a RRC establishment including a NAS Service Request. The Fast Path indicator in the received paging triggers the UE to also include the UPF Index and UPF UL TEID and PDU Session ID. As part of the RRC establishment, the RAN and the UE establishes a Data Radio Bearer (DRB) with default parameters for SDFP transmissions. +7. RAN understands based on the included UPF index and UPF UL TEID that a SDFP shall be established. RAN allocates a RAN N3 TEID, maps it to the DRB and establishes a N3 tunnel based on the SDFP information provided by the UE (i.e. UPF index and the UPF UL TEID) and the RAN preconfigured list of UPFs supporting SDFP. RAN sends an Initial UE message (NAS: Service Request, RAN N3 TEID, PDU Session ID) to AMF. +8. The AMF takes the received NAS Service Request as a response to the paging request. AMF sends a Nsmf\_PDUSession\_UpdateSMContext Request message with the NAS Service Request, RAN N3 TEID, PDU Session ID included to the SMF which handles the PDU Session. +9. The SMF understands based on the included RAN N3 TEID that the PDU Session shall be moved to active SDFP state. SMF sends a N4 Session Modification Request (RAN N3 TEID, PDU Session, Fast Path indicator) to the UPF. The UPF stores the RAN N3 TEID for the PDU Session and opens the PDU Session for SDFP transmissions. UPF acknowledges to SMF by sending a N4 Session Modification Response message. The SMF keeps the UE in CM-IDLE but may keep a record of the SDFP transmission, e.g. in charging information, or statistics. +10. SMF acknowledges to AMF by sending a Nsmf\_PDUSession\_UpdateSMContext Response to AMF. +11. UPF forwards any buffered DL data to the RAN. +12. RAN forwards DL data to the UE. +13. Any additional uplink and downlink small data may be transmitted. +- 14-15. The UP Activity Timeout timer expires in UPF and RAN. RAN releases the RRC connection. + +#### 6.5.4.3a Alternative 2: SDFP transfer initiated by DL data + +This is alternative solution for DL data transfer on a QoS flow where fast path is enabled but not active (i.e. the RAN N3 DL TEID is unknown or expired), as described in the figure below. In this solution, if the UE has PDU session for SDFP and receives paging from the network, it always establishes the DRB for PDU session for SDFP. The RAN can send dummy uplink packets to UPF to establish the tunnel between RAN and UPF. + + + +``` + +sequenceDiagram + participant UE + participant RAN + participant AMF + participant SMF + participant UPF + + Note right of UPF: 1. DL Data + UPF->>SMF: 2. DL Data Notification + SMF->>AMF: 3. Namf_MT_EnableUEReachability + AMF->>RAN: 4. Paging + RAN->>UE: 5. Paging + UE->>RAN: 6. RRC for SDFP + RAN->>AMF: 7. N2 connection establishment + RAN->>UPF: 8. UL Data + UPF->>RAN: 9. DL Data + RAN->>UE: 10. DL Data + UE<-->RAN: 11. UL & DL Data + RAN<-->UPF: 11. UL & DL Data + Note over RAN: 12. UP Act. Timeout + Note over UPF: 13. UP Act. Timeout + RAN->>UE: 14. RRC Release + +``` + +Sequence diagram illustrating SDFP transfer initiated by DL data. The diagram shows interactions between UE, RAN, AMF, SMF, and UPF. The sequence starts with DL Data arriving at the UPF, followed by notifications and paging to the UE. The UE responds with an RRC establishment for SDFP transfer. The RAN establishes an N2 connection with the AMF and forwards UL data to the UPF. The UPF then forwards buffered DL data to the RAN, which in turn forwards it to the UE. Additional UL & DL data may be transmitted. Finally, UP Activity Timeout timers expire in the UPF and RAN, and the RAN releases the RRC connection. + +**Figure 6.5.4.3a-1: SDFP transfer initiated by DL data** + +1. DL data arrives in the UPF for a PDU Session that is SDFP enabled but not currently active (i.e. the RAN N3 DL TEID is unknown or expired). +- 2-5. The UE is in CM\_IDLE and the UPF notifies the SMF about DL data. SMF notifies the AMF using the Namf\_MT\_EnableUEReachability service for SDFP transfer. The AMF sends a paging message to the RAN. The RAN pages the UE. +6. UE responds to the paging with a RRC establishment for SDFP transfer. Parameters for selection of UPF for the PDU Session for the UE are passed to the RAN i.e. the UPF index and the UPF UL TEID. As part of the RRC establishment, the RAN and the UE establishes a Data Radio Bearer (DRB) with default parameters for SDFP transmissions. +7. RAN set up N2 UE association using the 5G S-TMSI received in step 4 and provide the AMF with NGAP UE ID. AMF replies with NG AMF ID. This step is same as step 1b in MO case. +8. RAN understands based on the included UPF index and UPF UL TEID that a SDFP shall be established. RAN allocates a RAN N3 DL TEID, maps it to the DRB and establishes a N3 tunnel based on the SDFP information provided by the UE (i.e. UPF index and the UPF UL TEID) and the RAN preconfigured list of UPFs supporting SDFP. The RAN then passes the uplink small data (can be dummy packets) sent by the UE in step 6 to the selected UPF. +9. The UPF stores the RAN N3 TEID for the PDU Session and forwards any buffered DL data to the RAN. +10. RAN forwards DL data to the UE. +11. Any additional uplink and downlink small data may be transmitted. +- 12-14. The UP Activity Timeout timer expires in UPF and RAN. RAN releases the RRC connection. + +## 6.5.5 Impacts on existing entities and interfaces + +**Editor's note:** This clause describes impacts to existing entities and interfaces. + +New parameter with SDFP security information on N1, N11, N4 and N2. + +New parameters UPF index and UPF UL TEID in RRC message to the UE. + +New parameter RAN N3 TEID in GTP-U message to UPF. + +SDFP function in UE, RAN, UPF, AMF and SMF. + +## 6.5.6 Evaluation + +**Editor's note:** This clause provides an evaluation of the solution. + +# 6.6 Solution 6: Small Data Communication based on Data PDU routed over the User Plane. + +## 6.6.1 Introduction + +### 6.6.1.1 General + +This solution applies to Key issue 1 and Key issue 2. The main idea of the solution is to provide a simple migration for the 5G-IoT UE implementation building on the CP CIoT optimization and at the same time keep the user data separated from the Control Plane within the Core Network. + +To overcome the drawback of routing user data via the Core Networks control plane function(s) AMF and SMF, a new proxy function is introduced that includes the functionality needed for handling of the user data in a Data PDU sent over Uu using Signalling Radio Bearer. + +Similar to CP CIoT optimization and NB-IoT RAT, the Data PDU is embedded in an RRC message (Signalling Radio Bearer, SRB). The Data PDU is transparent to the RRC layer, similar legacy NB-IoT. The difference compared to legacy is that the Data PDU shall not be passed to the NAS upper layer, instead passed to the new function/proxy that performs i.e. integrity protection, ciphering and header compression. + +NOTE 1: This solution does not address congestion issues related to the usage of Signalling Radio Bearers in RAN when an IoT device uses e.g. NB-IoT RAT and 5G CP CIoT optimization. + +NOTE 2: It is assumed that if this solution is selected for 5GS, then the UE will detect the 5G PLMN and support for small data communication by decoding the System Information Broadcasted in e.g. MIB-NB, SIB1-NB. + +### 6.6.1.2 Protocol stack for User data + +The figure below shows the protocol stack for user data including the new function/proxy here called New Upper layer. + + + +Figure 6.6.1.2-1: Protocol stack for User plane data. This diagram shows the protocol layers for UE, RAN, and UPF. UE layers: Application, IP/nonIP, New Upper layer, RRC, RLC, MAC, PHY. RAN layers: Relay (containing RRC, RLC, MAC, PHY) and N3. UPF layers: IP/nonIP, New Upper layer, and N3. Arrows show data flow from UE Application down to PHY, then through RAN Relay layers, and finally to UPF layers. + +Figure 6.6.1.2-1: Protocol stack for User plane data + +### 6.6.1.3 Architecture reference models + + + +Figure 6.6.1.3-1: Architecture for small data delivery via UPF to DN and NEF. This network architecture diagram shows UE connected to RAN via N1. RAN connected to AMF via N2 and to UPF via N3. AMF connected to SMF via N11. SMF connected to UPF via N4. UPF connected to DN via N6 and to NEF via Nx. + +Figure 6.6.1.3-1: Architecture for small data delivery via UPF to DN and NEF + +## 6.6.2 Functional Description + +The following principles apply: + +- Small data using encapsulated Data PDU: + - Small data is exchanged between the UE and the Proxy function using encapsulated Data PDU in both uplink and downlink direction. + - The proxy function is implemented in the UPF used as PDU Session Anchor (PSA) for the small data session. + + + +Figure 6.6.2-1: The location of the proxy function. This diagram is similar to Figure 6.6.1.3-1 but highlights the 'Proxy' function within the UPF. The UPF is shown with a dashed box labeled 'Proxy' inside it. The RAN connects to the UPF via N3, and the UPF connects to the DN via N6 and to the NEF via Nx. + +Figure 6.6.2-1: The location of the proxy function + +- RAN detects the message type is of Data PDU type. RAN forwards the Data PDU to the proxy function in the UPF. + +NOTE: The detection that the message type is of Data PDU type could be based on an indicator in the RRC message e.g. utilizing *criticalExtensionsFuture*. Details to be decided by RAN WG2. + +- The proxy function extracts or encapsulates the user data from/in the Data PDU. This includes e.g. the security operations and header compression. +- The proxy function forwards/receives the user data over the UPF to/from the PDU session anchor point. +- PDU Session Establishment: + - The PDU session establishment reuse the procedure in TS 23.502 [7], clause 4.3.2.2.1 with the difference that the UPF node will be configured with security parameters to be stored in the UE context. The AMF provides the security parameters via the SMF to the UPF and the UPF stores the UE Context as long as the PDU Session is established. +- Supported PDU session types: + - Small data transfer supports IP and unstructured data. +- Integrity protection, ciphering and header compression: + - Integrity protection and ciphering for small data are performed by a proxy function (Similar to existing NAS PDU integrity protection and ciphering functionality may be re-used in the proxy function). + +**Editor's note:** Detailed security solution for the proxy function is FFS and shall be selected and specified by SA WG3. Example of a possible solution could be to use the same NAS key but different packet counters for the different "flows", meaning that NAS signalling terminating in the AMF would have it's own packet counters and the user data packets terminating in the proxy will have it's own packet counters. Another possible solution could be to generate new key and packet counters for the User data communication between the UE and the proxy function. + +- UE and proxy function may perform header compression for IP data. +- Roaming: + - In case of home routed roaming the proxy is in the V-PLMN. The data is delivered from the UPF in V-PLMN, on the N9 interface, via the UPF in the H-PLMN to the Data Network. + - In case of roaming of NIDD via NEF an IWK-NEF located in the V-PLMN is used for providing interconnection with the NEF in the H-PLMN. The IWK-NEF (similar to IWK-SCEF in EPC) relays data between UPF/proxy function in V-PLMN to NEF in H-PLMN. +- Early Data Transmission may be initiated by the UE and the NG-RAN node may indicate to the PSA that the connection is triggered for EDT. EDT can be combined with AS based Release Assistance Information. +- AS based Release Assistance Information (RAI) can be used by the UE to indicate whether it is a single UL packet and if a single consecutive DL packet is expected. + - The RAN node will forward the RAI to the PSA and wait for receiving an End Indication and optionally DL Data PDU from the PSA. After receiving the End Indication, the RAN will send RRC message to the UE allowing the UE to re-enter RRC\_IDLE. The RRC message will include the optional DL Data PDU. + +### 6.6.3 Support of EPC interworking + +The UE supports EPC interworking by supporting both EPC NAS and 5G NAS plus the support for small data over NAS in both 4GS and 5GS. From a UE perspective the solution can be almost identical, only difference may be in the 5G solution where the UE might need to mark the Data PDU. + +## 6.6.4 Procedures + +### 6.6.4.1 Small Data via UPF + +#### 6.6.4.1.1 General + +Compared to EPC, 5GC requires that the UE first performs registration and then PDU Session Establishment for setting up all required PDU sessions. Before any procedures below, it is assumed that a successful registration procedure has been performed that included the UE's Preferred Network Behaviour information. + +#### 6.6.4.1.2 Assumptions + +- A UE that shall send or receive small data is assumed to have established a PDU session for small data. The PDU Session Anchor (PSA) stores the specific UE security parameters for the small data PDU session in the UE context. +- For a RAN node, there may be one specific UPF that acts as the PDU Session Anchor for all small data PDU sessions from multiple UEs. + - The small data from any UE, connected to that RAN node, is then forwarded via a common N3 tunnel towards this UPF. The tunnel is configured either when configuring the RAN node, or when the first small data PDU session is established (as in solution 29 in clause 6.29). + - The small data from the UPF to a UE is sent via the common N3 tunnel, for all small data UEs, connected to the RAN node that the UE is connected with. The RAN identifies the UE and the corresponding RRC Connection based on the UE ID (e.g. 5G-GUTI) and PDU session ID. + - If the RAN does not have a common N3 tunnel for small data PDU session when receiving small data from a UE, then the RAN node will trigger the establishment of a common N3 tunnel by sending an N2 message requesting the SMF to configure such. +- The UPF may keep track of the RRC connection to the UE by a UE Location Freshness Timer as proposed in solution 29 in clause 6.29. The timer is reset when the UPF receives UL traffic from the UE. As long as the UE Location Freshness Timer has not elapsed, the UPF sends a DL Data PDU to the same RAN node from which it last received UL traffic from this UE. When the DL Data PDU shall be delivered to the UE and the UE Freshness Activity timer has elapsed the UPF requests the AMF to page the UE by sending a Downlink Data Notification to the SMF. +- When the DL Data PDU cannot be delivered to the UE, the RAN node deletes the Data PDU and notifies the UPF that the UE is not reachable. Then the UPF may requests the AMF to page the UE. +- Once the common N3 tunnel is established for small data communication, there is no need to release it as long as the Common UPF node for small data is not changed. + +## 6.6.4.1.3 + +## PDU Session Establishment + + + +``` +sequenceDiagram + participant UE + participant RAN + participant AMF + participant SMF + participant UPF/Proxy + participant PCF + participant UDM + + Note left of UE: 1. PDU Session Establishment Request + UE->>AMF: Request + Note right of AMF: 2. Step 2-12 according to TS 23.502 clause 4.3.2.2.1 + AMF->>RAN: + RAN->>UE: 3. PDU session establishment Accept + Note right of AMF: 4. Step 14-16 according to TS 23.502 clause 4.3.2.2.1 + AMF->>RAN: + RAN->>UE: +``` + +Sequence diagram for PDU Session Establishment enabling Data over UPF. The diagram shows interactions between UE, RAN, AMF, SMF, UPF/Proxy, PCF, and UDM. Step 1: UE sends PDU Session Establishment Request to AMF. Step 2: AMF initiates steps 2-12 according to TS 23.502 clause 4.3.2.2.1. Step 3: AMF sends PDU session establishment Accept to UE. Step 4: AMF initiates steps 14-16 according to TS 23.502 clause 4.3.2.2.1. + +**Figure 6.6.4.1.3-1: PDU Session Establishment enabling Data over UPF** + +1. The UE sends a PDU session establishment request message that includes the PDU session ID, PDU type, DNN and S-NSSAI. Based on e.g. the Preferred Network Behaviour and S-NSSAI the AMF selects an SMF and invokes the Nsmf\_PDUSession\_CreateSMContext request to trigger the PDU session establishment. +2. Steps 2-12 are executed according to TS 23.502 [7], clause 4.3.2.2.1 with the following changes: + - The AMF provides UE specific security parameters to the SMF. + - In step 10, the SMF includes required security parameters for the proxy function located in the UPF node that acts as the PDU Session Anchor (PSA). + - A common N3 tunnel is established for the requested PDU session, if the N3 tunnel was not already established. +3. The AMF forwards the PDU session establishment accept message to the UE. +4. Steps 14-16 are executed according to TS 23.502 [7] clause 4.3.2.2.1 + +#### 6.6.4.1.4 Mobile Originated Data Transport + + + +``` + +sequenceDiagram + participant UE + participant RAN + participant AMF + participant SMF + participant UPF/Proxy + + Note left of UE: 0. UE is in CM-IDLE + UE->>RAN: 1. RRC Connection establishment (AN parameters, Transport(PDU session ID, Data PDU)) + Note right of RAN: 2. Detects that the transport message is for the proxy function. + RAN->>UPF/Proxy: 3. Forward UL Data PDU + Note right of UPF/Proxy: 4. The proxy checks integrity and decrypts data and provides Header Decompression + UPF/Proxy->>DN: 5. Data + Note left of UPF/Proxy: DL data available at UPF + Note right of UPF/Proxy: 6. Apply Header Compression, encryption and integrity protection + UPF/Proxy->>RAN: 7. Forward DL Data PDU + RAN->>UE: 8. RRC DL message (transport(PDU session ID, Data PDU)) + Note bottom: 9. AN release procedure (see TS 23.502 clause 4.2.6) + +``` + +The sequence diagram illustrates the Mobile Originated Data Transport process. It begins with the UE in CM-IDLE state. Step 1 shows the UE sending an RRC Connection establishment message to the RAN, which includes AN parameters and a Transport PDU containing the session ID and data. Step 2 indicates the RAN detects this message is for the proxy function. Step 3 shows the RAN forwarding the UL Data PDU to the UPF/Proxy. Step 4 details the proxy checking integrity, decrypting data, and providing header decompression. Step 5 shows data being forwarded to the DN. A dashed box labeled 'DL data available at UPF' contains steps 6 and 7. Step 6 shows the proxy applying header compression, encryption, and integrity protection. Step 7 shows the UPF/Proxy forwarding the DL Data PDU to the RAN. Step 8 shows the RAN sending an RRC DL message to the UE. Step 9 indicates an AN release procedure is initiated. + +Sequence diagram for Mobile Originated Data Transport showing interactions between UE, RAN, AMF, SMF, and UPF/Proxy. + +**Figure 6.6.4.1.4-1: Mobile Originated Data Transport** + +0. The UE is in CM-IDLE and has an established small data PDU session. +1. The UE establishes an RRC connection and sends an integrity protected Data PDU as part of this. The Data PDU carries encrypted uplink data as payload and the corresponding PDU session ID. +2. RAN detects that the transport message from the UE is for the Proxy in the PSA. The RAN node associates the UE ID (e.g. 5G-GUTI) with the RRC connection in case of DL data forwarding in step 8. +3. RAN forwards the Data PDU together with the PDU session ID and UE ID on the N3 Tunnel to the UPF node acting as PSA and to the proxy function in the UPF node. + If the RAN does not have a common N3 tunnel for small data PDU session, then the RAN node will trigger the establishment of a common N3 tunnel by sending an N2 message requesting the SMF to configure such. +4. The proxy function in the UPF node verifies the integrity of the incoming Data PDU and decrypts the data in the payload and decompresses the IP header if header compression was applied in the UE on the IP data. +5. UPF forwards the data to the Data Network (DN). +6. [Conditional] If there is data available in UPF, the proxy within UPF applies integrity protection, encryption and header compression for the transport to the UE. +7. [Conditional] The UPF forwards the Data PDU together with the PDU session ID and UE ID over the N3 tunnel to the RAN. +8. [Conditional] RAN identifies the receiver and sends the Data PDU to the UE over DL RRC signaling message. + +9. Based on RAN specified inactivity conditions, the RAN releases the UE's RRC connection and corresponding CN connections according to AN release procedure in TS 23.502 [7], clause 4.2.6. + +#### 6.6.4.1.4b Mobile Originated Data Transport, using EDT and AS based RAI + + + +``` + +sequenceDiagram + participant UE + participant RAN + participant AMF + participant SMF + participant UPF/Proxy + + Note over UE: 0. UE is in CM-IDLE + UE->>RAN: 1. RRCEarlyDataRequest (AN parameters (RAI), Transport(PDU session ID, Data PDU)) + Note over RAN: 2. Detects that the transport message is for the proxy function. + RAN->>UPF/Proxy: 3. Forward UL Data PDU + Note over UPF/Proxy: 4. The proxy checks integrity and decrypts data and provides Header Decompression + UPF/Proxy->>External: 5. Data + Note over SMF: 6. Apply Header Compression, encryption and integrity protection + SMF->>RAN: 7. Forward DL Data PDU + RAN->>UE: 8. RRCEarlyDataComplete (transport(PDU session ID, Data PDU)) + +``` + +Sequence diagram for Mobile Originated Data Transport, using EDT and AS based RAI. The diagram shows the interaction between UE, RAN, AMF, SMF, and UPF/Proxy. The process starts with the UE in CM-IDLE state. The UE sends an RRCEarlyDataRequest message to the RAN. The RAN detects that the transport message is for the proxy function. The RAN forwards the UL Data PDU to the UPF/Proxy. The proxy checks integrity and decrypts data and provides Header Decompression. The proxy sends the Data to an external entity. The SMF applies Header Compression, encryption and integrity protection. The SMF forwards the DL Data PDU to the RAN. The RAN sends an RRCEarlyDataComplete message to the UE. + +**Figure 6.6.4.1.4b-1: Mobile Originated Data Transport** + +0. The UE is in CM-IDLE and has an established small data PDU session. + 1. The UE sends RRCEarlyDataRequest message including an integrity protected Data PDU. The UE may also include an AS based Release Assistance Information (RAI), that indicates whether a DL message is expected or this was a single uplink data packet. The Data PDU carries encrypted uplink data as payload and the corresponding PDU session ID. + 2. RAN detects that the transport message from the UE is for the Proxy in the PSA and check the RAI if such was included. The RAN node associates the UE ID (e.g. 5G-GUTI) with the RRC connection in case of DL data forwarding in step 8. + 3. RAN forwards the Data PDU together with the PDU session ID, UE ID, EDT indicator and RAI over the N3 Tunnel to the UPF node acting as PSA and to the proxy function in the UPF node. +- If the RAN does not have a common N3 tunnel for small data PDU session, then the RAN node will trigger the establishment of a common N3 tunnel by sending an N2 message requesting the SMF to configure such. +4. The proxy function in the UPF node verifies the integrity of the incoming Data PDU and decrypts the data in the payload and decompresses the IP header if header compression was applied in the UE on the IP data. + +Furthermore, if RAI was included the UPF node should either: + +- send an End Indicator, set to "No Further Data", to the RAN node if the RAI single UL data packet and the UPF node does not have any pending downlink data; + +- or, wait for the expected DL data packet. + +If there was no RAI included then the UPF may send an End Indicator, set to "No Further Data", to RAN if the UPF does not have any pending DL data. This will enable the RAN to quickly send RRCEarlyDataComplete message to the UE. + +- UPF forwards the data to the Data Network (DN). +- [Conditional] If there is data available in UPF, the proxy within UPF applies integrity protection, encryption and header compression for the transport to the UE. +- The UPF either forwards the Data PDU together with the PDU session ID and UE ID or send an empty Data PDU together with an End Indicator, set to "No Further Data", and UE ID over the N3 tunnel to the RAN. +- The RAN identifies the receiver using the UE ID and sends a RRCEarlyDataComplete message to the UE. The RRCEarlyDataComplete message will include the Data PDU to the UE. The UE will return the RRC\_IDLE after this step. + +#### 6.6.4.1.5 Mobile Terminated Data Transport + + + +``` + +sequenceDiagram + participant UE + participant RAN + participant AMF + participant SMF + participant UPF/Proxy + + Note right of UPF/Proxy: 0. DL data + Note over UE, RAN, AMF, SMF, UPF/Proxy: 1. UE in Idle: Network Triggered Service Request according to TS 23.502 clause 4.2.3.3 + Note right of UPF/Proxy: 2. Apply Header Compression, encryption and integrity protection + Note over SMF, RAN: 3. Forward DL Data PDU + Note over RAN, UE: 4. RRC DL message (transport(PDU session ID, Data PDU)) + Note left of UE: UL data available + Note over UE, RAN: 5. RRC UL message(transport(PDU session ID, Data PDU)) + Note over RAN: 6. Detects that the transport message shall be forwarded to the Proxy in the UPF + Note over RAN, UPF/Proxy: 7. Forward UL Data PDU + Note right of UPF/Proxy: 8. The proxy applies Header decompression and checks integrity and decrypts data + Note right of UPF/Proxy: 9. UL data + Note over UE, RAN, AMF, SMF, UPF/Proxy: 10. AN release procedure (see TS 23.502 clause 4.2.6) + +``` + +The sequence diagram illustrates the Mobile Terminated Data Transport process. It begins with the UPF/Proxy receiving downlink data (0). A dashed box labeled '1. UE in Idle: Network Triggered Service Request according to TS 23.502 clause 4.2.3.3' spans the initial interaction between the UE, RAN, AMF, SMF, and UPF/Proxy. Next, the UPF/Proxy applies header compression, encryption, and integrity protection (2). The SMF then forwards the DL Data PDU to the RAN (3), which sends an RRC DL message to the UE (4). A dashed box labeled 'UL data available' contains the UE sending an RRC UL message to the RAN (5). The RAN detects that the transport message should be forwarded to the proxy in the UPF (6). The RAN then forwards the UL Data PDU to the UPF/Proxy (7). The proxy applies header decompression, checks integrity, and decrypts the data (8), resulting in the final UL data (9). Finally, an AN release procedure is initiated across all components (10). + +Sequence diagram for Mobile Terminated Data Transport showing interactions between UE, RAN, AMF, SMF, and UPF/Proxy. + +**Figure 6.6.4.1.5-1: Mobile Terminated Data Transport** + +- The UPF receives downlink data for a small data PDU Session to the UE. + +1. Network Triggered Service request according to TS 23.502 [7] clause 4.2.3.3 step 2-6 is performed. The UE responds on the page with a Control Plane Service Request NAS message which will not trigger any DRB establishment. +2. The proxy function in the UPF node acting as PSA apply header compression, ciphering and integrity protection. +3. The UPF forwards available Data PDU together with the PDU session ID and UE ID to the RAN node over the N3 Tunnel. +4. RAN delivers the Data PDU over RRC to the UE. +5. [Conditional] The UE sends an integrity protected Data PDU in an uplink RRC message. The Data PDU carries encrypted uplink data as payload and corresponding PDU session ID. +6. [Conditional] The RAN detects that the transport message is from the UE and for the Proxy in the UPF node. +7. [Conditional] The RAN forwards the Data PDU together with the PDU session ID and UE ID to the proxy function located within the UPF node. +8. [Conditional] The proxy function verifies the integrity of the incoming Data PDU and decrypts the data in the payload and decompresses the IP header if header compression was applied in the UE on the IP data. +9. [Conditional] The UPF forwards the data to the DN. +10. Based RAN specified inactivity conditions, the RAN releases the UE's RRC connection and corresponding CN connections according to AN release procedure in TS 23.502 [7], clause 4.2.6. + +#### 6.6.4.2 NIDD via NEF specific procedures + +##### 6.6.4.2.1 General + +This clause details the additional functionality to support NIDD via NEF as shown in the architecture reference model in clause 6.6.1.3. The procedures show reuse of T8 and T6 interface, it is possible that stage 3 would decide to use an alternative protocol than T6 for the Nx reference point. + +##### 6.6.4.2.2 Nx Session Establishment + +On top of the PDU session establishment procedure in clause 6.6.4.1.3 the following applies: + +- Based on either subscription data or DNN with "invoke NEF selection" indicator, the SMF will select an NEF for NIDD based on the UE subscription profile. +- The SMF configures the NEF and UPF anchor for data transfer for the specific UE ID and PDU session ID. +- The SMF also updates the AMF with the NEF ID with Nsmf\_PDUSession\_CreateSMContext Response in order for the AMF to invoke Namf\_EventExposure\_Notify (User Identity) service once the UE becomes reachable or is about to become reachable. + +### 6.6.4.2.3 Mobile Terminated NIDD procedure + + + +``` + +sequenceDiagram + participant SCS/AS + participant NEF + participant UPF/Proxy + participant SMF + participant AMF + participant RAN + participant UE + + Note right of SCS/AS: 1. MT NIDD Submit Request + SCS/AS->>NEF: 1. MT NIDD Submit Request + Note right of NEF: 2a. Authorization and load control + NEF-->>SCS/AS: 2b. MT NIDD Submit Response + Note right of NEF: 3. NIDD Submit Request + NEF->>UPF/Proxy: 3. NIDD Submit Request + Note right of UPF/Proxy: 4. UE in Idle: Network Triggered Service Request according to TS 23.502 clause 4.2.3.3 + UPF/Proxy->>RAN: 4. UE in Idle: Network Triggered Service Request according to TS 23.502 clause 4.2.3.3 + Note right of RAN: Optional steps if UE is not reachable in step 4 + Note right of UPF/Proxy: 4b. NIDD Submit Response + UPF/Proxy-->>NEF: 4b. NIDD Submit Response + Note right of NEF: 4c. NEF buffer DL data + Note right of NEF: 5. MT NIDD Submit Response + NEF-->>SCS/AS: 5. MT NIDD Submit Response + Note right of AMF: 6a. Naf_EventExposure_Notify + AMF-->>SMF: 6a. Naf_EventExposure_Notify + Note right of NEF: 6b. NIDD Submit Indication + NEF-->>SMF: 6b. NIDD Submit Indication + Note right of NEF: 7. NIDD Submit Request + NEF->>UPF/Proxy: 7. NIDD Submit Request + Note right of UPF/Proxy: 8. MT Data Transport according to clause 6.6.4.1.5 step 2-4 + UPF/Proxy->>RAN: 8. MT Data Transport according to clause 6.6.4.1.5 step 2-4 + Note right of UPF/Proxy: 9. NIDD Submit Response + UPF/Proxy-->>NEF: 9. NIDD Submit Response + Note right of NEF: 10. MT NIDD Submit Response + NEF-->>SCS/AS: 10. MT NIDD Submit Response + +``` + +Sequence diagram for Mobile Terminated NIDD procedure via NEF. Lifelines: UE, RAN, AMF, SMF, UPF/Proxy, NEF, SCS/AS. The process involves an MT NIDD Submit Request from SCS/AS to NEF, authorization, a NIDD Submit Request from NEF to UPF/Proxy, a Network Triggered Service Request from UPF/Proxy to UE (if idle), optional steps if UE is not reachable, a NIDD Submit Response from UPF/Proxy to NEF, an Naf\_EventExposure\_Notify from AMF to SMF, a NIDD Submit Indication from NEF to SMF, a NIDD Submit Request from NEF to UPF/Proxy, MT Data Transport from UPF/Proxy to UE, a NIDD Submit Response from UPF/Proxy to NEF, and finally an MT NIDD Submit Response from NEF to SCS/AS. + +**Figure 6.6.4.2.3-1: Mobile Terminated NIDD Transport via NEF** + +0. The UE has registered and performed PDU session establishment for NIDD via NEF. + 1. If SCS/AS has already activated the NIDD service for a given UE, and has downlink non-IP data to send to the UE, the SCS/AS sends an MT NIDD Submit Request (External Identifier or GPSI, non-IP data, Reliable Data Service Configuration, Maximum Latency, Priority, PDU Session Establishment Option) message to the NEF. + 2. The NEF determines the PDU session Context based on the DNN associated with the NIDD configuration and the User Identity. If an NEF PDU session context corresponding to the External Identifier or GPSI included in step 1 is found, then the NEF checks whether the SCS/AS is authorised to send NIDD requests and that the SCS/AS has not exceeded the quota of data submission to the PDU session. +- If no NEF PDU session context is found, then the NEF, depending on PDU session Establishment Option, may either: +- send a NIDD Submit Response (Cause) with appropriate error cause value. The flow stops at this step; or + - perform device triggering towards the UE to establish a PDU session according to TS 23.502 [7] clause 4.13.2.2. +3. If an NEF PDU session context corresponding to the External Identifier or GPSI included in step 1 is found, then the NEF sends a NIDD Submit Request (User Identity, PDU session ID, NEF ID, non-IP data, NEF Wait Time, Maximum Re-transmission time) message toward the UPF/proxy function. + +4. If the UPF can immediately deliver the non-IP data to the UE e.g. when UE is already in RRC\_CONNECTED mode, or UE is in RRC\_IDLE and UPF is able to initiate paging procedure (see TS 23.502 [7] clause 4.2.3.3), the procedure proceeds at step 8 + +If the UE is determined not reachable within the NEF Wait time the UPF sends NIDD Submit Response (Cause, Requested Re-Transmission Time) to the NEF. + +The AMF may indicate in Requested Re-Transmission time IE the time when the NEF is expected to re-transmit the DL data to the currently unreachable UE. In this case the NEF buffers the DL data and wait for the notification that the UE becomes reachable. + +5. The NEF may send an MT NIDD Submit Response (Requested Re-Transmission time, Cause) to the SCS/AS informing of the received results. The flow stops at this step. +6. When the AMF detects that the UE is reachable (e.g. by performing periodic registration, or when the UE is about to become reachable e.g. extended idle mode DRX cycle expiring, AMF anticipating MO communication pattern for the UE etc.), and the AMF has the Not Reachable for NIDD flag set, then the AMF invokes *Namf\_EventExposure\_Notify* (User Identity) service. The NIDD Submit Indication (User Identity) message could also come from the UPF if the UE initiated MO communication, +7. If the data has not been purged, the NEF sends a NIDD Submit Request (User Identity, PDU session ID, NEF ID, non-IP data, NEF Wait Time, Maximum Re-transmission time) message toward the UPF/Proxy function. +8. UPF/proxy function performs MT data transport according to clause 6.6.4.1.5 +9. If the UPF/proxy function was able to initiate step 8, then the UPF sends a NIDD Submit Response (cause) message towards the NEF acknowledging the NIDD Submit Request from NEF received in step 3 or step 7 +10. The NEF sends an MT NIDD Submit Response to acknowledge the MT NIDD Submit Request. + +#### 6.6.4.2.4 Mobile Originated NIDD procedure + + + +``` + +sequenceDiagram + participant UE + participant RAN + participant AMF + participant SMF + participant UPF/Proxy + participant NEF + participant SCS/AS + + Note over UE, UPF/Proxy: 1. MO Data Transport according to clause 6.6.4.1.4 step 0-4 + UPF/Proxy->>NEF: 2. NIDD Submit Request + NEF->>SCS/AS: 3. MO NIDD Indication + SCS/AS->>NEF: 4. MO NIDD Ack + NEF->>UPF/Proxy: 5. NIDD Submit Response + +``` + +Sequence diagram for Mobile Originated NIDD procedure. The diagram shows seven vertical lifelines: UE, RAN, AMF, SMF, UPF/Proxy, NEF, and SCS/AS. Step 1 is a box spanning UE to UPF/Proxy labeled '1. MO Data Transport according to clause 6.6.4.1.4 step 0-4'. Step 2 is an arrow from UPF/Proxy to NEF labeled '2. NIDD Submit Request'. Step 3 is an arrow from NEF to SCS/AS labeled '3. MO NIDD Indication'. Step 4 is a return arrow from SCS/AS to NEF labeled '4. MO NIDD Ack'. Step 5 is a return arrow from NEF to UPF/Proxy labeled '5. NIDD Submit Response'. + +**Figure 6.6.4.2.4-1: Mobile Originated NIDD Transport via NEF** + +0. The UE has registered and performed PDU session establishment for NIDD via NEF. +1. The UE sends MO data according to clause 6.6.4.1.4 including the PDU session ID corresponding to the session for NIDD via NEF. +2. The UPF sends NIDD Submit Request (User Identity, PDU session ID, NEF ID, non-IP data, MO Exception data counter) message to the NEF. +3. When the NEF receives the non-IP data, and finds an NEF PDU session context and the related T8 Destination Address, then it sends the non-IP data to the SCS/AS that is identified by the T8 Destination address, in a MO NIDD Indication (External Identifier or GPSI, non-IP data, Reliable Data Service Configuration). +4. The SCS/AS responds to the NEF with a MO NIDD Acknowledgement. +5. The NEF sends NIDD Submit Response to UPF. + +## 6.6.5 Impacts on existing entities and interfaces + +### UE: + +- The handling of user data to/from the application. +- Support for new indication in the RRC Layer used for routing data PDU to and from the UPF. + +### RAN: + +- New indication in the RRC Layer used for routing small data to and from the UPF. +- Support the common N3 tunnel for all small data in DL and UL. + +### AMF: + +- Provide the UE specific security parameters to UPF and UE. + +**Editor's note:** Details are FFS and depends on SA WG3 design. + +### SMF: + +- Selection and configuration of UPF based on the small data routing. + +### UPF: + +- Adding the Proxy function to the UPF that includes functionalities as e.g. integrity protection, encryption and header compression. +- Sending small Data PDUs over the common N3 tunnel. + +## 6.6.6 Evaluation + +Even though the signalling radio bearer is still used it would not impact the available radio resources blocks for NB-IoT since both SRB1bis and DRB use same scheduled NPUSCH and NPDSCH resources. + +This solution supports UE mobility and roaming. + +This solution enables the RAN to provide different priority to NAS messages and small data PDU messages if needed. + +This solution supports delivery of pending DL SMS after paging or combined with other NAS signaling e.g. Periodic Registration or registration due to mobility. + +### Pros: + +- Only impacting RRC relating to the indication of small data PDU message, UE NAS layer and the handling of user data to/from the application via the new upper layer functionality that used to be in the NAS layer for Control plane CIoT EPC optimisation. + +**NOTE:** UE NAS layer anyway needs to be updated to support 5GC, so part of the above mentioned change is in any case needed. + +- User data is separated from the control plane, which is an architectural principle for the 5GC. +- Core Network Congestion due to the user data handling in the control plane is avoided, since the user data is routed in the user plane. +- SCS/AS API is not affected. +- UE's lower layer and application functionality is not affected. + +### Cons: + +- New function is introduced in the UPF that includes functionalities as e.g. integrity protection, encryption and header compression. +- New security endpoint in the new UPF function is introduced. + +- A new indication is introduced in the RRC layer for routing purposes, indicating whether it is a NAS message or data PDU message. +- New routing solution in RAN for the user data PDU. + +## 6.7 Solution 7: Small data frequent communication + +### 6.7.1 Introduction + +This solution addresses the key issue #2, Frequent Small data communication. + +The solution allows the UE used for frequent small data communication to use the eDRX power saving method as investigated in KI#4. This allows UE power efficiency for traffic patterns for frequent small data communication with gaps between transmissions. + +This solution uses combinations of RRC Inactive, EDT, power saving methods, and HLCOM (see key issue 3 High latency communication) to meet the architecture requirement on both resource-efficiency and UE power efficiency. The solutions have two options for data buffering at MT data transmissions: + +- a) DL data buffering in RAN (solution in clause 6.7.4.2.2). +- b) DL data buffering in CN (solution 6.7.4.2.1). +- c) DL data buffering in CN (moving the UE to IDLE). + +Option a), with DL data buffering in RAN, is preferably used when a UE is not using eDRX (or eDRX with quite short sleep cycle e.g. a minute). In these cases, the RAN buffering can be very efficient. Option b), with DL data buffering in CN, is preferred when a UE is using eDRX (with longer sleep cycles e.g. a minute or more). In such cases, the CN has efficient buffer handling possibilities also considering full UE mobility. Alternatively, option c) with DL data buffering in CN with UE moved to CM-IDLE can be used for UE using longer sleep cycles. + +CN buffering is also used when SCS/AS has requested UE reachability Monitoring Events, except in case of option a). CN is able to send UE reachability event reports for SCS/AS that has requested notification when the UE wakes up from its power saving state. The RAN does not handle such reporting. + +### 6.7.2 Functional Description + +This solution for frequent small data communication supports the following functions: + +- Small data is transmitted with reduced signalling using the RRC Inactive state. For single and dual packet transmissions (UL+DL), even further reduction of signalling over the radio is achieved using the Early Data Transmission (subject to RAN decision). +- Fast release of the RRC connection at single and dual packet transmissions is supported, hence maximizing the UE power efficiency. +- Support for delivery of IP data and Unstructured (NIDD) data. +- Support for MT data transmission to power saving devices (KI 4 functions e.g. eDRX) using extended buffering and UE reachability event notifications (KI 3 functions). +- The existing UP security mechanisms in 5G system are supported. +- Support for charging, roaming, and policy control. Further 5G CIoT support for charging of messages are supported. + +### 6.7.3 Support of EPC interworking + +#### General: + +For DL data buffering, interworking between 5GC and EPC is achieved by a combined PGW/SMF and PGW-U+UPF. If a SMF/UPF has data buffered for a UE when the UE moves to EPC and becomes reachable then buffered data will get delivered in EPC (and vice versa). + +When interworking with EPC with N26, the source side may also based on CIoT capability at target side decide if the PDU session or PDN connection shall be transferred during mobility. + +#### **EPC to 5GC:** + +For a UE using CP CIoT EPS Optimization based PDN connection, CM-IDLE mode mobility is used from EPC to 5GC, and 5GC decides during mobility or next MO/MT data if the RRC Inactive optimization is used. Mobility from EPC to 5GC can also be made in CM-CONNECTED mode for a UE using UP CIoT EPS Optimization based PDN connection, by a handover in CM-CONNECTED mode. + +#### **5GC to EPC:** + +Mobility from 5GC to EPC, can either be made as CM-IDLE mode mobility, or as 5GC to EPS CM-CONNECTED mode handover procedure if UP is supported on the EPC side (if not supported only CM-IDLE mode mobility is used to EPC). On the EPS side it is decided if either the UP CIoT EPS Optimization or the CP CIoT EPS Optimization shall be applied. + +### **6.7.4 Procedures** + +#### **6.7.4.1 MO transmissions** + +##### **6.7.4.1.0 General** + +MO transmissions for frequent small data communication uses RRC Inactive and Early Data Transmission to reduce the signalling. RRC Inactive with MO transmission saves a UE context in the RAN at an initial small data transmission. All subsequent MO small data transmissions can then benefit of MO UL and DL transmission of small data without any 5G CP signalling. The RAN simply forwards any UL data on the existing N3 interface. And any subsequent DL data and additional UL data can be forwarded in the same optimized way. + +**NOTE:** Unlike CP-data in the EPS, there is no limit or break even for how much subsequent DL&UL data can be forwarded during a single RRC connection with this solution before there is a signalling penalty i.e. before the optimization becomes less optimized compared to sending the small data without any optimization at all. + +Early Data Transmission with RRC Inactive and MO transmission makes even further signalling optimization over the radio by piggy back the first UL data potentially the first DL data to the RRC establishment signalling. This would save an additional one or potentially two messages over the radio. + +**Editor's note:** Whether existing AS RAI can be re-used when the UE is aware of potential pending DL data in the CN is FFS. + +##### **6.7.4.1.1 MO transmission with RRC Inactive** + +An optimized data transmission for small data can be achieved using the RRC Inactive state for the UE connected to the 5GS. RRC Inactive is supported in 5GS from Rel-15 when NG-RAN is used. This solution proposes to use RRC Inactive also when NB-IoT and LTE-M are used. + +The RRC\_INACTIVE feature can transmit small data without necessarily performing a full state transition to RRC\_CONNECTED (see TR 38.804 [15], Annex G). + +**NOTE:** RRC Inactive for NB-IoT & LTE-M connected to 5GC is work in progress in RAN and coordination with RAN is needed. + + + +``` + +sequenceDiagram + participant UE + participant RAN + participant UPF-(NEF) + participant AF + Note left of UE: 0: UL data + UE->>RAN: 1: PRACH + RACH Response + UE->>RAN: 2: RRCConnectionResumeRequest (Resume ID) + RAN->>UE: 3: RRCConnectionResume + UE->>RAN: 4: UL data PDU + RAN->>UPF-(NEF): 5: UL data PDU + UPF-(NEF)->>AF: 6: UL/DL data + UPF-(NEF)-->>RAN: 7: DL data PDU + RAN-->>UE: 8: DL data PDU + RAN->>UE: 9: RRCConnectionRelease(Suspend ind) + Note left of UE: 10: RRC Inactive + +``` + +Sequence diagram for RRC Inactive with MO transmission. Lifelines: UE, RAN, UPF-(NEF), AF. The sequence starts with 0: UL data from UE. 1: PRACH + RACH Response from RAN to UE. 2: RRCConnectionResumeRequest (Resume ID) from UE to RAN. 3: RRCConnectionResume from RAN to UE. 4: UL data PDU from UE to RAN. 5: UL data PDU from RAN to UPF-(NEF). 6: UL/DL data from UPF-(NEF) to AF. 7: DL data PDU from UPF-(NEF) to RAN (dashed line). 8: DL data PDU from RAN to UE (dashed line). 9: RRCConnectionRelease(Suspend ind) from RAN to UE. 10: RRC Inactive from UE. + +**Figure 6.7.4.1.1-1: RRC Inactive with MO transmission** + +The UPF-(NEF) entity in the figure above is the UPF-NEF (i.e. Small data delivery function) in the Indirect Model case (i.e. when NIDD API is used) and it is a UPF in the Direct Model case. + +1-3. The RRC connection is moved from inactive to active. + +4-5. The UE sends a UL data PDU with small data to the RAN. The RAN forwards the UL data PDU to the UPF. + +If UE provided an AS RAI in step 4 which indicated single packet, or if the Expected UE Behaviour stored in the UE context in RAN contains a Release Assistance Information which indicates single packet (and the AS RAI is not present), then RAN continues to step 9 and immediately suspends the RRC connection unless there is pending DL data in RAN by which the pending DL data is sent to the UE and the RRC connection may be kept for potential subsequent UL (as a response to the pending DL data). + +6. For the Direct Model case the UPF forwards data to/from the AF (i.e. SCS/AS). For the Indirect Model case this step is the NIDD API. See for example the UPF-NEF solution 35. + +7-8. The receiver may respond with a DL data PDU, e.g. an acknowledgement, which is forwarded to the UE by the RAN. + +If UE provided an AS RAI in step 4 which indicated dual packets, or if the Expected UE Behaviour stored in the UE context in RAN contains a Release Assistance Information which indicates dual packets (and the AS RAI was not present), then RAN continues to step 9 and immediately suspends the RRC connection unless there were both pending DL data in RAN and DL data received in step 7 by which all DL data is sent to the UE and the RRC connection may be kept for potential subsequent UL (as a response to the pending DL data). + +9. The RAN suspends the RRC connection to inactive mode after a RAN specific timeout. + +10. UE enters RRC Inactive mode. + +#### 6.7.4.1.2 MO transmission with Early Data Transmission and RRC Inactive + +A very efficient data transmission can be achieved for one of the most frequent small data transmissions scenarios, i.e. one UL message (acknowledged or unacknowledged). Acknowledgements, if used, are often generated by a protocol layer such as Small data transmission function (see solution 35). The Small data transmission function is assumed to be dimensioned for low latency response of small data communications, allowing the potential acknowledgement to be included as Early Data Transmission in the RRC Command message. This enables low delay communication and reduced UE power consumption with a minimum signalling. + + + +``` + +sequenceDiagram + participant UE + participant RAN + participant UPF-(NEF) + participant AF + + Note left of UE: 0: UL data + UE->>RAN: 1: PRACH + RACH Response + RAN-->>UE: 2: RRC Resume Request with EDT UL data PDU + RAN->>UPF-(NEF): 3: UL data PDU + UPF-(NEF)->>AF: 4: UL/DL data + UPF-(NEF)-->>RAN: 5: DL data PDU + RAN-->>UE: 6: RRCConnectionRelease(Suspend ind) with EDT DL data PDU (if present) + Note left of UE: 7: RRC Inactive + Note left of RAN: 7: RRC Inactive + +``` + +Sequence diagram for MO transmission with Early Data Transmission and RRC Inactive. The diagram shows interactions between UE, RAN, UPF-(NEF), and AF. The sequence starts with 0: UL data at the UE. 1: PRACH + RACH Response from RAN to UE. 2: RRC Resume Request with EDT UL data PDU from UE to RAN. 3: UL data PDU from RAN to UPF-(NEF). 4: UL/DL data from UPF-(NEF) to AF. 5: DL data PDU from UPF-(NEF) to RAN (dashed line). 6: RRCConnectionRelease(Suspend ind) with EDT DL data PDU (if present) from RAN to UE. 7: RRC Inactive state reached by both UE and RAN. + +**Figure 6.7.4.1.2-1: MO transmission with Early Data Transmission and RRC Inactive** + +The UPF-(NEF) entity in the figure above is the UPF-NEF (i.e. Small data delivery function) in the Indirect Model case (i.e. when NIDD API is used) and it is a UPF in the Direct Model case. + +NOTE: EDT has been agreed in RAN for R15. Work with EDT in R16 will be started. + +0. A UE decides to send a small data sensor value to the SCS/AS. +1. The UE is in RRC Inactive and before the UL data PDU can be transmitted a resume of the radio connection is invoked. +2. The UL data PDU is included as Early Data Transmission with the RRC Resume Request. +3. The RAN finds the UE context using the Resume ID and forwards the UL data PDU on the N3 interface to the UPF. + If UE provided an AS RAI in step 2 which indicated single packet, or if the Expected UE Behaviour stored in the UE context in RAN contains a Release Assistance Information which indicates single packet (and the AS RAI was not present), then RAN immediately suspends the RRC connection unless there is pending DL data in RAN by which RAN instead sends a RRC Connection Resume to the UE (to keep the RRC connection for potential subsequent UL and DL data) with a pending DL data packet included as Early Data Transmission. Normal inactivity will in that case trigger the suspension of the RRC Connection. +4. For the Direct Model case the UPF forwards data to/from the AF (i.e. SCS/AS). For the Indirect Model case this step is the NIDD API. See for example the UPF-NEF solution. +5. The receiver may respond with a DL data PDU, e.g. an acknowledgement. +6. The RAN receives the DL data PDU before the RRC respond timer expires in the RAN and the UE provided AS RAI indicated dual packets or if the Expected UE Behaviour stored in the UE context in RAN indicates dual packets and the AS RAI was not present, then RAN expects no further data and includes the DL data PDU as Early Data Transmission with the RRC Connection Release with suspend indication sent to the UE. + +If the RRC respond timer expires without any received DL data and RAN expects further data (i.e. UE provided AS RAI indicated dual packets, or if the Expected UE Behaviour stored in the UE context in RAN indicates dual or multiple packets and the AS RAI was not present), then RAN sends an RRC Connection Resume to the UE to allow DL data that may have been delayed. Normal inactivity will in that case trigger the suspension of the RRC Connection. + +If AS RAI was not present and the Expected UE Behaviour stored in the UE context in RAN indicates multiple packets or does not include any Release Assistance Information, then RAN determines that further packets *can be expected* and instead moves the UE to RRC\_CONNECTED state by sending an RRC Connection Resume to the UE. Normal inactivity will in that case trigger the suspension of the RRC Connection. + +7. The UE and RAN enter RRC Inactive mode. + +## 6.7.4.2 MT transmissions + +### 6.7.4.2.0 General + +MT transmissions are typically less frequent in massive IoT scenarios, but nevertheless they need to be handled. + +The procedure in clause 6.7.4.2.2 describes RRC Inactive with option a) DL data buffering in RAN as listed in clause 6.7.1. + +The procedure below (clause 6.7.4.2.1) describes RRC Inactive with option b) DL data buffering in CN as listed in clause 6.7.1. + +Some details on availability notifications, are left for KI 3 solutions. + +### 6.7.4.2.1 MT transmission with CN extended buffering at RRC Inactive + +This procedure describes option b) DL data buffering in CN as listed in clause 6.7.1. + + + +``` + +sequenceDiagram + participant UE + participant RAN + participant AMF + participant SMF + participant UPF-(NEF) + participant AF + + Note over UE, AMF: UE not reachable eDRX as KI 4 (RRC inactive) + RAN->>AMF: 0. N2 Notification + AMF->>SMF: 0. Nsmf_PDUSession_UpdateSMContext (buffering info) + SMF->>UPF-(NEF): 0. N4 request to start buffering + AF->>UPF-(NEF): 1. DL data + Note over UPF-(NEF): 2. Data buffering + UPF-(NEF)->>SMF: 3. N4 data notification + SMF->>AMF: 3. Namf_MT_EnableUEReachability Req + AMF->>RAN: 4. N2 notification + SMF->>AMF: 5. Namf_MT_EnableUEReachability Resp + AMF->>UPF-(NEF): 5. N4 request + Note over UE, UPF-(NEF): 6. UE contacts the network + UPF-(NEF)->>RAN: 7. DL data + RAN->>UE: 7. DL data + Note over UE, RAN: 9. RRC Inactive + UPF-(NEF)->>AF: 8. API interaction + +``` + +Sequence diagram for MT transmission with CN extended buffering at RRC Inactive. The diagram shows interactions between UE, RAN, AMF, SMF, UPF-(NEF), and AF. The process starts with 'UE not reachable eDRX as KI 4 (RRC inactive)'. The RAN sends an N2 Notification to the AMF, which then sends an Nsmf\_PDUSession\_UpdateSMContext (buffering info) to the SMF. The SMF sends an N4 request to start buffering to the UPF-(NEF). Downlink data arrives at the UPF-(NEF) and is buffered. The UPF-(NEF) sends an N4 data notification to the SMF. The SMF sends a Namf\_MT\_EnableUEReachability Req to the AMF, which sends an N2 notification to the RAN. The SMF sends a Namf\_MT\_EnableUEReachability Resp to the AMF, which sends an N4 request to the UPF-(NEF). The UE contacts the network, and the RAN sends DL data to the UE. The UPF-(NEF) performs an API interaction with the AF. Finally, the RAN enters RRC Inactive state. + +**Figure 6.7.4.2.1-1: MT transmission with CN extended buffering at RRC Inactive** + +The UPF-(NEF) entity in the figure above is the UPF-NEF (i.e. Small data delivery function) in the Indirect Model case (i.e. when NIDD API is used) and it is a UPF in the Direct Model case. + +0. Extended Data Buffering is established when RAN transition a UE using eDRX to RRC Inactive state, the RAN sends a N2 Notification to AMF. RAN provides buffering support information if there is any. AMF uses the Nsmf\_PDUSession\_UpdateSMContext service to pass the buffering info (i.e. buffering duration) to SMF. SMF uses N4 messages to remove UPF N3 DL tunnel, activate extended buffering of DL data and set the Buffering duration. +1. DL data arrives. +2. DL data is buffered in the UPF based on step 0b. +3. The SMF requests a UE reachability report via Namf\_MT\_EnableUEReachability, based on N4 data notification from UPF. + +The SMF may optionally just wait for the next MO data from UE in step 6 to trigger the sending of downlink data without invoke enabling the UE reachability reporting. + +4. The AMF may use the N2 Notification procedure to retrieve UE reachability info. RAN may provide new buffering support information, if there is any. +5. The AMF notifies the SMF with the latest reachability info (either UE is reachable or still not reachable with potentially new buffering duration). The SMF uses N4 data request to update buffering duration for the UPF DL Tunnel if needed. +6. The UE contacts the network and the AMF either receives an N2 notification triggered by an RRC resume or an N2 Path Switch Request (if the RRC resume triggers a RAN node change). The AMF notifies the SMF/UPF of the UE reachability. +7. UPF delivers the buffered DL data to the UE. +8. For the Indirect Model, the interaction with the AF is according to the NIDD API. See for example the UPF-NEF solution. +9. RAN moves the UE to RRC Inactive state after a user inactivity timeout or based on Release Assistance Information if available in Expected UE Behavior. Depending on sleep cycle length and local configuration the RAN may then execute step 0 above and re-establish the CN extended data buffering in SMF/UPF, otherwise RAN buffering is used at next DL data event. + +NOTE: If the UE does not contact the network before expiry of the extended buffering duration timer, the buffered data may be discarded in the SMF/UPF. + +#### 6.7.4.2.2 MT transmission with RAN buffering at RRC Inactive + + + +``` + +sequenceDiagram + participant UE + participant RAN + participant UPF + Note right of UPF: 1. DL data PDU + UPF->>RAN: 1. DL data PDU + Note right of RAN: 2. DL data PDU + RAN->>UE: 2. DL data PDU + Note left of UE: 3. RRC Inactive + RAN->>UE: 3. RRC Inactive + +``` + +Sequence diagram for Mobile Terminated data with RAN buffering at RRC inactive procedure. The diagram shows three entities: UE, RAN, and UPF. The sequence of messages is: 1. UPF sends a DL data PDU to RAN. 2. RAN sends a DL data PDU to UE. 3. RAN moves the UE to RRC Inactive state. + +**Figure 6.7.4.2.2-1: Mobile Terminated data with RAN buffering at RRC inactive procedure** + +1. The UPF sends a DL data PDU towards the UE. RAN buffer the DL data during RAN paging (if necessary) or during the UE sleep cycle (if power saving method is used). + +NOTE: The AMF may use CN buffering (clause 6.7.4.2.1 or 6.7.4.2.3) if the UE uses eDRX with sleep cycles longer than e.g. one minute. + +2. RAN delivers to UE when UE becomes reachable. +3. RAN moves the UE to RRC Inactive state after a user inactivity timeout or based on Release Assistance Information if available in Expected UE Behavior. + +## 6.7.5 Impacts on existing entities and interfaces + +This solution uses and is dependent on the solution in clause 6.38. In addition, the following impacts to existing entities and interfaces exists: + +RAN: + +- Send buffering info with remaining eDRX interval to AMF. +- Support for EDT is optionally needed. +- RAN paging with extended unreachable cycles. + +- N2 notifications procedure of UE reachability. + +**AMF:** + +- New parameter in the Nsmf\_PDUSession\_UpdateSMContext service to pass buffering info (i.e. buffering duration) to SMF. +- Handling of 'Availability after DDN failure' monitoring event based on N2 Notification of DL data failure at RRC Inactive. +- N2 notifications procedure of UE reachability. + +**SMF:** + +- Send buffering info (i.e. buffering duration) to UPF. + +**UPF:** + +- Extended buffering while UEs are sleeping. + +## 6.7.6 Evaluation + +The solution uses the CM-CONNECTED with RRC\_INACTIVE state and the Early Data Transmission optimization when applicable, to transmit MO and MT small data in a resource efficient system signalling manner, especially over the radio interface. + +The solution supports delivery of IP data and Unstructured (Non-IP) data. + +The solution can be used to convey small data over N6, i.e. the Direct Model case, and over a northbound API at NEF, i.e. the Indirect Model case. In the latter case the solution can use e.g. solution 35 to provide the API. + +The solution uses the 5GS user plane security mechanisms, has minimum AS impacts and can use the charging, roaming and policy control that exists in the 5GS. + +## 6.8 Solution 8: Enhancing MICO for Mobile terminated data/signaling + +### 6.8.1 Introduction + +#### 6.8.1.1 General + +This solution applies to Key issue 4: Power Saving Functions, Track 2. The solution is based on keeping a UE, using MICO mode, in CM\_CONNECTED and RRC\_CONNECTED state until at least all pending downlink data and/or signalling has been delivered to the UE. + +### 6.8.2 Functional Description + +The following principles apply: + +- For mobile terminated data while a UE is in MICO mode, functions for Key Issue 3: High latency communication are used. +- When the AMF knows there may be MT data, MT SMS, network originated signaling or any other DL message pending, the AMF maintains the N2 connection and provides a Connected time value to the RAN. +- The Connected time value indicates the minimum time the RAN should keep the UE in RRC\_CONNECTED state regardless of inactivity. The Connected time value is provided in N2 Request carrying: + - NAS Registration Accept message; or + - NAS Service Accept message. + +- If the RAN node receives a Connected time value, the RAN shall keep the UE in RRC\_CONNECTED for at least the indicated duration. Once the Connected time has elapsed and the RAN inactivity timer has also expired, the RAN releases the UE's RRC connection. + +NOTE 1: The RAN node may release the RRC connection after the Connected time has elapsed and the RAN inactivity timer has also expired. Alternatively, the RAN node may set the RAN inactivity timer to the value of the Connected time, and release the RRC connection after the RAN inactivity timer has expired. + +NOTE 2: The C-DRX is assumed to be configured to similar value as I-DRX e.g. 1.28s, 2.56s, 5.12s or even 10.24s. + +- The AMF takes the Maximum Response Time if provided by the UDM, and any local AMF configuration into account for determining the Connected time value. +- On the UE side, in MICO mode, if the UE moves to CM-IDLE for any reason other than a successful RRC release procedure, e.g. due to RLF, the UE shall initiate NAS recovery, even if the registration procedure has been completed successfully. + +NOTE 3: This is current Rel-15 UE behavior, i.e. this does not imply additional UE impacts. + +### 6.8.3 Support of EPC interworking + +Rel-15 MICO and PSM interworking applies according to TS 23.501 [5] clause 5.17.2.1, as this solution has no additional NAS impacts. + +On the T8 and Nnef reference points the same parameter Maximum Response Time is used in EPC (e.g. for PSM) and 5GS for MICO, respectively. + +### 6.8.4 Procedures + +No modification to procedure call flows, only Connected time information is added to N2 Request from AMF to RAN node. + +### 6.8.5 Impacts on existing entities and interfaces + +In AMF: + +- Decide on a Connected time to be provided to RAN based on Maximum Response Time if available and local configuration, and provide value to RAN. + +In RAN: + +- Maintain RRC connection for at least the received Connected time, if received from the AMF. + +In UE: + +- No impacts identified. + +### 6.8.6 Evaluation + +The solution proposes an enhancement for mobile terminated data/signalling by introducing a minimum time to keep the UE in RRC\_CONNECTED (the Connected time). There are no modifications to the procedure call flows, only the Connected time information is added to N2 Request from AMF to RAN node. RAN WGs may provide a more precise analysis of actual power saving based on the UE power consumption in the different RRC states. + +The solution addresses the following architectural requirements for Key Issue#4: + +- Solutions shall enable UE power savings while also supporting delay-sensitive mobile terminating communications triggered by mobile originated communications. + +## 6.9 Solution 9: Enhanced MICO mode with Active Time + +### 6.9.1 Introduction + +This solution addresses Key Issue #4 (Power Saving Functions). The proposal is to enable a PSM (Power Saving Mode) equivalent feature from EPS in 5GS. In order to do so, the Mobile Initiated Connection Only (MICO) mode (see TS 23.501 [5] clause 5.4.1.3) is enhanced with an optional Active Time to realize power saving. Active Time is meant to be only used in combination with MICO mode. This solution is a NAS based solution with no RAN impact that allows for deep sleep periods of up to similar duration as in EPS PSM. + +### 6.9.2 Functional Description + +As the 5GC has a different architecture and some new functionality compared to EPC, some adaptations are needed compared to PSM in EPS: + +#### **Handling of Active Time and interaction with MICO mode:** + +In EPC if the UE wants to use the PSM, it shall request an Active Time value during every Attach and TAU/RAU procedures. If the network supports PSM and accepts that the UE uses PSM, the network confirms usage of PSM by allocating an Active Time value to the UE. In EPS the UE and the MME/SGSN starts the Active timer with the Active Time value allocated by the network when transitioning from ECM\_CONNECTED to ECM\_IDLE. + +The same principles can be used on 5GC, with the difference that in 5GS the MICO mode is a new feature not supported in EPS. + +A UE in MICO mode need not listen to paging while in CM-IDLE. A UE in MICO mode may stop any access stratum procedures in CM-IDLE, until the UE initiates transition from CM-IDLE to CM-CONNECTED. When the AMF indicates MICO mode to a UE, the AMF considers the UE always unreachable while the UE CM state in the AMF is CM-IDLE and the Active timer expires. The AMF rejects any request for downlink data delivery for UE in MICO mode and whose UE CM state in the AMF is CM-IDLE with an appropriate cause. The proposal is therefore to apply PSM functionality on MICO mode terminals if applicable: the UE may indicate its preference for MICO mode and optionally request an Active Time value during Initial Registration or Registration Update procedure. The AMF, based on local configuration, Expected UE Behaviour if available, UE indicated preferences, UE subscription information and network policies, or any combination of them, determines whether MICO mode is allowed and optionally an Active Time value for the UE, and indicates it to the UE during Registration procedure. If the UE does not indicate preference for MICO mode during Registration procedure, the AMF shall not activate MICO mode for this UE. When the AMF allocates the active time, the AMF should not allocate all PLMN Registration Area to the UE. + +The UE and AMF start the Active timer with the Active Time value allocated by the network when transitioning from CM\_CONNECTED state to CM\_IDLE state. When the Active timer expires, the UE enters the MICO mode. The UE and the AMF re-negotiate the MICO mode and the Active Time value at every subsequent Registration procedure. When the UE is in CM-CONNECTED, the AMF may deactivate MICO mode by triggering Registration Update procedure through UE Configuration Update procedure. + +#### **Mobile terminated data:** + +As indicated in Key Issue #4, the reachability and buffering aspects will be addressed in the key issue on high latency communication. + +#### **SCS/AS influencing the configuration of the power savings functions:** + +In EPS the SCS/AS may issue network parameter configuration requests to the network, via the SCEF, to suggest parameter values that may be used for Maximum Latency, Maximum Response Time and Suggested Number of Downlink Packets. By suggesting values for these parameters, the SCS/AS may influence certain aspects of UE/network behaviour such as the UE's PSM, extended idle mode DRX, and extended buffering configurations. In 5GC the support for SCS/AS influencing the configuration of the power savings functions shall at least be at the same level as in EPS. The solution for this will be handled in the key issue "Network Parameter Configuration API via NEF" (see NOTE 1 in Key Issue #4). + +### 6.9.3 Support of interworking + +Interworking when a UE is in MICO mode (defined in TS 23.501 [5] clause 5.17.2.1) is reused, where the UE shall locally disable MICO mode and perform the TAU or Attach procedure as defined in TS 23.501 [5] clause 5.17.2 which + +may include PSM (re-)negotiation. When the UE moves back to 5GC from EPC it locally disables PSM and MICO mode with or without Active Time can be renegotiated during the (re-)registration procedure. + +## 6.9.4 Procedures + +The existing procedures in 5GC will be reused to handle the Active Time signalling between the AMF and UE, by considering also subscription data. In particular, the negotiation procedure of enhanced MICO mode with Active Time is depicted as follows. + + + +``` + +sequenceDiagram + participant UE + participant RAN + participant AMF + participant UDM + + Note right of AMF: 3. Determines whether MICO mode is allowed and an Active Time value for the UE + + UE->>AMF: 1. Registration Request (MICO mode preference, Active Time) + AMF->>UDM: 2. Nudm_SDM_Get + AMF->>UE: 4. Registration Accept (MICO mode indication, Active Time) + Note left of RAN: 5. Enters CM-IDLE and starts an Active timer + Note left of RAN: 6. Enters MICO mode when Active timer expires + Note right of AMF: 5. Enters CM-IDLE and starts an Active timer + Note right of AMF: 6. Enters MICO mode when Active timer expires + +``` + +Sequence diagram illustrating the negotiation procedure of enhanced MICO mode with Active Time between UE, RAN, AMF, and UDM. + +**Figure 6.9.4-1: Negotiation procedure of enhanced MICO mode with Active Time** + +1. UE may indicate preference for MICO mode and optionally request an Active Time value during Initial Registration or Registration Update procedure. + 2. The AMF may retrieve the UE subscription information from the UDM. +- NOTE: The UE subscription information may include the Expected UE behaviour (see Solutions for Key Issue #13). +3. The AMF, based on local configuration, Expected UE Behaviour if available, UE indicated preferences, UE subscription information and network policies, or any combination of them, determines whether MICO mode is allowed and optionally an Active Time value for the UE. + 4. The AMF indicates the MICO mode indication and optional an Active Time value to the UE in the Registration Accept message. The AMF may also provide a Periodic registration timer in the Registration Accept message to decide the power saving interval for the UE. + 5. After the Registration procedure completed, the UE and AMF start the Active timer with the Active Time value allocated by the network when transitioning from CM\_CONNECTED state to CM\_IDLE state. When the UE and the AMF enter CM-CONNECTED state from CM-IDLE state during the Active timer is running, the UE and the AMF stops the Active timer. + 6. After the Active timer expires, the UE enters the MICO mode. The AMF considers the UE is not reachable for paging. + +## 6.9.5 Impacts on existing entities and interfaces + +AMF: + +- Determines Active Time value and indicates it to the UE in the Registration Accept message. + +UE: + +- Indicates the preferred Active Time value to the AMF in the Registration Request message. + +- Runs the Active timer as received from the AMF. + +## 6.9.6 Evaluation + +The solution proposed to enhance MICO mode with an Active Time. The UE and network can negotiate MICO mode and Active Time during Registration procedure. The solution is based on the same principle as Power Saving Mode in EPS. + +The solution addresses the following Architectural Requirements for Key Issue#4: + +- Solutions shall enable UE power savings while also supporting mobile terminating communications with a delay governed by the duration of the UE's sleep cycles. +- Sleep cycle durations supported by 5GC should be the same as supported by eDRX and PSM in EPC. + +# 6.10 Solution 10: Solution for supporting High Latency Communication + +## 6.10.1 Introduction + +This solution addresses the Key Issue 3 - "High Latency Communication". + +## 6.10.2 Functional Description + +Functions for High latency communication can be used to handle mobile terminated (MT) communication with UEs being unreachable while using power saving functions in 5GS. + +High latency communication is handled by notification procedures requested by NFs, e.g. AF, SMF, UPF, when a UE wakes up from its power saving state and sends downlink data to the UE when the UE is reachable. This notification procedure is based on notification service operations including UE Reachability, and Availability after DDN (downlink data notification) failure. + +For UE allowing high latency communication, the following two notification service operations can be used to optimize system resources and reduce signaling overhead: + +- UE reachability notification for MT communication. +- UE availability notification procedure after DDN failure. + +## 6.10.3 Support of interworking + +The same principle of solution 24 applies. + +## 6.10.4 Procedures + +### 6.10.4.1 Support for UE Reachability Notification for Mobile Terminated Communication + +The network can accommodate the UE with scheduled MT communication, e.g. the AF/SMF subscribes the notification service from the AMF for the UE reachability. + +For AF requesting event exposure from the AMF for the UE reachability notification, the AF can buffer the packets for MT communication before receiving the notification. + +Further, the SMF can request event exposure from the AMF for the UE reachability. There are two alternatives to handle DDN due to MT communication when the UPF receives the MT packets. + +#### Alternative 1: + +1. The UPF notifies the SMF for the downlink packets by sending DDN. +2. The SMF checks the UE's reachability and determines if it needs to send the DDN to the AMF or not. + +If the UE is in power saving mode, the SMF notifies the UPF to buffer the packets and indicates the buffer size, + +expected time for UE's availability, e.g. next time to be in idle state. + +If the UE is in idle mode, the SMF further sends the DDN to the AMF. + +#### Alternative 2: + +1. The SMF has notified the UPF about the buffering information according to the UE reachability. +2. The UPF buffers the packets accordingly and sends the DDN only after reaching the maximum size of the buffering. + +Further, if the UE is in CM-CONNECTED mode with RRC INACTIVE, extended buffering may be done at RAN. If RAN based paging fails or if RAN notification update guard timer expires RAN initiates AN release and send buffered data to AMF. AMF can then initiate CN based paging and take further action as specified in clause 6.10.4.2 step 4 onwards. + +### 6.10.4.2 Support for UE Availability Notification Procedure after DDN Failure + +The AF/SMF/UPF can subscribe to UE availability notification after DDN failure. + +For the AF requesting event exposure from the AMF for the UE availability notification after DDN failure, the AF buffers the packets for MT communication before receiving the notification for UE availability. + +For the SMF subscribing UE availability notification after DDN failure, the UPF buffers the packets for MT communication until receiving the notification for UE availability from the AMF or reaching the buffering criteria indicated by the SMF/AMF. + +For the UPF subscribing UE availability notification after DDN failure, the UPF buffers the packets for MT communication until receiving the notification for UE availability from the AMF/SMF or reaching the buffering criteria indicated by the AMF/SMF. + +Figure 6.10.4.2-1 shows the notification procedure subscribed by the SMF for UE availability after DDN failure. + +**Editor's note:** It is FFS for the notification procedure subscribed by UPF/AF for UE availability notification after DDN failure. + + + +``` + +sequenceDiagram + participant DN + participant UPF + participant SMF + participant AMF + participant NG-RAN + participant UE + + Note right of DN: 1. Downlink Data + DN->>UPF: 1. Downlink Data + Note right of UPF: 2. DDN + UPF->>SMF: 2. DDN + Note right of SMF: 3. DDN (subscribe to UE availability notification if DDN failure) + SMF->>AMF: 3. DDN (subscribe to UE availability notification if DDN failure) + Note left of AMF: 4. Paging + AMF->>NG-RAN: 4. Paging + Note right of NG-RAN: 5. DDN Failure (buffering size, expected available time, subscription event confirm) + NG-RAN->>SMF: 5. DDN Failure (buffering size, expected available time, subscription event confirm) + Note right of SMF: 6. DDN Failure (buffering size, expected available time) + SMF->>UPF: 6. DDN Failure (buffering size, expected available time) + Note right of UPF: Buffering Packets + Note left of UE: 7. Registration update request + UE->>AMF: 7. Registration update request + Note right of AMF: 8. Namf_EventExposure + AMF->>SMF: 8. Namf_EventExposure + Note right of SMF: 8. Namf_EventExposure + SMF->>UPF: 8. Namf_EventExposure + Note right of SMF: 9. Downlink Packets + SMF->>NG-RAN: 9. Downlink Packets + NG-RAN->>UE: 9. Downlink Packets + +``` + +Sequence diagram illustrating the notification procedure for UE availability after DDN failure. The diagram shows interactions between UE, NG-RAN, AMF, SMF, UPF, and DN. The sequence starts with DN sending Downlink Data to UPF (1). UPF sends DDN to SMF (2). SMF sends DDN (subscribe to UE availability notification if DDN failure) to AMF (3). AMF initiates Paging (4) to NG-RAN. NG-RAN sends DDN Failure (buffering size, expected available time, subscription event confirm) to SMF (5). SMF sends DDN Failure (buffering size, expected available time) to UPF (6). UPF starts Buffering Packets. UE sends Registration update request to AMF (7). AMF sends Namf\_EventExposure to SMF (8). SMF sends Namf\_EventExposure to UPF (8). Finally, SMF sends Downlink Packets to NG-RAN (9), which are then received by UE. + +**Figure 6.10.4.2-1: Notification procedure for UE availability after DDN failure** + +1. The UPF receives downlink data packets from data network. +2. The UPF sends downlink data notification message to the SMF. +3. When a SMF sends DDN (downlink data notification) to the AMF, it indicates also if it subscribes the notification service from the AMF for the UE availability when DDN failure. + +4. The AMF may initiate paging procedure. +5. The DDN failure may be of many causes: paging failure, the paging suspension due to activated MICO mode, the UE activates high latency communication. If the DDN failure happens, the AMF replies to the SMF for the DDN failure with an indication for confirming the notification service for the next UE availability. Further, the AMF may base on UE's reachability information to calculate buffering info and then include the following information in DDN response message: the buffer size (number of packets), buffering time, expected UE reachable time. +6. The SMF forwards the buffering information to the UPF. The UPF starts to buffer packets according to the received buffering info. +7. The UE contacts the AMF via registration update procedure. +8. The AMF notifies the SMF/UPF for the UE availability. +9. The UPF starts to deliver buffered downlink packets. + +## 6.10.5 Impacts on existing entities and interfaces + +Impacts on AMF: + +- Support for UE Reachability Notification from AF and SMF; +- Support for UE Availability Notification Procedure after DDN Failure from AF/SMF/UPF. + +Impacts on SMF: + +- Support subscribing to UE availability notification after DDN failure, and indicate buffering information to UPF. +- Requesting event exposure from the AMF for the UE reachability, checking the UE's reachability and determining if it needs to send the DDN to the AMF or not, and notification to the UPF to buffer packets and indicate the buffer size, expected time for UE's availability, if necessary; + +Impacts on UPF: + +- Support subscribing to the UE availability notification after DDN failure; +- Buffer the packets for MT communication until receiving the notification for UE availability from the AMF/SMF or reaching the buffering criteria indicated by the AMF/SMF. + +## 6.10.6 Evaluation + +The solution proposes two notification procedures for mobile terminated communication, UE reachability notification and UE availability notification procedure after DDN failure. The solution also combines the downlink packet buffering function with the notification procedure, increasing the complexity of MT communication handling for AMF/SMF/UPF. + +The solution addresses the architectural requirements of key issue 3 to "provide the AF (i.e. SCS/AS) with UE status information (e.g. reachability notification or the time when the UE is expected to be reachable)". + +# 6.11 Solution 11: Extended buffering in SMF and NEF + +## 6.11.1 Introduction + +This solution addresses Key Issue 3 (High latency communication). + +High latency communication is handled by extended buffering of downlink data in the SMF. The AMF indicates to the SMF when the UE is expected to wake up from its power saving state. Based on such indication, the SMF triggers extended buffering. Buffering may be performed by the SMF or the UPF as currently defined in TS 23.501 [5]. This solution focuses on when extended buffering is performed in the SMF. + +## 6.11.2 Functional Description + +The handling is specified in the Network Triggered Service Request procedure. When the downlink data is received, the UPF sends the data notification to the SMF, and the SMF indicates the AMF to page the UE. + +The AMF then detects that the UE is in a power saving state (e.g. MICO) and cannot be reached by paging at the moment. The AMF optionally indicates to the SMF together with the expected time radio bearers can be established to the UE and a DL Buffering Suggested Packet Count. + +## 6.11.3 Support of interworking + +Interworking with EPC is achieved by a combined PGW-C+SMF. If an SMF has data buffered for a UE when the UE moves to EPC and becomes reachable then buffered data will get delivered in EPC via the P-GW-U. If an S-GW has data buffered for a UE when the UE moves to 5GC and becomes reachable then the buffered data will be sent to the PGW-U+UPF by the S-GW and will be delivered in 5GC via the UPF. + +**Editor's Note:** The details of how buffered data is forwarded in the interworking case are FFS. + +## 6.11.4 Procedures + +### 6.11.4.1 Data Transfer via N6 interface + +The procedure of extended buffering for Data Transfer via N6 interface is depicted as following. + + + +``` + +sequenceDiagram + participant UE + participant RAN + participant AMF + participant SMF + participant UPF + + Note left of UE: 0. UE in CM-IDLE and potentially temporarily unavailable (e.g. eDRX) + + Note right of UPF: DL data + UPF->>SMF: 1a. Data Notification + SMF-->>UPF: 1b. Data Notification Ack + SMF->>UPF: 1c. DL data + Note right of SMF: 2. Decides ext. buff. is enabled + SMF->>AMF: 3.N1N2MessageTransfer (indication of whether ext. buff. is enabled) + Note right of AMF: 4. Determines UE is unreachable + AMF->>SMF: 5. N1N2MessageTransfer(DL Buffering Requested, Extend Max. wait time) + Note right of SMF: 6. Stores DL PDUs until time T + + Note right of UE: 7.a UE triggered Service request procedure (TS 23.502 clause 4.2.3.2) + Note right of UE: 7.b Periodic Registration Update procedure (TS 23.502 clause 4.2.2.2) + + Note right of UE: 8. Downlink data transfer via N6 interface + +``` + +Sequence diagram illustrating the extended buffering for Data Transfer via N6 interface. The diagram shows interactions between UE, RAN, AMF, SMF, and UPF. The process starts with the UE in CM-IDLE. Downlink data arrives at the UPF, which sends a Data Notification to the SMF. The SMF replies with a Data Notification Ack and forwards the data. The SMF then decides to enable extended buffering and informs the AMF via N1N2MessageTransfer. The AMF determines the UE is unreachable and informs the SMF via another N1N2MessageTransfer with DL Buffering Requested. The SMF stores the DL PDUs until time T. Later, the UE triggers a Service request or Periodic Registration Update procedure, after which the Downlink data transfer via N6 interface occurs. + +**Figure 6.10.4.1-1: Extended buffering for Data Transfer via N6 interface** + +0. The UE is assumed to be temporarily unavailable (i.e. in some power saving state). +1. When the first downlink data packet is received, the UPF sends a Data Notification message to the SMF. The SMF replies with a Data Notification Ack message to the UPF. The UPF forwards the downlink data packets towards the SMF. +2. The SMF determines that Extended Buffering is possible. +3. The SMF contacts the AMF and invokes the Namf\_Communication\_N1N2MessageTransfer to the AMF. Based on PCC rules, the SMF indicates to the AMF whether extended buffering is possible or not. + +4. The AMF detects that the UE is in a power saving state (e.g. eDRX or MICO) and cannot be reached by paging at the moment. +5. Based on the status of the UE of step 4, the AMF sends a Namf\_Communication\_N1N2MessageTransfer response to the SMF indicating that the DL buffering is requested due to the UE in power saving state and temporarily unreachable and the maximum wait time. +6. The SMF stores the DL Data for the maximum wait time and does not send any additional Data Notification if subsequent downlink data packets are received. + +NOTE: The DL Buffering Suggested Packet Count is derived from the subscription information which is provided by the SCS/AS via T8 API. + +**Editor's Note:** Whether the AMF or SMF determines the DL Buffering Suggested Packet Count is FFS. + +7a or 7b. The UE triggered Service Request procedure or Periodic Registration procedure may occur. + +8. When receiving UE reachable indication in step 6, the SMF sends the buffered downlink data to the UE. + +#### 6.11.4.2 Data Transfer via API + +For MT Data that is sent via the NEF, the buffering should happen in the NEF. The same principle of clause 6.11.4.1 applies to DL data buffered in the NEF in case of data transfer via APIs. For data transfer via NEF, the NEF uses the same interactions with the SMF as the UPF uses in Figure 6.11.4.1-1. + +### 6.11.5 Impacts on existing entities and interfaces + +AMF: + +- Indicates DL buffering requested and maximum wait time to the SMF. + +SMF: + +- Based on indication of AMF that the DL buffering is requested, it triggers extended buffering. +- Buffers downlink data. + +### 6.11.6 Evaluation + +Solution 11 proposes extended buffering for high latency communication. The SMF triggers extended buffering locally based on the indication of unreachable UE sent by the AMF. The solution meets the following Architectural Requirement of Key Issue 3: "Send DL data to UEs at the earliest possible opportunity when the UEs are applying power saving functions". + +## 6.12 Solution 12: Solution for Management of Enhanced Coverage for 5GC + +### 6.12.1 Introduction + +This solution addresses the Key Issue 6 - "Management of Enhanced Coverage". + +### 6.12.2 Functional Description + +#### 6.12.2.1 Support of Enhanced Coverage + +The UE shall indicate its capability of support for Enhanced Coverage (i.e. CE mode B capability support) in the Initial Registration or Registration Update Request message to the AMF. The AMF stores UE capability of support for enhanced Coverage in the UE context in AMF. + +#### 6.12.2.2 Support of restriction of use of Enhanced Coverage + +The usage of Enhanced Coverage may require use of extensive resources (e.g. radio and signalling resources) from the network. Specific subscribers can be restricted to use Enhanced Coverage feature through Enhanced Coverage Restricted information that is stored in UDM as part of subscription data and specifies per PLMN whether the Enhanced + +Coverage functionality is restricted or not for the UE. Enhanced Coverage Restricted information indicates whether CE mode B is restricted for the UE, or both CE mode A and CE mode B is restricted for the UE, or both CE mode A and CE mode B is not restricted for the UE. + +The AMF receives Enhanced Coverage Restricted information from the UDM during registration procedure. AMF based on local configuration, UE Usage setting, UE subscription information and network policies, or any combination of them, determines whether Enhanced Coverage (i.e. CE mode B or both CE mode B & CE mode A) is restricted for the UE and stored updated Enhanced Coverage restriction information in the UE context in AMF. If the UE usage setting indicated that UE is "voice centric" then the AMF shall set CE mode B restricted for the UE in Enhanced Coverage restriction information. + +The AMF sends Enhanced Coverage Restricted information to the UE in the Registration Accept message. The UE shall use Enhanced Coverage Restricted information to determine if Enhanced Coverage is restricted or not. The AMF provides an Enhanced Coverage Restricted information to the RAN via N2 signalling whenever the UE context is established in the RAN, e.g. during N2 Paging procedure, Service Request procedure, initial Registration and periodic Registration procedure. + +For roaming UEs, if the UDM doesn't provide any Enhanced Coverage Restricted information or the provided Enhanced Coverage Restricted information is in conflict with the roaming agreement, the AMF uses default Enhanced Coverage Restricted information locally configured in the VPLMN based on the roaming agreement with the subscriber's HPLMN. + +The UE that indicates its support Enhanced coverage over N1 interface shall also support restriction of the Enhanced Coverage over N1 interface. The UE shall assume that restriction for use of Enhanced Coverage is same in the equivalent PLMNs. + +## 6.12.3 Support of EPC interworking + +### 6.12.3.1 IDLE Mode aspects + +- When UE moves from 5GS to EPS, the UE context information sent by AMF to MME includes the Enhanced Coverage Restricted information. MME determines Enhanced Coverage Restricted parameter and CE mode B restricted parameter from Enhanced Coverage Restricted information and stores it in MME's MM context. +- When UE moves from EPS to 5GS, the MME's MM context information sent by MME to AMF includes the Enhanced Coverage Restricted parameter and CE mode B restricted parameter. AMF determines Enhanced Coverage Restricted information from CE mode B restricted parameter and Enhanced Coverage Restricted parameter and stores it in the UE context at AMF. + +### 6.12.3.2 CONNECTED Mode aspects + +- When a UE is CM-CONNECTED in 5GC and a handover to EPS occur, source NG-RAN provides Enhanced Coverage Restricted information to the target eNB. +- When a UE is CM-CONNECTED in EPS and a handover to 5GC occur, source eNB provides Enhanced Coverage Restricted information to the target NG RAN. + +## 6.12.4 Procedures + +### 6.12.4.1 Procedure for restriction of use of Enhanced Coverage + + + +``` + +sequenceDiagram + participant UE + participant RAN + participant AMF + participant UDM + UE->>AMF: 1. N1: Registration Request (EC support capability) + AMF->>UDM: 2. Nudm_SDM_Get (EC Restriction information) + Note over AMF: 3. AMF determines EC Restriction information +based on UE subscription data, UE usage +setting, local policy and stores it +in UE context in AMF. + AMF->>RAN: 4. N2 Message (EC Restriction information, N1 Registration Accept (EC Restriction information)) + AMF->>UE: 4. N1: Registration Accept (EC Restriction information) + Note over UE: 5. UE use the Enhanced +Coverage Restricted information +to determine if Enhanced +Coverage is restricted or not + +``` + +Sequence diagram illustrating the procedure for restriction of use of Enhanced Coverage. The diagram shows interactions between UE, RAN, AMF, and UDM. + +**Figure 6.12.4.1-1: Procedure for restriction of use of Enhanced Coverage** + +1. The UE sends N1 registration Request message to AMF with UE Enhanced Coverage (EC) support capability indication. +2. The AMF retrieves the subscription data for the UE from the UDM using Nudm\_SDM\_Get service operation. UDM may retrieve this information from UDR by Nudr\_UDM\_Query (Access and Mobility Subscription data). This includes also the *Enhanced Coverage Restriction information* (i.e. CE mode B is restricted for the UE, or both CE mode A and CE mode B is restricted for the UE, or both CE mode A and CE mode B is not restricted for the UE). +3. AMF based on local configuration, UE Usage setting, UE subscription information and network policies, or any combination of them, determines whether Enhanced Coverage (i.e. CE mode B or both CE mode B & CE mode A) is restricted for the UE and stored updated Enhanced Coverage restriction information in the UE context in AMF. +4. The AMF sends Enhanced Coverage Restricted information to the UE in the Registration Accept message. The AMF also provides an Enhanced Coverage Restricted information to the RAN via N2 signalling. +5. The UE shall use the Enhanced Coverage Restricted information to determine if Enhanced Coverage is restricted or not. + +### 6.12.4.2 Enhanced Coverage Restriction Control and via NEF + +The support for Enhanced Coverage Restriction Control via NEF enables 3rd party service providers to query status of, enhanced coverage restriction or enable/disable enhanced coverage restriction per individual UEs. + + + +``` + +sequenceDiagram + participant AS/AF + participant NEF + participant UDM + participant AMF + + Note right of AS/AF: 1. Nnef_ECRestriction_Update() / Nnef_ECRestriction_Status_Get() + AS/AF->>NEF: 1. Nnef_ECRestriction_Update() / Nnef_ECRestriction_Status_Get() + Note right of NEF: 2. NEF handling + NEF->>UDM: 3. Nudm_SDM_Update() / Nudm_SDM_Get() + Note right of UDM: 4. For Nudm_SDM_Update service operation UDM notifies AMF + UDM->>AMF: 5. Nudm_SDM_Notification() + Note left of AMF: 6. Update Enhanced Coverage Restriction Information in UE Context + AMF->>NEF: 7. Nudm_SDM_Update() / Nudm_SDM_Get() + Note right of NEF: 8. 1. Nnef_ECRestriction_Update() / Nnef_ECRestriction_Status_Notify() + NEF->>AS/AF: 8. 1. Nnef_ECRestriction_Update() / Nnef_ECRestriction_Status_Notify() + +``` + +Sequence diagram illustrating the Procedure for Enhanced Coverage Restriction Control and via NEF. The diagram shows interactions between AMF, UDM, NEF, and AS/AF. The sequence starts with AS/AF sending Nnef\_ECRestriction\_Update() or Nnef\_ECRestriction\_Status\_Get() to NEF. NEF handles this and then sends Nudm\_SDM\_Update() or Nudm\_SDM\_Get() to UDM. UDM performs internal handling and notifies AMF via Nudm\_SDM\_Update(). AMF then sends Nudm\_SDM\_Notification() to AMF (dashed line). A dashed box labeled '6. Update Enhanced Coverage Restriction Information in UE Context' is shown. Finally, AMF sends Nudm\_SDM\_Update() or Nudm\_SDM\_Get() to NEF, which then sends Nnef\_ECRestriction\_Update() or Nnef\_ECRestriction\_Status\_Notify() to AS/AF. + +**Figure 6.12.4.2-1: Procedure for Enhanced Coverage Restriction Control and via NEF** + +1. The AF/AS uses Nnef\_ECRestriction\_Update() request service operation in order to enable/disable Enhanced Coverage restriction or Nnef\_ECRestriction\_Status\_Get() service operation to query the status of enhanced coverage restriction. Both service operation includes External Identifier or MSISDN and AS/AF Identifier as required input. Enhanced Coverage Restriction Data provides an indication to either enable or disable the enhanced coverage restriction and is required input for Nnef\_ECRestriction\_Update() request service operation only. +2. If either the AS/AF is not authorized to perform this request (e.g. if the SLA does not allow for it), or the AS/AF has exceeded its quota or rate of submitting Enhanced Coverage requests, the NEF indicates service operation failure to AS/AF with appropriate cause code and flow stops here. Otherwise the flow continues to step 3. +3. The NEF uses Nudm\_SDM\_Update() service operation to update the subscription data for Enhanced Coverage restriction. The NEF uses Nudm\_SDM\_Get() service operation to query the status of for Enhanced Coverage restriction. UDM may retrieve this information from UDR by using Nudr\_UDM\_Query() service operation. +4. For Nudm\_SDM\_Update() when the subscriber data for Enhanced Coverage restriction is updated at the UDM, serving NF (i.e. AMF in this case) is notified with the updated Enhanced Coverage restriction information in the subscription data. AMF may subscribe for the notification for Enhanced Coverage restriction information change. + +In case of Nudm\_SDM\_Get() service operation steps 5 & 6 are skipped. + +5. The UDM uses Nudm\_SDM\_Notification() service operation and provide AMF with updated Enhanced Coverage restriction information. +6. The AMF updates Enhanced Coverage restriction information stored in the UE context at AMF. The AMF will transfer the Enhanced Coverage Restricted Information stored as part of its UE context during AMF change. + +NOTE: UE is informed of the updated Enhanced Coverage Restricted information at the next Registration procedure, or based on the local policy the network can de-register the UE indicating re-registration is required. + +7. The UDM sends response of Nudm\_SDM\_Update ( ) / Nudm\_SDM\_Get ( ) service operation to the NEF. +8. The NEF sends response of Nnef\_ECRestriction\_Update ( ) / Nnef\_ECRestriction\_Status\_Get ( ) service operation to the AS/AF. + +## 6.12.5 Impacts on existing entities and interfaces + +### UE: + +- Indicate Enhanced Coverage support capability indication to the AMF. +- Receives Enhanced Coverage Restriction Information as part of N1 procedure (i.e. Initial and periodic Registration Accept). +- Stores Enhanced Coverage Restriction Information per PLMN and use Enhanced Coverage mode based on Enhanced Coverage restriction Information provided by the AMF. + +### RAN: + +- Receives an Enhanced Coverage Restricted information from the AMF via N2 signalling whenever the UE context is established in the RAN, e.g. during N2 Paging procedure, Service Request procedure, initial Registration and periodic Registration procedure. +- Determines if UE is restricted to operate in Enhanced Coverage mode based on the Enhanced Coverage Restriction information provided by the AMF. + +### AMF: + +- Receives Enhanced Coverage Restriction information as part of subscription data from the UDM. +- Based on local configuration, UE Usage setting, UE subscription information and network policies, or any combination of them, determines whether Enhanced Coverage (i.e. CE mode B or both CE mode B & CE mode A) is restricted for the UE. +- Stores Enhanced Coverage Restriction information as part of UE context in AMF. +- The AMF provides an Enhanced Coverage Restricted information to the UE via N1 signalling (i.e. during N2 during initial Registration and periodic Registration procedure.) +- Provides an Enhanced Coverage Restricted information to the RAN via N2 signalling whenever the UE context is established in the RAN, e.g. during N2 Paging procedure, Service Request procedure, initial Registration and periodic Registration procedure.. + +### UDM/UDR: + +- Contains Enhanced Coverage Restriction information as part of subscription data. UDM may retrieve it from the UDR. +- Support new Nudm\_SDM\_Update ( ) service operation with NEF as consumer to update the subscription data for Enhanced Coverage restriction. +- Interface with NEF to provide status of Enhanced Coverage restriction using updated Nudm\_SDM\_Update ( ) service operation with NEF as consumer. + +### NEF: + +- Support new Nnef\_ECRestriction\_Update ( ) request service operation with AS/AF as consumer in order to enable/disable Enhanced Coverage restriction. +- Support new Nnef\_ECRestriction\_Status\_Get ( ) service operation with AS/AF as consumer to query the status of enhanced coverage restriction. + +## 6.12.6 Evaluation + +The solution is based on the same principles as in EPS. Main difference is in terms of messages carrying the EC related information for 5G system. + +The solution addresses all Architectural Requirements for the key issue#6 - Management of Enhanced Coverage. + +## 6.13 Solution 13: SCEF+NEF Node + +### 6.13.1 Introduction + +This clause presents a solution for Key Issue 9 - Support of common north-bound APIs for EPC-5GC Interworking. + +The following principles apply to this solution: + +- As a general architecture principle, the 3GPP network topology should be hidden from the AF (corresponding to SCS/AS in EPS); thus, we should avoid a situation where the AF needs to be aware of whether the UE is served by EPC or 5GC. The AF should not have to change the network node that it contacts when a UE moves between 5G and EPC. +- Configuration of common services that are supported by EPC and 5GC should not be dependent on whether the UE is attached to 5GC or EPC, thus the APIs that are used by the AF or SCS/AS to access a given service should not depend on whether the UE is attached to EPC or 5GC. Using 3rd party APIs an AF however maybe able to find the access technology the UE is currently connected. Consequently, an AF can access the available 3rd party services with the expected level of support available under that technology. +- If the availability or expected level of support of a service API associated with a UE changes, for example due to a mobility between 5GC and EPC, the AF or SCS/AS can be made aware of the change. Note that the same principle already applies in EPC where the SCEF is notified if the UE switches to being served by an MME that does not support a configured monitoring event. +- For a given UE, the node that the AF or SCS/AS contacts for some services is configured in the network. The same is already true in EPC. For example, with respect to NIDD, the SCEF ID associated with the UE for a NIDD PDN Connection is provided to the MME by the HSS during T6a connection establishment. For other features (e.g. Device Triggering, Group Message Delivery MBMS, and NIDD) TS 23.682 [6] recommends that the SCS/AS may determine the IP address(es)/port(s) of the SCEF associated with a UE by performing a DNS query using the External Identifier or using a locally configured SCEF identifier. +- A UE can be associated with different exposure nodes for each service. The same is already true in EPC. For example, one SCEF might be used for monitoring, another SCEF instance might be used for NIDD to one APN, and yet another SCEF instance might be used for NIDD to another APN. + +### 6.13.2 Functional Description + +When a UE is capable of switching between EPC and 5GC, it shall only be associated with combined SCEF+NEF node(s) for Service Capability Exposure. The SCEF+NEF hides the underlying network topology from the AF (i.e. SCS/AS) and hides whether the UE is served by 5GC or EPC. Figure 6.13.2-1 shows the SCEF+NEF architecture. + + + +Figure 6.13.2-1: Architecture view of the SCEF+NEF node. The diagram shows an AF (Application Function) at the top connected via an N33 interface to three SCEF+NEF instances. Instance #1 is connected to EPC Node 1, EPC Node 2, NF1, and NF2. Instance #2 is connected to EPC Node 3, EPC Node 4, NF3, and NF4. Instance #3 is connected to EPC Node 5, EPC Node 6, NF5, and NF6. Each instance contains an SCEF and an NEF. APIs are shown: API 1 for Instance #1, API 2 for Instance #2, and API 3 and API 4 for Instance #3. + +**Figure 6.13.2-1: Architecture view of the SCEF+NEF node** + +Interaction between the SCEF and NEF within the combined SCEF+NEF is required. For example, when the SCEF+NEF supports monitoring APIs, the SCEF and NEF need to share context/state information about a UE's configured monitoring events in case the UE between from EPC and 5GC. This interaction between the SCEF and NEF shall not be standardized. The common state information is characterized as information that needs to be maintained by the combined SCEF+NEF node in order to meet the external interface requirements of the combined node. + +The common state information includes at least the following data that needs to be identical in a combined SCEF+NEF: + +- SCEF+NEF ID (must be the same towards the AF / SCS/AS). +- SCEF+NEF common IP address and port number. +- Monitoring state for any ongoing monitoring request. +- Configured set of APIs supported by SCEF+ NEF. +- PDN Connection/PDU Session State and NIDD Configuration Information, including Reliable Data Service state information. +- Network Parameter Configuration Information (e.g. Maximum Response Time and Maximum Latency). + +If a configured service becomes unavailable or its level of support changes because of change of access network for a UE, the SCEF+NEF will notify the SCS/AS. A configured service may become unavailable because the UE is now being served by a node (e.g. MME) or NF (e.g. AMF) that does not support the configured service. + +If the service exposure function that is associated with a given service for a UE is configured in the UE's subscription information, then an SCEF+NEF identity shall be used to identify the exposure function. For example, if a UE is capable of roaming between EPC and 5GC, then the SCEF ID that is associated with any of the UE's APN configurations should point to an SCEF+NEF node. + +In EPC, the SCEF is part of the HPLMN. This solution assumes that an NEF or SCEF+NEF that exposes API's to 3rd party AFs (i.e. SCS/AS) is part of the HPLMN. + +## 6.13.3 Support of EPC interworking + +As noted above, interaction between the SCEF and NEF in the SCEF+NEF need not be standardized, even though the architectural data requirements implied by the external interfaces are specified. + +Consistent with existing EPS-5GS interworking scenarios in TS 23.501 [5], the subscriber data base is managed by a combined HSS+UDM node. Thus, SCEF+NEF implementations need not perform the same procedures with the + +HSS+UDM twice. For example, monitoring events only need to be configured by the SCEF+NEF one time, by using either EPC or 5GC procedures. In other words, when a monitoring event has been configured by the SCEF procedures towards the HSS, the NEF need not repeat the same monitoring event configuration towards the UDM, and vice versa. Whether the SCEF+NEF uses SCEF or NEF procedures for monitoring event configuration is an implementation decision. + +### 6.13.4 Procedures + +Refer to clause 6.14.4 for procedures that show how the SCS/AS or AF subscribes and unsubscribes to the SCEF+NEF to be notified of service changes when a UE's serving CN Type changes, how the SCEF+NEF notifies the SCS/AS or AF of service changes when a UE's serving CN Type changes, and how the SCS/AS or AF queries the SCEF+NEF of supporting service. + +### 6.13.5 Impacts on existing entities and interfaces + +In terms of the CAPIF, the SCEF+NEF should be viewed as a single node. + +The API interface that is exposed by the SCEF+NEF interface is an N33 / Nnef interface that supports the T8 APIs. + +### 6.13.6 Evaluation + +The solution shows how the API termination point(s) associated with the UE can remain consistent even when the UE switches between EPC and 5GC. + +If the level of support of a given service changes (e.g. due to the UE's mobility between EPC and 5GC), the SCEF+NEF will notify the SCS/AS. + +Since the solution continues the EPC assumption that the exposure function(s) that serve a UE will not change, there is no need to provide a way for the AF to detect API termination point changes and there is no need to specify how the exposure functions to exchange UE context. + +## 6.14 Solution 14: APISupportCapability service + +### 6.14.1 Introduction + +This clause presents a solution for Key Issue 9 - Support of common north-bound APIs for EPC-5GC Interworking, in particular it addresses the issue of how the AF becomes aware of the availability/the expected level of a given service when the UE changes between EPC and 5GC. + +This solution assumes that the combined SCEF+NEF node provides a newly defined service called APISupportCapability. This service relies on a new Event Id and a new Query service provided by HSS+UDM. The SCEF+NEF node subscribes to this Event Id or consumes this Query service in order to retrieve the CN Type (e.g., 5GC or EPC or 5GC/EPC or None) that has most recently served the UE. With this CN Type information, the APISupportCapability service determines the availability or expected level of support of common north-bound APIs, this can be further informed to the north-bound applications via a response to the request of the applications or via a notification to the subscription of the applications. + +### 6.14.2 Functional Description + +When the IoT UE is capable of moving between 5GC and EPC, the UE shall be associated with a combined HSS+UDM node and a combined SCEF+NEF node for Service Capability Exposure. The SCEF+NEF hides the underlying network topology from the AF (i.e. SCS/AS) and whether the UE is served by 5GC or EPC. The HSS+UDM supports a new CN Type Change Event Id or CN Type Query. Figure 6.14.2-1 shows the proposed architecture when CAPIF function is not supported for the solution. Figure 6.14.2-2 shows the proposed architecture when CAPIF function is supported for the solution. + +NOTE: The purpose of Figure 6.14.2-1/6.14.2-2 is to simply show the interaction between the AMF, MME, HSS+UDM, and SCEF+NEF with respect to CN Type queries, CN Type Change subscriptions, and CN Type Change notifications; although not shown in the figure, the SCEF+NEF interacts directly with the AMF and MME in other procedures which are not related to this solution. + +If the Service Capability Exposure that is associated with a given service for a UE is configured in the UE's subscription information, then an SCEF+NEF identity shall be used to identify the exposure function. For example, if a UE is + +capable of roaming between EPC and 5GC, then the SCEF ID associated with any of the UE's APN configurations should point to an SCEF+NEF node, if the SCEF ID is stored in the UE's subscription. + + + +Figure 6.14.2-1: Combined NEF+SCEF NF without CAPIF support. The diagram shows an IoT UE connected to both an EPC (containing an MME) and a 5GC (containing an AMF). Both the MME and AMF are connected to a central HSS+UDM node. The HSS+UDM is connected to a combined SCEF+NEF node, which contains separate EPC (SCEF) and 5GC (NEF) components. This SCEF+NEF node is connected via an N33/Nnef interface to an AF (Application Function) box. The AF box contains an EPC (SCS/AS, API invoker) and a 5GC (AF) component. + +**Figure 6.14.2-1: Combined NEF+SCEF NF without CAPIF support** + + + +Figure 6.14.2-2: Combined NEF+SCEF NF with CAPIF support. This diagram is similar to Figure 6.14.2-1 but includes a CAPIF core function. The CAPIF core function is connected to the SCEF+NEF node via a CAPIF-3/4/5 interface and to the AF via a CAPIF-1 interface. The SCEF+NEF node is connected to the AF via an N33/Nnef/CAPIF-2 interface. The UE is now labeled as '3G/4G/5G capable UE'. + +**Figure 6.14.2-2: Combined NEF+SCEF NF with CAPIF support** + +Interactions between the SCEF and NEF within the combined SCEF+NEF node is not required to be standardized. + +In the case of architecture without CAPIF support, the AF is locally configured with the API termination points for each service. In case of architecture with CAPIF support, the AF obtains the service API information from the CAPIF core function via the Availability of service APIs event notification or Service Discover Response as specified in TS 23.222 [20]. + +For each UE, a service API may become unavailable because the UE is being served by a node (e.g. MME) or NF (e.g. AMF) even if the service is exposed by SCEF+NEF. + +If a service API provided by SCEF+NEF becomes unavailable or its level of support changes because of the change of CN Type serving the UE, the SCEF+NEF node may inform the change to the related AF per the AF's subscription to the API supported Change event. + +HSS+UDM supports CN Type Change Event Id. When the HSS+UDM detects that the UE switches between being served by a MME and an AMF, the CN Type Change Event is triggered. HSS+UDM supports CN Type Query. When the UE or all members of a UE Group are being served by a MME, EPC is determined as CN type. When the UE or all members of a UE Group are being served by an AMF, 5GC is determined as CN type. When the UE is operating in dual registration mode, i.e. the UE is registering both in EPC and 5GC, or some members of a UE Group are registering in EPC while some members are registering in 5GC, 5GC/EPC is determined as CN type. + +SCEF+NEF supports APISupportCapability service, which will be configured on AF without CAPIF support or discovered by AF with CAPIF support. This service consists of Subscribe/Unsubscribe/Notification/Get service operations. + +SCEF+NEF determines the CN Type locally in the following conditions: + +- The Freshness Timer of last query request is not expired. The Freshness Timer is a parameter that is configured based on local SCEF policy. When an APISupportCapability\_Query Request is received, the SCEF checks if it recently retrieved the CN Type for the indicated UE ID or External Group ID. If the elapsed time since the last retrieval of the CN Type for the indicated UE ID or External Group ID is less than the Freshness Timer, then the + +SCEF may respond to the AF with the CN Type that was last retrieved, thus avoiding repeated HSS+UDM requests. + +- The SCEF+NEF has established a direct connection with MME or AMF or SMF for Non-IP data transfer. + +Otherwise, SCEF+NEF gets the CN Type serving the UE from HSS+UDM. With the CN Type information, the SCEF+NEF can determine the availability or expected level of support of a given service. The third party applications will be informed of such information. + +For the subscription to APISupportCapability service, the subscription may include the duration of subscription. If the duration of subscription is expired, the SCEF deletes the subscription to the APISupportCapability service without any explicit signalling interaction. For the CN type Change event subscription, the subscription may include the duration of subscription. If the duration of subscription is expired, the related NF locally unsubscribe the CN type change event without any explicit signalling interaction. + +### 6.14.3 Support of EPC interworking + +Consistent with existing EPS-5GS interworking scenarios in TS 23.501 [5] and TS 23.502 [7]. + +### 6.14.4 Procedures + +#### 6.14.4.1 Subscribe and Notify service operations information flow + + + +``` + +sequenceDiagram + participant UE + participant MME + participant AMF + participant HSS+UDM + participant SCEF+NEF as SCEF + NEF + participant AF + + Note right of SCEF+NEF: SCEF + NEF + AF->>SCEF+NEF: 1. APISupportCapability_Subscribe (UE ID or External Group ID, callback URI) + SCEF+NEF->>HSS+UDM: 2. Event Subscribe or Monitoring Request (CN Type Change, UE ID or External Group ID) + HSS+UDM->>SCEF+NEF: 3. Store CN Type Change Event subscription + Note left of AMF: 4. UE Changes between being served between EPC and 5GC + AMF-->>SCEF+NEF: 4.1 Nudm_UECM_Registration or Nudm_UECM_Deregistration + AMF-->>HSS+UDM: 4.2 Update Location Request + HSS+UDM->>SCEF+NEF: 5. Detects that the UE is changing between EPC and 5GC + SCEF+NEF->>HSS+UDM: 6. Event Notify or Monitoring Response or Indication (CN Type, UE ID or External Group ID) + Note right of SCEF+NEF: 7. Based on the CN Type and the subscription, it determines the API that can be supported + SCEF+NEF->>AF: 8. APISupportCapability_Notify (API Indication, UE ID or External Group ID) + Note right of AF: 8a. To Callback URI + AF-->>AF: 9. Acquire the availability or expected level of support of a service + +``` + +Sequence diagram illustrating the APISupportCapability\_Subscribe and Notify operations information flow. The diagram shows interactions between UE, MME, AMF, HSS+UDM, SCEF+NEF (combined), and AF. The process starts with the AF sending a subscription request to the SCEF+NEF. The SCEF+NEF then sends an event subscribe request to the HSS+UDM. The HSS+UDM stores the subscription. When the UE changes between EPC and 5GC, the AMF sends a Nudm\_UECM\_Registration or Nudm\_UECM\_Deregistration message to the SCEF+NEF. The SCEF+NEF detects the change and sends an event notify response to the HSS+UDM. Based on the CN Type and subscription, the SCEF+NEF determines the API that can be supported and sends an API support capability notify message to the AF. The AF then acquires the availability or expected level of support of a service. + +**Figure 6.14.4.1-1: APISupportCapability\_Subscribe and Notify operations** + +1. The AF subscribes to APISupportCapability service for a UE or a group of UEs by sending APISupportCapability\_Subscribe (UE ID or External Group ID, callback URI, Duration of Reporting) message to the SCEF+NEF node. + +The callback URI parameter is optional and is used in step 8a if provided. + +The Duration of Reporting is optional and is used to indicate when the subscription is invalid. + +2. If the SCEF+NEF has not established connection with MME/AMF/SMF for Non-IP data transfer, he SCEF+NEF subscribes the CN Type Change event to HSS+UDM by sending Event Subscribe or Monitoring Request (CN Type Change, UE ID or External Group ID, Duration of Reporting) message. Otherwise, Step 2 ~ Step 6 are omitted, the SCEF+NEF determines the CN type based on the active type of connection for Non-IP data transfer. + +If Monitoring Request is used, it shall include Reference ID as a parameter. If Duration of Reporting is received at Step 1, it shall include Duration of Reporting as a parameter. + +3. HSS+UDM stores the CN Type Change Event subscription for the UE or a group of UEs indicated in step 2. +4. UE changes between being served between EPC and 5GC. If UE changes to EPC from 5GC, the AMF will invoke Nudm\_UECM\_Deregistration service operation to HSS+UDM, the MME will send Update Location Request message to HSS+UDM. If UE changes to 5GC, the AMF will invoke Nudm\_UECM\_Registration service operation to HSS+UDM. +5. Upon reception of the messages at step 4, the HSS+UDM will detect that the UE is switching between EPC and 5GC. If the UE or the group the UE belongs to is indicated in the CN Type Change Event subscription at step 3, then the HSS+UDM determines the CN Type that is serving or going to serve the UE or the group. If the UE is operating in dual registration mode, the HSS+UDM determines the 5GC/EPC as CN Type. If some members of the group are registering in EPC while some members are registering in 5GC, the HSS+UDM determines the 5GC/EPC as CN Type. +6. The HSS+UDM informs SCEF+NEF of the CN Type information by sending Event Notify or Monitoring Response or Indication (CN Type, UE ID or External Group ID). + +The CN Type denotes the 5GC or EPC or 5GC/EPC serving the UE or the group. + +If Monitoring Response or Indication is used, it shall include Reference ID indicated in step 2. + +7. According to the CN Type received and local configuration, the SCEF+NEF node determines the availability or expected level of support of common north-bound APIs for the UE or the group. +8. SCEF+NEF inform AF of the availability or expected level of support of common north-bound APIs for the UE or the group by sending APISupportCapability\_Notify (API Indication, UE ID or External Group ID) message. + +API Indication can either be the list of available north-bound API or the list of pair (north-bound API, status). The status indicate whether the north-bound API is available or unavailable. + +- 8a. [Conditional] If callback URI is provided at step 1, then SCEF+NEF will send the APISupportCapability\_Notify (API Indication, UE ID or External Group ID) message to the node addressed by callback URI. +9. Upon reception of the messages at step 8, the AF obtains and stores the availability or expected level of support of a given service for the UE or the group. If required later, the AF can select the valid north-bound API based on availability or expected level of support of a given service for the UE or the group. + +#### 6.14.4.2 Unsubscribe service operation information flow + +If the AF invokes APISupportCapability\_Subscribe service to SCEF+NEF node with the Duration of Reporting parameter, the subscription on the SCEF+NEF and HSS+UDM are implicitly unsubscribed if the Duration of Reporting expires, i.e. the explicit unsubscribe service operation is not needed. + +In case the explicit unsubscribe operation is needed, the information flow is as following: + + + +``` + +sequenceDiagram + participant AF + participant SCEF+NEF as SCEF + NEF + participant HSS+UDM + Note right of SCEF+NEF: SCEF + NEF + AF->>SCEF+NEF: 1. APISupportCapability_Unsubscribe Request(UE ID or External Group ID) + SCEF+NEF->>HSS+UDM: 2. Event Unsubscribe Request or Monitoring Request(CN Type Change, UE ID or External Group ID) + Note left of HSS+UDM: 3. Delete CN Type Change Event subscription + HSS+UDM->>SCEF+NEF: 4. Event Unsubscribe Response or Monitoring Response or Indication (result indication) + Note right of SCEF+NEF: 5. Delete APISupportCapability subscription + SCEF+NEF->>AF: 6. APISupportCapability_Unsubscribe Response (Result Indication) + +``` + +Sequence diagram for APISupportCapability\_Unsubscribe operations. The diagram shows the interaction between HSS+UDM, SCEF+NEF (grouped), and AF. The steps are: 1. AF sends APISupportCapability\_Unsubscribe Request(UE ID or External Group ID) to SCEF+NEF. 2. SCEF+NEF sends Event Unsubscribe Request or Monitoring Request(CN Type Change, UE ID or External Group ID) to HSS+UDM. 3. HSS+UDM performs 'Delete CN Type Change Event subscription'. 4. HSS+UDM sends Event Unsubscribe Response or Monitoring Response or Indication (result indication) to SCEF+NEF. 5. SCEF+NEF performs 'Delete APISupportCapability subscription'. 6. SCEF+NEF sends APISupportCapability\_Unsubscribe Response (Result Indication) to AF. + +Figure 6.14.4.2-1: APISupportCapability\_Unsubscribe operations + +1. The AF unsubscribes to APISupportCapability service API for a UE or a group of UEs by sending APISupportCapability\_Unsubscribe Request(UE ID or External Group ID) message to the SCEF+NEF node. + +- The SCEF+NEF unsubscribes the CN Type Change event from HSS+UDM by sending Event Unsubscribe or Monitoring Request (CN Type Change, UE ID or External Group ID) message. + +If Monitoring Request is used, it shall include the Reference ID for Deletion. + +- HSS+UDM deletes the CN Type Change Event subscription for the UE or a group of UEs indicated in step 2. +- HSS+UDM responses to the SCEF+NEF by sending Event Unsubscribe Response or Monitoring Response or Indication (result indication) message to SCEF+NEF. +- If result indication indicates the operation is successful, the SCEF+NEF deletes the APISupportCapability subscription. +- SCEF+NEF acknowledges the operation result by sending APISupportCapability\_Unsubscribe Response (Result Indication) to AF. + +### 6.14.4.3 Query service operation information flow + + + +``` + +sequenceDiagram + participant AF + participant SCEF+NEF as SCEF+NEF + participant HSS+UDM + Note right of SCEF+NEF: [SCEF + NEF] + AF->>SCEF+NEF: 1. APISupportCapability_Query Request (UE ID or External Group ID) + SCEF+NEF->>HSS+UDM: 2. Nudm_UE ContextManagement_Get Request (CN Type, UE ID or External Group ID) + Note left of HSS+UDM: 3. Determine the CN Type based on the registered MME and AMF + HSS+UDM->>SCEF+NEF: 4. Nudm_UE ContextManagement_Get Response (CN Type) + Note right of SCEF+NEF: 5. Based on the CN Type, AF determines the API that can be supported + SCEF+NEF->>AF: 6. APISupportCapability_Query Response (API Indication) + Note right of AF: 7. Acquire the availability or expected level of support of a service + +``` + +Sequence diagram for APISupportCapability\_Query operation. Lifelines: HSS+UDM, SCEF+NEF (combined), and AF. The sequence starts with the AF sending a Query Request to the SCEF+NEF. The SCEF+NEF then sends a Get Request to the HSS+UDM. The HSS+UDM determines the CN Type and returns a Get Response. The SCEF+NEF then determines the supported API and returns a Query Response to the AF. Finally, the AF acquires the availability or expected level of support. + +Figure 6.14.4.3-1: APISupportCapability\_Query operation + +- The AF requests the availability or expected level of support of a service API for a UE or a group of UEs from SCEF+NEF by sending APISupportCapability\_Query Request (UE ID or External Group ID) message to the SCEF+NEF node. +- If the Freshness Timer of last query is not expired, the SCEF+NEF determines the CN type locally, Step 2 ~ Step 4 are omitted. Otherwise, the SCEF+NEF gets the CN Type serving the UE or the group from UDM+HSS by sending Nudm\_UE ContextManagement\_Get Request (CN Type, UE ID or External Group ID) message. + +CN Type indicates that this request is for the serving CN Type of the indicated UE or group. + +- Upon reception of the request at step 3, the HSS+UDM determines the CN Type that is serving the UE or the group based on the registered MME or AMF. +- The HSS+UDM informs SCEF+NEF of the CN Type by sending Nudm\_UE ContextManagement\_Get Response (CN Type, Freshness Timer) message. The Freshness Timer is set per operator's policy, e.g. based on the statistics of UE activity. +- According to the CN Type received and local configuration, the SCEF+NEF node determines the availability or expected level of support of common north-bound APIs for the UE or the group. +- SCEF+NEF inform AF of the availability or expected level of support of common north-bound APIs for the UE or the group by sending APISupportCapability\_Query Response (API Indication) message. + +API Indication can either be the list of available north-bound API or the list of pair (north-bound API, status). The status indicate whether the north-bound API is available or unavailable. + +7. Upon reception of the messages at step 7, the AF obtains the availability or expected level of support of a given service for the UE or the group. If required, the AF can select the valid north-bound API based on availability or expected level of support of a given service for the UE or the group. + +## 6.14.5 Impacts on existing entities and interfaces + +Enhancements on HSS+UDM include the following: + +- CN Type Change Event, it should provide the subscription and notification for CN Type Change Event Id to SCEF+NEF; +- CN Type Information Retrieval, it should support the query request for CN Type from SCEF+NEF; + +Enhancements on SCEF+NEF include the following: + +- APISupportCapability service, it supports informing AF of the availability or expected level of support of a given service via a response to the request of the applications or via a notification to the subscription of the applications. +- CN Type Change Event Subscribe/Notify, it should support the subscription to CN Type Change Event to HSS+UDM and receive the notification for CN Type Change Event from HSS+UDM. +- CN Type Information Retrieval, it should support the request for CN Type from HSS+UDM. + +Enhancements on AF include the following: + +- APISupportCapability service, it supports obtainment of the availability or expected level of support of a given service by requesting or subscribing to the SCEF+NEF via APISupportCapability service. + +The API interface that is exposed by the SCEF+NEF interface is an N33 / Nnef interface that supports the T8 APIs. + +In terms of the CAPIF, the SCEF+NEF should be viewed as a single node. + +## 6.14.6 Evaluation + +The solution describes how, if the level of support of a given service changes (e.g. due to the UE's movement between EPC and 5GC), the SCEF+NEF will notify the SCS/AS. + +# 6.15 Solution 15: External parameter provisioning in the 5GC + +## 6.15.1 Introduction + +This solution applies to Key issue 10 (Network Parameter Configuration API via NEF) and to Key issue 13 (Support for Expected UE Behaviour). + +The solution attempts to generalize the handling of external parameter provisioning in the network for the available northbound APIs. + +The "external parameters" are used as general term for the parameters which can be provisioned via different northbound APIs, e.g. Communication Pattern parameters (described in TS 23.682 [6] clause 5.10.1), Network Configuration parameters (described in TS 23.682 [6] clause 4.5.21), or Expected UE Moving Trajectory (described in TS 23.502 [7] clause 4.15.6). + +New Communication Pattern parameters to assist network/UE configuration for CIoT features are described in Solution 26 (see clause 6.26). + +## 6.15.2 Functional Description + +The main principles of the solution are: + +- Certain external parameters are specific to the PDU Session behaviour. Such parameters are classified as session management (SM) parameters and these are provisioned to the SMF (i.e. SMF-Associated parameters). +- Certain external parameters are specific to the UE mobility management (MM) configuration and these parameters are provisioned to the AMF (i.e. AMF-Associated parameters). + +- Another external parameters may be specific to the Policy Control (PC) and can be appropriately stored in the UDR for access by the PCF (i.e. PCF-Associated parameters). +- The UDM/UDR classifies the external parameters into AMF- Associated parameters, SMF- Associated parameters and possibly PCF- Associated parameters. The SMF- Associated parameters are further associated with a particular subscribed DNN and/or S-NSSAI. + +While processing the external parameters, the UDM/UDR consider whether the concerned UE has subscribed DNN(s). If there is no subscribed DNN (e.g. the UE uses SMS only) or S-NSSAI in the user subscription, the UDM/UDR classifies all external parameters as AMF- Associated parameters. If there is at least one subscribed DNN or S-NSSAI, the UDM/UDR determines the DNN and the S-NSSAI to which the sending AF is associated with. + +It is a subject of local policy in the UDM/UDR which external parameters are classified as AMF- Associated, SMF- Associated, and PCF- Associated parameters. + +NOTE: It may be possible for parameters to be classified as being associated with multiple NFs. + +Each external parameter set may be associated with a validity time. The validity time is stored at the UDM/UDR and in each of the NFs, to which parameters has been provisioned (e.g. in AMF or SMF). Upon expiration of the validity time, each node deletes the parameters autonomously without explicit signalling. This processing is similar to the handling of validity time in EPS as described in TS 23.682 [6] clause 5.10.1. + +### 6.15.3 Support of EPC interworking + +The support of interworking in this solution depends on the conclusions for Key Issue 9 (Support of common north-bound APIs for EPC-5GC Interworking). + +Assuming that for EPC interworking a co-located SCEF+NEF entity and co-located HSS+UDM entity are deployed, then the enhancement proposed in this solution to the UDM and NEF would be applicable to the co-located entities. During mobility to/from EPC the entities in the target CN (e.g. MME in EPC; or AMF and/or SMF in 5GC) need to download the "external parameters" from the HSS+UDM. The HSS+UDM sends the "external parameters" in the corresponding format to be processed in the target CN entity. + +A possible mapping table between EPS Communication Pattern parameters and 5GS Expected UE Behaviour is shown in solution 26 (see clause 6.26.3). + +The mapping of the EPS Network Configuration parameters and 5GS Network Configuration parameters is one to one. + +### 6.15.4 Procedures + +In this clause the procedure for external parameter provisioning is described. + + + +``` + +sequenceDiagram + participant AMF + participant SMF + participant UDM/UDR + participant NEF + participant AF1 + participant AF2 + + Note right of AF1: 1. Add/update/delete request +(API CP: Communication Pattern, AF ID.) +(API NPC: Max.Res.T, Max.Latency, ...) +Note right of AF2: 1. Add/update/delete request +(API CP: Communication Pattern, AF ID.) +(API NPC: Max.Res.T, Max.Latency, ...) +AF1->>NEF: 1. Add/update/delete request +AF2->>NEF: 1. Add/update/delete request +NEF->>UDM/UDR: 2. Discover UDM +NEF->>UDM/UDR: 3. Update CP/NC Parameter Request (external parameter set(s), AF ID) +Note right of UDM/UDR: 4a. Classifies CP/NC parameters +(considering single or multiple Apps): +- for AMF +- for SMF to relevant DNN/S-NSSAI +Note right of UDM/UDR: 4b. Update UE subscription +UDM/UDR->>NEF: 5. Update CP Parameter Response +NEF->>AF1: 6. Update Response +NEF->>AF2: 6. Update Response +UDM/UDR->>AMF: 7a. Update (AMF associated parameters) +Note right of AMF: 7b. UE/RAN Configuration Update +Note right of SMF: 8a. TS 23.502 subclause 4.3.2.2.1 (PDU Session Establishment), steps 1-3 +Note right of SMF: 8b. 23.502 4.3.2.2.1 step 4 + SMF associated parameters. +SMF->>AMF: 8c.Nsmf_PDUSessionCreateSMContextResponse (TS 23.502 4.3.2.2.1 step 5 + SMF associated parameters) +Note right of SMF: 8d. TS 23.502 subclause 4.3.2.2.1 (PDU Session Establishment), step Steps 6-20 + +``` + +Sequence diagram showing external parameters provisioning to AMF and SMF. Lifelines: AMF, SMF, UDM/UDR, NEF, AF1, AF2. The process involves AFs sending requests to NEF, NEF discovering UDM, NEF sending update requests to UDM, UDM classifying parameters for AMF and SMF, UDM updating UE subscription, UDM sending responses to NEF, NEF sending responses to AFs, UDM sending updates to AMF, AMF performing UE/RAN configuration update, and finally PDU session establishment steps involving SMF and AMF. + +**Figure 6.15.4.1-1: External parameters provisioning to AMF and to SMF** + +1. The AF(s) may use various APIs to provide parameters specific to a given UE application (or the UE as such if a single application is used in the UE) in order to help the network for efficient configuration. The AF(s) may add/modify/delete the parameters to the network (e.g. to NEF). +2. NEF/SCEF discovers a UDM/UDR based on the UE's External ID. Similar to step 2 in TS 23.682 [6] clause 5.10.2. +3. NEF to UDM: Nudm\_ParameterProvision\_Update (GPSI, AF ID, NEF Transaction Reference ID(s), external parameter set(s), validity time(s)). +4. In step 4a the UDM/UDR may categorizes the external parameters into AMF- Associated and SMF- Associated parameters. The SMF parameters are further associated with a particular subscribed DNN and/or S-NSSAI. The UDM/UDR uses the AF ID to determine the corresponding DNN and S-NSSAI. +In step 4b the UDM/UDR updates the corresponding fields in the UE subscription. +5. - 6. Steps similar to steps 5, 6 in TS 23.682 [6] clause 5.10.2. +7. UDM to AMF: Nudm\_SubscriberDataManagement (SDM)\_Notification (SUPI, AMF- Associated parameters, etc.). + +The AMF stores and uses the received AMF parameters to derive the appropriate UE configuration. The AMF-Associated parameters can be e.g. "Stationary indication", "Battery Indication" or "Expected UE Moving Trajectory", "Maximum Latency", "Maximum Response Time", "Suggested Number of Downlink Packets". For example, the AMF may determine a Registration area based on parameters "Stationary indication" or "Expected + +UE Moving Trajectory". The AMF identifies whether there are overlapping parameter set(s) and merges the parameter set(s), if necessary. + +8. PDU Session Establishment procedure steps 1-3 from TS 23.502 [7] clause 4.3.2.2.1. + +In step 8a, the PDU Session Establishment procedure is triggered. + +In step 8b, UDM to SMF: the UDM performs service operation Nudm\_SubscriberDataManagement (SDM)\_Notification (SUPI, SMF-Associated parameter set, DNN/S-NSSAI, etc.). See step 4 of PDU Session Establishment in TS 23.502 [7], clause 4.3.2.2.1 + +The SMF stores the received SMF-Associated parameters and associates them with a PDU Session based on the DNN and S-NSSAI included in the message from UDM. The SMF identifies whether there are overlapping parameter set(s) and merges the parameter set(s), if necessary. The SMF-Associated parameters can be e.g. Communication Duration Time, Periodic Time, Scheduled Communication Time, Suggested Number of Downlink Packets. The SMF uses the SMF-Associated parameters to also appropriately configure the UPF. For example, the SMF can use the Scheduled Communication Type to configure the UPF how many downlink packets to buffer. The SMF may use e.g. the Communication duration time to determine to deactivate UP connection after the Communication duration time expires and the SMF performs the procedure CN-initiated selective deactivation of UP connection of an existing PDU Session as described in TS 23.502 [7] clause 4.3.7. + +Step 8c: If the PDU session uses NAS-SM to transfer PDUs, the SMF forwards to the AMF all parameters in step 8b of the PDU Session Establishment procedure. The AMF may identify whether there are overlapping SMF parameter set(s) and merge the parameter set(s), if necessary e.g. when the UE context is provided to the NG-RAN after RRC msg #3. + +NOTE 1: If the PDU sessions uses NAS-SM to transfer PDUs, the delivery of the UE Expected Behavior parameters to the NG-RAN is done by the AMF. If the PDU session does not use NAS-SM to transfer PDUs, the delivery of the UE Expected Behavior parameters to the NG-RAN is done by the SMF. See Solution 28 for more details. + +Step 8d: the remaining steps of the PDU Session Establishment procedure are executed. + +NOTE 2: The SMF can update the parameters in the AMF during the PDU Session Modification procedure. In that case, Steps 8a-8d of this message flow would coincide with the steps of Figure 4.3.3.2-1 of TS 23.502 [7]; in particular, Step 8c would match Step 3a of the PDU Session Modification Procedure. + +The deletion or modification of external parameters is performed similarly to the descriptions in TS 23.682 [6] clause 5.10.2. + +## 6.15.5 Impacts on existing entities and interfaces + +Enhancements to UDM/UDR (or potentially to co-located HSS+UDM) include the following: + +- The external parameters are categorized into AMF-Associated, SMF-Associated -specific and PCF-Associated parameters. The SMF parameters are further associated with a particular subscribed DNN and/or S-NSSAI. + +Enhancements to SMF include the following: + +- The SMF uses the SMF-Associated parameters to appropriately configure the UPF; +- The SMF provides the SMF-Associated parameters to the AMF when a PDU session is created. + +Enhancements to the AMF include the following: + +- The AMF takes into account the SMF associated parameters from all SMFs when deriving CN Assistance Information provided to NG-RAN. + +## 6.15.6 Evaluation + +This solution allows multiple AFs to provide the CN with set of external parameters (e.g. Communication Pattern parameters, Network Configuration parameters) to be used for network configuration and UE configuration. + +## 6.16 Solution 16: UE assisted Inter-UE QoS Support for Data over NAS + +### 6.16.1 Introduction + +This solution addresses Key Issue 14: QoS Support for NB-IoT for the case of Data over NAS. It can also be applied to WB-E-UTRA (eMTC) when Data over NAS is used. + +### 6.16.2 Functional Description + +The solution is based on the UE providing a QoS index during RRC connection procedure for the case of Data over NAS. + +The following applies to the solution: + +- During registration procedure, if Data over NAS is set-up, the AMF provides a QoS index to the UE. The AMF receives the QoS index from the UDM during the exchange as defined in TS 23.502 [7]. +- When the UE decides to send data over NAS, during the RRC connection establishment procedure, the UE provides the QoS index in RRC connection request message. +- The RAN determines how to handle the connection based on the UE provided QoS index, i.e the RAN can prioritise resource allocation between different UEs when some of the UEs are using data over NAS based on the received QoS index. +- If the RAN decides to go ahead and establish the RRC connection and the UE sends the data over NAS payload, the RAN sends the UE provided QoS index to the AMF in the N2 message carrying the Data over NAS payload. +- The AMF can check whether the QoS index provided by the UE and the QoS index configured by the network are the same. In case they are different, the AMF has detected a misbehaving UE, i.e. a UE that is not compliant with 3GPP specifications. The AMF may then back-off or deregister the UE with a corresponding cause code. + +### 6.16.3 Support of EPC interworking + +### 6.16.4 Procedures + +#### 6.16.4.1 QoS Index configuration during Registration Procedure + + + +``` +sequenceDiagram + participant UE + participant RAN + participant AMF + participant UDM + Note right of AMF: 2. Steps 4-13 of Registration procedure TS 23.502 4.2.2.2.2 + Note right of UDM: 3. Step 14 of Registration procedure TS 23.502 4.2.2.2.2, UDM provides QoS index + Note right of AMF: 4. Steps 15-21 of Registration procedure TS 23.502 4.2.2.2.2 + UE->>AMF: 1. Registration Request (Data over NAS) + AMF->>UE: 5. Registration Accept (QoS Index) + UE-->>AMF: 6. Registration Complete +``` + +Sequence diagram showing QoS index configuration during Registration procedure. The diagram involves four entities: UE, RAN, AMF, and UDM. The sequence starts with the UE sending a Registration Request (Data over NAS) to the AMF. This is followed by a block representing steps 4-13 of the registration procedure (TS 23.502 4.2.2.2.2). Then, step 14 (TS 23.502 4.2.2.2.2) occurs, where the UDM provides the QoS index to the AMF. This is followed by a block representing steps 15-21 of the registration procedure (TS 23.502 4.2.2.2.2). Finally, the AMF sends a Registration Accept (QoS Index) to the UE, and the UE sends a Registration Complete message back to the AMF. + +**Figure 6.16.4.1-1: QoS index configuration during Registration procedure** + +All steps from TS 23.502 [7] clause 4.2.2.2.2 are followed with the following differences. + +1. If the UE wants to use Data over NAS, it indicates this to the AMF in NAS Registration request message. +2. (Steps 4-13 from TS 23.502 [7] clause 4.2.2.2.2 unchanged). +3. In Step 14, the UDM includes the QoS index in the Access and Mobility Subscription data. +4. (Steps 15-21 from TS 23.502 [7], clause 4.2.2.2.2 unchanged). +5. The AMF provides with the QoS Index to the UE in the Registration accept message. The UE stores this value, and only uses it if Data over NAS is set up with SMF, and the UE decides to send a data packet over NAS. + +#### 6.16.4.2 Using QoS index in MO Data over NAS + +The following call flow is based on Solution 1 (clause 6.1) for Data Transport over NAS-SM, but can easily be used for other possible data over NAS solutions. + + + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant AMF + participant SMF/NEF + participant UPF + + Note left of UE: 0. UE is in CM-IDLE + UE->>NG-RAN: 1. RRC connection Request(QoS index) + Note right of NG-RAN: 2. Consider QoS index for resource prioritization + NG-RAN->>UE: 3. RRC connection setup + UE->>NG-RAN: 4. RRC connection Complete(NAS transport (SM data transfer, PDU Session ID)) + NG-RAN->>AMF: 5. Initial UE message (QoS index, NAS transport (SM data transfer, PDU session ID)) + Note right of AMF: 6. AMF checks a posteriori UE provided QoS index = NW provided QoS index + Note bottom: 7. Complete Data transport over NAS-SM + +``` + +Sequence diagram illustrating the use of QoS index in MO data over NAS. The diagram shows interactions between UE, NG-RAN, AMF, SMF/NEF, and UPF. The process starts with the UE in CM-IDLE state. The UE sends an RRC connection Request with a QoS index to the NG-RAN. The NG-RAN considers the QoS index for resource prioritization. The NG-RAN sends an RRC connection setup to the UE. The UE responds with an RRC connection Complete message containing NAS transport (SM data transfer, PDU Session ID). The NG-RAN then sends an Initial UE message (QoS index, NAS transport (SM data transfer, PDU session ID)) to the AMF. The AMF checks the a posteriori UE provided QoS index against the NW provided QoS index. Finally, data transport is completed over NAS-SM. + +**Figure 6.16.4.2-1: Use of QoS index in MO data over NAS** + +0. The solution applies when the UE initiates data transport over NAS(-SM) from CM-IDLE state. +1. If the UE has been configured with QoS index and decides to send data over NAS(-SM), then the UE includes the QoS index in RRC connection request. +**Editor's note: The exact mechanism by which the QoS index will be provided to RAN will be defined by RAN WG2.** +2. The RAN node considers the UE provided QoS index to prioritise resource allocation between different UEs when some of the UEs are using data over NAS. +3. RAN node sends RRC connection setup. +4. UE sends RRC connection Complete(NAS transport(SM data transfer, PDU Session ID)) as per Solution 1. +5. The RAN node sends the UE provided QoS index in the Initial UE message to AMF together with the NAS transport message. +6. AMF can check if the UE is misbehaving by comparing the UE provided QoS index with the NW configured QoS index. If the AMF detects the UE is misbehaving it may take multiple actions, e.g. deregister the UE with specific cause code, or reject NAS transport with a back-off timer. +7. Completion of data transport over NAS-SM as per Solution 1. + +## 6.16.5 Impacts on existing entities and interfaces + +The solution has impacts on the following network functions: + +1. AMF: Provision of QoS index to the UE, and a potential a-posteriori check on whether the UE is providing the correct QoS Index. +2. UDM: QoS index storage in subscription information. +3. RAN: Receive QoS index from UE and perform prioritization based on it. +4. UE: configuration of QoS index and providing QoS index in RRC connection request for Data over NAS. + +## 6.16.6 Evaluation + +Advantages: + +- Support QoS differentiation among UEs that use NAS to deliver data. +- Support any types of data, IP, Ethernet, unstructured data. + +Disadvantages: + +- Does not support QoS differentiation if the UE sends only one UL message in Early Data Transmission over NAS. +- Increase the size of some RRC messages to carry QoS index. + +## 6.17 Solution 17: UE-Driven Packet Classification + +### 6.17.1 Introduction + +This solution is proposed for Key Issues 14, QoS Support for NB-IoT. The NB-IoT devices may use UP solutions to send frequent and small data in the UP. The UE may establish a PDU Session as described in TS 23.502 [7], clause 4.3.2. The NB-IoT devices may require 5GS to support multiple QoS flows in one Unstructured PDU Session. For example, one QoS Flow may be used to carry low priority data such as regular sensor data. Another QoS Flow may be used to carry the emergent messages, such as high temperature alarm, high heart beat rate. + +### 6.17.2 Functional Description + +The NB-IoT devices request PDU Session Establishment to send unstructured data. Based on the UE Subscription information in the UDM/UDR, the UE may support multiple QoS Flows in one unstructured PDU Session and based on the SLA, the SMF can assign multiple QoS Rules to the UE. Each QoS Rule is associated with one QoS Flow Identifier (QFI), but there are no Packet Filter Sets. The local policy handling function in the UE can understand the QoS parameters in the QoS rule(s) (such as 5QI, and bit rate). The UE may have non-standardized packet filtering mechanisms for CIoT protocols. Based on the QoS requirements and the QoS parameters in the QoS rule(s), the UE has its own logic to perform packet classification and map the UL PDU to QoS Flows. + +During the PDU Session Establishment, the SMF also sends multiple QoS Profiles to the (R)AN, each QoS Profile has a unique QFI for one QoS Flow the UE may use. + +During the PDU Session Establishment, the SMF also sends multiple N6 Service Data Flow (SDF) templates to the UPF. Each N6 SDF template has an N6 Packet Filter Set (PFS) and each N6 PFS is mapped to one N3/N9 QFI. In case of N6 IP tunnel, the SMF may assign one unique IP address/prefix for each QoS Flow. Alternatively, the SMF may assign the same IP address/prefix for all QoS Flows, but each QoS Flow uses a unique UDP port, or unique Flow Label, or Traffic Class as part of SDF template. The UPF establishes IP tunnel(s) with the AS using the assigned IP address(es)/prefix(es) or UDP port(s). + +When the UE sends an UL PDU, the UE uses its own logic to map the UL PDU to QoS Flow. The UE may add a QFI to the UL PDU and sends to the (R)AN. The (R)AN receives the UL PDU, adds a QFI as part of N3 header and sends the N3-encapsulated PDU to the UPF. The UPF removes the N3 encapsulation, adds the N6 tunnel header to the PDU. Different QoS Flows can be associated with a unique N6 IP address/prefix and/or unique UDP port of UPF. The UPF sends the PDU with unique N6 IP packet header to the Application Server (AS). + +The UPF can classify DL unstructured PDUs received from N6 interface into multiple QoS Flows with different QFI. The AS may send downlink packets to the UE. The AS uses the source information in the N6 tunnel header that the UPF used to send the UL PDU for sending DL packet to the UPF. The UPF receives the DL PDU, uses the mapping between N6 PFS and QFI to classify the PDUs into QoS Flows and send the DL PDU to the (R)AN. The (R)AN sends the DL PDU to the UE using a data radio bearer (DRB) assigned to the QoS Flow. + +### 6.17.3 Support of EPC interworking + +Not applicable. + +## 6.17.4 Procedures + +The high-level procedure for sending UL unstructured PDU is described in Figure 6.17.4-1. + + + +``` + +sequenceDiagram + participant SMF + participant UE + participant RAN as (R)AN + participant UPF + participant DN + + Note left of SMF: During PDU Session Establishment + SMF->>UE: 1. QoS Rules with no Packet Filter Sets + SMF->>UPF: 2. QFI-N6 Tunnel Mapping + Note right of UE: 3. Classify UL Unstructured PDU, Attach QFI + UE->>RAN: 4. UL Unstructured PDU with QFI + Note right of RAN: 5. Recognise QFI, Encapsulate UL Unstructured PDU Packets + RAN->>UPF: 6. N3 UL PDU with QFI + Note right of UPF: 7. Read UL QFI, remove N3 tunnel header, select N6 Tunnel Header, Encapsulate UL unstructured PDU + UPF->>DN: 8. UL PDU Carried in N6 Tunnel + +``` + +Sequence diagram illustrating the high-level procedure for sending UL unstructured PDU delivery. The diagram shows interactions between SMF, UE, (R)AN, UPF, and DN. The process starts with PDU Session Establishment (steps 1 and 2). Then, the UE classifies the PDU (step 3), sends it to the (R)AN (step 4). The (R)AN encapsulates it (step 5) and sends it to the UPF (step 6). The UPF decapsulates and re-encapsulates it (step 7) before sending it to the DN (step 8). + +**Figure 6.17.4-1: High level description of UL unstructured PDU delivery** + +1. During PDU Session Establishment procedure, the SMF sends QoS Rules to the UE. The QoS Rules do not contain Packet Filter Sets. +2. During PDU Session Establishment procedure, the SMF assigns tunnel parameters for N6 interface. In case of IP/UDP tunnel, the SMF assigns IP address(es) and UPD port number for QoS Flow(s). + +Some other steps are required but not shown in the procedure. For example, the SMF sends QoS Profiles to the (R)AN, the (R)AN establish DRB(s) for QoS Flows. + +If required, one of the QoS Flows may be assigned to carry high priority data, and another QoS Flow is assigned to carry low priority data. + +The SMF assigns corresponding QoS Rules to the UEs, QoS Profiles to the (R)AN, QoS and charging policies to the UPF to reflect the Priority Level, Packet Delay Budget requirements, bit rate requirements and other QoS parameters for QoS Flows. + +3. The UE may have non-standardized packet filtering mechanisms. When the UE wants to send UL PDUs, based on the QoS requirements and the QoS parameters in the QoS rule(s), the UE has its own logic to map UL unstructured PDUs into QoS Flows. +4. The UE sends UL unstructured PDU to the (R)AN using the assigned DRB. The (R)AN performs bit rate control for the UL of unstructured PDU Session according to the QoS Profile(s). +5. The (R)AN receives the UL PDU. The (R)AN encapsulates the UL PDU with N3 tunnel header. +6. The (R)AN sends to the N3-encapsulated PDU to the UPF. +7. The UPF reads the UL QFI, removes the N3 tunnel header. The UPF uses the mapping between UL QFI and N6 tunnel header (e.g. N6 IP source address/prefix) to encapsulate the UL PDU into N6 tunnel PDU format. + +8. The UPF sends UL PDU in the N6 tunnel. + +## 6.17.5 Impacts on existing entities and interfaces + +In the UE: + +- Since no Packet Filter Sets are specified for unstructured PDU data, the UE uses its own logic to classify PDUs into QoS Flows in the uplink. The QoS Rules for unstructured QoS Flows do not have Packet Filter Sets. +- For downlink, the (R)AN uses the assigned DRB(s) for each QoS Flow as the current (R)AN specifications. + +In the UPF: + +- The UPF uses the mapping between N3/N9 QFI and N6 tunnel Packet Filter Sets to send UL PDU to the AS. In case of IP/UDP tunnel, each N6 PFS has a unique set of source IP address/prefix, source UDP port number(s), Flow Label. +- In the downlink, the AS uses the information in the N6 tunnel header to send the DL packets to the UPF. The UPF uses the mapping between N3/N9 QFI and N6 tunnel Packet Filter Sets to classify DL packets into QoS Flows and send to the (R)AN. + +## 6.17.6 Evaluation + +Solution 17 supports QoS differentiation among QoS flows, among PDU Sessions, and among UEs for unstructured data. This solution allows multiple QoS flows in one unstructured PDU Session, which helps to reduce the air interface and CN signaling for PDU Session establishment, modification, handover, AF influence traffic routing and other related procedures. + +In case of MT data, the solution assumes that the AS selects the appropriate tunnel when sending DL data. For MT initiated data it is unclear for the AS which DL tunnel to initially use. + +Impacts to UE: + +- The solution requires changes in the UE to support proprietary packet classification for unstructured PDUs into QoS flows. +- In Rel. 15, one Unstructured PDU Session supports only one QoS Flow. Using Solution 17, one Unstructured PDU Session supports multiple QoS Flows. An application software in the UE may use proprietary methods to classify UL PDUs into multiple QoS flows of the same Unstructured PDU Session. + +Impacts to UPF: + +- There is no impacts to the packet classification method of the UPF. The packet classification in the UPF uses the existing packet filtering mechanism based on N6 tunnel header, such as IP tunnel header. After classifying downlink packets, the UPF sends the downlink PDUs to the N3 or N9 QoS flows as it does for the IP or Ethernet traffic. +- In Rel. 15, one N6 tunnel header is mapped to one unstructured PDU session. Using Solution 16, one N6 tunnel header is mapped to one QoS flow of an Unstructured PDU Session. + +Impacts to QoS Model: + +- In Rel. 15, the Unstructured PDU Session type supports only one QoS flow. The IP or Ethernet PDU Session types support multiple QoS Flows by using packet filters in the UE and UPF. +- Solution 17 allows one Unstructured PDU Session to support multiple QoS Flows. A new feature of Solution 17 is that there is no standardized packet filtering methods to be applied in the UE for unstructured data. For Unstructured PDU Sessions having multiple QoS flows, the QoS Rules sent from the SMF to the UE does not contain packet filters for unstructured data. The UE uses its own logic to classify PDUs into QoS Flows in the UL. +- For the UPF, the SMF sends a mapping between QFI of N3 or N9 tunnel to N6 tunnel header. The UPF uses existing N6 tunnel packet filtering to classify DL PDUs into N3 or N9 QoS flows. This is different from the current mapping in Rel. 15, where one N6 tunnel header is mapped to one Unstructured PDU Session. + +## 6.18 Solution 18: QoS control for unstructured PDU sessions + +### 6.18.1 Introduction + +This solution addresses Key Issue #14, QoS Support for NB-IoT by introducing a mechanism to differentiate traffic flows within a single unstructured PDU session. + +### 6.18.2 Functional Description + +#### 6.18.2.1 QoS Flow mapping for unstructured PDU Session + +Similar to the QoS model defined in TS 23.501 [5], the SMF performs the binding of Service Data Flows (SDFs) to QoS Flows based on the QoS and service requirements (e.g. the received PCC rules). The SMF assigns the QFI for a new QoS Flow and derives its QoS profile from the information provided by the PCF. When applicable, the SMF provides the QFI together with the QoS profile to the (R)AN. The SMF provides the SDF template, i.e. Field Position based Packet Filter (see clause 6.18.2.2) associated with the SDF received from the PCF) together with the SDF template precedence value included in the PCC rule, the QoS related information, and the corresponding packet marking information, i.e. the QFI to UPF. For each SDF, when applicable, the SMF generates a QoS rule. Each of these QoS rules contain the QoS rule identifier, the QFI of the QoS Flow, the Field Position based Packet Filter of the UL part of the SDF template, optionally the Field Position based Packet Filter for the DL part of the SDF template, and the QoS rule precedence value set to the precedence value of the PCC rule from which the QoS rule is generated. The QoS rules are then provided to the UE. + +The principle for classification and marking of User Plane traffic and mapping of QoS Flows to AN resources is illustrated in Figure 6.18.2.1-1. + + + +Diagram illustrating the principle for classification and User Plane marking for QoS Flows and mapping to AN Resources for Unstructured PDU Session. The diagram shows three main components: UE, AN, and UPF, connected by arrows representing data flow. At the top, an oval labeled 'Application /Service Layer' sends 'Data packets from applications' to the UE. The UE uses 'QoS rules for unstructured PDU Session (mapping UL packets to QoS flows and apply QoS flow marking)' to map packets to 'QoS flow (all packets marked with the same "QoS flow ID")'. These are then 'Mapping QoS flows to AN Resources' into the AN. The AN establishes a 'PDU session' and maps flows to 'AN Resources'. The AN sends packets to the UPF, which uses 'SDF templates (classify packets to SDFs) for QoS flow marking' to further classify them. + +**Figure 6.18.2.1-1: Principle for classification and User Plane marking for QoS Flows and mapping to AN Resources for Unstructured PDU Session** + +In DL, incoming data packets are classified by the UPF based on SDF templates according to the precedence of the PCC rule authorizing the service data flow, (without initiating additional N4 signalling). The UPF conveys the classification of the User Plane traffic belonging to a QoS Flow through an N3 (and N9) User Plane marking using a QFI. The AN binds QoS Flows to AN resources (i.e. Data Radio Bearers of in case of 3GPP RAN). For PDU Session types used by NB-IoT (i.e. IPv6, IPv4, and Unstructured), dedicated bearers are not supported in NB-IoT, so multiple QoS Flows can be band to one AN resource. It is up to the AN to establish they AN resources that QoS Flows can be mapped to, and to release it. + +If no match is found and all QoS Flows are related with a DL Field Position based Packet Filter, the UPF shall discard the DL data packet. + +In UL, the UE evaluates UL packets against the Packet Filter in the QoS rules for Unstructured PDU Session based on the precedence value of QoS rules in increasing order until a matching QoS rule (i.e. whose packet filter matches the UL packet) is found. The UE uses the QFI in the corresponding matching QoS rule to bind the UL packet to a QoS Flow. The UE then binds QoS Flows to AN resources. + +If no match is found and the default QoS rule contains an UL Packet Filter, the UE shall discard the UL data packet. + +## 6.18.2.2 QoS Rule for Unstructured PDU Session + +The QoS rules for unstructured PDU sessions are the extension of the QoS rules used for structured PDU sessions. A generic filtering component type is defined that can fit into the existing QoS rules as defined by clause 9.8.4.9 of TS 24.501 [10]. + +The packet filter content is made of a variable number of packet filter components. Each packet filter component has a type followed by a value. clause 9.8.4.9 of TS 24.501 [10] dictates that each filter component type can appear in a filter only once. + +In order to extend the filtering capability, a new component type "Generic filter type" is added to the list of supported components. In addition, the Generic filter type component is exempt from the rule to appear only once in a filter. The generic filter component type can be realized using the field position based packet filter or any variation thereof. + +To construct a filter that matches more than one field in the packet, multiple such Generic filter components are used in a manner similar to the other components. In addition, this Generic filter component can also be used along with other pre-defined filter components. + +### 6.18.2.2.1 Achieving Reflective QoS + +Reflective QoS for IP and Ethernet traffic is enabled by setting rules for the UE to construct an uplink filtering rule from the downlink packet. These rules only support UDP/TCP/ESP as the upper layer protocols for IP type traffic. + +In order to achieve reflective QoS for any traffic type, including unstructured PDU sessions, the following procedures are defined: + +- Install QoS rules with filter direction set as "Reflective". This reflective filter acts as a template that the UE can use to create the uplink filter; +- Only one filter per QFI can be installed as a reflective filter. This is to prevent any ambiguity in picking the filter needed to construct the uplink filter; +- The presence of a reflective filter supersedes the construction rules specified in clause 6.2.5.1.4.2 of TS 24.501 [10]; +- Packet filter components apart from the Generic filter component can be included in reflective filter. When included, the value indicated in these components are ignored; +- When the filter is marked as a reflective filter, the "value" field in the packet filter component of the Generic filter is omitted. + +### 6.18.2.3 Field position based Packet Filters + +The Field position based Packet Filters is used in the QoS rules or SDF template for Unstructured PDU Session to identify a QoS Flow. The Field position based Packet Filter may contain one or more fields position information and their matching value. The information to generate Field position based Packet Filters can be either provided by an AF or preconfigured in the network. + +Figure 6.18.2.3-1 represents the format of an example of unstructured protocol over non-IP. + +| Field 1
(Value: A1)
(Length: a bit) | Field 2
(Value: A2)
(Length: x bit) | Other field(s)
(Value: ...)
(Length: y bit) | Field 3
(Value: A3)
(Length: z bit) | Other field(s)
(Value: ...)
(Length: ...) | +|-------------------------------------------|-------------------------------------------|---------------------------------------------------|-------------------------------------------|-------------------------------------------------| +|-------------------------------------------|-------------------------------------------|---------------------------------------------------|-------------------------------------------|-------------------------------------------------| + +**Figure 6.18.2.3-1: Format of An Example Unstructured Protocol over non-IP** + +As shown in the figure below, Field Position 1, Field Position 2 and Field Position 3 respectively represent the header field that contain in the Example Unstructured Protocol over non-IP in Figure 6.18.2.3-1. The field positions are defined + +by two attribute, the offset and the length $\langle O, L \rangle$ . The offset is defined as the starting position in the packet, in number of bits, and the length field is defined as the number of bits in this field. In addition, a matching value for the referenced part of the unstructured PDU and an operation for the comparison of the set of bits is given. Fields that including in the Field Position based Packet Filters might be any field in the Unstructured Protocol. + +| Field Position | Field Position Offset (bit) | Field Position Length (bit) | Operation ( $=, >, <, or, and, xor$ ), | Matching Value Example | +|------------------|-----------------------------|-----------------------------|----------------------------------------|------------------------| +| Field Position 1 | 0 | a | = | A1 | +| Field Position 2 | a | x | = | A2 | +| Field Position 3 | $a+x+y$ | z | = | A3 | + +Figure 6.18.2.3-2 Field Position based Packet Filters for An Example Unstructured Protocol + +## 6.18.3 Support of EPC interworking + +Editor's note: This clause describes if and how EPC-5GC interworking is supported by this solution. + +## 6.18.4 Procedures + +The high-level procedure for sending UL unstructured PDU is described in Figure 6.18.4-1. + + + +``` + +sequenceDiagram + participant SMF + participant UE + participant (R)AN + participant UPF + participant DN + + Note left of SMF: During PDU Session Establishment + SMF->>UE: 1. QoS Rules with Field Position base Packet Filter Sets + SMF->>UPF: 2. SDF Templates with Field Position base Packet Filter Sets, N6 Tunnel + Note right of SMF: 3. Classify UL Unstructured PDU according to QoS Rule for Unstructured PDU Session + UE->>(R)AN: 4. UL Unstructured PDU with QFI + Note right of (R)AN: 5. Recognise QFI, Encapsulate UL Unstructured PDU Packets + (R)AN->>UPF: 6. N3 UL PDU with QFI + Note right of UPF: 7. QFI Verification, remove N3 tunnel header and encapsulate UL unstructured PDU with N6 Tunnel Header, + UPF->>DN: 8. UL PDU Carried in N6 Tunnel + +``` + +Sequence diagram showing the high-level procedure for sending UL unstructured PDU delivery. The diagram involves five entities: SMF, UE, (R)AN, UPF, and DN. The process starts with PDU Session Establishment where SMF sends QoS Rules and SDF Templates to UE and UPF respectively. Then, UE sends UL Unstructured PDU with QFI to (R)AN. (R)AN recognizes QFI, encapsulates the PDU, and sends N3 UL PDU with QFI to UPF. UPF verifies QFI, removes the N3 tunnel header, and encapsulates the PDU with an N6 Tunnel Header. Finally, the UL PDU is carried in the N6 Tunnel to DN. + +Figure 6.18.4-1: High level description of UL unstructured PDU delivery + +1. During PDU Session Establishment procedure, the SMF sends QoS Rules for Unstructured PDU Session to the UE. The QoS Rules contain Field Position based Packet Filter Sets. +2. During PDU Session Establishment procedure, the SMF sends SDF Templates with Field Position based Packet Filter Sets and tunnel parameters for N6 interface. In case of IP/UDP tunnel, the SMF assigns IP address(es) and UPD port number for QoS Flow(s). +3. When the UE wants to send UL PDUs, the UE evaluates UL packets against the Field Position based Packet Filter in the QoS rules for Unstructured PDU Session based on the precedence value of QoS rules in increasing + +order until a matching QoS rule (i.e. whose packet filter matches the UL packet) is found. The UE uses the QFI in the corresponding matching QoS rule to bind the UL packet to a QoS Flow. + +4. The UE sends UL unstructured PDU to the (R)AN using the assigned DRB. The QFI is attached to the UL PDU. +5. The (R)AN receives the UL PDU. The (R)AN encapsulates the UL PDU with N3 tunnel header. +6. The (R)AN sends to the N3-encapsulated PDU to the UPF. +7. UPF verifies whether QFIs in the UL PDUs are aligned with the QoS Rules for Unstructured PDU Session provided to the UE. The UPF removes the N3 tunnel header and encapsulate UL unstructured PDU with N6 Tunnel Header. +8. The UPF sends UL PDU in the N6 tunnel. + +The high-level procedure for sending DL unstructured PDU is described in Figure 6.18.4-2. + + + +``` + +sequenceDiagram + participant SMF + participant UE + participant RAN as (R)AN + participant UPF + participant DN + + Note left of SMF: During PDU Session Establishment + SMF->>UE: 1. QoS Rules with Field Position base Packet Filter Sets + SMF->>UPF: 2. SDF Templates with Field Position base Packet Filter Sets, N6 Tunnel + Note right of DN: + DN->>UPF: 3. DL PDU Carried in N6 Tunnel + Note right of UPF: 4. Classify DL Unstructured PDU according to SDF templates with Filed Position based Packet Filter for Unstructured PDU Session + UPF->>RAN: 5. UL Unstructured PDU with QFI + Note right of RAN: 6. Binds QoS Flows to AN resources + RAN->>UE: 7. DL Unstructured PDU + +``` + +Sequence diagram showing the high-level procedure for sending DL unstructured PDU delivery between SMF, UE, (R)AN, UPF, and DN. The process starts with PDU Session Establishment where SMF sends QoS Rules and SDF Templates to UE. Then, DN sends DL PDU to UPF, which classifies it and sends it to (R)AN with QFI. (R)AN binds resources and delivers the DL PDU to UE. + +**Figure 6.18.4-2: High level description of DL unstructured PDU delivery** + +1. During PDU Session Establishment procedure, the SMF sends QoS Rules for Unstructured PDU Session to the UE. The QoS Rules contain Field Position based Packet Filter Sets. +2. During PDU Session Establishment procedure, the SMF sends SDF Templates with Field Position based Packet Filter Sets and tunnel parameters for N6 interface. In case of IP/UDP tunnel, the SMF assigns IP address(es) and UPD port number for QoS Flow(s). +3. DN sends DL PDUs carried in N6 Tunnel. The QoS requirements may be embedded in the fields of unstructured PDU and the N6 tunnel parameters. +4. The UPF Classifies DL Unstructured PDU according to SDF templates with Filed Position based Packet Filter and N6 tunnel parameters for Unstructured PDU Session. +5. The UPF sends DL Unstructured PDU with QFI to RAN. +6. The (R)AN binds QoS Flows to AN resources. + +7. The (R)AN sends DL Unstructured PDU to UE. + +## 6.18.5 Impacts on existing entities and interfaces + +In the UE: + +- In UL, for unstructured PDU Session, the UE determines and bind the UL packet to a matching QoS rule based on the Field Position based Packet Filter in the QoS rules. + +In the UPF: + +- In DL, for unstructured PDU Session, the UPF classifies the incoming data packets based on SDF templates with Field Position based Packet Filters. + +## 6.18.6 Evaluation + +Solution 18 supports QoS differentiation among QoS flows, among PDU Sessions, and among UEs for unstructured data. This solution allows multiple QoS flows in one unstructured PDU Session, which helps to reduce the air interface and CN signaling for PDU Session establishment, modification, handover, AF influence traffic routing and other related procedures. + +Impacts to QoS Model: + +- Solution 18 requires new standardization of field position based (FPB) packet filters to be used in the UE and UPF. +- The SMF sends FPB packet filters to the UE and UPF, in the same way as the SMF sends IP or Ethernet packet filters to the UE and UPF. + +Impacts to UE: + +- The NB-IoT UEs need to be designed to support FPB packet filters. In the uplink, the UE uses FPB packet filter to classify UL PDUs into QoS flows of the same Unstructured PDU Session. + +Impacts to UPF: + +- In Rel. 15, in the downlink the UPF uses N6 tunnel header to classify DL PDUs into Unstructured PDU Session to be sent over N3 or N9 tunnel by using the mapping of one N6 tunnel header and one unstructured PDU Session. +- Using Solution 18, the UPF uses N6 tunnel header and FPB packet filters to classify PDUs into QoS flows of N3 or N9 interface; one N6 tunnel header may support multiple QoS flows of a single unstructured PDU session. + +## 6.19 Solution 19: 5GS UP Optimization for Infrequent Small Data Transmission + +### 6.19.1 Introduction + +This solution addresses the Key Issue 1: Support for infrequent small data transmission. This solution has commonality with RRC procedure for RRC-Inactive, which can resolve Key issue 2: Frequent small data communication. + +This solution is to optimize small data transmission for the UEs from CM-IDLE mode. It enables transfer of user plane data without need for the Service Request procedure. It is proposed to keep AS context in the NG-RAN including information the UPF connection and relevant QoS flow(s) to be used for the connection, even when UE moves into CM-IDLE. When UE resumes the connection, the NG-RAN uses the information to activate DRB, AS security and User Plane connectivity over N3 for the small data packet delivery to the UPF. The UPF also keeps N3 tunnel information for the PDU session to allow UL data transmission. + +This solution has following characteristics: + +- The AS context contains information related to the N3 tunnel, N2AP association, UE context and DRB context, AS security information, Header Compression context, and any necessary for RRC resume. The AS context is configured during PDU session establishment or registration. + +NOTE 1: The content of the AS Context is expected to be further confirmed by RAN WGs. + +- UE and NG-RAN may perform header compression for IP data based on the Header Compression context. +- The AS context is kept in NG-RAN and UE after the connection suspend procedure. +- AS security context is established between the NG-RAN and the UE. Therefore, existing AS security mechanism is re-used. +- NG-RAN performs Connection Suspend procedure to suspend the connection for the UE. NG-RAN indicates release cause set to RRC-suspend, and includes the resume ID which is stored by the UE. + +NOTE 2: RAN WGs are expected to confirm that RRC Connection Release procedure is used for connection suspend. + +- UE performs Connection Resume procedure using resume ID from CM-IDLE/RRC-IDLE state. So this solution is also applicable to MICO mode UE. + +NOTE 3: RAN WGs are expected to confirm whether to re-use Connection Resume procedure that is used for RRC-Inactive in NR. + +- After the UE performs RRC resume procedure, if NG-RAN determines if the AS context for the UE is valid, then the NG-RAN derives the AS security information, DRB, QoS flow and N3 tunnel information for the UE. The NG-RAN activates AS security, related DRB(s) and N3 tunnel(s). +- As NG-RAN keeps N3 Uplink Tunnel Endpoint ID in the AS context, user plane for uplink transmission is maintained. Also UPF keeps N3 Uplink Tunnel Endpoint ID to allow UL data. +- In case of serving NG-RAN is changed, new NG-RAN sends N3 Downlink TEID to SMF, and SMF updates this information to UPF so that path for downlink data transmission becomes available. +- In case of selective activation of UP connections during service request procedure or CN-initiated selective deactivation of UP connection (see TS 23.502 [7]), when the UE enters CM-IDLE via Connection Suspend procedure the AS context only contains the PDU session(s) that are active. When there is MO Data, the procedure is as follows: + - The UE performs Connection Resume procedure at RRC layer. The UE and NG-RAN resume the PDU sessions that were active during Connection suspend procedure. + - RRC layer notifies NAS the change of state to RRC connected and the PDU session(s) that are active. The NAS needs to be aware that all PDU session(s) that were active during Connection suspend procedure will be reactivated at the next RRC resume procedure, regardless of whether NAS needs this or not. If the NAS requires to further activate PDU session(s) that is/are not active, the UE initiates service request from CM connected, i.e. after Connection resume procedure is complete, to activate the necessary PDU session(s). + +NOTE 4: Given that IoT devices are not likely to have a large number of PDU sessions, to reduce power consumption and signalling it is recommended that selective activation/deactivation of UP connection(s) is not used and all PDU sessions are activated when the UE is in CM-CONNECTED. + +## 6.19.2 Functional Description + +### 6.19.2.1 General + +The AS context is stored in NG-RAN and it includes the relevant UPF or PDU session related information for the UE, which has been provided during PDU session establishment. During PDU Session establishment procedure, SMF provides N2 SM information which is stored in the NG-RAN in the AS Context. The UE and the NG-RAN use Resume ID to identify AS context. + +When NG-RAN suspends the RRC connection to the UE, NG-RAN notifies the AMF with the AS context to be kept in the AMF as transparent. If new serving NG-RAN fails to retrieve the AS context from the old NG-RAN, the NG-RAN asks to the AMF to retrieve the AS context stored in the AMF. + +When UE in CM-IDLE to send UL data or the UE receives paging message, the UE request to resume RRC Connection, if there is suspended AS context stored in the UE. During resume procedure, the NG-RAN derives necessary information to activate AS security, DRB and the path over N3 to the UPF. After RRC connection + +established, the UE can send UL data, and then the RAN forwards the data on the N3 interface. Given all information required to forward UL data is derived from the AS context for the UE, the NG-RAN does not have to signal to the AMF before sending UL data. The NG-RAN conditionally (e.g. if a DL tunnel is expected to be needed based on AS RAI) notifies AMF of UE's connection resume without depending on timing of UL data forwarding. + +### 6.19.2.2 Mobility + +Connected mode mobility is supported by existing handover procedures. + +When the UE requests RRC resume and if the NG-RAN doesn't have valid AS context to resume the UE's connection, the NG-RAN performs context fetch to retrieve the valid AS context that is kept in the last serving NG-RAN. + +If there is Xn connectivity, the new NG-RAN performs NGAP procedure for context fetch with the last serving NG-RAN. If there is no Xn connectivity, the new NG-RAN requests the context from the last serving NG-RAN. + +NOTE: For the case that the old NG-RAN is not within Xn connectivity area, RAN WG3 need to study whether indirect context retrieval via AMF or another NF is to be defined. + +If the NG-RAN node fails to fetch the valid AS context, the NG-RAN should reject resume and UE follows procedures that will be defined in stage-3. + +When the UE enters a new TA currently not part of the UE registration area, the UE requests RRC resume and will initiate a NAS registration update. The SMF shall subscribe UE location change to the AMF in order to determine UPF re-allocation and update N3 tunnel information. The SMF may subscribe change of serving NG-RAN node to the AMF in order to determine update of N3 tunnel information. + +### 6.19.2.3 Security + +This solution allows existing AS security mechanism as it is. + +## 6.19.3 Support of EPC Interworking + +Support and use of UP optimization is negotiated independently in EPC and 5GC. Existing interworking procedures can therefore be reused. + +## 6.19.4 Procedures + +### 6.19.4.1 PDU Session Establishment + + + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant AMF + participant UPF + participant SMF + participant PCF + participant UDM + participant DN + + UE->>AMF: 1. PDU Session Establishment Request + Note right of AMF: 2. SMF selection + AMF->>SMF: 3a. Namf_PDUSession_CreateSMContext Request + SMF->>UDM: 4a-4b. Registration/ Subscription retrieval/ Subscription for updates + UDM-->>SMF: + SMF->>AMF: 5. Namf_PDUSession_CreateSMContext Response + rect rgb(255, 255, 255) + Note over UE, DN: 6. PDU Session authentication/authorization + end + Note right of SMF: 7a. PCF selection + SMF->>PCF: 7b. Session Management Policy Establishment or Modification + PCF-->>SMF: + Note right of SMF: 8. UPF selection + SMF->>PCF: 9. Session Management Policy Modification + PCF-->>SMF: + SMF->>UPF: 10a. N4 Session Establishment/Modification Request + UPF-->>SMF: 10b. N4 Session Establishment/Modification Response + SMF->>AMF: 11. Namf_Communication_N1N2MessageTransfer + AMF->>NG-RAN: 12. N2 PDU Session Request (NAS msg) + NG-RAN->>UE: 13. AN-specific resource setup (PDU Session Establishment Accept) + UE->>NG-RAN: 14. N2 PDU Session Request Ack + Note over UE, UPF: First Uplink Data + AMF->>SMF: 15. Nsmf_PDUSession_UpdateSMContext Request + SMF->>UPF: 16a. N4 Session Modification Request + UPF-->>SMF: 16b. N4 Session Modification Response + SMF->>AMF: 17. Nsmf_PDUSession_UpdateSMContext Response + AMF->>SMF: 18. Nsmf_PDUSession_SMContextStatusNotify + SMF->>UE: 19. IPv6 Address Configuration + Note over UE, UPF: First Downlink Data + Note right of SMF: 20. Unsubscription / Deregistration + SMF-->>UDM: + +``` + +Sequence diagram for UE-requested PDU Session Establishment for 5GS UP Optimization. Lifelines: UE, NG-RAN, AMF, UPF, SMF, PCF, UDM, DN. The process involves 20 steps including request, selection, context creation, authentication, policy establishment, and final data transfer. + +**Figure 6.19.4-1: UE-requested PDU Session Establishment for 5GS UP Optimization** + +It is assumed that the UE has already registered in the 5G system. + +When UE requests PDU session establishment, the UE indicate to use 5GS UP optimization to the AMF, and the AMF indicates the request of 5GS UP optimization to the SMF. During PDU Session establishment procedure, the SMF informs NG-RAN of the established PDU session is used for 5GS UP Optimization. The SMF needs to know usage of 5GS UP optimization for the PDU session for keeping N3 UL TEID. The NG-RAN needs to know usage of 5GS UP optimization for determining to apply RRC suspend/resume and store the information for the PDU Session in the AS context. + +1. The UE provides an indication that it wants to use 5GS UP Optimization (e.g., use of Resume/Suspend procedure) to the AMF. + +NOTE 1: It is assumed that NG-RAN broadcasts system information will indicate the support of resume/suspend. + +2. AMF selects an SMF that supports the use of 5GS UP Optimization. + +3. The AMF indicates the support of 5GS UP Optimization in the Nsmf\_PDUSession\_CreateSMContext Request operation. Then the SMF considers this PDU session establishment message is for 5GS UP Optimization, and can determine the UP connection for this PDU session should not be de-activated. + +The AMF provides the registration area of the UE to the SMF in order to assist that the SMF selects the UPF which can be maintained while UE mobility happens within the registration area. + +NOTE 2: It is assumed UPF would not be changed in the registration area. If UE moves out of the registration area, UPF can be re-allocated during mobility registration procedure, by invoking Nsmf\_PDUSession\_UpdateSMContext. + +... + +8. SMF selects a UPF that supports the 5GS UP optimization. + +... + +11. SMF includes the indication of 5GS UP Optimization in N2 SM message to the NG-RAN so that NG-RAN can decide to perform RRC suspend procedure to the UE, and to store information for the PDU session in the AS context. + +... + +#### 6.19.4.2 UL data transmission from CM-IDLE + +The following figure shows an example of how MO small data packet is delivered from the UE. + + + +``` + +sequenceDiagram + participant UE + participant RAN + participant AMF + participant SMF + participant UPF + + Note left of UE: ... + UE->>RAN: 1a. RRC Resume Req + RAN-->>AMF: Context Fetch + UE->>RAN: UL data + RAN->>AMF: 2. N2AP: Connection Resume + AMF->>SMF: 3. Nsmf_PDUSession_UpdateSMContext Req + SMF->>UPF: 4. N4 Session Modification + UPF-->>SMF: DL data + SMF->>AMF: 5. Nsmf_PDUSession_UpdateSMContext Resp + AMF->>RAN: 6. N2AP: Connection Resume + RAN->>UE: 1b. RRC Resume Resp + Note right of UE: ... + +``` + +Sequence diagram illustrating MO data transmission using 5GS UP Optimization. The diagram shows interactions between UE, RAN, AMF, SMF, and UPF. The process starts with the UE sending an RRC Resume Request to the RAN. The RAN performs a Context Fetch with the AMF. The UE then sends UL data to the RAN. The RAN sends an N2AP: Connection Resume message to the AMF. The AMF sends an Nsmf\_PDUSession\_UpdateSMContext Req to the SMF. The SMF sends an N4 Session Modification to the UPF. The UPF sends DL data to the SMF. The SMF sends an Nsmf\_PDUSession\_UpdateSMContext Resp to the AMF. The AMF sends an N2AP: Connection Resume message to the RAN. Finally, the RAN sends an RRC Resume Response to the UE. + +Figure 6.19.4.2-1: MO data Transmission using 5GS UP Optimization + +- 1a/1b. The UE triggers RRC Connection Resume procedure including Resume ID which identifies the AS context stored in the NG-RAN. Using the valid AS Context for the UE, the NG-RAN performs AS security check, DRB is established, and NG-RAN enables N3 UL TEID for data delivery. + +If the Resume ID indicates another NG-RAN within Xn connectivity, i.e. old NG-RAN, the NG-RAN performs direct context fetch via Xn. + +NOTE 1: For the case that the old NG-RAN is not within Xn connectivity, RAN WG3 need to study whether indirect context fetch via AMF or another network function is to be defined. + +If NG-RAN fails to get valid AS context, it rejects RRC Connection Resume with an appropriate cause, so that the UE performs the related NAS procedure. + +UE can send UL data right after successful RRC Connection Resume procedure. The NG-RAN forwards the UL data received from the UE to the UPF by using N3 UL TEID in the AS context. + +2. If NG-RAN expect no DL data e.g. based on AS RAI indicating single packet or based on the Expected UE Behavior (with Release Assistance Information/Traffic Pattern/Traffic Profile available in the UE context in NG-RAN) indicating single packet (and the AS RAI is not present), NG-RAN immediately suspends the RRC connection and this procedure stops here. If NG-RAN expect DL data, the NG-RAN notifies the AMF that UE connection has been resumed by sending N2AP message which includes N2 SM info and PDU Session ID. The NG-RAN includes N3 DL TEID for the PDU session in the N2 SM message. +3. The AMF enters CM-Connected state. The AMF identifies the UE context, and forwards N2 SM message to the SMF. +4. The SMF identifies the UE and the PDU session. If there is N2 SM message in the Nsmf\_PDUSession\_UpdateSMcontext request message, the SMF performs N4 Session Modification to update N3 DL TEID to the UPF. + +If there is DL data arrived for the UE, the UPF forwards the data to the NG-RAN using N3 DL TEID. + +5. The SMF sends Nsmf\_PDUSession\_UpdateSMcontext response. If there is any change for the PDU session e.g., in case of the QoS targets cannot be fulfilled for a QFI, the SMF informs this information in the N2 SM information. +6. The AMF acknowledges the connection resume to the NG-RAN. If there is change of PDU session as received in N2 SM message from the SMF, NG-RAN can perform RRC reconfiguration. The AMF shall also provide the indication of single or dual packet information to NG-RAN (e.g. by including the Expected UE Behavior) in case the NG-RAN does not already have this information). + +NOTE 2: Handling of pending DL data/signalling for the UE resuming RRC connection with AS RAI will be discussed during the normative phase, if this solution is agreed for conclusions. + +#### 6.19.4.2b UL data transmission from CM-IDLE with Early Data Transmission + +The following figure shows a single MO small data delivered from the UE using Early Data Transmission. + +NOTE 1: For Early Data Transmission with dual or multiple packet transmission, or unknown number of packets, the procedure continues after step 1a as in previous clause 6.19.4.2 except that first UL data packet does not require a specific UL message from UE to RAN. + + + +``` + +sequenceDiagram + participant UE + participant RAN + participant AMF + participant SMF + participant UPF + Note over UE: 0: UL data + UE->>RAN: PRACH + RACH Response + UE->>RAN: 1a. RRC Connection Resume Req w EDT + RAN->>UPF: 2. UL data + RAN->>UE: 1b. RRC Connection Release w suspend ind + Note over UE: 3: Suspended + Note over RAN: 3: Suspended + +``` + +Sequence diagram for Single MO data Transmission using 5GS UP Optimization and EDT. The diagram shows interactions between UE, RAN, AMF, SMF, and UPF. The sequence starts with the UE sending '0: UL data' to the RAN. The RAN responds with 'PRACH + RACH Response'. The UE then sends '1a. RRC Connection Resume Req w EDT' to the RAN, which forwards '2. UL data' to the UPF. The RAN then sends '1b. RRC Connection Release w suspend ind' to the UE. Finally, both the UE and RAN enter a '3: Suspended' state. + +**Figure 6.19.4.2b-1: Single MO data Transmission using 5GS UP Optimization and EDT** + +- 1a. The UE sends RRC Connection Resume Request with the UL data included as Early Data Transmission with the RRC Connection Resume Request. Using the valid AS Context for the UE, the NG-RAN enables N3 UL TEID for data delivery. +- 1b. Either based on the AS Release Assistance Indication (RAI) included by the UE in step 1a indicating single packet transmission, or if the Expected UE Behavior is available and stored in the UE context in RAN (with a Release Assistance Information present) indicating single packet (and the AS RAI is not present in step 1a), then NG-RAN immediately suspends the RRC connection (to minimize UE power consumption). +2. The NG-RAN forwards the UL data received from the UE to the UPF by using N3 UL TEID in the AS context. +3. UE and RAN remain suspended. + +NOTE 2: Handling of pending DL data/signalling for the UE resuming RRC connection with AS RAI will be discussed during the normative phase, if this solution is agreed for conclusions. + +### 6.19.4.3 DL data transmission + +The following figure shows an example of how MT small data packet is delivered to the UE in CM-IDLE. + + + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant AMF + participant SMF + participant UPF + + Note left of UE: CM-IDLE + UPF->>SMF: 1. Data Notification + SMF->>AMF: 2a. Namf_Comm_N1N2MessageTransfer Req + AMF-->>SMF: 2b. Namf_Comm_N1N2MessageTransfer Res + AMF->>NG-RAN: 3. Paging + NG-RAN->>UE: 4. Paging + UE->>NG-RAN: 5a. RRC Resume Req. + Note right of NG-RAN: Context Fetch + NG-RAN-->>AMF: Context Fetch + UE->>NG-RAN: 5b. RRC Resume Res. + NG-RAN->>AMF: 6. N2AP: Connection Resume + AMF->>SMF: 7. Nsmf_PDUSession_UpdateSMContext req + SMF->>UPF: 8. N4 Session Modification + UPF->>NG-RAN: DL data + NG-RAN->>UE: DL data + SMF->>AMF: 9. Nsmf_PDUSession_UpdateSMContext res + AMF->>NG-RAN: 10. N2AP: Connection Resume + +``` + +Sequence diagram illustrating MT data Transmission using 5GS UP Optimization. The diagram shows interactions between UE, NG-RAN, AMF, SMF, and UPF. The sequence starts with the UE in CM-IDLE state. The UPF sends a Data Notification to the SMF. The SMF sends a Namf\_Comm\_N1N2MessageTransfer Req to the AMF. The AMF responds with a Namf\_Comm\_N1N2MessageTransfer Res. The AMF sends a Paging message to the NG-RAN. The NG-RAN performs paging to the UE. The UE triggers an RRC Resume procedure. The NG-RAN performs a Context Fetch from the AMF. The NG-RAN sends an N2AP: Connection Resume message to the AMF. The AMF sends an Nsmf\_PDUSession\_UpdateSMContext req to the SMF. The SMF performs an N4 Session Modification to the UPF. The UPF sends DL data to the NG-RAN. The NG-RAN sends DL data to the UE. The SMF sends an Nsmf\_PDUSession\_UpdateSMContext res to the AMF. The AMF sends an N2AP: Connection Resume message to the NG-RAN. + +**Figure 6.19.4.3-1: MT data Transmission using 5GS UP Optimization** + +1. At arrival of DL data, UPF notifies to SMF. +- 2a. The SMF determines the AMF serving the UE, and invokes Namf\_Comm\_N1N2MessageTransfer to the AMF including PDU Session ID. +- 2b. The AMF responds to the SMF. +3. The AMF send a paging message to the NG-RAN. +4. The NG-RAN performs paging to the UE. +5. The UE triggers RRC Connection Resume procedure including Resume ID which identifies the stored AS context in the NG-RAN. Using the valid AS Context for the UE, the NG-RAN performs security check, DRB is established, and NG-RAN enables N3 DL TEID for data delivery. + +If the Resume ID indicates another NG-RAN within Xn connectivity, i.e. old NG-RAN, the NG-RAN performs direct context fetch via Xn. + +NOTE: For the case that the old NG-RAN is not within Xn connectivity, RAN WG3 need to study whether indirect context fetch via AMF or another network function is to be defined. + +If the NG-RAN fails to retrieve valid AS context, it rejects the RRC connection Resume with an appropriate cause, so that the UE performs Service Request. + +6. The NG-RAN notifies the AMF that UE connection has been resumed by sending N2AP message which includes N2 SM message and PDU Session ID. The NG-RAN includes N3 DL TEID for the PDU session in the N2 SM message. +7. The AMF enters CM-Connected state after receiving the N2AP message. The AMF determines the SMF based on the PDU Session ID received from step 2a and 6, and the AMF sends N2 SM message to the SMF. +8. The SMF identifies the UE and the PDU session. Based on the received N2 SM message, the SMF performs N4 Session Modification to update N3 DL TEID to the UPF. The UPF forwards the data to the NG-RAN using N3 DL TEID. + +9. The SMF sends Nsmf\_PDUSession\_UpdateSMContext response. +10. The AMF acknowledges the connection resume to the NG-RAN. + +#### 6.19.4.4 Connection Suspend procedure + +This procedure is used by the NG-RAN to suspend the connection if 5GS UP Optimization is supported. + + + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant AMF + participant SMF + participant UPF + Note left of NG-RAN: 1. UE Context suspend request + NG-RAN->>AMF: 1. UE Context suspend request + Note right of AMF: 2. Nsmf_PDUSession_UpdateSMContext req + AMF->>SMF: 2. Nsmf_PDUSession_UpdateSMContext req + Note right of SMF: 3. N4 Session Modification + SMF->>UPF: 3. N4 Session Modification + Note right of SMF: 4. Nsmf_PDUSession_UpdateSMContext res + SMF->>AMF: 4. Nsmf_PDUSession_UpdateSMContext res + Note right of AMF: 5. UE Context suspend response + AMF->>NG-RAN: 5. UE Context suspend response + Note right of NG-RAN: 6. RRC Connection Suspend + NG-RAN->>UE: 6. RRC Connection Suspend + +``` + +Sequence diagram of the Connection Suspend procedure. The diagram shows five lifelines: UE, NG-RAN, AMF, SMF, and UPF. The sequence of messages is: 1. UE Context suspend request (NG-RAN to AMF); 2. Nsmf\_PDUSession\_UpdateSMContext req (AMF to SMF); 3. N4 Session Modification (SMF to UPF); 4. Nsmf\_PDUSession\_UpdateSMContext res (SMF to AMF); 5. UE Context suspend response (AMF to NG-RAN); 6. RRC Connection Suspend (NG-RAN to UE). + +**Figure 6.19.4.4-1: Connection Suspend procedure** + +1. The NG-RAN initiates the Connection Suspend procedure to the AMF. In the N2 message, the NG-RAN includes all PDU Session ID(s) that have been activated. +2. The AMF sends Nsmf\_PDUSession\_UpdateSMContext Request to inform connection suspend of the PDU Session, based on the PDU session ID(s) in step 1. +3. The SMF determines to disable N3 DL TEID for the PDU session as UE goes to RRC suspended while SMF keeps N3 UL TEID to allow uplink data transmission when UE resumes the connection. The SMF performs N4 Session Modification procedure with UPF to disable N3 DL TEID. The UPF enables Downlink Data Notification. +4. The SMF sends Nsmf\_PDUSession\_UpdateSMContext Response to the AMF. +5. The AMF sends UE Context suspend response to the NG-RAN to successfully complete the connection suspend procedure. +6. The NG-RAN sends RRC message to suspend the RRC Connection toward the UE with including the Resume ID to be used for identifying the AS context for the RRC connection resume. The UE keeps the AS context. + +#### 6.19.4.5 CN-initiated UP Deactivation procedure + +For UE in CM-CONNECTED with multiple active PDU sessions, when SMF decides deactivation of a PDU session for the UE, it may decide also whether UP optimization will be applied for the PDU session based on triggering condition for PDU session deactivation (e.g. UPF reports inactivity for the PDU session). When the SMF decides to apply UP optimization for the PDU session which will be deactivated, it informs RAN to store corresponding AS context for 5G UP optimization support when UE in CM-IDLE tries to transmit UL data. + +**Editor's note:** It is FFS whether selective PDU Session deactivation needs to be applied for CIOT in 5G System. + +**Editor's note:** The need for CN-initiated UP Deactivation procedure will be separately evaluated and concluded from other part of the solution 19. + + + +``` + +sequenceDiagram + participant UE + participant RAN + participant AMF + participant SMF + participant UPF + + Note over UE, UPF: 0. UE has established the PDU session with 5GS UP Optimization + + rect rgb(240, 240, 240) + Note right of SMF: 1. SMF determines PDU session +deactivation and allowing 5G UP +optimization of the PDU session + end + + SMF->>UPF: 2. N4 session modification + UPF-->>SMF: + SMF->>AMF: 3. Namf_Communication_ +N1N2Message Transfer +(N2 Resource Release) + AMF->>RAN: 4. N2 PDU Session +Resource Release +Command + RAN-->UE: 5. RRC Reconfiguration + RAN->>AMF: 6. N2 PDU Session +Resource Release Response + AMF->>SMF: 7. Nsmf_PDUSession_ +UpdateSMContext + + Note over UE, UPF: + + UE->>RAN: 8. RRC Resume + rect rgb(255, 255, 255) + Note over RAN, AMF: Context Fetch + end + RAN->>UE: 9. RRC Resume + + UE->>RAN: UL data + RAN->>UPF: UL data + +``` + +Sequence diagram of CN-initiated UP Deactivation procedure involving UE, RAN, AMF, SMF, and UPF. The diagram shows steps 0 through 9, including N4 session modification, N2 resource release, RRC reconfiguration, and UL data flow. + +**Figure 6.19.4.5-1: CN-initiated UP Deactivation procedure** + +0. It assumes that UE established multiple PDU sessions with 5GS UP Optimization which includes uplink session. +1. During UE in CM-CONNECTED state, the SMF determines that UP connection of the PDU session needs to be deactivated. And SMF also determines whether whole UP connection will be deactivated (for example, for the case that UE is reported as out of allowed area or out of LADN service area) or uplink UP connection will be maintained for 5G UP optimization (for example, UPF's report of inactivity case). +2. The SMF performs N4 Session Modification procedure with UPF to disable N3 DL and UL TEIDs or disable only N3 DL TEID while keeping N3 UL TEID. +3. The SMF may send an N11 message containing N2 SM Session Release Request to release the (R)AN resources associated with the PDU session and may include indication of 5G UP optimization. +4. The AMF forwards the N2 SM Session Release Request to the RAN. +5. RAN releases AS resource for the PDU session as indicated N2 SM Session Release Request. When 5G UP optimization is indicated in the message, RAN stores AS context of the PDU session for 5G UP optimization support when UE transmits UL data from CM-IDLE. The RAN may issue NG-RAN specific signalling (e.g. RRC connection reconfiguration) to the UE. After deactivation of the PDU Session, if the PDU session needs to be activated, UE and 5G CN will follow Service Request procedure as specified in subclause 4.2.3 of TS 23.502 [7] until UE transits to CM-IDLE state. +6. The RAN acknowledges the N2 Session Release Request by sending an N2 PDU Session Response to the AMF. +7. The AMF sends an N11 message to acknowledge the SM request received in step 4. +8. After UE entered CM-IDLE state through Connection Suspend procedure specified in subclause 6.19.4.4, UE may trigger RRC Resume procedure including Resume ID for uplink data transmission. +9. RAN may respond RRC Resume request with updated AS context including the AS context saved at step 5 in addition to the AS context saved during Connection Suspend procedure specified in subclause 6.19.4.4. + +10. UE may transmit uplink data according to the AS context after receiving response from RAN at step 9. And other following procedure as specified in subclause 6.19.4.2 will proceed. + +## 6.19.5 Impacts on existing entities and interfaces + +UE: + +- Support of connection suspend and resume procedures. +- Storing the relevant AS information at transition to CM-IDLE. + +RAN: + +- Support of connection suspend and resume procedures. +- Storing the relevant AS information at transition to CM-IDLE. + +AMF: + +- Support of connection suspend and resume procedures. + +The following additional impact results from the CN-initiated UP Deactivation procedure in clause 6.19.4.5: + +UE: + +- Support for reactivation of PDU session that was previously deactivated during connection resume procedure. + +RAN: + +- Support keeping AS context for PDU sessions that have been deactivated. + +SMF: + +- Decision whether to apply 5G UP optimization for the deactivated PDU session; protocol impact to include indication of 5G UP optimization to AMF. + +## 6.19.6 Evaluation + +This solution introduces 5G UP optimization similar to EPS UP optimization, i.e. enables the RAN to suspend the UE's RRC connection, to store the AS context in the RAN and to resume the RRC connection when small data needs to be sent (after fetching the AS context from a different RAN node if needed). + +In comparison to EPS UP optimization an additional enhancement has been proposed: avoiding to resume the RRC connection if the UE sends a single UL packet only (indicated by AS Release Assistance Indication). As the UE is in CM-IDLE state when its RRC connection has been suspended, the solution can be easily combined with eDRX with long sleep cycles and the related HLCom mechanisms for CM-IDLE. + +The key benefit of the solution is that the UE can send data from CM-IDLE without having to perform a full service request. This saves over-the-air signaling since the RRC connection can be resumed and the already negotiated AS security context can be reused. Since the UPF N3 information is also stored in the AS context, another benefit is that small data sent by the UE can be forwarded to the UE immediately. The additional enhancement proposed in comparison to EPS UP optimization, namely to avoid resuming the RRC connection if the UE sends a single UL packet only (indicated by AS Release Assistance Indication), has the additional benefit that N2, N11 and N4 signaling for re-establishing an N3 tunnel can be completely avoided. The solution has impact to UE, RAN and CN. + +With respect to the CN-initiated UP Deactivation procedure in clause 6.19.4.5: Storing the AS context for deactivated PDU sessions may save signaling in case the UE may want to send UL data from CM-IDLE (with suspended RRC connection) for a PDU session that was deactivated before the RRC connection was suspended. However, this proposal has additional system impact to UE, RAN and SMF. These impacts do not appear justified given that CIoT devices are unlikely to have many PDU sessions active in parallel. Therefore it is recommended to not pursue the part of the solution described in clause 6.19.4.5. + +## 6.20 Solution 20: NIDD API support by SMF for infrequent small data transfer via NAS-SM + +### 6.20.1 Introduction + +#### 6.20.1.1 General + +This solution applies to Key issue 1 (support for infrequent small data transmission), builds on top of solution 1 (as documented in clause 6.1) and adds support for the NIDD API to the SMF. + +#### 6.20.1.2 Architecture reference models + +##### 6.20.1.2.1 General + +In addition to the architecture reference models in clause 6.1.1.2 the following clauses provide the reference models to support the NIDD API for small data transfer via NAS-SM. + +##### 6.20.1.2.2 Non-roaming reference architecture + + + +``` + +graph TD + UE[UE] -- N1 --> AMF[AMF] + RAN[RAN] -- N2 --> AMF + AMF -- N12 --> AUSF[AUSF] + AMF -- N8 --> UDM[UDM] + AMF -- N11 --> SMF[SMF] + AUSF -- N13 --> UDM + UDM -- N10 --> SMF + SMF -- "Nm (NIDD API)" --> SCSAS[SCS/AS] + +``` + +The diagram illustrates the non-roaming architecture. A User Equipment (UE) is connected to a Radio Access Network (RAN), which in turn connects to an Access and Management Function (AMF) via the N2 interface. The UE also has a direct connection to the AMF via the N1 interface. The AMF is connected to an AUSF via the N12 interface and to a UDM via the N8 interface. The AUSF is connected to the UDM via the N13 interface. The AMF is also connected to a Session Management Function (SMF) via the N11 interface. The UDM is connected to the SMF via the N10 interface. Finally, the SMF is connected to a Service Capability Server/Application Server (SCS/AS) via the Nm (NIDD API) interface. + +Figure 6.20.1.2.2-1: Architecture for small data delivery via NAS and NIDD API (non-roaming). + +Figure 6.20.1.2.2-1: Architecture for small data delivery via NAS and NIDD API (non-roaming) + +##### 6.20.1.2.3 Roaming reference architectures + + + +``` + +graph TD + UE[UE] -- N1 --> AMF[AMF] + RAN[RAN] -- N2 --> AMF + AMF -- N12 --> AUSF[AUSF] + AMF -- N8 --> UDM[UDM] + AMF -- N11 --> VSMF[V-SMF] + AUSF -- N13 --> UDM + UDM -- N10 --> HSMF[H-SMF] + VSMF -- N16 --> HSMF + HSMF -- "Nm (NIDD API)" --> SCSAS[SCS/AS] + +``` + +The diagram illustrates the home-routed roaming architecture. It is divided into two domains by a vertical dashed line: VPLMN (Visited PLMN) on the left and HPLMN (Home PLMN) on the right. In the VPLMN, a UE is connected to a RAN, which connects to an AMF via the N2 interface. The UE also has a direct connection to the AMF via the N1 interface. The AMF is connected to an AUSF via the N12 interface and to a UDM via the N8 interface. The AMF is also connected to a V-SMF via the N11 interface. In the HPLMN, the AUSF is connected to the UDM via the N13 interface. The UDM is connected to an H-SMF via the N10 interface. The V-SMF is connected to the H-SMF via the N16 interface. Finally, the H-SMF is connected to a Service Capability Server/Application Server (SCS/AS) via the Nm (NIDD API) interface. + +Figure 6.20.1.2.3-1: Architecture for small data delivery via NAS and NIDD API (home-routed roaming). + +Figure 6.20.1.2.3-1: Architecture for small data delivery via NAS and NIDD API (home-routed roaming) + +### 6.20.2 Functional Description + +In addition to clause 6.1.2, the following principles apply: + +- Support of NIDD API: + - The NIDD API is supported for PDU sessions of type unstructured. + - The SMF supports the NIDD API towards the SCS/AS for non-roaming scenarios. In case of home-routed roaming, the H-SMF supports the NIDD API. + - Whether or not the NIDD API shall be invoked for a PDU session is determined by a per DNN per S-NSSAI Invoke NIDD API indication in the subscription. + - If the subscription includes an Invoke NIDD API indication and an SMF ID for the S-NSSAI / DNN requested by the UE, then the AMF selects that SMF for the small data PDU session. + - The SMF ID for a given S-NSSAI / DNN in the subscription can be updated by means of the NIDD configuration procedure. + - The SMF can provide a Maximum Packet Size for unstructured PDU Session to the UE via PCO. + - The SMF performs buffering for unstructured DL data received via the NIDD API while the UE is unreachable. + - SMF subscribes to UE reachability event reporting from the AMF. AMF informs SMF how long a UE is expected to be unreachable (if known to the AMF). + +**Editor's note:** Interactions with CAPIF are FFS. + +## 6.20.3 Support of EPC interworking + +EPC interworking is enabled by the principles documented in clause 6.1.3 with the following differences: + +- NIDD API is terminated on a co-located SMF (capable of small data transfer via NAS) and SCEF, referred to as SMF+SCEF. +- Idle-mode mobility from 5GS to EPS is performed as per the procedure described in TS 23.502 [7] clause 4.11.1.3.2 with the following differences: + - Step 5b: SMF+SCEF maps the PDU session for Data over NAS-SM to an SCEF PDN Connection and sets the Control Plane Only PDN Connection Indication. +- Idle-mode mobility from to EPS to 5GS is performed as per the procedure described in TS 23.502 [7] clause 4.11.1.3.3 with the following differences: + - AMF indicates support of CIoT Optimizations when requesting the UE context from the MME via N26; + - for a PDN connection for which Control Plane Only PDN Connection Indication is set: + - (H-)SMF does not select a (H-)UPF; + - in the case of home-routed roaming: + - Step 14: the AMF selects a V-SMF supporting small data over NAS-SM; + - Step 14: V-SMF does not select a V-UPF. + +**Editor's note:** How the same IP address can be used with SCEF is FFS. + +## 6.20.4 Procedures + +### 6.20.4.1 PDU Session Establishment (non-roaming) + +This procedure replaces the PDU session establishment procedure described in clause 6.1.4.1 for non-roaming scenarios. It takes the PDU Session Establishment procedure as described in TS 23.502 [7], clause 4.3.2.2.1 as the baseline. + + + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant AMF + participant SMF + participant UPF + participant PCF + participant UDM + + Note left of UE: 1. PDU Session Establishment Request (DNN, S-NSSAI, "Data over NAS-SM requested") + UE->>AMF: 1. PDU Session Establishment Request (DNN, S-NSSAI, "Data over NAS-SM requested") + Note right of AMF: 2. SMF selection + AMF->>SMF: 3. Nsmf_PDUSession_CreateSMContext Request/Response + SMF->>UDM: 4. Registration/subscription retrieval/subscribe for updates + Note right of SMF: 5. UPF selection + SMF->>UPF: 6. N4 Session Establishment/Modification SMF provides N4 data transfer info + Note right of SMF: 7. Nnamf_Communication_N1N2MessageTransfer + SMF->>AMF: 7. Nnamf_Communication_N1N2MessageTransfer + Note left of AMF: 8. NAS transport(PDU session ID, SM: PDU session establishment response) + AMF->>UE: 8. NAS transport(PDU session ID, SM: PDU session establishment response) + +``` + +Sequence diagram of PDU Session Establishment enabling Data over NAS-SM and NAS API. Lifelines: UE, NG-RAN, AMF, SMF, UPF, PCF, UDM. The process involves 8 steps: 1. UE sends PDU Session Establishment Request to AMF; 2. AMF performs SMF selection; 3. AMF sends Nsmf\_PDUSession\_CreateSMContext Request/Response to SMF; 4. SMF registers with UDM; 5. SMF performs UPF selection; 6. SMF sends N4 Session Establishment/Modification to UPF; 7. SMF sends Nnamf\_Communication\_N1N2MessageTransfer to AMF; 8. AMF sends NAS transport response to UE. + +**Figure 6.20.4.1-1: PDU Session Establishment enabling Data over NAS-SM and NAS API** + +1. The UE sends a PDU session establishment request message as SM payload of a NAS transport message. The NAS transport message contains PDU session ID and a "Data transfer over NAS-SM preference" indication along with other regular information e.g. DNN, S-NSSAI, etc. if applicable. +2. If the subscription includes an Invoke NIDD API indication and an SMF ID for the DNN and S-NSSAI requested by the UE, then the AMF selects the SMF identified by the SMF ID. + +If the subscription includes an Invoke NIDD API indication but no SMF ID for the DNN and S-NSSAI requested by the UE, then the AMF rejects the PDU session establishment request. + +Otherwise, the AMF takes the received "Data transfer over NAS-SM requested" indication received from the UE into account to select an SMF that supports Data over NAS-SM if available for the requested DNN, and S-NSSAI if it applies. The AMF stores the association of the PDU Session ID and the selected SMF ID in the UE context. + +3. The AMF forwards the Data transfer over NAS-SM requested indication to the SMF by invoking Nsmf\_PDUSession\_CreateSMContext request. The SMF replies with an Nsmf\_PDUSession\_CreateSMContext Response. +4. The SMF registers with the UDM and retrieves the Session Management Subscription data for the corresponding SUPI, DNN and S-NSSAI). + +If the subscription includes an Invoke NIDD API indication for the DNN and S-NSSAI requested by the UE and if an SCS/AS has performed the NIDD Configuration procedure (see clause 6.20.4.5) with the SMF for this UE, then the procedure continues with step 7. + +If the subscription includes an Invoke NIDD API indication for the DNN and S-NSSAI requested by the UE but no SCS/AS has performed the NIDD Configuration procedure with the SMF for this UE, then the SMF rejects the PDU session establishment with an appropriate cause code. + +**Editor's note:** Need for support and procedures for Secondary authorization/authentication are FFS. + +5. [Conditional] The SMF selects a UPF. +6. [Conditional] The SMF configures the UPF for data transfer via N4. +7. The SMF sends a PDU Session Establishment Accept providing indication that Data Over NAS-SM is enabled for this PDU session without including the N2 SM container. +8. The AMF forwards the NAS message to the UE. + +## 6.20.4.2 PDU Session Establishment (home-routed roaming) + +This procedure takes the PDU Session Establishment procedure as described in TS 23.502 [7], subclause 4.3.2.2.2 as the baseline. + + + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant AMF + participant V-SMF + participant V-UPF + participant H-SMF + participant H-UPF + participant PCF + participant UDM + + Note right of AMF: 2. SMF selection + Note right of V-SMF: 4. V-UPF selection + Note right of V-SMF: 5. N4 Session Establishment/Modification +V-SMF provides N4 data transfer info. + Note right of H-SMF: 8. V-UPF selection + Note right of H-SMF: 9. N4 Session Establishment/Modification + + UE->>AMF: 1. PDU Session Establishment Request +(DNN, S-NSSAI, "Data over NAS-SM requested") + AMF->>V-SMF: 3. Nsmf_PDU Session_Create SMContext Request/Response + V-SMF->>H-SMF: 6. Nsmf_PDU Session_Create SMContext Request + H-SMF->>UDM: 7. Registration/subscription retrieval/subscribe for updates + H-SMF->>V-SMF: 10. Nsmf_PDU Session_Create SMContext Response + V-SMF->>AMF: 11. Nsmf_Communication N1N2MessageTransfer + AMF->>UE: 12. NAS transport(PDU session ID, SM: PDU session establishment response) + +``` + +Sequence diagram for PDU Session Establishment (home-routed roaming) showing interactions between UE, NG-RAN, AMF, V-SMF, V-UPF, H-SMF, H-UPF, PCF, and UDM. + +**Figure 6.20.4.2-1: PDU Session Establishment enabling Data over NAS-SM and NAS API** + +- The UE sends a PDU session establishment request message as SM payload of a NAS transport message. The NAS transport message contains PDU session ID and a "Data transfer over NAS-SM preference" indication along with other regular information e.g. DNN, S-NSSAI, etc. if applicable. +- If the subscription includes an Invoke NIDD API indication and an SMF ID for the DNN and S-NSSAI requested by the UE, then the AMF selects the SMF identified by the SMF ID. If the subscription includes an Invoke NIDD API indication but no SMF ID for the DNN and S-NSSAI requested by the UE, then the AMF rejects the PDU session establishment request. Otherwise, the AMF takes the received "Data transfer over NAS-SM requested" indication received from the UE into account to select an SMF that supports Data over NAS-SM if available for the requested DNN, and S-NSSAI if it applies. The AMF stores the association of the PDU Session ID and the selected SMF ID in the UE context. +- The AMF forwards the Data transfer over NAS-SM requested indication and the Invoke NIDD API indication (if included in the subscription) to the SMF by invoking Nsmf\_PDUSession\_CreateSMContext request. The SMF replies with an Nsmf\_PDUSession\_CreateSMContext Response. +- [Conditional] If the V-SMF has not received the Invoke NIDD API indication, the SMF selects a UPF. +- [Conditional] If the SMF has not received the Invoke NIDD API indication, the SMF configures the UPF for data transfer via N4. +- The V-SMF sends the Nsmf\_PDUSession\_CreateSMContext request including the Data transfer over NAS-SM requested indication to the H-SMF. If the V-SMF has configured a V-UPF in step 5, the V-SMF includes V-CN-Tunnel-Info towards the H-SMF. + +**Editor's note:** Need for support and procedures for Secondary authorization/authentication are FFS. + +7. The SMF registers with the UDM and retrieves the Session Management Subscription data for the corresponding SUPI, DNN and S-NSSAI). If the subscription includes an Invoke NIDD API indication for the DNN and S-NSSAI requested by the UE and if an SCS/AS has performed the NIDD Configuration procedure (see clause 6.20.4.5) with the SMF for this UE, then the procedure continues with step 10. If the subscription includes an Invoke NIDD API indication for the DNN and S-NSSAI requested by the UE but no SCS/AS has performed the NIDD Configuration procedure with the SMF for this UE, then the SMF rejects the PDU session establishment with an appropriate cause code. +8. [Conditional] If the subscription does not include an Invoke NIDD API indication for the DNN and S-NSSAI requested by the UE, then the H-SMF selects a H-UPF. +9. [Conditional] If the subscription does not include an Invoke NIDD API indication for the DNN and S-NSSAI requested by the UE, then the H-SMF configures the H-UPF. +10. The H-SMF sends a Nsmf\_PDUSession\_CreateSMContext response to the V-SMF including an indication that Data Over NAS-SM is enabled for this PDU session without including the N2 SM container. If the H-SMF has selected and configured a H-UPF in steps 8 and 9, then the H-SMF also includes H-CN Tunnel Info. +11. The SMF sends a PDU Session Establishment Accept providing an indication that Data Over NAS-SM is enabled for this PDU session without including the N2 SM container. +12. The AMF forwards the NAS message to the UE. + +### 6.20.4.3 Mobile Originated Data Transport via NAS-SM and NIDD API + + + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant AMF + participant V-SMF + participant HSMF as (H-)SMF + participant SCS/AS + + Note right of V-SMF: Home-routed roaming + UE->>AMF: 1. Mobile Originated Data Transport via NAS- SM and N6 (clause 6.1.4.2, steps 0-3) + AMF->>V-SMF: 2. N11/N16 message (SM data transfer, PDU session ID) + V-SMF->>HSMF: + HSMF->>SCS/AS: 3. MO NIDD indication + SCS/AS-->>HSMF: 4. MO NIDD acknowledgement + alt (A) DL data available: Mobile Terminated NIDD procedure (clause 6.X.4.4) + alt (B) No further DL data available: Mobile Originated Data Transport via NAS- SM and N6 (clause 6.1.4.2, steps 11-14) + +``` + +Sequence diagram of the Mobile Originated NIDD procedure. The diagram shows interactions between UE, NG-RAN, AMF, V-SMF, (H-)SMF, and SCS/AS. A shaded area indicates 'Home-routed roaming' involving the V-SMF and (H-)SMF. The procedure starts with data transport from UE to AMF, then to V-SMF, then to (H-)SMF via N11/N16. (H-)SMF sends an indication to SCS/AS and receives an acknowledgement. Two conditional paths are shown: (A) if DL data is available, a Mobile Terminated NIDD procedure occurs; (B) if no further DL data is available, data transport continues from UE via AMF, V-SMF, and (H-)SMF. + +Figure 6.20.4.3-1: Mobile Originated NIDD procedure + +1. Steps 1-3 of Figure 6.1.4.2-1. +2. AMF forwards the data to the (V-)SMF handling the PDU session identified by the PDU session ID contained in the NAS transport message. In case of home-routed roaming, the V-SMF forwards the data to the H-SMF. +3. When the (H-)SMF receives the uplink data and finds a related NIDD configuration, the (H-)SMF sends the data in an MO NIDD Indication (External Identifier or MSISDN, non-IP data,) to the SCS/AS. If no NIDD configuration is associated with the UE's PDU session, the data is discarded, MO NIDD Indication is not sent, and the flow continues at step 4. + +Editor's note: Whether the PDU session is released is FFS. + +4. The SCS/AS responds to the H-(SMF) with a MO NIDD Acknowledgement (Cause). +5. If downlink data is available then the MT NIDD procedure as per clause 6.20.4.4 is executed. Otherwise, if no uplink data is available, clause 6.1.4.2 steps 11-14 are executed. + +#### 6.20.4.4 Mobile Terminated Data Transport via NAS-SM and NIDD API + +Figure 6.20.4.4-1 illustrates how SCS/AS sends unstructured (non-IP) data to a given user as identified via External Identifier or MSISDN. This procedure assumes that the NIDD configuration procedure has been completed before. + + + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant AMF + participant V-SMF as V-SMF (Home-routed roaming) + participant HSMF as (H)-SMF + participant SCSAS as SCS/AS + + Note left of UE: No PDU session to (H)-SMF established + SCSAS->>HSMF: 1. MT NIDD Submit Request + HSMF->>SCSAS: 2a. Authorization and load control + Note right of HSMF: 2b. Device triggering procedure (TS 23.502 clause 4.13.2.2) + HSMF->>SCSAS: 2c. MT NIDD Submit Response + Note right of HSMF: 2d. Wait for PDU session establishment + Note left of UE: 2e. PDU session establishment procedure (clause 6.X.4.1 or clause 6.X.4.2) + Note left of UE: UE not reachable + HSMF->>SCSAS: 3a. MT NIDD Submit Response + Note right of HSMF: 3b. Wait for UE reachability + HSMF->>AMF: 4. Namf_Communication_N1N2MessageTransfer (PDU Session ID, SM data transfer) + Note left of UE: 5. Mobile Terminated Data Transport via NAS-SM and N6 (clause 6.1.4.3 steps 3-9) + HSMF->>SCSAS: 6. MT NIDD Submit Response + Note left of UE: (A) UL data available + Note right of HSMF: 7a. Mobile Originated NIDD procedure (clause 6.X.4.3) + Note left of UE: (B) No further UL data available + Note right of HSMF: 7b. Mobile Terminated Data Transport via NAS-SM and N6 (clause 6.1.4.3, steps 15-18) + +``` + +Sequence diagram of the Mobile Terminated NIDD procedure. Lifelines: UE, NG-RAN, AMF, V-SMF (Home-routed roaming), (H)-SMF, SCS/AS. The procedure involves MT NIDD Submit Request/Response, Device triggering, PDU session establishment, N2 message transfer, and subsequent data transport or MT NIDD response based on UL data availability. + +**Figure 6.20.4.4-1: Mobile Terminated NIDD procedure** + +1. The SCS/AS sends a MT NIDD Submit Request (External Identifier or MSISDN, , non-IP data, Priority, PDN Connection Establishment Option) message to the (H)-SMF. The Maximum Latency is an optional field that is used to indicate maximum delay acceptable for downlink data and may be used to configure the buffer duration; a Maximum Latency of 0 indicates that buffering is not allowed. If Maximum Latency is not provided, the + +(H-)SMF determines the acceptable delay based on local policies. Priority is an optional field that is used to indicate the priority of the non-IP data packet relative to other non-IP data packets. PDN Connection Establishment Option is an optional field that is used to indicate what the (H-)SMF should do if the UE has not established the PDU session (wait for the UE to establish the PDU session, respond with an error cause, or send a device trigger; see step 2). If PDN Connection Establishment Option is not provided with the non-IP packet, the (H-)SMF uses the PDN Connection Establishment Option that was provided during NIDD Configuration to decide how to handle the absence of a PDU Session. + +2. The (H-)SMF determines the PDU session based on the S-NSSAI and DNN associated with the NIDD configuration and the user identity. If a PDU session context has been found but the non-IP packet size is larger than the Maximum Packet Size that was provided to the SCS/AS during NIDD Configuration, the (H-)SMF sends a NIDD Submit Response (Cause) with a cause value indicating the reason for the failure condition and the flow stops at this step. Otherwise, the flow continues with step 3. + +If no PDU session is found, then the (H-)SMF, depending on PDN Connection Establishment Option, may either: + +- send a NIDD Submit Response (Cause) with appropriate error cause value. The flow stops at this step; or +- perform device triggering towards the UE (via NEF) to establish a PDU session. The (H-)SMF may use Priority to configure the priority of the device trigger and may use Maximum Latency to configure the validity period of the device trigger. + +In this case, the (H-)SMF sends a NIDD Submit Response (Buffered Indication, Trigger Indication, cause) with an appropriate cause value. The Buffered Indication indicates if the (H-)SMF buffered the non-IP data. The Trigger Indication is used to indicate that a trigger was sent in order to establish the PDU session. + +If data is not buffered, the flow stops at this step, otherwise, it proceeds to step 2d; or + +- accept the NIDD Submit Request, and execute step 2c with an appropriate cause value, and wait for the UE to establish a PDU session to this (H-)SMF (step 2d). If data is not buffered, the flow stops at step 2b. + +NOTE 2: The duration for which the (H-)SMF may wait for establishment of a PDU session to the (H-)SMF for the given UE is implementation dependent. + +- 3a. If a PDU session context corresponding to the External Identifier or MSISDN included in step 1 is found but the UE is currently not reachable, then the (H-)SMF informs the SCS/AS about the unreachability of the UE. The (H-)SMF may include information when the transmission may be attempted again (re-requested re-transmission time) based on how long the UE is expected to be unreachable. +- 3b. The (H-)SMF buffers the data and waits for the UE to become reachable. +4. If the UE is reachable, the (H-)SMF encapsulates the downlink data as payload in an SM data transfer message. In case of home-routed roaming, the (H-)SMF forwards the SM data transfer message and the PDU session ID to the AMF (via V-SMF in case of home-routed roaming) using the Namf\_Communication\_N1N2MessageTransfer service operation. +5. Downlink data is delivered to the UE as per clause 6.1.4.3, steps 3-9. +6. The (H-)SMF sends an MT NIDD Submit Response to the SCS/AS. +7. Uplink data, if available, is sent according to clause 6.20.4.3. Otherwise, clause 6.20.4.3, steps 15-18, is executed. + +#### 6.20.4.5 NIDD configuration procedure + +Figure 6.20.4.5-1 illustrates the procedure for configuring necessary information at SMF and UDM for data delivery via the NIDD API. The procedure can also be used for replacing and deleting configuration information. + +NOTE 1: In order to avoid MO NIDD failure, the NIDD configuration procedure should be performed by the SCS/AS prior to the UE establishing a PDU session that is served by the SMF. MT non-IP data from the SCS/AS can be contained in the NIDD Configuration Request message. + + + +``` + +sequenceDiagram + participant SCS/AS + participant SMF + participant UDM + Note right of SMF: 2. SMF handling + Note right of UDM: 4. UDM handling + SCS/AS->>SMF: 1. NIDD configuration request + SMF->>UDM: 3. NIDD authorization request + UDM->>SMF: 5. NIDD authorization response + SMF->>SCS/AS: 6. NIDD configuration response + +``` + +Sequence diagram of the NIDD configuration procedure. The diagram shows three lifelines: UDM, SMF, and SCS/AS. The sequence of messages is: 1. NIDD configuration request from SCS/AS to SMF; 2. SMF handling (internal message); 3. NIDD authorization request from SMF to UDM; 4. UDM handling (internal message); 5. NIDD authorization response from UDM to SMF; 6. NIDD configuration response from SMF to SCS/AS. + +**Figure 6.20.4.5-1: NIDD configuration procedure** + +1. The SCS/AS sends an NIDD Configuration Request (External Identifier or MSISDN, SCS/AS Identifier, NIDD Duration, T8 Destination Address, Requested Action, PDN Connection Establishment Option) message to the SMF. T8 Destination Address is an optional parameter included by the SCS/AS to indicate that the non-IP data is to be delivered to an address different from the address of the requesting SCS/AS. PDN Connection Establishment Option an optional field that is used to indicate what the SMF should do if the UE has not established the PDU session and MT non-IP data needs to be sent (wait for the UE to establish the PDU session, respond with an error cause, or send a device trigger via the NEF; see step 2 of the MT NIDD Procedure in clause 6.20.4.4). When PDN Connection Establishment Option is included in the Configuration of NIDD procedure, the SMF will use the value as the default preference from the SCS/AS when handling all MT non-IP packets associated with the NIDD connection. + +When MT non-IP data is included in the NIDD Configuration request message, the SMF can send the MT non-IP data to the UE only after a PDU session to the SMF is established as defined in clause 6.20.4.1 or 6.20.4.2. In such cases, upon successful completion of step 6 of the NIDD Configuration procedure, clause 6.20.4.4 is executed. + +NOTE 2: It is up to the SCS/AS to determine whether and if NIDD Duration can be set to never expire. + +NOTE 3: The SCS/AS is expected to be configured to use the same SMF as the one selected by the AMF during the UE's attachment to the network. + +NOTE 4: A relative priority scheme for the treatment of multiple SCS/AS NIDD Configuration Requests, e.g. for deciding which requests to serve under overload condition, can be applied. This priority scheme is an implementation option that is used locally by the SMF, i.e. it is neither used nor translated in procedures towards other functions. + +2. If the Requested Action is set to "Cancel" it indicates the purpose of the request is to cancel the transaction and the flow proceeds to step 6. If the Requested Action is set to "Update", the purpose of the transaction is to update the parameters associated with the configuration (i.e. PDN Connection Establishment Option). Otherwise, the request is for a new NIDD configuration and the SMF stores the External Identifier or MSISDN, SCS/AS Identifier, T8 Destination Address, PDN Connection Establishment Option, and NIDD Duration. If either the SCS/AS is not authorized to perform this request (e.g. based on policies, if the SLA does not allow for it) or the NIDD Configuration Request is malformed, the SMF performs step 6 and provides a Cause value appropriately indicating the error. Depending on the configuration, the SMF may change the NIDD Duration. + +3. The SMF sends an NIDD Authorization Request (External Identifier or MSISDN, S-NSSAI, DNN) message to the UDM to authorize the NIDD configuration request for the received External Identifier or MSISDN, and to receive necessary information for NIDD, if required. + +NOTE 5: The SMF uses the SCS/AS Identifier and External Identifier or MSISDN that was obtained in step 1 to determine what S-NSSAI and DNN will be used to enable transfer of non-IP data between the UE and the SCS/AS. This determination is based on local policies. + +4. The UDM examines the NIDD Authorization Request message, e.g. with regard to the existence of External Identifier or MSISDN and maps the external identifier to SUPI and/or MSISDN. If this check fails, the UDM follows step 5 and provides a result indicating the reason for the failure condition to the SMF. + +5. The UDM sends an NIDD Authorization Response (SUPI and MSISDN or External Identifier, Result) message to the SMF to acknowledge acceptance of the NIDD Authorization Request. The SUPI and, if available, the MSISDN (when NIDD Configuration Request contains an External Identifier) or if available, External Identifier(s) (when NIDD Configuration Request contains an MSISDN) are returned by the UDM in this message. This allows the SMF to correlate the SCS/AS request received in step 1 of this procedure with the PDU session established for this subscriber. +6. The SMF sends an NIDD Configuration Response (Maximum Packet Size, and Cause) message to the SCS/AS to acknowledge acceptance of the NIDD Configuration Request and the deletion of the identified NIDD configuration, if it was requested. If the NIDD Configuration was accepted, the SMF will create an association between the T8 instance ID, External Identifier or MSISDN, SUPI, and PDU Session ID of the unstructured PDU Session. In the MT NIDD procedure, the SMF will use T8 instance ID and External Identifier or MSISDN to determine the SUPI and PDU Session ID of the unstructured PDU Session. In the MO NIDD procedure, the SMF will use the SUPI and PDU Session ID to obtain the T8 instance ID, External Identifier or MSISDN. The Maximum Packet Size is the maximum NIDD packet size that was transferred to the UE by the SMF in the PCO. If no maximum packet size was provided to the UE by the SMF, the SMF sends a default configured max packet size to SCS/AS. + +## 6.20.5 Impacts on existing entities and interfaces + +**Editor's note:** This clause describes impacts to existing entities and interfaces. + +## 6.20.6 Evaluation + +**Editor's note:** This clause provides an evaluation of the solution. + +# 6.21 Solution 21: NIDD service activation + +## 6.21.1 Introduction + +This solution addresses the Key Issue 1 and 8 in perspective of NIDD API(s) for infrequent small data transmission and capability exposure to AF. + +In this solution, NIDD via NEF is called as NIDD service. And making association between NF (e.g., AMF or SMF) and NEF for NIDD service is called NIDD service activation. + +This solution proposes procedure for NIDD service activation between AMF/SMF and NEF. NIDD service means non-IP data delivery service between UE and AS/AF via NEF. This solution also optimizes NIDD service activation for a group of UEs, as massive number of devices are expected in the IoT service. + +**Editor's note:** This solution allows both AMF or SMF for NIDD services. The NF which can be used for NIDD will be decided as part of other solution. + +This solution has the following characteristics: + +- NEF subscribes NIDD service activation to NFs e.g., AMF or SMF. When the AMF/SMF determines the UE begins to use NIDD (based on negotiation via MM-NAS or SM-NAS procedure), AMF/SMF informs NEF of the NIDD service activation. +- During this subscribe-notify operation, AMF/SMF and NEF exchanges necessary information for NIDD service activation. +- As follows bulk subscription in TS 23.502 [7], NEF can subscribe NIDD service activation to all NFs that support NIDD service. When AMF or SMF begin to serve the UE that request NIDD, it notifies the NEF that the NIDD service activation for the UE is detected. +- This subscribe-notify service operation for NIDD service activation is independent with NAS procedure. +- After NIDD service activation, the NEF notifies to the AS/AF that the NIDD service is activated. + +## 6.21.2 Functional Description + +### 6.21.2.1 General + +The NEF can subscribe to the NF that provides necessary services, e.g., NIDD via NEF. NEF can determine target NF by querying to NRF or UDM. Or the NEF can provision the subscription for NIDD service activation to the UDM, and the UDM provides this information to the serving NF as UE's subscription data. Upon receiving the event subscription for NIDD service activation from the NEF, the NF stores this information. When the corresponding event occurs for the requested subscription, the NF notifies the NEF with requested information. + +For a group of UEs, NEF can perform bulk subscription for NIDD service activation. When the NEF performs bulk subscription for any UE (i.e. all UEs), group of UE(s), it subscribes to all the NFs that provide the necessary services e.g. In a given PLMN, NEF may subscribe to all AMFs or SMFs that support NIDD service. Upon receiving bulk subscription from the NEF, the NFs store this information. Whenever the corresponding event(s) occur for the requested UE(s) as in bulk subscription request, NFs notify the NEF with the requested information. + +During this subscribe-notify service operation, necessary information for NIDD service activation is exchanged. + +**Editor's note:** It is for further study whether NEF can use Nudr services for this procedure. + +### 6.21.2.2 Mobility + +When serving NF changes, it retrieves the UE context from the old NF. In the UE context, there is information for the subscription of NIDD service activation so that the new serving NF determines NIDD service activation is required. The serving NF notifies NEF with the necessary information for the NIDD, so that connection between NF and NEF for NIDD can be maintained. It also can be achieved by Nudm services for SDM Subscription-Notification which allows to notify change of serving NFs. + +**Editor's note:** It is FFS to consider roaming scenario. + +## 6.21.3 Support of EPC Interworking + +**Editor's note:** This clause describes if and how EPC-5GC interworking is supported by this solution. + +## 6.21.4 Procedures + +### 6.21.4.1 NIDD service activation for AMF based solution + +In this solution, based on the presence of the serving AMF for the UE, the NEF performs invoking either Namf\_NIDDservice\_Subscribe to the AMF or Nudm\_ParameterProvision\_Update to the UDM in order to provision the information for NIDD service activation to the AMF. + +After the AMF receives the information for NIDD service activation to the UE that has registered, the AMF may perform UE configuration Update procedure to inform availability of NIDD service to the UE. + +**Editor's note:** It is FFS whether the service operation can be re-named or can re-use existing service operation. + + + +``` + +sequenceDiagram + participant UE + participant AMF + participant UDM + participant NEF + participant AS/AF + + Note right of AS/AF: 1. NIDD Configuration + AS/AF->>NEF: 1. NIDD Configuration + Note right of NEF: 2a. Nudm_ParameterProvision_Update (Event subscription of NIDD service) + NEF->>UDM: 2a. Nudm_ParameterProvision_Update (Event subscription of NIDD service) + Note right of UDM: 2b. Namf_NIDDservice_Subscribe + UDM->>AMF: 2b. Namf_NIDDservice_Subscribe + Note right of AMF: 3. Nudm_SDM_Notification (Event subscription of NIDD service) + AMF->>UDM: 3. Nudm_SDM_Notification (Event subscription of NIDD service) + Note left of AMF: 4. During Registration procedure, AMF determines to provide NIDD service to the UE + AMF->>NEF: 5. Namf_NIDDservice_Notify + Note right of NEF: 6. Nnef_NIDDservice_activated + NEF->>AS/AF: 6. Nnef_NIDDservice_activated + +``` + +Sequence diagram for NIDD service Activation for AMF based solution. Lifelines: UE, AMF, UDM, NEF, AS/AF. The sequence starts with NIDD Configuration from AS/AF to NEF. NEF then sends Nudm\_ParameterProvision\_Update (Event subscription of NIDD service) to UDM. UDM sends Namf\_NIDDservice\_Subscribe to AMF. AMF sends Nudm\_SDM\_Notification (Event subscription of NIDD service) to UDM. During Registration procedure, AMF determines to provide NIDD service to the UE. AMF then sends Namf\_NIDDservice\_Notify to NEF. NEF sends Nnef\_NIDDservice\_activated to AS/AF. + +**Figure 6.21.4.1-1: NIDD service Activation for AMF based solution** + +1. NEF and AS/AF performs NIDD configuration procedure. The AS/AF requests NIDD configuration to the NEF. The AS/AF provides External Identify of UE and necessary information to the NEF for NIDD. The NEF creates UE context for the NIDD service based on the received information from the AS/AF. During this operation, NEF can retrieve the information of serving AMF for the UE from the UDM, if the UE has already registered in the network. +- 2a. If the NEF cannot retrieve the information of the serving AMF in the step 1, which means there is no serving AMF for the UE, the NEF provisions the information for NIDD service activation to the UDM In this information, External ID of UE, NEF ID, and Reference ID are included. The UDM stores this information in the UE's subscription data. This information can be considered as event subscription for NIDD service activation to the serving AMF. +- 2b. If the NEF retrieves the information of the serving AMF in the step 1, the NEF subscribes the AMF with information for NIDD service activation. In this message, External ID of UE, NEF ID, and Reference ID are included. The reference ID is used as correlating identifier when the AMF notifies to NEF for this request. In addition, necessary information for NIDD service can be included in this message, e.g. maximum latency for NIDD, communication pattern. +3. After Step 2a, as the UE hasn't registered yet to the network, the UDM provides UE's subscription data when UE performs initial registration procedure. +4. If the UE has already registered and the UE has requested NIDD service, the AMF may trigger UE Configuration Update procedure after step 2b in order to inform the UE of availability of NIDD service. During Registration procedure, the AMF determines whether to provide NIDD service to the UE based on the received information from step 2b or step 3. The UE indicates use of NIDD service in Registration request message, and the AMF responds with the permission of NIDD service for the UE. +5. After AMF decides to provide NIDD service to the UE, the AMF notifies the NEF with the reference ID, NEF ID, and AMF ID. The reference ID and NEF ID are the received one in the step 2b or step 3. With this information, the NEF determines this notification is related with the NIDD service activation. +6. The NEF notifies to the AS/AF that the NIDD service for the UE is activated. The AS/AF can send downlink data to the UE. + +#### 6.21.4.2 NIDD service activation for SMF based solution + +In this solution, based on the presence of the serving SMF for PDU session for the UE, the NEF performs invoking either Nsmf\_NIDDservice\_Subscribe to the SMF or Nudm\_ParameterProvision\_Update to the UDM in order to provision the information for NIDD service activation to the SMF. + +If NIDD configuration has taken place prior to the PDU session establishment from the UE, the SMF can retrieve the information for the NIDD service activation from the subscription information during PDU session establishment procedure. In this case, the SMF can complete PDU session establishment for NIDD and activation of NIDD service successfully. The NEF notifies to the AS/AF of NIDD service activation. After the AS/AF receives the notification for NIDD service activation, it can send downlink non-IP data to the UE. + +If NIDD configuration hasn't taken place prior to the PDU session establishment from the UE, the SMF cannot retrieve the information for the NIDD service activation. In this case, the SMF rejects the PDU session establishment request from the UE. The AS/AF may decide to perform device triggering for PDU session establishment if there is no NIDD service activation notification from the NEF for a certain duration, which is based on local configuration in the AS/AF. + +**Editor's note:** It is FFS whether the service operation can be re-named or can re-use existing service operation. + +Error! No + +1 + +Error! No text of specified style in + + + +``` +sequenceDiagram + participant UE + participant SMF + participant UDM + participant NEF + participant AS/AF + + Note right of AS/AF: 1. NIDD Configuration + AS/AF->>NEF: + Note right of NEF: 2. Nudm_ParameterProvision_Update (NIDD configuration) + NEF->>UDM: + Note left of SMF: 3. PDU Session Establishment for NIDD via NEF + UE->>SMF: + Note right of SMF: 4. Nsmf_NIDDservice_Notify + SMF->>NEF: + Note right of NEF: 5. Nnef_NIDDservice_activated + NEF->>AS/AF: +``` + +Sequence diagram showing the interaction between UE, SMF, UDM, NEF, and AS/AF for NIDD configuration and PDU session establishment. + +**Figure 6.21.4.2-1: When PDU session establishment after NIDD configuration** + +1. NEF and AS/AF performs NIDD configuration procedure. The AS/AF requests NIDD configuration to the NEF. The AS/AF provides External Identify of UE and necessary information to the NEF for NIDD. The NEF creates UE context for the NIDD service based on the received information from the AS/AF. During this operation, NEF cannot retrieve the information of serving SMF for the UE from the UDM, as the UE hasn't established the PDU session for the NIDD. +2. The NEF provisions the information for NIDD service activation to the UDM. In this information, External ID of UE, NEF ID, and Reference ID are included. The UDM stores this information in the UE's subscription data. This information can be considered as event subscription for NIDD service activation to the serving SMF. +3. When the UE requests PDU Session Establishment for NIDD, the SMF retrieves the UE's SM subscription data which includes the information for NIDD service activation as provisioned in the step 2. The SMF determines to provide NIDD service to the UE based on this information. +4. The SMF notifies the NEF with the External ID, reference ID, NEF ID, and SMF ID. The reference ID and NEF ID are the received information in the step 3. With this information, the NEF determines this notification is related with the NIDD service activation. +5. The NEF notifies to the AS/AF that the NIDD service for the UE is activated. The AS/AF can send downlink data to the UE. + +#### 6.21.4.3 Bulk subscription of NIDD service activation + + + +``` + +sequenceDiagram + participant AS/AF + participant NEF + participant NRF + participant SMF + participant AMF + Note right of AS/AF: 1. NIDD Configuration + AS/AF->>NEF: 1. NIDD Configuration + Note right of NEF: 2. Nnrf_NFStatusSubscribe (NIDD Capability) + NEF->>NRF: 2. Nnrf_NFStatusSubscribe (NIDD Capability) + Note right of SMF: 3a. NF Registration + SMF->>NRF: 3a. NF Registration + Note right of AMF: 3b. NF Registration + AMF->>NRF: 3b. NF Registration + Note right of NRF: 4. Nnrf_NFStatusNotify (NIDD Capability) + NRF->>NEF: 4. Nnrf_NFStatusNotify (NIDD Capability) + Note right of NEF: 5a. Nsmf_NIDDservice_Subscribe + NEF->>SMF: 5a. Nsmf_NIDDservice_Subscribe + Note right of NEF: 5b. Namf_NIDDservice_Subscribe + NEF->>AMF: 5b. Namf_NIDDservice_Subscribe + Note right of AMF: 6. NF determines to provide NIDD service to the UE + Note right of SMF: 7a. Nsmf_NIDDservice_Notify + SMF->>NEF: 7a. Nsmf_NIDDservice_Notify + Note right of AMF: 7b. Namf_NIDDservice_Notify + AMF->>NEF: 7b. Namf_NIDDservice_Notify + +``` + +Sequence diagram for Bulk NIDD service activation. Lifelines: AMF (stack), SMF (stack), NRF, NEF, UDM, AS/AF. The sequence starts with 1. NIDD Configuration from AS/AF to NEF. 2. Nnrf\_NFStatusSubscribe (NIDD Capability) from NEF to NRF. 3a. NF Registration from SMF to NRF. 3b. NF Registration from AMF to NRF. 4. Nnrf\_NFStatusNotify (NIDD Capability) from NRF to NEF. 5a. Nsmf\_NIDDservice\_Subscribe from NEF to SMF. 5b. Namf\_NIDDservice\_Subscribe from NEF to AMF. 6. NF determines to provide NIDD service to the UE (internal to AMF/SMF). 7a. Nsmf\_NIDDservice\_Notify from SMF to NEF. 7b. Namf\_NIDDservice\_Notify from AMF to NEF. + +**Figure 6.21.4.2-1: Bulk NIDD service activation** + +1. NEF and AS/AF performs NIDD configuration procedure. The AS/AF requests NIDD configuration to the NEF. The AS/AF provides External Group Identify and necessary information to the NEF for NIDD. The NEF creates UE context for the NIDD service based on the received information from the AS/AF. + 2. NEF subscribes the NRF for registered NF with NIDD service capability. + - 3a/3b. When NF instantiates, it registers itself to the NRF along with the NIDD service capability. NRF acknowledge the registration. + 4. NRF notifies the NEF with the registered NFs along with the NIDD service capability. + - 5a/5b. NEF subscribes with the corresponding NFs for group of UEs based on the NIDD configuration at step 1. The NEF subscribes NFs with information for NIDD service activation. In this message, External group ID of UE, NEF ID, and Reference ID are included. The reference ID is used as correlating identifier when the NFs notify to NEF for this request. In addition, necessary information for NIDD service can be included in this message, e.g., maximum latency for NIDD, communication pattern. +- The NEF may subscribe for a single UE with External ID if it has resolved the External Group ID to External IDs from the UDM during step 1. +6. The NFs determine whether to provide NIDD service to the UE based on NAS level negotiation. The UE indicates use of NIDD service in the NAS request message, and the NF responds with the permission of NIDD service for the UE. The NF detects the subscription for the NIDD service received in step 5, based on the External Group ID or External ID for the UE in the UE context. + +**Editor's note:** Detail operation of step 6 depends on how AMF/SMF establishes connection for NIDD via NEF to the UE. + +7a/7b. After NFs determine to provide NIDD service to the UE, the NFs notify the NEF with the External Group ID, External ID, reference ID, NEF ID, and NF ID. The reference ID and NEF ID are the received one in the step 5. With this information, the NEF determines this notification is related with the step 5. + +### 6.21.5 Impacts on existing entities and interfaces + +**Editor's note:** This clause describes impacts to existing entities and interfaces. + +### 6.21.6 Evaluation + +**Editor's note:** This clause provides an evaluation of the solution. + +## 6.22 Solution 22: eDRX for CM-IDLE state in 5GS + +### 6.22.1 Introduction + +The proposal is to enable an eDRX equivalent feature from EPS in 5GS. It addresses Key Issue 4, Power saving functions. + +### 6.22.2 Functional Description + +The proposal is to enable an eDRX equivalent feature from EPS in 5GS. + +As the 5GC has a different architecture and some new functionality compared to EPC some adaptations are needed compared to eDRX in EPS. The following adaptations are needed: + +- eDRX sleep cycle negotiation: + +In EPC the UE requests extended idle mode DRX parameters during attach procedure and RAU/TAU procedure and the SGSN/MME may reject or accept the UE request for enabling extended idle mode DRX. + +In case the SGSN/MME accepts the extended idle mode DRX, the SGSN/MME based on operator policies and, if available, the extended idle mode DRX cycle length value in the subscription data from the HSS, may also provide different values of the extended idle mode DRX parameters than what was requested by the UE. If the SGSN/MME accepts the use of extended idle mode DRX, the UE applies extended idle mode DRX parameters either as received or modified by SGSN/MME. + +The same principles can be used on 5GC but the procedures used by the UE to request extended idle mode DRX parameters will be Registration and Registration Update. + +In EPS the UE and the SGSN/MME handles the request in 5GS the UE handling shall be the same but in 5GC it will be the AMF instead of SGSN/MME. + +- Subscription information: + +Extended idle mode DRX cycle length value needs to be added in the subscription data from the UDM using the same principles as in EPS. + +- Hyper SFN, Paging Hyperframe and Paging Time Window: + +Same handling as in EPC but in 5GC the AMF will assign the Paging Time Window. The AMF will include the Paging Time Window in the extended DRX parameters to the UE and in the paging eDRX information to the (R)AN. + +NOTE 1: Whether the solution for Hyper SFN and Paging Hyperframe in NB-IoT and WB-E-UTRAN in the 5GS Rel-16 will look the same as extended idle mode DRX (eDRX) in E-UTRAN depends on RAN further work. + +- For WB-E-UTRAN (eMTC) the ng-eNB broadcasts an indicator for support of eDRX in 5GC in addition to the existing indicator for support of eDRX in EPC as defined in TS 36.331 [23]. + +NOTE 2: This solution is also applicable for CM-IDLE with Suspend (i.e. Solution 19). + +### 6.22.3 Support of EPC interworking + +eDRX depends on UE provided parameters in Attach/TAU and Registration Request, respectively, as well as subscription information and local policies in the MME and AMF, respectively. Therefore eDRX handling can be kept separate in EPC and 5GC and no specific interworking is required. + +### 6.22.4 Procedures + +The existing procedures in 5GC will be reused to handle the eDRX signalling between AMF, (R)AN, UDM and UE. + +### 6.22.5 Impacts on existing entities and interfaces + +The UE shall send request for extended idle mode DRX parameters to the AMF. The UE will also receive the extended DRX parameters and utilize this information for extended DRX handling. + +The AMF shall handle the request from the UE and reject, modify or accept the request. If accepted (as is or with modification) the AMF shall set the extended idle mode DRX parameters and supply relevant parameters to UE and (R)AN. + +The UDM may include the extended idle mode DRX cycle length value in the subscription data to the AMF. + +The (R)AN will receive the paging eDRX information from the AMF. + +### 6.22.6 Evaluation + +This solution enables extended DRX equivalent to eDRX support in EPS to ensure battery efficiency while UEs are in CM-IDLE state. The solution addresses the architectural requirements of key issue 4 track 1 ("5G NAS/5GC support of extended idle mode DRX"). + +## 6.23 Solution 23: MICO Mode Management for Expected Application Behaviour + +### 6.23.1 Introduction + +This solution addresses Key Issue 4: Power Saving Functions. + +A UE in MICO mode need not listen to paging while in CM-IDLE and is only reachable for DL data or signalling when the UE is in CM-CONNECTED. A UE in MICO mode may stop any access stratum procedures in CM-IDLE, until the UE initiates transition from CM-IDLE to CM-CONNECTED. In order to minimize UE power consumption, the UE should be put into the MICO mode whenever possible, i.e. when there is no DL data for the UE. + +This solution assumes that Expected UE behaviour (communication pattern) information is available and may indicate scheduled DL communication. Expected UE behaviour provisioning is provided by the solution to Key Issue 13 Support for Expected UE Behaviour. It manages MICO mode for the UE according to the communication pattern information. + +When the communication pattern information indicates scheduled DL communication, the UE may be put into MICO mode between the scheduled DL communications. In this case, the AMF allocates a periodic registration timer value for the UE such that the UE performs Periodic Registration Update upon expiry of the periodic registration timer and exits MICO mode, at or before the scheduled DL communication time, and thus allowing DL communication according to the schedule. + +If the DL communication is scheduled between 13:00 and 14:00, the AMF may request the UE in MICO mode to perform Periodic Registration Update to exit MICO mode at or ahead of the example 1 hour window through the allocation of the periodic registration timer value. The synchronisation of the periodic registration timer expiry relative to the scheduled DL communication time is implementation specific. This synchronisation should be loose enough to tolerate time inaccuracy and signalling delay when exiting MICO mode. + +In order to prevent the synchronization from being broken by UL transmissions the AMF may provide a "*do not reset the timer for Periodic Registration*" indication together with the periodical registration timer value to the UE. If the "*do not reset the timer for Periodic Registration*" indication is provided, once started the UE keeps its periodic registration + +timer running all the way to the expiry and only restarts it when it expires, even if it enters and leaves CM-CONNECTED or MICO mode is enabled or disabled. When the timer expires, the UE performs registration update. + +If the periodic registration timer value is renegotiated during a Registration procedure, e.g., a mobility registration procedure, the periodic registration timer is stopped and restarted using the renegotiated value even when the "*do not reset the timer for Periodic Registration*" indication was provided by the AMF. The AMF should ensure the renegotiated timer value to be aligned with the DL communication schedule. + +### 6.23.2 Functional Description + +During registration (update), the AMF may disallow/deactivate MICO mode for the UE if the communication pattern parameters indicate uncertainty of DL communication, or that DL communication is happening soon, e.g. within a preconfigured time window. The AMF may allow/activate MICO mode in the other cases for UE power saving. + +For a UE in MICO mode, if the communication pattern parameters indicates the absence of DL communication, the AMF may allocate a large periodic registration timer value so that the UE can enter deep sleep between Periodic Registration Updates for power saving. If the communication pattern parameters indicate scheduled DL communication the AMF should allocate a periodic registration timer value such that the UE performs Periodic Registration Update to renegotiate MICO mode before or at the scheduled DL communication time from the Expected UE Behaviour. + +The AMF may provide a "*do not reset the timer for Periodic Registration*" indication to the UE together with the periodic registration timer value. If the "*do not reset the timer for Periodic Registration*" indication is provided by the AMF, the UE keeps its periodic registration timer running while in CM-CONNECTED and performs periodic registration update when the timer expires, in order to re-negotiate MICO mode and its parameters. The periodic registration timer is only restarted on expiry. If the periodic registration timer value is renegotiated during a Registration procedure the periodic registration timer is stopped and restarted using the renegotiated value even when the "*do not reset the timer for Periodic Registration*" indication was provided by the AMF. When the periodic registration timer is started is not changed by this solution. + +### 6.23.3 Support of interworking + +The periodic Registration timer in 5GS is equivalent to the periodic TAU timer in EPS, and the MICO UE behaviour is equivalent to the PSM UE behaviour in EPS. + +Mobility from 5GS to EPS: + +- The MICO UE will not receive the "*do not reset the timer for Periodic Registration*" from the EPC. After performing an Attach procedure or a TAU procedure in the EPS, the MICO UE therefore considers that the indication is removed. + +Mobility from EPS to 5GS: + +- Only if the UE receives the "*do not reset time timer for Periodic Registration*" from 5GC in a Registration procedure (e.g. due to periodic registration or mobility registration), does the UE start to behave accordingly, as described in clause 6.23.2. + +### 6.23.4 Procedures + +Figure 6.23.4-1 illustrates the procedure of obtaining communication pattern parameters and managing MICO mode based on them. + + + +``` + +sequenceDiagram + participant UE + participant RAN + participant AMF + participant UDM + Note right of AMF: 3. Determine MICO mode periodic registration time and decide whether timer is not stoppable based on subscription/ communication pattern parameters + UE->>RAN: 1. Registration Request(MICO mode) + AMF->>UDM: 2. Obtain communication pattern parameters + AMF->>RAN: 4. Registration Accept(MICO mode do not reset Periodic Registration timer) + Note left of UE: 5. Keep periodic registration timer running while in CMCONNECTED + +``` + +Sequence diagram illustrating Communication pattern based MICO mode management. The diagram shows interactions between UE, RAN, AMF, and UDM. Step 1: UE sends Registration Request(MICO mode) to RAN. Step 2: AMF sends Obtain communication pattern parameters to UDM. Step 3: AMF determines MICO mode periodic registration time and decides whether timer is not stoppable based on subscription/ communication pattern parameters. Step 4: AMF sends Registration Accept(MICO mode do not reset Periodic Registration timer) to RAN. Step 5: UE keeps periodic registration timer running while in CMCONNECTED. + +**Figure 6.23.4-1: Communication pattern based MICO mode management** + +1. The UE performs the Registration procedure, with any Registration type (Initial Registration, Mobility Registration Update, or Periodic Registration Update) with the AMF, which includes MICO mode preference. +2. The AMF obtains communication pattern parameters from the UDM. This step is optional if the AMF has valid communication pattern information in local configuration. +3. The AMF determines MICO mode, periodic registration timer value and the "*do not reset the timer for Periodic Registration*" indication for the UE according to the communication pattern parameters and operator policy. +4. The AMF informs the UE that the Registration is accepted, including the accepted MICO mode and "*do not reset the timer for Periodic Registration*" indication. +5. The UE keeps the periodic registration timer running, even while in CM-CONNECTED, i.e. even if unscheduled UL data transmissions occur, and is only restarted when it expires. + +### 6.23.5 Impacts on existing entities and interfaces + +In the AMF: + +- determining MICO mode and periodic registration timer value for the UE taking into account communication pattern information and providing a "*do not reset the timer for Periodic Registration*" indication to the UE, if required. + +In the UE: + +- receiving "*do not reset the timer for Periodic Registration*" indication from the AMF and, according to the indication, keeping its periodic registration timer running to expiry even if it enters and leaves CM-CONNECTED. + +### 6.23.6 Evaluation + +The solution addresses the following Architectural Requirements for Key Issue#4: + +- Solutions shall optimize UE power savings according to expected and desired UE and application behaviour (e.g. communication pattern) if such information is available. + +When the communication pattern information indicates scheduled DL communication, the UE may be put into MICO mode between the scheduled DL communications, where the UE does not listen to paging and therefore saves power, while still becoming reachable according to the communication pattern schedule. + +The use of MICO mode management is not applicable to all application scenarios and may cause additional signalling and power consumption in the cases where scheduled downlink communication with longer intervals is not required. + +The combination of non-stoppable periodic registration timer (as indicated by the "*do not reset the timer for Periodic Registration*" indication) and MICO mode management are used together to support different ways the AS prepares DL traffic: + +- The AS prepares DL traffic during a specific time window, however when in the time window is not known. Once the DL traffic becomes available, the DL traffic should be delivered to the UE. +- The AS can either prepare the DL traffic ahead of the communication pattern window and queue it in the network, or use (if available) monitoring events to get notification that DL traffic can be sent to the UE. + +MICO mode management with the non-stoppable periodic registration timer can save power for a UE while allowing the network to maintain control of the wake up schedule and therefore optimising UE power according to the expected and desired UE and application behaviour. + +## 6.24 Solution 24: High latency communication with extended buffering and event notifications + +### 6.24.1 Introduction + +This clause addresses the high latency communication key issue #3. + +### 6.24.2 Functional Description + +Functions for High latency communication may be used to handle mobile terminated (MT) communication with UEs being unreachable while using power saving functions e.g. UE Power Saving Mode, extended idle mode DRX or MICO. "High latency" refers to the initial response time before normal exchange of packets is established. That is, the time it takes before a UE has woken up from its power saving state and responded to the initial downlink packet(s). + +High latency communication is handled by extended buffering of downlink data in the UPF/SMF. Optionally High latency communication can also be handled by notification procedures. + +High latency communication by extended buffering of downlink data in the UPF/SMF is controlled by the AMF/SMF. The AMF asks the SMF/UPF, to buffer downlink data until the UE is expected to wake up from its power saving state, see clause 6.24.4.1. If a SMF/UPF change is invoked, the buffered packets are forwarded and will not be lost. The number of packets to buffer is decided by the SMF/UPF, but the AMF may optionally provide supporting information. Optionally, a suggested number of packets to buffer may also be provided by the SCS/AS as input to the SMF/UPF, see key issue 10. + +An SCS/AS may optionally use notification procedures to handle High latency communication (see clause 6.24.4.2). The SCS/AS requests to receive notification when a UE wakes up from its power saving state to be able to send downlink data to the UE when the UE becomes reachable. Especially, for long latencies (e.g. infrequent mobile terminated communication) this is suitable. This notification procedure can be triggered based on following monitoring events (see clause 4.15.3.1 in TS 23.502 [7]): + +- Monitoring event: UE Reachability; or +- Monitoring event: Availability after DDN failure. + +An SCS/AS may request a one-time "UE Reachability" notification when it wants to send data to the UE. Alternatively, the SCS/AS may request repeated "Availability after DDN failure" notifications where each notification is triggered by a DDN failure, i.e. the SCS/AS sends a downlink packet which is discarded by SMF/UPF but which triggers the AMF to send an event notification to the SCS/AS next time the UE wakes up. + +If CM-CONNECTED with RRC inactive state is activated for the UE with power saving state for long time, the downlink data handling (i.e. CN extended buffering) and notification is handled in the 5GC in the same way applied for CM-IDLE state, with additional support of information from RAN side. The RAN support information for high latency communication is provided through the N2 notification procedure, see clause 4.8.3 in TS 23.502 [7]. + +The tools for High latency communication make the behaviour of the 3GPP network predictable when sending mobile terminated data to UEs applying power saving functions. The network will deliver downlink packets with high + +reliability for both stationary and mobile UEs when the UE wakes up from its power saving state. Therefore, SCS/AS can adapt its retransmissions to reduce the load on both the SCS/AS itself and the network. + +### 6.24.3 Support of EPC interworking + +Interworking between 5GC and EPC is achieved by a combined P-GW/SMF and P-GW-U+UPF. If a SMF/UPF has data buffered for a UE when the UE moves to EPC and becomes reachable then buffered data will get delivered in EPC (and vice versa). + +### 6.24.4 Procedures + +#### 6.24.4.1 Extended buffering + +##### 6.24.4.1.1 General + +Functions for High latency communication may be used to handle mobile terminated (MT) communication with UEs being unreachable while using power saving functions (see KI#4). "High latency" refers to the initial response time before the delivery of MT packets is possible. That is, the time it takes before a UE has woken up from its power saving state and responded to the initial downlink packet(s). + +The High latency communication includes invoking extended buffering of MT data at the UPF when the UE is in a power saving state and not reachable. The handling shall be specified in the Network Triggered Service Request procedure. Establishing the user plane for delivering the buffered data when the UE contacts the AMF by signalling shall be specified in the Registration procedure. The AMF uses its parameter DL Data Buffer Expiration Time in the MM context information to know if there is buffered DL data to be delivered when the UE becomes reachable. When set, the DL Data Buffer Expiration Time shall be cleared at any user plane setup to the RAN when the buffered DL data can be delivered. At Registration procedure with AMF change, the old AMF shall indicate in the context response to the new AMF that buffered DL data is waiting and hence the new AMF shall establish the user plane for delivery of the buffered DL data. When the DL Data Buffer Expiration Time has expired, the AMF considers no DL data to be buffered and no indications of Buffered DL Data Waiting are sent during context transfers at Registration procedure. At Registration procedure with UPF change, the buffered DL data is forwarded to the new UPF. + +For UE in CM-CONNECTED with RRC-Inactive mode, it is operator configured local policies in the network that decides if and when CN extended buffering or RAN buffering is used and for what sleep cycle lengths. + +For HLCOM, it's the SMF/UPF that provides CN extended buffering, and the AMF provides buffering related support information towards SMF/UPF. + +For UE in CM-IDLE mode and UE in CM-CONNECTED RRC-Inactive mode, AMF provides buffering support information to SMF/UPF based on the NAS level information negotiated between UE and AMF based on the following: + +- MICO related parameters. +- Other UE sleep cycle related parameters (related to KI#4). +- eDRX related parameters (related to KI#4). A UE using MICO mode is assumed to be able to benefit from Extended buffering. Any DL data being buffered for the UE can be delivered to the UE when it contacts the network. + +**Editor's note:** The details for the handling of extended buffering is FFS and is dependent on KI#4 Power saving functions. + +##### 6.24.4.1.2 DL data in CM-IDLE mode + +For UE in CM-IDLE mode, the figure below shows the call flow of AMF providing buffering related support information to SMF/UPF and downlink data handling. Extended buffering is used for UE that is using a power saving method (see KI#4). Extended buffering should not be used for a UE which has a monitoring event, 'UE Reachability' or 'Availability after DDN failure', configured. + + + +``` + +sequenceDiagram + participant UE + participant RAN + participant AMF + participant SMF + participant UPF + participant UDM + participant NEF + participant SCS/AS + + Note right of SCS/AS: 1. Downlink data + SCS/AS->>UPF: 1. Downlink data + Note right of UPF: 2. DDN + UPF->>SMF: 2. DDN + Note right of SMF: 3. Namf_comm_N1N2MessageTransfer Req_ + SMF->>AMF: 3. Namf_comm_N1N2MessageTransfer Req_ + Note right of AMF: 4. UE not reachable due to power saving + Note right of AMF: 5. Namf_comm_N1N2MessageTransfer Resp (unreachable + buffering info) + AMF->>SMF: 5. Namf_comm_N1N2MessageTransfer Resp (unreachable + buffering info) + Note right of SMF: 6. DDN Failure (buffering info) + SMF->>UPF: 6. DDN Failure (buffering info) + Note right of UPF: 7. Extended data buffer + Note left of UE: 8. UE contacts the network, e.g. SR, Registration Req, NW initiated SR + UE->>RAN: 8. UE contacts the network, e.g. SR, Registration Req, NW initiated SR + Note right of AMF: 9. Event Notification + AMF->>SMF: 9. Event Notification + Note right of SMF: Down link data + SMF-->>UE: Down link data + Note right of UPF: Data discarded if not sent when buffer timer expires + +``` + +Sequence diagram illustrating Data Buffering in SMF/UPF for CM-IDLE mode. The diagram shows the interaction between UE, RAN, AMF, SMF, UPF, UDM, NEF, and SCS/AS. The process starts with Downlink data being sent from SCS/AS to UPF. The UPF sends a DDN to the SMF. The SMF sends a Namf\_comm\_N1N2MessageTransfer Req\_ to the AMF. The AMF checks UE reachability and finds it unreachable due to power saving. The AMF sends a response indicating unreachability and buffering info. The SMF sends a DDN Failure (buffering info) to the UPF. The UPF starts extended data buffering. The UE then contacts the network (e.g., SR, Registration Req, NW initiated SR). The AMF sends an Event Notification to the SMF. The SMF sends Down link data to the UE. The UPF discards data if not sent when buffer timer expires. + +**Figure 6.24.4.1.2-1: Data Buffering in SMF/UPF for CM-IDLE mode** + +The Network Triggered Service Request procedure as specified in TS 23.502 [7] clause 4.2.3.3 would be updated based on the description below. + +1. The application sends downlink data to UPF. +2. The UPF sends a Downlink Data Notification (DDN) message to the SMF if there is no N3 tunnel. +3. The SMF initiates Namf\_Comm\_N1N2MessageTransfer\_Requeust service towards AMF to setup N3 tunnel. +4. The AMF checks the UE reachability in CM-IDLE mode, and UE not reachable due to power saving. If UE is not reachable due to eDRX/DRX, the AMF schedules a paging. +5. The AMF sends Namf\_Comm\_N1N2MessageTRansfer Response to indicate the UE is unreachable. If the UE is unreachable due to power saving, the AMF also indicates DL Buffering Requested and provides buffering supporting information (e.g. DL Buffering Duration time and optionally a DL Buffering Suggested Packet Count). + +The AMF stores a new value for the DL Data Buffer Expiration Time in the MM context for the UE based on the DL Buffering Duration time. The DL Data Buffer Expiration Time is used for UEs using power saving state and indicates that there are buffered DL data waiting in the UPF. When the DL Data Buffer Expiration Time has expired, the AMF considers no DL data to be buffered and no indications of Buffered DL Data Waiting are sent during context transfers at Registration procedure. + +NOTE: If AMF is configured to support Notify on availability after DDN failure as specified in clause 6.24.4.2.3, Extended data buffering is not invoked. + +6. The SMF sends DDN failure with DL Buffering Requested indication and buffering supporting information to UPF. The SMF includes the DL Buffering Duration time and optionally a DL Buffering Suggested Packet Count. +7. The UPF starts extended data buffering based on the buffering support information. The UPF stores a new value for the DL Data Buffer Expiration Time based on the DL Buffering Duration time and does not send any + +additional Data Notification if subsequent downlink data packets are received in the UPF before the DL Buffer Expiration Time has expired for the UE. + +8. When UE enters CM-CONNECTED mode, the AMF notifies the same SMF that received the UE unreachable indication in step 5. + +At, for example, periodic or mobility registration update as specified in TS 23.502 [7] clause 4.2.2.2 extended buffering is handled with the following addition to step 22 (Registration Accept). If the DL Data Buffer Expiration Time for the UE in the AMF has not expired, the user plane setup procedure is activated. The message sequence should be similar for the UE triggered Service Request procedure specified in clause 4.2.3.2 of TS 23.502 [7] from the step when AMF activates the User Plane connections of the PDU Session(s). + +9. SMF/UPF trigger the setting of N3 tunnel and delivery the buffered data packets. + +##### 6.24.4.1.3 DL data in CM-CONNECTED mode without CN extended buffering + +The figure below shows the handling of downlink data in CM-CONNECTED mode without extended buffering in CN but with temporary buffering in the RAN . This procedure is used for UEs not applying any power saving method or the power saving time is limited. For UEs that do apply power saving methods (i.e. potentially very long buffering times), see clause 6.24.4.1.4. + + + +``` + +sequenceDiagram + participant UE + participant RAN + participant AMF + participant SMF + participant UPF + participant UDM + participant NEF + participant SCS/AS + + Note left of RAN: UE reachable + UPF->>RAN: 1. Downlink data + Note right of RAN: 2a. RAN Paging + RAN->>UE: 2b. Downlink data + +``` + +Sequence diagram for DL data in CM-CONNECTED mode without extended buffering. Lifelines: UE, RAN, AMF, SMF, UPF, UDM, NEF, SCS/AS. The sequence starts with a 'UE reachable' message from RAN to AMF. Then, '1. Downlink data' is sent from UPF to RAN. A dashed box labeled '2a. RAN Paging' is shown between RAN and UE. Finally, '2b. Downlink data' is sent from RAN to UE. + +**Figure 6.24.4.1.3-1: DL data in CM-CONNECTED mode without extended buffering** + +1. DL data arriving in UPF is forwarded on the N3 towards RAN. +- 2a. If the RRC connection is in RRC Inactive mode, RAN pages the UE. DL data is temporarily buffered in the RAN. If the UE does not respond to paging, e.g. may be temporarily unreachable, the RAN discards the DL data. +- 2b. If the RRC connection is in active mode, or transitions to active mode, the DL data is sent to the UE. + +##### 6.24.4.1.4 DL data in CM-CONNECTED mode with CN Extended buffering + +This procedure shows how DL data in CM-CONNECTED mode with Extended buffering is handled. Extended buffering is used for UE that is using a power saving method (see KI#4). Extended buffering should not be used for a UE which has a monitoring event, 'UE Reachability' or 'Availability after DDN failure', configured. For a UE in RRC inactive mode, the AMF provides buffering related support information to SMF/UPF and downlink data handling. + +The figure shows the Direct Model case. For the Indirect Model case the UPF may be replaced by a UPF-NIMF. + +NOTE 1: This solution assumes eDRX with long sleep cycles with RRC Inactive is supported (see KI#4 and KI#2). + + + +``` + +sequenceDiagram + participant UE + participant RAN + participant AMF + participant SMF + participant UPF + participant UDM + participant NEF + participant SCS/AS + + rect rgb(255, 255, 255) + Note over RAN, UPF: Extended Data buffering is established + RAN->>AMF: 0. N2 notif. + AMF->>SMF: 0. Buffering indication (buffering info) + SMF->>UPF: 0. Buffering indication (buffering info) + end + SCS/AS-->>UPF: 1. Downlink data + Note over UPF: Data buffering + SMF->>AMF: 2. Namf_MT_EnableUEReachability Req + AMF->>RAN: 3. N2 notification + AMF->>SMF: 4. Namf_MT_EnableUEReachability Resp + AMF-->UE: 5a. Paging + Note over UE, UPF: 5. UE contacts the network, e.g., RRC resume + RAN-->>UE: 6. Downlink Data + Note over SMF, UPF: 7. Otherwise if no step 5-6, Data is dropped, after expiration and UE is still not reachable + Note over UE, RAN: 8: RRC Inactive + +``` + +Sequence diagram for DL Data Buffering in SMF/UPF for RRC\_Inactive mode. Lifelines: UE, RAN, AMF, SMF, UPF, UDM, NEF, SCS/AS. The diagram shows the interaction for data buffering when a UE transitions to RRC\_Inactive. A dashed box labeled 'Extended Data buffering is established' covers steps 0 to 4. Step 0: RAN sends N2 notification to AMF with buffering info. Step 1: SCS/AS sends downlink data to UPF. Step 2: SMF sends Namf\_MT\_EnableUEReachability Req to AMF. Step 3: AMF sends N2 notification to RAN. Step 4: SMF sends Namf\_MT\_EnableUEReachability Resp to AMF. Step 5a: AMF sends Paging to UE. Step 5: UE contacts the network (e.g., RRC resume). Step 6: RAN sends Downlink Data to UE. Step 7: A conditional block 'Otherwise if no step 5-6, Data is dropped, after expiration and UE is still not reachable' is shown. Step 8: RAN marks UE as RRC Inactive. + +**Figure 6.24.4.1.4-1: DL Data Buffering in SMF/UPF for RRC\_Inactive mode** + +0. Depending on local configuration, Data Buffering is established when RAN transition a UE using eDRX to RRC\_Inactive state, the RAN sends a N2 Notification to AMF. RAN provides buffering support information if there is any. The AMF notifies SMF/UPF that the PDU session is subject for extended data buffering and includes buffering support info. +1. The application sends downlink data to UPF, and UPF will start to apply extended data buffering when N3 tunnel exists based on the indication received in step 0b above e.g. using the buffering information for the extended buffering. +2. [conditional] The SMF may request UE reachability report via Namf\_MT\_EnableUEReachability, based on notification from UPF which can either be similar to the DDN in CM-IDLE mode or a modification of the existing DDN message. + +The SMF may optionally just wait for the next MO data from UE in step 5 to trigger the sending of downlink data without invoke enabling the UE reachability reporting above. + +3. The AMF may use the N2 Notification procedure to retrieve UE reachability info. If UE is currently in RRC inactive state and not reachable, the RAN may provide new buffering support information, if there is any. RAN schedules a paging at next possible UE paging occasion and marks that a notification to AMF is required when the UE contacts the network next time. RAN also indicates to AMF that it has scheduled a paging for the next possible UE paging occasion. + +NOTE 2: The N2 request message that can trigger the RAN paging can be N2 UE Notification Request. + +4. The AMF notifies the SMF/UPF with the latest reachability info (either UE is reachable or still not reachable with new buffering support information). If the UE is reachable, step 5 is skipped and the procedure continues in step 6. + +- 5a. RAN may perform paging when the UE becomes reachable for paging. +5. When UE contacts with the network, either due to RAN paging or due to a UE triggered procedure before the RAN paging, and the AMF receives either a N2 notification triggered by a RRC resume, or an N2 Path Switch Request if a RRC resume triggers a RAN node change, the AMF notifies the SMF/UPF of the UE reachability. +6. UPF thus can deliver buffered downlink data to UE. +7. If the UE does not contact with the network before expiry of the timer set in the SMF/UPF for the extended buffering duration, the buffered data is discarded in the SMF/UPF. +8. RAN moves the UE to RRC Inactive state after a user inactivity timeout or based on Release Assistance Information if available in Expected UE Behaviour. Depending on sleep cycle length and local configuration the RAN may then execute step 0 above and re-establish the CN extended data buffering in SMF/UPF, otherwise RAN buffering is used at next DL data event. + +#### 6.24.4.2 Notification procedures + +##### 6.24.4.2.1 General + +If SCS/AS selects to send downlink data when UE becomes reachable, it can use one-time UE-Reachability notification (see clause 6.24.4.2.2). SCS/AS may also select the Notification of UE availability after downlink data delivery failure (see clause 6.24.4.2.3). + +If AMF or RAN receives MT control plane signalling for a UE which is not reachable currently, the AMF activates a UE availability notification to the originating NF (see clause 6.24.4.3). + +##### 6.24.4.2.2 Event Subscription and Notification of UE reachability + +If an SCS/AS wants to send downlink packet(s) when UE becomes reachable, the SCS/AS can subscribe for one-time "UE Reachability" monitoring event by following either Event Exposure using NEF specified in TS 23.502 [7] clause 4.15.3 (the figure below is a copy of the figure in TS 23.502 [7] clause 4.15.3.2.3). The SCS/AS sends the packet data when it receives notification that the UE is reachable. + + + +``` + +sequenceDiagram + participant AS + participant NEF + participant UDM + participant AMF + Note right of AMF: [Break] + AS->>NEF: 1. Nnef_EventExposure_Subscribe Request + NEF->>UDM: 2. Nudm_EventExposure_Subscribe Request + UDM->>AMF: 3.a. Namf_EventExposure_Subscribe Request + AMF-->>UDM: 3.b. Namf_EventExposure_Subscribe Response + UDM-->>NEF: 4. Nudm_EventExposure_Subscribe Response + NEF-->>AS: 5. Nnef_EventExposure_Subscribe Response + Note right of AMF: [Break] + AMF->>UDM: 6b. Namf_EventExposure_Notify + UDM->>NEF: 6a. Nudm_EventExposure_Notify + NEF->>AS: 7. Nnef_EventExposure_Notify + +``` + +Sequence diagram illustrating the Event Subscription of UE reachability notification. The diagram shows the interaction between AS, NEF, UDM, and AMF. The AS sends a Nnef\_EventExposure\_Subscribe Request to the NEF. The NEF sends a Nudm\_EventExposure\_Subscribe Request to the UDM. The UDM sends a Namf\_EventExposure\_Subscribe Request to the AMF. The AMF returns a Namf\_EventExposure\_Subscribe Response to the UDM. The UDM returns a Nudm\_EventExposure\_Subscribe Response to the NEF. The NEF returns a Nnef\_EventExposure\_Subscribe Response to the AS. Later, the AMF sends a Namf\_EventExposure\_Notify to the UDM. The UDM sends a Nudm\_EventExposure\_Notify to the NEF. The NEF sends a Nnef\_EventExposure\_Notify to the AS. + +**Figure 6.24.4.2.2-1: TS 23.502 [7]: Event Subscription of UE reachability notification** + +If UE is in CM-CONNECTED and RRC state is unknown (i.e. N2 notification procedure is not activated yet), the AMF shall trigger N2 Notification procedure to retrieve UE reachability information from RAN as shown below ( see also TS 23.502 [7] clause 4.8.3 for details). + + + +``` + +sequenceDiagram + participant SCS/AS + participant AMF + participant RAN + participant UE + participant NEF + participant UPF + participant UDM + participant SMF + + SCS/AS->>AMF: 1. Namf_EventExposure_Subscriber Request + AMF-->>RAN: 2. N2 notification + RAN-->>UE: 3a. paging + Note left of UE: 3b. UE contacts the network, e.g. with RRC resume + RAN-->>AMF: 4. N2 notification (RRC active), Path Switch Request + AMF->>NEF: 5. Namf_EventExposure_Notification + Note right of NEF: 6. Downlink data + UPF-->>UE: + +``` + +Sequence diagram illustrating Event Subscription and Notification for UE reachability. The diagram shows interactions between UE, RAN, AMF, SMF, UPF, UDM, NEF, and SCS/AS. The sequence starts with a Namf\_EventExposure\_Subscriber Request from SCS/AS to AMF. The AMF sends an N2 notification to the RAN. The RAN performs paging (3a) and the UE contacts the network (3b). The RAN sends an N2 notification (RRC active) and Path Switch Request to the AMF. The AMF sends a Namf\_EventExposure\_Notification to the NEF. Finally, downlink data is sent from the UPF to the UE. + +**Figure 6.24.4.2.2-2: Event Subscription and Notification for UE reachability** + +1. Same as the Figure 6.24.4.2.2-1 step 3a, AF (i.e. SCS/AS) subscribe to AMF for UE reachability report through Namf\_EventExposure\_Scubscriber Request service operation, when there is pending DL data towards UE. +2. If UE is in CM connected state, AMF send N2 Notification Request to the RAN to retrieve UE reachability info. If UE is in RRC inactive state and it is not currently reachable, RAN responds back to AMF indicating UE is not reachable. RAN schedules a paging at next possible UE paging occasion and also indicates to AMF that paging is scheduled for the next possible UE paging occasion. RAN marks that a notification to AMF is required when UE contacts the network next time. +- 3a. RAN may perform paging when the UE becomes reachable for paging. +- 3b. UE contacts the network with RRC resume, either due to RAN paging or due to UE triggered procedure before the RAN paging. +4. RAN reports, either a N2 notification, or an N2 Path Switch Request if a RRC resume triggers a RAN node change, to the AMF that UE is RRC connected and reachable. +5. Same as the Figure 6.24.4.2.2-1 step 6b, AMF notifies NEF/AF/SCS/AS that UE is reachable. +6. AF/SCS/AS sends downlink data to UE. + +NOTE: The N2 request message that can trigger the RAN paging can be N2 UE Notification Request. + +**Editor's note:** There are dependencies to KI Power saving. + +If the SCS/AS optionally wants to fine-tune the delivery of the downlink data within the time-window when the UE is reachable, the SCS/AS can configure optional parameters with proper value (as described in clause 6.24.4.5.3). + +##### 6.24.4.2.3 Notification of Availability after DDN failure + +If an SCS/AS wants to get notifications when the UE becomes reachable after a proceeding downlink data delivery failure, the SCS/AS can subscribe for the "Notification of availability after DDN failure" monitoring event. + +This is a different monitoring event from the "UE Reachability" monitoring event specified in 6.24.4.2.2. This information is provided to the AMF at registration through subscription data, see clause 6.24.4.2.4. The AMF notes this and sets a Notify-on-available-after-DDN-failure flag after a DDN failure. If the flag is set when the UE next contacts the network, the serving node notifies the NEF that the UE is reachable and clears the flag. + +An important use case for this feature is the application that wants to communicate with a UE that sleeps for a long time. If downlink packets from the application are not delivered, the application recognizes that the UE is not available by lack of response within a reasonable time from the UE, and then await notification from the network (i.e. from the AMF via the NEF) of UE reachability. + +For UE in CM-IDLE mode, the figure below shows the flow of AMF providing UE availability to NEF/AF after DDN failure. + + + +``` + +sequenceDiagram + participant UE + participant RAN + participant AMF + participant SMF + participant UPF + participant UDM + participant NEF + participant SCS/AS + + Note right of SCS/AS: 1. Downlink data + SCS/AS->>UPF: 1. Downlink data + Note right of UPF: 2. DDN + UPF->>SMF: 2. DDN + Note right of SMF: 3. Namf_comm_N1N2MessageTransfer Req_ + SMF->>AMF: 3. Namf_comm_N1N2MessageTransfer Req_ + Note right of AMF: CM-IDLE not reachable + AMF->>SMF: 4. Namf_comm_N1N2MessageTransfer Res_ + Note right of SMF: 5. DDN Failure + SMF->>UPF: 5. DDN Failure + Note right of AMF: 6. AMF sets a Notify on available after DDN failure + Note right of UE: 7. UE contacts the network, e.g., SR, Registration Req + UE->>RAN: 7. UE contacts the network, e.g., SR, Registration Req + Note right of AMF: 8. Event Exposure + AMF->>NEF: 8. Event Exposure + Note right of AMF: 9. AMF clear Notify on available after DDN failure flag + Note right of SCS/AS: 10. The application chooses to resend data that has been queued. + SCS/AS->>UPF: 11. Downlink data + UPF->>RAN: 11. Downlink data + RAN->>UE: 11. Downlink data + +``` + +Sequence diagram illustrating the notification flow for UE availability after DDN failure in CM-IDLE mode. The diagram shows interactions between UE, RAN, AMF, SMF, UPF, UDM, NEF, and SCS/AS. The process starts with downlink data from SCS/AS to UPF, followed by a DDN message to SMF, then an N1N2 message transfer request from SMF to AMF. The AMF checks UE reachability, finds it unreachable, and responds. The SMF then notifies the UPF of the DDN failure. The AMF sets a 'Notify on available after DDN failure' flag and schedules CN paging. When the UE contacts the network (e.g., SR, Registration Req), the AMF triggers an event exposure to the NEF. The AMF also clears the 'Notify on available after DDN failure' flag. Finally, the application resends data, and the AMF provides downlink data to the UE. + +**Figure 6.24.4.2.3-1: Notification - Availability Notification after DDN Failure (CM-IDLE)** + +1. AMF is provisioned with "Availability Notification after DDN failure" related information during registration (e.g. via UDM), and the application sends downlink data to UPF. + +NOTE 1: See notification parameter provisioning flows in clause 6.24.4.2.4 below. + +2. The UPF sends a Downlink Data Notification (DDN) message to the SMF if there is no N3 tunnel. +3. The SMF initiates Namf\_Comm\_N1N2MessageTransfer\_Reqeust service towards AMF to setup N3 tunnel. +4. The AMF checks the UE reachability in CM-IDLE mode. If UE is not reachable, i.e. due to a power saving method (see KI#4) or paging fails, The AMF send Namf\_Comm\_N1N2MessageTRansfer Response to indicate the failure. +5. The SMF sends DDN failure to UPF and the UPF discards data packets. +6. The AMF shall set the "Notify on availability after DDN failure" flag. The AMF also schedules a CN paging for next possible UE paging occasion. +7. When UE enters CM-CONNECTED mode, the AMF notes that UE is available and that the Notify-on-availability-after-DDN-failure flag for the UE is set. +8. The AMF triggers Namf\_EventExposure\_Notification towards the NEF/Application. +9. The AMF also clears the Notify-on-availability-after-DDN-failure flag for the UE. +10. The application realizes the UE is reachable and re-sends data. + +For UE in RRC-Inactive state where the N3 tunnel exists, RAN can discard the data if UE is not reachable. But it shall indicate to AMF that downlink data is discarded, and AMF shall set the "Notify on availability after DDN failure" flag. At next N2 notification with change to RRC-Connected (assuming N2 notification is already activated during configuration in 6.24.4.2.4) or Patch Switch Request, AMF triggers notification to application. + +The figure below shows the flow of AMF providing UE availability to NEF/AF after DDN failure. + + + +``` + +sequenceDiagram + participant UE + participant RAN + participant AMF + participant SMF + participant UPF + participant UDM + participant NEF + participant SCS/AS + + Note over UE, RAN: UE not reachable as KI#4 (RRC Inactive) + SCS/AS->>UPF: 1. Downlink data + RAN->>AMF: 2. N2 notification (DL Data failure) + Note over AMF: 3. AMF sets a Notify on availability after DDN failure flag + AMF->>NEF: 4. Event Notification + NEF->>SCS/AS: 4. API: Event Notification + RAN->>UE: 5a. Paging Request + UE->>RAN: 5b. UE contacts the network, e.g., RRC resume + RAN->>AMF: (N2 notification or Path Switch Request) + AMF->>NEF: 6. Event Notification + NEF->>SCS/AS: 6. API: Event Notification + UPF->>RAN: 7. Downlink data + RAN->>UE: 7. Downlink data + Note over UE, RAN: 8: RRC Inactive + +``` + +Sequence diagram showing the flow of AMF providing UE availability to NEF/AF after DDN failure. The diagram involves eight lifelines: UE, RAN, AMF, SMF, UPF, UDM, NEF, and SCS/AS. The sequence starts with the UE in an RRC Inactive state. The SMF sends downlink data to the UPF. The RAN checks UE reachability and sends an N2 notification to the AMF. The AMF sets a 'Notify on availability after DDN failure' flag. The AMF sends an event notification to the NEF and SCS/AS. The RAN sends a paging request to the UE. The UE contacts the network (e.g., RRC resume). The AMF sends an event notification to the NEF and SCS/AS. The RAN sends downlink data to the UE. The UE enters RRC Inactive state. + +**Figure 6.24.4.2.3-2: Notification - Availability Notification after DDN Failure (CM-CONNECTED / RRC-Inactive)** + +1. AMF is provisioned with "Availability Notification after DDN failure" related information during registration (e.g. via UDM), and the application sends downlink data to UPF/RAN. + +NOTE 2: See notification parameter provisioning flows in clause 6.24.4.2.4 below. + +2. The RAN check the UE reachability in RRC\_Inactive mode. If UE is not reachable, i.e. due to KI#4 (such as eDRX) or RAN paging fails, RAN sends a N2 Notification to indicate the failure. RAN schedules a RAN paging at next possible UE paging occasion. The RAN also marks that a notification to AMF is required when the UE contacts the network next time The RAN also indicates if RAN paging is scheduled for next possible UE paging occasion. + +NOTE 3: The N2 request message that can trigger the RAN paging can be N2 UE Notification. + +3. The AMF shall set the "Notify on availability after DDN failure" flag. +4. AMF may optionally send an event notification to the NEF and SCS/AS as a confirmation that the DL data in step 1 was received and that an 'Availability after DDN failure' notification will be sent as soon as the UE becomes available. +- 5a. RAN may perform paging when the UE becomes reachable for paging. +- 5b. When UE contacts the network with RRC resume, either due to RAN paging or due to a UE triggered procedure before the RAN paging, the RAN notifies AMF either through N2 notification, or Path Switch Request in case of RRC resume triggering RAN node change). +6. When the AMF receives the notification about UE availability from RAN and the AMF has a Notify-on-availability-after-DDN-failure flag set for the UE (set by step 3), the AMF clears the Notify-on-availability-after-DDN-failure flag for the UE and sends a Namf\_EventExposure\_Notification towards the NEF/AF/SCS/AS. + +7. The application realizes the UE is reachable and re-sends downlink data. +8. RAN moves the UE to RRC Inactive state after a user inactivity. Depending on sleep cycle length and local configuration, RAN may establish CN extended data buffering in SMF/UPF by executing step 0 in clause 6.24.4.1.4 above. Otherwise RAN buffering is used at next DL data event. + +##### 6.24.4.2.4 Configuration for notification related approaches + +###### 6.24.4.2.4.1 General + +For high latency communication, with the UE event notification approach as defined in 6.24.4.2.2 and UE availability notification after DDN failure approach as defined in 6.24.4.2.3 above, AF (e.g. SCA/AS) may need to provide some parameters to serving node (e.g. AMF). Below are 2 different ways of parameters provisioning. + +NOTE: Solutions (e.g. solution 15) for key issue 10, Network Parameter Configuration API via NEF, also cover similar approaches. + +###### 6.24.4.2.4.2 Configuration of notifications via UDM + +The figure below illustrates the procedure of configuring monitoring events parameters at the UDM or the AMF. The procedure is similar to external parameter provisioning in TS 23.502 [7] clause 4.15.6.2 + +The procedure is also used for replacing and deleting a monitoring event configuration. + + + +``` + +sequenceDiagram + participant AF + participant NEF + participant UDM/UDR + participant AMF + participant RAN + Note left of AF: 1. Nnef_ParameterProvision_update Request + AF->>NEF: 1. Nnef_ParameterProvision_update Request + Note right of NEF: 2. Update Request + NEF->>UDM/UDR: 2. Update Request + Note right of UDM/UDR: 3. Update Response + UDM/UDR->>NEF: 3. Update Response + Note left of AF: 4. Nnef_ParameterProvision_update Response + NEF->>AF: 4. Nnef_ParameterProvision_update Response + Note right of UDM/UDR: 5. Nudm_SubscriberDataManagement_UpdateNotification Notify + UDM/UDR-->>AMF: 5. Nudm_SubscriberDataManagement_UpdateNotification Notify + Note right of AMF: 6. N2 Notification + AMF-->>RAN: 6. N2 Notification + +``` + +Sequence diagram illustrating the monitoring event parameters configuration and deletion via UDM procedure. The diagram shows interactions between AF, NEF, UDM/UDR, AMF, and RAN. The steps are: 1. AF sends Nnef\_ParameterProvision\_update Request to NEF; 2. NEF sends Update Request to UDM/UDR; 3. UDM/UDR sends Update Response to NEF; 4. NEF sends Nnef\_ParameterProvision\_update Response to AF; 5. UDM/UDR sends Nudm\_SubscriberDataManagement\_UpdateNotification Notify to AMF; 6. AMF sends N2 Notification to RAN. + +**Figure 6.24.4.2.4.2-1: Monitoring event parameters configuration and deletion via UDM procedure** + +1. AF (SCS/AS) provides one or more configuration parameter(s) related to monitoring even for HLCOM to be updated in Nnef\_ParameterProvision\_UpdateRequest to the NEF. + +The PUI identifies the UE and the Transaction Reference ID identifies the transaction request between NEF and AF (SCS/AS). + +2. If the AF (SCS/AS) is authorised by the NEF to provision the parameters, the NEF requests to update and store the provisioned parameters as part of the subscriber data via Update Request message, the message includes the provisioned data and NEF reference ID. + +If the requester is not authorised to provision data, then the NEF continues in step 4 indicating the reason to failure in Nnef\_ParameterProvision\_Update response. + +3. UDM/UDR resolves the PUI to SUPI and stores the monitoring events parameters as part of the subscription data and responds with Update response message. + +If the SUPI cannot be derived from the PUI, then the Update Response indicates the reason in the cause value. + +4. NEF responds the request with Nnef\_ParameterProvision\_update response. If the procedure failed, the cause value indicates the reason. + +5. UDM/UDR notifies the AMF of the updated subscriber data via Nudm\_SDM\_UpdateNotification Notify message. + +- Based on received configuration parameters related to notifications, the AMF shall trigger the N2 notification procedure to delivery info to RAN (e.g. info related to Notification after DDN failure) and also retrieve the RRC state and reachability info and act accordingly as specified in the notification based approaches, if UE is in CM-CONNECTED mode. + +###### 6.24.4.2.4.3 Configuration directly at AMF + +The current event exposure functionality specified for AMF in TS 23.502 [7] is considered as sufficient for AF to do monitoring related configuration towards AMF via NEF. + +#### 6.24.4.3 Notification of Availability after MT control plane signalling + +The intention with this procedure is to describe how MT CP signalling is handled when CM-CONNECTED with RRC\_INACTIVE is used in combination with eDRX with long sleep cycles. The handling can be applied by other procedures such as MT SMS, NW initiated NAS signalling etc. Briefly RAN returns a NAS-Non-delivery notification back to AMF (indicating UE is unreachable). RAN and AMF remember the unreachability state and RAN reports to AMF at next RRC resume. + +If the network invokes any MT control plane signalling delivery to a UE when UE is not reachable due to a power saving state (e.g. MICO, eDRX etc), the AMF activates a UE availability notification to the originating NF. + +For UE in CM-IDLE mode, the figure below shows the flow of AMF providing UE availability to NF after MT control plane signalling delivery failure. + + + +``` + +sequenceDiagram + participant SMF + participant AMF + participant RAN + participant UE + participant SMF as SMF + Note right of SMF: 1. Namf_Communication_N1N2MessageTransfer() + SMF->>AMF: 1. Namf_Communication_N1N2MessageTransfer() + Note right of AMF: 2. Namf_Communication_N1N2MessageTransfer response (cause) + AMF-->>SMF: 2. Namf_Communication_N1N2MessageTransfer response (cause) + Note right of AMF: 3. paging Request + AMF-->>RAN: 3. paging Request + RAN-->>UE: 3. paging Request + Note left of UE: 4. UE contacts the network, e.g., Service Request + UE->>RAN: 4. UE contacts the network, e.g., Service Request + Note right of RAN: 5. Event Notification + RAN->>AMF: 5. Event Notification + Note right of AMF: 6. Namf_Communication_N1N2MessageTransfer() + AMF-->>SMF: 6. Namf_Communication_N1N2MessageTransfer() + +``` + +Sequence diagram illustrating the notification process for UE availability after MT control plane signalling failure in CM-IDLE mode. The diagram shows interactions between UE, RAN, AMF, SMF, UPF, UDM, NEF, and SCS/AS. + +**Figure 6.24.4.3-1: Notification - Availability Notification after MT control plane signalling failure (CM-IDLE)** + +- Any NF, e.g. SMF, in 5GC may trigger MT control signalling to UE through Namf\_Communication\_N1N2MessageTransfer Service Operation (). The N1N2TransferFailure Notification Target Address is included to subscribe to unreachability event in step 5. The MT control signalling may for example be SMF that triggers MT control signalling due to DL data. +- If the UE is currently not reachable due to a power saving method (see KI#4), the AMF returns a Namf\_Communication\_N1N2TransferFailureNotification with cause to indicate power saving as the failure and indicate that AMF will send a notification as soon as the UE becomes reachable. If the UE is currently not doing power saving, the AMF initiates the network triggered service request procedure and responds to the consumer NF with a result indication, If the AMF detects that the UE fails to respond to paging, the AMF invokes the Namf\_Communication\_N1N2TransferFailureNotification to indicate the failure to the consumer NF with a result + +indication and indicate that AMF will send a notification as soon as the UE becomes reachable. The AMF sets the "Notify on availability after MT control plane signalling failure" flag if not already set and schedules a CN paging if not MICO mode and if not already scheduled. The AMF remembers the NF to notify. + +3. When eDRX is used, the AMF may perform paging when the UE becomes reachable i.e. in PTW. +4. When UE enters CM-CONNECTED mode, either due to AMF paging or due to a UE triggered procedure before the paging, the AMF notes that UE is available and that the Notify on availability after MT control plane signalling flag for the UE is set. +5. The AMF triggers Namf\_EventExposure\_Notify service towards the corresponding NF(s) in step 1/2. The AMF also clears the "Notify on availability after MT control plane signalling failure" flag for the UE. +6. The NF realizes that the UE is reachable and re-sends the control plane signalling if needed. + +For UE in RRC-Inactive state where the N2 connection exists, the RAN can indicate the non NAS delivery due to UE not reachable. And the AMF shall set the "Notify on availability after MT control signalling" flag. At next UE contact to network, AMF is notified and triggers a notification towards corresponding NF. + +The figure below shows the flow of AMF providing UE availability to NF after MT control plane signalling delivery failure in RRC inactive state. + + + +``` + +sequenceDiagram + participant SMF + participant AMF + participant RAN + participant UE + participant NEF + Note left of UE: UE not reachable as KI4 (RRC Inactive) + SMF->>AMF: 1. Namf_Communication_N1N2MessageTransfer() + AMF-->>RAN: 2. N2 NAS non delivery (cause + info) + RAN-->>AMF: 3. Namf_Communication_N1N2MessageTransfer response (cause) + Note right of AMF: 3.AMF sets a Notify on availability after MT CP signaling failure + AMF-->>UE: 4. Paging Request + Note left of UE: 5. UE contacts the network, e.g., RRC resume, Path Switch Request + AMF->>SMF: 6. Event Notification + AMF-->>SMF: 7. Namf_Communication_N1N2MessageTransfer() + Note left of UE: 8: RRC Inactive + +``` + +Sequence diagram illustrating the notification process for MT control plane signalling failure in RRC inactive state. The diagram shows interactions between UE, RAN, AMF, SMF, UPF, UDM, NEF, and SCS/AS. The process starts with the UE in an RRC Inactive state. The SMF sends a Namf\_Communication\_N1N2MessageTransfer() request to the AMF. The AMF sends an N2 NAS non-delivery message (cause + info) to the RAN. The RAN responds with a Namf\_Communication\_N1N2MessageTransfer response (cause). The AMF then sets a 'Notify on availability after MT CP signaling failure' flag. The AMF sends a Paging Request to the UE. The UE contacts the network (e.g., RRC resume, Path Switch Request). The AMF sends an Event Notification to the SMF. The AMF sends a Namf\_Communication\_N1N2MessageTransfer() response to the SMF. Finally, the UE enters RRC Inactive state. + +**Figure 6.24.4.3-2: Notification - Availability Notification after MT control plane signalling failure (CM-CONNECTED / RRC-Inactive)** + +1. Any NF, e.g. SMF, in 5GC may trigger MT control signalling to UE through Namf\_Communication\_N1N2MessageTransfer Request () (event subscription parameters may be included in case the UE is not reachable) and AMF sends N2 Downlink NAS transport to RAN if AMF considers the UE in CM-CONNECTED mode. The MT control signalling may for example be SMF that triggers MT control signalling due to DL data. +2. The RAN checks the UE reachability if UE is in RRC\_Inactive state. If UE is not reachable, i.e. due to KI#4 (such as eDRX) or if RAN paging fails, the RAN sends a NAS non-delivery message to AMF to indicate the failure. If UE is not reachable due to eDRX, the RAN schedules RAN paging for the next possible UE paging occasion (if not already scheduled). and includes an indication to AMF that a paging has been scheduled. The RAN marks that a notification to AMF is required when the UE contacts the network next time. + +NOTE: The N2 request message that can trigger the RAN paging can be N2 UE Notification Request. + +3. AMF sends Namf\_Communication\_N1N2messageTransfer Response to the corresponding NF in step 1 and indicating that AMF will send a notification as soon as the UE becomes reachable. The AMF sets the "Notify on availability after MT control plane signalling failure" flag if not already set. The AMF remembers the NF to notify. +4. RAN may perform paging when the UE becomes reachable i.e. in PTW. +5. When UE contacts the network with RRC resume, either due to RAN paging or due to a UE triggered procedure before the RAN paging, the RAN notifies AMF (either through N2 notification, or Path Switch Request in case of RRC resume triggering RAN node change). +6. When the AMF receives the notification about UE availability from RAN and the AMF has a "Notify on availability after MT control plane signalling failure" flag set for the UE (set by step 3), the AMF sends Namf\_EventExposure\_Notification towards the corresponding NF(s) in step 3 and clears the "Notify on availability after MT control plane signalling failure" flag for the UE. +7. The NF realizes the UE is reachable and re-sends the MT signalling. +8. RAN moves the UE to RRC Inactive state. + +### 6.24.5 Impacts on existing entities and interfaces + +#### AMF: + +- Based on UE power saving state info, and optionally configuration parameters from UDM, providing DL data buffering information to SMF. +- Providing/Retrieving necessary information to/from RAN through N2 procedure (e.g. new N2 notification trigger to request to RAN to notify the AMF when the UE becomes reachable) to support providing DL data buffering information to SMF for UE in RRC\_INACTIVE/CM-CONNECTED. +- Event notification to SMF/UPF/NEF with UE reachability, and event activation after subscription or DDN failure or signalling failure. +- Paging scheduling based on UE power saving info. +- Notification related parameter configuration from UDM. + +#### SMF: + +- Forwards part of the policy information to AMF to help it deciding whether extended buffering needs to be applied or not. +- Parameter configuration from UDM, if it's deployed. +- Buffers downlink data based on the buffering info received from the AMF, if SMF buffering is applied. +Support of new Namf\_MT\_EnableUEReachability procedure for RRC\_INACTIVE/CM-CONNECTED (only applies for the CN extended buffering). +- New request to UPF to buffer data even when N3 is still active (only applies for the CN extended buffering). + +#### UPF: + +- Buffers downlink data based on the buffering info received from the SMF, if UPF buffering is applied. +- Support of buffering data when N3 is active (only applies for the CN extended buffering). +- Support of new Namf\_MT\_EnableUEReachability procedure for RRC\_INACTIVE/CM-CONNECTED (only applies for the CN extended buffering). + +#### UDM: + +- Pass configuration info to AMF (or SMF). +- Subscriber event request to AMF (or SMF). + +#### NEF: + +- Receives configuration from the AF and passes to the UDM. + +#### RAN: + +- Provide RRC inactive related info to CN, if RRC inactive is applied. +- Data buffering if RRC inactive without power saving state or if limited power saving time. +- RAN paging with extended unreachable cycles. +- Enhanced N2 notification procedure to indicate to CN that the UE is unreachable/reachable in RRC\_INACTIVE/CM-CONNECTED. + +#### UE: + +- Extended DRX in CM-CONNECTED with RRC-INACTIVE. + +### 6.24.6 Evaluation + +The solution proposes the notification procedure triggered by UE Reachability event or Availability after DDN failure event. The notification procedure for the UE in CM-CONNECTED with RRC\_INACTIVE state is also proposed. The proposed notification procedure is based on the same principles as the notification procedure for HLCOM in EPC, and addresses the Architectural requirements of key issue 3 to "Provide the AF (i.e. SCS/AS) with UE status information (e.g. reachability notification or the time when the UE is expected to be reachable)". + +The solution covers two different ways for SCS/AS to use for handling of "sleeping devices" i.e. high latency communications: a) extended buffering, and b) availability notifications. + +a) Extended buffering is provided differently depending on CM state and sleep cycle length: + +- CM-IDLE: An EPS like CN extended buffering made in UPF or in SMF depending on local configuration. +- CM-CONNECTED with RRC\_INACTIVE: Two options a) CN extended buffering made in UPF/SMF or b) no CN extended buffering i.e. buffering in RAN. + +b) Availability notifications: + +- UE Reachability Notification for CM-IDLE mode and for CM-CONNECTED with RRC\_INACTIVE. +- Availability Notification after DDN failure for CM-IDLE mode and for CM-CONNECTED with RRC\_INACTIVE. + +The solution also provides a way for the AF to provide configuration parameters to AMF (or SMF) through NEF/UDM in case UE Reachability notification or Availability Notification after DDN failure are used. + +The drawback with CN extended buffering and availability notifications for RRC\_INACTIVE and eDRX with sleep cycles longer than the NAS retransmission timer is that it requires to replicate CM-IDLE behaviour for CM-CONNECTED mode fully (for CN extended buffering) or partially (for availability notifications). + +## 6.25 Solution 25: HLCom buffering and event notification support for CM-IDLE + +### 6.25.1 Introduction + +This solution applies to Key issue 3: High Latency Communication, for the case of extended data buffering at the UPF for mobile terminated user plane data packets while the UE is unreachable and also support AF notifications. + +### 6.25.2 Functional Description + +The following principles apply: + +- When the SMF receives a Data Notification message or downlink data packet from UPF, the SMF determines whether Extended Buffering applies for the downlink packet or not, based on: + +- Policy information received from the PCC, which contains: + - For the PDU session whether Extended Buffering is enabled. +- Whether the selected UPF supports extended buffering. + +If it applies, the SMF including an "Extended buffering applies" indication in Namf\_Communication\_N1N2MessageTransfer. + +- Whenever an AMF receives a Namf\_Communication\_N1N2MessageTransfer including an "Extended buffering applies" indication from the SMF for a UE that is temporarily unreachable due to power saving function as per Key issue 4, the AMF replies with Namf\_Communication\_N1N2MessageTransfer Response indicating the UE is unreachable, and a Maximum estimated wait time for the UE to become reachable. The AMF stores an indication that MT data may be pending for the UE (this indication may be used for power saving solutions). + +NOTE: How the AMF determines the Maximum estimated wait time for the UE to become reachable depends on the power saving solution to be determined in Key issue 4. + +- If the AMF replies with Namf\_Communication\_N1N2MessageTransfer Response indicating the UE is unreachable, and a Maximum estimated wait time for the UE to become reachable, SMF decides the extended buffering time. +- If extended buffering is applied at UPF, SMF sends Failure indication with an indication to the UPF to buffer the downlink data packet Extended Buffering time to the UPF. The SMF may also indicate to the UPF to stop sending Data Notifications while the Extended buffering timer is running. +- When the UPF receives a Failure Indication with extended buffering time, the UPF buffers the DL data packet and initiates an extended buffering timer with the received value. If the extended buffering timer expires the UPF drops the DL data packet. +- PCC provides the Policy information for extended buffering to the SMF during Session Management Policy Establishment/Modification. + +### 6.25.3 Support of EPC interworking + +Interworking between 5GS and EPC is achieved by a combined P-GW-U+UPF. If a UPF has data buffered for a UE when the UE moves to EPC and becomes reachable then buffered data will get delivered in EPC (and vice versa). + +### 6.25.4 Procedures + +#### 6.25.4.1 Extended data buffering at UPF + +Figure 6.25.4.1-1 shows the call flow for extended data buffering at the UPF for user plane mobile terminated data. + + + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant AMF + participant SMF + participant UPF + + Note left of UE: 0. UE is in CM-IDLE and unreachable as per Key Issue 4: Power Saving Functions + Note right of UPF: 1. Data + UPF->>SMF: 2. Data Notification + SMF-->>UPF: 2b. Data Notification ACK + SMF-->>UPF: 2c. Downlink data + Note right of SMF: 3. Determines Extended Buffering Is Available + SMF->>AMF: 4. Namf_Communication_N1N2MessageTransfer ("Extended Buffering Available") + Note left of AMF: 5. Determines UE temporarily Unreachable + AMF->>SMF: 6. Namf_Communication_N1N2MessageTransfer Response (Unreachable, Estimated Max wait time) + SMF->>UPF: 7. Failure indication (Extended Buffer time) + Note right of UPF: 8. Buffer data packet, start extended buffer time + Note over UE, UPF: 9a. UE moves to CM-Connected as per Key issue 4: Power Saving Functions + Note right of UPF: 9a. UPF sends DL data + Note over UE, UPF: 9b. MT data transport via NAS-SM in clause 6.1.4.3 + Note right of UPF: 9c. Extended buffer time expires, UPF drops data packet + +``` + +Sequence diagram illustrating Extended buffering at UPF for mobile terminated user plane data. The diagram shows interactions between UE, NG-RAN, AMF, SMF, and UPF. The process starts with the UE in CM-IDLE and unreachable. The UPF receives data and notifies the SMF. The SMF determines if extended buffering is available and informs the AMF. The AMF determines the UE is temporarily unreachable and informs the SMF. The SMF sends a failure indication to the UPF. The UPF buffers the data packet. When the UE moves to CM-Connected, the UPF sends the DL data. The MT data transport via NAS-SM occurs. Finally, the extended buffer time expires, and the UPF drops the data packet. + +**Figure 6.25.4.1-1: Extended buffering at UPF for mobile terminated user plane data** + +1-2b. As per current Network Triggered Service Request defined in TS 23.502 [7], clause 4.2.3.3, steps 1 to 3a. + +2c. For the PDU session established to support small data transfer via NAS transmission, UPF sends the received downlink data to the SMF. + +3. The SMF determines whether Extended Buffering is available for the received downlink packet or not, based on: + +- Policy information received from the PCC, which contains: + - For the PDU session whether Extended Buffering is enabled. + - Whether the selected UPF supports extended buffering. + - Subscription information for the UE. + +4. The SMF includes "Extended buffering available" indication in Namf\_Communication\_N1N2MessageTransfer. + +5. The AMF determines the UE is temporarily unreachable due to power saving function (see Key issue 4). + +6. The AMF replies with Namf\_Communication\_N1N2MessageTransfer Response with a rejection indicating the UE is not reachable due to power saving function, and a Maximum estimated wait time for the UE to become reachable. The AMF stores an indication that there may be MT data pending for the UE. + +NOTE 1: How the AMF determines the Maximum estimated wait time for the UE to become reachable depends on the power saving solution to be determined in Key issue 4. + +As per currently specified in TS 23.502 [7], the AMF may include in the reject message an indication that the SMF needs not send DL data notifications to the AMF, if the SMF has not subscribed to the event of the UE reachability. The AMF stores an indication that the SMF has been informed that the UE is not reachable. + +7. If the AMF replied with Namf\_Communication\_N1N2MessageTransfer Response indicating the UE is unreachable due to power saving function, and a Maximum estimated wait time for the UE to become reachable, and if the SMF had determined that Extended Buffering applies, the SMF sends Failure indication with an indication to the UPF to buffer the downlink data packet Extended Buffering time and optionally a DL Buffering Suggested Packet Count to the UPF. The SMF may also indicate to the UPF to stop sending Data Notifications while the Extended buffering timer is running. + +NOTE 2: The DL Buffering Suggested Packet Count is derived from the subscription information which is provided by the SCS/AS via T8 API. + +**Editor's note: Whether the AMF or SMF determines the DL Buffering Suggested Packet Count is FFS.** + +8. The UPF based on SMF indication buffers the data packet and starts an Extended buffering timer. +- 9a. If the UE moves to CM-CONNECTED before the extended buffering timer expires, the UPF sends the buffered downlink data packet(s). +- 9b. If the PDU session is established for Data over NAS, the MT data is transmitted as described in clause 6.1.4.3. +- 9c. If the Extended buffering timer expires, the UPF drops the buffered data packets. + +#### 6.25.4.1A Extended data buffering at NEF + +The same principle of clause 6.25.4.1 applies to DL data buffered in the NEF in case of data transfer via APIs. For data transfer via NEF, the NEF uses the same interactions with the SMF as the UPF uses in Figure 6.25.4.1-1. + +#### 6.25.4.2 AF notification from AMF + +##### 6.25.4.2.1 General + +The AF may select to send data to the UE only when the UE is available. Availability for the UE would depend on the power saving scheme that the UE is using. For example, if the UE is using MICO, then an availability indication is sent when the UE transitions to CM-CONNECTED state due to MO data or other mobile originated signalling e.g., Registration update. For UEs in eDRX, availability may be triggered just prior to the Paging Time Window (PTW) of the UE. + +If AMF receives MT control plane signalling for a UE which is in CM-IDLE, the AMF activates a UE availability notification to the originating NF (see clause 6.24.4.3). + +##### 6.25.4.2.2 Event Subscription of UE reachability + +If an AF (or AS) wants to send downlink packet(s) when UE becomes reachable, the AF can subscribe for one-time "UE Reachability" monitoring event by following Event Exposure using NEF specified in TS 23.502 [7] clause 4.15.3.2.3. The AF sends DL data when it receives notification that the UE is reachable. + +##### 6.25.4.2.3 MT data transfer with Notification of UE availability + +The procedure for MT data transfer with UE reachability information is shown in Figure 6.25.4.2.3-1. + + + +``` + +sequenceDiagram + participant AF + participant AMF + participant SMF + participant UDM + participant NEF + participant UPF + + Note right of AF: 1. AF receives data to be sent to UE + AF->>AMF: 2. Subscribe to UE reachability event + Note left of AMF: 3. AMF determines UE is reachable based on power save scheme + AMF->>NEF: 4. Namf_EventExposure_Notify + NEF->>AF: 5. Nnef_EventExposure_Notify + Note over AMF, SMF, UDM, NEF, UPF: 6. Data is sent from the AF to UE (either over CP or UP) + +``` + +Sequence diagram illustrating the procedure for MT data transfer with UE monitoring. The diagram shows interactions between AMF, SMF, UDM, NEF, UPF, and AF. The sequence starts with the AF receiving data to be sent to the UE. The AF then subscribes to a UE reachability event. The AMF determines the UE is reachable based on a power save scheme. The AMF then notifies the NEF via Namf\_EventExposure\_Notify. The NEF then notifies the AF via Nnef\_EventExposure\_Notify. Finally, the data is sent from the AF to the UE, either over the CP or UP. + +**Figure 6.25.4.2.3-1: Procedure for MT data transfer with UE monitoring** + +1. AF has data to be sent to the UE. +2. AF subscribes to one-time "UE Reachability" monitoring event using steps 1 to 4 specified in TS 23.502 [7] clause 4.15.3.2.3. +3. AMF determines that UE is reachable based on the UE power save scheme. For example, MO data or PTW in case of eDRX. +4. AMF uses Step 6b of procedure in in TS 23.502 [7] clause 4.15.3.2.3 to notify the NEF. +5. NEF uses Step 7 of procedure in in TS 23.502 [7] clause 4.15.3.2.3 to notify the AF. +6. AF sends data for delivery to the UE. + +##### 6.25.4.2.4 Event Subscription of "Availability Notification after DDN Failure" + +The AF can subscribe the "Availability Notification after DNN Failure" monitoring event using NEF specified in TS 23.502 [7] clause 4.15.3.2.3. AMF sets a Notify-on-available flag after a DDN failure or the "UE is unreachable" monitoring event. If the flag is set when the UE next contacts the network, the AMF notifies the NEF that UE is reachable and then NEF informs AF UE is reachable. + +##### 6.25.4.2.5 Notification about "Availability Notification after DDN Failure" + +The Notification of "Availability Notification after DDN Failure" for CM\_IDLE mode is described in Figure 6.24.4.2.3-1 in clause 6.24.4.2.3 + +#### 6.25.4.3 AF notification from SMF + +##### 6.25.4.3.1 Application Notification overall procedure + +Figure 6.25.4.3.1-1 describes the Application Notification about Extended buffering procedure. + + + +``` +sequenceDiagram + participant UE + participant gNB + participant AMF + participant SMF + participant UPF + participant NEF + participant PCF + participant SCS/AS + + Note over all: 0. PDU Session Establishment to the DNN + SMF->>UPF: 1. AF requests monitoring data delivery status + UPF->>SMF: 2. Downlink data + Note over AMF, UPF: 3. Extended buffering in UPF as described in clause 6.25.4.1 + Note over SMF, UPF: 4. UPF pending DL data + Note over SMF, SCS/AS: 5. Monitoring report procedure + Note over SCS/AS, UPF: 6. Application buffered DL data or send DL data according to received report. +``` + +Sequence diagram illustrating the Application Notification about HLCom Extended buffering procedure. The diagram shows interactions between UE, gNB, AMF, SMF, UPF, NEF, PCF, and SCS/AS. The steps are: 0. PDU Session Establishment to the DNN; 1. AF requests monitoring data delivery status (SMF to UPF); 2. Downlink data (UPF to SMF); 3. Extended buffering in UPF as described in clause 6.25.4.1 (UPF to AMF); 4. UPF pending DL data (UPF to SMF); 5. Monitoring report procedure (SMF to SCS/AS); 6. Application buffered DL data or send DL data according to received report (SCS/AS to UPF). + +**Figure 6.25.4.3.1-1 Application Notification about HLCom Extended buffering procedure** + +0. UE establishes a PDN connection to the DNN. +1. SCS/AS monitors data delivery status to the 5GC, more details are described in clause 6.25.4.3.2. +2. DL data is arrived in UPF. +3. HLCom Extended buffering in UPF is performed as described in clause 6.25.4.1. +4. UPF pending the DL data as the received information from SMF. +5. SMF sends the monitoring report to SCS/AS, more details are described in clause 6.25.4.3.3. +6. SCS/AS may buffer the DL data or send the DL data according to the received monitoring report. + +##### 6.25.4.3.2 Event subscription for data delivery status + +Figure 6.25.4.3.2-1 is the event subscription procedure for data delivery status of DL data transmission from SCS/AS. + + + +``` +sequenceDiagram + participant SCS/AS + participant NEF + participant PCF + participant SMF + Note right of SCS/AS: 1. Nnef_EventExposure_Subscribe Request + SCS/AS->>NEF: 1. Nnef_EventExposure_Subscribe Request + Note right of NEF: 2. Npcf_EventExposure_Subscribe request + NEF->>PCF: 2. Npcf_EventExposure_Subscribe request + Note right of PCF: 3. Nsmf_EventExposure_Subscribe request + PCF->>SMF: 3. Nsmf_EventExposure_Subscribe request + Note right of SMF: 4. Nsmf_EventExposure_Subscribe Response + SMF->>PCF: 4. Nsmf_EventExposure_Subscribe Response + Note right of PCF: 5. Npcf_EventExposure_Subscribe response + PCF->>NEF: 5. Npcf_EventExposure_Subscribe response + Note right of NEF: 6. Nnef_EventExposure_Subscribe Response + NEF->>SCS/AS: 6. Nnef_EventExposure_Subscribe Response +``` + +Sequence diagram showing the event subscription procedure for data delivery status between SMF, PCF, NEF, and SCS/AS. + +**Figure 6.25.4.3.2-1: Event subscription procedure for data delivery status** + +1. SCS/AS sends Nnef\_EventExposure\_Subscribe Request to NEF requesting data delivery status. The IP Filter information is included in the message to identify the IP PDU traffic or the Ethernet packet filter. The monitoring events may include: + - Packet(s) in extended buffering and Expected wait time. + - Packet(s) discarded. + - Packet(s) transmitted. +2. NEF sends the Npcf\_EventExposure\_Subscribe Request to PCF. IP Filter information, monitoring event received from step 1 are included in the message. +3. PCF sends the Nsmf\_EventExposure\_Subscribe Request (NEF ID, Monitoring Event) message to the SMF which is served the PDN connection to SCS/AS. +4. SMF sends the Nsmf\_EventExposure\_Subscribe Response message to PCF. +5. PCF send sends the response message to NEF. +6. NEF sends the response to SCS/AS. + +##### 6.25.4.3.3 Monitoring report procedure for data delivery status + +This procedure, shown in Figure 6.25.4.3.3-1, informs the AF if the UE is not reachable and Extended DL data buffering is applied, or if UE becomes reachable after the Extended buffering has been applied. SMF sends the monitoring report to SCS/AS. + + + +``` + +sequenceDiagram + participant SMF + participant PCF + participant NEF + participant SCS/AS + + Note left of SMF: 0. UE unreachable + Note left of SMF: 1. Extended Buffering event + SMF->>NEF: 2. Nsmf_EventExposure_Notify (Extended Buffering event) + NEF->>SCS/AS: 3. Nnef_EventExposure_Notify (Extended Buffering event) + Note over SMF, SCS/AS: 4. UE enters connected mode, CN delivers buffered packets + SMF->>NEF: 5. Nsmf_EventExposure_Notify (Extended Buffering event) + NEF->>SCS/AS: 6. Nnef_EventExposure_Notify (Extended Buffering Event) + +``` + +Sequence diagram illustrating the Monitoring report procedure. Lifelines: SMF, PCF, NEF, SCS/AS. The process starts with the UE being unreachable (0) and an extended buffering event occurring (1). The SMF sends an Nsmf\_EventExposure\_Notify (Extended Buffering event) to the NEF (2), which then forwards it to the SCS/AS (3). A dashed line separates this from the next phase where the UE enters connected mode and buffered packets are delivered (4). After this, the SMF sends another Nsmf\_EventExposure\_Notify (Extended Buffering event) to the NEF (5), which again forwards it to the SCS/AS (6). + +**Figure 6.25.4.3.3-1: Monitoring report procedure** + +0. The UE is unreachable. +1. When the SCS/AS sends a downlink packet, the SMF determines that extended buffering applies. +2. SMF sends the Nsmf\_EventExposure\_Notify (Extended Buffering event) message to NEF. The following parameters may also be included according to the monitoring events in clause 6.25.4.3.2: + - Packet(s) in extended buffering; and + - Expected wait time; and + - DL Buffering Suggested Packet Count. +3. NEF transfers the Nnef\_EventExposure\_Notify to SCS/AS. The information about packet(s) in extended buffering allows the SCS/AS to not perform retransmission. The expected wait time indicates the expected pending time before the buffered packet(s) can be transmitted, i.e. before UE becomes reachable. + +The DL buffering suggested packet count indicates the expected maximum amount of data packets that will be buffered in the network. The SCS/AS may buffer the DL data or send the DL data according to the expected wait time and the DL buffering suggested packet count. + +NOTE: The DL Buffering Suggested Packet Count modified by the SMF is exposed towards the SCS/AS. + +4. If DL data transmission becomes available, for example, UE enters connected mode, CN delivers the buffered downlink packet(s), step 5 and step 6 are perform. +5. SMF sends the Nsmf\_EventExposure\_Notify (Extended Buffer event) message to NEF. The following parameter is included: + - Packet(s) have been transmitted. +6. NEF sends the Nnef\_EventExposure\_Notify (Extended Buffer event) message to SCS/AS. + +If at any point in time the CN drops the buffered packets, the SMF initiates the Nsmf\_EventExposure\_Notify (Extended Buffer event) procedure indicating Packet(s) discarded. + +### 6.25.5 Impacts on existing entities and interfaces + +#### PCC: + +- Management of Policies for extended buffering per PDU session. +- Provide policy information for extended buffering to SMF. +- Support event exposure for the Monitoring event from NEF. + +#### UPF: + +- Support extended buffering as requested by SMF (for data via N6). + +#### SMF: + +- Receive policies from PCF. +- Determine whether extended buffering applies, supported extended buffering for DL data or provide request for extended buffering to UPF. +- Support event exposure for the monitoring event from PCF. + +#### AMF: + +- Provide Estimated Maximum wait time to SMF. + +#### NEF: + +- Support extended buffering as requested by SMF (for data via APIs). + +### 6.25.6 Evaluation + +The solution proposes extended buffering and event notification for high latency communication. The SMF determines whether Extended Buffering applies for the downlink packet or not based on the policy information from the PCC and UPF capability. In addition, two notification procedures towards the AF are proposed: AF notification from AMF, including the "UE Reachability" event and "Availability Notification after DDN Failure" event; AF notification from SMF, i.e. the "Extended Buffering" event. + +The solution addresses the architectural requirements of key issue 3 to "provide the AF (i.e. SCS/AS) with UE status information (e.g. reachability notification or the time when the UE is expected to be reachable)", and "Send DL data to UEs at the earliest possible opportunity when the UEs are applying power saving functions". + +## 6.26 Solution 26: Expected UE Behaviour provisioning for CIoT + +### 6.26.1 Introduction + +This solution addresses Key Issue #13 (Support for Expected UE Behaviour), and partially addresses Key Issue #4 (Power Saving Functions) as well as Key Issue #3 (High Latency Communication) and indicates which parameters, among the Communication Parameters defined in TS 23.682 [6], shall be re-used for 5GC, investigating their relevance and analysing how they can be provided to the AMF and/or the SMF. + +This solution proposes that some of the Communication Pattern parameters defined in TS 23.682 [6] clause 5.10.1 are provided to 5GC to optimize the resource usage for CIoT. More specifically, the parameters to be used for 5GS are described in Table 6.26.1-1 below. The differences between the EPS Communication Pattern parameters and those proposed for 5GS are: + +1. The *Expected UE Moving Trajectory* (which is not present in TS 23.682 [6] but is described in TS 23.502 [7]) is added to the list of parameters. +2. The *Periodic Communication Indicator* is not needed because it can be implicitly inferred by the usage of the *Periodic Time*. + +3. The *Communication Duration Time* has been generalized to be applicable not only to periodic communication. In this proposal it indicates for how long the UE will normally stay in CM-Connected for data transmission, independently of whether the communication is periodic or not. +4. The *Scheduled Communication Type* (which is not present in TS 23.682 [6]) is added to the list of parameters. +5. The *Traffic Profile* (see TS 23.682 [6]) is added to the list of parameters. + +**Table 6.26.1-1: Description of parameters for Expected UE Behaviour** + +| Expected UE Behaviour parameter | Description | +|----------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Expected UE Moving Trajectory | Identifies the UE's expected geographical movement.
Example: A planned path of movement.
[optional] | +| Stationary Indication (see TS 23.682 [6] clause 5.10.1) | Identifies whether the UE is stationary or mobile
[optional] | +| Communication Duration Time (see TS 23.682 [6] clause 5.10.1) | Indicates for how long the UE will normally stay in CM-Connected for data transmission.
Example: 5 minutes.
[optional] | +| Periodic Time (see TS 23.682 [6] clause 5.10.1) | Interval Time of periodic communication
Example: every hour.
[optional] | +| Scheduled Communication Time (see TS 23.682 [6] clause 5.10.1) | Time and day of the week when the UE is available for communication.
Example: Time: 13:00-20:00, Day: Monday.
[optional] | +| Battery Indication (see TS 23.682 [6] clause 5.10.1) | Identifies power consumption criticality for the UE: if the UE is battery powered with not rechargeable/not replaceable battery, battery powered with rechargeable/replaceable battery, or not battery powered.
[optional] | +| Traffic Profile (see TS 23.682 [6]) | Identifies the type of data transmission: single packet transmission (UL or DL), dual packet transmission (UL with subsequent DL or DL with subsequent UL), multiple packets transmission
[optional] | +| Scheduled Communication Type | Indicates that the Scheduled Communication Type is Downlink only or Uplink only or Bi-directional [To be used together with Scheduled Communication Time]
Example:
[optional] | + +### 6.26.2 Functional Description + +It shall be possible to provide the parameters for CIoT in Table 6.26.1-1 to the AMF and/or to the SMF. The reasons are as follows: + +- *Expected UE Moving Trajectory* and *Stationary Indication*, to configure the UE with e.g. a Registration Area (TA-list) that includes the TA(s) along the Expected UE Moving Trajectory. These parameters can be used by the AMF and SMF. +- *Communication duration time*, to be used for inferring the end time of the communication. The end time could be used to initiate the transition from CM-CONNECTED to CM-IDLE state. With this value, the SMF can trigger the PDU Session deactivation, and then if there is no more activated PDU session(s) to the UE, the AMF can trigger AN release. This parameter can be used by both the AMF and the SMF. +- *Periodic time*, to be used for determining mobility management parameters, such as determining the periodic time of registration update so as to save the signalling. Moreover, the SMF can manage the buffering time for downlink data to the UE, e.g., in the case of UE is in MICO mode which has periodic communication parameter, the SMF expects the UE is supposed to be reachable in the time of periodic communication. This parameter can be used by both the AMF and the SMF. + +- *Scheduled communication time*, to be used for determining MICO mode UE so as to save energy consumption of some specific devices. Moreover, the SMF can determine the inactivity for a certain PDU session, or trigger the PDU Session release procedure when the time expires and no ongoing traffic for such PDU session. This parameter can be used by both the AMF and the SMF. +- *Scheduled communication type*, to be used for indicating that the scheduled communication time is DL only or UL only or bi-directional. It may be used together with the *Scheduled communication time*. This parameter can be used by both the AMF and the SMF along with the *Scheduled communication time*. +- *Traffic Profile*, to be used for indicating how many packets are expected. It may be used together with the *Scheduled communication time*. This parameter can be used by both the AMF and the SMF along with the *Scheduled communication time*. + +NOTE 1: The *Scheduled Communication Type* and the *Traffic Profile* should not be used by the AMF to release the UE when Release Assistance Indication from the UE is available. + +- *Battery Indication*, to be used for indicating the power consumption criticality for the UE. This parameter should be sent to the AMF is mainly used by the RAN. + +NOTE 2: How Expected UE Behavior influences CM-CONNECTED to CM-IDLE state transitions, mobility management parameters, and MICO mode may also be influenced by the parameters (Maximum Response Time and Maximum Latency) that are provided by solutions to Key Issue #10 (Network Parameter Configuration API via NEF). + +The above mentioned parameters are to be forwarded to the RAN to allow optimisation of Uu resource allocation for NB-IoT UE differentiation. The *Expected UE Moving Trajectory* is used also for WB-EUTRA. + +### 6.26.3 Support of EPC interworking + +The support for interworking between EPC and 5GC is based on the idle-mode mobility procedures defined in subclause 4.11.1.3 of TS 23.502 [7]. + +When a UE for which the Expected UE Behaviour parameters are used is moving to/from EPS, the following mapping with the Communication Pattern parameters applies: + +**Table 6.26.3-1: mapping between EPS Communication Pattern parameters and 5GS Expected UE Behaviour** + +| EPS Communication Pattern parameter | 5GS Expected UE Behaviour parameter | +|-------------------------------------|--------------------------------------------------------------------------------------------------------| +| 1) Periodic communication indicator | No explicit equivalent parameter, but it is implicitly indicated by the presence of the Periodic Time. | +| 2) Communication duration time | Communication Duration Time (as in EPS) | +| 3) Periodic time | Periodic Time (as in EPS) | +| 4) Scheduled communication time | Scheduled communication time (as in EPS) | +| 5) Stationary indication | Stationary Indication (as in EPS) | +| 6) Battery indication | Battery Indication (as in EPS) | +| 7) Traffic Profile | Traffic Profile (as in EPS) and Scheduled Communication Type | + +The mapping between parameters is done in the HSS+UDM combined entity. + +### 6.26.4 Procedures + +The external parameter provisioning procedure defined in TS 23.502 [7] clause 4.15.6.2 (External Parameter Provisioning) can be reused to provide Communication Pattern parameters to 5GC. + +NOTE: How the parameters are provided to ng-eNBs is to be discussed together with RAN WGs. + +### 6.26.5 Impacts on existing entities and interfaces + +The following nodes are impacted: + +- NEF to provide the Expected UE Parameters to UDM; + +- AMF/SMF to receive and use the related Expected UE Parameters from the UDM during registration and/or PDU session establishment; +- RAN to receive the Expected UE Parameters from the AMF/SMF via N2 and N11 interface. + +### 6.26.6 Evaluation + +This solution analysed and identified which new and existing parameters are to be provided to the AMF, SMF and ng-eNB to optimise the network behaviour for an effective CIoT operation. + +## 6.27 Solution 27: Reuse of EPS Overload Control Mechanisms + +### 6.27.1 Introduction + +This solution corresponds to Key Issue 7: Overload Control for small data. + +In EPC there are several solutions for overload control which are designed to protect various network entities when overload occurs and to prevent overload occurring in the first place. This solution considers whether the features identified in KI7: Overload Control for small data architectural baseline (control plane data back-off timer, control plane overload start indication and service gap) as applied in EPC can be applied to protect 5GC. In addition this solution also applies APN rate control and low access priority from EPC to 5GC. + +### 6.27.2 Functional Description + +#### 6.27.2.1 Small Data Rate Control + +Small Data Rate Control in 5GC, similar to APN Rate Control in EPC, is to allow operators to offer customers services such as "maximum of Y messages per day" as well as allowing the network operator to protect the UPF/NEF. + +Small Data Rate Control provides 3 settings; 'number of packets per time unit', whether exception reports can be sent when the rate control limit has been reached and if they can the 'number of additional allowed exception report packets per time unit' beyond the base small data rate control limit. The settings for uplink and downlink are separate. The UE observes the limits and 5GC may enforce the limits. + +#### 6.27.2.2 Service Gap Control + +Service Gap Control is an optional feature for CIoT UEs to control the frequency they access the network by providing a minimum gap between consecutive MO data communication initiated by the UE for delay tolerant applications. This helps to reduce peak loading in the network and allows a distribution of these accesses in time. + +Service Gap Time should be a subscription parameter stored in the UDR/UDM, which is used to set the Service Gap timer, and passed to the UE and AMF. + +The UE observes the Service Gap Time restriction and AMF enforces it. When the timer is running the UE does not initiate connections for MO data transfer or MO SMS, unless the MO data is exception data in NB-IoT. The UE can still initiate connections for signalling only and to respond to paging. + +#### 6.27.2.3 AMF and SMF Overload + +In 5GC general mechanisms exist, as described in TS 23.501 [5] clauses 5.19.5 and 5.19.6 for the AMF and SMF to manage overload. The AMF can request an AN node to reject connection requests for various reasons related to overload control and the AMF and SMF can trigger NAS level congestion control, for example by the SMF indicating congestion in Nsmf\_PDUSession service responses, see TS 29.502 [26]. + +NB-IoT also includes exception reporting which for the purposes of AMF overload control is considered to be NB-IoT's equivalent of emergency access. + +AMF Overload Control is enhanced to take into account exception reporting conditions: + +- reject AN signalling connection requests that are for non-exception reporting; or +- only permit AN signaling connection requests for exception sessions and mobile terminated services for that AMF. + +The AMF can also signal a percentage value of the amount of signaling traffic to be rejected. + +The RAN node may take the existing and new AMF Overload Control indications into account when configuring access barring mechanism for the related access technologies. + +If low access priority is supported then AMF Overload Control can further be enhanced to request the AN reject requests from low access priority UEs (e.g. UEs using a Delay Tolerant as RRC establishment cause). The AN node further enable access barring if all AMFs it is connected to send an N2 overload start message for low access priority UEs. + +NAS level congestion control specified in TS 23.501 [5] clause 5.19.7 is reused. + +#### 6.27.2.4 Control plane data back-off timer + +In EPC the control plane data back-off timer (T3448) can be returned to the UE in Attach/TAU/Service Accept or Service Reject messages. The UE then uses this timer to delay any further transmission of user data via Control Plane CIoT EPS Optimisation. + +The control plane data back-off timer and rules for when the UE is permitted to ignore it (e.g. exception data, response to paging) are reused in 5GC to prevent the UE from sending data over the control plane via NAS signalling. + +#### 6.27.2.5 Low Access Priority + +The UE may be configured with low access priority. When the UE is configured with a low access priority, when establishing an RRC connection for MO data it should indicate low access priority or Delay Tolerant in its RRC establishment cause. + +UE provides Low access priority indication (LAPI) in NAS message to the 5GC. + +**Editor's note:** It is FFS if LAPI is provided in MM message (e.g. registration request), or in SM message (e.g. PDU session establishment request), or in both. + +The UE may be configured with permission to override the low access priority, in which case if any PDU session is configured to use normal access priority then normal access priority is used instead of low access priority. + +The low access priority indication may be included in charging records for the UE. + +### 6.27.3 Support of EPC interworking + +Consistent with existing EPS-5GS interworking scenarios in TS 23.501 [5] with the following differences: + +- Small Data Rate Control is similar to APN Rate Control in EPC and share the same configuration; +- Service Gap timer is a subscription parameter and can be used both in EPC and 5GC. + +### 6.27.4 Procedures + +#### 6.27.4.1 Small Data Rate Control + +##### 6.27.4.1.1 General + +Small Data Rate Control is configured by the UPF or NEF via the SMF. The configuration is performed when a PDU Session is established using the procedure in TS 23.502 [7] clause 4.3.2.2, with enhancements for Small Data Rate Control limits. + +During PDU Session Establishment the Small Data Rate Control limits are retrieved from the UPF in step 10b and passed to the UE in the PDU Session Establishment Accept message sent to the UE in steps 11, 12 and 13 of the procedure described in clause 4.3.2.2.1 of TS 23.502 [7]. + +**Editor's note:** If and how the NEF provides the small data rate control limits is dependent upon solutions for KI#1 and KI#2 for data arriving in the network using an API. + +#### 6.27.4.2 Service Gap Control + +##### 6.27.4.2.1 General + +The Service Gap timer is a subscription parameter and is therefore stored in the UDR/UDM. When the Registration procedure is performed as defined in TS 23.502 [7] clause 4.2.2.2 the AMF retrieves the Service Gap Time as part of the Access and Mobility Subscription data and passed to the UE in the Registration Accept message. + +At subsequent accesses the AMF verifies that any Service Gap limitations have been observed. If the Service Gap limitations have not been observed then the AMF rejects the UE's request and returns the remaining time for the Service Gap timer. The UE starts its Service Gap timer with the value from the AMF and observes the Service Gap control restrictions. + +#### 6.27.4.3 Overload procedure + +##### 6.27.4.3.1 General + +No enhancements are required to the procedures, however additional code points maybe required to signal to the AN node the additional restrictions, described in clause 6.27.2.3 for AMF Overload Control. + +#### 6.27.4.4 Low access priority + +##### 6.27.4.3.1 General + +UE needs to provide Low access priority indication (LAPI) in NAS messages to the 5GC. + +**Editor's note:** It is FFS if LAPI is provided in MM message (e.g. registration request), or in SM message (e.g. PDU session establishment request), or in both. + +For the low access priority indication to be included in charging records the UE needs to include the priority in the PDU session establishment request to the SMF. The SMF can then forward the priority information to other network nodes, for example the PCF. + +#### 6.27.4.5 Control plane data back-off timer procedure + +The principle on Control Plane data back-off timer specified in section 4.3.7.4.2.7 of TS 23.401 [4] are reused for 5GS. If Release Assistance Indication in AS information is available to the AMF this can also be taken into account. + +### 6.27.5 Impacts on existing entities and interfaces + +Impacts on AMF: + +- Support of Service Gap Control. +- Support of Control plane data back-off timer. +- Support of Low Access Priority. + +Impact on SMF: + +- Small Data Rate Control is configured by the UPF or NEF via the SMF. + +Impact on UPF: + +- Support of Small Data Rate Control. + +Impacts on UE: + +- Support of Small Data Rate Control. +- Support of Service Gap Control. +- Support of Control plane data back-off timer. + +- Support of Low Access Priority. + +Impact on RAN: + +- Reject connection requests for various reasons related to overload control based on AMF indication. + +### 6.27.6 Evaluation + +To support the Overload Control for small data, the solution introduces the Small Data Rate Control, Service Gap Control, AMF/SMF Overload Control and Control plane data back-off timer. The solution is based on the same principles as EPS Overload Control. + +The solution addresses all the architectural requirements of Key Issue 7. + +## 6.28 Solution 28: SMF assisted NG-RAN information + +### 6.28.1 Introduction + +This solution applies to Key Issue 13 (Support for Expected UE Behaviour), Key Issue 1 (Infrequent small data communication) and to Key Issue 2 (Frequent small data communication) to assist the NG-RAN configuration depending on the application behaviour. + +In particular this solution partially addresses the KI#1 requirements for "single packet transmission (UL or DL)" and "dual packet transmission (UL with subsequent DL, or DL with subsequent UL)" when the SD is transmitted over the User Plane. + +### 6.28.2 Functional Description + +The main principles of the solution are: + +- The NG-RAN node is provided with PDU Session specific information (called 'SMF assisted NG-RAN information') to be used for proper configuration of the radio interface upon activation of the UP connection; +- The SMF determines the SMF assisted NG-RAN information and provides it to the NG-RAN node within the N2 SM information during the UP connection activation. + - In case of PDU Session used for data transmission over user plane, the SMF may use the SMF-Associated parameters (e.g. Communication Pattern parameters, Network Configuration parameters) or network configuration to determine the 'SMF assisted NG-RAN information'. + - In case of PDU Session used for data transmission over control plane, the SMF provides the SMF-Associated parameters to the AMF, which, in turn, aggregate them and provide them to the NG-RAN. + +An AF can provision the 5GS with external parameters (e.g. Communication Pattern parameters or parameters from the Network Parameter Configuration API as specified in TS 23.682 [6], but also new parameters can be specified in Rel-16 as described in solution 26). During the PDU Session establishment procedure, the SMF is provisioned with some of the external parameters. + +NOTE 1: The provisioning of the external parameters to the SMF is described in solutions 15 and 26 and will be further detailed during the normative phase. + +Based on the SMF-Associated external parameters provisioned in the SMF from the UDM, network configuration or internal statistics, the SMF may determine 'SMF assisted NG-RAN information'. The SMF utilises the "SMF assisted NG-RAN information" in one of the following ways: + +- If the PDU Session uses user plane transport (i.e. data transport via N3/N9 tunnels), the SMF sends the SMF assisted NG-RAN information to the NG-RAN node included in the N2 SM Information container during the UP connection activation for this PDU Session; or +- If the PDU Session uses control plane transport (i.e. data PDUs are sent over NAS SM signalling), the SMF sends the SMF assisted NG-RAN information to the AMF during the PDU Session establishment procedure. The AMF stores the received SMF assisted NG-RAN information as part of the UE's context and associated PDU Session ID. This enables the AMF to send the SMF assisted NG-RAN information to the NG-RAN node at the earliest possible point (e.g. as shown in step 1 in clause 6.1.4.2 for MO SD transport for solution 1). + +The 'SMF assisted NG-RAN information' is used in the NG-RAN node mainly for decision for appropriate RRC state, e.g. whether to apply RRC Inactive state, transition from RRC Connected to RRC Inactive state or transition from RRC Connected to RRC Idle state. The 'SMF assisted NG-RAN information' may include one or more of the following information: + +- 'Expected Session activity behaviour' describing the periodicity of data transmission and/or the duration of data transmission for the PDU Session (e.g. based on the *Communication Duration Time* and *Periodic Time* parameters); or +- The external parameter *Suggested Number of Downlink Packets* (see Key Issue 10) indicates the expected number of uplink/downlink packets. + +NOTE 2: 'Expected Session activity behaviour' can have semantic similar to the semantic of the "Expected UE activity behaviour" (as specified in TS 23.401 [4] clause 4.3.21) but applicable for a Session activity, i.e. expected pattern of the Session's changes between data Transmission and Non-Transmission. + +### 6.28.3 Support of EPC interworking + +The support of interworking in this solution depends on the conclusions for Key Issue 9 (Support of common north-bound APIs for EPC-5GC Interworking). + +Assuming that for EPC interworking a co-located SCEF+NEF entity and co-located HSS+UDM entity are deployed, then the enhancement proposed in this solution to the UDM and NEF would be applicable to the co-located entities. During mobility to/from EPC the entities in the target CN (e.g. MME in EPC; or AMF and/or SMF in 5GC) need to download the "external parameters" from the HSS+UDM. The HSS+UDM sends the "external parameters" in the corresponding format to be processed in the target CN entity. + +A possible mapping table between EPS Communication Pattern parameters and 5GS Expected UE Behaviour is shown in Solution 26 (see clause 6.26.3). + +### 6.28.4 Procedures + +In this clause the procedure for PDU Session activation is described. + + + +The diagram illustrates the PDU Session activation procedure between a UE, NG-RAN, AMF, SMF, and UPF. It is divided into two main sections: (A) CP path and (B) UP path. + +**Section 0a: (A) PDU Session establishment for data transmission over CP steps 1-6 from clause 6.1.4.1 (Sol.1)** + +- 0b. SMF receives SMF-associated params from UDM +- 0c. Namf\_Communication\_N1N2MessageTransfer (SMF assisted NG-RAN info, N1 SM container) from SMF to AMF +- 0d. NAS transport (N1 SM container) from AMF to UE +- 0e. RRC Conn Req (opt. EDT) from UE to NG-RAN +- 0f. RAN queries UE context (AMF assisted info, SMF assisted NG-RAN info, etc.) from NG-RAN to AMF +- 0g. RRC Conn Setup from NG-RAN to UE +- Data PDU in NAS SM signalling (dashed line) from UE to SMF + +**Section 1a: (B) PDU Session establishment for data transmission over UP** + +- 1b. SMF receives SMF-associated params from UDM +- 2a. Service Request from UE to AMF +- 2b. DL data (dashed line) from UPF to SMF +- 3. Namf\_Communication\_N1N2MessageTransfer (N2 SM info (QoS params, SMF-assisted NG-RAN info), N1 SM container) from SMF to AMF +- 4. N2 Session request from AMF to NG-RAN +- 5. AN resource modification (incl. S1 SM info) from NG-RAN to UE +- 6. N2 Session response (N1 SM info) from NG-RAN to AMF +- 7. Nsmf\_PDUSession\_UpdateSMContext Request from AMF to SMF +- 8. RAN configures appropriate RRC state (from SMF to NG-RAN) +- Data PDU over DRB and N3 (dashed line) from UE to UPF + +Sequence diagram of PDU Session activation procedure showing two paths: Control Plane (CP) and User Plane (UP). + +**Figure 6.28.4-1: PDU Session activation procedure** + +If the PDU Session is used for data transmission over control plane (data over NAS SM), the following steps apply: + +- 0a. During the PDU Session establishment procedure, the PDU Session is configured with (small) data PDU transport over the CP (i.e. Data over NAS SM transport). +- 0b. The SMF may receive SMF-Associated external parameters from UDM during the retrieval of the UE subscription data from UDM. +- 0c. From SMF to AMF: the SMF replies to the AMF using e.g. Namf\_Communication\_N1N2MessageTransfer (SMF assisted NG-RAN information, N1 SM container, etc.). + +The SMF derives and sends the "SMF assisted NG-RAN information" (e.g. Communication Duration Time, Periodic Time, Scheduled Communication Type, Traffic Profile, Suggested Number of Downlink Packets) to the AMF. The AMF stores this information as part of the UE's context and associated with the particular PDU Session ID. This enables the AMF to send the "SMF assisted NG-RAN information" as UE differentiation info to the NG-RAN node at the earliest possible point (e.g. as shown in step 1 in clause 6.1.4.2 for MO SD transport for solution 1). + +If the SMF receives an updated SMF-Associated external parameters from the UDM, the SMF initiates a service operation towards the AMF to update the SMF assisted NG-RAN information. + +0d. From AMF to UE: the AMF uses NAS transport to send the N1 SM container to the UE. + +0e. The UE initiates RRC Connection establishment with indication for 'Data over NAS SM transport'. + +0f. The NG-RAN node may query UE context from the AMF. The AMF sends to the NG-RAN the UE context including AMF assisted information (e.g. RRC Inactive assistance information), SMF assisted NG-RAN information, etc. + +NOTE 1: The AMF provides the UE context to the NG-RAN before step 0g (RRC Connection Setup message) is executed. The exact format of the RAN-assistance information (including AMF assisted information and SMF assisted NG-RAN information) sent from the AMF to the NG-RAN node is to be decided during the normative phase together with RAN WGs. + +0g. The NG-RAN node sends RRC Connection Setup message to the UE to configure the RRC connection according to the AMF assisted information and SMF assisted NG-RAN information received from the AMF. + +NOTE 2: The procedure described in steps 0b - 0g can be also applied to send the UE QoS profile/differentiation information to the NG-RAN node, but the details are described in solution 52. + +As a result, Data PDUs can be transmitted in uplink and downlink over the NAS SM signalling. + +If the PDU Session is used for data transmission over user plane (data carried over N3), the following steps apply: + +1. During the PDU Session establishment procedure the PDU Session is configured for UP transport. The SMF may store in the UE's context the external SMF-Associated parameters, e.g. as received from UDM/UDR during UE SM context retrieval procedure. +2. Due to mobile originated communication (e.g. step 2a using Service Request) or due to mobile terminated communication (e.g. step 2b), the User Plane connection activation for this PDU Session is initiated. +3. The SMF initiates service operation towards the AMF e.g. Namf\_Communication\_N1N2MessageTransfer (N2 SM information (PDU Session ID, QoS, SMF assisted NG-RAN information (*Communication Duration Time, Periodic Time, Scheduled Communication Type, Traffic Profile, Suggested Number of Downlink Packets*))). + +The SMF may include within the N2 SM container the SMF assisted NG-RAN information. The SMF assisted NG-RAN information may contain one or more of the following parameters: *Communication Duration Time, Periodic Time, Scheduled Communication Type, Traffic Profile, Suggested Number of Downlink Packets*. + +4-7. Similar to the steps 12 - 14 in TS 23.502 [7] clause 4.2.3.2. + +8. The NG-RAN node may use the information received in the N2 SM information together with information received from the AMF to configure the radio interface. For example the NG-RAN node may receive e.g., RRC inactive assistance information from AMF and 'SMF assisted NG-RAN information' from one or more SMFs. The NG-RAN node may use the "RRC inactive assistance information" from AMF to determine the RRC inactive state configuration, and use the *Communication Duration Time* and *Periodic Time* to decide whether to configure the RRC Inactive state and/or the duration of the RRC Connected state. + +If the NG-RAN node receives *Scheduled Communication Type, Traffic Profile or Suggested Number of Downlink Packets*, the NG-RAN node may determine whether the data transmission has been completed and the NG-RAN node may determine the transition from RRC Connected to [RRC Idle or RRC Inactive states] without waiting for the UE inactivity time to expire; or the NG-RAN node may initiate selective UP connection deactivation (if there are additional PDU Sessions activated). + +As a result, Data PDUs can be transmitted in uplink and downlink over the NAS SM signalling. + +### 6.28.5 Impacts on existing entities and interfaces + +Enhancements to SMF include the following: + +- Derive the SMF assisted NG-RAN information and sends it: + - to the NG-RAN node within the N2 SM information if UP transport is used; or + +- to AMF over N11 if CP transport is used. + +Enhancements to AMF include the following: + +- storing the SMF assisted NG-RAN information received from the SMF and associated with a PDU Session ID in the UE context. +- sending and aggregating the SMF assisted NG-RAN information to the NG-RAN node together with the UE context. + +Enhancements to NG-RAN node include the following: + +- Using the SMF assisted NG-RAN information 1) from the N2 SM Information container or 2) from the UE context sent from AMF, in addition to "RRC Inactive assistance information" from the AMF, to fine-tune the configuration of the Uu interface, e.g. RRC Inactive state. + +### 6.28.6 Evaluation + +This solution allows to send to the NG-RAN node "SMF assisted NG-RAN information" specific for a particular PDU Session. The following uses cases are covered: + +- In cases of PDU Session using UP transport, during connection activation the SMF sends the "SMF assisted NG-RAN information" to the NG-RAN node within the N2 SM Information container. +- In case of PDU Session using data transport over control plane (Data-over-NAS transport), the SMF sends the "SMF assisted NG-RAN information" to the AMF during the PDU Session establishment procedure. The "SMF assisted NG-RAN information" is stored as part of the UE's context and sent to the NG-RAN within the UE's context. + +The "SMF assisted NG-RAN information" is used in the NG-RAN node to fine-tune the configuration of the Uu interface, e.g. RRC Inactive state. + +## 6.29 Solution 29: User Plane data transmission with ConnectionLess signalling + +### 6.29.1 Introduction + +This solution addresses primarily Key Issue 1: Support for infrequent small data transmission, Secondarily, it can provide improvements in the area of Key Issue 5: UE TX Power Saving Functions, Key Issue 7: Overload Control for small data. The Solution may also be applicable to Key Issue 2: Frequent small data communication, and ConnectionLess (CL) solution can be used alongside ConnectionOriented (CO) data solution. + +Solutions design to address Key Issue 3: High latency communication, Key Issue 4: Power Saving Functions, Key Issue 9: Support of common north-bound APIs for EPC-5GC Interworking, Key Issue 12: Inter-RAT mobility support to/from NB-IoT may be used in combination with this solution. + +It is assumed that solution 35 or some other means to provide the T8 API for NIDD service via user plane is supported. + +### 6.29.2 Functional Description + +The solution aims to cover at least following use cases: + +- (Massive) IoT UE that may move and need to send sporadic (potentially small amount) data: in this case the UE sends data to the 5GC via the user plane path without requiring more signalling in the network (RAN and Core) than the amount of user data to be transferred. + +In such situations, the following architectural concepts are proposed in order to support a fast switch from IDLE state to a CL-data state where data transfer occurs: + +- The service itself is not connectionless: + - The UE needs to register to the network and set-up a PDU session that is indicated for CL signalling. + +- When the UE exchanges MM or SM related signalling with the network a N2 connection is set-up. Once the MM or SM transaction(s) are over the N2 connection for the UE is released. +- The MM procedures (e.g. Registration, authentication, Registration Update, etc.) are independent from whether the UE will activate a PDU session used in ConnectionLess (CL) mode on the interface between RAN and Core. Thus an UE needs to Register to the network before being able to activate a PDU session to be used in ConnectionLess (CL) mode on the interface between RAN and Core. +- The UE is tracked at Registration Area level and performs Registration Updates as specified. +- The UE uses the same SM procedures to manage (set-up, release, etc.) a PDU session regardless of whether this PDU session is to be used in a Connection Oriented (CO) or in a ConnectionLess (CL) mode on the interface between RAN and Core. +- During the PDU session set-up procedure some parameters specific to the CL data transfer are nevertheless exchanged between the UE and the network. +- The solution is not technically dependent on any particular UE category. A UE that supports CL user plane and the additional CL parameters exchanged during the establishment of a PDU session may request CL PDU Session establishment, and the SMF authorises the request based on subscription data. +- A PDU session that has been established with CL data option may also be alternatively used as a CO PDU session. It would be technically possible to prevent this, but it would require additional logic to reject the UE request for DRB on CL PDU Session. +- The RAN-Core interface works in ConnectionLess (CL) mode for UP (User Plane) delivery: once the PDU session has been established, the UE is able to send and to receive data without any need to first set-up a connection on N2 or N3. All user plane traffic is carried over an N3 tunnel that can be shared by all active connectionless mode UEs that are currently being served by the same RAN node and the same PDU session type on the same UPF. The shared N3 tunnel works as follows: + - If there is no shared N3 tunnel between the UPF and the RAN node serving the UE when the N3 tunnel is established, then the SMF establishes a shared N3 tunnel and identifies it as a shared tunnel that can be re-used by other CL UEs served by the same RAN node. + - If there is already a shared N3 tunnel between the UPF and the RAN node when the N3 tunnel is established, then the SMF re-uses the existing shared N3 tunnel. + - The (re-)use of the shared N3 tunnel is determined based on the UE requesting CL PDU session, which implicitly indicates the UE capability to send and receive CL data. + - AN Release procedure related with one of the UEs using the shared N3 tunnel does not release the shared N3 tunnel, but only removes the affected UE from the users of the shared N3 tunnel. + - AN Release procedure related with the last remaining UE using the shared N3 tunnel releases the shared N3 tunnel. + - The CL procedure is only used over N3. The existing N9 procedures are re-used without any modification related with CL procedures. +- The support of the ConnectionLess (CL) mode on the interface between RAN and Core is independent of the nature of the data being carried in a PDU session (IPv4, IPv6, non IP). +- When the UE needs to send data (assuming the UE is already registered to the network and has established a PDU session): + - There is no N2 signalling exchange dedicated to the UE between the RAN and the Core. + - There is no N3 data plane connection dedicated to the UE between the RAN and the Core. + - As there is no signalling exchange dedicated to the UE between the RAN and the Core, the RAN gets no security material dedicated to the UE. Thus the security and the header (de)compression of the user plane traffic are handled in the 5GC (in the UPF part of the 5GC). The corresponding parameters (e.g. security algorithms, compression algorithms, etc.) are negotiated between the UE and the AMF/SMF at PDU session set-up. + +**Editor's note:** Any potential security impacts on signalling exchanges between the RAN and the UE in order to re-use of the security parameters in the stored UE context is to be studied by SA WG3. + +- As the Core network User plane Function (UPF) needs to decipher data received from a UE via the RAN, the UL (uplink) data are sent by the UE together with a non ciphered PDU session identifier allowing the UPF to retrieve the deciphering context of the PDU session. +- As the RAN needs to route Uplink (UL) traffic from the UE towards the UPF, the UE needs to put packet forwarding information in its UL traffic allowing the RAN to determine the relevant UPF. +- The 5GC provides via NAS signalling UPF CL Service information (UCLSI) to the UE: For DL traffic, UCLSI is associated with the UE RAN identifier and for UL traffic, it indicates the packet forwarding information allowing the RAN to determine the UPF. This information is provided on a per PDU session basis. + - The 5GC provides UCLSI information to the UE at least upon UE request for a PDU session set-up. This information needs also to be provided to the UE when the UPF that supports the PDU session of the UE has been changed. + - If UPF indicated by UCLSI is not known by RAN, then RAN uses a DNS procedure based on the UCLSI prefix to determine forwarding information to the UPF. +- When the UPF receives UL traffic with a PDU session identifier for which it has no corresponding context, the UPF fetches the corresponding information from the AMF/SMF. +- The UPF keeps track of the RAN from which it last received UL traffic from a UE and associates this information with a UE Location Freshness Timer. As long as the UE Location Freshness Timer has not elapsed, the UPF sends DL (Downlink) traffic for an UE towards the RAN from which it last received UL traffic from this UE. The DL data are sent by the UPF towards the RAN together with a non ciphered UE identifier. If the RAN can't deliver the PDU (the UE may have moved in the mean time) the RAN deletes the PDU and notifies the UPF that removes the relationship between the UE and the RAN. +- The network may use the expiry of the UE Location Freshness Timer as a trigger to re-authenticate the UE. +- When the UPF needs to send DL data towards an UE, and the UE Location Freshness Timer has elapsed, the UPF may request the AMF/SMF to page the UE. The AMF/SMF pages the UE in the Tracking Area List where it is registered. +- The timer values may be set to default timer values. The timer value of the UE Location Freshness Timer is determined by the network taking into account the UE subscription. +- The UE mobility relies on cell reselection, not on network controlled Hand-Overs and the UE may send a dummy UL data message to the UPF to refresh the UPF-RAN binding for the UE. + +**Editor's note:** The security aspects related with this solution need to be studied by SA WG3. + +The architecture for Data transmission with ConnectionLess RAN-Core interface consists of the following network elements (fig 6.29.2-1): + +- User equipment (UE). +- Radio Access Network (RAN). +- User plane Gateway (UPF). +- Core control plane (AMF and SMF). + + + +Figure 6.29.2-1: Architecture to support PDU sessions with Connectionless mode transfer on the RAN-Core interface. The diagram shows a network architecture with the following components and interfaces: NG UE connected to NG (R)AN via N1; NG (R)AN connected to AMF via N2 and to UPF via N3; AMF connected to AUF via N12 and N11, and to SMF via N13; SMF connected to AF via N5 and to UPF via N4; UPF connected to Data Network (local or central) via N6. + +**Figure 6.29.2-1: Architecture to support PDU sessions with Connectionless mode transfer on the RAN-Core interface** + +The User plane protocol stack is derived from the baseline connection oriented protocol stack with the UE-RAN layer PDCP split between lower and upper parts: + +- SDAP layer: This layer, placed between IP and access stratum, links UE and UPF, provides mapping between a QoS flow and a connectionless PDU session. +- PDCP Upper: This layer, placed between IP and access stratum, links UE and UPF, provides encryption and integrity protection between the UE and the network. The PDCP Upper UP layer takes care to avoid packets duplication (Sequence Numbering). The PDCP security procedure and detection of duplicated messages are executed as in CO case with these PDCP functions located in the UPF. +- PDCP Lower: This layer, placed between the UE and RAN, provides PDU session identification at RAN level. +- Core CLS Relay: This layer, placed between the RAN and UPF, provides relay of the PDU session identification and multiplexing of multiple PDU sessions over a N3 link between an UPF and an AN Node. + + + +Figure 6.29.2-2: User Plane Protocol stack for Connectionless mode transfer on the RAN-Core interface. The diagram shows the protocol stack layers for UE, RAN, and UPF. The UE stack includes Application, IP, etc., SDAP, PDCP Upper, PDCP Lower, RLC, MAC, and PHY. The RAN stack includes PDCP Lower, RLC, MAC, PHY, and a CLS Core relay layer. The UPF stack includes IP, etc., SDAP, PDCP Upper, PDCP Lower, CLS Core Relay, IP, and L1/L2. The RAN stack is split into two columns: the left column contains PDCP Lower, RLC, MAC, and PHY; the right column contains CLS Core relay, IP, and L1/L2. + +**Figure 6.29.2-2: User Plane Protocol stack for Connectionless mode transfer on the RAN-Core interface** + +Figure 6.29.2-2 shows the layers that are involved in CL data transfer. CL re-uses the existing protocol layers, and it adds the CLS Core Relay layer. Following layers are to be defined by RAN groups: + +- PDCP Lower. +- RLC: Radio control sublayer (responsible for segmentation and ARQ). +- MAC: Media Access control (responsible for connectionless access and HARQ). +- PHY: Physical Access. +- CLS Core relay: CL data relay layer. + +**Editor's note:** The protocol stacks over N3 is to be defined together with RAN groups. + +### 6.29.3 Support of EPC interworking + +Connectionless (CL) mode is only supported in 5GC, but not in EPC. It is only possible to initiate CL PDU session in 5GC. Mobility between EPC and 5GC is supported, but if a CL PDU session is transferred to EPS PDN connection, it will only work in Connection Oriented (CO) mode. The existing UPF may be maintained as CO anchor and so IP address continuity would be assured. + +### 6.29.4 Procedures + +#### 6.29.4.1 Identities + +##### 6.29.4.1.1 UPF CL SERVICE Id (UCLSI) + +UCLSI is used by UE, RAN and UPF to identify a PDU session with Connectionless mode data transfer on the RAN-Core interface. This identifier contains an Identifier of the UPF serving the PDU session and a local identifier for a specific connectionless PDU session for a specific UE. RAN uses UCLSI to derive the UPF that should handle Data exchanged with the UE. A UE may be allocated one or more UCLSI on one or more UPF, each UCLSI corresponding to a unique PDU session. + +#### 6.29.4.2 Assumptions + +- The AMF/SMF has to select an UPF that supports PDU sessions with Connectionless mode data transfer on the RAN-Core interface. The UPF selection procedure takes also into account the specific parameters (e.g. security algorithms, compression algorithms,...) proposed by the UE at PDU session set-up. +- The UPF manages a state per UCLSI. The UCLSI state can be: + - REACHABLE: The UCLSI is marked as REACHABLE when the UPF knows the identity of the RAN serving that UCLSI as the last correctly received UL PDU from the UE has been received by the UPF via this RAN. The UCLSI REACHABLE state is controlled by a freshness timer at the expiry of which the UCLSI state becomes IDLE. The Timer is (re)started at the reception of each UL PDU correctly received from the UE on that UCLSI. + - IDLE: The UPF does not know the identity of the RAN serving that UCLSI. Paging is required to send DL PDU for this UCLSI. +- The RAN is assumed to also run a UE Location Freshness timer for UCLSI availability. The Timer in the UPF is assumed to be shorter than the timer in RAN. +- The RAN and UPF set their UE Location Freshness timer to default value. The UE receives its timer value at CL PDU session establishment time. + +#### 6.29.4.3 Procedures + +##### 6.29.4.3.1 Set-up of a PDU sessions with Connectionless mode data transfer on the RAN-Core interface + +This procedure is used to establish PDU sessions with Connectionless mode data transfer on the RAN-Core interface. Procedure is re-using TS 23.502 [7] clause 4.3.2.2 UE Requested PDU Session Establishment with the following additions. + + + +``` + +sequenceDiagram + participant UE + participant (R)AN + participant AMF + participant UPF + participant SMF + participant PCF + participant UDM + participant DN + + UE->>AMF: 1. PDU Session Establishment Request + Note right of AMF: 2. SMF selection + AMF->>SMF: 3a. Nsmf_PDUSession_CreateSMContext Request + SMF-->>UDM: 4a-4b. Registration/ Subscription retrieval/ Subscription for updates + UDM-->>SMF: + SMF->>AMF: 5. Nsmf_PDUSession_CreateSMContext Response + rect rgb(255, 255, 255) + Note over UE, DN: 6. PDU Session authentication/authorization + end + Note right of SMF: 7a. PCF selection + SMF->>PCF: 7b. Session Management Policy Establishment or Modification + PCF->>SMF: + Note right of SMF: 8. UPF selection + SMF->>PCF: 9. Session Management Policy Modification + PCF->>SMF: + SMF->>UPF: 10a. N4 Session Establishment/Modification Request + UPF->>SMF: 10b. N4 Session Establishment/Modification Response + SMF->>AMF: 11. Namf_Communication_N1N2MessageTransfer + AMF->>(R)AN: 12. N2 PDU Session Request (NAS msg) + (R)AN->>UE: 13. AN-specific resource setup (PDU Session Establishment Accept) + (R)AN->>AMF: 14. N2 PDU Session Request Ack + UE-->>UPF: First Uplink Data + AMF->>SMF: 15. Nsmf_PDUSession_UpdateSMContext Request + SMF->>UPF: 16a. N4 Session Modification Request + UPF->>SMF: 16b. N4 Session Modification Response + SMF->>AMF: 17. Nsmf_PDUSession_UpdateSMContext Response + SMF->>AMF: 18. Nsmf_PDUSession_SMContextStatusNotify + UPF-->>UE: First Downlink Data + SMF-->>UE: 19. IPv6 Address Configuration + SMF-->>UDM: 20. Unsubscription / Deregistration + +``` + +Sequence diagram for UE-requested PDU Session Establishment for non-roaming and roaming with local breakout. The diagram shows interactions between UE, (R)AN, AMF, UPF, SMF, PCF, UDM, and DN across 20 steps including session requests, selections, policy establishments, and data flow setup. + +**Figure 6.29.4.3.1-1: UE-requested PDU Session Establishment for non-roaming and roaming with local breakout** + +The procedure assumes that the UE has already registered on the AMF thus unless the UE is Emergency registered the AMF has already retrieved the user subscription data from the UDM. + +1. Additionally to Step 1 actions in TS 23.502 [7] clause 4.3.2.2.1, the UE may indicate CL PDU session request in the Request Type. +2. Additionally to Step 2 actions in TS 23.502 [7] clause 4.3.2.2.1, if the Request Type indicates CL PDU Session, then the AMF selects an SMF that supports CL PDU Sessions. +3. Additionally to step 3 in TS 23.502 [7] clause 4.3.2.2.1, the AMF includes the CL indication in the request that it forwards to SMF. +4. Additionally to step 4 in TS 23.502 [7] clause 4.3.2.2.1, the SMF considers also the CL subscription information when authorising the PDU session set-up, and responds to SMF. +- 5-7. As in TS 23.502 [7] clause 4.3.2.2.1 steps 5-7. +8. Additionally to the criteria in step 8 of TS 23.502 [7] clause 4.3.2.2.1, the SMF takes also the UPF ability to support CL signalling into account when selecting UPF. SMF chooses a UPF CL SERVICE Id (UCLSI) that identifies the PDU session and the UPF and gets from the AUC the keys to be used on the user plane link between the UPF and the UE. The UCLSI includes a UPF prefix for DNS query of the UPF IP address. + +**Editor's note:** The derivation of the keys to be used between UE and UPF is to be defined at SA WG3. It should consider the master Key output of the last authentication as well as the UCLSI and the Direction of the traffic. + +9. As in TS 23.502 [7] clause 4.3.2.2.1 step 9 +10. Additionally to Step 10 actions in TS 23.502 [7] clause 4.3.2.2.1, if the UE requested for CL PDU session in step 1 and the request is accepted by the network, the SMF includes also the CL PDU session indication and the UCLSI in the session establishment indication to the UPF. +11. Additionally to Step 11 actions in TS 23.502 [7] clause 4.3.2.2.1, the SMF includes the UCLSI to be used in this PDU session. If shared N3 tunnel does not exist yet, then the SMF creates it. +12. Additionally to Step 12 actions in TS 23.502 [7] clause 4.3.2.2.1, the AMF indicates acceptance of CL PDU session and includes the UCLSI. +13. Additionally to Step 13 actions in TS 23.502 [7] clause 4.3.2.2.1, RAN selects appropriate RAN connectionless mechanism and sends associated RRC message to UE along with NAS message from SMF providing PDU session set-up response. + - The UE calculates the key for the security association with UPF based on the same algorithm and on the same input parameters than used by the Core control plane (SMF) in step 10. + - UE may use the connectionless service to complete the user plane configuration (e.g. Router solicitation / IP address assignment, header compression initiation (if any), etc.). + - The UE stores the UCLSI for later use. +- 14-20. As in the corresponding steps in TS 23.502 [7] clause 4.3.2.2.1. + +##### 6.29.4.3.2 UE connectionless uplink data transfer + + + +``` + +sequenceDiagram + participant UE + participant RAN + participant UPF as Core-UPF + participant SMF as Core-CP (SMF) + + Note right of RAN: 3. Retrieval of Data path to UPF for UL traffic + Note right of UPF: 5. Context retrieval + + UE->>RAN: 1. Connectionless data + RAN-->>UE: 2. RAN acknowledgement + RAN->>UPF: 4. Connectionless data + UPF->>SMF: 7. Data + Note right of UPF: 6. check integrity and decrypt data + +``` + +Sequence diagram for UE triggered uplink connectionless transfer. Lifelines: UE, RAN, Core-UPF, Core-CP (SMF). The sequence starts with UE sending '1. Connectionless data' to RAN, which responds with '2. RAN acknowledgement'. A dashed box labeled '3. Retrieval of Data path to UPF for UL traffic' spans between RAN and Core-CP. RAN then sends '4. Connectionless data' to Core-UPF. Another dashed box labeled '5. Context retrieval' spans between Core-UPF and Core-CP. Core-UPF performs '6. check integrity and decrypt data' and finally sends '7. Data' to Core-CP. + +**Figure 6.29.4.3.2-1: UE triggered uplink connectionless transfer** + +###### **Pre-conditions:** + +- The UE has uplink connectionless data (a PDU) to send on one of its already established PDU sessions with Connectionless mode data transfer on the RAN-Core interface. +- The UE is currently under coverage of a radio cell that supports current connectionless mechanism configuration. + +1. The UE ciphers the PDU to transmit. The UE then puts the previously assigned UCLSI in the CLS UP data header and adds an integrity check signature. + +UE access stratum may replace the UCLSI with a shorter identifier if available from RAN and UE RAN freshness timer has not expired. + +- The UE sends uplink connectionless data transfer to the RAN using current configured connectionless mechanism. + +NOTE 1: The integrity check signature is to prevent another UE from injecting traffic on the PDU session. It is calculated on the UCLSI and ciphered PDU, not on any shorter RAN identifier possibly used instead the UCLSI on the air interface. + +2. RAN sends ack to the UE. + +RAN resets UE Location Freshness Timer for UCLSI and stores the mapping between the UCLSI and the UE RAN identifier. + +The UE resets the UE UCLSI Location Freshness Timer. + +3. If UPF indicated by UCLSI is not known by RAN then the RAN node constructs FQDN based on UPF prefix contained in the UCLSI, and obtains the destination UPF address via DNS procedure. + +NOTE 2: This step takes place only for the first user served by the RAN that is handled by a new UPF. + +4. Based on the received UCLSI, the RAN forwards all complete data PDUs with header including UCLSI and integrity check to UPF over appropriate transport interface (N3). + +5. Using the UCLSI, the UPF retrieves the context of the PDU Session. If such context is not available the UPF may send a query to the Core control plane (SMF). +6. Using stored key UPF verifies the integrity check signature and decrypts incoming uplink data. + +If the Integrity check is negative the UPF silently discards the data. Otherwise, (when needed) the UPF decompresses the PDU header. + +The UPF learns that UE is available on a given RAN (the UCLSI state is REACHABLE): the UPF (re)starts UE Location Freshness Timer for the UCLSI and stores the UCLSI to RAN transport interface mapping. + +- 7 The UPF forwards the PDU towards its destination. +- 8 Optionally, if requested during PDU session establishment, the UPF may acknowledge the outcome of the procedure in a DL CL message, see clause 6.29.4.3.3. + +##### 6.29.4.3.3 UE connectionless downlink data transfer + + + +``` + +sequenceDiagram + participant SMF as Core-CP (SMF) + participant UPF as Core-UPF + participant RAN + participant UE + Note right of UPF: 2. UPF selects RAN interface + Note left of UE: 5. Check integrity and decrypt data + SMF->>UPF: 1. Data + UPF->>RAN: 3. Connectionless data + RAN-->>UPF: -NACK (if required)- + RAN->>UE: 4. Connectionless data + UE->>RAN: 5 RAN Ack + +``` + +Sequence diagram for UE connectionless downlink data transfer. Lifelines: UE, RAN, Core-UPF, Core-CP (SMF). The sequence starts with Data (1) from SMF to UPF. UPF selects RAN interface (2). Connectionless data (3) is sent from UPF to RAN. RAN sends NACK (if required) (4) to UPF. Connectionless data (4) is sent from RAN to UE. UE checks integrity and decrypts data (5). RAN Ack (5) is sent from UE to RAN. + +**Figure 6.29.4.3.3-1: Downlink connectionless transfer** + +Pre-conditions: + +- The UE has previously established a PDU session with Connectionless mode data transfer on the RAN-Core interface. +1. The UPF receives downlink incoming data (a PDU). + 2. The UPF retrieves the UCLSI corresponding with the PDU session: + - if the UCLSI state of the PDU session is marked as "REACHABLE", the UPF uses the last known RAN serving this UCLSI. + - The UPF compresses the IP header (when needed), encrypts the data, adds an integrity check signature and selects the appropriate downlink RAN transport interface for the UCLSI. + - The UPF restarts UE Location Freshness Timer for UCLSI. + - if UCLSI state for the PDU session is "IDLE" then the UPF may either drop packet or initiate network page. This behaviour is controlled by a policy received from Core control plane (SMF) itself possibly depending on subscription. + +- The UPF sends a paging request for the UCLSI to Core CP, buffers the data and starts a paging timer. Core CP triggers the corresponding paging by the RAN. If the page response from UE arrives before the paging timer times out, then the UPF learns current RAN serving the UE and forwards the data via this RAN. This is further detailed in clause 6.29.4.3.4. +3. (assuming UCLSI state is marked REACHABLE) the UPF adds the UCLSI in the header and forwards the data over the downlink RAN transport interface for the UCLSI that was selected in step 2. For any downlink incoming data, RAN matches downlink UCLSI: + - if UCLSI is known to RAN then RAN transmits the data to UE: + - if UE transfer is successful, RAN restarts UE Location Freshness Timer for UCLSI. + - if UCLSI is not known to RAN (e.g. RAN previously had UE transfer fail or after RAN UE freshness timer for UCLSI expires) then RAN drops the data and sends NACK to UPF. + - if UPF receives NACK from RAN (e.g. the UCLSI was known but transfer failed or UCLSI was not known) then UPF clears UPF UE freshness timer and so marks UCLSI state as "IDLE" (the UCLSI is no more associated with any RAN Node). + 4. The RAN transmits the data to UE based on the UE identification corresponding with the UCLSI. + - if UE transfer fails, RAN drops packet, sends NACK to UPF and deletes its context for the UCLSI. + 5. When UE receives connectionless data, it processes the data (re-assembles, decrypts, etc.), delivers the data to the application and sends uplink acknowledgement. UE resets UCLSI freshness timer. + 6. If UPF UE freshness timer for UCLSI expires, UPF marks UCLSI state as "idle". + 7. If RAN UE freshness timer for UCLSI expires, RAN deletes UCLSI. + 8. If UE freshness timer for UCLSI expires or UE reselects a new cell, UE returns to connectionless idle state and stops monitoring downlink channels for data reception. + +##### 6.29.4.3.4 Paging for UE connectionless downlink data transfer + + + +``` + +sequenceDiagram + participant UE + participant RAN + participant UPF as Core-UPF + participant CP as Core-CP (AMF+SMF) + + Note right of CP: 1. DL Data + CP->>UPF: + Note right of UPF: 2. Paging needed + UPF->>CP: + Note right of CP: 3. Paging request + CP->>RAN: + Note right of RAN: 3. Paging + RAN->>UE: + Note right of UE: 4. Paging response (Service request) + UE->>CP: + Note right of CP: 5. NAS Reactivate CLS (UCLSI) + CP->>UE: + Note right of UE: 6. CL UL data transfer (e.g. dummy PDU) + UE->>UPF: + Note right of UPF: 7. CL DL data transfer + UPF->>UE: + +``` + +Sequence diagram for Paging for UE connectionless downlink data transfer. Lifelines: UE, RAN, Core-UPF, Core-CP (AMF+SMF). The sequence shows: 1. DL Data from Core-CP to Core-UPF; 2. Paging needed from Core-UPF to Core-CP; 3. Paging request from Core-CP to RAN; 3. Paging from RAN to UE; 4. Paging response (Service request) from UE to Core-CP; 5. NAS Reactivate CLS (UCLSI) from Core-CP to UE; 6. CL UL data transfer (e.g. dummy PDU) from UE to Core-UPF; 7. CL DL data transfer from Core-UPF to UE. + +Figure 6.29.4.3.4-1: Paging for UE connectionless downlink data transfer + +1. The UPF receives DL data but the corresponding UCLSI state is marked "IDLE" and the policy received from Core CP is to page the UE in that case (step 2 of clause 6.29.4.3.3). +2. The UPF notifies the SM that it has no RAN context for DL data related with an UCLSI. SMF requests (Permanent User Id; UCLSI) AMF to Page the UE corresponding to the permanent UE identifier (IMSI) associated with the UCLSI. The AMF retrieves the corresponding UE NAS identifier (GUTI like) for paging. +3. The AMF requests the RAN to page the UE and the RAN pages the UE. +4. The UE issues a NAS Page response to the Core CP (AMF). +5. The Core CP sends a NAS Reactivate CLS (UCLSI) to request the UE to reactivate the UCLSI. +6. The UE issues an UL Data request on the UCLSI (according to clause 6.29.4.3.2). The request contains in the UL CLS data Header the UCLSI as well as an indication that the data is dummy (if the UE has no data to send and chooses to send a dummy PDU). The UPF drops the data (if it indicated as a dummy data) and updates the UCLSI context: The UPF starts UE Location Freshness Timer for UCLSI and stores the UCLSI to RAN transport interface mapping. +7. The UPF restarts the DL data transmission according to Figure 6.29.4.3.3-1. + +##### 6.29.4.3.5 Mobility support + + + +``` + +sequenceDiagram + participant UE + participant Old RAN + participant New RAN + participant Core-UPF + participant Core-CP (SMF) + + Note over UE, Core-UPF: 1. CL UL/DL data transfer + Note over UE: 2. Cell change detected + Note over UE, Core-UPF: 3. CL UL data transfer (dummy data) + Core-UPF-->>Core-CP (SMF): 4a. Context retrieval + Note over Core-UPF: 4b. Update UCLSI context + +``` + +The diagram illustrates the mobility support process. It features five lifelines: UE, Old RAN, New RAN, Core-UPF, and Core-CP (SMF). + 1. A box spanning from UE to Core-UPF represents '1. CL UL/DL data transfer'. + 2. A box on the UE lifeline indicates '2. Cell change detected'. + 3. A box spanning from UE to Core-UPF represents '3. CL UL data transfer (dummy data)'. + 4. A dashed box between Core-UPF and Core-CP (SMF) represents '4a. Context retrieval'. + 5. A box on the Core-UPF lifeline represents '4b. Update UCLSI context'. + +Sequence diagram for Mobility support showing interactions between UE, Old RAN, New RAN, Core-UPF, and Core-CP (SMF). + +**Figure 6.29.4.3.5-1: Mobility support** + +1. The UE and UPF exchange UL and DL connectionless data. +2. The UE detects cell change while UCLSI remains valid. +3. The UE issues an UL Data request on the UCLSI (per clause 6.29.4.3.2). The request contains in the UL CLS data Header the UCLSI as well as an indication that the data is dummy (if the UE has no data to send and chooses to send a dummy PDU). RAN stores the mapping between UCLSI and UE RAN identifier. +4. Using the UCLSI, the UPF retrieves the context of the PDU Session. + - 4a. If such context is not available the UPF may send a query to the Core control plane (SMF). + - 4b. The UPF verifies the integrity check signature and decrypts incoming uplink data and drops the data (if it was indicated as a dummy data) and updates the UCLSI context: the UPF restarts UE Location Freshness Timer for UCLSI and stores the UCLSI to RAN transport interface mapping. + +##### 6.29.4.4.6 UPF Triggered Release and Redirection During UE Connectionless Active Mode + + + +``` + +sequenceDiagram + participant UE + participant RAN + participant UPF as Core-UPF + participant SMF as Core-CP (SMF) + Note right of UPF: 2. UPGW detects need for session release + UE->>UPF: 1. CL UL/DL data transfer + UPF->>SMF: 3. Connectionless release request + SMF->>UE: 4. Connectionless release request + +``` + +Sequence diagram illustrating UPF Initiated Release and Redirection. Lifelines: UE, RAN, Core-UPF, Core-CP (SMF). 1. CL UL/DL data transfer (UE to Core-UPF). 2. UPGW detects need for session release (Core-UPF internal). 3. Connectionless release request (Core-UPF to Core-CP). 4. Connectionless release request (Core-CP to UE). + +**Figure 6.29.4.4.6-1: UPF Initiated Release and Redirection** + +1. The UE and UPF exchange UL and DL connectionless data. +2. The UPF detects need for session release (security violation, UE traffic profile violation, gateway overload protection, etc.). +3. The UPF sends connectionless release request to the Core-CP (SM) with session identifier UCLSI. The UPF provides a release cause indication. +4. The Core-CP (SM) sends connectionless release request to the UE with session identifier UCLSI. The Core-CP (SM) provides information on the release cause indication and whether or not the network requires that UE request re-establishment of the PDU session using CL and/or CO mode. + +### 6.29.5 Impacts on existing entities and interfaces + +#### 6.29.5.1 Impact on interfaces + +The following interfaces are impacted: + +##### N3: + +- Support for a shared N3 tunnel used to transport user data from all active connectionless UEs on a given RAN that are assigned to the same UPF. + +#### 6.29.5.2 Impact on entities + +The following nodes are impacted: + +##### UPF: + +- support for user data encryption and integrity protection using per UCLSI security key. +- maintain UCLSI freshness timer and RAN node association. +- selective trigger paging for incoming traffic addressed to UE with expired UCLSI freshness timer. + +##### RAN: + +- support for at least one connectionless access mechanism (i.e. data over msg3, data over msg5). +- maintain RAN UCLSI freshness timer and UE RAN identifier association. +- Resolve the target UPF based on UCLSI. + +##### UE: + +- Ability to request ConnectionLess PDU session type. +- storing the assigned UCLSI for subsequent CL data transport. +- support for CL data transport using UCLSI. + +SMF: + +- Ability to negotiate ConnectionLess PDU session type. + +### 6.29.6 Evaluation + +## 6.30 Solution 30: NEF based infrequent small data transfer via NAS-SM + +### 6.30.1 Introduction + +#### 6.30.1.1 General + +This solution is built on top of Solution 1 in clause 6.1 and allows the exchange of infrequent small data via an API. The Architecture Reference Models, Functional Description, Interworking with EPS and Procedures of Solution 1 are taken as baseline and this solution describes the missing details to support infrequent small data transfer via NAS-SM via NEF between the SMF and AF. + +**NOTE:** As captured in clause 4, it is assumed that the exposure of network capabilities towards the SCS/AS is done via NEF. In addition, as captured in clause 8.9, *when a UE is capable of switching between EPC and 5GC, it shall only be associated with combined SCEF+NEF node(s) for Service Capability Exposure.* Consequently, data towards SCS/AS can be routed via a NEF+SCEF combined node. + +The solution also supports exposing small data APIs for infrequent small data transmission to the AF. The APIs are based on the NIDD APIs which are defined for the T8 interface in TS 29.122 [9]. + +API usage only applies to the case where the PDU Session type is Unstructured. + +The following principles apply to this solution: + +- A PDU Session terminates at NEF. +- The NEF exposes APIs to the AF for Small Data. The APIs are based on the T8 APIs that were defined in Release 15. + +Support for RDS is provided as described in Solution 49. + +#### 6.30.1.2 Architecture reference models + +##### 6.1.1.2.0 General + +This clause shows the architecture reference models that support API usage in the cases where a NAS Small Data Delivery PDU Session terminates at a NEF. + +This solution presents no Roaming Reference Architecture for the Local Breakout case because a Small Data API service will not be exposed by the visited network. This is in line with the architecture principle from TS 23.501 [5] which states "*For external exposure of services related to specific UE(s), the NEF resides in the HPLMN. Depending on operator agreements, the NEF in the HPLMN may have interface(s) with NF(s) in the VPLMN*". + +APIs are exposed to the AF via the N33/Nnef reference point. + +The N29 reference point will be used to send and receive small data packets via the NEF. + +##### 6.30.1.2.1 Non-roaming reference architectures + +Figure 6.30.1.2.1-1 depicts a simplified service based architecture with the entities involved in small data transfer via NEF. + + + +This diagram illustrates the service based architecture for small data delivery via NEF in a non-roaming scenario. At the top, three network functions (NEF, UDM, and AF) are connected to a common Service Based Interface (SBI). The NEF connects via the Nnef interface, the UDM via the Nudm interface, and the AF via the Naf interface. Below the SBI, three more network functions (AUSF, AMF, and SMF) are connected. The AUSF connects via the Nausf interface, the AMF via the Namf interface, and the SMF via the Nsmf interface. At the bottom, a User Equipment (UE) is connected to a Radio Access Network ((R)AN). The UE connects to the AMF via the N1 interface, and the (R)AN connects to the AMF via the N2 interface. + +Figure 6.30.1.2.1-1: Simplified Service Based Architecture for small data delivery via NEF (non-roaming). + +**Figure 6.30.1.2.1-1: Simplified Service Based Architecture for small data delivery via NEF (non-roaming)** + +##### 6.30.1.2.2 Roaming reference architectures + + + +This diagram illustrates the service based architecture for small data delivery via NEF in a roaming scenario with home routing. The architecture is split into two parts by a vertical dashed line: the Visited PLMN (VPLMN) on the left and the Home PLMN (HPLMN) on the right. In the VPLMN, the UE is connected to the (R)AN, which is connected to the AMF via the N2 interface. The UE also connects to the AMF via the N1 interface. The AMF is connected to the SMF via the Nsmf interface and to the IWG-NEF via the Namf interface. The IWG-NEF connects to the SBI via the Nnef interface. In the HPLMN, the SMF is connected to the UDM via the Nudm interface and to the NEF via the Nsmf interface. The NEF connects to the SBI via the Nnef interface, and the AF is connected to the SBI via the Naf interface. + +Figure 6.30.1.2.2-1: Simplified Service Based Architecture for small data delivery via NEF (roaming with home routed scenario). + +**Figure 6.30.1.2.2-1: Simplified Service Based Architecture for small data delivery via NEF (roaming with home routed scenario)** + +### 6.30.2 Functional Description + +In addition to clause 6.1.2, the following principles apply: + +- Support of NIDD API: + - The NIDD API is supported for PDU sessions of type unstructured. + - The NEF supports the NIDD API towards the SCS/AS for both non-roaming and home-routed roaming scenarios. + - Whether or not the NIDD API shall be invoked for a PDU session is determined by a per DNN per S-NSSAI Invoke NEF Selection indication in the subscription. + - If the subscription includes an Invoke NEF Selection indication and an NEF ID for the S-NSSAI / DNN requested by the UE, then the SMF selects that NEF for the small data PDU session. + - The NEF ID for a given S-NSSAI / DNN in the subscription can be updated by means of the NIDD configuration procedure. + +- The NEF performs buffering for unstructured DL data received via the NIDD API while the UE is unreachable. + +NOTE 1: See Solution 1 for UPF based data transfer. + +- API Exposure for Small Data: + - The NEF exposes the NIDD Configuration, MT NIDD, and MO NIDD APIs that are described in TS 23.682 [6] on the N33/Nnef reference point. +- Routing Unstructured Data Between the NEF and AF: + - Consistent with the method that is used in EPS and described in TS 23.682 [6], the NEF uses provisioned policies to map an AF Identity and UE Identity to a DNN/S-NSSAI combination when the Reliable Data Service is not enabled. When the Reliable Data Service is enabled, the NEF determines the association based on RDS port numbers and provisioned policies that may be used to map AF identities and User identity to an DNN. + +### 6.30.3 Support of EPC interworking + +EPC interworking is enabled by the principles documented in clause 6.1.3 with the following differences: + +- NIDD API is terminated on a co-located NEF (capable of small data transfer) and SCEF, referred to as NEF+SCEF. +- Idle-mode mobility from 5GS to EPS is performed as per the procedure described in TS 23.502 [7] clause 4.11.1.3.2 with the following differences: + - Step 5b: NEF+SCEF maps the PDU session for Data over NAS-SM to an SCEF PDN Connection and sets the Control Plane Only PDN Connection Indication. +- Idle-mode mobility from EPS to 5GS is performed as per the procedure described in TS 23.502 [7] clause 4.11.1.3.3 with the following differences: + - AMF indicates support of CIoT Optimizations when requesting the UE context from the MME via N26; + - for a PDN connection for which Control Plane Only PDN Connection Indication is set: + - SMF selects a NEF; + - in the case of home-routed roaming: + - Step 14: the AMF selects a V-SMF supporting small data over NAS-SM; + - Step 14: V-SMF selects a IWK-NEF. + - When the Invoke NEF Selection flag is present in the UE's subscription information for the PDU Session, the identified NEF will point to an SCEF+NEF if EPC Interworking is supported. + +### 6.30.4 Procedures + +#### 6.30.4.1 PDU Session Establishment (non-roaming) + +It takes the PDU Session Establishment procedure as described in TS 23.502 [7], subclause 4.3.2.2.1 as the baseline. + + + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant AMF + participant SMF + participant NEF + participant UDM + participant AF + + Note left of UE: 1. PDU Session Establishment Request (DNN, S-NSSAI, "Data over NAS-SM requested") + UE->>AMF: 1. PDU Session Establishment Request (DNN, S-NSSAI, "Data over NAS-SM requested") + Note right of AMF: 2. SMF selection + AMF->>SMF: 3. Nsmf_PDUSession_CreateSMContext Request/Response + SMF->>UDM: 4. Registration/subscription retrieval/subscribe for updates + Note right of SMF: 5. SMF-NEF Connection + SMF->>NEF: 5. SMF-NEF Connection + Note right of AF: 6. NIDD Configuration + AF->>NEF: 6. NIDD Configuration + Note right of SMF: 7. Namf_Communication_N1N2MessageTransfer + SMF->>AMF: 7. Namf_Communication_N1N2MessageTransfer + Note left of UE: 8. NAS transport(PDU session ID, SM: PDU session establishment response) + AMF->>UE: 8. NAS transport(PDU session ID, SM: PDU session establishment response) + +``` + +Sequence diagram of PDU Session Establishment enabling Data over NAS-SM via NEF (non-roaming). The diagram shows interactions between UE, NG-RAN, AMF, SMF, NEF, UDM, and AF. The process involves: 1. UE sends PDU Session Establishment Request (DNN, S-NSSAI, 'Data over NAS-SM requested') to AMF. 2. AMF performs SMF selection. 3. AMF sends Nsmf\_PDUSession\_CreateSMContext Request/Response to SMF. 4. SMF sends Registration/subscription retrieval/subscribe for updates to UDM. 5. SMF establishes SMF-NEF Connection. 6. AF sends NIDD Configuration to NEF. 7. SMF sends Namf\_Communication\_N1N2MessageTransfer to AMF. 8. AMF sends NAS transport (PDU session ID, SM: PDU session establishment response) to UE. + +**Figure 6.30.4.1-1: PDU Session Establishment enabling Data over NAS-SM via NEF (non-roaming)** + +- The UE sends a PDU session establishment request message as SM payload of a NAS transport message. The NAS transport message contains PDU session ID along with other regular information e.g. DNN, S-NSSAI, etc. if applicable. + - The AMF determines if the PDU Session uses NAS-SM to transfer PDUs. If the PDU Session will use NAS-SM to transfer PDUs, the AMF selects an SMF that supports Data over NAS-SM if available for the requested DNN, and S-NSSAI. The AMF stores the association of the PDU Session ID and the selected SMF ID in the UE context. +- NOTE 1: How the AMF determines if the PDU Session uses NAS-SM to transfer PDUs will be determined as part of the Key Issue 15 conclusion. +- The AMF invokes Nsmf\_PDUSession\_CreateSMContext request including DNN, S-NSSAI, PDU Session ID. The SMF replies with an Nsmf\_PDUSession\_CreateSMContext Response. The AMF also indicates to the SMF if the PDU Session uses NAS-SM to transfer PDUs. + - The SMF registers with the UDM and retrieves the Session Management Subscription data for the corresponding SUPI, DNN and S-NSSAI. If the subscription includes an Invoke NEF Selection indication for the DNN and S-NSSAI indicated by UE, the SMF retrieves the NIDD information such as External Group Identifier, External Identifier or MSISDN, AF ID and decides to transfer data to the DN via NEF. The SMF selects the NEF based on the UE subscription profile. + - The SMF configures the NEF for data transfer. This procedure is described in clause 6.30.4.6. + - If NIDD configuration has been performed by the AF with the NEF, then the procedure continues at step 7. If the policies that may be used to map SUPI, DNN, S-NSSAI and Reliable Data Service Port Numbers (if applicable) to an AF Identity are provisioned in the NEF then the procedure continues at step 7. If NIDD configuration has not been performed by the AF with the NEF and AF Identity is configured at NEF then the NEF may initiate NIDD Configuration as described in clause 6.30.4.7. +- If an AF identity is not been provisioned for the procedure of clause 6.30.4.7 then the PDU session establishment fails. +- The SMF sends a PDU Session Establishment Accept providing indication that Data Over NAS-SM is enabled for this PDU session without including the N2 SM container. + - The AMF forwards the NAS message to the UE. + +#### 6.30.4.2 PDU Session Establishment (home-routed roaming) + +This procedure takes the PDU Session Establishment procedure as described in TS 23.502 [7], subclause 4.3.2.2.2 as the baseline. + + + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant AMF + participant V-SMF + participant IWK-NEF + participant H-SMF + participant NEF + participant UDM + + UE->>AMF: 1. PDU Session Establishment Request +(DNN, S-NSSAI, "Data over NAS-SM +requested") + Note right of AMF: 2. SMF +selection + AMF->>V-SMF: 3. Nsmf_PDU +Session_Create +SMContext +Request/Response + V-SMF->>H-SMF: 4. Nsmf_PDU +Session_Create +SMContext +Request + H-SMF<->UDM: 5. Registration/subscription +retrieval/subscribe for updates + H-SMF->>V-SMF: 6. Nsmf_PDU +Session_Create +SMContext +Response + Note over V-SMF, NEF: 7. Connection establishment between V-SMF and NEF via +IWK-NEF + AMF->>V-SMF: 8. Namf_Communication_ +N1N2MessageTransfer + AMF->>UE: 9. NAS transport(PDU session ID, +SM: PDU session establishment response) + +``` + +Sequence diagram for PDU Session Establishment (home-routed roaming) via NEF. Lifelines: UE, NG-RAN, AMF, V-SMF, IWK-NEF, H-SMF, NEF, UDM. The process involves a request from UE to AMF, SMF selection, Nsmf\_PDUSession\_CreateSMContext request from AMF to V-SMF, forwarding to H-SMF, registration with UDM, response back to V-SMF, connection establishment between V-SMF and NEF via IWK-NEF, and finally NAS transport from AMF to UE. + +**Figure 6.30.4.2-1: PDU Session Establishment enabling Data over NAS-SM via NEF (home-routed roaming)** + +1. The UE sends a PDU session establishment request message as SM payload of a NAS transport message. The NAS transport message contains PDU session ID along with other regular information e.g. DNN, S-NSSAI, etc. if applicable. +2. The AMF determines if the PDU Session uses NAS-SM to transfer PDUs. If the PDU Session will use NAS-SM to transfer PDUs, the AMF selects an SMF that supports Data over NAS-SM if available for the requested DNN, and S-NSSAI. The AMF stores the association of the PDU Session ID and the selected SMF ID in the UE context. + +NOTE 1: How the AMF determines if the PDU Session uses NAS-SM to transfer PDUs will be determined as part of the Key Issue 15 conclusion. + +3. The AMF invokes *Nsmf\_PDUSession\_CreateSMContext* request including DNN, S-NSSAI, PDU Session ID. The V-SMF replies with an *Nsmf\_PDUSession\_CreateSMContext* Response. The AMF also indicates to the V-SMF if the PDU Session uses NAS-SM to transfer PDUs. +4. The V-SMF sends the *Nsmf\_PDUSession\_CreateSMContext* request to the H-SMF. The V-SMF also indicates to the H-SMF if the PDU Session uses NAS-SM to transfer PDUs. +5. The H-SMF registers with the UDM and retrieves the Session Management Subscription data for the corresponding SUPI, DNN and S-NSSAI. If the subscription includes an Invoke NEF Selection indication for the DNN and S-NSSAI indicated by UE, the H-SMF informs the V-SMF to transfer data to the DN via NEF. +6. The H-SMF responds to the V-SMF. +7. The V-SMF configures the NEF via the IWK-NEF for data transfer. + +8. The V-SMF sends a PDU Session Establishment Accept providing indication that Data Over NAS-SM is enabled for this PDU session without including the N2 SM container. +9. The AMF forwards the NAS message to the UE. + +#### 6.30.4.3 Mobile Originated Data Transport via NAS-SM and N6 (NEF Anchored) + +The Mobile Originated Data Transport Procedure of Solution 1 (see clause 6.1.4.2) is used, with the following modifications: + +- The UPF is changed to an NEF. +- Between steps 5 and 6, the NEF uses the MO NIDD Indication procedure of TS 23.682 [6], clause 5.13.4 to provide the data to the AF. + +#### 6.30.4.4 Mobile Terminated Data Transport via NAS-SM and N6 (NEF Anchored) + +The Mobile Terminated Data Transport Procedure of Solution 1 (see clause 6.1.4.3) is used, with the following modifications: + +- The UPF is changed to an NEF. +- The NEF may buffer DL data as described in TS 23.682 [6]. +- The procedure is initiated by the AF invoking the MT NIDD Submit Request as described in TS 23.682 [6], clause 5.13.3. +- If UL Data is included in step 14, then the NEF will uses the MO NIDD Indication procedure of TS 23.682 [6], clause 5.13.4 to provide the data to the AF. + +#### 6.30.4.5 NIDD Configuration for Data Transport via NAS-SM + +The NIDD Configuration procedure will take place between the AF and NEF as described in TS 23.682 [6], clause 5.13.2. The NEF uses the UDM/UDR to authorise the NIDD Configuration. + +#### 6.30.4.6 SMF-NEF Connection + + + +``` + +sequenceDiagram + participant UE + participant SMF + participant ROAMING as ROAMING (IWK-NEF) + participant NEF + + Note left of UE: 1. PDU Session Establishment procedure + SMF->>NEF: 2. Create NEF Connection Request + NEF-->>SMF: 3. Create NEF Connection Response + +``` + +Sequence diagram illustrating the SMF-NEF Connection Establishment Procedure. The diagram shows the interaction between UE, SMF, ROAMING (containing IWK-NEF), and NEF. Step 1: PDU Session Establishment procedure between UE and SMF. Step 2: SMF sends 'Create NEF Connection Request' to NEF via IWK-NEF. Step 3: NEF sends 'Create NEF Connection Response' back to SMF via IWK-NEF. + +**Figure 6.30.4.6-1: SMF-NEF Connection Establishment Procedure** + +1. UE performs steps 1-4 of PDU Session Establishment Procedure for Data transfer over NAS-SM described in clause 6.30.4.1. The SMF receives the Session Management Subscription data for the corresponding SUPI, DNN and S-NSSAI that is associated with an Invoke NIDD API indication, NEF ID and NIDD information such as External Group Identifier, External Identifier or MSISDN and AF ID. +2. If the subscription information corresponding to DNN and S-NSSAI includes Invoke NIDD API indication, the SMF shall create a PDU session towards the NEF. The SMF does so by sending a Create NEF Connection Request (User Identity, PDU session ID, NEF ID, NIDD information, S-NSSAI, DNN) message towards the + +NEF. If the IWK-NEF receives the Create NEF Connection Request message from the SMF, it shall forward it toward the NEF. + +If an AF has performed the NIDD Configuration procedure (see NIDD configuration procedure of TS 23.682 [6]) with the NEF for User Identity received in step 2, then step 3 is executed. If no AF has performed the NIDD Configuration procedure with the NEF for the User Identity, then the NEF initiates a NIDD Configuration by NEF procedure (see clause 6.30.4.7) with AF. + +- The NEF creates an NEF PDU session Context for the user identified via User Identity and PDU session ID. The NEF sends a Create NEF Connection Response (User Identity, PDU session ID, NEF ID, S-NSSAI, DNN) message towards the SMF confirming establishment of the PDU session to the NEF for the UE. If the IWK-NEF receives the Create NEF Connection Response message from the NEF, it shall forward it toward the SMF. + +#### 6.30.4.7 NIDD Configuration by NEF + +Figure 6.30.4.7-1 illustrates the procedure for configuring necessary information triggered by NEF for data delivery via the NIDD API. + + + +``` + +sequenceDiagram + participant UDM + participant NEF + participant AF + Note over UDM, AF: 0. PDU Session Establishment procedure + NEF->>AF: 1. NIDD Configuration Trigger + AF->>NEF: 2. NIDD Configuration Request + NEF->>UDM: 3. NIDD Authorization Request + Note over UDM: 4. UDM handling + UDM->>NEF: 5. NIDD Authorization Response + NEF->>AF: 6. NIDD Configuration Response + +``` + +Sequence diagram illustrating the NIDD Configuration by NEF Procedure. The diagram shows interactions between UDM, NEF, and AF. The sequence starts with '0. PDU Session Establishment procedure'. Then, '1. NIDD Configuration Trigger' is sent from NEF to AF. '2. NIDD Configuration Request' is sent from AF to NEF. '3. NIDD Authorization Request' is sent from NEF to UDM. '4. UDM handling' is a self-call on the UDM. '5. NIDD Authorization Response' is sent from UDM to NEF. Finally, '6. NIDD Configuration Response' is sent from NEF to AF. + +**Figure 6.30.4.7-1: NIDD Configuration by NEF Procedure** + +- UE performs steps 1-5 of PDU Session Establishment Procedure for Data transfer over NAS-SM described in clause 6.30.4.1. If NIDD Configuration has not been performed by the AF with the NEF and AF Identity is configured at NEF then the NEF may initiate NIDD Configuration. +- The NEF sends an NIDD Configuration Trigger (External Group Identifier, External Identifier or MSISDN, AF ID, NEF ID) message to the AF for asking the NIDD Configuration Request for the UE identified by External Identifier or MSISDN. +- The AF sends an NIDD Configuration Request message to the NEF as described in TS 23.682 [6], clause 5.13.2. The NIDD Configuration Request includes the Authorization Token. The Authorization Token is used for authorizing the AF by the UDM (the Authorization Token is shared between UDM and AF during SLA). +- The NEF sends an NIDD Authorization Request (External Group Identifier, External Identifier or MSISDN, S-NSSAI, DNN, AF ID, Authorization Token) message to the UDM to authorize the NIDD configuration request for the received External Identifier or MSISDN. +- The UDM examines the NIDD Authorization Request message with Authorization Token. If this check fails, the UDM follows step 5 and provides a result indicating the reason for the failure condition to the NEF. +- The UDM sends an NIDD Authorization Response (SUPI and MSISDN or External Identifier, Result) message to the NEF to acknowledge acceptance of the NIDD Authorization Request. The SUPI and, if available, the MSISDN (when NIDD Configuration Request contains an External Identifier) or if available, External Identifier(s) (when NIDD Configuration Request contains an MSISDN) are returned by the UDM in this + +message. This allows the NEF to correlate the AF request received in step 1 of this procedure with the PDU session to be established for this subscriber if this procedure takes place during a PDU Session Establishment procedure. + +6. The NEF sends an NIDD Configuration Response message as described in TS 23.682 [6], clause 5.13.2 to the AF to acknowledge acceptance of the NIDD Configuration Request. If the NIDD Configuration was accepted, the NEF assigns a TLTRI to the NIDD Configuration and creates an association between the TLTRI, External Identifier or MSISDN, SUPI, and PDU session ID which is received from the SMF in step 5 of the PDU Session Establishment procedure in clause 6.30.4.1. In the MT NIDD procedure, the NEF will use TLTRI and External Identifier or MSISDN to determine the SUPI and PDU session ID of PDU session for delivering non-IP data. In the MO NIDD procedure, the NEF will use the SUPI and PDU session ID to obtain the TLTRI, External Identifier or MSISDN. + +### 6.30.5 Impacts on existing entities and interfaces + +The same impacts indicated in clause 6.1.5 apply, with the following differences: + +NEF: + +- Support for extended buffering. +- Support for the NIDD Configuration, MT NIDD, and MO NIDD APIs as described in TS 29.122 [9] and TS 23.682 [6]. +- Support for services on the N29 interface with the SMF for Unstructured PDU Sessions (similar to the functionality that is available on the N4 interface between the SMF and UPF). + +### 6.30.6 Evaluation + +Solution 30 is part of Solution 1 and allows the exchange of infrequent unstructured small data via NIDD API. The NEF supports the NIDD API towards the AF for both non-roaming and home-routed roaming scenarios. The same pros and cons of Solution 1 apply. + +This solution successfully addresses Key Issues 1 (Support API(s) for infrequent small data transmission and capability exposure to AF). + +## 6.31 Solution 31: Deferring of Periodic Registration Update + +### 6.31.1 Introduction + +This solution applies to Key issue 4 (Power Saving Functions) as maximize sleeping period of the UE when the UE applies extended idle mode DRX. + +During in idle mode period (i.e. CM-IDLE), UE repeatedly performs paging monitoring procedure in every Paging Occasion to check incoming call. Also, UE shall perform periodic Registration Update procedure to update reachability with AMF. In other words, major jobs of the UE in idle mode period is that paging reception and periodic Registration Update. It is clear that maximization of idle period is important for the extreme power saving requirements. The time for paging reception is an appointment between UE & eNB (absolute time calculation) so it can't be changed. However, the time for periodic Registration update is an appointment between UE & AMF. Therefore the time for Registration update is adjustable if the AMF is aware & allowed of this. + +### 6.31.2 Functional Description + +When the AMF configures idle mode eDRX via NAS procedure (i.e. Registration Update), the AMF can additionally provide the applicability of "Deferring of Periodic Registration Update" for further power saving. If the UE receives the indication, the UE can defer the time for next Registration Update procedure to the nearest Paging Occasion time when the periodic Registration Update timer is expired. So the UE can avoid waking-up twice when the time for paging reception and the time for execution of Registration Update is adjacent. + +If the AMF indicates to use "Deferring of Periodic Registration Update", then the AMF should respect the UE's behaviour for deferring of periodic Registration Update. Therefore the AMF should take the eDRX period into account when the AMF calculates mobile reachable timer. Support of the "Deferring of Periodic Registration Update" is optional both for UE and AMF. + +Editor's note: whether this batching of periodic registration update and paging reception is covered by implementation is FFS. + +### 6.31.3 Support of interworking + +Editor's note: This clause describes if and how EPC-5GC interworking is supported in this solution. + +### 6.31.4 Procedures + +Figure 6.31.4-1 illustrates the procedure of configuring of Deferring of Periodic Registration Update. + + + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant AMF + Note left of UE: + UE->>AMF: 1. Registration Update (eDRX parameter + Deferring of Periodic Registration Update is required) + AMF-->>UE: 2. Registration Accept (eDRX parameter + Deferring of Periodic Registration Update is allowed) + Note left of UE: 3a. UE is allowed to defer the next periodic Registration update by the nearest Paging Occasion when the periodic registration update timer is expired. + Note right of AMF: 3b. AMF applies eDRX period when derives Mobile reachable timer + +``` + +The diagram shows a sequence of interactions between a User Equipment (UE), a Next Generation Radio Access Network (NG-RAN), and an Access and Management Function (AMF). + 1. The UE sends a 'Registration Update' message to the AMF, which includes an 'eDRX parameter' and an indication that 'Deferring of Periodic Registration Update is required'. + 2. The AMF responds with a 'Registration Accept' message, indicating that 'eDRX parameter + Deferring of Periodic Registration Update is allowed'. + 3. Two parallel actions occur: + - 3a. The UE is allowed to defer the next periodic Registration update by the nearest Paging Occasion when the periodic registration update timer is expired. + - 3b. The AMF applies the eDRX period when deriving the Mobile reachable timer. + +Sequence diagram illustrating the configuration of Deferring of Periodic Registration Update between UE, NG-RAN, and AMF. + +Figure 6.31.4-1: Configuration of Deferring of Periodic Registration Update + +1. The UE may indicate capability of "Deferring of Periodic Registration Update" while the UE is performing NAS procedures (i.e. Registration) along with desired idle mode eDRX parameters for power saving. +2. If the AMF accepts the usage of Deferring of Periodic Registration Update, the AMF should indicate this via Registration Accept message. +- 3a. The UE determines the next periodic Registration Update time. If the Deferring of Periodic Registration Update indicated by the AMF, the UE can defer the time for next Periodic Registration Update procedure to the time for nearest Paging Occasion. + +Editor's note: Necessity of the indication "Deferring of Periodic Registration Update is required" by a UE is FFS. + +- 3b. The AMF applies eDRX period to set Mobile Reachable Timer and control of PPF (Paging Proceed Flag). + +### 6.31.5 Impacts on existing entities and interfaces + +Editor's note: This clause describes impacts to existing entities and interfaces. + +In the AMF: + +- Considering eDRX period for Mobile Reachable timer handling. + +In the UE: + +- Indicating the capability of Deferring of Registration Update to AMF. Also adjust (defer) the execution time for next periodic Registration Update to the time for nearest PO. + +### 6.31.6 Evaluation + +**Editor's note:** This clause provides an evaluation of the solution. + +## 6.32 Solution 32: MO Data Buffering in the UE + +### 6.32.1 Introduction + +This clause presents a solution for Key Issue 5 - UE Tx Power Saving Functions. + +This solution is suitable for UEs whose traffic patterns can be characterized as non-delay sensitive or high-latency. For example, many IoT applications are characterised by the fact that they collect data and send the data to one or more AF(s) (i.e. SCS/AS(s)) in a delay tolerant manner; e.g. they collect data and it is acceptable if the data is not sent to the SCS/AS(s) until hours after it is collected. + +The premise of the solution is that when a delay tolerant application on the UE decides to initiate MO traffic and the UE is in RRC Idle Mode, the UE may decide to delay establishing an RRC Connection and transmitting the MO data until the UE decides that it can be sent with relatively low power. For example, when the UE is in good coverage, is able to use a non-3GPP AN, or is in a particular location. + +### 6.32.2 Functional Description + +The following principles apply to this solution: + +- In order to minimize UE power consumption, the UE delays establishing an RRC connection for sending MO data until it is able to transmit with relatively low power. Thus, MO data might not be sent when the data is collected. The UE may send the data when conditions are suitable to the UE and without regard to whether the AF(s) (i.e. SCS/AS(s)) are ready to receive the data. + +**Editor's note:** It is FFS how the UE determines that traffic is delay tolerant (e.g. it may be implementation dependent and not specified, configured via OMA DM, OMA LwM2M, UICC Application Configuration, or configured NAS/AS signalling). + +**Editor's note:** It is FFS how and when the UE decides to begin transmitting (e.g. it may be implementation dependent and not specified or configuration dependent (e.g. configured signal quality threshold, configured AN type, configured location)). + +### 6.32.3 Support of EPC interworking + +**Editor's note:** This clause describes if and how EPC-5GC interworking is supported by this solution. + +### 6.32.4 Procedures + +Figure 6.32.4-1 shows the procedure for delaying MO data until it can be transmitted with relatively low power. + + + +``` + +sequenceDiagram + participant UE + participant 5GC + participant AF + Note left of UE: 1. Collect Data + Note left of UE: 2. Coverage Improves + UE->>AF: 3. MO Data + +``` + +Sequence diagram illustrating the procedure for buffering MO data in the UE. The diagram shows three lifelines: UE, 5GC, and AF. The UE performs two internal steps: '1. Collect Data' and '2. Coverage Improves'. After these steps, the UE sends a message labeled '3. MO Data' to the AF. The 5GC lifeline is shown but not involved in the sequence. + +**Figure 6.32.4-1: Procedure for Buffering MO Data in the UE** + +1. An application on the UE collects data. + +NOTE: If there are multiple UE applications, they may collect data separately or in a coordinated manner. + +2. The UE delays initiating MO data because it is in weak coverage. How the UE ultimately decides when to send the MO data is implementation and/or application dependent and is not specified. +3. The UE sends the application data to the AF. + +### 6.32.5 Impacts on existing entities and interfaces + +**Editor's note:** This clause describes impacts to existing entities and interfaces. + +### 6.32.6 Evaluation + +**Editor's note:** This clause provides an evaluation of the solution. + +## 6.33 Solution 33: Delayed Paging Response + +### 6.33.1 Introduction + +This solution propose a solution for Key Issue 5 - UE Tx Power Saving Functions. + +UE transmitting power is sensitive to the link quality, for example, the UE's transmitting power needed is about 100 times higher when RSRP is -100dBm compared to when RSRP is 80dBm. In the current mechanisms, when a page arrives, the UE will attempt to transmit the page response in any coverage condition, e.g. in good, in weak coverage, or even in enhanced coverage. When in weak coverage, UE might transmit with maximum TX power, and maybe try many times; when in enhanced coverage, UE will repeat the TX signal tens or hundred times, all of which consume significant amount of UE battery power. + +Some IoT devices or applications are delay tolerant i.e. the data exchange is not urgent, (e.g. IoT device software update, advertisement push, notification message etc). This solution intends to avoid the UE responds the paging in a very bad coverage, which would consumes much more UE battery power. + +This solution targeting moving mobile terminals and may not be applied to stationary mobiles for which coverage is unchanged most of the time. + +### 6.33.2 Functional Description + +This clause describes a solution for delayed response to the paging by the UE when paged for delay tolerant services. A UE capable of delayed paging response indicates its capability for delayed paging during registration and the UE is + +allocated a delayed paging response window. The AMF can obtain the delayed paging response window from the specific AF which UE subscribes. When such a UE is paged with indication for delayed paging and the radio coverage conditions are poor, the UE may decide to delay the transmission of the response to the paging until radio conditions improve, while still within the delayed paging response window. + +Some assumptions and requirements are made: + +- 1) The AF may subscribe for delayed paging service so that it is notified when the UE responds to the paging. +- 2) The AMF can determine the delayed paging response window from the subscription data. +- 3) The AMF can obtain the delay tolerant information via the Namf\_Communication\_N1N2MessageTransfer service operation related to the incoming downlink data. +- 4) The AF or the UPF can buffer the downlink data so it is available at least during the delayed paging response window. +- 5) The mechanism to establish the PDU Session and data transmission depends on the solution defined in other key issues. +- 6) The UE monitors all paging occasions (POs) including POs within the delayed paging response window. In case the UE uses the eDRX feature the UE monitors only the PO's scheduled within the PTW that was received during eDRX negotiation. + +### 6.33.3 Support of EPC interworking + +Not applicable since there is no corresponding mechanism specified in EPC. + +### 6.33.4 Procedures + + + +``` + +sequenceDiagram + participant AF + participant NEF + participant SMF/UPF + participant AMF + participant gNB + participant UE + + Note right of AMF: 1) Subscribe for delayed paging response notification + UE->>AMF: 2) Registration Request (delayed_paging_capability) + Note right of AMF: 3) The AMF gets the UE subscription information and verifies the UE is allowed delay tolerant paging + AMF->>UE: 4) Registration Accept (delayed paging response window) + AF->>NEF: 5) Nnef_DataTransfer (external UE Id, delayed_paging_ind) + NEF->>AMF: 6) Namf_Communication_N1N2MessageTransfer (UE Id, delayed_paging_ind) + AMF->>gNB: 7) Paging Request (UE Id, delayed_paging_ind) + gNB->>UE: 8) Paging (UE Id, delayed_paging_ind) + Note left of UE: 9) UE reads the paging and may delay the paging until better radio conditions within the delayed paging response window + UE->>AMF: 10) Paging Response/Service Request + Note right of AMF: 11) If no paging response is received within delayed paging response window, the AMF may fall back to normal paging. + AMF->>AF: 12) Notification (UE Id, response to delayed paging) + +``` + +Sequence diagram illustrating the paging procedure for delay tolerant UEs and applications. The diagram shows interactions between UE, gNB, AMF, SMF/UPF, NEF, and AF. The process starts with the AF subscribing for delayed paging response notification (1). The UE sends a Registration Request with delayed\_paging\_capability (2). The AMF verifies the UE is allowed delay tolerant paging (3). The AMF sends a Registration Accept with delayed paging response window (4). The AF sends Nnef\_DataTransfer with external UE Id and delayed\_paging\_ind (5). The AMF sends Namf\_Communication\_N1N2MessageTransfer with UE Id and delayed\_paging\_ind (6). The gNB sends a Paging Request with UE Id and delayed\_paging\_ind (7). The gNB sends a Paging with UE Id and delayed\_paging\_ind (8). The UE reads the paging and may delay the paging until better radio conditions within the delayed paging response window (9). The UE sends a Paging Response/Service Request (10). The AMF checks if no paging response is received within the delayed paging response window (11). The AMF sends a Notification with UE Id and response to delayed paging (12). + +**Figure 6.33.4-1: Paging for delay tolerant UEs and applications** + +1. An AF may subscribe with the SMF/UPF/AMF for delayed paging response, e.g. to be notified when the UE responds to delayed paging. The AF may also provision the delayed tolerant service level information via the NEF, this information is used by the AMF to determine the delayed paging response window. +2. UE initiates Registration Request, indicating to the AMF that UE is delayed paging capable. + +3. The AMF obtains UE subscription information to verify the UE attributes and the subscribed service characteristic information. The AMF may obtain a delayed paging response service information from the subscription information. +4. The AMF accepts the registration request from the UE and returns delayed paging response window. The AMF shall take into account the subscription information when determining the delayed paging response window. +5. When an AF wants to exchange delay tolerant data with a UE, the AF invokes downlink Nnef\_DataTransfer (external UE Id, delayed\_paging\_ind). The delayed\_paging\_ind parameter is present when the AF request is for delayed paging. +6. The NEF derives the UE identity from UE's External identifier and triggers Namf\_Communication\_N1N2\_message\_transfer service operation. +- 7-8. When AMF receives the Namf\_Communication\_N1N2MessageTransfer with delayed paging indication, the AMF sends paging message to the UE with delayed paging indicator. The AMF may page the UE in registration area granularity in order to avoid the case where the UE has moved out of the paging area, e.g. the last known cell or tracking area. The AMF can also page the UE within a narrower area (e.g. the cell list) than the registration area in order to save paging overhead, and if the AMF does not receive UE paging response during the delayed paging response window, AMF can re-page the UE in the whole registration area. +- 9-10. After receiving the paging message with delayed paging indication, the UE may delay the response to the paging if current radio conditions are not good (based on UE implementation or radio signal quality thresholds configured in the UE via OMA DM, for example) until better radio conditions within the delayed paging response window. If signal quality thresholds are used for the UE to decide when the radio condition are good or not good, the operator may configure the UE with lower signal quality thresholds so that the UE employs the paging delay behaviour only when the current radio coverage is really bad or the worst coverage (e.g. the UE is close to cell borders or coverage hole). This way the UE's chances to get better radio coverage conditions before the delayed paging response window expires are much higher. + +NOTE 1: If a UE, based on implementation, is determined to be temporary stationary, then the UE may decide not to delay the page response even if the radio conditions are not good. + +11. The expected Paging Response/Service Request from the UE is received within the delayed paging response window. If the paging response is not received after the delayed paging response window timer expires, AMF will fall back to normal paging and will re-page the UE with normal paging. +12. The AMF notifies the AF about the UE response to the delayed paging. + +NOTE 2: If the UE receives a normal paging message during the delayed paging response window, the UE shall respond to this paging message. All pending DL data can then be delivered including the DL data that triggered the delayed paging message. + +### 6.33.5 Impacts on existing entities and interfaces + +NEF: + +- New API allowing the AF to provision the network via the NEF with delayed tolerant service requirements. + +AMF: + +- AMF to support the new function of delayed tolerant paging response window e.g. acquire new subscription info, determine the window size, and provision the delayed paging response window to the UE during Registration procedure. + +RAN: + +- The Uu Paging message need to include one new bit, the "delayed paging indicator", so the UE can differentiate whether the page is for delay tolerant DL data or not. + +UE: + +- UE to support delayed paging capability indication within the Registration Request message and the new behaviour associated with this feature. + +### 6.33.6 Evaluation + +In case the UE can delay the page response and corresponding communication until the radio channel improves, the UE can save power. However, there is no guarantee that the radio channel will improve during the delayed paging window, the radio channel could even deteriorate and make the power consumption worse. Based on UE implementation, the UE needs to evaluate the opportunity/risk and determine whether to perform the delayed page response taking into consideration e.g. the added power consumption while monitoring the radio channel and the expected mobility. + +## 6.34 Solution 34: Provisioning of UE TX power saving parameters + +### 6.34.1 Introduction + +This solution addresses the Key Issue#5 - "UE TX Power Saving Functions" and Key Issue #13 - "Support for Expected UE Behaviour". + +### 6.34.2 Functional Description + +UE TX power saving is intended to optimize the power consumption of UE when in bad or weak coverage. This solution has following feature - + +1. UE applying TX power saving feature are assumed to be Delay Tolerant UEs. Such UE shall be configured as Delay Tolerant, or for Low Access Priority, or Unified Access Control Access Priority 1. +2. UE determines bad/weak coverage based on locally configured minimum signal quality threshold i.e. if the serving cell signal drops below a configured minimum signal quality threshold. UEs supporting Enhanced Coverage may derive configured minimum signal quality threshold from CE Mode A & B criterion. For NB-IoT UEs CE level 1 or CE level 2 criterion can be used to determine minimum signal quality threshold. +3. Such UE is provisioned with the following UE TX power saving parameters - + - **MO Data buffering Indicator** - This indicates if MO data buffering is enabled or disabled in the UE when the UE is in bad or weak coverage condition. + - **MO Data Buffer Timer** - Maximum Time for MO data buffering i.e. maximum time for transmission delay. This timer is started when UE has MO data to send. If running, this timer is stopped when the UE is in good coverage. On expiry of this timer UE may transmit buffered MO data even if coverage condition is not improved. + +In addition, following parameters may also be provisioned: + +- **Suggested number of MO PDU to buffer** - Indicated suggested maximum number of MO PDUs to be buffered by the UE. In absence of this parameter number of MO PDUs to be buffered is left to the UE implementation. + - **Exception Data buffering Indicator** - This indicates whether or not to also buffer Exception data when the UE is in bad or weak coverage conditions. +4. UE TX power saving parameters may be pre-configured in the UE (e.g. at manufacturing) or by using OTA mechanisms. + 5. UE TX power saving parameters may be included part of Expected UE Behaviour parameters specified in clause 4.15.6.3 of TS 23.502 [7]. Similar to Expected UE Behaviour parameters, UE TX power saving parameters may be provisioned in AMF from AS/AF via NEF (as specified in clause 4.15.6 of TS 23.502 [7]). AMF provides these parameters to the UE via Registration or Configuration Update procedure. + +### 6.34.3 Support of EPC interworking + +No additional impact for EPC interworking. UE that supports connectivity to both EPC and 5GC can be configured with UE Tx power saving parameters and can apply those for MO data buffering when in bad/weak coverage. The UE Tx power saving parameters only apply when the UE is connected to the 5GC. + +### 6.34.4 Procedures + +5GS may expose the capability of UE TX power saving towards external AF/AS, NEF may provide APIs that allows external AF/AS to control UE TX power saving parameters. UE TX power saving parameters may be included part of Expected UE Behaviour parameters specified in clause 4.15.6.3 of TS 23.502 [7]. Similar to Expected UE Behaviour parameters, UE TX power saving parameters may be provisioned in AMF from AS/AF via NEF (as specified in clause 4.15.6 of TS 23.502 [7] and Solution 15: External parameter provisioning in the 5GC). AMF sends UE TX power saving parameters to the UE via registration or configuration update procedure. UE TX power saving parameters value provided by the network overrides any pre-configured value in the UE. + +### 6.34.5 Impacts on existing entities and interfaces + +UE: + +- Configuration of UE TX power saving parameters for MO data buffering as specified in clause 6.34.2. + +NEF: + +- Capability exposure via API to allows external AF/AS to control UE TX power saving parameters. + +AMF: + +- For external parameter provisioning there is no additional impact on top of solution 15. + +### 6.34.6 Evaluation + +In order to minimize the impact on the network interfaces the solution allows pre-configuring UE TX power saving parameters in the UE. For the scenarios that require 3rd party application server /function to have control, UE TX power saving parameters can be exposed via NEF APIs. It is expected that NEF APIs are not used to frequently update UE TX power saving parameters else it may lead to signalling overload in the 5GS. However this aspect is not specific to this solution and applies in general to any external parameter provisioning in the 5GC (covered in solution #15 and solution #26). + +## 6.35 Solution 35: Small data delivery + +### 6.35.1 Introduction + +This solution addresses key issue #1, Infrequent Small data communication, key issue #2, Frequent Small data communication, and key issue #9 Support of common north-bound APIs for EPC-5GC Interworking. This solution enables the NEF to support the same NIDD API for both UP and CP data. If the 3rd party Application Server has to select different NEFs just because the small data is routed over the UP or the CP path to the UE, the route inside the 3GPP network would not be transparent to the Application Server. + +### 6.35.2 Functional Description + +#### 6.35.2.1 Architecture + +The 5GS is assumed to support functions for small data communication corresponding to EPS. These EPS functions are aka "NIDD procedures" and involves transmission either using the T8 API (see TS 23.682 [6], clause 5.13) or directly over the SGi (see TS 23.401 [4], clause 4.3.17.8.3.3). + +To support small data communication using an API corresponding to T8 NIDD API, this solution uses NEF which supports the T8 NIDD API and a UPF. The UPF supports small data delivery via user plane connectivity to NEF. Optionally the UPF can be co-located with a NEF. The NEF supports an NIDD API, common for EPC CIoT and 5G CIoT, on the northbound interface. The Small data function is also referred to as "UPF-NEF" in figures below. + +The figure 1 below shows two approaches to support frequent small data communication with the SCS/AS, either: + +- using T8 NIDD API; or +- directly over N6. + +The former refers to the NIDD API over T8 interface specified in TS 23.682 [6]. + +Roaming is supported by using UPF in VPLMN and in HPLMN connected with N9 interface as shown in Figure 6.35.2.1-2 below. + +This solution includes the connectivity between UPF and NEF for Small Data Communication using T8, and meets the following architecture requirements: + +- KI 1 and KI 2 architecture requirements of both IP-based and Non-IP based small data communication. The 5G User Plane is designed to handle IP communication and Non-IP/Unstructured communication. +- Both infrequent and frequent small data communication can be supported with API access for SCS/AS. +- The SMF manages connectivity between UPF and NEF for Small Data Communication using T8. + +Figure 6.35.2.1-1 shows the non-roaming case. In this case, small data is tunnelled between the UPF and NEF via N6n. + +Roaming is supported as shown in Figure 6.35.2.1-2 below. For roaming case, UPF in VPLMN connects to UPF in HPLMN via N9 interface which has connectivity via N6n with NEF in HPLMN. + +The N6n reference point is between UPF and NEF for support of small data transmission using UP transport. From UPF viewpoint, N6n is like N6 but using tunnelling between UPF and NEF in the same PLMN e.g. based on IP encapsulation/decapsulation as shown below in Figure 6.35.2.1-1. + + + +Figure 6.35.2.1-1: 5G non-roaming architecture reference model. This diagram shows the internal architecture of a 5G network. At the top, a Service Based Interface (SBI) connects the Network Slice Selection Function (NSSF), Network Repository Function (NRF), Policy Control Function (PCF), Unified Data Management (UDM), and Application Function (AF). Below the SBI, the AUSF, AMF, SMF, and NEF are connected. The AMF is connected to the User Equipment (UE) via the N1 interface and to the Radio Access Network (RAN) via the N2 interface. The RAN is connected to the UPF via the N3 interface. The SMF is connected to the UPF via the N4 interface. The NEF is connected to the UPF via the N6n interface. The NEF also connects to an external AF via the NIDD API. The diagram is divided into two models: 'Indirect model' (involving the NEF) and 'Direct model' (involving the UPF and AF directly via N6). + +Figure 6.35.2.1-1: 5G non-roaming architecture reference model + + + +Figure 6.35.2.1-2: Roaming 5G System architecture. This diagram illustrates the architecture for roaming. It is split into two parts by a vertical dashed line. On the left (VPLMN), the UE connects to the RAN, which connects to the AMF. The AMF connects to the SMF and the NEF. The SMF connects to the UPF. The UPF connects to the RAN via the N3 interface. The AMF connects to the UE via the N1 interface. The AMF also connects to the SMF via the N2 interface. The SMF connects to the UPF via the N4 interface. The UPF connects to the RAN via the N3 interface. The UPF connects to the NEF via the N6n interface. The NEF connects to an external AF via the NIDD API. On the right (HPLMN), the architecture is similar to the non-roaming case, with the UE, RAN, AMF, SMF, UPF, and NEF. The UPF in the VPLMN connects to the UPF in the HPLMN via the N9 interface. The NEF in the HPLMN connects to the UPF in the HPLMN via the N6n interface. The NEF in the HPLMN also connects to an external AF via the NIDD API. The diagram shows the 'Indirect model' and 'Direct model' for the HPLMN part. + +Figure 6.35.2.1-2: Roaming 5G System architecture + +#### 6.35.2.2 Small data delivery + +The Small data delivery enables UE - SCS/AS communication. The Small data delivery is supported by a NEF which supports the NIDD API and a UPF. The UPF may be dedicated for small data delivery which support N6n connectivity to NEF. + +The UPF-NEF interface for small data communication is assumed to be inside the operator domain: + +Northbound NEF interface: + +- API for NIDD related procedures as specified in the TS 29.122 [9] clause 4.4.5. +- The Common API Framework (CAPIF). + +Southbound NEF interface: + +- N6n interface. +- Forwarding NIDD received over T8 NIDD API to the UE via user plane. +- The southbound interface has a PDU session layer which support PDU Sessions of different types. IPv6 and IPv4 PDU session type shall be supported. PDU Sessions of Unstructured PDU session type (aka "Non-IP") are also supported. +- All types of data (IP data and Unstructured data) should be tunnelled over N6n. NEF is located within the operator network and its interfaces should not be directly exposed to UEs for security reasons. +- Higher layer IoT protocols be used towards the UE on top of the PDU Session layer, but those protocols are outside of the scope of 3GPP. + +The UPF N4 interface: + +- PFCP Session Establishment and N6n tunnelling establishment. +- SMF support for UDM interaction at NIDD Configuration and NIDD Authorization Update (see TS 23.682 [6]). +Stage 3 decision if new UP→CP message are used or if the existing PFCP Session Modification message is used. + +The NEF supports store-and-forward of small data. The northbound API is terminated in the NEF. + +NOTE 1: Additional application layer functionality of the NEF is beyond the scope of 3GPP. + +The following principles apply in addition: + +Southbound as part of the NEF: + +- N6n tunnelling establishment by Nnef service operation. NEF supports N6n tunnels between UPF and NEF. +- The NEF supports Functionalities for Unstructured PDU Session Type data transfer, i.e. IP encapsulation for downlink data and IP decapsulation for uplink data. +- The NEF stores its NEF ID in the UDM during NIDD Configuration. +- Reliable Data Service between UE and NEF is supported when requested and authorized. The UE indicates its capability of supporting RDS to the network using PCO and the SMF indicates its NEF support for RDS to the UE in the PCO. + +SMF: + +- The SMF retrieves the NEF ID from the UDM during PDU Session establishment procedure, and the SMF provides the N6 PtP tunnel information (toward NEF) to the UPF or the UE. +- The SMF allocates UPF N6n PtP tunnel information or uses N4 services with UPF to allocate UPF N6n PtP tunnel information (if UPF is used to allocate the end points). +- The SMF uses Nnef services to provide the UPF N6n PtP tunnel information (the IPv6 address and the UDP port of the tunnel end at the UPF) to the NEF and to request NEF to allocate a NEF N6n PtP tunnel information. +- The SMF uses Nnef services to negotiate support of RDS and maps this information with RDS support indication in PCO . +- The SMF provides the NEF N6n PtP tunnel information to the UPF, as a separate N4 service or using the same N4 service as the RAN N3 Tunnel information is provided to the UPF (i.e. the PFCP Session Establishment Request). + +### 6.35.3 Support of EPC interworking + +Interworking could be supported via explicit 5GS and EPS specifications, but it is proposed to re-use the already specified 5GS - EPS interworking principles. + +It is proposed to not add in the EPS specifications the PGW - SCEF interface corresponding to UPF-NEF interface in 5GC, but the already agreed 5GS - EPS interworking principles can be re-used to provide interoperability between EPS and 5GS. TS 23.502 [7] clause 4.11.0.a.4 specifies that combined SMF+PGW-C can be assigned to a UE that is indicating 5G NAS capability. The combined SMF+PGW-C can then select a combined UPF+PGW-U node, as shown in TS 23.501 [5] clause 4.3. + +The N6n interface is proposed for Rel-16 5GC only, so interoperability requires network support for combined SCEF+NEF node. For UE moving between 5GC and EPC, connectivity options supported by UE and combined SCEF+NEF node may differ. + +**Editor's note:** Maintenance of RDS context in the mobility between EPC and 5GC is FFS. + +The capability of tunnelling User Plane small data from UPF to NEF provides thus the same capability for User Plane small data over the combined UPF+PGW-U and combined SCEF+NEF (as specified in solution 13) also when the 5GS + EPS capable UE is served by EPS. + +**Editor's note:** How to determine whether APN corresponds to N6 or N6n DNN after mobility to 5GS is FFS. + +Since DNN intended for small data over the user plane is configured in the network to be associated with NEF supporting T8 services, there is no need to indicate small data over user plane in the PDU Session or PDN Connection establishment and the EPS - 5GS mobility does not introduce any additional requirements on the UE context transfer. + +### 6.35.4 Procedures + +#### 6.35.4.1 Connection establishment for UPF and NEF + +Figure 6.35.4.1-1 shows connection setup procedure for user plane small data delivery using T8 NIDD API. Transport of small data over IP (IPv4, IPv6) and Unstructured PDU session types is supported. Small data is tunnelled over the N6n interface, the tunnel is configured at connection establishment. + + + +``` + +sequenceDiagram + participant UE + participant RAN as (R)AN + participant AMF + participant SMF + participant UDM + participant UPF + participant NEF + participant AF + + Note right of NEF: 0. NIDD Configuration + NEF->>AF: + UE->>AMF: 1. PDU Session Establishment Request + AMF->>SMF: 2. SMF selection + AMF->>SMF: 3. Nsmf_PDUSession_CreateSMContext Request/Response + SMF->>UDM: 4. Registration/subscription retrieval/subscribe for updates + SMF->>UPF: 5. UPF selection + SMF->>NEF: 6. Communication establishment + AMF->>SMF: 7. Namf_Communication_N1N2MessageTransfer + AMF->>UE: 8. NAS transport(PDU Session ID, SM: PDU Session Establishment Response) + SMF->>AMF: 9. Nsmf_PDUSession_UpdateSMContext + SMF->>UPF: 10. N4 Session Modification Request/Response + Note right of SMF: Data transfer via User Plane in clause 6.35.4.2 + +``` + +Sequence diagram illustrating the NIDD configuration and small data transfer path setup procedure. The diagram shows interactions between UE, (R)AN, AMF, SMF, UDM, UPF, NEF, and AF. The process starts with a PDU Session Establishment Request from UE to AMF. The AMF performs SMF selection and sends a CreateSMContext Request/Response to SMF. SMF performs Registration/subscription retrieval/subscribe for updates and UPF selection. SMF sends a Communication establishment request to NEF. AMF sends a NAS transport (PDU Session ID, SM: PDU Session Establishment Response) to UE. SMF sends an UpdateSMContext to AMF. SMF sends an N4 Session Modification Request/Response to UPF. Finally, data transfer occurs via the User Plane as described in clause 6.35.4.2. Step 0, NIDD Configuration, is shown as a bidirectional message between NEF and AF. + +**Figure 6.35.4.1-1: NIDD configuration and small data transfer path setup procedure** + +It is assumed that NIDD configuration between NEF and AF has been performed already (Step 0). During NIDD configuration, the NEF stores NIDD configuration parameters along with NEF's routing information (e.g., IPv6 address, + +port number, etc) to the UE's SM subscription data. The data path to the NEF is established by the UE performing PDU Session Establishment procedure. + +The PDU Session Establishment Procedure is performed as defined in TS 23.502 [7] with the following additions: + +1. The UE includes in PDU Session Establishment Request a specific DNN per URSP. This DNN is configured in the network to be associated with NEF supporting T8 NIDD API services. +2. The AMF selects a SMF based on the specific DNN requested by the UE along with the other parameters as specified in TS 23.502 [7]. +4. The SMF determines that the PDU Session requires the involvement of a NEF (i.e. for the T8 NIDD API). The SMF retrieves NEF information from the UE's subscription data in the UDM, i.e. NEF ID. +5. The SMF selects UPF. The SMF allocates UPF N6n Tunnel information and UPF N3/N9 Tunnel information. If the UE requests IP PDU session type (e.g., IPv4, IPv6), the SMF allocates an IP address/prefix for the PDU Session as described in TS 23.501 [5] clause 5.8.1. If the UE requests Unstructured PDU session type, the SMF allocates an IPv6 prefix for the PDU Session without involving the UE. +6. The SMF provides the NEF with the UPF N6n Tunnel information, the PDU Session Type and optionally the allocated IP address/prefix for the UE for the N6n UPF-NEF tunnel and with NIDD configuration parameters, e.g., External Identifier, AF ID (i.e. T8 destination address), and DNN as retrieved in Step 4. The NEF associates the NIDD configuration for the UE with the UPF N6n Tunnel information and the allocated IP address/prefix for the UE for the PDU Session. The NEF stores the N6n Tunnel information in order to route the DL small data towards the UE on PDU session determined based on DNN associated with the NIDD configuration and the user identity. + +The NEF responds to the SMF including the NEF N6n Tunnel information. New Nnef service operations that supports the above parameters is used for the N6n tunnel configuration. + +If the UE indicated in the PCO its willingness to support RDS, the SMF negotiates RDS with the NEF during that step. + +7. SMF includes the APN Rate Control parameters in the PCO. If RDS has been successfully negotiated with the NEF, the SMF sends a RDS indication to the UE in PCO; +- 8-9. Same as the PDU Session Establishment Procedure defined in TS 23.502 [7] +10. SMF updates the UPF using N4 Session Modification Request with the NEF N6n Tunnel information and the RAN N3 Tunnel Information. + +#### 6.35.4.2 MO small data transfer + +Figure 6.35.4.2-1 shows delivery over user-plane procedure. + + + +``` + +sequenceDiagram + participant UE + participant RAN as (R)AN + participant UPF + participant NEF + participant AF + + Note right of UPF: Uplink Data Transfer + UE->>UPF: 1. uplink data transfer + Note right of UPF: 2. IP encapsulation + UPF->>NEF: 3. uplink data transfer + Note right of NEF: 4. IP decapsulation + NEF->>AF: 5. NIDD API for UL data + + Note right of NEF: Downlink Data Transfer + AF->>NEF: 1. NIDD API for DL data + Note right of NEF: 2. IP encapsulation + NEF->>UPF: 3. downlink data transfer + Note right of UPF: 4. IP decapsulation + UPF->>UE: 5. downlink data transfer + +``` + +Sequence diagram illustrating Small Data delivery over User Plane using T8 NIDD API. The diagram shows uplink and downlink data flows between UE, (R)AN, UPF, NEF, and AF. A wavy line separates the uplink and downlink phases. + +**Figure 6.35.4.2-1: Small Data delivery over User Plane using T8 NIDD API** + +For uplink data: + +1. The UE sends uplink data via user plane. +- 2-3. The UL PDU is encapsulated and forwarded on the N6n tunnel. +4. The NEF receives the small data over the N6n connection and determines target AF. The NEF performs IP decapsulation (i.e. removes the IP header). +5. NEF forwards the received small data as NIDD to the AF via T8 NIDD API using public user identity. + +For downlink data: + +1. NEF receives the NIDD from the AF via T8 NIDD API targeted for public user identity. +2. The NEF resolves the 3GPP user identities, determines if UP or CP shall be used for the received DL packet and determines target N6n Tunnel and the UE IP address (if any). The NEF performs IP encapsulation based on the N6n Tunnelling information. +- 3-4. The NEF transfers downlink data to the UPF. The UPF acting as PDU Session Anchor performs IP decapsulation for the received data (i.e. removes the N6n tunnelling headers) and determines the PDU Session for the UE to deliver the data. +5. The UPF forwards the small data to the UE. + +### 6.35.5 Impacts on existing entities and interfaces + +Impacts on SMF: establishment of a N6n tunnel between UPF and NEF. + +Impacts on UDM to support UDM Services equivalent to the NIDD Configuration and NIDD Authorization Update procedures in TS 23.682 [6]. Provision of NEF ID to the SMF. + +The NEF supports tunnelling of small data over N6n with a UPF and new Nnef service operation needed for the point-to-point tunnel management between UPF and NEF. + +NOTE: In this solution IP tunnelling at N6n is assumed, but the tunnel type is expected to be specified as part of Stage 3. + +Impacts on UPF to support N6n Tunnelling with NEF including encapsulation/decapsulation. + +### 6.35.6 Evaluation + +In addition to small data over N6, this solution can support as a new feature also small data via NEF over user plane. + +This solution enables the 5GC to use the same NEF and NIDD API for both UP and CP data. A 3rd party Application Server can use T8 NIDD API towards the UE whether the UE supports UP data or CP data for its small data transmission. That is, the route inside the 3GPP network is transparent to the Application Server, and the T8 NIDD API is available also for UEs supporting UP data. + +The solution supports UPF and NEF inter-connected via N6n reference point. + +This solution can be deployed via combined node that supports UPF and NEF functionality in a single node. + +## 6.36 Solution 36: CM-CONNECTED with RRC Inactive state for frequent small data transmission + +### 6.36.1 Introduction + +This solution applies to Key issue 2 (Frequent small data communication). The key idea of the solution is to introduce CM-CONNECTED with RRC Inactive for frequent small data transmission. + +### 6.36.2 Functional Description + +CM-CONNECTED with RRC Inactive is used for frequent small data transmission with following enhancement to avoid frequent N3 tunnel switching for UE with mobility within the RNA, especially for frequent single UL or single UL/DL scenarios: + +- The SMF sends Small Data Information to the RAN to assist the RAN's decision whether the UE can be sent to RRC Inactive state as described in subclause 6.28.2. The Frequent Small Data Information may include frequent small data indication, communication pattern, etc. The SMF may retrieve Small Data Information based on network configuration, user subscription, etc. +- The UE may send Request for Small amount of Data in RRC Resume Request. +- The RAN may decide not to switching N3 path to serving RAN to avoid unnecessary N2 signalling and UE reconfiguration of RNA due to new anchor RAN node after the path switch. + +Additionally, following enhancement for supporting the UP CN-initiated deactivation of UP connection procedure specified in clause 6.36.4.3: + +- The RAN may remove the PDU session context locally without RAN paging during the CN-initiated deactivation of UP connection for a UE in RRC connection inactive state. + +### 6.36.3 Support of EPC interworking + +There is no interworking with EPC since this solution requires support for RRC Inactive and EPC does not support RRC Inactive. + +### 6.36.4 Procedures + +#### 6.36.4.1 Connection Inactive procedure + +The serving RAN node may decide to move the UE to RRC Inactive state based on UE activity, small data Information, etc. as described in subclause 6.28.2, when the UE is in CM-CONNECTED with RRC Connected state. + +NOTE: The details of the procedure will be defined by RAN Group in Rel-15. + +#### 6.36.4.2 Connection Resume procedure + +The Connection Resume procedure is used by the UE to perform RRC Inactive to RRC Connected state transition. After the Resume procedure, the UE may deliver small data via resumed user plane. + + + +``` + +sequenceDiagram + participant UE + participant New RAN + participant Old RAN + participant UPF + + Note left of UE: RRC_INACTIVE + UE->>New RAN: 1. RRC Resume Request + Note right of New RAN: 2. UE Context Retrieval & Forward Tunnel Establishment + New RAN->>Old RAN: + Old RAN-->>New RAN: + New RAN->>UE: 3. RRC Resume + Note left of UE: RRC_CONNECTED + UE->>UPF: 4. Small Data delivery + Note right of New RAN: 5. Connection Inactive procedure + New RAN->>Old RAN: + Old RAN-->>New RAN: + +``` + +Sequence diagram of the Connection Resume procedure for small data transmission. The diagram shows four lifelines: UE, New RAN, Old RAN, and UPF. The UE starts in RRC\_INACTIVE state and sends a '1. RRC Resume Request' to the New RAN. The New RAN performs '2. UE Context Retrieval & Forward Tunnel Establishment' with the Old RAN (indicated by a dashed box). The New RAN then sends '3. RRC Resume' to the UE, which transitions to RRC\_CONNECTED state. The UE then sends '4. Small Data delivery' to the UPF via the New RAN and Old RAN (indicated by dashed lines with 'X' marks). Finally, the New RAN performs '5. Connection Inactive procedure' (indicated by a dashed box) with the Old RAN. + +**Figure 6.36.4.2-1: Resume procedure for small data transmission** + +0. The "Small Data Information" has been provided to the old RAN node at PDU session establishment as PDU Session specific information (called 'SMF assisted NG-RAN information') within the N2 SM information, see clause 6.28.2 +1. UE to RAN: RRC Resume Request (Resume ID, Request for Small amount of Data). + +The UE initiates the transition from RRC Inactive state to RRC Connected state. Optionally, the UE may include Request for Small amount of Data in the Resume Request. + +NOTE 1: The details of how the request for "Small amount of Data" is indicated in the RRC Resume request is up to RAN WG2 to define. + +2. [Conditional] The new RAN node performs UE Context Retrieval. + +UE Context Retrieval is performed when the UE Context associated with the UE attempting to resume its connection is not locally available at the new RAN. The UE Context Retrieval via radio access network is specified in TS 38.300 [19]. + +The new RAN, based on the "Small Data Information" received in the UE Context or Request for Small amount of Data received from the UE, may decide to establish a forwarding tunnel between target RAN and old RAN rather than to perform N3 Path switch for frequent small data transmission. + +NOTE 2: The old RAN node keep the UE context, since the N3 tunnel is not switched to the new RAN node. + +NOTE 3: Is up to RAN to define the mechanisms to establish the forwarding tunnel between the Old RAN and the target RAN. + +NOTE 4: How RAN makes decision whether to establish forwarding tunnel or N3 path switch on receiving both "Small Data Information" and Request for Small amount of Data is up to RAN implementation. + +- New RAN to UE: RRC Resume message. + +The new RAN confirms to the UE that the UE has entered RRC Connected state. + +- The UE delivers small data via user plane. + +- The new RAN may trigger Connection Inactive procedure to move UE to RRC inactive state. The old RAN node will remain as Anchor RAN node and the UE will reuse the same Resume ID and RNA as before the transitioning to RRC\_Connected state. After this procedure, the new RAN removes UE context and forwarding tunnel and indicates the old RAN that the UE enters RRC inactive state. + +NOTE 5: This procedure refers to the Connection Resume Procedure defined for NG-RAN. The detailed procedure will be aligned to the procedure for E-UTRA which will be defined by RAN Group in Rel-15. + +#### 6.36.4.3 CN-initiated deactivation of UP connection when the UE is in RRC inactive state + +The following procedure is used to deactivate UP connection (i.e. data radio bearer and N3 tunnel) for an established PDU session of a UE in CM-CONNECTED state and RRC\_Inactive state. + +NOTE 1: This procedure can be evaluated separately from clauses 6.36.4.1 and 6.36.4.2. + + + +``` + +sequenceDiagram + participant UE + participant RAN + participant AMF + participant SMF + + rect rgb(255, 255, 255) + Note over UE, SMF: 0. The UE has established the PDU session and the UE is in inactive state + end + + Note right of SMF: 1. The SMF determines +that PDU session needs +deactivation + + SMF->>AMF: 3. N11 message (N2 SM Session Release) + AMF->>RAN: 4. N2 message (N2 SM session release, 'skip-indicator') + + Note left of RAN: 5. Remove UP resource +locally without +notification to the UE + + RAN->>AMF: 6. N2 message (response) + AMF->>SMF: 7. N11 message (Response) + + RAN->>UE: 8. RRC message (Resume ID) + UE->>RAN: 9. RRC message (Resume ID, ...) + +``` + +Sequence diagram for CN-initiated deactivation of UP connection when the UE is in RRC inactive state. The diagram shows interactions between UE, RAN, AMF, and SMF. + +Figure 6.36.4.3-1 + +- The SMF determines that the UP connection of the PDU session needs to be deactivated. + +2. The SMF initiates an N4 Session Modification procedure indicating the need to remove (R)AN Tunnel Info for N3 tunnel of the corresponding PDU session. +3. The SMF sends an N11 message containing N2 SM Session Release Request to release the (R)AN resources associated with the PDU session. +4. The AMF forwards the N2 SM Session Release Request to the RAN. +5. The RAN removes UP resources for the PDU session(s) received in step 4 and do not perform RAN paging, if the UE is in RRC\_inactive state; +6. The RAN acknowledges the N2 Session Release Request by sending an N2 PDU Session Response ("N1 SM Message Not Transferred") to the AMF. +7. The AMF sends an N11 message to acknowledge the SM request received in step 4. +8. When the UE triggers the Connection Resume procedure, the UE provides its Resume ID needed by the RAN to access the UE's stored Context; +9. The RAN confirms the Resume Procedure UE entered RRC Connected state. The RAN indicates the resumed PDU sessions via PDU session IDs; + +NOTE 2: The exact mechanism by which the PDU sessions are synchronized will be defined by RAN WG2. + +10. The UE releases locally the UP resources related to the PDU Sessions not received from the NG-RAN in step 9. + +### 6.36.5 Impacts on existing entities and interfaces + +RAN: + +- The RAN decides whether the UE can be sent to RRC Inactive state based on the frequent small data indication received from the SMF. +- The RAN, based on the "Small Data Information" received from the SMF, may decide establish a forwarding tunnel between target RAN and old RAN during the Resume procedure. + +SMF: + +- The SMF includes "Small Data Information" in the N2 SM information if the SMF determines the PDU session is used for frequent small data. + +UE: + +- The UE includes Request for Small Data in the RRC Resume Request. + +Additionally, following impacts for supporting the UP CN-initiated deactivation of UP connection procedure specified in clause 6.36.4.3. + +RAN: + +- The RAN removes UP resources for the PDU session(s) and do not perform RAN paging during the CN-initiated deactivation of UP connection procedure, if the UE is in RRC inactive state. +- The RAN notifies the available PDU sessions during the Resume procedure. + +UE: + +- The UE releases locally the UP resources related to the PDU Sessions not received during the Resume procedure. + +### 6.36.6 Evaluation + +RAN-CN signalling load can be minimized for small data communication for UEs that have mobility within a RAN Notification Area. + +With CN-initiated deactivation of UP connection when the UE is in RRC inactive state (subclause 6.36.4.3), the paging signalling caused by UP connection deactivation can be avoided. There is minor impact on the RRC resume message and no additional signalling is introduced. + +## 6.37 Solution 37: Monitoring + +### 6.37.1 Introduction + +This solution addresses key issue #11 - "Monitoring". + +### 6.37.2 Functional Description + +The Monitoring Events feature is intended for monitoring of specific events in 3GPP system and making such monitoring events information reported via the NEF. It is comprised of means that allow NFs in 5GS for configuring the specific events, the event detection, and the event reporting to the requested party. + +5GS supports various monitoring events. List of monitoring event already supported in 5GC are specified in Table 4.15.3.1-1 of TS 23.502 [7]. + +**Editor's note:** It is FFS if any additional Monitoring event is required to be supported by 5GS. + +Support for Monitoring Events can be offered either via AMF (as described in clause 6.37.4.1), or via UDM (as described in clause 6.37.4.2), or via PCF (as described in clause 6.37.4.2) and can be reported via the NEF (as specified in clause 4.15.3 of TS 23.502 [7]). Based on operator policies, it shall be possible to configure Monitoring Events such that some Monitoring Event follows procedures in clause 6.37.4.1 while another Monitoring Event follows procedures in clause 6.37.4.3. + +### 6.37.3 Support of EPC interworking + +#### 6.37.3.1 General + +The support of EPC interworking relies on combined SCEF + NEF node as specified in solution #13. Interaction between the SCEF and NEF in the SCEF+NEF need not be standardized. + +Monitoring events only need to be configured by the SCEF+NEF one time, by using either EPC or 5GC procedures. In other words, when a monitoring event has been configured by the SCEF procedures towards the HSS, the NEF need not repeat the same monitoring event configuration towards the UDM, and vice versa. + +Consistent with existing EPS-5GS interworking scenarios in TS 23.501 [5], the subscriber data base is managed by a combined HSS+UDM node. + +#### 6.37.3.2 Interworking with N26 interface + +When UE moves from 5GS to EPS, the UE context information sent by AMF to MME includes the monitoring event configuration information. Similarly when UE moves from EPS to 5GS, the MME's MM context information sent by MME to AMF includes the monitoring event configuration information. + +#### 6.37.3.3 Interworking without N26 interface + +When SCEF+NEF performs the procedure of monitoring via the AMF as described in clause 4.15.3.2.4 ("Exposure with bulk subscription") in TS 23.502 [7], if the AMF determines the interworking without N26 interface is supported, the AMF shall subscribe UE's mobility from 5GS to EPS from UDM+HSS on behalf of SCEF+NEF as described in clause 7.1.2 of TS 23.501 [5]. When UE's mobility from 5GS to EPS happens and Serving MME sends Update Location Request to the UDM+HSS, the UDM+HSS sends Serving MME ID to the SCEF+NEF which is the Notification Consumer. Then the SCEF+NEF performs the procedure of configuring monitoring at the MME as described in clause 5.6.1.1 of TS 23.682 [6]. + +When SCEF+NEF performs the procedure of monitoring via the UDM+HSS as described in clause 4.15.3.2.2, when UE's mobility between 5GS and EPS happens, the UDM+HSS performs the procedure of configuring monitoring at the MME as described in clause 5.6.1.1 of TS 23.682 [6] and at the AMF as described in clause 4.15.3.2.2 of TS 23.502 [7]. + +### 6.37.4 Procedures + +#### 6.37.4.1 Monitoring events at AMF + +Procedure for monitoring via AMF is specified in clause 4.15.3.2.1 of TS 23.502 [7]. + +#### 6.37.4.2 Monitoring events at UDM + +Procedure for monitoring via UDM is specified in clause 4.15.3.2.2 of TS 23.502 [7]. + +#### 6.37.4.3 Monitoring events at PCF + +##### 6.37.4.3.1 General + +In EPC Monitoring Events via the PCRF enables the SCEF (or AF/AS) to retrieve the location information and to report communication failure of a UE. In 5GC Location reporting and communication failure event reporting are supported via AMF and PCF. + +##### 6.37.4.3.2 PCF service operations information flow + + + +``` + +sequenceDiagram + participant AS + participant NEF + participant PCF + participant AMF + + Note left of AS: 1. Nnef_EventExposure_Subscribe Request + AS->>NEF: 1. Nnef_EventExposure_Subscribe Request + Note right of NEF: 2. Npcf_EventExposure_Subscribe Request + NEF->>PCF: 2. Npcf_EventExposure_Subscribe Request + Note right of PCF: 3a. Namf_EventExposure_Subscribe Request + PCF-->>AMF: 3a. Namf_EventExposure_Subscribe Request + Note right of AMF: 3b. Namf_EventExposure_Subscribe Response + AMF-->>PCF: 3b. Namf_EventExposure_Subscribe Response + Note right of PCF: 4. Npcf_EventExposure_Subscribe Response + PCF-->>NEF: 4. Npcf_EventExposure_Subscribe Response + Note right of NEF: 5. Nnef_EventExposure_Subscribe Response + NEF-->>AS: 5. Nnef_EventExposure_Subscribe Response + + Note right of PCF: 6a. Npcf_EventExposure_Notify + PCF-->>NEF: 6a. Npcf_EventExposure_Notify + Note right of NEF: 6b. Namf_EventExposure_Notify + NEF-->>AMF: 6b. Namf_EventExposure_Notify + Note right of AMF: 7. Nnef_EventExposure_Notify + AMF-->>NEF: 7. Nnef_EventExposure_Notify + Note right of NEF: 8. Namf_EventExposure_Notify + NEF-->>PCF: 8. Namf_EventExposure_Notify + +``` + +Sequence diagram illustrating Npcf\_EventExposure\_Subscribe and Notify operations between AS, NEF, PCF, and AMF. + +**Figure 6.37.4.3.2-1: Npcf\_EventExposure\_Subscribe and Notify operations** + +1. The AS subscribes to one or several Event(s) (identified by Event ID) and provides the associated notification endpoint of the AS by sending Nnef\_EventExposure\_Subscribe request. + +Event Reporting Information defines the type of reporting requested (e.g. one-time reporting, periodic reporting or event based reporting, for Monitoring Events). If the reporting event subscription is authorized by the NEF, the NEF records the association of the event trigger and the requester identity. The subscription may also include Maximum number of reports and/or Maximum duration of reporting IE. + +2. The NEF subscribes to received Event(s) (identified by Event ID) and provides the associated notification endpoint of the NEF to PCF by sending Npcf\_EventExposure\_Subscribe request. + +- 3a. [Conditional] If the requested event (e.g. monitoring of Loss of Connectivity) requires AMF assistance, then the PCF sends the Namf\_EventExposure\_Subscribe to the AMF serving the requested user. As the PCF itself is not the Event Receiving NF, the PCF shall additionally provide the notification endpoint of itself besides the notification endpoint of NEF. Each notification endpoint is associated with the related (set of) Event ID(s). This is to assure the PCF can receive the notification of subscription change related event. + +- 3b. [Conditional] AMF acknowledges the execution of Namf\_EventExposure\_Subscribe. + +If the subscription in step 1 is applicable to a group of UE(s) or any UE, the PCF sends the Namf\_EventExposure subs request to the corresponding AMF in case subscription applied to a UE or a group of UE(s), or all the AMF in this PLMN in case subscription applied to any UE. + +4. PCF acknowledges the execution of Npcf\_EventExposure\_Subscribe. + +If the subscription is applicable to a group of UE(s) and the Maximum number of reports is included in the Event Report information in step 1, the Number of UEs is included in the acknowledgement. + +5. NEF acknowledges the execution of Nnef\_EventExposure\_Subscribe to the requester that initiated the request. +- 6a. [Conditional - depending on the Event] The PCF detects the event occurs and sends the event report, by means of Npcf\_EventExposure\_Notify message to the associated notification endpoint of the NEF. +- 6b. [Conditional - depending on the Event] The AMF detects the event occurs and sends the event report, by means of Namf\_EventExposure\_Notify message to associated notification endpoint of the NEF. + +If the AMF has a maximum number of reports stored for the UE or the individual member UE the AMF shall decrease its value by one for the reported event if the UE or the individual member UE. + +For both step 6a and step 6b, when the maximum number of reports is reached and if the subscription is applied to a one UE, The NEF unsubscribes the monitoring event(s) to the PCF and the PCF unsubscribes the monitoring event(s) to AMF for the UE. + +For both step 6a and step 6b, when the maximum number of reports is reached for an individual group member UE, the NEF uses the Number of UEs received in step 4 to determine if reporting for the group is complete. If the NEF determines that reporting for the group is complete, the NEF unsubscribes the monitoring event(s) to the PCF and the PCF unsubscribes the monitoring event(s) to AMF for each individual UE within that group. + +When the Maximum duration of reporting expires in the NEF, the PCF and the AMF, then each of these nodes shall locally unsubscribe the monitoring event. + +7. [Conditional - depending on the Event] The NEF forwards to the AS the reporting event received by either Npcf\_EventExposure\_Notify and/or Nnef\_EventExposure\_Notify. +8. [Conditional - depending on the Event] The AMF detects the subscription change related event occurs, e.g. Subscription Correlation ID change due to AMF reallocation, it sends the event report, by means of Namf\_EventExposure\_Notify message to the associated notification endpoint of the PCF. + +### 6.37.5 Impacts on existing entities and interfaces + +PCF: + +- Support of new service operations - Npcf\_EventExposure\_Subscribe, Npcf\_EventExposure\_Notify. + +### 6.37.6 Evaluation + +This solution addresses the architectural requirements for the Key Issue #11 - "Monitoring". + +## 6.38 Solution 38: eDRX RRC\_INACTIVE STATE in 5GS + +### 6.38.1 Introduction + +The proposal is to enable an eDRX equivalent feature from EPS in 5GS for UE in RRC\_INACTIVE. It addresses Key Issue 4, Power saving functions. + +### 6.38.2 Functional Description + +The proposal is to enable an eDRX equivalent feature from EPS in 5GS for UE in RRC\_INACTIVE. + +As the 5GC has a different architecture and some new functionality compared to EPC some adaptions are needed compared to eDRX in EPS. The following adoptions are needed: + +- eDRX sleep cycle negotiation: + +In EPC the UE requests extended idle mode DRX parameters during attach procedure and RAU/TAU procedure and the SGSN/MME may reject or accept the UE request for enabling extended idle mode DRX . + +In case the SGSN/MME accepts the extended idle mode DRX, the SGSN/MME based on operator policies and, if available, the extended idle mode DRX cycle length value in the subscription data from the HSS, may also provide different values of the extended idle mode DRX parameters than what was requested by the UE. If the SGSN/MME accepts the use of extended idle mode DRX, the UE applies extended idle mode DRX parameters either as received or modified by SGSN/MME. + +The same principles can be used on 5GC but the procedures used by the UE to request extended DRX parameters will be Registration and Registration Update. + +Three alternatives regarding extended DRX parameters are listed: + +Alternative 1: The same extended DRX parameters and thus DRX cycle is used for UE in CM-IDLE as well as in CM-CONNECTED with RRC\_INACTIVE. This ensures that paging occasions will overlap when UE is paged by the CN (CM-IDLE) or by NG-RAN (RRC\_INACTIVE). + +Alternative 2: The UE requests different extended DRX parameters in the registration request to be used when in UE is in CM-IDLE and CM-CONNECTED with RRC\_INACTIVE. The AMF may reject or accept the UE request for enabling extended DRX for RRC inactive. If the AMF accepts the use of extended DRX for RRC inactive, the AMF indicates the enabling of extended DRX for inactive to the UE and passes the requested extended RRC inactive DRX parameters to RAN. Then the RAN decides and configures DRX parameters for RRC inactive as specified in TS 38.300 [19]. + +Alternative 3: The UE requests idle mode eDRX parameters from the AMF. The AMF passes the UE's Accepted idle mode eDRX parameters to the RAN. If the UE supports eDRX in RRC inactive, the RAN configures the UE with an eDRX cycle in RRC-INACTIVE up to the value for the UE's idle mode eDRX cycle as provided by the AMF or up to the maximum value allowed based on the NAS (and SMS) retransmission timers (whichever is lower). The RAN buffers DL packets up to the duration of the eDRX cycle chosen by RAN. + +NOTE 1: The maximum value will be determined by CT groups and is assumed to be configured in the RAN. + +In EPS the UE and the SGSN/MME handle the request. In 5GS the UE handling shall be the same but in 5GC it will be the AMF instead of SGSN/MME. + +- Subscription information : + +Extended DRX cycle length value needs to be added in the subscription data from the UDM using the same principles as in EPS. For alternative 2, an RRC\_INACTIVE specific extended DRX cycle needs to be added. + +- Hyper SFN, Paging Hyperframe and Paging Time Window. + +Same handling as in EPC but in 5GC the AMF will assign the Paging Time Window. The AMF will include the Paging Time Window in the extended DRX parameters to the UE and in the paging eDRX information to the NG-RAN. + +NOTE 2: Whether the solution for Hyper SFN and Paging Hyperframe in NB-IoT and WB-E-UTRAN in the 5GS Rel-16 will look the same as extended idle mode DRX (eDRX) in E-UTRAN depends on RAN further work. + +### 6.38.3 Support of EPC interworking + +eDRX depends on UE provided parameters in Attach/TAU respective Registration Requests, plus subscription information and local policies in the MME respective AMF. This means the eDRX handling can be kept separate in EPC and 5GC and no specific interworking is required. + +### 6.38.4 Procedures + +The existing procedures in 5GC will be reused to handle the eDRX signalling between AMF, NG-RAN, UDM and UE. + +### 6.38.5 Impacts on existing entities and interfaces + +In alternative 1 the UE shall send request for extended DRX parameters, that are valid for CM-IDLE and CM-CONNECTED with RRC\_INACTIVE to the AMF. + +In alternative 2 the UE sends RRC\_INACTIVE specific extended DRX parameters to the AMF. The UE will also receive the extended DRX parameters and utilize this information for extended DRX handling. + +In alternative 3 the UE requests idle mode eDRX parameters from the AMF. The AMF passes the UE's Accepted idle mode eDRX parameters to the RAN. The RAN configures the UE with an eDRX cycle up to the value for the UE's idle mode eDRX cycle as provided by the AMF or up to the maximum value allowed based on the NAS (and SMS) retransmission timers (whichever is lower). For CM-CONNECTED with RRC\_INACTIVE, the RAN is assumed to be able to buffer DL packets for the duration of the eDRX cycle chosen by RAN. + +The AMF shall handle the request from the UE and reject, modify or accept the request. If accepted (as is or with modification) the AMF shall set the extended DRX parameters and supply relevant parameters to UE and NG-RAN. + +The UDM may include the extended DRX cycle length value in the subscription data to the AMF. + +The NG-RAN will receive the paging eDRX information from the AMF. + +### 6.38.6 Evaluation + +This solution uses eDRX for CM-CONNECTED with RRC\_INACTIVE. It allows eDRX cycles longer than the 2.54 seconds to increase device battery efficiency while UEs are using CM-CONNECTED with RRC\_INACTIVE. The length of the eDRX cycle supported in RRC inactive depends on the alternative chosen during study conclusion. + +## 6.39 Solution 39: UE availability after DDN failure for multiple AFs + +### 6.39.1 Introduction + +This solution addresses Key Issue 3 (High latency communication) in case of multiple Application Functions (AFs). + +When multiple AFs communicate with a UE, each of them can subscribe to the "Availability after DDN failure" event. When a Downlink Data Notification (DDN) failure occurs it should be possible for the CN to notify only a subset of all the AFs that subscribed to the "Availability after DDN failure" event (e.g., only the AF(s) that previously sent the data which triggered the DDN failure, or only the AF(s) that want to be notified for a specific traffic type). + +### 6.39.2 Functional Description + +When an AF subscribes to the "Availability after DDN failure" event, the AF includes a Traffic Descriptor to identify the data sent by the AF. The event is subscribed to UDM through NEF. + +When the AF sends the downlink data, CN identifies which AF sent the down link data by using the Traffic description information received from AF. When the UE becomes available, the CN notifies the AF that has subscribed to the event and sent the data. + +The function can be divided into Event Subscription and Activate Event Report: + +- Event Subscription: + - AF subscribe the "availability after DDN failure event". The subscribing event includes traffic description information to identify the data sent by the AF. The event is subscribed to UDM through NEF. The NEF generate NEF Reference ID for the event. The NEF Reference ID identify the correlation between the event and the AF that subscribe the event. + - The UDM sends the subscription to AMF including NEF ID, NEF Reference ID and Event type. + - Based on Slice information, DNN, and/or AF Service ID, the UDM sends the subscription to (V-)SMF for existing PDU Session or during PDU Session establishment. The SMF send traffic filters to detect the traffics sent by the AF. These traffic filters are designed according to the traffic description info sent by AF. The (V-)UPF detects the traffic sent by AF and report to the (V-)SMF in the DDN message. +- Activate Event Report: + +- After receiving the DDN message for the AF service, the (V-)SMF sends message to AMF including the NEF Reference ID. +- AMF activates the event after DDN failure based on the NEF Reference ID. +- When the UE become reachable, the AMF notify the corresponding AF that has subscribed the event and sent the data. + +### 6.39.3 Support of EPC interworking + +The solution is only applied for 5GC. + +### 6.39.4 Procedures + +#### 6.39.4.1 Event Configuration + +The procedure of Event Configuration is depicted in Figure 6.39.4.1-1. + +The procedure supports the non-roaming case, the local breakout (LBO) case as well as the home routed case. + +The procedures' message flows for the non roaming and LBO cases are the same. The only difference is that in the latter case the AMF, the SMF, the UPF are located in the visited network. + +In case of home routed roaming, the UDM subscribes the event to the V-SMF through the H-SMF. + + + +``` + +sequenceDiagram + participant AF + participant NEF + participant UDM + participant AMF + participant VSMF as (V)SMF + participant VUPF as (V)UPF + + Note right of AF: 1. Nnef_EventExposure_Subscribe Request(Availability after DDN failure, Traffic Descriptor) + AF->>NEF: 1. Nnef_EventExposure_Subscribe Request(Availability after DDN failure, Traffic Descriptor) + Note right of NEF: 2. Nudm_EventExposure_Subscribe Request(Availability after DDN failure, Traffic Descriptor) + NEF->>UDM: 2. Nudm_EventExposure_Subscribe Request(Availability after DDN failure, Traffic Descriptor) + Note right of UDM: 3a. Namf_EventExposure_Subscribe Request + UDM->>AMF: 3a. Namf_EventExposure_Subscribe Request + Note right of AMF: 3b. Namf_EventExposure_Subscribe Response + AMF->>UDM: 3b. Namf_EventExposure_Subscribe Response + Note right of UDM: 4. Nsmf_EventExposure_Subscribe request(Availability after DDN failure, Traffic Descriptor) + UDM->>VSMF: 4. Nsmf_EventExposure_Subscribe request(Availability after DDN failure, Traffic Descriptor) + Note right of VSMF: 5a. N4 Session Establishment/Modification Request (Traffic Descriptor, Traffic Indicator) + VSMF->>VUPF: 5a. N4 Session Establishment/Modification Request (Traffic Descriptor, Traffic Indicator) + Note right of VUPF: 5b. N4 Session Establishment/Modification Response + VUPF->>VSMF: 5b. N4 Session Establishment/Modification Response + Note right of VSMF: 6. Nsmf_EventExposure_Subscribe response + VSMF->>UDM: 6. Nsmf_EventExposure_Subscribe response + Note right of UDM: 7. Nudm_EventExposure_Subscribe response + UDM->>NEF: 7. Nudm_EventExposure_Subscribe response + Note right of NEF: 8. Nnef_EventExposure_Subscribe response + NEF->>AF: 8. Nnef_EventExposure_Subscribe response + +``` + +Sequence diagram for Event Configuration - Availability Notification after DDN Failure. The diagram shows the interaction between AMF, (V)SMF, (V)UPF, UDM, NEF, and AF. The sequence starts with the AF sending a Nnef\_EventExposure\_Subscribe Request to the NEF. The NEF then sends a Nudm\_EventExposure\_Subscribe Request to the UDM. The UDM sends a Namf\_EventExposure\_Subscribe Request to the AMF. The AMF sends a Namf\_EventExposure\_Subscribe Response to the UDM. The UDM sends an Nsmf\_EventExposure\_Subscribe request to the (V)SMF. The (V)SMF sends an N4 Session Establishment/Modification Request to the (V)UPF. The (V)UPF sends an N4 Session Establishment/Modification Response to the (V)SMF. The (V)SMF sends an Nsmf\_EventExposure\_Subscribe response to the UDM. The UDM sends a Nudm\_EventExposure\_Subscribe response to the NEF. Finally, the NEF sends a Nnef\_EventExposure\_Subscribe response to the AF. + +**Figure 6.39.4.1-1: Event Configuration - Availability Notification after DDN Failure** + +1. The AF subscribes to the "Availability after DDN failure" event by invoking Nnef\_EventExposure\_subscribe (UE ID/Group ID, AF ID, Availability after DDN failure, DNN/S-NSSAI/AF-Service-ID, Traffic Descriptor) service of the NEF. The "Availability after DDN failure" element is used to identify the event type of the subscription. + +The Traffic Descriptor is sent by the AF if it wants to be notified of the availability after DDN failure for a specific traffic type. The Traffic Descriptor can be e.g. an IP-3-Tuple(destination IP address/IPv6 prefix, port number, protocol in use), an Application ID, a non-IP descriptor, or an Ethernet traffic descriptor or other descriptor information that can be used to identify specific AF service. UE ID can be GPSI and Group ID can be external group ID. + +2. The NEF receives the request from the AF and invokes Nudm\_EventExposure\_subscribe (UE ID/Group ID, AF ID, Availability after DDN failure, DNN/S-NSSAI/AF-Service-ID, Traffic Descriptor, NEF ID, NEF Reference + +ID) towards the UDM. The NEF Reference ID is used to identify the correlation between the event and the AF that subscribe the event. + +3. From UDM to AMF: Namf\_EventExposure\_Subscribe request(Availability after DDN failure, NEF ID, NEF Reference ID). The AMF responds to the request. +4. The UDM determines the (V-)SMF based on the Slice information, DNN, and/or AF Service ID. From UDM to (V-)SMF: Nsmf\_EventExposure\_Subscribe(Availability after DDN failure, Traffic Descriptor, NEF ID, NEF Reference ID). Traffic Descriptor is used to indicate the traffic corresponding to the event and identify the AF that provide the service. The (V-)SMF generates a Traffic Indicator that allows the (V-)SMF to correlate the Traffic Descriptor, NEF ID and NEF Reference ID for future events. + +**NOTE 1:** In the home routed case, the UDM sends the subscription to the V-SMF via the H-SMF. + +5. The (V-)SMF sends an N4 Session Establishment/Modification Request to the (V-)UPF and provides Traffic Descriptor and the related Traffic Indicator to the UPF. +6. The (V-)SMF acknowledges the execution of Nsmf\_EventExposure\_Subscribe. + +**NOTE 2:** In the home routed case, the V-SMF sends the subscription to the UDM via the H-SMF. + +7. The UDM acknowledges the execution of Nudm\_EventExposure\_Subscribe. +8. The NEF acknowledges the execution of Nnef\_EventExposure\_Subscribe. + +#### 6.39.4.2 Notification + +The procedure for notification after DDN failure is depicted if Figure 6.39.4.2-1. + + + +``` + +sequenceDiagram + participant UE + participant (R)AN + participant AMF + participant (V-)SMF + participant (V-)UPF + participant UDM + participant NEF + participant AF + + AF->>(V-)UPF: 1. DL Data + (V-)UPF->>(V-)SMF: 2. Data Notification (Traffic Indication) + (V-)SMF->>AMF: 3. Namf_CommunicationN1N2MessageTransfer(NEF ID, NEF Reference ID) + Note over UE, AMF: DDN failure (e.g. UE is in PSM) + AMF->>(V-)SMF: 4. Namf_CommunicationN1N2MessageTransfer Response + (V-)SMF->>(V-)UPF: 5. DDN Failure Indication + Note over AMF: 6. AMF set event + Note over UE, AMF: 7. UE contacts the network(e.g. TAU) + AMF->>NEF: 8. Namf_EventExposure_Notify + NEF->>AF: 9. Nnef_EventExposure_Notify + +``` + +Sequence diagram illustrating the Notification - Availability Notification after DDN Failure procedure. The diagram shows interactions between UE, (R)AN, AMF, (V-)SMF, (V-)UPF, UDM, NEF, and AF. The sequence starts with DL Data from AF to (V-)UPF, followed by a Data Notification from (V-)UPF to (V-)SMF. The (V-)SMF then sends a Namf\_CommunicationN1N2MessageTransfer to the AMF. A DDN failure event (e.g., UE in PSM) occurs. The AMF sends a response to the (V-)SMF, which then sends a DDN Failure Indication to the (V-)UPF. The AMF sets an event. The UE contacts the network (e.g., TAU). The AMF sends a Namf\_EventExposure\_Notify to the NEF, which then sends an Nnef\_EventExposure\_Notify to the AF. + +**Figure 6.39.4.2-1: Notification - Availability Notification after DDN Failure** + +1. (V-)UPF receives the downlink data sent by AF. + +**NOTE 1:** In the home routed case, the data is received by the V-UPF via the H-UPF. + +2. (V-)UPF sends Downlink Data Notification (DDN) message to the (V-)SMF, including the Traffic Indicator related to the Traffic Descriptor that triggered the event so the (V-)SMF can determine which service the downlink data belongs to. If multiple applications are bound to the same QoS flow, the UPF sends the DDN message per application to the (V-)SMF for this QoS flow. + +3. Based on the Traffic Indicator, the (V-)SMF can determine which Event the downlink data belongs to and determine the NEF ID and the NEF Reference ID to be sent to the AMF. The (V-)SMF sends Namf\_CommunicationN1N2MessageTransfer to AMF including the NEF ID and the NEF Reference ID. This message is sent even if the (V-)SMF had previously been notified that the UE is unreachable. +4. If DDN fails (e.g. UE is not reachable), the AMF sends Namf\_CommunicationN1N2MessageTransfer response to SMF to notify if of the DDN failure. +5. The SMF (V-)sends DDN failure indication to (V-)UPF. +6. The AMF notes the subscription option for notification of availability after DDN failure for the UE, and sets a Notify-on-available-after-DDN-failure flag corresponding to the NEF ID and NEF Reference ID received in step 3. +7. At some later time, the UE contacts the network, e.g., to perform registration, or as it executes a service request. +8. If the Notify-on-available-after-DDN-failure flag for the UE is set then AMF sends Namf\_EventExposure\_Notify (UE ID, NEF Reference ID) to the NEF to notify that the UE is available. +9. NEF identifies the corresponding AF based on NEF Reference ID and sends Nnef\_EventExposure\_Notify to AF to notify that the UE is available. Only the AFs linked to the Traffic Indicator (and related Traffic Descriptor) are notified. + +### 6.39.5 Impacts on existing entities and interfaces + +#### NEF: + +- Receives the Traffic Descriptor from the AF and passes to the UDM. + +#### UDM: + +- Subscribes to the AMF event "Availability after DDN failure", passing the NEF ID and NEF Reference ID to the AMF. +- The UDM sends the subscription to "Availability after DDN failure" to the SMF for an existing PDU Session or during PDU Session establishment including Traffic Descriptor, NEF ID and NEF Reference ID. + +#### (V-)SMF: + +- The SMF sends the Traffic Descriptor to the UPF so it can detect the traffic sent by the AF along with a Traffic Indicator for UPF to relate the Traffic Descriptor with the Traffic Indicator. +- After receiving the DDN message with Traffic Indicator, the SMF sends a message to AMF including the NEF ID and the NEF Reference ID. The SMF sends this message even if it had previously been notified that the UE is unreachable. + +#### H-SMF: + +- Forward messages between V-SMF and UPF in the home routed case. + +#### UPF: + +- The UPF detects the traffic sent by AF and sends to the SMF the DDN message including the Traffic Indicator. If multiple applications are bound to the same QoS flow, the UPF sends the DDN message per application to the SMF for this QoS flow. + +#### AMF: + +- AMF activates the event after DDN failure based on the NEF ID and the NEF Reference ID. +- When the UE becomes reachable, the AMF notifies the corresponding AF that has subscribed the event and sent the data. + +### 6.39.6 Evaluation + +The Solution proposes the Availability after DDN failure notification procedure in case of multiple Application Functions (AFs). The AF provides the Traffic Descriptor information during the Event Configuration procedure, and the Traffic Descriptor information can be used by the network to determine the corresponding AF. + +The solution addresses the architectural requirements for key issue 3 "Provide the AF (i.e. SCS/AS) with UE status information (e.g. reachability notification or the time when the UE is expected to be reachable)". + +## 6.40 Solution 40: Infrequent small data transmission with temporary PDU session + +### 6.40.1 Introduction + +This solution applies to address the Key Issue 1: Support for infrequent small data transmission. + +The solution assumes that the UE does not establish a PDU session before sending small data packet based on the negotiation with network. The network shall establish a temporary PDU session for the data transmission. During the lifetime of PDU session, the uplink and downlink data can be delivered. + +The solution is used to specific application scenario, e.g. MO-initiated infrequent small data transmission. + +### 6.40.2 Functional Description + +The AMF decides PDU session mode based on UE support and preference for temporary session, the UE subscription data, local configuration, Expected UE Behaviour, or negotiated MICO mode. To avoid additional PDU session establishment/release signalling at every MO-initiated small data transaction, the AMF may take into account the interval time of small data transaction if available, e.g. the Periodic Time parameter of Expected UE Behaviour. + +The infrequent small data transmission procedure for a scenario where the user data is forwarded to application server via control plane is illustrated in figure 6.40.4-1. + +### 6.40.3 Support of EPC interworking + +This solution does not support EPC-5GC interworking. When the UE with a PDN connection moves from EPC to 5GC, the UE shall release the PDN connection and deliver small data as shown in 6.40.4. When the UE with temporary PDU session moves from 5GC to EPC, the UE establishes a PDN connections for small data delivery. + +### 6.40.4 Procedures + + + +``` + +sequenceDiagram + participant UE + participant AMF + participant SMF + participant UPF + + Note over UE, AMF: 0. Negotiation of the PDU Session mode + UE->>AMF: 1. Data Transport(NAS Data PDU,DNN) + Note over AMF: 2. Check Integrity and decrypts data + AMF->>SMF: 3. PDU session Request (Temporary PDU Session indication) + SMF->>UPF: 4. N4 session establishment (Temporary PDU Session indication) + SMF->>AMF: 5. PDU session Response + AMF->>SMF: 6. N2 Message (User Data) + SMF->>UPF: 7. N4 Message (User Data) + SMF->>UPF: 8. N4 Message (User Data) + SMF->>AMF: 9. N2 Message (User Data) + Note over AMF: 10. Data encryption and Integrity protection + AMF->>UE: 11. Data Transport(NAS Data PDU) + Note over AMF, SMF, UPF: 12. PDU session release procedure + +``` + +The diagram illustrates the sequence of messages for the Small data transmission procedure. It begins with the UE and AMF negotiating the PDU Session mode. The UE sends a NAS Data PDU with DNN to the AMF. The AMF checks integrity and decrypts the data. The AMF then sends a PDU session Request with a Temporary PDU Session indication to the SMF. The SMF initiates an N4 session establishment with the UPF using the same indication. The SMF sends a PDU session Response to the AMF. The AMF sends an N2 Message (User Data) to the SMF. The SMF sends N4 Messages (User Data) to the UPF. The SMF sends an N2 Message (User Data) back to the AMF. The AMF performs data encryption and integrity protection. The AMF then transports the NAS Data PDU back to the UE. Finally, a PDU session release procedure is initiated between the AMF, SMF, and UPF. + +Sequence diagram of the Small data transmission procedure involving UE, AMF, SMF, and UPF. + +**Figure 6.40.4-1: Small data transmission procedure** + +0. During UE Registration procedure, the UE and AMF negotiate the PDU session mode to determine either temporary PDU session mode or normal PDU session mode is used. The AMF decides PDU session mode based on UE support and preference of temporary session, the UE subscription data, local configuration, Expected UE Behaviour if available, or negotiated MICO mode. +1. If the temporary PDU session is applied, the UE transmits the NAS Data PDU with the related DNN and S-NSSAI to the AMF without any established PDU session. For IP data, the UE uses a locally created IP address as the source IP address of the IP packet. +2. The AMF checks the integrity of the incoming NAS PDU and decrypts the user data it contains. +3. If the UE has no PDU Session for this DNN and S-NSSAI and the temporary PDU session mode is applied, based on one or any combination of DNN, Network Slice Selection Assistance Information, operator's local configuration or policy and routing information, the AMF selects a SMF and initiates the PDU session establishment procedure with a temporary PDU session indication to the SMF. +4. The SMF selects a specific pre-configured UPF and initiates the N4 session establishment procedure with a temporary PDU session indication to the UPF. +5. The SMF sends the response message to the AMF. + +6. The AMF forward the user data to the SMF. +7. The SMF forward the user data to the UPF and the UPF forward the user data to the DN via N6 interface. For IP data, if the temporary PDU session indication is received from the SMF in step 4, the UPF shall store the source IP address of the IP packet and change it to the IP address allocated by the SMF. +8. The UPF receives the DL user data and forwards the user data to the SMF. For IP data, the UPF changes the destination IP address of external IP packet to the IP address stored for the UE. +9. The SMF receives the DL user data and forwards the user data to the AMF. +10. If downlink data is received, the AMF encrypts and integrity protects the NAS transport message with downlink user data. +11. The AMF transmits the DL NAS Data PDU to the UE. +12. After the data transmission, the temporary PDU session is released. The temporary PDU session may be released by the AMF based on the Release Assistance Indication information from the UE, or by the SMF based on the expiration of inactivity timer (see TS 23.502 [7] clause 4.3.4.2). + +### 6.40.5 Impacts on existing entities and interfaces + +Impacts on AMF: + +- Support of the negotiation of PDU session mode with UE; +- Support of the establishment/release of temporary PDU session; + +Impacts on SMF: + +- Support of the establishment of temporary PDU session without N1 SM message (PDU Session Establishment Request) sent from the UE; +- Support of the release of temporary PDU session; + +Impacts on UPF: + +- Support of IP address translation of UL/DL IP packet for temporary PDU session; + +Impacts on UE: + +- Support of negotiation of PDU session mode with AMF; +- Support of sending small data packet without PDU session establishment. + +### 6.40.6 Evaluation + +The solution proposes that the UE can send small data packets without having to support a user-plane stack, AS security and without PDU session establishment between UE and network based on the negotiation with the network. The temporary PDU session is introduced for the small data transmission, and established in an on-demand way, which saves session resource consumption of PDU session in 5GC. The core network signalling will increase due to establishment and release of temporary PDU session. The amount of signalling depends on how frequently the UE sends UL small data and how quickly the network releases the PDU session based on Release Assistance Indication information from the UE or expiration of inactivity timer (e.g. determined by interval of data transmission). There is no support for DL-initiated small data. + +The solution avoids the PDU session related signalling between UE and network and avoids storing a PDU session context in the UE. + +In case there is no default DNN and S-NSSAI for the UE and the AMF, the UE needs to send the DNN and S-NSSAI together with UL small data. + +## 6.41 Solution 41: Combining RRC-INACTIVE and 5G UP optimization + +### 6.41.1 Introduction + +This solution addresses key issue 2, key issue 4 and key issue 13. + +While RRC-INACTIVE could be an appropriate solution to handle frequent small data, one open question is how to efficiently handle traffic patterns where the frequent small data occurs in bursts with significantly long silence periods in-between the bursts. To optimize UE power consumption during those silence periods, the UE may benefit from using power saving methods like MICO mode or eDRX. + +Given that MICO mode assumes the UE to be in CM-IDLE it anyhow does not apply to RRC-INACTIVE. However, eDRX may apply to RRC\_INACTIVE (as has been proposed in solution 38). + +The latter has led to the question where DL data buffering should be performed while the UE is in RRC-INACTIVE with eDRX. + +One option to address this problem has been proposed in solution 7 where the buffering is performed in the core network while the UE is in RRC-INACTIVE state, i.e. while the N3 interface is still up and the core network is thus far - by design - not aware of UE reachability. This solution proposes an alternative. + +### 6.41.2 Functional Description + +The following principles apply to this solution: + +- The UE is assumed to request idle mode eDRX parameters from the AMF taking the delay tolerance of all expected mobile terminating communication into account. The AMF determines the Accepted eDRX parameters. + +NOTE 1: This assumption is in line with similar assumptions made in 23.682 [6] clause 4.5.13.1: *"A UE should request for extended idle mode DRX only when all expected mobile terminating communication is tolerant to delay."* and *"The extended idle mode DRX cycle length requested by UE takes into account requirements of applications running on the UE."* + +- The AMF also passes the UE's Accepted eDRX parameter to the RAN. +- The RAN configures the UE's eDRX parameters while the UE is in RRC\_INACTIVE as follows: + - The RAN configures the eDRX cycle up to the UE's Accepted eDRX parameters as provided by the AMF or up to the maximum value allowed based on the NAS retransmission timers (whichever is lower). + +NOTE 2: The maximum value will be determined by CT groups and is assumed to be configured in the RAN. + +- The RAN shall only configure an eDRX cycle for which the RAN is capable and willing to buffer DL data. +- While the UE is in RRC\_INACTIVE with eDRX the buffering is performed in the RAN. +- Based on the UE's idle mode eDRX cycle as provided by the AMF and taking the UE's inactivity into account the RAN dynamically determines if: + - the RAN keeps the UE in RRC\_INACTIVE with an eDRX cycle up to the UE's Accepted eDRX parameters as provided by the AMF or up to the maximum value allowed based on the NAS retransmission timers (whichever is lower) (implying that the RAN buffers DL packets up to the duration of the eDRX cycle chosen by RAN); or alternatively, + - the RAN uses 5GS UP Optimization (see solution 19), i.e. suspends the UE's RRC connection. In this case the buffering of DL data is performed in the core network using normal CM-IDLE procedures. + +NOTE 3: For eDRX cycles requested by the UE that are significantly longer than the maximum value allowed based on the NAS retransmission timers, the RAN is assumed to use 5GS UP Optimization (see solution 19), i.e. to suspend the UE's RRC connection instead of using RRC-INACTIVE, after sustained UE inactivity. + +### 6.41.3 Support of EPC interworking + +Solution does not apply to EPC. + +### 6.41.4 Procedures + +Existing procedures are reused. + +### 6.41.5 Impacts on existing entities and interfaces + +General: + +- Support for eDRX in RRC-INACTIVE (see related impacts documented for solution 38) and 5GS UP optimization (see related impacts documented for solution 19). + +RAN: + +- Support for buffering up to the maximum value allowed based on the NAS retransmission timers. + +**Editor's note:** This clause describes impacts to existing entities and interfaces. + +### 6.41.6 Evaluation + +Solution 41 illustrates how RRC-INACTIVE as defined in Rel-15 can be combined with 5G UP optimization (see Solution 19) and eDRX to efficiently support bursty frequent small data. The key idea is to use RRC-INACTIVE (combined with short eDRX sleep cycles as needed) while a frequent small data burst is sent; during a silence period (i.e. in-between two bursts) the UE's RRC connection is suspended and long eDRX sleep cycles can be applied as needed. To reduce over-the-air signaling when the next frequent small data bursts begins, i.e. when the UE sends small data from CM-IDLE, 5G UP optimization (as per Solution 19) is proposed to be used. + +In combination with RRC-INACTIVE 5G UP optimization jointly ensures that bursty frequent small data can be sent with minimal signaling overhead while extended DRX sleep cycles ranging from a few seconds to hours can be supported without causing significant system impacts. The impacts are the same as for Solution 19. + +## 6.42 Solution 42: NAS based Redirection between Core Networks + +### 6.42.1 Introduction + +This NAS based solution applies to Key issue 15 of load balancing the UEs between the two systems. + +### 6.42.2 Functional Description + +This solution is a procedure to steer the UE during the (re-)registration procedure. + +In EPC, when UE sends the Attach Request to the MME and MME determines that the UE need to move to the 5G system, the MME shall reject the Attach Request and send an appropriate EMM cause indicating the target CN system to the UE. After, the UE shall disable S1 mode and re-enable the N1 mode if it was disabled and perform registration in the target 5G system. Similar, in case of 5GC, the AMF will send a Registration Reject with a cause indicating to the UE to register in the EPC network. Upon the indication, the UE shall disable the N1 mode and re-enable the S1 mode if was disabled. + +### 6.42.3 Support of EPC interworking + +TS 23.501 [5], clause 5.17 applies when a registered/connected UE(s) is moved to 5GC or EPC systems. + +### 6.42.4 Procedures + +#### 6.42.4.1 Redirection using NAS indication + +##### 6.42.4.1.1 General + +When a UE triggered registration either in EPC or 5GC network, network redirects the UE to target system by indication in the NAS layer. + +##### 6.42.4.1.2 Redirection from EPC to 5GC network + + + +``` + +sequenceDiagram + participant UE + participant RAN + participant MME + participant AMF + Note left of UE: + UE->>MME: 1. Attach/TAU Request + MME-->>UE: 2. Attach/TAU Reject + Note right of UE: + UE->>AMF: 3. Registration Request + AMF-->>UE: 4. Registration Accept + +``` + +Sequence diagram for Redirection from EPC to 5GC network. The diagram shows four lifelines: UE, RAN, MME, and AMF. The sequence of messages is: 1. Attach/TAU Request from UE to MME; 2. Attach/TAU Reject from MME to UE; 3. Registration Request from UE to AMF; 4. Registration Accept from AMF to UE. + +**Figure 6.42.4.1.2-1: Redirection from EPC to 5GC network** + +1. The UE sends the Attach or TAU Request as step#1-2 of Figure 5.3.2.1-1 in TS 23.401 [4]. The UE includes an indication that it supports N1 mode and its Preferred Network Behaviour. The Preferred Network Behaviour includes the 5GS/EPS CIoT optimisations the UE supports and what it would prefer to use. Based on the indication that the UE supports N1 mode and that Preferred Network Behaviour, the MME knows the UE can be redirected to 5GC. +2. If the MME decides to redirect the UE to the 5GC network, then the MME rejects the UE's attach request and sends an Attach / TAU Reject with appropriate EMM cause to indicating the UE to be registered in the 5GC network. + +NOTE: If 5GC is not available for a UE that is redirected from EPC, it can lead to the UE returning to EPC. This can be avoided by taking the 5GC coverage into account in the redirection policy in the MME. + +3. Upon target CN type indication in the Attach Reject the UE disables S1 mode and re-enables the N1 mode if disabled, and the UE starts the 5GC Registration procedure, see Figure 4.2.2.2.2-1 in TS 23.502 [7]. + +If the UE cannot find a cell supporting connectivity to 5GC, the UE re-enables the S1 mode and attempts to attach to EPC. + +4. After, the 5GC will accept the UE registration as described in the Figure 4.2.2.2.2-1 in TS 23.502 [7]. + +##### 6.42.4.1.3 Redirection from 5GC to EPC network + + + +``` + +sequenceDiagram + participant UE + participant RAN + participant AMF + participant MME + Note left of UE: + UE->>AMF: 1. Registration Request + AMF-->>UE: 2. Registration Reject + Note right of UE: + UE->>MME: 3. Attach/TAU Request + MME-->>UE: 4. Attach/TAU Accept + +``` + +Sequence diagram for Redirection from 5GC to EPC network. The diagram shows four lifelines: UE, RAN, AMF, and MME. The sequence of messages is: 1. Registration Request from UE to AMF; 2. Registration Reject from AMF to UE; 3. Attach/TAU Request from UE to MME; 4. Attach/TAU Accept from MME to UE. + +**Figure 6.42.4.1.3-1: Redirection from 5GC to EPC network** + +1. The UE sends the Registration Request as step#1-3 of Figure 4.2.2.2.2-1 in TS 23.502 [7]. This can be initial, mobility or periodic registration. The UE includes an indication that it supports S1 mode and its Preferred Network Behaviour. The Preferred Network Behaviour includes the 5GS/EPS CIoT optimisations the UE + +supports and what it would prefer to use. Based on the indication that the UE supports S1 mode and the Preferred Network Behaviour, the AMF knows the UE can be redirected to EPC. + +2. AMF decides to redirect the UE to the EPC, the AMF rejects the UE's Registration Request and sends a Registration Reject with appropriate MM cause to indicating to the UE to attempt a registration in the EPC network. + +NOTE: If EPC is not available for a UE that is redirected from 5GC, it can lead to the UE returning to 5GC. This can be avoided by taking the EPC coverage into account in the redirection policy in the AMF. + +3. Upon CN type indication in the Registration Reject, the UE disables the N1 mode and re-enables the S1 mode if disabled, and the UE starts the EPC Attach or TAU procedure, see Figure 5.3.2.1-1 in TS 23.401 [4]. + +If the UE cannot find a cell supporting connectivity to EPC, the UE re-enables the N1 mode and attempts to attach to 5GC. + +4. After, the EPC will accept the UE Attach/TAU as described in the Figure 5.3.2.1-1 in TS 23.401 [4]. + +##### 6.42.4.1.4 Interaction with Steering of Roaming + +If the AMF rejects the registration request and redirects the UE to EPC, the steering of roaming as described in Annex C in TS 23.122 [21] cannot be applied. In this case the UE may be redirected to EPC as described in this solution. + +### 6.42.5 Impacts on existing entities and interfaces + +EPC impacts: + +- If a MME determines that the UE needs to be redirected to other system, then MME needs to use an appropriate EMM cause and notify to the UE in NAS layer. + +5GC impacts: + +- AMF uses an appropriate EMM cause and notifies to the UE over NAS. + +UE impacts: + +- UE needs to understand the NAS rejection value and performs actions accordingly, i.e. disable the S1 or N1 mode. + +### 6.42.6 Evaluation + +This solution uses a NAS level indication in registration/attach rejection to indicate to the UE that the N1/S1 mode needs to be disabled. The UE then disables the N1/S1 mode and performs an attach/registration to the target CN type. The solution uses existing procedures. + +NOTE: Whether a new cause value needs to be defined for a redirection, is up to Stage 3. + +## 6.43 Solution 43: RRC based Redirection between Core networks + +### 6.43.1 Introduction + +This RRC based solution applies to Key issue 15 of load balancing the UEs between the two systems. + +### 6.43.2 Functional Description + +This solution provides a procedure to redirect the UE between the 5GC or EPC by the network over a RRC notification. + +Proposed to re-use the "**target CN indication**" in the N2 release message by the AMF (in Rel-15 specified for Emergency Services) for the load balancing purpose. In this case, when the AMF is notified (e.g. by O&M) or determines based on local policy, and UE's Preferred Network Behaviour, then the AMF triggers N2 release with an indication to redirect the UE to the target CN. After, the UE performs Attach/TAU procedure in EPC. + +In addition, similar indication needs to be introduced in the S1-AP interface i.e. MME will indicate the RAN to perform the redirection of a UE to the target 5GC system which will be notified to the UE in the RRC release. In fact, similar + +mechanism is defined in TS 36.413 [22] (cause IE "Load Balancing TAU Required") for load balancing between MMEs within the EPC. Similar, upon determining (e.g. by O&M notification or by local policy, and UE's Preferred Network Behaviour) by the MME that the UE(s) needs to move to target network, then MME will trigger UE context release command with a cause IE i.e. target CN information (i.e. 5GC) to the RAN which is notified to the UE in the RRC release, thus UE can perform the registration procedure in target CN system (i.e. 5GC). In addition, MME may provide the RFSP Index and handover restriction list to the RAN which allows the RAN to set proper camping policies to the UE to ensure the UE stays in 5GC when it returns to Idle mode, and to prevent handovers to 5GC in Connected mode. After, the UE performs registration procedure in 5G system. + +NOTE: Idle-mode camping policies are not supported for NB-IoT UEs. + +Editor's note: It is FFS if the target CN needs to know that the UE has been redirected. + +### 6.43.3 Support of EPC interworking + +TS 23.501 [5], clause 5.17 applies when a registered/connected UE(s) is moved to 5GC or EPC systems. + +### 6.43.4 Procedures + +#### 6.43.4.1 Redirection using RRC indication + +##### 6.43.4.1.1 General + +The network will redirect the UEs to the target system based on load balancing determination as below. + +##### 6.43.4.1.2 Redirection from EPC to 5GC network + + + +``` + +sequenceDiagram + participant UE + participant RAN + participant MME + participant AMF + Note left of UE: 0. Attached with EPC + MME->>RAN: 1. Initial Context Release Command + RAN->>UE: 2. RRC Release + RAN->>MME: 3. Initial Context Release Complete + UE->>AMF: 4. Registration Request + AMF->>UE: 5. Registration Accept + +``` + +Sequence diagram illustrating the redirection from EPC to 5GC network. The diagram shows four entities: UE, RAN, MME, and AMF. The sequence of messages is: 0. Attached with EPC (UE to MME); 1. Initial Context Release Command (MME to RAN); 2. RRC Release (RAN to UE); 3. Initial Context Release Complete (RAN to MME); 4. Registration Request (UE to AMF); 5. Registration Accept (AMF to UE). + +**Figure 6.43.4.1.2-1: Redirection from EPC to 5GC network** + +0. A UE is attached to the EPC network. As part of Attach / TAU procedure, the UE includes an indication that it supports N1 mode and its Preferred Network Behaviour. The Preferred Network Behaviour includes the 5GS/EPS CIoT optimisations the UE supports and what it would prefer to use. Based on the indication that the UE supports N1 mode and the Preferred Network Behaviour, the MME knows the UE can be redirected to 5GC. +1. If the MME has determined that the UE need to be redirected to the 5GC, when the MME releases the S1 context, the MME includes an indication of the target CN information (i.e. 5GC) to the Initial Context Release command. + +In addition, MME may provide the RFSP Index to the RAN which allows the RAN to set proper camping policies to the UE to ensure the UE stays in 5GC when it returns to Idle mode. + +NOTE 1: Defining the appropriate cause value of indication is up to the Stage 3. + +2. RAN node will release the RRC connection with an indication of the target core network type and idle-mode camping policies. +3. RAN node sends the Release complete to the MME. + +4. After the RRC release, the UE attempts to perform a registration procedure to the 5G system. + +The AS layer in the UE informs the NAS about the CN type. If the UE finds a cell supporting connection to 5GC, NAS layer sends a Registration Request to 5GC based on the target CN type from the AS layer. + +The AMF gets the UE context from EPC as described in the clause 4.11 in TS 23.502 [7], if the N26 interface exists. + +5. The AMF sends the Registration Accept to the UE. Afterwards, the AMF may provide a handover restriction list to the RAN to prevent the handovers to EPC. + +##### 6.43.4.1.3 Redirection from 5GC to EPC network + + + +``` + +sequenceDiagram + participant UE + participant RAN + participant AMF + participant MME + Note left of UE: 0. Registered in 5GC + AMF->>RAN: 1. N2 Release + RAN->>UE: 2. RRC Release + RAN->>AMF: 3. N2 Release Ack + UE->>MME: 4. TAU Request + MME->>UE: 5. TAU Accept + +``` + +Sequence diagram showing the redirection from 5GC to EPC network. The diagram involves four entities: UE, RAN, AMF, and MME. The sequence of messages is: 0. Registered in 5GC (UE to AMF), 1. N2 Release (AMF to RAN), 2. RRC Release (RAN to UE), 3. N2 Release Ack (RAN to AMF), 4. TAU Request (UE to MME), and 5. TAU Accept (MME to UE). + +**Figure 6.43.4.1.3-1: Redirection from 5GC to EPC network** + +0. A UE is registered in the 5G system. As part of Registration procedure, the UE includes an indication that it supports S1 mode and its Preferred Network Behaviour. The Preferred Network Behaviour includes the 5GS/EPS CIoT optimisations the UE supports and what it would prefer to use. Based on the indication that the UE supports S1 mode and that Preferred Network Behaviour, the AMF knows the UE can be redirected to EPC. +1. If the AMF has determined that the UE need to be redirected to the EPC, when the AMF releases the N2 connection, the AMF includes an indication of the target CN information (i.e. EPC) to the N2 release command. + +In addition, AMF may provide the RFSP Index to the RAN which allows the RAN to set proper camping policies to the UE to ensure the UE stays in EPC when it returns to Idle mode. + +2. RAN triggers RRC release procedure includes target CN indicated received in N2 procedure is conveyed to the UE. +3. RAN sends N2 release acknowledgement to the AMF. +4. Based on the RRC indication, the UE attempts to perform the registration procedure i.e. mobility Attach or TAU procedure in EPC. + +The AS layer in the UE informs the NAS about the available and target CN types. If the UE finds a cell supporting connection to EPC, the NAS layer sends an Attach or TAU Request to EPC based on the target CN type from the AS layer. + +The MME retrieves the UE context from 5GC as described in the clause 4.11 in TS 23.502 [7], if the N26 interface exists. + +NOTE: As per current procedures the AS layer indicates the available core networks to the NAS layer. If the target CN is not available for the UE, the UE stays registered in the source core network. + +5. After, the MME sends the Attach/TAU Accept message to the UE. The MME may provide a handover restriction list to the RAN to prevent handovers to 5GC. + +### 6.43.5 Impacts on existing entities and interfaces + +EPC impacts: + +- If a MME determines that the UE needs to be redirected to other system, then the MME needs to create an appropriate cause and notify to the RAN in S1-AP. +- RAN needs to provide the redirection indication in RRC to the UE. + +5GC impacts: + +none identified. UE Impacts: + +- The UE needs to understand redirection indication and perform actions accordingly. The existing redirection indication in RRC Connection Release (cnType) in WB-E-UTRAN can be reused and a similar indication needs to be added for NB-IoT. + +NOTE: Defining the appropriate cause value of indication is up to the Stage 3. + +### 6.43.6 Evaluation + +This solution uses an RRC level indication in RRC connection release after the registration/attach procedure to indicate to the UE that the target CN type needs to be selected. Such procedure exists for 5GS, but a similar procedure for EPS would need to be specified. Handovers and idle-mode mobility to the old CN type are prevented using existing procedures. The solution is not applicable for NB-IoT UE. Idle-mode mobility to the old CN type cannot be prevented if the operator uses the same RAT type(s) and frequencies in both EPS and 5GS. + +## 6.44 Solution 44: C-IoT UE Core Network selection based on S-NSSAIs + +### 6.44.1 Introduction + +This solution applies to Key Issue 15: Core Network selection for Cellular IoT. + +### 6.44.2 Functional Description + +#### 6.44.2.1 General + +The following applies for Whether and how the 5GS C-IoT feature(s) are indicated to UE: + +- An NG-RAN node that supports access to both EPC and 5G-CN is configured to broadcast in system information broadcast the **5G Cellular IoT support information**. + +NOTE 1: For WB-E-UTRAN/EPS there already exists SIB2 broadcast of "up-CIoT-EPS-Optimisation-r13" and/or "cp-CIoT-EPS-Optimisation-r13" (see TS 36.331 [23]). Therefore the UE receives information on C-IoT support for both EPC and 5G CN with no impacts to EPS. + +The UE supporting both EPC and 5G Cellular IoT and requiring Cellular IoT services performs CN selection as follows: + +- The UE first checks in SIB whether there is 5G Cellular IoT information. If the 5G Cellular IoT support is present and consistent with UE required Cellular IoT feature(s), the UE selects 5G CN. + +NOTE 2: Whether 5G C-IoT may have incompatible support scenarios is dependent on the conclusion of other key issues in this TR. + +- If the UE does not find in SIB 5G Cellular support information consistent with its own requirements, the UE checks the presence of "up-CIoT-EPS-Optimisation-r13" and/or "cp-CIoT-EPS-Optimisation-r13". If the EPC C-IoT support is compatible with UE EPC C-IoT support (e.g. UE and EPS support Control Plane C-IoT EPS optimization), the UE selects EPC. + +UE Cellular IoT indication of Requested 5G Cellular IoT feature: + +- When the UE initiates RRC connection establishment procedure, the UE indicates which CN is selected as per Rel-15 for E-UTRA. +- If the UE selected EPS, the UE proceeds as per TS 23.401 [4]. +- If the UE selected 5G CN, the UE further indicates Requested 5G Cellular IoT support information in RRC. The NG-RAN uses this information for AMF selection. +- The UE further indicates the Requested 5G Cellular IoT support information at NAS layer for the AMF to perform SMF selection based on this information. + +#### 6.44.2.2 5G Cellular IoT support information based on S-NSSAIs + +The key idea is that 3GPP standardizes S-NSSAI value(s) that correspond to a specific (set of) 5G Cellular IoT feature(s). + +NOTE: This correspondence is dependent on which 5G CIoT features are selected for normative work. + +The 5G Cellular IoT support information as described in clause 6.44.2.1 is the S-NSSAI(s). The NG-RAN broadcasts the S-NSSAI(s) corresponding to 5G Cellular IoT features. + +In this option, the Requested 5G Cellular IoT support information as per clause 6.44.2.1 is an S-NSSAI in the Requested NSSAI. + +The UE already includes the Requested NSSAI in RRC and in NAS, the NG-RAN node already performs AMF selection based on Requested NSSAI. Therefore, this option does not have RRC or NAS signalling impacts, and no impacts to AMF selection, as it reuses Network slicing feature for those aspects. + +### 6.44.3 Support of EPC interworking + +By broadcasting C-IoT support in 5G CN, the UE can select the appropriate CN type based on C-IoT support before initiating RRC connection establishment procedures. + +### 6.44.4 Procedures + +Figure 6.44.4-1 shows the call flow for Core Network selection for Cellular IoT. + + + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant 5G_CN as 5G CN + participant EPC + + Note left of UE: 1. SIB: 5G C-IoT support information (S-NSSAI-based) + UE->>NG-RAN: + Note left of UE: 2. CN type selection + Note right of UE: A) 5G CN selected, use of S-NSSAI + Note right of UE: 3a. Registration procedure as per TS 23.501 using SST=5G C-IoT feature + Note right of UE: 4b. AMF selection based on Requested C-IoT support information + Note right of UE: 5b. Continue Registration procedure as per TS 23.501 + Note right of UE: UE provides Requested 5G C-IoT support information + Note right of UE: AMF provides Allowed 5G C-IoT support information + Note right of UE: B) EPS selected + Note right of UE: 3b. Attach/TAU procedure as per TS 23.401 + +``` + +Sequence diagram illustrating Core Network Selection between UE, NG-RAN, 5G CN, and EPC. The process starts with SIB broadcasting, followed by CN type selection. It then branches into two paths: A) 5G CN selected, use of S-NSSAI (involving registration and AMF selection) and B) EPS selected (involving attach/TAU procedure). + +**Figure 6.44.4-1: Core Network Selection** + +1. The NG-RAN broadcasts 5G Cellular IoT support information in SIB via S-NSSAIs and also broadcasts "up-CIoT-EPS-Optimisation-r13" and/or "cp-CIoT-EPS-Optimisation-r13" for EPS C-IoT support if it applies. + +2. The UE uses the received broadcasted information to perform CN selection with the criteria described in clause 6.44.4.1. + +#### **A) UE selects 5G CN, use of S-NSSAI.** + +3a. The UE initiates Registration procedure including the S-NSSAI corresponding to the UE 5G C-IoT features in the Requested NSSAI in both RRC and NAS. Registration procedure continues as per TS 23.501 [5] using regular Network slicing feature for AMF selection, Allowed NSSAI, etc. The UE receives in the Allowed NSSAI an S-NSSAI corresponding to the 5G C-IoT features enabled by the network. + +4b. The NG-RAN takes into consideration the Requested 5G C-IoT support information when selecting the AMF. + +5b. Registration procedure continues as per TS 23.501 [5] with the following modifications. The AMF decides based on the UE Requested 5G C-IoT support information, network support, subscription information and/or local policies what is the Allowed 5G C-IoT support information, and provides it to the UE in registration accept message. UE knows which features are enabled based on the Allowed 5G C-IoT support information. + +#### **B) UE selects EPC.** + +3b. Attach/TAU procedure as per TS 23.401 [4] + +### 6.44.5 Impacts on existing entities and interfaces + +In UE: + +- Receive broadcast information regarding 5G CIoT support. +- Perform CN selection based on which 5G CIoT features are supported in 5G CN and/or EPC. +- Know S-NSSAI value corresponds to certain 5G CIoT feature(s). + +In NG-RAN: + +- Broadcast in SIB new information for 5G Cellular IoT support. + +### 6.44.6 Evaluation + +**Editor's note:** This clause provides an evaluation of the solution. + +## 6.45 Solution 45: Core Network Type and Node Selection for CIoT UE Using Explicit Indications + +### 6.45.1 Introduction + +This clause presents a solution for Key Issue 15: Core Network selection for Cellular IoT. It addresses the requirements captured in the key issue to support core network type selection at UE, core network node selection at RAN, AMF and MME. + +### 6.45.2 Functional Description + +When camping on an E-UTRA cell connected to both EPC and 5GC, in order to support UEs with different capabilities in the same network, the eNB that supports access to 5GC broadcasts that it can connect to 5GC (as described in TS 23.501 [5], clause 5.17.1). In addition, RAN broadcasts the 5G CIoT optimisations supported by the 5GS via NB-IoT/WB-E-UTRA access. The UE AS layer indicates the 5G CIoT optimisations broadcast to the UE NAS layer as well as the "E-UTRA connected to 5GC" capability. The UE selects a core network type (5GC or EPC) taking into account the CIoT optimisations broadcast for each network type and which optimisations the UE supports and prefers. + +The UE AS layer is made aware of whether a NAS signalling connection is to be initiated to 5GC (the existing "5GC requested" indication) and additionally the 5GS CIoT optimisations supported. The UE shall inform RAN of the "5GC requested" and the supported 5GS CIoT optimisations in an RRC message during the RRC connection establishment procedure. The RAN will take those optimisations supported by UE and AMF supported optimizations into account for AMF selection when 5GC is requested. + +When the UE performs the registration procedure it includes its Preferred Network Behaviour in the Registration Request message and the AMF replies with the Supported Network Behaviour in the Registration Accept message. The Preferred Network Behaviour indicates the Network Behaviour the UE can support and what it would prefer to use. The Supported Network Behaviour indicates the 5G CIoT Optimisations the network accepts. + +### 6.45.3 Support of EPC interworking + +The supported CIoT optimisations broadcast for EPC and 5GC allows a UE to select the CN type before initiating the RRC connection establishment. The optimisations indicated to the RAN during RRC connection establishment allows RAN to select an AMF in 5GC. + +### 6.45.4 Procedures + +#### 6.45.4.1 Registration Procedure + +Steps 1-23 are executed according to TS 23.502 [7], clause 4.2.2.2.2 with the following changes: + +Step 1: The UE includes the Preferred Network Behaviour in the Registration Request message. + +Step 21: The AMF includes the Supported Network Behaviour in the Registration Accept message. + +Editor's note: The granularity of CIoT optimisations indicated in the Preferred and Supported Network Behaviour is FFS. + +#### 6.45.4.2 Core network type selection at UE and AMF selection at RAN + + + +``` + +sequenceDiagram + participant UE + participant RAN + participant MME + participant AMF + Note left of UE: 1. Broadcast(5GC connected Indication, EPC CIoT optimisations, 5G CIoT optimisations) + Note left of UE: 2. Based on the Preferred Network Behavior and CIoT optimisations discovered from broadcast, select the CN + Note left of RAN: 3. RRCConnectionSetupComplete(CIoT optimisations) + Note left of AMF: 4. Based on the CIoT optimisations at RRC layer, select AMF + Note left of AMF: 5. Initial UE Message + +``` + +Sequence diagram illustrating Core network type selection at UE and AMF selection at RAN. The diagram shows four lifelines: UE, RAN, MME, and AMF. The sequence of messages is: 1. RAN broadcasts (5GC connected Indication, EPC CIoT optimisations, 5G CIoT optimisations) to UE. 2. UE selects the core network type (EPC or 5GC) based on the broadcast indications and its Preferred Network Behaviour. 3. UE sends RRCConnectionSetupComplete (CIoT optimisations) to RAN. 4. RAN selects the AMF based on the CIoT optimisations at the RRC layer. 5. RAN sends Initial UE Message to AMF. + +Figure 6.45.4.2-1: Core network type selection at UE and AMF selection at RAN + +- The RAN is connected to both EPC and 5GC, and broadcasts the following information: + - 5GC Connected Indication: indicate that RAN can connect to 5GC (as described in TS 23.501 [5], clause 5.17.1), and + - EPS CIoT optimisations that the network supports (as described in TS 23.401 [4], clause 5.3.2.1), e.g., *up-CIoT-EPS-Optimisation*, *cp-CIoT-EPS-Optimisation*, and + - whether it supports 5GS CIoT optimisations and it can connect to an AMF that supports 5GS CIoT optimisations. + +Editor's note: The granularity of 5GC CIoT optimisations to be broadcasted are for FFS. + +- The UE selects the core network type (EPC or 5GC) based on the broadcast indications for both EPC and 5GC, and the UE's Preferred Network Behaviour. + - 5GC is selected and the UE indicates the 5GS CIoT optimisations supported by UE, which is used for AMF selection, to RAN at RRC layer. +- Editor's note: The granularity of CIoT optimisations to be indicated over RRC layer are for FFS. +- In addition to the existing AMF selection behaviour, the 5GS CIoT optimisations information supported by UE and AMF is taken into account when the RAN selects an AMF. + - RAN sends Initial UE Message to the selected AMF. + +### 6.45.5 Impacts on existing entities and interfaces + +Enhancements on UE include the following: + +- Core network type selection based on UE's Preferred Network Behaviour, and CIoT optimisations broadcast by the RAN that connects to both EPC and 5GC; +- Indicate the Preferred Network Behaviour to the MME during Attach/TAU procedure or to AMF during Registration procedure; +- Indicate the 5GS CIoT optimisations supported by UE, which is for AMF selection, to RAN during the RRC connection establishment procedure. + +Enhancements on RAN include the following: + +- Take the 5GS CIoT optimisations supported information from UE into consideration in case of AMF selection. + +### 6.45.6 Evaluation + +This solution addresses the architectural requirements for key issue 15 i.e. UE selecting a core network type taking into account: + +- the CIoT optimizations broadcast by the RAN for each network type (EPC, 5GC); and +- the CIoT optimizations supported by the UE. + +This solution supports Preferred and Supported network behavior based on the same principles as in EPS. The difference is in terms of the preferred and supported network behavior parameters information for 5G system. + +## 6.46 Solution 46: Network controlled UL data transmission delay + +### 6.46.1 Introduction + +UE transmitting power is sensitive to the link quality, for example, the transmitting power under -100dBm coverage is about 100 times than the power under -80dBm. In the current mechanisms, when uplink data arrives, the UE will attempt to transmit the data in any coverage condition, e.g. in weak coverage, or in enhanced coverage. When in weak coverage, UE will transmit the data with maximum TX power, and maybe try many times; when in enhanced coverage, UE will repeat tens of re-transmission, all of which consume greatly UE power. + +For some IoT applications that do not require urgent transmission; these applications are very tolerant with transmission delay, e.g. daily routine data report, etc. This solution allows the UE to choose a time with better coverage to transmit uplink data under the tolerant time for more power saving purpose. + +The AF shall have some prior knowledge on the maximum delay time the UE reports the monitored data, then AF can know the exact time at which AF can collect the reported data. For example, UE is configured to report daily routine data to the AF at 8:00 am each day, and this routine data may contain the data of 24hour (from 8:00 am to 8:00 am). If one hour delayed time is configured to the UE, the AF knows the UE may not report the data at 8:00 am and may report at 9:00 pm. + +### 6.46.2 Functional Description + +This clause describes the solution for uplink data. In this solution, the network authorizes the UE to delay the uplink data transmission within the configured delay tolerant window. UE can find a better coverage during the authorized delay tolerant window, when there is uplink data to be transmitted. Some assumptions and requirements are made. + +- 1) The services characteristic can be subscribed, and the AMF/SMF can obtain the subscribed service characteristic information. +- 2) The mechanism to establish PDU Session and data transmission depends on the solution defined in other key issues. +- 3) There is a direct or indirect interface between the SMF and the AF for information exchange. + +### 6.46.3 Support of EPC interworking + +Not applicable since there is no corresponding mechanism specified in EPC. + +### 6.46.4 Procedures + +This clause describes high-level procedures and information flows for the solution. + + + +``` + +sequenceDiagram + participant UE + participant RAN + participant AMF + participant SMF/UPF + participant UDM + participant AF + + Note left of UE: 7. When UL data arrives, +UE choses the better +coverage to send UL data +within the delay time +window. + UE->>AMF: 1. PDU Session Establishment Request (with delay transmission request) + AMF->>SMF/UPF: 2. Nsmf_PDUSession_CreateSMContext Request (with delay transmission request) + Note right of SMF/UPF: 3. SMF obtains UE service +subscription info. + SMF/UPF->>AF: 4. Delay time window fetch + AF-->>SMF/UPF: + SMF/UPF->>AMF: 5. Namf_Communication_N1N2MessageTransfer (with delay time window) + AMF->>UE: 6. PDU Session Establishment Accept (with delay time window) + Note right of AF: 8. AF expects the UL data +could be received up to +the delay time window. + +``` + +Sequence diagram for Delay UL transmission for MO case showing interactions between UE, RAN, AMF, SMF/UPF, UDM, and AF. + +**Figure 6.46.4-1: Delay UL transmission for MO case** + +1. UE initiates PDU Session Establishment Request, indicating to the SMF that UE is requesting delayed transmission and the identity of the AF the UE intends to transmit data to in this PDU Session. +2. After receiving the request, the AMF selects the SMF and send Nsmf\_PDUSession\_CreateSMContext Request to SMF (with delayed transmission indication and AF identity). +3. SMF verifies in the UE subscription information the validity of the UE request. +4. Optionally, SMF can interact with AF via direct or indirect interface to obtain the allowed delay time window from the AF the UE requests. Or SMF can obtain the allowed delay time window based on UE subscription information. + +**Editor's note:** The way how the SMF identifies the AF in this case is FFS. + +**Editor's note:** Security issues need to be considered for a direct interaction between SMF and AF. Indirect interaction need to be detailed. + +- 5-6. The SMF accepts the PDU Session to the UE with the delay time window. + +**NOTE:** The delayed time window can also be configured in the UE. + +7. When UL data belonging to the PDU Session arrives from the application, UE can choose to wait for a better coverage to send UL data within the delay time window. It can be based on UE implementation or radio signal quality thresholds configured in the UE via device management, to determine whether the coverage is really bad. Or, the operator may configure the UE with lower signal quality thresholds so that the UE employs the transmission delay behavior only when the current radio coverage is really bad or the worst coverage (e.g. the UE is close to cell borders or coverage hole). + +**Editor's note:** It is FFS how the UE can predict whether the coverage is likely to improve or degrade during the delayed time window, e.g. if the UE is close to a coverage hole. + +8. The AF expects the UL data could be received not later than the allowed delayed time window. + +### 6.46.5 Impacts on existing entities and interfaces + +- New API allowing the AF to provision the network via the NEF with delayed tolerant service requirements. +- UE, AMF and SMF to support the new function to establish a delay tolerant PDU Session. +- Delay tolerant indication needs to be added in PDU Session Establishment Request. +- The delay time window is optionally added in PDU Session Establishment Accept. + +### 6.46.6 Evaluation + +**Editor's note:** This clause provides an evaluation of the solution. + +## 6.47 Solution 47: Improved Signalling/Data plane separation for Data over NAS small data solutions + +### 6.47.1 Introduction + +This solution applies to Key Issue 1: Support for infrequent small data transmission and Key Issue 2: Frequent small data communication. + +The solution is applicable as an addition to solutions 1, 2, 3, 6 and 40. + +### 6.47.2 Functional Description + +To enable more independent scalability of the data plane and signalling plane security functions for "Data over NAS", it is proposed that different encryption and integrity protection key sequences are used for "data" and for "signalling". + +This approach was used in 2G-GPRS but was ignored in R13 CIoT optimisations. + +### 6.47.3 Support of EPC interworking + +The EPC security mechanisms are used in EPC, e.g. EPC security is enabled during the TAU to EPC, and 5GC security is enabled during TAU to NG-RAN. + +### 6.47.4 Procedures + +These are the same as in the base solution, except that for: + +- Integrity protection, ciphering and header compression: + - Integrity protection and ciphering for small data are performed by AMF (existing NAS PDU integrity protection and ciphering functionality are re-used, except that the "data over NAS" PDUs use a per-PDU session parameter (and which is different to those used for NAS signaling) for the "BEARER" input to the NAS integrity and confidentiality algorithms). + +**NOTE:** The "Data over NAS" PDU already has to carry information on the PDU session to enable routing towards the correct data network, etc. However, this information would now need to be sent unencrypted. + +TS 33.501 [25] is very closely modelled on TS 33.401 [24] and both these specifications use a parameter called BEARER as an input into the generation of the key sequences for the confidentiality and integrity protection. + +However, currently the BEARER parameter is not used fully within the NAS security. TS 33.401 [24] clause 8.1.1 ("NAS input parameters and mechanism") states *"The BEARER identity is not necessary since there is only one NAS signalling connection per pair of MME and UE, but is included as a constant value so that the input parameters for AS and NAS will be the same, which simplifies specification and implementation work"*. + +This creates the opportunity to use (in a somewhat similar manner to GPRS) different security streams for signalling and data (and different security streams per PDN connection) by setting the BEARER parameter according to the PDU session ID. + +As TS 33.501 [25] is still under development, some extracts from TS 33.401 [24] are copied below: + +# Annex B + +/..../ + +*The input parameters to the ciphering algorithm are a 128-bit cipher key named KEY, a 32-bit COUNT, a 5-bit bearer identity BEARER, the 1-bit direction of the transmission i.e. DIRECTION, and the length of the keystream required i.e. LENGTH. The DIRECTION bit shall be 0 for uplink and 1 for downlink.* + +/..../ + + + +Figure B.1-1: Ciphering of data. This diagram illustrates the ciphering process between a Sender and a Receiver, separated by a dashed vertical line. On the Sender side, four inputs (COUNT, DIRECTION, BEARER, and LENGTH) and a KEY are fed into an EEA block. The EEA block outputs a KEYSTREAM BLOCK. This KEYSTREAM BLOCK is then XORed (indicated by a circle with a cross) with a PLAINTEXT BLOCK to produce a CIPHERTEXT BLOCK. On the Receiver side, the CIPHERTEXT BLOCK is XORed with the same KEYSTREAM BLOCK to recover the PLAINTEXT BLOCK. The EEA block on the receiver side also takes COUNT, DIRECTION, BEARER, and LENGTH as inputs. + +Figure B.1-1: Ciphering of data + +/..../ + + + +Figure B.2-1: Derivation of MAC-I/NAS-MAC (or XMAC-I/XNAS-MAC). This diagram illustrates the derivation of MAC-I/NAS-MAC on the Sender side and XMAC-I/XNAS-MAC on the Receiver side, separated by a dashed vertical line. On the Sender side, inputs COUNT, MESSAGE, DIRECTION, and BEARER, along with a KEY, are fed into an EIA block. The EIA block outputs a MAC-I/NAS-MAC. On the Receiver side, the same inputs (COUNT, MESSAGE, DIRECTION, BEARER, and KEY) are fed into an EIA block, which outputs an XMAC-I/XNAS-MAC. + +Figure B.2-1: Derivation of MAC-I/NAS-MAC (or XMAC-I/XNAS-MAC) + +/ end of extracts from TS 33.401 [24] / + +### 6.47.5 Impacts on existing entities and interfaces + +The UE and the security termination point in the network (e.g. AMF) need to have a common way to generate the PDU Session ID, and, then need to use it with their existing implementations of the confidentiality and integrity algorithms. + +### 6.47.6 Evaluation + +Editor's note: This clause provides an evaluation of the solution. + +Editor's note: This solution needs to be evaluated by SA WG3. + +## 6.48 Solution 48: NB-IoT idle mode inter-RAT mobility reusing EPS features + +### 6.48.1 Introduction + +This solution addresses KI#12 Inter-RAT mobility support to/from NB-IoT. + +The Key Issue as a baseline assumes the radio capabilities for NB-IoT are different to those for WB-E-UTRAN and NR, therefore 2 sets of capabilities are maintained by the AMF. In the KI the SMF is also responsible for whether a PDU session is maintained, reconnected or released. Both of these aspects are described in this solution. + +In order to support the baseline and architectural requirement from the key issue, the relevant features are reused from EPS for NB-IoT idle mode inter-RAT mobility. + +### 6.48.2 Functional Description + +#### 6.48.2.1 General + +Inter-RAT mobility to/from NB-IoT, follows the existing limitations in EPS and is limited to idle mode mobility only. + +#### 6.48.2.2 UE Radio Capability Handling + +A UE only provides its NB-IoT radio capabilities to the network over NB-IoT and these are stored separately from radio capabilities from other RATs by the AMF. + +When the UE Radio Capabilities are sent to the RAN, only the related capabilities for the RAT type the UE is using are sent to RAN, e.g. if the UE is using NB-IoT then only the NB-IoT radio capabilities are sent to RAN. + +#### 6.48.2.3 PDU Session Handling + +PDU session handling is controlled by "PDU session continuity at inter RAT mobility information" in the UDM, which indicates per DNN/S-NSSAI whether to: + +- maintain the PDU session; +- disconnect the PDU session with a reactivation request; +- disconnect the PDU session without reactivation request; +- leave it up to local VPLMN policy. + +when the UE moves between a "broadband" RAT (WB-E-UTRAN or NR) and a "narrowband" RAT (NB-IoT). During PDU session establishment the SMF retrieves the "PDU session continuity at inter RAT mobility information" (if available) from the UDM. Local SMF configuration is used when the UDM provides no information. + +The AMF informs the SMF at an inter-RAT idle mobility event, e.g. between NB-IoT connected to 5GC and WB-EUTRAN or NR connected to 5GC about a RAT type change in the Nsmf\_PDUSession\_UpdateSMContext message during the Registration procedure. Based on this (h-)SMF handles the PDU session according to "PDU session continuity at inter RAT mobility information" from the UDM or based on local policy. + +NOTE: The "PDU session continuity at inter RAT mobility information" and "PDN continuity at inter-RAT mobility" subscription should be the same so that the PDU sessions/PDN connections are handled the same by both CN types. + +#### 6.48.2.4 Determining RAT Type Change + +Dedicated TAIs are used for NB-IoT; AMF ensures that the TAI list that is allocated either only contains TAIs of NB-IoT or other RAT types. This approach ensures that a Registration request is triggered when the UE moves to or from NB-IoT. + +As documented in 23.502 [7], the AMF determines the RAT Type based on the Global RAN Node ID associated with the N2 interface. In other words, as per Rel-15 AMF distinguishes WB-EUTRA from NR based on the node type (gNB vs. NG-eNB). + +By additionally considering the dedicated TAIs assigned for NB-IoT, the AMF distinguishes WB-EUTRA and NB-IoT (which are both served by an NG-eNB). + +For mobility to EPC, the MME can continue to determine whether the RAT type has changed based on TAIs that can only be assigned to an NB-IoT RAT type or other RAT types, and a TAI List cannot mix NB-IoT RAT types with other RAT types. + +When the RAT type has changed the SMF(s) are informed to allow them to update the PDU sessions accordingly. The SMF also stores the last RAT type to help with the PDU session handling. + +### 6.48.3 Support of EPC interworking + +Idle-mode mobility from 5GS to EPS and from EPS to 5GS is performed as per the procedure described in TS 23.502 [7] clause 4.11.1.3.2 and clause 4.11.1.3.3 respectively. + +For Idle-mode mobility from 5GS to EPS, the "PDN continuity at inter RAT mobility" which is received in the subscription information from HSS is taken into account by the target MME to decide how to handle the PDU session. + +After the Idle-mode mobility from EPS to 5GS, SMF interacts with UDM to retrieve the subscription information for the PDU session, the "PDU session continuity at inter RAT mobility information" included in the subscription is taken into account by the SMF to decide how to handle the PDU session. + +### 6.48.4 Procedures + +#### 6.48.4.1 RAT change with mobility between 5GC and EPC with N26 + +When idle mode inter-RAT mobility includes changing the core network type, i.e. between EPC and 5GC and vice versa, at the same time as changing RAT types no additional procedures are required. + +The procedure for idle mode mobility towards EPC defined in TS 23.502 [7] clause 4.11.1.3.2 is reused (5GS to EPC handover with N26). When mobility towards EPC occurs, the MME performs the actions related to RAT type change defined in TS 23.401 [4], clause 5.3.3.1 (tracking area update procedure with S-GW change), i.e. take the "PDN continuity at inter RAT mobility" into account and perform the relevant actions. + +The procedures for idle mode mobility towards 5GC defined in TS 23.502 [7] clause 4.11.1.3.3 (EPS to 5GC Mobility Registration using N26) are reused. If there is the subscription information for the PDU session in the SMF, the SMF then subsequently maintains, reconnects or releases the PDU session according to the "PDU session continuity at inter RAT mobility information". If there is no subscription information for the PDU session in the SMF, SMF first retrieves the "PDU session continuity at inter RAT mobility information" from the UDM and then decides how to handle the PDU session. + +#### 6.48.4.2 RAT change with mobility between 5GC and EPC without N26 + +When idle mode inter-RAT mobility includes changing the core network type, i.e. between EPC and 5GC and vice versa, at the same time as changing RAT types no additional procedures are required. + +The procedure defined in TS 23.501 [5] clause 5.17.2.3.2 (Mobility for UEs in single-registration mode) is reused with the following addition: + +- If the network determines that the UE is changing RAT type, if the UE requests to relocate the PDU session from EPC to 5GC or 5GC to EPC, the SMF/MME uses the "PDU session continuity at inter RAT mobility" or "PDN continuity at inter-RAT mobility" information, respectively, in the subscription to determine whether to maintain the PDU session/PDN connection (if being handed over) or reject the PDU session request, with the relevant cause. +- If the UE requested to move the PDU session and the "PDN continuity at inter RAT mobility" information indicated "disconnect the PDN connection with a reactivation request" the network should provide a suitable cause code to the UE so that it can request a new PDU session. + +#### 6.48.4.3 RAT change without mobility between 5GC and EPC + +When the UE remains connected to 5GC but is performing idle mode inter-RAT mobility, the registration procedure defined in TS 23.502 [7], clause 4.2.2.2.2 is reused. As specific TACs are allocated for NB-IoT, the procedure is triggered by the UE when the UE moves between NB-IoT and "broadband" RAT (WB-E-UTRAN or NR). In this case the following steps are updated to account for the idle mode mobility: + +- Steps 4 and 5 fetch the MM context from the old AMF in the case of AMF change. +- Step 17 is executed when RAT Type change occurs the Nsmf\_PDUSession\_UpdateSMContext service is used to inform the SMF(s) about the RAT type change for all PDU sessions where the UE has not released them. If any + +PDU session are released by the UE then the Nsmf\_PDUSession\_ReleaseSMContext is used instead as currently defined. + +Step 17 of the procedure invokes steps 5 onwards, without the N11 and N2 interactions, of TS 23.502 [7] clause 4.2.3.2 (UE triggered service request). In the procedure when the SMF receives the indication that the RAT Type has changed it uses the stored "PDU session continuity at inter RAT mobility" information to determine whether to maintain the PDU session (if being handed over) or reject the PDU session request, with the relevant cause. + +#### 6.48.4.4 Determining RAT Type Change + +No additional procedures are required to determine RAT type change. + +The RAT type the UE is currently using is stored in the UE context so that the AMF can determine that the RAT type has changed. The SMF also stores the current RAT type that a PDU session is using so it can determine whether the RAT type for the PDU session has changed. + +### 6.48.5 Impacts on existing entities and interfaces + +#### UDM: + +- The subscription data is updated to include "PDU session continuity at inter RAT mobility information". + +#### SMF: + +- Retrieval and use of "PDU session continuity at inter RAT mobility information" when PDU sessions are created. +- Handle indication of idle mode inter-RAT mobility and update PDU Session(s) based on "PDU session continuity at inter RAT mobility information" or local policy. + +#### AMF: + +- Retrieval and separate storage of NB-IoT radio capabilities and supply only the relevant radio capabilities depending upon the RAT type in use to RAN. +- Determine RAT Type change based on Global RAN Node and TAIs. +- Inform SMF about RAT Type change during the UE triggered registration procedure. + +### 6.48.6 Evaluation + +This solution addresses architectural baseline and requirements of Key Issue #12 while addressing the open issues for handling PDU sessions at idle mode inter-RAT mobility. The solution follows the principles use by EPC to determine the actions (maintain or disconnect, with or without reactivation request, or left to VPLMN policy) for a PDU session being stored in the subscription data or in the absence of subscription data local policy can be used. + +## 6.49 Solution 49: Support for RDS with infrequent small data transmission solutions #1, 2, 3 + +### 6.49.1 Introduction + +This solution for RDS that can be build on top of existing solutions 1, 2, 3. Solution 4 already has support of RDS so nothing additional is needed for Solution 4 to support RDS. + +The following principles apply to this solution: + +- RDS runs between two end-points of an unstructured PDU session i.e. between UE and UPF, or between UE and NEF. +- Protocol for Reliable Data Service between UE and SCEF (as defined in TS 24.250 [8]) is used for RDS. +- For a PDU Session between UE and NEF, the NEF exposes APIs to the AF/AS for Small Data transmission. The APIs are based on the NIDD APIs which are defined for the T8 interface in TS 29.122 [9]. + +- For a PDU Session between UE and UPF, the UPF uses Point-to-Point (PtP) tunnel N6 mechanisms (similar to Point-to-Point SGi tunnel mechanism for EPS defined in TS 23.401 [4]). +- RDS is enabled or disabled based on DNN or NSSAI Configuration per SLA. +- The UE indicates its capability of supporting RDS to the network. +- The NEF or UPF indicates its support for RDS to the UE. + +### 6.49.2 Functional Description + +Protocol stack diagrams for support for RDS are shown below. + + + +Figure 6.49.2-1: RDS protocol between UE and NEF (over NAS-SM). This diagram illustrates the protocol stack for RDS when it is carried over NAS-SM. The stack starts with 'Application' at the top, followed by 'RDS', 'NAS-SM', and 'NAS-MM'. Below these, the '5G-AN Protocol Layer' is shown. The path goes from the UE through the 5G-AN (containing L1, L2, IP, SCTP, NG-AP) to the AMF (containing L1, L2, IP, SCTP, NG-AP, NAS-MM). A 'Relay' function is indicated at the AMF. The connection between the AMF and SMF is labeled N11. The SMF then connects to the NEF via the N29 interface. At the NEF, another 'Relay' function is shown, and the RDS data is passed to the AF/AS via the N33 interface. The diagram also shows the N11 and N29 interfaces between the AMF and SMF, and the N33 interface between the NEF and AF/AS. + +Figure 6.49.2-1: RDS protocol between UE and NEF (over NAS-SM) + + + +Figure 6.49.2-2: RDS protocol between UE and NEF (over NAS-MM). This diagram illustrates the protocol stack for RDS when it is carried over NAS-MM. The stack starts with 'Application' at the top, followed by 'RDS', and 'NAS-MM'. Below these, the '5G-AN Protocol Layer' is shown. The path goes from the UE through the 5G-AN (containing L1, L2, IP, SCTP, NG-AP) to the AMF (containing L1, L2, IP, SCTP, NG-AP, NAS-MM). A 'Relay' function is indicated at the AMF. The connection between the AMF and NEF is labeled Nxx. At the NEF, another 'Relay' function is shown, and the RDS data is passed to the AF/AS via the N33 interface. The diagram also shows the Nxx interface between the AMF and NEF, and the N33 interface between the NEF and AF/AS. + +Figure 6.49.2-2: RDS protocol between UE and NEF (over NAS-MM) + + + +Figure 6.49.2-3: RDS protocol between UE and UPF. The diagram shows the protocol stack for RDS across the UE, 5G-AN, AMF, SMF, and UPF. The UE stack includes Application, RDS, NAS-SM, NAS-MM, and 5G-AN Protocol Layer. The 5G-AN stack includes a Relay, NG-AP, SCTP, IP, L2, and L1. The AMF stack includes a Relay, NAS-MM, NG-AP, SCTP, IP, L2, and L1. The SMF stack includes a Relay, NAS-SM, and N11. The UPF stack includes a Relay, RDS, N4, and N6. Interfaces shown are N2 (between 5G-AN and AMF), N11 (between AMF and SMF), N4 (between SMF and UPF), and N6 (between UPF and the external network). + +**Figure 6.49.2-3: RDS protocol between UE and UPF** + +Solution 1 requires RDS support between UE and NEF and UE and UPF as shown in Figure 6.49.2-1 and Figure 6.49.2-3, respectively. + +Solution 2 requires RDS support between UE and NEF and UE and UPF as shown in Figure 6.49.2-2 and Figure 6.49.2-3, respectively. + +Solution 3 requires RDS support UE and UPF as shown in Figure 6.49.2-3. + +In addition, Solution 1 needs to be updated to have capability to have PDU session to NEF. + +PDU session to NEF can be based on using new flag "Invoke NEF selection" and "NEF ID" associated with each DNN, NSSAI and stored as part of UE subscription data in the UDM. Based on "Invoke NEF selection" flag SMF (for Solution 1) or AMF (for Solution 2) selects the identified NEF and establishes the PDU session to NEF. + +The UE indicates its capability of supporting RDS to the network using PCO and the SMF negotiates RDS support with the NEF or UPF. The SMF indicates network support for RDS to the UE in the PCO. This is similar to how it is done in EPS with the SCEF or P-GW (as described in TS 23.682 [6]). + +### 6.49.3 Support of EPC interworking + +In addition to the EPC Interworking principles that are described for Solutions 1, 2, and 3, the following principles apply: + +- When the "Invoke NEF Selection" flag is present in the UE's subscription information for the PDU Session, the identified NEF will point to an SCEF+NEF if EPC Interworking is supported. +- When the "Invoke NEF Selection" flag is not present in the UE's subscription information for the PDU Session, the identified SMF will select a PGW+UPF as the PDU Session anchor. + +### 6.49.4 Procedures + +Same as defined for Solution 1, 2, 3 with additional aspects specified in clause 6.49.2 above. + +### 6.49.5 Impacts on existing entities and interfaces + +Support of RDS protocol (as defined in TS 24.250 [8]) by UE, NEF and UPF. + +### 6.49.6 Evaluation + +This solution provides support of Reliable Data Service using same design principles as the support of RDS in EPS and using existing RDS protocol as defined in TS 24.250 [8]. RDS runs between two end-points of an unstructured PDU session, i.e. between UE and UPF, or between UE and NEF. This solution offers a flexible approach and can be built on top of existing solutions for infrequent and frequent small data. + +## 6.50 Solution 50: AF Notifications after DDN failure + +### 6.50.1 Introduction + +This solution addresses Key Issue 3 (High latency communication) in case of multiple Application Functions (AFs). + +When multiple AFs communicate with a UE, each of them can subscribe to the "Availability after DDN failure" event. When a Downlink Data Notification (DDN) failure occurs it should be possible for the CN to notify only a subset of all the AFs that subscribed to the "Availability after DDN failure" event (e.g., only the AF(s) that previously sent the data which triggered the DDN failure, or only the AF(s) that want to be notified for a specific traffic type). + +### 6.50.2 Functional Description + +When an AF subscribes to the "Availability after DDN failure" event, an application ID which identifies the AF is included in the message. The event is subscribed to UDM through NEF. + +When the AF send the downlink data, CN identifies the AF by using the application detection function. When the UE becomes available, the CN notifies the AF that has subscribed to the event and sent the data. + +The function can be divided into Event Subscription and Activate Event Report: + +- Event Subscription: + - AF subscribe the "availability after DDN failure event" together with application ID to NEF. The NEF generate NEF Reference for the event. The NEF Reference ID identify the correlation between the event and the AF that subscribe the event. + - The NEF sends the subscription to AMF via UDM including NEF Reference ID, Event type("availability after DDN failure event"). The AMF stores the "availability after DDN failure" monitoring event. + - The NEF sends the subscription to (h)SMF via UDM for existing PDU Session or during PDU Session establishment. The subscription request includes NEF Reference ID ,Event type("application detection event") and Application ID. The (h)SMF activates the application detection in the (h)UPF for the application ID. The (h)UPF detects the traffic sent by AF and report to the (h)SMF in the N4 Report message. + - After receives N4 Report message from the (h)UPF, the (h)SMF notifies the NEF that the traffic sent by AF has been detected. The NEF maintains the list of AF which has subscribed the "UE availability after DDN failure" event and sent the downlink data, and need to be notified after the UE becomes available. + - The NEF further subscribes the "UE reachability" event after receiving application detection notification from (h)SMF. The AMF stores the "UE reachability" event. +- Event Report: + - When the UE is reachable, the downlink data will be delivered to UE successfully. In this case the AMF notifies the "UE reachability" event to NEF. The NEF then removes the AF list and stop storing any new detected Application ID into the list. + - When the UE becomes unreachable, the AMF notifies the NEF. The NEF then starts to store the new detected Application ID into the list. + - When the UE is not reachable, the AMF remembers the DDN failure. When the UE becomes reachable again, the AMF notifies the "UE availability after DDN failure" to the NEF. The NEF then notifies the corresponding AF that has subscribed the event and sent the data. + +### 6.50.3 Support of EPC interworking + +The NEF+SCEF subscribes the "availability after DDN failure event" to the MME. After it receives notification from the MME about the "UE availability after DDN failure" event, the NEF+SCEF notifies the corresponding AF that has subscribed the event and sent the data. + +The NEF+SCEF subscribes the application detection event in SMF+PGW-C via the UDM. When the application is detected in SMF+PGW-C, the SMF+PGW-C then notifies the NEF+SCEF so the NEF+SCEF can add the application ID in the AF list and subscribe the "UE reachability" event with Idle State Indication to the MME. After the + +NEF+SCEF receives notification from the MME that the UE is reachable, the NEF+SCEF removes the AF list and stop storing any new detected Application ID into the list. Later when the UE becomes idle state, the AMF notifies the NEF. The NEF then starts to store the new detected Application ID into the list. + +### 6.50.4 Procedures + +#### 6.50.4.1 Event Configuration + +The procedure of Event Configuration is depicted in Figure 6.50.4.1-1. + + + +``` + +sequenceDiagram + participant AF + participant NEF + participant UDM + participant (h)SMF + participant (h)UPF + participant AMF + + Note right of AF: 1. Nnef_EventExposure_Subscribe Request(Availability) + AF->>NEF: 1. Nnef_EventExposure_Subscribe Request(Availability) + Note right of NEF: 2a. Nudm_EventExposure_Subscribe Request + NEF->>UDM: 2a. Nudm_EventExposure_Subscribe Request + Note right of UDM: 2b. Namf_EventExposure_Subscribe request + UDM->>AMF: 2b. Namf_EventExposure_Subscribe request + AMF-->>UDM: + Note right of UDM: 3a. Nudm_EventExposure_Subscribe Request + UDM->>NEF: 3a. Nudm_EventExposure_Subscribe Request + Note right of NEF: 3b. Nsmf_EventExposure_Subscribe Request + NEF->>(h)SMF: 3b. Nsmf_EventExposure_Subscribe Request + Note right of (h)SMF: 4a. N4 Session Establishment/Modification Request + (h)SMF->>(h)UPF: 4a. N4 Session Establishment/Modification Request + Note right of (h)UPF: 4b. N4 Session Establishment/Modification Response + (h)UPF-->>(h)SMF: 4b. N4 Session Establishment/Modification Response + Note right of (h)SMF: 5a. Nsmf_EventExposure_Subscribe Response + (h)SMF-->>UDM: 5a. Nsmf_EventExposure_Subscribe Response + Note right of UDM: 5b. Nudm_EventExposure_Subscribe Response + UDM-->>NEF: 5b. Nudm_EventExposure_Subscribe Response + Note right of NEF: 6. Nnef_EventExposure_Subscribe response + NEF-->>AF: 6. Nnef_EventExposure_Subscribe response + Note right of NEF: 7. Downlink data + NEF->>(h)SMF: 7. Downlink data + Note right of (h)SMF: 8. N4 Report + (h)SMF->>AMF: 8. N4 Report + Note right of (h)SMF: 9. Nsmf_EventExposure_Notify request + (h)SMF->>NEF: 9. Nsmf_EventExposure_Notify request + Note right of AMF: 10b. Namf_EventExposure_Subscribe request + AMF->>UDM: 10b. Namf_EventExposure_Subscribe request + Note right of UDM: 10a. Nudm_EventExposure_Subscribe Request + UDM->>NEF: 10a. Nudm_EventExposure_Subscribe Request + +``` + +Sequence diagram for Event Configuration - Availability Notification after DDN Failure. Lifelines: AMF, (h)SMF, (h)UPF, UDM, NEF, AF. The sequence shows the AF sending a subscription request to the NEF, which then propagates through the UDM and (h)SMF to the AMF. The AMF responds back through the chain. The (h)SMF also sends N4 Session Establishment/Modification requests to the (h)UPF and N4 Reports to the AMF. The (h)SMF sends Nsmf\_EventExposure\_Notify requests to the NEF. The NEF sends Nnef\_EventExposure\_Subscribe response to the AF. The AMF sends Nsmf\_EventExposure\_Notify requests to the (h)SMF. The (h)SMF sends Nsmf\_EventExposure\_Notify requests to the (h)UPF. The (h)SMF sends Nsmf\_EventExposure\_Notify requests to the AMF. The AMF sends Nsmf\_EventExposure\_Notify requests to the (h)SMF. The (h)SMF sends Nsmf\_EventExposure\_Notify requests to the (h)UPF. The (h)SMF sends Nsmf\_EventExposure\_Notify requests to the AMF. + +Figure 6.50.4.1-1: Event Configuration - Availability Notification after DDN Failure + +- The AF subscribes to the "Availability after DDN failure" event by invoking Nnef\_EventExposure\_subscribe(UE ID/Group ID, Application ID, Availability after DDN failure, DNN/S-NSSAI/AF-Service-ID) service of the NEF. The "Availability after DDN failure" element is used to identify the event type of the subscription. UE ID can be GPSI and Group ID can be external group ID. +- The NEF receives the request from the AF and invokes Nudm\_EventExposure\_subscribe (UE ID/Group ID, Availability after DDN failure, NEF ID, NEF Reference ID) towards the UDM. The NEF Reference ID is used to identify the correlation between the event and the AF that subscribe the event. The UDM sends Namf\_EventExposure\_Subscribe request(Availability after DDN failure, NEF ID, NEF Reference ID) to AMF. The AMF responds to the request. +- The NEF invokes Nudm\_EventExposure\_subscribe (UE ID/Group ID, Application Detection, DDN/S-NSSAI/AF Service ID, NEF ID, NEF Reference ID) towards the UDM. The UDM determines the SMF based on the Slice information, DNN, and/or AF Service ID. The UDM invokes Nsmf\_EventExposure\_subscribe (Application Detection, Application ID, NEF ID, NEF Reference ID) towards the (h)SMF. + +From UDM to (h)SMF: Nsmf\_EventExposure\_Subscribe(Application Detection, Application ID, NEF ID, NEF Reference ID). + +- If the (h)SMF has no Packet Flow Description of the Application ID, it retrieves the corresponding PFD from the NEF. The (h)SMF activates the application detection function to detect the traffic of the Application ID in the (h)UPF by using N4 Session Establishment/Modification Request. +- The (h)SMF acknowledges the execution of Nsmf\_EventExposure\_Subscribe. + +The UDM acknowledges the execution of Nudm\_EventExposure\_Subscribe. + +6. The NEF acknowledges to AF. +7. (h)UPF receives the downlink data sent by AF. +8. The (h)UPF detects the application traffic and reports start of the application by N4 Report message to (h)SMF. +9. The (h)SMF notifies the application detection event to NEF including the detected Application ID. +10. The NEF receives the Application ID and puts it into an AF List. The AF list is composed of Application IDs and indicates who shall be notified UE availability after DDN failure event. If not subscription before, the NEF further subscribes the UE reachability event to AMF via UDM. + +#### 6.50.4.2 Notification + +The procedure for notification after DDN failure is depicted in Figure 6.50.4.2-1. + + + +``` + +sequenceDiagram + participant UE + participant RAN as (R)AN + participant AMF + participant vSMF as (v)SMF + participant vUPF as (v)UPF + participant hUPF as (h)UPF + participant NEF + participant AF + + Note right of AF: 1. DL Data + AF->>hUPF: 1. DL Data + hUPF->>vUPF: 2. Data Notification + vUPF->>AMF: 3. Namf_CommunicationN1N2MessageTransfer + Note left of AMF: 4a Network initiated service request procedure + AMF->>NEF: 4b. Namf_EventExposure_Notify + Note left of AMF: 5a. DDN failure (e.g. UE is in PSM) + AMF->>vSMF: 5b. Namf_CommunicationN1N2MessageTransfer Response + vSMF->>vUPF: 6. DDN Failure Indication + Note left of AMF: 7. UE contacts the network(e.g. TAU) + AMF->>NEF: 8. Namf_EventExposure_Notify + NEF->>AF: 9. Nnef_EventExposure_Notify + +``` + +Sequence diagram illustrating the Notification - Availability Notification after DDN Failure procedure. The diagram shows interactions between UE, (R)AN, AMF, (v)SMF, (v)UPF, (h)UPF, NEF, and AF. The sequence starts with DL Data from AF to (h)UPF, followed by Data Notification from (h)UPF to (v)UPF. (v)UPF then sends Namf\_CommunicationN1N2MessageTransfer to AMF. A '4a Network initiated service request procedure' occurs between AMF and UE. After this, AMF sends Namf\_EventExposure\_Notify to NEF. A '5a. DDN failure (e.g. UE is in PSM)' occurs. AMF then sends Namf\_CommunicationN1N2MessageTransfer Response to (v)SMF. (v)SMF sends DDN Failure Indication to (v)UPF. A '7. UE contacts the network(e.g. TAU)' occurs. AMF then sends Namf\_EventExposure\_Notify to NEF. Finally, NEF sends Nnef\_EventExposure\_Notify to AF. + +**Figure 6.50.4.2-1: Notification - Availability Notification after DDN Failure** + +1. (v)UPF receives the downlink data sent by AF. +2. (v)UPF sends Downlink Data Notification (DDN) message to the (v)SMF, on arrival of the first downlink data packet for the QoS flow. +3. The (v)SMF sends Namf\_CommunicationN1N2MessageTransfer to AMF, if the (v)SMF has not been notified that the UE is unreachable. +4. If the UE is reachable, the AMF performs network initiated service request procedure to bring the UE into CONNECTED mode. The AMF then notifies UE reachability event to NEF. The NEF removes the AF list and stop storing any new detected Application ID in the list. The procedure stops. + +Later when the UE becomes unreachable, the AMF sends notification to NEF, the NEF then starts to store the new detected Application ID in the list. + +5. If DDN fails (e.g. UE is not reachable), the AMF sends Namf\_CommunicationN1N2MessageTransfer response to (v)SMF to notify the DDN failure. +6. The (v)SMF sends DDN failure indication to UPF. +7. At some later time, the UE contacts the network, e.g., to perform registration, or as it executes a service request. + +8. The AMF sends Namf\_EventExposure\_Notify(UE ID) to the NEF to notify that the UE is available after DDN failure. +9. The NEF checks the list of AF which has subscribed the event and sent the downlink data, and sends Nnef\_EventExposure\_Notify(UE ID, NEF Reference ID) to the AF in that list to notify. + +### 6.50.5 Impacts on existing entities and interfaces + +#### NEF: + +- Receives the Application ID from the AF and then requests to subscribe the "Availability after DDN failure" event in AMF, and invokes Application detection on the application in (h)SMF. +- Receives the application detection report from (h)SMF and requests to subscribe "UE reachability" event in AMF and maintain a AF list. +- Receives the notification on UE reachable event from AMF and then remove the AF list and stop storing the new detected Application ID into the list. +- Receives the notification on UE unreachable event from AMF and then start to store the new detected Application ID into the list. +- Receives the notification on the "Availability after DDN failure" event from AMF and then notify "Availability after DDN failure" event to the AF identified in the AF list. + +#### UDM: + +- The UDM sends the subscription to "Application Detection" to the (h)SMF for an existing PDU Session or during PDU Session establishment including Application ID, NEF ID and NEF Reference ID. +- Sends the "Availability after DDN failure" monitoring event subscription to the AMF. + +#### (h)SMF: + +- The (h)SMF receives new subscription event "Application Detection" from UDM to detect the application. +- The (h)SMF notifies the NEF that the application has been detected. + +#### AMF: + +- When the UE becomes reachable without DDN failure, the AMF notifies the NEF on the "UE reachability" event. +- When the UE becomes reachable after DDN failure, the AMF notifies the NEF on the "Availability after DDN failure" event. + +### 6.50.6 Evaluation + +The solution proposes the Availability after DDN failure notification procedure in case of multiple Application Functions (AFs). The AF provides the Application ID during the Event Configuration procedure, and the (h)SMF use application detection function to detect the application traffic in the (h)UPF. For PDU Session with home routed it is the home SMF to active the application detection in the home UPF. The NEF subscribes the "Availability after DDN failure" in the AMF and to notify the AF that has subscribed the event and has sent packet data. + +The solution addresses the architectural requirements for key issue 3 "Provide the AF (i.e. SCS/AS) with UE status information (e.g. reachability notification or the time when the UE is expected to be reachable)". + +## 6.51 Solution 51: Core Network steering via CN type selection rules configuration/reconfiguration + +### 6.51.1 Introduction + +This solution covers the redirection of a C-IoT UE from 5GC to EPC and viceversa, as per Key issue #15. + +### 6.51.2 Functional Description + +The proposed solution is as follows: + +- It is proposed to add a new UE configuration parameter named "CN type selection rules". The CN type selection rules are PLMN specific and may be provided in USIM (by HPLMN), or provided by the visited PLMN during registration procedure or via UE configuration update procedure or during registration in registration accept message. +- CN type selection rules provided by the HPLMN: + - The CN type selection rules that apply to the HPLMN are provided by the HPLMN either in USIM or in ME via a NAS information element in registration accept message or via UE configuration update. The CN type selection rules values may be: + - Prefer 5GC over EPC. + - The UE shall select 5GC over EPC when 5GC is available for this PLMN. + - The UE can still select EPC when 5GC not available. + - Prefer EPC over 5GC. + - The UE shall select EPC over 5GC when EPC is available for this PLMN. + - The UE can still select 5GC when EPC not available. + +**Editor's note:** How to avoid frequent CN type changes resulting from the CN type selection rule is FFS. + +- The HPLMN can already from Rel-15 define CN type preference for VPLMNs in the Operator Controlled PLMN Selector with Access Technology (see TS 23.122 [21]), where the Access Technology can refer to E-UTRAN (which refers to EPC) or NG-RAN (which refers to 5GC). +- The visited PLMN may override the HPLMN provided CN type preference in Operator Controlled PLMN Selector with Access Technology by providing its own PLMN specific CN type selection rule. + +**Editor's note:** Whether VPLMN specific CN type selection rule always takes precedence is FFS. + +- The visited PLMN may take into account operator policies or other considerations when providing the PLMN specific CN type selection rules. +- When the UE is accessing 5GC the visited PLMN may provide the PLMN specific CN type selection rules in registration accept message and can modify them at any time via the UE Configuration Update procedure for access and mobility management related parameters (TS 23.502 [7] clause 4.2.4.2). +- When the UE is accessing EPC the visited PLMN may provide the PLMN specific CN type selection rules in attach/TAU accept message. +- The UE behaves as follows: + - In initial CN type selection from RM-DEREGISTERED: + - In the absence of any CN type selection rules, the UE selects the CN type that indicates support for Cellular IoT features. If both EPC and 5GC support Cellular IoT features, the CN type selection is implementation dependent. + - If the UE is performing PLMN selection the Operator Controlled PLMN Selector with Access Technology information is used by the UE if present. + - If the UE is configured with PLMN specific CN type selection rule by the V-PLMN, the UE performs CN type selection based on the PLMN specific CN type selection rules, overriding the Access Technology part of Operator Controlled PLMN Selector with Access Technology information. + - When the UE is RM-REGISTERED with 5GC and moves from CM-CONNECTED to CM-IDLE: + +- If the UE has a CN type selection rule indicating "Prefer EPC over 5GC" then the UE shall prioritize cells supporting EPC when performing cell selection/reselection and shall select EPC if available in the cell the UE is camping on. +- If the UE has a CN type selection rule indicating "Prefer 5GC over EPC" then the UE shall prioritize cells supporting 5GC when performing cell selection/reselection. + +**Editor's note: Prioritizing CN type during cell selection/reselection needs to be confirmed by RAN WG2.** + +- When the UE is EMM-REGISTERED with EPC and moves from EMM-CONNECTED to EMM-IDLE: + - If the UE has a CN type selection rule indicating "Prefer 5GC over EPC" then the UE shall prioritize cells supporting 5GC when performing cell selection/reselection and shall select 5GC if available in the cell the UE is camping on. + - If the UE has a CN type selection rule indicating "Prefer EPC over 5GC" then the UE shall prioritize cells supporting EPC when performing cell selection/reselection. + +**Editor's note: Prioritizing CN type during cell selection/reselection needs to be confirmed by RAN WG2.** + +When the network prefers the UE to select 5GC and the UE is in CM-CONNECTED state with 5GC, the core network may prevent the RAN to redirect/handover the UE to EPC using the Mobility Restrictions to the radio access network within Handover Restriction List. + +When the network prefers the UE to select EPC and the UE is in ECM-CONNECTED state with EPC, the core network may prevent the RAN to redirect/handover the UE to 5GC using the Handover Restriction List. + +**NOTE:** CN type selection rules provided by a PLMN during registration or using UE configuration update are assumed to be stored in the ME as long as the UE is registered with that PLMN. This aspect is subject to review and final decision by CT WG1. + +### 6.51.3 Support of EPC interworking + +Since the configuration in the UE applies in case of CN type selection, it is only modifying the rules in the UE for a procedure (CN type selection) that is already defined in Rel-15, and already takes into account EPC interworking. The actual procedures of a UE moving between EPC and 5GC in CM-IDLE mode are not modified. + +### 6.51.4 Procedures + +No procedures are modified. Only new "CN type selection rules" IE is added to existing messages: + +- Registration accept message (5G NAS); +- UE configuration update (5G NAS); +- attach/TAU accept (EPC NAS). + +### 6.51.5 Impacts on existing entities and interfaces + +On AMF/MME: + +- New "CN type selection rules" IE in NAS messages; +- Configuration for CN steering. + +On UE: + +- New "CN type selection rules" IE in NAS messages; +- Modification in CN selection rules based on CN type selection rules; +- Modification in cell selection/reselection procedures based on the currently registered CN type. + +### 6.51.6 Evaluation + +This solution provides the CN type selection rules to the UE either in USIM or in NAS in attach/registration acceptance. The UE then prioritizes the cells supporting the preferred CN type in cell selection/reselection and selects the preferred CN type if available in the cell the UE is camping on. The solution has an impact to the cell selection/reselection procedures that needs to be confirmed by 3GPP RAN WG2. + +## 6.52 Solution 52: Inter-UE QoS differentiation based on retrieval of UE Context + +### 6.52.1 Introduction + +This solution addresses Key Issue 14: QoS Support for NB-IoT for the case of Data over NAS. This solution is intended to be used in combination with Data over NAS solutions (e.g., Solution 1 and Solution 30) and allows an ng-eNB to schedule resources for RRC connection establishment messages 4 and 5, by retrieving the NB-IoT UE QoS Index from the AMF before message 4 is sent. + +### 6.52.2 Functional Description + +The solution is based on the following principles. + +At UE initial registration: + +- a) The UE indicates to the AMF its 5G-S-TMSI. +- b) The AMF retrieves the newly defined NB-IoT UE QoS Index from the UDM and stores it locally indexing it per 5G-S-TMSI. + +At entering CM-CONNECTED: + +- a) The UE provides the 5G-S-TMSI in the *RRConnectionRequest* message. +- b) The ng-eNB uses the combined information to retrieve the UE information either from the AMF by means of a new N2 procedure. +- c) Based on the retrieved UE information, which includes at least the NB-IoT UE QoS Index, the ng-eNB is able to differentiate/prioritise the NB-IoT UEs before replying with the *RRConnectionSetup* message and provide an appropriate configuration to the UE in *RRConnectionSetup*. + +### 6.52.3 Support of EPC interworking + +There is no interworking with EPC required as the ng-eNB only retrieves information from the CN the UE is already registered with. + +### 6.52.4 Procedures + +#### 6.52.4.1 Provision of UE Context to AMF + + + +``` + +sequenceDiagram + participant UE + participant RAN + participant AMF + participant UDM + Note right of AMF: 2. 4-13 of Registration procedure TS 23.502 4.2.2.2.2 + Note right of AMF: 3. Step 14 of Registration procedure (TS 23.502 4.2.2.2.2) including NB-IoT UE QoS Index + Note right of AMF: 4. Steps 15-20 of Registration procedure (TS 23.502 4.2.2.2.2) + Note right of AMF: 5. Stores NB-IoT UE QoS Index per 5G-S-TMSI + UE->>AMF: 1. Registration Request (5G-S-TMSI) + AMF->>UDM: + UDM-->>AMF: + AMF->>UE: 6. Registration Accept + UE-->>AMF: 7. Registration Complete + +``` + +Sequence diagram showing the provision of UE Context to AMF during registration. Lifelines: UE, RAN, AMF, UDM. The sequence starts with a Registration Request (5G-S-TMSI) from UE to AMF. A large block labeled '2. 4-13 of Registration procedure TS 23.502 4.2.2.2.2' spans from AMF to UDM and back. Inside this block, step 3 is 'Step 14 of Registration procedure (TS 23.502 4.2.2.2.2) including NB-IoT UE QoS Index' and step 4 is 'Steps 15-20 of Registration procedure (TS 23.502 4.2.2.2.2)'. After the block, step 5 is 'Stores NB-IoT UE QoS Index per 5G-S-TMSI' in the AMF. Step 6 is 'Registration Accept' from AMF to UE. Step 7 is 'Registration Complete' from UE to AMF. + +**Figure 6.52.4.1-1: Provision of QoS context to AMF at UE registration** + +1. During the registration procedure, the UE, based on the Preferred Network Behaviour indication indicates it wants to send data over NAS and provides the AMF with the 5G-S-TMSI. +2. Steps 4-13 of the registration procedure in TS 23.502 [7] clause 4.2.2.2.2. +3. The AMF retrieves the NB-IoT UE QoS Index from the UDM. The NB-IoT UE QoS Index is a subscription parameter used to differentiate the QoS handling among NB-IoT UEs. +4. Step 15-20 of the registration procedure. +5. The AMF locally stores the NB-IoT UE QoS Index per 5G-S-TMSI. +- 6,7. Completion of the registration procedure. + +#### 6.52.4.2 Retrieval of UE Context from AMF and Inter-UE QoS differentiation + +The existing mechanism in EPC for retrieving QoS parameters is updated to allow the ng-eNB to determine whether it should retrieve the UE information from the AMF. + +**NOTE:** As clarified in R3-151181 (and related notes of RAN WG3#88 in R3-151324), since the MMEC for one MME node must be unique across all MME nodes connected to the same eNB, similarly the S-TMSI is enough to select the proper AMF. + + + +``` + +sequenceDiagram + participant UE + participant ng-eNB + participant AMF + Note right of ng-eNB: 4) Based on info in step 3, prioritize UE wrt others + UE->>ng-eNB: 1) RRCConnectionRequest (5G-S-TMSI) + ng-eNB->>AMF: 2) RETRIEVE UE INFORMATION (5G-S-TMSI) + AMF-->>ng-eNB: 3) UE INFORMATION TRANSFER (NB-IoT UE QoS Index, UE Radio Capability) + Note right of ng-eNB: 4) Based on info in step 3, prioritize UE wrt others + ng-eNB->>UE: 5) RRCConnectionSetup + UE->>ng-eNB: 6) RRCConnectionSetupComplete (NAS-PDU) + ng-eNB->>AMF: 7) Initial UE Message (NAS PDU) (5G-S-TMSI) + +``` + +Sequence diagram illustrating UE QoS differentiation and context retrieval from the AMF during a CM-IDLE to CM-CONNECTED state transition. The diagram shows interactions between UE, ng-eNB, and AMF. The UE sends an RRCConnectionRequest (5G-S-TMSI) to the ng-eNB. The ng-eNB sends a RETRIEVE UE INFORMATION (5G-S-TMSI) message to the AMF. The AMF responds with a UE INFORMATION TRANSFER (NB-IoT UE QoS Index, UE Radio Capability) message. The ng-eNB then prioritizes the UE based on the information received. The ng-eNB sends an RRCConnectionSetup message to the UE. The UE responds with an RRCConnectionSetupComplete (NAS-PDU) message. Finally, the ng-eNB sends an Initial UE Message (NAS PDU) (5G-S-TMSI) to the AMF. + +**Figure 6.52.4.2-1: UE QoS differentiation and context retrieval from the AMF at CM-IDLE to CM-CONNECTED state transition.** + +- 1) The UE sends *RRCConnectionRequest* message to the ng-eNB which includes the 5G-S-TMSI and CN indication for which CN the UE is registered with. The ng-eNB uses the new CN indication to determine whether to retrieve the UE information from EPC or 5GC. + +NOTE 1: According to TS 36.331 [23], the *RRCConnectionRequest-NB* message already includes the 40-bit S-TMSI and has 17 spare bits. To include the full 48-bit 5G-S-TMSI, assuming the 40 bits of the S-TMSI are re-used, only 8 bits are needed. For other RRC messages, such as the *RRCEarlyDataRequest-NB* message for Early Data Transmission, such limitation does not apply because they use different physical RACH resources which are larger. + +- 2) The ng-eNB, based on configuration may send the N2 RETRIEVE UE INFORMATION (5G-S-TMSI) message to the AMF to retrieve the NB-IoT QoS Index. The ng-eNB may retrieve additional parameters (e.g., UE Radio Capabilities). + +- 3) The AMF replies with the N2 UE INFORMATION TRANSFER (with at least the NB-IoT UE QoS index) message to the ng-eNB with the UE information. + +NOTE 2: The retrieval of further information from the SMF depends on the solution for KI#13 (see Solution 15 for provision of UE Expected Behaviour to the NG-RAN). + +- 4) The ng-eNB uses the retrieved UE information to prioritise the UE as appropriate and determine the configuration for the UE in the *RRCConnectionSetup*. + +- 5) The ng-eNB sends *RRCConnectionSetup* to the UE, including configuration for optional features the UE supports, if required. + +- 6) The UE sends *RRCConnectionSetupComplete*, including the initial NAS-PDU. + +- 7) The ng-eNB sends the initial NAS-PDU to the AMF. + +### 6.52.5 Impacts on existing entities and interfaces + +#### UE/RRc: + +- For NB-IoT, sends the whole 5G-S-TMSI to ng-eNB in RRC Message 3 +- A new N2 procedure to retrieve UE information from the AMF. + +#### AMF: + +- At registration, retrieve from UDM and store locally the UE QoS Index. +- A new N2 procedure to provide UE information to the ng-eNB. + +UDM: + +- Addition of UE QoS Index to subscription data. + +### 6.52.6 Evaluation + +The solution addresses Key Issue 14 (QoS Support for NB-IoT for the case of Data over NAS) since it allows the ng-eNB to prioritize different NB-IoT UEs before RRC message 4 is sent, therefore allowing to improve the schedule of resources for RRC connection establishment messages 4 and 5. Similarly to the solution agreed for EPS CIoT Rel-14, the RAN - AMF interaction will cause a delay in the transmission of RRC msg4, which results in a higher power consumption in the NB-IoT UE since it has to constantly monitor the NPDCCH until the msg4 can be decoded. + +The solution does not allow to prioritize RRC Message 3 (e.g., in case of Early Data Transmission with a single UL PDU). + +Advantages: + +- Support QoS differentiation among UEs that use NAS to deliver data. +- Support any types of data, IP, Ethernet, unstructured data. + +Disadvantages: + +- Increase the size of some RRC messages to carry 5G-S-TMSI. + +# --- 7 Evaluation + +**Editor's note:** This clause will provide a general evaluation of the solutions. + +## 7.1 Key Issue 1: Support for infrequent small data transmission + +The following solutions are addressing key issue 1: + +- **Solution 1** supports small data transfer inside a PDU session in NAS-SM via AMF/SMF to UPF. To also support the NIDD API (i.e. to address the architectural requirements to "support API(s) for infrequent small data transmission and capability exposure to AF"), solution 1 relies on solution 30, which extends solution 1 by supporting non-IP data in a PDU session via AMF/SMF/NEF and the NIDD API to AFs. Solution 1 supports early data and reuses EPC interworking as defined in Rel-15, i.e. relies on mapping PDU sessions to PDN connections. Solution 1 follows the same concept as EPS CP optimization. This enables low complexity IoT devices that support both EPC and 5GC connectivity to send small data over NAS (i.e. without having to support a user-plane stack, AS security, etc.) regardless of the core network those devices are connected to. Whether to send the existing SM header or a shortened SM header with the small data is up to CT WG1 to decide. +- **Solution 2** transfers small data inside a PDU session by means of NAS-MM. In addition solution 2 introduces a user-plane tunnel (Nx interface) between AMF and UPF to bypass SMF for small data transfer to the UPF. This results in AMF impact to support a user-plane interface (Nx interface) on the AMF and related changes to the SMF to support Nx tunnel establishment. When the UE moves from CM-IDLE to CM-CONNECTED the Nx interface first needs to be established before small data can be forwarded between AMF to UPF. As a result DL data in response to UL data sent by the UE will be delayed compared to solution 1 due to the tunnel setup signaling. No SM header is needed for solution 2. +- In contrast to solution 1 and 2, **solution 3** is not a generic solution as it only supports small data transfer of non-IP data. The solution does not establish a PDU session but establishes a Non Session Data Delivery (NSDD) context in the SMF instead. The benefit of not establishing a PDU session is however not obvious since NSDD context is anyhow established at the SMF. Interworking with EPC is not supported as per the solution description (the solution targets UEs that only support 5GC-NAS). +- **Solution 4** relies on use of the RDS protocol (already defined for EPS) for reliable delivery of small data unstructured PDUs. It does not require establishment of a PDU session as the RDS header contains the routing + +information for the small data transfer between UE and AF. As compared to solution 30 it carries data over NAS-MM between UE and AMF and then from AMF to NEF directly. For IP small data transfer, solution 4 would need to rely on either solution 1 or 2. From a signaling perspective it is more efficient than solution 30 but when combined with either solution 1 or 2 it would also be required to support PDU session establishment logic for IP data transfer via the UPF. + +- **Solution 6** proposes to send IP and non-IP small data in a DATA PDU in RRC via SRB to the RAN, which in turn forwards the small data to a UPF. As per the solution description, a single UPF appears to be assumed (as the UE does not include any UPF ID or similar information together with the UL data). As a consequence there is no support for different UPFs for different DNNs, slices or even load-balancing reasons. While this may be addressable, the solution has two other key drawbacks: (1) In contrast to the other infrequent small data solutions, solution 6 requires the UE to support an additional security association per PDU session and (2) the solution has RAN impact (handling of new DATA PDU in RRC; determining the target UPF and new forwarding mechanism for small data to/from target UPF) compared to all other solutions which are transparent to the RAN. The latter is important to ensure simple migration to 5GC. This solution does not add any additional load for control plane entities (AMF and SMF). +- **Solution 40** proposes to establish a PDU session for sending UL data, which gets released after UL data is sent and related DL data has been received or after the expiration of the inactivity timer. As a consequence there is no support for DL-initiated small data. The solution avoids user-plane stack and AS security complexity. The solution avoids the PDU session related signaling between UE and network and avoids the complexity of storing a PDU session context in the UE. The temporary PDU session is introduced for the small data transmission, and established in an on-demand way, which saves PDU session resource consumption in 5GC. The core network signaling will increase due to establishment and release of temporary PDU session. The amount of signaling depends on how frequently the UE sends UL small data and how quickly the network releases the PDU session based on Release Assistance Indication information from the UE or expiration of inactivity timer (e.g. determined by interval of data transmission). In case there is no default DNN and S-NSSAI for the UE and the AMF, the UE needs to send the DNN and S-NSSAI together with UL small data. The solution requires a network address translation (NAT) function in the UPF since the UE uses a locally generated IP address, which needs to be translated to a routable IP address. + +Additional load for control plane entities (AMF and SMF) that is implied by all solutions except solution 6 can be addressed by dynamically adding virtualized AMF and SMF entities as needed. Control plane overload can be addressed by solutions for KI#7. + +## 7.2 Key Issue 2: Frequent small data communication + +### 7.2.1 Overview + +Solution 5 proposes to send MO small data together with an indication of the target UPF and the UL-TEID to the RAN, which in turn forwards the data to that UPF. Security is provided by a per PDU session security association between UE and UPF, i.e. AS security is not used. For MT data a procedure similar to paging in CM-IDLE state is used. The solution impacts both RAN and CN to support the fast-path model; the UE is impacted due to the need to additionally support a per PDU session security association with the UPF. Solution 5 can be used with Early Data Transfer (EDT) and eDRX. It is also compatible with RRC Inactive. + +Solution 7 proposes two aspects: + +1. Extend RRC Inactive as specified in Rel-15 by support for early data. +2. Re-building CM-IDLE state and related HLCom functionality in CM-CONNECTED state with RRC Inactive to support eDRX with long sleep cycles in RRC-Inactive. + +Supporting early data for RRC-Inactive has only very limited system impact (UE, RAN and AMF). In contrast to this, RAN and CN impact to support long sleep cycles in RRC Inactive is significant (due to the need to make AMF, SMF and UPF aware about the unreachability of the UE to make the CN behave as if the UE was in CM-IDLE state while the UE is actually in CM-CONNECTED state). + +Solution 19 proposes to introduce RRC Connection suspend and resume procedures similar to User Plane CIoT EPS Optimization. The solution bypasses Service Request procedure, based on RAN maintaining the AS context of the suspended UE. In comparison to EPS UP optimization an additional enhancement has been proposed: avoiding to fully resume the RRC connection if the UE sends a single UL packet only (indicated by AS Release Assistance Indication). As the UE is in CM-IDLE state when its RRC connection has been suspended, the solution can be easily combined with + +eDRX with long sleep cycles and the related HLCom mechanisms for CM-IDLE. The solution has limited impact to UE, RAN and CN. + +Solution 29 proposes to send UL small data together with UPF CL Service information (UCLSI) to the RAN. The RAN in turn looks up the target UPF by performing a DNS look-up using the UCLSI and forwards the data to the UPF using a shared N3 tunnel for UEs that are served by the same NR node. To identify the UE and PDU session the small data belongs to within the shared tunnel, the UCLSI is included as additional header information. For MT data the UPF keeps track of the last known RAN node serving a UE. Until a UE Location Freshness Timer expires, the UPF sends DL data to this last known RAN node. If the UE is not reachable in this last known RAN node, the DL data will be dropped, and the UE will be paged to determine its new serving RAN node. Solution 29 can be used with EDT and eDRX. It is also compatible with RRC Inactive. + +Solution 36 proposes to leverage RRC Inactive with two enhancements for frequent small data: + +- 1) Enable the RAN to avoid switching the N3 tunnel to the new RAN node by establishing a data forwarding tunnel between old and new RAN nodes. +- 2) Enable removing UP resources locally in the RAN, i.e. without paging the UE, in case of CN-initiated PDU session deactivation when the UE is in RRC Inactive. + +While (1) only impacts the RAN, (2) also impacts the AMF. + +Frequent Small Data Information including small data indication, Communication Pattern, etc. is sent to RAN in order to assist the RAN decision whether to send the UE to RRC Inactive state. UE resume request is extended to include small data indication which the NG-RAN can use to decide upon N3 path switching. + +Solution 41 illustrates how RRC Inactive as defined in Rel-15 can be combined with 5G UP optimization (see solution 19 above) and eDRX to efficiently support bursty frequent small data. The interoperability between RRC Inactive and eDRX is achieved via using short eDRX cycles in RRC Inactive. The solution re-uses the existing procedures for the AMF to pass the NAS negotiated eDRX value to RAN, and RAN configuring eDRX cycle and using RRC Inactive when applicable, taking into account also the RRC Inactive Assistance Information received from the AMF. If RAN chooses to use eDRX in RRC Inactive state, then the RAN node is responsible for DL data buffering. + +### 7.2.2 Enhancements of existing procedures + +RRC Inactive, eDRX, and EDT are already existing signalling optimisations, and even higher optimisation can be achieved by combining them. RRC Inactive can be enhanced further with EDT and eDRX. The feasibility of avoiding N3 tunnel switching by data forwarding would still need to be verified with RAN WG3. + +RRC Inactive, specifically when combined with the foreseen enhancements is already a significant improvement over the EPS capabilities, and consequently the 5G User Plane improvements need to be weighed against RRC Inactive. + +However, to efficiently address bursty frequent small data scenarios, i.e. scenarios where frequent small data occurs in bursts with significantly long silence periods in-between the bursts, solutions are required to enable UE power saving during those silence periods. Since long eDRX cycles cannot be supported efficiently in CM-CONNECTED with RRC Inactive the UE should be moved to CM-IDLE in order to leverage long eDRX sleep cycles. + +To reduce over-the-air signaling when the UE sends small data from CM-IDLE, the subsequent one-shot small data or burst of small data seems to need some User Plane optimisation among the candidate solutions documented in clause 7.2.1. + +Solution 41 in turn combines 5G UP optimization with RRC Inactive to jointly ensure that bursty frequent small data can be sent with minimal signaling overhead while extended DRX sleep cycles ranging from a few seconds to hours can be supported without causing significant system impacts. + +### 7.2.3 Optimised UP data solutions + +Solutions 5 and 29 can be used together with RRC Inactive, but since all these are optimising the RRC Connection establishment, some of the radio interface benefits of the proposed UP solutions are already available via RRC Inactive. Consequently, RRC Inactive and EDT can offer comparable optimisations at the radio interface. + +Solutions 5 and 29 can be used with EDT and eDRX. + +The proposed UP optimisations are characterized by the following aspects: + +- Shared N3 tunnel. +- User Plane data does not require CN overload protection that is needed for Control Plane data. +- User plane QoS and HLCom concepts can be re-used. + +These capabilities need to be weighed against the additional complexity caused by the solutions. + +### 7.2.4 UPF-NEF interface + +Solution 35 introduces new interface between UPF and NEF to support communication via NEF (T8 NIDD API) in addition to communication via UPF. + +Without this interface, T8 NIDD API cannot be provided over user plane. + +## 7.3 Key Issue 3: High latency communication + +For key issue 3 - High latency communication, the following two categories of solutions are proposed: + +- Extended buffering of downlink data in the network (solution 11, solution 24 and solution 25). +- Notification towards the AF(s) (solution 10, Solution 24, Solution 25 and solution 39). + +For Extended buffering of Downlink data in the network: + +Solution 10 proposes extended data buffering in UPF but use the term/concept of "UE availability after DDN failure" for communication between UPF/SMF/AMF. + +Solution 11 proposes to handle the High latency communication by extended buffering of DL data in the SMF. The SMF determines whether DL data shall be buffered based on input from the AMF. The AMF indicates to the SMF that the UE is unreachable, a Maximum estimated wait time for the UE to become reachable and, optionally, a DL Buffering Suggested Packet Count. The buffered DL data can be sent from the UPF/NEF to the RAN, as soon as the UE becomes reachable. The solutions has no impacts on UPF or NEF. Buffering in SMF meets the Architectural Requirement of key issue 3: "Send DL data to UEs at the earliest possible opportunity when the UEs are applying power saving functions". For UEs that remain in idle mode for a long time the associated UPF may change while the associated SMF will not. Since this solution is based on buffering in the SMF, it is more appropriate for this case because it would not require forwarding any buffered data among UPFs in case of UPF change. + +Solution 24 proposes to handle the High latency communication by extended buffering of downlink data in the UPF or SMF, and controlled by the AMF/SMF. The AMF asks the SMF to buffer downlink data, and provide buffering information to SMF. The SMF forward buffering information to UPF, and may decide the number of packets to buffer. + +Solution 25 proposes to buffer the DL data in UPF (for data via N6) or in the NEF (for data via APIs) based on the decision of the SMF which determines whether Extended Buffering applies for the downlink packet or not. The AMF indicates to the SMF that the UE is unreachable, a Maximum estimated wait time for the UE to become reachable and optionally a DL Buffering Suggested Packet Count. The SMF indicates to the UPF/NEF to buffer DL data with Extended Buffering time. The buffered DL data can be sent from the UPF/NEF to RAN as soon as the UE becomes reachable. Contrary to Solution 11, since this solution is based on UPF buffering, it seems more appropriate for UEs in idle mode for short periods of time because the associated UPF will most likely not change. + +For solutions for notification towards the AF(s): + +- Notification towards a single AF: + - Solution 10 proposes two notification procedures for Mobile Terminated Communication, UE reachability notification and UE availability notification procedure after DDN failure and has the same principles of solution 24 and 25. + - Solution 24 proposes the notification procedure from the AMF triggered by UE Reachability event or Availability after DDN failure event. The notification procedure for the UE in CM-CONNECTED with RRC\_INACTIVE state is also proposed and this aspect is not in scope for event notifications towards the SCS/AS. The triggers to generate the events within the network depend upon solutions to other key issues + +and are not in scope for notification procedures aspect of this key issue. The proposed notification procedure is based on the same principles as the notification procedure for HLCOM in EPC. In addition, this solution proposes a procedure to notify internal 5GCN NFs of UE availability after MT CP signalling. + +- Solution 25 proposes two notification procedures towards the AF: one from the AMF for notification of UE reachability and Availability after DDN failure (with reference to solution 24), and a second one from the SMF for data delivery status report to enhance the "extended data buffering" method. For MT control plane signaling handling in this solution, solution 24 is referenced. +- Notification of availability after DDN failure towards multiple AFs: + - Solution 39 is based on Solution 25 and proposes the Availability after DDN failure notification procedure in case of multiple Application Functions (AFs). The AF provides the Traffic Descriptor information during the Event Configuration procedure, and the Traffic Descriptor information can be used by the network to determine the corresponding AF at notification. The Availability after DDN failure event is sent to the AMF by the UDM, and the Availability after DDN failure event including Traffic Descriptor information is sent to the SMF by the UDM. After receiving the DDN message for the AF service, the SMF sends the message to the AMF including the NEF Reference ID. Once the event has happened, the AMF notifies the corresponding AF(s). + - Solution 50 proposes the Availability after DDN failure notification procedure in case of multiple Application Functions (AFs). The AF provides the application ID during the Event configuration procedure, and the Application ID is used by the network to determine the corresponding AF at notification. The "Application detection event" is sent to the SMF by the UDM, and the "Availability after DDN failure event" is sent to the AMF by the UDM. The SMF activates the "Application detection event" based on the application ID reported by the UPF. Once the event has happened, the SMF notifies the NEF the traffic sent by AF has been detected. Then the NEF subscribes the UE reachability event. The NEF notifies the corresponding AF(s) based on the SMF's notification and AMF's notification. + - The solutions above address the architectural requirements of key issue 3 to "Provide the AF (i.e. SCS/AS) with UE status information (e.g. reachability notification or the time when the UE is expected to be reachable)". The triggers to generate the events were not considered since they depend upon solutions to other key issues. + +Based on the evaluation above, it can be seen that all solutions support UE reachability notification and Availability after DDN failure notification from AMF in CM-IDLE mode. Solution 25 also covers the delivery of an SMF based buffering status report for the extended buffering approach. Solution 24 covers in addition the handling of these notifications in RRC inactive state and CM-IDLE with suspend. + +NOTE: Due to the limited duration of eDRX cycles for RRC-INACTIVE, it is assumed that there is no need for interaction between RRC-INACTIVE and HLCOM. + +## 7.4 Key Issue 4: Power Saving Functions + +**Editor's note:** This clause will capture the evaluation for key issue 4. + +For Key Issue 4, Track 1 ("extended DRX support in CM-IDLE"), Solution 22 has been proposed and enables eDRX in CM-IDLE state equivalent to eDRX support in EPS. + +For Key Issue 4, Track 1 ("extended DRX support in RRC-INACTIVE/ CM-CONNECTED"), Solutions 38 and 41 have been proposed. + +The key idea of Solution 38, Alternative 3 (and the related Solution 41) is to enable UE power saving as follows: + +- For short silence periods the ng-eNB can configure extended DRX in RRC-INACTIVE/CM-CONNECTED with sleep cycles up to the duration of the NAS (and SMS) retransmission timers. Limiting the sleep cycles to the NAS (and SMS) retransmission timers enables the core network to consider the UE reachable while the UE is in RRC-INACTIVE/CM-CONNECTED state with extended DRX. +- For longer silence periods, CM-IDLE state can be used along with longer extended DRX sleep cycles. As the UE is in CM-IDLE, the buffering and notification mechanisms that need to be specified for CM-IDLE anyhow can be re-used. (Note that this approach can be combined with different UP-based small data solutions, which are discussed as part of key issue 2). + +The benefit of this approach is that extended DRX sleep cycles ranging from a few seconds to hours can be supported without additional system impacts. + +In contrast to this, Solution 38 Alternative 1 aims at supporting very long sleep cycles in RRC-INACTIVE state, which leads to system impact by re-building CM-IDLE HLcom functionality in CM-CONNECTED state. This stems from the need to make the AMF, SMF and UPF aware about the unreachability of the UE to be able to behave as if the UE was in CM-IDLE state while the UE is actually in CM-CONNECTED state. + +For Key Issue 4 Track 2, Solutions 8, 9 and 23 are proposed. + +Solution 8 proposes an enhancement for mobile terminated data/signalling by introducing a minimum time to keep UE in RRC\_CONNECTED (the Connected time). The solution can save power and allows a faster DL data delivery. + +Solution 9 proposed the enhancement for MICO mode with Active Time. The Solution is based on the same principle as Power Saving Mode in EPS, and can save power for the case when the wait for subsequent data is long (e.g., if an external AF has a long response time). + +Solution 23 proposed to determining MICO mode and periodic registration timer value for the UE, taking into account communication pattern information, and providing a "do not reset the timer for Periodic Registration" indication to the UE and saves UE power according to the expected and desired UE and application behaviour. + +The above solutions jointly address all Architectural Requirements for Key Issue#4 (Power Saving Function) - Track 2. + +## 7.5 Key Issue 5: UE TX Power Saving Functions + +The solutions #32, #33, #34, #46 are understood to display some gains in some scenarios, some degradation in some other scenarios; no systematic gain is guaranteed. + +## 7.6 Key Issue 6: Management of Enhanced Coverage + +**Editor's note:** This clause will capture the evaluation for key issue 6. + +## 7.7 Key Issue 7: Overload Control for small data + +Key Issue 7 has only 1 solution: Solution 27. + +Solution 27 introduces Small Data Rate Control, Service Gap Control, AMF/SMF Overload Control and Control plane data back-off timer. The solution is based on the same principles as the Overload Control functions of EPS, and addresses all the Architectural requirements of Key Issue 7. + +## 7.8 Key Issue 8: Support of the Reliable Data Service + +For Key Issue 8 following two solutions are specified: + +- Solution 4 (Reliable data Service Support): This solution target both Key Issue 8 and Key Issue 1. Solution 4 has RDS support over NAS-MM layer. +- Solution 49 (Support for RDS with infrequent small data transmission solutions #1, 2, 3): This solution builds on top of other small data solutions i.e. solution #1, #2, and #3. + +In solution 4 support of RDS is similar to support of RDS over solution 2 (as described in solution 49) i.e. over NS-MM. Solution 49 provides a generic mechanism for RDS support and is based on RDS support design principles in EPS. + +## 7.9 Key Issue 9: Support of common north-bound APIs for EPC-5GC Interworking + +Key Issue 9 has 2 solutions. + +Solution 13 introduces the combined SCEF+NEF node. By using a combined node, the solution shows how the API termination point(s) associated with the UE can remain consistent even when the UE switches between EPC and 5GC. + +Since the solution continues the EPC principle that the exposure function(s) related to a UE will not change, there is no need to provide a way for the AF to detect API termination point changes and there is no need for exposure functions to exchange UE context. Solution 1 also points out that if the level of support of a given service changes (e.g. due to the UE's movement between EPC and 5GC), the SCEF+NEF will notify the SCS/AS. + +Solution 14 builds on solution 13 by showing, in more detail, if the level of support of a given service changes (e.g. due to the UE's movement between EPC and 5GC), the SCEF+NEF notifies the SCS/AS. + +## 7.10 Key Issue 10: Network Parameter Configuration API via NEF + +### 7.10.1 Overview + +Solution 15 addresses Key Issue 10. It aligns with the architectural baseline of the key issue in that it describes how an NEF API can be used to provide the network with Maximum Latency, Maximum Response Time, and Suggested Number of Downlink Packets and add the data to the UE's subscription information in the UDM/UDR. + +Solution 15 states that "*It is a subject of local policy in the UDM/UDR which external parameters are classified as AMF- Associated, SMF- Associated, and PCF- Associated parameters*" This flexibility, in terms of how parameters are classified, aligns the solution with solutions that have been selected for other Key Issues. + +### 7.10.2 Evaluation Relative to Key Issue 3 (High Latency Communication) + +Key Issue 3 (High Latency Communication) concluded that Solution 11 (DL data buffered in the SMF) and Solution 25 (DL data buffered in UPF/NEF) are used as the basis for normative work to address the extended buffering for high latency communication. + +In Solution 11, the AMF requests that the SMF buffer data and indicates how long the UE is expected to be sleeping. Thus, Maximum Response Time, and Maximum Latency may be considered an AMF- Associated parameters when Solutions 11 is used. The solution also uses the Suggested Number of Downlink Packets, however how the AMF or SMF determines the Suggested Number of Downlink Packets is left for the normative phase. + +In Solution 25, the AMF requests that the SMF configure the UPF to buffer data and indicates how long the UE is expected to be sleeping. Thus, Maximum Response Time, and Maximum Latency may also be considered an AMF- Associated parameters when Solutions 25 is used. The solution also uses the Suggested Number of Downlink Packets, however how the AMF or SMF determines the Suggested Number of Downlink Packets is left for the normative phase. + +### 7.10.3 Evaluation Relative to Key Issue 4 (Power Savings Functions) + +Key Issue 4 (Power Savings Functions) concluded that Solutions 22, 38 (Alternative 3), 8, 9, and 23 are used as the basis for normative work. Solution 22 states that "*Extended idle mode DRX cycle length value needs to be added in the subscription data from the UDM using the same principles as in EPS*". In both Solution 22 and Solution 38, alternative 3, the AMF provides the UE's accepted eDRX parameters. Solutions 8 and 9 describe that the AMF considers Maximum Response Time and Maximum Latency when configuring the UE's MICO mode. Thus, Maximum Response Timer and Maximum Latency may be considered AMF- Associated parameters. + +## 7.11 Key Issue 11: Monitoring + +Solution 37 addresses the architectural requirements for the Key Issue #11 - "Monitoring". Solution 37 describes how events may be monitored via the AMF, UDM, and PCF. It can be concluded that, Monitoring via the PCF is not required since is no scenario identified for Monitoring via the PCF in 5GC. + +In EPC there are two 2 ways of Monitoring Location and Communication Failure; one via the MME and one via the PCRF. TS 23.682 [6] does not specify why there are 2 methods or when each method should be used. However, one advantage of monitoring via the PCRF in EPC is that it can be used to monitor Location and Communication Failure when the UE accesses the network via WLAN. Since the MME is not involved in a WLAN access, monitoring via the MME is not possible. However, in 5GC, monitoring via the AMF is sufficient since the AMF is involved in when the UE accesses the network via WLAN (via the N3IWF). + +## 7.12 Key Issue 12: Inter-RAT mobility support to/from NB-IoT + +Solution 48 addresses the architectural baseline and requirements of Key Issue #12 by supporting separate radio capability handling for NB-IoT and by handling PDU sessions at idle mode inter-RAT mobility following the principles + +used by EPC, i.e. to determine the actions (maintain or disconnect, with or without reactivation request, or left to VPLMN policy) for a PDU session being stored in the subscription data or in the absence of subscription data based on local policy. + +## 7.13 Key Issue 13: Support for Expected UE Behaviour + +The combination of Solution 15 and Solution 26 describes in detail how and which parameters are to be provided to AMF and SMF to allow the 5GC to operate as effectively as EPC for devices with communication patterns. + +The parameters identified by Solution 26 are also provided by the 5GC to RAN, similarly to EPS, to support NB-IoT UE differentiation, appropriately configure the Uu radio interface, minimize the UE state transitions and achieve optimum network behaviour. + +- For PDU Session using data over NAS, Solution 28 describes how SMF sends the 'SMF assisted NG-RAN information' to the AMF during PDU Session establishment. The AMF transfers both the 'AMF assisted NG-RAN information' and the 'SMF assisted NG-RAN information' to the NG-RAN within the UE context. +- For PDU Session using data over UP, Solution 28 describes how the SMF sends 'SMF assisted NG-RAN information' within the N2 SM information. + +## 7.14 Key Issue 14: QoS Support for NB-IoT + +For Key Issue #14 four solutions categorized into two groups are captured in this TR: + +- Solutions for Inter-UE QoS differentiation: + - Solution 16 is based on the UDM provisioning the AMF and the UE of a QoS Index which, at service request, is indicated by the UE to the ng-eNB and used by the ng-eNB to prioritize the UE before RRC Message 4 is sent. The AMF later polices the usage of such QoS Index. + - In Solution 52 at registration the AMF retrieves from the UDM the NB-IoT QoS Index associated to that UE, it stores it locally and associates it to the 5G-S-TMSI indicated by the UE in the registration request. Later at service request, the ng-eNB, if not stored locally, can retrieve from the AMF the NB-IoT QoS Index associated to the indicated 5G-S-TMSI and, based on that, it prioritizes the UE before sending RRC Message 4. Such additional roundtrip may lead to some extra delay, but it allows to retrieve other information such as the UE Radio Capabilities. + - Both solutions allow to apply Inter-QoS differentiation before the ng-eNB sends RRC Message 4. +- Solutions for Intra-UE QoS differentiation: + - Solution 17 supports QoS differentiation among QoS flows of the same Unstructured PDU Session. The SMF sends QoS Rules to the UE without packet filters for Unstructured PDU Sessions. The UE uses its own logic to classify PDUs into QoS Flows in the UL. The SMF sends the N6 tunnel headers and mapping between N6 tunnel header and QFI of N3 or N9 tunnel for QoS Flows of Unstructured PDU Session to the UPF. The UPF classifies DL PDUs into N3 or N9 QoS flows using existing mechanism that filters DL PDUs based on N6 tunnel header. + - Solution 18 supports QoS differentiation among QoS flows of the same Unstructured PDU Session. A new packet filtering, Field Position Based (FPB) packet filter, is to be standardized. The SMF sends FPB packet filters to the UE and UPF. The UE and UPF need to support the new FPB packet filters for classifying unstructured PDUs into UL and DL QoS Flows, respectively. + +## 7.15 Key Issue 15: Core Network selection for Cellular IoT + +The solutions for KI#15 either address the architectural requirements for: + +- core network type selection at UE and core network node selection at RAN, AMF and MME, or +- redirection between CN types, e.g. for operator policy or load conditions, architectural requirements. + +The following solutions address the core network type selection at UE and core network node selection architectural requirements: + +- Solution 44. This solution uses standardised S-NSSAI(s) broadcast in system information that indicate sets of 5G CIoT features supported by the network. The solution requires the S-NSSAI(s) broadcast to be standardised and which feature(s) each standardised S-NSSAI represents. The UE provides the S-NSSAI for the feature(s) it wishes to use when establishing a connection. +- Solution 45. This solution uses an indication for each 5G CIoT optimisations, relevant for CN selection, broadcast in system information and the UE provides which 5G CIoT optimisations it prefers when establishing a connection in RAN and when performing registration, similar to the existing mechanism used in EPC. + +Both solutions can fulfil the requirements for Key Issue #15. However, solution #45 has following advantages. Solution 45 is based on similar mechanism used in EPC and therefore enables better interworking logic with EPC system. Solution 44 may lead to complex logic of mapping CIoT optimizations in EPC with standardized S-NSSAI values. It is also to be noted that low complexity CIoT devices may support single slice and therefore may not be pre-configured with any S-NSSAI values. In addition given the size of S-NSSAI is 32 bits long, it would be not efficient to broadcast standardized S-NSSAI in system information as compared to only few bits required for Solution 45. + +The following solutions address architectural requirements for redirection between CN types: + +- Solution 42. This solution uses a NAS level indication in registration/attach rejection to indicate to the UE that the N1/S1 mode needs to be disabled. The UE then disables the N1/S1 mode and performs an attach/registration to the target CN type. The solution uses existing procedures. + +NOTE: Whether a new cause value needs to be defined for a redirection, is up to Stage 3. + +- Solution 43. This solution uses an RRC level indication in RRC connection release after the registration/attach procedure to indicate to the UE that the target CN type needs to be selected. Such procedure exists for 5GS, but a similar procedure for EPS would need to be specified. Handovers and idle-mode mobility to the old CN type are prevented using existing procedures. The solution is not applicable for NB-IoT UE. Idle-mode mobility to the old CN type cannot be prevented if the operator uses the same RAT type(s) and frequencies in both EPS and 5GS. +- Solution 51. This solution provides the CN type selection rules to the UE either in USIM or in NAS in attach/registration acceptance. The UE then prioritizes the cells supporting the preferred CN type in cell selection/reselection and selects the preferred CN type if available in the cell the UE is camping on. The solution has an impact to the cell selection/reselection procedures that needs to be confirmed by 3GPP RAN WG2. + +## 7.16 Key Issue 16: Support of Group communication and messaging + +Group Message Delivery service can be supported by unicast MT NIDD between NEF and UE, with group based NIDD API used between AF(SCS/AS) and NEF. + +Several solutions to Key issue#1 and Key Issue #2 supports unicast MT NIDD. For example - Solution 30 supports MT NIDD delivery over control plane and solution 35 supports unicast MT NIDD over user plane. For evaluation of unicast MT NIDD solutions please refer to clause 7.1 and 7.2. + +Solution 30 also supports NIDD Configuration for group basis, which is essential to support Group Message Delivery service provided by NIDD API equivalent to T8 group message delivery API. + +## 7.17 Key Issue 17: MSISDN-less MO SMS + +No new solution is needed for Key Issue 17 as the agreed architectural baseline for this key issue provides sufficient details on a solution to start the normative work. + +# --- 8 Conclusions + +**Editor's note:** This clause will capture conclusions from the study. + +## 8.1 Key Issue 1: Support for infrequent small data transmission + +Solution 1 and solution 30 are recommended for normative work to support infrequent small data transmission via N6 and NIDD API. + +## 8.2 Key Issue 2: Frequent small data communication + +For Key Issue 2, it is recommended to use Solution 19 as the basis for normative work. + +NOTE: Solution 19 can also be used for infrequent small data scenarios. + +## 8.3 Key Issue 3: High latency communication + +For Key Issue 3, it is concluded that: + +- Solution 11 (DL data buffered in the SMF) and Solution 25 (DL data buffered in UPF/NEF) are used as the basis for normative work to address the extended buffering for high latency communication. +- Solution 25 is used as the basis for normative work to address the notification towards the AF for high latency communication. + +NOTE 1: For Solution 11 and 25, whether the AMF or SMF determines the DL Buffering Suggested Packet Count will be addressed during the normative phase. + +NOTE 2: For Solution 11, the details of how buffered data is forwarded in the interworking case will be addressed during the normative phase. + +- To address the availability after DDN failure notification for the case of multiple AFs, Solution 39 is used as the basis for normative work for the event configuration. + +NOTE 3: How to report the detection of the data from the AF will be addressed during the normative phase. + +## 8.4 Key Issue 4: Power Saving Functions + +For key issue 4, track 1, it is recommended that solution 22 is used as the basis for normative work to support extended DRX for UEs in CM-IDLE state. + +For Key Issue 4, Track 1, it is recommended that Solution 38 Alternative 3 is used as the basis for normative work to support extended DRX for UEs in RRC-INACTIVE/CM-CONNECTED state. As eDRX sleep cycles in RRC-INACTIVE are recommended to be supported up to the NAS (and SMS) retransmission timers, the core network considers the UE reachable while the UE is in RRC-INACTIVE/CM-CONNECTED state with extended DRX. This implies that from the perspective of this key issue there is no need to support specific high latency communication functionality for RRC-INACTIVE/CM-CONNECTED with extended DRX. + +NOTE: The maximum value for the eDRX cycle that can be supported in RRC-INACTIVE/CM-CONNECTED taking into account the NAS (and SMS) retransmission timers will be determined by CT groups. How the RAN learns whether a UE supports eDRX in RRC-INACTIVE will be determined as part of the normative phase. + +For Key Issue 4, Track 2, it is concluded that one solution is not sufficient to address the architectural requirement due to different application scenarios. It is therefore recommended that Solution 8, Solution 9 and Solution 23 are used as the basis for normative work to address UE power saving in different application scenarios. + +## 8.5 Key Issue 5: UE TX Power Saving Functions + +For Key Issue 5 "UE TX Power Saving Functions" it is recommended that no solution be specified addressing MT data reception and MO data transmission. + +## 8.6 Key Issue 6: Management of Enhanced Coverage + +For Key Issue #6 (Management of Enhanced Coverage), it is recommended to use Solution #12: "Solution for Management of Enhanced Coverage for 5GC" for normative work in the Rel-16. + +## 8.7 Key Issue 7: Overload Control for small data + +Solution 27 includes configuring the UE with low access priority and signalling it over N1 and it is concluded this is not required. Small Data Rate Control, Service Gap Control, AMF/SMF Overload Control and Control plane data back-off timer from Solution 27 are required. + +For Key Issue #7 (Overload Control for small data), it is recommended to use Small Data Rate Control, Service Gap Control, AMF/SMF Overload Control and Control plane data back-off timer from Solution #27: "Reuse of EPS Overload Control Mechanisms" as the basis for normative work. + +## 8.8 Key Issue 8: Support of the Reliable Data Service + +For Key Issue 8 (Support of the Reliable Data Service) it is proposed to use Solution 49 as the basis for normative work. + +## 8.9 Key Issue 9: Support of common north-bound APIs for EPC-5GC Interworking + +For the Key Issue 9 " Support of common north-bound APIs for EPC-5GC Interworking", it is concluded that, when a UE is capable of switching between EPC and 5GC, it shall only be associated with combined SCEF+NEF node(s) for Service Capability Exposure. It is recommended that the principles of Solution 13 be used for normative work. + +It is recommended that the principles of Solution 14 be used for normative work when specifying how, if availability and expected the level of support of a given service changes (e.g. due to the UE's movement between EPC and 5GC), the SCEF+NEF notifies the SCS/AS of the change and how the SCS/AS queries the SCEF+NEF for the availability and expected level of support of a service. + +NOTE: The north-bound APIs which can be supported by an EPC or 5GC network are discovered by the SCEF+NEF node via the CAPIF function and/or via local configuration of the SCEF+NEF node. Different sets of APIs can be supported by the two network types. + +## 8.10 Key Issue 10: Network Parameter Configuration API via NEF + +For Key Issue #10 (Network Parameter Configuration API via NEF), it is recommended to use Solution #15: External parameter provisioning in the 5GC as the basis of normative work in Rel-16. Maximum Response Timer and Maximum Latency will be considered AMF- Associated parameters. + +NOTE: Consistent with the Key Issue 3 conclusions, whether Suggested Number of Downlink Packets is considered an AMF-, SMF-, or PCF- Associated parameter will be addressed during the normative phase. + +## 8.11 Key Issue 11: Monitoring + +For Key Issue #11 (Monitoring), it is recommended to use Solution #37: Monitoring as the basis of normative work in Rel-16. Monitoring events at PCF in solution #37 will not be considered for Release -16 normative work. + +NOTE: For interworking between EPC and 5GC, Monitoring Location and Communication Failure is supported via AMF and MME. + +## 8.12 Key Issue 12: Inter-RAT mobility support to/from NB-IoT + +It is recommended to select solution 48 as the basis for normative work. + +## 8.13 Key Issue 13: Support for Expected UE Behaviour + +For Key Issue 13, it is concluded that: + +- Solution 15 and Solution 26 are used as the basis for normative work to address how and which parameters are provided to the CN. + +- For the provision of the parameters identified by Solution 26 to the NG-RAN, Solution 28 is used as the basis for normative work. + +NOTE: The protocol details of the signalling towards NG-RAN are left for normative phase, in cooperation with RAN WGs. + +## 8.14 Key Issue 14: QoS Support for NB-IoT + +For inter-UE QoS differentiation for Data over NAS, Solution 52 is selected as the basis for the normative phase. + +NOTE 1: Whether the differentiation is based on the NB-IoT UE QoS Index or on existing parameters is to be decided during the normative phase. + +For intra-UE QoS differentiation no solution is selected as the basis for the normative phase. + +## 8.15 Key Issue 15: Core Network selection for Cellular IoT + +For the architectural requirement on CN Type Selection for CIoT and discovery of 5G CIoT feature(s), it is recommended to use Solution 45 as the basis for the normative work. + +NOTE: The 5GS CIoT feature(s) to be included in RAN information broadcast, and indicated by the UE in the RRC and NAS signalling will be defined as part of the normative work. + +For the architectural requirement on CN redirection for CIoT UEs, it is recommended to use Solution 42 as the basis for the normative work. + +## 8.16 Key Issue 16: Support of Group communication and messaging + +For Group Message Delivery via unicast MT NIDD, NEF shall provide API to the AF (i.e. SCS/AS) equivalent to T8 group message delivery API, also NEF shall support unicast MT NIDD to the UE. + +## 8.17 Key Issue 17: MSISDN-less MO SMS + +The agreed Key Issue 17 architectural baseline will be used as the basis of normative work. + +# Annex A: Change history + +| Change history | | | | | | | | +|----------------|---------|-----------|----------|-----|-----|-------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2018-09 | SP#81 | SP-180793 | | | | MCC editorial update for presentation to TSG SA#81 for information | 1.0.0 | +| 2018-12 | SP#82 | SP-181109 | - | - | - | 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). Title corrected. | 16.0.0 | +| 2019-06 | SP#84 | SP-190432 | 000
3 | 1 | B | Conclusion for key issue 2 | 16.1.0 | \ No newline at end of file diff --git a/marked/Rel-16/23_series/23731/04cfca33e3fc26513abe649d7474f733_img.jpg b/marked/Rel-16/23_series/23731/04cfca33e3fc26513abe649d7474f733_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..38bdd479eacc64f8a3995a31516a93636c1e43e0 --- /dev/null +++ b/marked/Rel-16/23_series/23731/04cfca33e3fc26513abe649d7474f733_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6488ecff72fdf2ac3cb9d37e6ea274f067a64cfecf86a9a71b21177fbcf806d7 +size 44500 diff --git a/marked/Rel-16/23_series/23731/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg b/marked/Rel-16/23_series/23731/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a9f72593681f09873e4488dfb40bcf88b0d7eb9a --- /dev/null +++ b/marked/Rel-16/23_series/23731/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e2a94409f3039fcd200b6990c320536244b2dbeafe55238fc336550529a98597 +size 172763 diff --git a/marked/Rel-16/23_series/23731/077f85b82901283b4657fd2b45fc0294_img.jpg b/marked/Rel-16/23_series/23731/077f85b82901283b4657fd2b45fc0294_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..638474621692c55e82b201b4189cdf0f8810e7b1 --- /dev/null +++ b/marked/Rel-16/23_series/23731/077f85b82901283b4657fd2b45fc0294_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:601ba08a4707293662bea98da292fbe3d5c65cee9b3616db679b5ee92196fbf7 +size 91082 diff --git a/marked/Rel-16/23_series/23731/0931f3e098bd4539041de11c50cec2d2_img.jpg b/marked/Rel-16/23_series/23731/0931f3e098bd4539041de11c50cec2d2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..60984dd69f2308e6a6c9e4de51683c640a9504f9 --- /dev/null +++ b/marked/Rel-16/23_series/23731/0931f3e098bd4539041de11c50cec2d2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:af3aca16420c465d71ba532b345cfc76a6de0a8a8ece18af124a10b80e2b3d12 +size 88557 diff --git a/marked/Rel-16/23_series/23731/1230eaa9d75a09d7e7b8509931e9190e_img.jpg b/marked/Rel-16/23_series/23731/1230eaa9d75a09d7e7b8509931e9190e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2c805be0feec11a538c361de70b99b807ac2bda1 --- /dev/null +++ b/marked/Rel-16/23_series/23731/1230eaa9d75a09d7e7b8509931e9190e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4f64031ecfac9ca63ffd1e18cf16b19ac5440258c39c6ed8ebd7894e3436cfd4 +size 42511 diff --git a/marked/Rel-16/23_series/23731/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/marked/Rel-16/23_series/23731/1a827b10290f33d4fec04d0e8ef7a897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3f26a16c477c36e00f680439050a2fb884dc0c15 --- /dev/null +++ b/marked/Rel-16/23_series/23731/1a827b10290f33d4fec04d0e8ef7a897_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3c15cb1c93e16484d5da89e09264b50fc936d46f2b235db3d61fd633c4252212 +size 193538 diff --git a/marked/Rel-16/23_series/23731/20136850feb70fd71c7d41cdae203ebb_img.jpg b/marked/Rel-16/23_series/23731/20136850feb70fd71c7d41cdae203ebb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b45de02be136cbb717c549975806b49dbe9d38ae --- /dev/null +++ b/marked/Rel-16/23_series/23731/20136850feb70fd71c7d41cdae203ebb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:50be4b5f0b9a56722564d7309416ab184afc9ed3da529d621663b3c4213cb443 +size 51612 diff --git a/marked/Rel-16/23_series/23731/26d664119ad25250780f554633444e54_img.jpg b/marked/Rel-16/23_series/23731/26d664119ad25250780f554633444e54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9947c6682c9798acdd9623603a5ca415667fdb59 --- /dev/null +++ b/marked/Rel-16/23_series/23731/26d664119ad25250780f554633444e54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b3891e030bb95be30ed337e2364a8e70e3aee8817895540a09b797f10a5999cb +size 175008 diff --git a/marked/Rel-16/23_series/23731/2734e7f9be3e1dc046f14be2e6c9a085_img.jpg b/marked/Rel-16/23_series/23731/2734e7f9be3e1dc046f14be2e6c9a085_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6a0f303aa18165f9274efbcc3705eafde7f23caf --- /dev/null +++ b/marked/Rel-16/23_series/23731/2734e7f9be3e1dc046f14be2e6c9a085_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c0e9eb71df8eb4813c7bc545e84179bdecb399acca8b502d9276cad082ffab95 +size 55725 diff --git a/marked/Rel-16/23_series/23731/28085f681b9fff76a53c5b8b32338ee1_img.jpg b/marked/Rel-16/23_series/23731/28085f681b9fff76a53c5b8b32338ee1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f678624da56d700f7d3b4f7981c582744af163e8 --- /dev/null +++ b/marked/Rel-16/23_series/23731/28085f681b9fff76a53c5b8b32338ee1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b62492c41ec199be3011e63019c4f40426173ed238b98fffb60d03a7f9bd7e95 +size 84669 diff --git a/marked/Rel-16/23_series/23731/28d75f39a24203712ee907b32cf0bbe5_img.jpg b/marked/Rel-16/23_series/23731/28d75f39a24203712ee907b32cf0bbe5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f4af2fd984c116da60e6ec5ffb4f6bacb089216d --- /dev/null +++ b/marked/Rel-16/23_series/23731/28d75f39a24203712ee907b32cf0bbe5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f770e205ebb0cb36fc980cb10d892503acd634ebd0c27adfe7717ba634803b0e +size 104440 diff --git a/marked/Rel-16/23_series/23731/2a476a0b3dbc3429436246db4784ff9f_img.jpg b/marked/Rel-16/23_series/23731/2a476a0b3dbc3429436246db4784ff9f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6fe78482cac4965a8346047e99c566681af54632 --- /dev/null +++ b/marked/Rel-16/23_series/23731/2a476a0b3dbc3429436246db4784ff9f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5b363880b97ab901bc88ad9d98fdf4d15cc2878519ffb99f60936ab98f91b006 +size 60988 diff --git a/marked/Rel-16/23_series/23731/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg b/marked/Rel-16/23_series/23731/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f9b66c3122ad01b8b45856cf21b5e0cc51e387b9 --- /dev/null +++ b/marked/Rel-16/23_series/23731/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a2999da402cc032f7a2b601ebda6180f4002a7cd5875a3901ed62f10fec20d17 +size 20680 diff --git a/marked/Rel-16/23_series/23731/2f587210e4f97c32758c5972e2e83d20_img.jpg b/marked/Rel-16/23_series/23731/2f587210e4f97c32758c5972e2e83d20_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..483b176376cf2dca3eee4f94c602730857365859 --- /dev/null +++ b/marked/Rel-16/23_series/23731/2f587210e4f97c32758c5972e2e83d20_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:954027eed19d50f7dc9b612b5ad04a9611a4be6dccc21ec0517d95f2bb04fd8a +size 56856 diff --git a/marked/Rel-16/23_series/23731/30387053b5b3fede6873f6a46a9ca4a9_img.jpg b/marked/Rel-16/23_series/23731/30387053b5b3fede6873f6a46a9ca4a9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cecd21bcd2d039c65e13fdfa9792eafaac34a76f --- /dev/null +++ b/marked/Rel-16/23_series/23731/30387053b5b3fede6873f6a46a9ca4a9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bbe2aa4e2a5a2f7a7c49d84b30ecd49072f9326df3b67d0958770f84859cff90 +size 85171 diff --git a/marked/Rel-16/23_series/23731/315bdbeafb39026e19b77c26b19d9d1f_img.jpg b/marked/Rel-16/23_series/23731/315bdbeafb39026e19b77c26b19d9d1f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..384ab3e291e9b6505be70eaff6ede6c8f80b41d0 --- /dev/null +++ b/marked/Rel-16/23_series/23731/315bdbeafb39026e19b77c26b19d9d1f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b04e6a58d4da1779ee4cf260a1bf3551c2b97aa2f0036d7f1b85dd4ad8540174 +size 34915 diff --git a/marked/Rel-16/23_series/23731/329c96049bb432e9c2cbda4e224a0c9c_img.jpg b/marked/Rel-16/23_series/23731/329c96049bb432e9c2cbda4e224a0c9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..54b22fab53138995adabd5fb51af7a5edd59392c --- /dev/null +++ b/marked/Rel-16/23_series/23731/329c96049bb432e9c2cbda4e224a0c9c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:35f2cb90f9a98ed49ee7c46c0ce76a87a621952e9e2c5229a0afe47e1610d205 +size 52403 diff --git a/marked/Rel-16/23_series/23731/32ff77da4286b58c4778033acaa10836_img.jpg b/marked/Rel-16/23_series/23731/32ff77da4286b58c4778033acaa10836_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..44e3513a20dfdb74a366027901943050a0846e24 --- /dev/null +++ b/marked/Rel-16/23_series/23731/32ff77da4286b58c4778033acaa10836_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:af90cf4910630ae03c9323e680c90a7304ec7f8300fe6299c5863eb456b8eebb +size 160843 diff --git a/marked/Rel-16/23_series/23731/3337af75dfee8af7687b4f49914d6c93_img.jpg b/marked/Rel-16/23_series/23731/3337af75dfee8af7687b4f49914d6c93_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3250c2d1b3c351d579c7fd068d1097e99bab7674 --- /dev/null +++ b/marked/Rel-16/23_series/23731/3337af75dfee8af7687b4f49914d6c93_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2852afa55b1205ccb353ca0d3f0ae8c6bdc08bcb3eed030697df82419d7c07b1 +size 103281 diff --git a/marked/Rel-16/23_series/23731/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg b/marked/Rel-16/23_series/23731/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7c089a9a96daa7ab6cc6c4653f9b0eda56cc140c --- /dev/null +++ b/marked/Rel-16/23_series/23731/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7770915f4772952966934dc8748fd0f247fab35b3be564760b7ee2bc5526c2df +size 153476 diff --git a/marked/Rel-16/23_series/23731/347010b7ac06d3ae97927fde0f784d7c_img.jpg b/marked/Rel-16/23_series/23731/347010b7ac06d3ae97927fde0f784d7c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7e5da1bd3474a74626a9fa31738f6b5a701ce66b --- /dev/null +++ b/marked/Rel-16/23_series/23731/347010b7ac06d3ae97927fde0f784d7c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7977e1be54f335a596c98de9e79e61c7ffa4ae7423f1fa41360813bdf16fa21f +size 106611 diff --git a/marked/Rel-16/23_series/23731/3dea2a7c8e1120f769d0bc8ee347340d_img.jpg b/marked/Rel-16/23_series/23731/3dea2a7c8e1120f769d0bc8ee347340d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8476409e6e8e41ea61e59efe9810a0380150d54c --- /dev/null +++ b/marked/Rel-16/23_series/23731/3dea2a7c8e1120f769d0bc8ee347340d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3eb1b2d10c0f05498ae5367a70323dd37cab6c2e4eb0931f8ea970acb79d9d34 +size 41509 diff --git a/marked/Rel-16/23_series/23731/408c4798ea60469e0728a7cbbd598668_img.jpg b/marked/Rel-16/23_series/23731/408c4798ea60469e0728a7cbbd598668_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e4b89db5292a1de235c50665069df978d2ec538c --- /dev/null +++ b/marked/Rel-16/23_series/23731/408c4798ea60469e0728a7cbbd598668_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0ac1d19ff482d7ac706e39d6f39fbf863a794cd7db31494f42283ceb688d9ae7 +size 56289 diff --git a/marked/Rel-16/23_series/23731/4636adff5682a064f0ae5f13a1d464a6_img.jpg b/marked/Rel-16/23_series/23731/4636adff5682a064f0ae5f13a1d464a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..98057760232acbf586642bb1180ec4f1be23a32d --- /dev/null +++ b/marked/Rel-16/23_series/23731/4636adff5682a064f0ae5f13a1d464a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:08dd2f27a9b071b7b07e47a259baa7d2455f063649a689bd248ec3e158f37b40 +size 94303 diff --git a/marked/Rel-16/23_series/23731/4669a2ca9d019b9c2de9a9d9a0c4e644_img.jpg b/marked/Rel-16/23_series/23731/4669a2ca9d019b9c2de9a9d9a0c4e644_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b9ac9686763a75baf016764ad04311bc05d37b7e --- /dev/null +++ b/marked/Rel-16/23_series/23731/4669a2ca9d019b9c2de9a9d9a0c4e644_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c639ffa2f599d6665dd68e60e0f2fe12c96f5bfba21a9d82bcc0e38160a3f98f +size 38917 diff --git a/marked/Rel-16/23_series/23731/49fe8fe978c0f7e73112d231feb377eb_img.jpg b/marked/Rel-16/23_series/23731/49fe8fe978c0f7e73112d231feb377eb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cb9a4e0c7fa0744fe76347bb092cb702d670129e --- /dev/null +++ b/marked/Rel-16/23_series/23731/49fe8fe978c0f7e73112d231feb377eb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0424ec62ac2c6c6bfe71273858a8081f8c3601603a89d23031f189f59de856c4 +size 43020 diff --git a/marked/Rel-16/23_series/23731/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg b/marked/Rel-16/23_series/23731/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dfe87f200ffd3689452d33ce78f56499e5c66eb3 --- /dev/null +++ b/marked/Rel-16/23_series/23731/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ac9233e81edc2d1d3a895d365afb72bc47ff9c7dfc487a782795cb679274b094 +size 38365 diff --git a/marked/Rel-16/23_series/23731/55136bc716146672fc680fa05989f1d2_img.jpg b/marked/Rel-16/23_series/23731/55136bc716146672fc680fa05989f1d2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..98860f8facf11089bb070fe9f4b93ef5ab90286f --- /dev/null +++ b/marked/Rel-16/23_series/23731/55136bc716146672fc680fa05989f1d2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0686eb250d2d056ba82bd8176f0501ace875b3c24050ce252421828a456dc79b +size 55159 diff --git a/marked/Rel-16/23_series/23731/56a5265d174ce056c1dbe5e7a60839fc_img.jpg b/marked/Rel-16/23_series/23731/56a5265d174ce056c1dbe5e7a60839fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..534c7b04836a442071b5dea837df47cce01cb2e2 --- /dev/null +++ b/marked/Rel-16/23_series/23731/56a5265d174ce056c1dbe5e7a60839fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6543c83e2a4b0d1020f7126016f5492982de3f355d19964c529c8e2285663018 +size 46928 diff --git a/marked/Rel-16/23_series/23731/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Rel-16/23_series/23731/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1ed0b7fc3614f4165a8f17c83eb364e6ad3a00a4 --- /dev/null +++ b/marked/Rel-16/23_series/23731/5a4e62bead259c258d069fd3663ea670_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c9aefebd7ea9a91ff7a8007d21d35a8bc9fc5e6a164926eedba848f4716768a2 +size 42539 diff --git a/marked/Rel-16/23_series/23731/5e9af8986a5845504f251d3079da8078_img.jpg b/marked/Rel-16/23_series/23731/5e9af8986a5845504f251d3079da8078_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7f2b984eb14e43ca23c7f64e590c46bef8139020 --- /dev/null +++ b/marked/Rel-16/23_series/23731/5e9af8986a5845504f251d3079da8078_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b68cdb7eb7be27d857c098aec71f95b263e7db3858956f9eee8398a82de6dde0 +size 90364 diff --git a/marked/Rel-16/23_series/23731/60a40901e77feeb97ab6cf9c6d9418c3_img.jpg b/marked/Rel-16/23_series/23731/60a40901e77feeb97ab6cf9c6d9418c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3ff105e24bd0b5307e18896f5c503e6d596f5b91 --- /dev/null +++ b/marked/Rel-16/23_series/23731/60a40901e77feeb97ab6cf9c6d9418c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cec2ddda7b844cb02d712e6b47c00057842232b233f5a925a80ee15eb7c67660 +size 28883 diff --git a/marked/Rel-16/23_series/23731/65550960f5c5afd9d27706aaeddb0638_img.jpg b/marked/Rel-16/23_series/23731/65550960f5c5afd9d27706aaeddb0638_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..976fa7b06f2372f4b5d3613893351bb8756d61a4 --- /dev/null +++ b/marked/Rel-16/23_series/23731/65550960f5c5afd9d27706aaeddb0638_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bb509727dcc4785c0a4dfd103e23d56418f7d826a1642ab7215f57a4bffd3039 +size 33713 diff --git a/marked/Rel-16/23_series/23731/68a5a1a1a761c652b4b4c56da7cf9914_img.jpg b/marked/Rel-16/23_series/23731/68a5a1a1a761c652b4b4c56da7cf9914_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5d7e23c537efa20da7b4795e902235e1e1122462 --- /dev/null +++ b/marked/Rel-16/23_series/23731/68a5a1a1a761c652b4b4c56da7cf9914_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f446d19777833536e591c2f92bd3a199f326233958c6ebd6647895d057496511 +size 39175 diff --git a/marked/Rel-16/23_series/23731/6b3f7e259271c098750fd242877aae01_img.jpg b/marked/Rel-16/23_series/23731/6b3f7e259271c098750fd242877aae01_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1d83c9926c98e67e75c29d774dab2af08f792bd1 --- /dev/null +++ b/marked/Rel-16/23_series/23731/6b3f7e259271c098750fd242877aae01_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cea26de0f9214701e394463839b4071a7c29fe23cf684edb2cf7c7c0110100d3 +size 3801 diff --git a/marked/Rel-16/23_series/23731/71b0a68b4dd64961465d2b0e790538de_img.jpg b/marked/Rel-16/23_series/23731/71b0a68b4dd64961465d2b0e790538de_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..426904b0edc7833fecda5b669c39ad3fb8869a76 --- /dev/null +++ b/marked/Rel-16/23_series/23731/71b0a68b4dd64961465d2b0e790538de_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:13a2cd230f812f2919e3f653fc3bdcd7fc05b8a822170dd96b8a4d33ff97e64d +size 67156 diff --git a/marked/Rel-16/23_series/23731/74b540f71bcf10a8a66b2f01ea8c08ec_img.jpg b/marked/Rel-16/23_series/23731/74b540f71bcf10a8a66b2f01ea8c08ec_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4af488bd7ed9bc16bf7ccd173a16e304e0bdb3b4 --- /dev/null +++ b/marked/Rel-16/23_series/23731/74b540f71bcf10a8a66b2f01ea8c08ec_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5b18eb0895a2ca1c6eec5128ef6ad2a6c83309493417732ce769b2fb83a0f59d +size 122664 diff --git a/marked/Rel-16/23_series/23731/74d23510f27b21403a7be84820821863_img.jpg b/marked/Rel-16/23_series/23731/74d23510f27b21403a7be84820821863_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9b06dbf9b662a12fd817ca4e256cd20f0d2313bb --- /dev/null +++ b/marked/Rel-16/23_series/23731/74d23510f27b21403a7be84820821863_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3c3ce02720b9f993ac88fc97f1a4b988e49af39bd140b3c5f46c5f8762016e8e +size 83277 diff --git a/marked/Rel-16/23_series/23731/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg b/marked/Rel-16/23_series/23731/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..431ccf7c730e65c588ea93ff3317ead11f8363e7 --- /dev/null +++ b/marked/Rel-16/23_series/23731/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ef04890b5cc508079d785cb2964240826963ac1cea58d34532f452ae6ca8721c +size 72658 diff --git a/marked/Rel-16/23_series/23731/7a1dee155822446f7828dcb055c465c3_img.jpg b/marked/Rel-16/23_series/23731/7a1dee155822446f7828dcb055c465c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5fcca3164a0fbe12ded0e1c6ce9b9f67ed3d8fee --- /dev/null +++ b/marked/Rel-16/23_series/23731/7a1dee155822446f7828dcb055c465c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d60b89ff6eb053c80c1f88243f5240c48ec3aca25710342d77c4e9ff615534f9 +size 239454 diff --git a/marked/Rel-16/23_series/23731/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg b/marked/Rel-16/23_series/23731/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..89d1fe372fd464408baf901bbfc45f28a91200e9 --- /dev/null +++ b/marked/Rel-16/23_series/23731/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:008028a2a4479530b4a46648fbc60644a8a5ded0c8d576265da24473b3725a8b +size 28186 diff --git a/marked/Rel-16/23_series/23731/7fa73e6e0a02786ca9d45fb976726e79_img.jpg b/marked/Rel-16/23_series/23731/7fa73e6e0a02786ca9d45fb976726e79_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..33e6691806e4b4c2fbd5dc7c6aeee0ce60d48db2 --- /dev/null +++ b/marked/Rel-16/23_series/23731/7fa73e6e0a02786ca9d45fb976726e79_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f4ee41646a59944f6e9259475d4ea5e20ebfc99335509ad990941381a2801719 +size 4114 diff --git a/marked/Rel-16/23_series/23731/85b53faf49a839f512153285c78fbbdb_img.jpg b/marked/Rel-16/23_series/23731/85b53faf49a839f512153285c78fbbdb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..87c91f9f402c44a9803415ec08377b37e6c5fc51 --- /dev/null +++ b/marked/Rel-16/23_series/23731/85b53faf49a839f512153285c78fbbdb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b312e51eed5342697379180da707cb8a8a265c3b0c689abb582948542530d34a +size 139599 diff --git a/marked/Rel-16/23_series/23731/86bd357c573c9696393f5bde4d4cce4f_img.jpg b/marked/Rel-16/23_series/23731/86bd357c573c9696393f5bde4d4cce4f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9e75acbf1f9959940c4c4eed69b48f0f247b7fc7 --- /dev/null +++ b/marked/Rel-16/23_series/23731/86bd357c573c9696393f5bde4d4cce4f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5edfa33ac809f407511cc88d7ed2a85372256476c442afbde83838666409715d +size 63508 diff --git a/marked/Rel-16/23_series/23731/8a0a9aa5fac5d73eefb772afd44649f6_img.jpg b/marked/Rel-16/23_series/23731/8a0a9aa5fac5d73eefb772afd44649f6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5ab6ca4565af310b78a114ad48e296eb83ff697b --- /dev/null +++ b/marked/Rel-16/23_series/23731/8a0a9aa5fac5d73eefb772afd44649f6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:75f4f744319cafa98195d8d47167ddbf45550010be51578faaac85a1b51aad28 +size 63089 diff --git a/marked/Rel-16/23_series/23731/8c880d6b715587bd710a9ba8414469b1_img.jpg b/marked/Rel-16/23_series/23731/8c880d6b715587bd710a9ba8414469b1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a0a7bcdca97992b207de8e0fbf877d9f7fbb13c2 --- /dev/null +++ b/marked/Rel-16/23_series/23731/8c880d6b715587bd710a9ba8414469b1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6be31b101abe132b263bd1a330f1c1d6cc14ca0ff9fe8b451d0dbb5fc05da975 +size 31739 diff --git a/marked/Rel-16/23_series/23731/901755bf86813427f3a32efa0363a27c_img.jpg b/marked/Rel-16/23_series/23731/901755bf86813427f3a32efa0363a27c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e900444106a65b8361c07dd77f0a699aa1904b3c --- /dev/null +++ b/marked/Rel-16/23_series/23731/901755bf86813427f3a32efa0363a27c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5ef2f5aa3c1bbddbc920cc40949b6abd29647640ec6d3f3357552e8574d42477 +size 99497 diff --git a/marked/Rel-16/23_series/23731/90ddb84c323b956e2d50a54d3f870566_img.jpg b/marked/Rel-16/23_series/23731/90ddb84c323b956e2d50a54d3f870566_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7cd4c9918a6cf9969949437e5f74e1b516f4a5fe --- /dev/null +++ b/marked/Rel-16/23_series/23731/90ddb84c323b956e2d50a54d3f870566_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1711c3cbf157118707f05660df2bad8ccbb997e0ac585965eaa7620a22b09acf +size 41707 diff --git a/marked/Rel-16/23_series/23731/997233d405f0d4b89ddeb7683e047f66_img.jpg b/marked/Rel-16/23_series/23731/997233d405f0d4b89ddeb7683e047f66_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8709c587d23ef39d1cd31089b614396a1c6ca524 --- /dev/null +++ b/marked/Rel-16/23_series/23731/997233d405f0d4b89ddeb7683e047f66_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f198af5ac6122cef859c7b07dd0cfd288071ef39f9617c277b06d03dda614b37 +size 101420 diff --git a/marked/Rel-16/23_series/23731/9b686adccf125267a013fa25721231a3_img.jpg b/marked/Rel-16/23_series/23731/9b686adccf125267a013fa25721231a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7e15c94ba0a9136148ca402fcb24fac4ae1c977c --- /dev/null +++ b/marked/Rel-16/23_series/23731/9b686adccf125267a013fa25721231a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:29a979bc16bf4567e31bdf4192bb951002ba73ea36e90a2efe07b68ce7171850 +size 21951 diff --git a/marked/Rel-16/23_series/23731/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg b/marked/Rel-16/23_series/23731/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7aaa29bd1dbec55abed2a179113658428606d78e --- /dev/null +++ b/marked/Rel-16/23_series/23731/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2609054018d76ebfe5a909cbb012b663fcea80564120c1b7da21e0d50ccaab9b +size 45388 diff --git a/marked/Rel-16/23_series/23731/9f6dec4d4e9fde40bce018861ef1278e_img.jpg b/marked/Rel-16/23_series/23731/9f6dec4d4e9fde40bce018861ef1278e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f143d6fe08ae5c6e4ba20c29f2d4b3f84eff5f0b --- /dev/null +++ b/marked/Rel-16/23_series/23731/9f6dec4d4e9fde40bce018861ef1278e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9b9c5aee6b6863cef4e333472342d63350ea8f0c2f1d54d81672fc8310f4e99d +size 31666 diff --git a/marked/Rel-16/23_series/23731/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg b/marked/Rel-16/23_series/23731/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0d57d0a1a2c5c8591087f220e358768ea888dcf9 --- /dev/null +++ b/marked/Rel-16/23_series/23731/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3fba91c0ab2c9e32c4b4c90cf7f305b543f57b1e2e21af75748a1ee49739c06c +size 178118 diff --git a/marked/Rel-16/23_series/23731/a0e8fe7862a6d7341faf5dac275277cc_img.jpg b/marked/Rel-16/23_series/23731/a0e8fe7862a6d7341faf5dac275277cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fffd8654ac03c27e4a408071c1725b089940968f --- /dev/null +++ b/marked/Rel-16/23_series/23731/a0e8fe7862a6d7341faf5dac275277cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8799adb927aef228bffae2246c07573bcb200b682ac1ed70c28cc3595e536125 +size 165819 diff --git a/marked/Rel-16/23_series/23731/a1890b9a9b85f13e67ed59bbad623659_img.jpg b/marked/Rel-16/23_series/23731/a1890b9a9b85f13e67ed59bbad623659_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1149d83391b2b0c63335968086d7d1c39ee0518f --- /dev/null +++ b/marked/Rel-16/23_series/23731/a1890b9a9b85f13e67ed59bbad623659_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1fd86efd0e977a3e55a1c31b447cb664852f514b631de1dfd73255cfbf9f1c3e +size 128693 diff --git a/marked/Rel-16/23_series/23731/a24e89a6fe9bb70c83f8bf5202baba95_img.jpg b/marked/Rel-16/23_series/23731/a24e89a6fe9bb70c83f8bf5202baba95_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..18959b540f5ec8de2d06f2a1cf8b1fc85ef0bb3b --- /dev/null +++ b/marked/Rel-16/23_series/23731/a24e89a6fe9bb70c83f8bf5202baba95_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:34f481c5ddb530adde27ab965a45c202e2a03848e07fa871a34b1fae25d3eb0b +size 83837 diff --git a/marked/Rel-16/23_series/23731/adc59ed6840bcb2d392ea323abfccedc_img.jpg b/marked/Rel-16/23_series/23731/adc59ed6840bcb2d392ea323abfccedc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a0f613d78a4c54855b73f278dca12f4fb80fba26 --- /dev/null +++ b/marked/Rel-16/23_series/23731/adc59ed6840bcb2d392ea323abfccedc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:73bd505bce2df32a4088c2f5bea7f13a47141ba638a12aebc789524724d8b167 +size 35958 diff --git a/marked/Rel-16/23_series/23731/ae0dd5533e0b7fd2db452b5e2fdf8e5b_img.jpg b/marked/Rel-16/23_series/23731/ae0dd5533e0b7fd2db452b5e2fdf8e5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c1d3b5811da57bdf00de760ae8f317769a76b9c1 --- /dev/null +++ b/marked/Rel-16/23_series/23731/ae0dd5533e0b7fd2db452b5e2fdf8e5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b1e111214fbe0727cab0d528d51735ba0e2dabeda1df121d6eb21d72177b3177 +size 98068 diff --git a/marked/Rel-16/23_series/23731/aeb2a26a07219661191294dba528067a_img.jpg b/marked/Rel-16/23_series/23731/aeb2a26a07219661191294dba528067a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..559b389d85b60c9b9870ea20a0acd38e98646e4f --- /dev/null +++ b/marked/Rel-16/23_series/23731/aeb2a26a07219661191294dba528067a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5b56578aaeebf34c4d4895adc6236b2f595419cf0f0a449005c11d4574387053 +size 29002 diff --git a/marked/Rel-16/23_series/23731/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg b/marked/Rel-16/23_series/23731/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5c3f8b6e32719a24cbf5a8ea86c98a7aa2c1feb1 --- /dev/null +++ b/marked/Rel-16/23_series/23731/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4bc47d78de911ad76178a6507ba4ec2cb27bff10d253cb88ffceb10dfb3ac98a +size 58472 diff --git a/marked/Rel-16/23_series/23731/b3cd59f24a21fab4cd8ac6fe743ab3a9_img.jpg b/marked/Rel-16/23_series/23731/b3cd59f24a21fab4cd8ac6fe743ab3a9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0bd1d949af6d3bd17336423f24ba52747f963bdd --- /dev/null +++ b/marked/Rel-16/23_series/23731/b3cd59f24a21fab4cd8ac6fe743ab3a9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ea28653578d847bb6d3fc7058de2f6edd45be3c6a605b92f49610fdd318e1bab +size 35672 diff --git a/marked/Rel-16/23_series/23731/b97737027bd1b2effd7ca4dba8914877_img.jpg b/marked/Rel-16/23_series/23731/b97737027bd1b2effd7ca4dba8914877_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9354a3d7f20d93cbf8ed56661f79c11a8461de1d --- /dev/null +++ b/marked/Rel-16/23_series/23731/b97737027bd1b2effd7ca4dba8914877_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:00e5c5564b97d0afdbf6b1d1bf9b6ffd365efa0e7e8dfd5dcdc760535290b604 +size 40171 diff --git a/marked/Rel-16/23_series/23731/c2f36c545b190860d04e1d84e58d22cc_img.jpg b/marked/Rel-16/23_series/23731/c2f36c545b190860d04e1d84e58d22cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..84e07c78b666f7fce008d54c99e6de968fd7d852 --- /dev/null +++ b/marked/Rel-16/23_series/23731/c2f36c545b190860d04e1d84e58d22cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ef5d217c2918db91f455d9666aef42cef3e2fa9a4836fb4b4b70d295270876ef +size 98696 diff --git a/marked/Rel-16/23_series/23731/c2fc2621e8206d24427b56bcb2398fc0_img.jpg b/marked/Rel-16/23_series/23731/c2fc2621e8206d24427b56bcb2398fc0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d743947529069f98a0cc1a544d8c6b15148c7484 --- /dev/null +++ b/marked/Rel-16/23_series/23731/c2fc2621e8206d24427b56bcb2398fc0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:40f27bf63f0ece6be927414c5e139d6e779f0afc42c780a0f17170fd32b93341 +size 35794 diff --git a/marked/Rel-16/23_series/23731/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg b/marked/Rel-16/23_series/23731/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b84abe87455080af52ca0ad2e6cc9cfb1beac657 --- /dev/null +++ b/marked/Rel-16/23_series/23731/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4717bfa708b125b6661297239a1fc868d2a7181d4729a7a492ad93cf904486c5 +size 148214 diff --git a/marked/Rel-16/23_series/23731/ca5566458a134032dd860e88fdaa0d2b_img.jpg b/marked/Rel-16/23_series/23731/ca5566458a134032dd860e88fdaa0d2b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..98b293bab5f8c7a2733f976b383984087f1605bb --- /dev/null +++ b/marked/Rel-16/23_series/23731/ca5566458a134032dd860e88fdaa0d2b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8b6aa6ece8f509b07ce74c218af0de5b5df696acc3a448f191a36f659b00f3cc +size 100790 diff --git a/marked/Rel-16/23_series/23731/db39acbd11df5eb7e79ab84562fb8f74_img.jpg b/marked/Rel-16/23_series/23731/db39acbd11df5eb7e79ab84562fb8f74_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b18d02698960b225ef00feac5f9c0315f9ace1f7 --- /dev/null +++ b/marked/Rel-16/23_series/23731/db39acbd11df5eb7e79ab84562fb8f74_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:57823ee51f639ea6b2ab3acb8587f3fc809a69408d291a64e981b25011463438 +size 59862 diff --git a/marked/Rel-16/23_series/23731/dd5771673aececa53d42ece89218299d_img.jpg b/marked/Rel-16/23_series/23731/dd5771673aececa53d42ece89218299d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..985abe09d3b01e0841567711ce53e0117a363426 --- /dev/null +++ b/marked/Rel-16/23_series/23731/dd5771673aececa53d42ece89218299d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ef8bc154e2ae76f988364a30e097289a1197b796bf7193a6a3c03ddc4b252f91 +size 50676 diff --git a/marked/Rel-16/23_series/23731/dfe74512a9c9fb620f72c9dbc22874aa_img.jpg b/marked/Rel-16/23_series/23731/dfe74512a9c9fb620f72c9dbc22874aa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c1400c7371f3262a81041b1a08b6162d257ce7b5 --- /dev/null +++ b/marked/Rel-16/23_series/23731/dfe74512a9c9fb620f72c9dbc22874aa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ff406a7fca5a6c43bb6924ece4a32984ba3062fd78418700828141f14f057f23 +size 126901 diff --git a/marked/Rel-16/23_series/23731/e05b36c0d46549e681ce6581422c66b2_img.jpg b/marked/Rel-16/23_series/23731/e05b36c0d46549e681ce6581422c66b2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..164d5b61c47fe4ee0aa04126a575691d34b0d671 --- /dev/null +++ b/marked/Rel-16/23_series/23731/e05b36c0d46549e681ce6581422c66b2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ce8560e1c4db22202df5109e6da62e45e1414b360cd135d31f8bf7ec2234d372 +size 72653 diff --git a/marked/Rel-16/23_series/23731/e312e2a5beb4c6cb8bc0a3aed9944d96_img.jpg b/marked/Rel-16/23_series/23731/e312e2a5beb4c6cb8bc0a3aed9944d96_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c6f492cf342828d19c20d9df5537a5697ee18267 --- /dev/null +++ b/marked/Rel-16/23_series/23731/e312e2a5beb4c6cb8bc0a3aed9944d96_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4a5d2ff792a3b19065a4dfeba7486ecdb48378adb49450bee4e1dc15364f346c +size 4141 diff --git a/marked/Rel-16/23_series/23731/e38f0349f1b6094626cbfeab7105f029_img.jpg b/marked/Rel-16/23_series/23731/e38f0349f1b6094626cbfeab7105f029_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b128cc5e0930f455e690955c95342900c5837e89 --- /dev/null +++ b/marked/Rel-16/23_series/23731/e38f0349f1b6094626cbfeab7105f029_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3fe1ba9d7f67c31a4429b757cdf3c3f853542c8216d3acfa21b921c8c8019e95 +size 49028 diff --git a/marked/Rel-16/23_series/23731/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/Rel-16/23_series/23731/e6df2733626a85205c1db682e6259c46_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c808f87f56d8bee71c33f18180e1db5f890aa47d --- /dev/null +++ b/marked/Rel-16/23_series/23731/e6df2733626a85205c1db682e6259c46_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:40be71349c9b8ec168c5185a057290fbec74568880ebaba2ce4b7f5c8f7f468d +size 39763 diff --git a/marked/Rel-16/23_series/23731/e7010c66da16316c2935dfbbef5056b3_img.jpg b/marked/Rel-16/23_series/23731/e7010c66da16316c2935dfbbef5056b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..226bbd2a2586dd2de1c9abec72e430fe86b1c237 --- /dev/null +++ b/marked/Rel-16/23_series/23731/e7010c66da16316c2935dfbbef5056b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2b2a0a82b17a556d93a40252f2d9cfd4ba94248568a23b127862680dff8c90a4 +size 102929 diff --git a/marked/Rel-16/23_series/23731/e90b25c8d90cadc3f76c376701cf27ed_img.jpg b/marked/Rel-16/23_series/23731/e90b25c8d90cadc3f76c376701cf27ed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dac3d8d8126f1fc39a6fe835c73cc43f824c7e73 --- /dev/null +++ b/marked/Rel-16/23_series/23731/e90b25c8d90cadc3f76c376701cf27ed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7202f900b0e2142ca8bab73a95c64bddea769e495b77476df0b4ab39d2572bb4 +size 82796 diff --git a/marked/Rel-16/23_series/23731/ead623e6a8ec701df64567695a57d01c_img.jpg b/marked/Rel-16/23_series/23731/ead623e6a8ec701df64567695a57d01c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4fdfaaaf7ce2a28591c3cda7049f629734dabea0 --- /dev/null +++ b/marked/Rel-16/23_series/23731/ead623e6a8ec701df64567695a57d01c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c668c8b214c6e90ec6ddec3746555c7f66dcc5f13daae5d76243e1a827cb42d5 +size 37744 diff --git a/marked/Rel-16/23_series/23731/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg b/marked/Rel-16/23_series/23731/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..750e4bc4ec607cd2bd1034da939751df11066376 --- /dev/null +++ b/marked/Rel-16/23_series/23731/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b8ae1d435a885f338d20d04eb66dded06513e607c5c7801d7420863190baf26a +size 183184 diff --git a/marked/Rel-16/23_series/23731/f1fbb1287d999c7034742de35bdab836_img.jpg b/marked/Rel-16/23_series/23731/f1fbb1287d999c7034742de35bdab836_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7cb031fe86ab5a940d53137874f8b8a42d82ee90 --- /dev/null +++ b/marked/Rel-16/23_series/23731/f1fbb1287d999c7034742de35bdab836_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:119446a548e9e6eb63483c7b770417d7014c9bfe6d0a8667d4fcba05fc7b1d82 +size 32547 diff --git a/marked/Rel-16/23_series/23731/fd3cbb53e991f8209ba17b398f426e13_img.jpg b/marked/Rel-16/23_series/23731/fd3cbb53e991f8209ba17b398f426e13_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..44797a1bbedc9e76bc1b71a1f7145b2c22f47765 --- /dev/null +++ b/marked/Rel-16/23_series/23731/fd3cbb53e991f8209ba17b398f426e13_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8c1d2cd8bdfe5f0fed3600f53527b34695eedbf113ae62917a6b0c73c37d07dc +size 77314 diff --git a/marked/Rel-16/23_series/23731/fe7304192caf64cda93b580c5e7e5c06_img.jpg b/marked/Rel-16/23_series/23731/fe7304192caf64cda93b580c5e7e5c06_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a71e4d73d150d7a3fe4c3b5a1bd70a2c4216d381 --- /dev/null +++ b/marked/Rel-16/23_series/23731/fe7304192caf64cda93b580c5e7e5c06_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2d32cfdded54a472adc0e4e39c85c90c64adbafd06adcc28f95d8caac2b0214d +size 57766 diff --git a/marked/Rel-16/23_series/23731/ffb6acd27b8e3a54392840948a75869f_img.jpg b/marked/Rel-16/23_series/23731/ffb6acd27b8e3a54392840948a75869f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..064cf45df471fb1780ae0071d94620854ba91502 --- /dev/null +++ b/marked/Rel-16/23_series/23731/ffb6acd27b8e3a54392840948a75869f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4f7a1a5e38a2cdd073ec1aaf4db8bc2ca2e63928384b072ee549eff24f51ad0f +size 116776 diff --git a/marked/Rel-16/23_series/23731/raw.md b/marked/Rel-16/23_series/23731/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..674248da3b66ffc9afc249b9618dad371fba9721 --- /dev/null +++ b/marked/Rel-16/23_series/23731/raw.md @@ -0,0 +1,6676 @@ +# Contents + +| | | +|-----------------------------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 10 | +| 1 Scope..... | 11 | +| 2 References..... | 11 | +| 3 Definitions and abbreviations ..... | 12 | +| 3.1 Definitions..... | 12 | +| 3.3 Abbreviations ..... | 12 | +| 4 Architectural Requirements and Assumptions..... | 12 | +| 4.1 Architectural Requirements..... | 12 | +| 4.2 Architectural Assumptions..... | 13 | +| 5 Key Issues ..... | 13 | +| 5.1 Key Issue 1: Enhancement to LCS Architecture..... | 13 | +| 5.1.1 Description ..... | 13 | +| 5.2 Key Issue 2: Positioning via user plane transmission ..... | 14 | +| 5.2.1 Description ..... | 14 | +| 5.3 Key Issue 3: Support of low latency and high performance LCS..... | 14 | +| 5.3.1 Description ..... | 14 | +| 5.4 Key Issue 4: Reduce overhead for repetitive non-successful privacy verification ..... | 15 | +| 5.4.1 Description ..... | 15 | +| 5.5 Key Issue 5: Slicing dependent location service..... | 15 | +| 5.5.1 Description ..... | 15 | +| 5.6 Key Issue 6: Scalability..... | 16 | +| 5.6.1 Description ..... | 16 | +| 5.7 Key Issue 7: Location service exposure..... | 16 | +| 5.7.1 Description ..... | 16 | +| 5.8 Key Issue 8: Support of IoT UEs ..... | 17 | +| 5.8.1 Description ..... | 17 | +| 5.9 Key Issue 9: Support EUTRAN positioning methods ..... | 17 | +| 5.9.1 Description ..... | 17 | +| 5.10 Key Issue 10: Support NR positioning methods..... | 17 | +| 5.10.1 Description ..... | 17 | +| 5.11 Key Issue 11: Coordination of Positioning Signalling Transmitted via Control Plane Path and User Plane Path..... | 17 | +| 5.11.1 Description ..... | 17 | +| 5.12 Key Issue 12: LCS support for Non-3GPP access ..... | 18 | +| 5.12.1 Description ..... | 18 | +| 5.13 Key Issue 13: Support of Flexible and Efficient Periodic and Triggered Location..... | 18 | +| 5.13.1 Description ..... | 18 | +| 5.14 Key Issue 14: Positioning Access selection for LCS service..... | 18 | +| 5.14.1 Description ..... | 18 | +| 5.15 Key Issue 15: Location continuity support ..... | 19 | +| 5.15.1 Description ..... | 19 | +| 5.16 Key Issue 16: Distribution Positioning Assistance Data..... | 19 | +| 5.16.1 Description ..... | 19 | +| 6 Solutions..... | 20 | +| 6.1 Solution 1: 5GS LCS Functionality and Allocation to 5GS elements - Option 1 and Option 2 ..... | 20 | +| 6.1.1 Introduction ..... | 20 | +| 6.1.2 Functional Description ..... | 21 | +| 6.1.2.1 Common Functionality ..... | 21 | +| 6.1.2.2 Option A: EPS like allocation..... | 21 | +| 6.1.2.3 Option B: LMF centric allocation..... | 23 | +| 6.1.3 Procedures ..... | 25 | +| 6.1.4 Impacts on existing entities and interfaces..... | 25 | +| 6.1.5 Evaluation..... | 25 | +| 6.2 Solution 2: LMF Based Location Solution ..... | 25 | +| 6.2.1 Introduction ..... | 25 | + +| | | | +|-----------|----------------------------------------------------------------------------------------|----| +| 6.2.2 | Functional Description ..... | 26 | +| 6.2.2.1 | Architecture ..... | 26 | +| 6.2.2.2 | Reference points and Service based interfaces ..... | 27 | +| 6.2.3 | Procedures ..... | 28 | +| 6.2.3.1 | 5GC-MT-LR Procedure..... | 28 | +| 6.2.3.2 | 5GC-MO-LR Procedure ..... | 31 | +| 6.2.3.3 | Periodic and Triggered 5GC-MT-LR Procedure ..... | 33 | +| 6.2.3.4 | Optimized Periodic and Triggered 5GC-MT-LR Procedure ..... | 36 | +| 6.2.3.5 | Low Power Periodic and Triggered 5GC-MT-LR Procedure ..... | 38 | +| 6.2.4 | Compatibility with the Location Solution for regulatory services in Release 15..... | 41 | +| 6.2.4.1 | Architectural Compatibility ..... | 41 | +| 6.2.4.2 | Compatibility on the N1 Reference Point..... | 42 | +| 6.2.4.3 | Compatibility on the N2 Reference Point..... | 42 | +| 6.2.4.4 | Compatibility on the NLs Reference Point..... | 42 | +| 6.2.4.5 | Compatibility on the NLg and NLg* Reference Points..... | 43 | +| 6.2.4.6 | Compatibility on the NLh Reference Point ..... | 44 | +| 6.2.5 | Impacts on existing entities and interfaces..... | 44 | +| 6.2.5.1 | Impacts to UDM and Nudm SBI ..... | 44 | +| 6.2.5.2 | Impacts to GMLC and Ngmlc SBI ..... | 45 | +| 6.2.5.3 | Impacts to LMF and Nlmf SBI ..... | 46 | +| 6.2.5.4 | Impacts to UE ..... | 49 | +| 6.2.5.5 | Impacts to AMF and Namf SBI..... | 51 | +| 6.2.5.6 | Impacts to the NG-RAN ..... | 51 | +| 6.2.6 | Evaluation..... | 52 | +| 6.3 | Solution 3: Enhancement to LCS architecture ..... | 52 | +| 6.3.1 | Description ..... | 52 | +| 6.3.2 | Reference LCS architecture..... | 52 | +| 6.3.2 | Functional Description ..... | 53 | +| 6.3.4 | Impacts on existing entities and interfaces..... | 54 | +| 6.3.5 | Evaluation..... | 54 | +| 6.4 | Solution 4: Positioning operations considering different LMF deployment scenarios..... | 54 | +| 6.4.1 | Introduction ..... | 54 | +| 6.4.2 | Functional Description ..... | 54 | +| 6.4.2.1 | Common Functionality ..... | 54 | +| 6.4.2.2 | Solution 4A: AMF based selection solution with positioning signalling via AMF..... | 55 | +| 6.4.2.3 | Solution 4B: LMF centric based selection solution..... | 55 | +| 6.4.3 | Procedures ..... | 55 | +| 6.4.3.1 | Procedures for the Solution 4A..... | 55 | +| 6.4.3.1.1 | 5GC-MO-LR Procedure for the Solution 4A..... | 55 | +| 6.4.3.1.2 | 5GC-MT-LR Procedure for the Solution 4A ..... | 57 | +| 6.4.3.2 | Procedures for the Solution 4B..... | 58 | +| 6.4.3.2.1 | 5GC-MT-LR Procedure for the Solution 4B ..... | 58 | +| 6.4.3.2.2 | 5GC-MO-LR Procedure for the Solution 4B..... | 59 | +| 6.4.4 | Impacts on existing entities and interfaces..... | 60 | +| 6.4.4.1 | Impacts of Solution 4A ..... | 60 | +| 6.4.4.2 | Impacts of Solution 4B ..... | 60 | +| 6.4.5 | Evaluation..... | 60 | +| 6.4.5.1 | Evaluation of Solution 4A ..... | 60 | +| 6.5 | Solution 5: Privacy Check with UE privacy setting..... | 60 | +| 6.5.1 | Introduction ..... | 60 | +| 6.5.2 | Functional Description ..... | 60 | +| 6.5.3 | Procedures ..... | 61 | +| 6.5.3.1 | 5GC-MT-LR with privacy check..... | 61 | +| 6.5.3.2 | Privacy Setting Update ..... | 63 | +| 6.5.3.3 | 5GC-MT-LR with privacy check based on LMF based architecture ..... | 64 | +| 6.5.4 | Impacts on existing entities and interfaces..... | 65 | +| 6.5.5 | Evaluation..... | 65 | +| 6.6 | Solution 6: User Privacy Setting send via AMF ..... | 65 | +| 6.6.1 | Introduction ..... | 65 | +| 6.6.2 | Functional Description ..... | 65 | +| 6.6.3 | Procedures ..... | 65 | +| 6.6.3.1 | Privacy Setting Update ..... | 65 | + +| | | | +|-----------|-----------------------------------------------------------------------------|----| +| 6.6.3.2 | Privacy Verification ..... | 66 | +| 6.6.3.3 | GMLC service..... | 66 | +| 6.6.3.3.1 | General ..... | 66 | +| 6.6.3.3.2 | Ngmlc_UserPrivacy_Set service operation..... | 67 | +| 6.6.3.4 | PPR service..... | 67 | +| 6.6.3.4.1 | General ..... | 67 | +| 6.6.3.4.2 | Nppr_PVPreference_Set service operation..... | 67 | +| 6.6.4 | Impacts on existing entities and interfaces..... | 67 | +| 6.6.5 | Evaluation..... | 68 | +| 6.7 | Solution 7: User Privacy Setting send via LMF ..... | 68 | +| 6.7.1 | Introduction ..... | 68 | +| 6.7.2 | Functional Description ..... | 68 | +| 6.7.3 | Procedures ..... | 68 | +| 6.7.3.1 | Privacy Setting Update ..... | 68 | +| 6.7.3.2 | Privacy Verification..... | 70 | +| 6.7.3.3 | Service of GMLC and PPR..... | 70 | +| 6.7.4 | Impacts on existing entities and interfaces..... | 70 | +| 6.7.5 | Evaluation..... | 70 | +| 6.8 | Solution 8: slice dependent LMF selection..... | 70 | +| 6.8.1 | Introduction ..... | 70 | +| 6.8.2 | Functional Description ..... | 70 | +| 6.8.3 | Procedures ..... | 70 | +| 6.8.4 | Impacts on existing entities and interfaces..... | 71 | +| 6.8.5 | Evaluation..... | 72 | +| 6.9 | Solution 9: Solution for position service exposure ..... | 72 | +| 6.9.1 | Introduction ..... | 72 | +| 6.9.2 | Functional Description ..... | 72 | +| 6.9.2.1 | Architecture ..... | 72 | +| 6.9.3 | Procedures ..... | 73 | +| 6.9.3.1 | Location Service exposure procedure, non-roaming ..... | 73 | +| 6.9.3.2 | Location Service exposure procedure, roaming ..... | 74 | +| 6.9.3.3 | Optimized Deferred Location Service exposure procedure..... | 76 | +| 6.9.4 | Impacts on existing entities and interfaces..... | 77 | +| 6.9.5 | Evaluation..... | 77 | +| 6.10 | Solution 10: Solution for LDR type service exposure via NEF ..... | 78 | +| 6.10.1 | Introduction ..... | 78 | +| 6.10.2 | Functional Description ..... | 78 | +| 6.10.2.1 | Architecture ..... | 78 | +| 6.10.3 | Procedures ..... | 79 | +| 6.10.3.1 | LDR type service exposure procedure..... | 79 | +| 6.10.3.2 | Application request to update LDR type service..... | 81 | +| 6.10.3.3 | Application request to cancel LDR type service ..... | 82 | +| 6.10.3.4 | UE provides the expected location privacy provisioning to the network ..... | 83 | +| 6.10.4 | Impacts on existing entities and interfaces..... | 83 | +| 6.10.5 | Evaluation..... | 84 | +| 6.11 | Solution 11: Solution for Location Service exposure to NG-RAN..... | 84 | +| 6.11.1 | Introduction ..... | 84 | +| 6.11.2 | Functional Description ..... | 84 | +| 6.11.3 | Procedures ..... | 84 | +| 6.11.3.1 | NG-RAN Location exposure procedure..... | 84 | +| 6.11.4 | Impacts on existing entities and interfaces..... | 85 | +| 6.11.5 | Evaluation..... | 85 | +| 6.12 | Solution 12: LCS support for non-3GPP access ..... | 85 | +| 6.12.1 | Introduction ..... | 85 | +| 6.12.2 | Functional Description ..... | 86 | +| 6.12.2.1 | Architecture ..... | 86 | +| 6.12.2.2 | New Reference points and Service based interfaces ..... | 86 | +| 6.12.3 | Procedures ..... | 87 | +| 6.12.3.1 | 5GC-MT-LR Procedure..... | 87 | +| 6.12.3.2 | 5GC-MO-LR Procedure ..... | 88 | +| 6.12.4 | Impacts on existing entities and interfaces..... | 89 | +| 6.12.4.1 | Impacts to UDM ..... | 89 | + +| | | | +|----------|-----------------------------------------------------------------------------------------------------|-----| +| 6.12.4.2 | Impacts to GMLC ..... | 89 | +| 6.12.4.3 | Impacts to LMF ..... | 89 | +| 6.12.4.4 | Impacts to AMF ..... | 89 | +| 6.12.4.5 | Impacts to N3IWF ..... | 89 | +| 6.12.4.6 | Impacts to UE ..... | 89 | +| 6.12.5 | Evaluation ..... | 89 | +| 6.13 | Solution 13: LCS support for non-3GPP access ..... | 89 | +| 6.13.1 | Introduction ..... | 89 | +| 6.13.2 | Functional Description ..... | 89 | +| 6.13.2.1 | Architecture ..... | 89 | +| 6.13.2.2 | Location information for non-3GPP access ..... | 90 | +| 6.13.3 | Positioning Procedures ..... | 91 | +| 6.13.3.1 | Common Positioning Procedures When UE is served by the Same PLMN ..... | 91 | +| 6.13.3.2 | MT-LR Procedures When UE is served by the Different PLMNs via 3GPP access and Non-3GPP access ..... | 93 | +| 6.13.3.3 | MO-LR Procedures When UE is served by the Different PLMNs via 3GPP access and Non-3GPP access ..... | 96 | +| 6.13.3.4 | NI-LR Procedures When UE is served by the Different PLMNs via 3GPP access and Non-3GPP access ..... | 96 | +| 6.13.4 | Impact on existing entities and interfaces ..... | 96 | +| 6.13.5 | Evaluation ..... | 96 | +| 6.14 | Solution 14: Reuse R15 existing location service architecture for commercial use cases ..... | 97 | +| 6.14.1 | Introduction ..... | 97 | +| 6.14.2 | Functional Description ..... | 97 | +| 6.14.2.1 | Architecture to support Location Services ..... | 97 | +| 6.14.2.2 | Reference point to support Location Services ..... | 99 | +| 6.14.2.3 | Service Based Interfaces to support Location Services ..... | 100 | +| 6.14.2.4 | Network Functions to support Location Services ..... | 100 | +| 6.14.3 | Procedures ..... | 101 | +| 6.14.3.0 | LMF selection ..... | 101 | +| 6.14.3.1 | 5GC-MT-LR Procedure ..... | 101 | +| 6.14.3.2 | 5GC-MO-LR Procedure ..... | 103 | +| 6.14.3.3 | Deferred 5GC-MT-LR Procedure for Periodic, Triggered and UE Available Location Events ..... | 104 | +| 6.14.3.4 | LMF change procedure via serving LMF ..... | 110 | +| 6.14.4 | Impacts on existing entities and interfaces ..... | 111 | +| 6.14.4.1 | Impacts to UDR and UDM ..... | 111 | +| 6.14.4.2 | Impacts to GMLC ..... | 111 | +| 6.14.4.3 | Impacts to UE ..... | 111 | +| 6.14.4.4 | Impacts to AMF ..... | 112 | +| 6.14.4.5 | Impacts to LMF ..... | 112 | +| 6.14.5 | Evaluation ..... | 112 | +| 6.15 | Solution 15: Enhancement to LCS architecture ..... | 112 | +| 6.15.1 | Introduction ..... | 112 | +| 6.15.2 | Functional Description ..... | 112 | +| 6.15.3 | Procedures ..... | 114 | +| 6.15.3.1 | RAN-LMC registration ..... | 114 | +| 6.15.3.2 | LMC performance control ..... | 115 | +| 6.15.4 | Impacts on existing entities and interfaces ..... | 116 | +| 6.15.5 | Evaluation ..... | 116 | +| 6.16 | Solution 16: Solution for position via user plane transmission ..... | 117 | +| 6.16.1 | Introduction ..... | 117 | +| 6.16.2 | Functional Description ..... | 117 | +| 6.16.3 | Procedures ..... | 117 | +| 6.16.3.1 | UE establishes the connection with UCF ..... | 117 | +| 6.16.3.2 | UE initiated position via user plane ..... | 118 | +| 6.16.3.3 | Network initiated position via user plane ..... | 118 | +| 6.16.4 | Impacts on existing entities and interfaces ..... | 119 | +| 6.16.5 | Evaluation ..... | 119 | +| 6.17 | Solution 17: Solution for Flexible and Efficient Periodic and Triggered Location ..... | 119 | +| 6.17.1 | Introduction ..... | 119 | +| 6.17.2 | Functional Description ..... | 120 | +| 6.17.3 | Procedures ..... | 120 | + +| | | | +|----------|------------------------------------------------------------------------------------------------------------------|-----| +| 6.17.3.1 | Generic Procedure..... | 120 | +| 6.17.4 | Impacts on existing entities and interfaces..... | 122 | +| 6.17.5 | Evaluation..... | 122 | +| 6.18 | Solution #18: UDM based Positioning Access selection for LCS service..... | 122 | +| 6.18.1 | Introduction ..... | 122 | +| 6.18.2 | Functional Description ..... | 122 | +| 6.18.3 | Procedures ..... | 123 | +| 6.18.4 | Impacts on existing entities and interfaces..... | 124 | +| 6.18.5 | Evaluation..... | 124 | +| 6.19 | Solution #19: Distribution of Positioning Assistance Information ..... | 124 | +| 6.19.1 | Introduction ..... | 124 | +| 6.19.2 | Functional Description ..... | 124 | +| 6.19.3 | Procedures ..... | 125 | +| 6.19.3.1 | UE Assisted and UE Based Positioning and Assistance Delivery Procedure ..... | 125 | +| 6.19.3.2 | Obtaining Non-UE Associated Network Assistance Data..... | 126 | +| 6.19.3.3 | Broadcasting assistance data for UE assisted or UE based positioning ..... | 127 | +| 6.19.4 | Impacts on existing entities and interfaces..... | 128 | +| 6.19.5 | Evaluation..... | 128 | +| 6.20 | Solution 20: LMF selection in GMLC ..... | 128 | +| 6.20.1 | Introduction ..... | 128 | +| 6.20.2 | Functional Description ..... | 128 | +| 6.20.3 | Procedures ..... | 128 | +| 6.20.3.1 | Procedure for LMF selection in GMLC with MO-LR and NI-LR..... | 128 | +| 6.20.3.2 | Procedure for LMF selection in GMLC with 5GC-MT-LR..... | 129 | +| 6.20.4 | Impacts on existing entities and interfaces..... | 131 | +| 6.20.5 | Evaluation..... | 131 | +| 6.21 | Solution 21: Solution for Low Power Periodic and Triggered Location ..... | 132 | +| 6.21.1 | Introduction ..... | 132 | +| 6.21.2 | Functional Description ..... | 132 | +| 6.21.3 | Procedures ..... | 132 | +| 6.21.3.1 | General..... | 132 | +| 6.21.3.2 | Low Power Periodic and Triggered 5GC-MT-LR Procedure ..... | 132 | +| 6.21.4 | Impacts on existing entities and interfaces..... | 135 | +| 6.21.4.1 | Impacts to LMF and Nlmf SBI..... | 135 | +| 6.21.4.2 | Impacts to UE ..... | 135 | +| 6.21.4.3 | Impacts to AMF and Namf SBI..... | 135 | +| 6.21.4.4 | Impacts to the NG-RAN ..... | 135 | +| 6.22 | Solution 22: LCS continuity Support for N26 based Handover..... | 136 | +| 6.22.1 | Introduction ..... | 136 | +| 6.22.2 | Functional Description ..... | 136 | +| 6.22.3 | Procedures ..... | 136 | +| 6.22.3.1 | LCS support during Handover from 5GS to EPS..... | 136 | +| 6.22.3.2 | LCS support during Handover from EPS to 5GS..... | 138 | +| 6.22.4 | Impacts on existing entities and interfaces..... | 140 | +| 6.22.5 | Evaluation..... | 140 | +| 6.23 | Solution #23: Unified NEF Location Service Exposure ..... | 140 | +| 6.23.1 | Introduction ..... | 140 | +| 6.23.2 | Functional Description ..... | 141 | +| 6.23.3 | Procedures ..... | 141 | +| 6.23.3.1 | Unified Location Service Exposure Procedure..... | 141 | +| 6.23.3.2 | Alternative procedure for NEF to use AMF event exposure service via the UDM..... | 144 | +| 6.23.3.3 | Enhanced NG-RAN Location Reporting Procedure..... | 145 | +| 6.23.4 | Impacts on existing entities and interfaces..... | 146 | +| 6.23.5 | Evaluation..... | 146 | +| 6.24 | Solution #24: GMLC based Positioning Access selection for LCS service ..... | 146 | +| 6.24.1 | Introduction ..... | 146 | +| 6.24.2 | Functional Description ..... | 146 | +| 6.24.3 | Procedures ..... | 147 | +| 6.24.4 | Impacts on existing entities and interfaces..... | 148 | +| 6.24.5 | Evaluation..... | 148 | +| 6.25 | Solution #25: Coordination of Positioning Signalling Transmitted via Control Plane Path and User Plane Path..... | 148 | + +| | | | +|------------|--------------------------------------------------------------------------------------------------|-----| +| 6.25.1 | Introduction ..... | 148 | +| 6.25.2 | Functional Description ..... | 148 | +| 6.25.3 | Procedures ..... | 148 | +| 6.25.4 | Impacts on existing entities and interfaces ..... | 149 | +| 6.25.5 | Evaluation ..... | 149 | +| 6.26 | Solution 26: Local LCS architecture ..... | 149 | +| 6.26.1 | Introduction ..... | 149 | +| 6.26.2 | Functional Description ..... | 150 | +| 6.26.3 | Procedures ..... | 150 | +| 6.26.3.1 | Local LMF registration ..... | 150 | +| 6.26.3.2 | AMF based Local LMF selection ..... | 151 | +| 6.26.4 | Impacts on existing entities and interfaces ..... | 152 | +| 6.26.5 | Evaluation ..... | 152 | +| 6.27 | Solution #27: Bulk operation of LCS service request targeting to multiple UEs ..... | 153 | +| 6.27.1 | Introduction ..... | 153 | +| 6.27.2 | Functional Description ..... | 153 | +| 6.27.2.1 | Option 1: LCS service request stored in the UDR as the subscription data ..... | 153 | +| 6.27.2.2 | Option 2: LCS service request stored in the UDR as the application data ..... | 153 | +| 6.27.3 | Procedures ..... | 153 | +| 6.27.3.1 | Option 1: LCS service request stored in the UDR as the subscription data ..... | 154 | +| 6.27.3.2 | Option 2: LCS service request stored in the UDR as the application data ..... | 155 | +| 6.27.4 | Impacts on existing entities and interfaces ..... | 156 | +| 6.27.4.1 | Impacts to UDR and UDM ..... | 156 | +| 6.27.4.2 | Impacts to GMLC ..... | 156 | +| 6.27.4.3 | Impacts to NEF ..... | 156 | +| 6.27.5 | Evaluation ..... | 156 | +| 6.28 | Solution #28: Enhanced NG-RAN to support high accuracy location estimation ..... | 156 | +| 6.28.1 | Introduction ..... | 156 | +| 6.28.2 | Functional Description ..... | 157 | +| 6.28.3 | Procedures ..... | 157 | +| 6.28.3.1 | 5GC-MT-LR Procedure ..... | 157 | +| 6.28.3.2 | MO-LR Procedure ..... | 157 | +| 6.28.3.3 | 5GC- Deferred 5GC-MT-LR Procedure for Periodic, Triggered and UE Available Location Events ..... | 157 | +| 6.28.3.4 | Location Service Exposure Procedure ..... | 158 | +| 6.28.3.4.1 | Location exposure to AF ..... | 158 | +| 6.28.3.4.2 | NG-RAN being the LCS client ..... | 158 | +| 6.28.4 | Impacts on existing entities and interfaces ..... | 158 | +| 6.28.4.1 | Impacts to NG-RAN node ..... | 158 | +| 6.28.4.2 | Impacts to N2 ..... | 158 | +| 6.28.4.3 | Impacts to AMF ..... | 158 | +| 6.28.5 | Evaluation ..... | 158 | +| 7 | Evaluation ..... | 158 | +| 7.1 | Evaluation of Solutions for Key Issue #4 ..... | 159 | +| 7.2 | Evaluation of Complete E2E Solutions for Key Issue 1 ..... | 159 | +| 7.3 | Evaluation of Architectural Solutions ..... | 159 | +| 7.4 | Evaluation of Solutions for Location Service Exposure ..... | 159 | +| 7.5 | Evaluation of Solutions for Non-3GPP Access ..... | 160 | +| 7.6 | Evaluation of Solutions for Miscellaneous Functional Enhancements ..... | 160 | +| 7.7 | Evaluation of Solutions for Key Issue #9 and #10 ..... | 161 | +| 7.8 | Evaluation of Solutions for Key Issue #3 ..... | 161 | +| 8 | Conclusions ..... | 161 | +| 8.0 | General conclusions ..... | 161 | +| 8.1 | Conclusions of key issue 1 ..... | 161 | +| 8.2 | Conclusion for Key Issue #4 ..... | 162 | +| 8.3 | Conclusion for Key Issue #12 ..... | 162 | +| 8.4 | Conclusion for Key Issues #6 and #8 ..... | 162 | +| 8.5 | Conclusion for Key Issue #7 ..... | 162 | +| 8.6 | Conclusion for Key Issue #9 and #10 ..... | 162 | +| 8.7 | Agreement for Key Issue #14 ..... | 162 | + +| | | | +|-----------------|----------------------------------------------------------|------------| +| 8.8 | Conclusions for Key Issue #3..... | 163 | +| 8.9 | Conclusion for Key Issues 5..... | 163 | +| 8.10 | Conclusions for other Key Issues..... | 163 | +| Annex A: | Supported positioning methods..... | 164 | +| A.1 | Supported positioning methods in EUTRAN Rel-15 ..... | 164 | +| A.2 | Supported positioning methods in NR Rel-15 ..... | 165 | +| Annex B: | Evaluation tables for Key Issues ..... | 167 | +| B.1 | Evaluation table for of Solutions for Key Issue #4..... | 167 | +| B.2 | Evaluation table for of Solutions for Key Issue #7 ..... | 168 | +| B.3 | Evaluation table for Key Issue #3 ..... | 169 | +| Annex C: | Change history..... | 170 | + +--- + +## 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 objectives of this Technical Report are to enhance the service-based architecture used for location services in the 5G system, and corresponding Network Functions (NFs) and procedures, to meet the service requirements defined in, SA WG1 (e.g. TS 22.261 [2] and TS 22.071 [3]), including the consideration of roaming and non-roaming scenarios, and access via 3GPP as well as non-3GPP access technologies (un-trusted, and trusted in TR 23.716 [9]). Of particular consideration is how to support location services in 5GS and EPS interworking scenarios, and in non-3GPP access and 3GPP access interworking scenarios. + +This Technical Report will need to consider related architectures and functions developed in RAN, and implications if any. + +--- + +# 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.261: "Service requirements for next generation new services and markets; Stage 1". +- [3] 3GPP TS 22.071: "Technical Specification Group Systems Aspects; Location Services (LCS)". +- [4] 3GPP TS 23.501: "System Architecture for the 5G System; Stage 2". +- [5] 3GPP TS 23.502: "Procedures for the 5G System; Stage 2". +- [6] 3GPP TS 23.271: "Functional stage 2 description of Location Services (LCS)". +- [7] 3GPP TS 38.305: "NG Radio Access Network (NG-RAN); Stage 2 functional specification of User Equipment (UE) positioning in NG-RAN". +- [8] 3GPP TR 38.913: "Study on scenarios and requirements for next generation access technologies". +- [9] 3GPP TR 23.716: "Study on the Wireless and Wireline Convergence for the 5G system architecture". +- [10] 3GPP TR 22.872: "Study on positioning use cases". +- [11] 3GPP TS 38.455: "NR Positioning Protocol A (NRPPa)". +- [12] 3GPP TS 36.305: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Stage 2 functional specification of User Equipment (UE) positioning in E-UTRAN". +- [13] Open Mobile Alliance, OMA AD SUPL: "Secure User Plane Location Architecture", (
-internal | +| LCS Server in PLMN | Client handling component | Location Client Control Function | LCCF | +| | | Location Client Authorization Function | LCAF | +| | | Location Client Co-ordinate Transformation Function | LCCTF | +| | | Location Client Zone Transformation Function | LCZTF | +| | System handling component | Location System Control Function | LSCF | +| | | Location System Billing Function | LSBF | +| | | Location System Operations Function | LSOF | +| | | Location System Broadcast Function | LSBcF | +| | Subscriber Handling component | Location System Co-ordinate Transformation Function | LSCTF | +| | | Location Subscriber Authorization Function | LSAF | +| | | Location Subscriber Translation Function | LSTF | +| | Positioning component | Location Subscriber Privacy function | LSPF | +| | | Positioning Radio Control Function | PRCF | +| | | Positioning Calculation Function | PCF | +| | | Positioning Signal Measurement Function | PSMF | +| | Context & Data component | Positioning Radio Resource Management | PRRM | +| | | Positioning Assistance Data Storage Function | PADSF | +| | | Positioning Context of UE Storage Function | PCUSF | + +In addition to those functionalities in above table, the AMF should support transport NRPPa messages defined in TS 38.455 [11] between UE and the LMF. + +NOTE 1: The RAN WG may develop new positioning component for NG-RAN. Thus, above table will be updated accordingly. + +In following two clauses, two options for function allocations are described, respectively. + +NOTE 2: Some function block in above table may be associated with each entity, e.g. LSOF. That does not mean each entity will provide the same service. + +NOTE 3: In both options, PCF and PADSF are introduced in NG-RAN at concept level. However, detailed architecture, functionalities, and procedures are under RAN WG remit, and will be updated accordingly. + +### 6.1.2.2 Option A: EPS like allocation + +In this option, + +- The AMF implement all LCS related functionalities in MME (see clause 6.3.13 of TS 23.271 [6]). +- The LMF implement all LCS related functionalities in E-SMLC (see clause 6.3.14 of TS 23.271 [6]). +- The AMF uses UDSF to store UE related positioning context (for how to manage AMF with UDSF, see clause 5.21.2 of TS 23.501 [4]). +- The UDM is enhanced to support Positioning Assistance Data storage, and support assistance data retrieval from other CP NFs. + +Table 6.1.2.2-1 and figure 6.1.2.2-1 show the distribution of LCS functional blocks to 5G network elements and general LCS Logical Architecture for 5G. + +In this option, mapping LCS related procedure defined in TS 23.271 [6] to Service base procedure is needed. + +**Table 6.1.2.2-1: Allocation of LCS functional entities to 5G elements** + +| | UE | RAN | GMLC | AMF | LMF | UDSF | UDM/UDR | PPR | PMD | Client | +|--------------------------------------|----|-----|---------------|-----|-----|------|---------|-----|-----|--------| +| Location client functions | | | | | | | | | | | +| LCF | X | | | X | | | | | | X | +| LCF Internal | | | | | | | | | | | +| Client handling functions | | | | | | | | | | | +| LCCTF | | | X | | | | | | | | +| LCCF | | | X | | | | | | | | +| LCAF | | | X | | | | | | | | +| LCZTF | | | X | | | | | | | | +| System handling functions | | | | | | | | | | | +| LSCF | | | | X | | | | | | | +| LSBF | | | X | X | | | | | | | +| LSOF | X | X | X | X | X | | | | | | +| LSBcF | | X | | | X | | | | | | +| LSCTF | | | X | | | | | | | | +| LIMS-IWF | | | X
(Note 1) | | | | | | | | +| Subscriber handling functions | | | | | | | | | | | +| LSAF | | | X | X | | | | X | | | +| LSPF | | | X | X | | | X | X | | | +| LSTF | | | | | | | | | X | | +| Positioning functions | | | | | | | | | | | +| PRCF | | | | | X | | | | | | +| PCF | X | X | | | X | | | | | | +| PSMF | X | X | | | | | | | | | +| PRRM | | X | | | | | | | | | +| Context & Data component | | | | | | | | | | | +| PADSF | | X | | | | | X | | | | +| PCUSF | | | | | | X | | | | | +| | UE | RAN | GMLC | AMF | LMF | UDSF | UDM/UDR | PPR | PMD | Client | + + + +Figure 6.1.2.2-1: Generic LCS Logical Architecture for 5GC. The diagram shows the logical architecture for 5G Core Network (5G CN) involving various Network Functions (NFs) and their interfaces. On the left, a User Equipment (UE) block contains LCF, PCF, PSMF, and LSOF. It connects via the NR-Uu interface to the NG-RAN block, which contains PCF, LSOF, PADSF, LSBcF, PSMF, and PRRM. The NG-RAN connects via the N2 interface to the 5G CN. Inside the 5G CN, the AMF (Access and Management Function) contains LSAF, LCF, LSOF, LSPF, LSBF, and LSCF. The LMF (Location Management Function) contains PRCF, LSOF, PCF, and LSBcF. The UDM/UDR (Unified Data Management/Unified Data Repository) contains LSPF, PADSF, and PMD. The PMD (Positioning Management Function) contains LSTF, PMD, LSAF, LSPF, and PPR. The UDSF (User Data Storage Function) contains PCUSF and UDSF. The GMLC (Gateway Mobile Location Centre) contains LCCF, LCAF, LSOF, LSBF, LCCTF, LSAF, LSPF, LSCTF, LCZTF, and LIMS-IWF. The GMLC connects to the LRF (Location Retrieval Function) via the Le interface. The LRF connects to the External LCS Client via the Le interface. The Internal LCS Consumer connects to the GMLC via the Nilc interface. The AMF connects to the LMF via the Namf interface. The LMF connects to the UDM/UDR via the Nudm interface. The UDM/UDR connects to the PMD via the Npdm interface. The PMD connects to the PPR via the Nppr interface. The PPR connects to the UDSF via the Nudsf interface. The UDSF connects to the GMLC via the Ngmlc interface. + +**Figure 6.1.2.2-1: Generic LCS Logical Architecture for 5GC** + +**Editors' note:** The detail of services provided by NFs in this option is FFS. + +### 6.1.2.3 Option B: LMF centric allocation + +In this option: + +- The AMF partially implement one LCS related functionalities i.e. LSOF (see clause 5.4.2.3 of TS 23.271 [6]). +- The LMF implement all LCS related functionalities in E-SMLC (see clause 6.3.14 of TS 23.271 [6]) and most of LCS related functionalities in MME. +- The LMF uses UDSF to store UE related positioning context. + +**Editors' note:** The details of how LMF and UDSF interact in scale in and out scenario are FFS. + +- The UDM is enhanced to support Positioning Assistance Data storage, and support assistance data retrieval from other CP NFs. + +Table 6.1.2.3-1 and figure 6.1.2.3-1 show the distribution of LCS functional blocks to 5G network elements and general LCS Logical Architecture for 5G. + +Compared to that of Option A, this option require LMF implement following functionality: LCF, LSCF, LSBF, LSAF and LSPF (those are originally implemented by MME), in addition to all LCS related functionalities in E-SMLC (see clause 6.3.14 of TS 23.271 [6]). + +Table 6.1.2.3-1: Allocation of LCS functional entities to 5G elements + +| | UE | RAN | GMLC | AMF | LMF | UDSF | UDM/UDR | PPR | PMD | Client | +|--------------------------------------|----|-----|---------------|-----|-----|------|---------|-----|-----|--------| +| Location client functions | | | | | | | | | | | +| LCF | X | | | | X | | | | | X | +| LCF Internal | | | | | | | | | | | +| Client handling functions | | | | | | | | | | | +| LCCTF | | | X | | | | | | | | +| LCCF | | | X | | | | | | | | +| LCAF | | | X | | | | | | | | +| LCZTF | | | X | | | | | | | | +| System handling functions | | | | | | | | | | | +| LSCF | | | | | X | | | | | | +| LSBF | | | X | | X | | | | | | +| LSOF | X | X | X | X | X | | | | | | +| LSBcF | | X | | | X | | | | | | +| LSCTF | | | X | | | | | | | | +| LIMS-IWF | | | X
(Note 1) | | | | | | | | +| Subscriber handling functions | | | | | | | | | | | +| LSAF | | | X | | X | | | X | | | +| LSPF | | | X | | X | | X | X | | | +| LSTF | | | | | | | | | X | | +| Positioning functions | | | | | | | | | | | +| PRCF | | | | | X | | | | | | +| PCF | X | X | | | X | | | | | | +| PSMF | X | X | | | | | | | | | +| PRRM | | X | | | | | | | | | +| Context & Data component | | | | | | | | | | | +| PADSF | | X | | | | | X | | | | +| PCUSF | | | | | | X | | | | | +| | UE | RAN | GMLC | AMF | LMF | UDSF | UDM/UDR | PPR | PMD | Client | + + + +The diagram illustrates the Generic LCS Logical Architecture for 5GC. It is divided into three main vertical sections: UE, NG-RAN, and 5GC. + +- UE (User Equipment):** Contains LCF, PCF, PSMF, and LSOF. It connects to the NG-RAN via the NR-Uu interface. +- NG-RAN:** Contains PCF, LSOF, PADSF, LSBcF, PSMF, and PRRM. It connects to the 5GC via the N2 interface. +- 5GC (5G Core Network):** Contains several Network Functions (NFs) and their interfaces: + - LMF (Location Management Function):** Contains PRCF, LSOF, LSAF, LSCF, PCF, LSBcF, LSPF, LSBF, and LCF. It connects to the AMF via the Nlmf interface. + - UDM/UDR (Unified Data Management/Unified Data Repository):** Contains LSPF, PADSF, and UDM/UDR. It connects to the AMF via the Nudm interface. + - AMF (Access and Management Function):** Contains LSOF and AMF. It connects to the UDSF via the Namf interface. + - UDSF (UDSF Function):** Contains PCUSF and UDSF. It connects to the GMLC via the Nudsf interface. + - GMLC (Gateway Mobile Location Centre):** Contains LCCF, LCAF, LSOF, LSBF, LCCTF, LSAF, LSPF, LSCTF, LCZTF, and LIMS-IWF. It connects to the LRF via the Ngmlc interface. + - LRF (Location Retrieval Function):** Connects to the External LCS Client via the Le interface. + - Internal LCS Consumer:** Connects to the GMLC via the Nilc interface. + - External LCS Client:** Connects to the LRF via the Le interface. + +Figure 6.1.2.3-1: Generic LCS Logical Architecture for 5GC. The diagram shows the logical architecture for 5G Core Network (5GC) Location Services (LCS). It includes the User Equipment (UE), NG-RAN, and 5GC components. The UE contains LCF, PCF, PSMF, and LSOF. The NG-RAN contains PCF, LSOF, PADSF, LSBcF, PSMF, and PRRM. The 5GC contains LMF, AMF, UDSF, GMLC, LRF, and various other network functions (NFs) like PCF, LSOF, LSAF, LSCF, LSPF, PADSF, UDM/UDR, PMD, PPR, and Internal LCS Consumer. Interfaces are labeled as NR-Uu, N2, Nlmf, Nudm, Npd, Nppr, Namf, Nudsf, Ngmlc, Nilc, and Le. + +Figure 6.1.2.3-1: Generic LCS Logical Architecture for 5GC + +Editors' note: The detail of services provided by NFs in this option is FFS. + +### 6.1.3 Procedures + +Editor's note: This clause describes high-level procedures and information flows for the solution. + +### 6.1.4 Impacts on existing entities and interfaces + +Editor's note: This clause describes impacts to existing entities and interfaces. + +### 6.1.5 Evaluation + +Editor's note: This clause provides an evaluation of the solution. + +## 6.2 Solution 2: LMF Based Location Solution + +### 6.2.1 Introduction + +The LMF based solution is intended to address or resolve, partly or completely, the following key issues: + +- Key Issue 1: Enhancement to LCS Architecture. +- Key Issue 3: Support of low latency LCS. +- Key Issue 5: Slicing dependent location service. +- Key Issue 6: Scalability. + +- Key Issue 8: Support of IoT UEs. +- Key Issue 12: LCS support for Non-3GPP access. +- Key Issue 15: Location continuity support. + +The LMF based solution may also enable, or be compatible with, other solutions to address or resolve some of the other key issues. + +## 6.2.2 Functional Description + +### 6.2.2.1 Architecture + +The LMF based location solution focuses location support on the LMF and bypasses the AMF except for obtaining UE reachability, status and subscription information and exchanging location related messages with a target UE or NG-RAN. The service based architecture and corresponding reference point architecture for roaming and non-roaming UEs are shown below. + + + +This diagram illustrates the non-roaming reference architecture for the LMF-based solution. At the top, the LMF and UDM are connected via the Nlmf and Nudm interfaces respectively. Below them, the AMF and vGMLC are connected via the Namf and Ngmlc interfaces. The AMF is connected to the (R)AN via the N2 interface, which is in turn connected to the UE. The vGMLC is connected to the LCS Client via the Le interface. + +Figure 6.2.2-1: Non-roaming reference architecture for LMF Based Solution + +Figure 6.2.2-1: Non-roaming reference architecture for LMF Based Solution + + + +This diagram illustrates the roaming reference architecture for the LMF-based solution, divided into VPLMN and HPLMN by a dashed vertical line. In the VPLMN, the UE is connected to the (R)AN, which is connected to the AMF via the N2 interface. The AMF is connected to the LMF via the Namf interface and to the vGMLC via the Ngmlc interface. The LMF is connected to the UDM via the Nlmf interface. In the HPLMN, the UDM is connected to the hGMLC via the Nudm and Ngmlc interfaces. The hGMLC is connected to the LCS Client via the Le interface. + +Figure 6.2.2-2: Roaming reference architecture for LMF Based Solution + +Figure 6.2.2-2: Roaming reference architecture for LMF Based Solution + + + +Figure 6.2.2-3: Non-roaming reference architecture for LMF Based Solution in reference point representation. The diagram shows a UE connected to an (R)AN, which is connected to an AMF. The AMF is connected to an LMF via the NLs\* interface. The LMF is connected to a UDM via the NLg\* interface. The UDM is connected to a GMLC via the NLh interface. The GMLC is connected to an LCS Client via the Le interface. The entire system is labeled 5GC. + +**Figure 6.2.2-3: Non-roaming reference architecture for LMF Based Solution in reference point representation** + + + +Figure 6.2.2-4: Roaming reference architecture for LMF Based Solution in reference point representation. The diagram shows a UE connected to an (R)AN, which is connected to an AMF. The AMF is connected to an LMF via the NLs\* interface. The LMF is connected to a vGMLC via the NLg\* interface. The vGMLC is connected to an hGMLC via the Lr interface. The hGMLC is connected to a UDM via the NLh interface. The UDM is connected to an LCS Client via the Le interface. The system is divided into two domains: VPLMN 5GC (containing UE, (R)AN, AMF, LMF, vGMLC) and HPLMN 5GC (containing UDM, hGMLC, LCS Client). + +**Figure 6.2.2-4: Roaming reference architecture for LMF Based Solution in reference point representation** + +Figure 6.2.2-1 is identical to Figure 4.4.4.1-1 in TS 23.501 [4] except for the removal of the LRF in Figure 6.2.2-1 which is not relevant to commercial location services. Figure 6.2.2-3 is similar to Figure 4.4.4.1-2 in TS 23.501 [4] with the following differences: + +- LRF is removed. +- The NLs interface between the AMF and LMF is replaced by an NLs\* interface which is similar in some respects. +- The NLg interface between an AMF and GMLC is replaced by an NLg\* interface between an LMF and GMLC which can be based on the same protocol. + +## 6.2.2.2 Reference points and Service based interfaces + +For the LMF based solution, reference points not realized by service based interfaces comprise: + +- N1:** Reference point between UE and AMF via NAS. +- N2:** Reference point between NG-RAN and AMF. +- Le:** Reference point between a GMLC and a LCS Client. +- Lr:** Reference point between a VGMLC and HGMLC. + +Reference points realized by service based interfaces comprise: + +- NLg\*:** Reference point between a GMLC and an LMF. +- NLs\*:** Reference point between an AMF and LMF. +- NLh:** Reference point between a GMLC and UDM. + +Service Based Interfaces used by the LMF based solution comprise: + +- Ngmlc:** Service-based interface exhibited by GMLC (not used). + +**Nlmf:** Service-based interface exhibited by LMF. + +**Namf:** Service-based interface exhibited by AMF. + +**Nudm:** Service-based interface exhibited by UDM. + +The LMF based solution uses existing service operations defined in TS 23.502 [5] for the Namf and Nudm service based interfaces. For the Nlmf service based interface, two new service operations are added as shown below. + +**Table 6.2.2.2-1: Nlmf Service Operations** + +| Service Name | Service Operations | Operation Semantics | Example Consumer | Corresponding Service Operations in TS 23.502 [5] | +|----------------------|------------------------------------|---------------------|------------------|---------------------------------------------------| +| Nlmf_ProvideLocation | Obtain UE Location | Request/Response | GMLC | Namf_Location_ProvideLocation | +| Nlmf_EventNotify | Report a UE location related event | Notify | GMLC | Namf_Location_EventNotify | + +The corresponding service operations in TS 23.502 [5] provide a very similar service except that they are provided by an AMF instead of an LMF and are restricted to regulatory rather than commercial location. This would allow the protocol(s) developed at a stage 3 level for the Namf service operations in TS 23.502 [5] to be extended for use with the new LMF service operations. + +The Nlmf\_Location\_DetermineLocation service operation defined in TS 23.502 [5] is not needed for the LMF based solution. + +## 6.2.3 Procedures + +### 6.2.3.1 5GC-MT-LR Procedure + +Figure 6.2.3.1-1 shows a 5GC Mobile Terminated Location Request (5GC-MT-LR) procedure for a roaming UE. A 5GC-MT-LR procedure for a non-roaming UE would comprise a subset of the procedure shown in Figure 6.2.3.1-1. With this procedure: + +- Privacy requirements can be configured in the HGMLC or transferred from the UDM to the HGMLC and are not needed in the AMF. +- AMF support is limited to functions already defined for other NFs, e.g. providing the LMF with UE reachability, status and location information, and providing connectivity access to the UE and NG-RAN. + + + +``` + +sequenceDiagram + participant UE + participant RAN as (R)AN + participant AMF + participant LMF + participant VGMLC + participant UDM + participant HGMLC + participant LCS_Client as LCS Client + + Note right of LCS_Client: Error! No text of specified style in + LCS_Client->>HGMLC: 1. LCS Service Request + HGMLC->>UDM: 2. Nudm_UE ContextManagement_Get Request + UDM-->>HGMLC: 3. Nudm_UE ContextManagement_Get Response + HGMLC->>VGMLC: 4. LCS Service Request + VGMLC->>LMF: 5. Nlmf_ProvideLocation_Request + LMF-->>HGMLC: 6. Nlmf_ProvideLocation_Request + LMF->>AMF: 7. Nlmf_MT_EnableUEReachability_Request + Note left of AMF: 8. Network Triggered Service Request + AMF-->>LMF: 9. Nlmf_MT_EnableUEReachability_Response + LMF-->>UE: 10. Location Notification Invoke + UE-->>LMF: 11. Location Notification Response + LMF->>AMF: 12. Nlmf_EventExposure_Subscribe + AMF-->>LMF: 13. Nlmf_EventExposure_Notify + Note over UE, LMF: 14. UE Positioning + LMF->>VGMLC: 15. Nlmf_ProvideLocation_Response + VGMLC-->>HGMLC: 16. LCS Service Response + HGMLC-->>LMF: 17. Nlmf_ProvideLocation_Response + LMF-->>LCS_Client: 18. LCS Service Response + +``` + +Sequence diagram for 5GC Mobile Terminated Location Request (5GC-MT-LR) for a roaming UE. The diagram shows interactions between UE, (R)AN, AMF, LMF, VGMLC, UDM, HGMLC, and LCS Client. The process involves a location request from the LCS Client to the HGMLC, followed by context management requests to the UDM, then to the VGMLC, LMF, and finally the AMF. The AMF then triggers a network-triggered service request to the UE. The UE responds with location information, which is passed back through the chain to the LCS Client. + +**Figure 6.2.3.1-1: 5GC Mobile Terminated Location Request (5GC-MT-LR) for a roaming UE** + +1. An external LCS client sends a location request to an HGMLC in the HPLMN for the target UE. The HGMLC verifies the authorization of the LCS Client to locate the target UE and UE privacy requirements. + +NOTE 1: The external LCS client may instead be an NF or an AF which accesses the HGMLC via an NEF as described in clause 6.9 for Solution 9. + +2. The HGMLC invokes the Nudm\_UE ContextManagement\_Get service operation towards the home UDM of the target UE with the GPSI or SUPI of the UE. +3. The UDM returns the serving AMF address and possibly a VGMLC address, a current access type, and/or an LMF address in the VPLMN. The UDM may also return subscribed privacy requirements for the target UE - e.g. if not stored in the HGMLC. + +NOTE 2: If the UDM does not return an AMF address, the HGMLC may also query the home HSS of the target UE for a serving MME address as described in clause 9.1.1 of TS 23.271 [6]. The EPC-MT-LR procedure described in clause 9.1.15 of TS 23.271 [6] may then be performed instead of steps 4-18. + +4. If a VGMLC address was not returned in step 3, the HGMLC may use the NRF service in the HPLMN to select an available VGMLC in the VPLMN, based on the VPLMN address contained in the AMF address received in step 3. The HGMLC forwards the location request to the VGMLC and includes the AMF address, the target UE identity (e.g. SUPI), any LMF address received in step 3, any access type received at step 3 and any privacy requirements for the UE. +5. The VGMLC determines an LMF in the VPLMN and invokes the Nlmf\_ProvideLocation Request service operation to forward the location request to the LMF. If the VGMLC and LMF functions are combined, this step may be omitted. + +NOTE 3: The VGMLC may determine an LMF in the following alternative ways: + +- 1) If VGMLCs, LMFs and AMFs are fully interconnected (e.g. via an operator IP intranet), a VGMLC may determine an LMF based on any suitable criteria (e.g. location QoS, type of LCS + +client, VGMLC ID, access type) and independently of the AMF. As one example, a VGMLC could be configured with all LMFs in the VPLMN and could select LMFs on a round robin basis. + +- 2) If an AMF is allowed to use some but not all LMFs in the VPLMN, a VGMLC could be configured with the allowed LMFs for each AMF - and could then select an LMF based on specific criteria (e.g. QoS) or randomly. + - 3) A VGMLC may use the NRF service in the VPLMN to request a set of available LMFs in the VPLMN and may then select one LMF as in (1). Use of the NRF service can support network slicing (e.g. similar to SMF selection in clause 4.3.2.2.3 of TS 23.502 [5]) if the HGMLC is configured with an S-NSSAI or obtains an S-NSSAI from the UDM for the target UE in step 3. + - 4) When a UE registers with the 5GC, the serving AMF could select an LMF (e.g. using the NRF service and an S-NSSAI). The AMF or the LMF (e.g. as described in clause 6.8.3 for Solution 8) can then provide the LMF address to the UDM along with the AMF address. If at a later time the selected LMF is changed, e.g. due to change of UE's AN, the AMF or the LMF updates the UDM accordingly. The UDM can then provide the LMF address in step 3 to the HGMLC which would provide the address to the VGMLC in step 4. This alternative might be supported only for UEs from certain HPLMNs and/or UEs with a subscription to 5GC-MT-LR usage. +6. As an optional optimization, instead of performing steps 4 and 5, if the HGMLC can determine or select the LMF (e.g. based on the VPLMN identity, AMF address, using the NRF service or by receiving an LMF address from the UDM in step 3), the HGMLC may invoke the Nlmf\_ProvideLocation Request service operation to forward the location request directly to the LMF. + +NOTE 2: When this optimization is used, the HGMLC needs to support the Nlmf SBI. Therefore, if the HPLMN operator wishes to avoid support of the Nlmf SBI by combining GMLCs with LMFs, steps 4 and 5 should be used rather than step 6. + +7. The LMF invokes the Namf\_MT\_EnableUEReachability Request service operation towards the serving AMF to verify UE reachability. + +NOTE 3: If the serving AMF is no longer available, the LMF uses the NRF service in the VPLMN to select another AMF from the same AMF set as the previous serving AMF. + +8. If the UE is currently in CM Connected state for 3GPP or non-3GPP access, this step is skipped. Otherwise, if the UE is currently in CM Idle state for 3GPP access but is reachable, the AMF performs a 3GPP network triggered service request in order to place the UE in connected state. +9. The AMF invokes the Namf\_MT\_EnableUEReachability Response service operation towards the LMF to confirm UE reachability. +10. The LMF may notify the UE and verify UE privacy requirements based on any privacy requirements received from the HGMLC in steps 4-6. If this occurs, the LMF sends a supplementary services Location Notification invoke to the UE via the serving AMF using the Namf\_Communication\_N1N2MessageTransfer service operation. + +NOTE 5: Transfer of supplementary services messages and positioning messages between the LMF and UE for steps 10, 11 and 14 may be based on the procedure in clause 4.13.5.4 in TS 23.502 [5] in the case of 3GPP access or may use the procedure summarized in clause 6.13.3 for Solution 13 in the case of non-3GPP access. + +11. The UE notifies the user of the location request and verifies user permission if UE privacy is to be verified. The UE then returns a supplementary services Location Notification response to the LMF indicating whether the user grants or withholds permission for the location request when UE privacy is verified. The supplementary services response is transferred via the serving AMF and delivered to the LMF using an Namf\_Communication\_N1MessageNotify service operation. +12. If the LMF needs to know the current access type(s) (i.e. 3GPP and/or non-3GPP) and any serving cell for the UE prior to performing positioning in step 14 and prefers to obtain this from the serving AMF rather than the UE, NG-RAN or N3IWF (e.g. to reduce latency), the LMF invokes the Namf\_EventExposure\_Subscribe service operation towards the AMF to obtain UE location information and includes the immediate one time notification flag. + +13. The serving AMF returns the UE access type(s) and location information to the LMF (e.g. 3GPP access type and serving cell ID). +14. The LMF may perform one or more of the positioning procedures described in clauses 4.13.5.4, 4.13.5.5 and 4.13.5.6 of TS 23.502 [5] for 3GPP access or the positioning procedures summarized in clause 6.13.3 for Solution 13 for non-3GPP access. In the case of the procedure in clause 4.13.5.4 of TS 23.502 [5] for 3GPP access or step 4d in clause 6.13.3 for Solution 13 for non-3GPP access, the LMF may include a routing identifier identifying the LMF in any positioning message intended for the UE which is sent to the serving AMF (e.g. at step 1 in Figure 4.13.5.4-1 in TS 23.502 [5]), which the AMF can then forward to the UE in the NAS transport message (e.g. at step 3 in Figure 4.13.5.4-1 in TS 23.502 [5]). The LMF determines the UE location using information obtained in this step and/or in step 13. + +NOTE 6: In the event of a change of serving AMF for the UE within the same PLMN and while positioning is in progress, the old AMF can return an error indication to the LMF when the LMF attempts to send a positioning protocol message to the UE, the NG-RAN or the N3IWF. In addition, if the LMF subscribes to event notification from the old AMF for a change of AMF using the AMF event exposure service operation, the old AMF can notify the LMF when a change of AMF occurs. Provided the LMF is able to access the new AMF, the LMF can resume any of steps 10-14 with the new AMF. For positioning in the UE or NG-RAN that is already in progress when a change of AMF occurs, positioning protocol messages can be returned by the UE or NG-RAN to the LMF via the new AMF, since the messages would include a routing identifier indicating the LMF. This will enable a positioning session between the UE and LMF to continue following a change of AMF. + +NOTE 7: In the event of mobility of a target UE from 5GC to EPC, the LMF can subscribe to notification by the old AMF. The LMF can then return any UE location so far obtained or an error indication to the HGMLC at steps 15-17. In the case of an error indication, the HGMLC can repeat steps 2 and 3 to query the UDM and HSS for a new AMF and new MME address. When an MME address is returned by the HSS, the HGMLC can perform an EPC-MT-LR as described in clause 9.1.15 of TS 23.271 [6] to obtain the UE location. + +- 15-18. The LMF returns the location estimate to the LCS client via the VGMLC and/or HGMLC. + +### 6.2.3.2 5GC-MO-LR Procedure + +Figure 6.2.3.2-1 summarizes a 5GC Mobile Originated Location Request (5GC-MO-LR) procedure for a roaming UE. A 5GC-MO-LR procedure for a non-roaming UE would comprise a subset of the procedure shown in Figure 6.2.3.2-1. With this procedure: + +- The LMF and VGMLC can be combined to avoid support of the Nlmf SBI in the VPLMN. +- Subscription to MO-LR support is assumed to be provided to the AMF by the UDM and could be provided to the LMF when the LMF requests UE status information from the AMF. As an alternative, the LMF could query the UDM. +- The LMF is selected by the AMF. + + + +``` + +sequenceDiagram + participant UE + participant (R)AN + participant AMF + participant LMF + participant VGMLC + participant UDM + participant HGMLC + participant LCS Client + + Note left of UE: 1. UE Triggered Service Request + UE->>AMF: 2. NAS Transport (MO-LR Request) + AMF->>LMF: 3. Namf_Communication_N1MessageNotify (MO-LR Request) + LMF->>AMF: 4. Namf_EventExposure_Subscribe + AMF->>LMF: 5. Namf_EventExposure_Notify + Note over UE, LMF: 6. UE Positioning + LMF->>VGMLC: 7. Nlmf_EventNotify + VGMLC->>HGMLC: 8. MO-LR Location Information + HGMLC->>LMF: 9. Nlmf_EventNotify + LMF->>HGMLC: 10. Location Information + HGMLC->>AMF: 11. Namf_Communication_N1N2MessageTransfer (MO-LR Response) + AMF->>UE: 12. NAS Transport (MO-LR Response) + +``` + +Sequence diagram for 5GC Mobile Originated Location Request (5GC-MO-LR) for a roaming UE. The diagram shows interactions between UE, (R)AN, AMF, LMF, VGMLC, UDM, HGMLC, and LCS Client. The process starts with a UE Triggered Service Request (1) from UE to (R)AN. The UE then sends a NAS Transport (MO-LR Request) (2) to the AMF. The AMF sends a Namf\_Communication\_N1MessageNotify (MO-LR Request) (3) to the LMF. The LMF sends a Namf\_EventExposure\_Subscribe (4) to the AMF. The AMF sends a Namf\_EventExposure\_Notify (5) to the LMF. A UE Positioning (6) block follows. The LMF sends a Nlmf\_EventNotify (7) to the VGMLC. The VGMLC sends a MO-LR Location Information (8) to the HGMLC. The HGMLC sends a Nlmf\_EventNotify (9) to the LMF. The LMF sends a Location Information (10) to the HGMLC. The HGMLC sends a Namf\_Communication\_N1N2MessageTransfer (MO-LR Response) (11) to the AMF. Finally, the AMF sends a NAS Transport (MO-LR Response) (12) to the UE. + +**Figure 6.2.3.2-1: 5GC Mobile Originated Location Request (5GC-MO-LR) for a roaming UE** + +1. The UE performs a service request if in idle state. +2. The UE sends a supplementary services MO-LR request to the serving AMF indicating a request for a location estimate, location assistance data or sending of a location estimate to an LCS client via transfer to third party (TTTP). For TTTP, the UE identifies the external LCS client and possibly the HGMLC. The MO-LR is sent inside a NAS transport message. The UE may include a default routing identifier in the NAS transport message indicating that the AMF may select any LMF in the VPLMN. +3. The AMF selects an LMF in the VPLMN based on receiving a default routing identifier in step 2 and invokes the Namf\_Communication\_N1MessageNotify service operation towards this LMF to transfer the MO-LR request. The AMF includes a SUPI for the UE. + +NOTE 1: The AMF may select the LMF using the NRF service and may make use of an S-NSSAI to support network slicing. Alternatively, LMF selection may occur when a UE first registers as described for Solution 8 in clause 6.8, in which case the LMF address may be part of the UE context in the AMF. + +4. The LMF invokes the Namf\_EventExposure\_Subscribe service operation towards the AMF to obtain UE location information and the UE subscription to MO-LR and includes the immediate one time notification flag. +5. The serving AMF returns UE location information to the LMF (e.g. current access types and any serving cell ID) and UE subscription to MO-LR. The LMF verifies that the UE is subscribed to the MO-LR request received in step 3. + +**Editor's note:** It is assumed that the Namf\_EventExposure service operation is extended to allow provision of UE subscription information for an MO-LR. An alternative could be a new service operation. A decision on preferred support is FFS. + +6. If the MO-LR request indicates a request for a location estimate or sending of a location estimate to an LCS client via TTTP, the LMF may perform one or more of the positioning procedures described in clauses 4.13.5.4, 4.13.5.5 and 4.13.5.6 of TS 23.502 [5] in the case of 3GPP access, or the positioning procedures for Solution 13 summarized in clause 6.13.3 in the case of non-3GPP access. The LMF then determines the UE location using information obtained in this step and/or in step 5. If the MO-LR request indicates a request for location assistance data, the LMF performs the positioning procedure described in clause 4.13.5.4 of TS 23.502 [5] in the case of 3GPP access, or the positioning procedure for Solution 13 summarized in clause 6.13.3 in the case of non-3GPP access, to transfer the assistance data to the UE. For procedures involving the UE, the LMF may include a routing identifier identifying the LMF in any positioning message intended for the UE which is sent to the serving AMF (e.g. as at step 1 in Figure 4.13.5.4-1 in TS 23.502 [5]), which the AMF can then forward to the + +UE in the NAS transport message (e.g. as at step 3 in Figure 4.13.5.4-1 in TS 23.502 [5]). If TTTP was not requested in step 2, steps 7-10 are skipped. + +7. The LMF selects a VGMLC in the VPLMN and invokes the Nlmf\_EventNotify service operation towards the VGMLC. The service operation includes the location obtained in step 6, the SUPI for the UE, the LCS client ID and any HGMLC address provided in step 2. This step can be omitted if the LMF and VGMLC functions are combined in the same entity. +8. The VGMLC forwards the location, the UE identity and LCS client identity to the HGMLC. The VGMLC may determine the HGMLC address if not provided in step 7 from the HPLMN identity inferred from the SUPI. +9. As an optional optimization, if the HGMLC address is provided by the UE in step 2 or can be determined by the LMF (e.g. based on the HPLMN identity as inferred from the UE identity), the LMF may invoke the Nlmf\_EventNotify service operation towards the HGMLC. The service operation includes the location obtained in step 6, the SUPI for the UE and the LCS client ID provided in step 2. When step 9 occurs, steps 7 and 8 are omitted. +10. The HGMLC provides the UE location and a UE identity to the external LCS client. +11. The LMF invokes the Namf\_Communication\_NIN2MessageTransfer service operation towards the AMF to send a supplementary services MO-LR response to the AMF confirming completion of the MO-LR request in step 2 and including any location determined in step 6 +12. The AMF forwards the MO-LR response to the UE in a NAS transport message. + +### 6.2.3.3 Periodic and Triggered 5GC-MT-LR Procedure + +Figure 6.2.3.3-1 summarizes a periodic and triggered 5GC-MT-LR procedure for a roaming UE. A periodic and triggered 5GC-MT-LR procedure for a non-roaming UE would comprise a subset of the procedure shown in Figure 6.2.3.3-1. The trigger events may comprise any of: + +- UE available event. +- Area event (UE entering, leaving or remaining with the area). +- Motion event (UE moving by more than a threshold straight line distance from a previous location). + +Only one of these events may be requested by an LCS Client or the UE available event may be combined with either a periodic event or another triggered event. When a UE is already available, a request for the UE available event is equivalent to requesting a current location for the target UE. With this procedure: + +- The LMF and VGMLC can be combined to avoid support of the Nlmf SBI in the VPLMN. +- Privacy requirements can be configured in the HGMLC or transferred from the UDM to the HGMLC and are not needed in the AMF. +- The same LMF may be used for each successive periodic or triggered location fix thereby avoiding overhead to assign and release the LMF for each location and enabling use of information obtained by the LMF for previous location fixes. +- Trigger detection occurs in the UE. + + + +``` + +sequenceDiagram + participant UE + participant RAN as (R)AN + participant AMF + participant LMF + participant VGMLC + participant UDM + participant HGMLC + participant LCS_Client as LCS Client + + Note right of LCS_Client: 1. LCS Service Request + LCS_Client->>HGMLC: 1. LCS Service Request + Note right of HGMLC: 2. Nudm_UE ContextManagement_Get Request + HGMLC->>UDM: 2. Nudm_UE ContextManagement_Get Request + Note right of UDM: 3. Nudm_UE ContextManagement_Get Response + UDM-->>HGMLC: 3. Nudm_UE ContextManagement_Get Response + Note right of HGMLC: 4. LCS Service Request + HGMLC->>VGMLC: 4. LCS Service Request + Note right of VGMLC: 5. Nlmf_ProvideLocation_Request + VGMLC->>LMF: 5. Nlmf_ProvideLocation_Request + Note right of LMF: 6. Nlmf_ProvideLocation_Request + LMF-->>VGMLC: 6. Nlmf_ProvideLocation_Request + Note right of VGMLC: 7. Nlmf_ProvideLocation_Response + VGMLC->>LMF: 7. Nlmf_ProvideLocation_Response + Note right of LMF: 8. LCS Service Response + LMF-->>HGMLC: 8. LCS Service Response + Note right of HGMLC: 9. Nlmf_ProvideLocation_Response + HGMLC-->>VGMLC: 9. Nlmf_ProvideLocation_Response + Note right of VGMLC: 10. LCS Service Response + VGMLC-->>LCS_Client: 10. LCS Service Response + Note right of AMF: 11. Nlmf_MT_EnableUEReachability_Request + AMF->>LMF: 11. Nlmf_MT_EnableUEReachability_Request + Note right of LMF: 12. Network Triggered Service Request + LMF-->>AMF: 12. Network Triggered Service Request + Note right of AMF: 13. Nlmf_MT_EnableUEReachability_Response + AMF-->>LMF: 13. Nlmf_MT_EnableUEReachability_Response + Note right of LMF: 14. Nlmf_EventExposure_Subscribe + LMF-->>AMF: 14. Nlmf_EventExposure_Subscribe + Note right of AMF: 15. Nlmf_EventExposure_Notify + AMF-->>LMF: 15. Nlmf_EventExposure_Notify + Note right of LMF: 16. Location Notification Invoke + LMF-->>UE: 16. Location Notification Invoke + Note right of UE: 17. Location Notification Response + UE-->>LMF: 17. Location Notification Response + Note right of LMF: 18. UE Positioning + LMF-->>AMF: 18. UE Positioning + Note right of AMF: 19. LCS Periodic-Triggered Event Invoke + AMF-->>UE: 19. LCS Periodic-Triggered Event Invoke + Note right of UE: 20. LCS Periodic-Triggered Event Invoke Ack + UE-->>AMF: 20. LCS Periodic-Triggered Event Invoke Ack + Note right of AMF: 21. Nlmf_EventNotify + AMF-->>LMF: 21. Nlmf_EventNotify + Note right of LMF: 22. LCS Service Response + LMF-->>HGMLC: 22. LCS Service Response + Note right of HGMLC: 23. Nlmf_EventNotify + HGMLC-->>VGMLC: 23. Nlmf_EventNotify + Note right of VGMLC: 24. LCS Service Response + VGMLC-->>LCS_Client: 24. LCS Service Response + Note right of UE: 25. Event Detected + UE-->>AMF: 25. Event Detected + Note right of AMF: 26. UE Triggered Service Request + AMF-->>LMF: 26. UE Triggered Service Request + Note right of LMF: 27. MO-LR Request (location estimate) + LMF-->>AMF: 27. MO-LR Request (location estimate) + Note right of AMF: 28. Determine UE Location + AMF-->>UE: 28. Determine UE Location + Note right of UE: 29. MO-LR Response + UE-->>AMF: 29. MO-LR Response + Note right of AMF: 30. Nlmf_EventNotify + AMF-->>LMF: 30. Nlmf_EventNotify + Note right of LMF: 31. LCS Service Response + LMF-->>HGMLC: 31. LCS Service Response + Note right of HGMLC: 32. Nlmf_EventNotify + HGMLC-->>VGMLC: 32. Nlmf_EventNotify + Note right of VGMLC: 33. LCS Services Response + VGMLC-->>LCS_Client: 33. LCS Services Response + Note right of UE: 34. Event Detected + UE-->>AMF: 34. Event Detected + +``` + +Sequence diagram for Deferred 5GC-MT-LR for periodic, triggered and UE available event for a roaming UE. The diagram shows interactions between UE, (R)AN, AMF, LMF, VGMLC, UDM, HGMLC, and LCS Client. The process involves service requests, context management, location provision, and event notifications. + +**Figure 6.2.3.3-1: Deferred 5GC-MT-LR for periodic, triggered and UE available event for a roaming UE** + +1. An external LCS client sends a location request for a periodic and triggered location for a target UE to an HGMLC in the HPLMN for the UE. The location request provides the type of location reporting being requested and associated parameters. For periodic location, the request includes the time interval between successive location reports and the total number of reports. For triggered reporting for an area event, the request includes details of the target area, whether the trigger event to be reported is the UE being inside, entering into or leaving the target area, and whether event reporting shall include UE location estimates. For triggered reporting for the motion event, the request includes a threshold linear distance for triggering a location report and whether event reporting shall include UE location estimates. For the UE available trigger event, no additional parameters are needed. The HGMLC may verify UE privacy requirements. + +NOTE 1: The external LCS client may instead be an NF or an AF which accesses the HGMLC via an NEF as described in clause 6.9 for Solution 9. + +- 2-3. The HGMMLC queries the UDM for the serving AMF address, UE privacy requirements and possibly a VGMLC address, current access type and/or an LMF address in the VPLMN as described for steps 2-3 in Figure 6.2.3.3-1. + +NOTE 2: The HGMMLC may also query the home HSS of the target UE for a serving MME address as described in clause 9.1.1 of TS 23.271 [6]. The deferred EPC-MT-LR procedure for Periodic and Triggered Location described in clause 9.1.19 of TS 23.271 [6] may then be performed instead of steps 4-34 - e.g. if the HSS returns an MME address but the UDM does not return an AMF address. + +- 4-6. The HGMMLC forwards the location request to the LMF via a VGMLC or directly as described for steps 4-6 of Figure 6.2.3.3-1. The HGMMLC includes in the location request the AMF address, the UE identity (e.g. SUPI), the type of location reporting being requested and associated parameters, a reference number to be used to identify later responses, and any privacy requirements for the UE. For area event reporting, the HGMMLC, VGMLC or LMF may convert the target area into an equivalent set of cells or TAs in the VPLMN. LMF selection (if needed) by the VGMLC may be supported as described for step 5 of Figure 6.2.3.1-1. + +- 7-10. If the LMF supports the type of periodic and triggered location requested, the LMF returns an acknowledgment to the LCS client, via the VGMLC and/or HGMMLC, indicating that the request for periodic or triggered location was accepted. + +- 11-13. The LMF verifies UE reachability and that the UE is in a connected state as described for steps 7-9 of Figure 6.2.3.1-1. + +- 14-15. If the UE is not reachable (e.g. is in eDRX or PSM), the LMF invokes the Namf\_EventExposure\_Subscribe service operation towards the AMF in order to be informed by the AMF when the UE again becomes reachable. At that point and if the UE may not yet be in connected state, the LMF may again perform steps 11-13. The LMF may also perform steps 14-15 to obtain the current access type(s) (i.e. 3GPP and/or non-3GPP) and any serving cell ID for the UE from the AMF after the UE becomes reachable as in steps 12-13 of Figure 6.2.3.1-1. + +NOTE 3: In the event of a change of serving AMF for the UE within the same PLMN when the UE becomes reachable, the old AMF can notify the LMF and the LMF can perform steps 14-15 to obtain the current access type(s) (i.e. 3GPP and/or non-3GPP) and any serving cell ID for the UE from the new AMF. + +NOTE 4: In the event of mobility of a target UE from 5GC to EPC when the UE becomes reachable, the old AMF can notify the LMF. The LMF can then return an error indication to the HGMMLC using steps 21-23. The HGMMLC can then repeat steps 2 and 3 to query the UDM and HSS for a new AMF and new MME address. When an MME address is returned by the HSS, the HGMMLC can perform a deferred EPC-MT-LR for Periodic and Triggered Location as described in clause 9.1.19 of TS 23.271 [6]. + +- 16-17. Once the UE is reachable, the LMF may verify UE privacy requirements, based on UE privacy requirements received from the HGMMLC in steps 3-5, via a supplementary services interaction as in steps 10-11 for Figure 6.2.3.3-1. + +18. If triggered location for the UE available event was requested, the LMF performs UE positioning as for step 14 of Figure 6.2.3.1-1. If no other triggered or periodic location reporting was requested, the LMF skips steps 19-20 and 25-34 and performs steps 21-24 to return the UE location to the LCS Client after which the procedure terminates. + +19. If periodic location or triggered location for the area event or motion event was requested, the LMF sends a supplementary services LCS Periodic-Triggered Event Invoke message to the UE via the serving AMF by invoking the Namf\_Communication\_N1N2MessageTransfer service operation. The message carries the location request information received from the VGMLC or HGMMLC, the reference number assigned by the HGMMLC and the HGMMLC address if the same LMF will not be used in step 27. The LMF includes a routing identifier in the Namf\_Communication\_N1N2MessageTransfer service operation indicating whether later trigger event reports (in step 27) are to be sent by the UE to the same LMF. The routing identifier would be transferred to the UE by the serving AMF in a NAS transport message used to convey the LCS Periodic-Triggered Event Invoke to the UE and would identify the LMF when use of the same LMF is required. The routing identifier may otherwise be omitted or set to a default value that indicates any LMF. + +20. If the request in step 19 can be supported, the UE returns an acknowledgment to the LMF. which is transferred via the serving AMF and delivered to the LMF using an Namf\_Communication\_N1MessageNotify service operation. + +- 21-24. The LMF sends a response to the LCS client via the VGMLC and/or HGMLC carrying any location estimate obtained at step 18 for the UE available event. When steps 19-20 were performed, the response also confirms that event reporting for periodic or triggered location was activated in the UE. The VGMLC (if used) and optionally the LMF can then release state information for the periodic and triggered 5GC-MT-LR request. If the LMF indicates in step 19 that the same LMF must be used for later trigger event reports (in step 27), the LMF retains state information for the UE. +25. If steps 19 and 20 are performed, the UE monitors for occurrence of the trigger event requested in step 19 (e.g. a periodic trigger event, an area trigger event or a motion trigger event). When a trigger event is detected, the UE proceeds to step 26. +26. The UE performs a service request if in idle state. +27. The UE sends a supplementary services 5GC-MO-LR request to an LMF which is transferred via the serving AMF and delivered to the LMF using an Namf\_Communication\_N1MessageNotify service operation. The request indicates an event report for a periodic and triggered location request and includes the type of trigger event being reported, the HGMLC address if received at step 19, and the reference number. The request may also include a location estimate if reporting of a location estimate is required. If requested in step 19, the UE may ensure the MO-LR request is routed by the serving AMF to the same LMF that initiated the periodic and triggered location request by including any routing identifier received at step 19. Otherwise, the UE can include a default routing identifier to indicate that the AMF may select any LMF in the VPLMN. +- NOTE 5: Step 27 does not require the same serving AMF as in steps 16-20 so mobility between AMFs is supported. In the event of mobility of a target UE from 5GC to EPC prior to step 26, the UE may report a trigger event detected at step 25 according to steps 13-24 of Figure 9.1.19.1-1 of TS 23.271 [6] if the deferred EPC-MT-LR procedure for Periodic and Triggered Location is supported by both the UE and EPC. +28. If a location estimate was not included in step 27 and if reporting of location estimates was requested at step 5 or step 6, the LMF performs steps 12-14 of Figure 6.2.3.1-1 to obtain a location estimate for the UE. +29. The LMF returns an MO-LR return result to the UE via the serving AMF using the Namf\_Communication\_N1N2MessageTransfer service operation to confirm that an event report will be sent to the LCS client. +30. The LMF selects a VGMLC (which may be different to the VGMLC for steps 3-7) and invokes an Nlmf\_EventNotify service operation towards the VGMLC with an indication of the type of event being reported, the reference number, the H-GMLC address and a location estimate if this was requested and obtained at step 27 or step 28. This step may be omitted if the LMF and VGMLC are combined. +31. The VGMLC forwards the information received in step 30 to the HGMLC. +32. As an optional optimization, steps 30 and 31 are omitted and the LMF instead sends the information in step 30 directly to the HGLMC. +33. The HGMLC uses the reference number received in step 31 or step 32 to identify the periodic and triggered location request received in step 1 and then sends the location estimate and type of trigger event being reported to the external LCS client. +34. The UE continues to monitor for further trigger events and instigates steps 26-33 each time a trigger event is detected. + +#### 6.2.3.4 Optimized Periodic and Triggered 5GC-MT-LR Procedure + +Figure 6.2.3.4-1 summarizes an optimized 5GC-MT-LR procedure for a roaming UE to support periodic and triggered location in the same manner as in Figure 6.2.3.3-1 but with less resource usage and less impact to the UE and LMF. A corresponding optimized procedure for a non-roaming UE would comprise a subset of the procedure shown in Figure 6.2.3.4-1. This procedure has the same characteristics as the procedure in Figure 6.2.3.3-1, but in addition: + +- The same LMF is always used for each successive periodic or triggered location fix thereby avoiding overhead to assign and release the LMF for each location and enabling use of information obtained by the LMF for previous location fixes. +- Support of the supplementary services MO-LR request and response is not needed by the UE or LMF. +- Trigger detection occurs in the UE, in the LMF or in both the UE and LMF. + + + +``` + +sequenceDiagram + participant UE + participant RAN as (R)AN + participant AMF + participant LMF + participant VGMLC + participant UDM + participant HGMLC + participant LCS_Client as LCS Client + + Note over all: 1-18. Steps 1-18 of Figure 6.X.3.3-1 + Note right of LMF: 19. Determine Trigger Detection + Note right of LMF: Trigger Detection by UE + Note right of LMF: Trigger Detection by LMF + + LMF->>UE: 20. Request Periodic-Triggered Positioning + UE-->>LMF: 21. Confirm Periodic-Triggered Positioning + LMF->>VGMLC: 22. Nlmf_EventNotify + VGMLC->>HGMLC: 23. LCS Service Response + LMF-->>HGMLC: 24. Nlmf_EventNotify + HGMLC->>LCS_Client: 25. LCS Service Response + + Note left of LMF: 26. Monitor status and/or location of the UE + Note right of LMF: 27. Event Detected + Note left of UE: 28. Event Detected + Note left of UE: 29. UE Triggered Service Request + UE->>LMF: 30. Positioning Message (event, location information) + + Note right of LMF: 31. Determine UE Location + LMF->>VGMLC: 32. Nlmf_EventNotify + VGMLC->>HGMLC: 33. LCS Service Response + LMF-->>HGMLC: 34. Nlmf_EventNotify + HGMLC->>LCS_Client: 35. LCS Service Response + + Note left of UE: 37. Event Detected + Note right of LMF: 36. Event Detected + +``` + +Sequence diagram for Optimized Periodic and Triggered 5GC-MT-LR for a roaming UE. The diagram shows interactions between UE, (R)AN, AMF, LMF, VGMLC, UDM, HGMLC, and LCS Client. It starts with steps 1-18 from Figure 6.X.3.3-1. The LMF (step 19) determines trigger detection. For UE-based detection (steps 20-21, 28-30), the LMF sends a request (20), UE confirms (21), detects an event (28), sends a service request (29), and a positioning message (30). For LMF-based detection (steps 26-27), the LMF monitors the UE (26) and detects an event (27). Both paths lead to location determination (31) and subsequent notifications (32-35) to the LCS Client via HGMLC and VGMLC. + +**Figure 6.2.3.4-1: Optimized Periodic and Triggered 5GC-MT-LR for a roaming UE** + +1-18. Steps 1 to 18 of Figure 6.2.3.3-1 are performed. + +19. The LMF determines whether to use trigger event detection by the LMF or by the UE - e.g. based on the type of periodic or triggered location being requested, the LMF capabilities, the UE capabilities (if known) and whether the UE employs power saving mode and is currently reachable. For trigger event detection by the LMF, steps 26-27 are performed and steps 20-21 and 28-30 are omitted. For trigger event detection by the UE, steps 20-21 and 28-30 are performed and steps 26-27 are omitted. In some implementations, an LMF may use both types of trigger detection in order to improve trigger detection reliability or if the UE and LMF detect different types of triggers. + +20. For trigger detection by the UE, the LMF sends a positioning protocol (e.g. LPP) message to the UE via the serving AMF using the *Namf\_Communication\_N1N2MessageTransfer* service operation. The LMF includes in the message a request for periodic or triggered location reporting by the UE as determined by the LMF in step 19 and the type of location measurements or location estimate to be provided by the UE for location reporting in step 30. The LMF also includes a routing identifier identifying the LMF in the *Namf\_Communication\_N1N2MessageTransfer* service operation which is transferred to the UE by the AMF. + +21. If the request in step 20 can be supported, the UE returns an acknowledgment to the LMF in a positioning protocol (e.g. LPP) message, which is transferred via the serving AMF and delivered to the LMF using an *Namf\_Communication\_N1MessageNotify* service operation. + +22-25. Steps 21-24 of Figure 6.2.3.3-1 are performed to confirm that event reporting for periodic or triggered location was activated in the LMF and/or UE and to return any location estimate for the UE available event obtained at step 18 if the UE available event was requested at step 5 or step 6. + +26. For trigger detection by the LMF, the LMF may monitor the status and/or location of the UE by periodically querying the AMF for new UE status and location information and/or subscribing to location event reporting from the AMF such as for a change of access type, cell ID or TA. When periodic location of the UE was requested in step 5 or step 6, step 26 may not be needed. +27. The LMF uses the information in step 26 or other information (e.g. the current time) to detect when a trigger event has occurred. When a trigger event is detected the LMF proceeds to step 31. +28. For trigger event detection by the UE, the UE monitors for occurrence of the trigger event requested in step 20. The monitoring may occur while the UE is in idle state and/or while the UE is unreachable from the network (e.g. with eDRX or PSM). The UE may also (e.g. periodically) request assistance data from the LMF to help determine a location, if needed to detect a trigger event. When a trigger event is detected, the UE proceeds to step 29. +29. The UE performs a service request if in idle state. +30. The UE sends a positioning protocol (e.g. LPP) message to the LMF which is transferred via the serving AMF and delivered to the LMF using an Namf\_Communication\_N1MessageNotify service operation. The request may indicate the type of event being reported and includes any location information (e.g. location measurements or a location estimate) that were requested in step 20. The UE includes the routing identifier received in step 20 to ensure the positioning protocol message is sent to the same LMF which instigated the periodic and triggered location request in step 20. +31. If inclusion of a location estimate in event reports was requested in step 5 or step 6, the LMF determines a location estimate for the UE based on any location measurements or location estimate received in step 30 in the case of UE trigger event detection or based on UE status or location information obtained in step 26 in the case of LMF trigger event detection. If necessary (e.g. to obtain a more accurate location estimate), the LMF may perform UE positioning as for step 14 of Figure 6.2.3.1-1. +- 32-35. Steps 30-33 of Figure 6.2.3.3-1 are performed to return an indication of the trigger event to the external client and a location estimate if this was requested. +36. For trigger event detection by the LMF, the LMF continues to monitor for and detect further trigger events as in steps 26-27 and instigates steps 31-35 each time a trigger event is detected. +37. For trigger event detection by the UE, the UE continues to monitor for and detect further trigger events as in step 28 and instigates steps 29-35 each time a trigger event is detected. + +### 6.2.3.5 Low Power Periodic and Triggered 5GC-MT-LR Procedure + +Figure 6.2.3.5-1 summarizes a low power variant of the optimized 5GC-MT-LR procedure in clause 6.2.3.4 for a roaming UE to support periodic and triggered location. A corresponding procedure for a non-roaming UE would comprise a subset of the procedure shown in Figure 6.2.3.5-1. This procedure has the same characteristics as the procedure in Figure 6.2.3.4-1, but in addition: + +- The UE is enabled to report the occurrence of trigger events and provide associated location information using connectionless transfer. +- Location determination and UE authentication can occur in non-real time in the LMF. +- Location reports from multiple UEs can be batched by the NG-RAN or N3IWF to the LMF to reduce signalling overhead. +- Transfer of location reports can be prioritized according to QoS requirements. +- The option of employing trigger detection in the LMF is not used. + + + +Sequence diagram for Low Power Periodic and Triggered 5GC-MT-LR for a roaming UE. The diagram shows interactions between UE, (R)AN, AMF, LMF, VGMLC, UDM, HGMLC, and LCS Client. It starts with steps 1-18 from Figure 6.X.3.3-1. Step 19: UE sends 'Request Periodic-Triggered Positioning' to LMF. Step 20: LMF sends 'Confirm Periodic-Triggered Positioning' to UE. Step 21: LMF sends 'Nlmf\_EventNotify' to VGMLC. Step 22: VGMLC sends 'LCS Service Response' to HGMLC. Step 23: LMF sends 'Nlmf\_EventNotify' to HGMLC. Step 24: HGMLC sends 'LCS Service Response' to LCS Client. Step 25: UE detects an event. Step 26: UE determines reporting mode. Step 27: UE reports using a NAS Signalling Connection. Step 28: UE sets up a signalling channel. Step 29: UE sends 'Positioning Message (event, location information)' to (R)AN. Step 30: UE releases the signalling channel. Step 31: (R)AN sends 'N2 Transport (network positioning message)' to AMF. Step 32: AMF sends 'Namf\_Communication\_N2InfoNotify (network positioning message)' to LMF. Step 33: LMF authenticates UE and determines location. Step 34: LMF sends 'Nlmf\_EventNotify' to VGMLC. Step 35: VGMLC sends 'LCS Service Response' to HGMLC. Step 36: LMF sends 'Nlmf\_EventNotify' to HGMLC. Step 37: HGMLC sends 'LCS Service Response' to LCS Client. Step 38: UE detects another event. A dashed box labeled 'Reporting using connectionless transfer via NG-RAN' encloses steps 28-33. + +**Figure 6.2.3.5-1: Low Power Periodic and Triggered 5GC-MT-LR for a roaming UE** + +1-18. Steps 1 to 18 of Figure 6.2.3.3-1 are performed. + +19. Step 20 of Figure 6.2.3.4-1 is performed. In addition, the LMF includes in the request for periodic or triggered location reporting a request for the UE to send event reports using connectionless transfer via NG-RAN and includes one or more UE IDs for connectionless reporting, ciphering information, a priority indication and criteria for reporting using connectionless transfer versus a NAS signalling connection. + +20. If the request in step 19 can be supported, the UE returns an acknowledgment to the LMF in a positioning protocol (e.g. LPP) message, which is transferred via the serving AMF and delivered to the LMF using an *Namf\_Communication\_N1MessageNotify* service operation. The UE indicates in the acknowledgment whether sending event reports using connectionless transfer is supported in addition to sending using a NAS signalling connection. + +21-24. Steps 21-24 of Figure 6.2.3.3-1 are performed to confirm that event reporting for periodic or triggered location was activated in the UE and to return any location estimate for the UE available event obtained at step 18 if the UE available event was requested at step 5 or step 6. + +25. The UE monitors for occurrence of the trigger event requested in step 19. The monitoring may occur while the UE is in idle state and/or while the UE is unreachable from the network (e.g. with eDRX or PSM). The UE may also (e.g. periodically) request assistance data from the LMF to help determine a location, if needed to detect a trigger event. When a trigger event is detected, the UE proceeds to step 26. + +26. The UE determines based on the criteria received in step 19 whether to report the trigger event using connectionless transfer or a NAS signalling connection. If the UE is already in connected state or can only access + +the 5GC via a type of RAN node which does not support connectionless transfer, the UE determines to use a NAS signalling connection. + +27. If the UE determines to use a NAS signalling connection at step 26, the UE performs steps 29-31 of Figure 6.2.3.4-1. The UE then skips steps 28-33. +28. If the UE determines to use connectionless transfer at step 26, the UE obtains any location measurements or location estimate requested in step 19. If the UE is using 3GPP access, the UE determines a suitable temporary serving cell and requests and obtains a signalling channel with an associated RAN node in NG-RAN. +29. The UE sends a positioning message to a RAN node for 3GPP access or an N3IWF for non-3GPP access. The positioning message includes the routing identifier for the LMF received in step 19, the UE ID or one of the UE IDs received in step 19, an authentication code to authenticate the UE ID and the priority indication received at step 19. The positioning message also includes a positioning protocol (e.g. LPP) message which includes any location measurements or location estimate obtained in step 28 and may identify the type of event being reported. The positioning protocol message may be ciphered using the ciphering information received at step 19. Other content of the positioning message is not ciphered. +30. The UE and the RAN node release the signalling channel in the case of 3GPP access. + +**Editor's note:** Details of how a signalling channel would be setup in step 28, used to transfer a positioning message in step 29 and released in step 30 would be for RAN to determine and are outside the scope of the study in this TR. Details on authentication of the UE ID would be for SA WG3 to approve or determine. + +31. For 3GPP access, the RAN node may obtain uplink location measurements of UE signalling received at step 28 and/or step 29. The RAN node sends a network positioning message included in an N2 Transport message to an AMF. The network positioning message includes any uplink location measurements obtained by the RAN node and the positioning protocol message, the UE ID, the authentication code and the priority indication received at step 29. The RAN node shall also include the routing identifier for the LMF received at step 29 in the N2 Transport message. The RAN node may use the priority indication to expedite sending of the network positioning message and/or to include information for additional UEs related to the same LMF in the same network positioning message. Any information for additional UEs would be treated and processed separately by the LMF. + +**Editor's note:** The RAN node may use security mechanism defined by SA WG3 for the connectionless transfer to protect the system. + +32. The AMF invokes the Namf\_Communication\_N2InfoNotify service operation towards the LMF indicated by the routing identifier received in step 31. The service operation includes the network positioning message received in step 31. +33. The LMF identifies the UE using the UE ID in the network positioning message and authenticates the UE ID using the authentication code in the network positioning message. The LMF then decipheres the positioning protocol message in the network positioning message if this was ciphered. If inclusion of a location estimate in event reports was requested in step 5 or step 6, the LMF uses any uplink location measurements included in the network positioning messages and any location measurements or location estimate included in the positioning protocol message to determine or verify a location estimate for the UE. The LMF may use the priority indication in the network positioning message to expedite or retard processing of the network positioning message at step 33. +- 34-37. Steps 30-33 of Figure 6.2.3.3-1 are performed to return an indication of the trigger event to the external client and a location estimate if this was requested. +38. The UE continues to monitor for and detect further trigger events as in step 25 and instigates steps 26-37 each time a trigger event is detected. + +## 6.2.4 Compatibility with the Location Solution for regulatory services in Release 15 + +### 6.2.4.1 Architectural Compatibility + +Figures 6.2.4.1-1 and 6.2.4.1-2 show service based and reference point representations, respectively, for the non-roaming architecture for the LMF based solution from Figures 6.2.2-1 and 6.2.2-2, respectively. The figures also show the differences to the non-roaming architecture for the location solution for Release 15 in Figures 4.4.4.1-1 and 4.4.4.1-2 in TS 23.501 [4]. The differences are highlighted by showing NFs and reference points which are present in the Release 15 solution but not in the LMF based solution using dashed lines and by showing NFs and reference points present for the LMF based solution but not Release 15 solution using dotted lines. + + + +Figure 6.2.4.1-1: Non-roaming reference architecture for LMF Based Solution versus Rel-15 Location Solution. This service-based interface diagram shows the following components and connections: UE connected to NG-RAN; NG-RAN connected to AMF via N2; AMF connected to LMF via N1; AMF connected to vGMLC via Namf; vGMLC connected to UDM via Ngmlc; vGMLC connected to LCS Client via Le; vGMLC connected to LRF via Le; LMF connected to UDM via Nlmf. The LRF and its associated Le reference point are shown with dashed lines, indicating they are present for Rel-15 location but not for the LMF Based location solution. + +**Figure 6.2.4.1-1: Non-roaming reference architecture for LMF Based Solution versus Rel-15 Location Solution** + + + +Figure 6.2.4.1-2: Non-roaming reference architecture for LMF Based Solution versus Rel-15 Location Solution in reference point representation. This reference point diagram shows the following components and connections: UE connected to NG RAN via N1; NG RAN connected to AMF via N2; AMF connected to LMF via NLs; AMF connected to GMLC via NLg; GMLC connected to UDM via NLh; GMLC connected to External Client via Le; GMLC connected to LRF via Le; LMF connected to GMLC via NLg\*. The LRF and its associated Le reference point are shown with dashed lines (present for Rel-15 location but not LMF Based location). The NLg\* reference point between AMF and GMLC is shown with dotted lines (present for LMF Based location but not Rel-15 location). The NLg reference point between AMF and GMLC is shown with dashed lines (present for Rel-15 location but not LMF Based location). + +**Figure 6.2.4.1-2: Non-roaming reference architecture for LMF Based Solution versus Rel-15 Location Solution in reference point representation** + +Figures 6.2.4.1-1 and 6.2.4.1-2 show that there are only two major differences. First, an LRF is present for the Rel-15 solution but absent for the LMF based solution. As the LRF provides support for regulatory location services but not commercial location services (e.g. as described in TS 23.167 [17]), it is not needed for commercial location support by the LMF based solution. The second difference concerns the replacement of the NLg reference point between the GMLC and AMF in the location solution in Rel-15 by an NLg\* reference point between the GMLC and LMF in the LMF based location solution. The consequences of this are described further down. + +Apart from these differences, the Rel-15 location solution and the LMF based location solution use the same set of NFs and the same set of reference points. In a PLMN, in which both solutions were present, the non-roaming architecture would be as shown in Figures 6.2.4.1-1 and 6.2.4.1-2 with all NFs and all reference points in each figure being present. This illustrates how both solutions may coexist in the same PLMN. The coexistence can be associated with a set of procedures and signalling supported by the common NFs (GMLC, AMF, LMF, NG-RAN and UE) for regulatory + +location as defined in Rel-15 and another set of procedures and signalling for commercial location as supported by these common NFs for the LMF based solution. + +#### 6.2.4.2 Compatibility on the N1 Reference Point + +The description of the procedures for the LMF based solution in clause 6.2.3 shows that AMF service operations defined for Rel-15 can be used to support all communication between an LMF and UE for both supplementary services and positioning for the LMF based location solution. Usage of AMF service operations in Rel-15 to support supplementary services occurs in steps 10 and 11 of Figure 6.2.3.1-1, steps 2, 3, 11 and 12 of Figure 6.2.3.2-1, steps 16, 17, 19, 20, 27 and 29 of Figure 6.2.3.3-1, steps 16 and 17 of Figure 6.2.3.4-1 and steps 16, 17, 19 and 20 of Figure 6.2.3.5-1. Transfer of a supplementary services message from an LMF to a UE in these steps is based on Rel-15 support for NAS transport message transfer from an AMF to the UE. Transfer of a supplementary services message from a UE to an LMF is also based on NAS transport message transfer to an AMF and makes use of the routing identifier added for positioning message transfer in clause 4.13.5.4 of TS 23.502 [5] to identify a destination LMF. The only departure from Rel-15 is to introduce a "default routing identifier" which is used to route to any LMF, as selected by an AMF, when transferring an MO-LR request from a UE where there is no preassigned LMF (e.g. as for steps 2 and 3 of Figure 6.2.3.2-1 and step 27 of Figure 6.2.3.3-1). This would be a new enhancement but can be backward compatible with a Release 15 UE by defining a default routing identifier which can be configured in later UEs and ensuring that the default routing identifier is never assigned to a particular LMF in any PLMN. + +Transfer of positioning messages between an LMF and UE (e.g. as at step 14 of Figure 6.2.3.1-1, step 6 of Figure 6.2.3.2-1, step 18 of Figure 6.2.3.3-1, steps 20, 21, 30 and 31 of Figure 6.2.3.4-1) uses the same transfer procedures as in Rel-15 as described in clause 4.13.5.4 of TS 23.502 [5], which are based on Namf communication service operations using NAS transport messages. + +With the exception of the default routing identifier, the LMF based solution introduces no new changes to the N1 reference point and thus could be used with a legacy UE from Rel-15 for location procedures (e.g. 5GC-MT-LR without UE privacy notification) which do not demand new UE functions. + +#### 6.2.4.3 Compatibility on the N2 Reference Point + +Use of the N2 interface to support message transfer between a UE and LMF for the LMF based location solution was described on clause 6.2.4.2 and did not result in any new impacts to the N2 reference point. + +The N2 reference point is also used by both the location solution in Release 15 and the LMF based location solution to transfer positioning messages between an LMF and NG-RAN node to support network assisted positioning and non-UE associated network assistance data. This occurs for the LMF based solution in step 14 of Figure 6.2.3.1-1, step 6 of Figure 6.2.3.2-1, steps 18 and 28 of Figure 6.2.3.3-1, steps 18 and 31 of Figure 6.2.3.4-1 and steps 18, 31 and 32 of Figure 6.2.3.5-1. Message transfer for each of these steps uses AMF service operations and N2 transport operations from Rel-15, the same as the location solution in Rel-15 as described in clauses 4.13.5.5 and 4.13.5.6 in TS 23.502 [5]. There is thus no new impact to the N2 reference point. + +#### 6.2.4.4 Compatibility on the NLs Reference Point + +For the location solution in Release 15, the NLs reference point supports the following LMF services and service operations as defined in clause 5.2.15 of TS 23.502 [5] which are used by a consumer AMF for the Release 15 location solution. + +**Table 6.2.4.4-1: LMF Services consumed by an AMF** + +| Service Name | Service Operations | Operation Semantics | Release 15 Location Consumer | LMF Based Solution Consumer | +|---------------|--------------------|---------------------|------------------------------|-----------------------------| +| Nlmf_Location | DetermineLocation | Request/Response | AMF | None | + +The services and service operations in Table 6.2.4.4-1 are not used by the LMF based solution nor is any other equivalent service needed on any other reference point. Thus, this portion of the location solution in Rel-15 does not need to be replicated in any way for the LMF based solution and can be used by a PLMN that supports both solutions for regulatory location but not commercial location. + +The NLs reference point also supports the following AMF services and service operations as defined in clause 5.2.2 of 23.502 [5] which are used by a consumer LMF for both the Release 15 location solution and the LMF based location solution. + +**Table 6.2.4.4-2: AMF Services Consumed by an LMF** + +| Service Name | Service Operations | Operation Semantic | Rel-15 Location Consumer | LMF based solution consumer | +|--------------------|----------------------|--------------------|--------------------------|-----------------------------| +| Namf_Communication | N1MessageNotify | Subscribe / Notify | LMF | LMF | +| | N1MessageSubscribe | | note 1 | note 1 | +| | N1MessageUnSubscribe | | note 1 | note 1 | +| | N1N2MessageTransfer | Request/ Response | LMF | LMF | +| | N2InfoSubscribe | Subscribe / Notify | note 1 | note 1 | +| | N2InfoUnSubscribe | | note 1 | note 1 | +| | N2InfoNotify | | LMF | LMF | +| Namf_EventExposure | Subscribe | Subscribe / Notify | None | LMF | +| | Unsubscribe | Subscribe / Notify | None | note 1 | +| | Notify | Subscribe / Notify | None | LMF | +| Namf_MT | EnableUEReachability | Request/Response | None | LMF | + +NOTE 1: Usage of these service operations by a consumer LMF is not defined but could possibly occur as part of implementation. + +The AMF service operations used for both Release 15 location and the LMF based location solution provide transfer of positioning messages and, for the LMF based solution, supplementary services messages, between an LMF and a UE or NG-RAN node. Except for use of a default routing identifier as discussed in clause 6.2.4.2, the usage of these service operations is the same for both solutions. + +The additional AMF based service operations used by the LMF based solution but not the location solution in Release 15 that are shown in Table 6.2.4.4-2 enable an LMF to request an AMF to enable UE reachability and to subscribe to immediate or later notification of UE reachability and current serving cell ID. The Namf\_EventExposure service operation also enables provision of information regarding UE subscription to MO-LR service as described for steps 4 and 5 of Figure 6.2.3.2-1. Alternatively, a new AMF (or possibly UDM) service operation might be defined to enable an LMF to request and obtain this information. This would be a new impact to an AMF (or UDM) and LMF. + +## 6.2.4.5 Compatibility on the NLg and NLg\* Reference Points + +For the location solution in Release 15, the NLg reference point supports the following AMF services and service operations as defined in clause 5.2.15 of TS 23.502 [5] which are used by a consumer GMLC. + +**Table 6.2.4.5-1: AMF Services consumed by a GMLC in Release 15** + +| Service Name | Service Operations | Operation Semantic | Rel-15 Location Consumer | +|---------------|--------------------|--------------------|--------------------------| +| Namf_Location | ProvideLocation | Request/Response | GMLC | +| | EventNotify | Notify | GMLC | + +For the LMF based location solution, the NLg\* reference point supports the following LMF services and service operations as defined in clause 6.2.2.2 which are used by a consumer GMLC. + +**Table 6.2.4.5-2: LMF Services consumed by a GMLC for the LMF based solution** + +| Service Name | Service Operations | Operation Semantics | LMF based solution consumer | +|----------------------|------------------------------------|---------------------|-----------------------------| +| Nlmf_ProvideLocation | Obtain UE Location | Request/Response | GMLC | +| Nlmf_EventNotify | Report a UE location related event | Notify | GMLC | + +The Namf\_Location\_ProvideLocation service operation in Release 15 corresponds to the Nlmf\_ProvideLocation service operation for the LMF based solution. Similarly, the Namf\_Location\_EventNotify service operation in Release 15 corresponds to the Nlmf\_EventNotify service operation for the LMF based solution. The main differences between these corresponding service operations are as follows: + +- The service operations are provided by an AMF in Release 15 and by an LMF for the LMF based solution. +- The service operations support access to regulatory location services in Release 15 and to commercial location services for the LMF based solution. + +The first difference transfers functional support from an AMF in Release 15 to an LMF for the LMF based solution. For a PLMN already supporting regulatory location services, this would increase LMF impacts but not AMF impacts. For a PLMN supporting commercial location services only, this would avoid new AMF impact at the expense of location impact to an LMF. + +The second difference would be associated with different message content at stage 3 and different procedures for supporting the service operations at a GMLC. The same type of difference occurs for support of location for regulatory services and commercial based services for EPS with regard to the Provide-Location-Request/Answer and Location-Report-Request/Answer Diameter commands for the MME-GMLC SLg interface defined in TS 29.172 [18]. In the case of EPS, a common protocol is used for both types of location although the message content and procedures are partly different. This suggests that the protocols defined to support the service operations in Table 6.2.4.5-1 for Release 15 in TS 29.518 [19] might be enhanced to support the service operations in Table 6.2.4.5-2 for the LMF based solution which would reduce stage 3 standardization. As an alternative, a new protocol might be defined for the NLg\* reference point for the LMF based solution which reuses parameters defined in TS 29.518 [19] for the NLg reference point. The extension of the protocol in TS 29.518 [19] for the NLg reference point or, at least, the reuse of existing parameters for this protocol would reduce standardization impacts for the NLg\* interface (compared to defining a new protocol from scratch) and would reduce impacts to support this protocol in any GMLC that already supports the location solution in Release 15. + +#### 6.2.4.6 Compatibility on the NLh Reference Point + +For the location solution in Release 15, the NLh reference point supports the following UDM services and service operations as defined in clause 5.2.3 of TS 23.502 [5] which are used by a consumer GMLC for the Release 15 location solution and for the LMF based location solution: + +**Table 6.2.4.6-1: NF services provided by UDM** + +| NF service | Service Operations | Operation Semantics | Rel-15 Location Consumer | LMF based solution consumer | +|------------------------------|--------------------|---------------------|--------------------------|-----------------------------| +| UE Context Management (UECM) | Get | Request/Response | GMLC | GMLC | + +For the location solution in Release 15, this service operation is invoked by a GMLC using the GPSI or SUPI of the target UE and returns the serving AMF address. For the LMF based solution, the service operation is invoked by a GMLC using the GPSI or SUPI of the target UE and returns the serving AMF address and optionally a VGMLC address, an LMF address and/or subscribed privacy requirements. The service operation in Release 15 would thus be extended to support the LMF based solution. + +### 6.2.5 Impacts on existing entities and interfaces + +Impacts to existing entities and interfaces are described here in terms of the additional impacts or reduced impacts compared to the 5GC location solution for regulatory services defined in Release 15. Impacts are categorized as follows: + +- New An all new impact with no counterpart in Release 15 and no other existing impact. +- Same The same impact as in Release 15. +- Same +/- X The same impact as in Release 15 plus or minus X. +- Commercial Impact solely due to commercial location (e.g. privacy, LCS Client identification). +- Existing An impact that already exists in Rel-15 for EPS and is the same impact for 5GS. + +#### 6.2.5.1 Impacts to UDM and Nudm SBI + +The Nudm\_UE ContextManagement service operation defined in TS 23.502 [5] in Release 15 for use by as GMLC in obtaining the serving AMF address for a 5GC-MT-LR can be reused by the LMF Based solution without significant change. The only difference to Release 15 would be to enable the service operation to be used by an GMLC in a different PLMN than the HPLMN to support roaming scenarios. + +UDM impact: same. + +Nudm SBI impact: same + inter-PLMN support. + +When slicing dependent location service is supported, the Nudm SBI needs to support the providing of S-NSSAI in the Nudm\_CM\_Get response. + +## 6.2.5.2 Impacts to GMLC and Ngmlc SBI + +No Ngmlc SBI is defined in Release 15 and none is needed for the LMF Based solution. + +However, the GMLC is a consumer of several SBIs and performs certain other actions associated with receiving a location request from another GMLC or LCS Client, sending a location request to another GMLC or LMF and selecting an LMF. The impacts are summarized in Tables 6.2.5.2-1 and 6.2.5.2-2 for a VGMLC and HGMLC, respectively, for the different location procedures described in clause 6.2.3 and are compared with corresponding GMLC impacts defined in Release 15. In a non-roaming scenario, a GMLC would have both the VGMLC and HGMLC impacts except for the GMLC-GMLC interaction which would not be an impact. + +**Table 6.2.5.2-1: VGMLC Impacts for the LMF Based Solution** + +| Procedure | Description | Corresponding or Similar Rel-15 Impact (if any) | +|-------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 5GC-MT-LR
Periodic Triggered 5GC-MT-LR |
Receive a location request for a target UE from an HGMLC and return a location response
Impact: new
Select an LMF in the VPLMN
Impact: new
Obtain a location estimate for a target UE from an LMF using the Nlmf ProvideLocation service operation.
The Nlmf ProvideLocation service operation can be an extension of the Namf Location ProvideLocation service operation at a stage 3 level with additional support for commercial location.
Impact: Same + commercial
| None | +| 5GC-MO-LRTTTP |
Receive a location estimate for a UE from an LMF using the Nlmf EventNotify service operation and transfer to an HGMLC.
The Nlmf EventNotify service operation can be an extension of the Namf ProvideLocation service operation at a stage 3 level.
Impact: same + commercial
| Receive a location estimate for a UE for an emergency services call from an AMF using the Namf Location EventNotify service operation and provide to a PSAP. | +| Periodic / Triggered 5GC-MT-LR |Receive periodic (or triggered) location responses from an LMF using the LMF EventNotify service operation and transfer to an HGMLC
The Nlmf ProvideLocation service operation can be an extension of the Namf Location ProvideLocation service operation at a stage 3 level with additional support for commercial location and event triggers.
Impact: Same + commercial + event triggers
| Receive a location estimate for a UE for an emergency services call from an AMF using the Namf Location EventNotify service operation and provide to a PSAP. | + +**Table 6.2.5.2-3: HGMLC Impacts for the LMF Based Solution** + +| Procedure | Description | Corresponding or Similar Rel-15 Impact (if any) | +|-------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------| +| 5GC-MT-LRPeriodic / Triggered 5GC-MT-LR | Receive a location request for a target UE from an LCS Client and return a location response
Impact: same + commercial | Receive a location request for a target UE from an LCS Client for regulatory services and return a location response. | +| | Verify LCS Client authorization and target UE privacy requirements.
Impact: new | None | +| | Query UDM for serving AMF address and optionally LMF address and VGMLC address
Impact: same + LMF/VGLMC address query option | Query UDM for serving AMF address | +| | Select a VGMLC in a VPLMN
Impact: new | None | +| | Obtain a location estimate for a target UE from a VGMLC
Impact: new | None | +| 5GC-MO-LR | Receive a location estimate for a UE from a VGMLC and transfer to an LCS Client.
Impact: new | None | +| Periodic / Triggered 5GC-MT-LR | Assign a reference number to a periodic or triggered 5GC-MT-LR.
Impact: new | None | +| | Receive periodic (or triggered) location responses from a VGMLC and transfer to an LCS Client.
Impact: new | None | + +### 6.2.5.3 Impacts to LMF and Nlmf SBI + +For the LMF based solution, the LMF needs to support the Nlmf\_ProvideLocation and Nlmf\_EventNotify service operations shown in Table 6.2.2.2-1. The Nlmf\_Location\_DetermineLocation service operation defined in Rel-15 is not needed for the LMF Based solution. + +Other impacts for the LMF are summarized below and are compared with LMF impacts already defined in Release 15. + +**Table 6.2.5.3-1: LMF Impacts for the LMF Based Solution** + +| Procedure | Description | Corresponding or Similar Rel-15 Impact (if any) | +|-------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 5GC-MT-LR
Periodic / triggered 5GC-MT-LR | Receive a location request for a target UE from a VGMLC using the NImf ProvideLocation service operation and return a location response.
Impact: new | None | +| | Use the NRF service to select another AMF when a previous serving AMF is not available.
Impact: appears the same as needed for a GMLC in Rel-15 | The same impact seems needed for a 5GC-MT-LR or 5GC-MT-LR without UDM Query at a GMLC though it is not yet defined. | +| | Verify reachability of a target UE using the Namf MT_EnableUEReachability service operation.
Impact: new | None | +| | Verify UE privacy requirements based on privacy requirements received from an HGMLC.
Impact: new | None | +| 5GC-MT-LR
Periodic / Triggered 5GC-MT-LR | Obtain UE status information (and subscription information for a 5GC-MO-LR) using the Namf UEStatus service operation.
Impact: new | None | +| 5GC-MO-LR | Obtain downlink location measurements or a location estimate from a target UE using the Namf Communication N1N2MessageTransfer and Namf_Communication_N1MessageNotify service operations.
Impact: same | Obtain downlink location measurements or a location estimate from a target UE using the Namf Communication N1N2MessageTransfer and Namf_Communication_N1MessageNotify service operations. | +| | Obtain uplink location measurements for a target UE from the NG-RAN using the Namf Communication N1N2MessageTransfer and Namf_Communication_N2InfoNotify service operations.
Impact: same | Obtain uplink location measurements for a target UE from the NG RAN using the Namf Communication N1N2MessageTransfer and Namf_Communication_N2InfoNotify service operations. | +| | Obtain non-UE associated network assistance data from the NG-RAN using the Namf Communication N1N2MessageTransfer and Namf_Communication_N2InfoNotify service operations.
Impact: same | Obtain non-UE associated network assistance data from the NG-RAN using the Namf Communication N1N2MessageTransfer and Namf_Communication_N2InfoNotify service operation. | +| | Compute a location estimate for a target UE based on information obtained from the UE and/or NG-RAN.
Impact: same | Compute a location estimate for a target UE based on information obtained from the UE and/or NG-RAN. | +| | Continue location for a target UE after inter-AMF handover.
Impact: new | None | + +| Procedure | Description | Corresponding or Similar Rel-15 Impact (if any) | +|------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------| +| 5GC-MO-LR | Receive a supplementary services MO-LR request from a UE using the Namf Communication N1MessageNotify service operation and return a response to the UE containing any location estimate obtained using the Namf Communication N1N2MessageTransfer service operation.
Impact: new | None | +| | For TTTP, select a VGMLC and send a location for the UE to the VGMLC using the Nlmf EventNotify service operation.
Impact: new | None | +| | Verify UE subscription to an MO-LR using UE subscription information obtained from the serving AMF.
Impact: new | None | +| | For an MO-LR for transfer of assistance data, transfer requested assistance data to the UE using the Namf Communication N1N2MessageTransfer service operation.
Impact: new | None | +| Periodic / Triggered 5GC-MT-LR | Send a location event report to the VGMLC using the Nlmf EventNotify service operation to confirm activation in the UE of triggered or periodic location.
Impact: new | None | +| | Select a VGMLC and send a location event report to the VGMLC using the Nlmf EventNotify service operation for each periodic or triggered location event detected by the UE (or LMF). | None | +| Periodic / Triggered 5GC-MT-LR (not optimized) | Send a supplementary services LCS Periodic-Triggered Event Invoke to a target UE to activate periodic or triggered location in the UE using the Namf Communication N1N2MessageTransfer service operation. Receive a confirmation from the UE using the Namf Communication N1MessageNotify service operation.
Impact: new | None | +| | Receive a supplementary services MO-LR request from a UE using the Namf Communication N1MessageNotify service operation for each periodic or triggered location event detected by the UE. Return a response to the UE confirming receipt using the Namf Communication N1N2MessageTransfer service operation.
Impact: new | None | +| | Optionally monitor and detect periodic or triggered location events.
Impact: new | None | + +| Procedure | Description | Corresponding or Similar Rel-15 Impact (if any) | +|--------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------| +| Periodic / Triggered 5GC-MT-LR (optimized) | Send a positioning protocol (e.g. LPP) message to a target UE to activate periodic or triggered location in the UE using the Namf Communication N1N2MessageTransfer service operation. Receive a confirmation from the UE using the Namf Communication N1MessageNotify service operation.
Impact: new | None | +| | Receive a positioning protocol (e.g. LPP) message from a UE using the Namf Communication N1MessageNotify service operation for each periodic or triggered location event detected by the UE.
Impact: new | None | +| Periodic / Triggered 5GC-MT-LR (low power) | Assign and include UE IDs, ciphering information, a priority indication and criteria for use of NG-RAN connectionless transfer in the positioning protocol message sent to a target UE to activate periodic or triggered location in the UE. | None | +| | Receive a network positioning message for an event report from a UE sent using connectionless NG-RAN transfer, and authenticate a UE ID and decipher an included positioning protocol message. | None | + +## 6.2.5.4 Impacts to UE + +For the LMF based solution, impacts for the UE are summarized below and are compared with LMF impacts already defined in Release 15. + +**Table 6.2.5.4-1: UE Impacts for the LMF Based Solution** + +| Procedure | Description | Corresponding or Similar Rel-15 Impact (if any) | +|------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------| +| 5GC-MT-LR
Periodic / triggered 5GC-MT-LR |
Receive a supplementary services request from an LMF for privacy notification and/or verification. Verify user privacy requirements if requested and return a supplementary services response to the LMF.
The supplementary services request is already defined for EPS.
Impact: existing
| None | +| 5GC-MT-LRPeriodic / Triggered 5GC-MT-LR
5GC-MO-LR |
Receive a DL positioning message from an LMF to request UE positioning capabilities, provide assistance data or request location information. Obtain any requested location information. Return any requested capabilities or location information to the LMF.
From a UE perspective, the positioning interaction can be the same as in Rel-15.
Impact: same
| Supports a UE Assisted and UE Based Positioning Procedure. | +| 5GC-MO-LR |Send a supplementary services MO-LR request to an LMF via the serving AMF to request a location estimate, assistance data or TTTP. Receive a response from the LMF via the AMF.
The supplementary services request is already defined for EPS and transfer of the MO-LR can use the same NAS transport message as used to send positioning messages. Thus, the new impact is small
Impact: existing plus small addition
| None | +| Periodic / Triggered 5GC-MT-LR |Monitor for and detect periodic or triggered location events. Optionally obtain a location estimate when a location event is detected.
This impact is already defined for EPS.
Impact: existing
| None | +| Periodic / Triggered 5GC-MT-LR (not optimized) |Receive a supplementary services LCS Periodic-Triggered Event Invoke from an LMF via the serving AMF to activate periodic or triggered location in the UE. Return a confirmation to the LMF.
The supplementary services messages are already defined for EPS and transfer can use the same NAS transport message as used to send positioning messages. Thus, the new impact is small
Impact: existing plus small addition
| None | + +| Procedure | Description | Corresponding or Similar Rel-15 Impact (if any) | +|--------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------| +| | Send a supplementary services MO-LR request to an LMF for each periodic or triggered location event detected by the UE and receive a confirmation response from the LMF.This impact is already defined for EPS.
Impact: existing | None | +| Periodic / Triggered 5GC-MT-LR (optimized) | Receive a positioning protocol (e.g. LPP) message from an LMF via the serving AMF to activate periodic or triggered location in the UE. Return a confirmation to the LMF.
Impact: new | None | +| | Send a positioning protocol (e.g. LPP) message to the LMF for each periodic or triggered location event detected by the UE.
Impact: new | None | +| Periodic / Triggered 5GC-MT-LR (low power) | Receive UE IDs, ciphering information, a priority indication and criteria for use of NG-RAN connectionless transfer in the positioning protocol message which activates periodic or triggered location in the UE. | None | +| | Depending on the received criteria, send event reports using NG-RAN connectionless transfer, including obtaining a signalling channel to a nearby RAN node and sending a positioning message containing a UE ID, an authentication code and a positioning protocol message containing event and location information. | None | + +### 6.2.5.5 Impacts to AMF and Namf SBI + +The LMF based solution uses service based operations already defined for the AMF in TS 23.502 [5] except for the Namf\_Location service operations which are not needed. However, to support a 5GC-MO-LR, it is assumed that the Namf\_EventExposure service operation is extended to allow provision of UE subscription information for an MO-LR. An alternative could be a new Namf service operation. A decision on preferred support is FFS. + +### 6.2.5.6 Impacts to the NG-RAN + +Except for support of a Periodic / Triggered 5GC-MT-LR using the low power procedure in clause 6.2.3.5, there are no new impacts to the NG-RAN beyond what is already defined in Rel-15. However, in order to support new positioning methods (e.g. for NR), there may be new impacts, although these would not be specific to the LMF based solution. + +For a Periodic / Triggered 5GC-MT-LR using the low power procedure in clause 6.2.3.5, an NG-RAN node needs to support the following: + +- setup and release of a temporary signalling channel to a UE. +- receive a positioning message from a UE containing a positioning protocol message, a routing ID and other parameters. +- optionally obtain UL location measurements for the UE. +- send a network positioning message, containing the information from the UE and any UL location measurements, to an LMF identified by the routing ID via an AMF. + +More details of these impacts would need to be determined by RAN. + +## 6.2.6 Evaluation + +**Editor's note:** This clause provides an evaluation of the solution. + +## 6.3 Solution 3: Enhancement to LCS architecture + +### 6.3.1 Description + +This solution addresses the Key Issue 1 "Enhancement to LCS architecture". + +Key architecture principles: + +- Support of function flexibility and scalability: location management function can be flexibly deployed, e.g. near UEs, the position signalling can be efficiently transferred to reduce latency and avoid overload on UE and network. +- SBA support: the NFs related to LCS supports SBI and the NF services, the clearer function decoupling among NFs to avoid the function duplication between NFs. +- Support service exposure: support the service exposure framework specified in R-15, and NEF provides location service exposure to external applications. +- Enable network slice: one network slice may have its separate location management function, and it can also support its specific positioning technologies. + +### 6.3.2 Reference LCS architecture + +The reference LCS architecture consist of the following network functions and entities: + +- Location Management Function (LMF). +- Access and Mobility Management Function (AMF). +- User plane Connection Function (UCF). +- Unified Data Management Function (UDM). +- Network Exposure Function (NEF). +- GMLC. + +The non-roaming LCS architecture is indicated in the figure below: + + + +``` + +graph TD + UE[UE] --- NG-RAN[NG-RAN] + NG-RAN -- N2 --> AMF[AMF] + NG-RAN -- N3 --> UPF[UPF] + AMF -- Namf --> NEF[NEF] + AMF -- Nucf --> UCF[UCF] + AMF -- Nlmf --> LMF[LMF] + AMF -- Nudm --> UDM[UDM] + UCF -- N6 --> UPF + GMLC[GMLC] -- Ngmlc --> UDM + GMLC -- Le --> LCS-Client((LCS Client)) + GMLC -- Le --> LRF[LRF] + LRF -- Le --> LCS-Client + +``` + +The diagram illustrates the non-roaming LCS reference architecture. At the bottom left, a UE (User Equipment) is connected to an NG-RAN (Next Generation Radio Access Network). The NG-RAN is connected to an AMF (Access and Management Function) via the N2 interface and to a UPF (User Plane Function) via the N3 interface. The AMF is connected to four network functions via Service Based Interfaces (SBIs): NEF (Network Exposure Function) via Namf, UCF (User plane Connection Function) via Nucf, LMF (Location Management Function) via Nlmf, and UDM (Unified Data Management Function) via Nudm. The UCF is connected to the UPF via the N6 interface. The GMLC (Gateway Mobile Location Centre) is connected to the UDM via Ngmlc. The GMLC is also connected to an LCS Client (Location Service Client) and an LRF (Location Retrieval Function) via Le interfaces. The LRF is further connected to the LCS Client via another Le interface. + +Diagram of non-roaming LCS reference architecture showing the interconnections between various network functions and entities. + +**Figure 6.3.2-1: non-roaming LCS reference architecture** + +The roaming LCS architecture is indicated in the figure below: + + + +Figure 6.3.2-2: roaming LCS reference architecture diagram. The diagram is split into two halves by a vertical dashed line: VPLMN (left) and HPLMN (right). In VPLMN, a UE is connected to an NG-RAN, which is connected to an AMF via N2. The AMF is connected to a UCF via N6. The UCF is connected to a UPF via N3. The AMF is also connected to a V-LMF via Namf. The V-LMF is connected to a NEF via Nlmf. The NEF is connected to a GMMLC via Nnef. The GMMLC is connected to an H-LMF via Ngmlc. In HPLMN, the H-LMF is connected to a NEF via Nnef. The NEF is connected to a UDM via Nudm. The UDM is connected to a GMMLC via Ngmlc. The GMMLC is connected to an LCS Client via Le. The GMMLC is also connected to an LRF via Le. + +**Figure 6.3.2-2: roaming LCS reference architecture** + +In roaming scenario, H-LMF in HPLMN performs privacy check for location service request from applications and then request V-LMF to obtain UE location if the location service request is allowed. In case that the position signalling between UE and V-LMF is transferred via user plane, the local-breakout PDU session is used to establish the connection between UE and UCF. The application functions in VPLMN may be allowed to obtain location service via NEF in VPLMN. + +## 6.3.2 Functional Description + +The LMF includes the following functionality: + +- Handle the location service request from UE, NEF and GMMLC. +- Support privacy check on location service request according to privacy profile. +- Supports location determination for a UE. +- Obtains downlink location measurements or a location estimate from the UE via control plane routing and/or user plane routing. +- Obtains uplink location measurements from the NG RAN. +- Obtains non-UE associated assistance data from the NG RAN. +- Generates charging records for location service. + +The AMF includes the following functionality: + +- Transfer the position signalling between LMF and RAN, between UE and LMF via control plane routing. +- Select LMF for the UE when UE registers the network. + +The NEF includes the following functionality: + +- Exposure of location service to application functions. +- Interact with LMF to address Location service request. + +The UCF includes the following functionality: + +- Support the signalling transfer between UE and LMF via user plane. + +**Editor's note: Functionalities and procedures related to UCF are to be defined.** + +The UDM includes the following functionality: + +- Maintain LCS subscription data and privacy profile. +- Maintain the position context: the serving NFs for positioning, the requested positioning service, e.g. LDR information for one UE. + +The GMLC includes the following functionality: + +- Interaction with the legacy LRF and LCS client to support the interworking. +- Request positioning service from LMF. + +### 6.3.4 Impacts on existing entities and interfaces + +**Editor's note:** This clause describes impacts to existing entities and interfaces. + +### 6.3.5 Evaluation + +**Editor's note:** This clause provides an evaluation of the solution. + +## 6.4 Solution 4: Positioning operations considering different LMF deployment scenarios + +### 6.4.1 Introduction + +This solution applies to Key Issue#3 "Support of low latency LCS" and has objectives to cover the following aspects from the KI#3 study: support of different latency levels and reduce network resource usage related to positioning operations by considering different LMF deployment scenarios. + +### 6.4.2 Functional Description + +#### 6.4.2.1 Common Functionality + +Solution principles include the possibility for the LMF selection by considering LMF deployment scenarios such as centrally located LMF (LMFc) and distributed LMF (LMFd) located close to or at the access network site. The selection of the LMF shall also enable deployment of LMF with different capabilities, e.g. LMFs supporting no or a subset of optional functionalities. + +The following factors may be considered during the LMF selection: + +- Requested Quality of Service information, e.g. + - LCS accuracy, + - Response time (latency), + - LCS QoS Class. +- Proximity of the requestor and target UE, +- Access Type (3GPP / N3GPP), +- 5G AN type (i.e. 5G NR or eLTE) and the serving AN node (i.e. gNB or NG-eNB) of the target UE, +- RAN configuration information, +- LMF capabilities, +- LMF load, + +- Indication of either a single event report or multiple event reports, +- Duration of event reporting, +- Network slicing information, e.g. S-NSSAI and NSI ID. + +**Editor's note:** It is FFS what other information may be considered for LMF selection. + +#### 6.4.2.2 Solution 4A: AMF based selection solution with positioning signalling via AMF + +In the Solution 4A, the flows after the LCS request is received by the AMF are: + +1. The AMF selects an LMF (LMFc or LMFd) and communicates the request to it over NLs. +2. The LMF instigates location operations with the gNB/UE to obtain positioning measurements, a location estimate or to transfer location assistance data, e.g. interacts with a gNB to arrange and get measurements, or with the UE for downlink positioning operation involving OTDOA. +3. The LMF computes the position estimate and returns it to the AMF over NLs. +4. The AMF forwards it to the requesting entity (e.g. UE or GMLC). + +It is assumed that the AMF has the NLs interface with the LMFd (i.e. as it is now for the AMF and LMFc). The positioning signalling between the LMFd and the gNB/UE at the steps 3 and 4 in this solution is based on routing of the NRPP/NRPPa messages that goes over NLs, N2, Uu (via NLs-AP and NAS). It is transparent to the AMF, but always go through the AMF acting as a router of the messages. + +#### 6.4.2.3 Solution 4B: LMF centric based selection solution + +In the solution 4B the concept of centrally located LMF and distributed located LMFs is adapted for the LMF centric architecture that presented in this TR as Solution 2 "LMF Based Location Solution" in clause 6.2. The specific of the LMF centric solution is that a MT-LR comes from the GMLC to the LMF instead of the AMF as in case of the traditional LCS architecture. + +**NOTE:** In Solution 2 (clause 6.2.3.1) the UE location is not known at cell level until the AMF has returned reachability information to the LMF (i.e. LMFc). The LMFc can use the NRF service to request a set of the available LMFd or be interconnected and configured with the available LMFd (e.g. via an operator IP intranet). + +When a positioning request comes to the LMF (i.e. LMFc), the LMFc may determine either to instigate location procedures with the UE/gNB by itself or to trigger the location procedures at an LMFd (e.g. based on the requested positioning QoS information). To support selection of an appropriate LMFd, the LMF obtains reachability information (e.g. serving cell identity) from the AMF. The LMF may then select an LMFd and to proxy for an LMFd forwarding to it the positioning request and the reachability information. Subsequent positioning operations depending on the used positioning methods take place between the LMFd and the UE, and/or between the LMFd and the gNB. When a location result is obtained, the LMFd returns it to the LMF, which passes it towards a LCS client via GMLC. For the requesting entity, it looks as if the LMF computed the position itself. + +### 6.4.3 Procedures + +#### 6.4.3.1 Procedures for the Solution 4A + +##### 6.4.3.1.1 5GC-MO-LR Procedure for the Solution 4A + +Figure 6.4.3.1-1 shows a 5GC Mobile Originated Location Request (5GC-MO-LR) procedure for AMF based selection solution where the positioning signalling between the LMF and the gNB/UE goes always via the AMF to route the NRPP/NRPPa messages. + + + +``` + +sequenceDiagram + participant UE + participant NG_RAN as NG RAN + participant LMFd + participant AMF + participant LMFc + + Note right of AMF: 2. LMF selection + + UE->>AMF: 1. Location Service request + AMF->>AMF: 2. LMF selection + AMF->>LMFd: 3. Namf_Communication_N1MessageNotify (MO-LR request, e.g. "assured") + AMF->>LMFc: 4. Namf_Communication_N1MessageNotify (MO-LR request, e.g. "best effort") + Note over LMFd, LMFc: 5a. Procedures with serving gNB + Note over LMFd, LMFc: 5b. Procedures for DL positioning + Note over LMFd, LMFc: 5c. Procedures for UL positioning + LMFd->>AMF: 6. Namf_Communication_N1N2MessageTransfer (MO-LR Response) + LMFc->>AMF: 7. Namf_Communication_N1N2MessageTransfer (MO-LR Response) + AMF->>UE: 8. Location Service Response + +``` + +Sequence diagram for 5GC Mobile Originated Location Request (5GC-MO-LR) for positioning signalling going through AMF. The diagram shows interactions between UE, NG RAN, LMFd, AMF, and LMFc. The sequence starts with a Location Service request from UE to AMF. The AMF performs LMF selection. It then either invokes Namf\_Communication\_N1MessageNotify to LMFd (MO-LR request, e.g. 'assured') or to LMFc (MO-LR request, e.g. 'best effort'). The selected LMF instigates procedures with the serving gNB (5a), for DL positioning (5b), or for UL positioning (5c). Finally, the LMF invokes Namf\_Communication\_N1N2MessageTransfer to the AMF (MO-LR Response), which then returns the Location Service Response to the UE. + +**Figure 6.4.3.1-1: 5GC Mobile Originated Location Request (5GC-MO-LR) for positioning signalling going through AMF** + +1. The UE with a LCS client requests some location service (e.g. positioning or delivery of assistance data) to the serving AMF at the NAS level. The LCS client may also request a specific LCS QoS. +2. Depending on the requested LCS QoS (e.g. assured or best effort positioning QoS class as defined in TS 22.071 [3]) AMF makes LMF selection. +3. Either: the AMF invokes the Namf\_Communication\_N1MessageNotify service operation to forward the location service request to a LMFd. +4. or the AMF invokes the Namf\_Communication\_N1MessageNotify service operation to transfer the location service request to a LMFc. +- 5a. The selected LMF instigates location procedures with the serving gNB for the UE - e.g. to obtain positioning measurements or assistance data. +- 5b. In addition to step 5a or instead of step 5a, for downlink positioning the selected LMF instigates location procedures with the UE - e.g. to obtain a location estimate or positioning measurements or to transfer location assistance data to the UE. +- 5c. For uplink positioning in addition to performing step 5a, the selected LMF instigates location procedures with gNB for the target UE - e.g. to obtain positioning measurements. +6. If step 3 was performed, the LMFd invokes the Namf\_Communication\_N1N2MessageTransfer service operation to provide a location service response to the AMF and includes any needed results - e.g. success or failure indication and, if requested and obtained, a location estimate for the UE. +7. If step 4 was performed, the LMFc invokes the Namf\_Communication\_N1N2MessageTransfer service operation to provide a location service response to the AMF and includes any needed results - e.g. success or failure indication and, if requested and obtained, a location estimate for the UE. +8. The AMF returns a location service response to the UE and includes any needed results - e.g. a location estimate for the UE. + +### 6.4.3.1.2 5GC-MT-LR Procedure for the Solution 4A + +Figure 6.4.3.1-2 shows a 5GC Mobile Terminated Location Request (5GC-MT-LR) procedure for AMF based selection solution where the positioning signalling between the LMF and the gNB/UE goes always via the AMF to route the NRPP/NRPPa messages. + + + +``` + +sequenceDiagram + participant UE + participant NG RAN + participant LMFd + participant AMF + participant LMFc + participant GMLC + participant LCS Client + + Note right of AMF: 3. LMF selection + + LCS Client->>GMLC: 1. Location Service request + GMLC->>AMF: 2. Nnamf_Location_ProvideLocationRequest + AMF->>AMF: 3. LMF selection + AMF->>LMFd: 4. Nlmf_Location_DetermineLocation_Request (MT-LR request e.g. "assured") + AMF->>LMFc: 5. Nlmf_Location_DetermineLocation_Request (MT-LR request, e.g. "best effort") + Note right of AMF: 6a. Procedures with serving gNB + Note right of AMF: 6b. Procedures for DL positioning + Note right of AMF: 6c. Procedures for UL positioning + LMFd->>AMF: 7. Nlmf_Location_DetermineLocation_Response (MT-LR Response) + LMFc->>AMF: 8. Nlmf_Location_DetermineLocation_Response (MT-LR Response) + AMF->>GMLC: 9. Nnamf_Location_ProvideLocation Response + GMLC->>LCS Client: 10. Location Service Response + +``` + +Sequence diagram of 5GC-MT-LR procedure for Solution 4A. Lifelines: UE, NG RAN, LMFd, AMF, LMFc, GMLC, LCS Client. The sequence starts with a Location Service request from LCS Client to GMLC, followed by Nnamf\_Location\_ProvideLocationRequest from GMLC to AMF. The AMF performs LMF selection and then sends Nlmf\_Location\_DetermineLocation\_Request to either LMFd (assured) or LMFc (best effort). The selected LMF then interacts with the NG RAN and UE through various positioning procedures (6a, 6b, 6c). Finally, the LMF sends a response back to the AMF, which then routes it through the GMLC to the LCS Client. + +**Figure 6.4.3.1-2: 5GC Mobile Terminated Location Request (5GC-MT-LR) for positioning signalling going through AMF** + +- The external LCS client sends a location service request to the GMLC for a location the target UE. The LCS client may also request a specific LCS QoS. +- The GMLC invokes the *Nnamf\_Location\_ProvideLocation* service operation towards the AMF to request the current location of the UE. +- Depending on the requested LCS QoS (e.g. assured or best effort positioning QoS class as defined in TS 22.071 [3]) AMF makes LMF selection. +- Either: the AMF invokes the *Nlmf\_Location\_DetermineLocation\_Request* service operation to forward the location service request to a LMFd. +- or the AMF invokes the *Nlmf\_Location\_DetermineLocation\_Request* service operation to transfer the location service request to a LMFc. +- The selected LMF instigates location procedures with the serving gNB for the UE - e.g. to obtain positioning measurements or assistance data. +- In addition to step 6a or instead of step 6a, for downlink positioning the selected LMF instigates location procedures with the UE - e.g. to obtain a location estimate or positioning measurements or to transfer location assistance data to the UE. +- For uplink positioning in addition to performing step 6a, the selected LMF instigates location procedures with gNB for the target UE - e.g. to obtain positioning measurements. +- If step 4 was performed, the LMFd invokes the *Nlmf\_Location\_DetermineLocation* service operation to provide a location service response to the AMF and includes any needed results - e.g. success or failure indication and, if requested and obtained, a location estimate for the UE. +- If step 5 was performed, the LMFc invokes the *Nlmf\_Location\_DetermineLocation* service operation to provide a location service response to the AMF and includes any needed results - e.g. success or failure indication and, if requested and obtained, a location estimate for the UE. +- The AMF invokes the *Nnamf\_Location\_ProvideLocation* service operation towards the GMLC to response the current location of the UE. + +10. The GMLC forwards the location service response to the LCS client. + +### 6.4.3.2 Procedures for the Solution 4B + +#### 6.4.3.2.1 5GC-MT-LR Procedure for the Solution 4B + +The 5G MT-LR procedure for the LMF centric solution (Solution 2) from clause 6.2.3.1 (Figure 6.2.3.1-1) is considered as a reference baseline. + +A high level flow diagram (MT-LR) to support the concept of centrally located LMF and distributed located LMFs for the LMF centric architecture is shown in Figure 6.4.3.2-1. + + + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant LMFd + participant AMF + participant LMFc + participant VGMLC + + Note left of UE: 8. Network Triggered Service Request (dashed box) + VGMLC->>LMFc: 5. Nlmf_ProvideLocation_Request + LMFc->>AMF: 7. Nlmf_MT_EnableUEReachability_Request + AMF->>UE: 8. Network Triggered Service Request + UE-->>AMF: 9. Nlmf_MT_EnableUEReachability_Response + AMF->>LMFc: 12. Nlmf_EventExposure_Subscribe + LMFc-->>AMF: 13. Nlmf_EventExposure_Notify + Note right of LMFc: 13a. LMF selection + LMFc->>LMFd: 13b. Nlmf_DetermineLocation_Request + Note left of LMFd: 14. UE Positioning + LMFd-->>LMFc: 14a. Nlmf_DetermineLocation_Response + LMFc-->>VGMLC: 15. Nlmf_ProvideLocation_Response + +``` + +Sequence diagram for 5GC Mobile Terminated Location Request (5GC-MT-LR) for a roaming UE in the LMF centric architecture. The diagram shows interactions between UE, NG-RAN, LMFd, AMF, LMFc, and VGMLC. The sequence starts with the VGMLC sending an Nlmf\_ProvideLocation\_Request to the LMFc. The LMFc then sends an Nlmf\_MT\_EnableUEReachability\_Request to the AMF. The AMF sends a Network Triggered Service Request to the UE. The UE responds with an Nlmf\_MT\_EnableUEReachability\_Response. The AMF then sends an Nlmf\_EventExposure\_Subscribe to the LMFc. The LMFc responds with an Nlmf\_EventExposure\_Notify. The LMFc then performs an LMF selection (13a) and sends an Nlmf\_DetermineLocation\_Request to the LMFd. The LMFd performs UE Positioning (14) and sends an Nlmf\_DetermineLocation\_Response to the LMFc. Finally, the LMFc sends an Nlmf\_ProvideLocation\_Response to the VGMLC. + +**Figure 6.4.3.2-1: 5GC Mobile Terminated Location Request (5GC-MT-LR) for a roaming UE in the LMF centric architecture with different LMF deployment scenarios** + +Prior to step 5, the MT-LR performs steps similar to the steps 1-4 of Figure 6.2.3.1-1 (see clause 6.2.3.1 for the step description). + +At the step 5 the VGMLC invokes the Nlmf\_ProvideLocation Request service operation to forward the location request to the LMF (i.e. LMFc). The step 5 and the steps 7-15 are performed in a manner similar to the corresponding steps of Figure 6.2.3.1-1 (see clause 6.2.3.1). Note that as a result of the steps 9, 12, 13 the LMF gets the UE reachability information (e.g. the UE serving cell identity) from the AMF. + +Some more steps, namely, 13a, 13b, and 14a are introduced additionally to support the different LMF deployment scenarios (see Figure 6.4.3.2-1) for the LMF centric architecture: + +- 13a. Based on the UE reachability information and depending on the requested LCS QoS (or/and other factors mentioned in 6.4.2.1) the LMFc determines either to instigate location procedures by itself or delegate the location procedures to an LMFd. In the former case, the flows are the same as in Solution 2 (clause 6.2.3.1, the steps 7-18). In the latter case, the LMFc determines an appropriate LMFd where the request is preferable to be served and the steps 13b and 14a are involved. +- 13b. The LMFc invokes the Nlmf\_Location\_DetermineLocation service operation to request the LMFd to get the UE location result by triggering the positioning operation of step 14. The service operation includes the serving cell identity, the client type and may include the required QoS. The positioning operation of step 14 encompasses various interactions between the LMFd and the NG-RAN node (e.g. gNB) or the UE. The LMFd has the protocol termination functions of an LMF, e.g. it can terminate an NRPPa protocol with the NG-RAN node and an NRPP protocol with the UE. + +- 14a. After the UE positioning operation of step 14, the LMFd invokes the Nlmf\_Location\_DetermineLocation Response service operation to return any needed results to the LMFc (e.g. a location estimate for the UE or obtained measurements for a final computation of the position). + +At the step 15 the LMFc returns the location result to the VGMLC in the Nlmf\_ProvideLocation\_Response message and LCS service response is forwarded to the LCS client (steps 16 and 18 in Figure 6.2.3.1-1). + +#### 6.4.3.2.2 5GC-MO-LR Procedure for the Solution 4B + +The 5G MO-LR procedure for the LMF centric solution (Solution 2) from clause 6.2.3.2 (Figure 6.2.3.2-1) is considered as a reference baseline. + +A high level flow diagram (MO-LR) to support the concept of centrally located LMF and distributed located LMFs for the LMF centric architecture is shown in Figure 6.4.3.2-2. + + + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant LMFd + participant AMF + participant LMFc + participant VGMLC + + Note over UE, AMF: 1. UE Triggered Service Request + UE->>AMF: 2. NAS Transport (MO-LR Request) + AMF->>LMFc: 3. Namf_Communication_N1MessageNotify (MO-LR Request) + LMFc->>AMF: 4. Namf_EventExposure_Subscribe + AMF->>LMFc: 5. Namf_EventExposure_Notify + Note over LMFc: 5a. LMF selection + LMFc->>LMFd: 5b. Nlmf_DetermineLocation_Request + Note over UE, NG-RAN, LMFd: 6. UE Positioning + LMFd->>LMFc: 6a. Nlmf_DetermineLocation_Response + LMFc->>VGMLC: 7. Nlmf_EventNotify + LMFc->>AMF: 8. Namf_Communication_N1N2MessageTransfer (MO-LR Response) + AMF->>UE: 9. NAS Transport (MO-LR Response) + +``` + +Sequence diagram for 5GC-MO-LR procedure for a roaming UE in the LMF centric architecture. The diagram shows interactions between UE, NG-RAN, LMFd, AMF, LMFc, and VGMLC. The process starts with a UE Triggered Service Request (1) from UE to AMF. This is followed by a NAS Transport (MO-LR Request) (2) from UE to AMF. The AMF then sends a Namf\_Communication\_N1MessageNotify (MO-LR Request) (3) to LMFc. LMFc sends a Namf\_EventExposure\_Subscribe (4) to AMF, which responds with Namf\_EventExposure\_Notify (5). LMFc then performs an LMF selection (5a) and sends a Nlmf\_DetermineLocation\_Request (5b) to LMFd. LMFd initiates the UE Positioning (6) with NG-RAN and UE. LMFd then sends a Nlmf\_DetermineLocation\_Response (6a) to LMFc. LMFc sends a Namf\_Communication\_N1N2MessageTransfer (MO-LR Response) (8) to AMF, which in turn sends a NAS Transport (MO-LR Response) (9) to UE. Finally, LMFc sends a Nlmf\_EventNotify (7) to VGMLC. + +**Figure 6.4.3.2-2: 5GC Mobile Originated Location Request (5GC-MO-LR) for a roaming UE in the LMF centric architecture with different LMF deployment scenarios** + +The MO-LR performs steps similar to the steps 1-5 of Figure 6.2.3.2-1 (see clause 6.2.3.2 for the step description). + +NOTE: As a result of the steps 3-5 the LMF gets the UE reachability information (e.g. the UE serving cell identity) from the AMF. + +Some more steps, namely, 5a, 5b, and 6a are introduced additionally to support the different LMF deployment scenarios (see Figure 6.4.3.2-2) for the LMF centric architecture: + +- 5a. Based on the UE reachability information and depending on the requested LCS QoS (or/and other factors mentioned in 6.4.2.1) the LMFc determines either to instigate location procedures by itself or delegate the location procedures to an LMFd. In the former case, the flows are the same as in Solution 2 (clause 6.2.3.2, the steps 7-12). In the latter case, the LMFc determines an appropriate LMFd where the request is preferable to be served and the steps 5b and 6a are involved. +- 5b. The LMFc invokes the Nlmf\_Location\_DetermineLocation service operation to request the LMFd to get the UE location result by triggering the positioning operation of step 6. The service operation includes the serving cell identity, the client type and may include the required QoS. The positioning operation of step 6 encompasses various interactions between the LMFd and the NG-RAN node (e.g. gNB) or the UE. The LMFd has the protocol termination functions of an LMF, e.g. it can terminate an NRPPa protocol with the NG-RAN node and an NRPP protocol with the UE. + +- 6a. After the UE positioning operation of step 6, the LMFd invokes the Nlmf\_Location\_DetermineLocation Response service operation to return any needed results to the LMFc (e.g. a location estimate for the UE or obtained measurements for a final computation of the position). + +At the step 7 the LMFc notifies the location result to the VGMLC in the Nlmf\_EventNotify service operation and the MO-LR location information is forwarded to the LCS client (steps 8 and 10 in Figure 6.2.3.2-1). The steps 8 and 9 provides MO-LR response to the AMF and further to the UE (similar to the steps 11 and 12 in Figure 6.2.3.2-1). + +## 6.4.4 Impacts on existing entities and interfaces + +### 6.4.4.1 Impacts of Solution 4A + +Impacted entities: + +- AMF: Capability for LMF selection to serve the location service request (e.g. based on the requested positioning QoS information). + +### 6.4.4.2 Impacts of Solution 4B + +Impacted entities: + +- LMF (i.e. LMFc): Capability for LMF selection to serve the location service request (e.g. based on the requested positioning QoS information). + +## 6.4.5 Evaluation + +### 6.4.5.1 Evaluation of Solution 4A + +The advantage of the selection of a LMFd located at the edge (close to or at the access network site) is to make interface for location operations between LMFd and gNB/UE as short/fast as possible, especially for the case that all the measurement operations take place under the same gNB (e.g. operations for downlink or uplink positioning). For instance, it accelerates the process when the LMFd instigates location operations with the gNB/UE to obtain positioning measurements, assistance data, or a location estimate. It brings gains both in terms of latency at the interface and "localized" signalling related to the instigation of positioning operation up to the edge in comparison with a lot of the latency and the signalling over the network in case of a centralized LMF located deep in the core, e.g. combined with the GMLC. + +The lack of the solution is not optimal path to deliver the positioning signalling between the LMFd and the gNB/UE since the routing of the NRPP/NRPPa messages goes through the AMF (via NLs-AP and NAS) located in core that impacts on the latency. A latency improvement can be obtained by deploying many AMFs close to the edge of the network, and correspondingly many LMFs also close to the edge of the network. This is an implementation issue and does not have a standard impact, but this has disadvantages in deployment cost and results in more overhead in the network due to frequent inter-AMF mobility. This approach is applicable for a deployment with a relatively small number of gNBs, each of which covers a large area with a lot of DUs/TRPs since there is a tradeoff between low positioning latency and frequent inter-AMF mobility. + +## 6.5 Solution 5: Privacy Check with UE privacy setting + +### 6.5.1 Introduction + +This solution addresses the Key Issue 4: Reduce overhead for repetitive non-successful privacy verification. + +### 6.5.2 Functional Description + +In order to reduce overhead for repetitive non-successful privacy verification, it is proposed that the UE indicates to the network the privacy setting according to the user's location privacy preference. The privacy setting specifies whether the LCS request from the external LCS client is disallowed. Emergency Services LCS Clients and Lawful Intercept LCS Clients are exempt from this procedure. + +With respect to the privacy handling requirement of commercial LCS request as defined in TS 22.071 [3] and the need to reduce the overhead caused by repetitive non-successful privacy verification: + +- it is proposed to introduce a kind of 5GC-MT-LR procedure with privacy check (See clause 6.5.3.1) based on the 5GC-MT-LR Procedure defined in clause 4.13.5.3 of TS 23.502 [5]; +- it is also proposed another kind of 5GC-MT-LR procedure with privacy check (See clause 6.5.3.X) based on the LMF based architecture as specified in clause 6.2. +- During the privacy verification with the UE about the current LCS request, the UE can indicate the privacy setting for the subsequent LCS request from the external LCS client, e.g. disallow the subsequent LCS requests for a time period. + +The procedure for privacy setting update (See clause 6.5.3.2) is also proposed: + +- It can be used along to indicate and update the privacy setting of the UE; +- Or it can be used along with 5GC-MT-LR with privacy check procedure, i.e., update the privacy setting which has been provided within 5GC-MT-LR with privacy check procedure. + +The GMLC, via privacy check W.R.T. the privacy setting and the subscription, can decide whether to reject the receiving LCS request immediately. When privacy setting disallows the LCS request, the GMLC rejects the LCS request immediately. + +## 6.5.3 Procedures + +### 6.5.3.1 5GC-MT-LR with privacy check + + + +``` + +sequenceDiagram + participant External Client + participant GMLC + participant UDM + participant AMF + participant LMF + participant NG-RAN + participant UE + + Note right of External Client: 1. LCS Service Request + External Client->>GMLC: 1. LCS Service Request + Note right of GMLC: 2. Nudm_UE ContextManagement_Get Request + GMLC->>UDM: 2. Nudm_UE ContextManagement_Get Request + Note right of UDM: 3. Nudm_UE ContextManagement_Get Response + UDM-->>GMLC: 3. Nudm_UE ContextManagement_Get Response + Note right of GMLC: 4. Namf_Location_ProvideLocation Request + GMLC->>AMF: 4. Namf_Location_ProvideLocation Request + Note right of AMF: 5. Network Triggered Service Request + AMF-->>NG-RAN: 5. Network Triggered Service Request + Note right of NG-RAN: 6. NAS Location Notification Invoke + NG-RAN->>UE: 6. NAS Location Notification Invoke + Note right of UE: 7. NAS Location Notification Return Result + UE-->>NG-RAN: 7. NAS Location Notification Return Result + Note right of NG-RAN: 8. Nudm_UECM_Update + NG-RAN->>AMF: 8. Nudm_UECM_Update + Note right of AMF: 9. Nlmf_Location_DetermineLocation Request + AMF->>LMF: 9. Nlmf_Location_DetermineLocation Request + Note right of LMF: 10. UE Positioning + LMF-->>AMF: 10. UE Positioning + Note right of AMF: 11. Nlmf_Location_DetermineLocation Response + AMF-->>LMF: 11. Nlmf_Location_DetermineLocation Response + Note right of AMF: 12. Namf_Location_ProvideLocation Response + AMF->>GMLC: 12. Namf_Location_ProvideLocation Response + Note right of GMLC: 13. LCS Service Response + GMLC-->>External Client: 13. LCS Service Response + +``` + +Sequence diagram for 5GC-MT-LR with privacy check procedure. The diagram shows interactions between UE, NG-RAN, AMF, LMF, UDM, GMLC, and External Client. The process starts with an LCS Service Request from the External Client to the GMLC. The GMLC then invokes Nudm\_UE ContextManagement\_Get Request to the UDM. The UDM responds with Nudm\_UE ContextManagement\_Get Response. The GMLC then sends Namf\_Location\_ProvideLocation Request to the AMF. The AMF initiates a Network Triggered Service Request to the UE via the NG-RAN. The UE responds with NAS Location Notification Return Result. The AMF then sends Nudm\_UECM\_Update to the UDM. The AMF also sends Nlmf\_Location\_DetermineLocation Request to the LMF. The LMF performs UE Positioning and returns Nlmf\_Location\_DetermineLocation Response to the AMF. The AMF then sends Namf\_Location\_ProvideLocation Response to the GMLC. Finally, the GMLC sends LCS Service Response to the External Client. + +Figure 6.5.3.1-1: 5GC-MT-LR with privacy check + +1. See as step1 in clause 4.13.5.3 of TS 23.502 [5]. +2. The GMLC invokes a Nudm\_UE ContextManagement\_Get service operation towards the home UDM of the target UE to be located with the GPSI or SUPI of this UE. + +3. The UDM returns the network addresses of the current serving AMF, UE subscription profile for LCS and may return the privacy setting for the subsequent LCS requests of the UE. + +The GMLC performs the privacy check according to UE subscription profile and the privacy setting, if existed. If either privacy setting or UE subscription profile indicates barring of LCS request, the GMLC immediately returns the rejection response back to the external LCS client. Otherwise, the GMLC requests AMF to provide the UE location. + +4. The GMLC invokes the Namf\_Location\_ProvideLocation service operation towards the AMF to request the current location of the UE. The service operation includes the SUPI, and client type and may include the required QoS and Supported GAD shapes. + +The service operation may also carry the indicator of privacy check related action. + +5. If the UE is in CM IDLE state, the AMF initiates a network triggered Service Request procedure as defined in clause 4.2.3.4 in TS 23.502 [5] to establish a signalling connection with the UE. +6. If the indicator of privacy check related action indicates that the UE must either be notified or notified with privacy verification, a notification invoke message is sent to the target UE indicating, the identity of the LCS client the Requestor Identity (if that is both supported and available) and whether privacy verification is required. +7. The target UE notifies the UE user of the location request and, if privacy verification was requested, waits for the user to grant or withhold permission. The UE then returns a notification result to the AMF indicating, if privacy verification was requested, whether permission is granted or denied for the current LCS request. + +The notification result may also indicate the privacy setting for the subsequent LCS requests. The privacy setting for the subsequent LCS requests indicates whether the subsequent LCS requests is disallowed by the UE. The privacy setting for the subsequent LCS requests may also indicate a time for privacy setting for disallowing the subsequent LCS requests. + +8. If receiving the privacy setting for the subsequent LCS requests from the UE, the AMF stores the privacy setting for the subsequent LCS requests. The AMF also invokes a Nudm\_UECM\_Update service operation towards the UDM of the target UE to request the store the privacy setting of the UE for the subsequent LCS requests. + +9-11. See as step 6-8 in clause 4.13.5.3 of TS 23.502 [5]. + +12. The AMF returns the Namf\_Location\_ProvideLocation Response towards the GMLC to return the location of the UE, if the AMF has not initiated the Privacy Verification process in step 6. The service operation includes the location estimate, its age and accuracy and may include information about the positioning method. + +If step 6 has been performed for privacy verification, the AMF returns the location information only, if it has received a NAS Location Notification Return Result indicating that permission is granted. + +If a NAS Location Notification Return Result message indicating that permission is not granted is received, or there is no response, with the requested privacy check action or the UE subscription profile indicating barring of LCS request, the AMF shall return an error response to the GMLC. + +The service operation shall also include the privacy setting for the subsequent LCS requests, if the privacy setting for the subsequent LCS requests is indicated by the UE. + +13. The GMLC sends the location service response to the external location services client. + +### 6.5.3.2 Privacy Setting Update + + + +``` +sequenceDiagram + participant UE + participant NG-RAN + participant AMF or LMF + participant UDM + participant GMLC + participant External Client + Note left of UE: 1. Privacy Setting Update Request + UE->>AMF or LMF: 1. Privacy Setting Update Request + Note right of AMF or LMF: 2. Nudm_UECM_Update + AMF or LMF->>UDM: 2. Nudm_UECM_Update + Note left of UE: 3. Privacy Setting Update Response + AMF or LMF->>UE: 3. Privacy Setting Update Response + Note right of External Client: 4. Figure 6.X.3-1: 5GC-MT-LR Procedure privacy check + UE->>External Client: 4. Figure 6.X.3-1: 5GC-MT-LR Procedure privacy check +``` + +Sequence diagram for Privacy Setting Update procedure. Lifelines: UE, NG-RAN, AMF or LMF, UDM, GMLC, External Client. The sequence shows: 1. UE sends a Privacy Setting Update Request to AMF or LMF; 2. AMF or LMF sends a Nudm\_UECM\_Update to UDM; 3. AMF or LMF sends a Privacy Setting Update Response to UE; 4. A horizontal bar labeled 'Figure 6.X.3-1: 5GC-MT-LR Procedure privacy check' spans across all lifelines below step 3. + +**Figure 6.5.3.2-1: Privacy Setting Update** + +1. If the UE user has changed the privacy setting for the subsequent LCS requests, the UE sends the updated privacy setting for the subsequent LCS requests to the AMF or LMF. + +For the case that Privacy Setting Update procedure between UE and LMF, it means the Privacy Setting Update procedure is transparent to the AMF and the AMF just transfer it as container between UE and LMF. + +If the UE in idle, the UE signalling connection is setup in prior to step 1. + +2. The AMF or LMF stores updated privacy setting for the subsequent LCS requests. The AMF or LMF also invokes a Nudm\_UECM\_Update service operation towards the home UDM of the target UE to request the update the privacy setting of the UE for the subsequent LCS requests. +3. The AMF or LMF responses the privacy setting update response to the UE. +5. If a new LCS request from the external LCS client arrives, the 5GC-MT-LR procedure with privacy check is executed based on the updated privacy setting for the subsequent LCS requests. + +### 6.5.3.3 5GC-MT-LR with privacy check based on LMF based architecture + + + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant AMF + participant LMF + participant VGMLC + participant UDM + participant HGMLC + participant LCS Client + + Note right of LCS Client: 1. LCS Service Request + LCS Client->>HGMLC: 1. LCS Service Request + Note right of HGMLC: 2. Nudm_UE ContextManagement_Get Request + HGMLC->>UDM: 2. Nudm_UE ContextManagement_Get Request + Note right of UDM: 3. Nudm_UE ContextManagement_Get Response + UDM->>HGMLC: 3. Nudm_UE ContextManagement_Get Response + Note right of HGMLC: 4. LCS Service Request + HGMLC->>VGMLC: 4. LCS Service Request + Note right of VGMLC: 5. Nlmf_ProvideLocation_Request + VGMLC->>LMF: 5. Nlmf_ProvideLocation_Request + Note right of LMF: 6. Nlmf_ProvideLocation_Request + LMF-->>AMF: 6. Nlmf_ProvideLocation_Request + Note right of AMF: 7. Nlmf_MT_EnableUEReachability_Request + AMF->>NG-RAN: 7. Nlmf_MT_EnableUEReachability_Request + Note right of NG-RAN: 8. Network Triggered Service Request + NG-RAN-->>UE: 8. Network Triggered Service Request + Note right of UE: 9. Nlmf_MT_EnableUEReachability_Response + UE-->>AMF: 9. Nlmf_MT_EnableUEReachability_Response + Note right of AMF: 10. Location Notification Invoke + AMF-->>LMF: 10. Location Notification Invoke + Note right of LMF: 11. Location Notification Response + LMF-->>AMF: 11. Location Notification Response + Note right of AMF: 12. Nudm_UECM_Update + AMF->>UDM: 12. Nudm_UECM_Update + Note right of UDM: 13. Nlmf_EventExposure_Subscribe + UDM->>LMF: 13. Nlmf_EventExposure_Subscribe + Note right of LMF: 14. Nlmf_EventExposure_Notify + LMF-->>AMF: 14. Nlmf_EventExposure_Notify + Note right of AMF: 15. UE Positioning + AMF->>VGMLC: 15. UE Positioning + Note right of VGMLC: 16. Nlmf_ProvideLocation_Response + VGMLC->>HGMLC: 16. Nlmf_ProvideLocation_Response + Note right of HGMLC: 17. LCS Service Response + HGMLC-->>LMF: 17. LCS Service Response + Note right of LMF: 18. Nlmf_ProvideLocation_Response + LMF-->>AMF: 18. Nlmf_ProvideLocation_Response + Note right of AMF: 19. LCS Service Response + AMF-->>LCS Client: 19. LCS Service Response + +``` + +Sequence diagram for 5GC-MT-LR with privacy check based on LMF based architecture. The diagram shows interactions between UE, NG-RAN, AMF, LMF, VGMLC, UDM, HGMLC, and LCS Client. The process involves a location request from the LCS Client, context management checks, service requests, and finally UE positioning and response delivery. + +**Figure 6.5.3.X-1 - 5GC Mobile Terminated Location Request (5GC-MT-LR) for a UE** + +Step1 to step 2 are as the same as step1 to 2 in chapter 6.2.3.1. + +- The UDM returns the serving AMF address and possibly a VGMLC address and/or an LMF address in the VPLMN. The UDM may also return subscribed privacy requirements for the target UE - e.g. if not stored in the HGMLC. + +If the privacy setting of the target UE is included in the privacy requirement and indicates that the LCS requests is disallowed, the HGMLC immediately returns the rejection response back to the LCS client. + +Step4 to step 10 are as the same as step4 to 10 in chapter 6.2.3.1. + +- The UE notifies the user of the location request and verifies user permission if UE privacy is to be verified. The UE then returns a supplementary services Location Notification response to the LMF indicating whether the user grants or withholds permission for the location request when UE privacy is verified. The supplementary services response is transferred via the serving AMF and delivered to the LMF using an Nlmf\_Communication\_N1MessageNotify service operation. + +The notification result may also indicate the privacy setting for the subsequent LCS requests. The privacy setting for the subsequent LCS requests indicates whether the subsequent LCS requests is disallowed by the UE. The privacy setting for the subsequent LCS requests may also indicate a time for privacy setting for disallowing the subsequent LCS requests. + +- If receiving the privacy setting for the subsequent LCS requests from the UE, the LMF invokes a Nudm\_UECM\_Update service operation towards the UDM of the target UE to request the store the privacy setting of the UE for the subsequent LCS requests. + +Step 13 to step 18 is same as step 12 to step 18 in 6.2.3.1. + +## 6.5.4 Impacts on existing entities and interfaces + +UE: + +- Provides the privacy permission for the current LCS request: granted or denied. +- Provides the privacy setting for the subsequent LCS requests: allowed or disallowed, time for privacy setting for disallowing the subsequent LCS requests. + +AMF or LMF: + +- Store the privacy setting for the subsequent LCS requests into the UE context if receives the privacy setting for the subsequent LCS requests from the UE. +- Interface with UDM to provide the privacy setting for the subsequent LCS requests if receives the privacy setting for the subsequent LCS requests from the UE. + +GMLC: + +- Interface with UDM to enforce the privacy check according to the UE subscription profile for LCS and privacy setting for the subsequent LCS requests. + +UDM: + +- Store privacy setting for the subsequent LCS requests, UE subscription profile for LCS (including the requested privacy check related action). + +## 6.5.5 Evaluation + +**Editor's note:** This clause provides an evaluation of the solution. + +Solution 5 is that the GMLC takes the privacy setting from the UE to decide whether immediately disallows the LCS request from external LCS client. + +Solution 5 can adapt to both the LMF based architecture and the AMF based architecture. It reuses the existing privacy verification procedure as much as possible without brings in extra NAS signalling overhead. + +## 6.6 Solution 6: User Privacy Setting send via AMF + +### 6.6.1 Introduction + +This solution addresses Key Issue 4: Reduce overhead for repetitive non-successful privacy verification. + +### 6.6.2 Functional Description + +GMLC is responsible for privacy verification based on information from PPR and UE. The function of PPR and procedure between GMLC and PPR could be found in TS 23.271 [6]. + +This solution mainly focuses on how UE provides privacy setting to GMLC. That is, once user has changed the Privacy Setting on UE, the UE updates the network with such changes during Registration procedure. Such update procedure involves AMF, PPR and GMLC. The PPR decides the UE privacy profile based on operator policy and UE provided Privacy Setting preference. The PPR sends the changed UE privacy profile to GMLC. When LCS request arrives, the GMLC performs the privacy verification. PPR may be a standalone network entity or it may be integrated in H-GMLC. + +### 6.6.3 Procedures + +#### 6.6.3.1 Privacy Setting Update + +The UE may provide Privacy Setting to GMLC during Registration procedure, once the Privacy Setting has changed by user. For this procedure, the V-GMLC is involved in roaming case. + + + +``` + +sequenceDiagram + participant UE + participant AMF + participant V-GMLC + participant H-GMLC + participant PPR + Note left of UE: 1. Registration Request (Privacy Setting Preference) + UE->>AMF: 1. Registration Request (Privacy Setting Preference) + AMF->>V-GMLC: 2. Ngmlc_UserPrivacy_Set Request + V-GMLC->>H-GMLC: 3. Ngmlc_UserPrivacy_Set Request + H-GMLC->>PPR: 4. Nppr_PVPreference_Set Request + PPR->>H-GMLC: 5. Nppr_PVPreference_Set Response + H-GMLC->>V-GMLC: 6. Ngmlc_UserPrivacy_Set Response + V-GMLC->>AMF: 7. Ngmlc_UserPrivacy_Set Response + AMF->>UE: 8. Registration Accept (Accepted Privacy Setting) + +``` + +Sequence diagram of the Privacy Setting Update procedure. Lifelines: UE, AMF, V-GMLC, H-GMLC, PPR. The sequence starts with UE sending a Registration Request (Privacy Setting Preference) to AMF. AMF sends Ngmlc\_UserPrivacy\_Set Request to V-GMLC. V-GMLC sends Ngmlc\_UserPrivacy\_Set Request to H-GMLC. H-GMLC sends Nppr\_PVPreference\_Set Request to PPR. PPR sends Nppr\_PVPreference\_Set Response to H-GMLC. H-GMLC sends Ngmlc\_UserPrivacy\_Set Response to V-GMLC. V-GMLC sends Ngmlc\_UserPrivacy\_Set Response to AMF. AMF sends Registration Accept (Accepted Privacy Setting) to UE. + +**Figure 6.6.3-1: Privacy Setting Update procedure** + +- UE sends Registration Request to AMF. The message includes the UE privacy setting preference, e.g. allowed service type. + - AMF sends Ngmlc\_UserPrivacy\_Set Request to V-GMLC including the UE privacy setting preference and UE ID. + - V-GMLC sends Ngmlc\_UserPrivacy\_Set Request to H-GMLC. + - H-GMLC sends Nppr\_PVPreference\_Set Request to PPR. The message includes the UE ID and UE privacy setting preference. + - PPR sends Nppr\_PVPreference\_Set Response to H-GMLC, which includes the PPR decided UE Privacy Setting. PPR may change the privacy setting preference based on operator policy. +- NOTE: If the PPR changes the UE Privacy Setting preference, the privacy verification procedure to the UE may still happen. This may lead to repetitive unsuccessful privacy verification procedure. +- H-GMLC stores the UE Privacy Setting, and sends Ngmlc\_UserPrivacy\_Set Response to V-GMLC. The message includes the UE Privacy Setting received from PPR. + - V-GMLC stores the UE privacy setting, and sends Ngmlc\_UserPrivacy\_Set Response to AMF. The message includes the UE Privacy Setting. + - AMF sends Registration Accept to UE. The message includes the UE Privacy Setting accepted by network. + +### 6.6.3.2 Privacy Verification + +When GMLC receives LCS Service Request from External Client, it performs privacy verification based on the subscriber LCS Privacy Profile (SLPP) information from PPR first and then the User privacy setting profile received from the PPR. If any one of the privacy verification fails, GMLC shall terminate the request, and response to the External client with appropriate error code. Otherwise, the GMLC continue the location procedure. + +### 6.6.3.3 GMLC service + +#### 6.6.3.3.1 General + +The following table shows the GMLC service and GMLC Service Operation. + +**Table 6.6.3.x.1-1: GMLC Services** + +| Service Name | Service Operations | Operation Semantic | Known Consumer(s) | +|-------------------|--------------------|--------------------|-------------------| +| Ngmlc_UserPrivacy | Set | Request/ Response | Peer GMLC, AMF | + +### 6.6.3.3.2 Ngmlc\_UserPrivacy\_Set service operation + +Service operation name: Ngmlc\_UserPrivacy\_Set. + +**Description:** Receives the UE Privacy Setting preference from the consumer NF and provides the Privacy Setting accepted by network to the consumer NF. + +**Input, Required:** UE Privacy Setting preference, UE ID. + +Input, Optional: None. + +**Output, Required:** Privacy Setting accepted by network. + +Output, Optional: None. + +### 6.6.3.4 PPR service + +#### 6.6.3.4.1 General + +The following table shows the PPR service and PPR Service Operation. + +**Table 6.6.3.4.1-1: PPR Services** + +| Service Name | Service Operations | Operation Semantic | Known Consumer(s) | +|-------------------|--------------------|--------------------|-------------------| +| Nppr_PVPreference | Set | Request/ Response | GMLC | + +#### 6.6.3.4.2 Nppr\_PVPreference\_Set service operation + +Service operation name: Nppr\_PVPreference\_Set. + +**Description:** Receives the UE Privacy Setting preference from the consumer NF and provides the Privacy Setting accepted by network to the consumer NF. + +**Input, Required:** UE privacy setting preference, UE ID. + +Input, Optional: None. + +**Output, Required:** Privacy Setting accepted by network. + +Output, Optional: None. + +## 6.6.4 Impacts on existing entities and interfaces + +Impacted entities: + +- UE provides privacy setting preference to AMF. +- AMF: + - Receive privacy setting preference from UE. + - Send the UE provided privacy setting preference to GMLC and receive updated setting from GMLC and provide it to UE. +- PPR decides the privacy setting based on UE provided setting preference operator policy, and provides it to GMLC. +- GMLC receives UE privacy setting profile from PPR and performs privacy check based on the setting. + +Impacted interfaces: + +- N1, and interface between AMF and PPR, interface between PPR and GMLC are impacted. + +## 6.6.5 Evaluation + +**Editor's note:** This clause provides an evaluation of the solution. + +# 6.7 Solution 7: User Privacy Setting send via LMF + +## 6.7.1 Introduction + +This solution addresses Key Issue 4: Reduce overhead for repetitive non-successful privacy verification. + +## 6.7.2 Functional Description + +In this solution, we use "UE-LMF" to denote the protocol that used to transfer messages between UE and LMF. The details of this protocol are left to stage 3. + +When user has changed the Privacy Setting on UE, the UE updates the network with such changes by using "UE-LMF" protocol. This "UE-LMF" protocol message is transferred via NAS message between UE and AMF, and the AMF and LMF use service interface operation to transfer those messages. The LMF in the VPLMN select VGMLC, and notify the changed privacy settings, the VGMLC will contact user's home network (i.e. HGMMLC and PPR are involved in following steps) to confirm such change is allowed, and return received result to LMF. + +The PPR decides the UE privacy profile based on operator policy and UE provided Privacy Setting preference. The PPR sends the changed UE privacy profile to GMLC. GMLC is responsible for privacy verification based on information received from PPR and UE. The function of PPR and procedure between GMLC and PPR could be found in TS 23.271 [6]. + +When LCS request arrives, the GMLC performs the privacy verification. PPR may be a standalone network entity or it may be integrated in H-GMLC. + +## 6.7.3 Procedures + +### 6.7.3.1 Privacy Setting Update + +The UE may provide Privacy Setting to GMLC by using "UE-LMF" protocol message, once the Privacy Setting has changed by user. If such change is made by user when UE is in IDLE mode, the UE initiates service request procedure to get NAS signalling established firstly. For this procedure, the V-GMLC is involved in roaming case. + + + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant AMF + participant LMF + participant V-GMLC + participant H-GMLC + participant PPR + + Note left of UE: 1. UE Triggered Service Request + UE->>AMF: 2. NAS Transport (Request Setting Change) + AMF->>LMF: 3. Namf_Communication_N1MessageNotify (Request Setting Change) + LMF->>V-GMLC: 4. Ngmlc_UserPrivacy_Set Request + V-GMLC->>H-GMLC: 5. Ngmlc_UserPrivacy_Set Request + H-GMLC->>PPR: 6. Nppr_PVPreference_Set Request + PPR->>H-GMLC: 7. Nppr_PVPreference_Set Response + H-GMLC->>V-GMLC: 8. Ngmlc_UserPrivacy_Set Response + V-GMLC->>LMF: 9. Ngmlc_UserPrivacy_Set Response + LMF->>AMF: 10. Namf_Communication_N1N2MessageTransfer (Accepted Privacy Setting) + AMF->>UE: 11. NAS Transport (Accepted Privacy Setting) + +``` + +Sequence diagram illustrating the Privacy Setting Update procedure. Lifelines: UE, NG-RAN, AMF, LMF, V-GMLC, H-GMLC, PPR. The procedure involves 11 steps: 1. UE Triggered Service Request (UE to AMF); 2. NAS Transport (Request Setting Change) (UE to AMF); 3. Namf\_Communication\_N1MessageNotify (Request Setting Change) (AMF to LMF); 4. Ngmlc\_UserPrivacy\_Set Request (LMF to V-GMLC); 5. Ngmlc\_UserPrivacy\_Set Request (V-GMLC to H-GMLC); 6. Nppr\_PVPreference\_Set Request (H-GMLC to PPR); 7. Nppr\_PVPreference\_Set Response (PPR to H-GMLC); 8. Ngmlc\_UserPrivacy\_Set Response (H-GMLC to V-GMLC); 9. Ngmlc\_UserPrivacy\_Set Response (V-GMLC to LMF); 10. Namf\_Communication\_N1N2MessageTransfer (Accepted Privacy Setting) (LMF to AMF); 11. NAS Transport (Accepted Privacy Setting) (AMF to UE). + +**Figure 6.7.3-1: Privacy Setting Update procedure** + +- User changed the UE privacy setting preference. If UE is in IDLE mode, the UE imitates service procedure to establish the NAS signalling. If UE is in CONNECTED mode, this step is skipped. + - UE sends NAS Transport message to the AMF. This NAS message includes "UE-LMF" message Request Setting Change (UE privacy setting preference, e.g. allowed service type). + - The AMF selects an LMF in the VPLMN and invokes the Namf\_Communication\_N1MessageNotify service operation towards this LMF to transfer the Request Setting Change. + - LMF sends Ngmlc\_UserPrivacy\_Set Request to V-GMLC including the UE privacy setting preference. + - V-GMLC sends Ngmlc\_UserPrivacy\_Set Request to H-GMLC. + - H-GMLC sends Nppr\_PVPreference\_Set Request to PPR. The message includes the UE ID and UE privacy setting preference. + - PPR sends Nppr\_PVPreference\_Set Response to H-GMLC, which includes the PPR decided UE Privacy Setting. PPR may change the privacy setting preference based on operator policy.. +- NOTE: If the PPR changes the UE Privacy Setting preference, the privacy verification procedure to the UE may still happen. This may lead to repetitive unsuccessful privacy verification procedure. +- H-GMLC stores the UE Privacy Setting, and sends Ngmlc\_UserPrivacy\_Set Response to V-GMLC. The message includes the UE Privacy Setting received from PPR. + - V-GMLC stores the UE privacy setting, and sends Ngmlc\_UserPrivacy\_Set Response to LMF. The message includes the UE Privacy Setting. + - The LMF invokes the Namf\_Communication\_N1N2MessageTransfer service operation towards the AMF to send Accepted Privacy Setting to the AMF. The Accepted Privacy Setting is a "UE-LMF" protocol message, and includes the UE Privacy Setting accepted by network. + - The AMF forwards the Accepted Privacy Setting to the UE in a NAS transport message. + +### 6.7.3.2 Privacy Verification + +Same as that of solution 6, please see clause 6.6.3. + +### 6.7.3.3 Service of GMLC and PPR + +Same as that of solution 6, please see clause 6.6.3. + +## 6.7.4 Impacts on existing entities and interfaces + +Impacted entities: + +- UE provides privacy setting to LMF, by using "UE-LMF" protocol. +- AMF provides "UE-LMF" protocol message transfer between UE and LMF. +- LMF: support "UE-LMF" protocol: + - Receive privacy setting from UE. + - Send the UE provided privacy setting to GMLC, receive updated setting from GMLC, and provide it to UE. +- PPR decides the privacy setting based on UE provided setting and operator policy, and provides it to LMF. +- GMLC receives UE privacy setting profile from PPR and performs privacy check based on the setting. + +Impacted interfaces: + +- N1, interface between LMF and GMLC, interface between PPR and GMLC are impacted. + +## 6.7.5 Evaluation + +**Editor's note:** This clause provides an evaluation of the solution. + +# 6.8 Solution 8: slice dependent LMF selection + +## 6.8.1 Introduction + +This solution is to address Key issue 5 "slice dependent location service". + +## 6.8.2 Functional Description + +To address the specific position service requirements, one separate LMF serves the position service for this network slice. When UEs which are allowed to this network slice access the network, the correct LMF is selected by AMF to serve these UEs when UEs register network. Normally one UE is only served by one LMF. + +## 6.8.3 Procedures + +The LMF selection procedure is indicated in the figure below: + + + +``` + +sequenceDiagram + participant UE + participant AMF + participant LMF + participant UDM + + Note right of AMF: 2. Step 4 to step 14 of Registration procedure in TS23.502 Figure 4.2.2.2.2-1 + + UE->>AMF: 1. Registration Request(LCS enabled indication) + Note right of AMF: 3. LMF selection + AMF->>LMF: 4.N_lmf_LCService_Activate Request(SUPI) + Note right of LMF: 5. UDM discovery + LMF->>UDM: 6. Nudm_SDM_Get request,response + LMF->>AMF: 7. N_lmf_LCService_Activate Response(Result indication) + LMF->>UDM: 8. Nudm_UE CM_Registration + Note right of AMF: 9. Step 15 to step 20 of Registration procedure in TS23.502 Figure 4.2.2.2.2-1 + AMF->>UE: 10. Registration Accept + +``` + +Sequence diagram illustrating LMF selection during UE registration. The diagram shows interactions between UE, AMF, LMF, and UDM. The process starts with a Registration Request from UE to AMF. The AMF then performs steps 4 to 14 of the registration procedure. Next, LMF selection occurs. The AMF sends an N\_lmf\_LCService\_Activate Request to the LMF. The LMF performs UDM discovery and sends a Nudm\_SDM\_Get request to the UDM. The UDM responds, and the LMF sends an N\_lmf\_LCService\_Activate Response to the AMF. The LMF also performs Nudm\_UE CM\_Registration. Finally, the AMF performs steps 15 to 20 of the registration procedure and sends a Registration Accept to the UE. + +**Figure 6.3.8-1: LMF selection during UE registration** + +1. UE sends Registration Request including LCS enabled indication. +2. AMF performs the related UE Registration procedure as specified in TS 23.502 [5]. +3. AMF discovers the LMF serving this UE via NRF. In order to discover the correct LMF serving that UE is allowed to access, AMF provides the corresponding S-NSSAI to NRF when discovering LMF. The position related subscription data may include the S-NSSAI for position service. +4. AMF request the selected LMF to activate location service for the UE. +5. LMF discovers and selects the UDM. +6. LMF request location related subscription data and context data from UDM, including privacy profile, the provisioning information of valid LDR service request that application functions ever requested. +7. LMF responds to AMF whether the location service for the UE is activated. +8. LMF performs NF registration towards UDM. +- 9-10. AMF performs the related UE Registration procedure as specified in TS 23.502 [5]. + +## 6.8.4 Impacts on existing entities and interfaces + +The solution impact the following network functions: + +- AMF needs to discover and select the correct LMF serving the network slice. + +## 6.8.5 Evaluation + +*Editor's note: This clause provides an evaluation of the solution.* + +# 6.9 Solution 9: Solution for position service exposure + +## 6.9.1 Introduction + +This solution address Key Issue 7 "Position service exposure" and Key Issue 3: "Support of low latency LCS" as well as at it secures roaming with EPS. + +## 6.9.2 Functional Description + +For external exposure the NEF receives location service request from an AF and sends the corresponding request to GMLC or LCS client sends a location request to GMLC. + +For internal exposure the requesting NF send a request to GMLC. To enable location privacy GMLC performs privacy check according to a privacy profile. The privacy profile is, depending on chosen solution, provisioned in GMLC, or downloaded from UDM. If the requested location service is allowed GMLC performs an 5GC MT-LR procedure. + +For roaming there will be an instance of GMLC in Home PLMN acting as H-GMLC and one instance in Visited PLMN acting as V-GMLC. The H-GMLC will retrieve the address of the V-GMLC from the UDM or HSS. + +### 6.9.2.1 Architecture + +The non-roaming LCS architecture is indicated in the figure below: + + + +``` + +graph TD + AF[AF] --- NEF[NEF] + NEF --- Nnef((Nnef)) + NF[NF] --- Namf1((Namf)) + LMF[LMF] --- Nlmf((Nlmf)) + UDM[UDM] --- Nudm((Nudm)) + Nnef --- SBI[Service Based Interface] + Namf1 --- SBI + Nlmf --- SBI + Nudm --- SBI + SBI --- Namf2((Namf)) + Namf2 --- AMF[AMF] + AMF --- N2((N2)) + N2 --- NG-RAN[NG-RAN] + NG-RAN --- UE[UE] + SBI --- Ngmlc((Ngmlc)) + Ngmlc --- GMLC[GMLC] + GMLC --- Le((Le)) + Le --- LCS-Client((LCS Client)) + +``` + +Figure 6.9.2.1-1: non-roaming LCS reference architecture diagram. The diagram shows a central Service Based Interface (SBI) bus. Above the bus, the AF (Application Function) connects to the NEF (Network Exposure Function). The NEF connects to the bus via the Nnef service interface. The NF (Network Function) connects to the bus via the Namf service interface. The LMF (Location Management Function) connects to the bus via the Nlmf service interface. The UDM (Unified Data Management) connects to the bus via the Nudm service interface. Below the bus, the AMF (Access and Management Function) connects to the bus via the Namf service interface. The AMF connects to the NG-RAN (Next Generation Radio Access Network) via the N2 interface. The NG-RAN connects to the UE (User Equipment). The GMLC (Gateway Mobile Location Centre) connects to the bus via the Ngmlc service interface. The GMLC connects to the LCS Client (Location Service Client) via the Le interface. + +**Figure 6.9.2.1-1: non-roaming LCS reference architecture** + +The roaming LCS architecture is indicated in the figures below: + + + +This diagram illustrates the Roaming LCS reference architecture with a 5GC VPLMN. It is divided into two main sections by a vertical dashed line: VPLMN on the left and EPC HPLMN on the right. In the VPLMN, a UE is connected to an NG-RAN, which is connected to an AMF via an N2 interface. The AMF is connected to an LMF via an Namf interface and to a V-GMLC via an Ngmlc interface. The LMF is connected to a Network Function (NF) stack via an Nlmf interface. The NF stack consists of an AF, a NEF (connected to the AF), and a UDM (connected to the NEF). The NEF is connected to the H-GMLC in the EPC HPLMN via an Nnef interface. The V-GMLC in the VPLMN is connected to the H-GMLC in the EPC HPLMN via an Lr interface. In the EPC HPLMN, the H-GMLC is connected to the UDM via an Nudm interface and to an LCS Client via an Le interface. The H-GMLC is also connected to an HSS. The 5GC HPLMN label is placed above the EPC HPLMN section. + +Roaming LCS reference architecture with 5GC VPLMN diagram + +Figure 6.9.2.1-2: Roaming LCS reference architecture with 5GC VPLMN + + + +This diagram illustrates the Roaming LCS reference architecture with an EPC VPLMN. It is divided into two main sections by a vertical dashed line: EPC VPLMN on the left and 5GC HPLMN on the right. In the EPC VPLMN, a V-GMLC is shown. In the 5GC HPLMN, an AF is connected to a NEF, which is connected to a UDM. The NEF is connected to an H-GMLC via an Nnef interface, and the UDM is connected to the H-GMLC via an Nudm interface. The V-GMLC in the EPC VPLMN is connected to the H-GMLC in the 5GC HPLMN via an Lr interface. The H-GMLC is connected to an LCS Client via an Le interface. + +Roaming LCS reference architecture with EPC VPLMN diagram + +Figure 6.9.2.1-3: Roaming LCS reference architecture with EPC VPLMN + +### 6.9.3 Procedures + +#### 6.9.3.1 Location Service exposure procedure, non-roaming + +The flow below indicates the procedure where an external AF, internal NF or LCS Client requests Location Service: + + + +``` + +sequenceDiagram + participant AF + participant LCS Client + participant NEF + participant NF + participant GMLC + participant UDM + participant AMF + participant LMF + + Note left of AF: 1a. Location Service Request + AF->>NEF: 1a. Location Service Request + Note left of LCS Client: 1b. LCS Service Request + LCS Client->>GMLC: 1b. LCS Service Request + Note left of NF: 1c. Ngmlc_ProvideLocation Request + NF->>GMLC: 1c. Ngmlc_ProvideLocation Request + Note right of GMLC: 2. Ngmlc_ProvideLocation Request + GMLC->>NF: 2. Ngmlc_ProvideLocation Request + Note right of NF: 3. Privacy check + NF->>GMLC: 3. Privacy check + Note right of GMLC: 4. 5GC MT-LR procedure + GMLC->>UDM: 4. 5GC MT-LR procedure + UDM->>AMF: 4. 5GC MT-LR procedure + AMF->>LMF: 4. 5GC MT-LR procedure + LMF->>AMF: 4. 5GC MT-LR procedure + AMF->>UDM: 4. 5GC MT-LR procedure + UDM->>GMLC: 4. 5GC MT-LR procedure + Note left of GMLC: 5a. Ngmlc_ProvideLocation Response + GMLC->>NEF: 5a. Ngmlc_ProvideLocation Response + Note left of GMLC: 5b. LCS Service Response + GMLC->>LCS Client: 5b. LCS Service Response + Note left of GMLC: 5c. Ngmlc_ProvideLocation Response + GMLC->>NF: 5c. Ngmlc_ProvideLocation Response + Note left of NEF: 6. Location Service Response + NEF->>AF: 6. Location Service Response + +``` + +Sequence diagram for Location Service exposure, non-roaming. Lifelines: AF, LCS Client, NEF, NF, GMLC, UDM, AMF, LMF. The diagram shows three main request paths: 1a (AF to NEF), 1b (LCS Client to GMLC), and 1c (NF to GMLC). All paths lead to a common 5GC MT-LR procedure involving the GMLC, UDM, AMF, and LMF. Responses are then returned along the respective request paths: 5a (GMLC to NEF), 5b (GMLC to LCS Client), and 5c (GMLC to NF). Finally, a Location Service Response is sent from the NEF to the AF (step 6). + +**Figure 6.9.3.1-1: Location Service exposure, non-roaming** + +- 1a. For external exposure via NEF, the AF will request location event exposure from the NEF by sending a Location Service Request message to the NEF including UE identity and the Location service type. +- 1b. For external exposure via GMLC, the LCS Client sends a LCS Service Request message to the GMLC including UE identity and the Location service type. +- 1c. For internal exposure, the NF selects an GMLC e.g. by using the NRF service. The NF sends an Ngmlc\_ProvideLocation Request message to the GMLC. +2. If step 1a has occurred, the NEF selects an GMLC e.g. by using the NRF service. The NEF sends an Ngmlc\_ProvideLocation Request message to the GMLC. +3. The GMLC performs privacy check based on privacy profile related to the target UE. +4. The GMLC performs a 5GC MT-LR procedure. +- 5a. If step 1a has occurred, the GMLC sends an Ngmlc\_ProvideLocation Response message to the NEF. The response includes location estimate or else an error indication. +- 5b. If step 1b has occurred, the GMLC sends an LCS Service Response to the LCS Client. The response includes location estimate or else an error indication. +- 5c. If step 1c has occurred, the GMLC sends an Ngmlc\_ProvideLocation Response message to the NF. The response includes location estimate or else an error indication. +6. If step 5c has occurred, the NEF sends Location Service Response to the AF. + +### 6.9.3.2 Location Service exposure procedure, roaming + +The flow below indicates the procedure where an external AF, internal NF or LCS Client requests Location Service: + + + +``` + +sequenceDiagram + participant AF + participant LCS Client + participant NEF + participant NF + participant H-GMLC + participant HSS + participant UDM + participant V-GMLC + participant 5GC + participant MME + + Note over AF, H-GMLC: 1a. Steps 1a - 2 of figure 6.x.3.1-1 + Note over NF, H-GMLC: 2. Privacy check + H-GMLC->>UDM: 3. Nudm_UECM_Get Request + UDM-->>H-GMLC: 4. Nudm_UECM_Get Response + Note over LCS Client, HSS: 1b. Procedures in EPC + H-GMLC->>V-GMLC: 5a. Ngmlc_ProvideLocation Request + H-GMLC->>V-GMLC: 5b. LCS Service Request + Note over V-GMLC, 5GC: 6a. 5GC MT-LR procedure + Note over V-GMLC, MME: 6b. EPC MT-LR procedure + V-GMLC-->>H-GMLC: 7a. Ngmlc_ProvideLocation Response + V-GMLC-->>H-GMLC: 7b. LCS Service Response + Note over AF, NF: 8a. Steps 5a - 6 of figure 6.x.3.1-1 + Note over LCS Client, HSS: 8b. Procedure is EPC + +``` + +Sequence diagram for Location Service exposure, roaming. Lifelines: AF, LCS Client, NEF, NF, H-GMLC, HSS, UDM, V-GMLC, 5GC, MME. The diagram shows a sequence of messages between these entities, with steps 1a-2, 2, 3, 4, 1b, 5a, 5b, 6a, 6b, 7a, 7b, 8a, and 8b. Steps 1a-2 and 8a are grouped as 'Steps 1a - 2 of figure 6.x.3.1-1' and 'Steps 5a - 6 of figure 6.x.3.1-1' respectively. Steps 1b and 8b are grouped as 'Procedures in EPC' and 'Procedure is EPC' respectively. Steps 6a and 6b are grouped as '5GC MT-LR procedure' and 'EPC MT-LR procedure' respectively. + +**Figure 6.9.3.2-1: Location Service exposure, roaming** + +- 1a. If the Home PLMN is an 5GC step 1a and 2 or step 1b or step 1c of Figure 6.9.3.1-1 are performed. +- 1b. If the Home PLMN is an EPC the procedures corresponding to step 1a, 2, 3 and 4 are performed.2. If step 1a has occurred, The H-GMLC performs privacy check based on privacy profile related to the target UE. +3. If step 1a has occurred, the H-GMLC invokes the Nudm\_UECM\_Get service operation towards the home UDM of the target UE with the GPSI or SUPI of the UE. +4. The UDM returns the V-GMLC address of the VPLMN. +- 5a. If both Home PLMN and Visited PLMN are 5GC, the H-GMLC sends an Ngmlc\_ProvideLocation Request message to the V-GMLC. +- 5b. If one of Home PLMN and Visited PLMN are EPC, the H-GMLC sends an LCS Service Request message to the V-GMLC. +- 6a. If the Visited PLMN is an 5GC the V-GMLC performs e 5GC MT-LR procedure. +- 6b. If the Visited PLMN is an EPC the V-GMLC performs e EPC MT-LR procedure. +- 7a. If step 5a was performed the V-GMLC sends an Ngmlc\_ProvideLocation Response message to the H-GMLC. The response includes location estimate or else an error indication. + +7b. If step 5b was performed the V-GMLC sends an LCS Service Response message to the H-GMLC. The response includes location estimate or else an error indication. + +8a. If the Home PLMN is an 5GC steps 5a and 6 or step 5b or step 5c of Figure 6.9.3.1-1 are performed. + +8b. If the Home PLMN is an EPC the procedure corresponding to step 8a are performed. + +### 6.9.3.3 Optimized Deferred Location Service exposure procedure + +The flow below indicates the procedure when an NF requests Location Deferred Service: + + + +``` + +sequenceDiagram + participant NF + participant GMLC + participant UDM + participant 5GC + participant UE + + NF->>GMLC: 1. Ngmlc_ProvideLocation Request + GMLC->>UDM: 2. Nudm_UECM_Get Request + UDM-->>GMLC: 3. Nudm_UECM_Get Response + Note over GMLC: 4. Privacy check + GMLC->>5GC: 5. Nxxx_Location_ProvideLocation Request + Note over 5GC,UE: 6. Trigger activation + 5GC->>GMLC: 7. Nxxx_Location_ProvideLocation Response + GMLC-->>NF: 8. Ngmlc_ProvideLocation Response + Note over 5GC,UE: 9. Event detected + 5GC->>NF: 10. Nxxx_Location_EventNotify + NF-->>GMLC: 11. Ngmlc_ProvideLocation Request (terminate) + Note over GMLC: 12. Privacy terminated + GMLC->>5GC: 13. Nxxx_Location_ProvideLocation Request (terminate) + Note over 5GC,UE: 14. Trigger deactivated + 5GC->>GMLC: 15. Nxxx_Location_ProvideLocation Response + GMLC-->>NF: 16. Ngmlc_ProvideLocation Response + +``` + +Sequence diagram for Optimized Deferred Location Service exposure procedure. Lifelines: NF, GMLC, UDM, 5GC, UE. The sequence shows the request, privacy check, activation, event detection, and termination steps. + +**Figure 6.9.3.3-1: Optimized Deferred Location Service exposure** + +1. The requesting NF (e.g. an internal AF or NEF in case of an external AF) selects an GMLC e.g. by using the NRF service. The NF invokes an Ngmlc\_ProvideLocation operation towards the GMLC indicating request for deferred location. +2. The H-GMLC invokes the Nudm\_UECM\_Get service operation towards the home UDM of the target UE with the GPSI or SUPI of the UE. +3. The UDM returns the address serving location NF. +4. The GMLC performs privacy check based on privacy profile related to the target UE. + +5. The GMLC invokes an Nxxx\_Location\_ProvideLocation service operation towards serving NF indicating Deferred service and the NF that is to receive the location information. +6. The location trigger is activated. This may include communication with the UE for the case the trigger resides in the UE.7. The serving NF returns acknowledgement of the operation to the GMLC. +8. The GMLC acknowledge the operation to the requesting NF. +9. The trigger event is detected. This may occur in the UE and will in such case include communication with the UE. +10. The serving NF invokes the Nxxx\_Location\_EventNotify operation towards the recipient NF including any requested location information. +11. The initiating NF may optionally explicitly terminate the Deferred request. The NF then invokes an Ngmlc\_ProvideLocation operation the GMLC indicating termination of a deferred location service. +12. The GMLC may at any time determine that the privacy conditions for allowing delivery of location are no longer valid and decides to terminate the Deferred service. +13. If step 11 or 12 has occurred, the GMLC invokes an Nxxx\_Location\_ProvideLocation service operation towards serving NF indicating termination of a Deferred service. +14. The serving NF acknowledge termination of the operation to the GMLC. +15. If step 11 has occurred, the GMLC acknowledge termination of the operation to the requesting NF. + +**Editor's note:** The NF designator "Nxxx" will be replaced by "Namf" or "Nlmf" once architecture option has been selected. + +## 6.9.4 Impacts on existing entities and interfaces + +**Editor's note:** This clause describes impacts to existing entities and interfaces. + +### NEF: + +- Expose Location Reporting" event to AF including authorization by the network of the AF to receive the requested information. +- Selection of source of location information. +- Interface with GMLC to retrieve location information. + +### GMLC: + +- Expose a service-based interface on which other NF can request location information. +- If acting as H-GMLC, authorize exposure of location information based on the subscriber privacy profile. +- If acting as V-GMLC, authorize exposure of location information based on operator policy. +- If acting as H-GMLC, request location information from V-GMLC. + +### UDM: + +- Retrieve address of V-GMLC from Visited PLMN during registration procedure and expose this information to GMLC. + +**Editor's note:** Impacts on AMF and LMF is FFS. + +## 6.9.5 Evaluation + +**Editor's note:** This clause provides an evaluation of the solution. + +## 6.10 Solution 10: Solution for LDR type service exposure via NEF + +### 6.10.1 Introduction + +This solution is to address Key Issue 7 "Position service exposure" and Key issue 4 "Reduce overhead for repetitive non-successful privacy verification". + +## 6.10.2 Functional Description + +The supported location service exposure includes LIR and LDR type service. + +NEF receive location service request from applications and send the corresponding request to LMF. To support interworking scenario that 5G UE resides in 4G, NEF sends location request to the 4G GMLC to get UE location via the position mechanism specified for EPC when NEF inquires UDM/HSS and knows the UE resides on 4G. To enable location privacy, UDM maintains privacy profile, and LMF performs privacy check according to privacy profile. If the requested LDR service is allowed, LMF stores the allowed location service information to UDM. + +To allow the users to provide the expected privacy provisioning information, the UE may send the expected privacy provisioning information to LMF via N1 message. LMF stores the privacy provisioning information from the UE, and further it determine whether the location service request from applications is allowed based on the maintained privacy provisioning information. + +### 6.10.2.1 Architecture + +The non-roaming LCS architecture is indicated in the figure below: + + + +``` + +graph TD + subgraph SBI [Service Based Interface] + direction LR + Nnef --- Nlmf --- Nudm --- Namf --- Nucf --- Ngmlc + end + + NEF --- Nnef + LMF --- Nlmf + UDM --- Nudm + AMF --- Namf + UCF --- Nucf + GMLC --- Ngmlc + + AMF ---|N2| NG-RAN + NG-RAN --- UE + NG-RAN ---|N3| UPF + UCF ---|N6| UPF + GMLC ---|Le| LCS_Client((LCS Client)) + GMLC --- LRF + LRF ---|Le| LCS_Client + +``` + +Figure 6.10.2-1: non-roaming LCS reference architecture diagram showing network functions NEF, LMF, UDM, AMF, UCF, GMLC connected to a service-based interface bus. Lower level components include UE, NG-RAN, UPF, LRF, and LCS Client with various point-to-point interfaces (N2, N3, N6, Le). + +**Figure 6.10.2-1 non-roaming LCS reference architecture** + +The roaming LCS architecture is indicated in the figure below: + + + +The diagram illustrates the roaming LCS reference architecture, divided into two main sections by a vertical dashed line: VPLMN (Visited PLMN) on the left and HPLMN (Home PLMN) on the right. + +**VPLMN (Left Side):** + +- UE** (User Equipment) is connected to **NG-RAN**. +- NG-RAN** is connected to **AMF** via the **N2** interface and to **UPF** via the **N3** interface. +- AMF** is connected to **V-LMF** via the **Nlmf** interface. +- AMF** is also connected to **UCF** via the **Nucf** interface. +- UCF** is connected to **GMMLC** via the **Ngmlc** interface. +- GMMLC** is connected to **UPF** via the **N6** interface. +- UPF** is connected to **NEF** via the **Nnef** interface. + +**HPLMN (Right Side):** + +- NEF** is connected to **H-LMF** via the **Nnef** interface. +- H-LMF** is connected to **GMMLC** via the **Ngmlc** interface. +- GMMLC** is connected to **UDM** via the **Nudm** interface. +- GMMLC** is also connected to **LRF** via the **Le** interface. +- LRF** is connected to **LCS Client** via the **Le** interface. + +Roaming LCS reference architecture diagram showing VPLMN and HPLMN components and their interconnections. + +Figure 6.10.2-2 roaming LCS reference architecture + +### 6.10.3 Procedures + +#### 6.10.3.1 LDR type service exposure procedure + +The flow below indicates the procedure that application requests LDR type service: + + + +``` + +sequenceDiagram + participant App + participant NEF + participant LMF + participant UDM + + App->>NEF: 1. Location Service Request(Public UE ID, LCS service type and description) + NEF-->>UDM: 2. Nudm_UE CM_Get + NEF->>LMF: 3. Nlmf_LCS_Create Request(SUPI, App ID, LCS type ID and description information, ) + Note over LMF: 4. Privacy check + LMF-->>NEF: 5. Nlmf_LCS_Create Response(Result indication) + NEF->>App: 6. Location Service Response (result indication) + LMF->>UDM: 7. Nudm_UDM_Create request(SUPI, the allowed location service information) + UDM-->>LMF: 8. Nudm_UDM_Create response + Note over LMF: 9. Activate location service request + +``` + +The sequence diagram illustrates the interaction for LDR type service exposure. It begins with the App sending a 'Location Service Request' to the NEF. The NEF then performs a 'Nudm\_UE CM\_Get' operation with the UDM. Next, the NEF sends an 'Nlmf\_LCS\_Create Request' to the LMF. The LMF performs a 'Privacy check' and then sends an 'Nlmf\_LCS\_Create Response' back to the NEF. The NEF sends a 'Location Service Response' to the App. The LMF then sends a 'Nudm\_UDM\_Create request' to the UDM, which responds with a 'Nudm\_UDM\_Create response'. Finally, the LMF performs an 'Activate location service request'. + +Sequence diagram for LDR type service exposure showing interactions between App, NEF, LMF, and UDM. + +**Figure 6.10.3.1-1: LDR type service exposure** + +1. In case that e.g. one application needs new location service, the application sends Location Service Request message to the NEF including GPSI, the LCS type, and the LCS service information which includes the related parameters. One example is the application requests the periodic location reporting for one UE, i.e. the location reporting is 5 minutes. LCS Type indicates this is a Location Deferred Request. +2. NEF determines the serving LMF via Nudm\_UE CM\_Get service operation. If the target UE does not register network and there is no serving LMF, NEF may discover and select one LMF via NF discovery to handle the location service request. To support interworking between 5GC and EPC, NEF as LCS client sends location service request to the 4G GMLC to get UE location via the position mechanism specified for EPC when NEF inquires UDM/HSS and knows the UE is residing in 4G. +3. NEF requests Nlmf\_LCS\_Create service operation from the serving LMF, and SUPI of the target UE, Application ID, LCS Type and related location service information are included in request message. +4. The serving LMF performs privacy check based on privacy profile related to the target UE. +5. The serving LMF respond to NEF whether the request is allowed. +6. NEF notice the result to the application via Location Service Response. +7. To store the corresponding location service information stored in UDM, the LMF requests Nudm\_UDM\_Create service operation from UDM including SUPI, Application ID, LCS type, the location service information. +8. UDM stores the corresponding location service information including SUPI, Application ID, LCS type, and then it responds to LMF via Nudm\_UDM\_Create response message. + +9. LMF activate the requested location service. For UE roaming in 5GC, H-LMF in HPLMN sends the authorized location service request to V-LMF in VPLMN, and V-LMF activates the location service request for this UE. When reporting UE location related to location service request, V-LMF sends UE location information to H-LMF, and H-LMF further sends UE location report to NEF. + +### 6.10.3.2 Application request to update LDR type service + +The flow below indicates the procedure that application requests to update the location service: + + + +``` + +sequenceDiagram + participant App + participant NEF + participant LMF + participant UDM + + Note right of LMF: 4. Privacy check + Note right of LMF: 9. Activate updated location service + + App->>NEF: 1. Location Service Request(Public UE ID, LCS service type, update service information) + NEF-->>UDM: 2. Nudm_UE CM_Get + NEF->>LMF: 3.Nlmf_LCS_Update Request(SUPI, App ID, LCS type ID, update service information ) + LMF-->>NEF: 5.Nlmf_LCService Response(Result indication) + NEF->>App: 6. Location Service Response (result indication) + LMF->>UDM: 7. Nudm_UDM_Update request(SUPI, the location service information) + UDM-->>LMF: 8. Nudm_UDM_Update response + +``` + +The sequence diagram illustrates the procedure for updating an LDR type service. It involves four main participants: App, NEF, LMF, and UDM. The process starts with the App sending a 'Location Service Request' to the NEF. The NEF then sends a 'Nudm\_UE CM\_Get' request to the UDM. Next, the NEF sends an 'Nlmf\_LCS\_Update Request' to the LMF. The LMF performs a 'Privacy check' and then sends an 'Nlmf\_LCService Response' back to the NEF. The NEF then sends a 'Location Service Response' to the App. The LMF also sends a 'Nudm\_UDM\_Update request' to the UDM, which responds with a 'Nudm\_UDM\_Update response'. Finally, the LMF performs the 'Activate updated location service' step. + +Sequence diagram for Update LDR type service showing interactions between App, NEF, LMF, and UDM. + +Figure 6.10.3.2-1: Update LDR type service + +1. In case that e.g. one application needs to update the location service which was requested, the application sends Location Service Request message to the NEF including GPSI, the LCS type, and the updated LCS service information. One example is the application expects to update the periodic location reporting time for one UE. LCS Type indicates this is a Location Deferred Request. +2. NEF determines the serving LMF via Nudm\_UE CM\_Get service operation. +3. NEF requests Nlmf\_LCS\_Update service operation from the serving LMF, and SUPI of the target UE, Application ID, LCS Type and updated location service information are included in request message. LCS Type indicates this is a Location Deferred Request. +4. The serving LMF performs privacy check based on privacy profile related to the target UE. +5. The serving LMF responds to NEF whether the request is allowed. +6. NEF notices the result to the application via Location Service Response. + +7. To update the corresponding location service information stored in UDM, the LMF requests Nudm\_UDM\_Update service operation from UDM including SUPI, Application ID, LCS type, the location service information. +8. UDM determines and update the corresponding location service information according to SUPI, Application ID, LCS type, and then it responds to LMF via Nudm\_UDM\_Update response message. +9. LMF activates the updated location service. + +### 6.10.3.3 Application request to cancel LDR type service + +The flow below indicates the procedure that application requests to cancel the location service: + + + +``` + +sequenceDiagram + participant App + participant NEF + participant LMF + participant UDM + Note right of LMF: 4. Authorize service request + Note right of LMF: 9. Disable the deleted location service + + App->>NEF: 1. Location Service Request(Public UE ID, LCS service type, cancel service indication) + NEF-->>UDM: 2. Nudm_UE CM_Get + NEF->>LMF: 3. Nlmf_LCS_Delete Request(SUPI, App ID, LCS type ID) + LMF->>NEF: 5. Nlmf_LCS_Delete Response(Result indication) + NEF->>App: 6. Location Service Response(result indication) + LMF->>UDM: 7. Nudm_UDM_Delete request(SUPI, the location service information) + UDM->>LMF: 8. Nudm_UDM_Delete response + +``` + +Sequence diagram for canceling LDR type service exposure. Lifelines: App, NEF, LMF, UDM. The process involves a request from App to NEF, a lookup by NEF to UDM, a delete request from NEF to LMF, authorization by LMF, a response from LMF to NEF, a response from NEF to App, a delete request from LMF to UDM, a response from UDM to LMF, and finally disabling the service by LMF. + +**Figure 6.10.3.3-1: Cancel LDR type service exposure** + +1. In case that e.g. one application needs to cancel the location service which was requested, the application sends Location Service Request message to the NEF including GPSI, the LCS type that request to cancel, and the indication on cancel service. +2. NEF determines the serving LMF via Nudm\_UE CM\_Get service operation. +3. NEF requests Nlmf\_LCS\_Delete service operation from the serving LMF, and SUPI of the target UE, Application ID and LCS Type are included in request message. +4. The serving LMF authorizes the service request. +5. The serving LMF responds to NEF whether the request is allowed. +6. NEF notices the result to the application via Location Service Response. + +7. To delete the corresponding location service information stored in UDM, the LMF requests Nudm\_UDM\_Delete service operation from UDM including SUPI, Application ID, LCS type. +8. UDM determines and deletes the corresponding location service information according to SUPI, Application ID, LCS type, and then it responds to LMF via Nudm\_UDM\_Delete response message. +9. LMF disable the location service that was cancelled. + +### 6.10.3.4 UE provides the expected location privacy provisioning to the network + +The flow below indicates the procedure that UE provides the expected location privacy provisioning to the network: + + + +``` + +sequenceDiagram + participant UE + participant AMF + participant LMF + UE->>AMF: 1. LCS Request(UE ID, LCS privacy indication) + AMF->>LMF: 2. Namf_Communication_N1MessageNotify (UE ID, N1 LCS Request) + Note over LMF: 3. Authorize service request + LMF->>AMF: 4. Namf_Communication_N1N2MessageTransfer (UE ID, N1 LCS Response) + AMF->>UE: 5. LCS Response (Result indication) + +``` + +Sequence diagram showing the procedure for UE providing location privacy information to the network. The diagram involves three entities: UE, AMF, and LMF. The sequence of messages is: 1. UE sends an LCS Request (UE ID, LCS privacy indication) to AMF. 2. AMF sends a Namf\_Communication\_N1MessageNotify (UE ID, N1 LCS Request) to LMF. 3. LMF performs an internal 'Authorize service request'. 4. LMF sends a Namf\_Communication\_N1N2MessageTransfer (UE ID, N1 LCS Response) to AMF. 5. AMF sends an LCS Response (Result indication) to UE. + +**Figure 6.10.3.4-1: UE provides Location privacy information to LMF** + +1. In case that e.g. the LCS privacy configuration information of the UE is changed by the UE user, UE sends N1 LCS request message including the updated LCS privacy information to AMF. LCS privacy information may indicate whether the exposure of UE location to applications is allowed. +2. AMF determines the serving LMF for the UE, and sends the N1 LCS request message to the serving LMF via Namf\_Communication\_N1MessageNotify service operation. +3. The serving LMF authorizes whether the LCS request from the UE is allowed according to UE LCS related subscription data and operator policy. +4. The serving LMF sends Namf\_Communication\_N1N2MessageTransfer request message including N1 LCS Response message to AMF to request AMF send N1 LCS Response to the UE, and LMF also store the LCS privacy information from the UE if the request is allowed. +5. The AMF sends N1 LCS Response to UE. + +### 6.10.4 Impacts on existing entities and interfaces + +The solution impact the following network functions: + +- To enable location service exposure including LIR and LDR type towards applications, NEF needs to support the related location exposure service and the corresponding service interface, and NEF also needs to interact with LMF to realize the location service required by the authorized applications. NEF sends location request to the 4G + +GMLC to get UE location via the position mechanism specified for EPC when NEF inquires UDM/HSS and knows the UE resides on 4G. + +- UDM integrates the functionality for subscriber privacy profile, including: maintain subscriber privacy profile and provides the subscriber privacy profile to the allowed service consumer i.e. LMF. UDM also needs to store the context for the allowed LDR type service request. +- LMF performs privacy check according to privacy profile. + +## 6.10.5 Evaluation + +The solution addresses Key Issue 7 "Position service exposure" and Key issue 4 "Reduce overhead for repetitive non-successful privacy verification". The benefits include: + +- The 5G system exposes location service to applications via general network service exposure framework, and the supported location service can include LDR and LIR type service. It avoids that applications need to support the legacy reference point with GMLC to obtain location service, and thus it provides the simple and efficient approach for location service exposure; +- Support the unified data management via UDM, including: subscriber privacy profile and avoid introducing one separate network function such as R-15 to handle subscriber privacy profile, and the authorized information of LDR type service request. + +# 6.11 Solution 11: Solution for Location Service exposure to NG-RAN + +## 6.11.1 Introduction + +This solution is to address Key Issue 1 "Enhancements to LCS architecture" and Key Issue 7 "Position service exposure" by adding NG-RAN as a potential internal LCS Client (i.e. internal consumer of Location Service). Providing LCS Service to RAN benefits use cases such as "QoS verification" and "Coverage optimization" as described in TR 36.880 [25] and in addition may be used by RRM procedures. + +It is assumed that the NG-RAN, as an internal LCS client, is always authorized to use the LCS service to obtain the target UE location estimation, thus no privacy verification and LCS service authorization are required for requests initiated by the NG-RAN. + +## 6.11.2 Functional Description + +This procedure is used by an NG-RAN to request the AMF to report the current the UE location when the target UE is in CM-CONNECTED state. + +## 6.11.3 Procedures + +### 6.11.3.1 NG-RAN Location exposure procedure + +The flow below indicates the procedure where NG-RAN requests Location service: + + + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant AMF + participant LMF + Note right of UE: 1. UE in CM CONNECTED mode + NG-RAN->>AMF: 2. RAN Initiated Location Request + AMF->>LMF: 3. Nlmf_Location_DetermineLocation Request + Note right of UE: 4. UE positioning + LMF->>AMF: 5. Nlmf_Location_DetermineLocation Response + AMF->>NG-RAN: 6. RAN Initiated Location Response + +``` + +Sequence diagram illustrating the location service exposure to NG-RAN. The diagram shows four lifelines: UE, NG-RAN, AMF, and LMF. The sequence of messages is: 1. UE in CM CONNECTED mode (a state box); 2. RAN Initiated Location Request from NG-RAN to AMF; 3. Nlmf\_Location\_DetermineLocation Request from AMF to LMF; 4. UE positioning (a state box); 5. Nlmf\_Location\_DetermineLocation Response from LMF to AMF; 6. RAN Initiated Location Response from AMF to NG-RAN. + +**Figure 6.11.3.1-1: Location service exposure to NG-RAN** + +1. The UE is in CM CONNECTED mode and the NG-RAN detects the need to get (accurate) UE location. + 2. If NG-RAN doesn't support LM functionality, it sends a RAN Initiated Location Request message to the AMF. The RAN Initiated Location Request message shall, contain the requested location information. The AMF determines the UE for which location is requested using the NGAP context associated with the RAN request. +- Step 3-5 follows Step 6-8 of 5GC-MT-LR Procedure defined in clause 6.14.3.1. +6. The AMF sends RAN Initiated Location Response to the NG-RAN. + +## 6.11.4 Impacts on existing entities and interfaces + +NG-RAN: + +- Need to handle two new messages, "RAN Initiated Location Request" and "RAN Initiated Location Response" on N2 interface. + +AMF: + +- Need to handle two new messages, "RAN Initiated Location Request" and "RAN Initiated Location Response" on N2 interface. + +N2: + +- NGAP protocol need to be extended with a new procedure consisting of two messages with proposed naming "RAN Initiated Location Request" and "RAN Initiated Location Response" respectively. + +## 6.11.5 Evaluation + +**Editor's note:** This clause provides an evaluation of the solution. + +This solution provides an efficient support for RAN Initiated Location Request as only the NG RAN, the AMF and the LMF are involved. + +NOTE: The solution does not assume any permanent UE ID to be provided to the RAN. + +# 6.12 Solution 12: LCS support for non-3GPP access + +## 6.12.1 Introduction + +The solution is intended to address or resolve, partly or completely, the following key issues: + +- Key Issue 1: Enhancement to LCS Architecture. + +- Key Issue 12: LCS support for non-3GPP access. + +## 6.12.2 Functional Description + +### 6.12.2.1 Architecture + + + +Figure 6.12.2-1: Non-roaming reference architecture diagram. The diagram shows a central Service Based Interface (SBI) bus connecting several network functions: UDM (via Nudm), GMLC (via Ngmlc), AMF (via Namf), SMF (via Nsmf), and LMF (via Nlmf). The AMF is connected to a UE (via N1) and an Untrusted Non-3GPP Access (via N2). The Untrusted Non-3GPP Access is connected to an N3IWF (via N3). The N3IWF is connected to a UPF (via N3). The UPF is connected to an SLP (via N6). The GMLC is connected to an LCS Client (via Le). The LMF is connected to an SLP (via Nle). + +**Figure 6.12.2-1: Non-roaming reference architecture** + +Figure 6.12.2-1 is similar to Figure 4.4.4.1-1 in TS 23.501 [4] with the following differences: + +- LRF is removed, because it's not relevant to commercial location services. +- Untrusted Non-3GPP access type is added. +- SUPL Location Platform (SLP) is added. +- The Nle interface between SUPL Location Platform and LMF is added. + +**Editor's note:** Whether the SUPL messages can be sent between the UE and SLP via the 3GPP control plane is FFS. + +If the UE only registered to untrusted non-3GPP access, the following information can be regarded as UE location information: + +- UE local IP address and optionally UDP or TCP source port number, +- BSSID of the attached AP or BSSID of detected AP, +- Civic address and/or geospatial location information. (More details can refer to Note 1 and Note 5 in solution 13.) + +### 6.12.2.2 New Reference points and Service based interfaces + +New Reference points not realized by service based interfaces comprise: + +**NLe:** Reference point between a SLP and an LMF. + +New Service Based Interfaces used by the solution comprise: + +**Nlmf:** Service-based interface exhibited by LMF. + +**Nudm:** Service-based interface exhibited by UDM. + +**Namf:** Service-based interface exhibited by AMF. + +This solution utilize the existing service operations defined in TS 23.502 [5] for the Nlmf, Namf and Nudm service based interfaces. + +For the Nlmf service based interface, one new service operation is added as shown below. + +**Table 6.12.2.2-1: Nlmf Service Operations** + +| Service Name | Service Operations | Operation Semantics | Example Consumer | +|---------------|--------------------|---------------------|------------------| +| Nlmf_Location | EventNotify | Subscribe/Notify | AMF | + +## 6.12.3 Procedures + +### 6.12.3.1 5GC-MT-LR Procedure + +Figure 6.12.3.1-1 illustrates the general network positioning for LCS clients external to the PLMN. In this scenario, it is assumed that the target UE is identified using an SUPI or GPSI. This procedure is applicable to a request from an LCS client for a current location. + + + +``` + +sequenceDiagram + participant External Client + participant GMLC + participant UDM + participant AMF + participant LMF + participant SLP + participant UE + Note left of UE: UE Positioning + External Client->>GMLC: 1. LCS Service Request + GMLC->>UDM: 2. Nudm_UECM_Get Request + UDM-->>GMLC: 3. Nudm_UECM_Get Response + GMLC->>AMF: 4. Namf_Location_ProvideLocation Request + AMF->>LMF: 5. Nlmf_Location_DetermineLocation Request + LMF->>SLP: 6. Location Request + Note left of UE: 7. UE Positioning + SLP-->>LMF: 8. Location Response + LMF-->>AMF: 9. Nlmf_Location_DetermineLocation Response + AMF-->>GMLC: 10. Namf_Location_ProvideLocation Response + GMLC-->>External Client: 11. LCS Service Response + +``` + +Sequence diagram for 5GC Mobile Terminated Location Request for Non-3GPP access (5GC-MT-LR). + +**Figure 6.12.3.1-1: 5GC Mobile Terminated Location Request for Non-3GPP access (5GC-MT-LR)** + +1. The external location services client sends a request to the GMLC for a location for the target UE identified by an GPSI or an SUPI. The request may include the required QoS, Supported GAD shapes and client type. +2. The GMLC invokes a Nudm\_UECM\_Get service operation towards the home UDM of the target UE to be located with the GPSI or SUPI of this UE. +3. The UDM returns the the address of current serving AMF. +4. The GMLC invokes the Namf\_Location\_ProvideLocation service operation towards the AMF to request the current location of the UE. The service operation includes the SUPI, and client type and may include the required QoS and Supported GAD shapes. +5. The AMF selects an LMF based on NRF query or configuration in AMF and invokes the Nlmf\_Location\_DetermineLocation service operation towards the LMF to request the current location of the UE. The service operation includes a LCS Correlation identifier, the access type and the client type and may include the required QoS and Supported GAD shapes. +6. If the access type is Non-3GPP access, the LMF sends the Location Request to SLP. +7. The SLP initiates positioning procedure towards UE. This shall use SUPL procedures based on OMA SUPL (OMA AD SUPL [13], OMA TS ULP [14]). + +8. The SLP sends the Location Response to LMF including the UE location information. +9. The LMF returns the Nlmf\_Location\_DetermineLocation Response towards the AMF to return the current location of the UE. The service operation includes the LCS Correlation identifier, the location estimate, its age and accuracy and may include information about the positioning method. +10. The AMF returns the Namf\_Location\_ProvideLocation Response towards the GMLC to return the current location of the UE. The service operation includes the location estimate, its age and accuracy and may include information about the positioning method. +11. The GMLC sends the location service response to the external location services client. + +### 6.12.3.2 5GC-MO-LR Procedure + +Figure 6.12.3.2-1 illustrates a 5GC Mobile Originated Location Request (5GC-MO-LR) procedure for a UE via non-3GPP access. In this scenario, it is assumed that the target UE is identified using a SUPI. + + + +``` + +sequenceDiagram + participant UE + participant N3IWF + participant UPF + participant SLP + participant LMF + participant AMF + participant GMLC + participant External Client + + Note over UE, N3IWF, UPF: 1. A PDU Session has been established + Note over UE, SLP: 2. Mobile Originated Positioning Procedures + SLP->>LMF: 3. Location information + LMF->>AMF: 4. Nlmf_Location_EventNotify + AMF->>GMLC: 5. Namf_Location_EventNotify + GMLC->>External Client: 6. Location Information + +``` + +Sequence diagram of the 5GC-MO-LR procedure. Lifelines: UE, N3IWF, UPF, SLP, LMF, AMF, GMLC, External Client. The process starts with a PDU session establishment (1) between UE, N3IWF, and UPF. Then, Mobile Originated Positioning Procedures (2) occur between UE and SLP. The SLP sends location information (3) to the LMF. The LMF sends an Nlmf\_Location\_EventNotify (4) to the AMF. The AMF sends a Namf\_Location\_EventNotify (5) to the GMLC. Finally, the GMLC sends location information (6) to the External Client. + +**Figure 6.12.3.2-1: 5GC Mobile Originated Location Request for Non-3GPP access (5GC-MO-LR)** + +1. The UE has established a PDU session with one of UPFs in PLMN via non-3GPP access. +2. The UE initiates positioning procedure by establishing a user plane connection with the SLP and shall use the OMA SUPL mechanism specified by OMA (OMA AD SUPL [13], OMA TS ULP [14]) to transport location related assistance data and location information between the UE and SLP. The UE may receive assistance data and determine its own location and send its location information to the SLP or the UE sends measurement results to the SLP. In case SLP determines the location of the UE, the SLP shall send the location information to the UE. If the UE requests to transfer the location information obtained to external LCS client, the LCS client ID is also included. +3. The SLP sends the Location information to LMF including the UE location information, and the UE identity. +4. If the location information obtained is requested to be transferred to external LCS client by the UE in step 2, the LMF invokes Nlmf\_EventNotify towards AMF. The service operation includes the UE identity, the LCS client ID, the location estimate, and accuracy and may include information about the positioning method. +5. The AMF invokes the Namf\_Location\_EventNotify towards the GMLC to return the current location of the UE. The service operation includes the UE identity, the LCS client ID, the location estimate, and accuracy and may include information about the positioning method. +6. The GMLC provides the UE location estimate and the UE identity to the external location services client. + +## 6.12.4 Impacts on existing entities and interfaces + +### 6.12.4.1 Impacts to UDM + +- GMLC being a new consumer of UDM service operation Nudm\_UECM\_Get. +- New Subscription data type: UE LCS privacy. + +### 6.12.4.2 Impacts to GMLC + +- Capability to invoke Nudm\_UECM\_Get service operation. +- Capability of LCS service request handling based on target UE privacy setting. + +### 6.12.4.3 Impacts to LMF + +- Adding interface between LMF and SLP. +- Capability to get access type within Nlmf\_Location\_DetermineLocation service operation. + +- Adding new service operation Nlmf\_Location\_EventNotify. + +#### 6.12.4.4 Impacts to AMF + +- Capability to send access type when invoking Nlmf\_Location\_DetermineLocation service operation towards LMF. + +#### 6.12.4.5 Impacts to N3IWF + +- Supporting SUPL procedures. + +#### 6.12.4.6 Impacts to UE + +- Supporting SUPL procedures. + +### 6.12.5 Evaluation + +**Editor's note:** This clause provides an evaluation of the solution. + +## 6.13 Solution 13: LCS support for non-3GPP access + +### 6.13.1 Introduction + +The solution intends to resolve the following key issues: + +- Key Issue 12: LCS support for non-3GPP access. +- Key Issue 14: Positioning Access selection for LCS service. + +### 6.13.2 Functional Description + +#### 6.13.2.1 Architecture + +The architectures in this solution can refer to Figure 6.3.2-1 (non-roaming LCS reference architecture) and Figure 6.3.2-2 (roaming LCS reference architecture) in Solution 3 with the following differences: + +- UCF is not shown since CP-based solution doesn't need the user plane function. +- NG-RAN is replaced by 5G-AN which comprises a NG-RAN and/or non-3GPP AN (N3IWF or TNGF) connecting to a 5G core network, the TNGF is defined in TR 23.716 [9] clause 7.1. + +NOTE: For trusted non-3GPP access network, the architecture and procedures are based on the solution described in clause 7.1 of TR 23.716 [9]. + +#### 6.13.2.2 Location information for non-3GPP access + +For the issue of what information can be regarded as location information for non-3GPP access: + +- If the UE only registered to non-3GPP access, following information can be regarded as UE location information: + +**Table 6.13.2-1: Supported UE location information of untrusted non-3GPP access** + +| | Untrusted non-3GPP Access | Trusted non-3GPP Access | +|-----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| UE Side | UE local IP address,
In case of WLAN access, BSSID of the attached AP or BSSID of detected AP,
Civic address and/or geospatial location information (NOTE 1, NOTE 5, NOTE 6). | Same as Untrusted non-3GPP Access | +| N3IWF/TNGF Side | UE local IP address and optionally UDP or TCP source port (NOTE 2) | UE local IP address and optionally UDP or TCP source port (NOTE 2),
Line identifier of the access point to which the UE is attached (NOTE 7) | +| AMF Side | UE local IP address and optionally UDP source port (NOTE 3).
Last known 3GPP access User Location Info (NOTE 4). | UE local IP address and optionally UDP source port (NOTE 3).
Last known 3GPP access User Location Info (NOTE 4).
Line identifier of the access point to which the UE is attached (NOTE 7) | + +NOTE 1: In case of WLAN access, the UE may retrieve its location from a WLAN AP, prior or after association with the AP, requesting the Civic Location ANQP element, the Geospatial Location ANQP element or both as specified in IEEE Std 802.11-2012, using ANQP procedures described in HS2.0 Rel 2 specification. + +NOTE 2: More details can refer to TS 23.501 [4] clause 5.6.2. + +NOTE 3: This location information can be provided by location change event, more details can refer to TS 23.502 [5] clause 5.2.2.3.1. + +NOTE 4: This location information is also named as Last known Cell-Id, more details can refer to TS 23.501 [4] clause 5.6.2. + +NOTE 5: Geospatial location information can be obtained if UE (e.g. laptop) has installed GNSS receiver, i.e. GPS. + +NOTE 6: Some Applications (e.g. Google Map) may map the WiFi AP's BSSID with the geospatial locations obtain through GPS when the UE switch on the GPS and WiFi simultaneously. When another UE detect the same AP, the Application will send the geospatial locations to the UE. Thus the UE obtain the geospatial locations even without switch on the GPS. If the Application map the geospatial locations to civic address, the UE can also obtain the civic address. + +NOTE 7: Since AAA interface exists between TNAP and TNGF in trusted non-3GPP access network, TNGF or core network function (e.g. AMF) can obtain Line ID (Logical Access ID see ETSI ES 282 004 [27]). More information on trusted non-3GPP access network can refer to TR 23.716 [9]. + +- If the UE registered to 3GPP access and non-3GPP access simultaneously, following information can be regarded as UE location information: + - All location information when the UE only registered to non-3GPP access, + - All location information when the UE only registered to 3GPP access, more details can refer to TS 36.305 [12]. + +For the issue of how to obtain the location information when the UE connects to non-3GPP access: + +In the current LCS system, LMF can obtain location measurements or location estimate from a UE via LPP protocol specified in TS 36.355 [15], and can also obtain location related information from NG-RAN via NRPPa protocol specified in TS 38.455 [11]. + +A similar solution can be applied to non-3GPP access, in which the LMF also obtains location measurements or location estimate from a UE via LPP protocol, and obtain location related information from N3IWF or TNGF via NRPPa protocol. + +- NOTE 7: It is assumed LPP protocol and NRPPa Protocol is reused in this solution. Both LPP protocol and NRPPa protocol should be enhanced to support non-3GPP location signalling procedure, but it belongs to RAN WG3 work scope. + +### 6.13.3 Positioning Procedures + +#### 6.13.3.1 Common Positioning Procedures When UE is served by the Same PLMN + +This positioning procedures shown in Figure 6.13.3.1-1, when UE is served by the same PLMN, can be triggered by: + +MO-LR (described in TS 23.271 [6] clause 9.2.6) or 5GC-NI-LR (described in TS 23.502 [5] clause 4.13.5.1) or 5GC-MT-LR procedure (described in TS 23.502 [5] clause 4.13.5.2 and 4.13.5.3) or 5GC-MT-LR (described in clause 6.2.3.1 proposed by solution 2) or 5GC-MO-LR (described in clause 6.2.3.2 proposed by solution 2), etc. + + + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant AMF + participant LMF + + Note over AMF, LMF: 1a. Namf_EventExposure_Subscribe +(Events: Location, Access Type, and CM state change) + LMF->>AMF: Subscribe + Note over AMF, LMF: 1b. Namf_EventExposure_Notify + AMF->>LMF: Notify + + Note right of AMF: 2. Determine the positioning +methods and/or access node. + + AMF->>NG-RAN: 3. Namf_Communication_N1N2MessageTransfer (Positioning Message, Access Type) + + rect rgb(240, 248, 255) + Note right of NG-RAN: 3GPP Access Positioning + NG-RAN->>UE: 4a. Obtain Measurements or Locations (TS23.502 4.13.5.4) + NG-RAN->>UE: 4b. Obtain Measurements or Locations (TS23.502 4.13.5.5) + NG-RAN->>NG-RAN: 4c. Obtain Measurements or Locations (TS23.502 4.13.5.6) + end + + Note over NG-RAN: N3IWF/TNGF + + rect rgb(255, 240, 245) + Note right of NG-RAN: Non-3GPP Access Positioning + NG-RAN->>UE: 4d. Obtain Measurements or Locations (TS23.502 4.13.5.4 with diff) + NG-RAN->>UE: 4e. Obtain Measurements or Locations (TS23.502 4.13.5.5 with diff) + end + + NG-RAN->>AMF: 5. Namf_Communication_N2InfoNotify (Positioning Message) + +``` + +The diagram illustrates the sequence of messages for common positioning procedures. It begins with the LMF sending a **Namf\_EventExposure\_Subscribe** to the AMF (step 1a) for events related to Location, Access Type, and CM state change. The AMF responds with a **Namf\_EventExposure\_Notify** (step 1b). The AMF then determines positioning methods (step 2) and sends a **Namf\_Communication\_N1N2MessageTransfer** to the NG-RAN (step 3). The NG-RAN performs several steps to obtain measurements or locations: 4a (same as step 2 to step 6 in TS23.502 clause 4.13.5.4), 4b (same as step 2 to step 6 in TS23.502 clause 4.13.5.5), 4c (same as step 2 to step 4 in TS23.502 clause 4.13.5.6), 4d (same as step 2 to step 6 in TS23.502 clause 4.13.5.4 with difference), and 4e (same as step 3 to step 5 in TS23.502 clause 4.13.5.5 with difference). These steps are grouped into categories: *3GPP Access Positioning-UE Assisted and UE Based Positioning Procedure*, *3GPP Access Positioning-Network Assisted Positioning Procedure*, *3GPP Access Positioning-Obtaining Non-UE Associated Network Assistance Data*, *Non-3GPP Access Positioning-UE Assisted and UE Based Positioning Procedure*, and *Non-3GPP Access Positioning-Obtaining UE Associated Network Assistance Data*. An **N3IWF/TNGF** block is shown between steps 4c and 4d. Finally, the NG-RAN sends a **Namf\_Communication\_N2InfoNotify** to the AMF (step 5). + +Sequence diagram showing common positioning procedures between UE, NG-RAN, AMF, and LMF. It details subscription, notification, method determination, message transfer, and various measurement/location acquisition steps for both 3GPP and Non-3GPP access. + +Figure 6.13.3.1-1: Common positioning procedures when UE is served by the same PLMN + +1. LMF may subscribe to the events of location change and/or access type change, and/or CM state change to AMF in step 1a. The AMF invoke the Namf\_EventExposure\_Notify service operation to notify the events in step 1b. +2. By considering UE/network position capacity, position QoS requirement, the access type(s) and/or the CM state per access type, the access type if received from HGMLC that request to perform Positioning procedure, LMF can determine the positioning methods. Furthermore, when NRPPa protocol is used to obtain location information from NG-RAN or N3IWF/TNGF, the LMF shall decide which access node should be chosen to transmit the location information. Based on other information in LMF, e.g. UE/network position capacity, the CM state per access type, position QoS requirement, LMF may override the access type received from HGMLC and determine the position methods corresponding to the other access type. + +When LPP protocol is used to obtain location information from UE, AMF shall decide which access node should be chosen to transmit the location information. For example, if CM-IDLE state in 3GPP, CM-CONNECTED state in N3GPP, AMF prefers to choose N3IWF/TNGF to relay positioning signalling to UE, rather than performs paging procedures via the 3GPP access. + +3. The LMF invokes the Namf\_Communication\_N1N2MessageTransfer service operation towards the AMF. + +When Access Type included in the Namf\_Communication\_N1N2MessageTransfer message indicates 3GPP Access should be used to transmit the location information, existing 3GPP Access Positioning Procedure specified in TS 23.502 [5] clause 4.13.5 should be performed, namely step 4b or step 4c. + +When Access Type included in the Namf\_Communication\_N1N2MessageTransfer message indicates non-3GPP Access should be used to transmit the location information, the non-3GPP Access Positioning Procedure should be performed, namely step 4e. + +When AMF select NG-RAN to relay positioning signalling to UE via LPP protocol, step 4a should be performed. + +When AMF select N3IWF/TNGF to relay positioning signalling to UE via LPP protocol, step 4d should be performed. + +NOTE 1: When step 4a or 4d is performed, the Positioning Message is corresponding to the Downlink (DL) Positioning message specified in TS 23.502 [5] clause 4.13.5.4. When step 4b or 4c or 4e is performed, the Positioning Message is corresponding to the Network Positioning message specified in TS 23.502 [5] clauses 4.13.5.5 and 4.13.5.6. + +NOTE 2: Step 4a, 4b, 4c, 4d and 4e is exclusive. + +4a. This step is same as step 2 to step 6 in TS 23.502 [5] clause 4.13.5.4. + +4b. This step is same as step 2 to step 6 in TS 23.502 [5] clause 4.13.5.5. + +4c. This step is same as step 2 to step 4 in TS 23.502 [5] clause 4.13.5.6. + +4d. This step is same as step 2 to step 6 in TS 23.502 [5] clause 4.13.5.4 with the following difference: + +- NG-RAN in TS 23.502 [5] clause 4.13.5.4 is corresponding to N3IWF/TNGF in Figure 6.13.3-1; +- Step 2 and 5 in TS 23.502 [5] clause 4.13.5.4 should be skipped; +- The location information returned is specified in clause 6.13.2. + +4e. This step is same as step 2 to step 4 in TS 23.502 [5] clause 4.13.5.5 with the following difference: + +- NG-RAN in TS 23.502 [5] clause 4.13.5.5 is corresponding to N3IWF/TNGF in Figure 6.13.3-1; +- The location information returned is specified in clause 6.13.2. + +5. The AMF invokes the Namf\_Communication\_N1MessageNotify service operation towards the LMF indicated by the routing identifier received in step 4 or step 5. + +NOTE 3: When step 4a or 4d is performed, the Positioning Message is corresponding to the Uplink (UL) Positioning message specified in TS 23.502 [5] clause 4.13.5.4. When step 4b or 4c or 4e is performed, the Positioning Message is corresponding to the Network Positioning message specified in TS 23.502 [5] clauses 4.13.5.5 and 4.13.5.6. + +#### 6.13.3.2 MT-LR Procedures When UE is served by the Different PLMNs via 3GPP access and Non-3GPP access + +This positioning procedures shown in Figure 6.13.3.2-1, can be triggered by 5GC-MT-LR Procedure described in TS 23.502 [5] clause 4.13.5.3 or 5GC-MT-LR procedure described in clause 6.2.3.1 proposed by solution 2, etc, when UE is served by the different PLMNs. + + + +``` + +sequenceDiagram + participant UE + participant V-5G-AN-1 + participant V-AMF-1 + participant V-LMF-1 + participant V-GMLC-1 + participant UDM + participant H-GMLC + participant LCS Client + + Note right of LCS Client: 1. LCS Service Request + Note right of H-GMLC: 2. Nudm_UEContextManagement_GetRequest + Note right of UDM: 3. Nudm_UEContextManagement_GetResponse + Note right of H-GMLC: 4. Select one PLMN/access type according to preference configuration + Note right of H-GMLC: 5. LCS Service Request + Note right of V-GMLC-1: 6. V-GMLC-1 forwards the LCS service requests directly to V-LMF-1 or via V-AMF-1 + Note right of V-LMF-1: 7. Obtain locations or measurements + Note right of V-GMLC-1: 8. V-GMLC-1 receives positioning results + Note right of V-GMLC-1: 9. LCS Service Response + Note right of H-GMLC: 10. If positioning succeeds, step 13 performs, else step 11-13 performs; + Note right of V-GMLC-2: 11. Similar procedures as step 5-9 + Note right of H-GMLC: 12. Choose and determine final positioning results + Note right of H-GMLC: 13. LCS Service Response + +``` + +Sequence diagram of MT-LR positioning procedures when UE is served by different PLMNs via 3GPP access and Non-3GPP access. The diagram shows interactions between UE, V-5G-AN-1, V-AMF-1, V-LMF-1, V-GMLC-1, UDM, H-GMLC, and LCS Client. It details the flow from an LCS Service Request to the final LCS Service Response, including context management, location acquisition, and result determination across multiple PLMNs. + +**Figure 6.13.3.2-1: MT-LR positioning procedures when UE is served by the different VPLMNs** + +1. An external LCS client sends a location request to an HGMLC in the HPLMN for the target UE. The HGMLC verifies the authorization of the LCS Client to locate the target UE and UE privacy requirements. +2. The HGMLC invokes the Nudm\_UE ContextManagement\_Get service operation towards the home UDM of the target UE with the GPSI or SUPI of the UE. +3. For each access type, in case the procedure is triggered by 5GC-MT-LR Procedure described in TS 23.502 [5] clause 4.13.5.3, the UDM returns serving AMF address, possibly a VGMLC address to HGMLC to perform routing function. In case the procedure is triggered by 5GC-MT-LR procedure described in clause 6.2.3.1 proposed by solution 2, the LMF address should also be included which will be provided to V-GMLC in step 5. + +UDM may also returns the access type(s) and its corresponding CM state(s) to HGMLC which will be used in step 4. + +NOTE 4: UDM request the CM state(s) information from AMF by invoking Namf\_EventExposure service when UDM need the CM state(s) information. + +4. When HGMLC finds that UE is served by the different PLMNs according to the obtained serving AMF addresses, HGMLC will determine one PLMN according to Configuration. + +NOTE 5: The Configuration which can be pre-configured in HGMLC or obtained from LCS service requests indicates which access type and/or CM state and/or PLMN should be the prioritized target. For example, the Configuration can be 3GPP access first and/or connected state first and/or VPLMN first. + +5. In case the procedure is triggered by 5GC-MT-LR Procedure described in TS 23.502 [5] clause 4.13.5.3, the HGMLC forwards the location request to the VGMLC and may include the AMF address received in step 3, the target UE identity (e.g. SUPI), access type and corresponding CM state (if needed). In case the procedure is triggered by 5GC-MT-LR procedure described in clause 6.2.3.1 proposed by solution 2, LMF address should also be included. +6. If the procedure is triggered by 5GC-MT-LR procedure described in clause 6.2.3.1 proposed by solution 2, the VGMLC invokes the Nlmf\_ProvideLocation Request service operation to forward the location request to the LMF directly based on the LMF address received in step 5. LMF receives the location request directly from VGMLC. + +If the procedure is triggered by 5GC-MT-LR Procedure described in TS 23.502 [5] clause 4.13.5.3, the VGMLC invokes the Namf\_Location\_ProvideLocation\_Request service operation to forward the location request to the AMF. LMF receives the location request directly from AMF. + +7. This step can refer to step 1-5 of clause 6.13.3.1 which is performed when UE is served by the same PLMN. + +NOTE 6: If the location request received by LMF has contained access type and/or CM state, step 1a-1b of clause 6.13.3.1 may be skipped. + +- 8-9. VGMLC will receive the location service response from LMF and then returns positioning result to the HGMLC. The location service response may contain positioning information (e.g. the information shown in Table 6.13.2-1), the information about the positioning method used and the indication whether the obtained location estimate satisfies the requested LCS QoS (e.g. accuracy) or not (described in TS 23.271 [6] clause 9.1.1). + +10. If HGMLC finds that location service response from chosen PLMN meets required LCS QoS, it will directly return results to LCS Client directly. Otherwise, if needed, HGMLC will forward location request to another PLMN so as to obtain the positioning result which can meet required LCS QoS shown as step 11. + +11. The step obtains the positioning information from another PLMN, the details are same as step 5-9. + +- 12-13. Finally, HGMLC will return final location service response to LCS client. Location service response can contain the positioning result which meet the required LCS QoS or both results from two different PLMNs (both failed or succeed). + + + +``` + +sequenceDiagram + participant UE + participant V-5G-AN-1 + participant V-AMF-1 + participant V-LMF-1 + participant V-GMLC-1 + participant UDM + participant H-GMLC + participant LCS Client + + Note right of LCS Client: 1. LCS Service Request + Note right of H-GMLC: 2. Nudm_UEContextManagement_GetRequest + Note right of UDM: 3. Nudm_UEContextManagement_GetResponse + Note right of H-GMLC: 4. Select one PLMN according to preference or randomly + Note right of H-GMLC: 5. LCS Service Request + Note right of V-GMLC-1: 6. V-GMLC-1 forwards the LCS service requests directly to VLMF-1 or via VAMF-1 + Note right of V-LMF-1: 7. Obtain locations or measurements + Note right of V-GMLC-1: 8. V-GMLC-1 receives positioning results + Note right of V-GMLC-1: 9. LCS Service Response + Note right of H-GMLC: 10. If positioning succeeds, step 13 performs, else step 11-13 performs; + Note right of H-LMF-2: 11. Similar procedures as step 6-8 + Note right of H-GMLC: 12. Choose and determine final positioning results + Note right of H-GMLC: 13. LCS Service Response + +``` + +Sequence diagram for MT-LR positioning procedures when UE is served by HPLMN and VPLMN. The diagram shows interactions between UE, V-5G-AN-1, V-AMF-1, V-LMF-1, V-GMLC-1, UDM, H-GMLC, and LCS Client. Steps include LCS Service Request, Nudm\_UEContextManagement\_GetRequest/Response, PLMN selection, forwarding of requests, location obtaining, and final result determination. + +**Figure 6.13.3.2-2: MT-LR positioning procedures when UE is served by HPLMN and VPLMN** + +Figure 6.13.3.2-2 shows the MT-LR positioning procedures when UE is served by HPLMN and VPLMN. The difference with procedures shown in Figure 6.13.3.2-1 is that the H-GMLC interacts with H-LMF directly shown in step 11 of Figure 6.13.3.2-2 without involving V-GMLC shown in step 11 of Figure 6.13.3.2-1. + +#### 6.13.3.3 MO-LR Procedures When UE is served by the Different PLMNs via 3GPP access and Non-3GPP access + +This procedures can be triggered by MO-LR (described in TS 23.271 [6] clause 9.2.6), and which PLMN/access type shall be chosen to performing MO-LR procedures is up to UE's implementation. + +#### 6.13.3.4 NI-LR Procedures When UE is served by the Different PLMNs via 3GPP access and Non-3GPP access + +This procedures can be triggered by 5GC-NI-LR (described in TS 23.502 [5] clause 4.13.5.1), and refer to step 1-5 of clause 6.13.3.1 which is performed when UE is served by the same PLMN. + +### 6.13.4 Impact on existing entities and interfaces + +When the UE is connecting to 3GPP and Non-3GPP simultaneously, for both scenarios that UE is served by the same PLMN and UE is served by the different PLMNs, common impacts on existing entities are: + +#### LMF: + +- Need to subscribe to the events of location change and/or access type change, and/or CM state change to AMF. +- Need to determine the positioning methods considering the UE/network position capacity, position QoS requirement, the access type(s) and/or the CM state per access type. +- Need to decide which access node should be chosen to transmit the location information when obtaining location related info when NRPPA is used. + +#### AMF: + +- Need to decide which access node should be chosen to transmit the location information by considering the access type(s) and/or the CM state per access type when LPP is used. + +N3IWF/TNGF: + +- Need to support NRPPa protocol to support positioning procedures for untrusted non-3GPP access. + +UE: + +- Need to support LPP protocol to support positioning procedures for untrusted non-3GPP access. + +For the specific scenario that UE is served by the same PLMN via 3GPP access and Non-3GPP access, impacts on existing entities are: + +LMF: + +- Need to determine whether to override the received access type which is determined by HGMLC to perform positioning procedure. + +For the specific scenario that UE is served by the different PLMNs via 3GPP access and Non-3GPP access, impacts on existing entities are: + +GMLC: + +- Need to choose one PLMN according to Configuration to forward LCS positioning requests. +- Need to support forwarding LCS positioning requests to another PLMN, when the positioning result from the first PLMN can't meet the QoS requirement, and determining final location service response to the LCS client. + +UE: + +- Need to determine which PLMN/access type shall be chosen to performing MO-LR procedures. + +### 6.13.5 Evaluation + +Solution 13 is one CP-based solution designed to support non-3GPP access positioning procedures, of which key points are that LMF can subscribe location, access type (s), CM state change event to AMF to determine positioning methods and/or which access node can be chosen to obtain location information. Specially, for the scenario the UE is served by different PLMNs for 3GPP and non-3GPP accesses, GMLC can assist to decide which PLMN/access should be chosen to perform positioning procedures. + +Solution 13 can adapt to both the LMF based architecture and the AMF based architecture. It reuses the existing 3GPP positioning procedures as much as possible with little impacts on existing network functions and little extra NAS signalling overhead. In addition, this solution can be applicable to most positioning scenarios, including MO-LR, 5GC-NI-LR, and 5GC-MT-LR procedures. + +## 6.14 Solution 14: Reuse R15 existing location service architecture for commercial use cases + +### 6.14.1 Introduction + +In Rel-15, Location Service feature is restricted to regulatory service, therefore, when location service is enabled, it is assumed that the UE is allowed to be located. However, in a commercial use case, the target UE user shall be able to set privacy as "not allowed to be located". + +A requester of the regulatory LCS service is assumed always authorised to use the service. However, in a commercial use case, the requestor UE or the requestor client may or may not be authorised to use the LCS service. + +The privacy setting of the target UE and the location subscriber authorization data of the requestor client / UE can be a Data Subset of the Subscription Data stored in the UDR accessed by the UDM.. + +Additionally, for commercial services, location service architecture needs to be extended to support roaming scenario, the location service exposure and Mobile Originating Location Request scenario. + +This solution is intended to address Key Issue 1 (Enhancement to LCS Architecture) and Key Issue 7 (Location service exposure). The solution also addresses the following additional key issues: + +- Key Issue 3: Support of low latency LCS. +- Key Issue 6: Scalability. +- Key Issue 8: Support of IoT UEs. +- Key Issue 15: Location continuity support. +- Key Issue 5: Slicing dependent location service. + +### 6.14.2 Functional Description + +#### 6.14.2.1 Architecture to support Location Services + +The following proposed architectures applies to both regulatory services and commercial services, in which only entities directly relevant to location services are shown: + +- Figure 6.14.2.1-1 shows architectural support for location services for non-roaming scenarios using service-based interface representation, where applicable (same with Figure 4.4.4.1-1 of TS 23.501 [4]). +- Figure 6.14.2.1-2 shows architectural support for location services for roaming scenarios using service-based interface representation, where applicable. +- Figure 6.14.2.1-3 shows architectural support for location services for non-roaming scenarios, using the reference point representation (same with Figure 4.4.4.1-2 of TS 23.501 [4]). +- Figure 6.14.2.1-4 shows architectural support for location services for roaming scenarios, using the reference point representation. + +NOTE 1: The reference point Le is shown for completeness only. + +NOTE 2: If an inter-GMLC scenario is required the reference points Lr defined in TS 23.271 [6] can be used. + +NOTE 3: R-GMLC is not shown in the figures below and is assumed to be the same as H-GMLC or V-GMLC respectively. + +**Editor's note:** Whether and how to follow the naming principle of the 5GC architecture for the LCS related reference points is FFS. + + + +``` + +graph TD + subgraph TopRow [ ] + AF[AF] + NEF[NEF] + CHF[CHF] + UDM[UDM] + end + subgraph BottomRow [ ] + AMF[AMF] + LMF[LMF] + GMLC[GMLC] + end + UE[UE] --- NG-RAN[NG-RAN] + NG-RAN --- AMF + GMLC --- LRF[LRF] + GMLC --- Le((Le)) + Le --- LCS-Client((LCS Client)) + + AF -- Naf --> SBI(( )) + NEF -- Nnef --> SBI + CHF -- Nchf --> SBI + UDM -- Nudm --> SBI + SBI -- Namf --> AMF + SBI -- Nlmf --> LMF + SBI -- Ngmlc --> GMLC + + style TopRow fill:none,stroke:none + style BottomRow fill:none,stroke:none + style SBI fill:none,stroke:none + +``` + +Figure 6.14.2.1-1: Non-roaming reference architecture for Location Services in service-based interface representation. The diagram shows a service-based interface (SBI) represented by a horizontal line. Above the SBI, four entities (AF, NEF, CHF, UDM) are connected via their respective service-based interfaces (Naf, Nnef, Nchf, Nudm). Below the SBI, three entities (AMF, LMF, GMLC) are connected via their respective service-based interfaces (Namf, Nlmf, Ngmlc). The AMF is connected to an NG-RAN, which is in turn connected to a UE. The GMLC is connected to an LRF and has a service-based interface (Le) connected to an LCS Client. + +**Figure 6.14.2.1-1: Non-roaming reference architecture for Location Services in service-based interface representation** + + + +This diagram illustrates the roaming reference architecture for Location Services (LCS) using service-based interfaces. It is divided into two domains by a vertical dashed line: VPLMN (Visited PLMN) on the left and HPLMN (Home PLMN) on the right. In the VPLMN, a UE is connected to an NG-RAN, which is connected to an AMF via an N2 interface. The AMF connects to an LMF via an Nlmf interface and to a V-GMLC via an Ngmlc interface. The V-GMLC is connected to an LRF. The AMF also connects to the HPLMN via a Namf interface. In the HPLMN, the H-GMLC connects to the AMF via an Ngmlc interface and to an LCS Client via a Le interface. The H-GMLC also connects to the CHF via an Nchf interface, to the UDM via an Nudm interface, to the AF via an Naf interface, and to the NEF via an Nnef interface. + +Roaming reference architecture for Location Services in service-based interface representation + +**Figure 6.14.2.1-2: Roaming reference architecture for Location Services in service-based interface representation** + +NOTE 1: For the LCS service exposure, Le is used to support legacy LCS clients and an SBI interface (to the NEF for external client or directly to a GMLC in case of authorized clients) is used to support the 5GC LCS service applications. + +NOTE 2: New 5GS LCS features may only be supported over the SBI interface. + + + +This diagram illustrates the non-roaming reference architecture for Location Services (LCS) using reference points. A UE is connected to an NG-RAN, which is connected to an AMF via an N2 interface. The AMF connects to the UE via an N1 interface, to the LMF via an NLs interface, to the UDM via an N8 interface, and to the GMLC via an NLg interface. The NG-RAN also connects to the LMF via an N2 interface. The LMF is connected to the LRF. The GMLC connects to the UDM via an NLh interface, to the CHF via an NLc interface, to the NEF via an NLe interface, to the AF via an NLe interface, and to the LCS Client via a Le interface. The GMLC is also connected to the LRF. + +Non-roaming reference architecture for Location Services in reference point representation + +**Figure 6.14.2.1-3: Non-roaming reference architecture for Location Services in reference point representation** + + + +Figure 6.14.2.1-4: Roaming reference architecture for Location Services in reference point representation. The diagram shows the architecture for location services in a roaming scenario between a Visited PLMN (VPLMN) and a Home PLMN (HPLMN). In the VPLMN, a UE is connected to an AMF via N1. The AMF is connected to an NG-RAN via N2, an LMF via NLs, and a V-GMLC via NLg. The V-GMLC is connected to an LRF. A dashed line separates the VPLMN from the HPLMN. In the HPLMN, the V-GMLC is connected to an H-GMLC via Nlr. The H-GMLC is connected to a CHF via NLcg, a UDM via NLh, and a NEF via NLe. The NEF is connected to an AF. The H-GMLC is also connected to an LCS Client via Le. + +**Figure 6.14.2.1-4: Roaming reference architecture for Location Services in reference point representation** + +#### 6.14.2.2 Reference point to support Location Services + +- N1:** Reference point between UE and AMF via NAS. +- N2:** Reference point between NG-RAN and AMF. +- Le:** Reference point between a GMLC and a LCS Client. + +Following reference points are realized by service based interfaces: + +- NLg:** Reference point between a GMLC and an AMF. +- NLs:** Reference point between an AMF and LMF. +- NLh:** Reference point between an GMLC and UDM. +- NLr:** Reference point between an H-GMLC and V-GMLC. +- NLc:** Reference point between GMLC and CHF. +- NLe:** Reference point between GMLC and NEF. + +#### 6.14.2.3 Service Based Interfaces to support Location Services + +- Ngmlc:** Service-based interface exhibited by GMLC. +- Nlmf:** Service-based interface exhibited by LMF. +- Namf:** Service-based interface exhibited by AMF. +- Nudm:** Service-based interface exhibited by UDM. +- Nchf:** Service-based interface exhibited by CHF. +- Nnef:** Service-based interface exhibited by NEF. +- Naf:** Service-based interface exhibited by AF. + +#### 6.14.2.4 Network Functions to support Location Services + +##### AMF: + +- Location Services management for regulatory services and commercial services. + +- Provide transport for Location Services messages between UE and LMF as well as between RAN and LMF. +- LMF selection. +- LCS service authorization to the requester UE for MO-LR scenario. + +##### **LMF:** + +- Supports location determination for a UE. +- Obtains downlink location measurements or a location estimate from the UE. +- Obtains uplink location measurements from the NG RAN. +- Obtains non-UE associated assistance data from the NG RAN. + +##### **GMLC:** + +- Privacy checking of the target UE for MT-LR scenario. +- LCS service authorization to the LCS Client for MT-LR scenario. +- Provide transport for Location Services messages between LCS Client and AMF. +- Collect charging information of the location services and report to the CHF. + +##### **UDM:** + +- Store and provide privacy setting of the target UE to the GMLC. +- Store and provide location subscriber authorization data of the requestor UE to the AMF. + +##### **NEF:** + +- Receive location service request from the AF. +- Provide location result to the AF. +- LCS service authorization of the AF. + +##### **CHF:** + +- Charge for the usage of LCS service. + +### 6.14.3 Procedures + +#### 6.14.3.0 LMF selection + +The selection of the LMF shall take into account that the selected LMF needs to correspond to the Access Type of the 5G AN serving the UE. + +NOTE: Location methods may differ depending on the Access Type, e.g. in case of WLAN Access some specific corporate data base may need to be accessed; As another example, for Wireline access, Location determination may just correspond to retrieval of geo coordinates corresponding to a Line Id. + +The selection of the LMF should also take into account the 5G AN node (e.g. gNB) currently serving the UE as the LMF may need to be configured, e.g. with the corresponding RAN topology information, so that it can carry out the positioning operation. + +The following factors may be considered during the LMF selection: + +- Requested Quality of Service information, e.g.: + - LCS accuracy, + - Response time (latency), + - LCS QoS Class. + +- Access Type (3GPP /N3GPP). +- 5G AN type (i.e. 5G NR or eLTE) and the serving AN node (i.e. gNB or NG-eNB) of the target UE. +- RAN configuration information. +- LMF capabilities. +- LMF load. +- LMF location. +- Indication of either a single event report or multiple event reports. +- Duration of event reporting. +- Network slicing information, e.g. S-NSSAI and NSI ID. + +#### 6.14.3.1 5GC-MT-LR Procedure + +Figure 6.14.3.1-1 illustrates the general network positioning for LCS clients external to the PLMN. In this scenario, it is assumed: + +- the target UE is identified using an SUPI or GPSI; +- the privacy setting of the UE is stored in the UDR as a Data Subset of the Subscription Data that is accessed by the UDM. + +This procedure is applicable to a request from an LCS client for a current location. + + + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant AMF + participant LMF + participant V-GMLC + participant H-GMLC + participant UDM + participant EC as External Client + participant NEF + participant AF + + Note right of H-GMLC: 1a. LCS Service Request + EC->>H-GMLC: 1a. LCS Service Request + Note right of H-GMLC: 1b. LCS Service Request + AF->>H-GMLC: 1b. LCS Service Request + Note right of H-GMLC: 2. LCS Privacy Check + H-GMLC->>UDM: 2. LCS Privacy Check + Note right of H-GMLC: 3. Nudm_UECM_Get + H-GMLC->>UDM: 3. Nudm_UECM_Get + Note right of AMF: 4. Namf_Location_ProvideLocation Request + AMF->>LMF: 4. Namf_Location_ProvideLocation Request + Note left of AMF: 5. Network Triggered Service Request + Note right of AMF: 6. Nlmf_Location_DetermineLocation Request + AMF->>LMF: 6. Nlmf_Location_DetermineLocation Request + Note left of LMF: 7. UE Positioning + Note right of LMF: 8. Nlmf_Location_DetermineLocation Response + LMF->>AMF: 8. Nlmf_Location_DetermineLocation Response + Note right of AMF: 9. Namf_Location_ProvideLocation Response + AMF->>H-GMLC: 9. Namf_Location_ProvideLocation Response + Note right of H-GMLC: 10a. LCS Service Response + H-GMLC->>EC: 10a. LCS Service Response + Note right of H-GMLC: 10b. LCS Service Response + H-GMLC->>AF: 10b. LCS Service Response + +``` + +Sequence diagram of the 5GC-MT-LR Procedure showing interactions between UE, NG-RAN, AMF, LMF, V-GMLC, H-GMLC, UDM, External Client, NEF, and AF. + +Figure 6.14.3.1-1: 5GC-MT-LR Procedure + +1. The external location services client or the AF (via NEF) sends a request to the (H-)GMLC for a location for the target UE identified by an GPSI or an SUPI. The request may include the required QoS, Supported GAD shapes and client type. NEF or (H-)GMLC authorizes the AF or the External Client for the usage of the LCS service. If the authorization fails, step 2-9 are skipped and NEF or (H-)GMLC responds to the external Client or the AF the failure of the service authorization in step 10. + +2. The (H-)GMLC invokes a Nudm\_SDM\_Get service operation towards the UDM of the target UE to get the privacy settings of the UE identified by its GPSI or SUPI. The UDM returns the target UE Privacy setting and the SUPI of the UE. The (H-)GMLC checks the privacy settings. If the target UE is not allowed to be located, step 3-9 are skipped. +3. The (H-)GMLC invokes a Nudm\_UECM\_Get service operation towards the UDM of the target UE to be located with SUPI of this UE. The UDM returns the network addresses of the current serving AMF and possibly the address of a V-GMLC (roaming case). + +The UDM is aware of the serving AMF address based on UE registration on an AMF (TS 23.502 [5], clause 4.2.2.2.2). The UDM made aware of a serving GMLC address by the AMF at UE registration on an AMF (modification to TS 23.502 [5], clause 4.2.2.2.2). + +4. The (H)GMLC invokes the Namf\_Location\_ProvideLocation service operation towards the AMF to request the current location of the UE. The service operation includes the SUPI, the client type (with potentially an override capability) and may include the required LCS QoS and Supported GAD shapes. + +**Editor's note:** The list of parameters of the Namf\_Location\_ProvideLocation service operation is not meant to be exhaustive, what other parameters are to be added is FFS. + +In the roaming case, if the H-GMLC received an address of a V-GMLC (together with the network addresses of the current serving AMF) from the UDM in step 3, the H-GMLC may send the location request to the V-GMLC that may invoke the Namf\_Location\_ProvideLocation service operation towards the AMF; otherwise, the H-GMLC may use the NRF service in the HPLMN to select an available V-GMLC in the VPLMN, based on the VPLMN identification contained in the AMF address received in step 3. + +5. If the UE is in CM IDLE state, the AMF initiates a network triggered Service Request procedure as defined in clause 4.2.3.4 to establish a signalling connection with the UE. If it is not possible to have the UE CM-CONNECTED, the AMF answers to the GMLC with the last known location of the UE (i.e. Cell ID) together with the age of this location. + +If the location request comes from a value added LCS client and the indicators of privacy related action indicates that the UE must either be notified and the UE supports notification of LCS, a notification invoke message is sent to the target UE indicating the type of location request from the LCS Client (e.g. current location or "current or last known location") and the identity of the LCS client and the Requestor Identity (if that is both supported and available). + +6. The AMF selects an LMF based on the current serving AN of the UE. This selection allows to select a LMF that depends on the access Type of the UE and in case of 3GPP access allows to select a LMF that is configured with proper information on the radio coverage of the UE; this selection may use a NRF query or use local configuration in AMF. The AMF invokes the Nlmf\_Location\_DetermineLocation service operation towards the LMF to request the current location of the UE. The service operation includes a LCS Correlation identifier, the serving cell identity and the client type and may include the required QoS and Supported GAD shapes. + +The LMF selection takes the 5G-AN currently serving the UE into account. + +7. The LMF performs one or more of the positioning procedures described in clauses 4.13.5.4, 4.13.5.5 and 4.13.5.6 of TS 23.502 [5]. During this step the LMF may use the Namf\_Communication\_N1N2MessageTransfer service operation to request the transfer of a Positioning related N1 message to the UE or the transfer of a Network Positioning message to the serving NG-RAN node (gNB or NG-eNB) for the UE. +8. The LMF returns the Nlmf\_Location\_DetermineLocation Response towards the AMF to return the current location of the UE. The service operation includes the LCS Correlation identifier, the location estimate, its age and accuracy and may include information about the positioning method. +9. The AMF returns the Namf\_Location\_ProvideLocation Response towards the (H-)GMLC to return the current location of the UE. The service operation includes the location estimate, its age and accuracy and may include information about the positioning method. (H-)GMLC reports to the CHF for the usage of the LCS service.10. + +The (H-)GMLC sends the location service response to the external location services client. If in step 2 the (H-)GMLC identifies that the target UE is not allowed to be located by the requested UE user, it rejects the LCS service request, and optionally indicate in the response the reason of the rejection, i.e. the target UE is not allowed to be located. + +#### 6.14.3.2 5GC-MO-LR Procedure + +Procedures described in Figure 6.14.3.1-2 is used for a UE to request its own location. + + + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant LMF + participant AMF + participant UDM + + Note left of UE: 1. UE Triggered Service Request + UE->>AMF: 2. LCS Service Request + AMF->>LMF: 3. Nlmf_Location_DetermineLocation Request + Note over UE, AMF: 4. UE Positioning + LMF->>AMF: 5. Nlmf_Location_DetermineLocation Respons + AMF->>UE: 6. LCS Service Response + +``` + +The diagram illustrates the 5GC-MO-LR procedure. It starts with a dashed box labeled '1. UE Triggered Service Request' involving the UE and NG-RAN. Step 2 shows the UE sending an 'LCS Service Request' to the AMF. Step 3 shows the AMF sending an 'Nlmf\_Location\_DetermineLocation Request' to the LMF. Step 4 is a 'UE Positioning' phase involving the UE, NG-RAN, and LMF. Step 5 shows the LMF sending an 'Nlmf\_Location\_DetermineLocation Respons' to the AMF. Step 6 shows the AMF sending an 'LCS Service Response' to the UE. + +Sequence diagram for 5GC-MO-LR Procedure showing interactions between UE, NG-RAN, LMF, AMF, and UDM. + +**Figure 6.14.3.1-2: 5GC-MO-LR Procedure** + +1. If the UE is in CM IDLE state, the UE performs a UE triggered service request as defined in TS 23.501 [4]. +2. The UE sends a NAS MO-LR Request to the AMF. The UE request may contain LCS requested QoS information (e.g. accuracy, response time, LCS QoS Class), the requested maximum age of location and the requested type of location (e.g. "current location", "current or last known location"). The AMF checks the LCS service authorization data obtained together with other UE subscription data from the UDM during UE registration for LCS service authorization. If the authorization fails, step 4-6 are skipped and AMF responds in Step 6 on the failure of LCS service authorization. + +Step 3-5 follows Step 6-8 of 5GC-MT-LR Procedure defined in clause 6.14.3.1. + +6. AMF responds UE of its location. + +#### 6.14.3.3 Deferred 5GC-MT-LR Procedure for Periodic, Triggered and UE Available Location Events + +Figure 6.14.3.3-1 summarizes a deferred 5GC-MT-LR procedure for Periodic, Triggered and UE Available Location Events for a roaming UE. A deferred 5GC-MT-LR procedure for a non-roaming UE would comprise a subset of the procedure shown in Figure 6.14.3.3-1. The procedure supports mobility of a UE within a VPLMN 5GCN and from a 5GCN to an EPC. + + + +``` + +sequenceDiagram + participant UE + participant RAN as (R)AN + participant AMF + participant LMF + participant VGMLC + participant UDM + participant HGMLC + participant LCS_Client as LCS Client + + Note right of LCS_Client: 1. LCS Service Request + LCS_Client->>HGMLC: 1. LCS Service Request + Note right of HGMLC: 2. LCS Privacy Check + HGMLC->>UDM: 2. LCS Privacy Check + Note right of UDM: 3. Nudm_UECM_Get + UDM->>HGMLC: 3. Nudm_UECM_Get + Note right of HGMLC: 4. LCS Service Request + HGMLC->>VGMLC: 4. LCS Service Request + Note right of VGMLC: 5. Namf_ProvidePositioningInfo Request + VGMLC->>AMF: 5. Namf_ProvidePositioningInfo Request + Note right of AMF: 6. Namf_ProvidePositioningInfo Response + AMF->>VGMLC: 6. Namf_ProvidePositioningInfo Response + Note right of VGMLC: 7. LCS Service Response + VGMLC->>HGMLC: 7. LCS Service Response + Note right of HGMLC: 8. LCS Service Response + HGMLC->>LCS_Client: 8. LCS Service Response + + Note left of AMF: 9. Wait for UE to become reachable + Note left of AMF: 10. Network Triggered Service Request + AMF->>RAN: 11. Location Notification Invoke + RAN->>UE: 11. Location Notification Invoke + Note right of UE: 12. Location Notification Response + UE->>RAN: 12. Location Notification Response + RAN->>AMF: 13. Nlmf_Location_DetermineLocation Request + + Note left of AMF: 14. UE Positioning Procedure + Note left of AMF: 15. Periodic-Triggered Location Request + Note left of AMF: 16. Periodic-Triggered Location Response + AMF->>LMF: 17. Nlmf_Location_DetermineLocation Response + + Note left of AMF: 21. Event Detected + AMF->>VGMLC: 18. Namf_Location_EventNotify + Note right of VGMLC: 19. LCS Service Response + VGMLC->>HGMLC: 19. LCS Service Response + Note right of HGMLC: 20. LCS Service Response + HGMLC->>LCS_Client: 20. LCS Service Response + + Note left of AMF: 22. Location Measurements + Note left of AMF: 23. UE Triggered Service Request + AMF->>LMF: 24. Event Report + Note right of LMF: 25. Event Report Acknowledgment + LMF->>AMF: 25. Event Report Acknowledgment + Note left of AMF: 26. UE Positioning Procedure + AMF->>LMF: 27. Determine UE Location + Note right of LMF: 28. Nlmf_EventNotify + LMF->>VGMLC: 28. Nlmf_EventNotify + Note right of VGMLC: 29. LCS Service Response + VGMLC->>HGMLC: 29. LCS Service Response + Note right of HGMLC: 30. LCS Services Response + HGMLC->>LCS_Client: 30. LCS Services Response + + Note left of AMF: 31. Event Detected + AMF->>LMF: 32. Cancel Location + Note right of LMF: 33. Nlmf_EventNotify + LMF->>VGMLC: 33. Nlmf_EventNotify + Note right of VGMLC: 34. LCS Service Response + VGMLC->>HGMLC: 34. LCS Service Response + Note right of HGMLC: 35. LCS Services Response + HGMLC->>LCS_Client: 35. LCS Services Response + + Note right of AMF: 38. Namf_CancelLocation + AMF->>VGMLC: 38. Namf_CancelLocation + Note right of VGMLC: 37. LCS Cancel Location + VGMLC->>HGMLC: 37. LCS Cancel Location + Note right of HGMLC: 36. LCS Cancel Location + HGMLC->>LCS_Client: 36. LCS Cancel Location + + Note right of AMF: 39. Nlmf_CancelLocation + AMF->>LMF: 39. Nlmf_CancelLocation + Note right of LMF: 40. Cancel Location + LMF->>RAN: 40. Cancel Location + RAN->>UE: 40. Cancel Location + +``` + +Sequence diagram for Deferred 5GC-MT-LR for periodic, triggered and UE available location events. Lifelines: UE, (R)AN, AMF, LMF, VGMLC, UDM, HGMLC, LCS Client. The diagram shows the interaction between these entities to handle location requests and responses, including privacy checks, positioning procedures, and event notifications. + +**Figure 6.14.3.3-1: Deferred 5GC-MT-LR for periodic, triggered and UE available location events** + +- An external LCS client sends a deferred location request for a periodic, triggered or UE available location event for a target UE to an HGMLC in the HPLMN for the UE. The location request provides the type of location reporting being requested and associated parameters. For periodic location, the request includes the time interval between successive location reports, the total number of reports and a location QoS. For triggered reporting for an area event, the request includes details of the target area, whether the trigger event to be reported is the UE being inside, entering or leaving the target area, whether event reporting shall include UE location estimates and if so a location QoS and the duration of reporting. For triggered reporting for the motion event, the request includes a threshold linear distance for triggering a location report, whether event reporting shall include UE location estimates and if so a location QoS and the duration of reporting. For the UE available location event, a location QoS may be included. + +NOTE 1: The external LCS client may instead be an NF or an AF which accesses the HGMLC via an NEF as described in clause 6.9 for Solution 9 and clause 6.23 for Solution 23. + +2. The HGMLC may verify UE privacy requirements by querying the UDM as described for step 2 in Figure 6.14.3.1-1. If the target UE is not allowed to be located, subsequent steps are skipped. + +3. The HGMLC invokes the Nudm\_UECM\_Get service operation towards the home UDM of the target UE with the GPSI or SUPI of the UE to obtain the serving AMF address and optionally a VGMLC address and current access type(s) for the target UE as described for step 3 of Figure 6.14.3.1-1. + +NOTE 2: The HGMLC may also query the HSS of the target UE for a serving MME address as described in clause 9.1.1 of TS 23.271 [6]. The deferred EPC-MT-LR procedure for Periodic and Triggered Location described in clause 9.1.19 of TS 23.271 [6] or the EPC-MT-LR procedure for the UE availability event described in clause 9.1.15 of TS 23.271 [6] may then be performed instead of steps 4-40 - e.g. if the HSS returns an MME address but the UDM does not return an AMF address. + +4. If a VGMLC address was not returned in step 3, the HGMLC may use the NRF service in the HPLMN to select an available VGMLC in the VPLMN, based on the VPLMN identification contained in the AMF address received in step 3. The HGMLC forwards the location request to the VGMLC and includes the AMF address, the target UE identity (e.g. SUPI), any access type(s) received at step 3 and any privacy requirements for the UE. The HGMLC also includes a contact address for the HGMLC (Notification Target Address, e.g. a URI) and an LDR reference number (Notification correlation ID) to be used for event reporting at steps 19, 29 and 34. + +5. The VGMLC invokes the Namf\_Location\_ProvidePositioningInfo Request service operation to forward the location request including all information received at step 4 to the serving AMF. The VGMLC may optionally determine an LMF and then includes the LMF identity in the request sent to the AMF. + +6-8. If the AMF supports a deferred location request, the AMF returns an acknowledgment to the external LCS client, via the VGMLC and HGMLC, indicating that the request for deferred location was accepted. The VGMLC may optionally release resources for the deferred location request at this point. + +NOTE 3: As an optional optimization, a VGMLC may not be used. In this case, instead of performing steps 4-7, the HGMLC invokes the Namf\_Location\_ProvidePositioningInfo Request service operation to forward the location request directly to the AMF. The AMF then returns an acknowledgment directly to the HGMLC. + +9. If the UE is not currently reachable (e.g. is using eDRX or PSM), the AMF waits for the UE to become reachable. + +NOTE 4: In the event of mobility of the UE to another AMF or to EPC when the UE becomes reachable, the old AMF can return an event indication to the HGMLC as at steps 18 and 19 and may include the address of the new serving AMF or MME if known. If a new serving AMF or MME is not known, the HGMLC can repeat steps 2 and 3 to query the UDM and HSS for the new AMF or MME address. The HGMLC can then restart the procedure from step 3. + +10. Once the UE is reachable, the AMF performs a network triggered service request if needed to move the UE into connected state. + +11. The AMF may notify the UE and verify UE privacy requirements based on any privacy requirements received from the HGMLC in steps 4-5. If this occurs, the AMF sends a supplementary services Location Notification invoke to the UE. + +12. The UE notifies the user of the location request and verifies user permission if UE privacy is to be verified. The UE then returns a supplementary services Location Notification response to the AMF indicating whether the user grants or withholds permission for the location request when UE privacy is verified. + +13. The AMF determines an LMF, e.g. based on an LMF identity provided by the VGMLC in step 5, the type of location request and current UE access type(s) or as described for step 6 in Figure 6.14.3.1-1. The AMF then invokes the Nlmf\_Location\_DetermineLocation Request service operation towards the LMF to initiate a request for deferred UE location. For a request for periodic or triggered location, the AMF includes all the information received in step 5 including the HGMLC contact address and LDR reference number. For a request for the UE available location event, the HGMLC contact address and LDR reference number are not included. In all cases, the request includes an LCS Correlation identifier, the serving cell identity, the client type and may include the required QoS and Supported GAD shapes. + +14. The LMF instigates a UE positioning procedure using the UE Assisted and UE Based Positioning Procedure described in clause 4.13.5.4 of TS 23.502 [5] and/or the Network Assisted Positioning Procedure described in clause 4.13.5.5 of TS 23.502 [5]. During this procedure, the LMF may request and obtain the UE positioning capabilities (e.g. which may indicate the type(s) of periodic and triggered location supported by the UE and the access types supported by the UE for event reporting). The LMF may also obtain the UE location - e.g. for a request for the UE available location event or when an initial location is requested for periodic or triggered UE location. For a request for the UE available location event, the LMF skips steps 15 and 16. +15. As part of step 14 and if periodic or triggered location was requested, the LMF sends a Periodic-Triggered Location Request to the UE via the serving AMF by invoking the Namf\_Communication\_N1N2MessageTransfer service operation. The Periodic-Triggered Location Request carries the location request information received from the AMF at step 13, including the HGMLC contact address and LDR reference number. The Periodic-Triggered Location Request also includes a deferred routing identifier, which can be the identification of the LMF when the LMF will act as a serving LMF or a default LMF identification otherwise. The Periodic-Triggered Location Request may indicate the allowed access types for event reporting at step 22 (e.g. one or more of NR, E-UTRA connected to 5GC, E-UTRA connected to EPC, non-3GPP access connected to 5GC) and may indicate certain allowed or required location measurements (or a location estimate) at step 22 for each location event reported (e.g. based on the positioning capabilities of the UE obtained as part of step 14 and the allowed access types). When EDT transfer is allowed for step 24, the Periodic-Triggered Location Request may also include information for EDT reporting as described for Solution 21 in step 19 of Figure 6.21.3.2-1. As part of NAS transport of the Periodic-Triggered Location Request from the serving AMF to the UE, the serving AMF includes an immediate routing identifier in the NAS transport message identifying the LMF - e.g. as already supported in Release 15 according to clause 4.13.5.4 of TS 23.502 [5]. +- NOTE 5: The deferred routing identifier may be global (e.g. an IP address, UUID or URI) or may be local. The deferred routing identifier is used for routing in step 24. However, the immediate routing identifier included by the AMF in step 15 is used for routing in step 16. The 2 routing identifiers may or may not be the same - e.g. may be different when the deferred routing identifier is for a default LMF or a LMF which is different to the current LMF. +16. If the request in step 15 can be supported, the UE returns an acknowledgment to the LMF as part of step 14, which is transferred via the serving AMF using the immediate routing identifier and delivered to the LMF using an Namf\_Communication\_N1MessageNotify service operation. +- NOTE 6: The Periodic-Triggered Location Request sent at step 15 and its acknowledgment at step 16 may be messages for a positioning protocol (e.g. LPP) or may be messages for a separate protocol (e.g. a supplementary services protocol). In the latter case, each message may carry an embedded positioning protocol message to enable the LMF to request or allow specific location measurements from the UE at step 24 and to set up an initial location session for the location reporting at step 24. +17. The LMF invokes the Nlmf\_Location\_DetermineLocation Response service operation towards the AMF to respond to the request at step 13. For a request for the UE available location event, the response includes any UE location obtained at step 14 and the LMF then releases all resources. For a periodic or triggered location request, the response includes any location obtained at step 14, a confirmation of whether periodic or triggered location was successfully activated in the UE according to steps 15 and 16 and the identification of the LMF in the case of successful activation with a serving LMF; the LMF also retains state information and resources for later steps if the LMF acts a serving LMF. +18. The AMF invokes the Namf\_Location\_EventNotify service operation towards the VGMLC and includes any location received at step 17 and for periodic or triggered location, a confirmation of whether periodic or triggered location was successfully activated in the target UE. The VGMLC may be the same VGMLC used in steps 5 and 6 or may be a different VGMLC. In the case of a different VGMLC, the AMF includes the HGMLC contact address and LDR reference number. The AMF also includes the LMF identification if received at step 17. The AMF may then release all resources for the location request and cease support for the procedure. +19. The VGMLC forwards the response received at step 18 to the HGMLC using the HGMLC contact address received at step 18 (for a different VGMLC) or received and stored at step 4 (for the same VGMLC) and includes the LDR reference number and any LMF identification that was received. The VGMLC may then release all resources for the location request and cease support for the procedure. +- NOTE 7: As an optional optimization, instead of performing steps 18 and 19, the AMF may invoke the Namf\_Location\_EventNotify service operation directly towards the HGMLC (e.g. if a VGMLC is not used or if the VGMLC ceases support after step 8). + +20. The HGMLC forwards the response to the external LCS client. If the location request at step 1 was for the UE available location event, the procedure terminates here and further steps 21-40 are not performed. + 21. For a periodic or triggered location request where steps 15 and 16 were successfully performed, the UE monitors for occurrence of the trigger or periodic event requested in step 15. When a trigger event is detected and if the UE is camped on or connected to (or can otherwise access) an access type allowed by the LMF at step 15, the UE proceeds to step 22. If the UE cannot access an allowed access type, the UE may skip reporting the trigger event or may report the trigger event at a later time when an allowed access type becomes available, according to requirements received from the LMF at step 15. + 22. The UE obtains any location measurements or a location estimate that were requested or allowed at step 15. + 23. The UE performs a service request if in idle state and if the UE will report the location event using a NAS signalling connection at step 24. The description here assumes that 3GPP access to 5GC is used for steps 23-27, although similar steps can apply to non-3GPP access to 5GC. + 24. The UE sends an event report message to the LMF which is transferred via the serving AMF (which may be different to the original serving AMF for steps 14-16) and is delivered to the LMF using an Namf\_Communication\_NIMessageNotify service operation. The event report may indicate the type of event being reported and includes any location measurements or location estimate obtained at step 22. The UE also includes the deferred routing identifier received in step 15 in the NAS Transport message used to transfer the event report from the UE to the AMF. The AMF then forwards the event report to either the serving LMF or any suitable LMF based on whether the deferred routing identifier indicates a particular LMF or any (default) LMF. The UE also includes the HGMLC contact address, the LDR reference number, whether location estimates are to be reported and if so the location QoS in the event report. The event report may be transferred to the serving AMF using a NAS signalling connection if the UE is in connected state or may be transferred using the EDT procedure described for Solution 21 by performing steps 29-32 in Figure 6.21.3.2-1. +- NOTE 8: When forwarding the event report message to the LMF in step 24 or when forwarding an uplink positioning message to the LMF in step 26 when step 26 is performed, the AMF does not include an LCS Correlation Identifier (because the AMF does not have an LCS Correlation Identifier). To allow the AMF to be aware that an LCS Correlation Identifier is not needed, the deferred routing identifier sent by the LMF in step 15 and possibly reassigned in step 25 can indicate that an LCS Correlation Identifier is not used. For example, a deferred routing identifier could include a flag or could be selected from a different range of identifiers to the immediate routing identifier sent by the AMF at step 15. +25. Unless the event report was sent at step 24 using EDT where a response from the LMF is not allowed, the LMF returns an acknowledgment for the event report to the UE. The acknowledgment may optionally include a new deferred routing identifier indicating a new serving LMF or a default (any) LMF. +- NOTE 9: The event report and acknowledgment sent at steps 24 and 25 may be messages for a positioning protocol (e.g. LPP) or may be messages for a separate protocol (e.g. a supplementary services protocol). In the latter case, the event report at step 24 may carry an embedded UL positioning message to enable the UE to include any location measurements or location estimate obtained at step 22. +- NOTE 10: Inclusion of a new deferred routing identifier in the event report acknowledgment at step 25 may be used to change the serving LMF (e.g. if a UE moves into an area or to an access type that is better supported by a different LMF or if the serving LMF is overloaded) or to enable a default LMF to become a serving LMF. +26. If the UE sends the event report to the LMF at step 24 using a NAS signalling connection when in connected state, the LMF may obtain location measurements or a location estimate for the UE by performing a UE positioning procedure using the UE Assisted and UE Based Positioning Procedure described in clause 4.13.5.4 of TS 23.502 [5] and/or the Network Assisted Positioning Procedure described in clause 4.13.5.5 of TS 23.502 [5]. + 27. If a location estimate is needed for event reporting, the LMF determines the UE location using the location measurements and/or location estimate(s) obtained at step 24 and/or step 26. + 28. The LMF selects a VGMLC (which may be different to the VGMLC for steps 3-8 and steps 18-20) and invokes an Nlmf\_EventNotify service operation towards the VGMLC with an indication of the type of event being reported, the H-GMLC contact address and LDR reference number, the identification of the LMF, and any location estimate obtained at step 27. + +NOTE 11: The LMF may select the VGMLC for step 28 using the NRF service or using configuration information in the LMF or may use the same VGMLC as for steps 3-8 (e.g. if the LMF acts as a serving LMF and received the VGMLC address from the AMF as part of step 13). + +29. The VGMLC forwards the information received in step 28 (e.g. including the type of event being reported, the LDR reference number and possibly the LMF identification) to the HGMLC which identifies the periodic and triggered location request from the LDR reference number. + +NOTE 12: As an optional optimization, instead of performing steps 28 and 29, the LMF may invoke the Nlmf\_EventNotify service operation directly towards the HGMLC. + +30. The HGMLC uses the LDR reference number received in step 29 to identify the periodic and triggered location request received in step 1 and then sends the type of event being reported and any location estimate to the external LCS client. The HGMLC may also verify UE privacy requirements before reporting the event and any location to the external LCS client. + +31. The UE continues to monitor for further periodic or trigger events and instigates steps 22-30 each time a trigger event is detected. + +NOTE 13: If the target UE is unable to access the 5GCN in the VPLMN for a repetition of step 23 but is allowed to and can access E-UTRA connected to EPC for the VPLMN, the UE may report the location event using event reporting for the Deferred EPC-MT-LR for Periodic and Triggered Location procedure described in clause 9.1.19 of TS 23.271 [6] by instigating steps 13-24 in Figure 9.1.19.1-1 in TS 23.271 [6]. In this case, the UE includes the HGMLC contact address and LDR reference number when sending the MO-LR Invoke at step 14 for Figure 9.1.19.1-1 in TS 23.271 [6] which enables the serving MME for the UE to report the location event to the HGMLC using steps 19-21 in Figure 9.1.19.1-1 in TS 23.271 [6]. Typically, the E-SMLC used for the procedure in clause 9.1.19 of TS 23.271 [6] would be different and separate from the LMF for steps 14-16 here, although a proprietary procedure might be used by a VPLMN to enable the E-SMLC to access (e.g. read and/or modify) state information for the UE in the LMF (e.g. using the HGMLC contact address and LDR reference number as a key to identify the UE state information), which might assist location of the UE by the E-SMLC and/or by the LMF at a later time. + +32. In order to cancel the location request (e.g. if the UE is powered off or if the user wishes to cancel the location), the UE performs step 24 and optionally step 23 to send a Cancel Location request message to the LMF indicating that periodic or triggered location was cancelled. + +33-35. The LMF forwards the cancellation request to the HGMLC and external LCS client. + +36. If the external LCS client wishes to cancel the periodic or triggered location, the external LCS client sends a request to the HGMLC. + +37-38. The HGMLC determines the serving AMF address as in steps 2-3 and forwards the cancellation request to the AMF either directly or via a VGMLC. The HGMLC includes the HGMLC contact address, the LDR reference number and the latest LMF identification received in step 19 or step 29 if either step has occurred and included an LMF identification. + +39. If an LMF identification was included in steps 37-38, the AMF forwards the cancellation request to the indicated LMF by invoking an Nlmf\_CancelLocation service operation and includes the HGMLC contact address and LDR reference number. The LMF then releases all resources for the location request. + +40. The AMF sends the cancellation request to the target UE as soon as the target UE becomes reachable and includes the HGMLC contact address and the LDR reference number. The UE then releases all resources for the location request. + +NOTE 14: Steps 39 and 40 are only performed if step 18 has already occurred and periodic or triggered location was activated in the UE. In this case, the AMF will have no knowledge of the location request (since all resources are released after step 18) and can thereby determine that step 18 must have occurred. If step 38 occurs before step 18, the AMF only performs steps 39 and 40 if step 13 has already occurred (and after step 17 occurs). Otherwise, if step 13 has not yet occurred, steps 39 and 40 are omitted. + +NOTE 15: The cancellation request sent to the UE at step 40 could be a message for supplementary services or a NAS message and can be resolved later as part of stage 3 definition. + +#### 6.14.3.4 LMF change procedure via serving LMF + +When a serving LMF is used for the procedure in Figure 6.14.3.3-1, mobility of the target UE may lead to a change of serving AMF for which the original serving LMF is not suitable. For example, the serving LMF may be very remote from the AMF leading to higher resource utilisation for AMF to LMF signalling or the LMF may not be configured with information (e.g. a cell database) for the current access network for the UE to enable location. In such a case, the serving LMF may need to change. Figure 6.14.3.4-1 shows a procedure to enable change of the serving LMF when a UE sends an event report at step 24 in Figure 6.14.3.3-1. + + + +``` + +sequenceDiagram + participant UE + participant RAN as (R)AN + participant AMF + participant LMF1 + participant LMF2 + + Note left of UE: 1. UE Triggered Service Request + UE->>AMF: 2. NAS Transport (LMF1 ID, Event Report) + Note right of AMF: 3. Determine new LMF2 + AMF->>LMF1: 4. Namf_Communication_N1MessageNotify (Event Report, new LMF2) + Note right of LMF1: 5. Determine new LMF2 + LMF1->>LMF2: 6a. Nlmf_LocationContextTransfer Request (Event Report) + LMF2-->>LMF1: 6b. Nlmf_LocationContextTransfer Response + AMF->>LMF2: 7. Namf_Communication_N1N2MessageTransfer Request (Event Report Acknowledgment) + AMF->>UE: 8. NAS Transport (Event Report Acknowledgment) + LMF2-->>AMF: 9. Namf_Communication_N1N2MessageTransfer Response + Note left of UE: 10. UE Positioning Procedure + Note right of LMF2: 11. Determine UE Location + +``` + +Sequence diagram illustrating the LMF change procedure via serving LMF. The diagram shows interactions between UE, (R)AN, AMF, LMF1, and LMF2. The process starts with a UE Triggered Service Request (1) from UE to AMF. The UE then sends a NAS Transport message (2) containing an event report to the AMF. The AMF evaluates and determines a new LMF2 (3). The AMF then sends a Namf\_Communication\_N1MessageNotify (4) to LMF1, indicating the event report and the new LMF2. LMF1 evaluates and determines a new LMF2 (5). LMF1 then sends an Nlmf\_LocationContextTransfer Request (6a) to LMF2, which responds with an Nlmf\_LocationContextTransfer Response (6b). The AMF then sends a Namf\_Communication\_N1N2MessageTransfer Request (7) to LMF2, which responds with a Namf\_Communication\_N1N2MessageTransfer Response (9). The AMF then sends a NAS Transport message (8) containing an event report acknowledgment to the UE. The UE then performs a UE Positioning Procedure (10) with LMF2, which determines the UE location (11). + +**Figure 6.14.3.4-1: Change of serving LMF for periodic and triggered UE location events** + +Precondition: Steps 1-22 in Figure 6.14.3.3-1 have been performed including possibly a repetition of steps 21-22 for a subsequent event report. A serving LMF is used and the current serving LMF is LMF1. + +1. The UE performs a service request if needed as for step 23 in Figure 6.14.3.3-1. +2. The UE sends a NAS Transport message containing an event report message to the serving AMF. The NAS Transport message includes a deferred routing identifier indicating LMF1. Step 2 corresponds to part of step 24 for Figure 6.14.3.3-1. +3. Based on operator configuration and policy, the AMF may evaluate and determine that LMF1 is unsuitable or unable to support location for the current UE access network or serving cell and determines LMF2 as being a more suitable LMF. +4. The AMF invokes the Namf\_Communication\_N1MessageNotify service operation towards LMF1. The service operation includes the event report received in step 2. If the AMF determined in step 3 that a new LMF2 should be used, it indicates that to the LMF1 as well. +5. If AMF did not indicate a new LMF in step 4, based on the operator configuration and policy, LMF1 may evaluate and determine that it is unsuitable or unable to support location for the current UE access network or serving cell and determines LMF2 as being a more suitable LMF. +- 6a. LMF1 invokes an Nlmf\_LocationContextTransfer service operation towards LMF2 to provide the current location context of the UE and includes the event report message received in step 3. The service operation includes the AMF identity and all the information originally received by LMF1 for the periodic or triggered location request either from the AMF according to the procedure in Figure 6.14.3.3-1 or from an earlier serving LMF according to this procedure. The service operation may also include the current status of event reporting (e.g. the number of event reports so far received from the UE and/or the duration of event reporting so far) and + +may include location related information for the UE such a previous location estimate or location measurements. LMF1 then releases all resources for the procedure. + +6b. LMF2 informs LMF1 of the location context transfer operation results. + +7. LMF2 invokes the Namf\_Communication\_N1N2MessageTransfer service operation towards the AMF to request the transfer of an Event Report Acknowledgment message to the UE. The Event Report Acknowledgment indicates a change of LMF and includes a deferred routing identifier indicating LMF2. + +NOTE: In a network where change of an serving LMF is possible, the original serving LMF shall not allow the UE to use EDT transfer at step 2 in which a response from the serving LMF is not possible. This will avoid not being able to return the deferred routing identifier indicating the new serving LMF2 to the UE in step 6. + +8. The AMF forwards the Event Report Acknowledgment to the UE in a NAS Transport message. + +9. The AMF informs the LMF2 of the result of the delivery of the Event Report Acknowledgement using the NAS Transport message. + +10. Unless EDT transfer is used at stage 2, LMF2 may obtain location measurements or a location estimate for the UE by performing a UE positioning procedure as at step 26 in Figure 6.14.3.3-1. + +11. If a location estimate is needed for event reporting, LMF2 determines the UE location as at step 27 in Figure 6.14.3.3-1. The rest of the procedure in Figure 6.14.3.3-1 then continues from step 28 with LMF2 retaining state information to enable support of subsequent event reports from the UE. + +### 6.14.4 Impacts on existing entities and interfaces + +#### 6.14.4.1 Impacts to UDR and UDM + +Impacts to UDR: New Data Subset of the Subscription Data Storage, i.e. the privacy setting of the target UE and the location subscriber authorization data of the requestor UE. + +Impacts to UDM: + +- GMLC being a new consumer of UDM service operation; +- new Subscription data types: UE LCS privacy and location subscriber authorization data of the requestor UE. + +#### 6.14.4.2 Impacts to GMLC + +- Capability to invoke Nudm\_SDM\_Get service operation. +- Capability of LCS service request handling based on target UE privacy setting. +- GMLC to GMLC interface (and addition of the V-GMLC role). +- Support a deferred location request from an external LCS Client (impact may be the same as for EPS) +- Forward a deferred location request from an HGMLC to a VGMLC (impact may be the same as for EPS) +- Forward a deferred MT-LR location request to an AMF and receive an immediate confirmation of acceptance and later confirmation of activation in the target UE and return these to an HGMLC or external LCS client. +- Receive event reports from an LMF and forward these to an HGMLC or external LCS client. +- Support cancelation of a periodic or triggered location. + +#### 6.14.4.3 Impacts to UE + +UE impacts comprise the following: + +- Support for privacy notification and verification for a 5GC-MT-LR. +- Support for invocation of a 5GC-MO-LR. + +- Support receipt of a Periodic-Triggered Location Request from an LMF for periodic triggered location and an ability to confirm or reject the request. +- Monitor for periodic or triggered location events and report the occurrence of an event to an LMF along with any requested location measurements or location estimate. +- Support change of an serving LMF during location event reporting. +- Support cancelation of periodic or triggered event reporting by the UE or by an external LCS Client. + +#### 6.14.4.4 Impacts to AMF + +AMF impacts comprise the following: + +Support for privacy notification and verification for a 5GC-MT-LR. + +- Support for an 5GC-MO-LR. + +Support a deferred MT-LR location request from a VGMLC or HGMLC. + +- Support an immediate response to a VGMLC or GGMLC to confirm acceptance of a periodic or triggered request and a later response to the VGMLC or HGMLC to confirm activation of the periodic or triggered location request in the UE. +- Support cancelation of a periodic or triggered location. +- Optionally support change of a serving LMF by determining a new LMF. +- Support a request for a deferred periodic or triggered location request for a target UE. + +#### 6.14.4.5 Impacts to LMF + +LMF impacts comprise the following: + +- Support a request for a deferred periodic or triggered location request for a target UE received from an AMF. +- Send a Periodic-Triggered Location Request to the UE to activate periodic or triggered location in the UE and receive a confirmation (or rejection) from the UE and include this in the response to the AMF. +- Receive triggered or periodic events reports from the UE for events detected by the UE and obtain the UE location if this is needed and forward the event report and any location to a VGMLC or HGMLC for return to an external LCS Client. +- support change of a serving LMF including determining a new LMF and sending location context information for the UE to the new serving LMF. +- Support cancelation of a periodic or triggered location. + +### 6.14.5 Evaluation + +**Editor's note:** This clause provides an evaluation of the solution. + +## 6.15 Solution 15: Enhancement to LCS architecture + +### 6.15.1 Introduction + +This solution addresses the modified Key Issue 1 "Enhancement to LCS architecture" and proposes LMF architecture split by including Location Management (LM) capabilities in the NG-RAN and the UE. Further, the impact to the 5GC, particularly LMF, are discussed. The solution also applies to Key Issue#3 "support of low latency LCS" and Key Issue#8 "Support of IoT UEs". + +### 6.15.2 Functional Description + +The solution proposal includes LM capabilities assigned to the NG-RAN and UE, referred as RAN-LMC (Location Management Component) and UE-LMC respectively, as shown in Figure 6.15.2-1. Legacy LCS functions from + +TS 23.271 [6] as well as enhanced LCS functions based on new positioning requirements and methods may be mapped to these roles. + +NOTE 1: The bullets of roles in NG-RAN and UE listed in this clause are subject to further work from RAN WGs. + + + +Figure 6.15.2-1: Enhanced LCS architecture with local LMF. The diagram shows a UE (User Equipment) connected to an NG RAN (Next Generation Radio Access Network). The UE contains a UE-LMC (Location Management Component) and the NG RAN contains a RAN-LMC. The NG RAN is connected to an AMF (Access and Management Function) via the N2 interface. The AMF is connected to an LMF (Location Management Function) via the NLs interface and to a GMLC (Gateway Mobile Location Centre) via the NLg interface. The GMLC is connected to a UDM (Unified Data Management) via the NLh interface and to an LRF (Location Retrieval Function) via the Le interface. The LMF is also connected to the UDM via the NLs interface. The AMF, LMF, GMLC, and LRF are part of the 5GC (5G Core). The GMLC is connected to an External Client via the Le interface. + +**Figure 6.15.2-1: Enhanced LCS architecture with local LMF** + +The RAN-LMC and UE-LMC perform partial location management role in the RAN and UE respectively and implement a subset of the functionalities of the LMF in the 5GC, as well as new functionalities arising out of performing location management at the RAN/UE levels. + +The RAN-LMC and UE-LMC perform the following roles in the enhanced LCS architecture: + +- Location measurement collection: collect location-related measurements for the Uu interface. +- Position calculation: compute absolute/relative positions based on collected location measurements. +- Location information report: report calculated positions to requesting entities over the Uu interface. +- Cooperation among peers: share location measurements, position-related information, load balancing, etc. among peer LMCs. +- Positioning performance monitoring: monitor and predict positioning performance. +- Communication to CN: Communicate with LMF, AMF and other 5GC LCS functions. + +NOTE 2: Details of some LCS functionalities and new positioning methods should be studied in RAN WGs. + +The LMF in 5GC should perform additional procedures in order to enable the RAN-LMC and UE-LMC to function in the enhanced LCS architecture: + +- Capability verification: Verify the positioning capabilities of RAN- or UE-LMCs. +- Authorization: authorize RAN- or UE-LMCs to operate in the network. +- Location group management: Manage grouping of RAN- or UE-LMCs for cooperation in order to meet positioning KPIs. +- Privacy management: Configure privacy rules for information sharing between and within groups of RAN- or UE LMCs. +- Location performance control: location performance management to control and guarantee overall positioning performance. +- Subscriber management: Billing and charging for RAN- or UE-LMCs. +- Location service management: allow for different and new types of location services to be provided by the RAN- or UE LMCs. + +### 6.15.3 Procedures + +#### 6.15.3.1 RAN-LMC registration + +Figure 6.15.3-1 shows a procedure which may be used by a RAN to register its LMC to LMF or by the LMF to activate a RAN-LMC in order to offload LCS traffic. This procedure is not associated with a UE location session. It is used to grant the use of a RAN-LMC at the LMF in 5GC. The procedure may be based on an NRPPa protocol in TS 38.455 [11] between the LMF and NG-RAN. + + + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant AMF + participant LMF + Note left of UE: Coordination between RAN-LMC and UE for location service related tasks + NG-RAN->>AMF: 1. N2 Transport (LMC registration request) + AMF->>LMF: 2. Namf_Communication_N2InfoNotify (LMC registration request) + LMF->>LMF: 3. Registration + LMF->>AMF: 4. Namf_Communication_N2MessageTransfer (LMC registration grant) + AMF->>NG-RAN: 5. N2 Transport (LMC registration grant) + +``` + +Sequence diagram for RAN-LMC registration at LMF. The diagram shows five steps: 1. NG-RAN sends an N2 Transport (LMC registration request) to AMF. 2. AMF sends a Namf\_Communication\_N2InfoNotify (LMC registration request) to LMF. 3. LMF performs Registration. 4. LMF sends a Namf\_Communication\_N2MessageTransfer (LMC registration grant) to AMF. 5. AMF sends an N2 Transport (LMC registration grant) to NG-RAN. A box at the bottom left indicates 'Coordination between RAN-LMC and UE for location service related tasks'. + +**Figure 6.15.3-1: Procedure for RAN-LMC registration at LMF** + +1. In case that the registration procedure is initiated by a RAN, the RAN includes an LMC registration request in an N2\_Transport message. +2. The AMF selects an LMF and invokes the Namf\_Communication\_N2InfoNotify service operation towards this LMF to transfer the LMC registration request. The service operation includes the RAN node identity. +3. The LMF determines if the registration can be granted based on the RAN's capability. In case that the procedure is initiated by the LMF, step 1 and 2 are omitted. Based on certain factors such as the LCS QoS and/or LMF traffic load, the LMF determines if an LMC in RAN should be granted. +4. The LMF invokes the Namf\_Communication\_N2MessageTransfer service operation towards the AMF to request the transfer of an LMC registration grant to a RAN node. The service operation includes the RAN node identity. +5. The AMF forwards the LMC registration grant to the RAN node indicated in step 4 in an N2 Transport message. The AMF includes a Routing identifier, in the N2 Transport message, identifying the LMF as the manager of the RAN-LMC. + +NOTE: Coordination procedures between UE and RAN-LMC should be studied within RAN scope. + +Alternatively, RAN-LMC registration may be handled by AMF. The procedure is adjusted as it is shown in Figure 6.15.3-2. This procedure may be combined with NG setup or RAN configuration update procedure over NG-AP in TS 38.413 [26]. The AMF informs the LMF about the LMC registration using AMF service message. + + + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant AMF + participant LMF + Note left of NG-RAN: Coordination between RAN-LMC and UE for location service related tasks + NG-RAN->>AMF: 1. NGAP (LMC registration request) + AMF->>AMF: 2. Registration + AMF->>NG-RAN: 3. NGAP (LMC registration grant) + AMF->>LMF: 3a. Namf_LMC registration/update + +``` + +Sequence diagram for RAN-LMC registration at AMF. Lifelines: UE, NG-RAN, AMF, LMF. 1. NG-RAN sends NGAP (LMC registration request) to AMF. 2. AMF performs Registration. 3. AMF sends NGAP (LMC registration grant) to NG-RAN. 3a. AMF sends Namf\_LMC registration/update to LMF. A box labeled 'Coordination between RAN-LMC and UE for location service related tasks' is shown between UE and NG-RAN. + +**Figure 6.15.3-2: Procedure of RAN-LMC registration at AMF** + +#### 6.15.3.2 LMC performance control + +The LMF monitors the performance of the registered RAN-LMC by receiving LMC performance report. The LMC performance report may be provided in an on-demand or periodic manner. Figure 6.15.3-3 shows the procedure for on-demand performance report. The performance reports may consist LCS QoS information and LCS load at RAN-LMC. The LMF makes further decision, such as deactivation or activation/usage of new RAN-LMCs, based on the performance report obtained. This procedure is not associated with a UE location session and based on an NRPPa protocol between the LMF and NG-RAN. + + + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant AMF + participant LMF + LMF->>AMF: 1. Namf_Communication_N2MessageTransfer (request LMC performance report) + AMF->>NG-RAN: 2. N2 Transport (request LMC performance report) + Note right of NG-RAN: 3. Calculate performance report + NG-RAN->>AMF: 4. N2 Transport (provide LMC performance report) + AMF->>LMF: 5. Namf_Communication_N2InfoNotify (provide LMC performance report) + +``` + +Sequence diagram for RAN-LMC performance control at LMF. Lifelines: UE, NG-RAN, AMF, LMF. 1. LMF sends Namf\_Communication\_N2MessageTransfer (request LMC performance report) to AMF. 2. AMF sends N2 Transport (request LMC performance report) to NG-RAN. 3. NG-RAN calculates performance report. 4. NG-RAN sends N2 Transport (provide LMC performance report) to AMF. 5. AMF sends Namf\_Communication\_N2InfoNotify (provide LMC performance report) to LMF. + +**Figure 6.15.3-3: Procedure for RAN-LMC performance control at LMF** + +1. The LMF invokes the Namf\_Communication\_N2MessageTransfer service operation towards the AMF to request the LMC performance report to a RAN node. The service operation includes the RAN node identity. +2. The AMF forwards the LMC performance report request to the RAN node indicated in step 1 in an N2 Transport message. + +NOTE: Step 1-2 are optional and used only in case of LMF is requesting a LMC performance report(e.g., triggered by resource demanding/low latency location service request). + +3. The RAN-LMC obtains the performance report requested in step 2. +4. The RAN node returns the performance report obtained in step 3 to the AMF in an N2 Transport message. The RAN node shall also include the Routing identifier of the manager LMF received at registration. + +5. The AMF invokes the Namf\_Communication\_N2InfoNotify service operation towards the LMF indicated by the routing identifier received in step 4. The service operation includes the LMC performance report received in step 4. + +Alternatively, RAN-LMC performance control may be handled by AMF. This procedure may be combined with the RAN configuration update procedure over NG-AP in TS 38.413 [26] as it is shown in Figure 6.15.3-4. AMF may request performance report from LMC (e.g., triggered by resource demanding/low latency location service request), and determines whether a new LMC needs to be activated/deactivated/used, the required configuration of RAN-LMCs, based on the performance report (e.g., LCS QoS information and LCS load) obtained. The AMF may provide the performance report to LMF using AMF service message. + + + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant AMF + participant LMF + Note right of NG-RAN: 2. Calculate performance report + AMF->>NG-RAN: 1. NGAP (request LMC performance report) + NG-RAN-->>AMF: 3. NGAP (provide LMC performance report) + AMF->>LMF: 3a. Namf_LMC registration/update + +``` + +Sequence diagram illustrating the procedure for RAN-LMC performance control at AMF. The diagram shows four lifelines: UE, NG-RAN, AMF, and LMF. The sequence of messages is: 1. AMF sends an NGAP (request LMC performance report) to NG-RAN. 2. NG-RAN calculates the performance report. 3. NG-RAN sends an NGAP (provide LMC performance report) to AMF. 3a. AMF sends a Namf\_LMC registration/update message to LMF. + +**Figure 6.15.3-4: Procedure for RAN-LMC performance control at AMF** + +In some circumstance, LMC registration and LMC performance control procedures can be combined. For instance, the LMC registration message may include also the LMC performance report information. Whenever the LMC performance changes, new LMC registration is performed. In the case of high dynamics on LCS load, RAN-LMC needs to send more frequent performance report. It is therefore unnecessary to verify capability of RAN-LMC upon reception of every performance report. Meanwhile, LMF/AMF may request LMC performance report only when needed to reduce the signalling overhead. In such cases, two independent procedures would be necessary. + +### 6.15.4 Impacts on existing entities and interfaces + +The enhanced LCS architecture requires LMC management functionalities implemented at LMF, such as LMC registration, capability verification and performance control. For the interactions between RAN-LMC and LMF, NRPPa protocol over N2 interface can be reused. + +In case the LMC management functionalities is implemented at AMF, the interactions between RAN-LMC and AMF may be based on new NGAP elementary procedures supporting LMC management, or be combined with the existing NG setup and/or RAN configuration update procedures. For both options, NG-RAN supports the functionality of LMC. + +### 6.15.5 Evaluation + +This solution proposes to distribute location management capability in RAN/UE, allowing for more flexible resource usage. When sufficient measurements and assistance information can be obtained within RAN, position calculation may be carried out at LMC in RAN. This avoids the signalling overhead from sending measurements to the centralized LMF in 5GC. For use cases with stringent latency requirements, a LMF may authorize LMC close to UE in order to reduce the delay caused by communication to the LMF in CN. + +The proposal also provides necessary procedures to include LMC management functionalities at either LMF or AMF. The pros and cons of the two options are summarized in Table 6.15-1. + +Table 6.15-1 + +| | Pros | Cons | +|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------| +| LMC management at LMF | Clean design: all LCS related functionalities are implemented at LMF. Allow for different location management architecture (e.g., hierarchical). | Longer communication path to LMC --> higher latency. | +| LMC management at AMF | Shorter communication path to LMC --> lower latency. | Complex functionality split between AMF and LMF. Synchronization of LMC management needed between AMF and LMF.
Increased complexity at AMF. | + +## 6.16 Solution 16: Solution for position via user plane transmission + +### 6.16.1 Introduction + +This solution addresses Key Issue 2 on Positioning via user plane transmission. + +### 6.16.2 Functional Description + +At network side, 5G LMF and UCF (User plane Connection Function) are required to support position via user plane. UCF establishes the secure connection with UE via user plane, and it transfers the SUPL message between UE and 5G LMF. 5G LMF supports MO and MT positioning via user plane, and 5G LMF computes the UE location according to the position measurement data contained in SUPL messages. + +### 6.16.3 Procedures + +#### 6.16.3.1 UE establishes the connection with UCF + +The flow below indicates the UE establishes the security connection with UCF. + + + +``` + +sequenceDiagram + participant UE + participant UCF + participant UDM + Note left of UE: 1. Discover UCF + Note left of UE: 2. Establish security connection between UE and UCF + UCF->>UDM: 3. Nudm_UECM_Registration Request + UDM-->>UCF: 4. Nudm_UECM_Registration Response + +``` + +Sequence diagram showing the connection establishment between UE and UCF. The diagram involves three lifelines: UE, UCF, and UDM. The sequence of messages is: 1. Discover UCF (internal to UE), 2. Establish security connection between UE and UCF (internal to UE), 3. Nudm\_UECM\_Registration Request (from UCF to UDM), and 4. Nudm\_UECM\_Registration Response (from UDM to UCF). + +Figure 6.16.3.1-1: the connection establishment between UE and UCF + +1. URSP configured in the UE may indicate which PDU session is used to establish the connection with UCF. UE retrieves UCF address via e.g. DNS mechanism or local configuration. For roaming scenario, UE interacts the UCF in VPLMN. +2. NF requests to establish the security connection with the selected UCF via user plane. +3. UCF sends Nudm\_UECM\_Registration Request (Public UE Identity, UCF NF type, UCF NF ID) to UDM to perform the serving NF registration. + +4. UDM stores the associated UE with the serving UCF, and it responds to UCF via Nudm\_UECM\_Registration Response message. + +After establishing the connection, UE and UCF maintain the connection context for later message transfer via user plane. + +#### 6.16.3.2 UE initiated position via user plane + +The flow below indicates the UE initiates position via user plane. + + + +``` +sequenceDiagram + participant UE + participant UCF + participant LMF + Note left of UE: UE already established connection with UCF + UE->>UCF: 1. Uplink message (message type, UE Identity, SUPL Payload) + Note right of UCF: 2. Determine the target NF + UCF->>LMF: 3. Nucf_Communication_MessageNotify(UE Identity, SUPL payload) + Note over UE, LMF: 4. SUPL position procedure +``` + +The diagram is a sequence diagram showing the interaction between a User Equipment (UE), a User Plane Function (UPF), and a Location Management Function (LMF). The sequence starts with a note on the UE side stating 'UE already established connection with UCF'. Step 1 shows the UE sending an 'Uplink message (message type, UE Identity, SUPL Payload)' to the UPF. Step 2 is a note on the UPF side indicating it will 'Determine the target NF'. Step 3 shows the UPF sending a 'Nucf\_Communication\_MessageNotify(UE Identity, SUPL payload)' to the LMF. Step 4 is a note spanning both the UE and LMF lifelines indicating the start of the 'SUPL position procedure'. + +Sequence diagram for UE initiated position via user plane + +**Figure 6.16.3.2-1: UE initiated position via user plane** + +0. UE already established the connection with UCF. +1. UE sends Uplink message including Public UE Identity, message type and SUPL payload to UCF, and the uplink message is encrypted with the security context, and message type indicates the message is for LCS service. +2. UCF decrypts the Uplink message and determines the serving NF type according to the associated message type with the serving NF type. UCF may further determine the serving LMF via requesting Nudm\_UECM\_Get serving operation from UDM if the UCF does not maintain the mapping between UE and the serving LMF. +3. UCF sends SUPL payload to the serving LMF via Nucf\_Communication\_MessageNotify including UE Identity and SUPL payload. +4. LMF identify the SUPL message and perform the SUPL positioning procedure. During SUPL procedure, UCF transfers the SUPL message between UE and LMF. + +#### 6.16.3.3 Network initiated position via user plane + +The flow below indicates the network initiates position via user plane. + + + +``` + +sequenceDiagram + participant UE + participant UCF + participant LMF + participant UDM + Note right of LMF: Determine to initiate MT LCS + LMF->>UDM: 1. Nudm_UECM_Get request response + LMF->>UCF: 2. Nucf_Communication_MessageTransfer request (UE Identity, SUPL Payload) + UCF->>UE: 3. Downlink message (SUPL payload) + Note over UE, LMF: 4. SUPL position procedure + +``` + +Sequence diagram for Network initiated position via user plane. Lifelines: UE, UCF, LMF, UDM. The sequence starts with LMF determining to initiate MT LCS. Step 1: LMF sends Nudm\_UECM\_Get request response to UDM (dashed arrow). Step 2: LMF sends Nucf\_Communication\_MessageTransfer request (UE Identity, SUPL Payload) to UCF (solid arrow). Step 3: UCF sends Downlink message (SUPL payload) to UE (solid arrow). Step 4: A box labeled '4. SUPL position procedure' spans between UE and LMF. + +**Figure 6.16.3.3-1: Network initiated position via user plane** + +0. When receiving location service request for one UE, LMF determines to initiate MT location via user plane. +1. If LMF does not store the UCF that serves the target UE, LMF may determine the serving LMF via requesting Nudm\_UECM\_Get serving operation from UDM. +2. LMF generates an SUPL initiation message and transfers it to UCF via Nucf\_Communication\_MessageTransfer request including UE Identity and SUPL payload. +3. UCF determines the target UE according to the stored context of the connection with UE, and it encrypts message and send the Downlink message to the target UE. +4. LMF and the target UE perform the SUPL positioning procedure. During SUPL procedure, UCF transfers the SUPL message between UE and LMF. + +### 6.16.4 Impacts on existing entities and interfaces + +The solution impact the following network functions: + +- New NF called "UCF" is required to establish the connection with UE and transfer the SUPL signalling between UE and LMF; +- LMF supports SUPL positioning process; +- To enable the interaction with 5GC NFs such as LMF via user plane connection, UE needs to select UCF and establish the connection with the UCF after registering the network. + +**Editor's note:** It is FFS if modifications to SUPL specifications are needed. + +### 6.16.5 Evaluation + +**Editor's note:** This clause provides an evaluation of the solution. + +## 6.17 Solution 17: Solution for Flexible and Efficient Periodic and Triggered Location + +### 6.17.1 Introduction + +This solution is intended to address Key Issue 13 on Support of Flexible and Efficient Periodic and Triggered Location. + +### 6.17.2 Functional Description + +For a 5GC location solution in which periodic and triggered location is supported and where trigger detection and instigation of event reporting is performed by a target UE, an LCS client provides an indication of the required trigger events to the 5GC (e.g. to a GMLC in the 5GC) using a transparent container along with the request for periodic and triggered location. The transparent container is subsequently transferred without alteration or interpretation through the 5GC to the UE according to how the particular 5GC location solution sends a request for periodic and triggered location to a target UE. The content of the transparent container indicates the required triggering event(s) and may include associated parameters (e.g. such a velocity or distance for triggers associated with UE velocity or UE location). The content of the transparent container is only meaningful to the LCS Client and UE and may be standardized by 3GPP, completely proprietary or partially standardized and partially proprietary (hybrid definition). As an example of a hybrid definition, 3GPP might define a high level structure for a transparent container that includes an ID or Type field having one set of standardized values and another set of proprietary values with the remainder of the container defined by 3GPP only for the set of standardized values. + +A second transparent container is used to allow a UE to report a type of detected trigger event back to an LCS Client when more than one type of trigger event is used. The second container could be included in a report of a trigger event sent from a UE to the 5GC (e.g. in an MO-LR request) and would be transferred without interpretation or alteration back to the LCS Client. The content of the second transparent container may also be standardized by 3GPP, completely proprietary or partially standardized and partially proprietary. + +When transparent containers are used, certain common parameters may be provided explicitly to the 5GC by an LCS Client to enable common support from the 5GC for all types of periodic and triggered location procedures. The common parameters may also assist the 5GC (e.g. a GMLC) to estimate resource usage in advance for a periodic and triggered location request received from an LCS Client and to decide whether to accept or reject the request. The common parameters could include: + +- Conditions for terminating a periodic and triggered location session (e.g. a maximum duration and/or a maximum number of event reports). +- Whether a location estimate is required for each event report. +- A maximum interval and/or a minimum interval between consecutive event reports. +- A maximum and/or a minimum event sampling interval for a target UE. + +### 6.17.3 Procedures + +#### 6.17.3.1 Generic Procedure + +Figure 6.17.3.1-1 shows a common generic procedure for support of a Periodic and Triggered 5GC-MT-LR Procedure using transparent containers. The procedure can be applicable to any type of Periodic and Triggered 5GC-MT-LR procedure such as the procedures described in clauses 6.2.3.3., 6.2.3.4 and 6.2.3.5 for the LMF based location solution. The messages shown in Figure 6.17.3.1-1 will depend on the particular type of Periodic and Triggered 5GC-MT-LR procedure and may be different, but the usage of the transparent containers may remain unchanged. + + + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant VPLMN_HPLMN_5GC as VPLMN / HPLMN 5GC + participant LCS_Client as LCS Client + + LCS_Client->>VPLMN_HPLMN_5GC: 1. LCS Service Request + VPLMN_HPLMN_5GC-->>LCS_Client: 2. LCS Service Response + + Note over UE, VPLMN_HPLMN_5GC: 3. UE becomes reachable + + VPLMN_HPLMN_5GC->>UE: 4. Location Notification Invoke + UE-->>VPLMN_HPLMN_5GC: 5. Location Notification Response + + VPLMN_HPLMN_5GC->>UE: 6. LCS Periodic-Triggered Event Invoke + UE-->>VPLMN_HPLMN_5GC: 7. LCS Periodic-Triggered Event Invoke Ack + + VPLMN_HPLMN_5GC-->>LCS_Client: 8. LCS Service Response + + Note over UE: 9. Event Detected + UE->>VPLMN_HPLMN_5GC: 10. Report Trigger Event (location estimate) + Note over UE, VPLMN_HPLMN_5GC: 11. UE Positioning + VPLMN_HPLMN_5GC-->>UE: 12. Report Trigger Event Ack + VPLMN_HPLMN_5GC-->>LCS_Client: 13. LCS Service Response + + Note over UE: 14. Event Detected + +``` + +Sequence diagram illustrating the Periodic and Triggered 5GC-MT-LR Procedure using Transparent Containers. The diagram shows interactions between UE, NG-RAN, VPLMN / HPLMN 5GC, and LCS Client. The procedure involves a location request, service response, reachability check, location notification, periodic event reporting, and UE positioning. + +**Figure 6.17.3.1-1: Periodic and Triggered 5GC-MT-LR Procedure using Transparent Containers** + +1. An external LCS client sends a location request for periodic and triggered location for a target UE to a VPLMN or HPLMN for the UE (e.g. a GMLC). The location request provides the type of location reporting being requested and associated parameters. The location request includes a transparent container TC1 that includes details of the trigger events to be reported. The transparent container TC1 may be encoded according to a standard (e.g. 3GPP) definition and/or a proprietary definition particular to the LCS Client. The location request may also include common parameters applicable to all type of trigger events such as a maximum duration of event reporting, a maximum number of event reports, whether a location estimate is required for each event report, a maximum interval and/or a minimum interval between consecutive event reports, and a maximum and/or a minimum event sampling interval for the target UE. +2. The HPLMN and/or VPLMN determine whether to accept or reject the location request - e.g. based on the common parameters and subscription information for the LCS Client and the target UE. For a roaming UE, where the request in step 1 is sent to the HPLMN, the HPLMN transfers the request to the VPLMN. If the request is accepted, the VPLMN or HPLMN returns a confirmation to the LCS Client. +3. If the UE is not currently reachable, the HPLMN/VPLMN waits for the UE to become reachable. +- 4-5. Once the UE is reachable, the HPLMN/VPLMN may verify UE privacy requirements, e.g. via a supplementary services interaction. +6. The HPLMN/VPLMN sends a request to the UE to perform periodic and triggered location. The request carries the location request information provided by the LCS Client in step 1, including the transparent container TC1 and any common parameters, and may include the identity of the LCS Client. +7. The UE interprets the transparent container TC1 using either a standardized 3GPP definition or a proprietary definition particular to the LCS Client. A proprietary definition may be identified from the LCS Client identity, if received in step 6, or from some standardized ID included in the container TC1 if the container is at least partially standardized. If the request can be supported, the UE returns an acknowledgment to the HPLMN/VPLMN. +8. Depending on the particular Periodic and Triggered 5GC-MT-LR procedure, the VPLMN and/or the HPLMN may return a response to the LCS Client to confirm that event reporting for periodic and triggered location was activated in the UE. + +9. The UE monitors for occurrence of the trigger event(s) defined by the transparent container TC1. When a trigger event is detected, the UE proceeds to step 10. +10. The UE sends a report to the HPLMN/VPLMN for the detected trigger event and may include a location estimate if available to the UE and if requested in step 6. The report may include a second transparent container TC2 indicating the type of detected trigger event, e.g. when more than one type of trigger event was requested by the LCS Client. +11. If a location estimate was not included in step 10 and if reporting of location estimates was requested by the LCS Client, the HPLMN/VPLMN performs positioning of the UE and obtains a location estimate. +12. The HPLMN/VPLMN send an acknowledgment to the UE to confirm that an event report will be sent to the LCS client. +13. The HPLMN/VPLMN sends an event report to the LCS Client and includes any transparent container TC2 received at step 10 and any location estimate received at step 10 or obtained at step 11. +14. The UE continues to monitor for further trigger events and instigates steps 10-13 each time a trigger event is detected. + +### 6.17.4 Impacts on existing entities and interfaces + +Impacts to existing entities and interfaces in the 5GS are as follows. + +VPLMN / HPLMN (e.g. GMLC, LMF, AMF): + +- transfer a transparent container from an LCS Client to a target UE as part of a periodic and triggered 5GC-MT-LR request. +- transfer a transparent container from a target UE to an LCS Client as part of reporting the occurrence of a trigger event. + +UE: + +- Interpret a transparent container sent by an LCS Client as part of a periodic and triggered 5GC-MT-LR request. +- Detect and report the trigger events defined by the transparent container. +- Include a transparent container indicating a detected trigger event in a report of the trigger event when more than one type of trigger event was instigated for a periodic and triggered location session. + +LCS Client: + +- Support of receiving and processing a transparent container sent by an UE as part of the LCS service response. +- Support of generating and signal a transparent container to a target UE as part of a LCS service request. + +### 6.17.5 Evaluation + +**Editor's note:** This clause provides an evaluation of the solution. + +## 6.18 Solution #18: UDM based Positioning Access selection for LCS service + +### 6.18.1 Introduction + +This solution addresses the Key Issue 14: Positioning Access selection for LCS service. + +### 6.18.2 Functional Description + +When UE accesses 5GC via 3GPP access and non-3GPP access simultaneously, the UDM is responsible to manage separate/independent UE Registration procedures for each access. For example, when UE initiates Registration procedure over 3GPP access, the AMF registers with the UDM by providing, e.g. AMF ID and Access Type. The UDM + +stores the AMF ID associated to the Access Type and does not remove the AMF ID associated to the other Access Type. + +When UDM receives request from GMLC, it is proposed that UDM decides access type to perform the positioning procedure based on, e.g. access type and associated serving AMF which is provided by AMF during Registration procedure and the UE state change in the access type (e.g. connectivity state changes) which is obtained by subscribing UE access and mobility information event to AMF. The UDM provides Access Type to the GMLC. + +### 6.18.3 Procedures + + + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant AMF + participant LMF + participant V-GMLC + participant UDM + participant H-GMLC + participant LCS Client + + LCS Client->>H-GMLC: 1. LCS Service Request + H-GMLC->>UDM: 2. Nudm_UEContextManagement_Get Request + UDM-->>H-GMLC: 3. Nudm_UEContextManagement_Get Response +(AMF address, V-GMLC address, LMF address, Access Type) + H-GMLC->>V-GMLC: 4. LCS Service Request + + rect rgb(240, 240, 240) + Note over V-GMLC, LMF: (A) + V-GMLC->>LMF: 5a. Nlmf_ProvideLocation_Request (Access Type) + LMF->>AMF: 6a. Namf_Communication_N1N2MessageTransfer +(Positioning Message, Access Type) + end + + rect rgb(240, 240, 240) + Note over V-GMLC, AMF: (B) + V-GMLC->>AMF: 5b. Namf_Location_ProvideLocation_Request (Access Type) + end + + Note over UE, NG-RAN: 7. Obtain locations via 3GPP access + Note over UE, NG-RAN: N3IWF + Note over UE, NG-RAN: 8. Obtain locations via N3GPP access + + rect rgb(240, 240, 240) + Note over AMF, LMF: (A) + AMF->>LMF: 9a. Namf_Communication_N1N2MessageTransfer +(Positioning Message) + LMF->>V-GMLC: 10a. Nlmf_ProvideLocation_Response + end + + rect rgb(240, 240, 240) + Note over AMF, V-GMLC: (B) + AMF->>V-GMLC: 9b. Namf_Location_ProvideLocation_Response + end + + V-GMLC->>H-GMLC: 11. LCS Service Response + H-GMLC->>LCS Client: 12. LCS Service Response + +``` + +Sequence diagram for Access Type selection for LCS service showing interactions between UE, NG-RAN, AMF, LMF, V-GMLC, UDM, H-GMLC, and LCS Client. + +**Figure 6.18.3-1: Access Type selection for LCS service** + +1. An external LCS client sends a location request to an HGMLC in the HPLMN for the target UE. The HGMLC verifies the authorization of the LCS Client to locate the target UE and UE privacy requirements. +2. The HGMLC invokes the Nudm\_UE ContextManagement\_Get service operation towards the home UDM of the target UE with the GPSI or SUPI of the UE. +3. The UDM returns the serving AMF address and possibly a VGMLC address and/or an LMF address in the VPLMN. The UDM also selects and returns Access Type to transmit the location information based on, e.g. Access Type, associated serving AMF and the UE state change (e.g. connectivity state changes) in the access. If the serving AMF for different Access Type is different, the UDM only returns the AMF address related to the selected Access Type and will not return the Access Type. +4. The HGMLC forwards the location request to the VGMLC and includes the AMF address, the target UE identity (e.g. SUPI), any LMF address received in step 3 and Access Type. + +- 5a. [Conditional] If solution in clause 6.2 (i.e. LMF Based Location Solution) is performed, the VGMLC invokes the Nlmf\_ProvideLocation Request service operation to forward the location request and Access Type to the LMF. + - 6a. [Conditional] If step 5a is performed, the LMF invokes the Namf\_Communication\_N1N2Message Transfer service operation to send the Positioning Message and Access Type to the AMF. + - 5b. [Conditional] If solution in clause 6.14 (i.e. Reuse R15 existing location service architecture for commercial use cases) is performed, the VGMLC invokes the Namf\_Location\_ProvideLocation\_Request service operation to forward the Access Type to the AMF. + 7. [Conditional] If the Access Type is 3GPP access, the step is performed. The step can be the steps 2-6 in clause 4.13.5.4 in TS 23.502 [5], steps 2-5 in clause 4.13.5.5 in TS 23.502 [5], steps 2-4 in clause 4.13.5.6 in TS 23.502 [5] or other new positioning procedures defined for 3GPP access. + 8. [Conditional] If the Access Type is N3GPP access, the step is performed. The step can be the steps 5-9 in clause 6.12.3.1 or other new positioning procedures defined for N3GPP access. + - 9a. [Conditional] If step 6a is performed, the AMF invokes the Namf\_Communication\_N1N2Message Transfer service operation to forward the Positioning Message to the LMF. + - 10a. [Conditional] If step 9a is performed, the LMF invokes the Nlmf\_ProvideLocation Response service operation to forward the location information to the VGMLC. + - 9b. [Conditional] If step 5b is performed, the VGMLC invokes the Namf\_Location\_ProvideLocation\_Response service operation to forward the location information to the VGMLC. +- 11-12. VGMLC returns the location estimate to the LCS client via HGMLC. + +### 6.18.4 Impacts on existing entities and interfaces + +Impacts are as follows: + +- UDM: decide the Access Type to transmit the location information (e.g. positioning message) and provide the Access Type to the GMLC. +- GMLC: send the Access Type received from UDM to AMF or LMF. +- LMF: send the Access Type received from GMLC to the AMF. +- AMF: triggers the procedure to obtain UE location in the specific access based on the Access Type received from GMLC or LMF. + +### 6.18.5 Evaluation + +**Editor's note:** This clause provides an evaluation of the solution. + +## 6.19 Solution #19: Distribution of Positioning Assistance Information + +### 6.19.1 Introduction + +This solution addresses the Key Issue 16. + +### 6.19.2 Functional Description + +The solution focuses on procedures for distributing positioning assistance data in the 5GS LCS system for Rel-15 architecture options involving the 5GC (Options 2, 4, 5 and 7 in TR 38.801 [16]). The 5GS LCS procedures outlined in TS 23.502 [5] are considered as the base. Furthermore, procedures for broadcasting encrypted assistance data are detailed. + +Maintenance, collection and distribution of positioning assistance data was done by E-SMLC in EPC. For 5GS LCS, this TR proposes LMF-centric allocation of LCS functions (Option B of Solution 1) and an LMF-based location solution (Solution 2). Hence, following the LMF-centric solution, the storing and updating of positioning assistance data is done by the LMF. + +The generic LCS Logical Architecture in clause 6.2 describes LCS Functional entities and their allocation to network elements. Within this framework a new LCS Functional entity, namely Positioning Assistance Data Source Function (PADSF) is introduced that is responsible for maintaining, updating and distributing up-to-date positioning assistance data within the 5GS LCS system. The PADSF is agnostic to the type of Access Network (AN) and hence may store, update and distribute assistance data for multiple ANs. The PADSF is implemented at the LMF and at the respective AN node NG-RAN as shown in Fig. 1. The justification for this split is as follows: Positioning assistance data, in general, can be RAT-dependent (ex. OTDoA assistance data) or RAT-independent (ex. GNSS assistance data). Further, it can be static or dynamic in nature, depending on whether it changes over time, over a target area or for specific UEs, etc. RAT-independent and RAT-dependent static assistance data will originate at the LMF, whereas RAT-dependent dynamic assistance data will originate in the respective RAT node. Hence the PADSF is distributed between the 5GC and AN. + +In terms of distributing the assistance data, existing LCS functions fulfil the role of maintaining and updating the positioning assistance data and there is no need to define a new function for this purpose: + +- Positioning Radio Control Function (PRCF). +- Positioning Radio Resource Management (PRRM). +- Location System Broadcast Function (LSBcF). + + + +Figure 6.19.2-1: Generic LCS Logical Architecture for 5GC (LMF-centric allocation). The diagram shows the logical architecture for 5GC. At the top, the LMF (Location Management Function) contains three functional entities: PRCF (Positioning Radio Control Function), PADSF (Positioning Assistance Data Source Function), and LSBcF (Location System Broadcast Function). The LMF is connected to the AM (Access Management Function) via the Nlmf interface. The AM is connected to the NG-RAN (Next Generation Radio Access Network) via the N2 interface. The NG-RAN contains three functional entities: PRRM (Positioning Radio Resource Management), LSBcF, and PADSF. The NG-RAN is connected to the UE (User Equipment) via the NR-Uu interface. The AM is also connected to the GML (GMLC) via the Ngmlc interface. The GMLC is connected to the AM via the Namf interface. + +**Figure 6.19.2-1: Generic LCS Logical Architecture for 5GC (LMF-centric allocation)** + +### 6.19.3 Procedures + +**Editor's note:** This clause describes high-level procedures and information flows for the solution. + +#### 6.19.3.1 UE Assisted and UE Based Positioning and Assistance Delivery Procedure + +The following procedure depicts a positioning service transaction that is used by the LMF to support UE based positioning, UE assisted positioning and delivery of assistance data for SA option 2. A single location request from the AMF may invoke one or more transactions, in which each transaction may perform a single positioning service (e.g. UE assisted positioning, UE capability retrieval). RAN positioning procedures related to LMF and UE communication should be specified as part of NR Positioning Protocol (NRPP). + + + +``` + +sequenceDiagram + participant LMF + participant AMF + participant NG-RAN + participant UE + + Note left of LMF: 1. Namf_Communication_N1N2MessageTransfer(DL Positioning Message) + LMF->>AMF: 1. Namf_Communication_N1N2MessageTransfer(DL Positioning Message) + Note right of AMF: 2. Network Triggered Service Request + AMF->>UE: 2. Network Triggered Service Request + Note left of AMF: 3. DL NAS TRANSPORT (DL Positioning Message) + AMF->>NG-RAN: 3. DL NAS TRANSPORT (DL Positioning Message) + Note right of NG-RAN: 4. DL NAS TRANSPORT (DL Positioning Message) + NG-RAN->>UE: 4. DL NAS TRANSPORT (DL Positioning Message) + Note right of UE: 5. Positioning Measurements and Computation + UE->>AMF: 6. UE Triggered Service Request + Note right of UE: 7. UL NAS TRANSPORT(UL Positioning Message) + UE->>NG-RAN: 7. UL NAS TRANSPORT(UL Positioning Message) + Note left of NG-RAN: 8. UL NAS TRANSPORT(UL Positioning Message) + NG-RAN->>AMF: 8. UL NAS TRANSPORT(UL Positioning Message) + Note left of AMF: 9. Namf_Communication_N1MessageNotify(UL Positioning Message) + AMF->>LMF: 9. Namf_Communication_N1MessageNotify(UL Positioning Message) + +``` + +Sequence diagram illustrating the UE Assisted and UE Based Positioning and Assistance Delivery Procedure. The diagram shows interactions between LMF, AMF, NG-RAN, and UE. The sequence starts with the LMF sending a Namf\_Communication\_N1N2MessageTransfer(DL Positioning Message) to the AMF. The AMF then initiates a Network Triggered Service Request to the UE. The AMF forwards the DL Positioning Message to the NG-RAN via DL NAS TRANSPORT. The NG-RAN forwards it to the UE via DL NAS TRANSPORT. The UE performs positioning measurements and computation. The UE then initiates a UE Triggered Service Request to the AMF. The UE sends the UL Positioning Message to the NG-RAN via UL NAS TRANSPORT. The NG-RAN forwards it to the AMF via UL NAS TRANSPORT. Finally, the AMF sends a Namf\_Communication\_N1MessageNotify(UL Positioning Message) to the LMF. + +**Figure 6.19.3-1: UE Assisted and UE Based Positioning and Assistance Delivery Procedure** + +1. The LMF invokes the Namf\_Communication\_N1N2MessageTransfer service operation towards the AMF to request the transfer of a Downlink (DL) Positioning message to the UE. The service operation includes the DL Positioning message. The Session ID parameter of the Namf\_Communication\_N1N2MessageTransfer service operation is set to the LCS Correlation identifier. The Downlink Positioning message provide assistance data to the UE. +2. If the UE is in CM IDLE state, the AMF initiates a network triggered Service Request procedure as defined in TS 23.502 [5] to establish a signalling connection with the UE. +3. The AMF forwards the Downlink Positioning message to the NG-RAN in a DL NAS TRANSPORT message. The AMF includes a Routing identifier, in the DL NAS TRANSPORT message, identifying the LMF. +4. The NG-RAN forwards the downlink positioning information and Routing identifier to the UE by DL NAS TRANSPORT message. +5. The UE stores any assistance data provided in the Downlink Positioning message and performs any positioning measurements and location computation requested by the Downlink Positioning message. +6. the UE has entered CM-IDLE state during step 4, the UE instigates the UE triggered Service Request as defined in TS 23.502 [5] in order to establish a signalling connection with the AMF. +7. The UE returns any location information obtained in step 5 to the NG-RAN in an Uplink Positioning message included in a NAS TRANSPORT message. The UE shall also include the Routing identifier in the UL NAS TRANSPORT message received in step 3. +8. The NG-RAN forwards the Uplink Positioning Information and Routing identifier to the AMF in a NAS TRANSPORT message. +9. The AMF invokes the Namf\_Communication\_N1MessageNotify service operation towards the LMF indicated by the routing identifier received in step 7. The service operation includes the Uplink Positioning message received in step 7 and the LCS Correlation identifier. Steps 1 to 9 may be repeated to send new assistance data. + +#### 6.19.3.2 Obtaining Non-UE Associated Network Assistance Data + +The following procedure is used by the LMF to support network assisted and network based positioning. This procedure is not associated with a UE location session. It is used to obtain network assistance data from a NG-RAN node (e.g. + +NG-RAN or ng-eNB). The procedure may be based on NRPPa protocol in TS 38.455 [11] between the LMF and NG-RAN. + + + +``` + +sequenceDiagram + participant LMF + participant AMF + participant NG-RAN + participant UE + Note right of NG-RAN: 3. Obtain Measurements + LMF->>AMF: 1. Namf_Communication_N1N2MessageTransfer (Network Positioning Message) + AMF->>NG-RAN: 2. N2 Transport (Network Positioning Message) + NG-RAN->>AMF: 4. N2 Transport (Network Positioning Message) + AMF->>LMF: 5. Namf_Communication_N2InfoNotify (Network Positioning Message) + +``` + +Sequence diagram illustrating the procedure for obtaining network assisted data. The diagram shows four lifelines: LMF, AMF, NG-RAN, and UE. The sequence of messages is: 1. LMF sends Namf\_Communication\_N1N2MessageTransfer (Network Positioning Message) to AMF; 2. AMF sends N2 Transport (Network Positioning Message) to NG-RAN; 3. NG-RAN performs 'Obtain Measurements'; 4. NG-RAN sends N2 Transport (Network Positioning Message) back to AMF; 5. AMF sends Namf\_Communication\_N2InfoNotify (Network Positioning Message) to LMF. + +**Figure 6.19.3-2: Obtaining Network Assisted Data** + +1. The LMF invokes the Namf\_Communication\_N1N2MessageTransfer service operation towards the AMF to request the transfer of a Network Positioning message to a NG-RAN in the NG-RAN. The service operation includes the Network Positioning message and the target NG-RAN node identity. The Network Positioning message may request positioning assistance information from the NG-RAN. +2. The AMF forwards the Network Positioning message to the target NG-RAN indicated in step 1 in an N2 Transport message. The AMF includes a Routing identifier, in the N2 Transport message, identifying the LMF. +3. The target NG-RAN obtains any positioning assistance information requested in step 2. +4. The target NG-RAN returns any positioning assistance information obtained in step 3 to the AMF in a Network Positioning message included in an N2 Transport message. The target NG-RAN shall also include the Routing identifier in the N2 Transport message received in step 2. +5. The AMF invokes the Namf\_Communication\_N2InfoNotify service operation towards the LMF indicated by the routing identifier received in step 4. The service operation includes the Network Positioning message received in step 4 and the UE identifier. Steps 1 to 5 may be repeated to request further positioning assistance information from the NG-RAN. + +#### 6.19.3.3 Broadcasting assistance data for UE assisted or UE based positioning + +The following procedure (Fig. 4) allows the LMF to broadcast positioning assistance data for UE assisted or UE based positioning. NRPPa will be used between the LMF and NG-RAN node. The NG-RAN node then broadcasts the positioning assistance data using a positioning SIB which needs updated RRC definitions for NR-specific assistance data (RAN scope). + + + +``` + +sequenceDiagram + participant LMF + participant AMF + participant NG-RAN + participant UE + Note left of LMF: 1. Namf_Communication_N1N2MessageTransfer (NetworkPositioning Message) + LMF->>AMF: 1. Namf_Communication_N1N2MessageTransfer (NetworkPositioning Message) + Note left of AMF: 2. N2 Transport (Network Positioning Message) + AMF->>NG-RAN: 2. N2 Transport (Network Positioning Message) + Note left of NG-RAN: 3. Broadcast Message (Network Positioning Message) + NG-RAN->>UE: 3. Broadcast Message (Network Positioning Message) + +``` + +Sequence diagram showing the procedure for broadcasting positioning assistance data. The diagram involves four entities: LMF, AMF, NG-RAN, and UE. Step 1: LMF sends a Namf\_Communication\_N1N2MessageTransfer (NetworkPositioning Message) to AMF. Step 2: AMF sends an N2 Transport (Network Positioning Message) to NG-RAN. Step 3: NG-RAN sends a Broadcast Message (Network Positioning Message) to UE. + +**Figure 6.19.3-3: Procedure for broadcasting positioning assistance data** + +1. The LMF invokes the Namf\_Communication\_N1N2MessageTransfer service operation towards the AMF to request the transfer of a Network Positioning message to a NG-RAN in the NG-RAN. The service operation includes the Network Positioning message and the target NG-RAN node identity. The Network Positioning message contains positioning assistance information for the UEs. +2. The AMF forwards the Network Positioning message to the target NG-RAN indicated in step 1 in an N2 Transport message. +3. The target NG-RAN broadcasts the positioning assistance information received in the Network Positioning message in step 2. + +### 6.19.4 Impacts on existing entities and interfaces + +*Editor's note: This clause describes impacts to existing entities and interfaces.* + +### 6.19.5 Evaluation + +*Editor's note: This clause provides an evaluation of the solution.* + +## 6.20 Solution 20: LMF selection in GMLC + +### 6.20.1 Introduction + +This solution applies to Key Issue 1 "Enhancement to LCS Architecture", Key Issue 3 "Support of low latency LCS" and Key Issue 5 "Slicing dependent location service". + +### 6.20.2 Functional Description + +Solution implies that the GMLC selects the LMF based on parameters such as positioning QoS, Client type, Serving cell id and S-NSSAI. + +### 6.20.3 Procedures + +#### 6.20.3.1 Procedure for LMF selection in GMLC with MO-LR and NI-LR + +Figure 6.20.3.1-1 shows a 5GC-MO-LR or 5GC-NI-LR procedure for GMLC based LMF selection solution where AMF request LMF selection from GMLC. + + + +``` +sequenceDiagram + participant UE + participant NG-RAN + participant AMF + participant V-GMLC + participant LMF + participant H-GMLC + + Note left of UE: 1a. Location Request + UE->>AMF: 1a. Location Request + Note right of AMF: 1b. NI-LR Request + AMF->>AMF: 1b. NI-LR Request + Note right of AMF: 2. Ngmlc_LmfSelection Request + AMF-->>V-GMLC: 2. Ngmlc_LmfSelection Request + Note right of V-GMLC: 3. Ngmlc_LmfSelection Response + V-GMLC-->>AMF: 3. Ngmlc_LmfSelection Response + Note right of AMF: 4. Positioning procedure + AMF->>H-GMLC: 4. Positioning procedure +``` + +Sequence diagram for LMF selection in GMLC with MO-LR and NI-LR. Lifelines: UE, NG-RAN, AMF, V-GMLC, LMF, H-GMLC. Steps: 1a. Location Request (UE to AMF), 1b. NI-LR Request (AMF to AMF), 2. Ngmlc\_LmfSelection Request (AMF to V-GMLC), 3. Ngmlc\_LmfSelection Response (V-GMLC to AMF), 4. Positioning procedure (AMF to H-GMLC). + +**Figure 6.20.3.1-1: Procedure for LMF selection in GMLC with MO-LR and NI-LR** + +- 1a. Either the UE with a LCS client requests some location service (e.g. positioning or delivery of assistance data) to the serving AMF at the NAS level. The LCS client may also request a specific LCS QoS; +- 1b. or the AMF initiate an NI-LR procedure. +2. To select an optimal LMF the AMF may select a V-GMLC based on NRF query or configuration in AMF and invoke the Ngmlc\_LmfSelection services operation towards the V-GMLC. The AMF includes the type of location service, QoS, UE identity, serving cell identity and S-NSSAI if available. +3. The V-GMLC, based on provided parameters, selects an LMF and provides LMF address to AMF in response. +4. The AMF continues positioning procedure using the selected LMF. If steps 2 and 3 did not occur or no LMF addresses was provided by the V-GMLC or the AMF is unable to use provided LMF addresses, the AMF selects an LMF based on NRF query or configuration in AMF. For a roaming scenario the procedure may include interaction between V-GMLC and H-GMLC. + +#### 6.20.3.2 Procedure for LMF selection in GMLC with 5GC-MT-LR + +Figure 6.20.3.2-1 shows a 5GC-MT-LR procedure for GMLC based LMF selection solution where GMLC selects LMF and informs AMF of selection. + + + +``` + +sequenceDiagram + participant External Client + participant H-GMLC + participant UDM + participant V-GMLC + participant AMF + participant LMF + participant NG-RAN + participant UE + + Note right of External Client: 1. LCS Service Request + External Client->>H-GMLC: 1. LCS Service Request + Note right of H-GMLC: 2. Nudm_UE ContextManagement_Get Request + H-GMLC->>UDM: 2. Nudm_UE ContextManagement_Get Request + Note right of UDM: 3. Nudm_UE ContextManagement_Get Response + UDM-->>H-GMLC: 3. Nudm_UE ContextManagement_Get Response + Note right of H-GMLC: 4. Ngmlc_ProvideLocation Request + H-GMLC->>V-GMLC: 4. Ngmlc_ProvideLocation Request + Note right of V-GMLC: 5. Namf_MT_EnableUEReachability Request + V-GMLC->>AMF: 5. Namf_MT_EnableUEReachability Request + Note right of AMF: 6. Network Triggered Service Request + AMF-->>V-GMLC: 6. Network Triggered Service Request + Note right of V-GMLC: 7. Namf_MT_EnableUEReachability_Response + V-GMLC-->>AMF: 7. Namf_MT_EnableUEReachability_Response + Note right of AMF: 8. Namf_EventExposure_Subscribe + AMF-->>V-GMLC: 8. Namf_EventExposure_Subscribe + Note right of V-GMLC: 9. Namf_EventExposure_Notify + V-GMLC-->>AMF: 9. Namf_EventExposure_Notify + Note right of V-GMLC: 10. LMF selection + V-GMLC-->>AMF: 10. LMF selection + Note right of AMF: 11. Namf_Location_ProvideLocation Request + AMF->>V-GMLC: 11. Namf_Location_ProvideLocation Request + Note right of AMF: 12. Network Triggered Service Request + AMF-->>V-GMLC: 12. Network Triggered Service Request + Note right of AMF: 13. Notificationprocedure + AMF->>AMF: 13. Notificationprocedure + Note right of AMF: 14. LMF selection + AMF-->>AMF: 14. LMF selection + Note right of AMF: 15. Nlmf_Location_DetermineLocation Request + AMF->>LMF: 15. Nlmf_Location_DetermineLocation Request + Note right of LMF: 16. UE Positioning + LMF-->>UE: 16. UE Positioning + Note right of LMF: 17. Nlmf_Location_DetermineLocation Response + LMF-->>AMF: 17. Nlmf_Location_DetermineLocation Response + Note right of AMF: 18. Namf_Location_ProvideLocation Response + AMF-->>V-GMLC: 18. Namf_Location_ProvideLocation Response + Note right of V-GMLC: 19. Ngmlc_ProvideLocation Response + V-GMLC-->>H-GMLC: 19. Ngmlc_ProvideLocation Response + Note right of H-GMLC: 20. LCS Service Response + H-GMLC-->>External Client: 20. LCS Service Response + +``` + +Sequence diagram for 5GC-MT-LR with LMF selection in GMLC. Lifelines: UE, NG-RAN, AMF, LMF, UDM, V-GMLC, H-GMLC, External Client. The process involves an LCS Service Request from the External Client to the H-GMLC, followed by context management and location requests through the UDM, V-GMLC, and AMF. It includes optional steps for UE reachability and network-triggered service requests. The AMF then performs LMF selection and sends a location determination request to the LMF, which returns a response through the AMF and V-GMLC back to the External Client. UE positioning occurs between the UE and the LMF. + +**Figure 6.20.3.2-1: 5GC-MT-LR with LMF selection in GMLC** + +1. The external location services client sends a request to the GMLC for a location for the target UE identified by an GPSI or an SUPI. The request may include the required QoS, Supported GAD shapes and client type. +2. The GMLC invokes a Nudm\_UE ContextManagement\_Get service operation towards the home UDM of the target UE to be located with the GPSI or SUPI of this UE. +3. The UDM returns the network addresses of the current serving AMF, UE subscription profile for LCS and may return the privacy setting for the subsequent LCS requests of the UE. +4. The H-GMLC invokes the Ngmlc\_ProvideLocation service towards the V-GMLC. +5. This step and steps 6 to 9 are only performed if the V-GMLC needs to know the serving cell for the UE prior to selecting LMF. The LMF invokes the Namf\_MT\_EnableUEReachability Request service operation towards the serving AMF to verify UE reachability. +6. If the UE is currently idle but reachable, the AMF performs a network triggered service request in order to place the UE in connected state. + +7. The AMF returns the result of the UE reachability operation. +8. The V-GMLC invokes the Namf\_EventExposure\_Subscribe service operation towards the AMF to obtain UE location information and includes the immediate one time notification flag. +9. The serving AMF returns UE location information to the LMF (e.g. serving cell ID). +10. The V-GMLC may define a list, in order of priority, of one or more selected LMFs to be used by the AMF. The list is based on e.g. the requested QoS, the type of External Client and information from NRF service. The list may also for each selected LMF include a condition on a certain S-NSSAI being used by the UE for the LMF to be applicable to be used. +11. The V-GMLC invokes the Namf\_Location\_ProvideLocation service operation towards the AMF to request the current location of the UE. The service operation includes the SUPI, and client type and may include the required QoS and Supported GAD shapes and the prioritized list of selected LMF addresses each with an optional S-NSSAI condition defined in step 4. +12. If the UE is in CM IDLE state, the AMF initiates a network triggered Service Request procedure to establish a signalling connection with the UE. +13. If the indicator of privacy check related action indicates that the UE must either be notified or notified with privacy verification, a notification procedure is performed. +14. The AMF selects the LMF with highest priority and fulfilling S-NSSAI criteria from the list provided in step 4. If no LMF addresses was provided by the GMLC or the AMF is unable to use any provided LMF address, the AMF selects an LMF based on NRF query or configuration in AMF. +15. The AMF invokes the Nlmf\_Location\_DetermineLocation service operation towards the LMF to request the current location of the UE. The service operation includes a LCS Correlation identifier, the serving cell identity and the client type and may include the required QoS and Supported GAD shapes. +16. The LMF performs one or more of the positioning procedures. +17. The LMF returns the Nlmf\_Location\_DetermineLocation Response towards the AMF to return the current location of the UE. The service operation includes the LCS Correlation identifier, the location estimate, its age and accuracy and may include information about the positioning method. +18. The AMF returns the Namf\_Location\_ProvideLocation Response towards the V-GMLC to return the current location of the UE. The service operation includes the location estimate, its age and accuracy and may include information about the positioning method. +19. The V-MLC returns location estimate or error indication to the H-GMLC. +20. The H-GMLC sends the location service response to the external location services client. + +### 6.20.4 Impacts on existing entities and interfaces + +#### GMLC: + +- Need to select LMF based e.g. on requested QoS, UE identity, Client type, serving cell id and S-NSSAI. + +#### AMF: + +- Need to request LMF selection from GMLC for MO-LR and NI-LR requests. +- Need handle LMF selection based on S-NSSAI for MT-LR requests. + +#### Ngmlc: + +- Need to support a new service "Ngmlc\_LmfSelection". + +### 6.20.5 Evaluation + +**Editor's note:** This clause provides an evaluation of the solution. + +## 6.21 Solution 21: Solution for Low Power Periodic and Triggered Location + +### 6.21.1 Introduction + +This solution is based on solution 2, and thus share the same architecture and base procedures as documented in clause 6.2. + +The only difference with solution 2 is the enhancement of Low Power Periodic and Triggered 5GC-MT-LR Procedure by using the EDT and RAI mechanism as in solution 1 of TR 23.724 [20]. Other procedures of solution 2 as in clause 6.2 are reused. + +**Editor's note:** This solution has dependency on the conclusion of TR 23.724 [20] and RAN developments for EDT support. + +### 6.21.2 Functional Description + +This solution has the same architecture and reference points definition as that of solution 2, i.e. clauses 6.2.2.1 and 6.2.2.2. + +### 6.21.3 Procedures + +#### 6.21.3.1 General + +All the procedures in solution 2, except the Low Power Periodic and Triggered 5GC-MT-LR Procedure in clause 6.2.3.5, apply to this solution. The enhanced Low Power Periodic and Triggered 5GC-MT-LR Procedure is described below. + +#### 6.21.3.2 Low Power Periodic and Triggered 5GC-MT-LR Procedure + +Figure 6.21.3.2-1 summarizes a low power variant of the optimized 5GC-MT-LR procedure in clause 6.2.3.4 for a roaming UE to support periodic and triggered location. A corresponding procedure for a non-roaming UE would comprise a subset of the procedure shown in Figure 6.2.3.5-1. This procedure has the same characteristics as the procedure in Figure 6.2.3.4-1, but in addition: + +- The UE is enabled to report the occurrence of trigger events and provide associated location information using EDT and RAI as proposed for Solution 1 in TR 23.724 [20]. +- The UE is enabled to request immediate release of the signalling connection by the RAN following the sending of an event report using EDT as proposed for Solution 1 in TR 23.724 [20], which can minimize the duration of the signalling connection. +- The UE is enabled to indicate an expectation of receiving a single response from the LMF after which the signalling connection is released by the AMF, which can reduce the duration of the signalling connection. +- The option of employing trigger detection in the LMF is not used. + + + +``` + +sequenceDiagram + participant UE + participant RAN + participant AMF + participant LMF + participant VGMLC + participant UDM + participant HGMLC + participant LCS Client + + Note over all: 1-18. Steps 1-18 of Figure 6.X.3.3-1 + Note left of UE: 25. Event Detected + Note left of UE: 26. Determine Reporting Mode + UE->>LMF: 19. Request Periodic-Triggered Positioning + LMF-->>UE: 20. Confirm Periodic-Triggered Positioning + LMF->>VGMLC: 21. Nlmf_EventNotify + VGMLC-->>HGMLC: 22. LCS Service Response + LMF-->>HGMLC: 23. Nlmf_EventNotify + HGMLC-->>LCS Client: 24. LCS Service Response + Note over RAN, AMF, LMF: 27. Reporting using a NAS Signalling Connection + Note left of RAN: 28. Setup Signalling Connection + Note right of LMF: Reporting using EDT + RAN->>UE: 29. RRC EDT Request (NAS Transport (UL positioning message), RAI) + UE-->>RAN: 30. RRC EDT Complete + RAN->>AMF: 31. Initial UE Message (NAS Transport (UL positioning message), RAI) + AMF->>LMF: 32. Namf_Communication_N2InfoNotify (UL positioning message, RAI) + Note left of LMF: 33. Determine Location + LMF-->>AMF: 34. Namf_Communication_N1N2MessageTransfer (DL positioning message) + AMF-->>RAN: 35. N2 Transport (NAS Transport (DL positioning message)) + AMF->>UE: 36. UE Context Release Command + RAN-->>UE: 37. RRC EDT Complete (DL positioning message) + LMF->>VGMLC: 38. Nlmf_EventNotify + VGMLC-->>HGMLC: 39. LCS Service Response + LMF-->>HGMLC: 40. Nlmf_EventNotify + HGMLC-->>LCS Client: 41. LCS Service Response + Note left of UE: 42. Event Detected + +``` + +Sequence diagram for Low Power Periodic and Triggered 5GC-MT-LR for a roaming UE. Lifelines: UE, RAN, AMF, LMF, VGMLC, UDM, HGMLC, LCS Client. The diagram shows steps 19 through 42, with a dashed box indicating 'Reporting using EDT' from step 28 to 37. + +**Figure 6.21.3.2-1: Low Power Periodic and Triggered 5GC-MT-LR for a roaming UE** + +1-18. Steps 1 to 18 of Figure 6.2.3.3-1 are performed. + +19. Step 20 of Figure 6.2.3.4-1 is performed. In addition, the LMF includes in the request for periodic or triggered location reporting an indication that the UE is permitted to send event reports using EDT. The LMF may also include criteria indicating when EDT may be used by the UE and which values of RAI the UE is permitted to include for EDT (e.g. RAI for immediate release and/or RAI for early release). + +NOTE 1: The LMF may determine UE support for EDT for event reporting, including values of RAI supported by the UE, by obtaining the positioning (e.g. LPP) capabilities of the UE prior to step 19. + +NOTE 2: Use of the permitted values of RAI may also be negotiated at the NAS level during registration of a UE as proposed for Solution 1 in TR 23.724 [20]. A UE may then only use EDT and particular RAI values if both agreed during registration and allowed by the LMF. + +20. If the request in step 19 can be supported, the UE returns an acknowledgment to the LMF in a positioning protocol (e.g. LPP) message, which is transferred via the serving AMF and delivered to the LMF using an Namf\_Communication\_N1MessageNotify service operation. + +- 21-24. Steps 21-24 of Figure 6.2.3.3-1 are performed to confirm that event reporting for periodic or triggered location was activated in the UE and to return any location estimate for the UE available event obtained at step 18 if the UE available event was requested at step 5 or step 6. +25. The UE monitors for occurrence of the trigger event requested in step 19. The monitoring may occur while the UE is in idle state and/or while the UE is not reachable from the network (e.g. with eDRX or PSM). The UE may also (e.g. periodically) request assistance data from the LMF to help determine a location, if needed to detect a trigger event. When a trigger event is detected, the UE proceeds to step 26. +26. The UE determines (e.g. based on any criteria received in step 19) whether to report the trigger event using a NAS signalling connection or EDT. If the UE is already in connected state or can only access a RAN node which does not support EDT, the UE determines to use a NAS signalling connection. +27. If the UE determines to use a NAS signalling connection at step 26, the UE performs steps 29-31 of Figure 6.2.3.4-1. The UE then skips steps 28-37. +28. If the UE determines to use EDT at step 26, the UE obtains any location measurements or location estimate requested in step 19, determines a suitable serving cell if accessing NG-RAN and requests and obtains an RRC signalling connection with a RAN node. +29. The UE sends an RRC EDT Request message to the RAN node. The RRC EDT Request message includes the 5G-GUTI and a NAS Transport message containing an UL positioning protocol (e.g. LPP) message which includes any location measurements or location estimate obtained in step 28 and may identify the type of event being reported. The NAS Transport message also includes the routing identifier received by the UE at step 19. The NAS Transport message is ciphered and integrity protected as defined in TS 24.501 [21]. The RRC EDT Request further includes an RAI as proposed for Solution 1 in TR 23.724 [20]. The RAI may indicate either immediate release or early release of the RRC signalling connection. For early release, the RAI may also indicate whether the UE expects to receive one DL positioning protocol message from the LMF in response. +30. If the RAI received in step 29 indicates immediate release, the RAN node sends an RRC EDT Complete message to the UE to immediately release the RRC signaling connection. + +**Editor's note:** Details of EDT support for NG-RAN (e.g. including new RRC messages) are still to be decided by RAN. The description here is based on current EDT support for Control Plane CIoT EPS optimization in TS 36.300 [22] and TS 23.401 [23] and proposed use of EDT and RAI for small data transfer for Solution 1 in clause 6.1 of TR 23.724 [20]. + +31. The RAN node sends an N2 Initial UE message to the serving AMF for the UE (identified by the 5G-GUTI). The Initial UE message includes the NAS Transport message received at step 29 and the RAI. +32. The AMF performs integrity protection verification and deciphering of the NAS Transport message as defined in TS 24.501 [21]. The AMF invokes the Namf\_Communication\_N2InfoNotify service operation towards the LMF indicated by the routing identifier received in the NAS Transport message in step 31. The service operation includes the UL positioning protocol message and the RAI received at step 31. If the RAI received at step 31 indicates either immediate release or early release where no LMF response is expected by the UE, the AMF omits support for steps 34-35, since the AMF does not expect to receive a response at step 34. +33. If inclusion of a location estimate in event reports was requested at step 5 or step 6, the LMF uses any location measurements or location estimate included in the UL positioning protocol message received at step 32 to determine a location estimate for the UE. +34. If the RAI received at step 31 indicates early release where the UE expects to receive a response from the LMF, the LMF invokes the Namf\_Communication\_N1N2MessageTransfer service operation towards the AMF to request the transfer of a DL positioning protocol message (e.g. an LPP message) to the UE. The service operation includes the DL positioning protocol message. + +**NOTE 3:** The DL positioning protocol message may be an acknowledgment of the UL positioning protocol message. + +35. If the AMF receives a DL positioning protocol message for the UE from the LMF at step 34, the AMF forwards the DL positioning protocol message to the RAN in a NAS Transport message. +36. Unless the AMF receives an RAI indicating immediate release at step 31, the AMF sends a UE Context Release Command to the RAN to release the RRC signalling connection to the UE. Step 36 is performed after step 35 when an RAI is received at step 31 indicating that a response is expected by the UE from the LMF. Step 36 is + +instead performed either after a timeout if step 35 does not occur or after step 32 when an RAI is received by the AMF indicating no response is expected by the UE from the LMF. + +NOTE 4: The AMF may also send any pending MT small data or pending MT SMS messages to the UE following step 31 and prior to step 36 as described for some of the small data solutions in TR 23.724 [20]. + +37. Unless the RAN previously performed step 30 for immediate release of the UE, the RAN sends an RRC EDT Complete message to the UE to release the RRC signalling connection to the UE and includes any NAS Transport message received at step 35 if step 35 occurs. + +38-41. Steps 30-33 of Figure 6.2.3.3-1 are performed to return an indication of the trigger event to the external client and a location estimate if this was requested. + +42. The UE continues to monitor for and detect further trigger events as in step 25 and instigates steps 26-41 each time a trigger event is detected. + +### 6.21.4 Impacts on existing entities and interfaces + +The solution adds the following new impacts in addition to those described in clause 6.2.4 when used to enhance Solution 2 in clause 6.2. + +#### 6.21.4.1 Impacts to LMF and Nlmf SBI + +**Table 6.21.4.1-1: LMF Impacts** + +| Procedure | Description | Corresponding or Similar Rel-15 Impact (if any) | +|--------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------| +| Periodic / Triggered 5GC-MT-LR (low power) | Provide criteria to a UE defining when event reporting using EDT may be used | None | +| | Receive an UL positioning message for an event report from a UE sent using EDT, and send a single response when the UE indicates a response is expected. | None | + +#### 6.21.4.2 Impacts to UE + +**Table 6.21.4.2-1: UE Impacts** + +| Procedure | Description | Corresponding or Similar Rel-15 Impact (if any) | +|--------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------| +| Periodic / Triggered 5GC-MT-LR (low power) | Receive criteria from an LMF for use of EDT for event reporting for periodic or triggered location. | None | +| | Depending on the received criteria, send event reports using EDT and include an RAI indicating immediate release or early release. | None | + +#### 6.21.4.3 Impacts to AMF and Namf SBI + +The solution relies on service based operations to be defined later for support of EDT by an AMF. + +#### 6.21.4.4 Impacts to the NG-RAN + +An NG-RAN node needs to support EDT. The support of EDT can be common to support of EDT for CIoT small data transfer as proposed in clause 6.1 of TR 23.724 [20] and is not specific to location services. + +## 6.22 Solution 22: LCS continuity Support for N26 based Handover + +### 6.22.1 Introduction + +This solution addresses one scenario of Key Issue 15: Location continuity support, that is: + +- Mobility between EPS and 5GC, when UE uses 3GPP access and/or non-3GPP access. + +This solution address for inter-system mobility cases, and it can work together with other intra-system mobility solutions. + +### 6.22.2 Functional Description + +The interworking between 5GS and EPS with N26 interface is specified in clause 5.17.2.2 of TS 23.501 [4], and the handover procedure via is specified in clause 4.11.1.2 of TS 23.502 [5]. During that handover procedure, location request from LCS Client may arrive at 5GC or EPS core network entities, e.g. AMF or MME. Or after core network entities received Location Request from GMLC and before actual positioning procedure finish, the handover required message maybe received from RAN. + +Since those handover procedure is on-going, continue performing positioning procedure within the source RAN may have problems, e.g. such positioning procedure may not able be finished due to UE moved to target side; the positioning result from the source side may not be accurate due to UE mobility. In such handover and location service simultaneously on-going scenarios, forwarding arrived location request to target side and trigger actual positioning procedure at target side has benefits over simply reject the location request. The benefits including that network can provide UE location timely and accurately. + +### 6.22.3 Procedures + +#### 6.22.3.1 LCS support during Handover from 5GS to EPS + +Within below figure 6.22.3.1-1, the MT-LR location request arrives at AMF (e.g. Step 4 of clause 4.13.5.3 of TS 23.502 [5], Namf\_Location\_Provide Request from V-GMLC), and this would trigger the positioning procedure. When such MT-LR procedure is still on-going, the NG-RAN may decides that a Handover is required. + + + +``` + +sequenceDiagram + participant UE + participant E-UTRAN + participant NG RAN + participant AMF + participant LMF + participant MME + participant E-SMLC + participant V-GMLC + participant H-GMLC + participant LCS Client + + Note right of AMF: A-1 +Within procedure in 4.13.5.3 of TS23.502: +Step4. AMF received Namf_Location_Provide Request from V-GMLC + AMF->>LMF: + Note left of AMF: A-2 +UE base positioning Procedure in 4.13.5.4 of TS23.502: +Step1. AMF received +Namf_communication_N1N2MessageTransfer() + LMF->>AMF: + Note left of AMF: B +Within procedure in 4.11.1.2.1 of TS23.502: +Step 1. Handover Required + AMF->>E-UTRAN: + Note right of AMF: C-1 +Within procedure in 4.13.5.3 of TS23.502: +Step9. AMF return Namf_Location_Provide Reponse to V-GMLC + AMF->>V-GMLC: + Note right of AMF: C-2 +Within in 4.13.5.4 of TS23.502 +Step7. AMF response LMF with +Namf_communication_N1N2MessageNotify() + AMF->>LMF: + Note right of AMF: D Forwarding Location/Positioning Request +Within procedure in 4.11.1.2.1 of TS23.502: +Step 3. Relocation Required + AMF->>MME: + Note right of MME: E-1 +Within procedure in 9.1.15 of TS23.271: +Step 6. MME send Location +Request to E-SMLC + MME->>E-SMLC: + Note right of E-SMLC: F-1 +Within procedure in 9.1.15 of TS23.271: +Step 7. E-SMLC perform Positioning procedure + E-SMLC->>MME: + Note right of MME: G-1 +Within procedure in 9.1.15 of TS23.271: +Step 8. MME received Location +Reponse from E-SMLC + MME->>AMF: + Note right of AMF: H: Forwarding Location Result +Define New Message or Re-USE context +Req/Response procedure + AMF->>LMF: + Note right of AMF: J +Within procedure in 4.13.5.3 of TS23.502: +Step 9. AMF response Namf_Location_Provide Response to V-GMLC + AMF->>V-GMLC: + +``` + +Sequence diagram illustrating LCS support during handover from 5GS to EPS. The diagram shows interactions between UE, E-UTRAN, NG RAN, AMF, LMF, MME, E-SMLC, V-GMLC, H-GMLC, and LCS Client. Key steps include: A-1 (AMF receives Namf\_Location\_Provide Request from V-GMLC), A-2 (AMF receives Namf\_communication\_N1N2MessageTransfer() from LMF), B (Handover Required), C-1 (AMF return Namf\_Location\_Provide Reponse to V-GMLC), C-2 (AMF response LMF with Namf\_communication\_N1N2MessageNotify()), D (Forwarding Location/Positioning Request), E-1 (MME send Location Request to E-SMLC), F-1 (E-SMLC perform Positioning procedure), G-1 (MME received Location Reponse from E-SMLC), H (Forwarding Location Result), and J (AMF response Namf\_Location\_Provide Response to V-GMLC). + +**Figure 6.22.3.1-1: LCS support during handover from 5GS to EPS** + +Step A-1: During the 5GC-MT-LR procedure, e.g. in clause 4.13.5.3 of TS 23.502 [5], step 4, the AMF received Namf\_Location\_ProvideLocation request from V-GMLC, which includes the SUPI, and client type and may include the required QoS parameters. The LMF is then contacted to perform one or more of the positioning procedures described in clause 4.13.5.4 and 4.13.5.5 of TS 23.502 [5]. + +Step A-2. Take the clause 4.13.5.4 of TS 23.502 [5] as an example, the step 1 of this procedure is triggered. The LMF invokes the Namf\_Communication\_N1N2MessageTransfer service operation towards the AMF. + +Step B: Before the complete of procedure triggered in Step A-2, or before Step A-2 but after Step A-1, the NG-RAN may decide to initiate the Handover. The AMF receives the Handover Required from NG-RAN as defined in clause 4.11.1.2.1 of TS 23.502 [5], step 1. + +Step C-1: Replace the step 9 in 4.13.5.3 of TS 23.502 [5], the AMF returns the Namf\_Location\_ProvideLocation Response towards the V-GMLC, to indicate that there is a Handover. + +Step C-2: The AMF invokes the Namf\_Communication\_N1MessageNotify service operation towards the LMF, to indicate that there is a Handover, and the abort of positioning procedure. + +Step D: The AMF needs to indicate the MME to perform Location Procedure in EPS and return the result, via N26 interface. The AMF may map the Namf\_Location\_ProvideLocation request message received to the message Provide Subscriber Location message, and send this message to MME by piggybacking in the Relocation Required, which is step 3 of procedure in 4.11.1.2.1 of TS 23.502 [5]. The MME assumes such Provide Subscriber Location is come from a GMLC, and triggers the Step F-1. At the same time, the handover procedure continues, as defined in 4.11.1.2.1 of TS 23.502 [5]. + +Step E-1: The MME send Location request to E-SMLC, as defined in clause 9.1.15 of TS 23.271 [6]. + +Step F-1: The E-SMLC performs the step 7 of clause 9.1.15 of TS 23.271 [6]. + +Step G-1: The E-SMLC performs the step 8 of clause 9.1.15 of TS 23.271 [6]. In this step, the MME receives the Location Response message from E-SMLC. That means the positioning result is from the target side. + +Step H: The positioning result is return to AMF via N26 interface. The context request/response pair message could to re-use with some modification, or defines new messages for this purpose. + +Step J: Like the step 9 in 4.13.5.3 of TS 23.502 [5], the AMF returns the Namf\_Location\_ProvideLocation Response towards the V-GMLC, to return the UE location to V-GMLC. + +#### 6.22.3.2 LCS support during Handover from EPS to 5GS + +Within below figure 6.22.3.2-1, the MT-LR location request (e.g. Provide Subscriber Location Request sent by VGMLC in step 2 of clause 9.1.15 of TS 23.271 [6]) arrives at MME, and this would trigger the positioning procedure. When such MT-LR procedure is still on-going, the NG-RAN decides that a Handover is required. + + + +``` + +sequenceDiagram + participant UE + participant E-UTRAN + participant NG RAN + participant AMF + participant LMF + participant MME + participant E-SMLC + participant V-GMLC + participant H-GMLC + participant LCS Client + + Note right of AMF: A +Within procedure in 9.1.15 of TS23.271: +Step 2. MME received Provide Subscriber Location from V-GMLC + MME->>V-GMLC: Step 6. Location Request + Note left of MME: B +Within procedure in 4.11.1.2.2.2 of TS23.502: +Step 2. Handover Required + MME->>E-SMLC: C Step C-1. MME send Location Abort to E-SMLC + MME->>V-GMLC: Step C-2. MME send Subscriber Location Report to V-GMLC + Note right of AMF: D. Forwarding Location Request +Within procedure in 4.11.1.2.2.2 of TS23.502: +Step 3. Forward Relocation Request + AMF->>NG RAN: + Note right of AMF: E +Within 4.13.5.3 of TS23.502: +Step 6. AMF send +Nlmf_Location_DetermineLocation_Request + AMF->>LMF: + Note left of AMF: UE base positioning Procedure in 4.13.5.4 of TS23.502: +Step 1. AMF received +Namf_communication_N1N2MessageTransfer() + Note right of AMF: F-2 +Within 4.13.5.3 of TS23.502: +Step 8. LMF received +Nlmf_Location_DetermineLocation_Response + LMF->>AMF: + Note right of AMF: G: Forwarding Location Result +Define New Message or Re-USE context +Req/Response procedure + AMF->>NG RAN: + Note right of AMF: H +Within procedure in 9.1.15 of TS23.271: +Step 9a. MME send Subscriber Location Report to V-GMLC + MME->>V-GMLC: + +``` + +Sequence diagram illustrating LCS support during handover from EPS to 5GS. The diagram shows interactions between UE, E-UTRAN, NG RAN, AMF, LMF, MME, E-SMLC, V-GMLC, H-GMLC, and LCS Client. It is divided into several steps: A (MME received Provide Subscriber Location from V-GMLC), B (Handover Required), C (MME send Location Abort to E-SMLC and Subscriber Location Report to V-GMLC), D (Forwarding Location Request), E (AMF send Nlmf\_Location\_DetermineLocation\_Request), UE base positioning Procedure, F-2 (LMF received Nlmf\_Location\_DetermineLocation\_Response), G (Forwarding Location Result), and H (MME send Subscriber Location Report to V-GMLC). + +**Figure 6.22.3.2-1: LCS support during handover from EPS to 5GS** + +Step A: During the EPS-MT-LR procedure, e.g. procedure in 9.1.15 of TS 23.271 [6], step 2, GMLC sends a Provide Subscriber Location message to the MME. This message carries the type of location information requested (e.g. current location and optionally, velocity), the UE subscriber's IMSI, LCS QoS information (e.g. accuracy, response time) and an indication of whether the LCS client has the override capability. The procedure may continue and step 6 of 9.1.15 of TS 23.271 [6] happens. + +Step B: Before the complete of procedure triggered in Step A, the E-UTRAN may decide to initiate the Handover. The MME receives the Handover Required from NG-RAN as defined in clause 4.11.1.2.2.2 of TS 23.502 [5], step 2. + +Step C-1: In such case, since the Handover is going to happen, continuing positioning at EPS side become useless, so the MME may send Location Abort to E-SMLC. + +Step C-2: The MME may also send Subscriber Location Report to V-GMLC, to indicate that there is a Handover imminent. + +Step D: The MME needs to indicate the AMF to perform Location Procedure in 5GS and return the result, via N26 interface. The MME sends the Provide Subscriber Location message to AMF, by piggybacking it in the Forward Relocation Request message, which is step 3 of procedure in 4.11.1.2.2.2 of TS 23.502 [5]. + +After receiving this message, the AMF needs to map the Provide Subscriber Location message to Namf\_Location\_ProvideLocation request message, and the MME assumes such Namf\_Location\_ProvideLocation is from a V-GMLC, and triggers the Step E. At the same time, the handover procedure continues, as defined in 4.11.1.2.2 of TS 23.502 [5]. + +Step E: As step 6 in clause 4.13.5.3 of TS 23.502 [5], the AMF selects an LMF based on NRF query or configuration in AMF and invokes the Nlmf\_Location\_DetermineLocation service operation towards the LMF to request the current location of the UE. + +Step F-1: As step 7 in clause 4.13.5.3 of TS 23.502 [5], the LMF performs one or more of the positioning procedures described in clause 4.13.5.4, 4.13.5.5 of TS 23.502 [5]. This step F-1 shows that clause 4.13.5.4 as an example. + +Step F-2: As step 8 in clause 4.13.5.3 of TS 23.502 [5], the LMF returns the Nlmf\_Location\_DetermineLocation Response towards the AMF to return the current location of the UE. + +Step G: The positioning result is returned to MME via N26 interface. The context request/response pair message could be re-used with some modification, or defines new messages for this purpose. + +Step H: Like the step 9a in 9.1.15 of TS 23.271 [6], the MME sends a Subscriber Location Report to the V-GMLC. + +### 6.22.4 Impacts on existing entities and interfaces + +Impacted entities: + +- AMF: forward LCS related message to MME, and receive such message from MME, to trigger positioning procedure; to forward positioning result to MME; mapping the Provide Subscriber Location message to and from the Namf\_Location\_ProvideLocation request message. +- MME: forward LCS related message to AMF, and receive such message from AMF, to trigger positioning procedure; to forward positioning result to AMF. + +Impacted interfaces: + +- N26, forwarding LCS related messages between AMF and MME. + +### 6.22.5 Evaluation + +**Editor's note:** This clause provides an evaluation of the solution. + +## 6.23 Solution #23: Unified NEF Location Service Exposure + +### 6.23.1 Introduction + +The Unified NEF Location Service Exposure solution addresses the following key issue: + +- Key Issue 7: Location service exposure. + +The solution enables the NEF to provide a unified exposure of different location services offered by 5GS to a consumer NF or AF. These location services include the GMLC (and LMF) based location solution and the AMF Event Exposure service based location solution. This unified exposure will enable a PLMN operator to offer location services to NFs and AFs using either one of these solutions or both solutions without impacting the SBI or API used by an NF or AF to access the NEF. In addition, by supporting a single unified SBI and API at an NEF, an optimal choice of solutions can be supported by the NEF (e.g. dependent on location accuracy and response time requirements) without impacting an AF or NF. + +GMLC based solution means any of the solutions described in this TR in which a GMLC is used. The AMF based location solution is the solution that makes use of AMF event exposure service as specified in TS 23.502 [5] and described in clause 6.23.3.1, or the enhanced procedure described in clause 6.23.3.3. + +### 6.23.2 Functional Description + +The service based architectures for roaming and non-roaming UEs are shown below. + + + +Figure 6.23.2-1: Non-roaming reference architecture for unified NEF location exposure. This diagram shows a UE connected to an (R)AN, which is connected to an AMF via an N2 interface. The AMF is connected to a Service Based Interface (SBI) via the Namf service. On the SBI, the LMF connects via Nlmf, the UDM via Nudm, and the AF or NF via Nnef. The AMF also connects to the SBI via the Ngmlc service. The NEF connects to the SBI via the Nnef service and is connected to an External AF. The GMMLC connects to the SBI via the Ngmlc service. + +Figure 6.23.2-1: Non-roaming reference architecture for unified NEF location exposure + + + +Figure 6.23.2-2: Roaming reference architecture for unified NEF location exposure. This diagram is split into two domains by a vertical dashed line: VPLMN (left) and HPLMN (right). In the VPLMN, a UE is connected to an (R)AN, which is connected to an AMF via an N2 interface. The AMF connects to the SBI via the Namf service. The LMF connects to the SBI via the Nlmf service. The vGMLC connects to the SBI via the Ngmlc service. In the HPLMN, the UDM connects to the SBI via the Nudm service. The AF or NF connects to the SBI via the Nnef service. The hGMLC connects to the SBI via the Ngmlc service. The NEF connects to the SBI via the Nnef service and is connected to an External AF. The AMF in the VPLMN connects to the hGMLC in the HPLMN via the Ngmlc service. + +Figure 6.23.2-2: Roaming reference architecture for unified NEF location exposure + +### 6.23.3 Procedures + +#### 6.23.3.1 Unified Location Service Exposure Procedure + +Figure 6.23.3.1-1 shows a unified location service exposure procedure provided by an NEF in an HPLMN for a target UE to a consumer NF in the HPLMN or to a consumer AF outside the HPLMN. The target UE can be roaming or non-roaming. The NEF service operations and APIs referenced in Figure 6.23.3.1-1 can be new and could use different names to those shown below for Figure 6.23.3.1-1. + +Mobility aspect is handled with existing procedures as defined in TS 23.501 [4] and TS 23.502 [5]. + + + +``` + +sequenceDiagram + participant External AF + participant HPLMN + participant VPLMN as VPLMN (roaming) or HPLMN (non-roaming) + Note right of HPLMN: HPLMN components: UDM, HGMLC, NEF, NF/AF + Note right of VPLMN: VPLMN components: UE, (R)AN, AMF, LMF + + External AF->>NEF: 1a. NEF API: LCS Service Request + NEF->>NF/AF: 1b. Nnef_ProvideLocation Request + Note right of NEF: 2. Determine Location Service + Note right of HPLMN: GMLC Location Service + NEF->>HGMLC: 3. Ngmlc_ProvideLocation Request + Note right of VPLMN: 4. Obtain UE Location using a GMLC based location service + HGMLC->>NEF: 5. Ngmlc_ProvideLocation Response + HGMLC->>NEF: 6. Ngmlc_LocationEvent Notify + + Note right of HPLMN: AMF Location Service + NEF->>UDM: 7. Nudm_UEContextManagement_Get Request + UDM->>NEF: 8. Nudm_UEContextManagement_Get Response + NEF->>AMF: 9. Namf_EventExposure Subscribe Request + AMF->>NEF: 10. Namf_EventExposure Subscribe Response + Note right of VPLMN: 11. Network Triggered Service Request + Note right of VPLMN: 12. (Enhanced) NG-RAN Location Reporting procedure + AMF->>NEF: 13. Namf_EventExposure Notify + AMF->>NEF: 14. Namf_EventExposure Notify + + NEF->>External AF: 15a. NEF API: LCS Service Response + NEF->>NF/AF: 15b. Nnef_ProvideLocation Response + NEF->>External AF: 16a. NEF API: LCS Service Response + NEF->>NF/AF: 16b. Nnef_ProvideLocation Response + +``` + +Sequence diagram of Unified Location Service Exposure Procedure for a roaming or non-roaming UE. The diagram shows interactions between a UE, (R)AN, AMF, LMF, UDM, HGMLC, NEF, NF/AF, and External AF. It details two main paths for location determination: one via the HGMLC (steps 3-6) and another via the AMF (steps 7-14). + +**Figure 6.23.3.1-1: Unified Location Service Exposure Procedure for a roaming or non-roaming UE** + +1a. An external AF sends an LCS Service Request to an NEF in the HPLMN for a target UE using an NEF API and includes an identification of the UE (e.g. SUPI or GPSI) and details of the location request such as whether a current or last know location is requested, the location accuracy and response time, and LDR request information. + +1b. As an alternative to step 1a, a consumer NF in the HPLMN for a target UE invokes an Nnef\_ProvideLocation Request service operation towards an NEF in the HPLMN and includes a global identification of the UE (e.g. SUPI or GPSI) and details of the location request as in step 1a. + +2. Based on the service requirements in step 1a or step 1b (e.g. location accuracy, location response time and whether triggered or periodic location is requested) and/or on HPLMN support for GMLC versus AMF based location service, the NEF determines whether to map the location request in step 1a or step 1b to a GMLC based location service or to an AMF based location service. When a GMLC based location service is determined, steps 3-6 are performed and steps 7-14 are omitted. When an AMF based location service is determined, steps 7-14 are performed and steps 3-6 are omitted. NEF takes the potential load to the system, e.g. AMF/UDM load, or GMLC load, into consideration when deciding which location service to use, or whether to reject the request from NF or AF. + +3. When a GMLC based location service is determined in step 2, the NEF invokes an Ngmlc\_ProvideLocation Request service operation towards an HGMLC in the HPLMN. The service operation may include all of the information received from the AF or NF in step 1a or 1b. +4. The HGMLC may first verify UE privacy requirements. If these are satisfied, the HGMLC then obtains one or more locations for the target UE as requested in step 3. The details of how this is done depend on the location solution used by the HGMLC which can employ any of the solutions described in this TR in which a GMLC is used. +5. The HGMLC invokes an Ngmlc\_ProvideLocation Response service operation towards the NEF to confirm the request in step 3 or to return the UE location. Which of these is used depends on the location request in step 3. For example, when a one-time current or last known location was requested in step 3, the HGMLC would return the current or last known location in step 5. When step 3 carries a deferred, periodic or triggered location request, step 5 may just return a confirmation of the request. +6. Optionally, if a deferred, periodic or triggered location request was sent in step 3, the HGMLC may invoke one or more Ngmlc\_LocationEvent Notify service operations towards the NEF, each carrying a notification of some event and possibly a UE location. +7. When an AMF based location service is determined in step 2, if the NEF needs to verify the target UE privacy requirements (e.g. for a location request from a consumer AF in step 1a), the NEF invokes an Nudm\_UEContextManagement\_Get Request service operation towards the UDM for the target UE to request the UE privacy requirements and the serving AMF address. Example of the AMF based location solution is that of the AMF event exposure based operation as described below, or the enhanced procedure described in clause 6.23.3.3. +8. When step 7 was performed, the UDM invokes the Nudm\_UEContextManagement\_Get Response service operation towards the NEF to return the serving AMF address and UE privacy requirements. The NEF then verifies UE privacy. + +NOTE: The AMF based location service does not support a real time query to the UE to verify UE privacy requirement by the user. + +**Editor's note:** The assumption in the above note would need to be verified. For example, UE privacy verification by an AMF could be added but would be an extra impact. + +9. The NEF invokes an Namf\_EventExposure Subscribe service operation towards the serving AMF for the target UE and indicates whether a one-time UE location is requested or multiple UE locations for some triggering event and includes information on location accuracy (e.g. cell ID or TA granularity or higher accuracy). The NEF sends the Namf\_EventExposure Subscribe service operation directly to the serving AMF as shown in Figure 6.23.3.1-1 when the NEF knows the AMF address (e.g. if steps 7 and 8 are performed). Otherwise, the NEF sends the Namf\_EventExposure Subscribe service operation to the serving AMF via a UDM as described below for Figure 6.23.3.2-1. +10. The AMF acknowledges the request in step 9 either directly as shown in Figure 6.23.3.1-1 or via the UDM as shown in Figure 6.23.3.2-1. +11. If the UE is currently reachable and in CM-IDLE state and if location is requested in step 9 with a cell ID accuracy or higher, the AMF perform a network triggered service request as described in TS 23.502 [5] to place the UE in CM-CONNECTED state. +12. If the AMF already has the current UE serving cell ID (e.g. following step 11) and the request in step 9 is for a one-time UE location with cell ID (or lower) accuracy and the AMF is able to convert the current serving cell ID into a geodetic location estimate, the AMF obtains the location estimate and proceeds to step 13. Otherwise, the AMF may perform the NG-RAN location reporting procedure defined in clause 4.10 of TS 23.502 [5] to obtain the current or last known UE location from the NG-RAN with a granularity of a cell ID or tracking area. Alternatively (e.g. if higher location accuracy is requested in step 9), the AMF may perform the enhanced NG-RAN location reporting procedure described in Figure 6.23.3.3-1 to obtain a UE location with higher accuracy. For either procedure, the AMF may request additional location reports from the NG-RAN if requested in step 9 for certain trigger events such as a change of cell ID or TA for a UE or entry into or out of an area of interest. +13. The AMF invokes the Namf\_EventExposure Notify service operation towards the NEF to provide the current or last known UE location as obtained at step 12. This service operation is valid for both direct access to the AMF by the NEF and indirect access via the UDM. + +14. Optionally, if additional triggered UE locations are requested in step 9, the AMF may invoke one or more Namf\_EventExposure Notify service operation towards the NEF to provide additional UE locations when certain trigger events occur (e.g. such as a UE changing serving cell or a serving TA or entering or leaving an area of interest). + +15a, 15b. The NEF returns the first UE location received at step 5 or step 13 or a confirmation of the location request received at step 5 in the case of a GMLC location service to the consumer AF (step 15a) or consumer NF (step 15b). If LCS service request is LDR type, LDR reference ID will be included in response message, and H(V)-LMF may store the LDR request information at H(V)-UDR. + +16a, 16b. Optionally, if one or more additional location reports are received at step 6 or step 14, the NEF returns one or more additional locations to the consumer AF (step 16a) or consumer NF (step 16b). + +#### 6.23.3.2 Alternative procedure for NEF to use AMF event exposure service via the UDM + +Figure 6.23.3.2-1 shows the procedure used by the NEF to access the serving AMF for the UE when the NEF does not have the address of the serving AMF and when AMF location reporting is selected by the NEF. + + + +``` + +sequenceDiagram + box "VPLMN (roaming) or HPLMN (non-roaming)" + participant UE + participant RAN as (R)AN + participant AMF + end + box "HPLMN" + participant UDM + participant NEF + end + + NEF->>UDM: 1. Nudm_EventExposure Subscribe Request + UDM->>AMF: 2. Namf_EventExposure Subscribe Request + AMF-->>UDM: 3. Namf_EventExposure Subscribe Response + UDM-->>NEF: 4. Nudm_EventExposure Subscribe Response + + rect rgb(255, 255, 255) + Note over AMF, RAN: 5. Network Triggered Service Request + end + + rect rgb(255, 255, 255) + Note over AMF, RAN: 6. Obtain UE Location using NG-RAN +Location Reporting procedure + end + + AMF->>NEF: 7. Namf_EventExposure Notify + AMF-->>NEF: 8. Namf_EventExposure Notify + +``` + +Sequence diagram showing the procedure for NEF to access the serving AMF via the UDM. The diagram shows entities UE, (R)AN, and AMF grouped under 'VPLMN (roaming) or HPLMN (non-roaming)', and UDM and NEF grouped under 'HPLMN'. The sequence involves 8 numbered steps of message exchange and internal procedures. + +**Figure 6.23.3.2-1: NEF Access to the Serving AMF via the UDM** + +1. The NEF invokes an Nudm\_EventExposure Subscribe service operation towards the UDM for the target UE for location reporting and indicates whether a one-time UE location is requested or multiple UE locations for some triggering event and includes the UE identity (SUPI or GPSI), information on location accuracy (e.g. cell ID or TA granularity or a higher accuracy). A correlation ID is also included. +2. The UDM invokes an Namf\_EventExposure Subscribe service operation towards the serving AMF for the target UE for location reporting and includes the information received in the service operation for step 1 including the correlation ID and a URL for the NEF. +3. The AMF acknowledges the request in step 2. +4. The UDM acknowledges the request in step 1. +5. The AMF performs a Network Triggered Service Request if needed to place the UE in CM-CONNECTED state. +6. The AMF obtains the current or last known location of the UE as described for step 12 of Figure 6.23.3.1-1, +7. The AMF invokes the Namf\_EventExposure Notify service operation towards the NEF indicated by the URL received in step 2 and includes the current or last known UE location as obtained at step 6 and the correlation ID received at step 2. + +- Optionally if additional triggered UE locations are requested in step 2, the AMF may invoke one or more Namf\_EventExposure Notify service operations towards the NEF to provide additional UE locations as in step 14 for Figure 6.23.3.1-1. + +#### 6.23.3.3 Enhanced NG-RAN Location Reporting Procedure + +Figure 6.23.3.3-1 shows the procedure used by a serving AMF to obtain a location estimate for the target UE from the NG-RAN with higher location accuracy than that possible using cell ID based location. The procedure could also be used for non-3GPP access from a UE if an N3IWF and AN replace the NG-RAN in Figure 6.23.3.3-1. The procedure is intended to supplement the NG-RAN Location reporting procedures defined in clause 4.10 of TS 23.502 [5] using the same NGAP messages between the AMF and NG-RAN. + + + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant AMF + + AMF->>NG-RAN: 1. Location Reporting Control (Location QoS) + NG-RAN-->>UE: 2. Location Measurement Request + UE-->>NG-RAN: 3. Location Measurement Response + Note over NG-RAN: 4. Determine UE Location + NG-RAN->>AMF: 5. Location Report + Note over NG-RAN: 6. UE Trigger Event + NG-RAN-->>UE: 7. Location Measurement Request + UE-->>NG-RAN: 8. Location Measurement Response + Note over NG-RAN: 9. Determine UE Location + NG-RAN-->>AMF: 10. Location Report + NG-RAN-->>UE: 11. Cancel Location Reporting + +``` + +The sequence diagram illustrates the Enhanced NG-RAN Location Reporting Procedure. It involves three main entities: UE (User Equipment), NG-RAN (Next Generation Radio Access Network), and AMF (Access and Management Function). The procedure starts with the AMF sending a 'Location Reporting Control (Location QoS)' message to the NG-RAN. The NG-RAN then sends a 'Location Measurement Request' to the UE, which responds with a 'Location Measurement Response'. Based on this, the NG-RAN performs an internal step 'Determine UE Location' and sends a 'Location Report' to the AMF. A 'UE Trigger Event' is also indicated. The NG-RAN may then send another 'Location Measurement Request' to the UE, which responds with another 'Location Measurement Response'. The NG-RAN performs another internal step 'Determine UE Location' and sends another 'Location Report' to the AMF. Finally, the NG-RAN sends a 'Cancel Location Reporting' message to the UE. + +Sequence diagram of the Enhanced NG-RAN Location Reporting Procedure involving UE, NG-RAN, and AMF. + +**Figure 6.23.3.3-1: Enhanced NG-RAN Location Reporting Procedure** + +Precondition: The UE is initially in CM\_CONNECTED state. + +- The AMF sends a Location Reporting Control message to the NG-RAN containing the information identifying the UE, a Reporting Type, an optional Location Reporting Level (e.g. indicating an area of interest), a Location QoS and optionally a maximum duration or maximum number of reports for triggered location. The Reporting Type can indicate a one-time location or a series of triggered locations based on criteria such as a change of serving cell, a fixed periodic interval or entry into or exit from an area of interest. + +**Editor's note:** The supported triggering events may align with those defined in Release 15 or may include additional triggering events such as fixed periodic events or movement of the UE by more than some threshold distance. The triggering events can be defined to align with triggering events used for GMLC based location to enable a unified location service from an NEF. + +- Depending on the location QoS requested in step 1, the NG-RAN may send a Location Measurement Request to the UE to request location measurements from the UE (e.g. of signals transmitted by the NG-RAN). +- If step 2 occurs, the UE obtains and returns the requested location measurements. +- Using any location measurements provided at step 3, any recent location measurements previously received from the UE and/or location measurements for the UE obtained by the NG-RAN, the NG-RAN determines the UE location. + +**Editor's note:** Support of steps 2-4 depends on new procedures and possibly new measurements to be agreed and added by RAN. + +5. The NG-RAN returns the UE location to the AMF in a Location Report message. +6. If triggered UE locations were requested at step 1, the NG-RAN waits until a trigger event occurs and then proceeds to step 7. +- 7-10. The NG-RAN repeats steps 2-5. Steps 6-10 are then repeated until a maximum number of reports or maximum duration is attained or until step 11 occurs. +11. For triggered location reporting, the AMF may cancel the location reporting in the NG-RAN - e.g. if no maximum duration or maximum number of reports was included at step 1. + +### 6.23.4 Impacts on existing entities and interfaces + +#### NG-RAN Impacts: + +- Impacts to support more accurate UE location determination for the Enhanced NG-RAN Location Reporting Procedure. + +#### AMF Impacts: + +- Impacts to request more accurate UE location for the Enhanced NG-RAN Location Reporting Procedure. +- Impacts for any changes to the AMF Event Exposure service operation to support additional types of triggered and periodic location reporting and more accurate location reporting. + +#### UDM Impacts: + +- Impacts to support additional types of triggered and periodic location reporting and higher location accuracy for the AMF and UDM Event Exposure service operations. + +#### NEF Impacts: + +- Impacts to support a new SBI to NFs and new API to AFs to enable a unified request for a UE location including a request for triggered or periodic location. +- Impacts to support a GMLC Provide Location SBI to request UE location from a GMLC. +- Impacts to support enhanced AMF and UDM Event Exposure SBIs to enable a request for UE location reporting with higher accuracy and/or additional types of periodic and triggered location. +- Impacts to query a UDM for UE privacy requirements and a serving AMF address. +- Impacts to verify UE privacy requirements. + +### 6.23.5 Evaluation + +**Editor's note:** This clause provides an evaluation of the solution. + +## 6.24 Solution #24: GMLC based Positioning Access selection for LCS service + +### 6.24.1 Introduction + +This solution addresses the Key Issue 14: Positioning Access selection for LCS service. + +### 6.24.2 Functional Description + +When UE accesses 5GC via 3GPP access and non-3GPP access simultaneously, the serving AMF may be same or different in the following scenarios: + +- Scenario 1: When served by the same PLMN for 3GPP and non-3GPP accesses, the UE is served by the same AMF. + +- Scenario 2: When served by different PLMNs for 3GPP and non-3GPP accesses, the UE is served by two AMFs belonging to two different PLMNs. + +In order to support the scenarios above, when GMLC receives LCS Service Request from LCS Client, it decides Access Type to transmit the positioning message based on the information in Table 6.24.2-1. + +**Table 6.24.2-1: Information for access type selection** + +| Information | Description | +|------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Access Type | The information is provided by UDM. UDM obtains the information from AMF during Registration procedure. | +| For each Access Type: | | +| Serving AMF address | The information is provided by UDM. UDM obtains the information during the Registration procedure. | +| Connectivity state | The information may be provided by UDM, AMF or LMF.
- - UDM and LMF obtain the information by invoking Namf_EventExposure service.
- - AMF locally maintains the connectivity state of the UE.
(Note 1) | YES
(Note 1) | YES
(Note 1) | YES
(Note 1) | YES
(Note 1) | YES
(Note 1) | YES
(Note 1) | YES
(Note 1) | +| 13 | YES
(Note 1) | YES
(Note 1) | YES
(Note 1) | YES
(Note 1) | YES
(Note 1) | YES
(Note 1) | YES
(Note 1) | YES
(Note 1) | +| 14 | YES | YES | YES | YES | YES | YES | YES | YES | +| 15 | YES | YES | YES | YES | YES | YES | YES | YES | +| 16 | YES | YES | YES | YES | YES | YES | YES | YES | +| 17 | YES | YES | YES | YES | YES | YES | YES | YES | +| 18 | YES | YES | YES | YES | YES | YES | YES | YES | +| 19 | YES | YES | YES | YES | YES | YES | YES | YES | +| 20 | YES | YES | YES | YES | YES | YES | YES | YES | +| 21 | YES | YES | YES | YES | YES | YES | YES | YES | +| 22 | YES | YES | YES | YES | YES | YES | YES | YES | +| 23 | YES
(Note 2) | YES
(Note 2) | YES
(Note 2) | YES
(Note 2) | YES
(Note 2) | YES
(Note 2) | YES
(Note 2) | YES
(Note 2) | +| 24 | YES
(Note 1) | YES
(Note 1) | YES
(Note 1) | YES
(Note 1) | YES
(Note 1) | YES
(Note 1) | YES
(Note 1) | YES
(Note 1) | +| 25 | YES | YES | YES | YES | YES | YES | YES | YES | + +NOTE 1: The assessment applies when 3GPP EUTRAN access type is used. + +NOTE 2: The assessment applies when "GMLC Location Service" used. + +**Editor's note:** The assessment is preliminary and may be modified based on new findings and modified or new solutions. + +## A.2 Supported positioning methods in NR Rel-15 + +Table A.2-1 indicates if the solutions in this TR supports a specific positioning method in NR and any identified condition of restriction. A YES indicates that the positioning method is supported, a NO indicates that the positioning method is not supported. + +A common criterion for support of all the listed methods in a 3GPP access network is that the solution allows the procedures defined in in clauses 4.13.5.4, 4.13.5.5 and 4.13.5.6 of TS 23.502 [5] to be used. + +**Table A.2-1: Supported positioning methods in NR** + +| Solution | CID | E-CID
Note1 | A-GNSS | OTDOA
Note1 | Barometric
pressure | WLAN | Bluetooth | TBS | +|-----------------|-----------------|------------------------|-----------------|------------------------|--------------------------------|-----------------|------------------|-----------------| +| 1 | YES | YES | YES | YES | YES | YES | YES | YES | +| 2 | YES | YES | YES | YES | YES | YES | YES | YES | +| 3 | YES | YES | YES | YES | YES | YES | YES | YES | +| 4 | YES | YES | YES | YES | YES | YES | YES | YES | +| 5 | YES | YES | YES | YES | YES | YES | YES | YES | +| 6 | YES | YES | YES | YES | YES | YES | YES | YES | +| 7 | YES | YES | YES | YES | YES | YES | YES | YES | +| 8 | YES | YES | YES | YES | YES | YES | YES | YES | +| 9 | YES | YES | YES | YES | YES | YES | YES | YES | +| 10 | YES | YES | YES | YES | YES | YES | YES | YES | +| 11 | YES | YES | YES | YES | YES | YES | YES | YES | +| 12 | YES
(Note 2) | YES
(Note 2) | YES
(Note 2) | YES
(Note 2) | YES
(Note 2) | YES
(Note 2) | YES
(Note 2) | YES
(Note 2) | +| 13 | YES
(Note 2) | YES
(Note 2) | YES
(Note 2) | YES
(Note 2) | YES
(Note 2) | YES
(Note 2) | YES
(Note 2) | YES
(Note 2) | +| 14 | YES | YES | YES | YES | YES | YES | YES | YES | +| 15 | YES | YES | YES | YES | YES | YES | YES | YES | +| 16 | YES | YES | YES | YES | YES | YES | YES | YES | +| 17 | YES | YES | YES | YES | YES | YES | YES | YES | +| 18 | YES | YES | YES | YES | YES | YES | YES | YES | +| 19 | YES | YES | YES | YES | YES | YES | YES | YES | +| 20 | YES | YES | YES | YES | YES | YES | YES | YES | +| 21 | YES | YES | YES | YES | YES | YES | YES | YES | +| 22 | YES | YES | YES | YES | YES | YES | YES | YES | +| 23 | YES
(Note 3) | YES
(Note 3) | YES
(Note 3) | YES
(Note 3) | YES
(Note 3) | YES
(Note 3) | YES
Note 3 | YES
Note 3 | +| 24 | YES
Note 2 | YES
Note 2 | YES
Note 2 | YES
Note 2 | YES
Note 2 | YES
Note 2 | YES
Note 2 | YES
Note 2 | +| 25 | YES | YES | YES | YES | YES | YES | YES | YES | + +NOTE 1: In Rel-15 only E-CID and OTDOA based on LTE signals is supported. + +NOTE 2: The assessment applies when 3GPP NR access type is used. + +NOTE 3: The assessment applies when "GMLC Location Service" is used. + +**Editor's note:** The assessment is preliminary and may be modified based on new findings and modified or new solutions. + +# Annex B: Evaluation tables for Key Issues + +## B.1 Evaluation table for of Solutions for Key Issue #4 + +Table B.1-1 shows the analysis of solutions for key issue#4. + +**Table B.1.-1: Analysis of solutions for Key Issue #4** + +| | Solution5 in clause 6.5 | Solution6 in clause 6.6 | Solution7 in clause 6.7 | Solution 14 in clause 6.14 | +|---------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------| +| Network function performs privacy verification for 5GC_MT_LR | GMLC | GMLC | GMLC | GMLC | +| How to transfer the privacy setting |
| 
| 
| N/A |
+| Where to store the privacy setting from the UE | UDM | PPR | PPR | UDM |
+| Which kind of message to carry privacy setting from the UE | "UE-LMF" message and NAS Location Notification Return Result | Registration message | "UE-LMF" message. | N/A |
+| Whether the network changes the privacy setting from the UE | -- | The PPR may change the privacy setting from the UE. If the PPR changes the UE Privacy Setting preference, the privacy verification procedure to the UE may still happen. This may lead to repetitive unsuccessful privacy verification procedure. | The PPR may change the privacy setting from the UE. If the PPR changes the UE Privacy Setting preference, the privacy verification procedure to the UE may still happen. This may lead to repetitive unsuccessful privacy verification procedure. | N/A |
+
+## --- B.2 Evaluation table for of Solutions for Key Issue #7
+
+Table B.2-1 shows the analysis of solutions for key issue#7.
+
+**Table 7.8.-1: Analysis of solutions for Key Issue #7**
+
+| | Solution 9 | Solution 10 | Solution 14 | Solution 23 | Solution 11 |
+|--------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------|----------------------------------------------------------------------------------------------|
+| Which NF that NEF forwards the received LCS request from external | GMLC | LMF | GMLC | a) HGMLC orb) AMF | Does not apply | +| How such NF is selected? | using the NRF service to find first GMLC, and in roaming case, HGMCL finds VGMLC by contacting UDM; | Query UDM for serving LMF, if non, use NRF service to get one; | Not Known, Le interface is used between NEF and GMLC; | a) Not mentioned?
b) Query UDM to get serving AMF | Does not apply | +| Inter faces aspects of NEF | North bound: Not mentioned; | NEF need support the corresponding service interface | an SBI to NEF for external client (?) | SBI interface to NF, and new APIs to AFs | Does not apply | +| Internal exposure to NF within 5G-CN | NF send request to GMLC; GMLC provide service based interface for location request | Solution itself does not differentiate external and internal exposure | ? not clear ?
an SBI interface (to the NEF for external client or directly to a GMLC in case of authorized clients); | via NEF, then NEF forward LCS request to GMLC; | Does not apply | +| Internal exposure to NG-RAN | Not mentioned | Not mentioned | Not mentioned | Not mentioned | For target UE in connect mode, the NG-RAN send Location request to AMF via N2 | +| Location Request type supported | Deferred Location supported, related serving NF activate and de-act the trigger, detect the event of the trigger. Serving NF not specified in CN, UE could be one. | Includes LDR and LIR; Request, update, and cancel LDR request procedure defined.
LMF will handle such location request. | Rel-15 defined procedure supported.
How to support "Deferred Location request" not clearly specified. | Including a request for triggered or periodic location. | 5GC NI LR used; | +| Privacy checking | GMLC perform | serving LMF performs | HGMLC interacts with UDM to perform | a) HGMLC interact with UDM
b) NEF interact with UDM | As NG-RAN is an internal LCS client, it is deemed that privacy verification is not required. | +| Other aspects | Target UE located in EPC considered. | UE provides the expected location privacy provisioning to the network(LMF) proposed. | LMF selection criterias defined | Enhanced NG-RAN Location Reporting Procedure proposed | Only UE in connect mode, such solution works. | +| Other key issues addressed | Key Issue 3: "Support of low latency LCS" | Key issue 4 "Reduce overhead for repetitive non-successful privacy verification". | Key Issue 1 (Enhancement to LCS Architecture) | | Key Issue 1 "Enhancements to LCS architecture" | +| Impacted NFs | NEF,GMLC,UDM | NEF,UDM,LMF | AMF,LMF,GMLC,UDM,CHF | AMF,UDM,NEF,NG-RAN | NG-RAN,AMF,UDM, | + +## B.3 Evaluation table for Key Issue #3 + +Table B.3.1: Evaluation on the solution of location management functionality support in NG-RAN + +| Solution | Impact to NRF and service framework | Impact to LMF | Impact to AMF | Impact to NG-RAN node | Impact to interfaces and service operations | +|----------|----------------------------------------------------------|--------------------------------------------------|---------------------------------------------------------------------------------------------------|----------------------------|---------------------------------------------| +| 15 | No | Yes, LMF enhanced for LMC performance management | Yes, LMC registration to AMF and AMF enhanced for LMC performance management | LMC supported | N2
New Namf_LMC service | +| 23 | No | No | Yes (minor). | LM functionality supported | N2 | +| 26 | Yes, AMF on behalf of LLMF, provides registration to NRF | No | Yes, AMF provides the LLMF registration info to NRF using NRF service operations | LLMF as one RAN capability | N2 | +| 28 | No | No | Yes (minor). NG RAN node LM capability preconfigured locally or received during N2 configuration. | LM functionality supported | N2 | + +# --- Annex C: Change history + +| Change history | | | | | | | | | +|----------------|---------|-----------|----|-----|-----|-------------------------------------------------------------------------------|--|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | | New version | +| 2018-12 | SP#82 | SP-181102 | - | - | - | 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/23737/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg b/marked/Rel-16/23_series/23737/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6f47bf14ab712d9e2104382b26053302f12520a3 --- /dev/null +++ b/marked/Rel-16/23_series/23737/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:942f1793e2684d2641ca609a63580d623b9c61bbd99467579d405ac684762e3d +size 52226 diff --git a/marked/Rel-16/23_series/23737/0b3d9fe35da3ee0c88f1420bb9ed7a03_img.jpg b/marked/Rel-16/23_series/23737/0b3d9fe35da3ee0c88f1420bb9ed7a03_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1835307629c1f1283f20a6abd42a1ca558b93b1e --- /dev/null +++ b/marked/Rel-16/23_series/23737/0b3d9fe35da3ee0c88f1420bb9ed7a03_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:23612c7868bb0f85e9194524a52fab8cf40e9065611ecbe6d2077c69cacde4ba +size 53476 diff --git a/marked/Rel-16/23_series/23737/0b87abe67b21a93777287649c33e755d_img.jpg b/marked/Rel-16/23_series/23737/0b87abe67b21a93777287649c33e755d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3f2c14a8c3a5ce8e125e752db6dd0913486e8b5f --- /dev/null +++ b/marked/Rel-16/23_series/23737/0b87abe67b21a93777287649c33e755d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:87cd540f8eb18e7f805a6c0537f4bc7a79bdd30a1ef9abefc2a0b78d5caa2555 +size 57422 diff --git a/marked/Rel-16/23_series/23737/0bf9346902e9a3bdabf05ceacc1947f5_img.jpg b/marked/Rel-16/23_series/23737/0bf9346902e9a3bdabf05ceacc1947f5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..125390189d4daf7a07d6fcbde7ad2a2849b77d3b --- /dev/null +++ b/marked/Rel-16/23_series/23737/0bf9346902e9a3bdabf05ceacc1947f5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:760aa7330ae24666c5938e0afb12141df4484b0ec6e9feaef75f4f34595bf51c +size 24139 diff --git a/marked/Rel-16/23_series/23737/0ee9d674085524d589646a6c3fb21ec3_img.jpg b/marked/Rel-16/23_series/23737/0ee9d674085524d589646a6c3fb21ec3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aacfaf5be6d078bad96a0d4fe3ec03998ce709a6 --- /dev/null +++ b/marked/Rel-16/23_series/23737/0ee9d674085524d589646a6c3fb21ec3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:90c0618604124bad2883f69d352e857755472ddc684797813b9260ef1f3a73ac +size 107709 diff --git a/marked/Rel-16/23_series/23737/107da2e3495b2f24352c9e3b26ec4841_img.jpg b/marked/Rel-16/23_series/23737/107da2e3495b2f24352c9e3b26ec4841_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3e190c38ab5171389a054945e81e88e75f3fdca8 --- /dev/null +++ b/marked/Rel-16/23_series/23737/107da2e3495b2f24352c9e3b26ec4841_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cec948f0968b9fd6f63e60eda05ebff18dc726a94e5cf2504bf5cee0a2ced498 +size 84419 diff --git a/marked/Rel-16/23_series/23737/12de9b926df0384ec07702671827c9cd_img.jpg b/marked/Rel-16/23_series/23737/12de9b926df0384ec07702671827c9cd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2d03e9910169fe722149e411fbed49a8809f72df --- /dev/null +++ b/marked/Rel-16/23_series/23737/12de9b926df0384ec07702671827c9cd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c01cbc264d5c0fa135e5231f08edb714f2f040c6f31bfc63fd18e12940d9d0b5 +size 51999 diff --git a/marked/Rel-16/23_series/23737/18291be12b470a557e8c9f3a74e021be_img.jpg b/marked/Rel-16/23_series/23737/18291be12b470a557e8c9f3a74e021be_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eded7f2c52f6c011c69c3454e5e6dcb9e8657db0 --- /dev/null +++ b/marked/Rel-16/23_series/23737/18291be12b470a557e8c9f3a74e021be_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2203df6c4608485e2b092112ca7f9169385db5e2e3873ba165e5ec1e35f25bb8 +size 20097 diff --git a/marked/Rel-16/23_series/23737/18722c46c9e8475524e634dedd08bac2_img.jpg b/marked/Rel-16/23_series/23737/18722c46c9e8475524e634dedd08bac2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7f92fc536fb3ed71ec3dc1e897c5f4945730ba0c --- /dev/null +++ b/marked/Rel-16/23_series/23737/18722c46c9e8475524e634dedd08bac2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cf2a9a21ba65a69536e5694d6744491458ab01464291e1212c374c3a847fa4ed +size 13145 diff --git a/marked/Rel-16/23_series/23737/187bba66c887c745c512add37a577c5e_img.jpg b/marked/Rel-16/23_series/23737/187bba66c887c745c512add37a577c5e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..094e39c33a9d10dae59d32603c33bc65e3af0e84 --- /dev/null +++ b/marked/Rel-16/23_series/23737/187bba66c887c745c512add37a577c5e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bcdd202efb014555f758b1933cc0efbdf3b13b2d9a006764825949afab7563e7 +size 12911 diff --git a/marked/Rel-16/23_series/23737/19d7a7ce68d3e9036613910b761c4b24_img.jpg b/marked/Rel-16/23_series/23737/19d7a7ce68d3e9036613910b761c4b24_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c30c8c73397027b73e8067f5ecb58946e88a5061 --- /dev/null +++ b/marked/Rel-16/23_series/23737/19d7a7ce68d3e9036613910b761c4b24_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4bedf03b7a60fe855b6356b3f82f3d033125b2d076052c0e62542499c9079adb +size 18473 diff --git a/marked/Rel-16/23_series/23737/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/marked/Rel-16/23_series/23737/1a827b10290f33d4fec04d0e8ef7a897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..614d2030f27c4a17658c654806cc6fb99f179d64 --- /dev/null +++ b/marked/Rel-16/23_series/23737/1a827b10290f33d4fec04d0e8ef7a897_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2f6265027eacf18ab9788347b0f92df2a8740911780a29f96c4611147bfcde37 +size 89037 diff --git a/marked/Rel-16/23_series/23737/1e030b5b6e3dbfb4ecf21f81c0f76458_img.jpg b/marked/Rel-16/23_series/23737/1e030b5b6e3dbfb4ecf21f81c0f76458_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bb50929ec0fc71dd64830e26e19e192e6f13e51a --- /dev/null +++ b/marked/Rel-16/23_series/23737/1e030b5b6e3dbfb4ecf21f81c0f76458_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fd1e88e0cbdbbca4953b9aec30d6352e94bc5639ddbe788c12790cd37c7a1974 +size 16654 diff --git a/marked/Rel-16/23_series/23737/1eadbbe42cfcac5c0023577110aec5e3_img.jpg b/marked/Rel-16/23_series/23737/1eadbbe42cfcac5c0023577110aec5e3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5041023c8862522b2616b27a81b3ea9cf043a0f0 --- /dev/null +++ b/marked/Rel-16/23_series/23737/1eadbbe42cfcac5c0023577110aec5e3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2690b7e8aabe69f1621936f592f33809ea6bf53e7a0f3c617adacd2cb0695ecc +size 25370 diff --git a/marked/Rel-16/23_series/23737/237b76118be454462fc9b4e96adaa6c7_img.jpg b/marked/Rel-16/23_series/23737/237b76118be454462fc9b4e96adaa6c7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..13f5a32dcbf063df103fdd6223f1744fb6985242 --- /dev/null +++ b/marked/Rel-16/23_series/23737/237b76118be454462fc9b4e96adaa6c7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3b5f9c05340f9c55d92da6ee054150cf50fab189bb7d6146372eea7554344804 +size 63454 diff --git a/marked/Rel-16/23_series/23737/2f587210e4f97c32758c5972e2e83d20_img.jpg b/marked/Rel-16/23_series/23737/2f587210e4f97c32758c5972e2e83d20_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ca518f0db6dc0ad8b751b5335fbb416809b4eb0a --- /dev/null +++ b/marked/Rel-16/23_series/23737/2f587210e4f97c32758c5972e2e83d20_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f9e43dac66ee12dc62e8e1c1d6387bbab5c62cd2f357c8384b83484102d853ca +size 42534 diff --git a/marked/Rel-16/23_series/23737/32ff77da4286b58c4778033acaa10836_img.jpg b/marked/Rel-16/23_series/23737/32ff77da4286b58c4778033acaa10836_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ca518f0db6dc0ad8b751b5335fbb416809b4eb0a --- /dev/null +++ b/marked/Rel-16/23_series/23737/32ff77da4286b58c4778033acaa10836_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f9e43dac66ee12dc62e8e1c1d6387bbab5c62cd2f357c8384b83484102d853ca +size 42534 diff --git a/marked/Rel-16/23_series/23737/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg b/marked/Rel-16/23_series/23737/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..16eaaa330764281bf52c250f0950bea80e21d590 --- /dev/null +++ b/marked/Rel-16/23_series/23737/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:104e930941d690c1332e6e3baade47bde9e7185998ba9aa4aeb51aa4b3bc81dc +size 173405 diff --git a/marked/Rel-16/23_series/23737/36117e9cb27c58484cd8d3e5f9dc7ac3_img.jpg b/marked/Rel-16/23_series/23737/36117e9cb27c58484cd8d3e5f9dc7ac3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8dd0863a2cefee6c653df409e20df2edebfebde9 --- /dev/null +++ b/marked/Rel-16/23_series/23737/36117e9cb27c58484cd8d3e5f9dc7ac3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7fb8eab30c809dce8c317a8c7d3d272cd457c9a6b45d25cdb67eea6603dfbcc8 +size 72141 diff --git a/marked/Rel-16/23_series/23737/3941735fafadf9a59b811f67fcdca7b3_img.jpg b/marked/Rel-16/23_series/23737/3941735fafadf9a59b811f67fcdca7b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9212ff7979c1222279818c72a8f18ca1ac2a3385 --- /dev/null +++ b/marked/Rel-16/23_series/23737/3941735fafadf9a59b811f67fcdca7b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3faa2d45f5accdddfc610b169dfc7a0fbf0676828ff743f7e718f67713871b1a +size 26151 diff --git a/marked/Rel-16/23_series/23737/3b00a61116faef21d3a6009fd350b46a_img.jpg b/marked/Rel-16/23_series/23737/3b00a61116faef21d3a6009fd350b46a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c5e3db680d23d15111cbdc22746c9961cd4bbd51 --- /dev/null +++ b/marked/Rel-16/23_series/23737/3b00a61116faef21d3a6009fd350b46a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:42c7b9e8c59473a154a68f306bbde52af0b202bd025481187d1e4e59e672bba9 +size 22076 diff --git a/marked/Rel-16/23_series/23737/3ef12ae236d1cf073177995b96528744_img.jpg b/marked/Rel-16/23_series/23737/3ef12ae236d1cf073177995b96528744_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b5209d92f8b5818694d624feacd9e37f69ca47a6 --- /dev/null +++ b/marked/Rel-16/23_series/23737/3ef12ae236d1cf073177995b96528744_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f547d5c6e32f2dbfc26ee0e3e9cce5f275cf216dfeb4eb1fe613d2105f860cf6 +size 25674 diff --git a/marked/Rel-16/23_series/23737/4356776ca004ecba5d599667a155d7d4_img.jpg b/marked/Rel-16/23_series/23737/4356776ca004ecba5d599667a155d7d4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c0748cc2bc00418de35a595622c1f946842d44b3 --- /dev/null +++ b/marked/Rel-16/23_series/23737/4356776ca004ecba5d599667a155d7d4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4b8b72164443ed420bbbc0a839b0cfb05da75cdcb62ae4100fc40cc54c998efe +size 73608 diff --git a/marked/Rel-16/23_series/23737/45fba45707b417219df161f8bce0f75a_img.jpg b/marked/Rel-16/23_series/23737/45fba45707b417219df161f8bce0f75a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e7f40aebf1584991849062ac2eabe3e2ad653f22 --- /dev/null +++ b/marked/Rel-16/23_series/23737/45fba45707b417219df161f8bce0f75a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c1946d5279edd2297bc8a6c9590006fa978f73a45692f3294976b1158ac932ad +size 47436 diff --git a/marked/Rel-16/23_series/23737/4792a2ccd62226861fadc22117edb7b1_img.jpg b/marked/Rel-16/23_series/23737/4792a2ccd62226861fadc22117edb7b1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7f786725c7e7a2825b0b88644b4f2ff4b5dee168 --- /dev/null +++ b/marked/Rel-16/23_series/23737/4792a2ccd62226861fadc22117edb7b1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b98abc62494b7fe337f18e2afb8a9530d4ec46afe5a3f473e9c8b450c9a902ac +size 54612 diff --git a/marked/Rel-16/23_series/23737/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg b/marked/Rel-16/23_series/23737/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0023884444bda8a88a4c5e9d22293bec434164f8 --- /dev/null +++ b/marked/Rel-16/23_series/23737/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:16aa8fe0b722d78df408bf89d4c2f7e61466eb972d35443bf29d81b983667897 +size 63602 diff --git a/marked/Rel-16/23_series/23737/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg b/marked/Rel-16/23_series/23737/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..99e9890cbf2433ed9a3d2d64ee5128444e5b69be --- /dev/null +++ b/marked/Rel-16/23_series/23737/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:33dd3af13d0400be8bd8c924efccffeb96ca0dc2a0bc94cf73f8b6dbad395cf4 +size 59971 diff --git a/marked/Rel-16/23_series/23737/4f148853ae68fdcf5e43f7604cab457d_img.jpg b/marked/Rel-16/23_series/23737/4f148853ae68fdcf5e43f7604cab457d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cc1eb8767bf2803804115dc14750c05abb525870 --- /dev/null +++ b/marked/Rel-16/23_series/23737/4f148853ae68fdcf5e43f7604cab457d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7c43d51f5b3ba14dc4368cc45cab81fd0f256fd60e7b8fdb1a48465cb70f0f90 +size 215778 diff --git a/marked/Rel-16/23_series/23737/4ff00a489baaa34a0c01070de1d613db_img.jpg b/marked/Rel-16/23_series/23737/4ff00a489baaa34a0c01070de1d613db_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d8e6f8a0500f41ddb66e37b33bb5fe71a48111dc --- /dev/null +++ b/marked/Rel-16/23_series/23737/4ff00a489baaa34a0c01070de1d613db_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a3c10e130c67db0ae2e184d58b93ce0d5428da2e975308195b91b5d04bb82437 +size 19512 diff --git a/marked/Rel-16/23_series/23737/5132b3a97ac70fe4765c1e07e66b72b3_img.jpg b/marked/Rel-16/23_series/23737/5132b3a97ac70fe4765c1e07e66b72b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..032ddf148deeb23cb4bf47b2fe1320c4afaa71ab --- /dev/null +++ b/marked/Rel-16/23_series/23737/5132b3a97ac70fe4765c1e07e66b72b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:96f2aeade7ee055638c60eac433cb7c638f19ed86d28ecadfc5389ad4ec841d8 +size 21225 diff --git a/marked/Rel-16/23_series/23737/56680df276d8e8d21e5ed5c8e21527c6_img.jpg b/marked/Rel-16/23_series/23737/56680df276d8e8d21e5ed5c8e21527c6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..53eba9b399ddc59220c4c05c79920fabf9659d1d --- /dev/null +++ b/marked/Rel-16/23_series/23737/56680df276d8e8d21e5ed5c8e21527c6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:85e80c001f482c0e7250bf34b75bc7f167c62ae33c2d49de6727eed15fb92646 +size 23890 diff --git a/marked/Rel-16/23_series/23737/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Rel-16/23_series/23737/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3c9d458d5497881cac8c32073979d624a8bffb83 --- /dev/null +++ b/marked/Rel-16/23_series/23737/5a4e62bead259c258d069fd3663ea670_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ee02fc7943f8e2d23d85c2f2deff0b269354413ceb216ec4cb3c734bf9fef6fd +size 224121 diff --git a/marked/Rel-16/23_series/23737/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-16/23_series/23737/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5d96f3f60573f738f13ac4b8e2d0970412a5d651 --- /dev/null +++ b/marked/Rel-16/23_series/23737/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:15bd801abca0e74f4311f792927a13e05d1eb264e32aa289242e33c2b3a9306a +size 9410 diff --git a/marked/Rel-16/23_series/23737/605ad256780bc1b6022dfb65a6e24a3b_img.jpg b/marked/Rel-16/23_series/23737/605ad256780bc1b6022dfb65a6e24a3b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7259531a9453e434bc0ec00b686f2ea633d612cf --- /dev/null +++ b/marked/Rel-16/23_series/23737/605ad256780bc1b6022dfb65a6e24a3b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cbd0082ba195891211e58a58825dc1437ceb982d2f808c0b03b590c6023b2387 +size 69033 diff --git a/marked/Rel-16/23_series/23737/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-16/23_series/23737/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a04442361ce82747c81cbe936b9a8389a754bc77 --- /dev/null +++ b/marked/Rel-16/23_series/23737/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4f8447d2ec9e26751af566aa7d693bec84359fcab40121a1e8e67e0e2764de60 +size 5406 diff --git a/marked/Rel-16/23_series/23737/67d03c9e89620d73e3786c869e559752_img.jpg b/marked/Rel-16/23_series/23737/67d03c9e89620d73e3786c869e559752_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2d21df4e35b79fd243fc5e2d4e3668fc41ed4e91 --- /dev/null +++ b/marked/Rel-16/23_series/23737/67d03c9e89620d73e3786c869e559752_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2da9c480d77f50d15685330e6ff6a48e93d26f23d179aa89dab638c6bae98fd3 +size 15975 diff --git a/marked/Rel-16/23_series/23737/683f755e8456c884716de4fce48c7e63_img.jpg b/marked/Rel-16/23_series/23737/683f755e8456c884716de4fce48c7e63_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c5714575b50a7fb80f5d855e304cf7ab15ae1aab --- /dev/null +++ b/marked/Rel-16/23_series/23737/683f755e8456c884716de4fce48c7e63_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c9e98c5583c4c773e9cea0cfab72dad9e349e2966f02eaf76f439af7c5a4acee +size 22964 diff --git a/marked/Rel-16/23_series/23737/745261f385368efa3f2259c8681874e9_img.jpg b/marked/Rel-16/23_series/23737/745261f385368efa3f2259c8681874e9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6377fdd0382fb1546fe5cdd9aec5e4bf298c2c11 --- /dev/null +++ b/marked/Rel-16/23_series/23737/745261f385368efa3f2259c8681874e9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0b6ff3260c70fdd77be56a1f5a895299099d81b09995788dbb479cf77511495b +size 61624 diff --git a/marked/Rel-16/23_series/23737/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg b/marked/Rel-16/23_series/23737/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2fceb6ec0115c1cbcaa584f386efd7b1866e6b25 --- /dev/null +++ b/marked/Rel-16/23_series/23737/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a54be8605f6faf269964b9742a81bb27ea0cab7b888bbfa3b94ab0e5150c13ab +size 107508 diff --git a/marked/Rel-16/23_series/23737/7d3d5fb5d09c0cd35a9d637be241651e_img.jpg b/marked/Rel-16/23_series/23737/7d3d5fb5d09c0cd35a9d637be241651e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5d64f00fd14e2f8ea0ab2e213d803e6b9d9948ad --- /dev/null +++ b/marked/Rel-16/23_series/23737/7d3d5fb5d09c0cd35a9d637be241651e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f24ded9b265791bff9ae69f6a17cf0361c3394b48532dfa8ec8679e6421b90c0 +size 223352 diff --git a/marked/Rel-16/23_series/23737/7fe5741e83bc9702d1b1d7585ddf66bd_img.jpg b/marked/Rel-16/23_series/23737/7fe5741e83bc9702d1b1d7585ddf66bd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..47bc660f2f0f944b060fb63b1e6dcacf240607ec --- /dev/null +++ b/marked/Rel-16/23_series/23737/7fe5741e83bc9702d1b1d7585ddf66bd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4568c9752e1ae41b8b9641d071970041f35945747868a78875c9b18e86ccb8e0 +size 223207 diff --git a/marked/Rel-16/23_series/23737/82fbb97c1145cac89ac72dd080fad17a_img.jpg b/marked/Rel-16/23_series/23737/82fbb97c1145cac89ac72dd080fad17a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6790fd9934db60c3f2150e2228644d9ee480a98d --- /dev/null +++ b/marked/Rel-16/23_series/23737/82fbb97c1145cac89ac72dd080fad17a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6b353cc0241299e538e9061cf084118a0cc869ab107ef28d38d52c8327a5482c +size 24039 diff --git a/marked/Rel-16/23_series/23737/8307f6b04df072c9332f9987e034272c_img.jpg b/marked/Rel-16/23_series/23737/8307f6b04df072c9332f9987e034272c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..67d4e3499fa6b360ae10842f08ef8ca76dc5dd37 --- /dev/null +++ b/marked/Rel-16/23_series/23737/8307f6b04df072c9332f9987e034272c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c6d7dd2558d3ab76b144524aeb1dd383c7603740c6ea677824a00abfcb15265d +size 41150 diff --git a/marked/Rel-16/23_series/23737/8592a32c2fdf17c1e562f0ba6b7e8e1a_img.jpg b/marked/Rel-16/23_series/23737/8592a32c2fdf17c1e562f0ba6b7e8e1a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dbabe3f2d6231d1ff5fa3e151e2ab5aeed0f4d3b --- /dev/null +++ b/marked/Rel-16/23_series/23737/8592a32c2fdf17c1e562f0ba6b7e8e1a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:38d41f9f7b1bb5547c1c7e9aa74bb339f16d2f8002712604cb1026fa7a2baf6a +size 12806 diff --git a/marked/Rel-16/23_series/23737/8fa679f79a1bb1f527cba9f29e784e89_img.jpg b/marked/Rel-16/23_series/23737/8fa679f79a1bb1f527cba9f29e784e89_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d70bf495992b36a570e5533b0187fdc202035c4c --- /dev/null +++ b/marked/Rel-16/23_series/23737/8fa679f79a1bb1f527cba9f29e784e89_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:26b4947f442b6e589b1c8a5c4df1fd2d6a3bddc722faefb9d3e5a93d6e26f42d +size 51153 diff --git a/marked/Rel-16/23_series/23737/907ece8ef4e70ee3f584e07ad4fd2df4_img.jpg b/marked/Rel-16/23_series/23737/907ece8ef4e70ee3f584e07ad4fd2df4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ebd51b7c122b05e581d0f98550255a7fad01030c --- /dev/null +++ b/marked/Rel-16/23_series/23737/907ece8ef4e70ee3f584e07ad4fd2df4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e15ac91ebb89de150d79ada6c67cc420c456e182bcac1e705375ce53db8ad750 +size 24312 diff --git a/marked/Rel-16/23_series/23737/90ddb84c323b956e2d50a54d3f870566_img.jpg b/marked/Rel-16/23_series/23737/90ddb84c323b956e2d50a54d3f870566_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..018b44d83edba241ae3e009b837ba0bee01fba10 --- /dev/null +++ b/marked/Rel-16/23_series/23737/90ddb84c323b956e2d50a54d3f870566_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5804054438fb019e2a9ba563f8fdd87f72489fc04e9ecf787d7aeba051e6b2b5 +size 222213 diff --git a/marked/Rel-16/23_series/23737/9694add1e3183133a9ddb9f41c48d00e_img.jpg b/marked/Rel-16/23_series/23737/9694add1e3183133a9ddb9f41c48d00e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..25e3a1ae7b9852dd3a19c63e72f56aced63e625b --- /dev/null +++ b/marked/Rel-16/23_series/23737/9694add1e3183133a9ddb9f41c48d00e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:918bf6b557254cc39f800ad8a3d9d8dcf16ed388becf551b61196eb83a878ed7 +size 18431 diff --git a/marked/Rel-16/23_series/23737/9b1ec0090070bdf52ea28763b8d52477_img.jpg b/marked/Rel-16/23_series/23737/9b1ec0090070bdf52ea28763b8d52477_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e55d353bfcfb1f892701d9aa5376a1c6b1543c0e --- /dev/null +++ b/marked/Rel-16/23_series/23737/9b1ec0090070bdf52ea28763b8d52477_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8c1733f97c78e3702dc0f9a22bb42046f55b9af0b7fc6b6a873a9375364849a5 +size 42660 diff --git a/marked/Rel-16/23_series/23737/9e5d66cdb5112ad5cab89552b126e4b9_img.jpg b/marked/Rel-16/23_series/23737/9e5d66cdb5112ad5cab89552b126e4b9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1a9c516806f62be89f389ef1b6c69e70ab08d5fe --- /dev/null +++ b/marked/Rel-16/23_series/23737/9e5d66cdb5112ad5cab89552b126e4b9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:28c34555f03701f5e22dcf0fc814b2e88b0b1b3c9f6ae02c35909b1460b2c00a +size 42172 diff --git a/marked/Rel-16/23_series/23737/9e8ebf03cae78f4f81b697548c2d7250_img.jpg b/marked/Rel-16/23_series/23737/9e8ebf03cae78f4f81b697548c2d7250_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8d1d15a70750487f02e92e6dfdc283e3fc1bead0 --- /dev/null +++ b/marked/Rel-16/23_series/23737/9e8ebf03cae78f4f81b697548c2d7250_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:571d04e8485fc5b1605a2063c597d59f2a03c22b26d917ab679277e80e58ab3b +size 72491 diff --git a/marked/Rel-16/23_series/23737/9ff1b32449ea068bba9647d71904bd59_img.jpg b/marked/Rel-16/23_series/23737/9ff1b32449ea068bba9647d71904bd59_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bc18cf0491f1fa661a401cc13f0bb16f45fc9c5c --- /dev/null +++ b/marked/Rel-16/23_series/23737/9ff1b32449ea068bba9647d71904bd59_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f4c9574ec5400edb5058eed1687e68195ccc084dad916c68f1bc94930d934c4b +size 19614 diff --git a/marked/Rel-16/23_series/23737/a0e8fe7862a6d7341faf5dac275277cc_img.jpg b/marked/Rel-16/23_series/23737/a0e8fe7862a6d7341faf5dac275277cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..53076e7338439103282dc758edc4f71eea156872 --- /dev/null +++ b/marked/Rel-16/23_series/23737/a0e8fe7862a6d7341faf5dac275277cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3050a6bea140ec0ad1e96f399efcc9917d2b237637031b7c567954e5a2ce09db +size 89370 diff --git a/marked/Rel-16/23_series/23737/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/Rel-16/23_series/23737/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4a1f866bdb20774b404de31b5b67e209caf04472 --- /dev/null +++ b/marked/Rel-16/23_series/23737/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:492f3001974d0cb412e3f1111932382031c5196046b31df15d0912e4ea55c74a +size 30351 diff --git a/marked/Rel-16/23_series/23737/a8050baf48cc2c8e25d5ea2d1a67ef39_img.jpg b/marked/Rel-16/23_series/23737/a8050baf48cc2c8e25d5ea2d1a67ef39_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6e91551c234994581c515d89d784bc2a70fc2b6d --- /dev/null +++ b/marked/Rel-16/23_series/23737/a8050baf48cc2c8e25d5ea2d1a67ef39_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c2370e342509285b6161f783db754eaae3da8de595e7f5e43ac23edfca5eb3ba +size 85841 diff --git a/marked/Rel-16/23_series/23737/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg b/marked/Rel-16/23_series/23737/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..46a2b971b8485ff36b37e8e0190ac212dfd99375 --- /dev/null +++ b/marked/Rel-16/23_series/23737/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:08e173b69759ee404678f05975840d68f341dc02c0b35b08de392abd1987eeeb +size 54890 diff --git a/marked/Rel-16/23_series/23737/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg b/marked/Rel-16/23_series/23737/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fbec6eedc4f63e9b37816eadddab080100498ab2 --- /dev/null +++ b/marked/Rel-16/23_series/23737/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c4439bc04767ec418a704bbe3a359156075005db88c1c76117ad610cfe4bbefd +size 57581 diff --git a/marked/Rel-16/23_series/23737/bd50d56ae2c12a92466ba2aea1a78040_img.jpg b/marked/Rel-16/23_series/23737/bd50d56ae2c12a92466ba2aea1a78040_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c338387ceb6ff66a19e5932cd3c395c0598e2d25 --- /dev/null +++ b/marked/Rel-16/23_series/23737/bd50d56ae2c12a92466ba2aea1a78040_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0a35b3e5b41559e361b011c175d3d812e5bdc91767ff76a2ae2dd5d28e6c1c18 +size 22988 diff --git a/marked/Rel-16/23_series/23737/c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg b/marked/Rel-16/23_series/23737/c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..23f38b3ebbe1147b426ec8503871fda0871ff527 --- /dev/null +++ b/marked/Rel-16/23_series/23737/c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f2a993b3030648041611914029858fcfe9b180ecdc04fd90926c71b6ff275c55 +size 60041 diff --git a/marked/Rel-16/23_series/23737/c188a16c19591cada6a7e3e3d690c21b_img.jpg b/marked/Rel-16/23_series/23737/c188a16c19591cada6a7e3e3d690c21b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..74c66c87af098e21d6c9ad35c6ccdbb73fa9c7e4 --- /dev/null +++ b/marked/Rel-16/23_series/23737/c188a16c19591cada6a7e3e3d690c21b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:28ddc400ec32347d97d3d0cabdaf9aae3cafab8201cab4e33ea03c2115d53c53 +size 16907 diff --git a/marked/Rel-16/23_series/23737/c2fc2621e8206d24427b56bcb2398fc0_img.jpg b/marked/Rel-16/23_series/23737/c2fc2621e8206d24427b56bcb2398fc0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..462b1dbd74a68415c4a530281aa7f7a09654741f --- /dev/null +++ b/marked/Rel-16/23_series/23737/c2fc2621e8206d24427b56bcb2398fc0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:86348358ca3d452a65214acd54368de61858f01722ed4cf913c3e747bd70f339 +size 24186 diff --git a/marked/Rel-16/23_series/23737/c9d8a18a6137ad054b841d7a614afb48_img.jpg b/marked/Rel-16/23_series/23737/c9d8a18a6137ad054b841d7a614afb48_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..16f717347d9286df3fc40a0d74848299f8670eea --- /dev/null +++ b/marked/Rel-16/23_series/23737/c9d8a18a6137ad054b841d7a614afb48_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e9ef7ceccd3a9f371de9018d80c4c4953104c33086842069afc857486766ba90 +size 15694 diff --git a/marked/Rel-16/23_series/23737/cb4cfa42ce34febde7bdb882f3fc3094_img.jpg b/marked/Rel-16/23_series/23737/cb4cfa42ce34febde7bdb882f3fc3094_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..99633d0e570897f36b34ed1be261be2afdd9651c --- /dev/null +++ b/marked/Rel-16/23_series/23737/cb4cfa42ce34febde7bdb882f3fc3094_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:75075e053e129295b46bcf61c319f374c892e8480de63a257920748f9168fc7c +size 38591 diff --git a/marked/Rel-16/23_series/23737/d0abac95583b52a3b35f74a215567334_img.jpg b/marked/Rel-16/23_series/23737/d0abac95583b52a3b35f74a215567334_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..340cb95bfc013435d20531371bf057de255d4cfc --- /dev/null +++ b/marked/Rel-16/23_series/23737/d0abac95583b52a3b35f74a215567334_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:39d0e22426167a6bd7e046ba566ac317c04505526aee48e43d93deec3cb841a0 +size 31420 diff --git a/marked/Rel-16/23_series/23737/d3b5eac55166fc428a223bba5c46961b_img.jpg b/marked/Rel-16/23_series/23737/d3b5eac55166fc428a223bba5c46961b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fb24982b785cb016878a28c08889e23cc74cd922 --- /dev/null +++ b/marked/Rel-16/23_series/23737/d3b5eac55166fc428a223bba5c46961b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d74d49181016bad82963c2586428047c92b93a71929592d4c9ee303d06f2ef04 +size 20002 diff --git a/marked/Rel-16/23_series/23737/d7372d5c7db77605b87637e0f8d87d54_img.jpg b/marked/Rel-16/23_series/23737/d7372d5c7db77605b87637e0f8d87d54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..80f074a14b3872d547bb05bf712740273638135d --- /dev/null +++ b/marked/Rel-16/23_series/23737/d7372d5c7db77605b87637e0f8d87d54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6f379ff8042cf28023a7641aabfa5cd1346a14e6e61a48d37605b7319825dff2 +size 12960 diff --git a/marked/Rel-16/23_series/23737/dd5771673aececa53d42ece89218299d_img.jpg b/marked/Rel-16/23_series/23737/dd5771673aececa53d42ece89218299d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f8f16a28e07e5e1d92407345dfff41aeb321bcee --- /dev/null +++ b/marked/Rel-16/23_series/23737/dd5771673aececa53d42ece89218299d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7ed8ef16e513b7d8625cb6c6b444eacba6a772ea4e25a365fa616ac322fc2529 +size 222670 diff --git a/marked/Rel-16/23_series/23737/ddee3e67e0dfc22e25188fa635a19558_img.jpg b/marked/Rel-16/23_series/23737/ddee3e67e0dfc22e25188fa635a19558_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..976400fdcc5a3a958b309a915f1f4e0d9e16479e --- /dev/null +++ b/marked/Rel-16/23_series/23737/ddee3e67e0dfc22e25188fa635a19558_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0d5f3cdc1645d390031094ec9415f83178d7a77043c9c037b8d5ddf05d82de0b +size 25938 diff --git a/marked/Rel-16/23_series/23737/e1476fd216f6cf773e262013fb4aba7d_img.jpg b/marked/Rel-16/23_series/23737/e1476fd216f6cf773e262013fb4aba7d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..001f0e3c7a4ec24a3251f37b86e51b30d13b0560 --- /dev/null +++ b/marked/Rel-16/23_series/23737/e1476fd216f6cf773e262013fb4aba7d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1ac53f7fc4995118731de8f8ac75fbab634c77403dbf4efb8fd5243a5a4bb92c +size 53179 diff --git a/marked/Rel-16/23_series/23737/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/marked/Rel-16/23_series/23737/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4aab3a8c991db1d26f213d800913a33e2020e081 --- /dev/null +++ b/marked/Rel-16/23_series/23737/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ee882915b524eb2d6c2594d15bf17e9ed08e7e9813977c489186a12f47289ba8 +size 43255 diff --git a/marked/Rel-16/23_series/23737/e354b57563dae469c00b412b2abdf765_img.jpg b/marked/Rel-16/23_series/23737/e354b57563dae469c00b412b2abdf765_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bde5e31f864b2ba469764c7b4bd339c364aa9832 --- /dev/null +++ b/marked/Rel-16/23_series/23737/e354b57563dae469c00b412b2abdf765_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1a95cdfc069209443d5f26705318b9609b816f151f4a5b268408afa1d1e81674 +size 221421 diff --git a/marked/Rel-16/23_series/23737/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/Rel-16/23_series/23737/e6df2733626a85205c1db682e6259c46_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..438b84254b24f18a3c4af2e9b3082f79f05bf056 --- /dev/null +++ b/marked/Rel-16/23_series/23737/e6df2733626a85205c1db682e6259c46_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6bf94de6364dc9285980814a9f7e00782d8fe688f42cfe6a2b42c4e52f798ab6 +size 21075 diff --git a/marked/Rel-16/23_series/23737/e76da0473640f804b16197e57460061f_img.jpg b/marked/Rel-16/23_series/23737/e76da0473640f804b16197e57460061f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b44cccefd0f9a7a4d8b8cd9b203c0f6e663670be --- /dev/null +++ b/marked/Rel-16/23_series/23737/e76da0473640f804b16197e57460061f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e21edfc1e72e297e516a22928900d1f0b85da3d158ed376be01980c9a8401a64 +size 47905 diff --git a/marked/Rel-16/23_series/23737/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg b/marked/Rel-16/23_series/23737/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6e59fa39159888fb31dc649522406adde619b436 --- /dev/null +++ b/marked/Rel-16/23_series/23737/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fb59eaa9f48b50447ce69e62b989f893ce990a223b79ad41f2427ed1073dbcde +size 172176 diff --git a/marked/Rel-16/23_series/23737/e90987faabad6a6665cd8ed1151dc474_img.jpg b/marked/Rel-16/23_series/23737/e90987faabad6a6665cd8ed1151dc474_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b364a8dd9b4f0e7066935ebf39917046d177c5f2 --- /dev/null +++ b/marked/Rel-16/23_series/23737/e90987faabad6a6665cd8ed1151dc474_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:45f4d61014fd674d7a3e59e294d8e90556af1dcc3ef87322ddd56b7c38dd625b +size 173773 diff --git a/marked/Rel-16/23_series/23737/ead623e6a8ec701df64567695a57d01c_img.jpg b/marked/Rel-16/23_series/23737/ead623e6a8ec701df64567695a57d01c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..20d269b30f85a1d13558aa19082e16ec5df08748 --- /dev/null +++ b/marked/Rel-16/23_series/23737/ead623e6a8ec701df64567695a57d01c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:255a7af9a0823521f49feb52ee6489302c2b3a544e5636f13ab2f562512bc28e +size 61405 diff --git a/marked/Rel-16/23_series/23737/ec31af936fa94a6917bf19f154df8ac3_img.jpg b/marked/Rel-16/23_series/23737/ec31af936fa94a6917bf19f154df8ac3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d4109c01a35275d4e5d11802088920122ea87c68 --- /dev/null +++ b/marked/Rel-16/23_series/23737/ec31af936fa94a6917bf19f154df8ac3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4a4b59004b233a8a1199a41fbd8ac27cbd9238e315e9b2b15e0680ce97e66fcf +size 41746 diff --git a/marked/Rel-16/23_series/23737/f97535cdaa4fe017f4659512f4f78028_img.jpg b/marked/Rel-16/23_series/23737/f97535cdaa4fe017f4659512f4f78028_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9de17c897714bbe909fd161220f923e08d5c9703 --- /dev/null +++ b/marked/Rel-16/23_series/23737/f97535cdaa4fe017f4659512f4f78028_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dff8f20ebe4f3a273ebc7ad7bcb613fd2a171e82237ef7a2a522028c3fc60b95 +size 26011 diff --git a/marked/Rel-16/23_series/23737/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/marked/Rel-16/23_series/23737/ff0952ef692c9d960ce5f6708bcc9711_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d2fa57e2858b4532a5adf31409c565cf7fa05792 --- /dev/null +++ b/marked/Rel-16/23_series/23737/ff0952ef692c9d960ce5f6708bcc9711_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e88af49375521c8c372f6a41fc26746e2893324ab2ece54a5eedbb0e9089d1eb +size 173323 diff --git a/marked/Rel-16/23_series/23737/ff5f89b660edddb67971d7d3d4ce87ef_img.jpg b/marked/Rel-16/23_series/23737/ff5f89b660edddb67971d7d3d4ce87ef_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0890ab30f40727da7de025f95c1fc923bc9c4489 --- /dev/null +++ b/marked/Rel-16/23_series/23737/ff5f89b660edddb67971d7d3d4ce87ef_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3308cd807b661ffa2f7addcd9780f482029ec496e50b7ace30f4dda5e2488707 +size 32245 diff --git a/marked/Rel-16/23_series/23737/raw.md b/marked/Rel-16/23_series/23737/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..698ae75cfe7543170343f92139617005b59e76e2 --- /dev/null +++ b/marked/Rel-16/23_series/23737/raw.md @@ -0,0 +1,5798 @@ +# **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on architecture aspects for using satellite access in 5G (Release 16)** + + + +--- + +The 5G logo, featuring 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 + + + +The 3GPP logo, featuring the text "3GPP" in a stylized, black, sans-serif font. Below the "P" is a red signal icon. Underneath the logo, the text "A GLOBAL INITIATIVE" is written in a smaller, black, sans-serif font. + +3GPP logo + +## --- **Keywords** + +--- + +3GPP, 5G, Architecture, Latency, Mobility + +## **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** + +--- + +
If PCF is used. | +| Changes to UPF needed | Yes | No | Maybe | UPF needs to send information on QoS Limitation to the SMF, if UPF information is available | +| Changes to N4 protocol/interface needed | Yes | No | Maybe | If UPF information is available. | +| Changes to SBI between AMF and SMF needed | No | Yes | Maybe | SBI = Service Based Interface, i.e. it refers to the SBA clients and servers that make use of the SBA architecture, e.g. AMF as SBA client and SMF as SBA server
If AMF information is available. | +| Changes to SBI between SMF and PCF needed | Yes | Yes | Maybe | SBI = Service Based Interface, i.e. it refers to the SBA clients and servers that make use of the SBA architecture, e.g. SMF as SBA client and PCF as SBA server.
If PCF is used. | + +Candidate Solution #14 addresses completely Key Issue #5 and provides a solution for the mobility aspects related to the use of satellite for backhaul. + +## 7.6 Evaluation of solutions for Key Issue #6 - RAN mobility with NGSO regenerative-based satellite access + +See Key Issue #1. + +## 7.7 Evaluation of solutions for Key Issue #7 - Multi connectivity with satellite access + +The satellite access is considered as a 3GPP access in SA WG2, a single registered UE cannot simultaneously establish multiple PDU sessions via different 3GPP RATs. Therefore, the multiple PDU sessions scenario described in KI #7 will not occur, and no solutions are needed. + +Dual-connectivity via satellite RAN and terrestrial RAN is a RAN issue, and RAN has conducted related study, thus SA WG2 should just follow RAN conclusion. + +## 7.8 Evaluation of solutions for Key Issue #8 - The role of satellite link in content distribution towards the edge + +This clause provides evaluation of Candidate Solutions for Key Issue #7. + +A unique Candidate Solution has been proposed: + +- Candidate Solution #6 - Role of satellite backhaul in content distribution towards the edge. Two approaches are proposed within Solution 6: + - Approach #A: Uplink classifier based Approach: This approach proposes to use UL CL standardized in TS 23.501 [6] clause 5.6.4.2 and TS 23.502 [3] clause 4.3.5.4. A UPF supporting UL CL is selected and diverts the traffic which matches with traffic filters provided by SMF. This solution should prevent the satellite link from multiple content transmissions. However, this approach implies having a permanent PDU session between the UE and the remote DN, and thus having a satellite link always loaded because of the resource allocation to each PDU session till their release + - Approach #B- Multi-homing: A multi-homed approach defined in TS 23.501 [6] clause 5.6.4.2 and TS 23.502 [3] clause 4.3.5.4 can also be appropriate. The PDU session is associated to multiple IPv6 prefix and a UPF supporting the Branching Point functionality is configured by SMF. The Branching Point provides traffic forwarding toward the PDU session anchors. Thus, one anchor can route the traffic toward a local DN and the other toward the remote DN. + +The evaluation of both approaches indicates that they are based on existing specifications and should not have any impact on existing specifications. + +## 7.9 Evaluation of solutions for Key Issue #9 - Multi connectivity with hybrid satellite/terrestrial backhaul + +Topics listed in KI#9 are out of scope of this study. Accordingly no solutions are proposed for this KI. + +## 7.10 Evaluation of solutions for Key Issue #10 - Regulatory services with super-national satellite ground station + +For Key Issue #10 - " Key Issue #10: Regulatory services with super-national satellite ground station ". This Key Issue identifies the following aspects that need to be solved for super-national cell coverage area. + +Two candidate solutions have been proposed. + +Candidate Solution #12 "Solution 12: Satellite cells for 5G satellite access with large or moving radio coverage". This solution introduces the definition and usage of Satellite cells and the support needed from UEs and sNBs. In a first approach, Satellite Cells are defined as Virtual Cells, whilst in a second approach satellite cells are defined as standard cells in association with the use of geographical zones that are sent by the network to the UE and stored with UEs. In both cases the main assumption is that the UE has access to its position. This Candidate Solution answers to a) to f) above. It is understood that charging and tariff notifications (items g) could be possible based on serving Satellite cells and/or Satellite TAs. + +Solution #13" Country specific PLMN selection" Country specific PLMN selection" allows the UE uses its awareness of its location. If the UE is aware of its location, it can use this knowledge to select among the PLMNs of the country of the present UE location. It can also trigger the UE to change PLMN when it changes country. If the UE is not aware of its location within certain country, Solution 13 allows the network to enforce the UE registration to PLMNs of the country of the UE location by rejecting the registration attempt to PLMN of another country and giving the UE a hint of which MCC PLMNs to attempt instead. Solution #13 answers to items a - d) of this Key Issue. In addition, the same solution helps to solve also item e) as well by ensuring that the UE is registered to a PLMN of the same country as the present UE location. + +# 8 Conclusions + +## 8.1 Conclusion on solutions for Key Issue #1 + +Solution #1 does not require any modification of the existing 3GPP specifications for the 5G-CN. Depending on its implementation it could require modifications for NG-RAN for UE location. Evaluation of the RAN aspects are within RAN groups' scope. + +Solution #12 needs further evaluation and may need further work in SA2 but has so far been found fulfil KI#1, but with a different set of properties and impacts to the 5GSUE, RAN and 5G-CN. So far, no show stoppers have been found from SA2 related aspects. As RAN dependencies have been identified in both solution #1 and solution #12, RAN groups need to evaluate these solutions. + +Whether Solution #1 and/or Solution #12 can proceed to normative work is conditional on the feedback from RAN groups. + +NOTE: The same conclusion is agreed for Key Issue #6. + +## 8.2 Conclusion on solutions for Key Issue #2 + +Key Issue #2 studied Mobility Management with moving satellite coverage area. 3GPP system should adapt to being usable over variety of satellite types without putting pre-requisite conditions on the capabilities of the satellites, or the satellite constellation to be used. The system impact on 3GPP system depends on what kind of satellites are used, and therefore, the following conclusions are made. + +Both Solutions #1 and #9 have been identified as having no impacts on the existing 3GPP specifications of the 5G-CN. It is thus concluded that no normative work is needed in SA2 for these solutions. Feedback and evaluation of these solutions has also been requested to the RAN Working Group. + +Solutions #7 and #8 have both impacts on the 5G-CN. Dependency with respect to Moving Tracking Areas in the case of Satellite based RAN has been identified for these solutions. Before concluding on the normative work for Solution #7 or Solution #8, input from RAN WGs is needed, e.g. if Moving Tracking Areas would be selected as a basis for normative activity during Rel. 17. + +## 8.3 Conclusion on solutions for Key Issue #3 + +It is concluded to take Candidate Solution #10 for normative work on this key issue. + +Key Issue #3 is for satellite delay's impact on NAS procedures. Following the evaluation in clause 6.10, no impacts are identified for LEO and MEO satellite systems for NAS timers. The Registration procedure needs to be modified for GEO satellite system to enable the AMF to indicate to the UE, when extended NAS timers are used in the current Registration Area that the UE shall use in the current Registration Area. + +## 8.4 Conclusion on solutions for Key Issue #4 + +Key Issue #4 studied QoS with satellite access. Following the evaluation in clause 7.4, it is concluded to take Candidate Solution #2 as the baseline for normative work on this Key Issue + +It is also proposed to use Candidate Solution #14 as way forward for KI#4, depending on decisions to be made by RAN groups with respect to mobility and QoS. + +## 8.5 Conclusion on solutions for Key Issue #5 + +It is proposed to use Candidate Solution #11 for the basis of normative work. + +For mobility aspects, it is proposed to use Candidate Solution #14 as way forward for KI#5, depending on decisions to be made by RAN groups with respect to mobility and QoS. + +## 8.6 Conclusion on solutions for Key Issue #6 + +Conclusions agreed for Key Issue #1 are also applicable to Key Issue #6. + +## 8.7 Conclusion on solutions for Key Issue #7 + +Key issue #7 includes study of simultaneous PDU Session multi-connectivity of a UE over terrestrial RAN and satellite-based NG-RAN. This topic is not further progressed in this study and it is concluded that no normative work is needed. + +**NOTE:** A device with two UEs may simultaneously have separate Registrations and PDU Sessions in satellite and terrestrial networks with different PLMNs. + +Key issue #7 also includes study of dual-connectivity over terrestrial RAN and satellite-based NG-RAN. This topic is more RAN related and will not be further progressed in this study. It is concluded that, for this topic, only alignment to RAN (if any) is needed in normative phase. + +## 8.8 Conclusion on solutions for Key Issue #8 + +It is concluded that Solution #6 has no impact on the 5GS architecture and thus requires no normative work. + +In order to satisfy requirements in certain geographies that indicate that the information broadcast by a satellite are receivable only within the limits of the country to which the PLMN belongs, during normative phase solutions need to be defined to restrict such broadcasting. Whether such solutions need to be defined in SA2 or RAN will be decided during normative work. + +## 8.9 Conclusion on solutions for Key Issue #9 + +As KI#9 goes beyond the scope of this study, it is concluded not to have a normative work on this Key Issue. + +## 8.10 Conclusion on solutions for Key Issue #10 + +Candidate Solution #12 and Candidate Solution #13 have been evaluated. SA2 is not aware of any issues that would prevent the feasibility of either solution. + +Both solutions have external dependencies outside of SA2. Before concluding on the normative work, SA2 requests the evaluation and guidance of RAN2 and RAN3 for Solution #12 and CT1 for Solution #13. + +# Annex A: Characteristics of satellite systems + +## A.1 General + +This annex describes the main characteristics of satellite systems when considering their integration with the 5G system. + +## A.2 Class of orbit + +On the one hand, our planet attracts as a main body the much smaller satellite, which motion is dictated as a consequence by the laws of Kepler. On the other hand, the environment of Earth can be also constraining: the higher density of the atmosphere, debris from launchers and former satellites in the lower altitudes, as well as higher energy particles trapped in the Van Allen belts between 2000 and 8000 km's altitudes are to be avoided. These two constraints contribute to defining several classes of orbits that are used for communication satellites: + +- **Geostationary (GEO)** satellites, located precisely in the plane of the Equator at an altitude of 35 786 km, these satellites rotate at the same rate as the Earth's rotation: a GEO satellite stands still with respect to Earth. Thanks to this property, a single GEO satellite is sufficient to create a continuous coverage. +- **Non-Geostationary Orbiting (NGSO)** satellites: NGSO satellites do not stand still with respect to Earth. Should service continuity be required over time, a number of satellites (a constellation) is required to meet this requirement; the lower the altitude the higher the number of satellites + +Different classes of NGSO satellites are listed below: + +- **Low-Earth Orbiting (LEO)** satellites, with altitude ranging 500 km and 2000 km, and with inclination angle of the orbital plane ranging from 0 to more than 90 degrees. These constellations are placed above the International Space Station and debris, and below the first Van Allen belt. +- **Medium-Earth Orbiting (MEO)** satellites, with altitude ranging from 8000 to 20,000 km. The inclination angle of the orbital plane ranges from 0 to more than 90 degrees. These constellations are placed above the Van Allen belts. +- **Highly-Eccentric Orbiting (HEO)** satellites, with a range of operational altitudes (the orbit of such satellites being designed for the spacecraft to be exploited when the vehicle is closer to its apogee - the higher part of the orbit -) between 7,000 km and more than 45,000 km. The inclination angle is selected so as to compensate, completely or partially, the relative motion of Earth with respect to the orbital plane, allowing the satellite to cover successively different parts of Northern land masses (e.g. Western Europe, North America, and Northern Asia). + + + +Diagram illustrating the classes of orbits of satellites around planet Earth. The diagram shows a central circle representing 'planet Earth'. Four elliptical orbits are depicted: GEO (Geostationary) is a circular orbit in the equatorial plane; MEO (Medium-Earth Orbiting) is a circular orbit above GEO; LEO (Low-Earth Orbiting) is a circular orbit below MEO; and HEO (Highly-Eccentric Orbiting) is a highly elliptical orbit that intersects the other orbits and is inclined relative to the equatorial plane. + +**Figure A.2-1: Illustration of the classes of orbits of satellites** + +## A.3 Geometrical coverage of satellite and propagation delay + +As depicted in the following figure, the theoretical geometrical coverage of a satellite is associated to its altitude and the minimum elevation angle under which the satellite is seen by the UE above the horizon. + + + +A diagram showing a satellite in orbit above Earth. The Earth is represented by a circle. The satellite is at a certain altitude, indicated by a vertical line from the Earth's center. The satellite's coverage area on Earth is shown as a shaded circular cap. A User Equipment (UE) is located on the Earth's surface. The angle between the horizon at the UE and the line of sight to the satellite is labeled 'Elevation Angle'. Other labels include 'Satellite altitude', 'Satellite Geometrical coverage', and 'Earth'. + +Diagram illustrating the geometrical coverage of a satellite. + +**Figure A.3-1: Illustration of the geometrical coverage of a satellite** + +The following figure illustrates the geometrical coverage for a LEO satellite and for geostationary-satellites: + + + +A world map showing the Earth with latitude and longitude lines. Two types of satellite coverage are indicated. A small blue circle over North America represents the 'Geometrical coverage for a LEO satellite'. Three large, overlapping elliptical regions represent the 'Geometrical coverage for a GEO satellite', centered at different longitudes. The map includes longitude labels from 210° to 270° and 0° to 270°, and latitude labels from 80° to -80°. + +World map showing the geometrical coverage of LEO and GEO satellites. + +**Figure A.3-2: Illustration of the geometrical coverage of a LEO satellite and of GEO satellites** + +The following tables provide elevation, distance and geometrical coverage related figures for different classes of satellites: + +| Class of orbit | Elevation angle (degrees) | | | +|----------------|-------------------------------------------------------|--------|--------| +| Altitude (km) | 0 | 10 | 90 | +| LEO | Distance - Satellite to UE (km) | | | +| 800 | 3 293 | 2 367 | 800 | +| 1400 | 4 452 | 3 480 | 1 400 | +| MEO | Distance - Satellite to UE (km) | | | +| 8000 | 12 886 | 11 826 | 8 000 | +| GEO | Distance - Satellite to UE (km) | | | +| 35786 | 41 679 | 40 586 | 35 786 | +| | | | | +| | | | | +| Class of orbit | Elevation angle (degrees) | | | +| Altitude (km) | 0 | 10 | 90 | +| LEO | Propagation Delay - Satellite to UE (millisec) | | | +| 800 | 11,0 | 7,9 | 2,7 | +| 1400 | 14,8 | 11,6 | 4,7 | +| MEO | Propagation Delay - Satellite to UE (millisec) | | | +| 8000 | 43,0 | 39,4 | 26,7 | +| GEO | Propagation Delay - Satellite to UE (millisec) | | | +| 35786 | 138,9 | 135,3 | 119,3 | +| | | | | +| | | | | +| Class of orbit | Elevation angle (degrees) | | | +| Altitude (km) | 0 | 10 | 90 | +| LEO | Geometrical Coverage Radius - (km) | | | +| 800 | 3 040 | 2 109 | - | +| 1400 | 3 887 | 2 910 | - | +| MEO | Geometrical Coverage Radius - (km) | | | +| 8000 | 7 087 | 6 022 | - | +| GEO | Geometrical Coverage Radius - (km) | | | +| 35786 | 9 050 | 7 952 | - | + +**Figure A.3-3: Geometrical coverage radius, propagation distance and delay for different orbits** + +NOTE: The above figure provides only examples, some designers may decide to select lower altitudes as this contribute lowering the propagation delay. + +The following table illustrates the number of satellites that are necessary for a constellation of satellites to provide continuous coverage for an elevation angle ranging from 5 to 10 degrees. Global coverage may not be fully achieved for MEO or GEO satellite, however in this case the vast majority of the world population is covered. + +| Class of orbit | # of satellites to cover Earth | +|----------------|--------------------------------| +| LEO | | +| 800 | circa 80 | +| 1400 | circa 50 | +| MEO | | +| 8000 | circa 10 | +| GEO | | +| 35786 | circa 3 | + +**Figure A.3-4: Illustration of number satellites in a constellation for continuous Earth coverage** + +## A.4 Type of satellite communication payloads + +Communication payloads embarked on-board satellites are of two main categories, for any type of satellite (whether GEO or NGSO): + +- **Transparent payloads:** the electromagnetic wave that are transmitted from Earth surface are converted by a satellite receive antenna into an electric signal which is channel filtered and amplified by low-noise amplifier (LNA). The signal is then frequency converted. A high power amplifier (HPA) delivers finally the signal to a + +transmitting antenna generating a reconditioned electromagnetic wave towards the Earth surface where receive station are located. + +- **Regenerative payloads:** an On-Board Processor (OBP), is inserted between the LNA and the HPA. This OBP allows converting the air interface between the uplink (from Earth to satellite) and the down link (from satellite to Earth). It allows to correct bits or packet in errors before retransmitting them, or to route packet between beams. Ultimately any network function can be implemented, as the expense of power and mass, thanks to an OBP (including gNB CU's or DU's, or any function attached to a CN). +- **Inter-Satellite Links (ISL):** can also interconnect regenerative satellite payloads. Through ISL's satellites can be interconnected through a dedicated mesh-network. + +## --- A.5 Handovers + +While a UE would stand still, hand overs from one satellite to another satellite could be imposed by the motion of NGSO satellite in a constellation, whilst GEO would stand still with respect to Earth. + +The average rate of hand over for a single UE would depend on the actual altitude of spacecrafts in a constellation. Typical values for LEO are in the order of 10 minutes. + +Not all UE's would be handed over simultaneously. + +NOTE: Such a handover mechanism is illustrated in Solutions #1 and #12 of this document. + +## --- A.6 Air interfaces + +Air interfaces can include: + +- 3GPP defined air interfaces, such as the New Radio; +- Non-3GPP defined air interfaces. + +Unless otherwise indicated, 3GPP NR will be assumed in this Technical Report. + +## --- A.7 General considerations on the use of satellite networks + +In relation to the coverage associate with Non-Geostationary Satellite Networks, or Geostationary-Satellite ones, the use of satellite networks is related to: + +- The complement of terrestrial networks where these terrestrial networks are not available, permanently for physically (maritime or aeronautical constraints) or economic reasons, or for temporary reasons associated to local a unavailability of a terrestrial of network (drought, Earth quake) or local overload of the demand; +- Satellite networks can be used for broadcast over large areas of a same content, for multicast (with acknowledge of delivery of content), for unicast; +- Use cases are related to the actual of altitude of the satellite platforms and the associated delay of propagation. + +# Annex B: Architecture Models for Satellite Integration in 5GS + +## B.1 Elementary satellite network architecture + +The physical implementation of satellite network architecture can always be sketched as displayed in the following figure: + + + +Figure B.1-1: Reference Satellite Access Network Architecture. This diagram shows a 'Satellite enabled UE' (represented by a smartphone icon) connected to a 'Satellite' via a dashed 'Service link'. The 'Satellite' is connected to a 'Hub' (represented by a satellite dish and a server icon) via a dashed 'Feeder link'. The 'Hub' is connected to a 'Data Network' (represented by a cloud icon) via a solid line. + +Figure B.1-1: Reference Satellite Access Network Architecture + +A satellite network is always composed of: + +- One, or more, satellite(s), embarking a telecommunication payload. +- Satellite enabled UEs, such as IoT devices, broadband vehicular or fixed terminals. +- A Hub, including an RF Earth station, and a data centre including (co-located or not) RAN and CN related functions. The hub is also interconnected to (a) data network(s). +- UEs interconnected to the hub through the satellite. + +## B.2 Reference architecture with satellite enabled NR-RAN + +The following figure depicts a reference architecture for a direct access with a satellite enabled NR-RAN (see below): + + + +Figure B.2-1: 5GS with Satellite enabled NR-RAN. This diagram shows a 'UE with Satellite access' (represented by a smartphone icon) connected to a 'Satellite enabled NR-RAN' (represented by a box with a satellite icon) via N1 and NR interfaces. The 'Satellite enabled NR-RAN' is connected to a '5G CN' (represented by a server icon) via N1, N2, and N3 interfaces. The '5G CN' is connected to a 'DN' (represented by a cloud icon) via the N6 interface. + +Figure B.2-1: 5GS with Satellite enabled NR-RAN + +Knowing the possible nature of satellite payloads (transparent or re-generative), the instantiation of this architecture can have several forms: + +In a first implementation, the satellite is transparent, the NR signals are generated from gNBs from a satellite enabled NR-RAN that are located on ground. The satellite is equivalent to a Radio Frequency (RF) Remote Unit, and is full transparent to the New Radio protocols, including the physical layer (see below). + + + +Figure B.2-2: 5GS with transparent satellite enabled NR-RAN. This diagram shows a 'UE' (represented by a smartphone icon) connected to a 'Radio Frequency Remote Unit' (represented by a satellite icon) via an NR-Uu interface. The 'Radio Frequency Remote Unit' is connected to a 'Remote Radio Unit' (represented by a satellite dish icon) via an NR-Uu interface. The 'Remote Radio Unit' is connected to a 'gNB' (represented by a server icon) via an N1/2/3 interface. The 'gNB' is connected to a '5G CN' (represented by a server icon) via an N1/2/3 interface. The '5G CN' is connected to a 'Data Network' (represented by a cloud icon) via an N6 interface. + +Figure B.2-2: 5GS with transparent satellite enabled NR-RAN + +In a second implementation, the satellite is regenerative. The satellite payload implements a gNB-DU as part of a satellite enabled NR-RAN. Some of the protocols of the NR are processed by the satellite. A Satellite Radio Interface (SRI) transports the F1 protocol between the on-ground CU and the on-board DU (it can be the NR (see below)). + + + +Diagram of 5GS with regenerative satellite enabled NR-RAN and distributed gNB. A UE connects to a satellite gNB-DU via NR-Uu. The gNB-DU connects to a Remote Radio Unit via F1 over SRI. The Remote Radio Unit connects to a gNB-CU. The gNB-CU connects to a 5G CN via N1/2/3. The 5G CN connects to a Data Network via N6. + +Figure B.2-3: 5GS with regenerative satellite enabled NR-RAN and distributed gNB + +In a third implementation, the satellite is regenerative. The satellite payload implements a full gNB supporting a satellite enabled NR-RAN. A Satellite Radio Interface (SRI) transports the N1/N2/N3 interfaces between the on-ground 5G CN and the on-board gNB-CU (see below). + + + +Diagram of 5GS with regenerative satellite enabled NR-RAN and on-board gNB. A UE connects to a satellite gNB via NR-Uu. The gNB connects to a Remote Radio Unit via NG over SRI. The Remote Radio Unit connects to a gNB-CU. The gNB-CU connects to a 5G CN via N1/2/3. The 5G CN connects to a Data Network via N6. + +Figure B.2-4: 5GS with regenerative satellite enabled NR-RAN and on-board gNB + +One can note that with a regenerative implementation (either with distributed gNB or not) a 5GS can have a global coverage, providing a single 5G CN with global or regional (continental or sub-continental) coverage as well. This is valid for GEO or LEO (see below): + + + +Diagram of 5GS with regenerative satellite enabled NR-RAN, with ISL for regional or global coverage. Three UEs connect to three separate satellite gNB-DUs via NR-Uu. The gNB-DUs are interconnected via F1 over SRI (ISL). The bottom gNB-DU connects to a Remote Radio Unit via F1 over SRI. The Remote Radio Unit connects to a gNB-CU. The gNB-CU connects to a 5G CN via N1/2/3. The 5G CN connects to a Data Network via N6. + +Figure B.2-5: 5GS with regenerative satellite enabled NR-RAN, with ISL for regional or global coverage + +Another configuration (see below) may consist in satellites each embarking a gNB supporting a satellite enabled NR-RAN, and 5G CN's accessing these gNBs, as described in the following figure, where specific (or not) satellite radio interfaces are used to handle control and user planes: + + + +The diagram illustrates a 5GS architecture with regenerative satellite enabled NR-RAN. It features three stacked satellite units, each containing a gNB. Each gNB is connected to a User Equipment (UE) via an NR-Uu interface. The gNBs are interconnected vertically via Xn-C and Xn-U interfaces over SRI. Each gNB is also connected to a Remote Radio Unit (RRU) via an NG over SRI interface. The RRUs are connected to a central 5G CN via NG (N1/N2/N3) interfaces. The 5G CN is connected to a Data Network via an N6 interface. + +Diagram of 5GS with regenerative satellite enabled NR-RAN, showing three stacked satellite gNB units connected to UEs and a central 5G CN via Remote Radio Units. + +Figure B.2-6: 5GS with regenerative satellite enabled NR-RAN, with ISL & multiple 5G CN connectivity + +# Annex C: Change history + +| Change history | | | | | | | | +|----------------|-----------|------|----|-----|-----|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2018-07 | | | | | | TR skeleton added as approved from S2-187199 during S2-128 | 0.0.0 | +| 2018-07 | | | | | | TR Scope added from S2-187245
Annex A (informative) added from S2-187236
Annex B (informative) added from S2-187246
Annex A "Change History" Renamed into "Annex C" | 0.1.0 | +| 2018-08 | S2#128BIS | | | | | During S2 128#bis, addition of:
- Reference scenarios in Clause 4 from S2-188487
- Key issues #1, #2, and #3 in Clause 5 from S2-188488, S2-188489 and S2-188490 | 0.2.0 | +| 2018-10 | S2#129 | | | | | During S2 129:
- Modification of title of clause 4.2 (addition of "assumptions")
- Addition of clause 4.3 from S2-1811139
- Addition of 2 points to be addressed on each of the Key Issues #1 & #2 from S2-1811139
- Addition of Key Issue on QoS with satellite access from S2-1811462
- Addition of Key issue on QoS Feedback from satellite backhaul from S2-1811463
- Addition of Solution #1 on Mobility Management from S2-1811540 | 0.3.0 | +| 2019-01 | S2#129BIS | | | | | During S2 129BIS:
- Editorial modifications as approved in S2-1812036 (Key issue #4 & #5 numbering, and Editor's note modification).
- From S2-1812776, addition of Key Issue #6 on RAN mobility with NGSO regenerative-based satellite access.
- From S2-1813212, addition of Key Issue #7 on Multi connectivity with satellite access
- From S2-1813224, Revision on Solution #1
- From S2-1812780, Addition of a New solution: new RAT type satellite
- From S2-1812781 add a solution for QoS with Satellite Backhaul by using UPF information to inform SMF about the need for QoS adaptation in case of the use of satellite connections for backhaul. | 0.4.0 | +| 2019-01 | S2-130 | | | | | During S2 130:
- From S2-1901000, Addition of "described in TR 23.793 [5]" associated to ATSSS in clause 5.7.1.
- From S2-1901067, Addition of new key issue #8 addressing distribution of content towards the edge has been added
- From S2-1901068, Addition of Solution #4.
- From S2-1901069, Addition of Solution #5 | 0.5.0 | +| 2019-04 | S2-131 | | | | | During S2 131:
- From S2-1902443, Addition of new Key issue #9 on multilink with satellite.
- From S2-1902883, Addition of Solution #6 on Key Issue #8: Role of satellite backhaul in content distribution towards the edge
- From S2-1902445, Addition of clarification for solution #3 allowing to resolve two Editor's notes on the use of the PCF
- From S2-1902446, Addition of Solution #7 on Idle mode mobility procedure for non-geostationary satellite access. | 0.6.0 | +| 2019-05 | S2-132 | | | | | During S2 132
- From S2-1903920, Key Issue #1 update
- From S2-1904022, Update to solution 4
- From S2-1904023, Solution evaluation of new RAT type: 'NR Sat Access' | 0.7.0 | +| 2019-05 | S2-133 | | | | | During S2 133:
- From S2-1906810, Update to solution #3.
- From S2-1906118, Update and evaluation of Solution #5. | 0.8.0 | +| 2019-07 | S2-134 | | | | | During S2 134:
- From S2-1907373; Clause 3 update
- From S2-1908363; Solution for support of gNBs on NGSO satellites
- From S2-1908364; Global evaluation for Key Issue #5
- From S2-1908369; evaluation and conclusion for Key Issue #8
- From S2-1908447; Update of RAT Type solution
- From S2-1908554; Idle mode mobility for Non-GEO satellite access | 0.9.0 | + +| | | | | | | | | +|-------------------------|-----------------------|---------------------------|---|---|---|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------| +| | | | | | | - From S2-1908555; Update of Solution #2: Addition of New RAT type satellite
- From S2-1908556; New solution - Distributed gNB for non-GEO constellations
- From S2-1908557; evaluation and conclusion for Key Issue #7 | | +| 2019-08 | SP#85 | SP-190632 | - | - | - | MCC editorial update for presentation to TSG SA#85 | 1.0.0 | +| 2019-10 | S2-135 | | | | | During S2 135:
- From S2-1910472: Reference update
- From S2-1910648: Satellite access is 3GPP access
- From S2-1910653: New Key Issue: Regulatory Services with Super-national Satellite Ground Station
- From S2-1910649: Solution 1 - Resolution of ENs and evaluation
- From S2-1909445: Solution 2 LCS update
- From S2-1909792: Solution#2 - Removal of EN on effect of newRAT type on NEF
- From S2-1909483: Update of Solution #3
- From S2-1910477: Removal of time sync EN in Solution 7
- From S2-1910481: Removal of location procedures EN in Solution 7
- From S2-1910652: Evaluation of Solution #6 for using satellite backhaul in content distribution towards the edge
- From S2-1910478: Evaluation for Solution #7 for key issue #2
- From S2-1910482: EN Resolution and solution evaluation for solution 8
- From S2-1909789: Solution#9 - Resolution of EN on ISL effect on newRAT types
- From S2-1910480: Update of Solution#9 and resolution of ENs
- From S2-1910484rev1: Evaluation of Solution#9 - Distributed gNB for NGSO Satellites
- From S2-1910485: Solution: NAS Timers management for Satellite Access
- From S2-1910526rev1: Combined solution for key issue 5
- From S2-1909435: evaluation of Key Issue #4 solutions
- From S2-1909480: Update of evaluation of solutions for Key Issue #5
- From S2-1909325: Conclusions for key issue 7
- From S2-1910650: Conclusion on solutions for Key Issue #8- From S2-1910651: Evaluation of Key Issue #2 solutions
- From S2-1910527: Conclusion for Key Issue #5.
Updated the structure of the TR consistently with the approved documents. | 1.1.0 | +| 2019-12 | S2-136 | | | | | During S2-136:
- From S2-1912152: Abbreviations update.
- From S2-1912559: Evaluation of Solutions and Conclusions for KI#1.
- From S2-1911467: Update to evaluation of KI #2.
- From S2-1912034: Removal of EN in clause 6.8.2 (KI 2).
- From S2-1912530: Evaluation and Conclusion for Solution to KI#3 in TR 23.737.
- From S2-1912543: Update of Solution #10 .
- From S2-1912038: Solution for Key Issue #4 and Key Issue #5 on QoS with satellite access and backhaul.
- From S2-1912039: Evaluation of KI #4 conclusions.
- From S2-1911726: Editorial Change in Solution#11.
- From S2-1912040: Proposed updates to solution #11 to align with AF session set up to request QoS.
- From S2-1912041: Removal of EN in clause 6.5.1 (KI 5).
- From S2-1912147: Update of solution evaluation and conclusion for KI #7.
- From S2-1912531: Evaluation of solutions for KI #9.
- From S2-1912532: Conclusion on solutions for KI #9.
- From S2-1912523: New solution for the PLMN selection part of Key Issue #10.
- From S2-1912524: Virtual Cell Solution for Mobility and Regulatory Support for Satellite Access in 5G.
- From S2-1912777: - Evaluation of KI #2 conclusions
- From S2-1912525: Evaluation of Solutions and Conclusions for KI#10.
From S2-1912151: Removal of EN in Annex A, clause A.5. | 1.2.0 | + +# **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on architecture aspects for using satellite access in 5G (Release 16)** + + + +--- + +The 5G logo consists of the text "5G" in a bold, black, sans-serif font. To the right of the text is a green graphic element consisting of three curved, wave-like lines of increasing height, representing a signal or connectivity. + +5G logo + + + +The 3GPP logo features the letters "3GPP" in a stylized, bold, black font. The "3" and "G" are connected at the top by a single horizontal line. Below the "P" is a red graphic element consisting of three curved, wave-like lines of increasing height, similar to the 5G logo. Below the logo, the text "A GLOBAL INITIATIVE" is written in a smaller, all-caps, sans-serif font. + +3GPP logo + +## --- **Keywords** + +--- + +3GPP, 5G, Architecture, Latency, Mobility + +## **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** + +--- + +
If PCF is used. | +| Changes to UPF needed | Yes | No | Maybe | UPF needs to send information on QoS Limitation to the SMF, if UPF information is available | +| Changes to N4 protocol/interface needed | Yes | No | Maybe | If UPF information is available. | +| Changes to SBI between AMF and SMF needed | No | Yes | Maybe | SBI = Service Based Interface, i.e. it refers to the SBA clients and servers that make use of the SBA architecture, e.g. AMF as SBA client and SMF as SBA server
If AMF information is available. | +| Changes to SBI between SMF and PCF needed | Yes | Yes | Maybe | SBI = Service Based Interface, i.e. it refers to the SBA clients and servers that make use of the SBA architecture, e.g. SMF as SBA client and PCF as SBA server.
If PCF is used. | + +Candidate Solution #14 addresses completely Key Issue #5 and provides a solution for the mobility aspects related to the use of satellite for backhaul.. + +## 7.6 Evaluation of solutions for Key Issue #6 - RAN mobility with NGSO regenerative-based satellite access + +See Key Issue #1. + +## 7.7 Evaluation of solutions for Key Issue #7 - Multi connectivity with satellite access + +The satellite access is considered as a 3GPP access in SA2, a single registered UE cannot simultaneously establish multiple PDU sessions via different 3GPP RATs. Therefore, the multiple PDU sessions scenario described in KI #7 will not occur, and no solutions are needed. + +Dual-connectivity via satellite RAN and terrestrial RAN is a RAN issue, and RAN has conducted related study, thus SA2 should just follow RAN conclusion. + +## 7.8 Evaluation of solutions for Key Issue #8 - The role of satellite link in content distribution towards the edge + +This clause provides evaluation of Candidate Solutions for Key Issue #7. + +A unique Candidate Solution has been proposed: + +- Candidate Solution #6 - Role of satellite backhaul in content distribution towards the edge. Two approaches are proposed within Solution 6: + - Approach #A: Uplink classifier based Approach: This approach proposes to use UL CL standardized in TS 23.501 [6] clause 5.6.4.2 and TS 23.502 [3] clause 4.3.5.4. A UPF supporting UL CL is selected and diverts the traffic which matches with traffic filters provided by SMF. This solution should prevent the satellite link from multiple content transmissions. However, this approach implies having a permanent PDU session between the UE and the remote DN, and thus having a satellite link always loaded because of the resource allocation to each PDU session till their release + - Approach #B- Multi-homing: A multi-homed approach defined in TS 23.501 [6] clause 5.6.4.2 and TS 23.502 [3] clause 4.3.5.4 can also be appropriate. The PDU session is associated to multiple IPv6 prefix and a UPF supporting the Branching Point functionality is configured by SMF. The Branching Point provides traffic forwarding toward the PDU session anchors. Thus, one anchor can route the traffic toward a local DN and the other toward the remote DN. + +The evaluation of both approaches indicates that they are based on existing specifications and should not have any impact on existing specifications. + +## 7.9 Evaluation of solutions for Key Issue #9 – Multi connectivity with hybrid satellite/terrestrial backhaul + +Topics listed in KI#9 are out of scope of this study. Accordingly no solutions are proposed for this KI. + +## 7.10 Evaluation of solutions for Key Issue #10 - Regulatory services with super-national satellite ground station + +For Key Issue #10 - " Key Issue #10: Regulatory services with super-national satellite ground station ". This Key Issue identifies the following aspects that need to be solved for super-national cell coverage area. + +Two candidate solutions have been proposed. + +Candidate Solution #12 “Solution 12: Satellite cells for 5G satellite access with large or moving radio coverage”. This solution introduces the definition and usage of Satellite cells and the support needed from UEs and sNBs. In a first approach, Satellite Cells are defined as Virtual Cells, whilst in a second approach satellite cells are defined as standard cells in association with the use of geographical zones that are sent by the network to the UE and stored with UEs. In both cases the main assumption is that the UE has access to its position. This Candidate Solution answers to a) to f) above. It is understood that charging and tariff notifications (items g) could be possible based on serving Satellite cells and/or Satellite TAs. + +Solution #13” Country specific PLMN selection” Country specific PLMN selection” allows the UE uses its awareness of its location. If the UE is aware of its location, it can use this knowledge to select among the PLMNs of the country of the present UE location. It can also trigger the UE to change PLMN when it changes country. If the UE is not aware of its location within certain country, Solution 13 allows the network to enforce the UE registration to PLMNs of the country of the UE location by rejecting the registration attempt to PLMN of another country and giving the UE a hint of which MCC PLMNs to attempt instead. Solution #13 answers to items a – d) of this Key Issue. In addition, the same solution helps to solve also item e) as well by ensuring that the UE is registered to a PLMN of the same country as the present UE location. + +# --- 8 Conclusions + +## 8.1 Conclusion on solutions for Key Issue #1 + +Solution #1 does not require any modification of the existing 3GPP specifications for the 5G-CN. Depending on its implementation it could require modifications for NG-RAN for UE location. Evaluation of the RAN aspects are within RAN groups' scope. + +Solution #12 needs further evaluation and may need further work in SA2 but has so far been found fulfil KI#1, but with a different set of properties and impacts to the 5GSUE, RAN and 5G-CN. So far, no show stoppers have been found from SA2 related aspects. As RAN dependencies have been identified in both solution #1 and solution #12, RAN groups need to evaluate these solutions. + +Whether Solution #1 and/or Solution #12 can proceed to normative work is conditional on the feedback from RAN groups. + +NOTE: the same conclusion is agreed for Key Issue #6. + +## 8.2 Conclusion on solutions for Key Issue #2 + +Key Issue #2 studied Mobility Management with moving satellite coverage area. 3GPP system should adapt to being usable over variety of satellite types without putting pre-requisite conditions on the capabilities of the satellites, or the satellite constellation to be used. The system impact on 3GPP system depends on what kind of satellites are used, and therefore, the following conclusions are made. + +Both Solutions #1 and #9 have been identified as having no impacts on the existing 3GPP specifications of the 5G-CN. It is thus concluded that no normative work is needed in SA2 for these solutions. Feedback and evaluation of these solutions has also been requested to the RAN Working Group. + +Solutions #7 and #8 have both impacts on the 5G-CN. Dependency with respect to Moving Tracking Areas in the case of Satellite based RAN has been identified for these solutions. Before concluding on the normative work for Solution #7 or Solution #8, input from RAN WGs is needed, e.g. if Moving Tracking Areas would be selected as a basis for normative activity during Rel. 17. + +## 8.3 Conclusion on solutions for Key Issue #3 + +It is concluded to take Candidate Solution #10 for normative work on this key issue. + +Key Issue #3 is for satellite delay's impact on NAS procedures. Following the evaluation in clause 6.10, no impacts are identified for LEO and MEO satellite systems for NAS timers. The Registration procedure needs to be modified for GEO satellite system to enable the AMF to indicate to the UE, when extended NAS timers are used in the current Registration Area that the UE shall use in the current Registration Area. + +## 8.4 Conclusion on solutions for Key Issue #4 + +Key Issue #4 studied QoS with satellite access. Following the evaluation in clause 7.4, it is concluded to take Candidate Solution #2 as the baseline for normative work on this Key Issue + +It is also proposed to use Candidate Solution #14 as way forward for KI#4, depending on decisions to be made by RAN groups with respect to mobility and QoS. + +## 8.5 Conclusion on solutions for Key Issue #5 + +It is proposed to use Candidate Solution #11 for the basis of normative work. + +For mobility aspects, it is proposed to use Candidate Solution #14 as way forward for KI#5, depending on decisions to be made by RAN groups with respect to mobility and QoS. + +## 8.6 Conclusion on solutions for Key Issue #6 + +Conclusions agreed for Key Issue #1 are also applicable to Key Issue #6. + +## 8.7 Conclusion on solutions for Key Issue #7 + +Key issue #7 includes study of simultaneous PDU Session multi-connectivity of a UE over terrestrial RAN and satellite-based NG-RAN. This topic is not further progressed in this study and it is concluded that no normative work is needed. + +**NOTE:** A device with two UEs may simultaneously have separate Registrations and PDU Sessions in satellite and terrestrial networks with different PLMNs. + +Key issue #7 also includes study of dual-connectivity over terrestrial RAN and satellite-based NG-RAN. This topic is more RAN related and will not be further progressed in this study. It is concluded that, for this topic, only alignment to RAN (if any) is needed in normative phase. + +## 8.8 Conclusion on solutions for Key Issue #8 + +It is concluded that Solution #6 has no impact on the 5GS architecture and thus requires no normative work. + +In order to satisfy requirements in certain geographies that indicate that the information broadcast by a satellite are receivable only within the limits of the country to which the PLMN belongs, during normative phase solutions need to be defined to restrict such broadcasting. Whether such solutions need to be defined in SA2 or RAN will be decided during normative work. + +## 8.9 Conclusion on solutions for Key Issue #9 + +As KI#9 goes beyond the scope of this study, it is concluded not to have a normative work on this Key Issue. + +## 8.10 Conclusion on solutions for Key Issue #10 + +Candidate Solution #12 and Candidate Solution #13 have been evaluated. SA2 is not aware of any issues that would prevent the feasibility of either solution. + +Both solutions have external dependencies outside of SA2. Before concluding on the normative work, SA2 requests the evaluation and guidance of RAN2 and RAN3 for Solution #12 and CT1 for Solution #13. + +# Annex A: Characteristics of satellite systems + +## A.1 General + +This annex describes the main characteristics of satellite systems when considering their integration with the 5G system. + +## A.2 Class of orbit + +On the one hand, our planet attracts as a main body the much smaller satellite, which motion is dictated as a consequence by the laws of Kepler. On the other hand, the environment of Earth can be also constraining: the higher density of the atmosphere, debris from launchers and former satellites in the lower altitudes, as well as higher energy particles trapped in the Van Allen belts between 2000 and 8000 km's altitudes are to be avoided. These two constraints contribute to defining several classes of orbits that are used for communication satellites: + +- **Geostationary (GEO)** satellites, located precisely in the plane of the Equator at an altitude of 35 786 km, these satellites rotate at the same rate as the Earth's rotation: a GEO satellite stands still with respect to Earth. Thanks to this property, a single GEO satellite is sufficient to create a continuous coverage. +- **Non-Geostationary Orbiting (NGSO)** satellites: NGSO satellites do not stand still with respect to Earth. Should service continuity be required over time, a number of satellites (a constellation) is required to meet this requirement; the lower the altitude the higher the number of satellites + +Different classes of NGSO satellites are listed below: + +- **Low-Earth Orbiting (LEO)** satellites, with altitude ranging 500 km and 2000 km, and with inclination angle of the orbital plane ranging from 0 to more than 90 degrees. These constellations are placed above the International Space Station and debris, and below the first Van Allen belt. +- **Medium-Earth Orbiting (MEO)** satellites, with altitude ranging from 8000 to 20,000 km. The inclination angle of the orbital plane ranges from 0 to more than 90 degrees. These constellations are placed above the Van Allen belts. +- **Highly-Eccentric Orbiting (HEO)** satellites, with a range of operational altitudes (the orbit of such satellites being designed for the spacecraft to be exploited when the vehicle is closer to its apogee - the higher part of the orbit -) between 7,000 km and more than 45,000 km. The inclination angle is selected so as to compensate, completely or partially, the relative motion of Earth with respect to the orbital plane, allowing the satellite to cover successively different parts of Northern land masses (e.g. Western Europe, North America, and Northern Asia). + + + +Diagram illustrating the classes of orbits of satellites around planet Earth. The diagram shows a central Earth with four orbital paths: GEO (Geostationary Orbit), MEO (Medium-Earth Orbit), LEO (Low-Earth Orbit), and HEO (Highly-Eccentric Orbit). The GEO orbit is a circular path in the equatorial plane. The MEO orbit is a circular path above the GEO orbit. The LEO orbit is a circular path below the MEO orbit. The HEO orbit is an elliptical path that is highly inclined to the equatorial plane, with its apogee (highest point) significantly higher than the GEO orbit. + +**Figure A.2-1: Illustration of the classes of orbits of satellites** + +## A.3 Geometrical coverage of satellite and propagation delay + +As depicted in the following figure, the theoretical geometrical coverage of a satellite is associated to its altitude and the minimum elevation angle under which the satellite is seen by the UE above the horizon. + + + +A diagram showing a satellite at a certain altitude above the Earth's surface. A User Equipment (UE) is shown on the Earth's surface, looking up at the satellite. The 'Satellite altitude' is indicated by a vertical line. The 'Satellite Geometrical coverage' is shown as a shaded area on the Earth's surface. The 'Elevation Angle' is the angle between the horizon and the line of sight to the satellite. The Earth is represented by a circle, and the UE is a small rectangle on its surface. + +Diagram illustrating the geometrical coverage of a satellite. + +**Figure A.3-1: Illustration of the geometrical coverage of a satellite** + +The following figure illustrates the geometrical coverage for a LEO satellite and for geostationary-satellites: + + + +A world map showing the geographical coverage of two types of satellites. The 'Geometrical coverage for a LEO satellite' is shown as a small, localized circular area over North America. The 'Geometrical coverage for a GEO satellite' is shown as a much larger, elongated circular area that covers a significant portion of the Earth's surface, including North America, South America, and parts of Europe and Africa. The map includes latitude and longitude lines. + +Map illustrating the geometrical coverage of a LEO satellite and a GEO satellite. + +**Figure A.3-2: Illustration of the geometrical coverage of a LEO satellite and of GEO satellites** + +The following tables provide elevation, distance and geometrical coverage related figures for different classes of satellites: + +| Class of orbit | Elevation angle (degrees) | | | +|----------------|-------------------------------------------------------|--------|--------| +| Altitude (km) | 0 | 10 | 90 | +| LEO | Distance - Satellite to UE (km) | | | +| 800 | 3 293 | 2 367 | 800 | +| 1400 | 4 452 | 3 480 | 1 400 | +| MEO | Distance - Satellite to UE (km) | | | +| 8000 | 12 886 | 11 826 | 8 000 | +| GEO | Distance - Satellite to UE (km) | | | +| 35786 | 41 679 | 40 586 | 35 786 | +| | | | | +| | | | | +| Class of orbit | Elevation angle (degrees) | | | +| Altitude (km) | 0 | 10 | 90 | +| LEO | Propagation Delay - Satellite to UE (millisec) | | | +| 800 | 11,0 | 7,9 | 2,7 | +| 1400 | 14,8 | 11,6 | 4,7 | +| MEO | Propagation Delay - Satellite to UE (millisec) | | | +| 8000 | 43,0 | 39,4 | 26,7 | +| GEO | Propagation Delay - Satellite to UE (millisec) | | | +| 35786 | 138,9 | 135,3 | 119,3 | +| | | | | +| | | | | +| Class of orbit | Elevation angle (degrees) | | | +| Altitude (km) | 0 | 10 | 90 | +| LEO | Geometrical Coverage Radius - (km) | | | +| 800 | 3 040 | 2 109 | - | +| 1400 | 3 887 | 2 910 | - | +| MEO | Geometrical Coverage Radius - (km) | | | +| 8000 | 7 087 | 6 022 | - | +| GEO | Geometrical Coverage Radius - (km) | | | +| 35786 | 9 050 | 7 952 | - | + +**Figure A.3-3: Geometrical coverage radius, propagation distance and delay for different orbits** + +NOTE: The above figure provides only examples, some designers may decide to select lower altitudes as this contribute lowering the propagation delay. + +The following table illustrates the number of satellites that are necessary for a constellation of satellites to provide continuous coverage for an elevation angle ranging from 5 to 10 degrees. Global coverage may not be fully achieved for MEO or GEO satellite, however in this case the vast majority of the world population is covered. + +| Class of orbit | # of satellites to cover Earth | +|----------------|--------------------------------| +| LEO | | +| 800 | circa 80 | +| 1400 | circa 50 | +| MEO | | +| 8000 | circa 10 | +| GEO | | +| 35786 | circa 3 | + +**Figure A.3-4: Illustration of number satellites in a constellation for continuous Earth coverage** + +## A.4 Type of satellite communication payloads + +Communication payloads embarked on-board satellites are of two main categories, for any type of satellite (whether GEO or NGSO): + +- **Transparent payloads:** the electromagnetic wave that are transmitted from Earth surface are converted by a satellite receive antenna into an electric signal which is channel filtered and amplified by low-noise amplifier (LNA). The signal is then frequency converted. A high power amplifier (HPA) delivers finally the signal to a + +transmitting antenna generating a reconditioned electromagnetic wave towards the Earth surface where receive station are located. + +- **Regenerative payloads:** an On-Board Processor (OBP), is inserted between the LNA and the HPA. This OBP allows converting the air interface between the uplink (from Earth to satellite) and the down link (from satellite to Earth). It allows to correct bits or packet in errors before retransmitting them, or to route packet between beams. Ultimately any network function can be implemented, as the expense of power and mass, thanks to an OBP (including gNB CU's or DU's, or any function attached to a CN). +- **Inter-Satellite Links (ISL):** can also interconnect regenerative satellite payloads. Through ISL's satellites can be interconnected through a dedicated mesh-network. + +## --- A.5 Handovers + +While a UE would stand still, hand overs from one satellite to another satellite could be imposed by the motion of NGSO satellite in a constellation, whilst GEO would stand still with respect to Earth. + +The average rate of hand over for a single UE would depend on the actual altitude of spacecrafts in a constellation. Typical values for LEO are in the order of 10 minutes. + +Not all UE's would be handed over simultaneously. + +NOTE: Such a handover mechanism is illustrated in Solutions #1 and #12 of this document. + +## --- A.6 Air interfaces + +Air interfaces can include: + +- 3GPP defined air interfaces, such as the New Radio; +- Non-3GPP defined air interfaces + +Unless otherwise indicated, 3GPP NR will be assumed in this Technical Report. + +## --- A.7 General considerations on the use of satellite networks + +In relation to the coverage associate with Non-Geostationary Satellite Networks, or Geostationary-Satellite ones, the use of satellite networks is related to: + +- The complement of terrestrial networks where these terrestrial networks are not available, permanently for physically (maritime or aeronautical constraints) or economic reasons, or for temporary reasons associated to local a unavailability of a terrestrial of network (drought, Earth quake) or local overload of the demand; +- Satellite networks can be used for broadcast over large areas of a same content, for multicast (with acknowledge of delivery of content), for unicast; +- Use cases are related to the actual of altitude of the satellite platforms and the associated delay of propagation. + +# Annex B: Architecture Models for Satellite Integration in 5GS + +## B.1 Elementary satellite network architecture + +The physical implementation of satellite network architecture can always be sketched as displayed in the following figure: + + + +Figure B.1-1: Reference Satellite Access Network Architecture. This diagram shows a 'Satellite enabled UE' (represented by a smartphone and a satellite dish) connected via a dashed 'Service link' to a 'Satellite'. The satellite is connected via a dashed 'Feeder link' to a 'Hub' (represented by a satellite dish and a server). The Hub is connected via a solid line to a 'Data Network' (represented by a cloud). + +**Figure B.1-1: Reference Satellite Access Network Architecture** + +A satellite network is always composed of: + +- One, or more, satellite(s), embarking a telecommunication payload. +- Satellite enabled UEs, such as IoT devices, broadband vehicular or fixed terminals. +- A Hub, including an RF Earth station, and a data centre including (co-located or not) RAN and CN related functions. The hub is also interconnected to (a) data network(s). +- UEs interconnected to the hub through the satellite. + +## B.2 Reference architecture with satellite enabled NR-RAN + +The following figure depicts a reference architecture for a direct access with a satellite enabled NR-RAN (see below): + + + +Figure B.2-1: 5GS with Satellite enabled NR-RAN. This diagram shows a 'UE with Satellite access' (represented by a smartphone) connected via N1 and NR interfaces to a 'Satellite enabled NR-RAN' (represented by a dashed box). The NR-RAN is connected via N1, N2, and N3 interfaces to a '5G CN' (represented by a green box). The 5G CN is connected via an N6 interface to a 'DN' (Data Network, represented by a cloud). + +**Figure B.2-1: 5GS with Satellite enabled NR-RAN** + +Knowing the possible nature of satellite payloads (transparent or re-generative), the instantiation of this architecture can have several forms: + +In a first implementation, the satellite is transparent, the NR signals are generated from gNBs from a satellite enabled NR-RAN that are located on ground. The satellite is equivalent to a Radio Frequency (RF) Remote Unit, and is full transparent to the New Radio protocols, including the physical layer (see below). + + + +Figure B.2-2: 5GS with transparent satellite enabled NR-RAN. This diagram shows a 'UE' (represented by a smartphone) connected via an NR-Uu interface to a 'Radio Frequency Remote Unit' (represented by a satellite). The RF Remote Unit is connected via another NR-Uu interface to a 'Remote Radio Unit' (represented by a satellite dish). The Remote Radio Unit is connected to a 'gNB' (represented by a server). The gNB is connected via N1/2/3 interfaces to a '5G CN' (represented by a green box). The 5G CN is connected via an N6 interface to a 'Data Network' (represented by a cloud). + +**Figure B.2-2: 5GS with transparent satellite enabled NR-RAN** + +In a second implementation, the satellite is regenerative. The satellite payload implements a gNB-DU as part of a satellite enabled NR-RAN. Some of the protocols of the NR are processed by the satellite. A Satellite Radio Interface (SRI) transports the F1 protocol between the on-ground CU and the on-board DU (it can be the NR (see below)). + + + +Figure B.2-3: 5GS with regenerative satellite enabled NR-RAN and distributed gNB. The diagram shows a User Equipment (UE) connected to a gNB-DU (satellite) via an NR-Uu interface. The gNB-DU is connected to a Remote Radio Unit (RRU) and a gNB-CU via an F1 over SRI interface. The gNB-CU is connected to a 5G CN via an N1/N2/N3 interface, which is then connected to a Data Network via an N6 interface. + +**Figure B.2-3: 5GS with regenerative satellite enabled NR-RAN and distributed gNB** + +In a third implementation, the satellite is regenerative. The satellite payload implements a full gNB supporting a satellite enabled NR-RAN. A Satellite Radio Interface (SRI) transports the N1/N2/N3 interfaces between the on-ground 5G CN and the on-board gNB-CU (see below). + + + +Figure B.2-4: 5GS with regenerative satellite enabled NR-RAN and on-board gNB. The diagram shows a User Equipment (UE) connected to a gNB (satellite) via an NR-Uu interface. The gNB is connected to a Remote Radio Unit (RRU) via an NG over SRI interface. The gNB-CU is connected to a 5G CN via an N1/N2/N3 interface, which is then connected to a Data Network via an N6 interface. + +**Figure B.2-4: 5GS with regenerative satellite enabled NR-RAN and on-board gNB** + +One can note that with a regenerative implementation (either with distributed gNB or not) a 5GS can have a global coverage, providing a single 5G CN with global or regional (continental or sub-continental) coverage as well. This is valid for GEO or LEO (see below): + + + +Figure B.2-5: 5GS with regenerative satellite enabled NR-RAN, with ISL for regional or global coverage. The diagram shows three User Equipment (UE) units connected to three separate gNB-DU (satellite) units via NR-Uu interfaces. These gNB-DU units are interconnected via F1 over SRI interfaces (ISL). The bottom gNB-DU is connected to a Remote Radio Unit (RRU) and a gNB-CU via an F1 over SRI interface. The gNB-CU is connected to a 5G CN via an N1/N2/N3 interface, which is then connected to a Data Network via an N6 interface. + +**Figure B.2-5: 5GS with regenerative satellite enabled NR-RAN, with ISL for regional or global coverage** + +Another configuration (see below) may consist in satellites each embarking a gNB supporting a satellite enabled NR-RAN, and 5G CN's accessing these gNBs, as described in the following figure, where specific (or not) satellite radio interfaces are used to handle control and user planes: + + + +The diagram illustrates a 5GS architecture with regenerative satellite enabled NR-RAN. It consists of three vertically stacked satellite units. Each unit contains a User Equipment (UE) connected to a gNB via an NR-Uu interface. The gNBs are interconnected by inter-satellite links (ISL) labeled Xn-C, Xn-U Over SRI. Each gNB is also connected to a Remote Radio Unit (RRU) via an NG over SRI interface. The RRUs are connected to a 5G Core Network (5G CN) via an NG (N1/N2/N3) interface. The 5G CNs are connected to a Data Network via an N6 interface. The diagram shows three such 5G CNs and Data Networks, one for each satellite unit. + +Diagram of 5GS with regenerative satellite enabled NR-RAN, showing three stacked satellite gNB units connected to UEs, Remote Radio Units, 5G CNs, and Data Networks via ISL and NG interfaces. + +Figure B.2-6: 5GS with regenerative satellite enabled NR-RAN, with ISL & multiple 5G CN connectivity + +# Annex C: Change history + +| Change history | | | | | | | | | +|----------------|-----------|------|----|-----|-----|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | | New version | +| 2018-07 | | | | | | TR skeleton added as approved from S2-187199 during S2-128 | | 0.0.0 | +| 2018-07 | | | | | | TR Scope added from S2-187245
Annex A (informative) added from S2-187236
Annex B (informative) added from S2-187246
Annex A "Change History" Renamed into "Annex C" | | 0.1.0 | +| 2018-08 | S2#128BIS | | | | | During S2 128#bis, addition of:
- Reference scenarios in Clause 4 from S2-188487
- Key issues #1, #2, and #3 in Clause 5 from S2-188488, S2-188489 and S2-188490 | | 0.2.0 | +| 2018-10 | S2#129 | | | | | During S2 129:
- Modification of title of clause 4.2 (addition of "assumptions")
- Addition of clause 4.3 from S2-1811139
- Addition of 2 points to be addressed on each of the Key Issues #1 & #2 from S2-1811139
- Addition of Key Issue on QoS with satellite access from S2-1811462
- Addition of Key issue on QoS Feedback from satellite backhaul from S2-1811463
- Addition of Solution #1 on Mobility Management from S2-1811540 | | 0.3.0 | +| 2019-01 | S2#129BIS | | | | | During S2 129BIS:
- Editorial modifications as approved in S2-1812036 (Key issue # 4 & #5 numbering, and Editor's note modification).
- From S2-1812776, addition of Key Issue #6 on RAN mobility with NGSO regenerative-based satellite access.
- From S2-1813212, addition of Key Issue #7 on Multi connectivity with satellite access
- From S2-1813224, Revision on Solution #1
- From S2-1812780, Addition of a New solution: new RAT type satellite
- From S2-1812781 add a solution for QoS with Satellite Backhaul by using UPF information to inform SMF about the need for QoS adaptation in case of the use of satellite connections for backhaul. | | 0.4.0 | +| 2019-01 | S2-130 | | | | | During S2 130:
- From S2-1901000, Addition of "described in TR 23.793 [5]" associated to ATSSS in clause 5.7.1.
- From S2-1901067, Addition of new key issue #8 addressing distribution of content towards the edge has been added
- From S2-1901068, Addition of Solution #4.
- From S2-1901069, Addition of Solution #5 | | 0.5.0 | +| 2019-04 | S2-131 | | | | | During S2 131:
- From S2-1902443, Addition of new Key issue #9 on multilink with satellite.
- From S2-1902883, Addition of Solution #6 on Key Issue #8: Role of satellite backhaul in content distribution towards the edge
- From S2-1902445, Addition of clarification for solution #3 allowing to resolve two Editor's notes on the use of the PCF
- From S2-1902446, Addition of Solution #7 on Idle mode mobility procedure for non-geostationary satellite access. | | 0.6.0 | +| 2019-05 | S2-132 | | | | | During S2 132
- From S2-1903920, Key Issue #1 update
- From S2-1904022, Update to solution 4
- From S2-1904023, Solution evaluation of new RAT type: 'NR Sat Access' | | 0.7.0 | +| 2019-05 | S2-133 | | | | | During S2 133:
- From S2-1906810, Update to solution #3.
- From S2-1906118, Update and evaluation of Solution #5. | | 0.8.0 | +| 2019-07 | S2-134 | | | | | During S2 134:
- From S2-1907373; Clause 3 update
- From S2-1908363; Solution for support of gNBs on NGSO satellites
- From S2-1908364; Global evaluation for Key Issue #5
- From S2-1908369; evaluation and conclusion for Key Issue #8
- From S2-1908447; Update of RAT Type solution
- From S2-1908554; Idle mode mobility for Non-GEO satellite access | | 0.9.0 | + +| | | | | | | | | +|---------|--------|-----------|---|---|---|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------| +| | | | | | |
- - From S2-1908555; Update of Solution #2: Addition of New RAT type satellite
- - From S2-1908556; New solution - Distributed gNB for non-GEO constellations
- - From S2-1908557; evaluation and conclusion for Key Issue #7
During S2 135:
- - From S2-1910472: Reference update
- - From S2-1910648: Satellite access is 3GPP access
- - From S2-1910653: New Key Issue: Regulatory Services with Super-national Satellite Ground Station
- - From S2-1910649: Solution 1 - Resolution of ENs and evaluation
- - From S2-1909445: Solution 2 LCS update
- - From S2-1909792: Solution#2 - Removal of EN on effect of newRAT type on NEF
- - From S2-1909483: Update of Solution #3
- - From S2-1910477: Removal of time sync EN in Solution 7
- - From S2-1910481: Removal of location procedures EN in Solution 7
- - From S2-1910652: Evaluation of Solution #6 for using satellite backhaul in content distribution towards the edge
- - From S2-1910478: Evaluation for Solution #7 for key issue #2
- - From S2-1910482: EN Resolution and solution evaluation for solution 8
- - From S2-1909789: Solution#9 - Resolution of EN on ISL effect on newRAT types
- - From S2-1910480: Update of Solution#9 and resolution of ENs
- - From S2-1910484rev1: Evaluation of Solution#9 - Distributed gNB for NGSO Satellites
- - From S2-1910485: Solution: NAS Timers management for Satellite Access
- - From S2-1910526rev1: Combined solution for key issue 5
- - From S2-1909435: evaluation of Key Issue #4 solutions
- - From S2-1909480: Update of evaluation of solutions for Key Issue #5
- - From S2-1909325: Conclusions for key issue 7
- - From S2-1910650: Conclusion on solutions for Key Issue #8- From S2-1910651: Evaluation of Key Issue #2 solutions
- - From S2-1910527: Conclusion for Key Issue #5.
Updated the structure of the TR consistently with the approved documents.
| 1.1.0 | +| 2019-11 | S2-136 | | | | |During S2-136:
- - From S2-1912152: Abbreviations update.
- - From S2-1912559: Evaluation of Solutions and Conclusions for KI#1.
- - From S2-1911467: Update to evaluation of KI #2.
- - From S2-1912034: Removal of EN in clause 6.8.2 (KI 2).
- - From S2-1912530: Evaluation and Conclusion for Solution to KI#3 in TR 23.737.
- - From S2-1912543: Update of Solution #10 .
- - From S2-1912038: Solution for Key Issue #4 and Key Issue #5 on QoS with satellite access and backhaul.
- - From S2-1912039: Evaluation of KI #4 conclusions.
- - From S2-1911726: Editorial Change in Solution#11.
- - From S2-1912040: Proposed updates to solution #11 to align with AF session set up to request QoS.
- - From S2-1912041: Removal of EN in clause 6.5.1 (KI 5).
- - From S2-1912147: Update of solution evaluation and conclusion for KI #7.
- - From S2-1912531: Evaluation of solutions for KI #9.
- - From S2-1912532: Conclusion on solutions for KI #9.
- - From S2-1912523: New solution for the PLMN selection part of Key Issue #10.
- - From S2-1912524: Virtual Cell Solution for Mobility and Regulatory Support for Satellite Access in 5G.
- - From S2-1912777: - Evaluation of KI #2 conclusions
- - From S2-1912525: Evaluation of Solutions and Conclusions for KI#10.
- - From S2-1912151: Removal of EN in Annex A, clause A.5 .
Application IDs"
Location ID = "all TA" | +| | No error | Total count of successful requests | .... | +| | UE Identification causes | Total count per error group | | +| | Subscription causes | Total count per error group | | +| | Congestion network failure causes | Total count per error group | | +| | Invalid message causes | Total count per error group | | + +The following table provides an example of CDIs for the UE CM state and UE RM state. + +**Table 6.6.1.9-2: Illustration of predefined CDIs example for the UE CM state and UE RM state** + +| Status | Status values | List of proposed CDIs | Scoping CDI parameter | +|----------|---------------|------------------------------------|---------------------------------------------------------------| +| RM state | REGISTERED | Total count of UE with this status | Access ID = " All "
Application ID = "all Application IDs" | +| | DEREGISTERED | Total count of UE with this status | Access ID = " All "
Application ID = "all Application IDs" | +| CM state | IDLE | Total count of UE with this status | Access ID = " All "
Application ID = "all Application IDs" | +| | CONNECTED | Total count of UE with this status | Access ID = " All "
Application ID = "all Application IDs" | + +#### 6.6.1.10 Procedure for Interactions with 5GC NFs for update of Data Collection Subscription to 5GC NFs + + + +A sequence diagram showing interactions between an NF (Network Function) and an NWDAF. The NF is on the left and the NWDAF is on the right. The sequence of messages is: 1. Nnf\_DataCollectionService\_Update() from NWDAF to NF (solid line with arrow), and 2. Nnf\_DataCollectionService\_Notify() from NF to NWDAF (dashed line with arrow). + +Sequence diagram for 5GC NF interactions + +**Figure 6.6.1.10-1: Procedure for Interactions with 5GC NFs for update of Data Collection Subscription to 5GC NFs** + +1. To update the subscription to NFs data, the NWDAF invokes an Nnf\_DataCollectionService\_Update service operation from the 5GC NFs with the subscription ID, newly requested subscription duration, new time frame for measurement, optionally new sampling interval, and the newly requested period between two notifications as described in clause 6.6.1.2. The 5GC NFs respond to the request service operation with the indication of success or failure of the subscription update request. + +**Editor's note:** The update of subscription for the other parameters (i.e., CDI scope, etc.) is FFS. + +2. To report the data from 5G NFs when it is available to be collected, the 5GC NFs invoke an Nnf\_DataCollectionService\_Notify service operation to notify NWDAF with the requested CDI(s) according to revised time interval. + +**NOTE:** If the 5GC NFs such as UPF are not allowed to access the NWDAF through the service based interface, the NWDAF may indirectly interact with the UPF through the SMF, respectively. + +#### 6.6.1.11 Procedure Interactions with AFs for update of Data Collection Subscription to AF + + + +A sequence diagram showing interactions between an AF (Application Function), an NEF (Network Exposure Function), and an NWDAF. The AF is on the left, the NEF is in the middle, and the NWDAF is on the right. The sequence of messages is: 1. Naf\_DataCollectionService\_Update() from NWDAF to AF (solid line with arrow, passing through the NEF), and 2. Naf\_DataCollectionService\_Notify() from AF to NWDAF (dashed line with arrow, passing through the NEF). + +Sequence diagram for AF interactions + +**Figure 6.6.1.11-1: Procedure for Interactions with AFs for update of Data Collection Subscription to AF** + +1. To update of subscription for data to be collected from AF, the NWDAF invokes a Naf\_DataCollectionService\_Update service operation from AF with the subscription ID, newly requested subscription duration, new time frame for measurement, optionally new sampling interval, and the newly requested period between two notifications as described in clause 6.6.1.2. The AF responds the request service operation with the indication of success or failure of the subscription update request. + +**NOTE 1:** The update of subscription for the other parameters (i.e., CDI scope, etc.) is left for the normative phase. + +2. To report the data to be collected from AF when it is available to be collected, the AF invokes a Naf\_DataCollectionService\_Notify service operation to notify NWDAF with the requested CDI(s) according to revised time interval. + +NOTE 2: If the AF is not allowed by the operator to access directly the NF(s) as specified in clause 6.2.10, TS 23.501 [2], the service operations in step 1-2 should use the NEF to interact between the AF and the NWDAF. + +NOTE 3: The exact definition of alternatives for data transfer from AF through NEF is left for the normative phase. + +## 6.6.2 Impacts on Existing Nodes and Functionality + +The solution requires the implementation of a new interface on CN NFs for data collection. + +It is clearly oriented towards the collection of data that allows spacial (i.e., in specific regions of the network slice) and temporal aspects of data that can be collected from NFs. + +## 6.6.3 Solution Evaluation + +This solution allows both the collection of data related to individual UEs and the collection of statistical data related to multiple UEs. + +This solution adds a mechanism in addition to the existing ones based OAM and Rel-15 event exposure. + +The solution enables data collection from any NF and AF, for any use case. The solution enables to collect data with a fine grain scoping level (e.g. UE groups, TAI), either aggregated or detailed. + +Techniques are described to facilitate the definition of metrics (see clause 6.6.1.9). + +In order to reduce computation effort on NWDAF and data volume, each NF or AF can provide the NWDAF with pre-processed analytics (metrics) instead of raw events. The solution encourages Collectable Data Items to be standardized. In order to encourage a fruitful data ecosystem, it may also be possible for an implementation to propose specific metrics to the community. + +## 6.7 Solution 7: Customizing mobility management based on NWDAF output + +### 6.7.1 Description + +This is a solution to Key Issue#9: Customizing mobility management based on NWDAF output. + +There are customization of mobility management Use Cases that are done in an offline fashion with low signalling frequency. There are other Use Cases that are done more in an online fashion with higher signalling frequency. The Solution below describes how associated analytics is used to support all Use Cases that can be performed by a 5GS NF independently. + + + +``` + +sequenceDiagram + participant AMF + participant NWDAF + participant NRF + Note right of NWDAF: 1. Register (Event-ID) + NWDAF->>NRF: 1. Register (Event-ID) + Note left of AMF: 2. Discover NWDAF (Event-ID) + AMF->>NRF: 2. Discover NWDAF (Event-ID) + Note left of AMF: 3. EventSubscription Subscribe (Event-ID) + AMF->>NWDAF: 3. EventSubscription Subscribe (Event-ID) + Note right of NWDAF: 4. NWDAF performs analytics, input data is retrieved from AMF. + Note left of AMF: 5. EventSubscription Notify (Event-ID, value) + NWDAF->>AMF: 5. EventSubscription Notify (Event-ID, value) + +``` + +Sequence diagram showing the interaction between AMF, NWDAF, and NRF for customizing mobility management with associated analytics. The sequence is: 1. NWDAF registers Event-ID with NRF; 2. AMF discovers NWDAF using Event-ID; 3. AMF subscribes to NWDAF Event-ID; 4. NWDAF performs analytics (input data from AMF); 5. NWDAF notifies AMF with Event-ID and value. + +**Figure 6.7.1-1: Customizing mobility management with associated analytics** + +Figure 6.7.1-1 shows a NWDAF instance that is associated with AMF and provides analytics for customized mobility management. + +1. First the NWDAF instance registers in NRF the Event-ID it supports (e.g. "UE expected geographical movement"). +2. AMF discovers the NWDAF instance that supports a specific Event-ID (e.g. "UE expected geographical movement"). +3. AMF subscribes to NWDAF Event-ID. +4. NWDAF carries out analytics to determine the "UE expected geographical movement". + +NOTE: AMF obtains input data using existing procedures in TS 23.502 [3]. How the input data is collected by NWDAF will follow the conclusions on key issue #3 + +5. NWDAF sends a notification to AMF including the Event-ID and the analytics value for the "UE expected geographical movement". + +The NWDAF instance providing "UE expected geographical movement" can be collocated with AMF, then NRF registration and discovery are not needed. In this case the NWDAF may provide analytics to AMF via internal interfaces. + +Alternatively, AMF may have locally configured the NWDAF instance that provides "UE expected geographical movement", then discovery via NRF may not be needed. + +## 6.7.2 Impacts on Existing Nodes and Functionality + +**NWDAF:** NWDAF needs to register the Event-ID with NRF. + +**NF:** A NF exposes network analytics, using existing Event Exposure framework, that needs to include new Event Ids. The NF also needs to discover the associated NWDAF instance using the Event-ID. + +**NRF:** Needs to include the Event-ID in the NWDAF register and discovery processes. + +## 6.7.3 Solution Evaluation + +By using an associated analytic solution: + +- The signalling and network load are lowered. + +- The delay is minimized. + +## 6.8 Solution 8: Performance improvement and supervision of mIoT terminals + +### 6.8.1 Description + +This solution is for Key Issue 8: Performance improvement and supervision of mIoT terminals. + +#### 6.8.1.1 Information for the support of Performance improvement and supervision of mIoT terminals + +The UE behavioural information from 5GC NFs for performance improvement and supervision of mIoT terminals is defined in Table 6.8.1.1-1. + +**Table 6.8.1.1-1: UE behavioural information collected from 5GC NF(s)** + +| Information | Presence | Source | Description | +|-----------------------------------|----------|---------|----------------------------------------------------------------------------------------------------------------| +| UE ID | M | AMF/SMF | Could be e.g. SUPI, which is used by NWDAF to correlate the UE behavioural information from different 5GC NFs. | +| Location info | | | | +| >Timestamp | O | AMF | The timing for the UE | +| >Location | O | AMF | The location info for the UE e.g. Cell ID or TA ID | +| Communication Pattern Info | | | | +| >Communication start time | O | SMF | Start time when the UE is available for communication | +| >Communication end time | O | SMF | End time when the UE is unavailable for communication | +| Network Configuration Info | | | | +| >UL or DL Packet Latency | O | SMF | Indicating the delay for uplink or downlink packets transfers for the UE | + +#### 6.8.1.2 Procedure for expected UE behavioural information provisioning + +Based on large amount of UE behavioural information from 5GC NF(s) corresponding to UEs in a SUPI list, NWDAF could clusters the UEs into one or more UE groups, where each UE group has an expected UE behavioural information, as defined in Table 6.8.1.2-1. + +**Table 6.8.1.2-1: Expected UE behavioural information for a UE group provided by the NWDAF** + +| Information | Presence | Description | +|--------------------------------------|----------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| Stationary indication | O | Identifies whether the UE is stationary or mobile, e.g. only on demand. (TS 23.682 [5], clause 5.10.1). | +| UE Moving Trajectory | O | Identifies the UE's expected geographical movement (TS 23.502 [3], clause 4.15.6).
Example: A planned path of movement | +| Periodic communication indicator | O | Identifies whether the UE communicates periodically or not, e.g. only on demand. (TS 23.682 [5], clause 5.10.1). | +| Communication duration time | O | Duration interval time of periodic communication (may be used together with 1) (TS 23.682 [5], clause 5.10.1).
Example: 5 minutes | +| Periodic time | O | Interval Time of periodic communication (may be used together with 1) (TS 23.682 [5], clause 5.10.1).
Example: every hour | +| Scheduled communication time | O | Time zone and Day of the week when the UE is available for communication (TS 23.682 [5], clause 5.10.1).
Example: Time: 13:00-20:00, Day: Monday | +| Maximum Latency | O | Indicating maximum delay acceptable for downlink data transfers (TS 23.682 [5], clause 4.5.21). | +| Maximum Response Time | O | Indicating the time for which the UE stays reachable to allow the AF to reliably deliver the required downlink data (TS 23.682 [5], clause 4.5.21). | +| Suggested Number of Downlink Packets | O | Indicating the number of packets that the UPF shall buffer in case the UE is not reachable (TS 23.682 [5], clause 4.5.21). | + + + +``` +sequenceDiagram + participant 5GC NFs + participant UDM + participant NWDAF + Note right of UDM: 1. Nnwdaf_EventsSubscription_Subscribe (SUPI List) + UDM->>NWDAF: 1. Nnwdaf_EventsSubscription_Subscribe (SUPI List) + NWDAF-->>UDM: + Note left of NWDAF: 2a. UE behavioral information + 5GC NFs->>NWDAF: 2a. UE behavioral information + Note right of NWDAF: 2b. NWDAF offline clusters the UE behavior information into one or more UE groups in which each UE group has an expected UE behavioral information + Note right of UDM: 3. Nnwdaf_EventsSubscription_Notify (List of expected UE behavioral info) + NWDAF-->>UDM: 3. Nnwdaf_EventsSubscription_Notify (List of expected UE behavioral info) +``` + +The diagram illustrates a sequence of interactions between three network functions: 5GC NFs, UDM, and NWDAF. The sequence begins with the UDM sending a '1. Nnwdaf\_EventsSubscription\_Subscribe (SUPI List)' message to the NWDAF. The NWDAF responds with a return message. Next, the 5GC NFs send '2a. UE behavioral information' to the NWDAF. The NWDAF then performs an internal processing step, '2b. NWDAF offline clusters the UE behavior information into one or more UE groups in which each UE group has an expected UE behavioral information'. Finally, the NWDAF sends '3. Nnwdaf\_EventsSubscription\_Notify (List of expected UE behavioral info)' to the UDM. + +Sequence diagram showing the procedure for expected UE behavioural information provisioning between 5GC NFs, UDM, and NWDAF. + +**Figure 6.8.1.2-1: Procedure for expected UE behavioural information provisioning** + +1. The UDM may subscribe expected UE behavioural information to the NWDAF by invoking Nnwdaf\_EventsSubscription\_Subscribe service operation. The input for the service operation should be: + - - Event ID. + - - Event Filter Information: SUPI List. + - - Target (list of SUPI, any UE). +2. Based on analytical result for large amount of UE behavioural information from 5GC NF(s) as defined in Table 6.8.1.1-1, NWDAF clusters the UE behavioural information into one or more UE groups in which each UE group has an expected UE behavioural information. +3. The NWDAF notifies the expected UE behavioural information as defined in Table 6.8.1.2-1 and UE group ID to the UDM by invoking the Nnwdaf\_EventsSubscription\_Notify service operation. The UDM stores the expected UE behavioural information as part of the subscription data for the corresponding UE(s). + +### 6.8.1.3 Procedure for mIoT terminals misused or hijacked Recognition + + + +``` + +sequenceDiagram + participant AMF + participant SMF + participant UDM + participant PCF + participant NWDAF + participant AF + + Note right of UDM: 0. Expected UE behavioral information provisioning + UDM->>NWDAF: + Note left of AMF: 1a. Nudm_SDM_Notification +(AMF specific Expected UE behavioral information) + UDM->>AMF: + Note left of SMF: 1b. Nudm_SDM_Notification +(SMF specific Expected UE behavioral information) + UDM->>SMF: + Note right of AMF: 2. Determination and Notification of behavioral Exception UE + AMF->>NWDAF: + Note right of NWDAF: 3. Determine the Exception UE +list are misused or hijacked or +a new terminal type + NWDAF-->>AF: + Note right of AF: 4. Exception Notification + AF->>NWDAF: + Note left of AMF: 5. Performing UE subscription / policy modification + AMF->>UDM: + AMF->>PCF: + +``` + +Sequence diagram illustrating the procedure for Massive UE are misused or hijacked Recognition. The diagram shows interactions between AMF, SMF, UDM, PCF, NWDAF, and AF. The steps are: 0. Expected UE behavioral information provisioning (UDM to NWDAF); 1a. Nudm\_SDM\_Notification (AMF specific) (UDM to AMF); 1b. Nudm\_SDM\_Notification (SMF specific) (UDM to SMF); 2. Determination and Notification of behavioral Exception UE (AMF to NWDAF); 3. Determine the Exception UE list are misused or hijacked or a new terminal type (NWDAF internal); 4. Exception Notification (NWDAF to AF); 5. Performing UE subscription / policy modification (AMF to UDM/PCF). + +**Figure 6.8.1.3-1: Procedure for Massive UE are misused or hijacked Recognition** + +0. As specified in clause 6.8.1.2-1, the NWDAF provides the expected UE behavioural information as defined in Table 6.8.1.2-1 for each UE to the UDM. Considering the received expected UE behavioural information, the UDM may store the expected UE behavioural information as part of the subscription data for the corresponding UE. This contains also NWDAF subscription onto NF(s) about the Event ID = Deviation from UE behaviour. +1. UDM/UDR notifies the updated subscriber data i.e. the expected UE behavioural information and UE group ID to the corresponding 5GC NFs (e.g. AMF, SMF). +2. During a UE communicates with the 5GC, NF e.g. AMF, the NF determines whether the UE's behavioural information matches its expected UE behavioural information, if not, the UE is regarded as an exception UE, then the NF should notify the NWDAF per the subscription received in step 1. +3. The NWDAF may perform further data analysis on certain UE exception UE behavioural information and find that does not match the expected UE behavioural information, then abnormal behaviour could be expected e.g. be UE misused or hijacked. +4. Based on analytical result, the NWDAF notifies exception UE ID list, corresponding Exception ID, corresponding Exception level to the AF according to the subscription to such notification. Based on these information, the AF may adjust e.g. recommended TCP Window Size, recommended Service Start and End time(e.g. for background data transfer), etc. For the untrusted AFs, the message can be send via the NEF. +- 5.1. According to the subscription to such notification, the NWDAF notifies exception UE ID list, corresponding Exception ID and Exception level to the relevant UDM/UDR. Taking these received information into account, the UDM/UDR may further update the UE subscription information, e.g. Supported SSC mode, default SSC mode, Subscribed S-NSSAI and periodic registration update timer. UE subscription change is sent to the registered NF (Serving AMF, serving SMF). +- 5.2. According to the subscription to such notification, the NWDAF notifies exception UE ID list, corresponding Exception ID and Exception level to the relevant PCF(s). Taking these received information into account, the PCF(s) may create or update the UE policy accordingly. + +## 6.8.2 Impacts on Existing Nodes and Functionality + +Editor's note: Capture impacts on existing 3GPP nodes and functional elements. + +## 6.8.3 Solution Evaluation + +Editor's note: Use this clause for evaluation at solution level. + +# 6.9 Solution 9: Recommendations produced by NWDAF + +## 6.9.1 Description + +### 6.9.1.1 Service principles + +This solution addresses Key issue #1: "Network Data Analytics feedback". + +The NWDAF offers a Recommendations service in order to propose recommendations (parameter values) to NFs. + +This solution extends the objective of the SID which is for the NWDAF to provide statistics and predictions. + +The use of the Recommendations service by an NF is optional. The recommendation service shall not assume application knowledge and configuration in the NWDAF. + +The purpose of the service is to better assist some NFs in the elaboration of its strategy, in certain use cases. + +Each NF may request the NWDAF Recommendations service for instance in case its decision may impact other NFs behaviours. + +Each type of recommendation belongs to a given domain (e.g. registration, reachability, mobility, service and application, forwarding, routing, roaming, security, resilience). There may different types of recommendations per domain. + +The NWDAF apart from providing statistical/prediction information, shall not intervene in the area of responsibility of each NF, which shall remain solely responsible for its decisions. The NFs may additionally coordinate their decisions with other NFs. + +After receiving a recommendation that the NF has requested, the NF shall then, according to its own criteria (for example applicative and business criteria) and its own service logic, make its optimal choice within its area of responsibility. + +The NF consumers of the NWDAF Recommendations service are fully in charge of all decisions concerning their own tuning. As a consequence, they should be able to operate with good performance in most situations, even in case of NWDAF absence or failure. + +The NWDAF should strive to ensure consistency in its recommendations, taking into account the previous recommendations performed across the different domains and the other NFs, in order to avoid conflicted decisions. + +### 6.9.1.2 Service definition + +The NWDAF should expose a generic service interface NWDAF\_RecommendationsService offering the following operations. + +**Table 6.9.1.2-1** + +| Operations | Description of each operation of the Recommendations Service | +|-------------|--------------------------------------------------------------| +| Subscribe | Subscription to recommendations | +| Unsubscribe | Cancel of a previous subscription | +| Notify | Notification of recommendations to the consumer NF | +| Request | Request to recommendations | + +The Recommendations service proposes pre-computed vectors of optimal parameter recommended values to NFs. + +A parameter recommended value is a single value or a range, for possible integration in the rules of the consumer NF. + +Each consumer NF shall provide in input, for a given type of recommendation, the target objects that are related to the parameter recommend values that will be derived. The NF may impose computational constraints (e.g. ranges of parameters to explore) on the results. + +The NWDAF in return shall provide, for each requested recommendation, a list of one or more suggested parameter combinations. For instance, these combinations can be lists of candidate QoS dedicated parameters, or lists of candidate UPFs for selection. + +Each combination is a vector of recommended parameter values, possibly with associated impacts (predicted KPIs) and a preference order, consistent between different domains. + +### 6.9.1.3 Recommendations Subscribe/Unsubscribe + +This procedure is used by any NF service consumer to subscribe/unsubscribe at NWDAF and to be notified of recommendation information. + + + +``` +sequenceDiagram + participant NF Service Consumer + participant NWDAF + Note right of NF Service Consumer: 1. Nnwdaf_Recommendations_Subscribe/ +Nnwdaf_Recommendations_Unsubscribe + NF Service Consumer->>NWDAF: Request + Note left of NWDAF: 2. Nnwdaf_Recommendations_Notify + NWDAF-->>NF Service Consumer: Notification +``` + +The diagram illustrates a sequence of interactions between an NF Service Consumer and the NWDAF. The consumer sends a message labeled '1. Nnwdaf\_Recommendations\_Subscribe/Nnwdaf\_Recommendations\_Unsubscribe' to the NWDAF. The NWDAF responds with a message labeled '2. Nnwdaf\_Recommendations\_Notify' back to the consumer. The return message is shown with a dashed line. + +Sequence diagram for NWDAF Recommendations Subscribe/Unsubscribe/Notify + +**Figure 6.9.1.3-1: NWDAF Recommendations Subscribe/Unsubscribe/Notify** + +1. The NF service consumer subscribes to or cancels subscription to recommendations by invoking the Nnwdaf\_Recommendations\_Subscribe or Nnwdaf\_Recommendations\_Unsubscribe service operation. +2. If NF service consumer has subscribed to recommendations, the NWDAF notifies the NF service consumer with the recommendations by invoking Nnwdaf\_Recommendations\_Notify service operation. + +### 6.9.1.4 Recommendations Request + +This procedure is used by the NF service consumer (e.g. UDM, AMF, SMF, PCF) to request and get from NWDAF recommendations, using Nnwdaf\_Recommendations\_Request. + + + +``` +sequenceDiagram + participant NF Service Consumer + participant NWDAF + Note right of NF Service Consumer: 1. Nnwdaf_Recommendations_Request + NF Service Consumer->>NWDAF: Request + Note left of NWDAF: 2. Nnwdaf_Recommendations_Response + NWDAF-->>NF Service Consumer: Response +``` + +The diagram illustrates a sequence of interactions between an NF Service Consumer and the NWDAF. The consumer sends a message labeled '1. Nnwdaf\_Recommendations\_Request' to the NWDAF. The NWDAF responds with a message labeled '2. Nnwdaf\_Recommendations\_Response' back to the consumer. The return message is shown with a dashed line. + +Sequence diagram for NWDAF Recommendations Request and Response + +**Figure 6.9.1.4-1: NWDAF Recommendations Request and Response** + +1. The NF service consumer requests recommendations by invoking Nnwdaf\_Recommendations\_Request service operation. +2. The NWDAF responds with recommendations to the NF service consumer. + +### 6.9.1.5 Contents of subscribe and request operations + +In addition to basic SBI parameters defined in TS 29.520 [10], the requests or the subscription should contain: + +- The desired recommendation on a given domain, expressed as a recRequirement object. + +- Observation period [start..end] in the future on which recommendations are requested. +- Maximum tolerable delay for the provision of the recommendations. +- Event parameters for periodic notification (as defined in Solution#1), +- Optional preferences on recommendations (as defined in Solution#1).. +- Target of Event Reporting (TER), Event Filtering Information (EFI) and Denotation of Explicit Lists (as defined in Solution #1). + +A recRequirement object is composed of: + +- the recommendation registered ID in the given domain. +- optional optimization goals: this parameter denotes the objectives of optimization requested, if several optimizations methods are possible. Several simultaneous objectives may be requested and hierachized. The requesting NF should use these goals parameters in order to fit its own strategy. +- optional constraints per requested parameter, expressed as parameter ranges. These constraints may be used by NFs to guide recommendations by passing UE up-to-date subscription profile values. + +### 6.9.1.6 Contents of notifications and responses + +In addition to the basic SBI parameters defined in TS 29.520 [10], the response to Request or the notification should contain: + +- Identification of the Request /Subscribe operation. +- Optional confidence score on recommendations. +- Possible limitations on the observation period and requested delay. +- Recommendations: candidate recommendations relevant for the observation period, expressed as an array of elementary recommendation objects recResult. + +Each recResult is a composed of: + +- Reference to the recommendation registered ID in the recommendation domain. +- The vector of tagged parameter recommended values or value ranges. +- Optionally: the associated impacts (a set of predicted analytics) if such parameters are chosen. +- Optionally: a preference order in order to suggest a preference among the various recResult objects. + +A recommended parameter may belong to the following categories. + +**Table 6.9.1.6-1** + +| Parameters categories | Example of parameters | +|-----------------------|------------------------------------------------------------------------| +| Time | Periodic registration timer, back-off timers | +| QoS | QoS profiles | +| NF | Identification of proposed UPF | +| Load ratio | Load reduction ratio, load balancing ratio | +| UEs | Identification of UEs suspected of performing a security attack | +| Location | List of relevant TA for the UE e.g. for paging or mobility restriction | +| Activity | Handover/No handover, blacklist UEs | + +Each parameter should have a clearly defined semantic and format, and should typically be defined in a 3GPP standard. + +NOTE: The exact definition of parameter types is to be defined by other solutions. + +The NWDAF may return an error if the parameters (in immediate response to subscription or request), or the traffic conditions do not permit to deliver relevant recommendations in due time. It may also return, in case of error, + +limitations of requested observation period and tolerable delay. It may also return, in case of coordination between different recommendations, the action it should take to use the response (wait a delay, wait for an event of another domain, etc.). + +## 6.9.2 Impacts on Existing Nodes and Functionality + +The solution requires the implementation of a new service on the NWDAF. + +## 6.9.3 Solution Evaluation + +This solution extends the objective of the SID which is for the NWDAF to provide statistics and predictions. + +In addition to solutions providing statistics and predictions, this solution allows to go one step further by allowing the NFs delegate some calculation of optimal parameters to the NWDAF, while remaining responsible for the final choices they make according to their own application logic. For instance, it can facilitate the decisions related to QoS provisioning (see Solution #3) and adjustment, or NF selection. + +The arrays of recommendations provided by the NWDAF are only support data for NF decision. These recommendations are based on computational analysis guided by NF specific constrains (considering that NF knowledge and logic shall not be replicated in NWDAF), enabling the NWDAF to provide processed data. For instance, the NF may choose a solution of secondary preference order in the array, for reasons relevant to the NF logic. The NF may also simply ignore all recommendations, for the same reason. + +Solution #1 provides statistics and predictions, while Solution #9 provides recommendations. Both are compatible, which means that a consumer NF may request a prediction, and then, knowing the results, decide to obtain recommendations on a subset of possible options. + +The solution #9 requires additional study on several aspects: + +- NF logic in the NWDAF; +- expression of associated impacts (response parameter as described in clause 6.9.1.6); +- possibility of subscribing simultaneously to multiple recommendations; +- consistency of recommendations. + +## 6.10 Solution 10:
The UE in idle mode may monitor and report the number of out-of-coverage entries (i.e. loosing service) per defined time. There may be cases when the UE loses service in low coverage areas which is not noticeable by the network if the UE is back to service before the next periodic update timer expires (when the UE is due to trigger a periodic update with the network).
The information about the number of out-of-coverage service entries without change of the registration area, excluding those due to rejection from the network, may indicate problems like UE often being in no or low coverage area (i.e. loosing service) for short periods of time. This information may be notified to the network operator or Service Provider (e.g. AF). The 3GPP network operator may improve the radio coverage conditions in general or at the locations where the UEs loose service.
| + +NOTE: SA WG2 to enquire with RAN WG2 and SA WG5 on whether any of the above listed UE analytics information is already available via the MDT or is to be made available within an ongoing SI/WI in these groups so that a duplications is avoided. + +Editor's note: Identify what triggers the UE to send a Terminal Analytics Update message. + +Editor's note: Identify whether the Terminal Analytics Update is sent via new or existing messages. + +## 6.16.2 Impacts on Existing Nodes and Functionality + +- UE, AMF and NWDAF: + - - New procedure to be defined to share Terminal Analytics via already available interfaces to 5GC. +- NWDAF: + - - New functionality at NWDAF to combine NW analytics with Terminal Analytics. + +## 6.16.3 Solution Evaluation + +Editor's note: Use this clause for evaluation at solution level. + +# 6.17 Solution 17: Trace based solution to collect UE related information in NWDAF + +## 6.17.1 Description + +This is a solution to Key Issue#13: UE Driven Analysis. + +### 6.17.1.1 NWDAF subscribes the trace events to TCE + +A new interface between NWDAF and TCE is supported to collect trace recording information. + +Figure 6.17.1-1 specified the Trace event subscribe procedure. NWDAF subscribes the trace events to the TCE with SUPI. The Trace events subscribe procedure can be applied to single UE or multiple UE. + + + +Sequence diagram for Figure 6.17.1-1: Trace event subscribe procedure. It shows two lifelines, NWDAF and EM. A solid arrow points from NWDAF to EM, representing the subscription request. A return arrow points from EM back to NWDAF. + +Figure 6.17.1-1: Trace event subscribe procedure + +Editor's note: The details of trace event in Trace events subscribe request is FFS. + +### 6.17.1.2 NWDAF triggers trace procedure + +A new interface between NWDAF and Management System is supported to exposure the Trace event request from NWDAF. + +NWDAF collects UE based information by triggering the Trace procedure in EM as specified in Figure 6.17.1-2. + + + +Sequence diagram for Figure 6.17.1-2: NWDAF triggers trace procedure. Lifelines include NWDAF, EM, NG-RAN, TCE/OAM, and UE. The sequence starts with NWDAF sending a request to EM. EM then sends a message to NG-RAN. NG-RAN interacts with TCE/OAM and UE. Finally, NG-RAN sends a response back to EM, which then responds to NWDAF. + +Figure 6.17.1-2: NWDAF triggers trace procedure + +1. NWDAF sends the Trace request message to Management System. The one or more SUPI and requested Trace event are included in this request message. + +Editor's note: The details of Trace event in the Trace request message is FFS. + +Steps 2 to be defined in TS 32.422 [20] and they are extrapolated by what is defined is defined already for E-UTRAN: + +2. EM initiates the Trace Session Activation to NG-RAN according to the request received from NWDAF. +3. NG-RAN starts the Trace session and stores MDT parameters. +4. NG-RAN performs the MDT procedure. The more details about MDT procedure and parameters are discussed in RAN WG2 and RAN WG3. NG-RAN sends the information to the TCE/OAM which received from UE. + +Editor's note: The impacts to the NG-RAN will be evaluated by RAN group. + +5. NG-RAN sends the Trace recording report to TCE/OAM. +6. f NWDAF subscribed the trace events as described in clause 6.17.1.1, TCE reports the trace events to NWDAF. + +## 6.17.2 Impacts on Existing Nodes and Functionality + +**Editor's note:** Capture impacts on existing 3GPP nodes and functional elements. + +NWDAF: + +- Support interface to Management System. +- Trigger the trace procedure to Management System. +- Support interface to TCE. +- Subscribe the trace event request in TCE. + +Management System: + +- Initiates trace procedure due to the trigger from NWDAF. + +TCE/OAM: + +- Support trace event subscribe service for NWDAF. +- Report the trace recording to NWDAF. + +## 6.17.3 Solution Evaluation + +**Editor's note:** Use this clause for evaluation at solution level. + +# 6.18 Solution 18: NWDAF assisting Future Background Data Transfer (BDT) + +## 6.18.1 Description + +This solution is for Key Issue 7: NWDAF assisting Future Background Data Transfer. + +As currently specified in clause 4.16.7 Negotiations for future background data transfer in TS 23.502 [3], H-PCF can provide one or more transfer policies for the future background data transfer based on requests from the AF. The transfer policy is generated by the H-PCF based on e.g. analytics information, the list of already agreed BDT stored in the UDR, and some other information listed in TS 23.503 [4]. The transfer policy is stored in UDR. At the time the ASP indicates that transfer of background data to the UE starts. The PCF retrieves the transfer policy and enforces it. + +It is considered that the network condition at the UE location could directly impact the transfer policy for future background data transfer provided to the ASP in particular: + +- UE Moving Trajectory. +- Network performance information such as NF available capacity of 5G NF which serves the UE. + +There are 2 variants of the solution: + +- AF knowledge of UE area: in this variant the AF provides the target area where Future Background Data Transfer is expected. This variant focuses on the fact that the AF has a better knowledge than the network on where the UE(s) should be at the expected time of the background data transfer. +- NWDAF prediction of the UE area: in this variant the AF does not provide the target area where Future Background Data Transfer is expected but the NWDAF has to determine (guess/predict) it based on: + - - the knowledge of the list of UE corresponding to the AF transfer. To avoid AF providing huge lists of UE(s) it is assumed that all these UE are configured to belong to a group and the AF only refers to the Group ID. + - - predictions on UE mobility: NWDAF derives the UE Moving Trajectory by collecting the UE level information such as location information from AMF. + +In both cases Network performance information is collected from OAM by NWDAF, possibly RAN OAM. + +### 6.18.1.1 Information to support Future Background Data Transfer + +The UE level information related to background data transfer per UE is defined in Table 6.18.1.1-1. + +This information is not needed in case of AF knowledge of UE area. + +**Table 6.18.1.1-1: NWDAF input data** + +| Information | Presence | Source | Description | +|---------------------------------|----------|--------|-----------------------------------------------------------| +| UE ID or Internal group Id | C | | Present if NWDAF requests location information | +| Location info | | | | +| >Timestamp | C | AMF | The age of the information | +| >Location Info | C | AMF | The location info for the UE e.g. Cell ID or TA ID | +| Network performance info | | | | +| Area information | C | OAM | Present if NWDAF requests network performance information | +| Load information | C | | Statistics on load in the area. | + +NOTE Network performance information is required for a BDT policy, we need to ask and cooperate with SA WG5 which NW performance indicators are available. + +### 6.18.1.2 Procedure for Future Background Data Transfer + +Prerequisite: The PCF may subscribe to or periodically requests upon AF: + +- NWDAF prediction of the number of UEs of an ASP in an area and the expected load in that area at a certain time and date. + +## 6.18.2 Impacts on Existing Nodes and Functionality + +Editor's note: Capture impacts on existing 3GPP nodes and functional elements. + +## 6.18.3 Solution Evaluation + +Editor's note: Use this clause for evaluation at solution level. + +# 6.19 Solution 19: NWDAF/NWDAF service registration and metadata exposure to NFs + +## 6.19.1 Description + +This is an extension of Solution #1 to describe the following aspects of Key Issue #1: Analytic Information Exposure to 5GS NF: + +- How the NWDAF provides/updates the available analytic information metadata to the 5GS NF (or subset of relevant analytic information metadata). + +Metadata refers a set of descriptive data on the analytic information provided by the NWDAF such as list of available analytic information, metrics, calculation algorithms, sampling rate etc, although the most relevant metadata is the available analytic information that will allow a NF to select a NWDAF instance that supports an analytic information (e.g. UE expected trajectory) while other metadata such as supported metrics, calculation algorithms or sampling rate are considered not needed in the context of the use cases defined in this TR so far and as such not used any longer in this description. + +The proposal uses the Event ID as one example of the required analytics metadata information, but this proposal is generic for any metadata and therefore can be extended when other metadata is required though the Event ID is the only example so far. + +The Registration and Discovery of a NWDAF instance/NWDAF service that supports analytics metadata of a specific analytic type is described below. Note that according to TS 23.502 [3], procedures to update the supported analytics are available although not mentioned here. + +#### 6.19.1.1 Registration of NWDAF/NWDAF service into the NRF + +This procedure extends the NF service Registration described in TS 23.502 [3], to include specific service parameters for NWDAF, i.e. analytics type. + + + +``` + +sequenceDiagram + participant NWDAF + participant NRF + Note right of NRF: 2. Store NF profile + NWDAF->>NRF: 1.Nnrf_NFManagement_NFRegister_request + NRF-->>NWDAF: 3. Nnrf_NFManagement_NFRegister_response + +``` + +Sequence diagram for NWDAF/NWDAF Service Registration. The diagram shows two lifelines: NWDAF and NRF. The sequence of messages is: 1. NWDAF sends Nnrf\_NFManagement\_NFRegister\_request to NRF. 2. NRF performs an internal action 'Store NF profile'. 3. NRF sends Nnrf\_NFManagement\_NFRegister\_response back to NWDAF. + +**Figure 6.19.1.1-1: NWDAF/NWDAF Service Registration** + +1. An NWDAF instance sends Nnrf\_NFManagement\_NFRegister Request message (the NWDAF profile) to NRF to inform the NRF of its NF profile when the NWDAF becomes operative for the first time. The NWDAF includes NF type: "NWDAF", FQDN or IP address of NWDAF, Names of supported NWDAF services, Endpoint information of instance(s) of each supported service and other service parameter. The other service parameters are the analytics metadata information, e.g. type of analytics that the NWDAF instance supports. In solution #1 this type of analytics is identified by an EventId. If some of the Events may be used by NFs that are not in the same domain as NWDAF then the NWDAF profile includes this information. +2. The NRF stores the NWDAF profile, as described in TS 23.502 [3]. +3. The NRF acknowledge NWDAF Registration is accepted via Nnrf\_NFManagement\_NFRegister response, as described in TS 23.502 [3]. + +#### 6.19.1.2 NWDAF/NWDAF service discovery + +This procedure extends the NF/NF service discovery described in TS 23.502 [3], to include discovery of a NWDAF instance supporting specific service parameters, e.g. analytics type. Note that if an AF discovers a NWDAF instance supporting specific analytic type, then the same procedure will be invoked by NEF if AF is external or by the AF itself if it is an NF. + + + +``` + +sequenceDiagram + participant ANY NF consuming NWDAF services + participant NRF + Note right of NRF: 2. Authorize NWDAF Service Discovery + ANY NF consuming NWDAF services->>NRF: 1. Nnrf_NFDiscovery_Request + NRF-->>ANY NF consuming NWDAF services: 3. Nnrf_NFDiscovery_Request Response + +``` + +Sequence diagram for NWDAF/NWDAF Service Discovery. The diagram shows two lifelines: ANY NF consuming NWDAF services and NRF. The sequence of messages is: 1. ANY NF consuming NWDAF services sends Nnrf\_NFDiscovery\_Request to NRF. 2. NRF performs an internal action 'Authorize NWDAF Service Discovery'. 3. NRF sends Nnrf\_NFDiscovery\_Request Response back to ANY NF consuming NWDAF services. + +**Figure 6.19.1.2-1: NWDAF/NWDAF Service Discovery** + +1. The NF service consumer intends to discover analytics services available in the network based on service name and target NF type "NWDAF", invokes Nnrf\_NFDiscovery\_Request (Nnwdaf\_EventSubscription/Nnwdaf\_AnalyticsInfo, NWDAF, NF type of the NF consumer). The parameter includes the requested analytics type, identified by an EventId. +2. The NRF authorizes the Nnrf\_NFDiscovery\_Request as described in TS 23.502 [3], +3. If allowed, the NRF determines the discovered NWDAF instance(s) or Nnwdaf\_EventSubscription or Nnwdaf\_AnalyticsInfo service instance(s) and provides the information of a set of discovered NWDAF instance(s) or NWDAF service instance(s) to the NF service consumer via Nnrf\_NFDiscovery\_Request Response message. as described in TS 23.502 [3]. + +## 6.19.2 Impacts on Existing Nodes and Functionality + +NWDAF: NWDAF registration to NRF following NF/NF Service Framework defined in TS 23.501 [2] for any NF, extended to provide the analytics metadata information (e.g. analytic type, identified by an EventID) in the Nnrf\_NFRegistration\_Request. + +During discovery, if the target NF is a NWDAF then if the fields related to analytics metadata information (e.g., Event ID) are used in the request, the NRF shall provide the corresponding NWDAF instance(s) that supports the fields related to the analytics metadata information. Otherwise, if fields related to analytics metadata information (e.g., Event ID) are not provided in the request, the NRF shall return all applicable NWDAF instance(s) supporting the requested Nnwdaf service(s). + +NF service consumer, needs to provide the requested analytics in metadata information, when using Nnrf\_NFDiscovery\_Request. + +## 6.19.3 Solution Evaluation + +This solution has minor impacts on the NF/NF service discovery framework, that only needs to include the analytics metadata information in service parameter. + +The solution proposes a smooth evolution from Rel-15 functionality. + +# 6.20 Solution 20: NWDAF analytics usage for UPF selection + +## 6.20.1 Description + +### 6.20.1.1 General + +This is a solution to Key Issue #6: NWDAF assisting traffic routing. + +For UPF selection, SMF is considering different parameters, among which the UE location information and the UPF dynamic load. UPF selection can be enhanced with NWDAF functionality. For example, SMF can use mobility information for the UE, such as analytics but also predictions. SMF can also consider UPFs load predictions coming from NWDAF. + +### 6.20.1.2 Procedures + +The procedure is based on SMF using NWDAF outputs. Current description reuses mechanisms as proposed in solution #1 for SMF to retrieve analytics from NWDAF, but any framework solution adopted for key issue #1: Analytic Information Exposure to 5GS NF can be reused. + +In this procedure, the SMF only has to contact the NWDAF once for UE mobility information and the UPF load. + + + +``` + +sequenceDiagram + participant SMF + participant NRF + participant AMF + participant NWDAF + + Note left of SMF: 3. UPF selection is needed + + SMF->>NWDAF: 1.Nnwdaf_EventSubscription_Request (target UPFs, load information) + NWDAF-->>SMF: 2.Nnwdaf_EventSubscription_Response (UPFs load information) + + SMF->>NWDAF: 4.Nnwdaf_AnalyticsInfo_Request (target UE, mobility information) + NWDAF-->>SMF: 5.Nnwdaf_AnalyticsInfo_Request response (target UE mobility information) + + SMF->>NRF: 6. Nnrf_Discovery_Request (NF type = UPF) + NRF-->>SMF: 7. Nnrf_NFDiscovery_Request response (list of UPFs) + + SMF->>NWDAF: 8.Nnwdaf_AnalyticsInfo_Request (target UPF(s), Load ) + NWDAF-->>SMF: 9.Nnwdaf_AnalyticsInfo_Request response (Load per UPF) + + Note left of SMF: 10. SMF performs UPF selection + +``` + +Sequence diagram illustrating UPF selection based on NWDAF outputs. The diagram shows interactions between SMF, NRF, AMF, and NWDAF. The process involves subscribing to UPF load information, requesting mobility information, discovering UPFs, and finally performing UPF selection based on analytics. + +**Figure 6.20.1.2-1: UPF selection based on NWDAF outputs** + +1. SMF subscribes towards NWDAF to be notified about UPF load information, if SMF is configured with the list of UPFs. +2. NWDAF accepts the subscription and provides already information available on UPFs load, which can be statistics (e.g. which NWDAF could get from e.g. OAM) or predictions. +3. During PDU session establishment, UPF selection is needed. +4. SMF request NWDAF for mobility information for the UE, e.g. analytics or predictions or both. +5. NWDAF returns UE mobility information to the SMF. The information is based on e.g. information which NWDAF retrieved previously from other NFs such as AMF. +6. If SMF needs to discover the UPF as defined in TS 23.501 [2]. +7. The result of the discovery is provided to SMF. If SMF already has stored the load per UPF steps 8 and 9 are skipped. +8. SMF request NWDAF to provide load per UPF(s). +9. NWDAF provides the load for the UPF(s), both based on historical information and predictions. +10. SMF selects the target UPF using information listed in TS 23.501 [2] for UPF selection and the analytics information provided by NWDAF, both statistics and predictions in UPF load and in UE mobility. + +## 6.20.2 Impacts on Existing Nodes and Functionality + +Impacts to NFs: + +- SMF: Support UPF selection with analytics information on both UE mobility and UPF load. + - - Request NWDAF for analytics on UE mobility during PDU session establishment; + +- - When SMF knows the list of UPFs (via configuration or by discovery via NRF), SMF subscribes to NWDAF or requests NWDAF to receive UPF load analytics. +- NWDAF: provide analytics on UPFs load based on e.g. information from OAM. + +## 6.20.3 Solution Evaluation + +This solution reuses the existing UPF discovery procedure defined in TS 23.501 [2] and reuses existing information and configuration in the SMF for UPF discovery. + +# 6.21 Solution 21: Supervision of IoT devices for risk precaution + +## 6.21.1 Description + +### 6.21.1.1 General + +In the key issue 8, it is mentioned that the IoT devices may be misused or hijacked, and hence brings security issues to the 3GPP system or application layer services. This solution proposes that, first, the NWDAF analysis is relied to detect the misbehaviours of IoT UE(s) and evaluate the risk brought by the misbehaviour UE(s). The NWDAF can perform analysis such as: + +- Detect out of the ordinary behaviour of a specific UE from within a group of mIoT UEs over a period of time. This can help identify a misbehaving UE, a theft of service from a UE or a hijacked UE. +- Detect out of the ordinary behaviour for set of UEs in a group within a short term to identify sudden change in behaviour that may indicate hijacking of multiple UEs, denial of service attacks, etc. + +Once the NWDAF deems that any risk brought by the misused or hijacked UEs is serious enough to notify or alert the subscribers, the NWDAF notifies the related subscribers (could be network functions or service providers) about the suspicious events or risk, so that the 3GPP system or service provider can adopt an appropriate action(s) for the risk. + +NOTE: The misused or hijacked UEs are UEs in which there are malicious applications running or UEs which have been stolen. + +### 6.21.1.2 Identifying misbehaving UE(s) + +When the network operator or IoT service provider asks the NWDAF for supervision of a specific or a group of IoT devices, the NWDAF performs data analysis on such devices based on the collected information from the application server and the 3GPP network to identify rogue behaviour for a single or multiple UEs. In order to identify misbehaving UEs, the NWDAF compare the UE runtime data with expected UE behaviours. + +NWDAF becomes aware of UE IDs belonging to a group of mIoT UEs via consulting the UDM for subscriber information. The expected behaviour for a group of mIoT UEs can be: + +- Provisioned into the UDM by the network operator based on for example its expectation about the behaviour, SLAs with IoT service providers managing groups of UEs, etc.; +- Identified by application server and provided directly to the NWDAF; or +- learned by the NWDAF itself via collection of historical data for that group. + +The following table 6.21.1.2-1 gives an example of the expected UE behaviour parameters. + +**Table 6.21.1.2-1: An example of expected UE behavioural information** + +| Information | Presence | Description | +|--------------------------------------|----------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| Stationary indication | O | Identifies whether the UE group is stationary or mobile, e.g. only on demand. (TS 23.682 [5], clause 5.10.1). | +| Periodic communication indicator | O | Identifies whether the UE group communicates periodically or not, e.g. only on demand. (TS 23.682 [5], clause 5.10.1). | +| Communication duration time | O | Duration interval time of periodic communication (may be used together with 1) (TS 23.682 [5], clause 5.10.1).Example: 5 minutes | +| Periodic time | O | Interval Time of periodic communication (may be used together with 1) (TS 23.682 [5], clause 5.10.1).
Example: every hour | +| Scheduled communication time | O | Time zone and Day of the week when the UE is available for communication (TS 23.682 [5], clause 5.10.1).
Example: Time: 13:00-20:00, Day: Monday | +| Maximum Latency | O | Indicating maximum delay acceptable for downlink data transfers (TS 23.682 [5], clause 4.5.21). | +| Maximum Response Time | O | Indicating the time for which the UE stays reachable to allow the AF to reliably deliver the required downlink data (TS 23.682 [5], clause 4.5.21). | +| Suggested Number of Downlink Packets | O | Indicating the number of packets that the UPF shall buffer in case the UE is not reachable (TS 23.682 [5], clause 4.5.21). | + +In order to collect some runtime data like UE current location, data rate etc., the NWDAF may request the 3GPP network to start monitoring the UE states, i.e. the NWDAF sends monitoring request to the NFs to collect the required network data, e.g., as reported by monitoring events listed in table 6.21.1.2-2. + +The information for the support of Performance improvement and supervision of mIoT terminals could also additionally be the information listed in Table 6.8.1.1-1. + +**Table 6.21.1.2-2: Examples of monitoring events** + +| Event | Description | Which NF detects the event | +|----------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------| +| Location Reporting | As specified in the table 4.15.3.1-1 in TS 23.502 [3] | As specified in the table 4.15.3.1-1 in TS 23.502 [3] | +| Change of SUPI-PEI association | | | +| Roaming status | | | +| Communication failure | | | +| Availability after DNN failure | | | +| Number of UEs present in a geographical area | | | +| UL or DL Packet Latency | Indicating the delay for uplink or downlink packets transfers for the UE | SMF | +| UL or DL data rate | Indicating the bit rate for uplink or downlink packets transfers for the UE | SMF | +| Frequent mobility re-registration | A stationary UE may re-select between neighbor cells due to radio coverage fluctuations. This may lead to multiple re-registrations if the cells belong to different registration areas. The number of re-registrations may be an indication for abnormal behavior. | AMF | + +### 6.21.1.3 Solving the risk brought by misbehaving UE(s) + +After the NWDAF completes the data analysis and detects some UEs with serious misbehaviours, e.g. unexpected UE location, abnormal traffic pattern, wrong destination address etc., the NWDAF determines whether to notify or alert the related 5GC NFs or application layer based on the subscriptions from these 5GC NFs. + +If PCF subscribes the notification, the NWDAF sends the PCF a notification about the risk or suspicious events, which triggers the PCF to update the AM/SM policies. The NWDAF can also send the notification directly to the AMF or SMF, if the AMF or SMF subscribes the notification, so that the AMF or SMF can, based on operator policies, adopt pre-defined anti-risk mechanisms. The following table gives examples of policies and actions for risk solving. The exact policies and actions to solve specific risks depend on operator's configurations. + +**Table 6.21.1.3-1: Examples of policies and actions for risk solving** + +| Risk description | AM/SM policy | Actions of NFs | +|----------------------------|-------------------------------------------------------------------------|----------------------------------------------------------------------------------------| +| Unexpected UE location | Add the area of current UE location into mobility restriction | AMF Applies mobility restriction | +| Unexpected elephant flows | Decrease the MBR for the related QoS flow | SMF updates the QoS rule | +| Unexpected wakeup | Apply MM back-off timer to the UE | AMF applies MM back-off timer to the UE | +| Suspicion of DDoS attack | Release the PDU session and Apply SM back-off timer | SMF releases the PDU session and applies SM back-off timer | +| Wrong destination address | Update the packet filter of the related QoS flow to block the wrong SDF | SMF updates the packet filter of the related QoS flow and configures the UPF | +| Ping-ponging stationary UE | NWDAF notifies the AMF or AF (Service Provider) | AMF may adjust UE registration area.
AF (Service Provider) may adjusts UE location. | + +Based on the subscription of the application server, the NWDAF sends the notification/alert to the application server, which may trigger application layer to activate some risk precaution methods. + +### 6.21.1.4 Procedures + +The procedure of using NWDAF to identify the misbehaviour IoT devices and trigger risk precaution for such IoT devices is shown in the Figure below. + + + +A large black rectangular area covering the top portion of the page, likely representing a redacted diagram. Below it, a small portion of a sequence diagram is visible, showing a dashed line and vertical lines representing lifelines and messages. + +**Figure 6.21.1.4-1: Procedure of using NWDAF to supervise IoT devices and enable risk precaution** + +0. When an IoT UE is registering to the network, the network decides whether to subscribe risk analytic report from the NWDAF. NWDAF becomes aware of the mIoT UE group that the UE belongs to and the expected behaviour for that group based mechanisms described in clause 6.21.1.2. During the registration procedure, UDM provides the expected UE behaviour parameters together with a UE group ID to the AMF/SMF. + - 1a. The AMF/SMF serving the UE may subscribe risk analytic report from the NWDAF for a specific UE. In the subscription message, the AMF/SMF may include expected UE behaviour parameters retrieved from the UDM. + - 1b. The PCF may subscribe risk analytic report from the NWDAF for a specific UE or a group of UEs. In the subscription message, the PC may include expected UE behaviour parameters for the UE or the UE group. + - 1c. The application layer SCS/AS may subscribe the risk analytic report from the NWDAF, where the subscription message may contain expected UE behaviour parameters identified on the application layer. The subscription message can be UE specific or UE group specific. + 2. The NWDAF starts the data analysis for the UEs indicated in the subscription message. + - 3-4. The NWDAF may collect some runtime data of the UE(s) by sending monitoring request to the related NFs. The monitoring request may be sent to the NFs directly or via NEF based on operator's configuration. + 5. The 5GC NFs (e.g. AMF, SMF) send event reports to the NWDAF based on the report requirements received in the monitoring request. +- NOTE: The detailed monitoring procedures via NEF refer to clause 4.15.3 in TS 23.502 [3]. +6. The NWDAF analyses the collected data for the IoT devices, and may detect some suspicious events which may be a risk, e.g., unexpected UE location, abnormal traffic pattern, wrong destination address. Based on the risk + +type and operator policies, The NWDAF determines whether to send a notification or alert to the application layer and the 3GPP network. + +7. The notification or alert sent to the application layer indicates an exception ID, which is used by the SCS/AS to choose appropriate security precaution methods, e.g. isolating the misbehaviour UE, locking the account etc. +8. The notification or alert may be sent to the PCF, so that the PCF can promptly adjust the related AM/SM policies (e.g. as described in the Table 6.21.1.3-1) to prevent the deterioration of the security issue. +9. The updated AM/SM policies are provisioned to the AMF/SMF via PCF service Npcf\_AM/SMPolicycontrol\_Update Notify. +10. The AMF/SMF enforce the updated policies. +11. The notification or alert containing the exception ID may be sent to the related 5GC NFs directly, e.g. AMF or SMF. +12. Once the AMF or SMF receives the exception ID, based on the operator policies, it adopts appropriate actions (e.g. as described in the Table 6.21.1.3-1) to relieve the risk. + +## 6.21.2 Impacts on Existing Nodes and Functionality + +### AMF: + +- Subscribes risk report from the NWDAF; +- Collects network data and sends data report to NWDAF if collecting network data was requested; +- Determines and enforces anti-risk mechanism if receiving an Exception ID from the NWDAF. + +### SMF: + +- Subscribes risk report from the NWDAF; +- Collects network data and sends data report to NWDAF if collecting network data was requested; +- Determines and enforces anti-risk mechanism if receiving an Exception ID from the NWDAF. + +### PCF: + +- Subscribes risk report from the NWDAF; +- Defines anti-risk policies based on received Exception IDs. + +### NEF: + +- Receives monitoring request from the NWDAF and forwards monitoring report to the NWDAF if needed. + +### NWDAF: + +- Collects network data from 5G NFs and/or SCS/AS; +- Sends monitoring request to the NEF if it supports; +- Performs data analysis to identify misbehaving UEs and risks; +- Notifies 5G NFs or SCS/AS about the identified risks and related UEs based on subscriptions. + +## 6.21.3 Solution Evaluation + +This solution relies on the NWDAF to identify misbehaving UEs and the risk(s) brought by such UEs. If the NWDAF identifies any risk, based on operator's policies, it sends notification or alert to subscribers who are interested in the risk report. A risk is indicated by an Event/Exception ID, if the PCF receives the Exception ID, it may define some anti-risk policies, e.g. adjusting MM/SM policies; if the AMF/SMF receives the Exception ID, it determines the anti-risk mechanism if needed, and then enforces the anti-risk mechanism. + +This solution allows the network to automatically identify misbehaving UEs, evaluate the risk(s) brought by such UEs, and solve the risk(s), which is useful to improve the efficiency of network management and strengthen the network capability of resisting risk, especially for the network serving massive IoT devices. + +## 6.22 Solution 22: Optimizing connection management based on NWDAF output + +### 6.22.1 Description + +#### 6.22.1.1 General + +This solution would like to utilize NWDAF to predict the time window in which the UE has or doesn't have UL/DL data transmission, so that the AMF can optimize connection management. Such prediction can be specified as the UE communication pattern. In order to obtain UE communication pattern, it is necessary to let the NWDAF know the communications that UE has. + +In Rel-15, communication pattern is defined as per UE level and the 5GC has been able to understand communication pattern (called "Expected UE Behaviour parameters" in TS 23.501 [2]) which is provisioned by external party via the NEF. However, in the case of the UE simultaneously communicating with multiple application servers, it may be not easy for application layer to know that per UE communication pattern. + +In this solution, the NWDAF is expected to discover UE communication pattern to optimize connection management. The NWDAF collects the UE communication history from 3rd party Application Servers, such as the time that the UE started each communication (identified by the application server IP and UE IP), service type, and the duration of the communication etc. + +By applying data mining, the NWDAF may be able to model the UE communication pattern, and then provide the analytical result to the AMF. The analytical result for a specific UE or a group of UE may be traditional communication pattern defined in TS 23.682 [5] with following additions: + +- The time and day that the UE might start a low latency communication, e.g. Time: 8:00-9:00, Day: Monday-Friday; and/or +- The time and day that the UE might not have any communication, e.g. Time: 23:00-7:00, Day: Sunday-Friday; + +The 5GC can utilize the UE mobility information and UE communication pattern to optimize connection management for a UE: + +- If the UE communication pattern indicates that the UE has a low latency communication for a time period, the AMF may keep the UE in CM-CONNECTED mode to reduce the latency of UE obtaining the service; +- If the UE communication pattern indicates that the UE has no communication in a time period, the AMF may advise the UE to adopt power saving method, e.g. PSM or MICO; +- If the UE communication pattern indicates that the UE has frequent communications in a time period, and the UE mobility information shows that the UE stay in a same place in that time period, the AMF may keep the UE in CM-CONNECTED mode to reduce the signalling on CM state transitions but without bring frequent handover. + +#### 6.22.1.2 Procedures + +The provision of UE communication pattern and UE mobility prediction from the NWDAF to the 5GC is shown in the Figure below. + + + +Figure 6.22.1.2-1: procedure of using NWDAF out to optimize connection management. The diagram shows a sequence of interactions between a UE (User Equipment) and an AMF (Access and Management Function). The UE sends a registration request to the AMF. The AMF then sends a subscription request to the NWDAF. The NWDAF responds with a UE communication pattern and UE mobility prediction. The AMF then sends a registration accept message to the UE, which includes the time period that the power saving can be activated. The UE then responds with a registration complete message. + +**Figure 6.22.1.2-1: procedure of using NWDAF out to optimize connection management** + +1. A UE registers to the AMF. +2. The AMF subscribes analytic result on UE communication. +3. The NWDAF provides the UE communication pattern and UE mobility prediction to the AMF. +4. The AMF has received UE communication pattern, and the UE communication pattern indicates that the UE has no communication in a time period, the AMF may suggest the UE adopting power saving, and then the AMF includes the time period that the power saving can be activated in the Registration Accept message. + +NOTE: Whether to adopt power saving and which power saving method is adopted are up to UE decision. + +5. The AMF stores the received analytic results, and then optimizes connection management for the UE as described in clause 6.22.1.1. + +## 6.22.2 Impacts on Existing Nodes and Functionality + +Editor's note: Capture impacts on existing 3GPP nodes and functional elements. + +## 6.22.3 Solution Evaluation + +Editor's note: Use this section for evaluation at solution level. + +# 6.23 Solution 23: AMF using NWDAF outputs to optimize UE mobility procedures + +## 6.23.1 Description + +### 6.23.1.1 General + +This is a solution to Key Issue #9: Customizing mobility management based on NWDAF output. + +In this solution, the AMF uses UE mobility information as provided by NWDAF. Current description reuses mechanisms as proposed in solution #1 for AMF to retrieve analytics from NWDAF, but any framework solution adopted for key issue #1: Analytic Information Exposure to 5GS NF can be reused. + +The UE mobility information as provided by NWDAF can contain historical UE mobility information or predictions, or both, and can be used by AMF as an input for optimizing UE mobility, e.g. registration area determination, paging area determination. + +## 6.23.1.2 Procedures + + + +``` + +sequenceDiagram + participant UE + participant AMF + participant PCF + participant NWDAF + + Note right of NWDAF: 3. NWDAF derives requested mobility information + Note left of AMF: 6.AMF applies its own logic for Registration Area Allocation + Note left of AMF: 9.Paging is needed, AMF applies its own logic for paging area. + + UE->>AMF: 1.Registration Request + AMF->>NWDAF: 2.Nnwdaf_AnalyticsInfo_Request / Nnwdaf_EventsSubscription_Subscribe request (target UE, mobility information) + Note right of NWDAF: 3. NWDAF derives requested mobility information + NWDAF-->>AMF: 4.Nnwdaf_AnalyticsInfo_Response / Nnwdaf_EventsSubscription_Subscribe response response (UE mobility information) + AMF->>PCF: 5. AM Policy Association Establishment + Note left of AMF: 6.AMF applies its own logic for Registration Area Allocation + AMF->>UE: 7.Registration Accept (Registration Area) + Note right of NWDAF: 8.Nnwdaf_EventsSubscription_Notify (UE mobility information) + Note left of AMF: 9.Paging is needed, AMF applies its own logic for paging area. + Note left of AMF: 10. Paging + +``` + +Sequence diagram showing the interaction between UE, AMF, PCF, and NWDAF for optimizing UE mobility procedures. The sequence starts with a Registration Request from UE to AMF. AMF then sends a request to NWDAF for mobility information. NWDAF derives the information and responds. AMF then establishes an AM Policy Association with PCF. AMF applies its own logic for Registration Area Allocation and sends a Registration Accept to UE. NWDAF may send a notification to AMF. AMF applies logic for paging area and initiates paging. + +**Figure 6.23.1.2-1: AMF using NWDAF outputs to optimize UE mobility procedures** + +1. The UE initiates registration. +2. The AMF, based on local policies, requests NWDAF for mobility information for the UE, using either Nnwdaf\_AnalyticsInfo or Nnwdaf\_EventsSubscription service. The AMF can request for analytics or for predictions or for both. +3. The NWDAF derives requested mobility information for the UE. + +NOTE 1: NWDAF can derive UE mobility information based on data collected for the UE, e.g. using framework procedure that will be agreed to be progressed as part of normative work for eNA data collection. + +4. The NWDAF provide requested UE mobility information to the AMF. +5. During AM Policy Association Establishment, the PCF provides AMF with the Access and mobility related policy control information (e.g. service area restrictions). +6. The AMF derives registration area for the UE based on the UE mobility information provided by NWDAF and the service area restrictions as instructed by PCF. + +NOTE 2: The AMF logic for deriving registration area is out of scope of 3GPP. + +7. The AMF sends a Registration Accept message to the UE containing the allocated Registration Area to the UE. +8. If the AMF used Nnwdaf\_EventsSubscription service in step 2, the AMF may receive updated mobility information from NWDAF for that UE. + +9. When AMF detects that paging the UE is needed, the AMF may use the information as provided by NWDAF to determine the paging area. + +NOTE 3: The AMF logic for deriving paging area is out of scope of 3GPP. + +10. The AMF pages the UE in the area determined at step 8. + +## 6.23.2 Impacts on Existing Nodes and Functionality + +The Nnwdaf\_EventsSubscription and Nnwdaf\_AnalyticsInfo services need to be enhanced to allow provisioning of analytics or predictions or both for mobility information for a specific UE. + +## 6.23.3 Solution Evaluation + +This solution only impacts the Nnwdaf\_EventsSubscription and Nnwdaf\_AnalyticsInfo services, with the addition of UE mobility event and request for either statistics or predictions or both. + +The main difference between this solution and solution 4 resides in the non-involvement of PCF: in the present solution, PCF is not involved in any recommendation regarding registration areas or paging areas, only AMF derives registration areas and paging areas for the UE based on inputs provided by NWDAF. + +## 6.24 Solution 24: Analytics Information Exposure to AF + +### 6.24.1 Description + +This solution addresses the issues of how to expose analytics information to AF as described in Key Issue #2 (Analytic Information Exposure to AF). + +NOTE: What information could expose to AF is based on the specific use case discussion outcome. + +#### 6.24.1.1 Procedure for AF subscription to NWDAF analytics + + + +``` +sequenceDiagram + participant AF + participant NWDAF + Note right of AF: 1. Nnwdaf_EventsSubscription_Subscribe/ +Nnwdaf_EventsSubscription_Unsubscribe + AF->>NWDAF: Request + Note left of NWDAF: 2. Nnwdaf_EventsSubscription_Notify + NWDAF-->>AF: Response +``` + +Sequence diagram showing the procedure for AF subscription to NWDAF analytics. The diagram involves two participants: AF and NWDAF. Step 1 shows a solid arrow from AF to NWDAF labeled '1. Nnwdaf\_EventsSubscription\_Subscribe/ Nnwdaf\_EventsSubscription\_Unsubscribe'. Step 2 shows a dashed arrow from NWDAF back to AF labeled '2. Nnwdaf\_EventsSubscription\_Notify'. + +Figure 6.24.1.1-1: Procedure for AF subscription to NWDAF analytics + +1. AF invokes the Nnwdaf\_EventsSubscription Subscribe operation for subscribing to NWDAF analytics or Nnwdaf\_EventsSubscription Unsubscribe operation to unsubscribe for NWDAF notifications. +2. NWDAF uses the Nnwdaf\_EventsSubscription Notify operation to expose the analytics information that AF subscribed to receive. + +The interaction between AF and NWDAF is direct if the AF is located inside operator network or the interaction is done via the NEF if the AF belongs to 3rd party as follows. + + + +``` + +sequenceDiagram + participant AF + participant NEF + participant NWDAF + AF->>NEF: Request + NEF->>NWDAF: Request + NWDAF-->>NEF: Response + NEF-->>AF: Response + +``` + +Sequence diagram illustrating the procedure for AF subscription to NWDAF analytics. The diagram shows three lifelines: AF (Application Function), NEF (Network Exposure Function), and NWDAF (Network Data Analytics Function). The sequence of messages is: 1. AF sends a solid arrow message to NEF. 2. NEF sends a solid arrow message to NWDAF. 3. NWDAF sends a dashed return arrow message to NEF. 4. NEF sends a dashed return arrow message to AF. + +**Figure 6.24.1.1-2: Procedure for AF subscription to NWDAF analytics (for AF not allowed for direct access to NWDAF)** + +1. The AF subscribes to or cancels subscription to analytic information via NEF by invoking the Nnef\_EventExposure\_Subscribe/ Nnef\_EventExposure\_Unsubscribe service operation. If the analytic information event subscription is authorized by the NEF, the NEF records the association of the event trigger and the requester identity. +2. Based on the request from the AF, the NEF subscribes to or cancels subscription to analytic information by invoking the Nnwdaf\_EventsSubscription\_Subscribe/ Nnwdaf\_EventsSubscription\_Unsubscribe service operation. In the subscription to NWDAF analytics, NEF may apply restrictions to the subscription request to NWDAF (e.g., restrictions to parameters or parameter values from Nnwdaf\_EventSubscription\_Subscribe service operations) based on operator configuration. +3. If the NEF subscribes to analytic information, the NWDAF notifies the NEF with the analytic information by invoking Nnwdaf\_EventsSubscription\_Notify service operation. +4. If the NEF receives the notification from the NWDAF, the NEF notifies the AF with the analytic information by invoking Nnef\_EventExposure\_Notify service operation. + +NOTE: The call flows only show a subscription-notify model for the simplicity instead of both request-response model and subscription-notification model. + +## 6.24.2 Impacts on Existing Nodes and Functionality + +NEF: The NEF needs to be enhanced to handle the analytics information exposure between NWDAF and AF. + +## 6.24.3 Solution Evaluation + +This solution is required in particular to provide NWDAF analytics exposure to AFs allowed to access the NWDAF and for 3rd Party AFs. + +# 6.25 Solution 25: Exposure with bulk subscription and NWDAF collecting data from UDR + +## 6.25.1 Description + +### 6.25.1.1 General + +This is a solution to Key Issue #3: Interactions with 5GS NFs/AFs for Data Collection. + +This solution reuses exposure with bulk subscription as defined in Rel-15 in TS 23.502 [3] clause 4.15.3.2.4, combined with the feature that NWDAF retrieves collected data from UDR directly via existing Nudr services. + +**Editor's note:** Whether the solution can be translated into a solution with NWDAF doing bulk subscription directly to Event Exposure services from 5GC NFs, or to a solution with NFs reporting directly to NWDAF after NEF subscribed to NF events on behalf of NWDAF, is FFS. + +## 6.25.1.2 Procedures + + + +``` + +sequenceDiagram + participant AnyNF1 as Any NF (e.g. AMF, SMF) + participant NRF + participant NEF + participant UDR + participant NWDAF1 as NWDAF 1 + participant NWDAF2 as NWDAF 2 + participant AnyNF2 as Any NF + + Note left of AnyNF1: Event triggers + NEF->>NRF: 1. Nnrf_NFManagement_NFStatusSubscribe + AnyNF1->>NRF: 2. Nnrf_NFManagement_NFRegister request + NRF-->>AnyNF1: 3. Nnrf_NFManagement_NFRegister response + NRF->>NEF: 4. Nnrf_NFManagement_NFStatusNotify + NWDAF1->>UDR: 5. Nudr_DM_Subscribe + NEF->>AnyNF1: 6. Namf_EventExposure_Subscribe + Note left of AnyNF1: Event triggers + AnyNF1->>NEF: 7. Namf_EventExposure_Notify + NEF->>UDR: 7a. Nudr_DM_Create/Update + AnyNF1->>NEF: 8. Namf_EventExposure_Notify + NEF->>UDR: 8a. Nudr_DM_Create/Update + UDR->>NWDAF1: 9. Nudr_DM_Notify + AnyNF2->>NWDAF1: 10. Nnwdaf_AnalyticsInfo_Request request + NWDAF1->>UDR: 11a. Nudr_DM_Query request + UDR-->>NWDAF1: 11b. Nudr_DM_Query response + NWDAF1->>AnyNF2: 12. Nnwdaf_AnalyticsInfo_Request response + NWDAF1->>UDR: 13a. Nudr_DM_Query request + UDR-->>NWDAF1: 13b. Nudr_DM_Query response + +``` + +Sequence diagram illustrating the exposure with bulk subscription and NWDAF collecting data from UDR. Lifelines: Any NF (e.g. AMF, SMF), NRF, NEF, UDR, NWDAF 1, NWDAF 2, Any NF. The sequence shows registration, subscription, event triggers, data updates, notifications, and analytics requests. + +Figure 6.25.1.2-1: Exposure with bulk subscription and NWDAF collecting data from UDR + +1. NEF registers with the NRF for any newly registered NF along with its NF services. +2. When an NF instantiates, it registers itself along with the supported NF services with the NRF. +3. NRF acknowledges the registration. +4. NRF notifies the NEF with the newly registered NF along with the supported NF services. +5. NWDAF 1 subscribes to notification to data modified in the UDR. The events can be changes on existing data, addition of data. The events can be related to specific data subset(s), either for a single UE, group of UE(s) (e.g. identifying a certain type of UEs such as IoT UEs) or any UE. +6. NEF evaluates the NF and NF services supported against the pre-configured events within NEF. Based on that, NEF subscribes with the corresponding NF either for a single UE, group of UE(s) (e.g. identifying a certain type of UEs such as IoT UEs), any UE. NF acknowledges the subscription with the NEF. +- 7-8. When the event trigger happens, NF notifies the requested information towards the subscribing NEF along with the time stamp. NEF stores the information in the UDR along with the time stamp using either Nudr\_DM\_Create or Nudr\_DM\_Update service operation as appropriate. UDR shall maintain history for information, i.e. UDR shall not erase similar type of information which was stored earlier. +9. If step 5 was performed by NWDAF 1, the update of UDR in previous step triggers a notification towards NWDAF 1. +10. Any NF can request analytics information to NWDAF 1. + +11. NWDAF 1 directly interrogates UDR for any relevant data needed to build analytics as requested in step 10. The request can be for specific data, or related to specific data subsets, either for a single UE, group of UE(s) or any UE. NWDAF 1 may also specify a time period in the request, in which case the answer from UDR will contain the requested information for timestamps belonging to the requested time period. +12. Based on data received in step 11b, NWDAF 1 can build analytics and provide them to the requesting NF. +- 13a-b. NWDAF 2 may also query UDR for some data to provide analytics or predictions to other NFs. + +## 6.25.2 Impacts on Existing Nodes and Functionality + +UDR stores the history of the various events received, which allows multiple NWDAFs in the PLMN to access the data. + +NWDAF is a consumer of Nudr\_DM service (query, subscribe, unsubscribe and notify service operations). + +Nudr\_DM service operations enhanced to allow query and subscription for a group of UEs or for any UEs. + +Nudr\_DM\_Query service enhanced to add a time or period parameter as key for the query. If no value is provided, regular Rel-15 behaviour applies, i.e. UDR will provide the last value stored. + +## 6.25.3 Solution Evaluation + +**Editor's note:** Use this clause for evaluation at solution level. + +## 6.26 Solution 26: Data Collection using NRF services + +### 6.26.1 Description + +#### 6.26.1.1 Service definition + +This solution addresses the Key Issue #3: "Interactions with 5GS NFs/AFs for Data Collection", and the various use cases which identify the need to obtain load information and sometimes locality (e.g. Use cases #3: "NWDA-Assisted Traffic Handling", #4: "Using NWDA output to customize mobility management"; #5: "NWDA-assisted Determination of Policy"). The NWDAF uses the NRF services (see TS 29.510 [21]) in order to discover the NFs and obtain information about the status of the discovered NFs. + +The service operation for NF discovery is Request from the Nnrf\_NFDiscovery service. The service operations for obtaining status information are NFStatusSubscribe and NFStatusNotify, from the Nnrf\_NFManagement service. + +The information provided by the NRF to the NWDAF with the Nnrf\_NFDiscovery\_Request and the Nnrf\_NFManagement\_NFStatusNotify operations are the NFProfile and the NFService. Most information elements are static and can be used for all purposes in order to set-up and maintain a consistent network map for data collection. Other dynamic information elements can be used by the NWDAF, depending on use cases, in order to perform estimations: + +- NF profile: NF capacity, NF load information, NF status, NF recovery time, NF locality. +- NF service: service capacity, service load information, service status, service recovery time. + +### 6.26.2 Impacts on Existing Nodes and Functionality + +NFs: Provide the relevant information (NF capacity, NF load information, NF status, NF recovery time, NF locality) to NRF. + +NWDAF: No impacts on the existing NWDAF interface. + +NRF: No impact. + +### 6.26.3 Solution Evaluation + +This solution enables retrieving global NF static and dynamic information from all NFs. It can be used as a complement and in conjunction with other Data Collection solutions (e.g. Network Exposure services of the AMF or SMF). + +The solution is needed at least in order to obtain a consistent view of network map and status of NFs. + +## 6.27 Solution 27: NWDAF assisting Determination of Background Data Transfer Policy + +### 6.27.1 Description + +This solution is for Key Issue 7: NWDAF assisting Future Background Data Transfer. + +As specified in clause 4.16.7 Negotiations for future background data transfer, in TS 23.502 [3], PCF can provide one or more background data transfer (BDT) policies for the future background data transfer based on requests from the 3rd party. Those requests consist of the following parameters: ASP identifier, Data volume per UE, number of UEs, Desired time windows, and optionally network area information. + +To determine BDT policy, it is essential to estimate the available data volume in the network. Therefore, it is beneficial that NWDAF outputs the maximum available data volume per UE optionally network area information in consideration of number of UEs as the analytics information. It aims to assist the determination of the BDT policy in the PCF. The PCF can easily judge that the policy request from the 3rd party is acceptable, when the requested data volume is less than the maximum available data volume. + +The value of the maximum available data volume per UE depends on not only network condition, but also how many UEs connect to the network. The algorithm to calculate the maximum available data volume should be implemented in the NWDAF. This is not scope of SA WG2 work. + +This solution assumes that the operator maps ASP identifier into Internal-Group identifier described in TS 23.501 [2]. In the UDR, the operator can retrieve the UEs belonging to the particular ASP by using Internal-Group identifier. + +#### 6.27.1.1 NWDAF Data Collection + +Table 6.27.1.1-1 shows the data collected by the NWDAF in a certain interval. To output the maximum available data volume per UE in consideration of how many UEs from the ASP connect in the network, the NWDAF utilizes the following information. + +**Table 6.27.1.1-1: Data collected by NWDAF** + +| Data collected by NWDAF | Presence | Source | Description | +|-----------------------------------------------|----------|---------------|--------------------------------------------------------------------------------------------------------------------------------------------| +| Number of UEs | M | UDR | The operator estimates the number of UEs which will be requested by 3rd party in order that the NWDAF calculates the analysis information. | +| ASP identifier | O | UDR | When NWDAF outputs the analysis information per ASP, ASP identifier will be used. | +| UE ID | O | UDR, UDM, PCF | e.g., SUPI, which is used by NWDAF to correlate the information from AMF/OAM. From Internal-Group identifier, UE IDs is listed up per ASP. | +| Network area | O | AMF | The location info for the UE belonging to the particular ASP, e.g. Cell ID or TA ID | +| UE Mobility pattern | O | AMF | mobility pattern of UEs belonging to the particular ASP. | +| Network Performance information per timestamp | M | OAM | See the following editor's note | + +Editor's note: How to align NWDAF input to the solutions to get input data from NF, either via Nxx\_DataCollection or Nxxx\_EventExposure is FFS. + +### 6.27.1.2 NWDAF output + +Table 6.27.1.2-1 and 6.21.2.3-2 shows the event id and the analytics information output by the NWDAF based on the input described in Table 6.27.1.1-1. This solution assumes that Solution 1 (clause 6.1) or 2 (clause 6.2) will be used as the method of analytics information feedback. The NWDAF outputs the maximum available data volume per UE for the particular ASP based on the total number of UEs in the particular network area at the particular time. + +Editor's note: How to align NWDAF output to the combined solution 1 and 2 is FFS. + +**Table 6.27.1.2-1: Event Id to provide analytics to enhance BDT functionality** + +| Event ID | Event Filter | Description | +|----------------------------------------------|------------------------------------------------------------------|------------------------------| +| List of Maximum available data volume per UE | ASP identifier,
Number of UEs,
Network area,
Time, Date | As defined in Table 6.27.2-1 | + +**Table 6.27.1.2-2: Content of List of Maximum available data volume per UE** + +| IE/Group Name | Presence | Description | +|-----------------------------------------------------|----------|----------------------------------------------------------------------------------------------------------------------------| +| List of Maximum available data volume per UE | | | +| > IEs | | | +| >>number of UEs | M | As defined in Table 6.27.2-1 | +| >> ASP identifier | O | As defined in Table 6.27.2-1 | +| >>Maximum available data volume per UE | M | NWDAF calculates this by considering the total number of UEs, time, date, network area and network performance information | +| >>Time | O | As defined in Table 6.27.2-1 | +| >>Date | O | As defined in Table 6.27.2-1 | +| >>Network area | O | As defined in Table 6.27.2-1 | + +## 6.27.2 Impact on Existing Nodes and Functionality + +NWDAF: NWDAF service is updated from Rel-15 specification. The existing Nnwdaf interface shall be updated in order to output the parameters in Table 6.1.1.2-2. The NWDAF also needs to have the feature to collect the data described in Table 6.27.1.1-1. + +NF service consumer: the impacts are to only support receiving the new analytics requests/responses/notifications. + +There is no impact on the negotiation procedures for BDT policy described in clause 4.16.7.2 TS 23.502 [3]. + +## 6.27.3 Solution Evaluation + +Editor's note: Use this clause for evaluation at solution level. + +# 6.28 Solution 28: Exposure to AF for Background Data Transfer + +## 6.28.1 Description + +This is a solution to Use Case #5 NWDA-assisted Determination of Policy and Key Issue #2: Analytic information exposure to AF. The network condition may be changed, after the background data transfer (BDT) policy is agreed between MNO and 3rd party. We assume that there are the cases where the background data traffic may get discarded for example when the network becomes congested, then other traffic is prioritized rather than the background data traffic. + +The NWDAF collects the network performance information, and the location information for each UE belonging to the particular ASP. Then, the NWDAF predicts which UEs will experience network condition, and notifies this analysis information of the PCF. + +We propose that the NWDAF notifies the PCF that the UE of an ASP will experience congestion and then PCF determines if the BDT policy should be re-negotiated for the particular ASP. The PCF judges whether this notification should be transferred to the particular AF. When the PCF transfers this, due to this, the AF may try to negotiate with the MNO regarding the BDT policy again. The final decision is up to 3rd party. + +#### 6.28.1.1 NWDAF Data Collection + +Table 6.28.1.1-1 shows the data collected by the NWDAF in a certain interval. To predict the network performance information of the particular UEs, the NWDAF needs to take the following information into account. + +**Table 6.28.1.1-1: Data collected by NWDAF** + +| Information | Presence | Source | Description | +|---------------------------------|----------|-------------|----------------------------------------------------------------------------------| +| UE ID | M | AMF,
UDR | Could be e.g. SUPI, which is used by NWDAF to correlate the information from AMF | +| Location info | | | | +| >Timestamp | O | AMF | The timing for the UE | +| >Location Info | O | AMF | The location info for the UE e.g. Cell ID or TA ID | +| UE Mobility pattern | O | AMF | UE mobility pattern | +| Network performance info | | | | + +#### 6.28.1.2 NWDAF output + +Table 6.28.1.2-1 and 6.28.1.2-2 show the event id and the analytics information output by the NWDAF based on the input information described in Table 6.28.1.1-1. This solution assumes that Solution 1 (clause 6.1) or 2 (clause 6.2) will be used as the method of analytics information feedback. The NWDAF notifies of the PCF that the BDT policy should be re-negotiated. + +**Table 6.28.1.2-1: EventId to provide analytics to enhance BDT functionality** + +| Event ID | Event Filter | Description | +|------------------------|-------------------------------------------------|--------------------------------| +| Network Condition list | List of UE identities, Time, Date, Network area | As defined in Table 6.18.1.2-2 | + +**Table 6.28.1.2-2: Content of Network Condition List** + +| IE/Group Name | Presence | Range | Semantics description | +|--------------------------------|----------|--------|--------------------------------------------------------------------------------------------------------------| +| Network Condition list | | 1 | | +| > Network Condition IEs | | 1 to M | | +| >>list of UE IDs | M | | | +| >> Expected Moving Trajectory | M | 1 to N | UE's expected geographical movement (e.g. as described in TS 23.502 [3] clause 14.5.6.3). | +| >>Network Performance Info | | | Performance information on the NF where the UE is expected to be according to the expected moving trajectory | + +### 6.28.1.3 PCF output + +Table 6.28.1.3-1 and 6.28.1.3-2 show the event id and the output by the PCF based on the input information described in Table 6.28.1.2-1. The solution assumes to use the outcome of Key Issue #2: Analytic information exposure to AF as the interface between AF and PCF. + +**Table 6.28.1.3-1: PCF requesting the ASP to renegotiate the BDT policy** + +| Event ID | Event Filter | Description | +|--------------------|------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| BDT policy warning | ASP identifier,
Time, Date, Network area
information | PCF requests the ASP to renegotiate the BDT policy, due to potential delays in the transmission of background data. The ASP may trigger a procedure to negotiate the BDT policy with the MNO. | + +**Table 6.28.1.3-2: Content of List of BDT policy warning** + +| IE/Group Name | Presence | Description | +|-----------------------------------|----------|------------------------------------------------------------------------------------------------------------------| +| List of BDT policy warning | | | +| > IEs | | | +| >> ASP identifier | M | Identifier to identify the ASP | +| >>BDT policy reference ID | M | Reference ID of agreed BDT policy | +| >>Time | O | It indicates the time when the background data of the UEs of this ASP may be delayed due to network conditions | +| >>Date | O | It indicates the date when background data of the UEs of this ASP may be delayed due to network conditions | +| >>Network area | O | indicates the network area where background data of the UEs of this ASP may be delayed due to network conditions | +| >>UE ID | O | Indicates the list of UEs whose background data of the UEs of this ASP may be delayed due to network conditions | + +## 6.28.2 Impact on Existing Nodes and Functionality + +NWDAF: NWDAF service is updated from Rel-15 specification. The existing Nnwdaf interface shall be updated in order to output the parameters in Table 6.28.1.2-1. The NWDAF also needs to have the feature to collect the data described in Table 6.28.1.1-1 from the other NFs. + +PCF: PCF is required to support the new EventId to request NW conditions for the and have the logic to judge whether the NW conditions impact the UEs of the ASP and then a notification should be transferred to the particular AF to renegotiate a BDT. Note that the BDT feature in Rel-15 indicates to the ASP on the recommended time or date to deliver traffic to its UEs, and the rating that the MNO will apply if the ASP complies with the BDT policy. With this notification, the MNO tries to ensure that the SLA can be fulfilled with the ASP, so that the ASP needs to renegotiate the BDT policy or expect that the MNO applies a rating for traffic that may experience delays. + +AF: the impacts are to support the request to renegotiate a new BDT policy due to network conditions. + +## 6.28.3 Solution Evaluation + +The NWDAF notifies the analysis information of the PCF in the same manner with the other solutions. The PCF judges whether the NW conditions impacts on the UEs of the ASP and notifies it of the particular AF in the ASP in order to renegotiate a BDT policy. This is the new feature for the PCF. As this situation does not occur frequently, the impact on the PCF is small. + +This solution is beneficial for the MNO and ASP, because this solution helps the MNO ensure that the SLA is fulfilled with the ASP. This solution contributes to detect the situation where the quality of the communication for the UE in is bad. + +## 6.29 Solution 29: NWDAF assisted MICO mode for mIoT terminals + +### 6.29.1 Description + +This is a solution to Key Issue #8: performance improvement and supervision of mIoT terminals. + +To enhance the mIoT terminal's battery life, the proper configuration of MICO related parameters are required. The AMF decides configuration parameters for MICO mode such as 1) Allow/disallow MICO mode, 2) periodic registration timer, 3) minimal reachable time before entering MICO mode, 4) the buffering duration and size for DL packets. The NWDAF may provide analytic information to AMF by collecting and analyse network, service, management, and user data from multiple entities. + +#### 6.29.1.1 MICO mode configuration by AMF + +In the current 5GC, AMF may utilize the external parameters provisioned by external AFs such as the behavioural pattern and communication pattern. Table 6.29.1.1-1 shows the communication pattern parameters from TS 23.682 [5] , and Table 6.29.1.1-2 shows the behavioural parameters from TR 23.724 [6]. + +**Table 6.29.1.1-1: Communication Pattern Parameters** + +| CP parameter | Description | +|-------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1) Periodic communication indicator | Identifies whether the UE communicates periodically or not, e.g. only on demand. [optional] | +| 2) Communication duration time | Duration interval time of periodic communication [optional, may be used together with 1)]
Example: 5 minutes | +| 3) Periodic time | Interval Time of periodic communication [optional, may be used together with 1)]
Example: every hour | +| 4) Scheduled communication time | Time zone and Day of the week when the UE is available for communication [optional]
Example: Time: 13:00-20:00, Day: Monday | +| 5) Stationary indication | Identifies whether the UE is stationary or mobile [optional] | +| 6) Battery indication | Identifies power consumption criticality for the UE: if the UE is battery powered with not rechargeable/not replaceable battery, battery powered with rechargeable/replaceable battery, or not battery powered. [optional] | +| X) Traffic Profile | Identifies the type of data transmission: single packet transmission (UL or DL), dual packet transmission (UL with subsequent DL or DL with subsequent UL), multiple packets transmission. [optional] | + +**Table 6.29.1.1-2: The expected UE behavioural parameters** + +| Expected UE Behaviour parameter | Description | +|----------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Expected UE Moving Trajectory | Identifies the UE's expected geographical movement.
Example: A planned path of movement.
[optional] | +| Stationary Indication (see TS 23.682 [5] clause 5.10.1) | Identifies whether the UE is stationary or mobile
[optional] | +| Communication Duration Time (see TS 23.682 [5] clause 5.10.1) | Indicates for how long the UE will normally stay in CM-Connected for data transmission.
Example: 5 minutes.
[optional] | +| Periodic Time (see TS 23.682 [5] clause 5.10.1) | Interval Time of periodic communication
Example: every hour.
[optional] | +| Scheduled Communication Time (see TS 23.682 [5] clause 5.10.1) | Time and day of the week when the UE is available for communication.
Example: Time: 13:00-20:00, Day: Monday.
[optional] | +| Battery Indication (see TS 23.682 [5] clause 5.10.1) | Identifies power consumption criticality for the UE: if the UE is battery powered with not rechargeable/not replaceable battery, battery powered with rechargeable/replaceable battery, or not battery powered.
[optional] | +| Scheduled Communication Type | Indicates that the Scheduled Communication Time is Downlink only or Uplink only or Bi-directional [To be used together with Scheduled Communication Time]
Example:
[optional] | + +These parameters may be highly coupled with the decision making algorithms of AMF for MICO mode. The absence of these parameters could cause poor management of MICO mode, and also, not correctly provisioned parameters can lead not desired MICO mode behaviour for mIoT terminals. + +## 6.29.1.2 NWDAF assisted MICO mode configuration by AMF + +The NWDAF may provide the parameters, not provisioned by AFs, by analysing data collected from various sources such as NFs, OAM, AFs, and UEs. + +### 6.29.1.2.1 Input Information for external parameter estimation + +The information to be collected for the NWDAF to estimate external parameters, not provisioned by AFs. The data sources can be divided into three groups, 1) network data from the NFs, 2) service data from the AF, and 3) management data from the OAM. The network data from 5GC to collect is defined in Table 6.29.1.2.1-1. Estimating the missing external provisioned parameter is the NWDAF implementation whether it implements regression algorithms, and/or deep learning algorithms. The input of required inputs could be categorized into two groups 1) the inputs for identification of the specific target, 2) the inputs to extract the estimation from the similar past situations or the similar group of targets. + +**Table 6.29.1.2.1-1: Network Data Collection for the analysis** + +| Information | Source | Description | +|---------------------------------|------------|---------------------------------------------------------------------------------------------------------------------------------------------------| +| Location Info | AMF or SMF | The location information of the UE. | +| DNN | SMF or PCF | To identify the DNN | +| S-NSSAI | SMF or AMF | To identify the S-NSSAI for the PDU Session which contains the QoS flow | +| UE ID | AMF or SMF | To identify UE | +| Internal Group ID | SMF | To identify UE group if available | +| Traffic usage report | UPF or SMF | To extract traffic characteristics such as flow length, size, and inter packet arrival time. | +| Subscription data | UDR/UDM | To extract the specific UE related information. To extract UE's service contract, UE context, application data, UE specific policy data, and etc. | +| External provisioned parameters | UDR/UDM | To extract the provisioned external parameters such as network configuration parameters, provisioned communication and behavioural patterns. | +| NF resource status | OAM/NRF | The status of assigned resources such as CPU and memory. | +| NF load | OAM/NRF | The load of specific NFs. | +| Service experience | AF | User or service provide feedback on service experience such as MOS. | + +NOTE: The correlation of analysed traffic information per DNN, per Slice, per service, per group of UE is dependent on usage of the information. Timestamp can be used to correlate the collected data from different entities. + +#### 6.29.1.2.2 Output Information to AMF + +When the AMF not have enough parameters for MICO mode configuration, it may request to the NWDAF with event ID and event filter to obtain the necessary parameters. The NWDAF may response to the AMF request with the estimated external parameter. Optionally, the accuracy and confidence interval can be contained on the response. It provides that the confidence on the results of the NWDAF compared to the past observed data. The examples of parameters are described in Table 6.29.1.1-1 and Table 6.29.1.1-2. After receiving the output from the NWDAF, the AMF can use them for the calculation of MICO mode parameters such as: + +- 1) Allow/disallow MICO mode; +- 2) Periodic registration timer; +- 3) Minimal reachable time before entering MICO mode; +- 4) The buffering duration and size for DL packets. + +## 6.29.1.2.3 Procedure + + + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant AMF + participant SMF + participant UPF + participant AF + participant NEF + participant UDM/UDR + participant NWDAF + + Note right of NWDAF: 0. Data Collection and Analysis + UE->>NG-RAN: 1. Registration Request (MICO preferences, ...) + NG-RAN->>AMF: + AMF->>UDM/UDR: 2. UE Subscription and Related Data Fetch + rect rgb(240, 240, 240) + Note over AMF: 3. Missing external provisioned parameter detection + end + AMF->>NWDAF: 4. Nnwdaf_analytics_request (Event ID of Expected External Provisioned Parameters, Target Filter, ...) + NWDAF->>AMF: 5. Nnwdaf_analytics_response (Analyzed External Provisioned Parameters, Accuracy and Confidence Interval, ...) + rect rgb(240, 240, 240) + Note over AMF: 6. MICO related parameter derivation + end + AMF->>NG-RAN: 7. Registration Accept (Periodic registration timer, MICO indication, ...) + NG-RAN->>UE: + Note over UE, UPF: Data communication + rect rgb(240, 240, 240) + Note over UE: 8. Wait and enter MICO mode + end + UPF->>AMF: 9. DL data notification + SMF->>AMF: + rect rgb(240, 240, 240) + Note over AMF: 10. Detect UE is un-reachable + end + AMF->>SMF: 11. Extended Buffering + SMF->>UPF: + +``` + +Sequence diagram illustrating the procedure to support NWDAF assisted MICO mode configuration. The diagram shows interactions between UE, NG-RAN, AMF, SMF, UPF, AF, NEF, UDM/UDR, and NWDAF. The process starts with a Registration Request from UE to NG-RAN, followed by UE Subscription and Related Data Fetch from AMF to UDM/UDR. The AMF then detects missing external provisioned parameters and sends an Nnwdaf\_analytics\_request to NWDAF. NWDAF responds with Nnwdaf\_analytics\_response. The AMF then performs MICO related parameter derivation and sends a Registration Accept to UE. A Data communication phase follows, where the UE waits and enters MICO mode. The UPF and SMF notify the AMF of DL data, and the AMF detects the UE is un-reachable, leading to Extended Buffering. + +**Figure 6.29.1.2.3-1: Procedure to support NWDAF assisted MICO mode configuration** + +0. The NWDAF may collect and analysed data from various sources described on the clause 6.29.1.2.1. +1. A UE sends registration request with MICO preference. +2. The AMF fetches UE related data from PCF and UDM/UDR according to the registration process according to TS 23.502 [3]. +3. The AMF detects the missing external provisioned parameters necessary for deciding MICO mode configuration parameters such as allow/disallow MICO mode, periodic registration timer, minimal reachable time, and the size and duration of the buffer. +4. The AMF sends Nnwdaf\_analtic\_request with the event ID and event filters for the UE. +5. The NWDAF responses to the AMF with the estimated external parameter values with the accuracy or the confidence interval. +(Optional) The accuracy and confidence interval can be provided to indicate the confidence on the results of the NWDAF compared to the past observed data. +6. The AMF calculates the MICO mode related configuration parameters. +7. The AMF response to the UE with the registration accept message that contains the MICO mode indication, the periodic registration timer value. Optionally, the minimum reachable time value can be delivered to the UE and/or the RAN via N2 interface. The minimum reachable timer value may be transformed into the active timer or connected timer value according to the TR 23.724 [6].Before entering MICO mode, the UE (or RAN) may wait a certain amount of time during the minimum reachable time value. The detailed mechanism are described in TR 23.724 [6]. +8. UPF and SMF notify DL packets to the AMF. +9. The AMF detects that the UE is not reachable due to MICO mode. +10. The AMF request SMF (or UPF) for the extended buffering with the buffering size and duration according to TR 23.724 [6]. + +## 6.29.2 Impacts on Existing Nodes and Functionality + +NWDAF: The NWDAF should be able collect data from NFs, AFs, and OAM, and should implement internal logic to analyse/estimate the missing external parameters. + +AMF: The AMF should have an interface to interact with the NWDAF to obtain the analytic information. Internally, the AMF may implements decision mechanism for MICO mode configuration based on the output of the NWDAF. + +## 6.29.3 Solution Evaluation + +The Solution 29 addresses Key Issue #8: performance improvement and supervision of mIoT terminals, and provides procedures and parameters to achieve performance enhancement on the battery lifetime of mIoT terminals using NWDAF assistance information. + +The solution clarifies effectively the two main requirements identified for the Key Issue: + +- What necessary input is required for the NWDAF - considering both operator owned and third party mIoT terminals? + +The solution defined a set of Network Data Collection parameters in Table 6.29.1.2.1-1 as input for NWDAF. The parameter set includes such parameters as 'External provisioned parameters' to deal with the information configured at mIoT terminals by operators or third party mIoT service providers. + +- What analytical results can be provided by the NWDAF for performance improvement and supervision of mIoT terminals? + +The solution defined a set of output parameters in Table 6.29.1.1-1 and Table 6.29.1.1-2 which can be used by AMF to decide MICO mode parameters for mIoT terminals. + +The solution resolves a battery lifetime issue for mIoT terminals. + +## 6.30 Solution 30: Network Status in a specific geographic area + +### 6.30.1 Description + +#### 6.30.1.1 General + +This is a solution to Key Issue #12: Support of Northbound Network Status Exposure. + +The solution allows for one-time or continuous reporting of user plane congestion status (congestion for RAN nodes) in a geographic area. + +#### 6.30.1.2 Procedures + +##### 6.30.1.2.1 Procedure for one-time or continuous reporting of network status in a geographic area + +This procedure is used by an AF to retrieve Network Status Information (NSI) from the network for a specific geographic area. The procedure can be used to request a one-time or continuous reporting of network status, as described in figure 6.30.1.2.1-1. + + + +``` + +sequenceDiagram + participant AF + participant NEF + participant NWDAF + participant OAM + + Note left of AF: One-time reporting + AF->>NEF: 1. Network Status Request (geographic area) + NEF->>AF: 2. Authorization + NEF->>AF: 3. Network Status Response + NEF->>AF: 4. Identification of NWDAF(s) + NEF->>NWDAF: 5. Nnwdaf_AnalyticsInfo_Request (user plane congestion, location) + NWDAF->>OAM: 6. Request (user plane congestion, location) + OAM->>NWDAF: 7. Response (user plane congestion) + NWDAF->>NEF: 8. Nnwdaf_AnalyticsInfo_Request response (user plane congestion) + NEF->>AF: 9. Derive NSI + AF->>NEF: 10. Network Status Report (NSI) + NEF->>AF: 11. Network Status Acknowledgement + + Note left of AF: Continuous reporting + NEF->>NWDAF: 12. Nnwdaf_EventsSubscription_Subscribe Request (user plane congestion, location, notification information) + NWDAF->>OAM: 13. Subscribe Request (user plane congestion, location) + OAM->>NWDAF: 14. Subscribe Response (user plane congestion) + NWDAF->>NEF: 15. Nnwdaf_EventsSubscription_Subscribe Response (user plane congestion, subscription correlation ID) + NEF->>AF: 16. Derive NSI + AF->>NEF: 17. Network Status Report (NSI) + NEF->>AF: 18. Network Status Acknowledgement + OAM->>NWDAF: 19. Notification (user plane congestion) + NWDAF->>NEF: 20. Nnwdaf_EventsSubscription_Notify (user plane congestion, notification information) + NEF->>AF: 21. Derive NSI + AF->>NEF: 22. Network Status Report (NSI) + NEF->>AF: 23. Network Status Acknowledgement + +``` + +Sequence diagram illustrating the procedure for one-time or continuous reporting of network status in a geographic area. The diagram shows interactions between AF, NEF, NWDAF, and OAM. It is divided into two sections: 'One-time reporting' and 'Continuous reporting'. + +**Figure 6.30.1.2.1-1: Procedure for one-time or continuous reporting of network status in a geographic area** + +1. When the AF needs to retrieve NSI in a geographic area, the AF sends a Network Status Request (Geographical area, AF Identifier, Duration, Threshold) message to the NEF. Duration indicates the time for which a continuous reporting is requested. The absence of Duration indicates a one-time reporting. Threshold indicates a range at which the AF wishes to be informed of the network status for the continuous reporting. Multiple Threshold values may be included. The AF may indicate whether NSI should be slice specific or not. The NEF assigns a TLTRI that identifies the Network Status Request. + +NOTE 1: Geographical area specified by AF could be at cell level (ECGI), TA level or other formats e.g. shapes (e.g. polygons, circles etc.) or civic addresses (e.g. streets, districts etc.) as referenced by OMA Presence API [25]. + +2. The NEF authorizes the AF request for notifications about potential network issues. The NEF stores AF Identifier, TLTRI, Duration, if present, and Threshold, if present. The NEF assigns an NEF Reference ID. +3. The NEF sends a Network Status Response (TLTRI, cause). The cause value indicates that the network has accepted the request in step 1. Based on operator policies, if either the AF is not authorized to perform this request (e.g. if the SLA does not allow for it) or the AF has exceeded its quota or rate of submitting requests, the cause value indicates the error and the flow stops at this step. +4. The NEF derives a Location Area from the Geographical Area provided by the AF. The Location Area is according to operator configuration either a 3GPP location area (e.g. list of TAs, list of cell(s) etc.). The NEF identifies, based on local configuration or via NRF, the NWDAF(s) responsible for the provided Geographical Area. If multiple NWDAF(s) need to be involved the NEF will have to aggregate the answers. + +For one-time reporting: + +5. The NEF sends Nnwdaf\_AnalyticsInfo\_Request to NWDAF, indicating request for user plane congestion status in a specific location. +- 6-7. The NWDAF requests the user plane congestion status for the requested location to OAM, and OAM provides back the requested information. If the NWDAF already has information about the user plane congestion status for the requested location, these steps are omitted. +8. The NWDAF provides the user plane congestion status information to the NEF. +9. The NEF verifies whether the Network Status Request identified via the NEF Reference ID is valid and active and stores the report. After receiving reports from all the involved NWDAF(s) to which step 5 was executed, the NEF derives the NSI for the requested Geographical Area by combining all reports with the same NEF Reference ID in an operator configurable way (governed by SLAs, network topology, usage, etc.). + +NOTE 2: Either exact values for congestion status, as reported by NWDAF(s) to NEF or abstracted values e.g. (High, Medium, Low) can be reported by the NEF to the AF. The calculation and the reporting of the NSI to the AF depends on operator configuration (SLAs, network topology, usage, etc.). + +10. The NEF sends a Network Status Report (TLTRI, NSI) message to the AF. + +NOTE 3: Either exact values for congestion status, as reported by NWDAF to NEF or abstracted values e.g. (High, Medium, Low) can be reported by the NEF to the AF. + +11. The AF sends a Network Status Acknowledgement to the NEF. + +For continuous reporting: + +12. The NEF sends Nnwdaf\_EventsSubscription\_Subscribe Request to the NWDAF, indicating request for user plane congestion status in a specific location, possibly with thresholds. +- 13-14. The NWDAF subscribe to OAM to get the user plane congestion status for the requested location, possibly providing congestion level thresholds, and OAM provides back the first report for requested information in the response. +15. The NWDAF provides the user plane congestion status information to the NEF. +16. The NEF verifies whether the Network Status Request identified via the NEF Reference ID is valid and active and stores the report. After receiving reports from all the involved NWDAF(s) to which step 12 was executed, the NEF derives the NSI for the requested Geographical Area by combining all reports with the same NEF Reference ID in an operator configurable way (governed by SLAs, network topology, usage, etc.). + +NOTE 4: Either exact values for congestion status, as reported by NWDAF(s) to NEF or abstracted values e.g. (High, Medium, Low) can be reported by the NEF to the AF. The calculation and the reporting of the NSI to the AF depends on operator configuration (SLAs, network topology, usage, etc.). + +17. The NEF sends a Network Status Report (TLTRI, NSI) message to the AF. + +NOTE 5: Either exact values for congestion status, as reported by NWDAF to NEF or abstracted values e.g. (High, Medium, Low) can be reported by the NEF to the AF. + +18. The AF sends a Network Status Acknowledgement to the NEF. + +19. A change of user plane congestion status corresponding to crossing a threshold set by the NWDAF is detected by OAM and notified to NWDAF. + +20. The NWDAF provides a notification for the user plane congestion status information to the NEF. + +21. The NEF verifies whether the Network Status Request identified via the NEF Reference ID is valid and active and stores the report. After receiving reports from all the involved NWDAF(s) to which step 12 was executed, the NEF derives the NSI for the requested Geographical Area by combining all reports with the same NEF Reference ID in an operator configurable way (governed by SLAs, network topology, usage, etc.). + +NOTE 6: Either exact values for congestion status, as reported by NWDAF(s) to NEF or abstracted values e.g. (High, Medium, Low) can be reported by the NEF to the AF. The calculation and the reporting of the NSI to the AF depends on operator configuration (SLAs, network topology, usage, etc.). + +22. The NEF sends a Network Status Report (TLTRI, NSI) message to the AF. + +23. The AF sends a Network Status Acknowledgement to the NEF. + +#### 6.30.1.2.2 Cancelling continuous reporting of network status + +The procedure as depicted in figure 6.30.1.2.2-1 is used for termination of the continuous reporting of network status. It can be triggered by the AF at any time before the Duration is over or if no Duration was provided. The NEF will trigger this procedure when the Duration is over. + + + +``` + +sequenceDiagram + participant AF + participant NEF + participant NWDAF + participant OAM + + Note right of NEF: 1a. Detect end of Duration + AF->>NEF: 1b. Cancel Network Status Request + Note right of NEF: 2b. Authorization + NEF->>AF: 3b. Cancel Network Status Response + Note right of NEF: 4. Nnwdaf_EventsSubscription_Unsubscribe Request (subscription correlation ID) + NEF->>NWDAF: 5. Unsubscribe Request (user plane congestion, location) + NWDAF->>OAM: 6. Unsubscribe Response + NWDAF->>NEF: 7. Nnwdaf_EventsSubscription_Unsubscribe Response + +``` + +Sequence diagram for cancelling continuous reporting of network status. Lifelines: AF, NEF, NWDAF, OAM. The diagram shows two scenarios: 1a) NEF detects end of duration and initiates cancellation; 1b) AF sends a cancel request. Both lead to a series of messages between NEF, NWDAF, and OAM to unsubscribe and then a final response back to the AF. + +**Figure 6. 30.1.2.2-1: Cancelling continuous reporting of network status** + +1a. The NEF detects that the requested Duration for an ongoing continuous reporting of network status to an AF is over and identifies the corresponding NEF Reference ID. + +1b. When the AF needs to terminate an ongoing continuous reporting of network status, the AF sends a Cancel Network Status Request (AF Identifier, TLTRI) message to the NEF. + +2b. If the AF requested to terminate an ongoing continuous reporting of network status in step 1b, the NEF authorizes the AF request and identifies the corresponding NEF Reference ID. + +3b. If the AF requested to terminate an ongoing continuous reporting of network status in step 1b, the NEF sends a Cancel Network Status Response (Cause) message to the AF. + +4. The NEF identifies the NWDAF(s) involved in the continuous reporting represented by the NEF Reference ID. The NEF sends a Nnwdaf\_EventsSubscription\_Unsubscribe Request (subscription correlation ID) to the identified NWDAF(s). +- 5-6. The NWDAF unsubscribe from OAM for the requested information and the OAM confirms unsubscription. +7. Afterwards, the NWDAF sends Nnwdaf\_EventsSubscription\_Unsubscribe Response to the NEF. + +## 6.30.2 Impacts on Existing Nodes and Functionality + +The NEF has to implement NetworkStatus API as defined for SCEF. + +The Nnwdaf\_AnalyticsInfo\_Request and Nnwdaf\_EventsSubscription\_Subscribe service operations have to be enhanced to allow requests for user plane congestion status for a given location, possibly with indication of thresholds. + +The SA WG5 services should allow for retrieving user plane congestion status for a specific location and thresholds. + +NOTE: Whether SA WG5 services allow for retrieving user plane congestion status for a specific location should be checked with SA WG5. + +## 6.30.3 Solution Evaluation + +This solution is the adaptation of T8 NetworkStatus API to NEF and 5GC. It provides the same level of functionality, i.e. for user plane congestion status. + +# 6.31 Solution 31: Network Status for a specific UE + +## 6.31.1 Description + +### 6.31.1.1 General + +This is a solution to Key Issue #12: Support of Northbound Network Status Exposure. + +The solution allows for one-time or continuous reporting of user plane congestion status (congestion for RAN nodes) for a specific UE. + +### 6.31.1.2 Procedure for one-time or continuous reporting of network status for a specific UE + +This procedure is used by an AF to retrieve Network Status Information (NSI) from the network for a specific UE. The procedure can be used to request a one-time or continuous reporting of network status, as described in figure 6.31.1.2-1. + + + +``` + +sequenceDiagram + participant AF + participant NEF + participant NWDAF + participant OAM + participant UDM + participant AMF + + Note left of AF: One-time reporting + AF->>NEF: 1. Network Status Request (GPSI) + NEF-->>AF: 2. Authorization + NEF-->>AF: 3. Network Status Response + NEF-->>AF: 4. Identification of NWDAF(s) + NEF->>NWDAF: 5. Nnwdaf_AnalyticsInfo_Request (user plane congestion, UE id) + NWDAF->>UDM: 6. Nudm_UECM_Get Request (UE id, NF type=AMF) + UDM-->>NWDAF: 7. Nudm_UECM_Get Request (AMF ID) + NWDAF->>AMF: 8. Namf_EventExposure_Subscribe Request (UE id, event = location, one time reporting) + AMF-->>NWDAF: 9. Namf_EventExposure_Subscribe Response (UE location) + NWDAF->>OAM: 10. Request (user plane congestion, location) + OAM-->>NWDAF: 11. Response (user plane congestion) + NWDAF-->>NEF: 12. Nnwdaf_AnalyticsInfo_Request response (user plane congestion) + NEF->>NEF: 13. Derive NSI + NEF->>AF: 14. Network Status Report (NSI, GPSI) + AF-->>NEF: 15. Network Status Acknowledgement + + Note left of AF: Continuous reporting + NEF->>NWDAF: 16. Nnwdaf_EventsSubscription_Subscribe Request (user plane congestion, UE id, notification information) + NEF->>NEF: 17. Derive area of interest for the UE + NEF->>OAM: 18. Subscribe Request (user plane congestion, location) + OAM-->>NEF: 19. Subscribe Response (user plane congestion) + NEF-->>NWDAF: 20. Nnwdaf_EventsSubscription_Subscribe Response (user plane congestion, subscription correlation ID) + NEF->>NEF: 23. Derive NSI + NEF->>AMF: 21. Namf_EventExposure_Subscribe Request (UE id, event = UE moving out of area of interest) + AMF-->>NEF: 22. Namf_EventExposure_Subscribe Response + NEF->>OAM: 24. Network Status Report (NSI) + AF-->>NEF: 25. Network Status Acknowledgement + OAM-->>NEF: 26. Notification (user plane congestion) + NEF-->>NWDAF: 27. Nnwdaf_EventsSubscription_Notify (user plane congestion, notification information) + NEF->>NEF: 28. Derive NSI + NEF->>AF: 29. Network Status Report (NSI, GPSI) + AF-->>NEF: 30. Network Status Acknowledgement + +``` + +Sequence diagram showing the procedure for one-time or continuous reporting of network status for a specific UE. The diagram involves six network functions: AF, NEF, NWDAF, OAM, UDM, and AMF. It is divided into two main sections: 'One-time reporting' and 'Continuous reporting'. + +**Figure 6.31.1.2-1: Procedure for one-time or continuous reporting of network status for a specific UE** + +1. When the AF needs to retrieve NSI for a given UE, the AF sends a Network Status Request (GPSI, AF Identifier, Duration, Threshold) message to the NEF. Duration indicates the time for which a continuous reporting is requested. The absence of Duration indicates a one-time reporting. Threshold indicates a range at + +which the AF wishes to be informed of the network status for the continuous reporting. Multiple Threshold values may be included. The AF may indicate whether NSI should be slice specific or not. The NEF assigns a TLTRI that identifies the Network Status Request. + +2. The NEF authorizes the AF request for notifications about potential network issues. The NEF stores AF Identifier, TLTRI, Duration, if present, and Threshold, if present. The NEF assigns an NEF Reference ID. +3. The NEF sends a Network Status Response (TLTRI, cause). The cause value indicates that the network has accepted the request in step 1. Based on operator policies, if either the AF is not authorized to perform this request (e.g. if the SLA does not allow for it) or the AF has exceeded its quota or rate of submitting requests, the cause value indicates the error and the flow stops at this step. +4. The NEF assigns a NEF Reference ID and identifies, based on local configuration or via NRF, the NWDAF responsible for providing network status for a UE. + +For one-time reporting: + +5. The NEF sends Nnwdaf\_AnalyticsInfo\_Request to NWDAF, requesting for user plane congestion status for a specific UE id. +- 6-9. The NWDAF may already know the UE location. If not, the NWDAF checks the UE location by first retrieving the AMF serving the UE (steps 6-7) and then by interrogating the AMF about the UE location. +- 10-11. The NWDAF requests the user plane congestion status for the UE location to OAM, and OAM provides back the requested information. These steps are omitted if the NWDAF already has the information. +12. The NWDAF provides the user plane congestion status information to the NEF. +13. The NEF verifies whether the Network Status Request identified via the NEF Reference ID is valid and active and stores the report. The NEF derives the NSI for the UE. + +NOTE 1: Either exact values for congestion status, as reported by NWDAF(s) to NEF or abstracted values e.g. (High, Medium, Low) can be reported by the NEF to the AF. The calculation and the reporting of the NSI to the AF depends on operator configuration (SLAs, network topology, usage, etc.). + +14. The NEF sends a Network Status Report (TLTRI, NSI) message to the AF. + +NOTE 2: Either exact values for congestion status, as reported by NWDAF to NEF or abstracted values e.g. (High, Medium, Low) can be reported by the NEF to the AF. + +15. The AF sends a Network Status Acknowledgement to the NEF. + +For continuous reporting: + +16. The NEF sends Nnwdaf\_EventsSubscription\_Subscribe Request to the NWDAF. + 17. The NWDAF determines the UE location, either via internal information or by applying the same steps as steps 6 to 9. The NWDAF then determines an area of interest. + - 18-19. The NWDAF subscribe to OAM to get the user plane congestion status for the UE location, possibly providing congestion level thresholds, and OAM provides back the first report for requested information in the response. + 20. The NWDAF provides the user plane congestion status information to the NEF. + - 21-22. The NWDAF subscribes to UE mobility event notification in order to be informed when the UE moves out of the area of interest (in order to define a new area of interest and request new information to OAM if the UE moves to a different area). + 23. The NEF verifies whether the Network Status Request identified via the NEF Reference ID is valid and active and stores the report. The NEF derives the NSI for the UE. +- NOTE 3: Either exact values for congestion status, as reported by NWDAF(s) to NEF or abstracted values e.g. (High, Medium, Low) can be reported by the NEF to the AF. The calculation and the reporting of the NSI to the AF depends on operator configuration (SLAs, network topology, usage, etc.). +24. The NEF sends a Network Status Report (TLTRI, NSI) message to the AF. + +25. The AF sends a Network Status Acknowledgement to the NEF. + 26. A change of user plane congestion status corresponding to crossing a threshold set by the NWDAF is detected by OAM and notified to NWDAF. + 27. The NWDAF provides a notification for the user plane congestion status information to the NEF. + 28. The NEF verifies whether the Network Status Request identified via the NEF Reference ID is valid and active and stores the report. The NEF derives the NSI for the UE. +- NOTE 4: Either exact values for congestion status, as reported by NWDAF(s) to NEF or abstracted values e.g. (High, Medium, Low) can be reported by the NEF to the AF. The calculation and the reporting of the NSI to the AF depends on operator configuration (SLAs, network topology, usage, etc.). +29. The NEF sends a Network Status Report (TLTRI, NSI) message to the AF. +- NOTE 5: Either exact values for congestion status, as reported by NWDAF to NEF or abstracted values e.g. (High, Medium, Low) can be reported by the NEF to the AF. +30. The AF sends a Network Status Acknowledgement to the NEF. + +## 6.31.2 Impacts on Existing Nodes and Functionality + +The NEF has to implement NetworkStatus API as defined for SCEF, with the addition of GPSI as an input parameter. + +The Nnwdaf\_AnalyticsInfo\_Request and Nnwdaf\_EventsSubscription\_Subscribe service operations have to be enhanced to allow requests for user plane congestion status for a given UE, possibly with indication of thresholds. + +The NWDAF has to retrieve UE location information using existing UDM and AMF services. + +The SA WG5 services should allow for retrieving user plane congestion status for a specific location and thresholds. + +NOTE: Whether SA WG5 services allow for retrieving user plane congestion status for a specific location should be checked with SA WG5. + +## 6.31.3 Solution Evaluation + +**Editor's note:** Use this clause for evaluation at solution level. + +## 6.32 Solution 32: Ensure slice SLA is guaranteed within certain region area + +### 6.32.1 Description + +This solution is for Key Issue 14: How to ensure that slice SLA is guaranteed. + +What slice customer care is, how many subscribers (e.g. 1 millions) can be served by the slice and the Service Experience statistics per application (e.g. average Service MOS 4.0 for Application X for the slice customer) and how many percent (e.g. 90% for Application X) UEs' service experience satisfy per application ID. + +A new slice may be created with dedicated 5GC resource e.g., dedicated SMF/UPF/PCF. Usually 5GC resource is enough while NG RAN is the bottleneck, therefore NG-RAN could be initially configured (e.g., by OAM) with reserved/prioritised resources for the new slice, for example give the slice customer 's devices guaranteed access up to X% (e.g. 20%) of the resources of NG-RAN, in particular area. Other existing slices can access to the reserved/prioritised X% resources of NG-RAN when the new slice is not using them. + +However, the initially configured X% of the resources of NG-RAN could overfit or underfit the slice customer requirement and may need to be modified based on the slice SLA fulfilment Info from 5GC. + +#### 6.32.1.1 Information for slice SLA guarantee + +The information for slice SLA guarantee is similar as the information for the support of QoS Profile Provisioning, see clause 6.3.1.1 for details. + +### 6.32.1.2 Procedure to support slice SLA guarantee with certain region area + +NSSF should control subscribers to access the new slice gradually in order to avoid/minimize the negative impact on the other existing slice SLA fulfilment (with signed SLA). + + + +``` + +sequenceDiagram + participant RAN + participant AMF + participant NSSF + participant NWDAF + participant OAM + + Note left of RAN: Repeat + OAM->>RAN: 0a. OAM creates a new slice and configures initial resources in RAN and in CN allocated to the slice + OAM->>NSSF: 0b. OAM notify initial #users and Slice SLA requirement + NSSF->>NSSF: 1. Allow partial number of subscribers to access the slice + NSSF->>NWDAF: 2a. NSSF Subscribe QoE + OAM->>NWDAF: 2b. OAM Subscribe QoE + NWDAF->>NSSF: 3a. Notify QoE + NWDAF->>OAM: 3b. Notify QoE + NSSF->>NSSF: 4. Determine slice SLA fulfilment + NSSF->>AMF: 5a. NSSF inform Slice SLA fulfilment Info + Note right of RAN: 5a. RAN may take into account the Slice SLA fulfilment Info to schedule radio resource + NWDAF->>OAM: 5b. Nnwdaf_Notify (Slice SLA fulfilment Info) + OAM->>OAM: 6. OAM adjust slice resource until slice is stable + OAM->>NSSF: 7. OAM notify new #users + +``` + +Sequence diagram illustrating the NWDAF-Assisted Slice SLA guarantee procedure. The diagram shows interactions between RAN, AMF, NSSF, NWDAF, and OAM. The process starts with OAM creating a new slice and configuring initial resources. OAM then notifies NSSF of initial user numbers and SLA requirements. NSSF allows a partial number of subscribers. NSSF subscribes to QoE from NWDAF, which in turn subscribes from OAM. NWDAF notifies NSSF and OAM of QoE. NSSF determines SLA fulfilment and informs RAN via AMF. RAN may use this info for scheduling. OAM adjusts resources until stable, then notifies NSSF of new user numbers. A 'Repeat' loop is indicated for steps 2a through 5a. + +**Figure 6.32.1.2-1: NWDAF-Assisted Slice SLA guarantee with certain region area** + +0a. OAM creates a new slice and configures initial resources in RAN (e.g. 20% for the new slice) and in CN allocated to the slice. + +0b: OAM notify the initial number of users and Slice SLA requirement e.g. the average Service MOS requirement and/or the requested number of subscribers and/or the requirement of percentage of the user satisfied to NSSF. + +1. For the newly created slice, NSSF only allow partial number of subscribers to access the slice. + +NOTE 1: NSSF initially allows partial (e.g. 10%) users number to access the slices assuming that users number do not impact the other existing slice SLA, allow NWDAF to train Service MOS Model and then calculate QoE information according to Solution 3: QoS profile Provisioning. + +2. The NSSF sends an Analytics request/subscribe (Event ID = Slice statistics Info, Event Filter information = (S-NSSAIs, Tracking Area, Time Window)) to NWDAF by invoking a Nnwdaf\_EventSubscription\_Subscribe. + +3. NWDAF monitor QoE per user or group of users and provides the QoE data analytics (e.g. the estimated average Service MOS and/or the number of registered subscribers and/or percentage of the user satisfied) to the NSSF and/or OAM. + +4. Based on QoE data analytics provided by NWDAF, NSSF determines whether slice SLA fulfilment (including the new and existing slices with SLA requirement) is overfitting or underfitting or fitting. + +5. NSSF determines the allowed number of the user for the slice and notifies slice SLA fulfilment to RAN via AMF or OAM. RAN could take into account slice SLA fulfilment to schedule Resource per slice within the RAN resource configured by OAM. + +NOTE 2: NSSF informs RAN is dependent on RAN WG3 and SA WG5 feedback. + +6. OAM trains slice resource model with the KPIs from OAM and QoE from NWDAF and then adjust slice resource until slice is stable e.g. RAN resource from 20% (initially configured by OAM when creating slice) to 15%. + +7. When slice is stable i.e. the RAN and CN resource configure is fixed, OAM notifies NSSF to update the allowed number of the user for the slice. + +## 6.32.2 Impacts on Existing Nodes and Functionality + +NWDAF: Provides QoE data analytics to the NSSF. + +NSSF: + +- Get the QoE data analytics from NWDAF; +- Determines the per slice SLA fulfilment information (per TA) based on the QoE from NWDAF; +- Controls partial number of subscribers to access the slice to avoid negative impact on the existing slice SLA; +- Provides the SLA fulfilment information to RAN via AMF or via OAM. + +OAM: + +- Notifies NWDAF to do QoE for a slice. +- May obtain information on SLA fulfilment from NSSF and determines the resource usage for RAN and notifies NSSF to update the allowed number of the user for the slice. + +AMF: + +- Transfers the per slice SLA fulfilment information per TA from NSSF to RAN. + +RAN: + +- Receives slice SLA fulfilment information from NSSF via AMF or via OAM, which may be taken into account when scheduling radio resource; + +## 6.32.3 Solution Evaluation + +This solution allows NSSF to determine per slice SLA fulfilment information based on QoE from NWDAF. + +With per slice SLA fulfilment information, NSSF could control subscribers to access a new slice gradually in order to avoid/minimize the negative impact on the other existing slice SLA fulfilment. + +Optionally, this solution also allows RAN to take into account the per slice SLA fulfilment information to schedule radio resource. + +The solution applies effectively in some region areas (may also in certain time period), in which the slice SLA is concerned. + +# 6.33 Solution 33: Ensure slice SLA is guaranteed within certain region area + +## 6.33.1 Description + +### 6.33.1.1 A Use Case + +A possible use case from Key issue#14, is that an SLA has been agreed between MNO and a customer that covers the following KPIs: + +- Number of users (group of users) per slice and even per TA or other larger defined area. +- Different fulfilment for different applications such as: + - - 80% of users running application 1 shall have a at least QoE\_1 or higher (where QoE\_1 might be an agreed MOS value). + - - 90% of users running application 2 shall have a at least QoE\_2 or higher (where QoE\_2 might be an agreed MOS value). + - - etc. + +Here it is assumed that a specific slice is going to be used for this customer. + +### 6.33.1.2 Providing Analytics to OAM to assist SLA monitoring + +Assume that the MNO would like to assure that it can support the SLA by allocating a new slice. One way to do this is to set up resources in RAN and in CN allocated to the slice. + +One way to proceed is to start letting the customer populate the slice with users by introducing an initial number of users and add more and more UEs into the network and let them start using the applications. Each user is allocated an initial QoS Flow, either per application if multiple QoS Flows are to be used or one general QoS Flow. The QoS profiles shall reflect the requirements of the services mapped on the QoS Flows as well as desired packet treatment at congestion. + +For a newly created slice, NSSF may only allow partial number of subscribers to access the slice. This admission control of the UEs allows to increase the maximum number of users belonging to the group in a controlled manner. OAM is aware of the number of users in the slice and add more and more when it sees it feasible. NSSF receives admission control information per slice and TA, which may be retrieved directly in OAM. If OAM does not have information per TA, such counter may be added in SA WG5. + +NWDAF monitor QoE per user in the allocated slice. But it also monitors all other groups of user's QoE that it has received a similar KPI for. NWDAF calculates continuously the fulfilment per application in the groups. OAM may subscribe to QoE info from NWDAF. + +For users with no agreements, the solution can be pure dimensioning, by letting for instance the large ordinary MBB slice have a minimum amount of resources. Or the proposed solution may also be applicable for slices without an associated SLA. + +OAM then uses this info and other info important for reaching the slice KPIs to optimize the resources in RAN and in CN if needed. For optimization done by OAM no further description is done in here in this document and is left for other groups in 3GPP, such as SA WG5 and considered outside of the scope of SA WG2. Only an overview of possible steps are added below for clarity of the overall solution. + +NOTE: OAM for RAN, CN and Transport Network most certainly have a better view on what optimizations can be done compared to letting SA WG2 decide upon this. Also RAN has a very good view on how UEs belonging to a certain slice is being supported by different RAN resources from a characteristics point of view. + +The convergence time shall be up to implementation, since it may depend on e.g. how the SLA is defined, the statistics involved and how active users are. Also, since the SLA is a statistical measure it needs some time to converge. A predictive model in Management Data Analytics Service (MDAS) in OAM may be used to act proactively. In conclusion the convergence time is dependent on how fast the SLA can be evaluated after corrective actions has been taken. + +## Flow Diagram. + + + +``` + +sequenceDiagram + participant RAN + participant AMF + subgraph NAS [Newly Added Slice] + PCF + SMF + UPF + end + participant NSSF + participant NWDAF + participant OAM + + Note right of NSSF: 0. NSSF receives new slice info from OAM including initial admission control info per slice and TA + Note right of NWDAF: 0. NWDAF receives the KPIs + Note right of NSSF: 1. NSSF do admission control for the users in the slice + Note right of NWDAF: 2. Nnwdaf_EventsSubscription_Subscribe (QoE) + Note right of AMF: 3. Users are regestering and use the slice as long as the admission control lets them in + Note right of NWDAF: 4. NWDAF monitor QoE continuously according to Solution 3: QoS Profile Provisioning + Note right of NWDAF: 5. Nnwdaf_Notify (QoE continuously) + Note right of OAM: 6. OAM evaluate SLA contiously and may take corrective actions + Note right of OAM: 7. OAM notifies new admission control info per slice and TA) + Note left of RAN: Continuously + +``` + +The sequence diagram illustrates the following steps: + +- NSSF receives new slice info from OAM including initial admission control info per slice and TA. +- NWDAF receives the KPIs. +- NSSF do admission control for the users in the slice. +- NWDAF subscribes to QoE information (Nnwdaf\_EventsSubscription\_Subscribe (QoE)). +- Users are registering and use the slice as long as the admission control lets them in. +- NWDAF monitor QoE continuously according to Solution 3: QoS Profile Provisioning. +- NWDAF notify continuously the QoE and slice ID per user (Nnwdaf\_Notify (QoE continuously)). +- OAM evaluate SLA contiously and may take corrective actions. +- OAM notifies new admission control info per slice and TA (indicated by a dashed return arrow). + +Sequence diagram showing the interaction between RAN, AMF, Newly Added Slice (PCF, SMF, UPF), NSSF, NWDAF, and OAM for slice admission and QoE monitoring. + +Figure 6.33.1.2-1 + +The steps are described here: + +0. The admission control info per slice and TA or other larger defined area is forwarded from OAM to NSSF. NWDAF receives only the KPI used for QoE monitoring. +1. NSSF may do admission control by accepting or not accepting more users to the slice. This acceptance may be done per TA. At each registration AMF forwards a slice request to NSSF. This is done by either local configuration, or UE request a general slice (not available in AMF) which forces AMF to ask NSSF. +2. OAM subscribes to QoE information per user belonging to specific slices with KPIs. And optionally to other/all users in general slices such as MBB, IoT from NWDAF. +3. Users register and use the slice. +4. NWDAF monitor QoE per user. +5. NWDAF notify continuously the QoE and slice ID per user. The NWDAF may add the gNB used per user. + +6. Some example steps OAM might take here are as follows: + +- 6.1 OAM continuously evaluate input, including the info received from NWDAF to evaluate towards the KPIs. +- 6.2 Optionally the analytics function in Management Data Analytics Service (MDAS) has a QoE prediction model and uses the input to update it. +- 6.3 Optionally, the predictive model is used for SLA evaluation, which will allow proactive measures. +- 6.4 If the SLA is breached OAM determines the cause and triggers appropriate actions in RAN, Transport Network and/or CN domain to remedy the breach. + +7. OAM notify new admission control info per slice and TA if number of users per slice and TA has been breached. + +To support the SLA admission control in NSSF may be done by controlling number of users in slice and even in TAs or other larger defined areas, as described in the flow diagram above. NSSF receives information from OAM to take decision on when users in a specific slice and TA may not access the slice. + +Admission could be done on registered users in NSSF dependent on SLA. Thus, it could also be used to gradually ramp up the number of allowed registered users to the contractual level of an SLA if desired. + +NOTE 1: There is an option that RAN continuously act upon the fast dynamicity within the slice inside the RAN domain, to assure that the slice KPIs are not being underfitting. RAN has knowledge of what UEs belonging to a slice and what resources they are using and the relation to other UEs. It should be considered that there is existing mechanism defined in RAN to monitor a slice. But this is left for other standardizations group, such as SA WG5. + +NOTE 2: This solution needs co-operation between standardization groups as described in the key issue #14 + +## 6.34 Solution 34: NWDAF collecting analytic information directly from UE + +### 6.34.1 Description + +#### 6.34.1.1 General + +This solution addresses key issue X and addresses the following: + +- What analytic data can be provided by the UE directly to the NWDAF. +- What analytic information can the NWDAF derive based on the information provided by the UE. +- How other NFs can use the NWDAF derived UE analytic information. + +The solutions in the FS\_eNA TR specify that any UE-related analytic information is collected by the NWDAF indirectly, i.e., either from the AMF for any UE location related information, or from the RAN based on information collected by OAM analytic functions. + +A solution is proposed for the UE to track its location when in IDLE mode and report to the NWDAF. The NWDAF uses the location information provided "indirectly" with the location information provided by the UE to derive statistical data with better confidence. + +#### 6.34.1.2 UE sending IDLE related location information directly to the NWDAF + +Examples of usage data provided by the UE can be the following: + +- Report duration: 10:35am - 11:35pm. +- Visited cells: (Cell-1, entry time, exit time), (Cell-2, entry time, exit time), etc. +- Location: (X1, Y1, Z1 @ 10:36am), (X2, Y2, Z2 @ 11:14am). + +The UE does not send usage data in real-time. Rather, such data is internally collected in the UE and is sent to the NWDAF in batches (e.g. every X hours). It is up to the UE implementation how often the UE provides such usage data. + +### 6.34.1.3 Usage of IDLE related location information by other NFs + +The NWDAF uses the UE location information from the AMF (location information in connected State) and directly from the UE (location information in IDLE) to derive more accurate statistical prediction of the UE location. + +The NWDAF can provide mobility prediction based on combining UE location information reported from the AMF (when UE is in CONNECTED state) and the UE (when the UE is in IDLE state). + +**Editor's note:** The usage of the NWDAF output that includes mobility predictions based on the UE historical location information requires further study + +### 6.34.1.4 Method to provide IDLE related location information to the NWDAF + +The UE can provide the "Location information in IDLE mode" by using a control plane procedure as specified in Solution 16 or via a user plane procedure as specified in Solution 15 in TR 23.791. + +## 6.34.2 Impacts on Existing Nodes and Functionality + +**Editor's note:** Capture impacts on existing 3GPP nodes and functional elements. + +## 6.34.3 Solution Evaluation + +**Editor's note:** Use this clause for evaluation at solution level. + +--- + +# 7 Overall Evaluation + +## 7.1 Key Issue 1& Key Issue 2 + +For analytic services, two types of solutions are described in the TR 23.791: + +- Generic solutions, which apply to multiple use cases: Solutions #1 and #9. +- Solutions specific to use cases: Solution #3, #4, #5, #7, #8, #10, #11, #18, #20, #21, #22, #23, #27, #29. These solutions might potentially reuse (refer to) the generic solutions. + +The services provided by the generic solutions can be further classified into three levels of analytics: + +- **Statistics of the past**, which may be considered simply as a report, but also as a "vanilla" estimation of the future in general, with the underlying paradigm that "future" shall be very similar to "past" (therefore no need to refine the prediction). +- **Predictions**, which are a step beyond the previous, because trend analysis may determine evolving drivers for the future which cannot be detected by basic statistics. But in this step, a major part of the decision-making process remains in the consumer NF. +- **Recommendations**, where the NF delegates some calculation of optimal parameters to the NWDAF, but still remains responsible for the final choices. + +Solution #1 provides statistics and predictions, while Solution #9 provides recommendations. + +Solution #9 (Recommendations produced by NWDAF) is a solution that has been evaluated to possibly only cover a limited number of key issues/use cases, which are a subset of what can be solved by analytics. It is not recommended for Release 16, because it requires additional study. It is desirable that this Solution be reconsidered following the results obtained on the implementations of Release 16, in order to examine its relevancy on stronger use case basis. + +For metadata exposure, Solution #13 supports the metadata exposure to NFs by introducing new service operation on NWDAF, and Solution #19 provides the metadata to NFs via NRF as a part of NF profile. + +## 7.2 Key Issue 2: Analytic Information Exposure to AF + +Solution 24 supports how to expose analytics information to an AF directly from NWDAF or via NEF. + +Regarding how to expose metadata information to an AF in untrusted domain, the exposure needs to be made via NEF. Solution 13 supports the metadata exposure to NFs by introducing new service operation on NWDAF while Solution 19 + +provides the metadata to NFs via NRF as part of NF profile. It is considered that Solution 19 can be used for the NEF to retrieve the NWDAF metadata. With this, the NEF service and the structure for metadata are needed to be defined. + +## 7.3 Key Issue 3: Interactions with 5GS NFs/AFs for Data Collection + +For Key Issue 3: Interactions with 5GS NFs/AFs for Data Collection, there are four solutions, i.e.: + +- Solution 6: Data Collection from NFs/AFs using a new service, i.e. introduce new services to collect massive pre-computed metrics over populations of UEs or groups of information (e.g., application ID), per spatial and temporal dimensions (e.g., per region of a network slice for a period of time); as well as for data collection from AF. +- Solution 14: Data Collection from NFs/AF via NF Event Exposure services, i.e. reuse the R15 NF event exposure services to collect not only individual UE data but also populations of UEs or groups of information (e.g., application ID), per spatial and temporal dimensions (e.g., per region of a network slice for a period of time) with following extensions: + - - Extensions on Data Collection via Event Exposure from AF directly and from 3rd Party AFs via the NEF. + - - Extensions on Exposure Framework (on Object Target and Event Filter Information, Collectable Data Item (CDI)) in order to collect massive pre-computed metrics over large populations (e.g. groups of UE, applications IDs). +- Solution 25: Exposure with bulk subscription and NWDAF collecting data from UDR, i.e. to reuse bulk subscription service of NEF defined in R15 that supports any NF to subscribe event exposure for multiple UEs; needs to be extended to collect data from AFs, and to be able to collect groups of information (e.g., application ID). This solution is a special case of EventSubscription. Some drawbacks are seen with this solution: + - 1) It is a bulk subscription meaning all data is stored, even data that is not of interest for analytics in NWDAF. + - 2) UDR must be dimensioned for long term data lake storing of massive amount of data. + - 3) Signalling towards UDR will be heavy for Data collection. + - 4) Signalling towards UDR will be heavy for Data retrieval from NWDAF. + +With the drawbacks mentioned above the method in this solution shall not be the primary way to retrieve NF related data. +- Solution 26: Data Collection using NRF services, i.e. reuses NRF services defined in R15 for the NWDAF to discover NFs and associated NF profiles. + +## 7.4 Key Issue 4: Interactions with OAM for Data Collection and Data Analytics Exposure + +For Key Issue 4 Interactions with OAM for Data Collection and Data Analytics Exposure, there is only one solution: + +- Solution 12: Data Collection from OAM using the existing SA WG5 services i.e. reuse the already defined SA WG5 services to collect data from OAM. + +## 7.5 Key Issue 5: NWDAF-Assisted QoS Profile Provisioning + +Solution 3 supports NWDAF-Assisted QoS Profile Provisioning for the non-standardized 5QI. + +## 7.6 Key Issue 6: NWDAF assisting traffic routing + +Table 7.6-1 + +| Criteria | Solution #11 | Solution #20 | +|------------------------------------|-----------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| UPF discovery and selection by SMF | NWDAF input data for traffic analysis are addressed.
Time information and UPF load information is provided to SMF. | Evolves UPF discovery and selection by SMF as defined in Rel-15 to take predictions on UPF load and UE location into account.
Maintains existing configuration in SMF, no extra operational cost.
Step 1 and 2 are better directly requested by and responded to SMF | +| Compliance with solution# to KI#1 | Compliant, reuses solution#1 | Compliant, reuses solution#1 | + +## 7.7 Void + +## 7.8 Key Issue 8: Performance improvement and supervision of mIoT terminals + +### 7.8.1 General mode for mIoT terminals + +There are two alternative solutions on how misused or hijacked UEs are recognized by using data analysis. + +NOTE: The misused or hijacked UEs are UEs in which there are malicious applications running or UEs which have been stolen. + +Solution 8 requires AMF/SMF to identify IoT UEs with unexpected behaviour first by comparing runtime UE behaviours with expected UE behaviours provided by UDM or NWDAF and optionally to take actions locally. The NWDAF will make further analysis on the result provided by the AMF/SMF to determine the misused or hijacked UEs. The analytic result from the NWDAF can be sent to 5G NFs or AF to trigger corresponding actions. + +Solution 21 relies on the NWDAF to identify the misused or hijacked UEs by itself. The NWDAF needs to collect runtime data of IoT UEs from the 5GC and compare the UE runtime behaviour with expected UE behaviours which may be obtained from AF or UDM, or learned by the NWDAF itself. The analytic result from the NWDAF is also sent to 5G NFs or AF to trigger corresponding actions. + +### 7.8.2 MICO mode for mIoT terminals + +Solution 29 NWDAF assisted MICO mode for mIoT terminals addresses performance enhancement on the battery lifetime of mIoT terminals. The solution provides necessary procedures and parameters for NWDAF to obtain required input data from NFs and/or AFs and deliver output data to an AMF. Based on the solution, the AMF can use the NWDAF assisted analytic information to decide MICO mode parameters values for mIoT terminals. The solution 29 can be selected as base for the normative work in Release 16. + +## 7.9 Key Issue 9: Customizing mobility management based on NWDAF output + +There are 6 different solutions described for this key issue. + +### 7.9.1 Registration area allocation + +Solution 4, 7 and 23 relate to optimizing registration areas: + +- Solution 4 "Optimizing registration area management and service restriction areas adjustment based on NWDAF output": this solution relies on the AMF using service area restrictions from PCF and statistics and/or predictions on UE mobility from NWDAF to derive registrations areas. +- Solution 7 "Customizing mobility management based on NWDAF output": some aspects of this solution are more related to the framework for eNA, such as the NWDAF registering the supported Event-IDs into NRF (e.g. "UE expected geographical movement") or NWDAF possibly being co-located with AMF. There is no specific AMF behaviour specified in this procedure. +- Solution 23 "AMF using NWDAF outputs to optimize UE mobility procedures": The Nnwdaf\_EventsSubscription and Nnwdaf\_AnalyticsInfo services need to be enhanced to allow provisioning of analytics or predictions or both for mobility information for a specific UE. Only AMF derives registration areas and paging areas for the UE based on inputs provided by NWDAF. + +## 7.9.2 Mobility restriction area handling + +Solution 4 "Optimizing registration area management based on NWDAF output": this solution supports PCF using statistics and/or predictions on UE mobility from NWDAF to optimize service area restrictions adjustment. + +## 7.9.3 Paging handling + +Solution 5 "Optimization based on paging failure prediction from NWDAF": for this solution, a couple of issues still need to be addressed or discussed. Some aspects of the proposal are related to RAN paging and would need to be discussed by RAN WGs. Regarding CN paging failures, whether aspects related to paging strategy need to be standardized between the AMF and the NWDAF is unclear, e.g. the AMF reporting the paging areas to the NWDAF. + +## 7.9.4 Handover decisions + +Solution 10 "NWDAF assisted Handover decision": in this solution, the 5GC can use the NWDAF output to predict the UE mobility and indicate the predicted UE location to the NG-RAN node serving the UE. Then the NG-RAN node can select a more suitable target cell during the handover or redirection. + +This solution is not under SA WG2 remit, rather it would require analysis from RAN WGs. + +## 7.9.5 Connection management + +Solution 22 "Optimizing connection management based on NWDAF output": this solution allows the AMF to optimize connection management for a UE based on communication pattern information and mobility information received from NWDAF. + +## 7.10 Void + +## 7.11 Void + +## 7.12 Key Issue 12: Support of Northbound Network Status Exposure + +Solution 30 allows to expose Network Status related to user plane congestion to an AF for a specific geographic area. The solution is an adaptation of SCEF procedure to expose Network Status (as defined in TS 23.682 [5]). + +Solution 31 allows to expose Network Status related to user plane congestion to an AF for a specific UE. + +## 7.13 Void + +## 7.14 Key Issue 14: How to ensure that slice SLA is guaranteed + +There are two different solutions described for this key issue, that are analysed below, using the comparison criteria in table 7.14-1, i.e. impacts on 5GS, amount of signalling, cost, deployment aspects, configuration effort. + +**Table 7.14-1** + +| Comparation criteria | Solution#32 | Solution#33 | +|----------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Impacts in the existing Radio Resource Management in OAM
(NOTE 1) | According to SA WG5 TS, RAN may be OAM configured with RRM policies per slice (see TS 28.541 [27], clause 4.3.36.1, Annex C). | Existing RRM policies are used (According to SA WG5 TS, RAN may be OAM configured with RRM policies per slice (see TS 28.541 [27], clause 4.3.36.1 and Annex C), unless SA WG5 decides to extend them. (RAN) OAM can receive QoS notifications and react accordingly. Actually it is up to OAM to determine where the issue is (RAN, transport, core) and to react accordingly. | +| Impacts in the existing NG-RAN RRM
(NOTE 2) | This solution impacts RAN RRM (new message 5a : "NWDAF notifies the new slice QoE fulfilment to RAN within the problematic area via AMF. RAN within the problematic area could take into account the new slice QoE fulfilment to schedule Resource per slice within the RAN resource configured by OAM"): This impacts RAN RRM. | NG-RAN monitors if RRM policies are fulfilled, and then take actions.
Analysis: No impacts on NG-RAN, besides OAM RRM policy configuration. | +| Impacts on 5GS NF | SLA monitoring functionality is placed in OAM with NWDAF assistance on QoE in the slice.
NSSF, AMF, and NG-RAN are impacted to be able to transfer the indication that QoE is not fulfilled and then take actions in NG-RAN.
NSSF role is extended to do admission control while this baseline feature was not defined in Rel-15; It may be needed to first define whether (and if yes how) to support admission control on a per slice basis (this requires that the entity doing admission control knows when slice resource are used and are no more used). | NSSF role is extended to do admission control while this baseline feature was not defined in Rel-15; It may be needed to first define whether (and if yes how) to support admission control on a per slice basis (this requires that the entity doing admission control knows when slice resource are used and are no more used). | +| Amount of signalling to NG-RAN that is assumed to be a bottleneck) | Signalling from AMF to RAN on QoE fulfilment cause extra signalling. | Signalling from NWDAF to OAM to provide QoE in the slice.
Analysis: No unnecessary signalling from AMF to NG-RAN. | +| Cost | Analysis: There are additional cost on the new requirements of NSSF, AMF and NG-RAN. However, the NSSF, AMF, NWDAF are expected to be deployed in a central way. The benefit is achieved in view of fast parameter convergence and more efficient radio resource usage. | Cost would be estimated by SA WG5, NWDAF service may need some extensions as well as defining SLA monitoring functionality.
Analysis: The cost is not clear yet since the SA WG5 solution is under development in TR 28.805 [26]. | +| Deployment issues | SA5 defined e2e SLA monitoring as defined in TR 28.805 [26] and QoE monitoring defined in this TR.
Analysis: The solution in this TR can be a compliment solution as for the OAM solution to be defined by SA WG5. | OAM solution only, implies that each NF complies with OAM SA5 TSs. Solution feasibility is unclear since the NWDAF monitor QoE per user and the granularity of notification from NWDAF to OAM is FFS.
Analysis: 5GS implements OAM TSs for SLA monitoring. The TR 28.805 [26] is still under progress and lack of complete solutions yet. | + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| NOTE 1: Impacts are only estimated since the RRM functionality is currently defined at SA WG5.
NOTE 2: Impacts are only estimated since NG-RAN is defined by RAN WGs.
NOTE 3: Proprietary OAM solutions are not considered. | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +--- + +## 8 Conclusions + +### 8.0 Conclusions on the framework for analytics + +The analytics framework in Rel-16 shall be based on the following principles: + +- Evolves the Network Data Analytics architecture and the NWDAF NF defined in TS 23.501 [2] and Nnwdaf services defined in TS 23.502 [3]. +- Complies with the specification of NF framework defined in TS 23.501 [2]. + - - NWDAF discovery functionality is required. + - - NWDAF profile and Nnwdaf\_EventExposure and Nnwdaf\_Analytics service include service authorization information to indicate the NF type, the NF realms which are allowed to consume each NWDAF service. + - - Multiple instances of NWDAF may exist. Each NWDAF instance informs the NRF of the list of NF services that it supports. + +NOTE: The relation with eSBA SID has not been investigated in this TR, any potential impact from eSBA will be handled during the normative phase. + +### 8.1 Key Issue 1: Analytic Information Exposure to 5GS NF + +On how a consumer request or subscribes to analytics, solution 1 is selected as basis for the normative work. + +On how analytics information is provided to consumers, solution 1 is selected as basis for the normative work. + +On how metadata is retrieved by each consumer of analytics, solution 19 is selected as basis for the normative work when NF discovers NWDAF via NRF, otherwise local configuration in each NF applies. + +### 8.2 Key Issue 2: Analytic Information Exposure to AF + +Regarding how to expose analytics information to AF, Solution 24 is selected for the normative work. + +Regarding how to expose metadata information to an AF in untrusted domain: + +- NEF should provide a service to expose NWDAF metadata to the AF, +- The NEF service and the structure for metadata will be defined in the normative phase, +- The NEF shall retrieve the NWDAF metadata using Solution 19. + +### 8.3 Key Issue 3: Interactions with 5GS NFs/AFs for Data Collection + +Regarding how to collect data from 5GC NFs/AFs to NWDAF, Solution 14 is selected for the normative phase and Solution 26 is selected from the aspects of NRF services as complementary solution. + +### 8.4 Key Issue 4: Interactions with OAM for Data Collection and Data Analytics Exposure + +Regarding how to collect data from OAM to NWDAF, Solution 12 is selected as the basis for the normative work. + +## 8.5 Key Issue 5: NWDAF-Assisted QoS Profile Provisioning + +Solution 3 is proposed to be selected for KI 5 in the normative work. + +## 8.6 Key issue 6: NWDAF assisting traffic routing + +To enable NWDAF assistance to traffic routing, both UPF selection and AF influence on traffic routing, it is recommended to select solution 20 as the basis for normative work and the list of input parameters for analytics listed in Table 6.11.1.2.1-1: Collecting Data for analysing traffic characteristics in solution 11. + +## 8.7 Key Issue 7: NWDAF assisting Future Background Data Transfer + +On what type of analytics information for Future Background Data Transfer could be provided by NWDAF for the PCF to determine the policy of future background data transfer, solution 18 is selected as a basis for normative work. + +On what information does NWDAF need as input to determine such analytics information, solution 18 is selected as a basis for normative work. + +In addition, solution 28 is selected as basis for normative work. The information flow for BDT described in solution 27 is selected for normative work. + +## 8.8 Key Issue 8: Performance improvement and supervision of mIoT terminals + +### 8.8.1 General mode for mIoT terminals + +It is concluded that Solution 8 and Solution 21 are used as the basis for normative work on how misused or hijacked UEs are recognized. + +NOTE: The misused or hijacked UEs are UEs in which there are malicious applications running or UEs which have been stolen. + +### 8.8.2 MICO model for mIoT terminals + +For the Key Issue 8: performance improvement and supervision of mIoT terminals, + +The solution 29 is selected as the basis for normative work on NWDAF assisted performance enhancement for the battery lifetime management of mIoT terminals. + +## 8.9 Key Issue 9: Customizing mobility management based on NWDAF output + +For optimizing registration area allocation, solution 23 and solution 4 are selected as basis for further normative work. The NWDAF service operations should be enhanced to allow for new Event-ID providing statistics or predictions on UE geographical movement, e.g. as described in solution 7. The AMF behaviour based on such statistics or predictions shall be left to implementation. + +For optimizing mobility restriction area handling, solution 4 is selected as basis for further normative work. + +For optimizing connection management for the UE, NWDAF service operations should be enhanced to allow for providing statistics or predictions on communication patterns for the UE, as described in solution 22. + +For optimizing paging or handover decisions, no specific normative work is required in SA WG2. + +## 8.10 Void + +## 8.11 Void + +## 8.12 Key Issue 12: Support of Northbound Network Status Exposure + +For exposure of Network Status to Northbound entities, procedures developed during normative phase will allow exposure of user plane congestion related information and will be based on: + +- solution 30 for Network Status in a specific geographic area; and +- solution 31 for Network Status for a specific UE. + +## 8.13 Key Issue 13: UE Driven Analytics + +It has been concluded that it would be useful for the NWDAF to collect the "UE Out of Coverage Entries" parameter. The "UE Out of Coverage Entries" parameter is described in solution 16. How the NWDAF collects the "UE Out of Coverage Entries" parameter has not been concluded. + +Further study is required before SA WG2 can conclude on a complete list of what UE Data Analytics parameters would be useful for the NWDAF and how those parameters should be collect by the NWDAF. + +There will be no normative work in Rel-16 on this topic. + +## 8.14 Void + +## 8.14A Key Issue 14: How to ensure that slice SLA is guaranteed + +The following conclusions are agreed for normative work related to Key Issue 14: + +- NWDAF provides analytics for slice QoE. +- The slice QoE analytics granularity when consumed by OAM will be per slice ID per user. +- SLA fulfilment evaluation is performed by OAM as indicated in TR 28.805 [26]. + +Any slice admission control mechanism in 5GC, based on NWDAF analytics and OAM triggers, requires further SA2 investigation and will not be progressed in Rel-16. + +No interaction between 5GC and NG-RAN on slice SLA or slice QoE will be progressed in Rel-16. + +## Annex A: Examples on Network Data Analytics Feedback + +### A.1 Examples for EventID + +The following are examples of EventIDs and EventFilters. The list of EventIDs and Event Filters are described in each solution for the different key issues. + +**Table A.1-1: Examples for EventID** + +| Event ID | Event Filter ( | Description (examples of patterns) | +|------------------------------------------------------|--------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| UE Behavior parameters
Expected Moving Trajectory | List of UE identities,
Time, Date | UE's expected geographical movement (e.g. as described in TS 23.502 [3] clause 14.5.6.3). | +| UE Behavior parameters
Communication pattern | | UE expected communication (e.g. communication of low latency applications at a given time and date, or Time and date when UE does not have any communication) | +| NW performance Pattern | NW area,
Time,
Date | NW expected performance pattern (e.g. Estimated load in a network area at a given time and date). | + +### A.2 Examples of Event Filter + +**Table A.2-1: Example of Event Filter** + +| Example of Event Filter Information | Value assertion (examples) | +|----------------------------------------------------------|----------------------------| +| S-NSSAI | = "MBB" | +| NF, NF set, NF region | = "all NFs" | +| TAI, Cell ID, geographical area, area type (rural/urban) | = "Cell-3" | +| DNN, Application Identifier | = "MMS" | + +### A.3 Example of content of Subscription/Request + +Table A.3-1 describes a simplified example of content of Subscription/Request focusing on UEs-groups= "UE-group1, UE-group2, UE-group3", SliceID= "SliceA", AfID= "App1", and denotation of explicit list "per UE groups". + +**Table A.3-1: Simplified example of content of Subscription/Request** + +| Event Parameter value | Target of Event Reporting | Event Filtering Information | Denotation of Explicit Lists | +|--------------------------------|------------------------------------------|--------------------------------------|------------------------------| +| Number of registrations (N) | "UE-group1"; "UE-group2";
"UE-group3" | Slice ID = "SliceA"
AFId = "App1" | DOE="per UE-group" | +| Service satisfaction level (R) | | | | + +## A.4 Example of content of notification/response + +Table A.4-1 describes an example of content of Notification/Response focusing. + +**Table A.4-1: Example of content of notification/response** + +| analytics for N-SSAI="SliceA"
and AFId= "App1" | Statistics in the case of explicit list | +|-----------------------------------------------------------|---------------------------------------------------------------| +| Number of registrations (N) |
(NOTE) | Actual location information of the originating MCData user; | +| Time Limit | O | Proposed time limit of the requested IP connectivity (1min- infinite); | +| NOTE: This information contains the latest available location information of the requesting MCData user that may be different to the latest available location information in the MC system. | | | + +## 7.28.1.5.4 IP connectivity group service + +### 7.28.1.5.4.1 General + +The initiation of a group IP connectivity to a selected group results in affiliated group members exchanging IP Data between associated data hosts linked with IP connectivity capable MCData clients. + +### 7.28.1.5.4.2 Procedure + +The procedure in figure 7.28.1.5.4.2-1 describes the case where an IP connectivity capable MCData client associated with a data host is initiating group MCData IP connectivity communication to other IP connectivity capable MCData clients associated with other data hosts. + +Pre-conditions: + +- Data hosts linked with MCData client 1 to MCData client n belong to the same group and are already registered for receiving MCData service and are affiliated. +- The total data volume limit, e.g. daily time limit or total data volume per day, does not restrict the establishment of an IP connectivity IP data exchange. +- MCData client 1 to MCData client n are linked with individual data hosts. +- MCData client 1 and MCData client n belong to the same MCData system. +- The data hosts linked with the IP connectivity capable MCData clients already have an IP address allocated. + + + +``` + +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 IPcon group request + MCData server->>Group management server: 3. Authorize request + Group management server->>MCData server: 4. Resolve group id + MCData server->>MCData server: 5. Transmission/ Reception control + MCData server->>MCData client 2 to n: 6. MCData IPcon group request + MCData client 2 to n->>MCData server: 7. n-times MCData IPcon group response + MCData server->>MCData client 1: 8. n-times MCData IPcon group response + Note over MCData client 1, MCData server, Group management server, MCData client 2 to n: 9. IP connectivity MCData bearer service IP address allocation + Note over MCData client 1, MCData server, Group management server, MCData client 2 to n: 10. Data transmission + +``` + +Sequence diagram illustrating the establishment of IPcon group communication. Lifelines: MCData client 1, MCData server, Group management server, and MCData client 2 to n. The sequence starts with MCData client 1 sending an 'initiate data request' to the MCData server. The MCData server sends an 'MCData IPcon group request' to the Group management server, which responds with 'Authorize request', 'Resolve group id', and 'Transmission/ Reception control'. The MCData server then sends an 'MCData IPcon group request' to MCData client 2 to n, which respond with 'n-times MCData IPcon group response'. The MCData server forwards this to MCData client 1. Steps 9 and 10 are shown as horizontal bars spanning all lifelines: 'IP connectivity MCData bearer service IP address allocation' and 'Data transmission'. + +**Figure 7.28.1.5.4.2: Establishment of IPcon group communication** + +1. MCData client 1 initiates an IP connectivity group request to a pre-configured group (identified by MCData group ID) and optionally particular members from that group. + 2. MCData client 1 sends a MCData IPcon group request towards the MCData server. The MCData IPcon group request contains target recipient(s) as provided by the MCData client 1. + 3. MCData server checks whether the MCData client 1 is authorized to send MCData IPcon group data request and that the target MCData clients are authorised to receive the IP connectivity service. + 4. 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. If a functional alias is active and associated with the MCData ID, the MC Data server verifies if certain conditions shall be considered, e.g. MCData client location, to establish the communication. + 5. The MCData server also applies transmission and reception control and the necessary policy to ensure that appropriate IP Data are transmitted between the MCData clients. + 6. MCData server initiates the MCData IPcon group request towards each MCData client determined in step 4. + 7. The receiving MCData clients 2 to n automatically accept the MCData IPcon group request and respond with MCData IPcon group response towards MCData server that contains the information if the request is accepted or the reason of rejection. If accepted, the MCData clients 2 to n will incorporate the time limit if required. + 8. MCData server forwards the MCData clients 2 to n accepted response to the MCData user of MCData client 1 who initiated the MCData IPcon group request. +- NOTE: The MCData client 1 considers the individual received time limits for discrimination purposes. +9. All involved MCData clients obtain the relevant IP addresses used for the MCData bearer service. + 10. All MCData clients exchange IP Data over the established media plane. The MCData server forwards the IP Data received from one MCData client to the target MCData client(s). + +#### 7.28.1.5.4.3 MCData IPcon group request + +Table 7.28.5.4.3-1 describes the information content of the MCData IPcon group request sent from the MCData client to the MCData server and from the MCData server to another MCData client. + +**Table 7.28.1.5.4.3-1: MCData IPcon group request** + +| Information element | Status | Description | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MCData ID | M | The MCData identity of the originator MCData user; | +| Functional Alias | O | The associated functional alias of the originator MCData user; | +| MCData group ID | M | The MCData group ID used for IP connectivity. | +| Application Priority | O | Contains the required application priority for the IP data communication. If not present, the MCData applies the predefined default application priority after reception of MCData IPcon response. | +| Location Information | O
(NOTE) | Actual location information of the originating MCData user; | +| Time Limit | O | Proposed time limit of the requested IP connectivity (1min- infinite); | +| NOTE: This information contains the latest available location information of the requesting MCData user that may be different to the latest available location information in the MC system. | | | + +#### 7.28.1.5.5 IP connectivity response + +##### 7.28.1.5.5.1 MCData IPcon response + +Table 7.28.1.5.5-1 describes the information content of the MCData IPcon data response as answer to MCData IPcon data request, applicable for point-to-point and group IP connectivity, exchanged between target MCData client and the originating MCData client. + +**Table 7.28.1.5.5-1: MCData IPcon data response** + +| Information element | Status | Description | +|----------------------------------------------------------------------------------------------------------|-------------|-------------------------------------------------------------------------------------------------------------| +| MCData ID | M | The MCData identity of the MCData user that has been addressed to establish an IP connectivity; | +| Functional Alias | O | The associated functional alias of the MCData user that has been addressed to establish an IP connectivity. | +| MCData ID | M | The MCData identity of the MCData user that asked to establish an IP connectivity; | +| Functional Alias | O | The associated functional alias of the MCData user that asked to establish an IP connectivity. | +| Time Limit | O
(NOTE) | Negotiated time (1 min – infinite) | +| Establishment reason | M | IP connectivity establishment reason | +| NOTE: The time limit is provided if the IPcon point-to-point request contained this information element. | | | + +#### 7.28.1.6 Functional model update + +IP connectivity as a new service requires the integration into the general MCData functional model and a detailed description as an IP connectivity functional model. Currently, IP connectivity is considered as an on-network service only. + + + +Figure 7.28.1.6-1: IP connectivity service in the On-network functional model. This diagram shows the functional architecture for IP connectivity. On the left, three external entities are connected to an MCDData server: 'Other MCDData server' via reference point MCDData-3, 'MCDData user database' via MCDData-2, and 'Interworking function to LMR system' via IWF-2. The MCDData server contains a 'Capability functions (SDS, FD, DS, IPcon)' block. This block connects to an 'MCDData UE' on the right via several reference points: MCDData-cap-1, MCDData-cap-n, MCDData-5 (labeled Rx), and MCDData-6 (labeled MB2C). The MCDData server also connects to an 'MCDData message store' via MCDData-8. The message store connects to the 'MCDData UE' via MCDData-7. The 'MCDData UE' contains an 'MCDData client' with 'Capability functions (SDS, FD, DS, IPcon)' and a 'Message store client'. All internal components and external connections pass through a central vertical bar labeled 'EPS'. + +**Figure 7.28.1.6-1: IP connectivity service in the On-network functional model** + +Figure 7.28.1.6-2 depicts the application plane functional model for IP connectivity. + + + +Figure 7.28.1.6-2: Application plane functional model for IP connectivity On-network. This diagram shows the application plane functional model. On the left, an 'MCDData server' contains an 'IPcon distribution function' and a 'Transmission / Reception control' block. The 'IPcon distribution function' connects to an 'MCDData UE' on the right via three reference points: MCDData-IPcon-1, MCDData-IPcon-2, and MCDData-IPcon-3. The 'MCDData UE' contains an 'MCDData client' with an 'IPcon function'. All internal components and external connections pass through a central vertical bar labeled 'EPS'. + +**Figure 7.28.1.6-2: Application plane functional model for IP connectivity On-network** + +In the model shown in figure 7.28.1.6-2, the following apply: + +- MCDData-IPcon-1 reference point is used for MCDData application signalling for establishing a session in support of MCDData IP connectivity. +- MCDData-IPcon-2 reference point carries bidirectional IP Data for point-to-point MCDData IP connectivity over the media plane between the IPcon distribution function of the MCDData server and the IPcon function of the MCDData client(s). +- MCDData-IPcon-3 reference point carries simultaneous bidirectional IP Data between multiple MCDData clients over the media plane between the IPcon distribution function of the MCDData server and the IPcon function of the MCDData client(s). + +## 7.28.2 Solution evaluation + +The proposed solution allows the use for two or more MCDData clients to participate in an IP connectivity session. The MCDData client is addressed by means of MCDData ID or optionally by means of a functional alias. IP connectivity can be limited in time by default. + +Editor's note: The withdrawal of an IP connectivity connection by an authorized user is FFS. + +Editor's note: The remote initiation of IP connectivity service is FFS. + +Editor's note: The control of QoS based on per packet priority is FFS. + +Editor's note: The impact of IP connectivity services on interworking is FFS. + +## 7.29 Solution 29 – Call forwarding and call transfer for private calls + +### 7.29.1 Solution description + +#### 7.29.1.1 General + +This solution addresses a key issue listed in subclause 5.26 on call forwarding and call transfer for private calls. It is based on the similar concepts as used by the TAS services in public networks for public users, but they are adapted to support the service functionality based on MCPTT IDs. Additionally the scope is limited to cover only the small subset of services needed by the mission critical user community. + +Stage 1 requirements have been defined requesting support for call forwarding and call transfer for private calls with and without floor control. The requirements are defined in 3GPP TS 22.179 [3] [R-5.6.3-014], [R-5.6.3-015], [R-6.7.4-015], and [R-6.7.4-016.] + +#### 7.29.1.2 Call forwarding unconditional + +Figure 7.29.1.2-1 below illustrates the procedure of call forwarding unconditional of private calls. + +Pre-conditions: + +1. MCPTT client 2 is authorized to use call forwarding and has call forwarding unconditionally enabled with the destination MCPTT client 3. +2. MCPTT client 2 is authorized to make private calls to MCPTT client 3. + + + +``` + +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. MCPTT server verifies that client2 is authorized to unconditionally forward the call to client3 + C1->>S: 1. MCPTT private call request + S->>C3: 3. MCPTT private call request with redirection info + S->>C1: 4. MCPTT Forwarding Indication + C3->>S: 5. MCPTT ringing + S->>C1: 6. MCPTT ringing + C3->>S: 7. MCPTT answer + S->>C1: 8. MCPTT answer + Note over C1, C3: 9. Media Plane Established between client 1 and 3 + +``` + +Sequence diagram for unconditional call forwarding. Lifelines: MCPTT Client 1, MCPTT Server, MCPTT Client 2, MCPTT Client 3. The sequence shows Client 1 sending a request to the Server, which then checks Client 2's forwarding settings. Upon finding it enabled, the Server sends a redirected request to Client 3. Client 3 rings and answers, and the Server then rings and answers on behalf of Client 1. Finally, a media plane is established between Client 1 and Client 3. + +**Figure 7.29.1.2-1: Call forwarding unconditional** + +1. The 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 unconditionally enabled. +3. The MCPTT server sends a MCPTT private call request with redirection information towards the MCPTT client 3. +4. The MCPTT server sends a MCPTT forwarding indication to MCPTT client 1. +5. MCPTT client 3 is alerted. MCPTT client 3 sends an MCPTT ringing to the MCPTT server. +6. The MCPTT server sends an MCPTT ringing to the MCPTT client 1. +7. The MCPTT user at MCPTT client 3 has accepted the call, which causes MCPTT client 3 to send an MCPTT answer to the MCPTT server. +8. The MCPTT server sends an MCPTT answer to MCPTT client1 indicating that client3 has accepted the call. +9. The media plane for communication is established. + +### 7.29.1.3 Call forwarding no reply + +Figure 7.29.1.3-1 below illustrates the procedure for call forwarding no reply of private calls. + +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 2 is authorized to make private calls to MCPTT client3. + + + +``` + +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. MCPTT server verifies that client2 has +subscribed to forward on no answer service +A timer with for the no answer timeout is +started + + C1->>S: 1. MCPTT private call request +(manual commencement) + S->>C2: 3.MCPTT private call request +(manual commencement) + C2->>S: 4. MCPTT ringing + S->>C1: 5. MCPTT ringing + Note right of S: 6. MCPTT client2 does not answer +within the specified time interval + S->>C3: 7. MCPTT private call request +with redirection info + C3->>S: 9. MCPTT ringing + S->>C1: 8. MCPTT Forwarding Indication + S->>C1: 10 . MCPTT ringing + C3->>S: 11. MCPTT answer + S->>C1: 12. MCPTT answer + Note over C1, S, C2, C3: 13. Media Plane Established between client 1 and 3 + +``` + +Sequence diagram illustrating the call forwarding no reply for a private call between MCPTT Client 1, MCPTT Server, MCPTT Client 2, and MCPTT Client 3. + +**Figure 7.29.1.3-1: Call forwarding no reply for private call** + +1. The 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. +3. The MCPTT server sends a MCPTT private call request towards the MCPTT client 2. +4. 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. +6. The MCPPT server becomes aware that MCPTT client 2 does not answer within the specified time interval. + +7. The MCPTT server sends a MCPTT private call request with redirection information towards the MCPTT client 3. +8. The MCPTT server sends a MCPTT forwarding indication to MCPTT client 1. +9. MCPTT client 3 is alerted. MCPTT client 3 sends an MCPTT ringing to the MCPTT server. +10. The MCPTT server sends an MCPTT ringing to the MCPTT client 1. +11. The MCPTT user at MCPTT client 3 has accepted the call, which causes MCPTT client 3 to send an MCPTT answer to the MCPTT server. +12. The MCPTT server sends an MCPTT answer to MCPTT client 1 indicating that client3 has accepted the call. +13. The media plane for communication is established. + +#### 7.29.1.4 Call forwarding not reachable + +Figure 7.29.1.4-1 below illustrates the procedure for call forwarding not reachable of private calls + +Pre-conditions: + +1. MCPTT client 2 is authorized to use call forwarding and has call forwarding not reachable enabled with the destination MCPTT client 3. +2. MCPTT client 2 is authorized to make private calls to MCPTT client 3. + + + +The sequence diagram illustrates the interaction between MCPTT Client 1, MCPTT Server, MCPTT Client 2 (not reachable), and MCPTT Client 3. The process starts with Client 1 sending a request to the Server. The Server then attempts to reach Client 2, but fails. Upon detecting unreachability, the Server checks if Client 2 has call forwarding enabled. Since it is, the Server forwards the request to Client 3. Client 3 rings and answers, and the Server then informs Client 1 of the forwarding. Finally, a media plane is established between Client 1 and Client 3. + +``` +sequenceDiagram + participant Client1 as MCPTT Client 1 + participant Server as MCPTT Server + participant Client2 as MCPTT Client 2 (not reachable) + participant Client3 as MCPTT Client 3 + + Note right of Server: 3. MCPTT server detects that MCPTT client 2 is not reachable + Note right of Server: 4. MCPTT server verifies that MCPTT client 2 has subscribed to forward on not reachable + + Client1->>Server: 1. MCPTT private call request + Server->>Client2: 2. MCPTT private call request + Note right of Server: 3. MCPTT server detects that MCPTT client 2 is not reachable + Note right of Server: 4. MCPTT server verifies that MCPTT client 2 has subscribed to forward on not reachable + Server->>Client3: 5. MCPTT private call request with redirection info + Client3->>Server: 7. MCPTT ringing + Server->>Client1: 6. MCPTT Forwarding Indication + Server->>Client1: 8. MCPTT ringing + Client3->>Server: 9. MCPTT answer + Server->>Client1: 10. MCPTT answer + Note bottom: 11. Media Plane Established between MCPTT client 1 and MCPTT client 3 +``` + +Sequence diagram for MCPTT private call forwarding when the reference source is not reachable. + +**Figure 7.29.1.4-1: Call forwarding not reachable for MCPTT private call** + +1. The MCPTT client 1 sends an MCPTT private call request towards the MCPTT server. +2. The MCPTT server sends a MCPTT private call request towards the MCPTT client 2. +3. The MCPTT server detects that MCPTT client 2 is not reachable. +4. The MCPTT server verifies that MCPTT client 2 has call forwarding not reachable enabled. +5. The MCPTT server sends a MCPTT private call request with redirection information towards the MCPTT client 3. + +6. The MCPTT server sends a MCPTT forwarding indication to MCPTT client 1. +7. MCPTT client 3 is alerted. MCPTT client 3 sends an MCPTT ringing to the MCPTT server. +8. The MCPTT server sends an MCPTT ringing to the MCPTT client 1. +9. The MCPTT user at MCPTT client 3 has accepted the call, which causes MCPTT client 3 to send an MCPTT answer to the MCPTT server. +10. The MCPTT server sends an MCPTT answer to MCPTT client 1 indicating that client3 has accepted the call. +11. The media plane for communication is established. + +#### 7.29.1.5 Call deflection + +Figure 7.29.1.5-1 below illustrates the procedure for call deflection of private calls. + +Pre-conditions: + +1. MCPTT client 2 is authorized to use call deflection. +2. MCPTT client 2 is authorized to make private calls to MCPTT client 3. + + + +``` + +sequenceDiagram + participant C1 as MCPTT Client 1 + participant S as MCPTT Server + participant C2 as MCPTT Client 2 + participant C3 as MCPTT Client 3 + + C1->>S: 1. MCPTT private call request + S->>C2: 2. MCPTT private call request + C2->>S: 3. MCPTT ringing + S->>C1: 4. MCPTT ringing + C2->>S: 5. MCPTT call deflection request + Note over S: 6. MCPTT server verifies that +client2 is authorized to deflect +the call to client3 + S->>C3: 7. MCPTT private call +request with deflection info + S->>C1: 8. MCPTT Forwarding +Indication + C3->>S: 9. MCPTT answer + S->>C1: 10. MCPTT answer + Note over C1,C3: 11. Media Plane Established between client 1 and 3 + +``` + +The diagram illustrates a sequence of interactions for call deflection in MCPTT. It involves four lifelines: MCPTT Client 1, MCPTT Server, MCPTT Client 2, and MCPTT Client 3. The sequence starts with Client 1 sending a private call request to the server. The server then requests the call to Client 2. Client 2 responds with ringing, which the server relays to Client 1. Client 2 then sends a call deflection request to the server. The server performs an authorization check. Upon approval, the server sends a private call request with deflection info to Client 3. The server sends a forwarding indication to Client 1. Client 3 answers, and the server relays the answer to Client 1. Finally, the media plane is established between Client 1 and Client 3. + +Sequence diagram for MCPTT private call deflection + +**Figure 7.29.1.5-1: Call deflection for MCPTT private call** + +1. The MCPTT client 1 sends an MCPTT private call request towards the MCPTT server. +2. The MCPTT server sends a MCPTT private call request towards the MCPTT client 2. +3. MCPTT client 2 is alerted. MCPTT client 2 sends an MCPTT ringing to the MCPTT server. +4. The MCPTT server sends an MCPTT ringing to the MCPTT client 1. +5. The MCPTT client 2 sends a call deflection request to the MCPTT server. +6. The MCPTT server verifies that MCPTT client 2 is authorized to perform call deflection. +7. The MCPTT server sends a MCPTT private call request with redirection information towards the MCPTT client 3. +8. The MCPTT server sends a MCPTT Forwarding Indication to MCPTT client 1. +9. The MCPTT user at MCPTT client 3 has accepted the call, which causes MCPTT client 3 to send an MCPTT answer to the MCPTT server. + +10. The MCPTT server sends an MCPTT answer to MCPTT client 1 indicating that client3 has accepted the call. +11. The media plane for communication is established. + +### 7.29.1.6 Call transfer unattended + +Figure 7.29.1.6-1 below illustrates the procedure for call transfer unattended of private calls + +Pre-conditions: + +1. MCPTT client2 is authorized to use call transfer. +2. MCPTT client1 is authorized to make private calls to client2 and to client3. + + + +``` +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: 8. MCPTT server verifies that client2 is authorized to transfer the call to client3 + + C1->>S: 1. MCPTT private call request + S->>C2: 2. MCPTT private call request + C2->>S: 3. MCPTT ringing + S->>C1: 4. MCPTT ringing + C2->>S: 5. MCPTT answer + S->>C1: 6. MCPTT answer + S->>C2: 7. MCPTT Call Transfer request + Note right of S: 8. MCPTT server verifies that client2 is authorized to transfer the call to client3 + S->>C3: 9. MCPTT private call request with transfer information + C3->>S: 10. MCPTT ringing + C3->>S: 11. MCPTT answer + S->>C2: 12. MCPTT server releases the connection with client2. + Note bottom: 13. Media Plane Established between client 1 and 3 +``` + +The sequence diagram illustrates the interaction between MCPTT Client 1, MCPTT Server, MCPTT Client 2, and MCPTT Client 3 for an unattended call transfer. The process begins with Client 1 sending a private call request to the server. The server then requests the call from Client 2, who rings and answers. Client 1 also rings and answers. The server then sends a call transfer request to Client 2. A note indicates the server verifies Client 2's authorization to transfer to Client 3. The server then sends a private call request with transfer information to Client 3. Client 3 rings and answers. Finally, the server releases the connection with Client 2, and a note indicates the media plane is established between Client 1 and Client 3. + +Sequence diagram for call transfer unattended for MCPTT private call + +**Figure 7.29.1.6-1: Call transfer unattended for MCPTT private call** + +1. The MCPTT client 1 sends an MCPTT private call request towards the MCPTT server. +2. The MCPTT server sends a MCPTT private call request towards the MCPTT client2. + +3. MCPTT client 2 is alerted. MCPTT client 2 sends an MCPTT ringing to the MCPTT server. +4. The MCPTT server sends an MCPTT ringing to the MCPTT client 1. +5. The MCPTT user at MCPTT client 2 has accepted the call, which causes MCPTT client 2 to send an MCPTT answer to the MCPTT server. +6. The MCPTT server sends an MCPTT answer to MCPTT client 1 indicating that MCPTT client 2 has accepted the call. +7. The MCPTT user at MCPTT client 2 wants to transfer the call and send a MCPTT transfer request to the MCPTT server. +8. The MCPTT server verifies that MCPTT client 2 is authorized to transfer the MCPTT private call to MCPTT client 3. +9. The MCPTT server sends a MCPTT private call request with transfer information towards the MCPTT client 3. +10. MCPTT client 3 is alerted. MCPTT client 3 sends an MCPTT ringing to the MCPTT server. +11. The MCPTT user at MCPTT client 3 has accepted the call, which causes MCPTT client 3 to send an MCPTT answer to the MCPTT server. +12. The MCPTT server releases the call with MCPTT client 2. +13. The media plane for communication is established. + +#### 7.29.1.7 Call transfer attended + +Figure 7.29.1.7-1 below illustrates the procedure for call transfer attended of private calls + +Pre-conditions: + +1. MCPTT client 2 is authorized to use call transfer. +2. MCPTT client 1 is authorized to make private calls to MCPTT client 2 and MCPTT client 3. MCPTT client 2 is authorized to make private calls to MCPTT client 3. + + + +``` + +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 left of S: 10. MCPTT server verifies that client2 and client3 can participate in the call + Note left of S: 16. MCPTT server verifies that client2 is authorized to transfer the client1 to client3 and connects them + Note left of S: 18. MCPTT server connects transferred party and transfer target + + C1->>S: 1. MCPTT private call request + S->>C2: 2. MCPTT private call request + C2->>S: 3. MCPTT ringing + S->>C1: 4. MCPTT ringing + C2->>S: 5. MCPTT answer + S->>C1: 6. MCPTT answer + C2->>S: 7. Call hold + S->>C1: 8. Call held + C2->>S: 9. MCPTT private call request + Note left of S: 10. MCPTT server verifies that client2 and client3 can participate in the call + S->>C3: 11. MCPTT private call request + C3->>S: 12. MCPTT ringing + C3->>S: 13. MCPTT answer + S->>C2: 14. MCPTT answer + C2->>S: 15. MCPTT Call Transfer request + Note left of S: 16. MCPTT server verifies that client2 is authorized to transfer the client1 to client3 and connects them + S->>C2: 17. MCPTT Call release + Note left of S: 18. MCPTT server connects transferred party and transfer target + Note right of C3: 19. Media Plane Established between client1 and client3 + +``` + +Sequence diagram for MCPTT private call transfer attended. Lifelines: MCPTT Client 1, MCPTT Server, MCPTT Client 2, MCPTT Client 3. The sequence shows Client 1 requesting a call, Client 2 being invited, then Client 1 requesting a transfer to Client 3, which is then established by the server. + +**Figure 7.29.1.7-1: Call transfer attended for MCPTT private call** + +1. The MCPTT client 1 sends an MCPTT private call request towards the MCPTT server. +2. The MCPTT server sends a MCPTT private call request towards the MCPTT client 2. + +3. MCPTT client 2 is alerted. MCPTT client 2 sends an MCPTT ringing to the MCPTT server. +4. The MCPTT server sends an MCPTT ringing to the MCPTT client 1. +5. The MCPTT user at MCPTT client 2 wants to transfer the call and send a MCPTT transfer request to the MCPTT server. +6. The MCPTT server sends an MCPTT answer to MCPTT client 1 indicating that MCPTT client 2 has accepted the call. +7. The MCPTT client 2 sends a Call hold request to the MCPTT server. +8. The MCPTT server sends a Call hold request to the MCPTT client 1. +9. The MCPTT client 2 sends an MCPTT private call request towards the MCPTT server. +10. The MCPTT server verifies that MCPTT client 2 is authorized to make a MCPTT private call to MCPTT client 3. +11. The MCPTT server sends a MCPTT private call request towards the MCPTT client 3. +12. MCPTT client 3 is alerted. MCPTT client 3 sends an MCPTT ringing to the MCPTT server. +13. The MCPTT user at MCPTT client 3 has accepted the call, which causes MCPTT client 3 to send an MCPTT answer to the MCPTT server. +14. The MCPTT sends an MCPTT answer to MCPTT client 3. +15. Now the MCPTT user at MCPTT client 3 decides to perform the actual transfer by sending a MCPTT call transfer request to the MCPTT server. +16. The MCPTT server verifies that MCPTT client 2 is authorized to transfer the MCPTT private call to MCPTT client 3. +17. The MCPTT server releases the call with MCPTT client 2. +- 18 The MCPTT server connects the transferred party and the transfer target. +19. The media plane for communication is established. + +#### 7.29.1.8 Call transfer with temporary three-way call + +Figure 7.29.1.8-1 below illustrates the procedure for call transfer with temporary tree-way call for private calls + +Pre-conditions: + +1. MCPTT client 2 is authorized to use call transfer. +2. MCPTT client 1 is authorized to make private calls to MCPTT client 2 and MCPTT client 3. MCPTT client 2 is authorized to make private calls to MCPTT client 3. + + + +``` + +sequenceDiagram + participant C1 as MCPTT Client 1 + participant S as MCPTT Server + participant C2 as MCPTT Client 2 + participant C3 as MCPTT Client 3 + + C1->>S: 1. MCPTT private call request + S->>C2: 2. MCPTT private call request + C2->>S: 3. MCPTT ringing + S->>C1: 4. MCPTT ringing + C2->>S: 5. MCPTT answer + S->>C1: 6. MCPTT answer + S->>C2: 7. MCPTT Call Transfer request + Note over S, C2: 8. MCPTT server verifies that client2 is authorized to transfer the call to client3 + S->>C3: 9.. MCPTT private call request with transfer information + C3->>S: 10. MCPTT ringing + C3->>S: 11. MCPTT answer + Note over S, C2: 12. Client1, Client2 and Client3 are connected in a temporary conference + rect rgb(255, 255, 255) + Note over C1, C3: 13. Media Plane Established between client1, client2 and client3 + end + Note over S, C2: 14a: MCPTT server releases the connection with client2. +14b: Client2 decides when to leave the call + S->>C2: + C2->>S: + rect rgb(255, 255, 255) + Note over C1, C3: 15. Media Plane Established between client 1 and 3 + end + +``` + +Sequence diagram illustrating a call transfer with a temporary three-way call for MCPTT private call. The diagram shows interactions between MCPTT Client 1, MCPTT Server, MCPTT Client 2, and MCPTT Client 3. The process involves a private call request from Client 1 to the Server, which then requests a call from Client 2. Client 2 rings and answers. The Server then rings Client 1, who answers. The Server then sends a call transfer request to Client 2. The Server verifies that Client 2 is authorized to transfer the call to Client 3. The Server then sends a private call request with transfer information to Client 3. Client 3 rings and answers. The Server then connects Client 1, Client 2, and Client 3 in a temporary conference. The Media Plane is established between Client 1, Client 2, and Client 3. The Server releases the connection with Client 2. Client 2 decides when to leave the call. Finally, the Media Plane is established between Client 1 and Client 3. + +**Figure 7.29.1.8-1: Call transfer with temporary three-way call for MCPTT private call** + +1. The MCPTT client 1 sends an MCPTT private call request towards the MCPTT server. +2. The MCPTT server sends a MCPTT private call request towards the MCPTT client 2. +3. MCPTT client 2 is alerted. MCPTT client 2 sends an MCPTT ringing to the MCPTT server. +4. The MCPTT server sends an MCPTT ringing to the MCPTT client 1. +5. The MCPTT user at client 2 has accepted the call, which causes MCPTT client 2 to send an MCPTT answer to the MCPTT server. + +6. The MCPTT server sends an MCPTT answer to client1 indicating that MCPTT client 2 has accepted the call. +7. The MCPTT user at MCPTT client 2 wants to transfer the call and send a MCPTT transfer request to the MCPTT server. +8. The MCPTT server verifies that MCPTT client 2 is authorized to transfer the MCPTT private call to MCPTT client 3. +9. The MCPTT server sends a MCPTT private call request with transfer information towards the MCPTT client 3. +10. MCPTT client 3 is alerted. MCPTT client 3 sends an MCPTT ringing to the MCPTT server. +11. The MCPTT user at MCPTT client 3 has accepted the call, which causes MCPTT client 3 to send an MCPTT answer to the MCPTT server. +12. Now MCPTT client 1, MCPTT client 2, and MCPTT client 3 are put in a temporary conference. +13. The media plane for communication is established between all involved parties. +14. The call to MCPTT client 2 can be released either server initiated or triggered by MCPTT client 2. +15. The media plane for communication is established between MCPTT client 1 and MCPTT client 3. + +The MCPTT user profile configuration data in Annex A.3 of 3GPP TS 23.379 [7] is enhanced by the following parameters to support call forwarding and call transfer functionality. + +**Table 7.29.1.8-1: MCPTT user profile data (on and off network)** + +| Reference | Parameter description | MCPTT UE | MCPTT Server | Configuration management server | MCPTT user database | +|-----------|------------------------------------------------------------------------|----------|--------------|---------------------------------|---------------------| +| | Allow private call forwarding | | Y | Y | Y | +| | Allow private call transfer | | Y | Y | Y | +| | Call Forwarding NoAnswer Timeout | Y | Y | Y | Y | +| | Call Forwarding List containing pairs of target MCPTT ID and condition | | Y | Y | Y | + +Because the forwarding/transfer is done based on MCPTT user identities, the related details have to be visible for the affected MCPTT users. Therefore, for conveying redirection-related information the following new parameters will be introduced in mcpttinfo. + +- Mcptt redirecting ID +- Mcptt redirection target ID + +Additionally, to support the transfer functionality the existing parameter
(subclause
reference) | Dependency on
other working
groups | +|----------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------|---------------------------------------------------| +| Key issue #1 - Allowed private communications | Solution #1 – Restricting incoming private communications | 7.1.2 | None | +| Key issue #2 - Dynamic group changes based on pre-configured conditions | Solution #3 – Client performs automatic group affiliation/de-affiliation | 7.3.2 | None | +| Key issue #3 - Arbitration of incoming communications | Solution #30 – Arbitration of incoming communications | 7.30.2 | None | +| Key issue #4 - Providing data for a user entering an ongoing MCData group conversation | Addressed by eMCData2 | | | +| Key issue #5 - Communication priority for functional aliases | Solution #33 – Communication priority for functional aliases | 7.33.2 | None | +| Key issue #6 - Network initiated activation and de-activation of functional alias(es) | Solution #2 – Implicit activation and deactivation of functional alias(es) | 7.2.2 | None | +| Key issue #8-1 - Emergency and imminent peril groups | Solution #5 – Support of functional aliases in emergency and imminent peril groups calls | 7.5.2 | None | +| Key issue #8-2 - Private calls and private emergency calls | Solution #4 – Support of functional aliases in private calls and private emergency calls
Solution #19 – Support of functional aliases in private calls and private emergency calls | 7.4.2, 7.19.2 | None | +| Key issue #8-3 - Temporary voice group calls | Solution #6 – Support of functional aliases in temporary voice group calls | 7.6.2 | None | +| Key issue #8-4 - Ambient listening and remotely initiated calls | (see NOTE) | | | +| Key issue #8-5 – Use of location dependent functional aliases for private calls | Solution #31 – Client performs automatic activation and deactivation of functional aliases based on location | 7.31.2 | None | +| Key issue #8-6 – Call restrictions when using functional aliases for private calls | Solution #4 – Support of functional aliases in private calls and private emergency calls | 7.4.2 | None | +| Key issue #8-7 – Multiple use of a functional alias for private calls | Solution #9 – Solution to support multiple functional alias use in private calls | 7.9.2 | None | +| Key issue #8-8 – Limit the number of parallel emergency group communications | Solution #5 – Support of functional aliases in emergency and imminent peril groups calls | 7.5.2 | None | +| Key issue #9 - Functional alias used via broadcast | Solution #8 – Solution to support functional alias via broadcast group calls | 7.8.2 | None | +| Key issue #10 - Functional alias using off-network communication mode | (see NOTE) | | | +| Key issue #11 - Multiple functional alias use | Solution #9 – Solution to support multiple functional alias use in private calls | 7.9.2 | None | +| Key issue #12-1 - Short data service (SDS) | Solution #15 – Support functional aliases for SDS
Solution #22 – Support functional alias controlling for MCData services | 7.16.2, 7.22.2 | None | +| Key issue #12-2 - File distribution (FD) | Solution #16 – Support functional aliases for File distribution (FD)
Solution #22 – Support functional alias controlling for MCData services | 7.16.2, 7.22.2 | None | +| Key issue #12-3 - Control functions | Solution #17 – Support functional aliases within MCData control procedures
Solution #22 – Support functional alias controlling for MCData services | 7.17.2, 7.22.2 | None | +| Key issue #13-1 - Video group calls | Solution #20 – Support of functional aliases for video group calls
Solution #23 – Support functional alias controlling for MCVideo service | 7.20.2, 7.23.2 | None | + +| Key issues | Solution | Evaluation
(subclause
reference) | Dependency on
other working
groups | +|---------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------|---------------------------------------------------| +| Key issue #13-2 - Video emergency group calls | Solution #18 – Support of functional aliases for video emergency group calls
Solution #23 – Support functional alias controlling for MCVideo service | 7.18.2, 7.23.2 | None | +| Key issue #13-3 - Video emergency private calls | Solution #21 – Support of functional aliases for private and emergency video calls
Solution #23 – Support functional alias controlling for MCVideo service | 7.21.2, 7.23.2 | None | +| Key issue #13-4 - Video control functions | The use of functional aliases is not required. | | | +| Key issue #13-5 - Ambient viewing call | (see NOTE) | | | +| Key issue #14 - Location information of an MC service user using a specific functional alias | Solution #10 – Location information for a specific functional alias | 7.10.2 | None | +| Key issue #15 - Prevent de-affiliation when using a specific functional alias(es) | Solution #11 – MC service server prevents de-affiliation when using a specific functional alias(es) | 7.11.2 | None | +| Key issue #16-1 - Functional alias and alternative addressing scheme for interworking with GSM-R | Solution #7 – Architecture to support GSM-R interworking | 7.7.2 | None | +| Key issue #16-2 - Interworking between MCPTT group call and advanced speech call items used in GSM-R | Solution #7 – Architecture to support GSM-R interworking | 7.7.2 | None | +| Key issue #16-3 - Private call between an MCPTT user and a GSM-R mobile station or controller | Solution #7 – Architecture to support GSM-R interworking | 7.7.2 | None | +| Key issue #16-4 - Bi-directional interworking for MCPTT user positioning information and location information provided for a GSM-R mobile station | Solution #7 – Architecture to support GSM-R interworking | 7.7.2 | None | +| Key issue #16-5 - Bi-directional interworking between MCData SDS and GSM-R SMS | | | | +| Key issue #17 – Provide a list of currently affiliated members of an MC service group associated with the activated functional alias(es) | Solution #12 – List of functional aliases used by affiliated group members | 7.12.2 | None | +| Key issue #18 – List of MCPTT group members who did not acknowledge the group call request | Solution #13 – List of MCPTT group members who did not acknowledge the group call request | 7.13.2 | None | +| Key issue #19 – Limit the number of simultaneous successful service authorizations | Solution #14 – MC service server limits the number of simultaneous successful service authorisations | 7.14.2 | None | +| Key issue #20 – User requests application layer priorities | Solution #26 – User requests application layer priorities | 7.26.2 | None | +| Key issue #21 – Group creation using functional aliases | (see NOTE) | | | +| Key issue #23 – Gateway UE function | Solution #27 – MC gateway UE | | | +| Key issue #22 – Application layer IP connectivity | Solution #28 – IP connectivity | 7.28.2 | None | +| Key issue #24 – Automatic start of an emergency group communication after an emergency group alert | Solution #25 – Triggering an emergency group communication after an emergency alert automatically | 7.25.2 | None | +| Key issue #25 – Additional commencement conditions for MCPTT group call setup | Solution #24 – Additional commencement modes for MCPTT Group calls | 7.24.2 | None | +| Key issue #26 – Call forwarding and call transfer for private calls | Solution #25 – Call forwarding and call transfer for private calls | 7.25.2 | None | + +NOTE: Less important for railways, related work can be shifted towards a later release. + +--- + +## 9 Conclusions + +This technical report fulfills the objectives of the study on an application architecture for the Future Railway Mobile Communication System (FRMCS) Phase 2, including the following: + +- 1) Identification of key issues (clause 5) and architecture requirements (clause 6). +- 2) Interworking scenarios with GSM-R (clause 4). +- 3) Individual solutions (clause 7) addressing the key issues (clause 5) +- 4) Overall evaluation (clause 8) of all the solutions and dependencies on other 3GPP groups identified in the overall evaluation which are required for fulfilling the solutions (clause 7). + +The results from the study will be considered for follow-up normative work in Release 16 as follows: + +The following solutions will be used as basis for technical specification: + +- Solution 1 on restricting incoming private communications (subclause 7.1) +- Solution 2 on implicit activation and deactivation of functional alias(es) (subclause 7.2) +- Solution 3 on client performs automatic group affiliation/de-affiliation (subclause 7.3) +- Solution 4 on support of functional aliases in private calls and private emergency calls (subclause 7.4) and solution 19 on support of functional aliases in private calls and private emergency calls (subclause 7.19) +- Solution 5 on support of functional aliases in emergency and imminent peril groups calls (subclause 7.5) +- Solution 8 on solution to support functional alias via broadcast group calls (subclause 7.8) +- Solution 9 on solution to support multiple functional alias use in private calls (subclause 7.9) +- Solution 10 on location information for a specific functional alias (subclause 7.10) +- Solution 11 on MC service server prevents de-affiliation when using a specific functional alias(es) (subclause 7.11) +- Solution 12 on list of functional aliases used by affiliated group members (subclause 7.12) +- Solution 13 on list of MCPTT group members who did not acknowledge the group call request (subclause 7.13) +- Solution 14 on MC service server limits the number of simultaneous successful service authorisations (subclause 7.14) +- Solution 15 on support functional aliases for SDS (subclause 7.15) together with solution 22 on support functional alias controlling for MCData services (subclause 7.22) +- Solution 16 on support functional aliases for File distribution (FD) (subclause 7.16) together with solution 22 on support functional alias controlling for MCData services (subclause 7.22) +- Solution 17 on support functional aliases within MCData control procedures (subclause 7.17) together with solution 22 on support functional alias controlling for MCData services (subclause 7.22) +- Solution 18 on support of functional aliases for video emergency group calls (subclause 7.18) together with solution 23 on support functional alias controlling for MCVideo services (subclause 7.23) +- Solution 20 on support of functional aliases for video group calls (subclause 7.20) together with solution 23 on support functional alias controlling for MCVideo services (subclause 7.23) +- Solution 21 on support of functional aliases for private and emergency video calls (subclause 7.21) together with solution 23 on support functional alias controlling for MCVideo services (subclause 7.23) +- Solution 24 on additional commencement modes for MCPTT Group calls (subclause 7.24) + +- Solution 25 on triggering an emergency group communication after an emergency alert automatically (subclause 7.25) +- Solution 26 on user requests application layer priorities (subclause 7.26) +- Solution 28 on IP connectivity (subclause 7.28) +- Solution 29 on call forwarding and call transfer for private calls (subclause 7.29) +- Solution 30 on arbitration of incoming communications (subclause 7.30) +- Solution 31 on client activation and deactivation functional aliases based on location (subclause 7.31) +- Solution 32 on functional alias and alternative addressing scheme for interworking with GSM-R (subclause 7.32) +- Solution 33 on communication priority for functional aliases (subclause 7.33) + +No architecture requirements were identified (clause 6). + +There were no dependencies to other 3GPP groups identified in the overall evaluation (clause 8). + +--- + +## Annex A: List of normative stage 1 requirements + +### A.1 Overview + +This annex provides the list of normative stage 1 requirements applicable for the study. The requirements are grouped by functional areas. + +The annex shall provide an overview on the progress made and which requirements are not yet fulfilled. + +### A.2 Functional alias + +NOTE: The additions made to existing Rel-15 requirements are underlined. + +#### A.2.1 Description + +The normative stage 1 requirements for functional aliases are documented in 3GPP TS 22.280 [2]. + +#### A.2.2 Requirements + +Table A.2.2-1 contains the list requirements to support functional aliases. + +**Table A.2.2-1: Requirements to support functional alias** + +| Reference | Description | Solution | +|---------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| [R-5.9a-001] | If the MCX Service system supports functional aliases, then the MCX Service shall provide a mechanism for the MCX User to activate one or more functional alias(es) for use by the MCX Users within that MCX Service system (i.e. the primary MCX Service system of the functional alias). | Rel-15 | +| [R-5.9a-001a] | The MCX Service system shall be able to use the functional alias as a unique identifier for MCX Users as Participant of an MCX Service Group, e.g. to display a functional alias as speaker identification or for the use in group member lists. | R-15 | +| [R-5.9a-001b] | The MCX Service system shall provide a mechanism for an MCX User to assign a functional alias for use on an MCX Service Group. | R-15 | +| [R-5.9a-002] | If the MCX Service system supports functional aliases, the MCX User shall be reachable by its functional alias(es). | 7.4 Solution 4 –
Support of functional aliases in private calls and private emergency calls
7.19 Solution 19 –
Support of functional aliases in private calls and private emergency calls | +| [R-5.9a-002a] | An MCX User shall be reachable by its functional alias from the primary MCX system while migrated to partner MCX Service systems. | Not addressed within the present document. | +| [R-5.9a-003] | If the MCX Service system supports functional aliases, then the MCX Service shall provide a mechanism for the MCX User to deactivate a functional alias. | Rel-15 | +| [R-5.9a-004] | If the MCX Service system supports functional aliases, then the MCX Service shall upon request provide the MCX User a list of functional aliases from which the user can select for activation/deactivation.
NOTE: The list may contain functional aliases based on a certain context, like location of the MCX User, operational schedule, etc. | Rel-15 | +| [R-5.9a-005] | If an MCX Service system supports functional alias, the MCX Service shall provide a mechanism for an MCX Service Administrator to create, delete and manage functional aliases, and for each functional alias indicate either if it can be simultaneously active for multiple MCX Users up to a per-alias configurable number, or if it is allowed to be taken over by an authorized MCX User, or none of these two options. | Rel-15 | +| [R-5.9a-006] | If a MCX User attempts to activate a functional alias that is already active for another MCX User, and is not allowed to be simultaneously active for multiple MCX Users or the number of simultaneous MCX Users is reached to the upper limit, the MCX Service shall inform the MCX User that the functional alias is already in use. | Rel-15 | +| [R-5.9a-007] | If an MCX User attempts to activate a functional alias that is already active for at least one other MCX User, and that functional alias is allowed to be simultaneously active for multiple MCX Users and the upper limit of number of simultaneous MCX Users is not reached, the MCX Service shall activate the functional alias for the MCX user and inform all other MCX User(s) with the same functional alias. | Rel-15 | +| [R-5.9a-008] | If an authorized MCX User attempts to activate a functional alias that is already used by another MCX User, and that functional alias is allowed to be taken over, and is not indicated for simultaneous activation to multiple MCX Users, the MCX Service shall offer the MCX User to take over the functional alias from the MCX User using the alias. | Rel-15 | +| [R-5.9a-008a] | If an authorized MCX User attempts to activate a functional alias that is already active for at least one other MCX User, and the upper limit of number of simultaneous MCX Users is reached, the MCX Service shall reject the MCX User's request. | Rel-15 | +| [R-5.9a-009] | If an authorized MCX User takes over the functional alias that is already active for another MCX User, the MCX Service shall activate the functional alias to the MCX User and inform the previous MCX User that the alias has been deactivated. | Rel-15 | +| [R-5.9a-010] | If an MCX Service system supports functional alias, the MCX Service shall allow the MCX User to perform an activation of an unlisted functional alias. that is defined in the MCX Service system. | Rel-15 | +| [R-5.9a-011] | If an MCX Service system supports functional alias, then an authorized MCX User shall be able to interrogate the MCX Service System of the alias(es) active for a certain MCX User. | Rel-15 | +| [R-5.9a-012] | If an MCX Service system supports functional alias, the MCX Service shall | Rel-15 | + +| | | | +|--|------------------------------------------------------------------------------------------------------------------------------------------------------------|--| +| | provide a mechanism for an MCX Service Administrator to authorize a MCX User to activate, deactivate, interrogate and take over a functional alias. | | +|--|------------------------------------------------------------------------------------------------------------------------------------------------------------|--| + +| | | | +|--------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------| +| [R-5.9a-014] | The MCX Service shall allow the functional alias to be structured as a combination of organizationally meaningful elements (e.g. user.agency@organization.country, role.mission@department.company, function.equipment.ID@city, label1.label2.label3@firstname.lastname). | Rel-15 | +| [R-5.9a-015] | The MCX Service system shall allow an MCX Service Administrator to make use of information (e.g. operational schedules, locations, velocity or direction) from external sources to create or delete a functional alias. | Rel-15 | +| [R-5.9a-016] | The MCX Service system shall allow the MCX Service Administrator to assign a communication priority for a functional alias. | 7.30 Solution 30 – Communication priority for functional aliases | +| [R-5.9a-017] | The MCX Service system shall allow the MCX Service Administrator to assign a time limit to a functional alias after which the functional alias will be deactivated. | 7.2 Solution 2 – Implicit activation and deactivation of functional alias(es) | +| [R-5.9a-018] | The MCX Service shall support automatic activation and de-activation of a functional alias based on the operational criteria (e.g. MCX User ID, login/logoff from the MCX Service system, specific external information supplied by external systems). | 7.2 Solution 2 – Implicit activation and deactivation of functional alias(es) | +| [R-5.9a-019] | The MCX Service shall provide a mechanism for an MCX Service Administrator to define a functional alias with related geographic areas that can be associated to MCX Users for the purpose of routing Location dependent communications, as part of handling MCX Service Private Communication requests, when the receiving party is based on the MCX User's current Location. | 7.x Solution x – Client performs automatic activation and deactivation of functional aliases based on location | +| [R-5.9a-020] | The MCX Service shall provide a mechanism for an MCX Service Administrator to configure for a particular functional alias, a set of functional aliases under the same authority to which a Private Communication (without Floor control) can be made by an MCX User registered to this particular functional alias. | 7.4 Solution 4 – Support of functional aliases in private calls and private emergency calls | +| [R-5.9a-021] | The MCX Service shall provide a mechanism for an MCX Service Administrator to configure for a particular functional alias, a set of functional aliases under the same authority from which Private Communication (without Floor control) is allowed to an MCX User registered to this particular functional alias. | 7.4 Solution 4 – Support of functional aliases in private calls and private emergency calls | +| [R-5.9a-022] | For private calls to functional aliases the authorizations in clause 5.9a.2 shall replace the authorizations defined in clause 6.7.3. | No solution required. | +| [R-5.9a-023] | The MCX Service system shall be capable of handling private calls to functional aliases that are allowed to be simultaneously active for multiple MCX Users by using group call mechanisms and by using first-to-answer private call mechanisms. | 7.9 Solution 9 – Solution to support multiple functional alias use in private calls (uses first-to-answer model only) | +| [R-5.9a-024] | The MCX Service system shall enable an MCX Service Administrator to select the mechanism to be used for handling of private calls to functional aliases that are allowed to be simultaneously active for multiple MCX Users. | 7.9 Solution 9 – Solution to support multiple functional alias use in private calls (uses first-to-answer model only) | +| [R-5.9a-025] | The MCX Service system shall be able to provide a mechanism to inform the MCX User about the functional alias activation status (e.g. activation accepted, activation pending, activation rejected). | Rel-15 | +| [R-5.9a-026] | The MCX Service shall provide the functional alias(es) of the transmitting MCX Service Group Member that enter the communication late in accordance with sub-clause 5.3. | Rel-15 | +| [R-5.9a-027] | The MCX Service shall provide a Location information report for every authorized MCX User associated with one functional alias in accordance with sub-clause 6.12. | 7.10 Solution 10 – Location information for a specific functional alias | +| [R-5.9a-028] | The MCX Service shall provide the functional alias(es) associated with the MCX Service User ID, of the transmitting Participant to the receiving MCX Users (UEs) unless the transmitting Participant's identity is restricted in accordance with sub-clause 6.4.3. | Not addressed by the present document. | +| [R-5.9a-029] | The MCX Service shall provide, upon request, the list of currently affiliated members of an MCX group which encompasses the MCX Service User ID and the associated functional alias(es) of each member in accordance with sub-clause 6.4.5. | 7.12 Solution 12 – List of functional aliases used by affiliated group members | + +| | | | +|----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------| +| [R-5.9a-030] | The MCX Service shall provide a mechanism for the enforcement of uniqueness of a functional alias within a Mission Critical organisation in accordance with sub-clause 6.9. | Rel-15 | +| [R-6.4.4-003] | The MCX Service shall be able to prevent the MCX User having registered a specific Functional Alias from revoking their affiliation with a specific MCX Service Group. | 7.11 Solution 11 – MC service server prevents de-affiliation when using a specific functional alias(es) | +| [R-6.4.4-004] | The MCX Service shall be able to prevent the MCX User to revoke his affiliation with a specific MCX Service Group if the MCX User is the only MCX User in the MCX Service Group registered a specific Functional Alias. | 7.11 Solution 11 – MC service server prevents de-affiliation when using a specific functional alias(es) | +| [R-6.12-006] | The MCX Service shall provide a means for an authorized MCX User to activate a one-time Location information report of an MCX User and periodic Location information update reports of an MCX User or a specific Functional Alias . | 7.10 Solution 10 – Location information for a specific functional alias | +| [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, functional alias(es), 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). | Not addressed within the present document. | +| [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, change of Selected MCX Service Group and (de)activation of functional alias(es). | Not addressed within the present document. | + +## A.3 Multi-talker control + +### A.3.1 Description + +The normative stage 1 requirements for multi-talker control are documented in 3GPP TS 22.179 [3]. + +### A.3.2 General requirements + +Table A.3.2-1 contains the list of requirements applicable for multi-talker control. + +**Table A.3.2-1: General requirements to support multi-talker control** + +| Reference | Description | Solution | +|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------| +| [R-6.2.3.7.2-001] | An MCPTT Group shall be configurable to allow multi-talker control. | Rel-15 | +| [R-6.2.3.7.2-002] | The MCPTT Service shall provide a mechanism for multiple MCPTT Users to talk simultaneously in an MCPTT Group configured for multi-talker control. | Rel-15 | +| [R-6.2.3.7.2-003] | The MCPTT Service shall determine which Participant(s) are allowed to transmit to all other Participant(s) in an MCPTT Group configured for multi-talker control. | Rel-15 | +| [R-6.2.3.7.2-004] | The MCPTT Service shall support all Participant(s) to receive audio from all other Participant(s) that are transmitting in an MCPTT Group configured for multi-talker control. | Rel-15 | +| [R-6.2.3.7.2-005] | The MCPTT Service shall provide a mechanism for the MCPTT Administrator to configure the maximum number of simultaneous talkers in an MCPTT Group configured for multi-talker control. | Rel-15 | +| [R-6.2.3.7.2-006] | The MCPTT Service shall allow an authorized MCPTT User to change the maximum number of simultaneous talkers at any time during a group call in an MCPTT Group configured for multi-talker control. | Rel-15 | + +### A.3.3 Requesting permission to transmit + +Table A.3.3-1 contains the list of requirements for requesting a permission to transmit. + +**Table A.3.3-1: Requirements to request permission to transmit** + +| Reference | Description | Solution | +|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------| +| [R-6.2.3.7.3-001] | The MCPTT Service shall enable authorized Participants to request to transmit to an MCPTT Group configured for multi-talker control. | Rel-15 | +| [R-6.2.3.7.3-002] | At call setup the MCPTT Service shall provide a notification, for example audio and/or visual, to the MCPTT Group Member attempting to transmit that there are no other Group Members who have affiliated to the MCPTT Group configured for multi-talker control. | Rel-15 | +| [R-6.2.3.7.3-003] | The MCPTT Service shall determine the transmitting Participant(s) when there are simultaneous requests for permission to transmit within the same call for an MCPTT Group configured for multi-talker control. | Rel-15 | +| [R-6.2.3.7.3-004] | Following an MCPTT Request for permission to transmit on the Selected MCPTT Group configured for multi-talker control the MCPTT Service shall provide an Affiliated MCPTT Group Member that made and was granted the request an indication of being allowed to transmit. | Rel-15 | + +### A.3.4 Override an active MCPTT transmission + +Table A.3.4-1 contains the list of requirements to support overriding of active MCPTT transmissions. + +**Table A.3.4-1: Requirements to override an active MCPTT transmission** + +| Reference | Description | Solution | +|---------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------| +| [R-6.2.3.7.4.1-001] | If the number of MCPTT Users requesting the permission to talk exceeds the maximum number of simultaneous talkers in an MCPTT Group configured for multi-talker control, the MCPTT Service shall apply the override mechanism. | Rel-15 | +| [R-6.2.3.7.4.1-002] | The MCPTT Service shall enable MCPTT Administrators to create a priority hierarchy for determining what Participants, Participant types, and urgent transmission types shall be granted a request to override an active MCPTT transmission on an MCPTT Group configured for multi-talker control. | Rel-15 | +| [R-6.2.3.7.4.1-003] | The priority hierarchy used for granting a request to override an active MCPTT transmission on a group configured for multi-talker control shall contain at least four (4) levels. | Rel-15 | +| [R-6.2.3.7.4.1-004] | The transmitting Participant on an MCPTT Group configured for multi-talker control shall be determined by the relative priorities of the Participants and Call type based on priority (e.g. MCPTT Emergency). | Rel-15 | +| [R-6.2.3.7.4.1-005] | Transmission requests of Participants with insufficient relative priority shall be rejected. | Rel-15 | +| [R-6.2.3.7.4.1-006] | The MCPTT Service shall provide a mechanism for Participants, to override an active MCPTT transmission of a transmitting Participant when the priority level of the overriding Participant or Call type based on priority (e.g. MCPTT Emergency) are ranked higher than the priority level of the transmitting Participant or Call type based on priority for an MCPTT Group configured for multi-talker control. | Rel-15 | +| [R-6.2.3.7.4.1-007] | If an authorized Participant overrides an MCPTT transmission, the MCPTT Service shall provide a means of notifying the overridden Participant(s) that the transmission has been overridden for an MCPTT Group configured for multi-talker control. | Rel-15 | +| [R-6.2.3.7.4.1-008] | The MCPTT Service shall revoke the transmit permission of the overridden transmitting Participant on an MCPTT Group configured for multi-talker control. | Rel-15 | + +## A.4 Automatic user regrouping and dynamic group participation + +NOTE: The additions made to existing Rel-15 requirements are underlined. + +### A.4.1 Description + +The normative stage 1 requirements for automatic user regrouping and dynamic group participation are documented in 3GPP TS 22.280 [2]. + +## A.4.2 Automatic user regrouping + +Table A.4.2-1 contains the list of requirements applicable for automatic user regrouping. + +**Table A.4.2-1: Requirements to support automatic user regrouping** + +| Reference | Description | Solution | +|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------| +| [R-6.6.4.2-002] | The MCX Service shall provide a means for combining a multiplicity of MCX Users into a new, temporary group based on a parameter or a combination of parameters (e.g., particular geographic area, Participant type, initiation of urgent type communication such as MCX Emergency Alert or MCX Emergency Group Communication ). | 7.3 Solution 3 – Client performs automatic group affiliation/de-affiliation | +| [R-6.6.4.2-002a] | The MCX Service shall provide a means for automatically combining a multiplicity of MCX Users into a temporary MCX Service Group based on certain criteria. For example, the criteria may include one or more parameters from the list below:
- • A specific element or combination of specific elements in the functional alias of a MCX User
- • Location (including speed and heading) of a MCX User
- • Location or particular geographic area specified by an MCX Service Administrator
- • MCX Service configuration (e.g. MCX User responsible for a certain geographic area or MCX User responsible for a certain MCX Service Group)
- • A specific element or combination of specific elements in the functional alias of a MCX User
- • Location (including speed and heading) of a MCX User
- • Location or particular geographic area specified by an MCX Service Administrator
- • MCX Service configuration (e.g. MCX User responsible for a certain geographic area or MCX User responsible for a certain MCX Service Group)
(NOTE 1,
NOTE 2) | The MCData data streaming capability shall provide setup time of:
- Less than 1 second for immediate setup of a data communication.
- Less than 3 second for normal setup of a data communication. | Not addressed within the present document. | +| NOTE 1: Setup time of a communication is essential because of their safety related character. | | | +| NOTE 2: Communication setup encompasses the value of the elapsed time between the communication establishment request and the indication of successful communication establishment. | | | + +## A.7.4 IP connectivity + +The following stage 1 requirements are documented in 3GPP TS 22.282 [5]. + +**Table A.7.4-1: IP connectivity** + +| Reference | Description | Solution | +|---------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------| +| [R-5.5.2-001] | The MCData Service shall enable an MCData user to initiate transport of IP data towards a server in the network or another MCData user. | 7.28 Solution 28 – IP connectivity | +| [R-5.5.2-002] | The MCData Service shall enable incoming transport of IP data towards an MCData user, initiated by another MCData user. | 7.28 Solution 28 – IP connectivity | +| [R-5.5.2-003] |
The MCData Service shall enable an authorized person for an MCData user to authorize initiation of transport of IP data from that MCData user to specific destinations.
This authorization may be preconfigured or may be provided by the authorized person when IP data transport to a new destination is initiated.
Authorization may be revoked on demand by the authorized person.
| 7.28 Solution 28 – IP connectivity | +| [R-5.5.2-004] |The MCData Service shall enable a MCData user or authorized person for this MCData user to authorize initiation of incoming transport of IP data from specific other MCData users.
This authorization may be preconfigured or may be provided by the authorized person when IP data transport from a new destination is initiated.
Authorization may be revoked on demand by the authorized person.
| 7.28 Solution 28 – IP connectivity | +| [R-5.5.2-005] | The MCData Service shall support incoming and outgoing IP data transport for a MCData user with a higher per packet priority. | 7.28 Solution 28 – IP connectivity | +| [R-5.5.2-006] | The MCData Service shall enable an authorized person to remotely authorize the use of higher per packet priority for a particular MCData user. | 7.28 Solution 28 – IP connectivity | + +## A.8 List of other requirements + +NOTE: The additions made to existing Rel-15 requirements are underlined. + +### A.8.1 Mission critical common requirements + +The following stage 1 requirements are documented in 3GPP TS 22.280 [2]. + +**Table A.8.1-1: Allowed private communication partners** + +| Reference | Description | Solution | +|----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------| +| [R-6.7.3-007] | The MCX Service shall provide a mechanism for an MCX Service Administrator to configure for a particular authorized MCX User, a set of MCX Users under the same authority to which a Private Communication (without Floor control) can be made by this particular MCX User . | 7.1 Solution 1 – Restricting incoming private communications | +| [R-6.7.3-007a] | The MCX Service shall provide a mechanism for an MCX Service Administrator to configure for a particular authorized MCX User, a set of MCX Users under the same authority from which Private Communication (without Floor control) is allowed to this particular MCX User. | 7.1 Solution 1 – Restricting incoming private communications | + +**Table A.8.1-2: Railway emergency alert / communication functionality** + +| Reference | Description | Solution | +|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------| +| [R-5.4.2-007a] | Depending on meaningful elements of a functional alias the MCX Service shall be able to restrict or allow MCX Users to be involved in more than one MCX Service Emergency Group Communication at a time. | Not addressed within the present document. | +| [R-5.6.2.4.1-013] | The MCX Administrator shall be able to configure whether the initiation of a MCX Service Emergency Alert shall also automatically trigger a MCX Service Emergency Group Communication. | 7.25 Solution 25 – Triggering an emergency group communication after an emergency alert automatically | + +**Table A.8.1-3: Support for multiple devices** + +| Reference | Description | Solution | +|---------------|------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------| +| [R-5.10-001a] | The MCX Service shall be able to allow the MCX Service Administrator to limit the number of simultaneous log ins of an MCX User to multiple MCX UEs. | 7.14 Solution 14 – MC service server limits the number of simultaneous successful service authorisations | + +**Table A.8.1-4: Location** + +| Reference | Description | Solution | +|---------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------| +| [R-5.11-002a] | The MCX Service shall be able to provide a mechanism for obtaining high accuracy Location information by integrating position information from multiple external sources (e.g. magnetometers, orientation sensors, GNSS). | Rel-15 | +| [R-7.8-002] | An MCX UE shall be capable of providing a mechanism for obtaining the distance between the MCX UE and other MCX UEs within communication range. | On-network: Rel-15.Off-network: Not addressed by the present document. | + +## A.8.2 Mission Critical Push to Talk (MCPTT) requirements + +The following stage 1 requirements are documented in 3GPP TS 22.179 [3]. + +**Table A.8.2-1: Commencement modes for MCPTT Group calls** + +| Reference | Description | Solution | +|----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------| +| [R-6.2.1-001a] | The MCPTT Service shall be capable of allowing an MCPTT Group Call setup request to proceed only if a minimum number of MCPTT Group Members are currently affiliated. | 7.24 Solution 24 – Additional commencement modes for MCPTT Group calls | +| [R-6.2.1-001b] | The MCPTT Service shall be capable of allowing an MCPTT Group Call setup request to proceed only if specific MCPTT Group Member(s) are currently affiliated. | 7.24 Solution 24 – Additional commencement modes for MCPTT Group calls | +| [R-6.2.1-010a] | If an MCPTT Group Call setup request requires acknowledgement from Affiliated MCPTT Group Members, and the required MCPTT Group Members did not acknowledge the call setup within a configured time, the MCPTT Service shall be able to provide the list of MCPTT Group Members who did not acknowledge the call to the initiating MCPTT User. | 7.13 Solution 13 – List of MCPTT group members who did not acknowledge the group call request | + +**Table A.8.2-2: Private calls** + +| Reference | Description | Solution | +|---------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------| +| [R-5.6.3-014] | The MCPTT Service shall provide a mechanism for an authorized MCPTT User to transfer an ongoing MCPTT Private Call (with Floor control) to another MCPTT user. | 7.29 Solution 29 – Call forwarding and call transfer for private calls | +| [R-5.6.3-015] | The MCPTT Service shall provide a mechanism for an authorized MCPTT User to configure forwarding of incoming MCPTT Private Calls (with Floor control) to another MCPTT user in the following situations:
- - Always
- - If the MCPTT User is not reachable
- - If the incoming private call is a call with manual commencement mode and the MCPTT User does not answer within a configured period
- - Based on manual input of the MCPTT User
- - Always
- - If the MCPTT User is not reachable
- - If the incoming private call is a call with manual commencement mode and the MCPTT User does not answer within a configured period
- - Based on manual input of the MCPTT User
NOTE: Operators should be able to choose which of these options they use to deliver Push services, and it should be possible to use these options independently from each other. | Only PS (IMS)
Supported | Only PS (IMS)
Supported | May trigger PS or CS bearer
Supported | Only PS (unclear how IMS services would trigger PDP activation)
Supported | +| It shall be possible to deploy Push services independently of other services defined by 3GPP. | Requires 3GPP PS bearer service | Requires network activated 3GPP PS bearer service | Requires 3GPP PS bearer service or CS bearer and SMS | Requires modified 3GPP PS bearer service and name resolution or presence service | +| The quality of service delivery shall be able to include time-sensitive as well as reliable delivery choices | No interface to request from delivery network | No interface to request from delivery network | No interface to request from delivery network | No interface to request from delivery network | + +| | Always on PDP | Static address NRPCA | SMS triggered bearer | Dynamic address NRPCA | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------|---------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------| +| General requirements | | | | | +| It shall be possible to use all available access networks (e.g. GERAN, UTRAN,). | Supported | Supported | Supported | Supported | +| It shall be possible for the Push Initiator to specify a bearer for the Push service, as a default the push service shall identify the bearer. The Push Initiator may, however, require certain grade of service for delivery, e.g. speed of delivery or delivery acknowledgement. | No interface to request grade of service from delivery network | No interface to request grade of service from delivery network | No interface to request grade of service from delivery network | No interface to request grade of service from delivery network | +| Provisioning
not scope of stage 2 | Supported by Push Application protocols defined by OMA | Supported by Push Application protocols defined by OMA | Supported by Push Application protocols defined by OMA | Supported by Push Application protocols defined by OMA | +| Subscription
not scope of stage 2 | Supported by Push Application protocols defined by OMA | Supported by Push Application protocols defined by OMA | Supported by Push Application protocols defined by OMA | Supported by Push Application protocols defined by OMA | +| Addressing and Routing | | | | | +| It shall be possible to uniquely identify Push Recipients. | MSISDN (IMSI); dynamic IP address | MSISDN (IMSI); IP address | MSISDN (IMSI); | name@domain | +| It shall be possible for Push Recipients to uniquely identify push initiators. | By source IP address or at application level | By source IP address or at application level; Not at network requested PDP activation | By source IP address or at application level or from information in trigger SMS | By source IP address or at application level; Not at network requested PDP activation | +| The addressing model shall include addresses of the device (e.g. IP address, SIP-URI, MSISDN) and application level addressing (i.e. user agents). | MSISDN (IMSI) SIP-URI from IMS or presence | MSISDN (IMSI) SIP-URI from IMS or presence | MSISDN (IMSI) SIP-URI from IMS or presence | name@domain in addition to IMS (in addition to presence) | +| It shall be possible to deliver Push Data to a Push Recipient with a dynamically allocated IP address. | Supported | Not Applicable | Supported | Supported | +| The Push service shall be able to deliver a Push Data to a Push Recipient that does not have an IP address currently assigned. | Not Applicable | Not Applicable | For small amount data within SMS | Address Resolver allows identity of Push Recipient resulting in establishment of PDP Context. | +| Both telecom and internet numbering and addressing schemes shall be supported. | Has typically an E.164 address but uses only IP address for data transfer | Has typically an E.164 address but uses only IP address for data transfer | Uses an E.164 address for trigger SMS (and small volume data transfer) but uses only IP address for data transfer | Aims at prevention of E.164 address but use (probably needed for charging); only IP address for data transfer | +| It shall be possible to address Push Recipients without allocating E.164 numbers. | Supported | Supported | Not Supported | Supported | + +| | Always on PDP | Static address
NRPCA | SMS triggered
bearer | Dynamic address
NRPCA | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------| +| General requirements | | | | | +| Delivery | | | | | +| The PLMN may set restrictions including maximum size of Push Data. | Not supported | Not supported | Not supported (small volume data within SMS) | Not supported | +| The Push service may offer classes of priority and service delivery. When offered this shall include support for the following ... | Supported by Push Application protocols defined by OMA. It may need support by the delivery network. | Supported by Push Application protocols defined by OMA. It may need support by the delivery network. | Supported by Push Application protocols defined by OMA. It may need support by the delivery network. | Supported by Push Application protocols defined by OMA. It may need support by the delivery network. | +| In case the Push Recipient declines a specific instance of Push Data , it shall be provided with means to indicate whether the push service is allowed to re-send it or not. | Supported by Push Application protocols defined by OMA | Supported by Push Application protocols defined by OMA | Supported by Push Application protocols defined by OMA | Supported by Push Application protocols defined by OMA | +| In the case that classes of priority and service delivery are not offered an attempt to deliver Push Data to the Push Recipient shall be made without unnecessary delay. | Supported | Supported | Dependant on properly configured SMSC. | Supported | +| Service Management (The basic principle of service management is "the user is in control") | Supported by Push Application protocols defined by OMA | Supported by Push Application protocols defined by OMA | Supported by Push Application protocols defined by OMA | Supported by Push Application protocols defined by OMA | +| The user is provisioned with the Push service by a Network Operator. If a user is provisioned with the push service, the provisioning data shall include a push subscription profile for push service settings and push service preferences. | Supported by Push Application protocols defined by OMA | Supported by Push Application protocols defined by OMA | Supported by Push Application protocols defined by OMA | Supported by Push Application protocols defined by OMA | +| Security | | | | | +| It shall be possible for the Push Recipient to be assured of the identity of the Push Initiator. | Supported by Push Application protocols defined by OMA | Supported by Push Application protocols defined by OMA | Supported by Push Application protocols defined by OMA. The trigger SM may provide identity of the Push Initiator. | Supported by Push Application protocols defined by OMA | +| Mechanisms shall be provided to ensure that the Push Data is sent to and accessed only by the intended addressed entity. | Supported | Supported | Supported | Supported | + +| | Always on PDP | Static address NRPCA | SMS triggered bearer | Dynamic address NRPCA | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------| +| General requirements | | | | | +| It shall be possible for the Push service or the user to deny unauthorized Push Data. | Supported by Push Application protocols defined by OMA Bearer protocols do not support. | Supported by Push Application protocols defined by OMA Bearer protocols allow support for this feature although it is UE implementation dependent | Supported by Push Application protocols defined by OMA Bearer protocols allow support for this features although it is UE implementation dependent. The UE may reject the SMS Trigger based on the content of the message. | Supported by Push Application protocols defined by OMA Bearer protocols allow support for this feature although it is UE implementation dependent | +| It shall be possible for the user to control acceptance of Push Data sent to the user based on the trust level of the Push Initiator. | Supported by Push Application protocols defined by OMA | Supported by Push Application protocols defined by OMA | Supported by Push Application protocols defined by OMA | Supported by Push Application protocols defined by OMA | +| The Push service shall provide data integrity and data confidentiality of the Push Data. | By the delivery network | By the delivery network | By the delivery network | By the delivery network | +| Privacy | | | | | +| The privacy of the user is important and the introduction of the push services should in no way result in unwanted information "spam" being sent to mobile users. | Supported by Push Application protocols defined by OMA Network and push service configuration | Supported by Push Application protocols defined by OMA Network and push service configuration | Supported by Push Application protocols defined by OMA Network and push service configuration | Supported by Push Application protocols defined by OMA Network and push service configuration | +| Access rules
Not within the scope of stage 2 TR. | Supported by Push Application protocols defined by OMA | Supported by Push Application protocols defined by OMA | Supported by Push Application protocols defined by OMA | Supported by Push Application protocols defined by OMA | +| Charging
Outside scope of stage 2 TR. | Unclear how push charging relates to delivery network charging (e.g. prepay, or how is roaming known ?) | Unclear how push charging relates to delivery network charging (e.g. prepay, or how is roaming known ?) | Unclear how push charging relates to delivery network charging (e.g. prepay, or how is roaming known ?) | Unclear how push charging relates to delivery network charging (e.g. prepay, or how is roaming known ?) | +| Push Subscription Profile Information
Not within the scope of Stage 2 TR. | Supported by Push Application protocols defined by OMA | Supported by Push Application protocols defined by OMA | Supported by Push Application protocols defined by OMA | Supported by Push Application protocols defined by OMA | +| Roaming | | | | | +| Push services shall be available when roaming. | Requires VPLMN PS bearer support and PS roaming agreement; may use local and home GGSN PDP | Requires VPLMN PS bearer support, static NRPCA support by UE and VPLMN and PS roaming agreement; has to use home GGSN | Requires VPLMN PS bearer support and PS roaming or only CS roaming agreement; SMS is mandatory GSM service ; home or visited GGSN or dial-in | Requires VPLMN PS bearer support, support of "new" NRPCA support by UE and VPLMN and PS roaming agreement; has to use home GGSN | +| The Push Recipients shall be able to select and receive pushed local services, subject to the user profile settings. | Possible | Possible | Possible | Possible | +| Barring of the Push service | | | | | + +| General requirements | Always on PDP | Static address NRPCA | SMS triggered bearer | Dynamic address NRPCA | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------|-------------------------------|---------------------------------------------|---------------------------------------| +| It shall be possible to provide the Push service to a user regardless of barring status of other services, providing that a bearer to deliver the Push Content is available. | Not possible if bearer barred | Not possible if bearer barred | Requires that PS or CS bearer is not barred | Not possible if bearer barred | +| It shall be possible for user to bar the Push service regardless of barring status of other services. | Not possible if bearer barred | Not possible if bearer barred | Not possible if bearer barred | Not possible if bearer barred | +| Standardization Effort | Fully specified | Fully specified. | Fully specified | New functionality is to be specified. | + +Comparing NRPCA to long-lived PDP contexts, the resource/performance effort moves from PDP context capacity to higher signalling traffic for PDP contexts establishment and release, i.e. NRPCA allows better usage of the GGSNs PDP Contexts capacity. There is no difference for the user data throughput capacity between approaches. The increase in signalling traffic for NRPCA impacts the performance requirements for the GGSN, SGSN, HLR, and in the case of NRPCA with dynamic IP address assignment the "new entity" (Address Resolver or Presence Server). + +For all approaches, except for SMS over CS, the UE has to be PS attached at the SGSN and this requires continuous mobility management procedures, i.e. routeing area updating. + +Compared with the other mechanisms NRPCA with dynamic IP addressing introduces new PLMN signalling. Large scale usage of that mechanism requires considerable performance upgrades for "new entity" i.e. Address Resolver (DNS) or Presence Server and additional HLR, GGSN and SGSN signalling performance. NRPCA with dynamic IP addressing moves resource usage from static PDP context to new static contexts on DNS or Presence Server and increases signalling between a number of network entities. NRPCA partly avoids potential delays compared to SMS when delivering the PDP Context activation request. The SMS trigger mechanism may, depending on delivery time requirements, require performance upgrades for SMSC, HLR and SGSN when used in large scale. But the performance may be shared with other SMS applications. + +NRPCA with dynamic IP address assignment requires new UE and new network functions. The other approaches, except NRPCA with static IP addressing, are already supported by all or many networks. The NRPCA roaming support depends on new, features supported by the visited network. + +The long-lived PDP Context does not require any mechanism to trigger PS based applications when the UE behaviour is to initiate PS connectivity, i.e. to activate a PDP Context. These PS based applications with this type of always-on behaviour will retain PS connectivity during the period of time the application wants to be available for Push services. Existing GPRS procedures (from Release 97) provide sufficient support for PS based applications with this always-on behaviour. + +## 6.2 Conclusion + +This TR has studied the mechanisms available to allow data to be pushed to a mobile device. The architecture used for Push services includes a Push Function and a Push Initiator. The Push Function acts as a gateway to mobile devices for data pushed from Push Initiators. The mobile device user subscribes to a push service via the Push Function and Push Initiator. + +When a mobile device has an active connection, either circuit-switched or packet-switched, data may be pushed to the device based on the subscription to push services agreed between the mobile user and the Push Function and Push Initiator. + +If a mobile device has a statically assigned IP address and is attached to the network, the method described for NRPCA with static IP address assignment may be used by the Push Function to initiate a PDP Context with the mobile. It was concluded that NRPCA with dynamic IP address assignment would not be standardised to support Push Services. + +When a mobile device is attached to a network but does not have an active PDP Context, it may be possible to send the Push Data using SMS, or to send a notification of pending Push Data using the SMS. SMS may also be used to send a notification to the UE to activate a PDP Context. + +It has been determined during this study that at least one of the mechanisms defined in clause 5.1.4 is required to allow the Push Function to learn the status of an active PDP Context, and in particular, when an active PDP Context is deactivated by the network. + +# Annex A: PDP Context State Notification message procedures + +In order for the GGSN to know where to forward the PDP Context State Notification message (abbreviated to NM) a new field will be defined as part of the APN configuration information in the GGSN. This field will contain a statically configured IP address that will be used by the GGSN to forward the NM. This field will be called the APN Notification Address and will be available for each PDP Context at the GGSN using the associated APN. + +The PDP Context State Notification Message will contain the following information: + +- Message Type; will be a value identifying the message as a PDP Context State Notification Message. +- State; will be the state of the PDP Context, which will currently only have one value indicating the PDP Context is DEACTIVATED. +- MSISDN; PDP Address will contain the values from the PDP Context being reported. + +When a PDP Context is deactivated the GGSN will issue a NM to the receiving entity defined at the APN Notification Address. In the case of SGSN-Initiated PDP Context Deactivation or MS-Initiated deactivation the GGSN will send a PDP Context State Notification message immediately after transmission of the Delete PDP Context Response message sent to the SGSN. In the case of GGSN-Initiated PDP Context Deactivation the GGSN would send a PDP Context State Notification Message immediately after transmission of the Delete PDP Context Request message sent to the SGSN. + +The GGSN will only send a PDP Context State Notification Message when the last PDP Context to a PDP address has been deactivated. + +The GGSN forwards the NM to the APN associated with the deactivated PDP Context in an IP packet and uses the APN Notification Address as the destination IP address. This mechanism allows the APN Notification Address to be a single Application Server such as a Push Function, or a generic Notification Server that handles NMs for a number of Application Servers supported at an APN. + +When a Notification Server is used the Notification Server may decide, using its own algorithms, how to process the NM from the GGSN. It may broadcast the NM to all its Application Servers, or to a subset of Application Servers. It may maintain a list of PDP Addresses/MSISDNs being serviced by Application Servers and perform a match between those values in the NM and that in its database to determine which Application Server to forward the NM. The definition of how a Notification Server processes NMs is outside the scope of this work. But enough information is provided in the NM for a Notification Server or Application Server to determine which PDP Context has been deactivated and take appropriate action based on that information. + +## Example Scenario 1) APN Notification Address is configured to use the IP address of the Push Function + +In this scenario the IP address of the Push Function is configured as the APN Notification Address, therefore the GGSN will forward the NM directly to the Push Function. + + + +``` + +sequenceDiagram + participant SGSN + participant GGSN + participant APN + participant PushFunction as Push Function + Note over GGSN: GGSN + Note over APN: APN + Note over PushFunction: Push Function + GGSN->>SGSN: Delete PDP Context Request + GGSN->>PushFunction: PDP Context State Notification Message (MSISDN, PDP Address, APN) + Note right of PushFunction: Note 1) + +``` + +**APN Notification Address = IP address of Push Function** + +**Note 1) the MSISDN and PDP Address in the NM are used to match with the information in the Push Function relating to the PDP Context that is now deactivated.** + +Sequence diagram showing GGSN sending a Delete PDP Context Request to the left and a PDP Context State Notification Message through the APN to the Push Function on the right. + +## Example Scenario 2) APN Notification Address is configured to use a Notification Server in the APN + + + +``` +sequenceDiagram + participant SGSN + participant GGSN + participant APN + participant NS as Notification Server + participant ASA as App Server A + participant ASB as App Server B + + Note right of APN: APN + + SGSN->>GGSN: Delete PDP Context Request + GGSN-->>SGSN: Delete PDP Context Response + GGSN->>NS: PDP Context State Notification Message (MSISDN, PDP Address, APN) + NS->>ASA: Forward NM + NS->>ASB: Forward NM + NS->>ASB: Forward NM + Note right of ASB: To other servers +``` + +Sequence diagram showing the interaction between SGSN, GGSN, APN, Notification Server, App Server A, and App Server B. The process involves a Delete PDP Context Request/Response followed by a PDP Context State Notification Message being forwarded to multiple application servers. + +The mechanism described in this Annex to notify a Push Function or Application Server regarding the state of a PDP Context is only one of several methods possible. + +# Annex B: NRPCA with no restrictions on APN and GPRS configuration + +The solution for NRPCA differs from the solution in clause 5.1.5.1 in the following ways: + +- There is no restriction on the number of GGSNs that can serve an APN. Therefore the proposal addresses how a NRPCA can begin at one GGSN and then the PDP Context can be Activated at another GGSN. +- In step 9 the SGSN must retain a copy of the GGSN Address for Control Plane that is received in step 4 PDU Notification Request (the home GGSN address), as well as the more recent value for the GGSN Address for Control Plane received from the GGSN' (the GGSN selected by the SGSN), unless the GGSN' is the same as the home GGSN. +- In step 11 the SGSN must use the GGSN Address for Control Plane of the home GGSN to send an Update Address Resolver message to the home GGSN (and subsequently the home AR). + + + +``` + +graph LR + UE[UE] -- Packet Domain Network --> GGSN[GGSN] + GGSN -- Gc --> HLR[HLR] + GGSN <--> AR[Address Resolver] + GGSN -- Gi --> OPD((Operator Specific PDN)) + OPD --> PF[Push Function PF] + PF --> I((Internet)) + I --> PI[Push Initiator PI] + PI -- "Push data flow" --> UE + +``` + +Figure B1: Architecture for NRPCA with dynamic IP addressing supporting Push. The diagram shows a UE connected to a Packet Domain Network, which is connected to a GGSN. The GGSN is connected to an Address Resolver and a Gc interface. The GGSN is also connected to an Operator Specific PDN via a Gi interface. The Operator Specific PDN is connected to a Push Function (PF), which is connected to the Internet. The Internet is connected to a Push Initiator (PI). A large red arrow labeled 'Push data flow' points from the PI towards the UE. + +**Figure B1: Architecture for NRPCA with dynamic IP addressing supporting Push** + +## Assumptions + +The Address Resolver is implemented using DNS and the User-ID is a unique name in the format user@realm and therefore any query to any Address Resolver in the network will always end up at the home AR for the User-ID. + +## Notes/Limitations + +This proposal requires three changes to the SGSN. In step 4 the PDU Notification Request will contain a null PDP Address. The SGSN must be modified to accept this field as null and forward the Request PDP Context Activation message to the UE with a null PDP Address field. The UE upon receiving a Request PDP Context Activation with a null PDP Address field will use this as an indicator to establish a PDP Context back to the APN contained in the Request PDP Context Activation. + + + +``` + +sequenceDiagram + participant PI + participant PF + participant GGSN + participant AddrRes + participant HLR + participant GGSN_prime as GGSN' + participant SGSN + participant UE + + Note right of PI: Home Network + Note left of PF: Visited Network + + PI-->>PF: 1. Push-Message + PF-->>GGSN: 2. Push Request + GGSN->>AddrRes: 3. Query AR + AddrRes-->>GGSN: 3a. Push Confirm + GGSN->>HLR: 3b. Send Routeing Info + GGSN->>SGSN: 4. PDU Notification Request + SGSN-->>GGSN: 5. PDU Notification Response + SGSN->>UE: 6. Request PDP Context Activation + UE->>SGSN: 7. Activate PDP Context Request + SGSN->>GGSN_prime: 8. Create PDP Context Request + GGSN_prime-->>SGSN: 9. Create PDP Context Response + SGSN->>UE: 10. Activate PDP Context Accept + SGSN-->>GGSN: 11. Update AR + GGSN-->>AddrRes: 12. Update AR + AddrRes-->>GGSN: 13. Push Confirm + GGSN-->>UE: 14. push data transfer + Note right of PF: Push Data + +``` + +Sequence diagram for NRPCA using dynamic IP address assignment. Lifelines: UE, SGSN, GGSN', HLR, AddrRes, GGSN, PF, PI. The diagram shows the interaction between these entities to activate a PDP context and transfer push data. Steps include Push-Message, Push Request, Query AR, PDU Notification Request/Response, PDP Context Activation, and Update AR messages. + +Note1: Solid arrow means Message type currently defined in 3G specifications + +Note2: Square arrow means Message type not currently defined in 3G specifications + +Note3: Long dash dot arrow means Message type defined in OMA Push specifications Push Access Protocol + +**Figure B2: NRPCA using dynamic IP address assignment** + +The sequence of events is explained for each step shown in the diagram. + +1. The PI sends Push-Message with User-ID to the PF. The Push-Message is defined in the WAP Push Access Protocol specification and is outside the scope of this work. +2. The PF validates the User-ID and PI relationship and sends a Push Request message to the GGSN. (The Push Request contains the User-ID and PF APN, the Push Request message format is TBD.) +3. The GGSN queries the AR using the User-ID to lookup the IMSI and IP address. The AR maintains a table of User-ID to IMSIs and IP addresses (depending on the existence of a PDP Context to the UE). If the IP address exists the AR executes step 3a. If no IP address is assigned for the User-ID the AR returns the matching IMSI to the GGSN. The GGSN queries the HLR as described in step 3b. +- 3a. If the GGSN is returned an IP address assigned to the User-ID, it responds with a Push Confirm message to the Push Function containing the IP address of the existing PDP Context. (The format of the Push Confirm message is TBD.) The Push Data can then be transmitted using this IP address and the Push Function proceeds to step 14. + +NOTE 1: The presence of an IP address in the AR table does not necessarily imply an existing PDP Context. If the UE uses static IP addressing the AR would have a permanent entry in its table for that UE's User-Id, but the UE may not have an active PDP Context at the time the Push Data is sent to the UE. In this case NRPCA using static IP addressing procedures as defined in TS 23.060 [6], clause 9.2.2.2 would be executed at step 11. + +- 3b. Using the IMSI matching the User-ID, the GGSN obtains routing information for the UE by issuing Send Routing Information request to the HLR. The HLR returns the address of the SGSN to which the UE is currently attached. +4. The GGSN sends a PDU Notification Request to the SGSN identified in step 3b with a null IP Address. The PDU Notification Request contains the fields; IMSI, Tunnel Endpoint Identifier Control Plane, End User Address, APN, GGSN Address for Control Plane, and Private Extension. An extension to TS 29.060 [22] is required to allow the End User Address (PDP Address) to be null, indicating the UE is to request a dynamically assigned IP address. +5. The GGSN receives a successful PDU Notification Response from the SGSN. +6. The SGSN sends Request PDP Context Activation (TI, PDP Type, PDP Address, APN) to UE, with a null PDP Address. +7. The UE sends Activate PDP Context Request to the SGSN with the null IP address and APN obtained from the Request PDP Context Activation. +8. The SGSN sends the selected GGSN' a Create PDP Context Request (GGSN selection is determined by rules defined in TS 23.060 [6], Annex A). The GGSN' obtains a dynamically assigned IP address (e.g. from a DHCP server, Radius server or address pool). Note: the selected GGSN' may be the same as the originating GGSN. +9. The GGSN' sends the SGSN a Create PDP Context Response which may contain the parameters; Cause, Reordering required, Recovery, Tunnel Endpoint Identifier Data I, Tunnel Endpoint Identifier Control Plane, Charging ID, End User Address, Protocol Configuration Options, GGSN Address for Control Plane, GGSN Address for user traffic, Quality of Service Profile, Charging Gateway Address. The SGSN must retain the GGSN Address for Control Plane that it received in step 4 from the originating (home) GGSN as well as the new GGSN Address for Control Plane this is received from the GGSN'. +10. After successful PDP Context creation the SGSN sends Activate PDP Context Accept to the UE with the assigned IP address. +11. The SGSN upon receiving the Create PDP Context Response, will use the GGSN Address for Control Plane it received in the PDU Notification Request (step 4) from the originating GGSN, to send an Update AR to the originating GGSN with the IP address of the PDP Context and associated IMSI. After sending the Update AR it will overwrite the GGSN Address for Control Plane with the GGSN Address for Control Plane value contained in the PDP Context Response from the GGSN' in step 9. + +NOTE 2: The SGSN may need to retain the original GGSN Address for Control Plane address so it can update the AR in the home network when the PDP Context is deactivated. + +12. The GGSN (originated) upon receiving the Update AR message from the SGSN will forward that message to its local Address Resolver, updating the entry for the IMSI and User-Id with the IP address for the activated PDP Context. +13. The GGSN sends a Push Confirm message to the PF with the newly assigned IP Address. +14. The Push Function sends the Push Data in IP packets using the IP address from the Push Confirm. + +## Deactivate PDP Context and Update Address Resolver + + + +``` +sequenceDiagram + participant SGSN + participant GGSN_prime as GGSN' + participant GGSN + participant AR as Address Resolver + Note left of SGSN: Deactivate PDP Context and Update Address Resolver + SGSN->>GGSN_prime: Delete PDP Context Request + GGSN_prime-->>SGSN: Delete PDP Context Response + Note left of SGSN: 1 ) Update AR + SGSN->>GGSN: Update AR + Note right of GGSN: 2 ) Update AR + GGSN->>AR: Update AR +``` + +Sequence diagram showing the deactivation of a PDP context and update of the address resolver. Lifelines: SGSN, GGSN', GGSN, and Address Resolver. The sequence is: 1. SGSN sends a Delete PDP Context Request to GGSN'. 2. GGSN' sends a Delete PDP Context Response to SGSN. 3. SGSN sends an Update AR message to GGSN (labeled '1 ) Update AR'). 4. GGSN sends an Update AR message to the Address Resolver (labeled '2 ) Update AR'). + +**Figure B3: Deactivate of PDP Context and update Address Resolver** + +(when PDP Context is at the visited GGSN) + +1. After the SGSN receives the Delete PDP Context Response message from the GGSN' (serving GGSN) it will generate an Update AR message towards the home GGSN using the address of the home GGSN it stored from step 4 of the PDU Notification Request. The Update AR message will contain an indication the IP address of the deleted PDP context must be removed from the AR tables. +2. The home GGSN upon receiving the Update AR message will forward the update to the AR. + +# Annex C: Change history + +| Change history | | | | | | | | +|----------------|--------|-----------|-----|-----|------------------------------------------------------------------------------|--------|---------------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 2004-03 | SP-23 | SP-040046 | | | Raised to v.6.0.0 after approval at SA#23 (same content as previous version) | 2.0.0 | 6.0.0 | +| 2004-04 | | | | | Missing / ambiguous abbreviations supplied | 6.0.0 | 6.0.1 | +| 2004-06 | SP-24 | SP-040446 | 001 | 2 | NRPCA with Dynamic IP Address Assignment conclusion | 6.0.1 | 6.1.0 | +| 2007-06 | - | - | - | - | Update to Rel-7 version (MCC) | 6.1.0 | 7.0.0 | +| 2008-12 | 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 | 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