3GPP TSG-CT WG4 Meeting #122	C4-241006

Changsha, P.R.China, 15th–19th April 2024

Source:	Chairman, TSG-CT WG4

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

Agenda item:	2

Document for:	INFORMATION

Saved 12/04/2024 10:12	UTC +8

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 Title	Tdoc C4-24#	Tdoc Title	Source	Result	Notes
1	Opening of the Meeting and Approval of the Agenda
2	Allocation of Documents to Agenda Items
1001	agenda Draft Agenda	CT4 Chair
1002	other Meeting guidelines for CT4 Working Group meeting	CT4 Chair
1003	agenda Detailed agenda & time plan for CT4 meeting: status at document deadline	CT4 Chair
1004	agenda Detailed agenda & time plan for CT4 meeting: status on eve of meeting	CT4 Chair
1005	agenda Proposed allocation of documents to agenda items for CT4 meeting: status at document deadline	CT4 Chair
1006	agenda Proposed allocation of documents to agenda items for CT4 meeting: status on eve of meeting	CT4 Chair
1007	agenda The allocation of documents to agenda items for CT4 meeting: status at the end of meeting	CT4 Chair
3	Meeting Reports
1008	report Previous TSG CT & SA Status Report	CT4 Chair
1009	report Previous CT4 meeting report	MCC
4	Input Liaison Statements
1015	LS in LS “N32-f lifetime and reconnection” to 3GPP CT4/SA3	5GMRR	5GMRR Doc 45_07r1 To: CT4, SA3 CC: *** GSMA 5GMRR described the N32 connection setup for the TLS security method between two SEPPs of different operators, according to TS 33.501 and TS 29.573 Release 18 and related GSMA procedures, (Ref: 5GMRR Doc 45_12 - LS Educational paper on N32 connection establishment for bilateral TLS). As the specifications do not provide clear guidance on N32-f lifetime, 5GMRR makes the following assumptions. The N32-f lifetime is under control of the client initiating the N32-f connection. It is expected that N32-f are long-lived connections which are kept active even if there is no traffic to be sent. Several methods are available to keep the connection alive. TCP keep-alive is the minimum recommended method to be supported. Other methods can optionally be supported. TCP keep-alive. TLS Heartbeat HTTP2 PING Frame After a timeout of heartbeat message or actual traffic, the client (initiator) should re-establish N32-f and, in case of failure, re-establish the N32 context. Note: This means that stability issues, resulting in N32 context re-establishment in the forward direction from I-SEPP to r-SEPP will impact N32-f connections in the reverse direction from r-SEPP to I-SEPP. Actions 3GPP is kindly asked to take the following actions: CT4/SA3 to provide feedback on the assumptions that N32-f are long lived connections under control of the initiating client CT4 to indicate the preferred method (if any) to keep N32-f connections alive. CT4 to confirm or reject the actions to be taken if a connection fails after timeout. *** Postponed from CT4#121 “Mamdoh: requirement already exists in 29.500, will provide reply LS Jesus: is 29.573 CR needed ? Corresponding 29.573 CR is needed, it will be provided to the next meeting thus the LS is postponed to the next meeting” Reply LS in 1133 (not available yet)
1016	LS in N32-f N32-c correlation	5GMRR	5GMRR Doc 45_08r1 To: CT4, SA3 CC: Postponed from CT4#121 Related CR in 1127 Reply LS in 1134
1017	LS in LS on nested JSON structures and reply to LS S3-235067	5GMRR	5GMRR Doc 46_08r1 - LS on nested JSON structures and reply to LS S3-235067 To: CT4 and SA3 CC: Postponed from CT4#121 “The issue of recursion of data type will be further discussed in the next meeting, thus this LS is postponed to the next meeting” Reply LS in 1136
1018	LS in Rel-18 Reply LS on improved KPIs involving end-to-end data volume transfer time analytics	SA WG5	S5-241086 To: SA2, CT3, CT4, RAN2, RAN3 CC: Contact: Intel, Verizon, China Mobile Postponed from CT4#121 “SA2 has related CR on this topic in S2-2402925 Based on the incoming LS, 29.244, 29.571 CRs may be needed, they will be provided to the next meeting thus the LS is postponed to the next meeting” Related CRs in 1061, 1062, 1222, 1084, 1276
1019	LS in Rel-17 Reply LS on the service requirement of restricting satellite access RAT type	RAN WG3	R3-241204 To: SA2, CT4 CC: CT1, SA1, RAN2 Contact: Ericsson *** 1. Overall Description: RAN3 has discussed the topic of inter-system mobility between TN and NTN. RAN3 has added codepoints for e-UTRA-LEO/MEO/GEO/OTHERSAT to NGAP and XnAP, and codepoints for NR-LEO/MEO/GEO/OTHERSAT to S1APand X2AP. 2. Actions: To SA2 and CT4 group. ACTION: RAN3 asks SA2 and CT4 to take the above into account and align their specifications if needed. ***
1020	LS in Rel-18 LS on provisioning ATSSS rules to the UE in EPC	CT WG1	C1-241721 To: SA2 CC: CT4 Contact: ZTE *** 1. Overall Description: Regarding UE establishing a PDN connection as a user-plane resource of an MA PDU session, there are following facts: In Rel-17, ATSSS_Ph2 introduces support of MA PDU session establishment with 3GPP access connected to EPC and non-3GPP access connected to 5GC. It specifies that ATSSS rules are not provided via the EPC (see clause 4.22.2.3.1 in TS 23.502). In Rel-18, ATSSS_Ph3 introduces support of MA PDU session establishment with untrusted non-3GPP access connected to EPC and 3GPP access connected to 5GC. It specifies that ATSSS rules may be provided via the EPC (see clause 4.22.2.4.1 in TS 23.502). Based on the above, CT1 would like to ask SA2 to provide an answer to following question: Why can ATSSS rules be provided via untrusted non-3GPP access to EPC but not via 3GPP access? 2. Actions: To SA WG2 group. ACTION: CT1 kindly asks SA2 to provide feedback for the question above. *** Propose to note
1021	LS in Rel-18 LS on LCS user plane connection binding to the UE	CT WG1	C1-241722 To: SA WG2 CC: CT WG4 Contact: Qualcomm *** 1. Overall Description: As part of the work on 5G_eLCS_Ph3, CT1 has specified protocol solutions for location service over user plane as defined in new TS 24.572: Step 1) UPP-CM procedure during which the LMF provides the user plane connection information to the UE. Step 2) The UE performs user plane connection establishment with the LMF (i.e., TLS connection) based on the information received from Step 1. Step 3) LCS-UPP procedure to transfer location service messages between the UE and the LMF. CT1 has found following issues: After the TLS connection is established, the UE and the LMF initiate LPP or LCS-SS procedure. For the LMF-initiated case, given that multiple UEs are served by the LMF and multiple TLS connections are active, the LMF needs to determine a TLS connection for the target UE. However, it has not been specified how to link the association between the TLS connection and the UE, e.g., how the LMF knows which TLS connection is for the UE who has received the UPP-CM command message. If the TLS connection can be linked to the ‘wrong UE’ then there could be a risk of location related data from one UE which is sent to another UE. Once the binding of the TLS connection to the UE is done, if there is a new LCS service request (e.g., MT-LR) for the same UE, the AMF invokes Nlmf_location_determinelocation service operation to the LMF. However, it has not been specified how the LMF associates the LCS service request to the TLS connection of the UE. In this case, the LMF cannot determine which TLS connection can be used for the LCS service request. Therefore, the LMF cannot reuse the TLS connection of this UE for subsequent LCS service request(s). ***
1022	LS in Rel-18 LS on Rel-18 RedCap enhancements work	CT WG1	C1-241809 To: SA2 CC: CT4, RAN2, RAN3 Contact: Huawei *** CT1 would like to inform that work on NR_redcap_enh-Core impacts CT1 specifications. CT1 has informally become aware of communication between SA2 and other working groups about Rel-18 RedCap enhancements work (LS exchange on "Rel-18 RedCap enhancements to address remaining ENs in TS 23.502"). As impacts on NR_redcap_enh-Core can result in impacts to CT1 specifications, CT1 would like to be in the loop of communications related to that work. *** Propose to note
1023	LS in Rel-18 Reply LS on RedCap UE MBS Broadcast reception	RAN WG2	R2-2401662 To: SA2 CC: RAN3, CT3, CT4 Contact: Nokia *** RAN2 thanks SA2 for the reply-LS on RedCap UE MBS Broadcast reception and for the CR to TS 23.247. Regarding the new questions from SA2 about the usage of MBS Frequency Selection Area (FSA) ID for RedCap UEs and non-RedCap UEs, RAN2 discussed the questions directed to RAN2 and have reached the following conclusion: From access stratum (AS) signalling point of view, it is feasible to configure the same MBS FSA ID for the RedCap UEs and non-RedCap UEs in the same MBS session. However, it is an upper layer decision what FSA IDs to configure to different UEs. Currently, if multiple FSA IDs provide the same MBS session, then it is up to UE implementation to select the frequency according to RAN2 specification. *** Propose to note
1024	LS in Rel-18 Response LS on NG-RAN receiving a GTP-U Error Indication	RAN WG3	R3-241122 To: CT4 CC: Contact: Nokia *** 1. Overall Description: RAN3 thanks CT4 for informing about the new CT4 requirement in clause 5.3.3.1 of 3GPP TS 23.527 for the case when the 5G-AN receives a GTP-U Error Indication. RAN3 decided to introduce a new IE in the PDU Session Resource Notify Released Transfer IE to indicate to SMF that GTP-U Error Indication was received from UPF. RAN3 agreed the attached NGAP CR. 2. Actions: To CT4 group: ACTION: RAN3 kindly ask CT4 to take RAN3 answer into account. ***
1025	LS in Rel-18 LS on restoration of N3mb Failure for MBS broadcast	RAN WG3	R3-241144 To: CT4 CC: SA2 Contact: Nokia *** 1. Overall Description: RAN3 has discussed how to handle N3mb failure in MBS scenario. The scenario was discussed both in the context of MBS MOCN RAN sharing for broadcast using unicast transport, and in the context of broadcast/multicast without MBS MOCN RAN sharing. RAN3 understands that MBS NG-U tunnels are operated for MBS broadcast in downlink only. Therefore, the gNB is not able to detect NG-U path failure using Echo Request. Accordingly, the gNB might not be able to request MBS broadcast transport from another CN due to user plane failure. RAN3 assumes that detection of NG-U path failure for MBS and associated recovery could rely on MB-UPF detection. However, this handling seems currently not specified in TS 23.527. 2. Actions: To CT4 group: ACTION: RAN3 kindly ask CT4 to give guidance how N3mb failure can be detected and recovered and update related specification, if needed. *** Related CR in 1107, 1244 Reply LS in 1108, 1245
1026	LS in Rel-18 LS Reply on Clarification related to the information exposed by the 5GC to NSCE server.	SA WG2	S2-2403703 To: CT3 CC: SA6, CT1, CT4, SA3 Contact: Huawei *** SA2 thanks CT3 for the LS on Clarification related to the information exposed by the 5GC to NSCE server. Please find SA2 answer as below. Question 1: Which of the network internal information provided in the Network Slice load information/analytics prediction can be exposed to an external AF or the NSCE Server? (For example, Area of Interest in terms of internal identities (e.g. TAI, Cell ID) sent to the NSCE server) SA2 Answer: TS 23.288, Clause 6.1.1.2 contains procedures for Analytics subscription by AFs via NEF, and Clause 6.1.2.2 contains procedures for Analytics request by AFs via NEF. According to those procedures, if the request from AF does not comply with the restrictions in the analytics exposure mapping, NEF may apply restrictions to the request to NWDAF (e.g. restrictions to parameters or parameter values) based on operator configuration and/or may apply parameter mapping (e.g. geo coordinate mapping to TA(s), Cell-id(s)). The NEF may also apply restrictions to the responses or notifications towards AFs (e.g. restrictions to parameters or parameter values) based on operator configuration. The output of Network Slice load statistics/prediction as described in Table 6.3.3A-2 and Table 6.3.3A-4 of TS 23.288 can be exposed, although it was not exposed to the AF, and the attached CR fixed it. Note that Network Slice Instance load statistics/prediction as described in Table 6.3.3A-1 and Table 6.3.3A-3 of TS 23.288 should not be exposed as Network Slice instance is within 5GC and it is assumed external AF or NEF is not aware of Network Slice Instance. Besides, as described in TS 33.501 clause 5.9.2.3, NEF and the AF shall fulfil the security requirements that include that “Internal 5G Core information such as DNN, S-NSSAI etc., shall not be sent outside the 3GPP operator domain.” But there is no agreement in SA2 whether a possible associated NSI ID in Load Level Analytics/predictions can be exposed or not to a trusted AF or an NEF. Please also note Area of Interest is not part of output but it should be included in the subscription to the Analytic “Load level information” as Analytics Filter Information. Besides, SA2 has updated TS 23.288 to add AF (NSCE server) in the consumer NF as attached and clarify Area of Interest can be list of TAs or Cells. If an AF provides geographical area, the NEF can map it in to list of TAs or Cells based on operator policy in the related procedures as mentioned above. Please see the details in the attachment for the above information. *** Propose to note
1027	LS in Rel-17 Reply LS on Authorization of NF service consumer for data collection via DCCF	SA WG3	S3-240830 To: 3GPP CT3 CC: 3GPP CT4, SA2 Contact: Huawei *** SA3 thanks CT3 the LS on Authorization of NF service consumer for data collection via DCCF. There is a note in TS 33.501 clause Annex.X.2 as following: “NOTE 6: In the case a new NF Service Consumer comes at a later stage to request the data, which is already being collected by DCCF, steps 1-10 apply. When the request is received by the NF Service Producer (i.e. the data producer), it authenticates the NF Service Consumer and verifies the access token provided along with the service request and sends to DCCF the access token verification response. DCCF based upon the response received, either updates the subscription info to include the new NF Service Consumer as well and sends the data to both the consumers (as specified in Clause 6.2.6.3.2 in TS 23.288 [105]), or in the case of access token verification failure, the DCCF rejects the request received by the NF Service Consumer.” Therefore, the DCCF shall update the subscription information to include the new NF Service Consumer(s)/source Data Consumer(s) after the authorization is successful performed by the NF Service Producer/Data Source. In other words, the Data Source can get and/or authorize the CCA of the new Data Consumer(s) to retrieve the same data in step10 of Annex X.2 of TS 33.501. *** Propose to note
1028	LS in Rel-17 LS on UUAA Status Information availability for SMF	SA WG3	S3-240835 To: CT4 CC: SA2, CT1 Contact: Lenovo *** Thanks for the clarification question asked in LS C4-230790 related to the need of uavAuthenticated information element. CT4 Question: CT4 kindly asks SA3 to clarify why the functionality of uavAuthenticated information element is needed. SA3 Answer: According to SA3 UUAA is to authenticate the UAV for security reasons, and we do not see any security benefits in repeating. But in the latest SA2 TS 23.256 V18.2.0, texts were removed related to AMF and SMF relations on UUAA execution [See SP-231244]. In its current form UUAA is triggered during registration and PDU session establishment independently. To align with latest SA2 TS 23.256 V18.2.0, SA3 agreed the Rel.17 and Rel.18 CRs which are attached here for your information. *** This an reply LS to the CT4 LS sent one year ago, related CRs were postponed according to C4-230790
1029	LS in Rel-18 Reply LS on Roaming Hub requirements as applicable to the Modified PRINS solution	SA WG3	S3-240887 To: SA CC: SA1, SA5, CT, CT4 Contact: Huawei *** SA3 received several LSes from GSMA 5GMRR related to the recent work on the modified PRINS solution. SA3 assumes that SA will coordinate a consolidated reply to GSMA. Therefore, SA3 would like to provide the following feedback on the requests included in S3-240208 on Roaming Hubs: Answer to Q 1: Regarding the definition of Roaming Hub, SA3 has agreed a CR S3-240891 for TS 33.501 on the definition of Roaming Hub according to the LS S3-240208 received from GSMA. Answer to Q 2.a: Regarding the requirement of roaming data session intervention, i.e., limiting roaming data usage, SA3 believes that these requirements need to be evaluated by SA1 and the corresponding impacts on the architecture by SA2 first. Answer to Q 2.b: Regarding the requirement related to the RH ability to prevent the establishment of, and to terminate the N32-c and N32-f connections, SA3 believes that the RH can request SEPP to terminate the N32-c and N32-f connections if necessary as described in clause 5.5, TS 29.573, based on the error message received from the RH. If this is not sufficient, then SA3 believes that these requirements may have impacts on the architecture, and need to be evaluated by SA1 and SA2 at first. *** Propose to note
1030	LS in Rel-18 Reply LS on IPX Service Hub requirements as applicable to the Modified PRINS solution	SA WG3	S3-240888 To: SA CC: SA1, SA2, CT, CT4 Contact: Huawei *** SA3 received several LSes from GSMA 5GMRR related to the recent work on the modified PRINS solution. SA3 assumes that SA will coordinate a single reply to GSMA. Therefore, SA3 would like to provide the following feedback on the requests included in S3-240209 on IPX Service Hubs and IPX Providers: Answer to Q 1: Regarding the definition of IPX Service Hub and IPX Provider, SA3 finds that the definition of IPX Service Hub is unclear, and would like GSMA to clarify the definition of IPX Service Hub. Answer to Q 2.a: Regarding the requirement of roaming data session intervention, i.e., limiting roaming data usage, SA3 believes that these requirements need to be evaluated by SA1 and the corresponding impacts on the architecture by SA2 first.. Answer to Q 2.b: Regarding the requirement of IPX Service Hub to aggregate N32 signalling traffic and use common identities, SA3 would like GSMA to clarify what does the aggregation mean. SA3 is also willing to receive feedback from SA2 and possibly SA1 on this requirement. *** Propose to note
1031	LS in LS on Registering JWT Claims at IANA	SA WG3	S3-240940 To: CT CC: 3GPP CT3, 3GPP CT4 Contact: Ericsson *** The 3GPP authorization framework uses the OAuth 2.0 framework as specified in RFC 6749. Access tokens shall be JSON Web Tokens (JWT) as described in RFC 7519. To support more granular authorization for 5G features, 3GPP introduces extra JWT claims per 5G use cases, which are defined in separate technical specifications. For example: TS 29.510 [2] specifies access token claims for 5G SBA use case. TS 33.434 [3] specifies access token claims for SEAL use case. TS 29.222 [4] specifies access token claims for CAPIF use case. TS 33.180 [5] specifies access token claims for 5G Mission Critical service. Since there is no coordination within 3GPP regarding defining JWT claims, it may happen that a conflict in JWT claim names is defined by different sub-WGs. SA3 understands that the CT will take measures to avoid the potential conflict during their stage 3 work. JWT claims can be registered by anyone in the industry at IANA. To prevent from potential conflict of JWT claim names in the industry, IANA registration may be considered. SA3 asks 3GPP CT to take decision whether IANA registration is necessary. If the answer is “yes”, SA3 suggest CT to take lead in coordinating the JWT claims registration process with IANA and inform SA3 with the outcome. *** The LS was discussed in CT#103, CT requested CT WGs to discuss this topic first to provide their views on whether there is a need to register JWT claims. If registration is needed, the existing procedure can be relied on. Related discussion paper in 1257
1032	LS in Rel-18 LS on removing Ranging/SL Positioning service exposure to Client UE through 5GC	TSG SA	SP-240497 To: SA2, SA3, CT1, CT4 CC: Contact: Xiaomi *** SA plenary has agreed to remove the feature of “Ranging/SL Positioning service exposure to Client UE through 5GC” for Rel-18 in both TS 23.586 and TS 33.533, and all the related solution developments will not be considered for Rel-18. Additionally, SA plenary also agreed to define UE Ranging/SL Positioning privacy profile in TS 33.533. For details, please check the attached 3 CRs. *** Related CRs in 1300, 1301, 1302,1303, 1304
1033	LS in Rel-18 LS on the Modified PRINS solution	TSG SA	SP-240503 To: GSMA 5GMRR, CT4 CC: SA3, SA1, SA2, CT Contact: Vodafone *** 3GPP TSG SA has agreed that the solution for Modified PRINS functionality, as specified by SA3 group in TS 33.501 for Release 18, can be applicable to Release 16 and 17 deployments, as per the attached CR. *** Related CR in 1132 Reply LS in 1135
5	WIDs	.
5.1	CT4 Led WIs	.
1036	WID new Rel-19 New WID on Service Based Interface Protocol Improvements Release 19	China Mobile
1230	discussion Rel-19 Subscriber Data Migration	Ericsson
1264	WID revised Rel-18 WID revision on EDGE_Ph2	Huawei	1269 has related discussion
1295	SID new Rel-19 New SID on AI Data Collection And Protocol	China Mobile
5.2	CT4 Supported WIs	.
6	Release 18
6.1	CT4 Led WIs
6.1.1	Service based Interface protocol improvements	SBIProtoc18
Main	1037	CR 29.518 1043 Rel-18 Attribute Name Correction	ZTE	WI SBIProtoc18 CAT F
Plenary	1038	CR 29.510 0982 Rel-18 Correct the reference to mbsServiceArea	ZTE	WI SBIProtoc18 CAT F
Plenary	1039	CR 29.510 0983 Rel-18 False Value of I/V-SMF Support Indication	ZTE	WI SBIProtoc18 CAT F
Main	1049	discussion Rel-18 Discussion on slice mapping and availability notification by NSSF	ZTE
Main	1050	CR 29.531 0198 Rel-18 Clarify vNSSF behaviour on S-NSSAI mapping in roaming case	ZTE	WI SBIProtoc18 CAT F
Plenary	1064	CR 29.518 1052 Rel-18 Callbacks	Nokia	WI SBIProtoc18 CAT F
Plenary	1065	CR 29.526 0083 Rel-18 Callbacks	Nokia	WI SBIProtoc18 CAT F
Plenary	1066	CR 29.531 0199 Rel-18 Callbacks	Nokia	WI SBIProtoc18 CAT F
Plenary	1067	CR 29.536 0122 Rel-18 Callbacks	Nokia	WI SBIProtoc18 CAT F
Plenary	1068	CR 29.555 0020 Rel-18 Callbacks	Nokia	WI SBIProtoc18 CAT F
Plenary	1069	CR 29.562 0151 Rel-18 Callbacks	Nokia	WI SBIProtoc18 CAT F
Plenary	1070	CR 29.598 0074 Rel-18 Callbacks	Nokia	WI SBIProtoc18 CAT F
Plenary	1071	CR 29.563 0087 Rel-18 Callbacks	Nokia	WI SBIProtoc18 CAT F
Plenary	1072	CR 29.256 0022 Rel-18 Callbacks	Nokia	WI SBIProtoc18 CAT F
Plenary	1073	CR 29.503 1237 Rel-18 Callbacks	Nokia	WI SBIProtoc18 CAT F
Plenary	1077	CR 23.003 0697 Rel-18 SUCI format	Nokia	WI SBIProtoc18 CAT F
Plenary	1078	CR 29.500 0426 Rel-18 Header case	Nokia	WI SBIProtoc18 CAT F
Plenary	1079	CR 29.501 0154 Rel-18 Query Parameter clarification	Nokia	WI SBIProtoc18 CAT F
Breakout	1080	CR 29.503 1238 Rel-18 Presence condition for PGW FQDN and IP address in SMF registration	Nokia	WI SBIProtoc18 CAT F
1084	CR 29.571 0539 Rel-18 Extend Trace for UE level measurements collection	Nokia	Moved to 6.3.1	WI SBIProtoc18 CAT F
Breakout	1087	CR 29.503 1240 Rel-18 Subscribe failure clarification	Nokia	WI SBIProtoc18 CAT F
Main	1106	CR 29.502 0765 Rel-18 Features supported by the Anchor SMF	Nokia	WI SBIProtoc18 CAT F
Plenary	1155	CR 29.500 0427 Rel-18 Expected Message Priority for Resource or Context	Ericsson	WI SBIProtoc18 CAT F
Plenary	1156	CR 29.500 0428 Rel-18 Indication of Intermediate NF	Ericsson	WI SBIProtoc18 CAT F
Plenary	1157	CR 29.510 0990 Rel-18 Missed UDSF for NF Group Id Query	Ericsson	WI SBIProtoc18 CAT F
Main	1158	CR 29.518 1060 Rel-18 Non-3GPP Not Taken Over Indication	Ericsson	WI SBIProtoc18 CAT F
Main	1159	CR 29.518 1061 Rel-18 To be Released PDU Session for Other Reasons during Handover	Ericsson	WI SBIProtoc18 CAT F
Main	1224	CR 29.573 0187 Rel-18 ABNF corrections	Ericsson	WI SBIProtoc18 CAT F
Breakout	1227	CR 29.505 0503 Rel-18 Incorrect definition of "any type" in OpenAPI	Ericsson	WI SBIProtoc18 CAT F
Plenary	1229	CR 29.500 0429 Rel-18 SBI Message Priority in a Response message	Ericsson	WI SBIProtoc18 CAT F
Plenary	1235	CR 29.571 0548 Rel-18 Definition of MbsSession	Ericsson	WI SBIProtoc18 CAT F
Plenary	1239	CR 29.510 0993 Rel-18 Definition of SelectionConditions	Ericsson	WI SBIProtoc18 CAT F
Plenary	1241	CR 29.510 0994 Rel-18 Addition of "servers" section in OpenAPI	Ericsson	WI SBIProtoc18 CAT F
Plenary	1265	discussion Discussion on unknown event	Huawei
Plenary	1266	CR 29.500 0430 Rel-18 Support of UNSUPPORTED_MONITORING_EVENT_TYPE error	Huawei	WI SBIProtoc18 CAT B
Plenary	1267	CR 29.564 0091 Rel-18 Returning failed event and the related error reason	Huawei	WI SBIProtoc18 CAT B
Plenary	1268	CR 29.571 0551 Rel-18 Removal of unused Job Types	Huawei	WI SBIProtoc18 CAT F
Breakout	1296	CR 29.503 1255 Rel-18 Missing Description fields in Nudm_UECM API definition	Ericsson	WI SBIProtoc18 CAT F
Plenary	1297	CR 29.526 0086 Rel-18 Missing Description fields in Network slice specific authentication and authorization (Nnssaaf_NSSAA API)	Ericsson	WI SBIProtoc18 CAT F
Plenary	1298	CR 29.501 0155 Rel-18 HTTP Multipart message support in PATCH Request	Microsoft EUROPE SARL	WI SBIProtoc18 CAT D
Breakout	1306	CR 29.509 0217 Rel-18 Clarification on deviation of naming-convention for enum values in Nausf specific Data Type	Ericsson	WI SBIProtoc18 CAT F
Plenary	1307	CR 29.510 0996 Rel-18 Clarify NRF behavior upon receiving invalid client information in discovery request	Samsung	WI SBIProtoc18 CAT B
6.1.2	Study on IETF QUIC Transport for 5GC Service Based Interfaces	FS_QUIC
6.1.3	Study on NRF API enhancements to avoid signalling and storing of redundant data	FS_NRFe
6.1.4	5GS support of NR RedCap UE with long eDRX for RRC_INACTIVE State	NR_REDCAP_Ph2
Plenary	1055	CR 23.008 0588 Rel-18 NR eRedCAP Not Allowed as Primary RAT	ZTE	WI NR_REDCAP_Ph2 CAT F
1056	CR 29.571 0537 Rel-18 Description of NR_EREDCAP RAT Type	ZTE	revised to C4-241076	Revision of C4-241076 WI NR_REDCAP_Ph2 CAT F
Main	1057	CR 29.518 1048 Rel-18 Correct SMF behaviour of sending a new Namf_MT_EnableUEReachability	ZTE	WI NR_REDCAP_Ph2 CAT F
Plenary	1076	CR 29.571 0537 Rel-18 Description of NR_EREDCAP RAT Type	ZTE	WI NR_REDCAP_Ph2 CAT F
6.1.5	CT aspects on Multiple location report for MT-LR Immediate Location Request for regulatory services	TEI18_MLR
6.1.6	CT aspects of enhancement to the 5GC location services - phase 3	5G_eLCS_Ph3
Breakout	1173	CR 29.572 0224 Rel-18 Resolve the EN and update attributes of MeasurementData service operation	CATT	WI 5G_eLCS_Ph3 CAT B
Breakout	1174	CR 29.515 0167 Rel-18 Remove the ENs for security parameters in the UPP	CATT	WI 5G_eLCS_Ph3 CAT F Overlapping with 1190
Breakout	1190	CR 29.515 0170 Rel-18 Resolve Editor’s Note	Huawei	WI 5G_eLCS_Ph3 CAT F
Breakout	1175	CR 29.572 0255 Rel-18 Update the security configuration for UPUnSubscribe	CATT	WI 5G_eLCS_Ph3 CAT F
Breakout	1176	CR 29.515 0168 Rel-18 Correct the description of data type IntegrityRequirements	CATT	WI 5G_eLCS_Ph3 CAT F Overlapping with 1191
Breakout	1191	CR 29.515 0171 Rel-18 Updates on integrity requirement	Huawei	WI 5G_eLCS_Ph3 CAT F
Breakout	1192	CR 29.572 0256 Rel-18 Support of LCS user plane connection binding to the UE	Huawei	WI 5G_eLCS_Ph3 CAT F
6.1.7	Enhancement of Shared Data Handling	ShDatID
6.1.8	Enhancement of Shared Data Handling [ShDatID] CT Aspects of Edge Computing Phase 2	EDGE_Ph2
Main	1103	CR 29.244 0841 Rel-18 HR-SBO indication	Nokia	WI EDGE_Ph2 CAT F Overlapping with 1113, 1270
Main	1113	CR 29.244 0842 Rel-18 Update N4 session information for a HR-SBO mode	Ericsson	WI EDGE_Ph2 CAT B
Main	1270	CR 29.244 0848 Rel-18 Application Function influence on traffic routing in HR-SBO	Huawei	WI EDGE_Ph2 CAT B
Main	1104	CR 29.564 0088 Rel-18 HR-SBO indication in UeIpInfo	Nokia	WI EDGE_Ph2 CAT F Overlapping with 1114, 1273
Main	1114	CR 29.564 0090 Rel-18 HR-SBO indication in GetPrivateUEIPaddrAndIdentifiers Response	Ericsson	WI EDGE_Ph2 CAT B
Main	1273	CR 29.564 0092 Rel-18 Application Function influence on traffic routing in HR-SBO	Huawei	WI EDGE_Ph2 CAT B
Plenary	1172	CR 29.503 1244 Rel-18 Add security parameter to ECS address IE	Samsung	WI EDGE_Ph2 CAT B
Plenary	1179	CR 29.503 1245 Rel-18 Add list of supported PLMNs to ECS address IE	Samsung	WI EDGE_Ph2 CAT B
Main	1243	CR 29.502 0769 Rel-18 dlAmbr for HR-SBO PDU session	Ericsson	WI EDGE_Ph2 CAT F
Main	1252	CR 29.502 0770 Rel-18 Correction on the Removal of VplmnOffloadingInfo for PDU session	Ericsson	WI EDGE_Ph2 CAT F
Main	1258	CR 29.244 0846 Rel-18 UE source IP address mapping for HR-SBO sessions with overlapping IP addresses	Ericsson, Nokia	WI EDGE_Ph2 CAT B
Main	1259	CR 29.244 0847 Rel-18 N6 tunneling between V-UPF and V-EASDF for HR-SBO PDU sessions with overlapping IP addresses	Ericsson, Nokia	WI EDGE_Ph2 CAT B
Main	1260	CR 29.510 0995 Rel-18 N6 tunnel Information for a V-UPF or a V-EASDF for HR-SBO PDU sessions	Ericsson	WI EDGE_Ph2 CAT B
Main	1261	CR 29.556 0037 Rel-18 N6 tunneling between V-UPF and V-EASDF for HR-SBO PDU sessions with overlapping IP addresses	Ericsson, Nokia	WI EDGE_Ph2 CAT B
Plenary	1269	discussion Discussion on new impacts to the EDGE_Ph2 work	Huawei
Main	1271	CR 29.502 0771 Rel-18 Traffic influence information Correction	Huawei	WI EDGE_Ph2 CAT F
Main	1272	CR 29.502 0772 Rel-18 Updates on protocolDescription and vEasdfSecurityInfo	Huawei	WI EDGE_Ph2 CAT F
Plenary	1299	discussion Requirements for updating ECS Address Configuration Information	Nokia
6.1.9	Enhancement of NSAC for maximum number of UEs with at least one PDU session/PDN connection	eNSAC
Main	1181	CR 29.536 0126 Rel-18 Indicate reason of delegation of request to Primary NSACF	Samsung	WI eNSAC CAT B
6.1.10	UPF enhancement for exposure and SBA	UPEAS
Main	1105	CR 29.564 0089 Rel-18 Input parameters of Nupf_GetPrivateUEIPaddr_Get Request	Nokia	WI UPEAS CAT F
6.1.11	5 MBS Phase 2	5MBS_PH2
Main	1085	CR 29.571 0540 Rel-18 NrRedCapUeInfo default value	Nokia	WI 5MBS_Ph2 CAT F Overlapping with 1247
Main	1247	CR 29.571 0549 Rel-18 Aligning the default value of nrRedCapUeInfo with stage 2 specification	Huawei	WI 5MBS_Ph2 CAT C
Main	1107	CR 23.527 0072 Rel-18 Broadcast MBS session restoration procedure for N3mb path failure	Nokia	WI 5MBS_Ph2, NR_MBS_enh-Core CAT F Overlapping with 1244
Main	1244	CR 23.527 0077 Rel-18 Detection and restoration mechanism for UP path failure for MBS broadcast session	Huawei	WI 5MBS_Ph2 CAT B
Main	1108	LS out Reply LS on Restoration of N3mb Failure for MBS broadcast	Nokia	R3-241144 To: RAN3 CC: SA2 Overlapping with 1245
Main	1245	LS out Rel-18 Reply LS on restoration of N3mb Failure for MBS broadcast from RAN3	Huawei
Main	1220	CR 29.571 0547 Rel-18 Removal of the defaule value of NR RedCap UE information	Qualcomm Incorporated	WI 5MBS_Ph2 CAT F
Main	1225	CR 29.532 0090 Rel-18 Supported Features in MBS Session Create request and response	Ericsson, Nokia, Huawei	WI 5MBS_Ph2 CAT F
6.1.12	Enhancements on Service-based support for SMS in 5GC	eSMS_SBI
6.1.13	Study on Reducing Information Exposure over SBI	FS_RedInfExp_SBI
Plenary	1086	pCR 29.857 Rel-18 Evaluation and Conclusion for KI#3	Nokia
Plenary	1240	pCR 29.857 Rel-18 Pseudo-CR on Evaluation and Conclusion update of solution #8 for Key issue#1	China Mobile
Plenary	1249	pCR 29.857 Rel-18 pCR on Update evaluation of key Issue #1	Huawei
TR 29.857v0.4.0	Samsung
6.1.14	Study on IMS Disaster Prevention and Restoration Enhancement	FS_IMS_RES
Breakout	1013	pCR 29.866 Rel-18 pCR on TR 29.866 Update Solution #3: Solution for maintaining IMS MT service uninterruptible in case of HSS/UDM failure	China Telecom Corporation Ltd.
Breakout	1014	pCR 29.866 Rel-18 pCR on TR 29.866 Evaluation and Conclusion of KI#4	China Telecom Corporation Ltd.
Breakout	1187	pCR 29.866 Rel-18 Solution for KI#1	Huawei
Breakout	1188	pCR 29.866 Rel-18 Solution for KI#2	Huawei, China Telecom
Breakout	1189	pCR 29.866 Rel-18 Solution for KI#3	Huawei
TR 29.866v0.4.0	China Telecom
6.1.15	CT aspects of home network triggered primary authentication	HN_Auth
Breakout	1193	CR 29.503 1246 Rel-18 Updates on auth-trigger URI	Huawei	WI HN_Auth CAT F
6.1.16	NRF API enhancements to avoid signalling and storing of redundant data	NRFe
Plenary	1074	CR 29.510 0986 Rel-18 Shared Data corrections and clean up	Nokia	WI NRFe CAT F
Plenary	1075	CR 29.510 0987 Rel-18 Retrieval of multiple shared data	Nokia	WI NRFe CAT F
6.1.17	CT impacts of EVS Codec Extension for Immersive Voice and Audio Services	IVAS_Codec
6.2	CT4 Supported WIs
6.2.1	Enhancements of UE Policy	UEP18
6.2.2	CT aspects of Enhanced support of Non-Public Networks Phase 2	eNPN_Ph2
6.2.3	Protocol enhancements for Mission Critical Services	MCPROTOC18
6.2.4	Support for 5WWC Phase 2	5WWC_Ph2
6.2.5	Mission critical system migration and interconnection enhancements	eMCSMI_Irail
6.2.6	CT aspects of proximity based services in 5GS Phase 2	5G_ProSe_Ph2
Breakout	1154	CR 29.555 0021 Rel-18 Correction on N5g-ddnmf_Discovery API	Ericsson	WI 5G_ProSe_Ph2 CAT F
6.2.7	Secondary DN authentication and authorization in EPC IWK cases	TEI18_SDNAEPC
6.2.8	CT aspects of Seamless UE session context recovery	SUECR
6.2.9	CT aspects of General Support of IPv6 Prefix Delegation in 5GS[	TEI18_IPv6PD
6.2.10	CT aspects of 5G System with Satellite Backhaul	5GSATB
6.2.11	5G Timing Resiliency and TSC & URLLC enhancements	TRS_URLLC
Plenary	1081	CR 29.503 1239 Rel-18 Time Sync Subscription Data	Nokia	WI TRS_URLLC CAT F
Main	1109	CR 23.527 0073 Rel-18 Restoration of TSS monitoring upon an NG-RAN failure with or w/o restart	Nokia, Ericsson	WI TRS_URLLC CAT B
Main	1110	CR 23.527 0074 Rel-18 Restoration of TSS monitoring upon an AMF failure with or w/o restart	Nokia, Ericsson	WI TRS_URLLC CAT B
Main	1117	CR 23.527 0075 Rel-18 Restoration of TSS monitoring upon an TSCTSF failure with or w/o restart	Ericsson, Nokia	WI TRS_URLLC CAT B
Main	1137	CR 29.518 1057 Rel-18 Restoration of TSS monitoring upon an NG-RAN failure with or w/o restart	Ericsson, Nokia	WI TRS_URLLC CAT B
Main	1138	CR 29.571 0544 Rel-18 Make IEs related TRS_URLLC nullable	Ericsson	WI TRS_URLLC CAT B
Plenary	1219	CR 29.503 1252 Rel-18 Updates on AstiAllowedInfo	Huawei	WI TRS_URLLC CAT B
6.2.12	Extensions to the TSC Framework to support DetNet	DetNet
6.2.13	CT aspects of 5G System Enabler for Service Function Chaining	SFC
6.2.14	CT aspects of Access Traffic Steering, Switch and Splitting support in the 5G system architecture; Phase	ATSSS_PH3
Plenary	1012	Work Plan Work Plan for ATSSS Phase 3	Lenovo
6.2.15	Enablers for Network Automation for 5G phase 3	eNA_PH3
6.2.16	CT aspects on enhancement of network slicing phase 3	eNS_PH3
Main	1040	CR 29.502 0758 Rel-18 Correction on PDU session release condition due to network slice replacement	ZTE	WI eNS_Ph3 CAT F
Main	1041	CR 29.502 0759 Rel-18 Clarification on PDU session establishment when network slice replacement happens	ZTE	WI eNS_Ph3 CAT F
Main	1042	CR 29.503 1235 Rel-18 Clarification on SMF registration when network slice replacement happens	ZTE	WI eNS_Ph3 CAT F
Main	1043	CR 29.536 0121 Rel-18 Clarification on NSAC when network slice replacement happens	ZTE	WI eNS_Ph3 CAT F
Main	1044	CR 29.510 0984 Rel-18 Clarification on presence of IE of snssaiListForEntirePlmn and nsacSaiList in NsacfInfo	ZTE, Nokia, Nokia Shanghai Bell	Revised to C4-241308	WI eNS_Ph3 CAT F
1308	CR 29.510 0984 Rel-18 Clarification on presence of IE of snssaiListForEntirePlmn and nsacSaiList in NsacfInfo	ZTE, Nokia
Main	1045	CR 29.518 1044 Rel-18 Correct the description related to partially allowed NSSAI	ZTE	WI eNS_Ph3 CAT F
Main	1046	CR 29.518 1045 Rel-18 Remove the EN related to partially allowed NSSAI	ZTE	WI eNS_Ph3 CAT F
Main	1047	CR 29.502 0760 Rel-18 Introduce the Slice Area Restriction indication	ZTE	WI eNS_Ph3 CAT F Overlapping with 1118
Main	1118	CR 29.502 0766 Rel-18 PDU session subject to area restriction for the S-NSSAI	Nokia	WI eNS_Ph3 CAT B
Main	1048	CR 29.518 1046 Rel-18 Subscribe to event notification for Slice Service Area	ZTE, Ericsson	WI eNS_Ph3 CAT F Overlapping with 1120
Main	1120	CR 29.518 1055 Rel-18 Presence-In-AOI-Report event for PDU session subject to area restriction	Nokia	WI eNS_Ph3 CAT B
Main	1119	CR 29.571 0543 Rel-18 Presence Info for partially allowed NSSAI and NS-AOS	Nokia	WI eNS_Ph3 CAT B
1121	CR 29.510 0988 Rel-18 Clarification to the NsacfInfo attributes	Nokia	withdrawn	WI eNS_Ph3 CAT F
Main	1122	CR 29.536 0123 Rel-18 Correct the feature name VHNSAC in structured datatypes	Nokia	WI eNS_Ph3 CAT F
Main	1123	CR 29.536 0124 Rel-18 Correction of QuotaUpdateRequestData and QuotaUpdateResponseData references	Nokia	WI eNS_Ph3 CAT F
Main	1124	CR 29.536 0125 Rel-18 NSAC optimization for network slice replacement	Nokia	WI eNS_Ph3 CAT B Overlapping with 1275
Main	1275	CR 29.536 0127 Rel-18 NSAC in network slice replacement	Huawei	WI eNS_Ph3 CAT F
Main	1274	CR 29.526 0084 Rel-18 NSSAA in network slice replacement	Huawei	WI eNS_Ph3 CAT F
6.2.17	Generic group management, exposure and communication enhancements	GMEC
Breakout	1035	CR 29.503 1234 Rel-18 Update the 5G VN group communication indication	China Mobile, China Southern Power Grid	WI GMEC CAT F
6.2.18	CT aspects of Next Generation Real time Communication services	NG_RTC
Breakout	1034	CR 29.330 0001 Rel-18 Update Experimental-Result-Code for Sc-pull procedure	China Mobile	WI NG_RTC CAT F
Breakout	1053	CR 29.364 0053 Rel-18 Extention of MMTEL service profile to support DC	ZTE	WI NG_RTC CAT F
Breakout	1054	CR 29.510 0985 Rel-18 Add MF Location Info in MF Profile	ZTE	WI NG_RTC CAT F
Breakout	1180	CR 29.571 0545 Rel-18 Support of SDP attributes a=3gpp-bdc-used-by and a=3gpp-req-app	Huawei	WI NG_RTC CAT F
Breakout	1182	CR 29.175 0001 Rel-18 Support of SDP attributes a=3gpp-bdc-used-by and a=3gpp-req-app	Huawei	WI NG_RTC CAT F
Breakout	1183	CR 29.175 0002 Rel-18 Correction on the Nimsas_MediaControl service	Huawei	WI NG_RTC CAT F
Breakout	1184	CR 29.175 0003 Rel-18 Correction on the Nimsas_SessionEventControl service	Huawei	WI NG_RTC CAT F
Breakout	1185	CR 29.176 0010 Rel-18 Clarification on the Media Context ID and termination ID	Huawei	WI NG_RTC CAT F
Breakout	1186	CR 29.330 0002 Rel-18 Correction on the XML Schema	Huawei	WI NG_RTC CAT F
6.2.19	CT Aspect of Further Architecture Enhancement for UAV and UAM Ph2	UAS_Ph2
6.2.20	CT aspects of Ranging based services and sidelink positioning	Ranging_SL
Breakout	1140	CR 24.080 0116 Rel-18 Resolve the EN on describing the relativeLocation and rangeDirection	vivo	WI Ranging_SL CAT F
Breakout	1177	CR 29.515 0169 Rel-18 Correct the description of feature Ranging_SL	CATT	WI Ranging_SL CAT F
Breakout	1194	CR 29.503 1247 Rel-18 Resolve Editor’s Note	Huawei	WI Ranging_SL CAT B
Breakout	1195	CR 29.515 0172 Rel-18 Updates on feature description	Huawei	WI Ranging_SL CAT F
Breakout	1196	CR 29.518 1067 Rel-18 Updates on feature description	Huawei	WI Ranging_SL CAT F
Breakout	1197	CR 29.572 0257 Rel-18 Updates on feature description	Huawei	WI Ranging_SL CAT F
Breakout	1198	CR 29.571 0546 Rel-18 Updates on RangingSlPosAuth	Huawei	WI Ranging_SL CAT F
Breakout	1199	CR 29.586 0001 Rel-18 Update the incorrect description	Huawei	WI Ranging_SL CAT F
Breakout	1200	CR 29.586 0002 Rel-18 Update the references	Huawei	WI Ranging_SL CAT F
Breakout	1201	CR 29.586 0003 Rel-18 Updates on announce-authorize URI	Huawei	WI Ranging_SL CAT F
Breakout	1202	CR 29.586 0004 Rel-18 Updates on discovery-authorize URI	Huawei	WI Ranging_SL CAT F
Breakout	1203	CR 29.586 0005 Rel-18 Updates on monitor-authorize URI	Huawei	WI Ranging_SL CAT F
Breakout	1204	CR 29.586 0006 Rel-18 Updates on the API Description	Huawei	WI Ranging_SL CAT F
Breakout	1300	CR 29.503 1256 Rel-18 Remove support of RangingSL Positioning service exposure to Client UE through 5GC	Xiaomi	WI Ranging_SL CAT F
Breakout	1301	CR 29.515 0175 Rel-18 Remove Ngmlc_Location_ProvideRanging	Xiaomi	WI Ranging_SL CAT F
Breakout	1302	CR 24.080 0117 Rel-18 Remove support of RangingSL Positioning service exposure to Client UE through 5GC	Xiaomi	WI Ranging_SL CAT F
Breakout	1303	CR 29.503 1257 Rel-18 UE RangingSL Positioning privacy profile	Xiaomi	WI Ranging_SL CAT B
Breakout	1304	CR 29.515 0176 Rel-18 Privacy notification and verification for UEs belonging to different PLMN(s)	Xiaomi	WI Ranging_SL CAT F
Breakout	1305	CR 29.586 0007 Rel-18 General update for the specification for SLPKMF services	Xiaomi	WI Ranging_SL CAT F
6.2.21	CT aspects of System Support for AI/ML-based Services	AIMLsys
Plenary	1276	CR 29.571 0552 Rel-18 JobType update for UE level measurements	Huawei	WI AIMLsys CAT B
6.2.22	CT aspects of Personal IoT Network	PIN
6.2.23	CT aspects of enhancement of 5G UE Policy	eUEPO
6.2.24	CT Aspect of Architecture Enhancements for Vehicle Mounted Relays	VMR
6.2.25	CT aspects on 5G AM Policy	AMP
6.2.26	Architecture Enhancements for XR and media services	XRM
Main	1092	CR 29.502 0762 Rel-18 Nsmf_PDUSession API features for XRM support	Nokia	WI XRM CAT F
Main	1093	CR 29.502 0763 Rel-18 Protocol Description for UL traffic	Nokia	WI XRM CAT F
Plenary	1094	CR 29.571 0541 Rel-18 PDU Set QoS parameters	Nokia	WI XRM CAT F
Main	1095	CR 29.244 0838 Rel-18 UPF reports for Congestion information and Data Rate monitoring	Nokia	WI XRM CAT F
Main	1096	CR 29.244 0839 Rel-18 Definition of congestion information for exposure	Nokia	WI XRM CAT F
Main	1097	CR 29.502 0764 Rel-18 ECN marking/Congestion Information Reporting Status during Xn and N2 handovers	Nokia	WI XRM CAT F
Main	1098	CR 29.244 0840 Rel-18 Resolving Editor's notes on EDB Indication and RTP Header Extension Type	Nokia	WI XRM CAT F Overlapping with 1115, 1278
Main	1115	CR 29.244 0843 Rel-18 Resolving Editor's Notes for End of Data Burst	Ericsson	WI XRM CAT B
Main	1278	CR 29.244 0850 Rel-18 Removal of EN on End of data Burst Indication	Huawei	WI XRM CAT F
Plenary	1116	CR 29.571 0542 Rel-18 Dependency between PDU Set QoS parameters	Ericsson	WI XRM CAT B
Plenary	1262	CR 29.571 0550 Rel-18 Removable data types for XRM	Ericsson	WI XRM CAT B
Main	1277	CR 29.244 0849 Rel-18 Description of IEs in congestion information monitoring	Huawei	WI XRM CAT F
Main	1279	CR 29.244 0851 Rel-18 Update the description of PDU set marking	Huawei	WI XRM CAT F
6.2.27	PLMN Selection based on Network Slice	PLMNsel_NS
6.2.28	MPS when access to EPC/5GC is WLAN	MPS_WLAN
6.2.29	Network Slice Capability Exposure for Application Layer Enablement	NSCALE
6.3	AoB for Rel-18	TEI18, …
6.3.1	TEI18	TEI18
Plenary	1051	CR 29.518 1047 Rel-18 Add EMM Registration Status in UE Context	ZTE	WI TEI18, 5GS_Ph1-CT CAT F
Main	1052	CR 29.244 0837 Rel-18 PFCP session deletion when new SMF takes over the PDU session	ZTE	WI TEI18, CUPS CAT F
Plenary	1061	CR 29.571 0538 Rel-18 Update the 5G Trace to support UE level measurement	China Mobile	WI TEI18 CAT B Overlapping with 1084
Plenary	1084	CR 29.571 0539 Rel-18 Extend Trace for UE level measurements collection	Nokia	WI SBIProtoc18 CAT F
Plenary	1062	CR 29.503 1236 Rel-18 Update the 5G Trace to support UE level measurement	China Mobile	WI TEI18 CAT B
1063	CR 29.502 0761 Rel-18 Update the 5G Trace to support UE level measurements	China Mobile	revised to C4-241222	Revision of C4-241222 WI TEI18 CAT B
Plenary	1222	CR 29.502 0761 Rel-18 Update the 5G Trace to support UE level measurement	China Mobile	WI TEI18 CAT B
Plenary	1088	discussion Rel-18 Shared VN Group Data	Nokia
Breakout	1089	CR 29.503 1219 Rel-18 SharedVnGroupDataIds	Nokia, Nokia Shanghai Bell	WI Vertical_LAN, TEI18 CAT F
Main	1099	CR 29.244 0797 Rel-18 MBS data usage reporting over N4mb for MBS charging	Nokia, Ericsson	WI TEI18, 5MBS_CH CAT B
Main	1100	CR 29.244 0798 Rel-18 MBS data usage reporting over N4 for MBS charging	Nokia, Ericsson	WI TEI18, 5MBS_CH CAT B
Main	1101	CR 29.532 0089 Rel-18 Definition of MBS related terms	Nokia	WI TEI18, 5MBS CAT F
Plenary	1102	CR 29.274 2104 Rel-18 IEs in Create Session Request/Response during the restoration of a PDN connection after a PGW-C/SMF change	Nokia	WI TEI18, RPCPSET CAT F
Plenary	1125	CR 29.510 0989 Rel-18 Add the nlmf_broadcast service to the service name list	Nokia	WI TEI18 CAT F
Main	1126	CR 29.518 1056 Rel-18 Clarify the semantics of the S-NSSAI and the NSI in the AmfEventArea datatype	Nokia	WI TEI18 CAT F
Plenary	1127	CR 29.573 0168 Rel-18 N32-f N32-c correlation	Nokia, Verizon	WI TEI18 CAT F
Main	1139	CR 29.531 0200 Rel-18 Miscellaneous corrections	Nokia	WI TEI18 CAT F
Breakout	1141	CR 23.003 0698 Rel-18 Clarification on NAI format for Anonymous SUPI in 5G-NSWO in SNPN access mode.	Ericsson	WI TEI18, eNPN_Ph2 CAT F
Breakout	1142	CR 23.003 0699 Rel-18 NAI format for anonymous SUCI with modified username for trusted non-3GPP access connected to 5GCN of an SNPN	Ericsson	WI TEI18, eNPN_Ph2 CAT F
Breakout	1143	CR 29.503 1241 Rel-18 Modification of CP-SOR (SOR-SNPN-SI) Information for SNPNs	Ericsson	WI TEI18, eNPN_Ph2 CAT F
Breakout	1144	CR 29.503 1242 Rel-18 Delimiting the GPSI values to be fetched to UDM	Ericsson	WI TEI18, EDGEAPP CAT F
Breakout	1151	CR 29.572 0251 Rel-18 Corrections on Local Origin	Ericsson	WI TEI18, 5G_eLCS_ph2 CAT F
Plenary	1163	CR 23.015 0027 Rel-18 AMF Determined PDU Session Establishment Rejection Due to ODB	Ericsson	WI TEI18 CAT F
Main	1164	CR 29.502 0767 Rel-18 Correction on Handover Failure Handling	Ericsson	WI TEI18 CAT F
Main	1165	CR 29.502 0768 Rel-18 Correction on Status Notification for Duplicate PDU Sessions	Ericsson	WI TEI18 CAT F
Breakout	1166	CR 29.503 1243 Rel-18 Correction of SMF Deregisrtation	Ericsson	WI TEI18 CAT F
Plenary	1167	CR 29.510 0991 Rel-18 Incorrect IE Name in Default Notification Subscription Data Type	Ericsson	WI TEI18 CAT F
Plenary	1168	CR 29.510 0992 Rel-18 Support of Emergency Sessions continuity during inter-PLMN mobility	Ericsson	WI TEI18 CAT F
Main	1169	CR 29.518 1065 Rel-18 Encoding for Binary NGAP IE with Contents Constraint and Unconstrianed OCTET STRING type	Ericsson	WI TEI18 CAT F
Main	1170	CR 29.518 1066 Rel-18 UE ID Usage for UE Related Resources	Ericsson	WI TEI18 CAT F
Breakout	1171	CR 29.572 0254 Rel-18 Resolving OpenAPI Warning	Ericsson	WI TEI18 CAT F
Breakout	1178	CR 29.555 0022 Rel-18 Update the output parameters of MonitorAuthDataForRestricted	CATT	WI TEI18, 5G_ProSe CAT F
Breakout	1205	CR 29.503 1248 Rel-18 Clarification on URI Path Segment Naming Conventions	Huawei	WI TEI18 CAT F
Breakout	1206	CR 29.503 1249 Rel-18 Editorial corrections	Huawei	WI TEI18 CAT F
Breakout	1207	CR 29.503 1250 Rel-18 Style Corrections of Nudm_SDM API	Huawei	WI TEI18 CAT F
Breakout	1208	CR 29.503 1251 Rel-18 Update on the reference of ncrOperationAllowed	Huawei	WI TEI18 CAT F
Breakout	1209	CR 29.504 0268 Rel-18 New feature AccessAndMobilityPolicyDataModify for Policy Data	Huawei	WI TEI18 CAT F
Breakout	1210	CR 29.509 0215 Rel-18 Style Corrections of Nausf API API	Huawei	WI TEI18 CAT F
Breakout	1211	CR 29.515 0173 Rel-18 Editorial corrections	Huawei	WI TEI18 CAT F
Breakout	1212	CR 29.515 0174 Rel-18 Style Corrections of Nlmf_Location API	Huawei	WI TEI18 CAT F
Breakout	1213	CR 29.555 0023 Rel-18 Clarification on URI Path Segment Naming Conventions	Huawei	WI TEI18 CAT F
Breakout	1214	CR 29.559 0039 Rel-18 Clarification on URI Path Segment Naming Conventions	Huawei	WI TEI18 CAT F
Breakout	1215	CR 29.572 0258 Rel-18 Editorial corrections	Huawei	WI TEI18 CAT F
Breakout	1216	CR 29.572 0259 Rel-18 Misalignment on AddEventNotifyDatas	Huawei	WI TEI18 CAT F
Breakout	1217	CR 29.572 0260 Rel-18 Style Corrections of Nlmf_Location API	Huawei	WI TEI18 CAT F
Breakout	1218	CR 29.598 0075 Rel-18 Style Corrections of Nudsf API API	Huawei	WI TEI18 CAT F
Plenary	1223	CR 23.527 0076 Rel-18 Restoration procedures for a PDU Session with Dual Connectivity	Ericsson	WI TEI18 CAT F
Main	1226	CR 29.244 0844 Rel-18 User Plane Inactivity Timer after the User Plane Inactivity Report is sent	Ericsson	WI TEI18 CAT F
Main	1228	CR 29.244 0845 Rel-18 Updating User Plane Inactivity Timer	Ericsson	WI TEI18, eNS_Ph3 CAT F
Breakout	1236	CR 29.503 1253 Rel-18 Update the Nudm_EventExposure_Subscribe for AKMA service	China Mobile	WI TEI18 CAT B
Breakout	1237	CR 29.509 0216 Rel-18 Definition of ProseAuthData	Ericsson	WI 5G_ProSe, TEI18 CAT F
Breakout	1238	CR 29.503 1254 Rel-18 Definition of ProseAuthenticationVectors	Ericsson	WI 5G_ProSe, TEI18 CAT F
Main	1246	CR 29.518 1070 Rel-18 Resolving the case of conflicting Target identifiers in the event subscription	Huawei	WI TEI18 CAT F
Main	1248	CR 29.518 1071 Rel-18 Clarification on NRPPa NGAP IE	Huawei, ZTE, China Telecom, China Mobile	WI TEI18 CAT F
Breakout	1280	CR 23.003 0700 Rel-18 Structure of W-APN, FQDN and HA-APN	Huawei	WI TEI18 CAT F
Main	1281	CR 29.244 0852 Rel-18 Add MB-SMF and MB-UPF to NodeID over N4mb	Huawei	WI TEI18 CAT F
Main	1282	CR 29.244 0853 Rel-18 Corrections on IE definition	Huawei	WI TEI18 CAT F
Main	1283	CR 29.502 0773 Rel-18 Correction on application errors of insufficient resource	Huawei	WI TEI18 CAT F
Main	1284	CR 29.502 0774 Rel-18 Correction on SupportedFeatures	Huawei	WI TEI18 CAT F
Main	1285	CR 29.502 0775 Rel-18 Release the PDU Session when S-NSSAI is not supported via ReleaseSMContext	Huawei	WI TEI18 CAT F
Plenary	1286	CR 29.526 0085 Rel-18 Miscellaneous corrections	Huawei	WI TEI18 CAT F
Main	1287	CR 29.531 0201 Rel-18 Miscellaneous corrections	Huawei	WI TEI18 CAT F
Main	1288	CR 29.556 0038 Rel-18 Correction on data type names of IPv4Addr and IPv6Addr	Huawei	WI TEI18 CAT F
Main	1289	CR 29.564 0093 Rel-18 Correction of Nupf_GetUEPrivateIPaddrAndIdentifiers API	Huawei	WI TEI18 CAT F
6.3.2	Roaming5G	Roaming5G, TEI18
Plenary	1128	CR 29.573 0182 Rel-18 EN on handling the applicative errors for termination of session and deregistration of the UE by RI	Nokia	WI Roaming5G CAT F
Plenary	1129	CR 29.573 0183 Rel-18 EN on the clash of the message ID created by the RI and any messages initiated by the c-SEPP	Nokia	WI Roaming5G CAT F
Plenary	1130	CR 29.573 0184 Rel-18 N32-f connection and/or N32-f context termination initiated by Roaming Intermediary	Nokia	WI Roaming5G, TEI18 CAT F
1131	CR 29.573 0185 Rel-18 Keeping an N32-f connection alive	Nokia	Withdrawn	WI Roaming5G CAT F
Plenary	1132	CR 29.573 0186 Rel-18 Support of Modified PRINS in earlier releases	Nokia	WI Roaming5G CAT F
1133	LS out Rel-18 Reply LS on N32-f lifetime and reconnection	Nokia	Withdrawn	C4-241015 To: GSMA 5GMRR, SA3 CC:
Plenary	1134	LS out Rel-18 Reply LS on N32-f N32-c correlation	Nokia	C4-241016 To: GSMA 5GMRR CC: SA3
Plenary	1135	LS out Rel-18 Reply LS on the Modified PRINS solution	Nokia	C4-241033 To: 3GPP SA, GSMA 5GMRR CC: SA3, SA1, SA2, CT
Plenary	1136	LS out Rel-18 Reply LS on nested JSON structures	Nokia	C4-241017 To: GSMA 5GMRR CC: SA3
Plenary	1221	discussion 29.573 Rel-19 congestion, failure control over N32	NTT DOCOMO, Inc
Plenary	1263	CR 29.573 0188 Rel-18 Correcting the figure heading	Nokia	WI Roaming5G CAT F
Plenary	1290	CR 29.500 0431 Rel-18 Replacing IPX with Roaming Intermediary	Huawei	WI TEI18, Roaming5G CAT F
Plenary	1291	CR 29.573 0189 Rel-18 Corrections on modificationsBlock	Huawei	WI TEI18, Roaming5G CAT F
Plenary	1292	CR 29.573 0190 Rel-18 Modification on the definition of Roaming Hub	Huawei	WI TEI18, Roaming5G CAT F
Plenary	1293	CR 29.573 0191 Rel-18 Replacing IPX with Roaming Intermediary	Huawei	WI TEI18, Roaming5G CAT F
Plenary	1294	CR 29.573 0192 Rel-18 Clarification on the usage of N32-f message ID	Huawei	WI TEI18, Roaming5G CAT F
6.3.3	AoB of Rel-18
Plenary	1257	discussion Rel-18 Discussion paper on the need for IANA registration for 3GPP-defined JWT claims for 5GC and NBI	Huawei
6.3.4	Open API version and External docs
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.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
7	Release 17
7.1	CT4 Led WIs
7.1.1	Service based Interface protocol improvements	SBIProtoc17
Main	1231	CR 29.518 1068 Rel-17 Content of JSON Patch requests	Ericsson	WI SBIProtoc17 CAT F
Main	1232	CR 29.518 1069 Rel-18 Content of JSON Patch requests	Ericsson	WI SBIProtoc17 CAT A
7.1.2	BEst Practice of PFCP	BEPoP
7.1.3	Service-based support for SMS in 5GC	SMS_SBI
7.1.4	CT aspects of Integration of GBA into SBA	GBA_5G
7.1.5	Enhancement of Network Slicing Phase 2	eNS_Ph2
7.1.6	CT Aspects of 5G eEDGE	eEDGE_5GC
7.1.7	CT aspects on Same PCF Selection For AMF and SMF	TEI17_SPSFAS
7.1.8	Enhancement of Inter-PLMN Roaming	EoIPR
7.1.9	Restoration of PDN Connections in PGW-C/SMF S	RPCPSET
Main	1233	CR 29.274 2105 Rel-17 PGW Node Name In Create Session Response message	Ericsson, Nokia	WI RPCPSET CAT F
Main	1234	CR 29.274 2106 Rel-18 PGW Node Name In Create Session Response message	Ericsson, Nokia	WI RPCPSET CAT A
7.1.10	Start of Pause of Charging via User Plane	SPOCUP
7.1.11	Enhancement to the 5GC LoCation Services-Phase 2	5G_eLCS_ph2
Breakout	1145	CR 29.515 0165 Rel-17 Integrity Result	Ericsson	WI 5G_eLCS_ph2 CAT F
Breakout	1146	CR 29.515 0166 Rel-18 Integrity Result	Ericsson	WI 5G_eLCS_ph2 CAT A
Breakout	1147	CR 29.518 1058 Rel-17 Integrity Result	Ericsson	WI 5G_eLCS_ph2 CAT F
Breakout	1148	CR 29.518 1059 Rel-18 Integrity Result	Ericsson	WI 5G_eLCS_ph2 CAT A
Breakout	1149	CR 29.572 0249 Rel-17 Integrity Result	Ericsson	WI 5G_eLCS_ph2 CAT F
Breakout	1150	CR 29.572 0250 Rel-18 Integrity Result	Ericsson	WI 5G_eLCS_ph2 CAT A
1151	CR 29.572 0251 Rel-18 Corrections on Local Origin	Ericsson	Moved to 6.3.1	WI TEI18, 5G_eLCS_ph2 CAT F
Breakout	1152	CR 29.572 0252 Rel-17 Missed Vertical Confidence in Local Location	Ericsson	WI 5G_eLCS_ph2 CAT F
Breakout	1153	CR 29.572 0253 Rel-18 Missed Vertical Confidence in Local Location	Ericsson	WI 5G_eLCS_ph2 CAT A
7.1.12	CT aspects of Support of different slices over different Non3GPP access	TEI17_N3SLICE
7.1.13	CT aspects of the architectural enhancements for 5G multicast-broadcast services	5MBS
Main	1111	CR 29.518 1053 Rel-17 MBS service area in the EnableGroupReachabilityReqData	Ericsson	WI 5MBS CAT F
Main	1112	CR 29.518 1054 Rel-18 MBS service area in the EnableGroupReachabilityReqData	Ericsson	WI 5MBS CAT A
7.1.14	Restoration of profiles related to UDR	ReP_UDR
7.1.15	Enhancement on the GTP-U entity restart	EGTPUR
7.1.16	Port allocation	Port_AL
7.1.17	Non-Seamless WLAN offload authentication in 5GS	NSWO_5G
7.2	CT4 Supported WIs
7.2.1	Stage 3 of Multimedia Priority Service (MPS) Phase 2	MPS2
7.2.2	Enhancement for the 5G Control Plane Steering of Roaming for UE in CONNECTED mode	eCPSOR_CON
7.2.3	Authentication and key management for applications based on 3GPP credential in 5G	AKMA-CT
7.2.4	CT aspects on Dynamically Changing AM Policies in the 5GC	TEI17_DCAMP
7.2.5	CT aspects of proximity based services in 5GS	5G_ProSe
7.2.6	CT aspects on Dynamic Management of Group-based Event Monitoring	TEI17_GEM
7.2.7	CT aspects of 5GC architecture for satellite networks	5GSAT_ARCH-CT
7.2.8	CT aspects for Support of Unmanned Aerial Systems Connectivity, Identification, and Tracking	ID_UAS
7.2.9	CT aspects of Enabling Multi-USIM devices	MUSIM
7.2.10	CT aspects of Access Traffic Steering, Switch and Splitting support in the 5G system architecture; Phase 2	ATSSS_PH2
7.2.11	CT aspects of Enhanced support of Non-Public Networks	eNPN
7.2.12	CT aspects of enhanced support of industrial IoT	IIoT
7.2.13	Enablers for Network Automation for 5G - phase 2	eNA_PH2
7.2.14	System enhancement for redundant PDU session	TEI17_SE_RPS
7.2.15	CT Aspects ofMinimisation of service Interruption	MINT
Breakout	1082	CR 29.509 0213 Rel-17 Disaster Condition PLMN List	Nokia	WI MINT CAT F
Breakout	1083	CR 29.509 0214 Rel-18 Disaster Condition PLMN List	Nokia	WI MINT CAT A
7.2.16	CT aspects of Architecture Enhancement for NR Reduced Capability Devices	ARCH_NR_REDCAP
Breakout	1090	CR 29.503 1210 Rel-17 RAT specific Subscribed Paging Time Window length values	Nokia	WI ARCH_NR_REDCAP CAT F
Breakout	1091	CR 29.503 1211 Rel-18 RAT specific Subscribed Paging Time Window length values	Nokia	WI ARCH_NR_REDCAP CAT A
7.2.17	Enhancements of 3GPP profiles for cryptographic algorithms and security protocols	eCryptP
7.2.18	CT aspects of NB-IoT/eMTC Non-Terrestrial Networks in EPS	IoT_SAT_ARCH_EPS
7.2.19	CT4 aspects of EDGEAPP	EDGEAPP
7.2.20	CT4 aspects of enhancement of RAN Slicing for NR	NRslice
7.3	AoB for Rel-17	TEI17, …
7.3.1	TEI17	TEI17
7.3.2	AoB of Rel-17
7.3.3	Open API version and External docs	TEI17
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
8	Release 16 and earlier
8.1	CT4 Led WIs
8.1.1	CT aspects on Enhancements to the Service-Based 5G System Architecture	5G_eSBA
8.1.2	CT aspects of Enhancing Topology of SMF and UPF in 5G Networks	ETSUN
8.1.3	CT aspects of Enhancement to the 5GC LoCation Services	5G_eLCS
8.1.4	CT Aspects of Media Handling for RAN Delay Budget Reporting in MTSI	E2E_DELAY
8.1.5	User data interworking, Coexistence and Migration	UDICOM
8.1.6	Service based Interface protocol improvements	SBIProtoc16
8.1.7	CT aspects of optimisations on UE radio capability signalling	RACS
Plenary	1242	CR 29.673 0054 Rel-16 Definition of UcmfNotification	Ericsson	WI RACS CAT F
Plenary	1250	CR 29.673 0055 Rel-17 Definition of UcmfNotification	Ericsson	WI RACS CAT A
Plenary	1251	CR 29.673 0056 Rel-18 Definition of UcmfNotification	Ericsson	WI RACS CAT A
8.1.8	CT aspect of single radio voice continuity from 5GS to 3G	5G_SRVCC
8.1.9	CT Aspects of 5G URLLC	5G_URLLC
8.1.10	SBA interactions between IMS and 5GC	eIMS5G_SBA
8.1.11	Load and Overload Control of 5GC Service Based Interfaces	LOLC
8.1.12	5GS Enhanced support of OTA mechanism for configuration parameter update	5GS_OTAF
8.1.13	CT aspects of support for integrated access and backhaul	IABARC-CT
8.1.14	Nudsf Service Based Interface	NUDSF
8.1.15	Nsoraf Service Based Interface	NSORAF
8.2	CT4 Supported WIs
8.2.1	CT aspects on Enablers for Network Automation for 5G	eNA
8.2.2	CT aspects of Access Traffic Steering, Switch and Splitting support in 5G system	ATSSS
8.2.3	CT aspects of 5GS enhanced support of vertical and LAN services	Vertical_LAN
8.2.4	CT aspects of Cellular IoT support and evolution for the 5G System	5G_CIoT
8.2.5	CT aspects on enhancement of network slicing	eNS
8.2.6	CT aspects of System enhancements for Provision of Access to Restricted Local Operator Services by Unauthenticated Ues	PARLOS
8.2.7	CT aspects on wireless and wireline convergence for the 5G system architecture	5WWC
8.2.8	CT aspects of architecture enhancements for 3GPP support of advanced V2X services	eV2XARC
8.2.9	CT aspects of application layer support for V2X services	V2XAPP
8.2.10	CT aspects on Enhancement of 3GPP Northbound APIs	eNAPIs
8.2.11	CT aspects on 5G System - Phase 1	5GS_Ph1-CT
Plenary	1253	CR 29.572 0261 Rel-15 Definition of VelocityEstimate	Ericsson	WI 5GS_Ph1-CT CAT F
Plenary	1254	CR 29.572 0262 Rel-16 Definition of VelocityEstimate	Ericsson	WI 5GS_Ph1-CT CAT A
Plenary	1255	CR 29.572 0263 Rel-17 Definition of VelocityEstimate	Ericsson	WI 5GS_Ph1-CT CAT A
Plenary	1256	CR 29.572 0264 Rel-18 Definition of VelocityEstimate	Ericsson	WI 5GS_Ph1-CT CAT A
8.3	AoB for Rel-16 and earlier	TEI16, TEI15, TEI14, …..
8.3.1	TEI16, TEI15…	TEI16, TEI15, TEI14, ….
Main	1058	CR 29.518 1049 Rel-16 Add GPSI as ueContextId in Namf_Location_ProvidePositionInfo	ZTE	WI TEI16, 5GS_Ph1-CT CAT F
Main	1059	CR 29.518 1050 Rel-17 Add GPSI as ueContextId in Namf_Location_ProvidePositionInfo	ZTE	WI TEI16, 5GS_Ph1-CT CAT A
Main	1060	CR 29.518 1051 Rel-18 Add GPSI as ueContextId in Namf_Location_ProvidePositionInfo	ZTE	WI TEI16, 5GS_Ph1-CT CAT A
Main	1160	CR 29.518 1062 Rel-16 Add GPSI to 5GC-MT-LR Procedure without UDM Query	Ericsson	WI TEI16 CAT F
Main	1161	CR 29.518 1063 Rel-17 Add GPSI to 5GC-MT-LR Procedure without UDM Query	Ericsson	WI TEI16 CAT A
Main	1162	CR 29.518 1064 Rel-18 Add GPSI to 5GC-MT-LR Procedure without UDM Query	Ericsson	WI TEI16 CAT A
8.3.2	AoB of Rel-16 and earlier
8.3.3	Open API version and External docs	TEI16
29.502 0 Rel16 API version and External doc update	Nokia	Email approval	CR possibly needed Email approval
29.503 0 Rel16 API version and External doc update	Nokia	Email approval	CR possibly needed Email approval
29.504 0 Rel16 API version and External doc update	China Mobile	Email approval	CR possibly needed Email approval
29.505 0 Rel16 External doc update	China Mobile	Email approval	CR possibly needed Email approval
29.509 0 Rel16 API version and External doc update	Orange	Email approval	CR possibly needed Email approval
29.510 0 Rel16 API version and External doc update	Ericsson	Email approval	CR possibly needed Email approval
29.511 0 Rel16 API version and External doc update	Deutsche Telekom	Email approval	CR possibly needed Email approval
29.515 0 Rel16 API version and External doc update	CATT	Email approval	CR possibly needed Email approval
29.518 0 Rel-16 API version and External doc update	Ericsson	Email approval	CR possibly needed Email approval
29.526 0 Rel-16 API version and External doc update	ZTE	Email approval	CR possibly needed Email approval
29.531 0 Rel-16 API version and External doc update	Huawei	Email approval	CR possibly needed Email approval
29.540 0 Rel-16 API version and External doc update	ZTE	Email approval	CR possibly needed Email approval
29.541 0 Rel-16 API version and External doc update	Ericsson	Email approval	CR possibly needed Email approval
29.542 0 Rel-16API version and External doc update	Ericsson	Email approval	CR possibly needed Email approval
29.544 0 Rel16 API version and External doc update	Nokia	Email approval	CR possibly needed Email approval
29.550 0 Rel-16 API version and External doc update	Orange	Email approval	CR possibly needed Email approval
29.562 0098 Rel-16 API version and External doc update	Ericsson	Email approval	CR possibly needed Email approval
29.563 0 Rel-16 API version and External doc update	Ericsson	Email approval	CR possibly needed Email approval
29.571 0 Rel-16 API version and External doc update	Huawei	Email approval	CR possibly needed Email approval
29.572 0 Rel-16 API version and External doc update	Ericsson	Email approval	CR possibly needed Email approval
29.573 0 Rel-16 API version and External doc update	Huawei	Email approval	CR possibly needed Email approval
9	Update of the Work Plan
1010	Work Plan Work Plan	CT4 Chair
10	AoB
10.1	Rel-19 Related Discussions
10.2	AoB
11	Future meetings
12	Check of Approved Output Documents
1011	other Output Documents	CT4 Chair
13	Closing of the Meeting (16:00 Local time Friday)