[{"name":"S2-2203625","title":"LS from RAN WG2: LS on paging subgrouping and PEI","source":"RAN WG2","contact":"Yanhua Li","contact-id":76945,"tdoctype":"LS in","for":"Action","abstract":"RAN WG2 discussed UE paging subgrouping as part of the Rel-17 work on UE power saving enhancement (see RP-200938). On paging subgrouping, the following provides the detailed agreements for the 2 approaches (CN-assigned subgrouping and UE ID-based subgrouping): \u00de Assume that one subgroup indication refers to either CN-assigned subgroups or UE ID-based subgroup (no overlapping) \u00de Both UE ID-based and CN-assigned subgrouping can be supported simultaneously in a cell, it is allowed to just support one of them. \u00de The total number of CN-assigned subgroups that is used is not fixed and can be configured up to 8 (e.g. by OAM). No impact on signalling is assumed. \u00de RAN introduces a new parameter Nsg-UEID to indicate its support of UE ID-based subgrouping. \u00de RAN does not support any type of subgrouping if its configuration for subgrouping is either absent or nullified (e.g. subgroupsNumPerPO is either absent or set to zero). FFS for the signalling details. \u00de We assume separate indications for UE capability of CN-assigned subgrouping and UE ID-based subgrouping. \u00de UE's capability of supporting the UE ID-based subgrouping is reported to RAN by AS UE capability signalling while R2 assumes that UE's capability of supporting the CN-assigned subgrouping is reported to CN by NAS signalling. RAN WG2 also discussed the Paging Early Indication, and agreed to the following: \u00de RAN WG2 assumes that if PEI is detected, and the PEI indicates that the UE has to monitor the associated PO, then the UE monitors paging DCI in the associated PO, including scheduling information for paging PDSCH (if included) as in legacy. This assumption may be updated based on RAN WG1 agreements. \u00de As a baseline RAN WG2 has a preference to support PEI with both DRX and eDRX, but potential issues (e.g. PEI and PTW) are FFS. \u00de For UE ID-based subgroups the UE identity is UE_ID = 5G-S-TMSI mod X, where X is 8192 (1024*8). \u00de Introduce a UERadioPagingInfo IE in the UECapabilityInformation message in NR in Rel-17. \u00de If the UE was not able to monitor the PEI occasion corresponding to its PO, the UE shall monitor the PO. Actions: To SA WG2 and CT WG1: RAN WG2 respectfully asks SA WG2 and CT WG1 to take the above information into account for their future work, and provide further information on the following issue once concluded: - NAS signalling between AMF and UE to convey the related information to the UE, e.g., UE's capability reporting by NAS.","secretary_remarks":"Revision of Postponed S2-2201921 from S2#150E. Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10030,"status":"noted","reservation_date":"2022-04-21 14:48:20","uploaded":"2022-04-21 14:49:13","revisionof":"S2-2201921","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, CT WG1, RAN WG3, RAN WG1","Cc":"","lsoriginalls":"R2-2111415","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2203625.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2203627","title":"LS on handling of packet filters when the supported number is exceeded","source":"CT WG3","contact":"Susana Fernandez","contact-id":42321,"tdoctype":"LS in","for":"Action","abstract":"TS 23.501 clause 5.7.1.4 states that in 5G, the UE can indicate the number of supported packet filters for signalled QoS rules of the PDU session during the PDU Session Establishment procedure or using the PDU Session Modification procedure after the first inter-system change from EPS to 5GS for a PDU Session established in EPS and transferred from EPS with N26 interface. When dynamic PCC is deployed, the PCF shall ensure that the sum of the packet filters used by all PCC rules which trigger the generation of signalled QoS rules does not exceed that number. The SMF ensures that the sum of the Packet Filters used by all signalled QoS rules for a PDU Session does not exceed the number indicated by the UE. The number of packet filters supported in LTE is limited to 16 per PDN connection but the number of packet filters per PDU session can be up to 1024 in 5G. As described in TS 23.502, clause 4.11.1.1, when the UE is served by the 5GC, during PDU Session establishment and GBR QoS Flow establishment, SMF+PGW-C performs EPS QoS mappings, from the 5G QoS parameters obtained from the PCF, and allocates TFT with the PCC rules obtained from the PCF if PCC is deployed. Otherwise, EPS QoS mappings and TFT allocation are mapped by the SMF+PGW-C locally. Question 1: For a UE with an established PDU session in 5GS with dynamic PCC deployment, how does the SMF+PGW-C know what packet filters will be part of the TFT allocation based on the PCC rules obtained from the PCF if the number of packet filters for signalled QoS rules exceeds the number supported in EPS? Is there any precedence criteria for the SMF+PGW-C to consider the pre-defined PCC rules (known or unknown to the PCF) in the TFT allocation? Question 2: For a UE with an established PDU session in 5GS without dynamic PCC deployment, how does the SMF+PGW-C know what packet filters will be part of the allocated TFT based on the local policy if the number of packet filters for signalled QoS rules exceeds the number supported in EPS?. Action: SA WG2 is kindly requested to answer the questions above, and update stage 2 if deemed necessary.","secretary_remarks":"Revision of Postponed S2-2201937 from S2#150E. Responses drafted in S2-2203824, S2-2203835. Final response in S2-2204728","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10110,"status":"replied to","reservation_date":"2022-04-21 14:48:20","uploaded":"2022-04-21 14:49:13","revisionof":"S2-2201937","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"C3-221503","lsreply":"S2-2204728","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2203627.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2203628","title":"LS from SA WG4: LS on Traffic Identification within 5G Media Streaming","source":"SA WG4","contact":"Thorsten Lohmar","contact-id":59317,"tdoctype":"LS in","for":"Action","abstract":"SA WG4 has executed a study on 5G Media Streaming extensions within Release 17. The study is about to be concluded. Among other key issues, SA WG4 has studied the use of Traffic Identification. A number of different 5G Media Streaming features rely on the 5G System being able to identify traffic flows corresponding to media sessions. However, multimedia streaming applications might not be able to uniquely identify the 5-tuples of a streaming session, because IP addresses and port numbers often change as a result of load balancing, CDN distribution, multiple concurrent HTTP requests for different types of resources, etc. This aspect of the study addressed how to use the available 5G System application detection functions e.g. for QoS profile usage. Action: SA WG4 kindly asks SA WG2 and CT WG3 to review specifically clause 5.3.5 of TR 26.804.","secretary_remarks":"Revision of Postponed S2-2201960 from S2#150E. Responses drafted in S2-2203842, S2-2204460. Final response in S2-2204725","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10040,"status":"replied to","reservation_date":"2022-04-21 14:48:20","uploaded":"2022-04-21 14:49:13","revisionof":"S2-2201960","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, CT WG3","Cc":"","lsoriginalls":"S4-220305","lsreply":"S2-2204725","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2203628.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2203630","title":"LS from GSMA: LS to 3GPP SA2 on VoLTE Roaming GBR Handling","source":"GSMA","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"GSMA NG NRG kindly requests SA WG2 to provide a functionality for VPLMN to apply its own QoS policy for bearer setup process in VoLTE roaming, including the GBR parameter values. Action: GSMA NG NRG kindly requests SA WG2 to take into account the request above and define a solution which allows VPLMN to be fully in charge of the QoS policy for VoLTE\/VoNR inbound roaming service by having possibility to override also the GBR parameter value sent by HPLMN during the bearer setup process.","secretary_remarks":"Revision of Postponed S2-2201970 from S2#150E. Response drafted in S2-2203838. Final response in S2-2204724","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10080,"status":"replied to","reservation_date":"2022-04-21 14:48:20","uploaded":"2022-04-21 14:49:13","revisionof":"S2-2201970","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"NRG 13_201r2","lsreply":"S2-2204724","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2203630.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2203643","title":"LS from CT WG3: Reply LS on Traffic Identification within 5G Media Streaming","source":"CT WG3","contact":"Tianmei Liang","contact-id":69846,"tdoctype":"LS in","for":"Information","abstract":"CT WG3 would like to thank SA WG4 for the LS on Traffic Identification within 5G Media Streaming and asks CT WG3 to review specifically clause 5.3.5 of TR 26.804. CT WG3 would like to comment below in lines for CT WG3 related analysis to the clause 5.3.3 of TR 26.804, meanwhile also remind the concerned issues\/limitation on ToS based Traffic Identification. {. . .}","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10150,"status":"noted","reservation_date":"2022-04-21 14:48:20","uploaded":"2022-04-22 05:13:38","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG4","Cc":"SA WG2","lsoriginalls":"C3-222477","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2203643.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2203650","title":"LS from CT WG4: Reply LS on Node Report Type value for PFCP node reports not defined by 3GPP","source":"CT WG4","contact":"Bruno Landais","contact-id":68755,"tdoctype":"LS in","for":"Information","abstract":"CT WG4 thanks BBF for their LS on Node Report Type value for PFCP node reports not defined by 3GPP. CT WG4 has agreed the attached 29.244 CR defining: - a new Node Report Type value for PFCP node reports not defined by 3GPP; and - a new Vendor-Specific Node Report Type IE in the PFCP Node Report Request indicating the type of the Vendor-Specific node report the UP function sends to the CP function. The CR enables BBF to define its own Vendor Specific Report IEs in the PFCP Node Report Request message and to define the corresponding report types in the Vendor-Specific Node Report Type IE, without the need to further liaise with CT WG4. See clauses 5.9 and 8.1.1 of TS 29.244 for the definition and usage of Vendor Specific IEs.","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":"2022-04-21 14:48:20","uploaded":"2022-04-22 05:13:38","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"BBF","Cc":"SA WG2","lsoriginalls":"C4-222437","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2203650.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2203657","title":"LS from GSMA ENSWI: LS on Traffic Categories","source":"GSMA ENSWI","contact":"Susana Sabater","contact-id":31269,"tdoctype":"LS in","for":"Action","abstract":"GSMA ENSWI defines technical requirements for E2E network slicing and identifies gaps that need to be addressed by SDOs in order to accelerate deployments according to these standards, both at network and UE level. GSMA ENSWI has discussed and agreed the traffic categories to be used as traffic descriptor in the URSP rules that the network provides to the UE to configure the network slices that the UE can use. The traffic categories are being incorporated in GSMA PRD NG.135 and are based on connectivity capabilities that traffic from different applications may demand. The following list of traffic categories has been agreed: - IMS traffic category; voice, video and SMS over IMS, as well as RCS, are included in this traffic. - Internet traffic; - IoT and machine to machine type of traffic, characterised by low data rates and requiring low latency occasionally. - On demand downlink streaming; characterised as downlink high data rates content and low latency - On demand uplink streaming; - Vehicular communications, including vehicle-to-infrastructure, vehicle-to-network, vehicle-to-vehicle, vehicle-to-pedestrian, vehicle-to-device and vehicle-to-grid. - Real time interactive traffic; characterised by bidirectional variable data rates and low latency - Unified communications traffic; instant messaging, VoIP and video collaboration are included in this category. - Background traffic; comprising processes for e.g. firmware\/software updates over the air - Location-based traffic, - Critical Communications, The new PRD NG.135 'E2E Network Slicing Requirements' is planned to be published in May 2022. Action: GSMA ENSWI kindly requests SA WG2 to consider the above list of categories to be specified as part of the URSP traffic descriptor and provide feedback to GSMA ENSWI on how these categories are supported. GSMA ENSWI asks SA WG2 to consider the importance of having agreed specifications in the earliest possible release.","secretary_remarks":"Response drafted in S2-2204635. Final response in S2-2204838","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10350,"status":"replied to","reservation_date":"2022-04-21 14:48:20","uploaded":"2022-04-28 08:27:05","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, GSMA TSGNS, NRG, UPG","Cc":"","lsoriginalls":"ENSWI10_Doc010","lsreply":"S2-2204838","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2203657.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2203661","title":"LS to CT WG3 and SA WG2 on EVEX","source":"SA WG4","contact":"Charles Lo","contact-id":50185,"tdoctype":"LS in","for":"Information","abstract":"SA WG4 wishes to inform CT WG3 and SA WG4 about the progress made on the Rel-17 EVEX (Event Exposure) work item during SA WG4#118-e and general outlook on completion of this work item. During SA WG4#118-e, four pCRs against TS 26.531 V1.0.0 were agreed, leading to the creation of Draft TS 26.532 V1.1.1 (see attached). Notably, only a few sections in this specification remain to be produced - primarily the Data Reporting Configuration API (invoked by the Provisioning AF on the Data Collection AF to create and manipulate a Data Reporting Configuration resource by defining data access profiles to control UE data exposure to different Event consumers), and specification of OpenAPI representation of RESTful APIs associate with data collection and reporting. Overall, we estimate that TS 26.532 is about 85% complete. The EVEX stage 2 specification, TS 26.531, already pseudo-complete at SA WG4#117-e was further enhanced by pCRs agreed during post-118-3 MBS AHG telcos and is essentially finished as TS 26.531 V1.2.0 (also attached). SA WG4 regards these two specifications to contain the most relevant information for CT WG3 in updating your Rel-17 stage 3 SBI specifications (e.g., TS 29.517, TS 29.122 and TS 29.522) to support the instantiation of EVEX functionality in the 5G Media Streaming domain. In addition, dCRs against Rel-17 5G Media Streaming stage 2 and stage 3 specifications TS 26.501 and TS 26.512 were agreed during SA WG4#118-e. In particular, and likely of interest to CT WG3 in producing changes to your stage 3 specifications is the dCR to TS 26.512 V17.0.0 in S4-220569 which can be found from the embedded links as indicated. SA WG4 hopes that the above information and referenced and attached documents will be timely and useful for CT WG3 towards generation of updated CT WG3 specifications, and possibly of interest to SA WG2 with regards to updating of your Rel-17 specification(s) to further align with EVEX functionality and\/or consider future Rel-18 SA WG2 work with similar purpose.","secretary_remarks":"Response drafted in S2-2204376. Final response in S2-2204729","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10180,"status":"replied to","reservation_date":"2022-04-21 14:48:20","uploaded":"2022-04-29 06:27:12","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3 and SA2","Cc":"","lsoriginalls":"S4-220576","lsreply":"S2-2204729","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2203661.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2203662","title":"LS on Inter-PLMN Handover of VoLTE calls and idle mode mobility of IMS sessions","source":"SA WG3-LI","contact":"Koen Jaspers","contact-id":9291,"tdoctype":"LS in","for":"Action","abstract":"SA WG3-LI has identified that the handover between PLMNs using home routing for ongoing IMS-sessions (calls) creates issues for LI. With home routing roaming, HPLMN operators may be required to switch off the IMS confidentiality protection for all roamers in order to allow the lawful interception of roamers in the VPLMN without involvement of the HPLMN. The hitherto assumption SA WG3 LI had was that during the IMS registration, the IMS confidentiality protection would be turned off and as a consequence, a full capture of IMS session related signalling and media would be possible in the VPLMN for lawful interception purpose. If an IMS session moves from a serving PLMN for which confidentiality protection is allowed to a VPLMN where it is not allowed, then the IMS confidentiality protection would need to be switched off mid-session. Similarly, when the inter-PLMN handover happens with an established IMS session for a roamer, without having the complete IMS session related information, an effective lawful interception of such roamers is not possible in the VPLMN. In order to have a non-compromised lawful interception in the VPLMN, complete information of IMS sessions shall be made available in the VPLMN. While this LS focusses on the Home Routed VoLTE roaming for VoLTE\/EPC (S8HR) it is also applicable to VoNR\/5G Core (N9HR). The following list states the requirements related to inter PLMN handover and idle mode mobility of IMS-sessions: 1. For any ongoing call, following handover, it must be possible to intercept that S8HR call in the new PLMN. 2. In order to support the above, a mechanism shall exist to ensure that the HPLMN can turn off IMS confidentiality protection when any UE roams to a VPLMN. In addition, a mechanism may be required to support turning on the IMS confidentiality protection when the UE returns or roams back to the HPLMN. 3. The handover handling shall ensure that the VPLMN lawful interception system has access to the relevant identifiers to enable the lawful interception of IMS services of roamers. The relevant identifiers shall include at the minimum, the following: a) 3GPP access level identifiers (MSISDN, IMSI, IMEI). b) IMS level identifiers (IMPU, IMPIs) of local served party and IMPU of remote end point user. c) SDP information (codec, PT, etc.) for the media stream. 4. The HPLMN shall have a mechanism to detect that a user has roamed into and back from a different country. a) The HPLMN may be required to suspend the lawful interception for any targeted outbound roamer (including NTNs). Such suspension, if executed, may include the suspension of lawful interception for the content of communications or the suspension of lawful interception of content of communication and the signaling. b) When the HPLMN is required to suspend lawful interception for any targeted outbound roamer, the HPLMN shall have the mechanism to detect that the UE has moved back to the home country in order to start\/resume the lawful interception of that UE when required. 5. The lawful interception system in the VPLMN shall be able to detect whether the HPLMN has correctly configured the IMS session (e.g. confidentiality protection off). Any action resulting from such detection is a CSP policy issue. SA WG3-LI is looking forward to discuss the detailed list of information that needs to be provided at inter PLMN handover\/idle mode mobility and the most appropriate way to make the information available. For example: a) What changes are needed so the IMS can make the required information available? b) What is the preferred mechanism to get the IMS-information provided to the VPLMN (e.g. as part of the registration process)? c) Are changes needed for the HPLMN to be able to deactivate or activate the IMS confidentiality protection during inter-PLMN handover? d) Are changes needed for the VPLMN to detect if the correct configurations for roamers to allow lawful interception are in use at the VPLMN? Taking the regulatory process and techni","secretary_remarks":"Response drafted in S2-2204719. Postponed","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10210,"status":"postponed","reservation_date":"2022-04-21 14:48:20","uploaded":"2022-05-02 13:25:59","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, CT WG1","Cc":"SA WG3, CT WG4","lsoriginalls":"S3i220244","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2203662.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2203664","title":"LS from BBF: 3GPP TS 29.244","source":"BBF","contact":"Lincoln Lavoie","contact-id":39231,"tdoctype":"LS in","for":"Information","abstract":"Dear Colleagues, We would like to thank CT WG4 for your liaison response titled Reply LS on Node Report Type value for PFCP node reports not defined by 3GPP with attached CR C4-222429. BBF has studied the TS 29.244 CR and acknowledges that the proposed CR contents to define a new Vendor-Specific Node Report Type IE in the PFCP Node Report Request will sufficiently address BBF needs. We look forward to continuing our fruitful relationship. Sincerely, Lincoln Lavoie, Broadband Forum Technical Committee Chair","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10170,"status":"noted","reservation_date":"2022-04-21 14:48:20","uploaded":"2022-05-11 06:05:08","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"SA WG2, SA WG3","lsoriginalls":"LIAISE-528-01","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2203664.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2203666","title":"LS from SA WG4: Reply LS to CT WG3 on Data Reporting API","source":"SA WG4","contact":"Charles Lo","contact-id":50185,"tdoctype":"LS in","for":"Information","abstract":"To: CT WG3. CC: SA WG2. Attachments: S4-220798; S4-220807","secretary_remarks":"Postponed","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10240,"status":"postponed","reservation_date":"2022-04-21 14:48:21","uploaded":"2022-05-16 16:23:27","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"SA WG2","lsoriginalls":"S4-220839","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2203666.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2203822","title":"Clarification on the TFT exceeding 16 for 5GS-EPS interworking","source":"ZTE","contact":"Zhendong Li","contact-id":38521,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: During PDU Session establishment and GBR QoS Flow establishment, the SMF+PGW-C locally determine what packet filters will be part of the TFT allocation. During EBI allocation, the SMF+PGW-C may remove packet filters which has been sent","secretary_remarks":"Revision of (Postponed) S2-2202823. Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10250,"status":"noted","reservation_date":"2022-05-05 13:56:08","uploaded":"2022-05-06 14:35:33","revisionof":"S2-2202823","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.12.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI16"}],"crnumber":3455.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2203822.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2203823","title":"Clarification on the TFT exceeding 16 for 5GS-EPS interworking","source":"ZTE","contact":"Zhendong Li","contact-id":38521,"tdoctype":"CR","for":"Approval","abstract":"Rel-17 mirror CR: Summary of change: During PDU Session establishment and GBR QoS Flow establishment, the SMF+PGW-C locally determine what packet filters will be part of the TFT allocation. During EBI allocation, the SMF+PGW-C may remove packet filters wh","secretary_remarks":"Revision of (Postponed) S2-2202824. Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10260,"status":"noted","reservation_date":"2022-05-05 13:56:09","uploaded":"2022-05-06 14:35:33","revisionof":"S2-2202824","revisedto":"","release":"Rel-17","crspec":"23.502","crspecversion":"17.4.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI16"}],"crnumber":3456.0,"crrevision":1.0,"crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2203823.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2203824","title":"[DRAFT] Reply LS On handling of packet filters when the supported number is exceeded","source":"ZTE","contact":"Zhendong Li","contact-id":38521,"tdoctype":"LS out","for":"Approval","abstract":"Proposes a Reply LS On handling of packet filters when the supported number is exceeded. Response to S2-2203627","secretary_remarks":"Response to S2-2203627. Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10120,"status":"noted","reservation_date":"2022-05-05 13:56:11","uploaded":"2022-05-06 14:35:33","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2203824.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2203835","title":"[DRAFT] Reply to LS handling of packet filters when the supported number is exceeded","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"This paper replies CT WG3 which NF decides PCC rules for TFT filter allocation to avoid reaching limit. Response to S2-2203627","secretary_remarks":"Response to S2-2203627. r00 agreed. Revised to S2-2204728.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10130,"status":"revised","reservation_date":"2022-05-05 16:21:19","uploaded":"2022-05-06 22:35:53","revisionof":"","revisedto":"S2-2204728","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"TEI17"},{"winame":" 5GS_Ph1-CT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2203835.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2203836","title":"Number of TFT filters exceeding allowed limit for 5GS to EPS interworking","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 4.11.1.1: PCF includes in PCC rule a new parameter (survival precedence) indicating the order of this PCC rule in TFT packet filter derivation\/allocation and SMF+PGW-C removes PCC rule(s) if TFT packet filter is not allocated due to num","secretary_remarks":"Revision of (Postponed) S2-2202183. r04 agreed. Revised to S2-2204726.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10270,"status":"revised","reservation_date":"2022-05-05 16:21:19","uploaded":"2022-05-06 22:35:53","revisionof":"S2-2202183","revisedto":"S2-2204726","release":"Rel-17","crspec":"23.502","crspecversion":"17.4.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI17"}],"crnumber":3430.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2203836.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2203837","title":"Number of TFT filters exceeding allowed limit for 5GS to EPS interworking","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add a new indication parameter in PCC rule indicating the orderthat the PCC rule can be skipped forin TFT packet filter allocation if the number of TFT packet filters derived from the PCC rules may reachesexceed the limite (i.e.16). Add","secretary_remarks":"Revision of (Postponed) S2-2202184. r01 agreed. Revised to S2-2204727.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10290,"status":"revised","reservation_date":"2022-05-05 16:21:20","uploaded":"2022-05-06 22:35:53","revisionof":"S2-2202184","revisedto":"S2-2204727","release":"Rel-17","crspec":"23.503","crspecversion":"17.4.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI17"}],"crnumber":712.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2203837.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2203838","title":"[DRAFT] Reply to LS to SA WG2 on VoLTE Roaming GBR Handling","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"TThis paper replies GSMA on GBR downgrade. Response to S2-2203630","secretary_remarks":"Response to S2-2203630. r07 + changes agreed. Revised to S2-2204724.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10090,"status":"revised","reservation_date":"2022-05-05 16:21:21","uploaded":"2022-05-06 22:35:53","revisionof":"","revisedto":"S2-2204724","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"TEI17"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA NRG CT WG3","Cc":"CC: CT WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2203838.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2203839","title":"Handling of GBR for IMS voice service in home routed roaming","source":"Ericsson, Deutsche Telekom","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Allow GBR downgrade for IMS voice service at home routed roaming.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10310,"status":"noted","reservation_date":"2022-05-05 16:21:21","uploaded":"2022-05-06 22:35:53","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.401","crspecversion":"17.4.0","workitem":[{"winame":"TEI17"}],"crnumber":3700.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2203839.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2203840","title":"Handling of GBR for IMS voice service in home routed roaming","source":"Ericsson, Deutsche Telekom","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Allow GBR downgrade for IMS voice service in home routed roaming.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10320,"status":"noted","reservation_date":"2022-05-05 16:21:22","uploaded":"2022-05-06 22:35:53","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.501","crspecversion":"17.4.0","workitem":[{"winame":"TEI17"}],"crnumber":3630.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2203840.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2203841","title":"E2E QoS and ToS\/TC over N33 for Traffic Identification within 5G Media Streaming.","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"discussion","for":"Agreement","abstract":"This paper discusses the need to support ToS\/TC over N33 to have e2e QoS control between the UE and the 5G Media Streaming server.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10330,"status":"noted","reservation_date":"2022-05-05 16:21:23","uploaded":"2022-05-06 22:35:53","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"TEI17"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2203841.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2203842","title":"[DRAFT] Reply LS on Traffic Identification within 5G Media Streaming","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"This paper replies SA WG4 about ToS\/TC over N33. Response to S2-2203628","secretary_remarks":"Response to S2-2203628. r02 agreed. Revised to S2-2204725.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10050,"status":"revised","reservation_date":"2022-05-05 16:21:23","uploaded":"2022-05-06 22:35:53","revisionof":"","revisedto":"S2-2204725","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"TEI17"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG4, CT WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2203842.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2203843","title":"Traffic Identification using ToS\/TC for 5G Media Streaming","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Change flow description to flow information clarifying the content of flow information is as specified in clause 5.7.6 of TS 23.501 Add note that if ToS\/TC is to be used for service data flow detection, collaboration between the operati","secretary_remarks":"Revision of (Postponed) S2-2202189. Postponed","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10340,"status":"postponed","reservation_date":"2022-05-05 16:21:23","uploaded":"2022-05-06 22:35:53","revisionof":"S2-2202189","revisedto":"","release":"Rel-17","crspec":"23.502","crspecversion":"17.4.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI17"}],"crnumber":3431.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2203843.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2204269","title":"Traffic identification based on AF provided ToS\/TC","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: A statement is added about the possibility for the AF to also provide a ToS (IPv4) or TC (IPv6) value that is set by the application as part of the flow description information. A note is added to describe the use case and the constrain","secretary_remarks":"r03 agreed. Revised to S2-2204730.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10380,"status":"revised","reservation_date":"2022-05-06 10:00:11","uploaded":"2022-05-06 15:47:36","revisionof":"","revisedto":"S2-2204730","release":"Rel-17","crspec":"23.503","crspecversion":"17.4.0","workitem":[{"winame":"TEI17"},{"winame":" 5GS_Ph1"}],"crnumber":724.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2204269.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2204351","title":"Handling of GBR for IMS voice service in home routed roaming.","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"discussion","for":"Agreement","abstract":"This paper proposes way forward to address an issue from GSMA that voice call setup fails due to HPLMN requested GBR value not compliant with roaming agreement.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10400,"status":"noted","reservation_date":"2022-05-06 11:09:07","uploaded":"2022-05-06 22:35:53","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"TEI17"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2204351.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2204376","title":"[DRAFT] Reply LS on LS to CT WG3 and SA WG2 on EVEX","source":"Samsung","contact":"Mehrdad Shariat","contact-id":75422,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on LS to CT WG3 and SA WG2 on EVEX. Response to S2-2203661","secretary_remarks":"Response to S2-2203661. r01 agreed. Revised to S2-2204729.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10190,"status":"revised","reservation_date":"2022-05-06 11:34:02","uploaded":"2022-05-06 17:14:45","revisionof":"","revisedto":"S2-2204729","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG4 CT WG3","Cc":"CC: CT WG3","lsoriginalls":"S4-220576","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2204376.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2204460","title":"[DRAFT] Reply LS on Traffic Identification within 5G Media Streaming","source":"Nokia, Nokia Shanghai Bell, Qualcomm Incorporated","contact":"Pallab Gupta","contact-id":87959,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG4. CC: CT WG3. Response to S2-2203628","secretary_remarks":"Response to S2-2203628. Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10070,"status":"noted","reservation_date":"2022-05-06 12:58:42","uploaded":"2022-05-06 13:18:40","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"TEI17"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG4 CT WG3","Cc":"CC: CT WG3","lsoriginalls":"S4-220305","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2204460.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2204503","title":"Support of LI at HO for S8 Home routing (LS S3i220244).","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"discussion","for":"Decision","abstract":"This DP is triggered by the LS S3i220244","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10410,"status":"noted","reservation_date":"2022-05-06 13:59:06","uploaded":"2022-05-06 22:35:53","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2204503.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2204627","title":"Inter-country VoIMS Handover and IMS idle mode mobility related to SA WG3LI LS in S2-2203662\/S3i220244.","source":"Vodafone","contact":"Chris Pudney","contact-id":1122,"tdoctype":"discussion","for":"Decision","abstract":"SA WG3Li has sent an LS in S2-2203662\/S3i220244 highlighting the issues of providing the lawful interception for the VoIMS and IMS session using S8HR\/N9HR home routing when cross-country Inter-PLMN handover or idle mode mobility occurs. This discussion pa","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10420,"status":"noted","reservation_date":"2022-05-06 17:57:36","uploaded":"2022-05-06 18:00:15","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2204627.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2204635","title":"[DRAFT] Reply LS on Traffic Categories","source":"Vodafone","contact":"Susana Sabater","contact-id":31269,"tdoctype":"LS out","for":"Approval","abstract":"To: GSMA ENSWI. CC: GSMA TSGNS, GSMA NRG, GSMA UPG. Response to S2-2203657","secretary_remarks":"Response to S2-2203657. r05 agreed. Revised to S2-2204838.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10360,"status":"revised","reservation_date":"2022-05-06 18:24:24","uploaded":"2022-05-06 18:58:59","revisionof":"","revisedto":"S2-2204838","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA ENSWI","Cc":"GSMA TSGNS, GSMA NRG, GSMA UPG","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2204635.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2204643","title":"Discussion on the SA WG3LI LS on Inter-PLMN Handover of VoLTE calls and idle mode mobility of IMS sessions.","source":"Nokia, Nokia Shanghai Bell","contact":"Rainer Liebhart","contact-id":68375,"tdoctype":"discussion","for":"Discussion","abstract":"This paper discusses the LS from SA WG3LI on inter-PLMN VoLTE HO, potential technical implications and proposes a way forward.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10430,"status":"noted","reservation_date":"2022-05-06 18:37:51","uploaded":"2022-05-06 18:52:12","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2204643.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2204719","title":"[DRAFT] LS on Joint CC for support of LI at HO for S8 Home routing","source":"SA WG2","contact":"Chris Pudney","contact-id":1122,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG3-LI, CT WG1, SA WG3","secretary_remarks":"Created at CC#1. Response to S2-2203662. r02 agreed. Revised to S2-2204731.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10220,"status":"revised","reservation_date":"2022-05-17 06:08:59","uploaded":"2022-05-17 06:09:44","revisionof":"","revisedto":"S2-2204731","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3-LI, CT WG1, SA WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2204719.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2204724","title":"Reply to LS to SA WG2 on VoLTE Roaming GBR Handling","source":"SA WG2","contact":"Judy Gan Juying","contact-id":72307,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG4, CT WG4, CT WG3, GSMA NRG. Attachments: S2-2203630","secretary_remarks":"Revision of S2-2203838r07 + changes. Approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10100,"status":"approved","reservation_date":"2022-05-23 07:09:35","uploaded":"2022-05-24 08:11:20","revisionof":"S2-2203838","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"TEI17"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2203630","lsto":"SA WG4, CT WG4, CT WG3, GSMA NRG","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2204724.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2204725","title":"Reply LS on Traffic Identification within 5G Media Streaming","source":"SA WG2","contact":"Judy Gan Juying","contact-id":72307,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG4, CT WG3. Attachments: 23.502 CR3431 (not agreed), 23.503 CR0724","secretary_remarks":"Revision of S2-2203842r02. Approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10060,"status":"approved","reservation_date":"2022-05-23 07:09:35","uploaded":"2022-05-24 08:11:20","revisionof":"S2-2203842","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"TEI17"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2203628","lsto":"SA WG4, CT WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2204725.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2204726","title":"Number of TFT filters exceeding allowed limit for 5GS to EPS interworking","source":"Ericsson","contact":"Judy Gan Juying","contact-id":72307,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 4.11.1.1: PCF includes in PCC rule a new parameter (survival precedence) indicating the order of this PCC rule in TFT packet filter derivation\/allocation and SMF+PGW-C removes PCC rule(s) if TFT packet filter is not allocated due to num","secretary_remarks":"Revision of S2-2203836r04. Approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10280,"status":"agreed","reservation_date":"2022-05-23 07:09:35","uploaded":"2022-05-24 08:11:20","revisionof":"S2-2203836","revisedto":"","release":"Rel-17","crspec":"23.502","crspecversion":"17.4.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI17"}],"crnumber":3430.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-220410","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2204726.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2204727","title":"Number of TFT filters exceeding allowed limit for 5GS to EPS interworking","source":"Ericsson","contact":"Judy Gan Juying","contact-id":72307,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add a new parameter in PCC rule indicating the order in TFT packet filter allocation if the number of TFT packet filters derived from the PCC rules may exceed the limit. Add a note that PCF can decide whether the PDU Session is subject","secretary_remarks":"Revision of S2-2203837r01. Approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10300,"status":"agreed","reservation_date":"2022-05-23 07:09:36","uploaded":"2022-05-24 08:11:20","revisionof":"S2-2203837","revisedto":"","release":"Rel-17","crspec":"23.503","crspecversion":"17.4.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI17"}],"crnumber":712.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-220410","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2204727.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2204728","title":"Reply to LS handling of packet filters when the supported number is exceeded","source":"SA WG2","contact":"Judy Gan Juying","contact-id":72307,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG3. Attachments: 23.502 CR3430, 23.503 CR0712","secretary_remarks":"Revision of S2-2203835r00. Approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10140,"status":"approved","reservation_date":"2022-05-23 07:09:37","uploaded":"2022-05-24 08:11:20","revisionof":"S2-2203835","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"TEI17"},{"winame":" 5GS_Ph1-CT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2203627","lsto":"CT WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2204728.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2204729","title":"Reply LS on LS to CT WG3 and SA WG2 on EVEX","source":"SA WG2","contact":"Mehrdad Shariat","contact-id":75422,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG4. CC: CT WG3","secretary_remarks":"Revision of S2-2204376r01. Approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10200,"status":"approved","reservation_date":"2022-05-23 07:09:37","uploaded":"2022-05-24 08:11:20","revisionof":"S2-2204376","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2203661","lsto":"SA WG4","Cc":"CT WG3","lsoriginalls":"S4-220576","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2204729.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2204730","title":"Traffic identification based on AF provided ToS\/TC","source":"Huawei, HiSilicon, Ericsson","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: A statement is added about the possibility for the AF to also provide a ToS (IPv4) or TC (IPv6) value that is set by the application as part of the flow description information. A note is added to describe the use case and the constrain","secretary_remarks":"Revision of S2-2204269r03. Approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10390,"status":"agreed","reservation_date":"2022-05-23 07:09:37","uploaded":"2022-05-24 08:11:20","revisionof":"S2-2204269","revisedto":"","release":"Rel-17","crspec":"23.503","crspecversion":"17.4.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI17"}],"crnumber":724.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-220410","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2204730.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2204731","title":"LS on Joint CC for support of LI at HO for S8 Home routing","source":"SA WG2","contact":"Chris Pudney","contact-id":1122,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG3-LI, CT WG1, SA WG3. CC: CT WG4","secretary_remarks":"Revision of S2-2204719r02. Approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10230,"status":"approved","reservation_date":"2022-05-23 07:09:38","uploaded":"2022-05-24 08:11:20","revisionof":"S2-2204719","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2203662","lsto":"SA WG3-LI, CT WG1, SA WG3","Cc":"CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2204731.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2204838","title":"Reply LS on Traffic Categories","source":"SA WG2","contact":"Susana Sabater","contact-id":31269,"tdoctype":"LS out","for":"Approval","abstract":"To: GSMA ENSWI. CC: GSMA TSGNS, GSMA NRG, GSMA UPG. Attachment: TR 23.700-85 v0.3.0 (link)","secretary_remarks":"Revision of S2-2204635r05. Approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10370,"status":"approved","reservation_date":"2022-05-23 07:10:03","uploaded":"2022-05-24 08:11:22","revisionof":"S2-2204635","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2203657","lsto":"GSMA ENSWI","Cc":"GSMA TSGNS, GSMA NRG, GSMA UPG","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2204838.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]