[{"name":"S2-1900036","title":"LS from CT WG4: Clarification request on NF authorization in UE Reachability Notification Request procedure","source":"CT WG4","contact":"Laurent Dubesset","contact-id":47514,"tdoctype":"LS in","for":"Action","abstract":"C4-188044 was submitted at CT WG4#87 but not concluded. It aimed at specifying the stage 3 required changes to TS 29.503 to allow the UDM informing the AMF of the identities of the Network Functions that are authorized to request notifications on this UE's reachability (steps 0a or 0b of UE Reachability Notification Request procedure defined in TS23.502, sub-clause 4.2.5.2). During the discussions, concerns were raised by some delegates whether this procedure is needed at all. Some delegates considered that it is redundant as OAUTH2.0 mechanism defined in TS 33.501 already provides a framework for Authorization of NF service access. In addition, it was commented that the FQDN is not a suitable identity for NF authorization as an HTTP client (in opposition to a Diameter one) doesn't set any origin identity such as a FQDN when sending a request to an HTTP server. The NF Instance Id of the NF Service Consumer is the primary identity for an NF when registering in the NRF and when requesting an OAUTH2.0 token. Action: CT WG4 kindly asks SA WG2 group to: - Clarify the use cases or the service layer consideration for the procedure of UDM providing authorized NF list (steps 0a or 0b of UE Reachability Notification Request procedure defined in TS23.502, sub-clause 4.2.5.2) and AMF using such list for subsequent authorization check, and - Confirm that the authorisation framework defined in TS 33.501 is not sufficient for authorizing NF to request UE's reachability. - If so, confirm that the list of the identities of the authorized Network Functions is a subscriber specific parameter and therefore is part of subscription information that may be stored in the UDR. - If so, remove the FQDN as a possible NF identity in TS 23.502, clause 4.2.5.2.","secretary_remarks":"Response drafted in S2-1900663. Postponed.","agenda_item_sort_order":28,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":14460,"status":"postponed","reservation_date":"2018-12-19 11:46:38","uploaded":"2018-12-19 11:47:59","revisionof":"","revisedto":"S2-1901414","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"SA WG3","lsoriginalls":"C4-188603","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1900036.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1900083","title":"Fixing text related to discovery and selection","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 6.3.1 - Adding what is registered in NRF - A discovery result gives an NF profile. The NF profile may contain addressing to the NF instance and optionally NF service instances. - Not clear what message routing model means. All messages are routed via IP. - Fixing references - Clarifying what an NF may subscribe to in the NRF - Fixing terminology 'target' NF - Wrong placement of text regarding SMF - The statement: 'The result of the NF discovery procedure is applicable to any subscriber that fulfils same discovery criteria', is not really correct. When doing discovery on a SUPI the discovery result is for this SUPI, but the discovery result is a NF profile, which may contain a SUPI range, and thus the range may be valid for other subscribers. - Status subscribe notifies if NF is deregistering, or changes in the NF profile, e.g. Service instances taken in our out of service. - The text related to roaming and slicing refers to 23.502, however nothing is stated with regards to slicing is referred clause. Thus this is a generic procedure. Also NRF in home may do discovery to NRF in visited, renaming target with remote. 6.3.2 - Clarifying the NF profile is received in a discovery - Clarifying that not only SMF instance is selected but also service instance - Moved SMF text from 6.3.1 6.3.3.2 - Clarifying that NF profile of UPF is received by SMF - Clarifying that UPF instances register their NF profiles in NRF 6.3.4 - Clarifying that an AUSF instance perform authentication. 6.3.5 - Clarifying that AMF has discovery and selection functionality - Inserting 'instance' in the right places - Clarifying that NF profile is received in discovery - Clarifying that associated AMF is GUAMI associated AMF - Moving slicing related paragraph to not misinterpret that bullet list is about slicing. 6.3.6.1 - Inserting 'instance' in the right places 6.3.7 subheadings - Inserting 'instance' in the right places - 'Candidate' NFs is something the is used in selection. - Clarifying that discovery may be needed since PCF instance address may not be present in the UE context - Making a distinction between H-PCF id and H-PCF instance 6.3.8 - Inserting 'instance' in the right places - Clarifying that selection is about which UDM instance that handles a subscription 6.3.9 - Inserting 'instance' in the right places - selection 'based on available instances' is unnecessary, would a UDR consumer really ever do the opposite? 6.3.10 - Inserting 'instance' in the right places - Making sure that registration is interpreted as registration from UE - Adding that also IP address(es) may be configured in AMF","secretary_remarks":"Revised in parallel session to S2-1901154.","agenda_item_sort_order":28,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":14470,"status":"revised","reservation_date":"2019-01-11 22:31:41","uploaded":"2019-01-15 13:55:47","revisionof":"","revisedto":"S2-1901154","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":742.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1900083.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1900553","title":"Correction on monitoring event for 'availability after DDN failure'.","source":"Samsung","contact":"Sunghoon Kim","contact-id":59112,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Change to 'Availability after Downlink Data Notification failure'.","secretary_remarks":"Revised in parallel session to S2-1901155.","agenda_item_sort_order":28,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":14500,"status":"revised","reservation_date":"2019-01-15 10:05:14","uploaded":"2019-01-15 10:36:32","revisionof":"","revisedto":"S2-1901155","release":"Rel-15","crspec":23.502,"crspecversion":"15.4.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":956.0,"crrevision":"","crcategory":"D","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1900553.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1900662","title":"Correction for NF authorized to request notification for UE reachability","source":"Nokia, Nokia Shanghai Bell","contact":"Yannick Lair","contact-id":76350,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Step 0 is removed. Step 3 is modified to remove the service authorization check on a per user basis.","secretary_remarks":"Revised in parallel session to S2-1901156.","agenda_item_sort_order":28,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":14530,"status":"revised","reservation_date":"2019-01-15 14:14:29","uploaded":"2019-01-15 14:59:56","revisionof":"","revisedto":"S2-1901156","release":"Rel-15","crspec":23.502,"crspecversion":"15.4.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":983.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1900662.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1900663","title":"[DRAFT] Reply LS on Clarification request on NF authorization in UE Reachability Notification Request procedure","source":"Nokia, Nokia Shanghai Bell","contact":"Yannick Lair","contact-id":76350,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG4. CC: SA WG3. Attachments: Agreed version of S2-1900662)","secretary_remarks":"Response to S2-1900036. Revised in parallel session to S2-1901157.","agenda_item_sort_order":28,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":14550,"status":"revised","reservation_date":"2019-01-15 14:17:38","uploaded":"2019-01-15 14:59:56","revisionof":"","revisedto":"S2-1901157","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"SA WG3","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1900663.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1900678","title":"Addition of PCF services","source":"Orange","contact":"Xiaofeng Huang","contact-id":34683,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add two following PCF services in Clause 7.2.4: Npcf_UEPolicyControl Npcf_EventExposure","secretary_remarks":"Agreed in parallel session. This was Block approved","agenda_item_sort_order":28,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":14520,"status":"agreed","reservation_date":"2019-01-15 14:48:42","uploaded":"2019-01-15 14:59:40","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":904.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-190155","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1900678.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901154","title":"Fixing text related to discovery and selection","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 6.3.1 - Adding what is registered in NRF - A discovery result gives an NF profile. The NF profile may contain addressing to the NF instance and optionally NF service instances. - Not clear what message routing model means. All messages are routed via IP. - Fixing references - Clarifying what an NF may subscribe to in the NRF - Fixing terminology 'target' NF - Wrong placement of text regarding SMF - The statement: 'The result of the NF discovery procedure is applicable to any subscriber that fulfils same discovery criteria', is not really correct. When doing discovery on a SUPI the discovery result is for this SUPI, but the discovery result is a NF profile, which may contain a SUPI range, and thus the range may be valid for other subscribers. - Status subscribe notifies if NF is deregistering, or changes in the NF profile, e.g. Service instances taken in our out of service. - The text related to roaming and slicing refers to 23.502, however nothing is stated with regards to slicing is referred clause. Thus this is a generic procedure. Also NRF in home may do discovery to NRF in visited, renaming target with remote. 6.3.2 - Clarifying the NF profile is received in a discovery - Clarifying that not only SMF instance is selected but also service instance - Moved SMF text from 6.3.1 6.3.3.2 - Clarifying that NF profile of UPF is received by SMF - Clarifying that UPF instances register their NF profiles in NRF 6.3.4 - Clarifying that an AUSF instance perform authentication. 6.3.5 - Clarifying that AMF has discovery and selection functionality - Inserting 'instance' in the right places - Clarifying that NF profile is received in discovery - Clarifying that associated AMF is GUAMI associated AMF - Moving slicing related paragraph to not misinterpret that bullet list is about slicing. 6.3.6.1 - Inserting 'instance' in the right places 6.3.7 subheadings - Inserting 'instance' in the right places - 'Candidate' NFs is something the is used in selection. - Clarifying that discovery may be needed since PCF instance address may not be present in the UE context - Making a distinction between H-PCF id and H-PCF instance 6.3.8 - Inserting 'instance' in the right places - Clarifying that selection is about which UDM instance that handles a subscription 6.3.9 - Inserting 'instance' in the right places - selection 'based on available instances' is unnecessary, would a UDR consumer really ever do the opposite? 6.3.10 - Inserting 'instance' in the right places - Making sure that registration is interpreted as registration from UE - Adding that also IP address(es) may be configured in AMF","secretary_remarks":"Revision of S2-1900083. Revised in parallel session to S2-1901258.","agenda_item_sort_order":28,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":14480,"status":"revised","reservation_date":"2019-01-23 02:05:36","uploaded":"2019-01-29 14:04:13","revisionof":"S2-1900083","revisedto":"S2-1901258","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":742.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1901154.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901155","title":"Correction on monitoring event for 'availability after DDN failure'.","source":"Samsung","contact":"Sunghoon Kim","contact-id":59112,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Change to 'Availability after Downlink Data Notification failure'.","secretary_remarks":"Revision of S2-1900553. Agreed in parallel session. This was Block approved","agenda_item_sort_order":28,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":14510,"status":"agreed","reservation_date":"2019-01-23 02:05:38","uploaded":"2019-01-29 14:04:13","revisionof":"S2-1900553","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.4.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":956.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-190158","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1901155.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901156","title":"Correction for NF authorized to request notification for UE reachability","source":"Nokia, Nokia Shanghai Bell","contact":"Yannick Lair","contact-id":76350,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Step 0 is removed. Step 3 is modified to remove the service authorization check on a per user basis.","secretary_remarks":"Revision of S2-1900662. Postponed","agenda_item_sort_order":28,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":14540,"status":"postponed","reservation_date":"2019-01-23 02:05:41","uploaded":"2019-01-29 14:04:13","revisionof":"S2-1900662","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.4.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":983.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1901156.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901157","title":"[DRAFT] Reply LS on Clarification request on NF authorization in UE Reachability Notification Request procedure","source":"SA WG2","contact":"Yannick Lair","contact-id":76350,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG4. CC: SA WG3. Attachments: Agreed version of S2-1900662)","secretary_remarks":"Revision of S2-1900663. Revised in parallel session to S2-1901257.","agenda_item_sort_order":28,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":14560,"status":"revised","reservation_date":"2019-01-23 02:05:42","uploaded":"2019-01-29 14:04:13","revisionof":"S2-1900663","revisedto":"S2-1901257","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"SA WG3","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1901157.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901257","title":"[DRAFT] Reply LS on Clarification request on NF authorization in UE Reachability Notification Request procedure","source":"SA WG2","contact":"Yannick Lair","contact-id":76350,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG4, SA WG3. Attachments: Agreed version of S2-1900662)","secretary_remarks":"Revision of S2-1901157. WITHDRAWN","agenda_item_sort_order":28,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":14570,"status":"withdrawn","reservation_date":"2019-01-24 13:07:27","uploaded":null,"revisionof":"S2-1901157","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4, SA WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901258","title":"Fixing text related to discovery and selection","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 6.3.1 - Adding what is registered in NRF - A discovery result gives an NF profile. The NF profile may contain addressing to the NF instance and optionally NF service instances. - Not clear what message routing model means. All messages are routed via IP. - Fixing references - Clarifying what an NF may subscribe to in the NRF - Fixing terminology 'target' NF - Wrong placement of text regarding SMF - The statement: 'The result of the NF discovery procedure is applicable to any subscriber that fulfils same discovery criteria', is not really correct. When doing discovery on a SUPI the discovery result is for this SUPI, but the discovery result is a NF profile, which may contain a SUPI range, and thus the range may be valid for other subscribers. - Status subscribe notifies if NF is deregistering, or changes in the NF profile, e.g. Service instances taken in our out of service. - The text related to roaming and slicing refers to 23.502, however nothing is stated with regards to slicing is referred clause. Thus this is a generic procedure. Also NRF in home may do discovery to NRF in visited, renaming target with remote. 6.3.2 - Clarifying the NF profile is received in a discovery - Clarifying that not only SMF instance is selected but also service instance - Moved SMF text from 6.3.1 6.3.3.2 - Clarifying that NF profile of UPF is received by SMF - Clarifying that UPF instances register their NF profiles in NRF 6.3.4 - Clarifying that an AUSF instance perform authentication. 6.3.5 - Clarifying that AMF has discovery and selection functionality - Inserting 'instance' in the right places - Clarifying that NF profile is received in discovery - Clarifying that associated AMF is GUAMI associated AMF - Moving slicing related paragraph to not misinterpret that bullet list is about slicing. 6.3.6.1 - Inserting 'instance' in the right places 6.3.7 subheadings - Inserting 'instance' in the right places - 'Candidate' NFs is something the is used in selection. - Clarifying that discovery may be needed since PCF instance address may not be present in the UE context - Making a distinction between H-PCF id and H-PCF instance 6.3.8 - Inserting 'instance' in the right places - Clarifying that selection is about which UDM instance that handles a subscription 6.3.9 - Inserting 'instance' in the right places - selection 'based on available instances' is unnecessary, would a UDR consumer really ever do the opposite? 6.3.10 - Inserting 'instance' in the right places - Making sure that registration is interpreted as registration from UE - Adding that also IP address(es) may be configured in AMF","secretary_remarks":"Revision of S2-1901154. This CR was agreed","agenda_item_sort_order":28,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":14490,"status":"agreed","reservation_date":"2019-01-24 13:07:27","uploaded":"2019-01-29 14:13:35","revisionof":"S2-1901154","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":742.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-190154","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1901258.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]