3GPP TSG-CT WG4 Meeting #126	C4-245006

Orlando, U.S; 18th – 22nd November 2024

Source:	Chairman, TSG-CT WG4

Title:	Proposed allocation of documents to agenda items for CT4#126, status at 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-245002
2	Allocation of Documents to Agenda Items
5001	agenda Draft Agenda	CT4 Chair
5002	other eMeeting 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	All Liaison statements are handled under this agenda item
4.1	Incoming liaisons
Plenary	5012	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 Postponed from CT4#125 Chair’s note from CT4#125: CT4 is fine with the proposal from CT3, and CT4 sees a need of corresponding 29501 CR, once that CR is agreed we can send a reply LS to CT3
Plenary	5013	LS in LS reply on MDT configuration control in NR-DC	SA WG5	S5-244659 To: RAN3, CT4 CC: Contact: Ericsson Postponed from CT4#125 Chair’s note from CT4#125: Corresponding CRs to be submitted to the next CT4 meeting, when those CRs are handled we can send reply. Related CRs in 5280 (and mirror)
Plenary	5015	LS in Reply LS on MDT configuration control in NR-DC	RAN WG3	R3-245684 To: SA5, CT4 CC: Contact: Huawei --- RAN3 thanks SA5 for the reply LS on MDT configuration control in NR-DC in document S5-244659. RAN3 would like to inform SA5 and CT4 about the guidance from RAN plenary for the non-inclusive language usage which is captured in RP-202179. Term “Master”. Example alternative terms: “Primary”, “Controller”, “Main” “Master” to be only replaced when used in “Master”/”Slave” context. Standalone use of “Master” is not to be replaced. (Note: the terms "master"/"secondary", as used in the context of Dual Connectivity in multiple RAN specifications and across the industry are not intended to be replaced.) Furthermore, according to 3GPP TR 21.801 v.18.0.0 Annex K, Table K.1 (first row), “master” is considered non-inclusive “when used in ‘master / slave’ context”. This is not the case in Dual Connectivity, where the SN is the Secondary Node. With such guidance above, the term “Master node” in the context of DC is not replaced in in RAN2 and RAN3 specifications. It is explicitly defined in section 3.1 and section 3.2 in TS 37.340. RAN3 would like SA5 and CT4 to retain the previous definition of the term “MN” meaning “Master node” to avoid misalignment and misleading between groups. RAN3 has no further comments on the SA5 CRs attached in the LS. --- RAN3’s reply to 5013.
Plenary	5014	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 Postponed from CT4#125 Chair’s note from CT4#125: [Rong] 29.244 and 29.518 CRs may be needed related to this LS Related CRs in 5078 (and mirror), 5079 (and mirror), 5278 Reply LS in 5106
Plenary	5016	LS in Rel-19 LS on Supporting MBS broadcast service for NR NTN	RAN WG3	R3-245844 To: RAN2, SA2, CT4 CC: Contact: Xiaomi --- RAN3 has discussed the NGAP impact to support NTN MBS in Rel-19. More specifically, how the AMF indicates to the gNB when the intended service area is smaller than the satellite footprint. RAN3 agreed that the intended service area provided to the gNB can be Mapped Cell ID(s), TAI(s), or geographical service area information. The name and encoding of the geographical service area information will align with RAN2 decision. RAN3 has started to work on the appropriate signalling solution (see attached agreed TPs – IE name and encoding are pending RAN2 discussion). RAN3 considers this may impact SA2 and CT4. ---
Plenary	5017	LS in Rel-19 LS on Transport level marking based on PDU Set Importance	SA WG2	S2-2410948 To: CT4 CC: - Contact: Intel --- As part of the XRM_Ph2 work item, SA2 has agreed the attached TS 23.501 CR in relation to Key Issue #3 in TR 23.700-70 (“Leverage PDU Set QoS information for DSCP marking over N3/N9 in the transport network”). SA2 could not agree whether the SMF should provide the list of transport level marking values to the UPF in a FAR or in a QER, see underlined text in the agreed CR: For QoS Flows that are configured for PDU Set QoS handling, the SMF may additionally take into account the PDU Set Importance when determining the transport level packet marking values. In this case, the SMF provides a list of transport level packet marking values for the downlink direction to the UPF, each of the transport level packet marking values corresponding to one or more PDU Set Importance values. When an I-SMF/I-UPF is inserted in the PDU Session, the I-SMF may instruct the I-UPF to derive the transport level packet marking of the outgoing N3 downlink packet based on the transport level packet marking of the incoming N9 downlink packet. SA2 is of the opinion that the decision of using FAR vs QER for the abovementioned purpose would be better addressed by CT4 experts. Therefore, SA2 kindly asks CT4 to provide feedback on whether the SMF should provide the list of transport level marking values to the UPF in a FAR or in a QER. --- Reply LS in 5083, 5197
Plenary	5018	LS in Rel-18 LS on Configuration of Slice Usage Control Information	SA WG2	S2-2411033 To: CT4 CC: CT1, CT3 Contact: ZTE --- SA2 thanks for CT4 for the LS (C4-243492) on Configuration of Slice Usage Control Information. SA2 would like to provide the answer to the following questions as the following: Q1: For SA-PDU Session, is the PDU Session inactivity timer independent of access type? SA2 answer: Yes. Q2: To support per S-NSSAI per access type slice usage control defined in 3GPP TS 23.501, does it need to configure different timer values to different access type in UDM? SA2 answer: No. Q3: If the answer of Q2 is no, what is the exact AMF/SMF behaviour of performing per S-NSSAI per access type network slice usage control (i.e. starting slice deregistration inactivity timer or PDU Session inactivity timer)? Does the AMF or SMF assign same timer value to 3GPP access and non-3GPP access? SA2 answer: Yes, the AMF/SMF assign same timer value to 3GPP access and non 3GPP access. The AMF (in case of slice deregistration inactivity timer) and UPF (in case of slice PDU session inactivity timer) starts the timer per S-NSSAI as per clause 5.15.15 of TS 23.501 --- Related CRs in 5048,5049,5050,5051, 5245, 5246
Plenary	5019	LS in Rel-18 LS Response on slice mapping between the HPLMN and EHPLMN	SA WG2	S2-2411063 To: CT1, CT4 CC: Contact: ZTE --- SA2 thanks for CT4 for the LS (C4-243606) on slice mapping between the HPLMN and EHPLMN. SA2 also received the LS (C1-239320) from CT1 and noted the LS at S2-160-Ad Hoc-e … SA2 would like to provide the answers as below: Q1: Is it necessary for the AMF to perform the mapping of the S-NSSAI(s) of EHPLMN and HPLMN S-NSSAI(s) and provide mapped HPLMN S-NSSAI corresponding to the S-NSSAI(s) of EHPLMN to the UE? SA2 answer: Yes. In order to avoid the impact on the UE side, when the UE selects a PLMN which is not derived from the SUPI, the network shall provide mapping information to the HPLMN to the UE together with the Configured S-NSSAI or Allowed NSSAI if different values are used. Q2: If the answer of Q1 is yes, which S-NSSAI(s) (i.e. either HPLMN S-NSSAI or S-NSSAI of EHPLMN, or both) should be used for I-SMF, A-SMF or other NFs selection? SA2 answer: SA2 agreed that the S-NSSAI of the Serving PLMN is used to select the I-SMF and S-NSSAI of the mapped S-NSSAI in the HPLMN is used to select the SMF for the PDU Session if a mapped S-NSSAI value of the HPLMN is present in the Allowed NSSAI. Q3: If the answer of Q1 is yes, how is the admission control of the HPLMN S-NSSAI and the mapped S-NSSAI of EHPLMN performed in the 5GC? Are there two NSACFs, i.e. one for HPLMN and the other for EHPLMN? SA2 answer: When different S-NSSAI values are used for HPLMN and EHPLMN, the (I-)SMF performs NSAC procedures separately for EHPLMN S-NSSAI and HPLMN S-NSSAI. Whether to deploy one NSACF (supporting both S-NSSAIs) or two NSACFs is per operator deployment. Please see the agreed CR from Rel-18 as attached. --- Related CRs in 5059, 5060, 5061, 5062
Plenary	5020	LS in Rel-19 Reply LS on RAN support of QoS monitoring capability	SA WG2	S2-2411247 To: CT WG4 CC: CT WG3 Contact: ZTE --- SA2 thanks CT WG4 for the LS on RAN support of QoS monitoring capability. SA2 has discussed the CT4 agreed CR and would like to ask the following questions: Question 1: Why is the RAN QoS monitoring capability value "UNKNOWN" needed. What is the expected SMF behaviour compared to receiving "NOT_SUPPORTED" or no indication at all? Question 2: According to SA2’s understanding of the CT4 CR, it seems that there is an inconsistency between clause 6.1.6.2.9 and 6.1.6.2.11 in the CT4 agreed CR. In the clause 6.1.6.2.9 (Type: PduSessionCreateData), the IE “qosMonitoringPdSupported” shall be present if the QME feature is supported by the I-SMF/V-SMF and SMF, and if the information is available. In the clause 6.1.6.2.11 (Type: HsmfUpdateData). In Inter-AMF mobility with I-SMF/V-SMF change with the target AMF not supporting the QME feature, in which case the attribute with value "UNKNOWN" shall be sent. When the AMF does not support QME feature and I/V-SMF and SMF support QME feature, the behaviour seems to be inconsistent: For the PDU session establishment, the I/V-SMF does not send this IE to (h)SMF. For the HO to the target AMF not supporting QME, the I/V-SMF send "UNKNOWN" to (h)SMF. --- Reply LS in 5268
Plenary	5024	LS in Rel-19 LS on the supporting 5G ProSe multi-hop Relays	CT1	C1-246002 To: SA2 CC: CT3, CT4 Contact: CATT --- ... In summary, CT1 kindly ask SA2 to provide answers to the following questions: Q1- Can the Rel-19 multi-hop relay 5G ProSe capabilities be associated with the existing pre-Rel-19 5G Prose capabilities? Q2- Can the Rel-19 multi-hop relay 5G ProSe Requested UE policies bits be associated with the existing pre-Rel-19 5G Prose Requested UE policies? Q3- Does "DHCP proxy" refer to DHCP relay agent as defined in related IETF RFCs, e.g. RFC 3046? --- Propose to note
Plenary	5025	LS in Rel-18 Reply LS on the maximum number of devices supported in SLPP	RAN2	R2-2409252 To: CT1 CC: CT4, SA2 Contact: vivo --- RAN2 thanks CT1 for the Reply LS on the maximum number of devices supported in SLPP. RAN2 will align with CT1 by clarifying that the maximum number of other UEs (i.e., UEs 2 to n) for sidelink positioning is also 63 in the stage 2 specification (see attachment). ---
Plenary	5027	LS in Rel-18 LS on request for IMS Data Channel related clarifications	SA3-LI	S3i240707 To: SA2, SA4, CT1, CT4 CC: SA3, CT3 Contact: Nokia --- … SA3 LI kindly requests SA2, SA4, CT1, CT4 to clarify and confirm the following: The IMS-AS in the remote UE’s side of the IMS session always notifies the DCSF about the IMS Data Channel related event notifications, irrespective which side initiates the IMS Data Channel setup (originating party or the terminating party). The statement 1 is true even if the local UE and the remote UE are in the same CSP domain. In addition to notifying the DCSF, the Remote UE’s network would also have an MF on the IMS Data Channel media. In the SessionEvenNotifictions, how are the Calling Identity and Called Identity populated by the IMS AS (i.e. which SIP headers from the initial INVITE, re-INVITE are used)? If call forwarding occurs at the terminating side (clause 10.123, TS 24.186), the two users present on the established IMS session (i.e. after the successful redirection) are: Original calling party. Redirected-to party. 5-1: Assuming Calling Identity is the original calling party, what would the Called Identity be that IMS AS sends in the session Event Notification to the DCSF, i.e.redirecting party identity or the redirected-to party identity? 5-2: If it is the former, what would be purpose including the Called Identity in the Session Event Notification, specially, when that user is not using the IMS Data Channel? 5-3: If it is the later, does the IMS-AS in the originating network know about the redirected-to party identity? 5-4: Do the MF in the Local UE side and Remote UE side have same role – e.g., MF in the UDP Proxy or HTTP Proxy? 2. Actions: To SA2, SA4, CT1, CT4: To clarify whether the IMS Data Channel architecture requires the DCSF and MF to be present in the Remote IMS. Does the figure 6.2.10.1-1 infer DCSF is not notified in the Remote UE’s side of the IMS network (meaning a conflict with the TS 24.186)? Confirm whether SA3-LI understanding as noted in 1, 2 and 3 are correct. Kindly clarify and provide answers to points/questions: 4, 5-1, 5-2, 5-3 and 5-4. ---
Plenary	5028	LS in Rel-19 Reply LS on UE-Satellite-UE Communication Architectures	SA3-LI	S3i240752 To: SA2 CC: SA3, CT1, CT3, CT4 Contact: Nokia --- SA3-LI thanks SA2 for their LS and the clarification in pursuing the UE-Satellite-UE communication architectures. Point number 1 In reference to point number 1 (where the IMS-AGW would be on-board the satellite), SA3-LI would update LI specifications to accommodate the possibility of a change in the IMS-AGW during an active IMS Session. SA3 LI believes that LI can be performed as long as P-CSCF is in control of the IMS-AGW change. Point number 2 In reference to point number 2 (where an intermediate UPF (I-UPF) is inserted to the media path with no IMS-AGW for a UE-Satellite-UE communication) the LI specifications for IMS LI will have to be enhanced. SA3-LI believes to support such an architecture, P-CSCF needs sufficient information to isolate the media flow packets for all IMS sessions, at any time during the IMS session. In SA3-LI understanding, the following are required for all UE-Satellite-UE IMS sessions, independent of LI: P-CSCF is able to identify the I-UPF. For this, I-UPF address/identity will be made available to the P-CSCF. P-CSCF is able to identify the tunnel used for the IMS media flow. For this, the tunnel ID used at the I-UPF will be made available to the P-CSCF. If a point-to-point tunnel is used (e.g. on N6), then the UDP port number along with the IP address of the I-UPF shall be made available to the P-CSCF. P-CSCF is able to identify the UDP port number (RTP) used for the media packets. Port numbers from the access side (N3) and the core-side (N6) will be available. P-CSCF is able to identify the QoS flow. For this, the QFI associated with QoS flow will be made available to the P-CSCF. SA3-LI kindly asks SA2 to confirm the above understanding. --- Propose to note
5291	LS in Reply-LS on GSMA CVD-2023-0069 5G Core Network Attacks	SA3	S3-244845 To: CT4 CC: GSMA CVD Contact: Huawei --- SA3 would like to thank CT4 for the LS on Reply-LS on GSMA CVD-2023-0069 5G Core Network Attacks. SA3 confirms that SA3 has same understanding with CT4. --- Propose to note
4.2	Outgoing liaisons
Plenary	5041	LS out Rel-18 Reply LS on N32-f lifetime and reconnection	NTT DOCOMO	C4-244021 To: GSMA 5GMRR, NRG CC: SA3 Overlapping with 5249
Plenary	5249	LS out Rel-18 Reply LS on N32-f lifetime and reconnection	Nokia	5GMRR Doc 45_07 To: GSMA 5GMRR Cc: SA3
Plenary	5077	LS out Rel-18 LS on PDU Set Information	Lenovo	To: SA WG4 Cc: CT WG3, SA WG2
Plenary	5083	LS out Rel-19 Reply LS on Transport level marking based on PDU Set Importance	Nokia	S2-2410948 To: SA2 CC: Overlapping with 5197
Plenary	5197	LS out Rel-19 Reply LS on Transport level marking based on PDU Set Importance	CATT	S2-2410948 To: SA2 Cc:
Plenary	5106	LS out Rel-18 LS on 5G Trace to support UE level measurement clarification	China Mobile	S5-244661 To: SA5 Cc: CT3
Plenary	5139	LS out Rel-19 LS on optimizations to the subscription of UPF events	Ericsson	To: SA2, CT3 CC:
Plenary	5196	LS out Rel-17 LS on UUAA Unsubscribe procedure	CATT	To: SA2 Cc: CT3
Plenary	5202	LS out Rel-19 LS on PS Data Off and Positioning over user plane connection	Huawei	To: SA2 Cc: CT1
Plenary	5268	LS out Reply LS on RAN support of QoS monitoring capability	Huawei	S2-2411247 To: SA WG2 Cc: CT WG3
Check of Approved Output Documents
5011	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
29.518 0 Rel16 API version and External doc update	Ericsson	Email approval	CR possibly needed Email approval
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 Impact introduced by C4-245032
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 Impact introduced by C4-245032
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 Impact introduced by C4-245032
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 Impact introduced by C4-245033
29.505 0 Rel18 External doc update	China Mobile	Email approval	CR possibly needed Email approval Impact introduced by C4-245229
29.509 0 Rel18 API version and External doc update	Orange	Email approval	CR possibly needed Email approval Impact introduced by C4-245033
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 Impact introduced by C4-245033
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 Impact introduced by C4-245034
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 Impact introduced by C4-245034
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	5120	CR 29.518 1140 Rel-16 Correction for deferred 5GC-MT-LR procedure	Huawei	WI TEI16, 5G_eLCS CAT F Overlapping with 5183
Plenary	5121	CR 29.518 1141 Rel-17 Correction for deferred 5GC-MT-LR procedure	Huawei	WI TEI16, 5G_eLCS CAT A
Plenary	5122	CR 29.518 1142 Rel-18 Correction for deferred 5GC-MT-LR procedure	Huawei	WI TEI16, 5G_eLCS CAT A
Plenary	5123	CR 29.518 1143 Rel-19 Correction for deferred 5GC-MT-LR procedure	Huawei	WI TEI16, 5G_eLCS CAT A
Plenary	5183	CR 29.518 1147 Rel-16 Correction for the deferred 5GC-MT-LR procedure	CATT, Ericsson	WI 5G_eLCS CAT F
Plenary	5184	CR 29.518 1148 Rel-17 Correction for the deferred 5GC-MT-LR procedure	CATT, Ericsson	WI 5G_eLCS CAT A
Plenary	5185	CR 29.518 1149 Rel-18 Correction for the deferred 5GC-MT-LR procedure	CATT, Ericsson	WI 5G_eLCS CAT F
Plenary	5186	CR 29.518 1150 Rel-19 Correction for the deferred 5GC-MT-LR procedure	CATT, Ericsson	WI 5G_eLCS 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]
Plenary	5208	CR 29.230 0715 Rel-17 Remove the additional MDT-Configuration-NR	Huawei, MCC	WI TEI17 CAT F
Plenary	5209	CR 29.230 0716 Rel-18 Remove the additional MDT-Configuration-NR	Huawei, MCC	WI TEI17 CAT A
Plenary	5210	CR 29.571 0604 Rel-17 Updates on the n3gaLocation	Huawei	WI TEI17 CAT F
Plenary	5211	CR 29.571 0605 Rel-18 Updates on the n3gaLocation	Huawei	WI TEI17 CAT A
Plenary	5212	CR 29.571 0606 Rel-19 Updates on the n3gaLocation	Huawei	WI TEI17 CAT A
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]
Plenary	5032	CR 29.503 1349 Rel-17 Correction for SNN related to 5G NSWO	Nokia	WI NSWO_5G CAT F
Plenary	5033	CR 29.503 1350 Rel-18 Correction for SNN related to 5G NSWO	Nokia	WI NSWO_5G CAT A
Plenary	5034	CR 29.503 1351 Rel-19 Correction for SNN related to 5G NSWO	Nokia	WI NSWO_5G CAT A
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	5059	CR 29.531 0226 Rel-18 Clarify slice mapping for non-roaming case	ZTE	WI TEI18 CAT F
Main	5060	CR 29.531 0227 Rel-19 Clarify slice mapping for non-roaming case	ZTE	WI TEI18 CAT A
Main	5061	CR 29.502 0817 Rel-18 Provision of slice mapping information to the (I-)SMF	ZTE	WI TEI18 CAT F
Main	5062	CR 29.502 0818 Rel-19 Provision of slice mapping information to the (I-)SMF	ZTE	WI TEI18 CAT A
Main	5063	CR 29.536 0136 Rel-18 Clarify NSAC procedures for EHPLMN S-NSSAI case	ZTE	WI TEI18, eNS_Ph3 CAT F
Main	5078	CR 29.502 0819 Rel-18 Update the Nsmf_PDUSession API to support UE level measurement trace	China Mobile	WI TEI18 CAT F
Main	5081	CR 29.502 0820 Rel-19 Update the Nsmf_PDUSession API to support UE level measurement trace	China Mobile	WI TEI18 CAT A WIC to be corrected
Breakout	5079	CR 29.503 1359 Rel-18 Update the Nudm_SDM to support UE level measurements trace	China Mobile	WI TEI18 CAT F
Breakout	5082	CR 29.503 1360 Rel-19 Update the Nudm_SDM to support UE level measurements trace	China Mobile	WI TEI18 CAT A WIC to be corrected
Breakout	5125	CR 29.562 0154 Rel-18 Reference correction	China Mobile	WI TEI18 CAT F
Main	5174	CR 29.502 0823 Rel-18 204 Response Code for HO Cancel and Failure	Ericsson, Verizon	WI TEI18 CAT F
Main	5175	CR 29.502 0824 Rel-19 204 Response Code for HO Cancel and Failure	Ericsson, Verizon	WI TEI18 CAT A
Main	5176	CR 29.502 0825 Rel-18 Mapped Slices Support for Non-Roaming Scenarios	Ericsson	WI TEI18 CAT F
Main	5177	CR 29.502 0826 Rel-19 Mapped Slices Support for Non-Roaming Scenarios	Ericsson	WI TEI18 CAT A
Main	5277	CR 29.244 0904 Rel-18 Support of Trace Reporting Consumer URI	Huawei	WI TEI18, NR_SON_MDT-Core CAT F
Main	5278	CR 29.244 0905 Rel-18 Support of UE level measurements configuration	Huawei	WI TEI18, PM_KPI_5G_Ph3 CAT F
Plenary	5279	CR 29.273 0553 Rel-18 Support of Trace Reporting Consumer URI	Huawei	WI TEI18, NR_SON_MDT-Core CAT F
Plenary	5280	CR 29.571 0612 Rel-18 Correction on MDT configuration for MN node	Huawei	WI TEI18, 5GMDT_Ph2 CAT F
Plenary	5281	CR 29.571 0613 Rel-19 Correction on MDT configuration for MN node	Huawei	WI TEI18, 5GMDT_Ph2 CAT A
18.5	CT aspects of NBI18 [NBI18]
18.6	CT aspects of SBIProtoc18 [SBIProtoc18]
Plenary	5039	CR 29.573 0217 Rel-18 Keepalive of TLS Session for N32-f	NTT DOCOMO	WI SBIProtoc18 CAT F Overlapping with 5247
5040	CR 29.573 0218 Rel-19 Keepalive of TLS Session for N32-f	NTT DOCOMO	revised to C4-245284	WI SBIProtoc18 CAT A
Plenary	5284	CR 29.573 0218 Rel-19 Keepalive of TLS Session for N32-f	NTT DOCOMO	WI SBIProtoc18 CAT A
Plenary	5247	CR 29.573 0219 Rel-18 N32-f Keepalive	Nokia	WI SBIProtoc18 CAT F
Plenary	5248	CR 29.573 0220 Rel-19 N32-f Keepalive	Nokia	WI SBIProtoc18 CAT A
Breakout	5229	CR 29.503 1365 Rel-18 CAG information does not allow multiple time periods per allowed CAG ID	Ericsson	WI SBIProtoc18 CAT F WIC to be corrected Also impacts TS29505_Subscription_Data.yaml TS29518_Namf_Communication.yaml
Breakout	5230	CR 29.503 1366 Rel-19 CAG information does not allow multiple time periods per allowed CAG ID	Ericsson	WI SBIProtoc18 CAT A
5249	LS out Rel-18 Reply LS on N32-f lifetime and reconnection	Nokia	Moved to 4.2
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]
Main	5276	CR 29.536 0138 Rel-18 NSAC handling on maximum number of UEs with at least one PDU Session/PDN Connection in Hierarchical architecture	Huawei	WI eNSAC CAT F
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]
Breakout	5187	CR 29.572 0300 Rel-18 Update to support NRPPa related measurements	CATT	WI 5G_eLCS_Ph3 CAT F Overlapping with 5203
Breakout	5188	CR 29.572 0301 Rel-19 Update to support NRPPa related measurements	CATT	WI 5G_eLCS_Ph3 CAT A
Breakout	5203	CR 29.572 0302 Rel-18 Updates on the Time Windows	Huawei	WI 5G_eLCS_Ph3 CAT F
Breakout	5204	CR 29.572 0303 Rel-19 Updates on the Time Windows	Huawei	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]
Breakout	5160	CR 29.175 0031 Rel-18 Clarification on the condition of notification	Huawei	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]
18.59	Enhancements on Service-based support for SMS in 5GC [eSMS_SBI]
18.60	CT aspects of eNA_Ph3 [eNA_Ph3]
Plenary	5108	CR 29.510 1093 Rel-18 Addition of missing service	Huawei	WI eNA_Ph3 CAT F
Plenary	5109	CR 29.510 1094 Rel-19 Addition of missing service	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]
18.65	CT aspects of Enhancement of Network Slicing Phase 3 [eNS_Ph3]
Plenary	5048	CR 29.503 1354 Rel-18 Applicability of Slice Deregistration Inactivity Timer	ZTE	WI eNS_Ph3 CAT F overlapping with 5245 Need to decide whether this change should go back to Rel-18
Plenary	5049	CR 29.503 1355 Rel-19 Applicability of Slice Deregistration Inactivity Timer	ZTE	WI eNS_Ph3 CAT A
Plenary	5245	CR 29.503 1371 Rel-19 Clarification on access type of Slice Deregistration Inactivity Timer	Nokia	WI TEI19 CAT F
Plenary	5050	CR 29.571 0597 Rel-18 Applicability of Timers for Slice Usage Control	ZTE	WI eNS_Ph3 CAT F overlapping with 5246 Need to decide whether this change should go back to Rel-18
Plenary	5051	CR 29.571 0598 Rel-19 Applicability of Slice Usage Control Info	ZTE	WI eNS_Ph3 CAT A
Plenary	5246	CR 29.571 0607 Rel-19 Clarification on Slice usage control information	Nokia	WI TEI19 CAT F
18.66	CT aspects of XRM [XRM]
Main	5072	discussion Rel-18 Discussion on PDU Set Information (PSI)	Lenovo
Main	5073	CR 29.571 0591 Rel-18 Correction of RtpHeaderExtInfo	Lenovo	WI XRM CAT F
Main	5074	CR 29.571 0592 Rel-19 Correction of RtpHeaderExtInfo	Lenovo	WI XRM CAT A
Main	5075	CR 29.244 0885 Rel-18 Correction of RTP Header Extension Additional Information	Lenovo	WI XRM CAT B
Main	5076	CR 29.244 0886 Rel-19 Correction of RTP Header Extension Additional Information	Lenovo	WI XRM CAT A
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]
Breakout	5038	CR 29.503 1314 Rel-19 Reauthentication pending	Nokia	WI TEI19, HN_Auth CAT F overlapping with 5056 (and mirror), 5231 Need to decide whether this change should go back to Rel-18
Breakout	5056	CR 29.503 1356 Rel-18 Add UE unreachable case of Re-AuthenticationNotification	ZTE	WI HN_Auth CAT F
Breakout	5057	CR 29.503 1357 Rel-19 Add UE unreachable case of Re-AuthenticationNotification	ZTE	WI HN_Auth CAT A
Breakout	5231	CR 29.503 1367 Rel-19 Reauthentication reattempt in another access	Ericsson	WI HN_Auth CAT B CAT B CR to frozen release is not desired
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
Plenary	5031	WID new Rel-19 New WID on CT aspects of energy efficiency and energy saving	Samsung
Plenary	5105	WID new Rel-19 New WID on CT aspects of 5G NR Femto	NTT DOCOMO	Revision of agreed WID from CT4#125
Plenary	5141	WID new Rel-19 New WID on Reducing Information Exposure over SBI	Samsung	UID 1060003 was allocated on CT4#125
Plenary	5166	WID new Rel-19 New WID on CT Aspects on TEI19_DLPMRl	Ericsson
Plenary	5195	WID new Rel-19 New WID on CT aspects of PRU Usage Extension supported by Core Network	CATT
19.2.2	CT4 Supported WIDs
Plenary	5084	WID new Rel-19 New WID on CT aspects of Extended Reality and Media service (XRM) Phase 2	Nokia	Revision of endorsed WID from CT4#125
Plenary	5199	discussion Rel-19 Discussion on the stage 2 status of AmbientIoT	Huawei
Plenary	5200	WID new Rel-19 New WID on CT aspects of Architecture support of Ambient power-enabled Internet of Things	Huawei
19.3	Revised WIDs for Rel-19
19.3.1	CT4 Led WIDs
Plenary	5085	WID revised Rel-19 CT aspects of enhancement of support for Edge Computing in 5G Core network - Phase 3	Nokia
Plenary	5150	WID revised Rel-19 revised WID on MPS4msg	Peraton Labs, CISA ECD, AT&T
19.3.2	CT4 Supported WIDs
Plenary	5107	WID revised Rel-19 Enhancement of controlling RAT utilization	VODAFONE Group Plc
Plenary	5194	WID revised Rel-19 Revised WID on CT aspects of Proximity-based Services in 5GS Phase 3	CATT
Plenary	5223	WID revised Rel-19 Revised WID on CT aspects of ProSe support in NPN	China Telecomunication Corp.
Plenary	5286	WID revised Rel-19 Revised WID on CT aspects of Multi-Access (ATSSS_Ph4)	Apple
19.4	TEI19 [TEI19]
Main	5026	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
5038	CR 29.503 1314 Rel-19 Reauthentication pending	Nokia	Moved to 18.75	WI TEI19, HN_Auth CAT F
Plenary	5080	CR 29.571 0599 Rel-19 Update the MeasurementType to support UE level measurement	China Mobile	WI TEI19 CAT B
5081	CR 29.502 0820 Rel-19 Update the Nsmf_PDUSession API to support UE level measurement trace	China Mobile	Moved to 18.4	WI TEI19 CAT A
5082	CR 29.503 1360 Rel-19 Update the Nudm_SDM to support UE level measurements trace	China Mobile	Moved to 18.4	WI TEI19 CAT A
Main	5086	CR 29.244 0887 Rel-19 GTP-U Path QoS Control Information	Nokia, MCC	WI TEI19, 5G_URLLC CAT F
Main	5087	CR 29.281 0135 Rel-19 PDU Session container for non-3GPP accesses	Nokia	WI TEI19, 5GS_Ph1-CT CAT F
Plenary	5088	CR 29.510 1090 Rel-19 Access Token Request parameters	Nokia	WI TEI19, 5GS_Ph1-CT CAT F
Plenary	5115	CR 29.510 1098 Rel-19 Update access token	Huawei	WI TEI19 CAT B
Plenary	5116	CR 29.510 1099 Rel-19 Missing re-used Data Type	Huawei	WI TEI19 CAT F
Breakout	5126	CR 29.503 1317 Rel-19 Additional PGW IP Address	Nokia	WI TEI19 CAT F
Breakout	5130	CR 29.515 0192 Rel-19 Addition of coarse location information of UE in Ngmlc_Location service response to NEF	CEWiT	WI 5G_eLCS_ph2 CAT B
Plenary	5132	CR 23.527 0089 Rel-19 PFCP sessions excluded from the restoration upon a SMF failure with SMF set being deployed	Ericsson	WI TEI19 CAT B
Plenary	5133	CR 29.244 0895 Rel-19 PFCP sessions excluded from the restoration upon a SMF failure with SMF set being deployed	Ericsson	WI TEI19 CAT B
Plenary	5138	CR 29.244 0896 Rel-19 Extra reference to 3GPP TS 29.512	Ericsson	WI TEI19 CAT F
Plenary	5142	discussion Rel-19 5G NF selection based on Service Reliability	Samsung
Breakout	5167	CR 29.515 0193 Rel-19 NRPPa Periodic Indication	Ericsson	WI TEI19_DLPMR CAT B
Main	5168	CR 29.518 1145 Rel-19 NRPPa Periodic Indication	Ericsson	WI TEI19_DLPMR CAT B
Main	5169	CR 29.572 0299 Rel-19 NRPPa Periodic Indication	Ericsson	WI TEI19_DLPMR CAT B
Breakout	5178	CR 29.503 1362 Rel-19 DNN and Slice information for Communication Failure Event	Ericsson	WI TEI19 CAT F
Main	5179	CR 29.518 1146 Rel-19 DNN and Slice information for Communication Failure Event	Ericsson	WI TEI19 CAT F
Plenary	5201	discussion Rel-19 Discussion on PS Data Off and Positioning over user plane connection	Huawei
5202	LS out Rel-19 LS on PS Data Off and Positioning over user plane connection	Huawei	Moved to 4.2
Breakout	5213	CR 29.572 0305 Rel-19 Support of PRU Usage Extension	Huawei	WI TEI19 CAT B
Main	5220	CR 29.518 1151 Rel-19 Correction of feature negotiation	Samsung Electronics Iberia SA	WI TEI19_NetShare CAT F Work item code to be corrected
5245	CR 29.503 1371 Rel-19 Clarification on access type of Slice Deregistration Inactivity Timer	Nokia	Moved to 18.65	WI TEI19 CAT F
5246	CR 29.571 0607 Rel-19 Clarification on Slice usage control information	Nokia	Moved to 18.65	WI TEI19 CAT F
Main	5250	CR 29.518 1154 Rel-19 incorrect namf-comm resouces name	Nokia	WI TEI19 CAT F
Main	5251	CR 29.518 1155 Rel-19 Incorrect namf-comm service name	Nokia	WI TEI19 CAT F
Breakout	5252	CR 29.572 0310 Rel-19 Incorrect resource URI definition	Nokia	WI TEI19 CAT F
Breakout	5253	CR 29.572 0311 Rel-19 Incorrect usage of HTTP for Nlmf_Broadcast service	Nokia	WI TEI19 CAT F
Breakout	5254	CR 29.572 0312 Rel-19 Eliminate the duplicate reference	Nokia	WI TEI19 CAT F
Plenary	5255	CR 29.573 0221 Rel-19 Incorrect n32fContextId name	Nokia	WI TEI19 CAT F
Main	5269	CR 29.531 0228 Rel-19 Correction on enumerations	Huawei	WI TEI19 CAT F
Main	5270	CR 29.536 0137 Rel-19 Correction on EacNotification data type	Huawei	WI TEI19 CAT F
Plenary	5271	CR 29.571 0609 Rel-19 Correction on Plmn Data type	Huawei	WI TEI19 CAT F
Plenary	5272	CR 29.571 0610 Rel-19 Add description in data types OpenAPI definition	Huawei	WI TEI19 CAT F
Plenary	5273	CR 29.571 0611 Rel-19 Support of Network Slice Area Scope of MDT	Huawei	WI TEI19, NR_ENDC_SON_MDT_Ph4-Core CAT B
Plenary	5274	CR 29.573 0222 Rel-19 Updates of the Roaming Intermediary Procedures	Huawei	WI TEI19 CAT F
Main	5275	CR 29.502 0828 Rel-19 Support of V-SMF procedures for Release SM context operation	Huawei	WI TEI19 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]
Breakout	5022	CR 29.503 1340 Rel-19 Enhancing Parameter Provisioning with Static IP address	Ericsson, Huawei, Nokia	WI TEI19_IP_SP_EXP CAT B
19.7	CT aspects of Providing per-subscriber VLAN instructions from UDM and DN-AAA [TEI19_VLANSUB]
Plenary	5069	CR 29.244 0884 Rel-19 Description for handling of allowed VLAN tags and use of VLAN Handling Information in SMF	Ericsson	WI TEI19_VLANSUB CAT B
Plenary	5070	CR 29.503 1358 Rel-19 VLAN tag handling information and allowd VLAN Tags	Ericsson	WI TEI19_VLANSUB CAT B overlapping with 5215
Plenary	5215	CR 29.503 1363 Rel-19 Support of VLAN handling instructions in SM subscription data	Huawei	WI TEI19_VLANSUB CAT B
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	5021	CR 29.503 1319 Rel-19 Shared Monitoring Suspension	Nokia, Ericsson	WI SBIProtoc19 CAT B
Breakout	5035	CR 29.503 1352 Rel-19 Enum indentation	Nokia	WI SBIProtoc19 CAT F
Breakout	5036	CR 29.505 0524 Rel-19 Enum indentation	Nokia	WI SBIProtoc19 CAT F
Breakout	5037	CR 29.503 1353 Rel-19 Additional Shared Snssai Infos Ids in SMF Selection Subscription Data	Nokia, Verizon	WI SBIProtoc19 CAT B
Plenary	5058	CR 29.510 1087 Rel-19 Clarify the case of the same S-NSSAI value used across different PLMNs	ZTE	WI SBIProtoc19 CAT F
Plenary	5104	CR 29.501 0170 Rel-19 Query parameter clarification	Nokia	WI SBIProtoc19 CAT F
Plenary	5128	CR 29.510 1046 Rel-19 Reducing Information Exposure using Resource Content Filters	Nokia	WI SBIProtoc19 CAT B
Breakout	5131	CR 29.504 0293 Rel-19 UP Path Change event outcome feature addition in UDR Feature negotiation table	CEWiT	WI SBIProtoc19 CAT B
Plenary	5140	CR 29.571 0602 Rel-19 MdtConfiguration	Nokia	WI SBIProtoc19 CAT F
Plenary	5170	CR 29.510 1106 Rel-19 Enhancement to P-CSCF Selection	Ericsson	WI SBIProtoc19 CAT B
Plenary	5171	CR 29.510 1107 Rel-19 Support to UPF Selection for 2G/3G Access	Ericsson	WI SBIProtoc19 CAT B
Main	5172	CR 29.502 0821 Rel-19 N1/N2 SM Rejection in 502 Response	Ericsson	WI SBIProtoc19 CAT B
Breakout	5193	CR 29.336 0189 Rel-19 Correction to the code of Include-Identifiers AVP	CATT	WI SBIProtoc19 CAT D
Plenary	5222	CR 29.510 1082 Rel-19 Canary test procedure clarifications	Ericsson	WI SBIProtoc19 CAT F
Plenary	5224	CR 29.510 1109 Rel-19 Canary test enhancements for preferred-xxx discoveries	Ericsson	WI SBIProtoc19 CAT B
Plenary	5225	CR 29.501 0171 Rel-19 Presence condition in an Information Element	Ericsson	WI SBIProtoc19 CAT F
Breakout	5227	CR 29.503 1364 Rel-19 Correction to Stale-Check Callback URI	Ericsson	WI SBIProtoc19 CAT F
Breakout	5228	CR 29.505 0525 Rel-19 AF-specific UE identifiers shall not be used for AF ID authorization	Ericsson	WI SBIProtoc19 CAT F
Breakout	5232	CR 29.503 1368 Rel-19 PP Data Entry is to be used when multiple AFs are expected to provision the same data	Ericsson	WI SBIProtoc19 CAT F
Breakout	5233	CR 29.503 1369 Rel-19 Addition of GET method to the PP Data resource	Ericsson	WI SBIProtoc19 CAT F
Breakout	5283	CR 29.503 1372 Rel-19 af-service-id attribute is not used in Identifier Translation procedure	Ericsson	WI SBIProtoc19 CAT F
19.11	Subscriber Data Migration [SUBDMIG]
Plenary	5173	CR 29.502 0822 Rel-19 UDM Group Re-Discovery and Synchronization Indications	Ericsson	WI SUBDMIG CAT B
Plenary	5234	CR 29.510 1110 Rel-19 Data restoration notification type used for subscriber data migration	Ericsson	WI SUBDMIG CAT F
Plenary	5235	CR 23.527 0090 Rel-19 Time-based restoration with subscriber data migration	Ericsson	WI SUBDMIG CAT B
Plenary	5237	CR 29.503 1370 Rel-19 Time-based restoration	Ericsson	WI SUBDMIG CAT B
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]
Breakout	5042	CR 29.503 1318 Rel-19 RAT restriction by serving PLMN policy	Nokia	WI ECRATU CAT B
Breakout	5206	CR 29.272 0866 Rel-19 RAT utilization control	Huawei	WI ECRATU CAT B
Breakout	5207	CR 29.230 0714 Rel-19 Add new AVPs for RAT utilization control	Huawei	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	5055	CR 29.500 0452 Rel-19 Clarification on SBI Header Setting	ZTE	WI TEI19_NetShare CAT B
Plenary	5181	CR 29.531 0223 Rel-19 Resolve EN for Network Slice Selection in Participating Operator Network	Ericsson, Nokia	WI TEI19_NetShare CAT B
Plenary	5256	CR 29.502 0827 Rel-19 Support of Indirect Network Sharing deployment	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	5257	CR 29.510 1113 Rel-19 Access token for RVAS	Nokia	WI TEI19_RVAS CAT B
19.24	CT Aspects of On-demand broadcast of GNSS assistance enhancement [TEI19_OBGAD]
Main	5023	CR 29.518 1121 Rel-19 Support of on-demand broadcast of GNSS assistance data	China Mobile, Huawei, Ericsson, Nokia	WI TEI19_OBGAD CAT B
5180	CR 29.518 1121 Rel-19 Support of on-demand broadcast of GNSS assistance data	China Mobile, Huawei, Ericsson, Nokia	withdrawn	WI TEI19_OBGAD CAT B
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]
Plenary	5047	CR 29.504 0292 Rel-19 N6 delay consideration	Nokia	WI eEDGE_5GC_Ph3 CAT B
Plenary	5091	CR 29.510 1091 Rel-19 N6 delay measurement protocols	Nokia	WI eEDGE_5GC_Ph3 CAT B Overlapping with 5118
Plenary	5118	CR 29.510 1101 Rel-19 Supported protocol to measure N6 delay	Huawei	WI eEDGE_5GC_Ph3 CAT B
Plenary	5092	CR 29.244 0888 Rel-19 N6 Delay Measurement and Reporting	Nokia	WI eEDGE_5GC_Ph3 CAT B
Plenary	5089	CR 29.571 0593 Rel-19 Local Offloading Information	Nokia	WI eEDGE_5GC_Ph3 CAT B
Plenary	5090	CR 29.502 0810 Rel-19 N11 and N16a enhancements for I-SMF based Local Offloading Management	Nokia	WI eEDGE_5GC_Ph3 CAT B
Plenary	5117	CR 29.510 1100 Rel-19 Discovery of SMF based on Local Offloading Management	Huawei	WI eEDGE_5GC_Ph3 CAT B
19.27	MPS for IMS Messaging and SMS services [MPS4msg]
5143	CR 23.540 0021 Rel-19 MPS for Messaging SMS over NAS SBI alignment	Peraton Labs, CISA ECD, AT&T	withdrawn	WI MPS4msg CAT B
Breakout	5144	CR 29.228 0700 Rel-19 MPS for IMS Messaging Indicator on Cx	Peraton Labs, CISA ECD, AT&T	WI MPS4msg CAT B
5145	CR 29.272 0863 Rel-19 MPS for Messaging Indication on s6a	Peraton Labs, CISA ECD, AT&T	withdrawn	WI MPS4msg CAT B
Breakout	5146	CR 29.336 0187 Rel-19 29.336 MPS for Messaging Indicator on S6t	Peraton Labs, CISA ECD, AT&T	WI MPS4msg CAT B
Breakout	5147	CR 29.338 0059 Rel-19 29.338 MPS for Messaging Indicator on S6c and SGd	Peraton Labs, CISA ECD, AT&T	WI MPS4msg CAT B
Breakout	5148	CR 29.503 1361 Rel-19 MPS for Messaging Indicator in UDM	Peraton Labs, CISA ECD, AT&T	WI MPS4msg CAT B
Breakout	5149	CR 29.562 0157 Rel-19 29.562 MPS for IMS Messaging Indication on Nhss	Perspecta Labs, CISA ECD, AT&T	WI MPS4msg CAT B
Breakout	5151	discussion Rel-19 Discussion on MPS for Messaging	Peraton Labs, CISA ECD, AT&T
Breakout	5152	CR 23.540 0022 Rel-19 MPS priority for Messaging SMS over NAS SBI	Peraton Labs, CISA ECD, AT&T	WI MPS4msg CAT F
Breakout	5153	CR 29.272 0864 Rel-19 29.272 MPS for Messaging Indicator on S6a	Peraton Labs, CISA ECD, AT&T	WI MPS4msg CAT B
19.28	Identifying non-3GPP Devices Connecting behind a UE or 5G-RG [UIA_ARC]
Plenary	5071	Work Plan Rel-19 Work plan for UIA_ARC	InterDigital Communications
Plenary	5216	CR 23.003 0706 Rel-19 Identifiers of N3GPP device behind UE/5G-RG	Huawei	WI UIA_ARC CAT B
Plenary	5217	CR 29.504 0294 Rel-19 Support of non-3GPP device information	Huawei	WI UIA_ARC CAT B
Plenary	5289	CR 29.504 0296 Rel-19 Non3gppDevice feature	Nokia	WI UIA_ARC CAT B
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]
Main	5182	CR 29.518 1135 Rel-19 New AMF Event of Trajectory Tracking for USS Change Over	Ericsson, LG Electronics, Huawei	WI UAS_Ph3 CAT B
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]
Plenary	5190	CR 29.128 0084 Rel-19 Support monitoring event for store and forward operation	CATT	WI 5GSAT_Ph3_ARCH CAT B
Plenary	5191	CR 29.272 0865 Rel-19 Support monitoring event for store and forward operation	CATT	WI 5GSAT_Ph3_ARCH CAT B
Plenary	5192	CR 29.336 0188 Rel-19 Support monitoring event for store and forward operation	CATT	WI 5GSAT_Ph3_ARCH CAT B
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]
Plenary	5189	CR 29.510 1108 Rel-19 Support 5G ProSe L3 multi-hop relay services	CATT	WI 5G_ProSe_Ph3 CAT B
19.37	CT aspects of UPF enhancement for Exposure And SBA Phase 2 [UPEAS_Ph2]
Main	5029	CR 29.244 0882 Rel-19 Support of handling of headers in N4 interface	Ericsson	WI UPEAS_Ph2 CAT B
Main	5030	CR 29.564 0118 Rel-19 Event Exposure for Handling of Payload Headers Functionality	Ericsson	WI UPEAS_Ph2 CAT B
Plenary	5064	Work Plan Rel-19 Work Plan for UPEAS_Ph2	ZTE
5065	CR 29.510 1088 Rel-19 Clarify the handling if no UPF is discovered	ZTE	withdrawn	WI UPEAS_Ph2 CAT F
Main	5066	CR 29.564 0119 Rel-19 Clarify the handling if no UPF is discovered	ZTE	WI UPEAS_Ph2 CAT B
Main	5093	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 Overlapping with 5282
Main	5282	CR 29.564 0112 Rel-19 Supporting UE NAT Mapping Event Exposure	Ericsson	WI UPEAS_Ph2 CAT B
Main	5137	CR 29.564 0120 Rel-19 UPF notifying the termination of the UPF event subscription	Ericsson	WI UPEAS_Ph2 CAT B
Plenary	5198	CR 29.503 1320 Rel-19 Required and/or Preferred UPF functionalities in subscription data	Ericsson, Nokia, Huawei	WI UPEAS_Ph2 CAT B Both of 5198 and 5285 are revision of C4-244545 (agreed CR from CT4#125)
Plenary	5285	CR 29.503 1320 Rel-19 Required and/or Preferred UPF functionalities in subscription data	[Ericsson, Nokia, Huawei], Samsung	WI UPEAS_Ph2 CAT B Both of 5198 and 5285 are revision of C4-244545 (agreed CR from CT4#125)
Main	5265	CR 29.244 0901 Rel-19 PFCP session due to UPF relocation	Huawei	WI UPEAS_Ph2 CAT F
Plenary	5288	CR 29.504 0295 Rel-19 Introduction of Handling of Payload Headers feature	Ericsson	WI UPEAS_Ph2 CAT B
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	5067	CR 29.510 1089 Rel-19 Update of NWDAF discovery	ZTE	WI AIML_CN CAT B Overlapping with 5111, 5164
Plenary	5111	CR 29.510 1096 Rel-19 New capability of MTLF	Huawei	WI AIML_CN CAT B
Plenary	5164	CR 29.510 1104 Rel-19 Providing an indication of supporting model training for LMF-based AI/ML Positioning during NRF registration	vivo	WI AIML_CN CAT B
Plenary	5110	CR 29.510 1095 Rel-19 New LMF service	Huawei	WI AIML_CN CAT B Overlapping with 5240
Plenary	5240	CR 29.510 1111 Rel-19 Add the nlmf_dataexposure service to the service name list	Nokia	WI AIML_CN CAT B
Plenary	5112	CR 29.510 1097 Rel-19 Supporting vertical federated learning	Huawei	WI AIML_CN CAT B Overlapping with 5165, 5241
Plenary	5165	CR 29.510 1105 Rel-19 Support of VFL capability information	vivo	WI AIML_CN CAT B
Plenary	5241	CR 29.510 1112 Rel-19 Extend the MlAnalyticsInfo to include the VFL capability	Nokia	WI AIML_CN CAT B
Main	5113	CR 29.518 1139 Rel-19 Presence-In-AOI-Report considering UE positioning capabilities	Huawei	WI AIML_CN CAT B Overlapping with 5162, 5239, 5242
Main	5162	CR 29.518 1144 Rel-19 New event ID of Namf_EventExposure service to support AI positioning	vivo	WI AIML_CN CAT B
Main	5239	CR 29.518 1152 Rel-19 Addition of Data Collection parameters in AMF for LMF data collection procedure	Ericsson	WI AIML_CN CAT B
Main	5242	CR 29.518 1153 Rel-19 Add UE positioning capabilities to event Exposure	Nokia	WI AIML_CN CAT B
Plenary	5161	Work Plan Rel-19 Work plan for the CT aspects of AIML_CN	vivo
Breakout	5163	CR 29.572 0298 Rel-19 Introduction of Nlmf_DataExposure service	vivo	WI AIML_CN CAT B Overlapping with 5238, 5244
Breakout	5238	CR 29.572 0307 Rel-19 LMF Enhancements for LMF based AI/ML Positioning – Stage 3 aspects	Ericsson	WI AIML_CN CAT B
Breakout	5244	CR 29.572 0309 Rel-19 New DataExposure service	Nokia	WI AIML_CN CAT B
Breakout	5205	CR 29.572 0304 Rel-19 Updates on the Reference model	Huawei	WI AIML_CN CAT B Overlapping with 5243
Breakout	5243	CR 29.572 0308 Rel-19 NWADF and DCCF as consumers of LMF service	Nokia	WI AIML_CN CAT B
19.40	CT aspects of Next Generation Real time Communication services [NG_RTC_Ph2]
Breakout	5052	CR 29.175 0024 Rel-19 Event Notification for PS Data Off Status	ZTE	WI NG_RTC_Ph2 CAT F
Breakout	5124	CR 29.175 0025 Rel-19 Update the description of EventInitiator data type	China Mobile	WI NG_RTC_Ph2 CAT D
Breakout	5127	CR 29.175 0026 Rel-19 Support of PS Data off feature for data channel	China Mobile	WI NG_RTC_Ph2 CAT B
Breakout	5129	CR 29.175 0027 Rel-19 Support of the specific PSI within Called ID for standalone DC	China Mobile	WI NG_RTC_Ph2 CAT B
Breakout	5134	CR 29.175 0028 Rel-19 Support of IMS AS Event Exposure Service	China Mobile, Huawei	WI NG_RTC_Ph2 CAT B
Breakout	5135	CR 29.562 0155 Rel-19 Support of IMS subscribe and Notify framework in HSS	China Mobile	WI NG_RTC_Ph2 CAT B
Breakout	5136	CR 29.562 0156 Rel-19 Add Nhss_imsEE service in HSS	China Mobile	WI NG_RTC_Ph2 CAT B
Breakout	5154	CR 29.175 0029 Rel-19 Report the PS Data Off Status to DCSF	Huawei	WI NG_RTC_Ph2 CAT B
Breakout	5155	CR 29.562 0158 Rel-19 Support of IMS AS registration to HSS	Huawei	WI NG_RTC_Ph2 CAT B
Breakout	5156	CR 29.571 0603 Rel-19 Add ImsEvent to the IMS common data	Huawei	WI NG_RTC_Ph2 CAT B
Breakout	5157	CR 29.510 1103 Rel-19 Support of IMS AS registration to NRF	Huawei	WI NG_RTC_Ph2 CAT B
Breakout	5158	CR 29.175 0030 Rel-19 Definition of Nimsas_ImsEE Service	Huawei	WI NG_RTC_Ph2 CAT B
Breakout	5159	CR 29.175 0021 Rel-19 Definition of Nimsas_ImsSessionManagement Service	Huawei	WI NG_RTC_Ph2 CAT B
Breakout	5219	CR 29.562 0159 Rel-19 Service description update to support IMS AS Instance Registration	China Mobile	WI NG_RTC_Ph2 CAT B
Breakout	5221	CR 29.562 0160 Rel-19 API defination update to support IMS AS Instance Registration	China Mobile	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	5043	Work Plan Rel-19 Work plan for VMR_Ph2	Qualcomm Incorporated
Plenary	5044	CR 29.572 0297 Rel-19 Support of additional ULI in MWAB	Qualcomm Incorporated	WI VMR_Ph2 CAT B Overlapping with 5218, 5258
Plenary	5218	CR 29.572 0306 Rel-19 Updates on Additional ULI to support MWAB-UE	Huawei	WI VMR_Ph2 CAT B
Plenary	5258	CR 29.572 0313 Rel-19 Additional ULI for MWAB	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]
Main	5068	CR 29.244 0883 Rel-19 Support for MPQUIC-IP and MPQUIC-E steering functionalities	Ericsson	WI MASSS CAT B overlapping with 5095, 5266, 5267
Main	5095	CR 29.244 0889 Rel-19 MPQUIC-IP and MPQUIC-E support	Nokia	WI MASSS CAT B
Main	5266	CR 29.244 0902 Rel-19 MPQUIC-UDP Steering Functionality	Huawei	WI MASSS CAT F
Main	5267	CR 29.244 0903 Rel-19 Support of additional MPQUIC-IP functionality	Huawei	WI MASSS CAT B
5094	CR 29.510 1092 Rel-19 MPQUIC-IP and MPQUIC-E capabilities	Nokia	withdrawn	WI MASSS CAT B
Plenary	5103	CR 29.571 0600 Rel-19 MPQUIC-IP and MPQUIC-E capabilities	Nokia	WI MASSS CAT B overlapping with 5114
Plenary	5114	CR 29.571 0601 Rel-19 Update ATSSS capabilities	Huawei	WI MASSS CAT B
Plenary	5287	Work Plan Rel-19 Work Plan for MASSS	Apple
19.46	CT Aspects on Subscription control for reference time distribution in EPS [TEI19_TIME_SUB_EPS]
Plenary	5045	CR 29.230 0713 Rel-19 New AVP for Time Reference Information Distribution Indication	Qualcomm Incorporated	WI TEI19_TIME_SUB_EPS CAT B
Plenary	5046	CR 23.008 0589 Rel-19 Addition of Time Reference Information Distribution Indication	Qualcomm Incorporated	WI TEI19_TIME_SUB_EPS CAT B overlapping with 5214
Plenary	5214	CR 23.008 0590 Rel-19 Support of Time Reference Information Distribution Indication	Huawei	WI TEI19_TIME_SUB_EPS CAT B
19.47	CT aspects of 5G NR Femto [5G_Femto]
Plenary	5053	CR 29.571 0584 Rel-19 Common Data Type for 5G Femto Information	ZTE	WI 5G_Femto CAT B
Plenary	5054	CR 29.503 1322 Rel-19 Provision of 5G Femto Information to UDM	ZTE, Samsung	WI 5G_Femto CAT B
19.48	CT aspects of Extended Reality and Media service (XRM) Phase 2 [XRM_Ph2]
Main	5096	CR 29.281 0136 Rel-19 PDU Set based handling for non-3GPP accesses	Nokia	WI XRM_Ph2 CAT B
Main	5097	CR 29.244 0890 Rel-19 PDU Set based handling for non-3GPP accesses	Nokia	WI XRM_Ph2 CAT B overlapping with 5264
Main	5264	CR 29.244 0900 Rel-19 PDU Set handling in non-3GPP accesses	Huawei	WI XRM_Ph2 CAT B
Main	5098	CR 29.244 0891 Rel-19 L4S support for non-3GPP accesses	Nokia	WI XRM_Ph2 CAT B
Main	5099	CR 29.244 0892 Rel-19 Identification and marking of Data Burst Size in DL GTP-U packets	Nokia	WI XRM_Ph2 CAT B overlapping with 5263
Main	5263	CR 29.244 0899 Rel-19 Support of Data Burst Size Marking Indication on N4	Huawei	WI XRM_Ph2 CAT B
Main	5100	CR 29.244 0893 Rel-19 Support of differentiated QoS handling for multiplexed media flows	Nokia	WI XRM_Ph2 CAT B
Main	5101	CR 29.244 0894 Rel-19 Transferring media related information over N6 using connect-UDP for e2e encrypted traffic	Nokia	WI XRM_Ph2 CAT B
Plenary	5119	CR 29.510 1102 Rel-19 Support for the MoQ relay functionality for XR	Huawei	WI XRM_Ph2 CAT B
Plenary	5259	CR 29.571 0608 Rel-19 Support of MoQ Transport protocol	Huawei	WI XRM_Ph2 CAT B
Main	5260	CR 29.244 0897 Rel-19 Support of MoQ Transport protocol on N4	Huawei	WI XRM_Ph2 CAT B
Plenary	5261	CR 29.556 0046 Rel-19 MoQ Relay Address	Huawei	WI XRM_Ph2 CAT B
Main	5262	CR 29.244 0898 Rel-19 Support of MoQ on N4 for encrypted XRM traffic	Huawei	WI XRM_Ph2 CAT B
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]
20	Study Items
20.1	Study on Protocol for AI Data Collection from UPF [FS_PAIDC-UPF]
Plenary	5102	pCR 29.889 Rel-19 PCR on Addressing the Editor's notes of Solutions #2 and #5	Nokia
5139	LS out Rel-19 LS on optimizations to the subscription of UPF events	Ericsson	Moved to 4.2
Plenary	5226	pCR 29.889 Rel-19 PCR_on clarification for the group of users	China Mobile
Plenary	5236	pCR 29.889 Rel-19 Clarifications to solution #2 and #5	Ericsson
TR 29.889v0.3.0	China Mobile
20.2	Study on Reducing Information Exposure over SBI [FS_RedInfExp_SBI]
TR 29.857v1.4.0	Samsung
20.3	Study on IMS Disaster Prevention and Restoration Enhancement [FS_IMS_RES]
TR 29.866v1.3.0	China Telecom
21	Any other business
5010	Work Plan Work Plan	CT4 Chair
5290	discussion Discussion on API Version Update Due to Cross Reference	CT4 Chair
22	Future meetings
23	Close of Meeting