3GPP TSG-CT WG4 Meeting #125	C4-244006

Hefei, P.R.China, 14th–18th October 2024

Source:	Chairman, TSG-CT WG4

Title:	Proposed allocation of documents to agenda items for CT4#125, status on eve of meeting

Agenda item:	2

Document for:	INFORMATION

Document available, not yet treated

Document available late, not yet treated

Document not available

Document treated

Document available later

NOTE 1: Hyperlinks assume that this document is extracted and stored in a directory and all documents are in a subdirectory "docs" of this directory.

NOTE 2: Late arrived Contributions will be handled only, if time allows and any company has the right to ask for postponing the document to the next meeting. The detailed agenda and time plan on eve of meeting, and the proposed allocation of documents to agenda items, are treated as being received on time even though they are available only at the start of the meeting (the chair does have some privileges)

NOTE 3: If a document which was received late (after the deadline) is a revision of a document which was received before the deadline, it is treated as being received on time.

Agenda	Agenda Item Title	Tdoc CP-24#	Document Title	Source	Decision	Notes
1	Opening of the meeting
1.1	Welcome speech	Welcome speech and other administrative information
1.2	IPR Declarations	Reminder about the IPR declaration
The attention of the delegates to the meeting of this Technical Specification Group is drawn to the fact that 3GPP Individual Members have the obligation under the IPR Policies of their respective Organizational Partners to inform their respective Organizational Partners of Essential IPRs they become aware of. The delegates are asked to take note that they are thereby invited: - to investigate whether their organization or any other organization owns IPRs which were, or were likely to become Essential in respect of the work of 3GPP. - to notify their respective Organizational Partners of all potential IPRs, e.g., for ETSI, by means of the IPR Information Statement and the Licensing declaration forms
1.3	Antitrust declarations	Reminder about the antitrust and competition laws
I also draw your attention to the fact that 3GPP activities are subject to antitrust and competition laws and that compliance with said laws is therefore required of any participant of this TSG/WG meeting including the Chairman and Vice Chairman. In case of question I recommend that you contact your legal counsel. The present meeting will be conducted with strict impartiality and in the interests of 3GPP. Furthermore, I would like to remind you that timely submission of work items in advance of TSG/WG/SWG meetings is important to allow for full and fair consideration of such matters.
1.4	Reminder for delegates attending the meeting
This meeting counts towards accrual and maintenance of voting rights. Please register using 3GPP portal: 3GPP Portal > Home.. Please confirm your participation by checking in by using the link provided by the tool when performing registration. Only possible after start of the meeting and before closing of the meeting. Meeting guidelines are provided in C4-244002
2	Allocation of Documents to Agenda Items
4001	agenda Draft Agenda	CT4 Chair	Noted
4002	other Meeting guidelines for CT4 Working Group meeting	CT4 Chair
4003	agenda Detailed agenda & time plan for CT4 meeting: status at document deadline	CT4 Chair	Noted
4004	agenda Detailed agenda & time plan for CT4 meeting: status on eve of meeting	CT4 Chair
4005	agenda Proposed allocation of documents to agenda items for CT4 meeting: status at document deadline	CT4 Chair	Noted
4006	agenda Proposed allocation of documents to agenda items for CT4 meeting: status on eve of meeting	CT4 Chair
4007	agenda The allocation of documents to agenda items for CT4 meeting: status at the end of meeting	CT4 Chair
3	Reports
4008	report Previous TSG CT & SA Status Report	CT4 Chair
4009	report Previous CT4 meeting report	MCC
4	Liaison statements	All Liaison statements are handled under this agenda item
4.1	Incoming liaisons
Plenary	4012	LS in LS “N32-f lifetime and reconnection”to 3GPP CT4/SA3	5GMRR	5GMRR Doc 45_07r1 To: CT4, SA3 CC: Contact: Bics Postponed from CT4#124 meeting
Plenary	4013	LS in Rel-18 Response LS on Restoration of N3mb Failure for MBS Broadcast	RAN3	R3-243888 To: CT4 CC: SA2 Contact: Nokia Postponed from CT4#124 meeting “Frank: should we cover all the three scenarios? We should give delegates more time considering all the scenarios. Only one scenario of the 3 in the incoming LS has been discussed during this meeting. More discussion needed in the next meeting” Related CR in 4212
Plenary	4014	LS in Rel-18 Reply on LS on the maximum number of devices supported in SLPP	CT WG1	C1-245040 To: RAN2 CC: CT4, SA2 Contact: vivo --- CT1 thanks RAN2’s LS regarding to the maximum number of devices that is supported in the SLPP messages (R2-2405988). CT1 would like to provide the following feedback: For ranging and sidelink positioning, the information transmitted over NAS via payload container IE has the limitation of a maximum length of 65536 octets from CT1 protocol point of view (the maximum size of a NAS message carrying payload container IE is specified in subclause 7.2.2 of TS 24.501 for further information). The related information includes e.g. SLPP messages, the result of the positioning request. So CT1 finds out that: The payload container IE may not be able to encapsulate a complete SLPP message with information for other UEs (UE2-UEn) with the maximum number of devices is 256 as defined by RAN2. The payload container IE may also not be able to encapsulate the absolute location result for other UEs (UE2-UEn) with the maximum number of devices is 256. This limitation also applies to the messages exchanged between UEs. To address the above issue, for RSPP supplementary messages, CT1 evaluated and achieved the consensus that the supported maximum number of other UEs (UE2-UEn) shall not be greater than 63 in R18 (see attachment), considering the associated information to be exchanged between UEs or between UE1 and LMF for ranging and sidelink positioning. --- Propose to note
Plenary	4015	LS in Rel-19 LS on supporting the 3xx based redirection mechanism for the "inner" resource creation	CT WG3	C3-244576 To: CT4 CC: CT1 Contact: Ericsson During CT3 #136, CT3 discussed and agreed the support of the 3xx based redirection mechanism for "inner" resource creation requests for all NBI and 5GC SBI APIs. Please refer to the discussion paper in C3-244464. CT3 kindly asks CT4 to consider the above agreement reached in CT3 and provide feedback (if needed).
Plenary	4016	LS in Response LS on Newly published data channel GSMA PRD TS.66	RAN WG5	R5-245464 To: GSMA TSG CC: SA, SA2, SA3, SA4, SA6, CT, CT1, CT3, CT4 Contact: Huawei --- RAN5 would like to thank GSMA TSG for the LS (TSG56_059) notifying the approval and publication of GSMA PRD TS.66 - IMS data channel API specification. RAN5 would also appreciate high level description in the LS about the TS.66 contents and association with GSMA PRD NG.134. RAN5#104 meeting endorsed a new Conformance Work Item (WI) proposal for IMS Data Channel in Rel-18. The main objective of this Conformance WI is to explicitly verify signalling conformance of UE core requirements for IMS Data Channel feature defined by CT1 in TS 24.186 and TS 24.229 (SIP and SDP aspects). An additional objective is to implicitly verify core requirements for data channel media type defined by SA4 in 3GPP TS 26.114. IMS Data Channel API conformance testing is outside the scope of RAN5, hence won’t be covered in this WI. RAN5 expects proponents of the new IMS Data Channel Conformance WI to submit the RAN5 endorsed WI proposal to the upcoming RAN Plenary#104 meeting (Melbourne, Australia 9 – 12 September 2024) for approval. Once the Conformance WI is approved, RAN5 will start IMS Data Channel conformance test development from RAN5#105 meeting (18 – 22 November 2024). Details of conformance test methodology and environment shall be figured out during the IMS Data Channel conformance test development work. At this stage, RAN5 is not expecting to invoke JavaScript APIs for IMS Data Channel conformance testing. --- Propose to note
4017	LS in Handling of TEI CRs	TSG RAN	Withdrawn	RP-240858 To: CC:
Plenary	4018	LS in LS on Avoiding Cross-TSG TEI	TSG RAN	RP-241686 To: TSG CT, CT WG1, CT WG3, CT WG4, CT WG6, TSG SA, SA WG1, SA WG2, SA WG3, SA WG4, SA WG5, SA WG6 CC: RAN WG1, RAN WG2, RAN WG3, RAN WG4, RAN WG5 Contact: NEC Lab --- TSG RAN has had an approved TEI handling procedure since March 2021 (RAN#91e). The latest approved version is RP-240858 (attached). The main purpose of this procedure is to improve transparency and traceability of TEI work. In line with previous inter-TSG agreement, it is not possible to trigger work in RAN WGs via TEI CRs coming from TSG SA/CT or SA/CT WGs. The same applies for the reverse direction. However, on several occasions in the recent past, RAN WGs received LSs from a WG of another TSG, with a request to introduce changes, based on an attached TEIxx CR. Please note that if SA (WGs) or CT (WGs) need RAN (WGs) to undertake work, a SA (WGs) or CT (WGs) Work Item with a Work Item Description (that is not only TEIxx) is required. Please note that MCC has given guidance that the receiving RAN groups should then use either the same SA/CT WI code that was in the incoming LS or the SA/CT WI code and a RAN WI code related to that. TSG RAN asks TSG CT (WGs) and TSG SA (WGs) to use an appropriate SA (WGs) or CT (WGs) WI code other than "TEIxx" when asking RAN (WGs) to undertake any necessary work required ---
Plenary	4019	LS in Rel-18 Reply LS on ECS Configuration Information	SA WG2	S2-2408700 To: TSG SA6 CC: TSG CT1, TSG CT3, TSG CT4 Contact: Samsung --- SA2 thanks SA6 for the feedback to resolve the issue. SA2 confirms that SA6 proposal can work for resolve the duplication issue of PLMN ID in the Spatial Validity Condition in TS 23.548. Accordingly, SA2 agrees to remove the list of PLMN IDs from the Spatial Validity Condition in TS 23.548. Please find the attached CR agreed in SA2 #164 meeting as a result of the corresponding discussion. ---
Plenary	4020	LS in Rel-18 LS Reply on support of provisioning ATSSS rules to the UE in EPC	SA WG2	S2-2408755 To: CT1 CC: CT4 Contact: NEC --- SA2 thanks CT1 for the LS on support of provisioning ATSSS rules to the UE in EPC. As the previous SA2 LS to CT1, SA2 does not change Rel-18 specifications for support of provisioning ATSSS rules to the UE in EPC. --- Propose to note
Plenary	4021	LS in LS on Completion of 5WWC_Ph2 (R18) work	SA WG2	S2-2409022 To: BBF, CableLabs CC: SA3, CT1, CT3, CT4 Contact: Nokia --- SA2 would like to inform BBF, CableLabs that SA2 (for the architecture), SA3 (for the security) and the corresponding 3GPP CT groups have completed the work on 5WWC_Ph2. The work on 5WWC_Ph2 corresponds as far as BBF/CableLabs is involved to Feature 2 described in clause 27.1 of TR 21.918 ('Release 18 Description; Summary of Rel-18 Work Items'). Architectural changes impacting BBF, CableLabs are specified in the latest R18 version of TS 23.316. --- Propose to note
Plenary	4022	LS in Rel-18 Reply LS on MPS PDU session handling for Non-MPS subscriber	SA WG2	S2-2409263 To: CT4 CC: Contact: Ericsson --- …… The essential issue listed above is that AMF only has the UE subscription level priority information and does not have any PDU session level priority information which may lead to the wrong message priority setting in AMF for the consequent PDU session related messages. SA2 would like to also indicate that there is potential issue even for the case when UE is MPS-subscriber, but a particular PDU session is not applied with priority handling (e.g., the MPS priority is only set for certain slice/DNN instead of all slice/DNN of the MPS-subscriber which may leads to the “wrong” doing of the AMF when setting the message priority for the PDU session). SA2 discussed the issue and has agreed the attached CRs to introduce the PDU Session level priority information provision from SMF to AMF. --- Related CRs in 4056 (and mirror), 4058 (and mirror), 4112 (and mirror), 4114 (and mirror), 4243 (and mirror)
Plenary	4023	LS in Rel-18 LS on Subscription of UPF event via I-SMF	SA WG2	S2-2409308 To: CT4 CC: CT3 Contact: Nokia --- CT4 observation: “whether SA2 considered both approaches above, and if so, on which criteria should the anchor SMF invoke the Nsmf_PDUSession API vs. the Nsmf_EventExposure to subscribe to UPF events via the I-SMF?” SA2 answer: SA2 has revised the 23.502 CR (see attachment) to use Nsmf_EventExposure for the anchor SMF to subscribe to UPF events via the I-SMF. CT4 observation: whether the anchor SMF should be able to determine if the requested UPF events/service are supported by the I-SMF/I-UPF, before triggering a subscription towards the I-SMF, and if so, how. SA2 answer: SMF needs to be able to determine whether relaying of subscription to UPF events is supported by the I-SMF. About what UPF events/service are supported by local UPF(s) controlled by I-SMF, the determination is up to I-SMF and not to SMF. Which means I-SMF may reject a Nsmf_EventExposure SUBSCRIBE from the anchor SMF if one of the target local UPF(s) doesn’t support the event. CT4 observation: whether the anchor SMF may need to subscribe to UPF events at the ULCL/BP and/or at the local PSA UPF; SA2 answer: the anchor SMF may need to subscribe to UPF events at the local ULCL/BP and/or at a local PSA UPF. CT4 observation: how to support subscriptions at the anchor SMF targeting ANY UE, e.g. ANY UE in a specific area, e.g. whether the anchor SMF should determine by itself the UEs present in the specific area and trigger then subscriptions, per PDU session, for the corresponding UEs? SA2 answer: .SA2 needs more time to analyze this case and will contact CT4 when this analysis has been carried out. ---
Plenary	4024	LS in Reply LS on clarifications on consent management	SA WG2	S2-2409440 To: TSG SA CC: TSG SA3, SA6, CT3, CT4 Contact: Samsung --- 3GPP SA2 would like to provide 3GPP SA with the input for response to LS S2-2407399 (OPG_173_Doc 04) as below. For Q3 in (S2-2407399) “For the UDM’s user consent information, are the user consent management aspects (e.g. capturing or revoking user consent from the subscriber) specified?”, SA2 suggests that the following SA2 references are added: The user consent aspect for MSISDN exposure to an authenticated and authorized AF is specified in clause 4.15.10A of TS 23.502.. The UE LCS Privacy Profiles in UDM is described in clause 5.4 of TS 23.273. The UE LCS Privacy Profiles contains Location Privacy Indication, which can be provided and updated by the UE and/or AF as specified in clause 6.12 of TS 23.273. --- Propose to note
Plenary	4025	LS in Rel-18 Reply LS on LCS user plane connection binding to the UE	SA WG2	S2-2409544 To: CT WG1 CC: CT WG4, SA WG3 Contact: CATT --- SA2 thanks CT1 for their reply LS (S2-2407423/C1-24394) on LCS user plane connection binding to the UE, SA2 agreed the CR in the attachment to align with CT1 agreements. --- Propose to note
Plenary	4026	LS in Reply LS on clarification on home network triggered re-authentication	SA WG3	S3-243412 To: CT4 CC: - Contact: Ericsson --- Question 1: Should the above user cases be considered as valid failure cases? Answer 1: From an SA3 perspective, case #2 shall be treated as failure case, the (source) AMF informs the UDM with a failure response. The UDM based on local policy can decide to wait for a subsequent AMF registration in UDM (e.g. after Handover is completed) before retrying to trigger authentication with another AMF in another access or with the new AMF that registers in the same access. In any case for cases #1 and #4, the AMF receiving the re-authentication notification message sends acknowledgement response message to the UDM. Case #3 is understood to be the same as Case#2 since from the UDM point of view the Re-Authentication Notification is always sent to the AMF currently registered. Therefore, the AMF can respond with a failure cause which is the same as the failure cause returned by case #2. For case #5 is a failure case and the UDM can take immediate action as already specified in 33.501, 6.1.5 (e.g. try AMF of another access). Question 2: Does SA3 see any need of differentiated handling in the UDM in each failure case? Or, what’s the expected UDM behaviour from the SA3 point of view? Answer 2: From SA3 perspective, when UDM requests to authenticate the UE, it means a situation that can only be addressed by authenticating the UE. The UDM handles the cases of the acknowledgement and the failures according to the existing specification in 33.501, 6.1.5. In the case of failures, the UDM may handle differently the failure case resulting from case #2 and case #5 above. Therefore, the AMF should respond with two different types of failure causes for the above scenarios. --- Related CRs in 4051, 4052, 4139 (and mirror), 4162 (and mirror) Reply LS in 4141
Plenary	4027	LS in Rel-18 LS on aggregation and other N32 topics in the context of mediated roaming	SA WG3	S3-243676 To: GSMA 5GMRR CC: CT4 Contact: BSI --- SA3 thanks GSMA 5GMRR for their LS reply (S3-242364) on the introduction of the domain ipxnetwork.org, and would like to provide the following responses and clarifications …… --- Propose to note
Plenary	4028	LS in LS on GSMA non-compliance with 3GPP specifications on 5G Roaming over Roaming Intermediaries	SA WG3	S3-243677 To: 3GPP TSG SA CC: CT4 Contact: Cable Labs --- SA3 would like to inform TSG SA that GSMA provided LS S3-242706 on 5G roaming over roaming intermediaries. SA3 specified an application layer security solution, namely PRINS, for 5G roaming over roaming intermediaries in Release 15, based on the requirements from GSMA on the end-to-end signalling security between HPLMN and VPLMN. While GSMA 5GMRR maintains that such end-to-end signalling security is its ultimate objective (see S3-234990), it recently informed SA3 that it has developed another type of solution for 5G roaming, so called "hop-by-hop TLS" (see S3-242706). Such hop-by-hop solution does not comply with TS 33.501, which mandates application layer end-to-end security using PRINS for roaming over roaming intermediaries. SA3 would like to ask TSG SA for guidance on how to resolve such issue with GSMA. --- Propose to note
Plenary	4029	LS in Rel-18 Reply LS on Resource content filters	SA WG3	S3-243678 To: CT4 CC: - Contact: Samsung --- SA3 thanks CT4 for their LS on Resource content filters. SA3 has reviewed the attached TR, has discussed the extension of Access Tokens as proposed in Solution #1 and #6 of 3GPP TR 29.857, and finds no security issues with these solutions. However, SA3 would like to point out that from SA3 perspective, C4-225023 and C4-213261 captured in clause 4 of TR 29.857 during the specification of SBA security were addressed by SA3. See also SA3 reply in S3-211581 (SA3 #110) and S3-223860 as the final conclusion of the problem identified by GSMA. Further, CT4 to note that, the solution #6 in TR 29.857 is only applicable for the particular token type, which is captured in the TS 33.501 clause 13.4.1.1.2 Access token request for accessing services of a specific NF Service Producer instance / NF Service Producer service instance. Because the Filter ID is not a common one that can be used for all the instances for a NFp type implicitly. In summary, from SA3 perspective resource content filters may not be required, however it is up to CT4 to decide whether to specify resource content filters considering 5G system benefits to specific NFp instances. --- Related pCR in 4046
Plenary	4030	LS in Rel-18 LS Reply on Newly Published data channel GSMA PRD TS.66	SA WG4	S4-241684 To: GSMA TSG CC: SA2, SA3, SA4, SA6, RAN5, SA, SA1, CT, CT1, CT3 & CT4 Contact: Huawei --- SA4 thanks GSMA for the LS on newly published data channel GSMA PRD TS.66 (S4-241435) and would like to provide the feedback as following: Question for SA4: GSMA would like to know, if, with reference to point 4 in the body of the LS, SA4 believes that there is the need to develop JavaScript APIs to control media stream? The content of point 4 is as below: Video pipeline and GSMA IR.94 extensions (new PRD) document would be the extension of GSMA IR.94 and would provide JavaScript API allowing to manipulate programmatically video media type. This work might be of interest to 3GPP SA4. Reply: SA4 has been working on the IMS-based AR Real Time Communication (see 3GPP TS 26.264), and Avatar based on IMS network (see 3GPP TR 26.813). These services require data channel application to capture, process and transport the video media, and the service logic should be controlled by the data channel application. Therefore, SA4 think that the JavaScript API for video pipeline is valuable. Questions for SA4 and SA6: GSMA would like to ask if there are plans to develop a reference implementation to test IMS Data Channel services. Reply: There are no plans to develop JavaScript code in SA4. --- Propose to note
Plenary	4031	LS in LS reply on improved KPIs involving end-to-end data volume transfer time analytics	SA WG5	S5-244658 To: RAN3 CC: SA2, CT3, CT4, RAN2 Contact: Ericsson --- SA5 thanks RAN3 for its LS on improved KPIs involving end-to-end data volume transfer time analytics in document R3-243941. SA5 would like to response to the questions with the following: RAN3 evaluated carefully the two specifications and made the following observations with respect to TS 28.552 and TS 28.558: TS 28.558 does not define M4 measurement. There seems to be a misalignment between the two specifications with respect to which entity performs the measurements. In particular, RAN3 identified the following cases: The “Average delay DL air-interface” is measured by the gNB-DU in TS 28.552 and by NRCellCU (for non-split and 2-split scenario) and GNBCUUPFunction (for 3-split scenario) in TS 28.558. The “Average delay DL in gNB-DU” is measured by the gNB-DU in TS 28.552 and by NRCellCU (for non-split and 2-split scenario) and GNBCUUPFunction (for 3-split scenario) in TS 28.558. The “UL PDCP SDU Loss Rate” is measured by the GNBCUUPFunction and NRCellCU in TS 28.552 and by GNBCUUPFunction in TS 28.558. From RAN3 perspective, the above misalignment should be corrected in TS 28.558 based on TS 28.552. From SA5 perspective, the misalignment between TS28.558 and TS 28.552 has been corrected in TS28.558v18.1.0. The missing M4 measurement has be added into TS28.558 as attached. For the following additional RAN3 observations on the S-TMSI identifier, Also, RAN3 made the following observations concerning the S-TMSI identifier: “S-TMSI” should be modified to “5G-S-TMSI”. S-TMSI is not available in the gNB-DU and in the gNB-CU-UP. S-TMSI may not be always available in the gNB-CU-CP. SA5 would like to thank RAN3 for the observation. NR MDT Trace Record Content and Trace Record Header are specified in TS32.423. SA5 agree that there is a benefit to have a (temporary) identifier in the management-based MDT measurement report. This identity shall be unique within the lifetime of the measurement session. So, some data analytics function (e.g., AIML related function) can have a better understanding that the collected data sets are measured from the same source. Therefore, it would be good to provide some kind of identifier to indicate the measurement was done in the same or different UE. The bullet g specified in TS28.558 is the “Measured UE Identifier”. It is Trace Target which is sent in Trace Activation. As specified in TS 32.422, IMSI or IMEISV or IMEI-TAC or SUPI is used as Trace Target in signalling-based MDT activation procedure in 5GC and NG-RAN, and the Trace Target for management-based NR MDT activation has been defined in TS 28.622. So, the “Measured UE Identifier” parameter specified in TS28.558 is not applicable to NG-RAN UE level (MDT) measurements. Therefore, SA5 has agreed to add a clarification in TS28.558 that the measurement bullet g) is only applicable for management-based activation of 5GC UE level measurement collection, and the bullet g) in NG-RAN UE level measurements are set to “N/A” instead of “S-TMSI”, please see the agreed CRs attached. --- Propose to note
Plenary	4032	LS in LS reply on MDT configuration control in NR-DC	SA WG5	S5-244659 To: RAN3, CT4 CC: Contact: Ericsson --- SA5 thanks RAN3 for its LS on MDT configuration control in NR-DC in document R3-243937. SA5 has discussed and agreed to specify a mNOnly indicator in mdtConfig data type. This attribute is only applicable to signalling based NR MDT procedure. According to 3GPP TS21.801, Annex K, ‘master’ is non-inclusive term. The possible alternative term is ‘main’. Therefore, SA5 has specified that “MN-only” as “Main Node Only”. SA5 Kindly ask RAN3 to take this into consideration. In addition, this change may have an impact on CT4. SA5 would like to ask CT4 to update corresponding specification accordingly. ---
Plenary	4033	LS in Rel-18 LS reply on 5G Trace to support UE level measurement	SA WG5	S5-244661 To: CT4 CC: CT3 Contact: China Mobile, Intel --- Q1: “How is the 5GC UE level measurements collection on SMF triggered/activated? SA5’s answer: SA5 will only keep the measurements collection activation specified in TS 32.422 to avoid the conflict and confusion. The attached SA5 CR (S5-243627) to remove the activation mechanism in TS 28.558 has been agreed in SA5. Q2: “What is the meaning of the following Information: … SA5’s answer: The “Trace reporting format” indicates reporting format of the Trace data, which is either streaming or file. However, the same information can be carried by the “Trace Collection Entity (TCE) IP Address” and “Trace Reporting Consumer URI” parameters, therefore the “Trace reporting format” parameter is not needed anymore. The attached CR (S5-243630/S5-243631) to remove “Trace reporting format” parameter from TS 32.422 has been agreed in SA5. The EP_N3 and EP_N9 are not necessarily the additoinal types of NE for 5GC UE level measurements collection using Trace mechanism defined in TS 32.422. But the measurements are collected and reported per EP_N3 and EP_N3 interface. The N4 Session Identifier is not used in signalling-based activation of 5GC UE level measurements collection, but only used for management-based activation. The attached CR (S5-245129/S5-245130) to clarify this in TS 28.558 has been agreed in SA5. Q3: “How is the 5GC UE level measurements collection on UPF triggered/activated? Can SMF re-use the existing Per QoS Flow per QoS Measurement mechanism as defined in clause 5.33.3.2 of 3GPP TS 23.501?” SA5’s answer: SA5 needs to correlate the UE level measurements collected by UPF and other NFs/nodes for one specific UE, and using the TR/TRSR under the Trace mechanism defined by TS 32.422 can support this correlation. The existing Per QoS Flow per QoS Measurement mechanism defined in clause 5.33.3.2 of 3GPP TS 23.501 cannot support the correlation with the measurements collected by other NFs/nodes for the UE. ---
Plenary	4034	LS in Rel-19 Reply LS on the stage 2 aspects of MINT_Ph2	TSG SA	SP-241013 To: CT1, SA1 CC: SA2, TSG CT, CT4 Contact: China Telecom --- TSG SA thanks CT1 for the LS (SP-240538 / C1-242675) on the stage 2 aspects of MINT_Ph2. TSG SA has considered the input from SA2 (SP-240558 / S2-2407313) and discussed the matter in their SA#104 meeting. TSG SA kindly asks CT1 to perform a study for MINT_Ph2_EPS. The context of the proposed scope differs compared to the Rel-17 MINT study in overall system aspects in that 4G/EPS is now the target system. Disaster roaming in case of 5G RAN failure between 5GS and EPS is in the scope for this study. EPS to EPS disaster roaming is out of scope. SA believes that the scope needs to be limited to 4G/EPS only without CS domain. The study scope needs to take into account the architectural relationship between the 5GS and EPS networks, including EPS interworking with 5GS as defined in TS 23.501. The study also needs to consider how to prevent signalling overload when UEs perform disaster roaming to EPS and when UEs return to 5GS. Specifically in the following SA1 requirement: Subject to regulatory requirements, operator's policy or UE capabilities, the 3GPP system shall be able to support a UE, with 5G-only national roaming access to a VPLMN, to obtain 4G connectivity service (e.g. voice call, mobile data service) from that VPLMN in the area where a Disaster Condition applies It needs to be clarified that the UE still receives service from IMS in HPLMN and only connectivity from VPLMN. Before concluding the study, CT1 should consult SA2 on the architectural impacts and consult SA for final decision on how to proceed with normative work. Based on Rel-17 MINT work, SA believes there will be architectural impacts that are under SA2 specifications scope. --- Propose to note
Plenary	4035	LS in Rel-18 Reply LS on data plane control by roaming hubs	TSG SA	SP-241014 To: GSMA 5GMRR CC: 3GPP SA WG1, 3GPP SA WG2, 3GPP SA WG3, 3GPP SA WG5, 3GPP CT WG4 Contact: Nokia --- 3GPP TSG SA thanks GSMA 5GMRR for their LS on data plane control by roaming hubs. 3GPP TSG SA reviewed the requirements listed in the LS from GSMA 5GMRR and would like to inform GSMA 5GMRR that there was no corresponding work in 3GPP WGs in Rel-18 and that there is currently no corresponding planned work in 3GPP WGs for Rel-19. 3GPP TSG SA would like to remind GSMA 5GMRR that work in 3GPP is based on direct contributions made by 3GPP members. 3GPP TSG SA expects GSMA 5GMRR to document appropriate architecture and service flows for data plane control by roaming hubs in GSMA’s roaming specifications. --- Propose to note
Plenary	4036	LS in Rel-18 LS on Security considerations for MPQUIC	TSG SA	SP-241015 To: IETF QUIC WG CC: SA3, SA2, CT, CT4 Contact: Intel --- 3GPP TSG SA would like to bring to the attention of IETF QUIC WG that the 3GPP Release 18 functionality for Access Traffic Steering, Switching and Splitting (ATSSS) has a dependency on the IETF draft on "Multipath Extension for QUIC" (draft-ietf-quic-multipath), as specified in 3GPP TS 23.501 clause 5.32.6.2.2. 3GPP TSG SA came to the realization that section 11 (Security Considerations) in the latest version of the aforementioned draft (draft-ietf-quic-multipath-08) is currently still TBD. Given that Release 18 in 3GPP is now frozen, TSG SA would like to kindly ask IETF QUIC WG to provide a new version of the IETF draft on "Multipath Extension for QUIC" to update section 11 (“Security Considerations”). --- Propose to note
Plenary	4037	LS in Reply LS on Newly published data channel GSMA PRD TS.66	TSG SA	SP-241404 To: GSMA TSG CC: Contact: InterDigital Propose to note
Plenary	4038	LS in LS on maintaining specification consistency between GSMA and 3GPP on 5G roaming over roaming intermediaries.	TSG SA	SP-241405 To: GSMA 5GMRR, GSMA NRG, GSMA NG CC: 3GPP SA WG1, 3GPP SA WG2, 3GPP SA WG3, 3GPP SA WG5, 3GPP CT WG4 Contact: NTT DOCOMO --- 3GPP TSG SA would like to emphasise the importance of maintaining consistency between GSMA and 3GPP specifications on 5G roaming over roaming intermediaries for operators and the ecosystems. It is TSG SA's understanding that (a) Prior to the formation of 5GMRR, GSMA defined the requirement of end-to-end protection of signalling messages between VPLMN and HPLMN in 5G, based on which SA3 specified and mandated the use of the application layer security solution PRINS for 5G roaming over roaming intermediaries; and (b) for 5G, GSMA specifies deployment options and models, as well as the interconnect architecture, while all specification of network function and SEPP behaviour is done within 3GPP. 3GPP security specifications provide a mechanism to fulfil the security requirements provided by GSMA. 3GPP TSG SA would like to point out that certain behaviours of interconnect nodes may influence the functionality and behaviour of network functions. In order to ensure compatibility of the ongoing 5G development in 3GPP with the deployment options and models defined by the GSMA, it is necessary that the behaviour of the intermediaries is well-defined, specified and aligned with the behaviour of the network functions. 3GPP specified an application layer security solution, namely PRINS, for 5G roaming over roaming intermediaries in Release 15, based on the requirements from GSMA on the end-to-end signalling security between HPLMN and VPLMN. While GSMA 5GMRR maintains that such end-to-end signalling security is its ultimate objective, it recently informed 3GPP that it has developed another type of solution for 5G roaming, so called "hop-by-hop TLS". Such hop-by-hop solution does not comply with TS 33.501 and does not meet the end-to-end security requirements for 5G roaming (see SP-241340), which mandates application layer end-to-end security using PRINS for roaming over roaming intermediaries. 3GPP TSG SA kindly asks GSMA 5GMRR and its member companies to work closely in and with the relevant 3GPP groups, especially SA2, SA3, and CT4 to avoid market fragmentation and incompatibilities. --- Propose to note
4.2	Outgoing liaisons
Plenary	4105	LS out Rel-19 LS on FS_IMS_RES	China Telecom Corporation Ltd.	To: SA2 CC: CT1, CT3
Plenary	4141	LS out Reply LS on clarification on home network triggered re-authentication	ZTE	To: SA3 CC:
Plenary	4203	LS out Rel-19 LS on Multicast MBS session restoration procedure for N3mb path failure	Nokia	R3-243888 To: RAN3 CC: SA2
5	Check of Approved Output Documents
4011	other Output Documents	CT4 Chair
6	OpenAPI version and ExternalDocs Update	This agenda item is used for allocating OpenAPI version and ExternalDocs update CRs for all releases
6.1	Rel-15 OpenAPI version and ExternalDocs Update CRs
6.2	Rel-16 OpenAPI version and ExternalDocs Update CRs
6.3	Rel-17 OpenAPI version and ExternalDocs Update CRs
29.256 0 Rel17 API version and External doc update	Qualcomm Incorporated	Email approval	CR possibly needed Email approval
29.309 0 Rel17 API version and External doc update	Ericsson	Email approval	CR possibly needed Email approval
29.502 0 Rel17 API version and External doc update	Nokia	Email approval	CR possibly needed Email approval
29.503 0 Rel17 API version and External doc update	Nokia	Email approval	CR possibly needed Email approval
29.504 0 Rel17 API version and External doc update	China Mobile	Email approval	CR possibly needed Email approval
29.505 0 Rel17 External doc update	China Mobile	Email approval	CR possibly needed Email approval
29.509 0 Rel17 API version and External doc update	Orange	Email approval	CR possibly needed Email approval
29.510 0 Rel17 API version and External doc update	Ericsson	Email approval	CR possibly needed Email approval
29.511 0 Rel17 API version and External doc update	Deutsche Telekom	Email approval	CR possibly needed Email approval
29.515 0 Rel17 API version and External doc update	CATT	Email approval	CR possibly needed Email approval
29.518 0 Rel17 API version and External doc update	Ericsson	Email approval	CR possibly needed Email approval
29.526 0 Rel17 API version and External doc update	ZTE	Email approval	CR possibly needed Email approval
29.531 0 Rel17 API version and External doc update	Huawei	Email approval	CR possibly needed Email approval
29.532 0 Rel17 API version and External doc update	Huawei	Email approval	CR possibly needed Email approval
29.536 0 Rel17 API version and External doc update	ZTE	Email approval	CR possibly needed Email approval
29.540 0 Rel17 API version and External doc update	ZTE	Email approval	CR possibly needed Email approval
29.541 0 Rel17 API version and External doc update	Ericsson	Email approval	CR possibly needed Email approval
29.542 0 Rel17 API version and External doc update	Ericsson	Email approval	CR possibly needed Email approval
29.544 0 Rel17 API version and External doc update	Nokia	Email approval	CR possibly needed Email approval
29.550 0 Rel17 API version and External doc update	Orange	Email approval	CR possibly needed Email approval
29.553 0 Rel17 API version and External doc update	CATT	Email approval	CR possibly needed Email approval
29.555 0 Rel17 API version and External doc update	CATT	Email approval	CR possibly needed Email approval
29.556 0 Rel17 API version and External doc update	Huawei	Email approval	CR possibly needed Email approval
29.559 0 Rel17 API version and External doc update	CATT	Email approval	CR possibly needed Email approval
29.562 0 Rel17 API version and External doc update	Ericsson	Email approval	CR possibly needed Email approval
29.563 0 Rel17 API version and External doc update4	Ericsson	Email approval	CR possibly needed Email approval
29.564 0 Rel17 API version and External doc update	China Mobile	Email approval	CR possibly needed Email approval
29.571 0 Rel17 API version and External doc update	Huawei	Email approval	CR possibly needed Email approval
29.572 0 Rel17 API version and External doc update	Ericsson	Email approval	CR possibly needed Email approval
29.573 0 Rel17 API version and External doc update	Huawei	Email approval	CR possibly needed Email approval
29.577 0 Rel17 API version and External doc update	Huawei	Email approval	CR possibly needed Email approval
29.578 0 Rel17 API version and External doc update	Nokia	Email approval	CR possibly needed Email approval
29.579 0 Rel17 API version and External doc update	China Telecom	Email approval	CR possibly needed Email approval
29.581 0 Rel17 API version and External doc update	Samsung	Email approval	CR possibly needed Email approval
29.598 0 Rel17 API version and External doc update	CISCO	Email approval	CR possibly needed Email approval
29.673 0 Rel17 API version and External doc update	Ericsson	Email approval	CR possibly needed Email approval
6.4	Rel-18 OpenAPI version and ExternalDocs Update CRs
29.175 0 Rel18 API version and External doc update	China Mobile	Email approval	CR possibly needed Email approval
29.176 0 Rel18 API version and External doc update	Huawei	Email approval	CR possibly needed Email approval
29.256 0 Rel18 API version and External doc update	Qualcomm SIncorporated	Email approval	CR possibly needed Email approval
29.309 0 Rel18 API version and External doc update	Ericsson	Email approval	CR possibly needed Email approval
29.502 0 Rel18 API version and External doc update	Nokia	Email approval	CR possibly needed Email approval
29.503 0 Rel18 API version and External doc update	Nokia	Email approval	CR possibly needed Email approval
29.504 0 Rel18 API version and External doc update	China Mobile	Email approval	CR possibly needed Email approval
29.505 0 Rel18 External doc update	China Mobile	Email approval	CR possibly needed Email approval
29.509 0 Rel18 API version and External doc update	Orange	Email approval	CR possibly needed Email approval
29.510 0 Rel18 API version and External doc update	Ericsson	Email approval	CR possibly needed Email approval
29.511 0 Rel18 API version and External doc update	Deutsche Telekom	Email approval	CR possibly needed Email approval
29.515 0 Rel18 API version and External doc update	CATT	Email approval	CR possibly needed Email approval
29.518 0 Rel18 API version and External doc update	Ericsson	Email approval	CR possibly needed Email approval
29.526 0 Rel18 API version and External doc update	ZTE	Email approval	CR possibly needed Email approval
29.531 0 Rel18 API version and External doc update	Huawei	Email approval	CR possibly needed Email approval
29.532 0 Rel18 API version and External doc update	Huawei	Email approval	CR possibly needed Email approval
29.536 0 Rel18 API version and External doc update	ZTE	Email approval	CR possibly needed Email approval
29.540 0 Rel18 API version and External doc update	ZTE	Email approval	CR possibly needed Email approval
29.541 0 Rel18 API version and External doc update	Ericsson	Email approval	CR possibly needed Email approval
29.542 0 Rel18 API version and External doc update	Ericsson	Email approval	CR possibly needed Email approval
29.544 0 Rel18 API version and External doc update	Nokia	Email approval	CR possibly needed Email approval
29.550 0 Rel18 API version and External doc update	Orange	Email approval	CR possibly needed Email approval
29.553 0 Rel18 API version and External doc update	CATT	Email approval	CR possibly needed Email approval
29.555 0 Rel18 API version and External doc update	CATT	Email approval	CR possibly needed Email approval
29.556 0 Rel18 API version and External doc update	Huawei	Email approval	CR possibly needed Email approval
29.559 0 Rel18 API version and External doc update	CATT	Email approval	CR possibly needed Email approval
29.562 0 Rel18 API version and External doc update	Ericsson	Email approval	CR possibly needed Email approval
29.563 0 Rel18 API version and External doc update	Ericsson	Email approval	CR possibly needed Email approval
29.564 0 Rel18 API version and External doc update	China Mobile	Email approval	CR possibly needed Email approval
29.571 0 Rel18 API version and External doc update	Huawei	Email approval	CR possibly needed Email approval
29.572 0 Rel18 API version and External doc update	Ericsson	Email approval	CR possibly needed Email approval
29.573 0 Rel18 API version and External doc update	Huawei	Email approval	CR possibly needed Email approval
29.577 0 Rel18 API version and External doc update	Huawei	Email approval	CR possibly needed Email approval
29.578 0 Rel18 API version and External doc update	Nokia	Email approval	CR possibly needed Email approval
29.579 0 Rel18 API version and External doc update	China Telecom	Email approval	CR possibly needed Email approval
29.581 0 Rel18 API version and External doc update	Samsung	Email approval	CR possibly needed Email approval
29.586 0 Rel18 API version and External doc update	Xiaomi	Email approval	CR possibly needed Email approval
29.598 0 Rel18 API version and External doc update	CISCO	Email approval	CR possibly needed Email approval
29.673 0 Rel18 API version and External doc update	Ericsson	Email approval	CR possibly needed Email approval
6.5	Rel-19 OpenAPI version and ExternalDocs Update CRs
29.175 0 Rel19 API version and External doc update	China Mobile	Email approval	CR possibly needed Email approval
29.176 0 Rel19 API version and External doc update	Huawei	Email approval	CR possibly needed Email approval
29.256 0 Rel19 API version and External doc update	Qualcomm Incorporated	Email approval	CR possibly needed Email approval
29.309 0 Rel19 API version and External doc update	Ericsson	Email approval	CR possibly needed Email approval
29.502 0 Rel19 API version and External doc update	Nokia	Email approval	CR possibly needed Email approval
29.503 0 Rel19 API version and External doc update	Nokia	Email approval	CR possibly needed Email approval
29.504 0 Rel19 API version and External doc update	China Mobile	Email approval	CR possibly needed Email approval
29.505 0 Rel19 External doc update	China Mobile	Email approval	CR possibly needed Email approval
29.509 0 Rel19 API version and External doc update	Orange	Email approval	CR possibly needed Email approval
29.510 0 Rel19 API version and External doc update	Ericsson	Email approval	CR possibly needed Email approval
29.511 0 Rel19 API version and External doc update	Deutsche Telekom	Email approval	CR possibly needed Email approval
29.515 0 Rel19 API version and External doc update	CATT	Email approval	CR possibly needed Email approval
29.518 0 Rel19 API version and External doc update	Ericsson	Email approval	CR possibly needed Email approval
29.526 0 Rel19 API version and External doc update	ZTE	Email approval	CR possibly needed Email approval
29.531 0 Rel19 API version and External doc update	Huawei	Email approval	CR possibly needed Email approval
29.532 0 Rel19 API version and External doc update	Huawei	Email approval	CR possibly needed Email approval
29.536 0 Rel19 API version and External doc update	ZTE	Email approval	CR possibly needed Email approval
29.540 0 Rel19 API version and External doc update	ZTE	Email approval	CR possibly needed Email approval
29.541 0 Rel19 API version and External doc update	Ericsson	Email approval	CR possibly needed Email approval
29.542 0 Rel19 API version and External doc update	Ericsson	Email approval	CR possibly needed Email approval
29.544 0 Rel19 API version and External doc update	Nokia	Email approval	CR possibly needed Email approval
29.550 0 Rel19 API version and External doc update	Orange	Email approval	CR possibly needed Email approval
29.553 0 Rel19 API version and External doc update	CATT	Email approval	CR possibly needed Email approval
29.555 0 Rel19 API version and External doc update	CATT	Email approval	CR possibly needed Email approval
29.556 0 Rel19 API version and External doc update	Huawei	Email approval	CR possibly needed Email approval
29.559 0 Rel19 API version and External doc update	CATT	Email approval	CR possibly needed Email approval
29.562 0 Rel19 API version and External doc update	Ericsson	Email approval	CR possibly needed Email approval
29.563 0 Rel19 API version and External doc update	Ericsson	Email approval	CR possibly needed Email approval
29.564 0 Rel19 API version and External doc update	China Mobile	Email approval	CR possibly needed Email approval
29.571 0 Rel19 API version and External doc update	Huawei	Email approval	CR possibly needed Email approval
29.572 0 Rel19 API version and External doc update	Ericsson	Email approval	CR possibly needed Email approval
29.573 0 Rel19 API version and External doc update	Huawei	Email approval	CR possibly needed Email approval
29.577 0 Rel19 API version and External doc update	Huawei	Email approval	CR possibly needed Email approval
29.578 0 Rel19 API version and External doc update	Nokia	Email approval	CR possibly needed Email approval
29.579 0 Rel19 API version and External doc update	China Telecom	Email approval	CR possibly needed Email approval
29.581 0 Rel19 API version and External doc update	Samsung	Email approval	CR possibly needed Email approval
29.586 0 Rel19 API version and External doc update	Xiaomi	Email approval	CR possibly needed Email approval
29.598 0 Rel19 API version and External doc update	CISCO	Email approval	CR possibly needed Email approval
29.673 0 Rel19 API version and External doc update	Ericsson	Email approval	CR possibly needed Email approval
7	Tdocs not fit into other agenda items
8	Release 8 and earlier All work items
9	Release 9 All work items
10	Release 10 All work items
11	Release 11 All work items
12	Release 12 All work items
13	Release 13 All work items
14	Release 14 All work items
15	Release 15 All work items
16	Release 16 All work items
Plenary	4145	CR 29.510 1057 Rel-16 Correct Links table	ZTE	WI TEI16 CAT F
Plenary	4146	CR 29.510 1058 Rel-17 Correct Links table	ZTE	WI TEI16 CAT A
Plenary	4147	CR 29.510 1059 Rel-18 Correct Links table	ZTE	WI TEI16 CAT A
Plenary	4148	CR 29.510 1060 Rel-19 Correct Links table	ZTE	WI TEI16 CAT A
17	Release 17
17.1	Rel-17 work planning
17.2	New WIDs for Rel-17
17.3	Revised WIDs for Rel-17
17.4	TEI17 [TEI17]
Breakout	4040	CR 29.503 1310 Rel-17 UeIdentifiers alignment	Nokia	WI TEI17 CAT F
Breakout	4041	CR 29.503 1311 Rel-18 UeIdentifiers alignment	Nokia	WI TEI17 CAT A
Breakout	4042	CR 29.503 1312 Rel-19 UeIdentifiers alignment	Nokia	WI TEI17 CAT A
Main	4204	CR 29.281 0132 Rel-17 Fixing the GTP-U Tunnel Status Information and Recovery Time Stamp IEs	Nokia	WI TEI17, SPOCUP, EGTPUR CAT F
Main	4205	CR 29.281 0133 Rel-18 Fixing the GTP-U Tunnel Status Information and Recovery Time Stamp IEs	Nokia	WI TEI17, SPOCUP, EGTPUR CAT A
Main	4206	CR 29.281 0134 Rel-19 Fixing the GTP-U Tunnel Status Information and Recovery Time Stamp IEs	Nokia	WI TEI17, SPOCUP, EGTPUR CAT A
17.5	Service Based Interface Protocol Improvements Release 17 [SBIProtoc17]
Plenary	4253	CR 29.510 1076 Rel-17 DataSetId Usage Essential Correction	Ericsson	WI SBIProtoc17 CAT F Chair’s note from CT4#124: We need to discuss before next CT4 meeting about a potential Rel-17 fix, where the UDR only registers "APPLICATION" and/or "POLICY", and the list of subsets it actually supports.
Plenary	4254	CR 29.510 1077 Rel-18 DataSetId Usage Essential Correction	Ericsson	WI SBIProtoc17 CAT A
Plenary	4255	CR 29.510 1078 Rel-19 DataSetId Usage Essential Correction	Ericsson	WI SBIProtoc17 CAT A
17.6	Multi-device and multi-identity enhancements [MuDe]
17.7	Stage-3 5GS NAS protocol development 17 [5GProtoc17] [5GProtoc17-non3GPP]
17.8	Protocol enhancements for Mission Critical Services [MCProtoc17]
17.9	Stage-3 SAE Protocol Development [SAES17] [SAES17-CSFB] [SAES17-non3GPP]
17.10	Enhancement for the 5G Control Plane Steering of Roaming for UE in CONNECTED mode [eCPSOR_CON]
17.11	IMS Stage-3 IETF Protocol Alignment [IMSProtoc17]
17.12	CT aspects of Enhancements to Mission Critical Data [eMCData3]
17.13	Stage 3 of Multimedia Priority Service (MPS) Phase 2 [MPS2]
17.14	PFD management enhancement [pfdManEnh]
17.15	BEst Practice of PFCP [BEPoP]
17.16	Restoration of PDN Connections in PGW-C/SMF Set [RPCPSET]
17.17	Stage 3 of eMONASTERY2 [eMONASTERY2]
17.18	CT aspects of 5GC architecture for satellite networks [5GSAT_ARCH-CT]
17.19	CT aspects of Enhanced MCCI with LMR Systems [eMCCI_CT]
17.20	CT aspects of AKMA [AKMA-CT]
17.21	PAP/CHAP protocols usage in 5GS [PAP_CHAP]
17.22	Service-based support for SMS in 5GC [SMS_SBI]
17.23	Enhancement of Inter-PLMN Roaming [EoIPR]
17.24	Mission Critical system migration and interconnection [MCSMI_CT]
17.25	CT aspects of Integration of GBA into SBA [GBA_5G]
17.26	Reliable Data Service Serialization Indication [RDSSI_CT]
17.27	CT aspects for Enabling Edge Applications [EDGEAPP]
17.28	CT aspects of eNPN [eNPN]
17.29	CT aspects of 5G_eLCS_ph2 [5G_eLCS_ph2]
17.30	CT aspects for ID_UAS [ID_UAS]
17.31	CT aspects of support of enhanced Industrial IoT [IIoT]
17.32	CT aspects of eV2XAPP [eV2XAPP]
17.33	CT aspects of 5G eEDGE [eEDGE_5GC]
17.34	Stage 3 for Enhancement of Network Slicing Phase 2 [eNS_Ph2]
17.35	Start of Pause of Charging via User Plane [SPOCUP]
17.36	CT aspects of ATSSS_Ph2 [ATSSS_Ph2]
17.37	CT aspects of eNA_Ph2 [eNA_Ph2]
17.38	CT aspects of proximity based services in 5GS [5G_ProSe]
17.39	CT aspects of Enabling Multi-USIM Devices [MUSIM]
17.40	CT aspects on TEI17_SPSFAS [TEI17_SPSFAS]
17.41	CT aspects on TEI17_SAPES [TEI17_SAPES]
17.42	CT aspects on TEI17_DCAMP [TEI17_DCAMP]
17.43	CT aspects on TEI17_GEM [TEI17_GEM]
17.44	CT3 aspects of N7 Interfaces Enhancements to Support GERAN and UTRAN [TEI17_NIESGU]
17.45	UICC-terminal interface testing for UEs with non-removable UICCs [nrUICC_UEConTest]
17.46	CT aspects of Support of different slices over different Non 3GPP access [TEI17_N3SLICE]
17.47	CT aspects of the architectural enhancements for 5G multicast-broadcast services [5MBS]
17.48	CT Aspects of Application Layer Support for Uncrewed Aerial Systems (UAS) [UASAPP]
17.49	CT aspects of eV2XARC_Ph2 [eV2XARC_Ph2]
17.50	CT aspects of MCOver5GS [MCOver5GS]
17.51	Enhancement of 5G PCC related services in Rel-17 [en5GPccSer17]
17.52	Enhancements of 3GPP Northbound Interfaces and Application Layer APIs [NBI17]
17.53	Stage 3 aspects of enh3MCPTT [enh3MCPTT-CT]
17.54	Enhanced Service Enabler Architecture Layer for Verticals [eSEAL]
17.55	System enhancement for redundant PDU session [TEI17_SE_RPS]
17.56	CT aspects of Support for Minimization of service Interruption [MINT]
17.57	IMS voice service support and network usability guarantee for UE’s E-UTRA capability disabled scenario in SA 5GS [ING_5GS]
17.58	CT aspects for enabling MSGin5G Service [5GMARCH]
17.59	Restoration of profiles related to UDR [ReP_UDR]
17.60	Enhancement on the GTP-U entity restart [EGTPUR]
17.61	Multi-device enhancements for device transfers [MuDTran]
17.62	CT aspects of Architecture Enhancement for NR Reduced Capability Devices [ARCH_NR_REDCAP]
17.63	Enhancements of 3GPP profiles for cryptographic algorithms and security protocols [eCryptPr]
17.64	IMS Optimization for HSS Group ID in an SBA environment [TEI17_IMSGID]
17.65	CT aspects of NB-IoT/eMTC Non-Terrestrial Networks in EPS [IoT_SAT_ARCH_EPS]
17.66	Repository for the 3GPP Allocated Port Numbers for New 3GPP Interfaces [PortAl]
17.67	Non-Seamless WLAN offload Authentication in 5GS [NSWO_5G]
17.68	CT aspects of AKMA TLS protocol profiles [AKMA_TLS]
17.69	Modifying PASSporT signing and verification [SPECTRE_Ph3]
17.70	CT aspects of enhancement of RAN Slicing for NR [NRslice]
17.71	CT aspects of 5GMS AF Event Exposure [EVEX]
17.72	Update of conformance test specifications to Rel-17 [UEConTest_R17]
17.73	Any other Rel-17 Work item or Study item
18	Release 18
18.1	Rel-18 work planning
18.2	New WIDs for Rel-18
18.3	Revised WIDs for Rel-18
18.4	TEI18 [TEI18]
Main	4056	CR 29.502 0798 Rel-18 PDU Session Priority	Ericsson, Nokia	WI 5GS_Ph1-CT, TEI18 CAT F Overlapping with 4114
Main	4057	CR 29.502 0799 Rel-19 PDU Session Priority	Ericsson, Nokia	WI 5GS_Ph1-CT, TEI18 CAT A
Main	4114	CR 29.502 0807 Rel-18 PDU Session Priority	ZTE	WI SBIProtoc18 CAT F
Main	4115	CR 29.502 0808 Rel-19 PDU Session Priority	ZTE	WI SBIProtoc18 CAT A
Main	4058	CR 29.518 1118 Rel-18 PDU Session Priority	Ericsson, Nokia	WI 5GS_Ph1-CT, TEI18 CAT F Overlapping with 4112, 4243
Main	4059	CR 29.518 1119 Rel-19 PDU Session Priority	Ericsson, Nokia	WI 5GS_Ph1-CT, TEI18 CAT A
Main	4112	CR 29.518 1122 Rel-18 PDU Session Priority	ZTE	WI SBIProtoc18 CAT F
Main	4113	CR 29.518 1123 Rel-19 PDU Session Priority	ZTE	WI SBIProtoc18 CAT A
Main	4243	CR 29.518 1129 Rel-18 PDU session priority	Huawei	WI TEI18 CAT F
Main	4244	CR 29.518 1130 Rel-19 PDU session priority	Huawei	WI TEI18 CAT A
Main	4098	CR 29.274 2114 Rel-18 MDT Configuration for immediate MDT	Huawei	WI TEI18, NR_SON_MDT-Core CAT F
Main	4099	CR 29.274 2115 Rel-19 MDT Configuration for immediate MDT	Huawei	WI TEI18, NR_SON_MDT-Core CAT A
Main	4100	CR 29.274 2116 Rel-18 Support of Trace Reporting Consumer URI	Huawei	WI TEI18, NR_SON_MDT-Core CAT F
4101	CR 29.274 2117 Rel-19 Support of Trace Reporting Consumer URI	Huawei	revised to C4-244251	Revision of C4-244251 WI TEI18, NR_SON_MDT-Core CAT A
Main	4251	CR 29.274 2117 Rel-19 Support of Trace Reporting Consumer URI	Huawei	WI NR_SON_MDT-Core, TEI18 CAT A
Plenary	4110	CR 29.500 0449 Rel-18 Access Token Claim Mismatch	ZTE	WI TEI18, 5G_eSBA CAT F
Plenary	4111	CR 29.500 0450 Rel-19 Access Token Claim Mismatch	ZTE	WI TEI18, 5G_eSBA CAT A
Plenary	4165	CR 29.571 0588 Rel-18 Update on access restrictions for satellite access	Huawei	WI TEI18, IoT_SAT_ARCH_EPS CAT F
Plenary	4166	CR 29.571 0589 Rel-19 Update on access restrictions for satellite access	Huawei	WI TEI18, IoT_SAT_ARCH_EPS CAT A
Main	4189	CR 29.518 1124 Rel-18 Correction of unavailability period	Huawei	WI TEI18, 5GSAT_Ph2 CAT F
Main	4190	CR 29.518 1125 Rel-19 Correction of unavailability period	Huawei	WI TEI18, 5GSAT_Ph2 CAT A
Plenary	4201	CR 29.501 0164 Rel-18 Restore deleted clause	Nokia, MCC	WI TEI18 CAT F
Plenary	4202	CR 29.501 0165 Rel-19 Restore deleted clause	Nokia, MCC	WI TEI18 CAT A
Main	4261	CR 29.518 1131 Rel-18 Correction on LCS Correlation ID as UE Context ID	Ericsson	WI TEI18 CAT F
Main	4262	CR 29.518 1132 Rel-19 Correction on LCS Correlation ID as UE Context ID	Ericsson	WI TEI18 CAT A
Breakout	4290	CR 23.632 0049 Rel-18 Not Cancelling MME registration upon EPS to 5GS mobility	Nokia	WI TEI18, 5GS_Ph1-CT CAT F
18.5	CT aspects of NBI18 [NBI18]
18.6	CT aspects of SBIProtoc18 [SBIProtoc18]
4112	CR 29.518 1122 Rel-18 PDU Session Priority	ZTE	Moved to 18.4	WI SBIProtoc18 CAT F
4113	CR 29.518 1123 Rel-19 PDU Session Priority	ZTE	Moved to 18.4	WI SBIProtoc18 CAT A
4114	CR 29.502 0807 Rel-18 PDU Session Priority	ZTE	Moved to 18.4	WI SBIProtoc18 CAT F
4115	CR 29.502 0808 Rel-19 PDU Session Priority	ZTE	Moved to 18.4	WI SBIProtoc18 CAT A
Breakout	4142	CR 29.503 1326 Rel-18 Correction of 3xx response	ZTE	WI SBIProtoc18 CAT F
Breakout	4143	CR 29.503 1327 Rel-19 Correction of 3xx response	ZTE	WI SBIProtoc18 CAT A
Plenary	4238	CR 29.573 0207 Rel-18 Autonomous correlation of N32-c and N32-f	NTT DOCOMO	WI SBIProtoc18 CAT F
Plenary	4239	CR 29.573 0216 Rel-19 Autonomous correlation of N32-c and N32-f	NTT DOCOMO	WI SBIProtoc18 CAT A
Plenary	4281	CR 29.501 0168 Rel-18 Missing clause	Ericsson, MCC	WI SBIProtoc18 CAT F
Plenary	4282	CR 29.501 0169 Rel-19 Missing clause	Ericsson, MCC	WI SBIProtoc18 CAT A
18.7	Stage-3 5GS NAS protocol development 18 general aspects [5GProtoc18]
18.8	Stage-3 5GS NAS protocol development 18 non 3GPP aspects [5GProtoc18-non3GPP]
18.9	Stage-3 SAE Protocol Development [SAES18]
18.10	Stage-3 SAE Protocol Development CSFB [SAES18-CSFB]
18.11	Stage-3 SAE Protocol Development non 3GPP [SAES18-non3GPP]
18.12	Protocol enhancements for Mission Critical Services [MCProtoc18]
18.13	MPS for Supplementary Services [MPSSupServ]
18.14	CT aspects of Mission Critical Services over 5MBS [MCOver5MBS]
18.15	CT aspects of Mission Critical Services over 5GProSe [MCOver5GProSe]
18.16	IMS Stage-3 IETF Protocol Alignment [IMSProtoc18]
18.17	CT aspects of Signal level Enhanced Network Selection [SENSE]
18.18	Rel-18 Enhancements of UE Policy [UEP18]
18.19	5GS support of NR RedCap UE with long eDRX for RRC_INACTIVE State [NR_REDCAP_Ph2]
18.20	CT aspects on Multiple location report for MT-LR Immediate Location Request for regulatory services [TEI18_MLR]
18.21	Enhancement of Shared Data ID and Handling [ShDatID_H]
18.22	CT Aspects of Edge Computing Phase 2 [EDGE_Ph2]
18.23	Enhancement of NSAC for maximum number of UEs with at least one PDU session/PDN connection [eNSAC]
18.24	Mission critical system migration and interconnection enhancements [eMCSMI_IRail]
18.25	CT aspects of application layer support for V2X services; Phase 3 [V2XAPP_Ph3]
18.26	CT aspects of proximity based services in 5GS Phase 2 [5G_ProSe_Ph2]
18.27	Support for 5WWC Phase 2 [5WWC_Ph2]
18.28	Enhancement of application detection event exposure [TEI18_ADEE]
18.29	CT aspects of General Support of IPv6 Prefix Delegation in 5GS [TEI18_IPv6PD]
18.30	CT aspects of 5G System with Satellite Backhaul [5GSATB]
18.31	Timing Resiliency and URLLC enhancements [TRS_URLLC]
18.32	Extensions to the TSC Framework to support DetNet [DetNet]
18.33	CT aspects for Enabling Edge Applications Phase 2 [EDGEAPP_Ph2]
18.34	Rel-18 enhancements of session management policy control [SMPC18]
18.35	CT aspects of 5G System Enabler for Service Function Chaining [SFC]
18.36	Enhancement of Network Automation Enablers [eNetAE]
18.37	CT aspects of enhancement of 5G UE Policy [eUEPO]
Plenary	4116	CR 29.510 1050 Rel-18 Unnecessary PCF Capability	ZTE	WI eUEPO CAT F Overlapping with 4187, 4207
Plenary	4117	CR 29.510 1051 Rel-19 Unnecessary PCF Capability	ZTE	WI eUEPO CAT A
Plenary	4187	CR 29.510 1070 Rel-18 Correction of UPF information	Huawei	WI eUEPO CAT F
Plenary	4188	CR 29.510 1071 Rel-19 Correction of UPF information	Huawei	WI eUEPO CAT A
Plenary	4207	CR 29.510 1072 Rel-18 Incorrect PCF registration parameters	Nokia	WI eUEPO CAT F
Plenary	4208	CR 29.510 1073 Rel-19 Incorrect PCF registration parameters	Nokia	WI eUEPO CAT A
18.38	CT aspect of Seamless UE context recovery [SUECR]
18.39	Secondary DN authentication and authorization in EPC IWK cases [TEI18_SDNAEPC]
18.40	CT aspects of enhancement to the 5GC location services - phase 3 [5G_eLCS_Ph3]
Breakout	4074	CR 29.572 0284 Rel-18 Modify the attributes of LocContextData	China Telecom	WI 5G_eLCS_Ph3 CAT F
Breakout	4075	CR 29.572 0285 Rel-19 Modify the attributes of LocContextData	China Telecom	WI 5G_eLCS_Ph3 CAT A
Breakout	4118	CR 29.572 0286 Rel-18 LCS Correlation ID in Nlmf_Location_CancelLocation Request	ZTE	WI 5G_eLCS_Ph3 CAT F
Breakout	4119	CR 29.572 0287 Rel-19 LCS Correlation ID in Nlmf_Location_CancelLocation Request	ZTE	WI 5G_eLCS_Ph3 CAT A
Breakout	4158	CR 29.572 0289 Rel-18 Update on cancel location	Huawei	WI 5G_eLCS_Ph3 CAT F
Breakout	4159	CR 29.572 0290 Rel-19 Update on cancel location	Huawei	WI 5G_eLCS_Ph3 CAT A
Breakout	4291	CR 29.515 0190 Rel-18 Correction to the user location report attributes	Nokia	WI 5G_eLCS_Ph3 CAT F
Breakout	4292	CR 29.515 0191 Rel-19 Correction to the user location report attributes	Nokia	WI 5G_eLCS_Ph3 CAT A
18.41	CT aspects of Enhanced support of Non-Public Networks Phase 2 [eNPN_Ph2]
18.42	CT aspects of SEAL data delivery enabler for vertical applications [SEALDD]
18.43	Enhanced Service Enabler Architecture Layer for Verticals Phase 3 [SEAL_Ph3]
18.44	CT Aspects of Application Layer Support for Uncrewed Aerial Systems (UAS), Phase 2 [UASAPP_Ph2]
18.45	CT Aspects of 5GC architecture for satellite networks, Phase 2 [5GSAT_Ph2]
18.46	CT Aspects of Uncrewed Aerial Systems (UAS), Phase 2 [UAS_Ph2]
18.47	CT aspects of Ranging_SL [Ranging_SL]
Breakout	4304	CR 29.572 0292 Rel-18 Clarification on the RangeDirection parameter	CATT	WI Ranging_SL CAT F
Breakout	4305	CR 29.572 0293 Rel-19 Clarification on the RangeDirection parameter	CATT	WI Ranging_SL CAT A
Breakout	4313	CR 29.572 0295 Rel-18 Updates on relative velocity	Xiaomi	WI Ranging_SL CAT F
Breakout	4314	CR 29.572 0296 Rel-19 Updates on relative velocity	Xiaomi	WI Ranging_SL CAT A
Breakout	4315	CR 24.080 0120 Rel-18 Updates on relative velocity	Xiaomi	WI Ranging_SL CAT F
Breakout	4316	CR 24.080 0121 Rel-18 Updates on SL-MT-LR for periodic triggered Location Events	Xiaomi	WI Ranging_SL CAT F
18.48	CT aspects of 5GFLS [5GFLS]
18.49	CT aspects of MCGWUE [MCGWUE]
18.50	GBA_U Based APIs [GBA_U_APIs]
18.51	CT aspects of AIML [AIMLsys]
18.52	CT aspects of NG_RTC [NG_RTC]
4102	CR 29.175 0016 Rel-18 DC resource release due to a CANCEL request	China Mobile	withdrawn	WI NG_RTC CAT F
Breakout	4103	CR 29.175 0017 Rel-18 DC resource release due to a CANCEL request	China Mobile	WI NG_RTC CAT F
Breakout	4104	CR 29.175 0018 Rel-18 Remove the MRF description	China Mobile	WI NG_RTC CAT F
Breakout	4231	CR 29.175 0020 Rel-18 Report the QoS info to DCSF	Huawei	WI NG_RTC CAT F
Breakout	4232	CR 29.176 0020 Rel-18 Correction on Nmf_MRM service	Huawei	WI NG_RTC CAT F
Breakout	4300	CR 29.175 0023 Rel-18 Remove the MRF	CATT	WI NG_RTC CAT F
18.53	CT aspects of 5G AM Policy [AMP]
18.54	CT aspects on Dynamically Changing AM Policies in the 5GC Phase 2 [TEI18_DCAMP_Ph2]
18.55	CT aspects of MPS_WLAN [MPS_WLAN]
18.56	CT aspects of ADAES [ADAES]
18.57	CT aspects of MSGin5G Service Ph2 [5GMARCH_Ph2]
18.58	CT aspects of VMR [VMR]
Plenary	4184	CR 29.510 1067 Rel-18 Discovery of LMF that supports LCS when MBSR is involved	Huawei	WI VMR CAT F Overlapping with 4309
Plenary	4185	CR 29.510 1068 Rel-19 Discovery of LMF that supports LCS when MBSR is involved	Huawei	WI VMR CAT A
Plenary	4309	CR 29.510 1083 Rel-18 LMF supports LCS when MBSR is involved	Nokia	WI VMR CAT F
Plenary	4310	CR 29.510 1084 Rel-19 LMF supports LCS when MBSR is involved	Nokia	WI VMR CAT A
18.59	Enhancements on Service-based support for SMS in 5GC [eSMS_SBI]
18.60	CT aspects of eNA_Ph3 [eNA_Ph3]
Plenary	4182	CR 29.510 1065 Rel-18 Discovery of AnLF based of interoperability indicator of the MTLF	Huawei	WI eNA_Ph3 CAT F
Plenary	4183	CR 29.510 1066 Rel-19 Discovery of AnLF based of interoperability indicator of the MTLF	Huawei	WI eNA_Ph3 CAT A
18.61	CT aspects of PIN [PIN]
18.62	CT aspects of PINAPP [PINAPP]
18.63	CT aspects of GMEC [GMEC]
18.64	CT aspects of 5MBS_Ph2 [5MBS_Ph2]
Main	4209	CR 29.244 0879 Rel-18 MBS session charging per rating group	Nokia	WI 5MBS_Ph2, 5MBS_CH CAT F
18.65	CT aspects of Enhancement of Network Slicing Phase 3 [eNS_Ph3]
18.66	CT aspects of XRM [XRM]
Main	4095	CR 29.502 0805 Rel-18 RAN-triggered ECN Marking or Congestion Information Status change	Huawei	WI XRM CAT F
Main	4096	CR 29.502 0806 Rel-19 RAN-triggered ECN Marking or Congestion Information Status change	Huawei	WI XRM CAT A
Main	4097	CR 29.244 0872 Rel-18 Correction on End of Data Burst Indication	Huawei	WI XRM CAT F
Main	4120	CR 29.244 0873 Rel-18 UPF Behaviour of Setting PDU Set Information	ZTE	WI XRM CAT F
Main	4193	CR 29.571 0591 Rel-18 Correction of RtpHeaderExtInfo	Lenovo	WI XRM CAT F
Main	4194	CR 29.571 0592 Rel-19 Correction of RtpHeaderExtInfo	Lenovo	WI XRM CAT A
18.67	CT aspects of Access Traffic Steering, Switching and Splitting support in 5G system – Phase 3 [ATSSS_Ph3]
Plenary	4195	Work Plan Rel-18 Work Plan for ATSSS Phase 3	Lenovo
18.68	CT4 aspects of UPF enhancement for exposure and SBA [UPEAS]
4090	CR 29.564 0108 Rel-19 Rejection if UPF event Exposure is not supported for non-IP PDU session	Huawei	Moved to 19.4	WI UPEAS CAT F
18.69	UE pre-configuration for 5MBS [UEConfig5MBS]
18.70	CT aspects of Enhanced Mission Critical Push-to-talk architecture phase 4 [enh4MCPTT]
18.71	CT aspects of Slice-based PLMN Selection [PLMNsel_NS]
18.72	Enhancement of Network Slicing UICC application for network slice-specific authentication and authorization [eNS_UICC]
18.73	CT aspects of MBS support for V2X services [TEI18_MBS4V2X]
18.74	CT aspects on Spending Limits for AM and UE Policies in the 5GC [TEI18_SLAMUP]
18.75	CT aspects of home network triggered primary authentication [HN_Auth]
Breakout	4051	CR 29.503 1314 Rel-19 Reauthentication pending	Nokia	WI TEI19, HN_Auth CAT B
Breakout	4052	CR 29.503 1315 Rel-19 Reauthentication required for SDM subscribe	Nokia	WI TEI19, HN_Auth CAT F
Breakout	4139	CR 29.503 1324 Rel-18 Clarify the application errors included in Re-AuthenticationNotification response	ZTE	WI HN_Auth CAT F
Breakout	4140	CR 29.503 1325 Rel-19 Clarify the application errors included in Re-AuthenticationNotification response	ZTE	WI HN_Auth CAT A
4141	LS out Reply LS on clarification on home network triggered re-authentication	ZTE	Moved to 4.2
Breakout	4162	CR 29.503 1329 Rel-18 Update on the failure cause	Huawei	WI HN_Auth CAT F
Breakout	4163	CR 29.503 1330 Rel-19 Update on the failure cause	Huawei	WI HN_Auth CAT A
18.76	CT aspects of Mission Critical ad hoc group Communications [MC_AHGC]
18.77	NRF API enhancements to avoid signalling and storing of redundant data [NRFe]
18.78	Network Slice Capability Exposure for Application Layer Enablement [NSCALE]
18.79	Application enablement aspects for subscriber-aware northbound API access [SNAAPP]
18.80	IVAS_Codec [IVAS_Codec]
18.81	Update of conformance test specifications to Rel-18 [UEConTest_R18]
18.82	Test method of GBA_U Based APIs [TEST_GBA_U_APIs]
18.83	UE conformance test for NB-IoT/eMTC Non-Terrestrial Networks in EPS [IoT_SAT_UEConTest]
18.84	Any other Rel-18 Work item or Study item
19	Release 19
19.1	Rel-19 Exception sheets or other Rel-19 work planning
4010	Work Plan Work Plan	CT4 Chair
19.2	New WIDs for Rel-19
4210	WID new Rel-19 New WID on CT aspects of Extended Reality and Media service (XRM) Phase 2	Nokia	Moved to 19.2.2
4318	WID new Rel-19 New WID on CT aspects of energy efficiency and energy saving	Samsung	Moved to 19.2.1
19.2.1	CT4 Led WIDs
Plenary	4078	WID new Rel-19 New WID on IMS Disaster Prevention and Restoration Enhancement	China Telecom Corporation Ltd.
Plenary	4155	WID new Rel-19 New WID on CT Aspects on Subscription control for reference time distribution in EPS	Qualcomm Incorporated
Plenary	4245	WID new Rel-19 New WID on CT aspects of 5G NR Femto	NTT DOCOMO
Plenary	4312	WID new Rel-19 New WID on Reducing Information Exposure over SBI	Samsung Electronics Iberia SA
Plenary	4318	WID new Rel-19 New WID on CT aspects of energy efficiency and energy saving	Samsung
19.2.2	CT4 Supported WIDs
Plenary	4210	WID new Rel-19 New WID on CT aspects of Extended Reality and Media service (XRM) Phase 2	Nokia
19.3	Revised WIDs for Rel-19
4197	WID revised Rel-19 Revised WID on CT Aspects of Phase 3 for UAS, UAV and UAM	LG Electronics, Ericsson	Moved to 19.3.2
19.3.1	CT4 Led WIDs
4245	WID new Rel-19 New WID on CT aspects of 5G NR Femto	NTT DOCOMO	Moved to 19.2.1
19.3.2	CT4 Supported WIDs
Plenary	4197	WID revised Rel-19 Revised WID on CT Aspects of Phase 3 for UAS, UAV and UAM	LG Electronics, Ericsson
Plenary	4271	Work Plan Rel-19 work plan for UAS_Ph3	LG Electronics
Plenary	4249	WID revised Rel-19 Revised WID on CT aspects of ProSe support in NPN	China Telecomunication Corp.
Plenary	4287	WID revised Rel-19 Revised WID on CT aspects of Enhancing Parameter Provisioning with static UE IP address and UP security policy	Ericsson
19.4	TEI19 [TEI19]
Breakout	4039	CR 29.503 1309 Rel-19 Wrong CR implementation	Nokia, MCC	WI TEI19 CAT F
Breakout	4053	CR 29.503 1316 Rel-19 Missing description	Nokia	WI TEI19 CAT F
Breakout	4054	CR 29.503 1317 Rel-19 Additional PGW IP Address	Nokia	WI TEI19 CAT F
Main	4060	CR 23.007 0399 Rel-19 Including Pending PDN Connection Restoration Indication during EPS to 5GS mobility	Ericsson, Nokia	WI RPCPSET, TEI19 CAT B
Main	4061	CR 29.274 2112 Rel-19 Including Pending PDN Connection Restoration Indication during EPS to 5GS mobility	Ericsson, Nokia	WI RPCPSET, TEI19 CAT B
Main	4062	CR 29.502 0800 Rel-19 PGW Change Indication for the restoration of a PDN connection during EPS to 5GS mobility	Ericsson, Nokia	WI RPCPSET, TEI19 CAT B
Main	4068	CR 29.502 0801 Rel-19 Populate the supportedPfcpFeatures and UPF events of ULCL/BP and local PSA	Ericsson	WI TEI19, UPEAS CAT B
Main	4069	CR 29.244 0869 Rel-19 Clarification on the Downlink Data Notification Delay for 5GC	Ericsson	WI TEI19 CAT F
Main	4070	CR 29.518 1120 Rel-19 The maxWaitingTime in the N1N2MsgTxFrFailureNotification	Ericsson	WI TEI19 CAT F
Plenary	4081	CR 29.573 0215 Rel-19 Applicative error originated by RI via N32-f	Huawei	WI TEI19 CAT F
Main	4082	CR 29.564 0107 Rel-19 Corrections on dlPeakThroughput and throughputStatisticMeasurements attributes	Huawei	WI TEI19 CAT F
Main	4083	CR 29.531 0221 Rel-19 Correction on NSAG Info List attribute	Huawei	WI TEI19 CAT F
Main	4084	CR 29.502 0803 Rel-19 Correction on enumerations	Huawei	WI TEI19 CAT F
Main	4085	CR 29.244 0870 Rel-19 Correction on the length of IEs	Huawei	WI TEI19 CAT F
Plenary	4086	CR 29.274 2113 Rel-19 Support of Time Reference Information Distribution Indication	Huawei	WI TEI19, TEI19_TIME_SUB_EPS CAT B
Main	4090	CR 29.564 0108 Rel-19 Rejection if UPF event Exposure is not supported for non-IP PDU session	Huawei	WI TEI19, UPEAS CAT F
Main	4121	CR 29.244 0874 Rel-19 Network Instance Assigned by UP Function in Full-Mesh Scenario	ZTE	WI TEI19, CUPS CAT B
Plenary	4127	CR 29.571 0584 Rel-19 Common Data Type for 5G Femto Information	ZTE	WI 5G_Femto CAT B
Plenary	4128	CR 29.503 1322 Rel-19 Provision of 5G Femto Information to UDM	ZTE	WI 5G_Femto CAT B
Plenary	4298	CR 29.503 1347 Rel-19 5G Femto CAG information provisioning	Samsung Electronics Iberia SA	WI TEI19, 5G_Femto CAT B
Breakout	4131	CR 29.579 0022 Rel-19 Add STRUCTURED TYPES in TS 29.579	China Telecom Corporation Ltd.	WI TEI19 CAT F
Breakout	4167	CR 29.503 1332 Rel-19 Add missing description for Nudm_PP	Huawei	WI TEI19 CAT F
Breakout	4168	CR 29.503 1333 Rel-19 Corrections on GpsiInfo	Huawei	WI TEI19 CAT F
Breakout	4169	CR 29.503 1334 Rel-19 Corrections on the DefaultDnnIndicator	Huawei	WI TEI19 CAT F
Breakout	4170	CR 29.503 1335 Rel-19 Miscellaneous corrections	Huawei	WI TEI19 CAT F
Breakout	4171	CR 29.559 0046 Rel-19 Add missing description	Huawei	WI TEI19 CAT F
Plenary	4174	CR 29.272 0862 Rel-19 Add Time Reference Information Distribution Indication	Huawei	WI TEI19_TIME_SUB_EPS CAT B
Breakout	4178	CR 29.503 1339 Rel-19 Misplaced paragraph	Nokia, CEWiT	WI TEI19 CAT F
Main	4196	CR 29.244 0878 Rel-19 Wrong reference to the Domain Name Protocol field	Ericsson	WI TEI19 CAT F
Main	4198	CR 29.502 0809 Rel-19 PDU session with a V/I SMF for an eDRX UE	Ericsson	WI TEI19 CAT F
Plenary	4211	CR 23.527 0086 Rel-19 Clarification to the Multicast MBS session restoration procedure for NG-RAN restart	Nokia	WI TEI19 CAT F
Plenary	4212	CR 23.527 0082 Rel-19 Multicast MBS session restoration procedure for N3mb path failure	Nokia, Huawei	WI TEI19, 5MBS_Ph2 CAT B
Plenary	4213	CR 29.273 0552 Rel-19 Notes on ePDG treating the UE with priority	Nokia	WI TEI19, MPS_WLAN CAT F
Main	4214	CR 29.244 0880 Rel-19 Clarification on End of Data Burst Indication	Nokia	WI TEI19, XRM CAT F
Plenary	4241	CR 29.518 1127 Rel-19 Definition of AMF event filter for UAV deviation from the expected trajectory	Huawei	WI TEI19, UAS_Ph3 CAT B Overlapping with 4269
Plenary	4269	CR 29.518 1135 Rel-19 New AMF Event of Trajectory Tracking for USS Change Over	Ericsson, LG Electronics	WI UAS_Ph3 CAT B
Main	4248	CR 29.502 0811 Rel-19 Notify of UE being reachable for DL signaling	Ericsson	WI TEI19 CAT F
Breakout	4263	CR 29.503 1344 Rel-19 Correction on Application Errors	Ericsson	WI TEI19 CAT F
Main	4264	CR 29.518 1133 Rel-19 PWS N2 Subscription per CBCF	Ericsson, one2many	WI TEI19 CAT F
4271	Work Plan Rel-19 work plan for UAS_Ph3	LG Electronics	Moved to 19.3.2
Main	4273	CR 29.518 1136 Rel-19 Correction of data type name	Huawei	WI TEI19 CAT F
Plenary	4274	CR 29.510 1080 Rel-19 Clarification on missing abbreviations	Huawei	WI TEI19 CAT F
Main	4275	CR 29.518 1137 Rel-19 29.518 Adding missing abbreviation	Huawei	WI TEI19 CAT F
Plenary	4276	CR 29.500 0455 Rel-19 Clarification on missing abbreviations	Huawei	WI TEI19 CAT F
Plenary	4277	CR 29.501 0166 Rel-19 Clarification on missing abbreviations	Huawei	WI TEI19 CAT F
Main	4278	CR 29.502 0815 Rel-19 Clarification on missing abbreviations	Huawei	WI TEI19 CAT F
Plenary	4288	CR 23.003 0704 Rel-19 Correction to wrong references	Ericsson, MCC	WI TEI19 CAT F
Plenary	4293	CR 29.510 1081 Rel-19 Clarification to the Source NF instance ID description in Access Token Claims	Nokia	WI TEI19, eNA_Ph3 CAT F
19.5	CT Aspects on Minimize the Number of Policy Associations [TEI19_MINPA]
19.6	CT aspects of Enhancing Parameter Provisioning with static UE IP address and UP security policy [TEI19_IP_SP_EXP]
Plenary	4050	CR 29.503 1313 Rel-19 Enhancing parameter provisioning with static UE IP address and 5G VN group data with UP security policy for the 5G VN group	Nokia	WI TEI19_IP_SP_EXP CAT B Overlapping with 4172, 4173, 4200
Plenary	4172	CR 29.503 1336 Rel-19 Add User Plane Security Policy	Huawei	WI TEI19_IP_SP_EXP CAT B
Plenary	4173	CR 29.503 1337 Rel-19 Support of Static IP address assignment parameters	Huawei	WI TEI19_IP_SP_EXP CAT B
Plenary	4200	CR 29.503 1340 Rel-19 Enhancing Parameter Provisioning with Static IP address and Security Policy	Ericsson	WI TEI19_IP_SP_EXP CAT B
19.7	CT aspects of Providing per-subscriber VLAN instructions from UDM and DN-AAA [TEI19_VLANSUB]
19.8	CT Aspects of Application Layer Support for Uncrewed Aerial Systems (UAS), Phase 3[UASAPP_Ph3]
19.9	CT aspects for Enabling Edge Applications Phase 3[EDGEAPP_Ph3]
19.10	Service Based Interface Protocol Improvements Release 19 [SBIProtoc19]
Plenary	4043	CR 29.510 1045 Rel-19 Nhss_Parameter Provisioning	Nokia	WI SBIProtoc19 CAT B
Breakout	4044	CR 23.632 0048 Rel-19 Nhss_Parameter Provisioning	Nokia	WI SBIProtoc19 CAT B
Breakout	4045	CR 29.563 0096 Rel-19 Removal of Editor's Note	Nokia	WI SBIProtoc19 CAT F
Plenary	4047	CR 29.510 1046 Rel-19 Reducing Information Exposure using Resource Content Filters	Nokia	WI SBIProtoc19 CAT B Should use the new WI as proposed in 4312
Breakout	4048	CR 29.598 0083 Rel-19 Complex Types	Nokia	WI SBIProtoc19 CAT F
Breakout	4049	CR 29.598 0084 Rel-19 Timer search with filters using meta tags	Nokia	WI SBIProtoc19 CAT F
Breakout	4063	CR 29.503 1319 Rel-19 Shared Monitoring Suspension	Nokia, Ericsson	WI SBIProtoc19 CAT B
Plenary	4071	CR 29.500 0448 Rel-19 Clarification on the Sender Timestamp and the Max-Rsp-Time	Ericsson	WI SBIProtoc19 CAT F
Main	4072	CR 29.502 0802 Rel-19 Clarification on the Sender and Origination Timestamp and the Max-Rsp-Time	Ericsson	WI SBIProtoc19 CAT F
4080	CR 29.501 0163 Rel-19 OpenAPI definition of boolean with false value prohibited	Huawei, China Mobile	revised to C4-244250	Revision of C4-244250 WI SBIProtoc19 CAT F
Plenary	4122	CR 29.510 1052 Rel-19 Shutdown Time	ZTE	WI SBIProtoc19 CAT B
Plenary	4144	CR 29.510 1056 Rel-19 Correction of 3xx response	ZTE	WI SBIProtoc19 CAT F
Breakout	4164	CR 29.503 1331 Rel-19 Add new EventType	Huawei	WI SBIProtoc19 CAT B
Main	4215	CR 29.518 1105 Rel-19 AMF Set level event exposure Bulk Subscriptions	Nokia, Ericsson	WI SBIProtoc19 CAT B
Main	4216	CR 29.564 0114 Rel-19 Subscription termination upon PFCP session release	Nokia	WI SBIProtoc19 CAT F
Breakout	4247	CR 29.503 1341 Rel-19 Support for AF Specific Identifier Selection in Multiple Identifiers Translation in UDM	CEWiT	WI SBIProtoc19 CAT B
Plenary	4250	CR 29.501 0163 Rel-19 OpenAPI definition of boolean with false value prohibited	Huawei, China Mobile	WI SBIProtoc19 CAT F
4252	CR 29.510 1075 Rel-19 Canary test procedure clarifications	Ericsson	Withdrawn	WI SBIProtoc19 CAT F
Main	4259	CR 29.502 0812 Rel-19 Clarify Charging ID in PDU Session Create Operation	Ericsson, AT&T	WI SBIProtoc19 CAT F
Main	4260	CR 29.502 0813 Rel-19 SMF Set Information During SM Context Creation	Ericsson, Nokia	WI SBIProtoc19 CAT B
Main	4270	CR 29.502 0814 Rel-19 Preliminary Service Support	Ericsson	WI SBIProtoc19 CAT B
Breakout	4272	CR 29.503 1345 Rel-19 Validity time in authorization data for NIDD authorization	Ericsson	WI SBIProtoc19 CAT F
Breakout	4279	CR 29.505 0523 Rel-19 Validity time in authorization data for service specific and NIDD authorization	Ericsson	WI SBIProtoc19 CAT F
Plenary	4280	CR 29.501 0167 Rel-19 Editorial Corrections	Ericsson	WI SBIProtoc19 CAT F
Breakout	4283	CR 29.503 1346 Rel-19 Implicit Unsubscribe for Shared Data	Ericsson	WI SBIProtoc19 CAT F
Plenary	4299	CR 29.510 1082 Rel-19 Canary test procedure clarifications	Ericsson	WI SBIProtoc19 CAT F
Plenary	4306	CR 29.256 0029 Rel-19 Correct the notification URI	CATT	WI SBIProtoc19 CAT F
19.11	Subscriber Data Migration [SUBDMIG]
Plenary	4123	CR 23.527 0085 Rel-19 Redirection due to Subscriber Data Migration	ZTE	WI SUBDMIG CAT B
4124	CR 29.510 1053 Rel-19 Redirection due to Subscriber Data Migration	ZTE	withdrawn	WI SUBDMIG CAT B
Plenary	4125	CR 29.571 0583 Rel-19 Redirection due to Subscriber Data Migration	ZTE	WI SUBDMIG CAT B
Plenary	4129	CR 29.500 0451 Rel-19 Redirection due to Subscriber Data Migration	ZTE	WI SUBDMIG CAT B
Plenary	4286	CR 23.527 0088 Rel-19 Immediate restoration for individual UE restoration requests	Ericsson	WI SUBDMIG CAT C
19.12	Rel-19 Enhancements of 3GPP Northbound and Application Layer Interfaces and APIs[NBI19]
19.13	IMS Stage-3 IETF Protocol Alignment [IMSProtoc19]
19.14	Protocol enhancements for Mission Critical Services [MCProtoc19]
19.15	Enhancement of controlling RAT utilization [ECRATU]
Plenary	4055	CR 29.503 1318 Rel-19 RAT restriction by serving PLMN policy	Nokia	WI ECRATU CAT B Overlapping with 4107
Plenary	4107	CR 29.503 1321 Rel-19 RAT utilization control information in 5GS	vivo	WI ECRATU CAT B
Plenary	4106	CR 29.272 0861 Rel-19 RAT utilization control information in EPS	vivo	WI ECRATU CAT B
19.16	Enhanced Mission Critical Location Management [enhMCLoc]
19.17	Stage-3 5GS NAS protocol development 19 general aspects [5GProtoc19]
19.18	Stage-3 5GS NAS protocol development 19 non 3GPP aspects [5GProtoc19-non3GPP]
19.19	Stage-3 SAE Protocol Development general [SAES19]
19.20	Stage3 SAE Protocol Development non 3GPP [SAES19-non3GPP]
19.21	CT Aspects of Indirect Network Sharing [TEI19_NetShare]
Plenary	4076	CR 29.510 1049 Rel-19 Support of Indirect Network Sharing	China Unicom, ZTE, Huawei	WI TEI19_NetShare CAT B Overlapping with 4265
Plenary	4265	CR 29.510 1079 Rel-19 H-SMF Discovery for Indirect Network Sharing	Ericsson	WI TEI19_NetShare CAT B
Plenary	4087	CR 29.502 0804 Rel-19 Support of Indirect Network Sharing	Huawei, China Unicom	WI TEI19_NetShare CAT B
Plenary	4088	CR 29.531 0222 Rel-19 Support of Indirect Network Sharing	Huawei, China Unicom	WI TEI19_NetShare CAT B Overlapping with 4267, 4294
Plenary	4267	CR 29.531 0224 Rel-19 S-NSSAI Mapping for Indirect Network Sharing	Ericsson	WI TEI19_NetShare CAT B
Plenary	4294	CR 29.531 0225 Rel-19 Retrieve the mapping of the hosting operator S-NSSAIs during the Registration procedure	Nokia	WI TEI19_NetShare CAT B
Plenary	4149	CR 29.500 0452 Rel-19 Clarification on SBI Header Setting	ZTE	WI TEI19_NetShare CAT B Overlapping with 4295
Plenary	4295	CR 29.500 0456 Rel-19 Clarification on the Originating Network ID header for Indirect Network Sharing	Nokia	WI TEI19_NetShare CAT B
Plenary	4150	CR 29.509 0228 Rel-19 Clarify the PLMN ID used in Serving Network Name	ZTE, China Unicom	WI TEI19_NetShare CAT B Overlapping with 4297
Plenary	4297	CR 29.509 0229 Rel-19 Clarification on Serving Network Name for Indirect Network Sharing	Nokia	WI TEI19_NetShare CAT B
Plenary	4266	CR 29.531 0223 Rel-19 Resolve EN for Network Slice Selection in Participating Operator Network	Ericsson	WI TEI19_NetShare CAT B
Plenary	4296	CR 29.502 0816 Rel-19 Clarification to PDU session establishment with Indirect Network Sharing	Nokia	WI TEI19_NetShare CAT B
19.22	CT aspects of railways specific enhancements to mission critical services [FRMCS_Ph5]
19.23	CT aspects of Architecture support of roaming value-added services [TEI19_RVAS]
Plenary	4126	CR 29.510 1054 Rel-19 AUSF/UDM Discovery in Target PLMN	ZTE	WI TEI19_RVAS CAT B
19.24	CT Aspects of On-demand broadcast of GNSS assistance enhancement [TEI19_OBGAD]
Main	4109	CR 29.518 1121 Rel-19 Support of on-demond broadcast of GNSS assistance data	China Mobile	WI TEI19_OBGAD CAT B Overlapping with 4242, 4268
Main	4242	CR 29.518 1128 Rel-19 Updating AMF event filter to support on-demand broadcast of GNSS assistance data	Huawei	WI TEI19_OBGAD CAT B
Main	4268	CR 29.518 1134 Rel-19 Number of UEs in Area Filter for LCS Broadcast Subscribed UE	Ericsson	WI TEI19_OBGAD CAT B
19.25	CT aspects of NF discovery and selection by target PLMN [TEI19_NFsel_by_tPLMN]
Plenary	4217	CR 29.500 0453 Rel-19 Routing requests with Target-apiRoot and w/o Scp-apiRoot in target PLMN	Nokia	WI TEI19_NFsel_by_tPLMN CAT B
Plenary	4218	CR 29.500 0454 Rel-19 Routing requests via alternative SCPs in target PLMN	Nokia	WI TEI19_NFsel_by_tPLMN CAT B
Plenary	4219	CR 29.510 1074 Rel-19 Routing requests via alternative SCPs in target PLMN	Nokia	WI TEI19_NFsel_by_tPLMN CAT B
Plenary	4220	CR 23.527 0087 Rel-19 NF reselection by SCP of target PLMN	Nokia	WI TEI19_NFsel_by_tPLMN CAT B
19.26	CT aspects of enhancement of support for Edge Computing in 5G Core network - Phase 3 [eEDGE_5GC_Ph3]
Main	4089	CR 29.556 0044 Rel-19 I-SMF based Local Offloading Management	Huawei	WI eEDGE_5GC_Ph3 CAT B Overlapping with 4221
Main	4221	CR 29.556 0045 Rel-19 New I-SMF consumer for I-SMF based Local Offloading Management	Nokia	WI eEDGE_5GC_Ph3 CAT B
Main	4181	CR 29.571 0590 Rel-19 Define the common data type for Local Offloading Policy Information	Huawei	WI eEDGE_5GC_Ph3 CAT B Overlapping with 4222
Main	4222	CR 29.571 0593 Rel-19 Local Offloading Information	Nokia	WI eEDGE_5GC_Ph3 CAT B
Main	4223	CR 29.502 0810 Rel-19 N16a enhancements for I-SMF based Local Offloading Management	Nokia	WI eEDGE_5GC_Ph3 CAT B
19.27	MPS for IMS Messaging and SMS services [MPS4msg]
19.28	Identifying non-3GPP Devices Connecting behind a UE or 5G-RG [UIA_ARC]
19.29	CT aspects on Spending Limits for UE Policies in Roaming scenario [TEI19_SLUPiR]
19.30	CT aspects of QoS monitoring enhancement [TEI19_QME]
19.31	CT Aspects of Phase3 for UAS, UAV and UAM [UAS_Ph3]
19.32	CT aspects of enhanced application layer support for location services [eLSAPP]
19.33	CT aspects of SEAL data delivery enabler for vertical applications Phase 2 [SEALDD_Ph2]
19.34	CT aspects of integration of satellite components in the 5G architecture Phase 3 [5GSAT_Ph3_ARCH]
19.35	CT aspects of ProSe support in NPN [TEI19_ProSe_NPN]
4249	WID revised Rel-19 Revised WID on CT aspects of ProSe support in NPN	China Telecomunication Corp.	Moved to 19.3.2
Plenary	4307	CR 23.003 0705 Rel-19 Update ProSe App Code format to support 5G ProSe in NPNs	CATT	WI TEI19_ProSe_NPN CAT B
19.36	CT aspects of Proximity-based Services in 5GS Phase 3 [5G_ProSe_Ph3]
Plenary	4160	CR 29.503 1328 Rel-19 Support of multi hop U2N and U2U	Huawei	WI 5G_ProSe_Ph3 CAT B Overlapping with 4256, 4301
Plenary	4256	CR 29.503 1342 Rel-19 Subscription Data for multi hop U2N and U2U	Ericsson	WI 5G_ProSe_Ph3 CAT B
Plenary	4301	CR 29.503 1348 Rel-19 Support 5G ProSe multi-hop relay services	CATT	WI 5G_ProSe_Ph3 CAT B
Plenary	4161	CR 29.571 0587 Rel-19 Support of multi hop U2N and U2U	Huawei	WI 5G_ProSe_Ph3 CAT B Overlapping with 4257, 4303
Plenary	4257	CR 29.571 0594 Rel-19 Subscription Data for multi hop U2N and U2U	Ericsson	WI 5G_ProSe_Ph3 CAT B
Plenary	4303	CR 29.571 0595 Rel-19 Support 5G ProSe multi-hop relay services	CATT	WI 5G_ProSe_Ph3 CAT B
Plenary	4240	CR 29.518 1126 Rel-19 Support for Multi-hop 5G ProSe Layer-3	Huawei	WI 5G_ProSe_Ph3 CAT B Overlapping with 4302
Plenary	4302	CR 29.518 1138 Rel-19 Support 5G ProSe multi-hop relay services	CATT	WI 5G_ProSe_Ph3 CAT B
Plenary	4317	CR 29.504 0291 Rel-19 Support 5G ProSe Multi-hop UE-to-Network Relay and Multi-hop UE-to-UE Relay	Huawei, CATT	WI 5G_ProSe_Ph3 CAT B
19.37	CT aspects of UPF enhancement for Exposure And SBA Phase 2 [UPEAS_Ph2]
Plenary	4064	CR 29.244 0868 Rel-19 Support of NAT exposure feature and Operator Configurable UPF capability	Ericsson	WI UPEAS_Ph2 CAT B Overlapping with 4091, 4132, 4133, 4154
Plenary	4091	CR 29.244 0871 Rel-19 Operator configurable UPF capability	Huawei	WI UPEAS_Ph2 CAT B
Plenary	4132	CR 29.244 0875 Rel-19 Support operator configurable parameter in N4	China Mobile	WI UPEAS_Ph2 CAT B
Plenary	4133	CR 29.244 0876 Rel-19 Supported functionality of NAT information exposure	China Mobile	WI UPEAS_Ph2 CAT B
Plenary	4154	CR 29.244 0877 Rel-19 Indicate the UPF capabilities on N4 interface	ZTE	WI UPEAS_Ph2 CAT B Overlapping also with 4246
Plenary	4246	CR 29.244 0881 Rel-19 UPF Packet Inspection functionalities	Ericsson	WI UPEAS_Ph2 CAT B
Plenary	4065	CR 29.571 0582 Rel-19 Operator Configurable UPF Capability	Ericsson	WI UPEAS_Ph2 CAT B Overlapping with 4136, 4137
Plenary	4136	CR 29.571 0585 Rel-19 Support of optional extended UPF functionalities	Nokia	WI UPEAS_Ph2 CAT B
Plenary	4137	CR 29.571 0586 Rel-19 Support operator configurable parameter in common data	China Mobile	WI UPEAS_Ph2 CAT B
Plenary	4066	CR 29.510 1047 Rel-19 Packet Inspection Functionality and Operator Configurable UPF Capability	Ericsson	WI UPEAS_Ph2 CAT B Overlapping with 4134, 4152, 4179, 4180, 4319
Plenary	4134	CR 29.510 1055 Rel-19 Support operator configurable parameter in NRF	China Mobile	WI UPEAS_Ph2 CAT B
Plenary	4152	CR 29.510 1061 Rel-19 Indicate the UPF capabilities in NRF	ZTE	WI UPEAS_Ph2 CAT B
Plenary	4179	CR 29.510 1063 Rel-19 Discovery of UPF based on new capabilities	Huawei	WI UPEAS_Ph2 CAT B
Plenary	4180	CR 29.510 1064 Rel-19 Discovery of UPF based on supported operator configurable UPF capability	Huawei	WI UPEAS_Ph2 CAT B
Plenary	4319	CR 29.510 1086 Rel-19 Adding new UPF capabilities	IPLOOK	WI UPEAS_Ph2 CAT B
Plenary	4067	CR 29.503 1320 Rel-19 Required and/or Preferred UPF functionalities in subscription data	Ericsson	WI UPEAS_Ph2 CAT B Overlapping with 4135, 4175
Plenary	4135	CR 29.503 1323 Rel-19 Support of optional extended UPF functionalities	Nokia	WI UPEAS_Ph2 CAT B
Plenary	4175	CR 29.503 1338 Rel-19 Support of optional extended UPF functionalities	Huawei	WI UPEAS_Ph2 CAT B
Plenary	4073	CR 29.510 1048 Rel-19 Discovering the serving UPF for a PDU session using the UE IP address	Ericsson	WI UPEAS_Ph2 CAT B Overlapping with 4153
Plenary	4153	CR 29.510 1062 Rel-19 Clarify ipv4AddressRanges used for UPF discovery by NEF	ZTE	WI UPEAS_Ph2 CAT B
Plenary	4092	CR 29.564 0109 Rel-19 Public UE IP address exposure	Huawei	WI UPEAS_Ph2 CAT B Overlapping with 4191, 4225
Plenary	4191	CR 29.564 0112 Rel-19 Supporting UE NAT Mapping Event Exposure	Ericsson	WI UPEAS_Ph2 CAT B
Plenary	4225	CR 29.564 0116 Rel-19 New UPF event to get the NATed UE public IP address and port number	Nokia	WI UPEAS_Ph2 CAT B
Plenary	4093	CR 29.564 0110 Rel-19 Supporting UPF event exposure subscription directly using UE’s IP address	Huawei	WI UPEAS_Ph2 CAT B Overlapping with 4192, 4224
Plenary	4192	CR 29.564 0113 Rel-19 Supporting direct subscription of UPF event exposure using UE’s IP address	Ericsson	WI UPEAS_Ph2 CAT B
Plenary	4224	CR 29.564 0115 Rel-19 Direct subscription to UPF event exposure using a UE IP address	Nokia, Huawei	WI UPEAS_Ph2 CAT B
Plenary	4094	CR 29.564 0111 Rel-19 UPF event exposure during UPF relocation	Huawei	WI UPEAS_Ph2 CAT B
Plenary	4151	Work Plan Rel-19 Work Plan for UPEAS_Ph2	ZTE
19.38	Rel-19 Enhancements of Network Automation Enablers [eNetAE19]
19.39	CT aspects of Core Network Enhanced Support for Artificial Intelligence (AI) and Machine Learning (ML) [AIML_CN]
Plenary	4077	discussion Rel-19 Work plan for the CT part of AIML_CN	vivo
Plenary	4258	CR 29.503 1343 Rel-19 LMF as Consumer of User Consent Subscription Data	Ericsson	WI AIML_CN CAT B
19.40	CT aspects of Next Generation Real time Communication services [NG_RTC_Ph2]
Breakout	4108	CR 29.175 0019 Rel-19 Supporting of network initiated IMS Data Channel	China Mobile	WI NG_RTC_Ph2 CAT B
Breakout	4233	CR 29.175 0021 Rel-19 Definition of Nimsas_ImsSessionManagement Service	Huawei	WI NG_RTC_Ph2 CAT B
Breakout	4234	CR 29.175 0022 Rel-19 Support of interworking with MTSI client	Huawei	WI NG_RTC_Ph2 CAT B
Breakout	4235	CR 29.176 0021 Rel-19 Support of interworking with MTSI client	Huawei	WI NG_RTC_Ph2 CAT B
Breakout	4236	CR 29.364 0054 Rel-19 Support of Standalone DC	Huawei	WI NG_RTC_Ph2 CAT B
19.41	CT aspects of application enablement for AIML services [AIML_App]
19.42	CT aspects for application enablement for mobile metaverse services [Metaverse_App]
19.43	CT Aspects of Vehicle Mounted Relays Phase 2 [VMR_Ph2]
Plenary	4156	Work Plan Rel-19 Work plan for VMR_Ph2	Qualcomm Incorporated
Breakout	4157	CR 29.572 0288 Rel-19 Support of location service in MWAB	Qualcomm Incorporated	WI VMR_Ph2 CAT B Overlapping with 4177, 4308
Breakout	4177	CR 29.572 0291 Rel-19 Add MWAB indication	Huawei	WI VMR_Ph2 CAT B
Breakout	4308	CR 29.572 0294 Rel-19 Support for MWAB involved positioning	CATT	WI VMR_Ph2 CAT B
Breakout	4176	CR 29.515 0187 Rel-19 Add MWAB indication	Huawei	WI VMR_Ph2 CAT B Overlapping with 4199, 4289
Breakout	4199	CR 29.515 0188 Rel-19 Support of location service in MWAB	Qualcomm Incorporated	WI VMR_Ph2 CAT B
Breakout	4289	CR 29.515 0189 Rel-19 Adding MWAB positioning indication	Nokia	WI VMR_Ph2 CAT B
Plenary	4186	CR 29.510 1069 Rel-19 Discovery of LMF that supports LCS when MWAB is involved	Huawei	WI VMR_Ph2 CAT B Overlapping with 4311
Plenary	4311	CR 29.510 1085 Rel-19 LMF supports LCS when MWAB is involved	Nokia	WI VMR_Ph2 CAT B
19.44	Alignment of eCall over IMS with CEN [eCallCEN]
19.45	CT aspects of Multi-Access (ATSSS_Ph4) [MASSS]
20	Study Items
20.1	Study on Protocol for AI Data Collection from UPF [FS_PAIDC-UPF]
Plenary	4079	pCR 29.889 Rel-19 Pseudo-CR on the Solution X to the Key Issue 1- efficient alternative protocol on Data collection	Huawei, China Mobile
Plenary	4130	pCR 29.889 Rel-19 solution to key_issue#1 Optimized UPF data collection based on existing mechanisms	China Mobile
Plenary	4226	pCR 29.889 Rel-19 Pseudo-CR on Description of existing UPF data collection mechanisms	Nokia
Plenary	4227	pCR 29.889 Rel-19 Pseudo-CR on Use cases and protocol requirements for intensive data collection from UPF	Nokia
Plenary	4228	pCR 29.889 Rel-19 Pseudo-CR on Addressing the Editor's notes of Solution #2	Nokia
Plenary	4229	pCR 29.889 Rel-19 Pseudo-CR on Provisioning of user and/or PDU session’s markers	Nokia
Plenary	4230	pCR 29.889 Rel-19 Pseudo-CR on Reduced Report Instructions Information	Nokia
TR 29.889v0.2.0	China Mobile
20.2	Study on Reducing Information Exposure over SBI [FS_RedInfExp_SBI]
Plenary	4046	pCR 29.857 Rel-18 Removal of Editor's Notes	Nokia
TR 29.857v1.3.0	Samsung
20.3	Study on IMS Disaster Prevention and Restoration Enhancement [FS_IMS_RES]
Plenary	4138	pCR 29.866 Rel-18 Pseudo-CR on updating the evaluation and conclusion of KI #3	ZTE, Ericsson
Plenary	4237	pCR 29.866 Rel-18 Update KI#3 evaluation and add KI#3 conclusion	Huawei, ZTE, Ericsson
Plenary	4284	pCR 29.866 Rel-18 Pseudo-CR on KI#4 Solution #10	Ericsson
Plenary	4285	pCR 29.866 Rel-18 Pseudo-CR on evaluation KI#4	Ericsson
TR 29.866v1.2.0	China Telecom
21	Any other business
22	Future meetings
23	Close of Meeting