3GPP TSG-CT WG4 Meeting #130	C4-253006

Goteborg, Sweden; 25th – 29th August 2025

Source:	Chairman, TSG-CT WG4

Title:	Proposed allocation of documents to agenda items for CT4#130, 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	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-253002
2	Allocation of Documents to Agenda Items
3001	agenda Draft Agenda	CT4 Chair
3002	other eMeeting guidelines for CT4 Working Group meeting	CT4 Chair
3003	agenda Detailed agenda & time plan for CT4 meeting: status at document deadline	CT4 Chair
3004	agenda Detailed agenda & time plan for CT4 meeting: status on eve of meeting	CT4 Chair
3005	agenda Proposed allocation of documents to agenda items for CT4 meeting: status at document deadline	CT4 Chair
3006	agenda Proposed allocation of documents to agenda items for CT4 meeting: status on eve of meeting	CT4 Chair
3007	agenda The allocation of documents to agenda items for CT4 meeting: status at the end of meeting	CT4 Chair
3	Reports
3008	report Previous TSG CT & SA Status Report	CT4 Chair
3009	report Previous CT4 meeting report	MCC
4	Liaison statements
4.1	Incoming liaisons
Plenary	3013	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#129 meeting. Related CRs were in C4-252056, C4-252057, reply LS was in C4-252058. It was decided to wait for outcome from SA2 Reply LS in 3084
Plenary	3014	LS in Rel-19 LS on Advanced MF capability registration and discovery	SA4	S4-250746 To: SA2, CT4 CC: Contact: Qualcomm Postponed from CT4#129 meeting. Waiting for the SA2 requirement on MF capability registration and discovery Reply LS in 3160
Plenary	3029	LS in Rel-19 Reply LS on Advanced MF capability registration and discovery	SA WG2	S2-2505955 To: SA4 CC: CT4 Contact: ZTE --- SA2 thanks SA4 for the LS (S4-250746) on Advanced MF capability registration and discovery. SA2 has discussed the solutions to enhance the MF capability registration and discovery. For the solution of using MF capability profile for MF registration and discovery, SA2 has agreed the CRs for TS 23.228 and TS 23.502 as attached. --- Attachments missing, links as below: TS 23.228 CR#1650 TS 23.502 CR#5414
Plenary	3015	LS in CVD-2025-0101 – Four critical vulnerabilities in the access control mechanism of the 5G core Network	GSMA CVD PoE	To: CT1, SA3, forwarded to CT4 by CT1 CC: Postponed from CT4#129 meeting. Received late, companies need time to look into this issue, will be handled in the next meeting Related CR in 3085, reply LS in 3086
Plenary	3016	LS in Rel-19 LS on UE parameters update header security	CT WG1	C1-253719 To: SA3 CC: CT4 Contact: Nokia --- CT1 has implemented the Stage 2 requirements introduced in 3GPP TS 33.501 via S3-251120; please find the attached CR. In the CR, the UE indicates whether it supports UPU header protection via the UPU header. In light of this decision, CT1 agreed that, the UDM cannot use UPU header protection until receiving an acknowledgement for UPU data sent without UPU header protection. However, since UDM operations in terms of UPU are out of the scope of CT1 specifications, CT1 has not specified the agreement. CT1 kindly requests SA3 to take the above into account and update 3GPP TS 33.501 if necessary. --- Does this impact CT4 spec?
Plenary	3017	LS in Rel-19 Reply LS on Encoding of (S)RTP Multiplexed Media Identification Information	CT WG1	C1-254120 To: CT4, SA2 CC: SA4, CT3 Contact: Ericsson --- CT1 thanks CT4 for the LS on Encoding of (S)RTP Multiplexed Media Identification Information. CT1 has discussed the question raised by CT4 on 1) Alignment of encoding of the MID information; and 2) (S)RTP multiplexed media identification information entry to be used by both (S)RTP and (S)RTCP traffic. CT1 agreed to align with CT4 encoding of (S)RTP multiplexed media identification information with the deviations: 1. In CT1, the length of the MID identification-tag is not added as a new parameter, instead, the MID identification tag is encoded as length of the MID identification-tag which is the first one octet and followed by value of the MID identification-tag; 2. CT1 refers to RFC 3550 only for SSRC encoding; 3. In CT1, the RTCP packet type field is encoded as a one-octet payload type field, which contains the binary representation of an integer between 200 and 204 (inclusive). In addition, CT1 would like to point out that, as an implementation option, apart from a single entry of (S)RTP multiplexed media identification information to apply to both (S)RTP and (S)RTCP traffic, a (S)RTP multiplexed media identification information can include one (S)RTP multiplexed media identification information entry for (S)RTP and one (S)RTP multiplexed media identification information entry for (S)RTCP to make the (S)RTP multiplexed media identification information applicable to both (S)RTP and (S)RTCP traffic. ---
Plenary	3018	LS in Rel-19 Reply LS on Encoding of (S)RTP Multiplexed Media Identification Information	CT WG3	C3-252475 To: CT4, CT1, SA4 CC: SA2 Contact: Nokia --- CT3 thanks CT4 for their LS on Encoding of (S)RTP Multiplexed Media Identification Information. CT3 has agreed the attached 29.514 CR and 29.512 CR to support encoding multiple instances of Multiplexed Media Identification Information. CT3 has agreed the CR with the overlapping range for RTP payload type and RTCP packet type in the multiplexed media with EN. ---
Plenary	3349	LS in Rel-19 Reply LS on Encoding of (S)RTP Multiplexed Media Identification Information	SA4	S4-251471 To: CT3 CC: SA2, CT1, CT4 Contact: interdigital --- SA4 thanks CT3 for their LS on Encoding of (S)RTP Multiplexed Media Identification Information. As per the IANA Real-Time Transport Protocol Parameters registry (https://www.iana.org/assignments/rtp-parameters/rtp-parameters.txt), the RTCP packet type values in the range 200-223 are designated as the primary assignment range. When this range is fully occupied, values in the range 194-199 are preferred for subsequent assignments. Also, the ranges 224-254 and 1-191 for RTCP packet type values are unassigned and should only be used when other values have been exhausted. RTP payload type values shall be in the range 0-127 (inclusive). Multiplexing of RTP and RTCP requires the RTCP packet type to be distinct from the RTP payload type plus 128, where 128 accounts for the M-bit of the RTP header, which may be 0 or 1 depending on the RTP packet. RFC 5761 section 4 details the existing conflicts and provides recommendations for IANA to register new RTCP packet types to help prevent future conflicts. In general, RTP and RTCP packets multiplexed onto a single port can be distinguished, provided the RTP payload types and RTCP packet types used in the RTP session are chosen according to the rules in section 4 of RFC 5761. Based on the IANA registration guidelines for RTCP packet type and the RTP payload type values, SA4 thinks that the RTP payload type and RTCP packet type values in the multiplexed media cannot share an overlapping range, if the guidelines specified in RFC 5761 are followed. ---
Plenary	3019	LS in Rel-17 LS on new AVPs in TS 29.214	CT WG3	C3-252476 To: CT4 CC: Contact: Ericsson CR defining these AVPs already agreed on CT4#129 meeting
Plenary	3020	LS in Rel-19 Reply LS on Security related protocol-specific parameters for N6 delay measurement	CT WG3	C3-252543 To: SA2, SA3 CC: CT4 Contact: Nokia --- CT3 thanks SA4 for the clarifications related to the security parameters transmitted over N4 to support N6 delay measurement and would like to ask the following questions. Question 1 (to SA2): Do the "protocol-specific configuration parameters", which are provided within the "N6 delay measurement assistance information" of the EAS Deployment Information in 3GPP TS 23.548 Table 6.2.3.4-1, contain the contents that are described in the SA4 LS reply in S3-251667? If the answer is "no", then what are the exact contents of the protocol-specific configuration parameters provided by the AF? Question 2 (to SA3): Whether the security related protocol-specific parameters for N6 delay measurement needs to be provisioned by the AF? --- Propose to Note
Plenary	3021	LS in Rel-19 Reply LS on Format of FQDN for PRINS - update	TSG CT	CP-251293 To: GSMA 5GMRR CC: CT4 Contact: Nokia --- 3GPP TSG CT would like to provide information to GSMA 5GMRR related to discussion on LS (5GMRR Doc 024_203r1) on Format of FQDN for PRINS from 5GMRR. 3GPP TSG CT has further revised the CR that CT4 has agreed to 3GPP TS 29.573 and where CT4 has sent an LS on the agreed CR out of their May meeting to GSMA 5GMRR, the CT4 tdoc number was C4-252416. 3GPP CT has approved the attached CR in CP-251183. The changes that were added in CT plenary are summarized on the cover page of CP-251183 in the description for “rev-3”. --- CR agreed by CT4#129 was further revised and approved on CT#108. This LS updates GSMA with such information. Propose to note
Plenary	3022	LS in Rel-19 Reply LS on UE usage of the RAT restrictions	RAN WG2	R2-2504931 To: CT1 CC: CT4, RAN Contact: Apple --- 1. Overall Description: RAN2 thanks CT1 for the Reply LS on UE usage of the RAT restriction. RAN2 has discussed the LS and confirms the AS layer support of ECRATU feature (i.e., cell selection and reselection procedure) by GERAN/UTRAN is optional. Also, in order to prepare Rel-19 CRs for TS 25.304 & TS 43.022, RAN2/RAN need know that whether separate NAS capabilities for 2G/3G RAT restriction and 4G/5G RAT restriction would be introduced in CT1 specification or not. --- Propose to note
Plenary	3023	LS in Rel-17 Reply LS on stage 1 requirements to support PWS over satellite NG-RAN in Rel-17	RAN WG3	R3-253867 To: SA1, CT1, RAN2 CC: SA2, CT4, RAN, SA Contact: Ericsson --- RAN3 thanks SA1 for the LS on stage 1 requirements for PWS support over satellite NG-RAN. RAN3 agrees that PWS for NTN is not supported in Rel-17/18 and has endorsed the attached CRs for NR NTN and IoT NTN. --- Propose to note
Plenary	3056	LS in Rel-17 Reply LS from RAN on removal of support of PWS over satellite NG-RAN in Rel-17 and 18	TSG RAN	RP-251859 To: CT1, SA1, CT, SA, RAN3, RAN2 CC: SA2, CT4 Contact: Aalyria --- 1. Overall Description: RAN thanks RAN3 for raising awareness on the Reply to the SA1 LS on Stage 1 requirements for PWS support over satellite NG-RAN. RAN discussed the issue from a RAN perspective, also considering the original conclusion by CT1 captured in the CT1 LS to SA1 (C1-250715) and highlighted by RP-251718, which identified possible “backward compatibility issues (e.g. country-specific duplicate detection timers for PLMNs using non-country specific PLMN ID with MCC 9xx over satellite access)”, and concluded that the issue identified by CT1 might not have impact on the NG-RAN, and thus the removal of PWS support for satellite NG-RAN in Rel-17 and Rel-18 need further assessment. Several companies highlighted that the removal of PWS support for satellite NG-RAN in Rel-17 and Rel-18 may have been driven by a misinterpretation of the relationship between non-country specific (e.g. 9xx) PLMNs and satellite access, highlighting that satellite access may be deployed without the use of non-country specific (e.g. 9xx) PLMNs, and non-country-specific PLMNs may be deployed without satellite access. 2. Actions: To CT1, CT, SA1, SA: ACTION: RAN asks CT1, CT, SA1, SA to take the above into account and either revert or confirm the removal of the support for PWS over satellite NG-RAN in Rel-17 and Rel-18. --- Propose to note
Plenary	3024	LS in Rel-19 LS on the latest Ambient IoT progress of RAN3	RAN WG3	R3-253941 To: SA2, CT4 CC: Contact: Huawei --- RAN3 would like to provide the following latest RAN3 progress of Ambient IoT: In case of indirect connectivity, as parallel sessions between gNB and AMF are supported, the AIOTF Identifier and the Correlation Identifier are included outside of the containers in all the Inventory related NGAP messages (in addition to including the Correlation Identifier inside the containers as previously agreed). In case of indirect connectivity, as parallel Command procedures for different devices between gNB and AMF within the same session are supported, the AIOTF Identifier, the Correlation Identifier, and the RAN A-IoT Device NGAP ID are included outside of the containers in all the Command related NGAP messages (in addition to including the Correlation Identifier and the RAN A-IoT Device NGAP ID inside the containers as previously agreed). Introduce a new A-IoT CN triggered Class 1 NGAP A-IoT Session Release procedure. Introduce a new gNB triggered Class 2 NGAP A-IoT Session Release Request procedure. In the case of Inventory only scenario, introduce Inventory Complete indication to inform the AIoT CN about the completion of the triggered Inventory session. FFS on how to provide such indication. NGAP: Command Request procedure is a per single device procedure. CN A-IoT Device NGAP ID is not needed. No NGAP signalling is introduced for providing the A-IoT RAN Information (served reader list, supported A-IoT areas, reader location) from the gNB to the AIOTF. About Reader Selection: Upon only receiving the area in Inventory Request, the gNB selects readers within the indicated area. Upon receiving neither the area nor the reader list in Inventory Request, the gNB selects all the served readers. WA: Upon only receiving the reader list in Inventory Request, the gNB selects the readers indicated by the reader list. ---
Plenary	3025	LS in Reply LS on SMS to emergency center	SA WG1	S1-252421 To: GSMA NG CC: SA2, CT1, CT4, SA Contact: Qualcomm --- SA1 thanks GSMA for their LS (NRG 024_202) on SMS to emergency center. SA1 would like to inform GSMA that a Rel-20 CR was agreed in S1-109 (S1-250986), later approved by SA (see latest 22.101 spec: https://www.3gpp.org/ftp/Specs/archive/22_series/22.101/22101-k00.zip). --- Propose to note
Plenary	3026	LS in Rel-19 Reply LS on paging ID length	SA WG2	S2-2505793 To: RAN2, CT4, SA3 CC: RAN3 Contact: CATT --- SA2 thanks RAN2 for the LS on paging ID length (S2-2504515/R2-2503197). SA2 has discussed the issue and would like to provide the following feedback. In TS 23.369 clause 6.2.2, it is specified that the AIOTF sends the AIoT Identification Information to be included in the paging message to the NG-RAN node, and the AIoT Identification Information can include Filtering Information or a single AIoT Device Identifier. For the Filtering Information, SA2 has agreed the attached pCR (S2-2505850) and asks CT4 to continue the stage 3 work of the Filter Information. Security aspect of the Filter Information will be decided by SA3. For the single AIoT Device Identifier, what identifier(s) to be used is under discussion in SA3. SA2 kindly asks CT4 to provide the maximum length of the Filtering Information, and kindly asks SA3 to provide feedback on security aspect of the Filtering Information and on the single AIoT Device Identifier. SA2 kindly asks RAN2 to take the above information into account. ---
Plenary	3027	LS in Rel-18 LS on Modification of User Plane Modification Procedure	SA WG2	S2-2505873 To: CT1, CT4 CC: - Contact: Ericsson --- SA2 modified significantly “Modification of User Plane Modification Procedure” in rel-18 and in rel-19. Additionally, rel-19 supports multiple LCS-UPP connections. Please work on the related stage 3 specifications to support the enhancement. Approved CRs for rel-18 and rel-19 are attached. ---
Plenary	3028	LS in Rel-19 Reply LS on Ethernet MA PDU session using MPQUIC-E steering	SA WG2	S2-2505931 To: CT4 CC: CT1 Contact: Nokia --- 1. Overall Description: SA2 thanks CT4 for their LS on Ethernet MA PDU session using MPQUIC-E steering functionality, highlighting the potential gaps in the stage 2 specification about handling MA PDU Session with MPQUIC-E steering functionality when ROHC is required. SA2 have discussed the questions raised by CT4 and would like to provide the below feedback. Q1: Can SA2 clarify the handling of MA PDU sessions using MPQUIC-E with a 3GPP access leg in EPS with respect to the PDN connection type to be signaled to the eNB? [SA2 Answer]: SA2 has discussed the question and agreed the solution (without any impacts on MME and SGW) as described in the attached CR5421. Q2: Can SA2 confirm CT4 assumption regarding the handling of MA PDU sessions using MPQUIC-E for HR PDU sessions and PDU sessions with an I-SMF. [SA2 Answer]: SA2 has discussed the question and agreed the solution (without any impact on VPLMN) as described in the attached CR5396. SA2 would also like to point out that I-SMF is not supported for MA PDU Sessions (please see the specification text highlighted below). Therefore, no corresponding change is required to support PDU sessions with an I-SMF. TS 23.501 clause 5.32.1 specifies below: In this Release of the specification, support for ATSSS assumes SMF Service Areas covering the whole PLMN or that a MA PDU Session is released over both accesses when the UE moves out of the SMF Service Area. TS 23.502, clause “4.23.5.1 PDU Session establishment procedure” also specifies as below: “If the service area of the selected SMF does not include the current UE location and the UE does not request for a MA PDU Session, the AMF selects an I-SMF that serves the area where UE” camps. “If the service area of the selected SMF does not include the current UE location and the UE requests a MA PDU Session, then the AMF rejects the MA PDU Session Establishment procedure.” ---
Plenary	3030	LS in Rel-19 Reply LS on Extending Charging Support in 5GC	SA WG2	S2-2506095 To: CT3 CC: SA5, CT4 Contact: Nokia --- SA2 thanks CT3 for the LS on Extending Charging Support in 5GC. SA2 discussed the questions in the received LS and has arrived at the following conclusions: Is the Primary Charging Address still required as a mandatory parameter to be stored in the UDR and provided to the PCF, SMF and AMF when the CHF Group ID is available? SA2 Answer: CHF group ID is a parameter independent from CHF Address, and when available is used for CHF selection via NRF. The exact details of CHF discovery and selection can be found in 6.3.11 of TS 23.501. To clarify this further from SA2 point of view, CHF group ID is added as a different parameter instead of indicating as part of Charging address and accordingly a CR is attached. Is the CHF Set ID and the CHF group ID mutually exclusive or can they still be both stored in the UDR and provided to the PCF, SMF and AMF together?? SA2 Answer: One or both of CHF Set ID and CHF Group ID could be present. SA2 would emphasize that CHF Set ID is used for binding aspects while CHF Group ID is used for scaling aspects (i.e., one or more CHF instances manage a specific set of SUPIs); hence, they are not mutually exclusive. --- Attachment missing, link as below: CR 1558 - TS 23.503
Plenary	3035	LS in Rel-19 LS reply on Extending Charging Support in 5GC	SA WG5	S5-253101 To: CT3 CC: SA2, CT4 Contact: Ericsson --- SA5 has discussed the questions in received LS S2-2504504/C3-251642 and have arrived at the following conclusions: Q1: Is the Primary Charging Address still required as a mandatory parameter to be stored in the UDR and provided to the PCF, SMF and AMF when the CHF Group ID is available? Answer: From a CHF perspective, CHF group ID can support NRF based CHF selection by CHF Consumer, independent of whether the Primary Charging Address is provided or not. Q2: Is the CHF Set ID and the CHF group ID mutually exclusive or can they still be both stored in the UDR and provided to the PCF, SMF and AMF together? Answer: From a CHF perspective there is no case defined where both CHF Set ID and CHF group ID would be required at the same time and only one of them is needed to support NRF based CHF selection by CHF Consumer. ---
Plenary	3031	LS in Rel-19 Reply LS on Transport Level Marking on N3/N9	SA WG2	S2-2506097 To: CT4 CC: - Contact: Lenovo --- CT4 would like to ask if the highlighted requirement in yellow implies a new requirement for N4 interface specific for XRM_Ph2? SA2 reply: The I-SMF may provide an indication in the FAR to derive the transport level marking of the outgoing packet based on the transport level marking value of the incoming packet . Then, I-UPF shall derive the transport level marking value of the outgoing N3 packet based on the incoming marking value of the N9 packet. If so, how can the I-SMF learn from the anchor SMF to instruct the I-UPF for a QoS flow 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 Reply: For downlink, the anchor SMF may send an indication that transport level marking is being applied and consistency of transport level marking is needed for the corresponding QoS Flow to the I-SMF via N16a interface. More generally, could SA2 clarify how transport level marking should be performed by I-UPF? SA2 reply: In general, If the I-SMF receives an indication from anchor SMF that transport level marking is being applied and consistency of transport level marking is needed for the corresponding QoS Flow, then it instructs the I-UPF to derive the transport level marking value of the outgoing N3 packet based on the transport level marking value of the incoming N9 downlink packet. If no such indication is received at I-SMF, The I-SMF can provide a transport level marking value in the FAR, and then the I-UPF performs the transport level marking for the QoS flow based on this transport level marking value. If no transport level marking value is included in the FAR, the I-UPF performs transport level marking based on its pre-configured logic, e.g., using a pre-configured value, or deriving the outgoing marking value based on the incoming marking value, or mapping tables or others. ---
Plenary	3032	LS in Rel-19 Reply LS on Questions on stage 2 requirements for AIML_CN	SA WG2	S2-2506099 To: CT4 CC: CT3 Contact: Nokia --- [For LS in C4-250630] Q1: Given that the metrics can be reported by OAM APIs, is it necessary for the NRF APIs to also support reporting the same metrics, and if so, can SA2 explain why? SA2 Answer:SA2 agrees that all the information listed in table 6.22.2-5 is available via OAM, see clause 5.10 in TS 28.552. SA2 thus removed the NOTE. Q2: If the answer to Q1 is yes, this required functionality does not fit with the current scope of the Nnrf_NFManagement_NFStatusSubscribe service operation. CT4 kindly asks SA2 to clarify which service operation is suitable for this purpose? SA2 answer: SA2 agrees that the intention of the Nnrf_NFManagementStatusSubscribe service operation is a subscription for information available in NF profiles, but the information listed in table 6.22.2-5 is not part of any NF profile. SA2 thus removed the reference to 6.22.2-5 from the quoted bullet. Q3: Accordingly, should NF metrics related to signalling storm information be reported per Service Name (i.e. with the NF instance aggregating metrics of all NF service instances supporting the same service name) or per NF service instance? SA2 answer: SA2 clarified that Request type designates a NF service instance. Q4: Does “Service Type” refer to “service name”? If the answer is yes, should SCP metrics related to signalling storm information be reported per "Service Name" or "Service instance"? If the answer is no, what does "Service Type" refer to? SA2 answer: SA2 clarified in Clause 5.2.29.2.1 of TS 23.502 that the subscription can be per NF service name or per NF service instance and that the reported “Request type” designates a NF service instance. [For LS in C4-251477] Q1) Regarding the "UE related Context Data collection" specified in Table 6.22.2-1 of TS 23.288: Requiring the SCP to provide information with UE granularity means that the NFs in the network would be required to be configured to use the custom header 3gpp-Sbi-Correlation-Info which is optional to support and may be subject to security/regulatory requirements (see TS 29.500). Furthermore, different NFs may use different UE identities, e.g. SUPI, GPSI, etc, for the same UE within this header Also the NFs of earlier releases that do not support this header do not provide UE information to the SCP, which would impact the accuracy of the statistics. Considering these limitations, CT4 would like to ask SA2 to confirm whether the information with UE granularity is required to be obtained by the SCP for the event exposure purpose. SA2 answer: SA2 agrees to remove requirements related to per-UE reporting from the SCP. An SCP can collect information on a per NF instance or NF service instance level. Related IEs have thus been transferred to a new Table 6.22.2-X Q2) According to TS 23.288 clause 6.22.2, the SCP is required to distinguish between different types of communications and signallings and provide information, for example, to collect the data of "Number of redundant signalling of NF" and "A posterior Request type of NF (0..max)" in Table 6.22.2-1, and "SCP Signalling statistics" in Table 6.22.2-3 which are depicted bellow. Currently there is no mechanism to enable SCP to differentiate between different types of communication SA2 refers to, e.g. whether the signalling is redundant or an "A posterior Request". Therefore, CT4 would like to ask SA2 to consider reverting the requirements on "A posterior Request type of NF (0..max)" and "Number of redundant signalling of NF", unless SA2 could provide clarification on how these requirements can be implemented. SA2 answer: SA2 agrees that this information cannot be observed by an SCP. The intention of Note 3 is rather to clarify that an SCP can perform retransmissions. Note 3 was clarified accordingly. Q3) CT4 would also appreciate SA2 to clarify what "different types of signalling" corresponds to for "SCP Signalling statistics". SA2 answer: The “different types of signalling” relate to the addressed service. The wording in the table has been clarified accordingly. Q4) "Heart-beat related information", "NF load status information", "Capacity and priority information" which are listed in TS 23.288 Table 6.22.2-2, may be provided by NRF. If required, SCP may get this information from NRF. Therefore, CT4 would like to ask for clarification on why the SCP is also required to provide this information. SA2 answer: SA2 agrees to remove requirements to expose heart-beat related information, NF load status information, and Capacity and priority information from the SCP --- Attachments missing, links as below: CR 1465 for TS 23.288 CR 5483 for TS 23.502
Plenary	3033	LS in Rel-16 LS on PLMN ID checks in interconnect scenarios when NFc supports multiple PLMN IDs	SA3	S3-252264 To: CT4 CC: CT3 Contact: Ericsson --- SA3 would like to inform CT4 about an issue with PLMN ID checks that may lead to service interruption, when the requesting NF consumer supports multiple PLMN IDs in interconnect scenarios. For security purposes, the NF producer needs to verify the PLMN ID of the NF consumer in the service request. Towards that goal, in Rel-15, after SA3’s request, CT4 added NF consumer's PLMN ID in the Access Token Claims (CR C4-191528) to enable the checks on NF consumer’s PLMN ID by pSEPP and the NF producer. In Rel-16, to consistently define authorization parameters for different services/procedures in the NRF, in the Access Token Request message, CT4 included a list of PLMN IDs instead of a single PLMN ID when NF supports multiple PLMN IDs (CR C4-203256). During issuing an access token, it is unclear how the NRF chooses which of the NF consumer’s PLMN ID to include in the Access Token Claims, if the access token request by the NF consumer includes multiple PLMN IDs. Additionally, access tokens can include only one PLMN ID of the NF consumer and NRF is not aware which PLMN ID does the NF consumer intend to use in the service request API message towards the target NF producer. Consequently, it may happen that the NF consumer obtains an access token from the NRF with a PLMN ID of the NF consumer that does not match with the PLMN ID that the NF consumer uses in the service request API message towards the target NF producer. Similarly, the PLMN ID in the access token might not match with the PLMN ID that the NF consumer uses in the service request body. As a result, for both cases access token verification fails, and the target NF producer rejects the service request. --- Related CRs in 3220 and mirrors, 3087, 3088, 3089 Reply LS in 3219
Plenary	3034	LS in LS on UE type identification for UAS charging requirements	SA5	S5-252788 To: CT3, CT4 CC: SA2 Contact: China Mobile --- According to TS 23.256, a UAV that is configured for UAS services (i.e. is provisioned with a CAA-Level UAV ID) registers to the 3GPP system for UAS services and provides the CAA-Level UAV ID and a UUAA Aviation Payload to 5GS or EPS. As defined in TS 24.501, the CAA-Level UAV ID is provided to 5GC with the value of service-level device ID setting to the CAA-Level UAV ID. Considering the above information and charging requirements, SA5 has the following question: Is there any attribute already defined in Rel-19 CT specifications indicating AMF and SMF that a UE is a UAV UE or is using UAS services? ---
Plenary	3036	LS in LS to 3GPP about the external data channel content access requirements	GSMA NG UPG	UPG14_109r3 To: SA1, SA2,SA3, SA4 ,SA6, CT, CT1, CT4 CC: Contact: Huawei --- 3. Question 3 to SA4 and CT: Does 3GPP SA4/CT plan to standardize a method allowing IMS Data Channel Applications to support external content references, e.g. <script src> or <img src> tags since 3GPP Release 18 provides no standards or profiles for handling such external resource loading. This gap might impact interoperability since implementations might evolve and become proprietary as some suppliers might chose to disallow external scripts, while others might permit it using the Internet connection. ---
Plenary	3057	LS in Rel-19 Reply LS on the conclusion of FS_MINT_Ph2	TSG SA	SP-250807 To: CT1, SA2, CT4 CC: TSG CT Contact: China Telecom --- TSG SA thanks CT1 and SA2 for their respective LS, (SP-250427 / C1-252559) and (SP-250711 / S2-2505932). TSG SA has discussed the matter in their SA#108 meeting. TSG SA has no concerns with the approval of the CT1 WID (MINT_Ph2) in CP-251282. In SP-250711 / S2-2505932, SA2 considers that it’s critical for MME to provide disaster roaming indication to HPLMN entity when 4G serving MME provides disaster roaming service to the UE (e.g. similar mechanism as 5G serving AMF provides the disaster roaming indication to the HPLMN NFs when provides the disaster roaming service to UE in Rel-17 MINT work). TSG SA respectfully asks CT4 to take this feedback into consideration and considers corresponding normative work. TSG SA respectfully asks CT1 to proceed the normative work, based on the scope of CP-251282. Meanwhile potential CT4 work may be also needed, thus CP-251282 may be further revised. TSG SA respectfully asks SA2 to plan how to perform the alignment to the normative work in CT1 as well as additional input based on CT4 updates (if any). TSG SA requests CT1 and CT4 to keep SA2 in the loop while developing their stage 3 solutions, as MINT_Ph2 stage 2 work will be performed after stage 3 and may require adjustments based on SA2 work. ---
4.2	Outgoing liaisons
Plenary	3160	LS out Rel-19 Reply LS on Advanced MF capability registration and discovery	Qualcomm Incorporated	To: SA4 Cc: SA2
Plenary	3161	LS out Rel-19 Reply LS on UE type identification for UAS charging requirements	Qualcomm Incorporated	To: SA5 Cc: CT3
Plenary	3297	LS out Rel-19 LS on Structure updates of AIoT Identifiers	CATT	To: SA2 Cc: SA3
5	Check of Approved Output Documents
3011	other Output Documents	CT4 Chair
3012	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.502 0 Rel19 API version and External doc update	Nokia	Email approval	CR possibly needed Email approval
29.503 0 Rel19 API version and External doc update	Nokia	Email approval	CR possibly needed Email approval
29.504 0 Rel19 API version and External doc update	China Mobile	Email approval	CR possibly needed Email approval
29.505 0 Rel19 External doc update	China Mobile	Email approval	CR possibly needed Email approval
29.509 0 Rel19 API version and External doc update	Orange	Email approval	CR possibly needed Email approval
29.510 0 Rel19 API version and External doc update	Ericsson	Email approval	CR possibly needed Email approval
29.511 0 Rel19 API version and External doc update	Deutsche Telekom	Email approval	CR possibly needed Email approval
29.515 0 Rel19 API version and External doc update	CATT	Email approval	CR possibly needed Email approval
29.518 0 Rel19 API version and External doc update	Ericsson	Email approval	CR possibly needed Email approval
29.526 0 Rel19 API version and External doc update	ZTE	Email approval	CR possibly needed Email approval
29.531 0 Rel19 API version and External doc update	Huawei	Email approval	CR possibly needed Email approval
29.532 0 Rel19 API version and External doc update	Huawei	Email approval	CR possibly needed Email approval
29.536 0 Rel19 API version and External doc update	ZTE	Email approval	CR possibly needed Email approval
29.540 0 Rel19 API version and External doc update	ZTE	Email approval	CR possibly needed Email approval
29.541 0 Rel19 API version and External doc update	Ericsson	Email approval	CR possibly needed Email approval
29.542 0 Rel19 API version and External doc update	Ericsson	Email approval	CR possibly needed Email approval
29.544 0 Rel19 API version and External doc update	Nokia	Email approval	CR possibly needed Email approval
29.550 0 Rel19 API version and External doc update	Orange	Email approval	CR possibly needed Email approval
29.553 0 Rel19 API version and External doc update	CATT	Email approval	CR possibly needed Email approval
29.555 0 Rel19 API version and External doc update	CATT	Email approval	CR possibly needed Email approval
29.556 0 Rel19 API version and External doc update	Huawei	Email approval	CR possibly needed Email approval
29.559 0 Rel19 API version and External doc update	CATT	Email approval	CR possibly needed Email approval
29.562 0 Rel19 API version and External doc update	Ericsson	Email approval	CR possibly needed Email approval
29.563 0 Rel19 API version and External doc update	Ericsson	Email approval	CR possibly needed Email approval
29.564 0 Rel19 API version and External doc update	China Mobile	Email approval	CR possibly needed Email approval
29.571 0 Rel19 API version and External doc update	Huawei	Email approval	CR possibly needed Email approval
29.572 0 Rel19 API version and External doc update	Ericsson	Email approval	CR possibly needed Email approval
29.573 0 Rel19 API version and External doc update	Huawei	Email approval	CR possibly needed Email approval
29.577 0 Rel19 API version and External doc update	Huawei	Email approval	CR possibly needed Email approval
29.578 0 Rel19 API version and External doc update	Nokia	Email approval	CR possibly needed Email approval
29.579 0 Rel19 API version and External doc update	China Telecom	Email approval	CR possibly needed Email approval
29.581 0 Rel19 API version and External doc update	Samsung	Email approval	CR possibly needed Email approval
29.586 0 Rel19 API version and External doc update	Xiaomi	Email approval	CR possibly needed Email approval
29.598 0 Rel19 API version and External doc update	CISCO	Email approval	CR possibly needed Email approval
29.673 0 Rel19 API version and External doc update	Ericsson	Email approval	CR possibly needed Email approval
7	Tdocs not fit into other agenda items
Plenary	3093	CR 29.564 0141 Rel-19 Bundling Event Reports of Multiple Subscriptions	Nokia, Ericsson	WI DUMMY CAT B
Plenary	3182	CR 29.564 0143 Rel-19 Skip Reporting Instruction	Ericsson, Nokia	WI PAIDC_UPF CAT B
Plenary	3323	CR 29.564 0146 Rel-19 Optimized UPF event subscription	China Mobile	WI DUMMY CAT B
Plenary	3330	CR 29.244 0995 Rel-19 Update PFCP establishment and modification with 5G VN group id	China Mobile	WI DUMMY CAT B
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	3046	CR 29.531 0247 Rel-16 Text correction for Nnssf_NSSAIAvailability Service	Oracle Corporation	WI eNS_Ph2 CAT F
Plenary	3045	CR 29.531 0246 Rel-17 Text correction for Nnssf_NSSAIAvailability Service	Oracle Corporation	WI eNS_Ph2 CAT A Category should be A
Plenary	3044	CR 29.531 0245 Rel-18 Text correction for Nnssf_NSSAIAvailability Service	Oracle Corporation	WI eNS_Ph2 CAT A Category should be A, WIC should be eNS_Ph2
Plenary	3043	CR 29.531 0244 Rel-19 Text correction for Nnssf_NSSAIAvailability Service	Oracle Corporation	WI eNS_Ph2 CAT A Category should be A, WIC should be eNS_Ph2
Plenary	3055	CR 29.531 0251 Rel-16 Clarification for NssfEventType	Oracle Corporation	WI eNS_Ph2 CAT F
Plenary	3054	CR 29.531 0250 Rel-17 Clarification for NssfEventType	Oracle Corporation	WI eNS_Ph2 CAT A Category should be A
Plenary	3053	CR 29.531 0249 Rel-18 Clarification for NssfEventType	Oracle Corporation	WI eNS_Ph2 CAT A Category should be A
Plenary	3052	CR 29.531 0248 Rel-19 Clarification for NssfEventType	Oracle Corporation	WI eNS_Ph2 CAT A Category should be A
Main	3149	discussion Resolution for mismatch of steering functionalities	Lenovo
Main	3150	CR 29.274 2123 Rel-16 Handling for UE requested MA PDU session with invalid capabilities – Method 1	Lenovo	WI ATSSS CAT F
Main	3151	CR 29.274 2124 Rel-17 Handling for UE requested MA PDU session with invalid capabilities – Method 1	Lenovo	WI ATSSS CAT A
Main	3153	CR 29.274 2125 Rel-18 Handling for UE requested MA PDU session with invalid capabilities – Method 1	Lenovo	WI ATSSS CAT A
Main	3154	CR 29.274 2126 Rel-19 Handling for UE requested MA PDU session with invalid capabilities – Method 1	Lenovo	WI ATSSS CAT A
Main	3155	CR 29.274 2127 Rel-16 Handling for UE requested MA PDU session with invalid capabilities – Method 2	Lenovo	WI ATSSS CAT F
Main	3156	CR 29.274 2128 Rel-17 Handling for UE requested MA PDU session with invalid capabilities – Method 2	Lenovo	WI ATSSS CAT A
Main	3157	CR 29.274 2129 Rel-18 Handling for UE requested MA PDU session with invalid capabilities – Method 2	Lenovo	WI ATSSS CAT A
Main	3158	CR 29.274 2130 Rel-19 Handling for UE requested MA PDU session with invalid capabilities – Method 2	Lenovo	WI ATSSS CAT A
Plenary	3219	LS out Rel-16 Reply LS on PLMN ID checks in interconnect scenarios when NFc supports multiple PLMN Ids	Huawei	To: SA3 Cc:
Plenary	3220	CR 29.510 1221 Rel-16 Providing list of PLMN IDs in Access Token Claim	Huawei	WI TEI16 CAT F
Plenary	3221	CR 29.510 1222 Rel-17 Providing list of PLMN IDs in Access Token Claim	Huawei	WI TEI16 CAT A
Plenary	3222	CR 29.510 1223 Rel-18 Providing list of PLMN IDs in Access Token Claim	Huawei	WI TEI16 CAT A
Plenary	3223	CR 29.510 1224 Rel-19 Providing list of PLMN IDs in Access Token Claim	Huawei	WI TEI16 CAT A
17	Release 17
17.1	Rel-17 work planning
17.2	New WIDs for Rel-17
17.3	Revised WIDs for Rel-17
17.4	TEI17 [TEI17]
Breakout	3265	CR 29.503 1494 Rel-17 Incomplete Implementation of CR0688	Ericsson, MCC	WI TEI17 CAT F
Breakout	3266	CR 29.503 1495 Rel-18 Incomplete Implementation of CR0688	Ericsson, MCC	WI TEI17 CAT A
Breakout	3267	CR 29.503 1496 Rel-19 Incomplete Implementation of CR0688	Ericsson, MCC	WI TEI17 CAT A
17.5	Service Based Interface Protocol Improvements Release 17 [SBIProtoc17]
Breakout	3171	CR 29.503 1485 Rel-17 Wrong CR implementation	Nokia, MCC	WI SBIProtoc16 CAT F
Breakout	3172	CR 29.503 1486 Rel-18 Wrong CR implementation	Nokia, MCC	WI SBIProtoc16 CAT A
Breakout	3173	CR 29.503 1487 Rel-19 Wrong CR implementation	Nokia, MCC	WI SBIProtoc16 CAT A
17.6	Multi-device and multi-identity enhancements [MuDe]
17.7	Stage-3 5GS NAS protocol development 17 [5GProtoc17] [5GProtoc17-non3GPP]
17.8	Protocol enhancements for Mission Critical Services [MCProtoc17]
17.9	Stage-3 SAE Protocol Development [SAES17] [SAES17-CSFB] [SAES17-non3GPP]
17.10	Enhancement for the 5G Control Plane Steering of Roaming for UE in CONNECTED mode [eCPSOR_CON]
17.11	IMS Stage-3 IETF Protocol Alignment [IMSProtoc17]
17.12	CT aspects of Enhancements to Mission Critical Data [eMCData3]
17.13	Stage 3 of Multimedia Priority Service (MPS) Phase 2 [MPS2]
17.14	PFD management enhancement [pfdManEnh]
17.15	BEst Practice of PFCP [BEPoP]
17.16	Restoration of PDN Connections in PGW-C/SMF Set [RPCPSET]
17.17	Stage 3 of eMONASTERY2 [eMONASTERY2]
17.18	CT aspects of 5GC architecture for satellite networks [5GSAT_ARCH-CT]
17.19	CT aspects of Enhanced MCCI with LMR Systems [eMCCI_CT]
17.20	CT aspects of AKMA [AKMA-CT]
17.21	PAP/CHAP protocols usage in 5GS [PAP_CHAP]
17.22	Service-based support for SMS in 5GC [SMS_SBI]
17.23	Enhancement of Inter-PLMN Roaming [EoIPR]
17.24	Mission Critical system migration and interconnection [MCSMI_CT]
17.25	CT aspects of Integration of GBA into SBA [GBA_5G]
17.26	Reliable Data Service Serialization Indication [RDSSI_CT]
17.27	CT aspects for Enabling Edge Applications [EDGEAPP]
17.28	CT aspects of eNPN [eNPN]
17.29	CT aspects of 5G_eLCS_ph2 [5G_eLCS_ph2]
17.30	CT aspects for ID_UAS [ID_UAS]
17.31	CT aspects of support of enhanced Industrial IoT [IIoT]
17.32	CT aspects of eV2XAPP [eV2XAPP]
17.33	CT aspects of 5G eEDGE [eEDGE_5GC]
17.34	Stage 3 for Enhancement of Network Slicing Phase 2 [eNS_Ph2]
3045	CR 29.531 0246 Rel-17 Text correction for Nnssf_NSSAIAvailability Service	Oracle Corporation	Moved to 16	WI eNS_Ph2 CAT F
3052	CR 29.531 0248 Rel-19 Clarification for NssfEventType	Oracle Corporation	Moved to 16	WI eNS_Ph2 CAT A Category should be A
3053	CR 29.531 0249 Rel-18 Clarification for NssfEventType	Oracle Corporation	Moved to 16	WI eNS_Ph2 CAT A Category should be A
3054	CR 29.531 0250 Rel-17 Clarification for NssfEventType	Oracle Corporation	Moved to 16	WI eNS_Ph2 CAT F
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]
Main	3147	CR 29.518 1230 Rel-18 IERSR for "UE Reachable for DL Traffic" and "Loss-of-Connectivity" events	Nokia	WI SBIProtoc18 CAT F
Main	3148	CR 29.518 1231 Rel-19 IERSR for "UE Reachable for DL Traffic" and "Loss-of-Connectivity" events	Nokia	WI SBIProtoc18 CAT A
18.7	Stage-3 5GS NAS protocol development 18 general aspects [5GProtoc18]
18.8	Stage-3 5GS NAS protocol development 18 non 3GPP aspects [5GProtoc18-non3GPP]
18.9	Stage-3 SAE Protocol Development [SAES18]
18.10	Stage-3 SAE Protocol Development CSFB [SAES18-CSFB]
18.11	Stage-3 SAE Protocol Development non 3GPP [SAES18-non3GPP]
18.12	Protocol enhancements for Mission Critical Services [MCProtoc18]
18.13	MPS for Supplementary Services [MPSSupServ]
18.14	CT aspects of Mission Critical Services over 5MBS [MCOver5MBS]
18.15	CT aspects of Mission Critical Services over 5GProSe [MCOver5GProSe]
18.16	IMS Stage-3 IETF Protocol Alignment [IMSProtoc18]
18.17	CT aspects of Signal level Enhanced Network Selection [SENSE]
18.18	Rel-18 Enhancements of UE Policy [UEP18]
18.19	5GS support of NR RedCap UE with long eDRX for RRC_INACTIVE State [NR_REDCAP_Ph2]
18.20	CT aspects on Multiple location report for MT-LR Immediate Location Request for regulatory services [TEI18_MLR]
18.21	Enhancement of Shared Data ID and Handling [ShDatID_H]
18.22	CT Aspects of Edge Computing Phase 2 [EDGE_Ph2]
18.23	Enhancement of NSAC for maximum number of UEs with at least one PDU session/PDN connection [eNSAC]
18.24	Mission critical system migration and interconnection enhancements [eMCSMI_IRail]
18.25	CT aspects of application layer support for V2X services; Phase 3 [V2XAPP_Ph3]
18.26	CT aspects of proximity based services in 5GS Phase 2 [5G_ProSe_Ph2]
18.27	Support for 5WWC Phase 2 [5WWC_Ph2]
18.28	Enhancement of application detection event exposure [TEI18_ADEE]
18.29	CT aspects of General Support of IPv6 Prefix Delegation in 5GS [TEI18_IPv6PD]
18.30	CT aspects of 5G System with Satellite Backhaul [5GSATB]
18.31	Timing Resiliency and URLLC enhancements [TRS_URLLC]
18.32	Extensions to the TSC Framework to support DetNet [DetNet]
18.33	CT aspects for Enabling Edge Applications Phase 2 [EDGEAPP_Ph2]
18.34	Rel-18 enhancements of session management policy control [SMPC18]
18.35	CT aspects of 5G System Enabler for Service Function Chaining [SFC]
18.36	Enhancement of Network Automation Enablers [eNetAE]
18.37	CT aspects of enhancement of 5G UE Policy [eUEPO]
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]
Main	3119	CR 29.518 1224 Rel-18 LCS-UP Context Creation and Removal	ZTE	WI 5G_eLCS_Ph3 CAT F
Main	3120	CR 29.518 1225 Rel-19 LCS-UP Context Creation and Removal	ZTE	WI 5G_eLCS_Ph3 CAT A
Main	3121	CR 29.572 0362 Rel-18 Invoke Nlmf_Location_UPConfig to Releae LCS-UP Connection	ZTE	WI 5G_eLCS_Ph3 CAT F
Main	3122	CR 29.572 0363 Rel-19 Invoke Nlmf_Location_UPConfig to Releae LCS-UP Connection	ZTE	WI 5G_eLCS_Ph3 CAT A
3232	CR 29.518 1240 Rel-19 Support for multiple LCS UPP	Huawei	Moved to 19.4	WI 5G_eLCS_Ph3 CAT B
Main	3255	CR 29.518 1241 Rel-18 Correction on LCS Correlation ID for LCS UPP CM	Ericsson	WI 5G_eLCS_Ph3 CAT F
Main	3256	CR 29.518 1242 Rel-19 Correction on LCS Correlation ID for LCS UPP CM	Ericsson	WI 5G_eLCS_Ph3 CAT A
18.41	CT aspects of Enhanced support of Non-Public Networks Phase 2 [eNPN_Ph2]
3119	CR 29.518 1224 Rel-18 LCS-UP Context Creation and Removal	ZTE	Moved to 18.40	WI 5G_eLCS_Ph3 CAT F
3120	CR 29.518 1225 Rel-19 LCS-UP Context Creation and Removal	ZTE	Moved to 18.40	WI 5G_eLCS_Ph3 CAT A
3121	CR 29.572 0362 Rel-18 Invoke Nlmf_Location_UPConfig to Releae LCS-UP Connection	ZTE	Moved to 18.40	WI 5G_eLCS_Ph3 CAT F
3122	CR 29.572 0363 Rel-19 Invoke Nlmf_Location_UPConfig to Releae LCS-UP Connection	ZTE	Moved to 18.40	WI 5G_eLCS_Ph3 CAT A
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	3233	CR 29.175 0075 Rel-18 Correction on the SessionId attribute description	Ericsson	WI NG_RTC CAT F
Plenary	3234	CR 29.175 0076 Rel-19 Correction on the SessionId attribute description	Ericsson	WI NG_RTC CAT A
Plenary	3253	CR 29.175 0084 Rel-18 Missing condition for mediaInstruction	Huawei	WI NG_RTC_Ph2 CAT F WIC should be NG_RTC
Plenary	3254	CR 29.175 0085 Rel-19 Missing condition for mediaInstruction	Huawei	WI NG_RTC_Ph2 CAT A WIC should be NG_RTC
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]
Breakout	3112	CR 29.503 1479 Rel-18 Service Specific Authorization for AF Requested QoS	Nokia	WI GMEC CAT F
Breakout	3113	CR 29.503 1480 Rel-19 Service Specific Authorization for AF Requested QoS	Nokia	WI GMEC CAT A
Breakout	3114	CR 29.505 0537 Rel-18 Service Specific Authorization for AF Requested QoS	Nokia	WI GMEC CAT F
Breakout	3115	CR 29.505 0538 Rel-19 Service Specific Authorization for AF Requested QoS	Nokia	WI GMEC CAT A
18.64	CT aspects of 5MBS_Ph2 [5MBS_Ph2]
18.65	CT aspects of Enhancement of Network Slicing Phase 3 [eNS_Ph3]
3043	CR 29.531 0244 Rel-19 Text correction for Nnssf_NSSAIAvailability Service	Oracle Corporation	Moved to 16	WI eNS_Ph3 CAT A Category should be A
3044	CR 29.531 0245 Rel-18 Text correction for Nnssf_NSSAIAvailability Service	Oracle Corporation	Moved to 16	WI eNS_Ph3 CAT F
3189	CR 29.503 1490 Rel-19 Slice deregistration inactivity timer value clarification	NTT DOCOMO	Moved to 19.4	WI eNS_Ph3, TEI19 CAT F
18.66	CT aspects of XRM [XRM]
Main	3068	CR 29.281 0138 Rel-18 PDU Set Information Container	Nokia	WI XRM CAT F
Main	3069	CR 29.281 0139 Rel-19 PDU Set Information Container	Nokia	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]
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	3062	WID new Rel-19 new WID_Protocol for AI Data Collection from UPF	China Mobile
19.2.2	CT4 Supported WIDs
19.3	Revised WIDs for Rel-19
3314	WID revised Rel-19 Revised WID on CT aspects of MINT support in EPS for 5G-only national roaming UE	China Telecommunications Corp.	Moved to 19.3.2
19.3.1	CT4 Led WIDs
Plenary	3163	WID revised Rel-19 Revised WID on CT aspects on Advanced Media Delivery	Qualcomm Incorporated
3182	CR 29.564 0143 Rel-19 Skip Reporting Instruction	Ericsson, Nokia	Moved to 7	WI FS_PAIDC_UPF CAT B
19.3.2	CT4 Supported WIDs
Plenary	3067	WID revised Rel-19 Revised WID on CT aspects of Extended Reality and Media service (XRM) Phase 2	Nokia
Plenary	3300	WID revised Rel-19 WID on CT aspects of Architecture support of Ambient power-enabled Internet of Things	Huawei
Plenary	3314	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	3037	CR 29.504 0319 Rel-19 Service parameter authorization in the PCF	Nokia	WI TEI19, UEP19 CAT F
Breakout	3038	CR 29.504 0320 Rel-19 Detailed UE Policy Delivery Outcome in the UDR	Nokia	WI TEI19, UEP19 CAT B
Breakout	3041	CR 29.509 0235 Rel-19 General text corrections	Orange	WI TEI19 CAT F
Plenary	3050	CR 29.571 0663 Rel-19 Correction for description of AMFRegionID	Vodafone Romania S.A.	WI TEI19 CAT F
Breakout	3058	discussion Rel-19 Adding new cause value to Nlmf_Location service	OPPO
Breakout	3059	CR 29.572 0360 Rel-19 Adding new cause value to Nlmf_Location service	OPPO	WI TEI19, 5G_eLCS_Ph3 CAT B
Breakout	3060	CR 29.572 0361 Rel-19 LMF relocation procedure related amendments	OPPO	WI TEI19, 5G_eLCS_Ph3 CAT B
Main	3070	CR 29.244 0979 Rel-19 Correction to End of Data Burst marking	Nokia	WI TEI19, XRM CAT F
Breakout	3094	CR 29.503 1475 Rel-19 SoR Clarifications	Ericsson	WI eCPSOR_CON, TEI19 CAT F
Breakout	3099	CR 29.505 0536 Rel-19 AF Specific UE Identifier storage in UDR	Nokia	WI EDGEAPP, TEI19 CAT B
Plenary	3102	CR 23.003 0715 Rel-19 Essential correction to the definition of the Routing identifier	OPPO	WI 5G_eLCS_Ph3, TEI19 CAT F
Plenary	3104	CR 23.003 0716 Rel-19 Mixture of two and three digit E.212 MNC codes within a single geographic MCC area shall instead be stated subject on local/regional regulations, i.e. shall be a national matter	Swedish Post and Telecom Authority (PTS)	WI TEI19 CAT F
Plenary	3108	CR 29.002 1274 Rel-19 Adding Serving node information as optional IE to Report the SM-Delivery Status	Nokia, AT&T	WI TEI19 CAT B
Breakout	3118	CR 29.503 1482 Rel-19 Remove references to re-authentication default subscription	Ericsson	WI HN_Auth, TEI19 CAT F
Main	3141	CR 29.536 0151 Rel-19 Exclude a condition for network slice admission control	ZTE	WI TEI19, eNSAC CAT F
Main	3164	CR 29.274 2131 Rel-19 Duplication PDN Session Detection in case of static IP allocation	Samsung	WI TEI19 CAT F
Plenary	3180	CR 29.571 0670 Rel-19 RAT Types for 2G/3G interworking scenarios	Ericsson	WI TEI19 CAT F
Main	3184	CR 29.564 0144 Rel-19 Including RAT type in the Event Reports	Ericsson	WI TEI19 CAT B
Plenary	3185	CR 23.003 0719 Rel-19 LCS Session Identity and LCS User Plane Connection/Binding ID	Ericsson	WI TEI19 CAT F
Breakout	3189	CR 29.503 1490 Rel-19 Slice deregistration inactivity timer value clarification	NTT DOCOMO	WI eNS_Ph3, TEI19 CAT F
Main	3190	CR 29.244 0990 Rel-19 Enhancements on the PFD Provisioning	Ericsson	WI TEI19 CAT B
Main	3191	CR 29.244 0991 Rel-19 (Un)Solicited Application Reporting and Application Detection Information	Ericsson	WI TEI19 CAT F
Main	3192	CR 29.244 0992 Rel-19 Editorial corrections	Ericsson	WI TEI19 CAT D
Breakout	3193	CR 29.572 0364 Rel-19 Support Multiple LCSUPP Connections per UE	Nokia	WI TEI19, 5G_eLCS_Ph3 CAT F
Plenary	3206	CR 29.500 0477 Rel-19 Correction of misused reference to "LCI" and typo	Nokia	WI TEI19 CAT F
Main	3207	CR 29.518 1234 Rel-19 Corrections to re-used data types	Nokia	WI TEI19 CAT F
Plenary	3208	CR 29.510 1219 Rel-19 Remove Redundant references	Nokia	WI TEI19 CAT F
Breakout	3209	CR 29.572 0365 Rel-19 Correction to the references	Nokia	WI TEI19 CAT F
Plenary	3213	CR 29.571 0674 Rel-19 Correction on the definition of Tac and MbsSecurityContext attributes	Huawei	WI TEI19 CAT F
Main	3214	CR 29.518 1235 Rel-19 Event Exposure on UE Reachable for DL Traffic for UE in RRC-Inactive	Huawei	WI TEI19 CAT F
Plenary	3224	CR 29.510 1225 Rel-19 Correction in OpenAPI	Huawei	WI TEI19 CAT F
Plenary	3229	CR 29.571 0675 Rel-19 Editorial corrections	Huawei	WI TEI19 CAT D
Main	3232	CR 29.518 1240 Rel-19 Support for multiple LCS UPP	Huawei	WI TEI19, 5G_eLCS_Ph3 CAT B
Breakout	3242	CR 29.338 0064 Rel-19 SM delivery HPLMN routing via SMS Router and SMSF addresses in RDR/RDA.	Cisco Systems, Nokia, AT&T	WI TEI19 CAT F
Breakout	3243	CR 29.338 0065 Rel-19 Adding MNR5GN3G to MWD Status	Cisco Systems	WI TEI19 CAT F
Breakout	3248	CR 29.503 1492 Rel-19 AF Specific GPSI Generation	Ericsson	WI EDGEAPP, TEI19 CAT F
Breakout	3249	CR 29.338 0066 Rel-19 SMSF Address encoding in Serving-Node and Additional-Serving-Node	Cisco	WI TEI19 CAT F
Plenary	3251	CR 29.002 1275 Rel-19 SMSF Address encoding in Serving-Node and Additional-Serving-Node	Cisco Systems	WI TEI19 CAT F
Main	3268	CR 29.502 0887 Rel-19 Correction on DNN Failure Handling with I-SMF	Ericsson	WI TEI19, 5G_CIoT CAT F
Main	3269	CR 29.502 0888 Rel-19 PDU Session Re-establishment due to N3 Path Failure	Ericsson	WI TEI19 CAT B
Main	3270	CR 29.502 0889 Rel-19 Release of Mismatching PDU Session in CM-CONNECTED Mode	Ericsson	WI TEI19 CAT F
Main	3271	CR 29.502 0890 Rel-19 User Plance Security Policy	Ericsson	WI TEI19 CAT B
Main	3272	CR 29.502 0891 Rel-19 VPLMN QoS Constraints for MPS PDU Session	Ericsson	WI TEI19 CAT B
Breakout	3273	CR 29.503 1497 Rel-19 RAT Type for PDU Session Events	Ericsson, Verizon	WI TEI19, 5G_CIoT CAT F
Plenary	3274	CR 29.510 1230 Rel-19 Disaster Roaming Indication	Ericsson	WI TEI19 CAT F
Plenary	3275	CR 29.510 1231 Rel-19 Access Token Retrive Key Operation	Ericsson	WI TEI19, SBA_KDATV-SEC CAT B
Breakout	3276	CR 29.572 0369 Rel-19 Multiple LCS-UPP Connection Support per UE	Ericsson	WI TEI19, 5G_eLCS_Ph3 CAT C
Main	3298	CR 29.502 0892 Rel-19 Update the AlternativeQosProfile	CATT	WI TEI19, XRM CAT F
Breakout	3301	CR 29.572 0370 Rel-19 Add LMF ID for user plane connection association	Huawei	WI 5G_eLCS_Ph3, TEI19 CAT B
Plenary	3310	CR 24.080 0127 Rel-19 Add ExtendedFacility	Huawei	WI TEI19 CAT B
Plenary	3315	CR 29.573 0231 Rel-19 Correction on senderN32fPortList and senderN32fPort attributes	Huawei	WI TEI19 CAT F
Breakout	3316	CR 29.504 0327 Rel-19 Introduction of UE ID Mapping Info Enhancement Feature	Ericsson	WI TEI19 CAT B
Plenary	3329	CR 29.510 1235 Rel-19 Addition of subscriber segmentation in chfinfo	Huawei	WI TEI19 CAT B
Breakout	3343	CR 29.328 0662 Rel-19 Correct the processing for T-ADS	Huawei	WI TEI19 CAT F
Breakout	3344	CR 29.272 0880 Rel-19 Correct the processing for T-ADS.	Huawei	WI TEI19 CAT F
3345	CR 29.571 0681 Rel-19 Update and replace obsoleted HTTP RFC	Huawei	Moved to 19.40	WI TEI19 CAT F
Plenary	3348	CR 24.010 0008 Rel-19 Changes to Supplementary service procedures for using Extened Facility IE	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]
19.7	CT aspects of Providing per-subscriber VLAN instructions from UDM and DN-AAA [TEI19_VLANSUB]
Breakout	3110	CR 29.503 1477 Rel-19 VlanTag correction	Nokia	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	3039	CR 29.503 1473 Rel-19 Wrong implementation of CR 1364	Nokia, MCC	WI SBIProtoc19 CAT F
Plenary	3042	CR 29.510 1201 Rel-19 Support for TAI-level weights in the NWDAF NF Profile	Orange	WI SBIProtoc19 CAT B
3047	CR 29.510 1202 Rel-19 producerSnssaiList and producerNsiList claims in Access Token	Nokia	withdrawn	WI SBIProtoc19 CAT F
Breakout	3049	CR 29.503 1474 Rel-19 Adding Serving node information as optional IE to Report the SM-Delivery Status	Nokia, AT&T, Cisco	WI SBIProtoc19 CAT B
Plenary	3085	CR 29.510 1204 Rel-19 producerSnssaiList and producerNsiList claims in Access Token	Nokia	WI SBIProtoc19 CAT F
Plenary	3086	LS out Rel-19 Reply LS on Four critical vulnerabilities in the access control mechanism of the 5G core Network	Nokia	CVD-2025-0101 To: GSMA CVD PoE CC: SA3
Plenary	3087	CR 29.510 1205 Rel-19 consumerPlmnId claim in Access Token	Nokia	WI SBIProtoc19 CAT F
Plenary	3088	CR 29.510 1206 Rel-19 Requester's PLMN IDs in Access Token Request	Nokia	WI SBIProtoc19 CAT F
Plenary	3089	CR 29.500 0474 Rel-19 Requester's PLMN IDs in service request to SCP	Nokia	WI SBIProtoc19 CAT F
Main	3090	CR 29.518 1223 Rel-19 Rejection of SMF initiated request during 5GS to EPS handover	Nokia	WI SBIProtoc19 CAT F
Main	3091	CR 29.502 0880 Rel-19 Incomplete statement in Release SM Context service operation	Nokia	WI SBIProtoc19 CAT F
Plenary	3092	CR 29.500 0475 Rel-19 Editor's note on NRF API URI usage for NFc reselection in inter-PLMN scenarios	Nokia	WI SBIProtoc19 CAT F
Plenary	3095	CR 29.500 0476 Rel-19 HTTP status code 422	Nokia	WI SBIProtoc19 CAT B
Breakout	3096	CR 29.505 0535 Rel-19 HTTP status code 422	Nokia	WI SBIProtoc19 CAT B
Breakout	3097	CR 29.503 1476 Rel-19 IP Index in DnnInfo	Nokia, Verizon	WI SBIProtoc19 CAT B
Plenary	3098	CR 29.510 1207 Rel-19 IP Index in SmfInfo	Nokia, Verizon	WI SBIProtoc19 CAT B
Breakout	3107	CR 29.598 0096 Rel-19 Partial timer delete success	Nokia	WI SBIProtoc19 CAT B
Plenary	3109	CR 29.501 0179 Rel-19 Use informative wording in annex E	Nokia	WI SBIProtoc19 CAT F
Breakout	3111	CR 29.503 1478 Rel-19 Supported Feature clarification	Nokia	WI SBIProtoc19 CAT F
Main	3136	discussion Rel-19 Discussion on an optimization of reporting mode per event	ZTE
Main	3137	CR 29.564 0142 Rel-19 Introduce a new attribute for UpfEvent	ZTE	WI SBIProtoc19 CAT F
Main	3138	CR 29.518 1229 Rel-19 Introduce a new attribute for AmfEvent	ZTE	WI SBIProtoc19 CAT F
Main	3139	LS out Rel-19 LS on reporting mode per event	ZTE	To: CT3 Cc:
Breakout	3174	CR 29.503 1488 Rel-19 Unsuccessful shared data retrieval clarification	Nokia	WI SBIProtoc19 CAT F
Breakout	3175	CR 29.503 1458 Rel-19 Shared Data Status	Nokia	WI SBIProtoc19 CAT B
Plenary	3212	CR 29.573 0230 Rel-19 Modifying parameters of an existing N32 association	Nokia	WI SBIProtoc19 CAT B
Breakout	3244	CR 29.503 1491 Rel-19 Timestamp in EE immediate event report for "SUPI-PEI association" events	Ericsson	WI SBIProtoc19 CAT B
Breakout	3247	CR 29.505 0539 Rel-19 PEI change timestamp in PeiUpdateInfo	Ericsson	WI SBIProtoc19 CAT B
Breakout	3250	CR 29.503 1493 Rel-19 Event Exposure Expiry Time Subscription Update	Ericsson	WI SBIProtoc19 CAT B
Plenary	3261	CR 29.500 0478 Rel-19 Binding Indication in Notification	Ericsson	WI SBIProtoc19 CAT F
Main	3262	CR 29.502 0885 Rel-19 Clarification on Reselction of Additional (H-)SMF	Ericsson	WI SBIProtoc19 CAT F
Main	3263	CR 29.502 0886 Rel-19 Handling of Insufficient Resource for PDU Session Establishment	Ericsson	WI SBIProtoc19 CAT F
Breakout	3264	CR 29.572 0368 Rel-19 Essential Clarification for Bits Order for SIB Types Bitmap	Ericsson	WI SBIProtoc19 CAT F
Plenary	3322	CR 29.510 1233 Rel-19 UDM AnyUe selection for Nudm_EE exposure service	Ericsson	WI SBIProtoc19 CAT B
Breakout	3324	CR 29.503 1498 Rel-19 UDM AnyUe selection for Nudm_EE exposure service	Ericsson	WI SBIProtoc19 CAT B
Plenary	3325	CR 29.510 1234 Rel-19 Registration and discovery of UDRs storing data for AnyUe	Ericsson	WI SBIProtoc19 CAT B
19.11	Subscriber Data Migration [SUBDMIG]
Plenary	3116	CR 23.527 0099 Rel-19 AUSF subscribers reallocation	Ericsson	WI SUBDMIG CAT B
Plenary	3117	CR 29.503 1481 Rel-19 AUSF subscribers reallocation	Ericsson	WI SUBDMIG CAT B
Plenary	3144	CR 23.527 0100 Rel-19 "Deregistration and Unsubscribe required" for data migration	Ericsson	WI SUBDMIG CAT B
Plenary	3145	CR 29.503 1483 Rel-19 "Deregistration and Unsubscribe required" for data migration	Ericsson	WI SUBDMIG CAT B
Plenary	3146	CR 29.504 0321 Rel-19 "Deregistration and Unsubscribe required" for data migration	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	3186	CR 29.503 1489 Rel-19 ECRATU Feature Flag	NTT DOCOMO	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]
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	3152	CR 29.503 1484 Rel-19 PEI Requested in monitoring event configuration	Ericsson	WI TEI19_RVAS CAT B
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]
Plenary	3072	CR 29.502 0877 Rel-19 Correction to H-SMF instance reselection by HPLMN	Nokia	WI TEI19_NFsel_by_tPLMN CAT F
Plenary	3073	CR 29.500 0473 Rel-19 Fixing references for Authorization of NF service access	Nokia	WI TEI19_NFsel_by_tPLMN CAT F
19.26	CT aspects of enhancement of support for Edge Computing in 5G Core network - Phase 3 [eEDGE_5GC_Ph3]
Main	3071	CR 29.244 0980 Rel-19 Protocol-specific configuration parameters for N6 delay measurements	Nokia	WI eEDGE_5GC_Ph3 CAT F
Main	3142	CR 29.571 0668 Rel-19 Correct the description of attributes included in LocalOffloadingManagementInfo	ZTE	WI eEDGE_5GC_Ph3 CAT F
Main	3143	CR 29.244 0986 Rel-19 Add a reference to stage 2 specification	ZTE	WI eEDGE_5GC_Ph3 CAT F
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]
Main	3211	CR 29.502 0884 Rel-19 Update of Nsmf_PDUSession_Update service to support Non-3GPP Device Connection Information	Nokia, InterDigital	WI UIA_ARC CAT B
Plenary	3346	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]
19.31	CT Aspects of Phase3 for UAS, UAV and UAM [UAS_Ph3]
Plenary	3210	CR 29.510 1220 Rel-19 Correction to the ServiceName	Nokia	WI UAS_Ph3 CAT F
Main	3277	CR 29.518 1243 Rel-19 Altitude reporting cancelation	LG Electronics, Ericsson	WI UAS_Ph3 CAT C
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]
Breakout	3124	CR 29.272 0877 Rel-19 SF Satellite Operation Not Allowed in UE Subscription	ZTE	WI 5GSAT_Ph3_ARCH CAT B Overlapping with 3165, 3291
Breakout	3165	CR 29.272 0878 Rel-19 Handling S&F not allowed	Samsung	WI 5GSAT_Ph3_ARCH CAT B
Breakout	3291	CR 29.272 0879 Rel-19 Add subscription data for S&F Satellite Operation	CATT	WI 5GSAT_Ph3_ARCH CAT B
Breakout	3125	CR 29.230 0726 Rel-19 AVP for SF Satellite Operation Not Allowed	ZTE	WI 5GSAT_Ph3_ARCH CAT B Overlapping with 3166
Breakout	3166	CR 29.230 0727 Rel-19 AVP for SF Satellite Operation Allowed	Samsung	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]
19.37	CT aspects of UPF enhancement for Exposure And SBA Phase 2 [UPEAS_Ph2]
Main	3188	CR 29.564 0145 Rel-19 Correction to remainingDataReports	Ericsson, Nokia	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	3317	Work Plan Rel-19 Work plan for the CT aspects of AIML_CN	vivo
Plenary	3140	CR 29.510 1211 Rel-19 Update of NWDAF discovery	ZTE, Nokia	WI AIML_CN CAT F
Plenary	3194	pCR 29.570 Rel-19 SCP Event Exposure Data Types and Alignment with SA2 Requirements	Nokia	Overlapping with 3218
Plenary	3218	pCR 29.570 Rel-19 Addressing the Editor's notes	Huawei
Plenary	3195	pCR 29.570 Rel-19 Corrections to SCP Event Exposure Data Definitions, API Versioning, and OpenAPI	Nokia
Plenary	3196	CR 29.571 0671 Rel-19 Addition of OverloadControlInfo data type	Nokia	WI AIML_CN CAT B
Plenary	3197	CR 29.571 0672 Rel-19 Update the NF signalling information	Nokia	WI AIML_CN CAT F
Plenary	3198	CR 29.510 1215 Rel-19 Support for VFL Access Token Parameters for External AF	Nokia	WI AIML_CN CAT B Overlapping with 3228
Plenary	3228	CR 29.510 1226 Rel-19 Access token to support VFL	Huawei	WI AIML_CN CAT B
Main	3199	CR 29.518 1233 Rel-19 Support per-UE Signalling Analytics in Signalling-Measurement-Report Event	Nokia	WI AIML_CN CAT B
Plenary	3200	CR 29.510 1216 Rel-19 VFL services	Nokia	WI AIML_CN CAT B
Breakout	3257	CR 29.572 0366 Rel-19 AIML Positioning Method	Ericsson	WI AIML_CN CAT B
Breakout	3258	CR 29.572 0367 Rel-19 Resolve Editor's Notes	Ericsson	WI AIML_CN CAT F Overlapping with 3319
Breakout	3319	CR 29.572 0371 Rel-19 Address ENs related to Nlmf_DataExposure service	vivo	WI AIML_CN CAT F
Breakout	3318	CR 24.080 0128 Rel-19 Clarification on deferred Location messages regarding on data collection	vivo	WI AIML_CN CAT F
TS 29.570v0.4.0	Huawei
19.40	CT aspects of Next Generation Real time Communication services [NG_RTC_Ph2]
Breakout	3100	CR 29.571 0666 Rel-19 Definition of transparent containers for IMS Exposure	Ericsson	WI NG_RTC_Ph2 CAT F
Breakout	3101	CR 29.562 0187 Rel-19 Incorrect "imsUeId" pattern in Nhss_imsEE service	Ericsson	WI NG_RTC_Ph2 CAT F
Breakout	3103	CR 29.175 0073 Rel-19 Correction on the data channel multiplexing	Huawei	WI NG_RTC_Ph2 CAT F
Breakout	3128	CR 29.510 1209 Rel-19 Media Capability Defined by Operator	ZTE	WI NG_RTC_Ph2 CAT F
Breakout	3129	CR 29.175 0074 Rel-19 Transcode DC Media to Video Media and Set to One-Way Only	ZTE	WI NG_RTC_Ph2 CAT B
Breakout	3205	CR 29.510 1218 Rel-19 Update Service names for IMS	Nokia	WI NG_RTC_Ph2 CAT B
Breakout	3235	CR 29.571 0677 Rel-19 Reference update: RFC 9796	Ericsson	WI NG_RTC_Ph2 CAT F Overlapping with 3345
Breakout	3345	CR 29.571 0681 Rel-19 Update and replace obsoleted HTTP RFC	Huawei	WI TEI19 CAT F
Breakout	3236	CR 29.175 0077 Rel-19 Nimsas_ImsParameterProvision API: removal of EN on RCD	Ericsson	WI NG_RTC_Ph2 CAT B Overlapping with 3281
Breakout	3240	CR 29.175 0081 Rel-19 Nimsas_ImsParameterProvision: correction on the Public User Identity	Ericsson	WI NG_RTC_Ph2 CAT F Overlapping with 3281
Breakout	3281	CR 29.175 0088 Rel-19 Update to Nimsas_ImsParameterProvision Service	China Mobile	WI NG_RTC_Ph2 CAT B
Breakout	3237	CR 29.175 0078 Rel-19 Nimsas_ImsParameterProvision API: editorial corrections	Ericsson	WI NG_RTC_Ph2 CAT D
Breakout	3238	CR 29.175 0079 Rel-19 Nimsas_ImsPP_Delete service operation definition	Ericsson	WI NG_RTC_Ph2 CAT B
Breakout	3239	CR 29.175 0080 Rel-19 Nimsas_ImsParameterProvision API: "201 Created" and "204 No Content" responses	Ericsson	WI NG_RTC_Ph2 CAT B
Breakout	3241	CR 29.175 0082 Rel-19 Nimsas_ImsParameterProvision API: specification of the OpenAPI file	Ericsson	WI NG_RTC_Ph2 CAT B Overlapping with 3280
Breakout	3280	CR 29.175 0087 Rel-19 Define the OpenAPI for Nimsas_ImsParameterProvision Service	China Mobile	WI NG_RTC_Ph2 CAT B
Breakout	3245	CR 29.175 0083 Rel-19 Instruction on transcoding for interworking	Huawei	WI NG_RTC_Ph2 CAT B
Breakout	3246	CR 29.176 0040 Rel-19 Instruction on transcoding for interworking	Huawei	WI NG_RTC_Ph2 CAT B
Breakout	3252	CR 29.176 0041 Rel-19 Correction on the data channel multiplexing	Huawei	WI NG_RTC_Ph2 CAT F
Breakout	3279	CR 29.175 0086 Rel-19 Update the service operation description	China Mobile	WI NG_RTC_Ph2 CAT B
Breakout	3282	CR 29.175 0089 Rel-19 Remove the editor note for Nimsas_ImsEE Service	China Mobile	WI NG_RTC_Ph2 CAT B
Breakout	3283	CR 29.175 0090 Rel-19 Remove the editor note in overview	China Mobile	WI NG_RTC_Ph2 CAT B
3290	CR 29.504 0324 Rel-19 Update the Nudr_DataRepository resource to add AIoT device profile data	China Mobile	Moved to 19.70	WI AmbientIoT-CT CAT B
Breakout	3320	CR 29.562 0188 Rel-19 Cancel procedure for subscriber specific IMS Events	Ericsson	WI NG_RTC_Ph2 CAT B
Breakout	3334	CR 29.571 0680 Rel-19 Correct the description of appBinInfo in ImsEventFilter	Huawei	WI NG_RTC_Ph2 CAT F
Breakout	3335	CR 29.175 0091 Rel-19 Add DC interworking indication in DcMediaSpecification	Huawei	WI NG_RTC_Ph2 CAT B
Breakout	3336	CR 29.329 0255 Rel-19 Add commands and AVPs to support IMS AS registration to HSS	Huawei	WI NG_RTC_Ph2 CAT B
Breakout	3337	CR 29.328 0660 Rel-19 Add IMS AS registration to HSS procedure via Sh interface	Huawei	WI NG_RTC_Ph2 CAT B
Breakout	3338	CR 29.175 0092 Rel-19 Add PUT operation in Nimsas_ImsSessionManagement_Update	Huawei	WI NG_RTC_Ph2 CAT F
Breakout	3339	CR 29.562 0189 Rel-19 Add 403 Forbidden in data structure of IMS AS registration in Nimsas_ImsUECM	Huawei	WI NG_RTC_Ph2 CAT F
Breakout	3340	CR 29.328 0661 Rel-19 Add HSS subscription to IMA AS procedure via Sh interface	Huawei	WI NG_RTC_Ph2 CAT B
Breakout	3341	CR 29.329 0256 Rel-19 Add commands and AVPs to support HSS subscription to IMS AS	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]
Plenary	3187	CR 23.003 0720 Rel-19 Context ID for MPQUIC	Ericsson	WI MASSS CAT B
Plenary	3326	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]
19.47	CT aspects of 5G NR Femto [5G_Femto]
Plenary	3123	CR 29.571 0667 Rel-19 Update or Removal of CAG List	ZTE	WI 5G_Femto CAT F
19.48	CT aspects of Extended Reality and Media service (XRM) Phase 2 [XRM_Ph2]
Main	3074	CR 29.244 0981 Rel-19 Data Burst Size and Time to Next Burst marking	Nokia	WI XRM_Ph2 CAT F Overlapping with 3179
Main	3179	CR 29.244 0989 Rel-19 Remove editor's note for BSSIZE and TTNB	Ericsson	WI XRM_Ph2 CAT B
Main	3075	CR 29.244 0982 Rel-19 Corrections to (S)RTP Multiplexed Media Identification Information encoding	Nokia	WI XRM_Ph2 CAT F
Main	3076	CR 29.244 0983 Rel-19 Corrections on Transferring media related information over N6	Nokia	WI XRM_Ph2 CAT F Overlapping with 3178
Main	3178	CR 29.244 0988 Rel-19 Remove editor's notes for Media related Information security	Ericsson	WI XRM_Ph2 CAT B
Main	3077	CR 29.571 0664 Rel-19 Additional RTP header extensions in ProtocolDescriptionRm	Nokia	WI XRM_Ph2 CAT B
Main	3078	CR 29.571 0665 Rel-19 RTP header extension for Expedited Transfer Indication	Nokia	WI XRM_Ph2 CAT B
Main	3079	CR 29.244 0984 Rel-19 RTP header extension for Expedited Transfer Indication	Nokia	WI XRM_Ph2 CAT B
Main	3080	CR 29.502 0878 Rel-19 Corrections on Available Bitrate Monitoring	Nokia	WI XRM_Ph2 CAT F
Main	3081	CR 29.502 0879 Rel-19 PDU Set handling in non-3GPP access	Nokia	WI XRM_Ph2 CAT F
Main	3082	CR 29.571 0651 Rel-19 PDU Set Importance for N6-unmarked PDUs	Nokia, Lenovo	WI XRM_Ph2, 5G_RTP_Ph2 CAT B
Main	3083	CR 29.244 0973 Rel-19 PDU Set Importance for N6-unmarked PDUs	Nokia, Lenovo	WI XRM_Ph2, 5G_RTP_Ph2 CAT B
Main	3084	LS out Rel-19 Reply LS on N6-Unmarked PDUs	Nokia	S4-250738 To: SA4 CC: SA2, CT3
Main	3159	CR 29.571 0669 Rel-19 New RTP header extension type	Lenovo	WI XRM_Ph2 CAT B
Main	3176	CR 29.502 0882 Rel-19 Transport Level Marking Indication	Ericsson, Nokia	WI XRM_Ph2 CAT B Overlapping with 3328
Main	3328	CR 29.502 0894 Rel-19 Support of Transport Level Marking with I-SMF insertion	Huawei	WI XRM_Ph2 CAT B
Main	3177	CR 29.244 0987 Rel-19 Transport Level Marking Indication	Ericsson, Nokia	WI XRM_Ph2 CAT B Overlapping with 3215
Main	3215	CR 29.244 0994 Rel-19 Transport level marking enhancement	Huawei	WI XRM_Ph2 CAT B
Main	3327	CR 29.502 0893 Rel-19 QoS Notification Control of PDU Set QoS in only one direction	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]
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]
Plenary	3066	Work Plan Rel-19 Work Plan for Energy_Sys	Samsung
Main	3126	CR 29.244 0985 Rel-19 Provision of I-UPF ID over N4 Interface	ZTE	WI EnergySys CAT B
Main	3127	CR 29.502 0881 Rel-19 Provision of I-UPF ID over N16a Interface	ZTE	WI EnergySys CAT B Overlapping with 3203
Main	3203	CR 29.502 0883 Rel-19 Reporting of I-UPF ID and ULI for Energy Consumption information collection	Nokia	WI EnergySys CAT B
Main	3202	CR 29.244 0993 Rel-19 Usage Reporting for EIF Energy Consumption Support	Nokia	WI EnergySys CAT B
Main	3204	CR 29.571 0673 Rel-19 Removal of Editor’s Note for EnergySavingIndicator	Nokia	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	3342	CR 29.244 0996 Rel-19 Add Rule Information in Application Detection Information IE to support IMS restoration procedures after PCRF/PCF failure	Huawei	WI IMS_RES-CT CAT B
Plenary	3347	CR 23.334 0186 Rel-19 Add RTCP RR packets trigger procedure to support IMS restoration procedures after PCRF/PCF failure	Huawei	WI IMS_RES-CT CAT B
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	3061	CR 29.510 1203 Rel-19 Addition of the AIoT Device Id ranges in AdmInfo	CEWiT	WI AmbientIoT-CT CAT B 3061, 3106, 3131, 3167, 3259, 3312 are overlapping with each other
Plenary	3106	CR 29.510 1208 Rel-19 Regular expression for AIoT device permanent IDs	Nokia	WI AmbientIoT-CT CAT F
Plenary	3131	CR 29.510 1210 Rel-19 AIoT Device ID Range	ZTE	WI AmbientIoT-CT CAT F
Plenary	3167	CR 29.510 1212 Rel-19 Adding AIoT device permanent ID range in Adminfo	Samsung	WI AmbientIoT-CT CAT B
Plenary	3259	CR 29.510 1228 Rel-19 AIoT Device Ranges Support for ADM	Ericsson	WI AmbientIoT-CT CAT B
Plenary	3312	CR 29.510 1232 Rel-19 Add the AIoT Device ID ranges to AdmInfo	China Mobile	WI AmbientIoT-CT CAT B
Plenary	3168	CR 29.510 1213 Rel-19 Adding ADM ID in NF profile	Samsung	WI AmbientIoT-CT CAT B
Plenary	3169	CR 29.510 1214 Rel-19 Updating Aiotfinfo in NF profile	Samsung	WI AmbientIoT-CT CAT B
Plenary	3201	CR 29.510 1217 Rel-19 Add AIoT to ServiceName Enum	Nokia	WI AmbientIoT-CT CAT B
Plenary	3230	CR 29.510 1227 Rel-19 Correction of feature name	Huawei	WI AmbientIoT-CT CAT F
Plenary	3105	CR 23.003 0717 Rel-19 Definition of AIoT Device Permanent Identifier and Filtering Information	Nokia	WI AmbientIoT-CT CAT F 3105, 3130, 3296, 3302 are overlapping with each other
Plenary	3130	CR 23.003 0718 Rel-19 Correct the Structure of Filter Information	ZTE	WI AmbientIoT-CT CAT B
Plenary	3296	CR 23.003 0722 Rel-19 Update the structures of AIoT IDs	CATT	WI AmbientIoT-CT CAT F
Plenary	3302	CR 23.003 0723 Rel-19 Updates on filtering information	Huawei	WI AmbientIoT-CT CAT B
Plenary	3216	CR 23.003 0721 Rel-19 AIoT Area ID definition	Huawei	WI AmbientIoT-CT CAT B
Plenary	3181	CR 29.504 0322 Rel-19 Adding resource URI for AIoT device profile data	Lenovo	WI AmbientIoT-CT CAT B Overlapping with 3289
Plenary	3289	CR 29.504 0323 Rel-19 Update the scope overview and service operations to add AIoT device profile data	China Mobile	WI AmbientIoT-CT CAT B
Plenary	3290	CR 29.504 0324 Rel-19 Update the Nudr_DataRepository resource to add AIoT device profile data	China Mobile	WI AmbientIoT-CT CAT B
Plenary	3299	CR 29.504 0325 Rel-19 Update the Nudr_DataRepository API to add AIoT device profile data	China Mobile	WI AmbientIoT-CT CAT B Overlapping with 3303
Plenary	3303	CR 29.504 0326 Rel-19 Updates on AmbientIoT data	Huawei	WI AmbientIoT-CT CAT B
Plenary	3333	CR 29.504 0328 Rel-19 Adding OAuth2 security scope for AIoT	Lenovo	WI AmbientIoT-CT CAT B
Plenary	3231	CR 29.571 0676 Rel-19 Completing AIoT Area ID definition and correction of references	Huawei	WI AmbientIoT-CT CAT B
3260	CR 29.510 1229 Rel-19 Clarify the Encoding of AIoT Device Simple Data Types	Ericsson	withdrawn	WI AmbientIoT-CT CAT F
Plenary	3278	CR 29.571 0678 Rel-19 Clarify the Encoding of AIoT Device Simple Data Types	Ericsson	WI AmbientIoT-CT CAT F
Plenary	3313	CR 29.571 0679 Rel-19 Add the AIoT Device ID range data type	China Mobile	WI AmbientIoT-CT CAT B
Plenary	3065	pCR 29.369 Rel-19 Correction of allowedArea in IndividualAfAuthorizationData	CEWiT
Plenary	3135	pCR 29.369 Rel-19 Corrections and Updates to ADM Service	ZTE
Plenary	3304	pCR 29.369 Rel-19 Pseudo-CR on resolve the EN	Huawei
Plenary	3305	pCR 29.369 Rel-19 Pseudo-CR on update the description for AllowedServiceOperation	Huawei
Plenary	3306	pCR 29.369 Rel-19 Pseudo-CR on clean up for TS 29.369	Huawei
Plenary	3311	pCR 29.369 Rel-19 Update the description of AIoT Device Profile Data Update	China Mobile
Plenary	3331	pCR 29.369 Rel-19 Pseudo-CR on AF Authorization Data service resource path	Lenovo
Plenary	3332	pCR 29.369 Rel-19 Pseudo-CR on ProblemDetails in error responses	Lenovo
Plenary	3285	pCR 29.506 Rel-19 Scope reference definitions and overview update	China Mobile	Overlapping with 3308, 3309
Plenary	3308	pCR 29.506 Rel-19 Pseudo-CR on TS Scope for TS 29.506	Huawei
Plenary	3309	pCR 29.506 Rel-19 Pseudo-CR on TS Overview for TS 29.506	Huawei
Plenary	3183	pCR 29.506 Rel-19 Pseudo-CR on New UDR service for AIoT	Lenovo	Overlapping with 3286
Plenary	3286	pCR 29.506 Rel-19 Definition of Nudr_DataRepository service for AIoT device profile data	China Mobile
Plenary	3287	pCR 29.506 Rel-19 Removal of clause 6	China Mobile
Plenary	3288	pCR 29.506 Rel-19 API definition for Nudr_DataRepository service	China Mobile
3300	WID revised Rel-19 WID on CT aspects of Architecture support of Ambient power-enabled Internet of Things	Huawei	Moved to 19.3.2
Plenary	3307	pCR 29.506 Rel-19 Pseudo-CR on TS Title for TS 29.506	Huawei
Main	3132	CR 29.518 1226 Rel-19 Correct the Description of AIoT Service	ZTE	WI AmbientIoT-CT CAT F
Main	3133	CR 29.518 1227 Rel-19 Content type of Multipart messages for AIoT service	ZTE	WI AmbientIoT-CT CAT F
Main	3134	CR 29.518 1228 Rel-19 Add a new value of application error	ZTE	WI AmbientIoT-CT CAT B
Main	3170	CR 29.518 1232 Rel-19 Updating AIoT NF services	Samsung	WI AmbientIoT-CT CAT B Overlapping with 3217, 3226, 3284, 3295
Main	3217	CR 29.518 1236 Rel-19 AIoT message delivery support for parallel sessions	Lenovo	WI AmbientIoT-CT CAT B
Main	3226	CR 29.518 1238 Rel-19 AIoT correlation ID	Huawei	WI AmbientIoT-CT CAT B
Main	3284	CR 29.518 1244 Rel-19 Add Correlation Identifier to Namf_AIoT Service API	China Mobile	WI AmbientIoT-CT CAT B
Main	3295	CR 29.518 1248 Rel-19 Add new identifiers in Namf_AIoT_MessageDelivery service operation	CATT	WI AmbientIoT-CT CAT B
Main	3225	CR 29.518 1237 Rel-19 AIoT sesseion release	Huawei	WI AmbientIoT-CT CAT B
Main	3227	CR 29.518 1239 Rel-19 AIoT transaction reference ID	Huawei	WI AmbientIoT-CT CAT B
Main	3292	CR 29.518 1245 Rel-19 Editorial corrections on AIoT services	CATT	WI AmbientIoT-CT CAT D
Main	3293	CR 29.518 1246 Rel-19 Update the Namf_AIoT Custom operation	CATT	WI AmbientIoT-CT CAT F
Main	3294	CR 29.518 1247 Rel-19 Update the AiotMessageReq type	CATT	WI AmbientIoT-CT CAT F
TS29.369v0.3.0	Huawei
TS29.506v0.1.0	China Mobile
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]
20	Study Items
20.1	Study on Protocol for AI Data Collection from UPF [FS_PAIDC-UPF]
Plenary	3321	pCR 29.889 Rel-19 Clarifications to Solution #4 and conclusion for KI#1	China Mobile
TR 29.889v1.1.0	China Mobile
20.2	Study on Reducing Information Exposure over SBI [FS_RedInfExp_SBI]
20.3	Study on IMS Disaster Prevention and Restoration Enhancement [FS_IMS_RES]
20.4	Study on IMS resiliency [FS_IMSResil]
Plenary	3048	pCR 29.867 Rel-19 Solution for P-CSCF failure detection based on IMS means	Nokia
Plenary	3051	pCR 29.867 Rel-19 KI#1 definition	Nokia
Plenary	3063	discussion 29.867 Rel-19 Discussion for Severe P-CSCF failure and recovery notifications	KDDI
Plenary	3064	pCR 29.867 Rel-19 Solution for Severe P-CSCF failure/recovery notification with PCO/ePCO	KDDI
Plenary	3162	pCR 29.867 Rel-19 Pseudo-CR on solution for SMF-initiated PDU session release	Qualcomm Incorporated
TR 29.867v0.2.0	KDDI
21	Any other business
3010	Work Plan Work Plan	CT4 Chair
Plenary	3040	ToR Terms of Reference (ToR) for 3GPP TSG CT WG4 (CT4)	CT4 Chair
22	Future meetings
23	Close of Meeting