3GPP TSG-CT WG4 Meeting #132	C4-255006

Dallas, US; 17th – 21st November 2025

Source:	Chairman, TSG-CT WG4

Title:	Proposed allocation of documents to agenda items for CT4#132, 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-25#	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	Consensus principle reminder
The attention of the delegates to the meeting is drawn to the fact that 3GPP endeavours to reach consensus on all decisions and therefore depends on a cooperative spirit of the Individual Members. In particular, Individual Members are encouraged to seek a consensus-based solution and only to sustain objections as a very last resort, and where absolutely necessary and well justified. The leadership will conduct the present meeting in a manner whereby informal methods of reaching consensus are encouraged, whilst ensuring that well justified concerns are taken into account.
1.5	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-255002
2	Allocation of Documents to Agenda Items
5001	agenda Draft Agenda	CT4 Chair
5002	other Meeting guidelines for CT4 Working Group meeting	CT4 Chair
5003	agenda Detailed agenda & time plan for CT4 meeting: status at document deadline	CT4 Chair
5004	agenda Detailed agenda & time plan for CT4 meeting: status on eve of meeting	CT4 Chair
5005	agenda Proposed allocation of documents to agenda items for CT4 meeting: status at document deadline	CT4 Chair
5006	agenda Proposed allocation of documents to agenda items for CT4 meeting: status on eve of meeting	CT4 Chair
5007	agenda The allocation of documents to agenda items for CT4 meeting: status at the end of meeting	CT4 Chair
3	Reports
5008	report Previous TSG CT & SA Status Report	CT4 Chair	Withdrawn
5009	report Previous CT4 meeting report	MCC
4	Liaison statements
4.1	Incoming liaisons
Plenary	5028	LS in Rel-19 LS on UE parameters update header security	CT WG1	C1-253719 To: SA3 CC: CT4 Contact: Nokia Postponed from CT4#131 meeting: Ulrich commented that CT4 may be impacted depending on the further response from SA3 Related CRs in 5072, 5073. Reply LS needed if the CRs can be agreed
Plenary	5029	LS in Rel-19 LS to SA2 and CT4 on N6-Unmarked PDUs	SA4	S4-250738 To: SA2, CT4 CC: Contact: Nokia Postponed from CT4#131 meeting: Related CRs in C4-254113, C4-254114 and reply LS in C4-254115 were submitted. However due to lack of progress in stage2, they were postponed. Related CRs in 5057, 5058 Reply LS in 5059
Plenary	5030	LS in Rel-19 LS on AIoT Device Permanent ID Length	SA WG2	S2-2507793 To: RAN2 CC: RAN1, CT4, SA3 Contact: Huawei Postponed from CT4#131 meeting, to wait for further response from RAN2. RAN2’s reply is now available in 5033. Related CR in 5212 Reply LS in 5208
Plenary	5033	LS in Rel-19 Reply LS on AIoT Device Permanent ID Length	RAN WG2	R2-2507931 To: SA2 CC: RAN1, CT4, SA3 Contact: Huawei --- RAN2 thanks SA2 for the LS on AIoT Device Permanent ID Length. RAN2 discussed this issue with below conclusion: - From RAN2 point of view, extending the AIoT Device permanent ID to 256-bit and 496-bit is feasible, based on the calculation of existing fields size in this release. - However, the less overhead of paging message, the better coverage performance for paging message reception. Also, it is appreciated for SA2 to consider the pressure that larger payload imposes on the total 1000-bit paging message space. ---
Plenary	5031	LS in Rel-19 LS on support multiple LCS secured user plane connections	CT WG1	C1-256625 To: CT4 CC: SA2 Contact: Ericsson --- CT1 has discussed the SA2 requirement change on the user plane modification procedure (LS S2-2505873). To support multiple LCS-UPP connections in Rel19, CT1 discussed how to guarantee UE has a unique ID for LCS-UP connection association and agreed UE to use routing information associated to the LMF to identify the LCS secured user plane connection, see attached agreed CRs. CT1 kindly asks CT4 to take the above into consideration and consider updating their TS accordingly. ---
Plenary	5032	LS in Rel-19 Reply LS on input data from UE for Case 3b	RAN WG2	R2-2507922 To: SA2 CC: CT1, CT4 Contact: Samsung --- RAN2 thanks SA2 for the LS on input data from UE for Case 3b. RAN2 understands that “ground truth data” for Case 3b is the UE position estimated by the UE and the related data consists of UE position estimate uncertainty and timestamp. If so, this is already supported through UE-based positioning in LPP protocol (i.e., TS 37.355). Therefore, from RAN2 perspective, the “ground truth data” and its related data for Case 3b can be provided from UE to LMF by reusing LPP protocol (i.e., TS 37.355). --- Propose to note
Plenary	5034	LS in Rel-19 Reply to Reply LS on removal of support of PWS over satellite NG-RAN in Rel-17 and 18	SA WG2	S2-2509321 To: CT, RAN CC: CT1, SA, SA1, RAN3, RAN2, SA2, CT4, CT6 Contact: Samsung --- SA2 thanks CT for their LS in CP-252246/ S2-2508164. SA2 has agreed attached CRs to align with CT and RAN agreements. --- Propose to note
Plenary	5035	LS in Rel-19 Reply LS on Encoding of (S)RTP Multiplexed Media Identification Information	SA WG2	S2-2509336 To: CT1 CC: CT4 Contact: China Mobile --- SA2 thanks to CT1 for the Reply LS on Encoding of (S)RTP Multiplexed Media Identification Information. SA2 agreed to update the TS 23.501 for the (S)RTP Multiplexed Media Identification Information based on the change of RTCP SDES item and RTP SDES header extension to MID identification-tag and the RTP SDES header extension id field, in order to align with TS 24.501. For details, please see the S2-2509335 as attached. ---
Plenary	5036	LS in Rel-18 LS on Encoding DNAI mapping information	SA WG2	S2-2509558 To: CT3 CC: CT4 Contact: Nokia --- In TS 23.502, Nnef_DNAIMapping_Subscribe service is defined in clause 5.2.6.34.2 with the following input parameters: Inputs, Required: EAS address information i.e. IP address/IP address range or FQDN. Inputs, Optional: DNN, S-NSSAI, AF identifier, Event Reporting Information defined in Table 4.15.1-1 Based on step 2 in clause 6.8 of TS 23.548, when NEF receives subscription request, if the mapping information is stored in UDR, the NEF determines the DNN and/or the S-NSSAI if not received from the AF, potentially using the AF identifier. If the NEF has not yet received the DNAI mapping information for this DNN and/or S-NSSAI, NEF invokes the Nudr_DM_Subscribe service to subscribe to DNAI mapping information for this DNN and/or S-NSSAI. The DNAI mapping information is based on operator configuration and in TS 23.502, DNAI mapping information is defined as part of Exposure Data (see Table 5.2.12.1-2). In SA2#171, SA2 discussed and cannot reach a consensus on whether SA2 should, and if from what release, align with TS 29.519 clause 6.2.23 on defining DNAI mapping information as part of Application Data. SA2 would like CT3 to check about the above information and kindly asks CT3 to provide feedback. --- Propose to note
Plenary	5037	LS in Rel-19 Reply LS on Structure updates of AIoT Identifiers	SA WG2	S2-2509655 To: CT4 CC: SA3, RAN2, RAN3, CT1 Contact: CATT --- SA2 thanks CT4 on the LS on Structure updates of AIoT Identifiers (S2-2508179/C4-253575), and has agreed the attached CR0072 to TS 23.369 to align with CT4 specification. SA2 has also agreed the attached CR0106 to TS 23.369 on the definition of AIoT Identification Information, and kindly asks CT4 to complete the corresponding stage 3 work. --- Related CRs in 5124, 5184, 5190, 5242 Reply LSes in 5183, 5193, 5207
Plenary	5038	LS in Rel-19 Response LS on Exposure of "UE Reachable for DL Traffic" event for a UE in CM-CONNECTED state with RRC-Inactive	SA WG2	S2-2509755 To: CT4 CC: - Contact: Huawei --- SA2 thanks CT4 for their LS on Exposure of "UE Reachable for DL Traffic" event for a UE in CM-CONNECTED state with RRC-Inactive in S2-2508178/C4-253434. If the AMF has received N2 notification (i.e. N2 MT Communication Handling request message) indicating that the UE is transitioning to RRC_INACTIVE state and the determined eDRX values for RRC_INACTIVE, the AMF can determine when the UE is reachable based on the eDRX value. Therefore, when the AMF receives a subscription for the "UE Reachable for DL Traffic" event, the AMF reports the UE is reachable for DL traffic when the UE becomes reachable for paging. SA2 has agreed the attached CR to clarify this case. --- Related CR in 5235 Reply LS needed if the CR is agreed
Plenary	5039	LS in LS on Potential UDR in SNPN for AIoT	SA WG3	S3-253683 To: SA2 CC: CT4 Contact: Ericsson --- SA2 has specified in TS 23.369 that UDR may store AIoT data including AIoT device profile data and AF authorization data. However, SA3 has specified that device credentials can be stored only in the ADM. ---
Plenary	5040	LS in Rel-19 Reply LS to GSMA on CVD-2025-0101	SA WG3	S3-253799 To: GSMA CC: CT4 Contact: Huawei --- SA3 thanks GSMA CVD PoE for their LS on the potential vulnerabilities in the access control mechanism of the 5G core Network. SA3 would like to provide the following responses: • 3GPP TS 33.501: §13.4.1.1.2 could be more explicit about the exact conditions and content of the list of S-NSSAIs (producerSnssaiList) in the access token, including case 1b. [SA3] In TS 33.501, it has been specified in clause 13.4.1.1.2 (step 2 of case 1a) that the NRF only includes authorized slices/NSSAIs in the token claim. The NRF issues an access token without a list of NSSAIs in the claim only if all slices are authorized. Thus, an NF Consumer will not be able to use an access token to access services of unauthorized slices served by the NF Producer. For more clarity, NOTEs have been added in the clauses 13.4.1.1.2 and 13.4.1.2.2 as suggested. As far as the “1b case” is of concern, similar behavior is specified for the NRF in clause 13.4.1.1.2 (similar normative text to the first bullet point above). The NRF only includes authorized slices/NSSAIs in the token claim. In order to keep consistence for the case 1a and the case 1b, clauses 13.4.1.1.2 and 13.4.1.2.2 are thus updated. The details can be found in the CR attached. --- Related CR in C4-253085 has been agreed, LS in C4-253086 was sent to GSMA, which are inline with SA3’s reply, therefore: Propose to note
Plenary	5041	LS in Rel-19 Reply LS on Security related protocol-specific parameters for N6 delay measurement	SA WG3	S3-253807 To: CT3 CC: CT4, SA2 Contact: Nokia --- SA3 thanks CT3 for the question regarding the security related protocol-specific parameters for N6 delay measurement. SA3 would like to answer CT3 that the security related protocol-specific parameters listed in S3-251667 for the N6 delay measurement can be provisioned by AF (i.e., provision by the AF is one option or it can be achieved by an out of band mechanism), excluding the shared secret. SA3 also would like to clarify that the shared secret can still be exchanged between the SMF and UPF, hence, the answer provided to CT4 in S3-251667 is not impacted. ---
Plenary	5251	LS in Service APIs for MBS User Services	5G-MAG TECH	5G-MAG_LS_Service APIs for MBS User Services To: CT3, CT4 CC: SA4
4.2	Outgoing liaisons
5223	discussion 29.867 Rel-19 Discussion on potential impact of Solution #2 on other Working Groups for FS_IMSResil	KDDI	revised to C4-255241	Revision of C4-255241
Plenary	5241	discussion 29.867 Rel-19 Discussion on potential impact of Solution #2 on other Working Groups for FS_IMSResil	KDDI
Plenary	5064	LS out Rel-19 LS on IMS resiliency	Qualcomm Incorporated	To: CT1, CT3 Cc:
Plenary	5183	LS out Rel-19 Reply LS on Structure updates of AIoT Identifiers	CATT	To: SA2, RAN2, RAN3 Cc: SA3, CT1
Plenary	5193	LS out Rel-19 Reply LS on Structure updates of AIoT Identifiers	Lenovo	S2-2509655 To: SA2 CC: SA3, RAN2, RAN3, CT1
Plenary	5207	LS out Rel-19 Reply LS on Structure updates of AIoT Identifiers	Huawei	To: SA2 Cc: SA3, RAN2, RAN3, CT1
5	Check of Approved Output Documents
5011	other Output Documents	CT4 Chair
5012	other List of agreed 5G API related CRs	CT4 Chair/MCC
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 update	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.369 0 Rel19 API version and External doc update	Huawei	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.506 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.570 0 Rel19 API version and External doc update	Huawei	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	5080	CR 29.562 0193 Rel-16 S-CSCF Deregistration Notification	Ericsson	WI eIMS5G_SBA CAT F
Plenary	5081	CR 29.562 0194 Rel-17 S-CSCF Deregistration Notification	Ericsson	WI eIMS5G_SBA CAT A
Plenary	5082	CR 29.562 0195 Rel-18 S-CSCF Deregistration Notification	Ericsson	WI eIMS5G_SBA CAT A
Plenary	5083	CR 29.562 0196 Rel-19 S-CSCF Deregistration Notification	Ericsson	WI eIMS5G_SBA CAT A
Plenary	5138	CR 29.502 0923 Rel-16 Correction on epsInterworkingIndication	NTT DOCOMO, Nokia	WI TEI16 CAT F
Plenary	5139	CR 29.502 0924 Rel-17 Correction on epsInterworkingIndication	NTT DOCOMO, Nokia	WI TEI16 CAT A
Plenary	5140	CR 29.502 0925 Rel-18 Correction on epsInterworkingIndication	NTT DOCOMO, Nokia	WI TEI16 CAT A
Plenary	5141	CR 29.502 0910 Rel-19 Correction on epsInterworkingIndication	NTT DOCOMO, Nokia	WI TEI16 CAT A
Plenary	5147	CR 23.380 0135 Rel-16 Resolve EN on PCF Message	ZTE	WI TEI16 CAT F
Plenary	5148	CR 23.380 0136 Rel-17 Resolve EN on PCF Message	ZTE	WI TEI16 CAT A
Plenary	5149	CR 23.380 0137 Rel-18 Resolve EN on PCF Message	ZTE	WI TEI16 CAT A
Plenary	5150	CR 23.380 0138 Rel-19 Resolve EN on PCF Message	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]
17.5	Service Based Interface Protocol Improvements Release 17 [SBIProtoc17]
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]
18.5	CT aspects of NBI18 [NBI18]
18.6	CT aspects of SBIProtoc18 [SBIProtoc18]
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]
Plenary	5015	CR 29.503 1510 Rel-18 EDRX and PTW for eRedcap subscriptions	Nokia	WI NR_REDCAP_Ph2 CAT F
Plenary	5016	CR 29.503 1511 Rel-19 EDRX and PTW for eRedcap subscriptions	Nokia	WI NR_REDCAP_Ph2 CAT A
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]
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]
Plenary	5093	CR 29.572 0385 Rel-18 Transfer UE UP Positioning capabilities in LocContextData	Nokia	WI 5G_eLCS_Ph3 CAT F
Plenary	5094	CR 29.572 0386 Rel-19 Transfer UE User Plane Positioning in LocContextData	Nokia	WI 5G_eLCS_Ph3 CAT A
Plenary	5095	CR 29.572 0387 Rel-18 Convey the updated UE user plane positioning capabilities in UP Configuration	Nokia	WI 5G_eLCS_Ph3 CAT F
Plenary	5096	CR 29.572 0388 Rel-19 Convey the updated UE user plane positioning capabilities in UP Configuration	Nokia	WI 5G_eLCS_Ph3 CAT A
Plenary	5136	CR 29.572 0380 Rel-18 UE ID with LCS User Plane Connection	Ericsson, Nokia	WI 5G_eLCS_Ph3 CAT F
Plenary	5137	CR 29.572 0381 Rel-19 UE ID with LCS User Plane Connection	Ericsson, 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]
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]
Plenary	5075	CR 29.571 0686 Rel-19 Add new data type of MediaIdRm	China Mobile	WI NG_RTC CAT A
5076	CR 29.571 0686 Rel-19 Add new data type of MediaIdRm	China Mobile	withdrawn	WI NG_RTC CAT A
Plenary	5077	CR 29.571 0695 Rel-18 Add new data type of MediaIdRm	China Mobile	WI NG_RTC CAT F
Plenary	5078	CR 29.175 0103 Rel-18 Update the data type to MediaIdRm	China Mobile	WI NG_RTC CAT F
Plenary	5079	CR 29.175 0104 Rel-19 Update the data type to MediaIdRm	China Mobile	WI NG_RTC CAT A
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]
18.59	Enhancements on Service-based support for SMS in 5GC [eSMS_SBI]
18.60	CT aspects of eNA_Ph3 [eNA_Ph3]
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]
18.65	CT aspects of Enhancement of Network Slicing Phase 3 [eNS_Ph3]
18.66	CT aspects of XRM [XRM]
18.67	CT aspects of Access Traffic Steering, Switching and Splitting support in 5G system – Phase 3 [ATSSS_Ph3]
18.68	CT4 aspects of UPF enhancement for exposure and SBA [UPEAS]
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]
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
19.2	New WIDs for Rel-19
19.2.1	CT4 Led WIDs
19.2.2	CT4 Supported WIDs
19.3	Revised WIDs for Rel-19
5179	WID revised Rel-19 Revised WID on CT Aspects of Phase 3 for UAS, UAV and UAM	CT3	withdrawn
19.3.1	CT4 Led WIDs
19.3.2	CT4 Supported WIDs
Plenary	5195	WID revised Rel-19 Revised WID on CT Aspects of Phase 3 for UAS, UAV and UAM	LG Electronics
Plenary	5247	WID revised Rel-19 Revised WID on CT aspects of MINT support in EPS for 5G-only national roaming UE	China Telecommunications Corp.
19.4	TEI19 [TEI19]
Breakout	5014	CR 29.504 0337 Rel-19 Feature CHFGroup	Nokia, Verizon	WI 5GS_Ph1-CT, TEI19 CAT F
Breakout	5067	CR 23.632 0051 Rel-19 PDU Session continuity for Emergency Sessions during intersystem mobility	Ericsson	WI UDICOM, TEI19 CAT F
Breakout	5068	CR 29.503 1520 Rel-19 Support of Inter PLMN Cross Border Mobility Control Indication	Telekom Deutschland GmbH	WI TEI19 CAT B
Breakout	5069	CR 29.272 0885 Rel-19 Support of Inter PLMN Cross Border Mobility Control Indication	Telekom Deutschland GmbH	WI TEI19 CAT B
Breakout	5074	CR 29.272 0886 Rel-19 MME/SGSN registration for SMS	Ericsson	WI TEI19 CAT F
Plenary	5090	CR 29.572 0382 Rel-19 Correction of figure name for Location Measurements procedure	Nokia	WI TEI19 CAT F
Plenary	5091	CR 29.572 0383 Rel-19 Correction of reference and table numbering errors	Nokia	WI TEI19 CAT F
Plenary	5092	CR 29.572 0384 Rel-19 Update the UE User Plane Positioning Capabilities	Nokia	WI TEI19, 5G_eLCS_Ph3 CAT F
Plenary	5100	CR 23.003 0728 Rel-19 Correction of LCS User Plane Binding Identifier Definition and Reference	Nokia	WI TEI19, 5G_eLCS_Ph3 CAT F
Plenary	5101	discussion Rel-19 Routing information for secured LCS UP connection	Nokia
Plenary	5102	CR 23.003 0729 Rel-19 Define LCS-UP Connection Identifier for identifying secured user-plane connections between UE and LMF	Nokia	WI TEI19, 5G_eLCS_Ph3 CAT B
Plenary	5103	CR 29.572 0389 Rel-19 Add LCS-UP Connection ID in Location Context Transfer	Nokia	WI TEI19, 5G_eLCS_Ph3 CAT B
Plenary	5104	CR 29.518 1274 Rel-19 Addition of LCS-UP Connection Identifier to N1N2MessageTransfer Service Operation	Nokia	WI TEI19, 5G_eLCS_Ph3 CAT B
Plenary	5105	CR 29.572 0390 Rel-19 Add AMF Identity to UpConfig to support AMF change handling for LCS-UPP	Nokia	WI TEI19, 5G_eLCS_Ph3 CAT F
Plenary	5106	CR 29.230 0730 Rel-19 Introduction of PC-Session-Recovery-Status new AVP	Ericsson	WI TEI19 CAT B
Breakout	5107	CR 29.504 0338 Rel-19 Introduction of BdtNotifUriPatch Feature	Ericsson	WI TEI19 CAT B
Breakout	5115	CR 29.328 0663 Rel-19 Clarification on Sh-Pull behavior, User data request for specific domains	Ericsson	WI TEI19 CAT F
Plenary	5131	CR 29.510 1259 Rel-19 Removal of Optional Input NF Producer Id for Key Retrieval	Ericsson	WI TEI19, SBA_KDATV-SEC CAT F
Main	5132	CR 29.518 1275 Rel-19 Expiry in Subscription Change Notification	Ericsson	WI TEI19 CAT F
Main	5133	CR 29.518 1276 Rel-19 Immediate Report in Subscription Modification Response	Ericsson	WI TEI19 CAT F
Plenary	5134	CR 29.572 0393 Rel-19 Support of UE with Multiple LCS-UPP connections Capability	Ericsson, CATT	WI TEI19, 5G_eLCS_Ph3 CAT B
Main	5151	CR 29.518 1278 Rel-19 Cleanup and corrections for MBS services	ZTE	WI TEI19, 5MBS_Ph2 CAT F
Breakout	5152	CR 29.505 0545 Rel-19 Editoral correction on description to DataChangeNotify	ZTE	WI TEI19 CAT F
Plenary	5153	CR 29.303 0139 Rel-19 Editoral correction	ZTE	WI TEI19 CAT F
Main	5154	CR 29.518 1279 Rel-19 Add missing reference	ZTE	WI TEI19 CAT F
Plenary	5160	CR 29.581 0055 Rel-19 Correction CR to TS 29.581	Samsung	WI TEI19 CAT F
Plenary	5161	CR 29.571 0698 Rel-19 Correction of attribute presence	Huawei	WI TEI19 CAT F
Plenary	5162	CR 29.571 0699 Rel-19 Correction of UserLocation	Huawei	WI TEI19 CAT F
Main	5163	CR 29.518 1280 Rel-19 Editorial corrections	Huawei	WI TEI19 CAT D
Main	5164	CR 29.518 1281 Rel-19 Correction of a data type	Huawei	WI TEI19 CAT F
Main	5165	CR 29.502 0926 Rel-19 Correction of a table note	Huawei	WI TEI19 CAT F
Main	5171	CR 29.502 0927 Rel-19 QoS Monitoring for packet delay for PDU session without N3 DL F-TEID	Ericsson	WI TEI19 CAT F
Main	5189	CR 29.244 1006 Rel-19 QoS Monitoring for redundant N3/N9 and PDU sessions	Ericsson	WI TEI19 CAT F
Main	5191	CR 29.564 0156 Rel-19 QoS Monitoring for redundant N3/N9 and PDU sessions	Ericsson	WI TEI19 CAT F
Plenary	5196	CR 23.003 0715 Rel-19 LCS identifiers	OPPO	WI 5G_eLCS_Ph3, TEI19 CAT F
Main	5199	CR 29.502 0928 Rel-19 Minor Correction	Ericsson	WI TEI19 CAT F
Main	5220	CR 29.244 1007 Rel-19 Update and replace ietf draft	Huawei	WI TEI19 CAT F
Plenary	5221	CR 29.369 0015 Rel-19 Correction of attribute presence	Huawei	WI TEI19 CAT F
Plenary	5222	CR 29.577 0026 Rel-19 Correction of attribute presence	Huawei	WI TEI19 CAT F
Plenary	5224	CR 29.509 0243 Rel-19 Correction of attribute presence	Huawei	WI TEI19 CAT F
Plenary	5225	CR 29.550 0051 Rel-19 Correction of attribute presence	Huawei	WI TEI19 CAT F
Plenary	5230	CR 29.571 0702 Rel-19 Editorial correction for Commondata OpenAPI	Huawei	WI TEI19 CAT D
Breakout	5231	CR 29.562 0200 Rel-19 Correction on S-CSCF registration procedure in Nhss_imsUECM	Huawei	WI TEI19 CAT F
Plenary	5232	CR 29.531 0253 Rel-19 Correction of attribute presence	Huawei	WI TEI19 CAT F
Plenary	5233	CR 29.556 0054 Rel-19 Correction of attribute presence	Huawei	WI TEI19 CAT F
Plenary	5234	CR 29.573 0236 Rel-19 Correction of attribute presence	Huawei	WI TEI19 CAT F
Main	5235	CR 29.518 1235 Rel-19 Event Exposure on UE Reachable for DL Traffic for UE in RRC-Inactive	Huawei	WI TEI19 CAT F
Main	5236	CR 29.518 1284 Rel-19 Correction on UPDP subscription and notification	Huawei	WI TEI19 CAT F
Plenary	5250	CR 24.010 0009 Rel-19 Changes to Supplementary service procedures for using Extended Facility IE	Huawei	WI TEI19 CAT F The CR was agreed on CT4#131
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]
19.7	CT aspects of Providing per-subscriber VLAN instructions from UDM and DN-AAA [TEI19_VLANSUB]
Plenary	5168	CR 29.244 1005 Rel-19 Allowed VLAN tags and VLAN Handling Information	Ericsson	WI TEI19_VLANSUB CAT F
Plenary	5169	CR 29.503 1524 Rel-19 Allowed VLAN tags and VLAN Handling Information	Ericsson	WI TEI19_VLANSUB CAT F
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]
Breakout	5017	CR 29.503 1512 Rel-19 Roaming Info Update	Nokia	WI SBIProtoc19 CAT F
Breakout	5018	CR 29.503 1513 Rel-19 Shared Data nesting	Nokia	WI SBIProtoc19 CAT F
Breakout	5020	CR 29.503 1502 Rel-19 Deregistration Reason	Nokia	WI SBIProtoc19 CAT F
Breakout	5025	CR 29.503 1519 Rel-19 UE Reachability for Data	Nokia	WI SBIProtoc19 CAT F
Breakout	5042	CR 29.505 0542 Rel-19 Storage of UPU Header Protection capabilities in UDR	Ericsson	WI SBIProtoc19 CAT F
Breakout	5049	CR 29.509 0241 Rel-19 Optionality of UPU Header Protection	Ericsson	WI SBIProtoc19 CAT F
Plenary	5053	CR 29.500 0483 Rel-19 3gpp-Sbi-Callback type values	Nokia	WI SBIProtoc19 CAT F
Plenary	5054	CR 29.500 0484 Rel-19 Clarifications to Authorization for indirect communication with delegated discovery	Nokia	WI SBIProtoc19 CAT F
Main	5055	CR 29.502 0920 Rel-19 Corrections for Conditional IEs	Nokia	WI SBIProtoc19 CAT F
Breakout	5072	CR 29.503 1521 Rel-19 UPU Header Security	Nokia	WI SBIProtoc19 CAT F
Breakout	5073	CR 29.505 0543 Rel-19 UPU Header Security	Nokia	WI SBIProtoc19 CAT F
Main	5099	CR 29.536 0154 Rel-19 Correction of Clause Number, Reference, and Table Number Errors	Nokia	WI SBIProtoc19 CAT F
Breakout	5109	CR 29.503 1522 Rel-19 PLMN level accuracy in "Location Reporting" event type	Ericsson	WI SBIProtoc19 CAT F
Plenary	5110	CR 29.571 0697 Rel-19 PLMN ID location in UserLocation	Ericsson	WI SBIProtoc19 CAT F
Breakout	5111	CR 29.503 1523 Rel-19 Old PEI in Nudm_EE	Ericsson	WI SBIProtoc19 CAT B
Breakout	5112	CR 29.505 0544 Rel-19 Old PEI in Nudr	Ericsson	WI SBIProtoc19 CAT B
Plenary	5125	CR 29.510 1258 Rel-19 Delegated Discovery and Reselection in Target PLMN	Ericsson	WI SBIProtoc19 CAT F
Plenary	5126	CR 29.500 0485 Rel-19 Delegated Discovery and Reselection in Target PLMN	Ericsson	WI SBIProtoc19 CAT F
Main	5127	CR 29.502 0922 Rel-19 Delegated Discovery and Reselection in Target PLMN	Ericsson	WI SBIProtoc19 CAT F
Breakout	5128	CR 29.542 0044 Rel-19 Add Condition for Conditional IE	Ericsson	WI SBIProtoc19 CAT F
Breakout	5129	CR 29.572 0391 Rel-19 Correction on the Condition for Conditional IE	Ericsson	WI SBIProtoc19 CAT F
Breakout	5130	CR 29.572 0392 Rel-19 Correction on LDR Reference	Ericsson	WI SBIProtoc19 CAT F
Breakout	5173	CR 29.503 1525 Rel-19 Conditional Attributes	Nokia	WI SBIProtoc19 CAT F
Main	5181	CR 29.518 1282 Rel-19 Should corresponds to presence as Optional	Ericsson	WI SBIProtoc19 CAT F
Plenary	5187	CR 29.515 0207 Rel-19 Correct the description of some conditional attributes	CATT	WI SBIProtoc19 CAT F
Plenary	5188	CR 29.555 0029 Rel-19 Correct the description of Monitored PLMN ID in MatchReport Service	CATT	WI SBIProtoc19 CAT F
19.11	Subscriber Data Migration [SUBDMIG]
Plenary	5113	discussion Rel-19 Status of SUBDMIG pending issues	Ericsson
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]
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]
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]
Breakout	5019	CR 29.503 1514 Rel-19 PEI in Monitoring Reports	Nokia	WI TEI19_RVAS CAT F
Plenary	5070	CR 29.510 1255 Rel-19 Subscription-based routing to a target PLMN	Ericsson, AT&T, Cisco	WI TEI19_RVAS CAT F
19.24	CT Aspects of On-demand broadcast of GNSS assistance enhancement [TEI19_OBGAD]
19.25	CT aspects of NF discovery and selection by target PLMN [TEI19_NFsel_by_tPLMN]
19.26	CT aspects of enhancement of support for Edge Computing in 5G Core network - Phase 3 [eEDGE_5GC_Ph3]
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]
Plenary	5050	Work Plan Rel-19 Work plan for UIA_ARC	InterDigital
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]
Main	5178	CR 29.502 0917 Rel-19 QoS Monitoring per QoS flow interworking with the NG-RAN	Ericsson	WI TEI19_QME CAT F
19.31	CT Aspects of Phase3 for UAS, UAV and UAM [UAS_Ph3]
Main	5135	CR 29.518 1277 Rel-19 Single Subscription for UAS Events per UE	Ericsson	WI UAS_Ph3 CAT F
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]
19.36	CT aspects of Proximity-based Services in 5GS Phase 3 [5G_ProSe_Ph3]
19.37	CT aspects of UPF enhancement for Exposure And SBA Phase 2 [UPEAS_Ph2]
Main	5172	CR 29.564 0154 Rel-19 Clarification for a subscription containing AppIds or Traffic filters	Ericsson	WI UPEAS_Ph2 CAT F
Main	5174	CR 29.564 0155 Rel-19 Receiving of a Subscription Termination Notification	Ericsson	WI UPEAS_Ph2 CAT F
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	5122	discussion Rel-19 Work plan for the CT aspects of AIML_CN	vivo
Plenary	5044	CR 29.510 1253 Rel-19 Correction of VFL client and server registration	Huawei	WI AIML_CN CAT F Overlapping with 5120
Plenary	5120	CR 29.510 1256 Rel-19 Clarification on only VFL client includes vflInterInfo and featureId	vivo	WI AIML_CN CAT F
Plenary	5045	CR 29.510 1254 Rel-19 Correction of VFL client and server discovery	Huawei	WI AIML_CN CAT F Overlapping with 5146
Plenary	5146	CR 29.510 1260 Rel-19 VFL discovery with feature IDs	ZTE	WI AIML_CN CAT F
Main	5046	CR 29.570 0003 Rel-19 Correction of SCP event report	Huawei	WI AIML_CN CAT F Partially overlaps with 5123 and 5204 on correcting the ScpSignallingInfo aspects
Main	5123	CR 29.570 0007 Rel-19 Alignment of ScpSignallingInfo	vivo	WI AIML_CN CAT F Overlapping with 5204
Main	5204	CR 29.570 0008 Rel-19 Alignment with SA2 for exposure of number of signalling messages sent and received between SCP and NF service instance	Nokia	WI AIML_CN CAT F
Main	5047	CR 29.570 0004 Rel-19 Alignment of event name with stage-2	Huawei	WI AIML_CN CAT F
Main	5048	CR 29.518 1272 Rel-19 Alignment of terminology with stage-2	Huawei	WI AIML_CN CAT F overlapping with 5203
Main	5203	CR 29.518 1283 Rel-19 Clarification of Signalling Measurement event descriptions to align with SA2	Nokia	WI AIML_CN CAT F
Main	5065	CR 29.518 1273 Rel-19 Signalling Storm Analytics data collection from AMF	NTT DOCOMO	WI AIML_CN CAT F
Main	5066	CR 29.571 0694 Rel-19 Add the nullable property for Snssai	NTT DOCOMO	WI AIML_CN CAT F
Main	5097	CR 29.570 0005 Rel-19 Clarification on expiry time handling during subscription modification	Nokia	WI AIML_CN CAT F
Main	5098	CR 29.570 0006 Rel-19 Correction of Report Type and clarification of reporting scope	Nokia	WI AIML_CN CAT F
Plenary	5118	CR 29.510 1241 Rel-19 Support of Positioning case information for NWDAF	vivo	WI AIML_CN CAT F Overlapping with 5145
Plenary	5119	CR 29.510 1242 Rel-19 Introduction of NWDAF supporting model training for LMF-based AI/ML positioning	vivo	WI AIML_CN CAT F Overlapping with 5145
Plenary	5145	CR 29.510 1248 Rel-19 Update of NWDAF discovery	ZTE, Nokia	WI AIML_CN CAT F
5121	CR 29.510 1257 Rel-19 Alignment of ScpSignallingInfo	vivo	withdrawn	WI AIML_CN CAT F
Plenary	5209	CR 29.572 0394 Rel-19 Support data collection for LMF based AIML positioning	Huawei	WI AIML_CN CAT F
19.40	CT aspects of Next Generation Real time Communication services [NG_RTC_Ph2]
Breakout	5027	CR 29.562 0192 Rel-19 Cancel procedure for subscriber specific IMS Events	Ericsson	WI NG_RTC_Ph2 CAT B
Breakout	5085	CR 29.175 0105 Rel-19 Update on ImsSessionEventNotification for IMS session management API	Huawei	WI NG_RTC_Ph2 CAT F
Breakout	5086	CR 29.175 0106 Rel-19 Audio/video support in the MDC2 interface	Huawei	WI NG_RTC_Ph2 CAT B
Breakout	5087	CR 29.176 0049 Rel-19 Audio/Video support in MDC2 interface	Huawei	WI NG_RTC_Ph2 CAT B
Breakout	5088	CR 29.176 0050 Rel-19 Correction on the description of associatedMediaId	Huawei	WI NG_RTC_Ph2 CAT F
Breakout	5089	CR 29.571 0696 Rel-19 Audio/Video support in MDC2 interface	Huawei	WI NG_RTC_Ph2 CAT B
Breakout	5114	CR 29.562 0198 Rel-19 HSS initiated IMS AS De-registration procedure	Ericsson	WI NG_RTC_Ph2 CAT B
Breakout	5116	CR 29.562 0199 Rel-19 IMS AS registration with re-assignment for new sessions	Ericsson	WI NG_RTC_Ph2 CAT B
Breakout	5159	CR 29.176 0051 Rel-19 Usage of Avatar ID	ZTE	WI NG_RTC_Ph2 CAT F
Breakout	5200	CR 29.175 0107 Rel-19 Update error handling for IMS session management	China Mobile	WI NG_RTC_Ph2 CAT B
Breakout	5202	CR 29.175 0108 Rel-19 Update PUT method on Individual IMS Session Resource	China Mobile	WI NG_RTC_Ph2 CAT B
Breakout	5227	CR 29.175 0109 Rel-19 Correction on Nimsas_ImsEE service operation	Huawei	WI NG_RTC_Ph2 CAT F
Breakout	5228	CR 29.175 0110 Rel-19 Correction on Nimsas_ImsSM service operation	Huawei	WI NG_RTC_Ph2 CAT F
Breakout	5237	CR 29.571 0703 Rel-19 Remove the editor's note for ImsEventFilter data type	Huawei	WI NG_RTC_Ph2 CAT F
Breakout	5238	CR 29.175 0099 Rel-19 Add an application error for Nimsas_ImsSM_update operation	Huawei	WI NG_RTC_Ph2 CAT F
Breakout	5243	CR 29.571 0704 Rel-19 Update on the AppBindingInfo	Huawei	WI NG_RTC_Ph2 CAT F
Breakout	5244	CR 29.175 0097 Rel-19 Add the multiAppBindingInfo attribute to DcMediaSpec	China Mobile, 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]
19.44	Alignment of eCall over IMS with CEN [eCallCEN]
19.45	CT aspects of Multi-Access (ATSSS_Ph4) [MASSS]
19.46	CT Aspects on Subscription control for reference time distribution in EPS [TEI19_TIME_SUB_EPS]
19.47	CT aspects of 5G NR Femto [5G_Femto]
19.48	CT aspects of Extended Reality and Media service (XRM) Phase 2 [XRM_Ph2]
Main	5056	CR 29.502 0921 Rel-19 RAN controlled UL bitrate recommendation	Nokia	WI XRM_Ph2, NR_XR_Ph3-Core CAT B
Main	5057	CR 29.571 0688 Rel-19 PDU Set Importance for N6-unmarked PDUs	Nokia, Lenovo	WI XRM_Ph2, 5G_RTP_Ph2 CAT B
Main	5058	CR 29.244 1001 Rel-19 PDU Set Importance for N6-unmarked PDUs	Nokia, Lenovo	WI XRM_Ph2, 5G_RTP_Ph2 CAT B
Plenary	5059	LS out Rel-19 Reply LS on N6-Unmarked PDUs	Nokia	S4-250738 To: SA4 CC: SA2, CT3
Main	5201	CR 29.571 0701 Rel-19 Wrong reference in Table 5.5.3.17-1 of TS 29.571	Samsung	WI XRM CAT F
19.49	CT aspects for application enablement for satellite access Phase 3 [5GSAT_Ph3_App]
19.50	CT aspects of Application enablement for XRM Services Phase 2 [XRM_Ph2_App]
19.51	Rel-19 Enhancements of UE Policy [UEP19]
19.52	Common API Framework (CAPIF) Phase 3 [CAPIF_Ph3]
19.53	CT aspects for enabling MSGin5G Service phase 3 [5GMARCH_Ph3]
19.54	CT aspects of security for mobility over non-3GPP access to avoid full primary authentication [Non3GPPMob_Sec]
19.55	NAS layer overhead reduction for data transfer using CP CIoT [NORDAT_CP]
19.56	CT Aspects on Deferred 5GC-MT-LR Procedure for Periodic Location Events based NRPPa Periodic Measurement Reports [TEI19_DLPMR]
19.57	Reducing Information Exposure over SBI [RedInfExp_SBI]
19.58	Network Controlled Network Slice Selection [TEI19_SliceSel]
19.59	PRU Usage Extension supported by Core Network [TEI19_PRUE]
19.60	Energy Efficiency and Energy Saving [EnergySys]
Breakout	5024	CR 29.503 1518 Rel-19 User Consent for collection and processing of energy-related information	Nokia	WI EnergySys CAT B
Plenary	5051	Work Plan Rel-19 Work Plan for Energy_Sys	Samsung
Main	5158	CR 29.244 1004 Rel-19 Clarify usage report for a PDU session with alternative S-NSSAI	ZTE	WI EnergySys CAT F
19.61	Support for PWS in Satellite E-UTRAN and Satellite NG-RAN [PWS_NTN]
19.62	CT aspects for application enablement aspects for MMTel [MMTel_App]
19.63	CT aspects of Rel-19 Application Data Analytics Enablement Service [TEI19_ADAES]
19.64	Rel-19 Enhancements of SM Policy [SMPC19]
19.65	CT Aspects for IP Domain usage [IPD]
19.66	CT aspects of UEId Service API support for MSISDN Verification operation [TEI19_MVOSNS]
19.67	IMS Disaster Prevention and Restoration Enhancement [IMS_RES-CT]
Plenary	5026	CR 23.380 0134 Rel-19 EPC/5GC health check and recovery upon IMS Terminating Call	Ericsson, China Telecom	WI IMS_RES-CT CAT B
Plenary	5108	CR 29.562 0197 Rel-19 Registration Timer Extension	Ericsson	WI IMS_RES-CT CAT B
Plenary	5226	CR 23.380 0139 Rel-19 Clarification on enhanced H.248 MOD request for PCRF/PCF bypass procedure	Huawei	WI IMS_RES-CT CAT F
19.68	CT aspects on Advanced Media Delivery [AMD_PRO-MED-CT]
19.69	CT aspects for ATSSS Rule Provisioning via 3GPP access connected to EPC [TEI19_ARP3E-CT]
19.70	CT aspects of Architecture support of Ambient power-enabled Internet of Things [AmbientIoT-CT]
Plenary	5043	CR 29.518 1252 Rel-19 Aligning the procedure list with stage-2	Huawei, ZTE	WI AmbientIoT-CT CAT B
Plenary	5124	CR 23.003 0730 Rel-19 AIoT Identification Information Structure	Ericsson	WI AmbientIoT-CT CAT F Overlapping with 5184, 5190, 5242
Plenary	5184	CR 23.003 0732 Rel-19 Definition of AIoT Identification Information	CATT	WI AmbientIoT-CT CAT F
Plenary	5190	CR 23.003 0733 Rel-19 Adding AIoT Identification Information	Lenovo	WI AmbientIoT-CT CAT B
Plenary	5242	CR 23.003 0734 Rel-19 Define AIoT Device Identification Information	Huawei	WI AmbientIoT-CT CAT B
Plenary	5155	CR 29.506 0003 Rel-19 Corrections on UDR service for AIoT	ZTE	WI AmbientIoT-CT CAT F
Plenary	5166	CR 29.369 0006 Rel-19 Add Reference to TS 29.369	Samsung	WI AmbientIoT-CT CAT B
Plenary	5167	CR 29.369 0007 Rel-19 Add security services offered by ADM	Samsung	WI AmbientIoT-CT CAT B
Plenary	5176	CR 29.506 0002 Rel-19 AIoT support for T-IDs	Lenovo	WI AmbientIoT-CT CAT B
5177	CR 29.369 0005 Rel-19 AIoT support for T-IDs	Lenovo	revised to C4-255246	Revision of C4-255246 WI AmbientIoT-CT CAT B
Plenary	5180	CR 23.003 0731 Rel-19 Adding AIoT Device Temporary Identifier	Lenovo	WI AmbientIoT-CT CAT B Overlapping with 5211
Plenary	5211	CR 23.003 0735 Rel-19 Define AIoT Device Temporary Identifier	Huawei	WI AmbientIoT-CT CAT B
Plenary	5192	CR 29.571 0700 Rel-19 Adding AIoT Device Temporary Identifier	Lenovo	WI AmbientIoT-CT CAT B
Plenary	5194	CR 29.369 0008 Rel-19 New ADM security service	Lenovo	WI AmbientIoT-CT CAT B
Plenary	5207	LS out Rel-19 Reply LS on Structure updates of AIoT Identifiers	Huawei	Moved to 4.2
Plenary	5208	LS out Rel-19 draft Reply LS on AIoT Device Permanent ID Length	Huawei
5210	CR 23.003 0734 Rel-19 Define AIoT Device Identification Information	Huawei	revised to C4-255242	Revision of C4-255242 WI AmbientIoT-CT CAT B
Plenary	5212	CR 23.003 0736 Rel-19 Update on the length of Identification Information	Huawei	WI AmbientIoT-CT CAT B
Plenary	5213	CR 29.369 0005 Rel-19 AIoT support for T-IDs	Lenovo, Huawei	WI AmbientIoT-CT CAT B Seems this tdoc is revised to 5246 while not indicated in the database Overlapping with 5219
Plenary	5246	CR 29.369 0005 Rel-19 AIoT support for T-IDs	Lenovo	WI AmbientIoT-CT CAT B Overlapping with 5219
Plenary	5219	CR 29.369 0014 Rel-19 Support T-ID handling information	Huawei	WI AmbientIoT-CT CAT B
Plenary	5214	CR 29.369 0009 Rel-19 Define Nadm_Sec General	Huawei	WI AmbientIoT-CT CAT B
Plenary	5215	CR 29.369 0010 Rel-19 Define Nadm_Sec_RandGet	Huawei	WI AmbientIoT-CT CAT B
Plenary	5216	CR 29.369 0011 Rel-19 Define Nadm_Sec_AuthenticationGet	Huawei	WI AmbientIoT-CT CAT B
Plenary	5217	CR 29.369 0012 Rel-19 Define Nadm_Sec_SessionKeyGet	Huawei	WI AmbientIoT-CT CAT B
Plenary	5218	CR 29.369 0013 Rel-19 Define Nadm_Sec_TidGet	Huawei	WI AmbientIoT-CT CAT B
5248	pCR 24.369 Rel-19 Pseudo-CR on security parameter length	Lenovo.	Withdrawn
19.71	Harmonization of test case definitions for cross-RAT usability [TestHarmon_CrossRAT]
19.72	CT aspects of MINT support in EPS for 5G-only national roaming UE [MINT_Ph2]
Plenary	5142	CR 29.274 2135 Rel-19 Create Session handling for disaster-roaming service continuity	LG Electronics	WI MINT_Ph2 CAT B
5156	CR 29.272 0887 Rel-19 MINT-EPS Support Indication	ZTE	withdrawn	WI MINT_Ph2 CAT B
Plenary	5157	CR 29.272 0888 Rel-19 Clarify MME and HSS behavior on authentication in disaster roaming service	ZTE	WI MINT_Ph2 CAT B
Breakout	5175	CR 29.503 1526 Rel-19 MINT-EPS Support Indication	ZTE	WI MINT_Ph2 CAT B
Breakout	5185	CR 29.503 1527 Rel-19 Support of MINT-EPS	CATT, China Telecom	WI MINT_Ph2 CAT B
Breakout	5186	CR 29.509 0242 Rel-19 Support of MINT-EPS	CATT, China Telecom	WI MINT_Ph2 CAT B
19.73	Protocol for AI Data Collection from UPF [PAIDC_UPF]
Plenary	5240	CR 29.564 0157 Rel-19 UPF subscription with 5G VN group Id	China Mobile	WI PAIDC_UPF CAT B
19.74	CT aspects of Lower Selection-priority for PLMN Selection [LoSePLMN-CT]
20	Release 20
20.1	Rel-20 Exception sheets or other Rel-20 work planning
20.2	New WIDs for Rel-20
Plenary	5013	discussion Principles for 6G SIDs in CT area	CT & CT WG Chairs
20.2.1	CT4 Led WIDs
Plenary	5052	SID new Rel-20 New SID on 6G Network Resilience and Reliability	China Telecom Corporation Ltd.
Plenary	5061	SID new Rel-20 New_SID_6G Study_Resilience and Reliability for 6G System	China Mobile
Plenary	5060	SID new Rel-20 New SID on Protocol aspects for Control Plane in Core Network of 6G System	Nokia
Plenary	5143	SID new Rel-20 New SID on Study of Unified Event Exposure in 6G System	Samsung
Plenary	5144	SID new Rel-20 New SID on Protocol aspects for User Plane in Core Network of 6G System	ZTE, CATT
Plenary	5170	discussion Rel-20 Discussion paper on multiple NRF instances in same region	NTT DOCOMO
Plenary	5182	SID new Rel-20 New SID on Protocol aspects for Data Framework in Core Network of 6G System	CATT
Plenary	5205	discussion Rel-20 Discussion on study on Protocols enhancement and evolution within Core Network	Huawei
Plenary	5206	SID new Rel-20 New SID on Protocols enhancement and evolution within Core Network	Huawei	f
20.2.2	CT4 Supported WIDs
Plenary	5197	discussion Rel-20 Discussion on the Protocol for AI Agent and AI framework in the 6G System	Huawei
Plenary	5198	SID new Rel-20 New SID on Study on the Protocol for AI Agent and AI framework in the 6G System	Huawei
Plenary	5245	discussion Rel-20 Discussion on protocol enhancement for AI in 6G	China Mobile
20.3	Revised WIDs for Rel-20
20.3.1	CT4 Led WIDs
20.3.2	CT4 Supported WIDs
20.4	TEI20 [TEI20]
5021	CR 29.503 1515 Rel-20 Support of allowed MAC addresses in SM subscription data in UDM	Nokia	Postponed	WI TEI20 CAT B Rel-20 5G-A related CRs are not handled in this meeting, see CP-252252
5022	CR 29.503 1516 Rel-20 Enhance the registration procedure to support the INS for disaster condition	Nokia	Postponed	WI TEI20 CAT B Rel-20 5G-A related CRs are not handled in this meeting, see CP-252252
5023	CR 29.503 1517 Rel-20 Inclusion of Forbidden EPS Areas in mobility restriction for NR to LTE mobility	Nokia	Postponed	WI TEI20 CAT B Rel-20 5G-A related CRs are not handled in this meeting, see CP-252252
21	Study Items
20.1	Study on Protocol for AI Data Collection from UPF [FS_PAIDC-UPF]
Plenary	5229	CR 29.889 0001 Rel-19 Update conclusion for KI#1	China Mobile	WI FS_PAIDC_UPF CAT B
21.2	Study on Reducing Information Exposure over SBI [FS_RedInfExp_SBI]
21.3	Study on IMS Disaster Prevention and Restoration Enhancement [FS_IMS_RES]
21.4	Study on IMS resiliency [FS_IMSResil]
Plenary	5062	pCR 29.867 Rel-19 Pseudo-CR on update of solution #1	Qualcomm Incorporated
Plenary	5063	pCR 29.867 Rel-19 Pseudo-CR on update of solution #3	Qualcomm Incorporated
Plenary	5071	Work Plan Rel-19 Work plan for FS_IMSResil	KDDI
5084	pCR 29.867 Rel-19 Pseudo-CR on SMF indicates the P-CSCF failure in PDN connection establishment	Huawei	revised to C4-255239	Revision of C4-255239
Plenary	5117	pCR 29.867 Rel-19 Pseudo-CR on Solution #2 clarification	KDDI
5223	discussion 29.867 Rel-19 Discussion on potential impact of Solution #2 on other Working Groups for FS_IMSResil	KDDI	revised to C4-255241	Revision of C4-255241
Plenary	5241	discussion 29.867 Rel-19 Discussion on potential impact of Solution #2 on other Working Groups for FS_IMSResil	KDDI	Moved to 4.2
Plenary	5239	pCR 29.867 Rel-19 Pseudo-CR on SMF indicates the P-CSCF failure in PDN connection establishment	Huawei
TR 29.867v0.4.0	KDDI
22	Any other business
5010	Work Plan Work Plan	CT4 Chair
5249	ToR Terms of Reference (ToR) for 3GPP TSG CT WG4 (CT4)	CT4 Chair
23	Future meetings
24	Close of Meeting