[{"name":"S2-1910872","title":"LS from CT WG4: LS on Support of Network Address Translation in the User Plane function","source":"CT WG4","contact":"yong yang","contact-id":59744,"tdoctype":"LS in","for":"Action","abstract":"CT WG4 has discussed the contribution C4-194233 which proposes one protocol solution over N4\/Sxb to support Network Address Translation in the UP function. Several companies expressed their support to introduce support of NAT in the user plane function. This is a legacy feature used in many operators' network to support various use cases. However, a few companies believe SA WG2 should specify first stage 2 requirements for the control over N4\/Sxb of NAT functionalities in the user plane function, if any, before CT WG4 can specify any protocol solution. Action: CT WG4 kindly requests SA WG2 to answer whether specific requirements are expected for the control of NAT in the user plane function over N4\/Sxb and, if so, to consider specifying the relevant stage 2 requirements.","secretary_remarks":"Postponed S2-1909962 from S2#135. Responses drafted in S2-1910981, S2-1911744, S2-1911879 and S2-1911889. Final response in S2-1912762","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10080,"status":"replied to","reservation_date":"2019-10-30 08:52:12","uploaded":"2019-11-04 09:40:45","revisionof":"S2-1909962","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG3","lsoriginalls":"C4-194528","lsreply":"S2-1912762","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1910872.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910882","title":"LS from NGMN: Secondary node sharing","source":"NGMN","contact":"Klaus Moschner","contact-id":59428,"tdoctype":"LS in","for":"Information","abstract":"NGMN study on small cell cost sharing: There is a long held vision of very high capacity networks using small cells in areas of high demand. With the expected availability of large quantities of mmWave spectrum for 5G, this opportunity in principle becomes even greater. But the economics of small cell deployment have proved very challenging in practice - and this challenge will only increase at mmWave frequencies, where coverage of an individual cell is typically even smaller. Unless the industry can find ways to reduce the per cell building, operation and maintenance costs, the opportunity to build out small cell networks using mmWave spectrum will be severely constrained. NGMN therefore carried out a study to identify and assess different approaches to improving the economics of small cells through some form of cost sharing between operators (with NR small cells typically anchored to a NR or E-UTRA coverage layer). This study was carried out as part of a wider project called 'Spectrum and Deployment Efficiencies'. At present, only an NGMN-internal report has been produced, but we expect to publish external reports soon. Secondary node sharing: In the study described above, as well as recognising the value of infrastructure sharing, we identified an architectural approach that we believe could be important and beneficial. This architectural approach is based on MOCN sharing, but specifically tailored to the small cell use case. It aims to achieve the greater cost savings of MOCN sharing, while addressing regulator concerns about the reduction in competition that MOCN sharing may bring. The key element of this approach is to embrace MOCN sharing, but only for high frequency (particularly mmWave) small cells. We anticipate that these small cells will primarily be used in a dual connectivity architecture, as secondary nodes in combination with a low frequency (anchor layer) master node. We therefore believe that there is value in secondary node sharing: a single small cell, shared between multiple MNOs, working as a secondary node in conjunction with the master nodes of multiple MNOs simultaneously. {...}","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10040,"status":"noted","reservation_date":"2019-10-30 09:03:45","uploaded":"2019-11-04 09:40:45","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"SA WG2","lsoriginalls":"MGMN_191025","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1910882.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910885","title":"LS from ETSI TC LI: LS to SA WG5 and SA WG2 on 5G Cell ID(s) in the SA WG5 billing system, related to Retained Data regulations","source":"ETSI TC LI","contact":"Gerald McQuaid","contact-id":25351,"tdoctype":"LS in","for":"Action","abstract":"ETSI TC LI thanks SA WG2, and SA WG5 for the reply LS on 5G Cell ID(s) in the SA WG5 billing specifications, and the confirmation on the current SA WG5 charging specifications for 5G access related to the user location information as information which will be available in the CHF CDRs generated for PDU sessions, with the granularity of the Cell Id when reported. In the context of dual connectivity, only the Cell Id of the Master Node is currently specified. ETSI TC LI confirms the need to have the capabilities of reporting the PSCell Id to the AMF, including the PSCell Id in addition to the PCELL in CHF CDRs for AMF. Therefore, ETSI TC LI kindly asks SA WG5 to include such functionality in its investigation on their ongoing Rel-16 work 'Charging AMF in 5G System Architecture Phase 1'. However, based on the recent work developed between SA WG2 and RAN WG3 on PSCell ID and PCELL information, as highlighted by the reply LS from SA WG2 to ETSI TC LI on Reporting all Cell IDs in 5G (S5-195060\/ S2-1908634), SA WG5 indicated that their specifications do not allow the PSCell Id to be available in the Billing system for EPC, since no MME CDR is specified for this context, and the PSCell Id is not propagated beyond the MME. As a result, ETSI TC LI kindly asks that: - Either the MME is a source of information for SA WG5 billing system to provide the available PSCell Ids in this node; - Or PSCell IDs to be made available at the SGW level, as primary source of information to SA WG5 billing for EPC usage. Such availability could be achieved by further development by SA WG2 either from MME or from RAN. In either case, such information source should be reliable and present at the beginning, at change of TAI\/TAU and at the end of session\/call, as such information could be used as possible evidence for Justice. Secondary RAT data usage report with PSCELL IDs could be a solution but only if it is reliable information available at the beginning\/end of call\/session, or at TAI\/TAU change during call\/session. Action: ETSI TC LI kindly asks SA WG2 to take the above request into account on EPC issue. TC LI kindly asks SA WG2 to ensure that the Secondary RAT data Usage Reports at the SGW are always available at the beginning\/end of call\/session and at TA change, in order to populate the 5GC billing system with PSCell IDs.","secretary_remarks":"This LS was postponed.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10140,"status":"postponed","reservation_date":"2019-10-30 09:03:45","uploaded":"2019-11-04 09:40:45","revisionof":"","revisedto":"S2-2000012","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG5, SA WG2","Cc":"TSG SA, SA WG3-LI, RAN WG3","lsoriginalls":"LI(19)P52055","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1910885.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910895","title":"LS from SA WG3: Reply LS to LS on 5GS Enhanced support of OTA mechanism for UICC configuration parameter update (C4-193790)","source":"SA WG3","contact":"Suresh Nair","contact-id":70166,"tdoctype":"LS in","for":"Information","abstract":"SA WG3 would like to thank CT WG4 for the LS received in S3-193661 (C4-193790). SA WG3 expects that CT WG4 proposed WID will only define new APIs to enable the UDM to request the encapsulation of UICC configuration parameters into secured packet format from the OTA server. SA WG3 understanding is therefore that the 5G OTA NF will not define storage and handling of OTA keys or other sensitive data and also, the definition of 5G OTA NF will not impact the existing OTA specifications. Therefore, SA WG3 does not foresee any impact on the security procedures from the CT WG4 proposed WID on '5GS Enhanced support of OTA mechanism for UICC configuration parameter update', as existing mechanisms such as SBA and NDS\/IP can be reused for protection of communication to the 5G OTA NF and for access control.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10050,"status":"noted","reservation_date":"2019-10-30 09:03:47","uploaded":"2019-11-04 09:40:45","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"CT WG1, CT WG6, SA WG2","lsoriginalls":"S3-193682","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1910895.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910897","title":"LS from SA WG4: LS on PDU session modification feature in TS 23.502 Procedures for the 5G System (5GS); Stage 2","source":"SA WG4","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"Within the scope of the 5G Media Streaming sub-system, SA WG4 foresees a feature that enables an AF, on behalf of a UE, to request a temporary boost in delivery data rate, e.g. to temporarily elevate the QoS Level of a QoS Flow. SA WG4 envisions the use of procedures to modify a PDU session, specifically via the Npcf_PolicyAuthorization service (as documented in clause 5.2.5.3) and the Nnef_AFSessionWithQoS service (as documented in clause 4.15.6.6). SA WG4 asks SA WG2 for clarification about the feasibility of requesting a temporary boost in delivery data rate, specifically: - What is the order of magnitude (e.g. milliseconds, seconds, minute) of the time needed to execute such a request originating from an AF (i.e. the time between initiating the request and the changes being propagated in the CN and the RAN)? - Are there restrictions on how often such requests can be submitted? - Does a more suitable procedure than the PDU session modification procedure exist for this purpose?. Action: SA WG4 kindly asks SA WG2 to provide responses to the above questions.","secretary_remarks":"This LS was postponed.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10150,"status":"postponed","reservation_date":"2019-10-30 09:03:47","uploaded":"2019-11-04 09:40:45","revisionof":"","revisedto":"S2-2000014","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"S4-191331","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1910897.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910898","title":"LS from SA WG5: LS reply from SA WG5 to NGMN on 5G End-to-End Architecture Framework","source":"SA WG5","contact":"Lan Zou","contact-id":35534,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 would like to thank NGMN for the LS 'LS from NGMN to SA WG5 on NGMN 5G End-to-End Architecture Framework'. SA WG5 work is related with the new topic 'Autonomic management and control' and 'network automation' mentioned in the NGMN LS. SA WG5 adopted the service based management architecture for the 5G network management and captured in Rel-16 TS 28.533 'Management and orchestration; Architecture framework'. SA WG5 also provided 'Management service deployment based on ZSM framework' in TS 28.533 section 5.3 which contains 3GPP cross domain loop and domain loop. SA WG5 would like also to inform NGMN that there are the following ongoing SA WG5 WIDs\/SIDs which are related to 'Autonomic management and control' and 'network automation': 1. Management automation: 1.1 Study on Self-Organizing Networks (SON) for 5G (SP-180827) 1.2 New SID on levels of autonomous network (SP-190928) 1.3 New WID on Self-Organizing Networks (SON) for 5G networks (SP-190785) 2. Management data analytics: 2.1 New SID Study on Management Data Analytics Service (SP-190930) 2.2 New WID on Closed loop SLS assurance (SP-190781) 3. Intent driven management: 3.1 Intent driven management services for mobile network (SP-180899) 4. Data reporting 4.1 Enhancement of performance assurance for 5G networks including network slicing (SP-190247) 4.2 Trace Management in the context of Services Based Management Architecture (SP-181073) 4.3 Management of QoE measurement collection (SP-181069) 4.4 KPI reporting (SP-190881) 4.5 Streaming trace reporting (SP-190782) SA WG5 is very happy to work together and address the management requirements from NGMN and update the SA WG5 work progress in the future.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10060,"status":"noted","reservation_date":"2019-10-30 09:03:47","uploaded":"2019-11-04 09:40:45","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"NGMN","Cc":"TSG RAN, TSG SA, SA WG2, SA WG3, SA WG6","lsoriginalls":"S5-196765","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1910898.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910969","title":"LS from SA WG3LI: LS on Enhancing Location Information Reporting with Dual Connectivity","source":"SA WG3LI","contact":"Alex Leadbeater","contact-id":71428,"tdoctype":"LS in","for":"Information","abstract":"SA WG3-LI thanks RAN WG3 on the work done to date related to enhancing both the opportunistic and on-demand location reporting capabilities to include PSCell ID reporting in the Dual Connectivity scenarios. SA WG3-LI also thanks RAN WG3 for the presentation delivered at the SA WG3LI#74 meeting explaining the enhancements developed by RAN WG3 for reporting all cells serving a UE in the User Location Information (ULI) in the DC scenarios. SA WG3-LI understands that a deficiency exists with the opportunistic location reporting where the ULI delivered at the start of a PDU session contains only the PCell ID as the DC is yet to be activated for the session and, thus, the PSCell ID may not be delivered until the end of the session. SA WG3-LI has subsequently analysed the DC procedures described in TS 37.340 and has found that the Path Update procedures involved in the scenarios where the UP PDCP control is transferred to the Secondary Node (the scenarios for Options 3x\/4a\/7x) may be potentially used to transport ULI with PSCell ID to the core network. Specifically, the S1AP E-RAB MODIFICATION INDICATION message and the NGAP PDU SESSION RESOURCE MODIFY INDICATION message may be used for that purpose.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10070,"status":"noted","reservation_date":"2019-11-04 11:04:38","uploaded":"2019-11-04 11:15:31","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"SA WG2, SA WG3, ETSI TC LI","lsoriginalls":"S3i190671","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1910969.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910981","title":"[DRAFT] Reply LS on Support of Network Address Translation in the User Plane function","source":"Samsung Electronics Romania","contact":"Sunghoon Kim","contact-id":59112,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS to S2-1910872 from CT WG4","secretary_remarks":"Response to S2-1910872. Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10090,"status":"noted","reservation_date":"2019-11-05 07:09:43","uploaded":"2019-11-08 11:00:32","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"CT WG3","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1910981.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911744","title":"[DRAFT] LS reply on Support of Network Address Translation in the User Plane function","source":"Huawei","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG4. CC: CT WG3","secretary_remarks":"Response to S2-1910872. Revised to S2-1911963.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10100,"status":"revised","reservation_date":"2019-11-08 14:07:44","uploaded":"2019-11-08 16:11:01","revisionof":"","revisedto":"S2-1911963","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"CT WG3","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911744.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911845","title":"LS from GSMA: Secured SMS roaming interface evolution in 5GC","source":"GSMA","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"Background: NG 5GJA welcomes the Release 15 specifications for the SEPP in 3GPP to protect the HTTP-based signalling via the N32 reference point between VPMN and HPMN when both PMNs are using the service-based 5G Core Network. Based on new discussion in 5GJA#10 on 10 October 2019, NG 5GJA has confirmed the important need to benefit of N32 security improvement for SMS roaming interface already reported in 5GJA5_120 LS SMS roaming interface evolution on 19 November 2018. By also including the SMS roaming interface in N32 in 5GS to complement the MAP and Diameter interfaces already proposed, it will be possible to provide integrity and confidentiality protection for the SMS user plane. Without SMS roaming interface via N32 and associated policy enforcement provided by SEPP, SMS would be excluded from the 5G design objective to secure all roaming interfaces. NG 5GJA has been informed that 3GPP does not have the possibility to include Service-Based support for SMS in 5GC (SB_SMS) in Rel17. NG 5GJA understands the 3GPP position and acknowledges this state of affairs. Nevertheless, and based on new discussion in 5GJA#10 on 10 October 2019, NG 5GJA has confirmed the important need to benefit of N32 security improvement for SMS roaming interface. Action: to TSG SA and SA WG2: TSG SA and it associated working group of SA WG2 are kindly requested to reconsider its decision and to include this requirement to benefit of N32 security improvement for SMS roaming interface in Rel17. TSG SA and it associated working group of SA WG2 are also kindly requested to respond to NG 5GJA on when such specifications providing a solution will be made available.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10160,"status":"noted","reservation_date":"2019-11-08 16:38:54","uploaded":"2019-11-08 17:24:31","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA, SA WG2","Cc":"CT WG4","lsoriginalls":"5GJA10_122","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911845.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911879","title":"[DRAFT] Reply LS on Support of Network Address Translation in the User Plane function","source":"Deutsche Telekom AG","contact":"Dieter Gludovacz","contact-id":38203,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG4","secretary_remarks":"Response to S2-1910872. Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10120,"status":"noted","reservation_date":"2019-11-08 17:47:08","uploaded":"2019-11-08 18:49:27","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911879.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911889","title":"[DRAFT] Reply LS on Support of Network Address Translation in the User Plane function","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"LS out","for":"Approval","abstract":"draft Reply LS on Support of Network Address Translation in the User Plane function","secretary_remarks":"Response to S2-1910872. Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10130,"status":"noted","reservation_date":"2019-11-08 18:37:29","uploaded":"2019-11-08 21:16:38","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4, BBF","Cc":"CT WG3","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911889.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911963","title":"[DRAFT] LS reply on Support of Network Address Translation in the User Plane function","source":"Huawei","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG4. CC: CT WG3","secretary_remarks":"Revision of S2-1911744. For e-mail approval","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10110,"status":"revised","reservation_date":"2019-11-19 22:27:38","uploaded":"2019-11-25 15:57:54","revisionof":"S2-1911744","revisedto":"S2-1912762","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"CT WG3","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911963.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912762","title":"LS reply on Support of Network Address Translation in the User Plane function","source":"SA WG2","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG4. CC: CT WG3","secretary_remarks":"e-mail revision of S2-1911963. Approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10120,"status":"available","reservation_date":"2019-11-28 05:47:21","uploaded":"2019-11-28 08:00:20","revisionof":"S2-1911963","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-1910872","lsto":"CT WG4","Cc":"CT WG3","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912762.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]