[{"name":"S2-180051","title":"LS from SA WG6: LS on Integration of northbound APIs with CAPIF","source":"SA WG6","contact":"Niranth Amogh","contact-id":39608,"tdoctype":"LS in","for":"Action","abstract":"As part of the CAPIF WID for Release 15, SA WG6 has specified the Common API Framework for 3GPP northbound APIs in TS 23.222. The primary objective of CAPIF is to specify a common northbound API framework to enable consistent development of northbound APIs across 3GPP, in particular towards the common aspects (e.g. onboarding, discover, publish, authentication, API management, etc.) that apply to any northbound API definition. TS 23.222 contains detailed specification of the common aspects of the API framework and the interactions with the CAPIF core function from both the API invoker and the API exposing function. TS 23.222 also includes an informative annex 'CAPIF relationship with network exposure aspects of 3GPP systems' that shows CAPIF relationship with SCEF\/NEF, and possible integration models.Your review of this annex, and any feedback would help us in identifying any missing aspects to achieve better alignment in integration of CAPIF with the specification(s) of northbound API","secretary_remarks":"Response drafted in S2-180659. This LS was postponed. Revised at S2#126 in S2-181428.","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":18930,"status":"revised","reservation_date":"2017-12-19 11:54:36","uploaded":"2017-12-19 11:58:34","revisionof":"","revisedto":"S2-181428","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"TSG SA, TSG CT, SA WG4, CT WG3","lsoriginalls":"S6-171851","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180051.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-180068","title":"23.502: Corrections to NRF and NSSF services","source":"Telecom Italia, ZTE, Oracle","contact":"Mario Madella","contact-id":23765,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: - Fixed the misaligment between clauses 4.2.2.2.3, 4.3.2.2.3, 4.17.5, 5.2.7.3 and 5.2.16. - Resolved the Editor's note on NRF as NSSF consumer. - Minor editorial change.","secretary_remarks":"Revised, merging part of S2-180666, to S2-181126.","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19180,"status":"revised","reservation_date":"2018-01-10 07:56:35","uploaded":"2018-01-16 07:56:55","revisionof":"","revisedto":"S2-181126","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180068.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-180071","title":"23.502: NEF service for background data transfer","source":"KDDI, Convida Wireless LLC, TOYOTA ITC, Huawei","contact":"Takeshi Usui","contact-id":59388,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Update of NEF service for background data transfer. Re-wrote the interaction between the NEF and AF as a service.","secretary_remarks":"Endorsed in parallel session","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19280,"status":"endorsed","reservation_date":"2018-01-10 16:08:23","uploaded":"2018-01-16 13:03:13","revisionof":"","revisedto":"S2-181502, S2-181504","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180071.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-180072","title":"23.502: Update of NEF server for PFD management","source":"KDDI, China Unicom","contact":"Takeshi Usui","contact-id":59388,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Update of NEF service for PFD management. Re-wrote the interaction between the NEF and AF as a service. Added the Transaction Reference ID for T8 interface.","secretary_remarks":"Endorsed in parallel session","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19320,"status":"endorsed","reservation_date":"2018-01-10 16:29:34","uploaded":"2018-01-16 12:59:22","revisionof":"","revisedto":"S2-181503, S2-181505","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180072.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-180131","title":"23.502: Improvements on the specification of the subscription to Network Exposure","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. \u00a7 4.15.1: adding target UE in the table 2. 5.2.2.3.2: add 'any UE' as target of AMF event subscription + Notification target address provided by Consumer NF \/ Subscription Correlation ID provided by Event Provider 3. Clarifying Notification target address and Subscription Correlation ID throughout all Event related services 4. Splitting up throughout all Nxxx Subscription services between Event Id (Mandatory, defined as part of the Nxxx service) and Event Filter information (Maximum number of reports, \u2026) where reference to 4.15.1 is made","secretary_remarks":"Revised, merging S2-180255, S2-180643, S2-180152 and S2-180151, to S2-181125.","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19120,"status":"revised","reservation_date":"2018-01-12 09:35:56","uploaded":"2018-01-16 14:42:26","revisionof":"","revisedto":"S2-181125","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180131.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-180150","title":"23.502: Correction to Application Triggering Procedure","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The Application Trigger procedure is corrected to let NEF query UDM instead of UDR. The interaction with UDM is a 2 step process. To get the SMSF address, Nudm_UECM_Get is used. To get the GPSI to SUPI mapping Nudm_SDM_Get is used. Additionally changes to Nudm_UECM_Get and Nudm_SDM_Get service operations are also specified to align with the changes done in Application Trigger procedure.","secretary_remarks":"Merged into S2-181131","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19390,"status":"merged","reservation_date":"2018-01-12 16:43:27","uploaded":"2018-01-16 11:30:10","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180150.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-180151","title":"23.502: Correction to Event Filter","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The mention of parameters like maximum number of reports, maximum duration of reporting etc are moved to be along with Event filter parameter mentioning with a reference to clause 4.15.1","secretary_remarks":"Merged into S2-181125.","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19250,"status":"merged","reservation_date":"2018-01-12 16:43:27","uploaded":"2018-01-16 11:30:10","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180151.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-180152","title":"23.502: Clarification on Network Capability Exposure for Analytics","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: It is proposed to remove this procedure from the specification.","secretary_remarks":"Merged into S2-181125.","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19170,"status":"merged","reservation_date":"2018-01-12 16:43:27","uploaded":"2018-01-16 11:30:10","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180152.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-180155","title":"23.502: Clarification on Use of List of Parameter Values to Match in Event Filters","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Clarify how 'list of parameter values to match' in the Event Filter can be used for some example events like area of interest, location change notification and AN type change notification. 2. For the UE reachability status event the words 'along with optional list of sessions to be activated' is removed. The reason is this was added during SA WG2#121 during which time Service Request call flow modelling was discussed through use of Namf_EventExposure_Notify. However in later meetings it has been agreed to use Nsmf_PDUSession_UpdateSMContext for this purpose. Hence there is no need to notify 'optional list of sessions to be activated' when UE becomes reachable.","secretary_remarks":"Revised to S2-181128.","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19260,"status":"revised","reservation_date":"2018-01-12 16:43:27","uploaded":"2018-01-16 11:30:10","revisionof":"","revisedto":"S2-181128","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180155.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-180178","title":"TS 23.502: Change to Required Inputs for Update service operation","source":"OTD","contact":"Jeffrey Gray","contact-id":61557,"tdoctype":"discussion","for":"Discussion","abstract":"This paper discusses the need for a change to the required input field for the NF Management Update service operation of the 5G architecture.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19330,"status":"noted","reservation_date":"2018-01-12 21:47:01","uploaded":"2018-01-16 13:56:28","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180178.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-180179","title":"23.502: Update Service operation required imputs","source":"OTD","contact":"Jeffrey Gray","contact-id":61557,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Specifies that the NF profile of the consumer NF be used as a required input for the NFUpdate service operation and removed as an optional parameter for the 'Inputs, Optional' field.","secretary_remarks":"Agreed in parallel session. Block Approved","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19340,"status":"approved","reservation_date":"2018-01-12 21:53:42","uploaded":"2018-01-16 13:56:28","revisionof":"","revisedto":"S2-181684","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180179.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-180242","title":"23.501: Clarification on UDR","source":"Samsung, Deutsche Telekom","contact":"Jicheol Lee","contact-id":51554,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: First change. Update the figure 4.2.5-2 to add oval representation over the Nudr reference point to make sure the Nudr has a service-based interface. In addition, some editorial update using the agreed terminologies (i.e. NF Service Consumer) for service based interface. Second change. To make a consistency for what is inside the UDR. In other words, the figure contains four types of data (i.e. subscription data, policy data, structured data for data exposure, and application data) and the description for what the UDR includes are stated as follows: As depicted in Figure 4.2.5-2, the 5G System architecture allows the UDM, PCF and NEF to store data in the UDR, including subscription data and policy data by UDM and PCF, structured data for exposure and application data (including Packet Flow Descriptions (PFDs) for application detection, application request information for multiple UEs) by the NEF To make them consistent, it is proposed to replace 'application request","secretary_remarks":"Endorsed in parallel session","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19430,"status":"endorsed","reservation_date":"2018-01-15 01:23:54","uploaded":"2018-01-16 07:04:46","revisionof":"","revisedto":"S2-181654","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"D","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180242.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-180243","title":"23.501: NF Service Discovery","source":"Samsung","contact":"Jicheol Lee","contact-id":51554,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. It is proposed to make sure that the NRF returns the HTTP URL-style endpoint address for the discovered NF service instances 2. NF Service Discovery is also service-based 3. NRF discovers the UPF's N4 reference point address.","secretary_remarks":"Revised to S2-181135.","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19500,"status":"revised","reservation_date":"2018-01-15 01:35:35","uploaded":"2018-01-16 07:04:46","revisionof":"","revisedto":"S2-181135","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180243.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-180244","title":"23.502: NF Service Discovery Corrections in 23.502","source":"Samsung","contact":"Jicheol Lee","contact-id":51554,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: First Change (in clause 4.3.2.2.3.2) and Second Changes (in clause 4.17.5) make sure to include the endpoint address (i.e. HTTP URLs) for the discovered NF services as a result of NF\/NF Service Discovery from the NRF.","secretary_remarks":"Revised to S2-181127.","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19210,"status":"revised","reservation_date":"2018-01-15 01:40:38","uploaded":"2018-01-16 07:04:46","revisionof":"","revisedto":"S2-181127","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180244.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-180255","title":"23.502: Clarification on Event co-relation ID","source":"CATT","contact":"Yali Guo","contact-id":67048,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarify each Event co-relation ID assoiates to one event; Add Event co-relation ID in the Nudm_EventExposure and Nnef_EventExposure service","secretary_remarks":"Merged into S2-181125.","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19150,"status":"merged","reservation_date":"2018-01-15 05:57:55","uploaded":"2018-01-16 11:52:46","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180255.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-180258","title":"23.501: T8 support in TS 23.501","source":"KDDI","contact":"Takeshi Usui","contact-id":59388,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Add description for T8 support. The description in TS 23.501 is similar with the one in TS 23.682.","secretary_remarks":"Not Handled","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19070,"status":"not treated","reservation_date":"2018-01-15 06:21:50","uploaded":"2018-01-16 13:38:56","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180258.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-180336","title":"23.502: Clarification on Communication Pattern and Expected UE behaviour","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: It is proposed to add the Communication Pattern parameters into the parameter list of Expected UE Behaviour.","secretary_remarks":"Revised to S2-181124.","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19090,"status":"revised","reservation_date":"2018-01-15 13:20:29","uploaded":"2018-01-16 12:28:57","revisionof":"","revisedto":"S2-181124","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180336.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-180337","title":"TS 23.502_Discussion on Communication Pattern and Expected UE behaviour","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"discussion","for":"Approval","abstract":"This contribution deals with the communication pattern provisioning.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19080,"status":"noted","reservation_date":"2018-01-15 13:20:29","uploaded":"2018-01-16 12:28:57","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180337.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-180338","title":"23.501: Funtionalities mapping between CAPIF and NEF architecture","source":"Huawei","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Add a new reference to TS 23.222 in the references part. Add the CAPIF into abbreviation part. Add a new sentence refer the role NEF in the CAPIF framework in clause 6.2.5.","secretary_remarks":"Not Handled","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":18980,"status":"not treated","reservation_date":"2018-01-15 13:20:29","uploaded":"2018-01-16 12:28:57","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180338.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-180339","title":"Funtionalities mapping between CAPIF and SCEF architecture","source":"Huawei","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add a new reference to TS 23.222 in the references part. Add the CAPIF into abbreviation part. Add a new sentence refer the role SCEF in the CAPIF framework in clause 4.4.8, and clarify that in a CAPIF, some of the functionalities of SCEF listed above are provided by the CAPIF core function as specified in TS 23.222[43], and that take precedence over the ones listed above when SCEF and CAPIF are both deployed..","secretary_remarks":"Not Handled","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":18950,"status":"not treated","reservation_date":"2018-01-15 13:20:29","uploaded":"2018-01-16 12:28:57","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.682,"crspecversion":"15.3.0","workitem":[{"winame":"NAPS"}],"crnumber":377.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180339.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-180343","title":"23.502: Clarification on the services for External Parameter Provisioning","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Modify the original figure of 4.15.6.2-1, and related descriptions in clause 4.15.6.2 to reflect the proposals mentioned above.","secretary_remarks":"Revised to S2-181129.","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19290,"status":"revised","reservation_date":"2018-01-15 13:20:30","uploaded":"2018-01-16 12:28:57","revisionof":"","revisedto":"S2-181129","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180343.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-180396","title":"23.502: update Nnrf_NFDiscovery service based on the UE IP address","source":"China Mobile","contact":"Wei Chen","contact-id":57801,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: New texts are added to clarify that UE IP address can be a opitional input parameter in Nnrf_NFDiscovery service to allow NEF to discover the BSF with the input of UE IP address. Besides, BSF is added into the cosumers list of Nnrf_NFManagement_NFRegister service to make NRF to store the BSF service information.","secretary_remarks":"Revised to S2-181130.","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19350,"status":"revised","reservation_date":"2018-01-15 15:47:37","uploaded":"2018-01-16 14:29:21","revisionof":"","revisedto":"S2-181130","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180396.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-180432","title":"23.501: Supporting Common API framework for NEF","source":"Convida Wireless LLC, Qualcomm Incorporated","contact":"Michael Starsinic","contact-id":72107,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarifies that functionality such as authentication, authorization and service capability API discovery are supported by the NEF based on the Common API Framework (CAPIF).","secretary_remarks":"Revised in parallel session to S2-181265","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":18990,"status":"revised","reservation_date":"2018-01-15 17:53:09","uploaded":"2018-01-16 12:06:20","revisionof":"","revisedto":"S2-181265","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180432.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-180470","title":"23.502: Application Trigger procedure updates","source":"Ericsson, Convida Wireless LLC","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The usage of Nudm_SDM_Get operation is described including new Subscription Data type: 'Identity translation'. This new Subscription Data type requires GPSI as access key, instead of SUPI. Nnef_Trigger service operation names are updated to reflect better the functionality performed.","secretary_remarks":"Revised, merging S2-180150, to S2-181131.","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19400,"status":"revised","reservation_date":"2018-01-15 23:43:16","uploaded":"2018-01-16 14:30:19","revisionof":"","revisedto":"S2-181131","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180470.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-180473","title":"23.502: Nudm SDM service Subscription Data types updates","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Data items are added\/removed for multiple Subscription Data types for the Nudm SDM service. Added information: - UE Usage Type for EPC interworking - LADN indicator per DNN - Priority services indicator (MPS) Removed information: -Homogeneous VoIP support indicator is provided by AMF to UDM since it is required for internal UDM processing, but it is not part of 'Access and Mobility Subscription data' required by AMF. -Default APN is not used by SMF.","secretary_remarks":"Revised to S2-181132.","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19460,"status":"revised","reservation_date":"2018-01-15 23:43:16","uploaded":"2018-01-16 14:30:19","revisionof":"","revisedto":"S2-181132","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180473.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-180479","title":"23.502: NEF service definitions for AF influence","source":"Huawei","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: It is proposed to add NEF service defintions to support AF influence. This paper relates to S2-180139 and S2-180480","secretary_remarks":"Revised to S2-181136.","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19530,"status":"revised","reservation_date":"2018-01-16 01:03:55","uploaded":"2018-01-16 02:31:56","revisionof":"","revisedto":"S2-181136","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180479.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-180516","title":"23.502: Fixes for UDM\/UDR services","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1) Fix the UDM service operation 2) Fix the UDR service name 3) Update subscription data table for Registration and MM subscription data type as PEI (i.e. IMEI), Homogenous support of IMS voice over PS Sessions are paramers sent by AMF to UDM and it need not be sent in the other direction.","secretary_remarks":"Revised to S2-181133.","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19440,"status":"revised","reservation_date":"2018-01-16 04:16:04","uploaded":"2018-01-16 14:57:01","revisionof":"","revisedto":"S2-181133","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180516.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-180606","title":"23.501: Clarification on UDM service consumption order of UECM and SDM","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Update the texts describing\/implying the UDM service operation order description","secretary_remarks":"Revised to S2-181134.","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19480,"status":"revised","reservation_date":"2018-01-16 07:31:11","uploaded":"2018-01-16 14:20:36","revisionof":"","revisedto":"S2-181134","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180606.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-180630","title":"Non-roaming Architecture for Network Exposure Function in reference point representation","source":"Intel","contact":"Puneet Jain","contact-id":36283,"tdoctype":"discussion","for":"Agreement","abstract":"This paper proposes to introduce Non-roaming Architecture for Network Exposure Function in reference point representation.","secretary_remarks":"Not Handled","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19030,"status":"not treated","reservation_date":"2018-01-16 08:44:52","uploaded":"2018-01-16 09:27:00","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180630.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-180643","title":"23.502: Clarification on Event co-relation ID","source":"ZTE","contact":"Jinguo Zhu","contact-id":32987,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarify that the Event co-relation ID is per event notification subscription.","secretary_remarks":"Merged into S2-181125.","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19160,"status":"merged","reservation_date":"2018-01-16 08:52:26","uploaded":"2018-01-16 10:21:01","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180643.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-180655","title":"23.501: Non-roaming Architecture for Network Exposure Function in reference point representation","source":"Intel","contact":"Puneet Jain","contact-id":36283,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Non-roaming architecture for Network Exposure Function reference point representation corresponding to service based interface between NEF and AF is added.","secretary_remarks":"Revised in parallel session to S2-181266","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19040,"status":"revised","reservation_date":"2018-01-16 09:12:03","uploaded":"2018-01-16 09:27:00","revisionof":"","revisedto":"S2-181266","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180655.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-180659","title":"[DRAFT] Reply LS on Integration of northbound APIs with CAPIF","source":"Qualcomm Incorporated","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG6","secretary_remarks":"Response to S2-180051. Not Handled","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19020,"status":"not treated","reservation_date":"2018-01-16 09:19:35","uploaded":"2018-01-16 14:13:31","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG6","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180659.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-180661","title":"Supporting Common API framework for SCEF","source":"Qualcomm Incorporated, Convida Wireless LLC","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarifies that SCEF functionality including authentication, authorization and service capability API discovery are supported via T8 based on the Common API Framework (CAPIF).","secretary_remarks":"Revised in parallel session to S2-181264.","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":18960,"status":"revised","reservation_date":"2018-01-16 09:23:53","uploaded":"2018-01-16 14:13:31","revisionof":"","revisedto":"S2-181264","release":"Rel-15","crspec":23.682,"crspecversion":"15.3.0","workitem":[{"winame":"NAPS"}],"crnumber":382.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180661.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-180666","title":"23.502: Update SMF selection","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Replace the Silce Selection Request message with the service-based invocation as described in the TS 23.502. 2. Add the S-NSSAI from the Configured NSSAI for the HPLMN in the request sent from AMF to NSSF during PDU Session Establishment procedure 3. Update NSSF Services described in the TS 23.502. Mapping of Requested NSSAI should be included in the input optionally. 4. Clarify NF consumer (e.g. AMF) discover NSSF as described in the S2-180663.","secretary_remarks":"NSSAI mapping part merged into S2-181126.","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19230,"status":"merged","reservation_date":"2018-01-16 09:26:48","uploaded":"2018-01-16 12:25:28","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180666.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-180681","title":"Integration of northbound APIs with CAPIF","source":"Qualcomm Incorporated, Convida Wireless LLC","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"discussion","for":"Agreement","abstract":"This paper discusses how to incorporate CAPIF into SA WG2's work on northbound API specifications.","secretary_remarks":"Not Handled","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":18940,"status":"not treated","reservation_date":"2018-01-16 09:31:50","uploaded":"2018-01-16 14:13:31","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180681.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-180706","title":"23.502: Updates of NSSF Services","source":"NTT DOCOMO","contact":"Malla Reddy Sama","contact-id":48655,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Generalizing the rejected S-NSSAI, and not to restrict the rejected S-NSSAI to be only a part of Requested NSSAI","secretary_remarks":"Endorsed in parallel session","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19240,"status":"endorsed","reservation_date":"2018-01-16 10:37:45","uploaded":"2018-01-16 10:58:18","revisionof":"","revisedto":"S2-181702","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180706.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181124","title":"23.502: Clarification on Communication Pattern and Expected UE behaviour","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: It is proposed to add the Communication Pattern parameters into the parameter list of Expected UE Behaviour.","secretary_remarks":"Revision of S2-180336. Endorsed in parallel session Revised to S2-181377.","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19100,"status":"revised","reservation_date":"2018-01-23 13:27:54","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180336","revisedto":"S2-181377","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181124.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181125","title":"23.502: Improvements on the specification of the subscription to Network Exposure","source":"Nokia, Nokia Shanghai Bell, Huawei, CATT, ZTE, Hisilicon,","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. \u00a7 4.15.1: adding target UE in the table 2. 5.2.2.3.2: add 'any UE' as target of AMF event subscription + Notification target address provided by Consumer NF \/ Subscription Correlation ID provided by Event Provider 3. Clarifying Notification target address and Subscription Correlation ID throughout all Event related services 4. Splitting up throughout all Nxxx Subscription services between Event Id (Mandatory, defined as part of the Nxxx service) and Event Filter information (Maximum number of reports, \u2026) where reference to 4.15.1 is made","secretary_remarks":"Revision of S2-180131, merging S2-180255, S2-180643, S2-180152 and S2-180151. Revised in parallel session to S2-181268","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19130,"status":"revised","reservation_date":"2018-01-23 13:27:54","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180131","revisedto":"S2-181268","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181125.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181126","title":"23.502: Corrections to NRF and NSSF services","source":"Telecom Italia, ZTE, Oracle, Huawei","contact":"Mario Madella","contact-id":23765,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: - Fixed the misaligment between clauses 4.2.2.2.3, 4.3.2.2.3, 4.17.5, 5.2.7.3 and 5.2.16. - Resolved the Editor's note on NRF as NSSF consumer. - Minor editorial change.","secretary_remarks":"Revision of S2-180068, merging part of S2-180666. Revised in parallel session to S2-181267","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19190,"status":"revised","reservation_date":"2018-01-23 13:27:54","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180068","revisedto":"S2-181267","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181126.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181127","title":"23.502: NF Service Discovery Corrections in 23.502","source":"Samsung","contact":"Jicheol Lee","contact-id":51554,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: First Change (in clause 4.3.2.2.3.2) and Second Changes (in clause 4.17.5) make sure to include the endpoint address (i.e. HTTP URLs) for the discovered NF services as a result of NF\/NF Service Discovery from the NRF.","secretary_remarks":"Revision of S2-180244. Endorsed in parallel session","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19220,"status":"endorsed","reservation_date":"2018-01-23 13:27:54","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180244","revisedto":"S2-181657","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181127.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181128","title":"23.502: Clarification on Use of List of Parameter Values to Match in Event Filters","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Clarify how 'list of parameter values to match' in the Event Filter can be used for some example events like area of interest, location change notification and AN type change notification. 2. For the UE reachability status event the words 'along with optional list of sessions to be activated' is removed. The reason is this was added during SA WG2#121 during which time Service Request call flow modelling was discussed through use of Namf_EventExposure_Notify. However in later meetings it has been agreed to use Nsmf_PDUSession_UpdateSMContext for this purpose. Hence there is no need to notify 'optional list of sessions to be activated' when UE becomes reachable.","secretary_remarks":"Revision of S2-180155. Agreed in parallel session. Block Approved","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19270,"status":"approved","reservation_date":"2018-01-23 13:27:54","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180155","revisedto":"S2-181555","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181128.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181129","title":"23.502: Clarification on the services for External Parameter Provisioning","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Modify the original figure of 4.15.6.2-1, and related descriptions in clause 4.15.6.2 to reflect the proposals mentioned above.","secretary_remarks":"Revision of S2-180343. Revised to S2-181355.","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19300,"status":"revised","reservation_date":"2018-01-23 13:27:54","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180343","revisedto":"S2-181355","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181129.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181130","title":"23.502: update Nnrf_NFDiscovery service based on the UE IP address","source":"China Mobile","contact":"Wei Chen","contact-id":57801,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: New texts are added to clarify that UE IP address can be a opitional input parameter in Nnrf_NFDiscovery service to allow NEF to discover the BSF with the input of UE IP address. Besides, BSF is added into the cosumers list of Nnrf_NFManagement_NFRegister service to make NRF to store the BSF service information.","secretary_remarks":"Revision of S2-180396. Agreed in parallel session. China mobile raise an issue with there being no IP address included. Revised to S2-181383.","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19360,"status":"revised","reservation_date":"2018-01-23 13:27:54","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180396","revisedto":"S2-181383","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181130.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181131","title":"23.502: Application Trigger procedure updates","source":"Ericsson, Convida Wireless LLC","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The usage of Nudm_SDM_Get operation is described including new Subscription Data type: 'Identity translation'. This new Subscription Data type requires GPSI as access key, instead of SUPI. Nnef_Trigger service operation names are updated to reflect better the functionality performed.","secretary_remarks":"Revision of S2-180470, merging S2-180150. Revised to S2-181357.","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19410,"status":"revised","reservation_date":"2018-01-23 13:27:54","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180470","revisedto":"S2-181357","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181131.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181132","title":"23.502: Nudm SDM service Subscription Data types updates","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Data items are added\/removed for multiple Subscription Data types for the Nudm SDM service. Added information: - UE Usage Type for EPC interworking - LADN indicator per DNN - Priority services indicator (MPS) Removed information: -Homogeneous VoIP support indicator is provided by AMF to UDM since it is required for internal UDM processing, but it is not part of 'Access and Mobility Subscription data' required by AMF. -Default APN is not used by SMF.","secretary_remarks":"Revision of S2-180473. Agreed in parallel session. Block Approved","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19470,"status":"approved","reservation_date":"2018-01-23 13:27:54","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180473","revisedto":"S2-181624","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181132.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181133","title":"23.502: Fixes for UDM\/UDR services","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1) Fix the UDM service operation 2) Fix the UDR service name 3) Update subscription data table for Registration and MM subscription data type as PEI (i.e. IMEI), Homogenous support of IMS voice over PS Sessions are paramers sent by AMF to UDM and it need not be sent in the other direction.","secretary_remarks":"Revision of S2-180516. Agreed in parallel session. Block Approved","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19450,"status":"approved","reservation_date":"2018-01-23 13:27:54","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180516","revisedto":"S2-181758","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181133.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181134","title":"23.501: Clarification on UDM service consumption order of UECM and SDM","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Update the texts describing\/implying the UDM service operation order description","secretary_remarks":"Revision of S2-180606. This was endorsed.","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19490,"status":"endorsed","reservation_date":"2018-01-23 13:27:54","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180606","revisedto":"S2-181557","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181134.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181135","title":"23.501: NF Service Discovery","source":"Samsung","contact":"Jicheol Lee","contact-id":51554,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. It is proposed to make sure that the NRF returns the HTTP URL-style endpoint address for the discovered NF service instances 2. NF Service Discovery is also service-based 3. NRF discovers the UPF's N4 reference point address.","secretary_remarks":"Revision of S2-180243. Revised in parallel session to S2-181269","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19510,"status":"revised","reservation_date":"2018-01-23 13:27:54","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180243","revisedto":"S2-181269","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181135.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181136","title":"23.502: NEF service definitions for AF influence","source":"Huawei","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: It is proposed to add NEF service defintions to support AF influence. This paper relates to S2-180139 and S2-180480","secretary_remarks":"Revision of S2-180479. Revised in parallel session to S2-181270","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19540,"status":"revised","reservation_date":"2018-01-23 13:27:54","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180479","revisedto":"S2-181270","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181136.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181264","title":"Supporting Common API framework for SCEF","source":"Qualcomm Incorporated, Convida Wireless LLC","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarifies that SCEF functionality including authentication, authorization and service capability API discovery are supported via T8 based on the Common API Framework (CAPIF).","secretary_remarks":"Revision of S2-180661. This CR was agreed. Revised at S2#126 in S2-182047","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":18970,"status":"revised","reservation_date":"2018-01-25 06:56:08","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180661","revisedto":"S2-182047","release":"Rel-15","crspec":23.682,"crspecversion":"15.3.0","workitem":[{"winame":"NAPS"}],"crnumber":382.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181264.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181265","title":"23.501: Supporting Common API framework for NEF","source":"Convida Wireless LLC, Qualcomm Incorporated","contact":"Michael Starsinic","contact-id":72107,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarifies that functionality such as authentication, authorization and service capability API discovery are supported by the NEF based on the Common API Framework (CAPIF).","secretary_remarks":"Revision of S2-180432. Revised to S2-181353.","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19000,"status":"revised","reservation_date":"2018-01-25 06:56:09","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180432","revisedto":"S2-181353","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181265.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181266","title":"23.501: Non-roaming Architecture for Network Exposure Function in reference point representation","source":"Intel","contact":"Puneet Jain","contact-id":36283,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Non-roaming architecture for Network Exposure Function reference point representation corresponding to service based interface between NEF and AF is added.","secretary_remarks":"Revision of S2-180655. Revised to S2-181354.","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19050,"status":"revised","reservation_date":"2018-01-25 06:56:09","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180655","revisedto":"S2-181354","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181266.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181267","title":"23.502: Corrections to NRF and NSSF services","source":"Telecom Italia, ZTE, Oracle, Huawei","contact":"Mario Madella","contact-id":23765,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: - Fixed the misaligment between clauses 4.2.2.2.3, 4.3.2.2.3, 4.17.5, 5.2.7.3 and 5.2.16. - Resolved the Editor's note on NRF as NSSF consumer. - Minor editorial change.","secretary_remarks":"Revision of S2-181126. Agreed in parallel session. Approved","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19200,"status":"approved","reservation_date":"2018-01-25 06:56:09","uploaded":"2018-01-26 18:07:53","revisionof":"S2-181126","revisedto":"S2-181847","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181267.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181268","title":"23.502: Improvements on the specification of the subscription to Network Exposure","source":"Nokia, Nokia Shanghai Bell, Huawei, CATT, ZTE, Hisilicon,","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. \u00a7 4.15.1: adding target UE in the table 2. 5.2.2.3.2: add 'any UE' as target of AMF event subscription + Notification target address provided by Consumer NF \/ Subscription Correlation ID provided by Event Provider 3. Clarifying Notification target address and Subscription Correlation ID throughout all Event related services 4. Splitting up throughout all Nxxx Subscription services between Event Id (Mandatory, defined as part of the Nxxx service) and Event Filter information (Maximum number of reports, \u2026) where reference to 4.15.1 is made","secretary_remarks":"Revision of S2-181125. Agreed in parallel session. Block Approved","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19140,"status":"approved","reservation_date":"2018-01-25 06:56:09","uploaded":"2018-01-26 18:07:53","revisionof":"S2-181125","revisedto":"S2-181453, S2-181804","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181268.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181269","title":"23.501: NF Service Discovery","source":"Samsung","contact":"Jicheol Lee","contact-id":51554,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. It is proposed to make sure that the NRF returns the HTTP URL-style endpoint address for the discovered NF service instances 2. NF Service Discovery is also service-based 3. NRF discovers the UPF's N4 reference point address.","secretary_remarks":"Revision of S2-181135. Agreed in parallel session. Block Approved","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19520,"status":"approved","reservation_date":"2018-01-25 06:56:09","uploaded":"2018-01-26 18:07:53","revisionof":"S2-181135","revisedto":"S2-181656","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181269.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181270","title":"23.502: NEF service definitions for AF influence","source":"Huawei","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: It is proposed to add NEF service defintions to support AF influence. This paper relates to S2-180139 and S2-180480","secretary_remarks":"Revision of S2-181136. Revised to S2-181356.","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19550,"status":"revised","reservation_date":"2018-01-25 06:56:09","uploaded":"2018-01-26 18:07:53","revisionof":"S2-181136","revisedto":"S2-181356","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181270.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181353","title":"23.501: Supporting Common API framework for NEF","source":"Convida Wireless LLC, Qualcomm Incorporated","contact":"Michael Starsinic","contact-id":72107,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarifies that functionality such as authentication, authorization and service capability API discovery are supported by the NEF based on the Common API Framework (CAPIF).","secretary_remarks":"Revision of S2-181265. Approved","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19010,"status":"approved","reservation_date":"2018-01-26 10:04:47","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181265","revisedto":"S2-181988","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181353.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181354","title":"23.501: Non-roaming Architecture for Network Exposure Function in reference point representation","source":"Intel","contact":"Puneet Jain","contact-id":36283,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Non-roaming architecture for Network Exposure Function reference point representation corresponding to service based interface between NEF and AF is added.","secretary_remarks":"Revision of S2-181266. This was endorsed.","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19060,"status":"endorsed","reservation_date":"2018-01-26 10:04:47","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181266","revisedto":"S2-181696","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181354.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181355","title":"23.502: Clarification on the services for External Parameter Provisioning","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Modify the original figure of 4.15.6.2-1, and related descriptions in clause 4.15.6.2 to reflect the proposals mentioned above.","secretary_remarks":"Revision of S2-181129. Approved","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19310,"status":"approved","reservation_date":"2018-01-26 10:04:47","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181129","revisedto":"S2-181556","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181355.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181356","title":"23.502: NEF service definitions for AF influence","source":"Huawei","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: It is proposed to add NEF service defintions to support AF influence. This paper relates to S2-180139 and S2-180480","secretary_remarks":"Revision of S2-181270. Approved","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19560,"status":"approved","reservation_date":"2018-01-26 10:04:47","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181270","revisedto":"S2-181584","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181356.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181357","title":"23.502: Application Trigger procedure updates","source":"Ericsson, Convida Wireless LLC","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The usage of Nudm_SDM_Get operation is described including new Subscription Data type: 'Identity translation'. This new Subscription Data type requires GPSI as access key, instead of SUPI. Nnef_Trigger service operation names are updated to reflect better the functionality performed.","secretary_remarks":"Revision of S2-181131. Approved","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19420,"status":"approved","reservation_date":"2018-01-26 10:04:47","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181131","revisedto":"S2-181638","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181357.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181377","title":"23.502: Clarification on Communication Pattern and Expected UE behaviour","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: It is proposed to add the Communication Pattern parameters into the parameter list of Expected UE Behaviour.","secretary_remarks":"Revision of S2-181124. For e-mail approval. WITHDRAWN","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19110,"status":"withdrawn","reservation_date":"2018-01-26 17:55:41","uploaded":null,"revisionof":"S2-181124","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181383","title":"23.502: update Nnrf_NFDiscovery service based on the UE IP address","source":"China Mobile","contact":"Wei Chen","contact-id":57801,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: New texts are added to clarify that UE IP address can be a opitional input parameter in Nnrf_NFDiscovery service to allow NEF to discover the BSF with the input of UE IP address. Besides, BSF is added into the cosumers list of Nnrf_NFManagement_NFRegister service to make NRF to store the BSF service information.","secretary_remarks":"Revision of S2-181130. For e-mail approval. e-mail revision 2 approved. Revised to S2-181405.","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19370,"status":"revised","reservation_date":"2018-01-26 17:55:41","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181130","revisedto":"S2-181405","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181383.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181405","title":"23.502: update Nnrf_NFDiscovery service based on the UE IP address","source":"China Mobile","contact":"Wei Chen","contact-id":57801,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: New texts are added to clarify that UE IP address can be a opitional input parameter in Nnrf_NFDiscovery service to allow NEF to discover the BSF with the input of UE IP address. Besides, BSF is added into the cosumers list of Nnrf_NFManagement_NFRegister service to make NRF to store the BSF service information.","secretary_remarks":"e-mail revision 2 of S2-181383. Approved","agenda_item_sort_order":29,"ainumber":"6.5.11","ainame":"Framework functions","tdoc_agenda_sort_order":19380,"status":"approved","reservation_date":"2018-02-02 10:04:25","uploaded":"2018-02-02 10:30:31","revisionof":"S2-181383","revisedto":"S2-181783","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181405.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]