3GPP TSG-CT WG4 Meeting #123	C4-242006

Hyderabad, India, 27th–31st May 2024

Source:	Chairman, TSG-CT WG4

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

Agenda item:	2

Document for:	INFORMATION

Saved 27/05/2024 12:49	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
2001	agenda Draft Agenda	CT4 Chair	Noted
2002	other eMeeting guidelines for CT4 Working Group meeting	CT4 Chair	Noted
2003	agenda Detailed agenda & time plan for CT4 meeting: status at document deadline	CT4 Chair	Noted
2004	agenda Detailed agenda & time plan for CT4 meeting: status on eve of meeting	CT4 Chair	Noted
2005	agenda Proposed allocation of documents to agenda items for CT4 meeting: status at document deadline	CT4 Chair	Noted
2006	agenda Proposed allocation of documents to agenda items for CT4 meeting: status on eve of meeting	CT4 Chair	Noted
2007	agenda The allocation of documents to agenda items for CT4 meeting: status at the end of meeting	CT4 Chair
3	Meeting Reports
2008	report Previous TSG CT & SA Status Report	CT4 Chair	withdrawn
2009	report Previous CT4 meeting report	MCC	Approved
4	Input Liaison Statements
2050	LS in LS “N32-f lifetime and reconnection” to 3GPP CT4/SA3	5GMRR	Postponed	5GMRR Doc 45_07r1 To: CT4, SA3 CC: 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” Postponed from CT4#122
2051	LS in Rel-18 LS on IVAS in MTSI, including RTP and SDP parameters	SA4	Noted	S4-240845 To: 3GPP CT1, 3GPP CT3, 3GPP CT4 CC: fraunhofer SA4 is about to conclude the Immersive Voice and Audio Services Codec (IVAS_codec) work item in Release 18 and has completed the work on the related specifications TS 26.250, TS 26.252, TS 26.253, TS 26.254, TS 26.255, TS 26.256, TS and 26.258. Part of TS 26.253 is the specification for the "RTP payload format and SDP parameters" in Annex A. In addition the CR related to TS 26.114 for IVAS introduction has been brought to a stable state. At its recent SA4#127-bis-e meeting SA4 has endorsed the attached CRs for TS 26.114 (IVAS introduction into MTSI) and TS 26.253 (Annex A on RTP payload format and SDP format parameters) and considers those being a stable basis for other specifications depending on them for supporting the IVAS codec, which includes the CT specifications of relevance. SA4 would like to ask CT1, CT3 and CT4 to take the above information into account as part of their work on the respective aspects of IVAS_Codec and base their work on the endorsed CRs in documents S4-240653 and S4-240664. Related contributions under agenda item 6.1.17
2052	LS in Rel-18 LS on ECS Configuration Information	CT WG1	Noted	C1-242674 To: SA2, SA3, SA6 CC: CT3, CT4 Contact: Samsung CT1 raised couple of questions to SA2, SA3, SA6 regarding ECS configuration info Propose to note
2053	LS in Rel-18 Reply LS on LS on Creation of private branches on the GitLab "5G_APIs" repository	SA WG5	withdrawn	S5-241920 To: 3GPP CT4 CC: 3GPP CT1, CT3, SA4, SA
2054	LS in Rel-19 LS on the stage 2 aspects of MINT_Ph2	CT WG1	Noted	C1-242675 To: TSG SA CC: TSG CT, SA2, CT4 Contact: China Telecom CT1 has discussed a WID proposal for MINT support in EPS (MINT_Ph2_EPS) in the CT1 April meeting, in order to support the following stage 1 service requirement specified in Rel-19 MINT_Ph2 by SA1: “Subject to regulatory requirements, operator's policy or UE capabilities, the 3GPP system shall be able to support a UE, with 5G-only national roaming access to a VPLMN, to obtain 4G connectivity service (e.g. voice call, mobile data service) from that VPLMN in the area where a Disaster Condition applies.” The WID proposal on MINT_Ph2_EPS includes both stage-2 and stage-3 aspects. The failure scenarios of the WID proposal is limited to RAN failure, consistent with the failure scenarios of Rel-17 MINT. With this, similar as working procedure done for Rel-17 MINT, CT1 is planning to define 4G PLMN selection for disaster roaming and end-to-end call flow regarding attach procedure after selection of a disaster roaming 4G PLMN. CT1 would like to ask TSG SA if there is any concern on this approach and expects any feedback on this way forward so that the normative phase can progress within Rel-19 timeframe. Propose to note
2055	LS in Rel-18 LS on Indicating the support of slice based N3IWF/TNGF selection from the UE to the network	CT WG1	Noted	C1-242934 To: SA2 CC: CT3, CT4 Contact: Nokia As per the current stage 2 requirements, the UE already indicates to the AMF whether it supports the slice-based N3IWF selection and/or the slice-based TNGF selection within the REGISTRATION REQUEST message during the registration procedure, which is in line with the legacy approach. However, as per the above stage 2 NOTEs, the UE also provides separate indications to the PCF about supporting those features. CT1 does not see the reason to step away from the legacy approach in which the AMF indicates to the PCF whether the UE supports slice-based N3IWF selection and/or the slice-based TNGF selection as this is aligned the protocol design defined from Rel-15. CT1 therefore asks SA2 to consider re-using the existing approach. Propose to note
2056	LS in Rel-18 Question on GPSI and Application Layer ID Mapping	CT WG3	Noted	C3-242616 To: SA2 CC: CT4 Contact: Ericsson CT3 would like to ask SA2: Question: Among the Nnef_UEId API and Nnef_ServiceParameter API, which one is better to implement the GPSI and Application Layer ID Mapping? Propose to note
2057	LS in Rel-18 LS on application layer ID	RAN WG2	Noted	R2-2403809 To: SA2, CT1, CT4 CC: Contact: Huawei RAN2 has agreed to add application layer ID in the SLPP header. RAN2 respectfully asks SA2, CT1 and CT4 to take the above agreement into account.
2058	LS in Rel-18 Reply to LS on Subscription of Data Channel	SA WG2	Noted	S2-2405107 To: CT4 CC: CT1 Contact: Samsung SA2 clarifies to CT4 that, the CR (C4-240719) fulfils stage 2 requirement of Data Channel subscription data and no extra information should be specified besides the authorization information. Propose to note
2059	LS in Rel-18 Reply LS on Rel-18 RedCap enhancements to address remaining ENs in TS 23.502	SA WG2	Noted	S2-2405421 To: RAN2, RAN3, CT1 CC: CT4 Contact: Huawei SA2 thanks RAN2 and CT1 LSs in the S2-2403889/R2-2401888 and S2-2403873/C1-241809. SA2 would like to provide the latest progress on REDCAP: - NR eRedCap indication is agreed to be included into the NGAP Initial UE message and the AMF shall store the NR eRedCap Indication in the UE context, consider that the RAT type is NR eRedCap, see 23.501 CR5254 (attached). - During handover from E-UTRA to NR, the target NG-RAN (i.e. gNB) provides the NR eRedCap indication to AMF in NGAP Path Switch Request message during Xn handover, or NGAP Handover Request Acknowledge message during N2 handover (including intra 5GS N2 handover and EPS to 5GS handover) based on the UE capability information provided by the source RAN to the target RAN. - SA2 has also agreed CR5371 for TS 23.501 (attached) to clarify that the UE provided (e)RedCap indication matches the UEs radio capabilities when accessing the network.
2060	LS in Rel-18 Reply to LS on provisioning ATSSS rules to the UE in EPC	SA WG2	OPEN	S2-2405458 To: CT1 CC: CT4 Contact: Samsung, NEC SA2 thanks CT1 to clarify on the provisioning ATSSS rules to the UE in EPC. CT1 asks a question with clause 4.22.2.3.1 in TS 23.502 text specified in Rel-17 and clause 4.22.2.4.1 in TS 23.502 text specified in Rel-18, as below: Why can ATSSS rules be provided via untrusted non-3GPP access to EPC but not via 3GPP access? SA2 wants to provide answer as below: In R17, the ATSSS Rules is not provided via 3GPP access to EPC, in order to minimize the impact on EPC. In R18, the ATSSS feature is enhanced to provide the ATSSS Rules via untrusted non-3GPP access to EPC, without further work on providing the ATSSS rule via 3GPP access to EPC. SA2 at present has no agreement to further update the specification. Related CRs being proposed in CT1 and CT4. Some techincal issues are raised few meetings ago. Length of ePCO IE, CT1 how to inform UE in 3GPP and non-3GPP access from EPC Wait for CT1 discussion before we agree CT4 changes. It should be possible to provide ATSSS rules over non-3GPP from EPC For CT4 part, 2094 We need to align the changes in CT1 and CT4 ZTE paper covers the issue. ZTE is fine to wait for CT1 agreement before CT4.
2061	LS in Rel-18 LS reply on LCS user plane connection binding to the UE	SA WG2	Noted	S2-2405797 To: CT1 CC: CT4, RAN2 Contact: CATT SA2 thanks CT1 for the liaison in S2-2403871/C1-241722 concerning the establishment and usage of a secure user plane connection between a UE and LMF for the transfer of LPP and certain LCS supplementary service messages. SA2 notes the following issues cited by CT1. 1. 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. 2. 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). SA2 has discussed above issues and agreed resolutions as bellow: Resolution of Issue 1: The LMF allocates an ID (e.g. LCS UP connection ID), to be used to associate with the LCS UP connection (and configuration for the connection to be established) for the UE. Resolution of Issue 2: If UE supports user plane positioning capability, the AMF shall include the same UE ID (i.e. SUPI or GPSI, existing parameters) in the subsequent Nlmf_Location_DetermineLocation request, LMF does the correlations of <SUPI or GPSI, LCS UP connection ID >. SA2 has agreed the attached CR to TS 23.273 to resolve both issues. Related CRs in CT4 2202, 2237.
2062	LS in Rel-18 Reply LS on LS on Creation of private branches on the GitLab "5G_APIs" repository	SA WG5	Noted	S5-241920 To: 3GPP CT4 CC: 3GPP CT1, CT3, SA4, SA Contact: Nokia Shanghai Bell 1 Overall description SA5 thanks CT4 for the LS on Creation of private branches on the GitLab "5G_APIs" repository in document C4-240636. Please find SA5’s reply below: SA5 is using “https://forge.3gpp.org/rep/sa5” as working repository to store and validate Forge code, and synchronize the validated OpenAPI code to "5G_APIs" repository to support unified 3GPP OpenAPI publication. There is no requirement for individual branches created under "5G_APIs" repository from SA5. SA5 code moderators will use the release draft branch only in "5G_APIs" repository without creating new branches or new private repositories. We would like to inform CT4, to fully leverage Forge/git as a version control system for a collaborative development environment, in SA5, we encourage CR authors to create CR development branch (private branch) under SA5 Forge repository when needed. The CR development branch may be used for immediate SA5 meeting or meetings in near future. SA5 working procedure provides guidance for the SA5 Forge repository branch naming conventions and branch clean up procedures to control the branch life span.
2063	LS in LS on MBS Communication Service Type	SA WG5	Noted	S5-242038 To: CT4 CC: RAN3 Contact: Ericsson SA5 has discussed and agreed to add MBS Communication Service Type IE into the QMCJob, which indicates whether doing QoE measurement shall be performed for MBS broadcast or multicast. This IE is used for both signaling and management based QoE measurement. For more details, please see the agreed CR.
2064	LS in LS on clarifications on consent management	GSMA OPG	OPEN	OPG_173_Doc_04 To: 3GPP SA3, 3GPP CT4, 3GPP CT3, 3GPP SA6 CC: 3GPP SA2, 3GPP SA Contact: Nokia Given the above context, GSMA OPG would like to get clarification from 3GPP on the following: When NEF or EES (as trusted AF) is exposing APIs using CAPIF RNAA, how is NEF or EES utilizing the UDM’s user consent information for processing authorization for API consumer/invoker? What is the relationship between CAPIF RNAA and UDM’s user consent information? Is there any plan/roadmap for a unified approach? For the UDM’s user consent information, are the user consent management aspects (e.g. capturing or revoking user consent from the subscriber) specified? Please illustrate. Is there any plan/roadmap for considering other legal bases for processing personal data apart from user consent (e.g. contract, legal obligations, vital interests of the data subject, public interest, and legitimate interest [GDPR]) in a unified way? What are the privacy considerations in 3GPP with respect to exposure of sensitive information (e.g. UE ID, location) to untrusted AFs.
2291	LS in Reply-LS on clarifications on consent management	SA3	OPEN	S3-242374 To: SA CC: SA2, SA6, CT3, CT4 Contact: Nokia New LS, any proposed handling?
2292	LS in Rel-18 Reply-LS on GSMA CVD-2023-0069 5G Core Network Attacks	SA3	Postponed	S3-242453 To: GSMA CVD CC: CT4 Contact: Huawei New LS, any proposed handling? Attachment seems to be wrong, S3-240895 is mentioned but S3-241895 is attached. Kimmo to ask for revision. Does CT4 formally access to GSMA papers being referred? Roya: should we postpone? We probably need the original LS from GSMA.
2293	LS in Rel-18 Reply LS on ECS configuration information	SA3	OPEN	S3-242620 To: CT1 CC: SA2, SA6, CT3, CT4 Contact: Huawei New LS, any proposed handling? Revision being asked by Kimmo due to attachment
2294	LS in Rel-18 LS on IVAS RTP payload format and support in MTSI	SA4	Noted	S4-241341 To: CT1, CT3, CT4 CC: Contact: Orange Proposed to postpone for discussion under clause 6.1.17
2295	LS in Rel-18 Reply LS on ECS Configuration Information	SA6	Noted	S6-242733 To: CT1 CC: SA2, SA3, CT3, CT4 Contact: Samsung New LS, any proposed handling?
5	WIDs	.
5.1	CT4 Led WIs	.
2103	discussion Rel-19 State of Rel-19 work related to additional enhancements for Uncrewed Aerial System in other WGs	Ericsson	Noted	Corresponding SA2 WI has NOT been approved Proposal to have rapporteurship from Ericsson and LGE Should be one (pointed out from CT persprctive)
2141	WID revised Rel-18 CT Aspects of Edge Computing Phase 2	Huawei	Revised to C4-242296	Wait for SA2 response to agree the changes related to CT4. Completion target meeting, should it be extended without exception? To be checked with CT Chair
2296	WID revised Rel-18 CT Aspects of Edge Computing Phase 2	Huawei
2104	WID revised Rel-18 Revised WID on CT impacts of EVS Codec Extension for Immersive Voice and Audio Services	Nokia	Agreed	CT1 has already endorsed.
2134	WID new Rel-19 Subscriber Data Migration	Ericsson	Revised to C4-242297	Any impact on AANF (related to AKMA)? (From CMCC) Need to make sure the split with SA5 remit. Question whether any updates on consumer NFs. Nokia, Huwei, China Telecom
2297	WID new Rel-19 Subscriber Data Migration	Ericsson
2180	discussion Rel-19 Discussion on TEI19_MINPA WID	Ericsson	Noted
2181	WID new Rel-19 New WID on CT Aspects on TEI19_MINPA	Ericsson	Revised to C4-242298	Nokia, Huawei, ZTE, China Telecom, Intel supports 29.571 changes not required as it is Boolean information
2298	WID new Rel-19 New WID on CT Aspects on TEI19_MINPA	Ericsson
2198	WID new Rel-19 New WID on Service Based Interface Protocol Improvements Release 19	China Mobile	Agreed
2235	WID new Rel-19 New SID on AI Data Collection And Protocol Release 19	China Mobile	Revised to C4-242299	Bruno: Nokia can support if comments below are captured. Scope should remain in the remit of existing architecture, i.e. study on notification. Study should also on existing protocol. Adding Subcription and reporting might help, and so these can be considered for the study. Proper justification over existing protocol should be covered in Justification. Should not be limited to UPF event exposure, where similar cases can be covered. Should not be limited to 5GC but should be applicable for e.g. 6G or future, so that it is future proof. SID should be updated to include these comments. Nokia will not agree if the scope is not limited to UPF exposure. Frank: Cannot agree based on comments in 2236. PFCP already supports reporting for different PFCP sessions, so efficiency is already covered. Shunsuke: Since Rel19 is supposed to be the last release, agree with the comment for requiring future proof protocol. Having multiple protocol increases cost and so should have clear justification. Marujua: Orange supports the new SID. With the experiment on PFCP, see the benefit in the study.
2299	WID new Rel-19 New SID on AI Data Collection And Protocol Release 19	China Mobile
2236	discussion Rel-19 Discussion on Protocol Optimization for AI Data Collection	China Mobile	Noted	Frank: still have concern with the study. UPF is still capable for handling. TCP based / UDP based is well known. Transmission of message is very small portion of load CP/UP separation, defined UPF event notification over HTTP as additional guideline, so going against this guideline is not sufficient If really required, clear stage2 requirement should be specified.
5.2	CT4 Supported WIs	.
2096	WID revised Rel-18 Revised WID on CT aspects of enhancement of 5G UE Policy	Intel	Endorsed	Related CR in 2284 (to 29.502), and should agree the CR to agree this WID update.
2131	WID new Rel-19 Protocol enhancements for Mission Critical Services	Ericsson	Revised to C4-242300	Updates already discussed in CT3, and requires update Huawei supports Justification needs to include ongoing SA6 work. Objective should clarify impacts for each WG.
2300	WID new Rel-19 Protocol enhancements for Mission Critical Services	Ericsson
2135	WID new Rel-19 CT aspects of Providing per-subscriber VLAN instructions from UDM and DN-AAA	Ericsson	Revised to C4-242301
2301	WID new Rel-19 CT aspects of Providing per-subscriber VLAN instructions from UDM and DN-AAA	Ericsson	Jesus: will check with SA2 whether the impact is already identified
2136	discussion Rel-19 Rel-19 WI on Providing per-subscriber VLAN instructions from UDM and DN-AAA	Ericsson	Noted	Hao : questioning whether we can already identify CT4 impact
2137	discussion Rel-19 Rel-19 WI on Enhancing Parameter Provisioning with static UE IP address and UP security policy	Ericsson	Noted	What is the image of "UP Security"? Stage 2 should have clear explantion.
2138	WID new Rel-19 CT aspects of Enhancing Parameter Provisioning with static UE IP address and UP security policy	Ericsson	Revised to C4-242302
2302	WID new Rel-19 CT aspects of Enhancing Parameter Provisioning with static UE IP address and UP security policy	Ericsson
2195	WID new Rel-19 New WID on enhancement of controlling RAT utilization	Vodafone GmbH	Revised to C4-242303	From CT4 perspective, Stage2 requirement should be clarified. If it comes from 23.122, this should be clarified.
2303	WID new Rel-19 New WID on enhancement of controlling RAT utilization	Vodafone GmbH
2271	discussion Rel-19 Rel-19 Enhancements of UE Policy	Ericsson	Noted	More clarification on clause 2.1 can help.
2281	discussion Rel-19 "Steering of Roaming (SoR) during the registration" part of Roaming value-added services	Ericsson	Noted	Notification shown on 2nd missing item seems to require stage2 clarfication. SA2 has mini-WID for Rel19 on RVAS. It seems to clash. SOR-AF has impact , and this WID needs to clarify the issue. CT1 discussed and objected to do work split. ZTE supports to split the notification and RVAS discussion as it has different aspect. Hanna: prefer not to split Jesus: Who will do the stage2 aspect for RVAS if SOR-AF aspect?
2282	WID new Rel-19 "Steering of Roaming (SoR) during the registration" part of Roaming value-added services	Ericsson	Revised to C4-242304
2304	WID new Rel-19 "Steering of Roaming (SoR) during the registration" part of Roaming value-added services	Ericsson
6	Release 18
6.1	CT4 Led WIs
6.1.1	Service based Interface protocol improvements	SBIProtoc18
Plenary	2012	CR 29.500 0426 Rel-18 Header case	Nokia	Revised to C4-242305	WI SBIProtoc18 CAT F Change on coversheet, and some minor typos. Question whether if existing implmentations might have case sensitive. Are we fine? But this is the right direction, so we should change in this manner. Ericsson is fine, Huawei asking for some checking.
2305	CR 29.500 0426 Rel-18 Header case	Nokia
Plenary	2013	CR 29.500 0432 Rel-18 Clarification on Feature Negotiation	Nokia	Revised to C4-242306	WI SBIProtoc18 CAT F Roya prefers different text for clarity. Varini has text proposal. To be discussed among interested parties
2306	CR 29.500 0432 Rel-18 Clarification on Feature Negotiation	Nokia
Breakout	2014	CR 29.503 1258 Rel-18 EmergencyInfo clarification	Nokia	WI SBIProtoc18 CAT F
Breakout	2015	CR 29.503 1259 Rel-18 Missing descriptions in Nudm_SDM API	Nokia	WI SBIProtoc18 CAT F
Breakout	2016	CR 29.563 0088 Rel-18 UeContextInPgw modification	Nokia	WI SBIProtoc18 CAT F
Breakout	2020	CR 29.509 0218 Rel-18 Default Configured S-NSSAIs	Nokia	WI SBIProtoc18 CAT F
Main	2046	CR 29.518 1077 Rel-18 Handling of unsupported event subscription	Huawei	WI SBIProtoc18 CAT B
Plenary	2048	CR 29.500 0428 Rel-18 Indication of Intermediate NF	Ericsson	Revised to C4-242307	WI SBIProtoc18 CAT F
2307	CR 29.500 0428 Rel-18 Indication of Intermediate NF	Ericsson
Main	2076	CR 29.673 0057 Rel-18 The term Payload is replaced with Content due to RFC 9113	Ericsson	WI SBIProtoc18 CAT F
Plenary	2079	CR 29.571 0554 Rel-18 Clarification on MNC Encoding	ZTE	Revised to C4-242308	WI SBIProtoc18 CAT F Ulrich: have different understanding on with or without leading MNC. Jesus: understands similar as ZTE, with or without 0 at the beginning should be interpreted same. Roya: wants to check internally, but prefers different text for clarification. Ulrich: ITU specifies the MNC, and we should not have our own understanding and update Zhijun: am fine to change text Mamdoh: we already have specification saying we can use 2 or 3 digits, so if we start defining new meaning us such, this might create backwards imcomptibility issue Zhijun: Jesus: if we have understanding that MNC starting with 0, we have many of these meanings in 23.003 and we need to correct all these
2308	CR 29.571 0554 Rel-18 Clarification on MNC Encoding	ZTE
Main	2089	CR 29.518 1081 Rel-18 Clarify the condition in which the SMF provides the MD-SDT Control Information to the UPF a new Namf_MT_EnableUEReachability request to the AMF	ZTE	Moved to 6.1.4	WI SBIProtoc18 CAT F
Main	2116	CR 29.502 0779 Rel-18 504 Gateway Timeout in Update SM Context procedure	Nokia	WI SBIProtoc18 CAT F
Plenary	2117	CR 29.510 1009 Rel-18 SEPP profile when no remote PLMN is reachable through the SEPP	Nokia	Revised to C4-242309	WI SBIProtoc18 CAT F The dummy value is mentioned as "e.g." is this fine? This should be left to implementation. However, fine to change "e.g." to "i.e." so that it is clear in all implementation. Also change "may" to "shall" for the inclusion of dummy MCC MNC What is the use case for SEPP not connecting to any other PLMN? E.g. for SNPN connectivity but no other PLMN This aspect should be clarified. Change for more clarity Roya:
2309	CR 29.510 1009 Rel-18 SEPP profile when no remote PLMN is reachable through the SEPP	Nokia
Main	2118	CR 29.518 1085 Rel-18 Handling of NW triggered SR during an on-going UE triggered SR race condition	Nokia	WI SBIProtoc18 CAT F
Plenary	2139	CR 29.510 1012 Rel-18 Clarifications to udrInfo, udmInfo, ausfInfo and pcfInfo	Ericsson	Revised to C4-242310	WI SBIProtoc18 CAT F Jesus: need to make sure that the implementation is to be consistent. Roya: Is there any way to check the logic? NRF is not required to check. If so, we should not make it as normative text but to make it informative. How to do this? Make it a note outside of table. Ulrich: the proposed text is misleading, and "may not include" is not in line with drafting rule Jesus: in a semented network, Group ID should be used, is this the same understanding. Zhijun: Yes, however use of Group ID is not mandatory, so to align with such implementation the wording should be clarified.
2310	CR 29.510 1012 Rel-18 Clarifications to udrInfo, udmInfo, ausfInfo and pcfInfo	Ericsson
Plenary	2140	CR 29.510 1013 Rel-18 Matching of ML Analytics Info	Ericsson	Revised to C4-242311	WI SBIProtoc18 CAT F Roya requests for more generic or Bruno : The WID should be TEI18, eNA Ph2
2311	CR 29.510 1013 Rel-18 Matching of ML Analytics Info	Ericsson	WI TEI18, eNA Ph2 CAT F
Main	2142	CR 29.531 0202 Rel-18 Returning UNSUPPORTED_EVENT_TYPE	Huawei	WI SBIProtoc18 CAT B
Main	2143	CR 29.536 0128 Rel-18 Returning UNSUPPORTED_EVENT_TYPE	Huawei	WI SBIProtoc18 CAT B
Plenary	2144	CR 29.571 0556 Rel-18 Corrections for MDT enhancements to support NPN	Huawei	Agreed	WI SBIProtoc18 CAT B
Plenary	2145	CR 29.571 0557 Rel-18 Description of mbsMediaComps attribute	Huawei	Revised to C4-242315	WI SBIProtoc18 CAT F WI code should be TEI18, 5MBS
2315	CR 29.571 0557 Rel-18 Description of mbsMediaComps attribute	Huawei	Agreed	WI TEI18, 5MBS CAT F WOP
Main	2146	CR 29.673 0058 Rel-18 Correction on OpenAPI definition of ManAssOpRequestlist	Huawei	Withdrawn	WI SBIProtoc18 CAT F
Main	2187	CR 29.518 1060 Rel-18 Non-3GPP Not Taken Over Indication	Ericsson	WI SBIProtoc18 CAT F
Breakout	2208	CR 29.503 1264 Rel-18 Remove additional application error	Huawei	WI SBIProtoc18 CAT F
Breakout	2209	CR 29.505 0506 Rel-18 Syntax of callbacks	Huawei	WI SBIProtoc18 CAT F
Breakout	2210	CR 29.515 0177 Rel-18 Returning UNSUPPORTED_EVENT_TYPE	Huawei	WI SBIProtoc18 CAT B
Breakout	2211	CR 29.572 0267 Rel-18 Returning UNSUPPORTED_EVENT_TYPE	Huawei	WI SBIProtoc18 CAT B
Plenary	2212	CR 29.571 0562 Rel-18 Update on data type Any type	Huawei	Agreed	WI SBIProtoc18 CAT F
Plenary	2240	CR 29.510 1014 Rel-18 Handling of certificate expiry/re-issue	Samsung	Revised to C4-242317	WI SBIProtoc18 CAT B For certificate exipry, who and when does the status change to "suspended"? To implementation It is not the issue for NRF checks this.
2317	CR 29.510 1014 Rel-18 Handling of certificate expiry/re-issue	Samsung
Breakout	2242	CR 29.503 1255 Rel-18 Missing Description fields in Nudm_UECM API definition	Ericsson	WI SBIProtoc18 CAT F
Main	2253	CR 29.564 0096 Rel-18 Correct the api name of Nupf_GetUEPrivateIPaddrAndIdentifiers service	CATT	WI SBIProtoc18 CAT F
Plenary	2267	CR 29.573 0203 Rel-18 HTTP redirection for multiple SEPPs per PLMN	Deutsche Telekom AG	WI SBIProtoc18 CAT F
Plenary	2268	discussion 29.573 Rel-18 HTTP redirection for multiple SEPPs per PLMN	Deutsche Telekom AG
Breakout	2269	CR 29.504 0271 Rel-18 Support of URI reference	Ericsson	WI SBIProtoc18 CAT F
Plenary	2273	discussion Rel-18 Discussion on support of 204 status code for HTTP GET method	China Mobile Com. Corporation	Noted	Ulrich: Why 200 OK with empty object cannot be used. John: 200 OK and 204 response has significant difference as mentioned in the discussion paper (200 OK responds resource representation, while no content is different while the transaction itself is successful) Jesus: supports the comment John Varini: 404 is the right way forward. Caixia: CT3 already is discussed this aspect. Can provide feedback to China Mobile. Zhenning: 404 cannot provide the way that the transaction is successfully treated. Thus 2xx would be better. 200 with empty entry with 204 coulde be the similar way. Another information is that 204 is used in CT3 from R15.... Jesus: Perhaps it should be limited to specific API on CT3 spec if they want Ulrich:
Plenary	2274	CR 29.500 0436 Rel-18 Service specific support of 204 status code for HTTP GET method	China Mobile	OPEN	WI SBIProtoc18 CAT F
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
Main	2038	CR 29.244 0855 Rel-18 Activation of DL data size reporting for support of MT-SDT	Ericsson	WI NR_REDCAP_Ph2 CAT F Overlapping with 2090
Main	2090	CR 29.244 0857 Rel-18 Clarify the condition in which the SMF provides the MD-SDT Control Information to the UPF	ZTE	WI NR_REDCAP_Ph2 CAT F
Main	2089	CR 29.518 1081 Rel-18 Clarify the condition in which the SMF provides the MD-SDT Control Information to the UPF a new Namf_MT_EnableUEReachability request to the AMF	ZTE	WI NR_REDCAP_Ph2 CAT F
Main	2045	CR 29.518 1076 Rel-18 Support for the eRedCap UEs	Huawei	WI NR_REDCAP_Ph2 CAT B Overlapping with 2080, 2260
Main	2080	CR 29.518 1080 Rel-18 eRedCAP Indication in UE Context	ZTE	WI NR_REDCAP_Ph2 CAT F
Main	2260	CR 29.518 1090 Rel-18 Transfer of the NR eRedCap indication from S-AMF to T-AMF	Nokia	WI NR_REDCAP_Ph2, NR_redcap_enh-Core CAT F
Main	2147	CR 29.244 0858 Rel-18 Support of NR_EREDCAP	Huawei	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
2049	CR 29.572 0265 Rel-18 Conditional SUPI and/or GPSI in Nlmf_Location service operations	OPPO	revised to C4-242237	Revision of C4-242237 WI 5G_eLCS_Ph3 CAT B
Plenary	2237	CR 29.572 0265 Rel-18 Conditional SUPI and/or GPSI in Nlmf_Location service operations	OPPO	Merged with C4-242312	WI 5G_eLCS_Ph3 CAT B Overlapping with 2202
Plenary	2202	CR 29.572 0256 Rel-18 Support of LCS user plane connection binding to the UE	Huawei, CATT	Revised to C4-242312	WI 5G_eLCS_Ph3 CAT F
2312	CR 29.572 0256 Rel-18 Support of LCS user plane connection binding to the UE	Huawei, CATT, OPPO
2077	CR 29.518 1079 Rel-18 LCS related clarification to N1MessageContainer	OPPO	revised to C4-242238	Revision of C4-242238 WI 5G_eLCS_Ph3 CAT F
2238	CR 29.518 1079 Rel-18 LCS related clarification to N1MessageContainer	OPPO	revised to C4-242239	Revision of C4-242239 WI 5G_eLCS_Ph3 CAT F
Plenary	2239	CR 29.518 1079 Rel-18 LCS related clarification to N1MessageContainer	OPPO	Withdrawn	WI 5G_eLCS_Ph3 CAT F
Plenary	2203	CR 29.518 1087 Rel-18 Update the description of EventNotify service	Huawei	Revised to C4-242313	WI 5G_eLCS_Ph3 CAT F WI code should be changed to TEI18 Offline discussion needed among Mamdoh and Hao.
2313	CR 29.518 1087 Rel-18 Update the description of EventNotify service	Huawei
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
Plenary	2043	CR 29.510 0999 Rel-18 Update EASDF registration and discovery	Huawei	Merged with C4-242318	WI EDGE_Ph2 CAT B Overlapping with 2110 Roya: fine to merge with Nokia paper in 2110
Plenary	2110	CR 29.510 1008 Rel-18 DNS security protocols supported by (V-)EASDF	Nokia	Revised to C4-242318	WI EDGE_Ph2 CAT F Roya: typo exists, and add changes to re-used data type Frank: Co-sign
2318	CR 29.510 1008 Rel-18 DNS security protocols supported by (V-)EASDF	Nokia, Huawei, Ericsson
Plenary	2109	CR 29.510 1007 Rel-18 ECS Address Configuration Information (EACI) application data subset	Nokia	Agreed	WI EDGE_Ph2 CAT F
Main	2111	CR 29.556 0040 Rel-18 Security of EAS discovery procedure via (V-)EASDF	Nokia	WI EDGE_Ph2 CAT F Overlapping with 2149
Main	2149	CR 29.556 0041 Rel-18 DNS Security Information of EASDF	Huawei	WI EDGE_Ph2 CAT B
Main	2148	CR 29.502 0780 Rel-18 DNS Security Information of vEASDF/Local DNS Server/Resolver	Huawei	WI EDGE_Ph2 CAT B
Main	2150	CR 29.502 0781 Rel-18 Service operations supported in HR-SBO	Huawei	WI EDGE_Ph2 CAT F
Main	2151	CR 29.556 0042 Rel-18 Service operations supported in HR-SBO	Huawei	WI EDGE_Ph2 CAT F
Plenary	2170	CR 29.503 1244 Rel-18 Add security parameter to ECS address IE	Samsung	Postponed to Wednesday Q5	WI EDGE_Ph2 CAT B
Plenary	2171	CR 29.503 1245 Rel-18 Add list of supported PLMNs to ECS address IE	Samsung	Postponed to Wednesday Q5	WI EDGE_Ph2 CAT B
6.1.9	Enhancement of NSAC for maximum number of UEs with at least one PDU session/PDN connection	eNSAC
6.1.10	UPF enhancement for exposure and SBA	UPEAS
Main	2112	CR 29.564 0094 Rel-18 Corrections to the Nupf_EventExposure service	Nokia	WI UPEAS CAT F
Main	2152	CR 29.502 0782 Rel-18 Subscription of UPF event via I-SMF	Huawei	WI UPEAS CAT B
Main	2153	CR 29.564 0095 Rel-18 UE ID corrections	Huawei	WI UPEAS CAT F
6.1.11	5 MBS Phase 2	5MBS_PH2
Main	2023	CR 29.532 0091 Rel-18 Correction of enumeration description and editorial mistake	Huawei	WI 5MBS_Ph2 CAT F
6.1.12	Enhancements on Service-based support for SMS in 5GC	eSMS_SBI
Breakout	2125	CR 23.540 0019 Rel-18 IP-SM-GW Reference Points for MO-SMS	Ericsson	WI eSMS_SBI CAT F
6.1.13	Study on Reducing Information Exposure over SBI	FS_RedInfExp_SBI
Plenary	2021	pCR 29.857 Rel-18 Correction of Example 3	Nokia	Agreed
TR 29.857v1.2.0	Samsung
6.1.14	Study on IMS Disaster Prevention and Restoration Enhancement	FS_IMS_RES
Breakout	2065	LS out LS on IMS (re)-registration procedure for routing without I-CSCF	China Telecom Corporation Ltd.
Breakout	2066	pCR 29.866 Rel-18 pCR on TR 29.866 Update Solution #2 Preventing the IMS disaster in the HSS overload scenario	China Telecom, Huawei
Breakout	2067	pCR 29.866 Rel-18 pCR on TR 29.866 Evaluation and conclusion for KI#4	China Telecom, Huawei
Breakout	2068	pCR 29.866 Rel-18 pCR on TR 29.866 Evaluation and conclusion for KI#1	China Telecom Corporation Ltd.
Breakout	2092	pCR 29.866 Rel-18 Pseudo-CR on new solution to address KI#3 in the case of PGW/SMF/UPF failure	ZTE
Breakout	2093	pCR 29.866 Rel-18 Pseudo-CR on new solution to address KI #3 in the case of UP data transfer failure	ZTE
Breakout	2172	pCR 29.866 Rel-18 Update Solution#4: Solution for HSS/UDM bypass	Huawei
Breakout	2173	pCR 29.866 Rel-18 Add mapping of solutions to Key Issues	Huawei
Breakout	2174	pCR 29.866 Rel-18 KI#2 evaluation and conclusion	Huawei
Breakout	2175	pCR 29.866 Rel-18 KI#3 evaluation and conclusion	Huawei
TR 29.866v0.5.0	China Telecom
6.1.15	CT aspects of home network triggered primary authentication	HN_Auth
Breakout	2091	CR 29.503 1262 Rel-18 Clarify response codes for Reauth Notification in different cases	ZTE	WI HN_Auth CAT F
6.1.16	NRF API enhancements to avoid signalling and storing of redundant data	NRFe
Plenary	2081	CR 29.510 1001 Rel-18 Write Access to Shared Profile Data	ZTE	Revised to C4-242314	WI NRFe CAT F
2314	CR 29.510 1001 Rel-18 Write Access to Shared Profile Data	ZTE
6.1.17	CT impacts of EVS Codec Extension for Immersive Voice and Audio Services	IVAS_Codec
Plenary	2100	CR 23.333 0146 Rel-18 Adding support for IVAS codec	Ericsson, Qualcomm Incorporated, Nokia	Revised to C4-242289	WI IVAS_Codec CAT B
2289	CR 23.333 0146 Rel-18 Adding support for IVAS codec	Ericsson, Qualcomm Incorporated, Nokia	Agreed
Plenary	2101	CR 29.333 0114 Rel-18 Adding support for IVAS codec	Ericsson, Nokia, Qualcomm Incorporated	Agreed	WI IVAS_Codec CAT B
Plenary	2102	CR 29.232 0663 Rel-18 Adding support for IVAS codec	Qualcomm Incorporated, Ericsson, Nokia	Agreed	WI IVAS_Codec CAT B
Plenary	2105	CR 23.334 0185 Rel-18 Adding support for IVAS codec	Nokia, Qualcomm Incorporated, Ericsson	Revised to C4-242288	WI IVAS_Codec CAT B
2288	CR 23.334 0185 Rel-18 Adding support for IVAS codec	Nokia, Qualcomm Incorporated, Ericsson	Agreed
Plenary	2106	CR 29.334 0155 Rel-18 Adding support for IVAS codec	Nokia, Qualcomm Incorporated, Ericsson	Agreed	WI IVAS_Codec CAT B
Plenary	2107	CR 29.238 0070 Rel-18 Adding support for IVAS codec	Nokia, Qualcomm Incorporated, Ericsson	Agreed	WI IVAS_Codec CAT B
Plenary	2108	CR 29.332 0203 Rel-18 Adding support for IVAS codec	Nokia, Qualcomm Incorporated, Ericsson	Agreed	WI IVAS_Codec CAT B
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	2184	CR 29.572 0266 Rel-18 Remote UE Indication in Location Information	Ericsson	WI 5G_ProSe_Ph2 CAT B
Breakout	2186	CR 29.518 1086 Rel-18 Remote UE Indication in Location Information	Ericsson	WI 5G_ProSe_Ph2 CAT B
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	2022	CR 29.503 1252 Rel-18 Updates on AF request Authorization information	Huawei, Nokia, Ericsson	Agreed	WI TRS_URLLC CAT B Revision of already agreed document, to correct attribute name
Plenary	2041	CR 29.571 0544 Rel-18 Make IEs related TRS_URLLC nullable	Ericsson	Revised to C4-242286	WI TRS_URLLC CAT B
2286	CR 29.571 0544 Rel-18 Make IEs related TRS_URLLC nullable	Ericsson	Agreed
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	2040	Work Plan Rel-18 Work Plan for ATSSS Phase 3	Lenovo
Plenary	2094	CR 29.274 2108 Rel-18 Provisioning of ATSSS parameters via APCO IE	ZTE	WI ATSSS_Ph3 CAT F
6.2.15	Enablers for Network Automation for 5G phase 3	eNA_PH3
Plenary	2031	CR 29.510 0998 Rel-18 Alignment of discovery parameters with stage-2	Huawei	Revised to C4-242319	WI eNA_Ph3 CAT F Clash with Nokia paper in TEI18 in 2259 In order to clarify the reason for adding the feature, to change the WI code, and merge the contents from 2259. WI code to be changed to TEI18, eNA_Ph2.
2319	CR 29.510 0998 Rel-18 Alignment of discovery parameters with stage-2	Huawei, Nokia	WI TEI18, eNA_Ph2 CAT F
Plenary	2095	CR 29.504 0269 Rel-18 Adding feature PfdDetermination	ZTE	Revised to C4-242321	WI eNA_Ph3 CAT F
2321	CR 29.504 0269 Rel-18 Adding feature PfdDetermination	ZTE
Plenary	2098	CR 29.510 1005 Rel-18 Correction of NWDAF registration	Huawei	Revised to C4-242322	WI eNA_Ph3 CAT F Questions raised, offline needed
2322	CR 29.510 1005 Rel-18 Correction of NWDAF registration	Huawei
Plenary	2099	CR 29.510 1006 Rel-18 Specifying access token request and claims for NWDAF containing MTLF	Huawei	Revised to C4-242323	WI eNA_Ph3 CAT B
2323	CR 29.510 1006 Rel-18 Specifying access token request and claims for NWDAF containing MTLF	Huawei
2189	CR 29.573 0198 Rel-18 Exchanging data or analytics between PLMNs	NTT DOCOMO	withdrawn	WI eNA_Ph3 CAT B
Plenary	2190	CR 29.500 0433 Rel-18 Exchanging data or analytics between PLMNs	NTT DOCOMO	Revised to C4-242325	WI eNA_Ph3 CAT B Wait if Jones have any feedback.
2325	CR 29.500 0433 Rel-18 Exchanging data or analytics between PLMNs	NTT DOCOMO
Plenary	2200	CR 29.573 0199 Rel-18 Exchanging data or analytics between PLMNs	NTT DOCOMO	Revised to C4-242324	WI eNA_Ph3 CAT B
2324	CR 29.573 0199 Rel-18 Exchanging data or analytics between PLMNs	NTT DOCOMO
6.2.16	CT aspects on enhancement of network slicing phase 3	eNS_PH3
Main	2087	CR 29.510 1004 Rel-18 Examples of NsacfInfo for different deployments	ZTE	WI eNS_Ph3 CAT F
Main	2088	CR 29.518 1046 Rel-18 Subscribe to event notification for Slice Service Area	ZTE	WI eNS_Ph3 CAT F
Main	2097	CR 29.518 1082 Rel-18 Update of Network Slice Deregistration Inactive Timer information	Huawei	WI eNS_Ph3 CAT B
Main	2255	CR 29.536 0125 Rel-18 NSAC optimization for network slice replacement	Nokia, Huawei, ZTE	WI eNS_Ph3 CAT B
6.2.17	Generic group management, exposure and communication enhancements	GMEC
Breakout	2204	CR 29.503 1263 Rel-18 Update on Group Identifier Translation	Huawei	WI GMEC CAT F
6.2.18	CT aspects of Next Generation Real time Communication services	NG_RTC
Breakout	2176	CR 29.175 0004 Rel-18 Correction on the Nimsas_MediaControl OpenAPI	Huawei	WI NG_RTC CAT F
Breakout	2177	CR 29.571 0558 Rel-18 Clarification on the maxRetry and maxTime of DcStream	Huawei	WI NG_RTC CAT F
Breakout	2178	CR 29.571 0559 Rel-18 Define the common data type for MDC interface	Huawei, China Mobile, CATT	WI NG_RTC CAT F
Breakout	2179	CR 29.176 0011 Rel-18 Update the MDC1 and MDC2 interface information	Huawei, China Mobile, CATT	WI NG_RTC CAT F
2182	CR 29.571 0560 Rel-18 Inclusion of video and audio media	Huawei	withdrawn	WI NG_RTC CAT F
2183	CR 29.175 0005 Rel-18 Inclusion of video and audio media	Huawei	withdrawn	WI NG_RTC CAT F
Breakout	2185	CR 29.176 0012 Rel-18 Inclusion of the video and audio media	Huawei	WI NG_RTC CAT F
Breakout	2191	CR 29.330 0003 Rel-18 Editorial correction to Sc-pull procedure	China Mobile	WI NG_RTC CAT D
Breakout	2192	CR 29.571 0561 Rel-18 Update the MediaProxy value and update the DcEndpoint data type	China Mobile, Huawei	WI NG_RTC CAT F
2193	CR 29.176 0013 Rel-18 Update the presence condition and cardinality for mediaProxyConfig	China Mobile	revised to C4-242266	Revision of C4-242266 WI NG_RTC CAT F
Breakout	2194	CR 29.175 0006 Rel-18 Update the presence condition and cardinality for mediaProxyConfig	China Mobile, Huawei	WI NG_RTC CAT F
Breakout	2196	CR 29.175 0007 Rel-18 Update the DcMediaSpecification for Nimsas_SessionEventControl Service API	China Mobile, Huawei	WI NG_RTC CAT F
Breakout	2197	CR 29.175 0008 Rel-18 Update the DcMediaSpecification Datatype for MdcEndpoint	China Mobile, Huawei, CATT	WI NG_RTC CAT F
Breakout	2244	CR 29.510 1015 Rel-18 Add new NotificationType for DC session event notification	CATT	WI NG_RTC CAT B
Breakout	2245	CR 29.175 0009 Rel-18 Update the SessionEventNotificationUri for session event notification	CATT	WI NG_RTC CAT F
Breakout	2266	CR 29.176 0013 Rel-18 Update the presence condition and cardinality for mediaProxyConfig	China Mobile, Huawei	WI NG_RTC CAT F
Breakout	2272	CR 29.175 0010 Rel-18 Report the media HOLD to DCSF	Huawei, CMCC	WI NG_RTC CAT F
Breakout	2285	CR 29.175 0011 Rel-18 Add the Media re-negotiation indication to Nimsas_MediaControl API to support AR	China Mobile, 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	2047	CR 29.518 1078 Rel-18 NGAP Reference to Ranging and Sidelink Positioning Service Information	Ericsson	WI Ranging_SL CAT F
Breakout	2184	CR 29.572 0266 Rel-18 Remote UE Indication in Location Information	Ericsson	Moved to 6.2.6	WI Ranging_SL CAT B
Breakout	2186	CR 29.518 1086 Rel-18 Remote UE Indication in Location Information	Ericsson	Moved to 6.2.6	WI Ranging_SL CAT B
Breakout	2205	CR 29.586 0008 Rel-18 Add missing description in the API	Huawei	WI Ranging_SL CAT F
Breakout	2206	CR 29.586 0009 Rel-18 Remove addtional data type	Huawei	WI Ranging_SL CAT F
Breakout	2207	CR 29.586 0010 Rel-18 Update on UserInfoId	Huawei	WI Ranging_SL CAT F
Breakout	2229	CR 29.504 0270 Rel-18 Feature support	Ericsson	WI Ranging_SL, AIMLsys CAT F
Breakout	2230	CR 29.515 0181 Rel-18 Alignment with naming conventions.	Ericsson	WI Ranging_SL CAT F
Breakout	2231	CR 29.518 1089 Rel-18 Alignment with naming conventions.	Ericsson	WI Ranging_SL CAT F
Breakout	2232	CR 29.572 0272 Rel-18 Alignment with naming conventions.	Ericsson	WI Ranging_SL CAT F
Breakout	2275	CR 29.505 0507 Rel-18 UE RangingSL Positioning privacy profile	Xiaomi, Ericsson	WI Ranging_SL CAT B
Breakout	2276	CR 29.504 0272 Rel-18 UE RangingSL Positioning privacy profile	Xiaomi, Ericsson	WI Ranging_SL CAT F
Breakout	2277	CR 29.503 1269 Rel-18 Update on UE RangingSL Positioning privacy profile	Xiaomi, Ericsson	WI Ranging_SL CAT F
Breakout	2278	CR 24.080 0118 Rel-18 Notification for privacy check on UE for RangingSl	Xiaomi, Ericsson	WI Ranging_SL CAT F
Breakout	2279	CR 29.518 1091 Rel-18 Notification for privacy check on UE for RangingSl	Xiaomi, Ericsson	WI Ranging_SL CAT F
Breakout	2280	CR 29.515 0183 Rel-18 Update privacy check for UEs belonging to different PLMN(s)	Xiaomi, Ericsson	WI Ranging_SL CAT F
Breakout	2290	CR 29.503 1257 Rel-18 UE RangingSL Positioning privacy profile	Xiaomi	WI Ranging_SL CAT B Revision of agreed CR from CT4#122 meeting, triggered by rapporteur checking
6.2.21	CT aspects of System Support for AI/ML-based Services	AIMLsys
6.2.22	CT aspects of Personal IoT Network	PIN
6.2.23	CT aspects of enhancement of 5G UE Policy	eUEPO
Main	2284	CR 29.502 0785 Rel-18 URSP rule enforcement reports in roaming	Intel	WI eUEPO CAT F
6.2.24	CT Aspect of Architecture Enhancements for Vehicle Mounted Relays	VMR
Plenary	2246	CR 29.510 1016 Rel-18 Support of location service involving MBSR	CATT	WI VMR CAT B
Plenary	2247	CR 29.515 0182 Rel-18 Add MBSR positioning indication	CATT	WI VMR CAT B
Plenary	2248	CR 29.572 0273 Rel-18 Update the attribute definition for MBSR serving cell indication	CATT	WI VMR CAT F
6.2.25	CT aspects on 5G AM Policy	AMP
6.2.26	Architecture Enhancements for XR and media services	XRM
Main	2042	CR 29.518 1075 Rel-18 Support for the XR Device with 2Rx	Huawei	WI XRM CAT B
Main	2082	CR 29.502 0778 Rel-18 Presence Condition of MDBV	ZTE	WI XRM CAT F Overlapping with 2154
Main	2154	CR 29.502 0783 Rel-18 Condition on Maximum Data Burst Volume	Huawei	WI XRM CAT F
Main	2124	CR 29.571 0555 Rel-18 Granularity of PduSetQosParaRm	Ericsson	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	2017	CR 23.632 0045 Rel-18 Interworking with IMS clarification	Nokia	WI TEI18 CAT F
Plenary	2018	CR 23.632 0046 Rel-18 UE context data synchronization	Nokia	WI TEI18 CAT F
Plenary	2019	CR 29.272 0852 Rel-18 UE context data synchronization	Nokia	WI TEI18 CAT F
Plenary	2024	CR 29.510 0997 Rel-18 Clarifying the self-references and editorial corrections	Huawei	WI TEI18 CAT F
Main	2025	CR 29.518 1072 Rel-18 Service name corrections	Huawei	WI TEI18 CAT F
Plenary	2026	CR 29.503 1260 Rel-18 Clarifying the self-references and editorial corrections	Huawei	WI TEI18 CAT F
Plenary	2027	CR 29.556 0039 Rel-18 Clarifying the self-references and editorial corrections	Huawei	WI TEI18 CAT F
Plenary	2028	CR 29.509 0219 Rel-18 Clarifying the self-references and editorial corrections	Huawei	WI TEI18 CAT F
Plenary	2029	CR 29.559 0040 Rel-18 Clarifying the self-references	Huawei	WI TEI18 CAT F
Plenary	2030	CR 29.598 0076 Rel-18 Clarifying the self-references and editorial corrections	Huawei	WI TEI18 CAT F
Main	2032	CR 29.518 1073 Rel-18 Resolving the case of incorrect UE identifiers in the body of Location service	Huawei	WI TEI18 CAT F
Main	2033	CR 29.518 1074 Rel-18 Correction of feature negotiation description	Huawei	WI TEI18 CAT F
Main	2034	CR 29.511 0060 Rel-18 Correction of feature negotiation description	Huawei	WI TEI18 CAT F
Main	2035	CR 29.540 0117 Rel-18 Correction of feature negotiation description	Huawei	WI TEI18 CAT F
Main	2036	CR 29.244 0854 Rel-18 Clarification on Downlink data delivery status feature	Ericsson	WI TEI18 CAT F
Main	2039	CR 29.244 0856 Rel-18 Clarification on the usage of TERMR	Ericsson	WI TEI18 CAT F
Plenary	2044	CR 29.510 1000 Rel-18 Missing description in the API	Huawei	WI TEI18 CAT F
Main	2069	CR 29.274 2107 Rel-18 Clarification on the PGW Restart Notification Acknowledge message	Ericsson, Nokia	WI RPCPSET, TEI18 CAT F
Main	2070	CR 29.502 0776 Rel-18 Inclusion of S-NSSAI for Serving PLMN for V-SMF insertion and inter PLMN change	Ericsson	WI TEI18 CAT F
Main	2071	CR 29.502 0777 Rel-18 Clarification on inter AMF change with a User Plane connection establishment	Ericsson	WI TEI18 CAT F
2073	CR 29.553 0032 Rel-18 Non-Standard API Version Specification in Server URL	Orange	Moved to 7.3.1	WI TEI18 CAT A
2075	CR 29.505 0505 Rel-18 Naming mismatch in the OpenAPI specification	Orange, Nokia	Moved to 7.3.1	WI TEI18 CAT A
Plenary	2078	CR 23.007 0395 Rel-18 PGW Restart Notification and Acknowledgement	Ericsson, Nokia	WI RPCPSET, TEI18 CAT F
Plenary	2083	CR 29.518 1047 Rel-18 Add EMM Registration Status in UE Context	ZTE	WI TEI18, 5GS_Ph1-CT CAT F
2084	CR 29.503 1261 Rel-18 Clarification on Dual Registration Flag Setting	ZTE	revised to C4-242243	Revision of C4-242243 WI TEI18, 5GS_Ph1-CT CAT F
Plenary	2243	CR 29.503 1261 Rel-18 Clarification on Dual Registration Flag Setting	ZTE	WI 5GS_Ph1-CT, TEI18 CAT F Overlapping with 2257
Plenary	2256	discussion Rel-18 Discussion on canceling MME registration after EPC to 5GC mobility	Nokia
Plenary	2257	CR 29.503 1268 Rel-18 Cancel MME registration after EPC to 5GC mobility	Nokia	WI TEI18, 5GS_Ph1-CT CAT F
Main	2113	CR 29.518 1083 Rel-18 Write-Replace Warning Indication & Stop Warning Indication	Nokia	WI TEI18 CAT F
Plenary	2114	CR 29.274 2109 Rel-18 QoS change upon Inter-PLMN mobililty	Nokia	WI TEI18 CAT F
Main	2115	CR 29.518 1084 Rel-18 EBI allocation applying to PDU sessions using SSC mode 1	Nokia	WI TEI18, 5GS_Ph1-CT CAT F
Main	2155	CR 29.244 0859 Rel-18 Correction on Ethernet Packet Filter	Huawei	WI TEI18 CAT F
Main	2156	CR 29.244 0860 Rel-18 Interface Type for 5G VN Internal	Huawei	WI TEI18 CAT F
Main	2157	CR 29.502 0784 Rel-18 Feature negotiation correction	Huawei	WI TEI18 CAT F
Breakout	2158	CR 29.509 0220 Rel-18 Feature negotiation correction	Huawei	WI TEI18 CAT F
Main	2159	CR 29.531 0203 Rel-18 Feature negotiation correction	Huawei	WI TEI18 CAT F
Main	2160	CR 29.573 0194 Rel-18 Feature negotiation correction	Huawei	WI TEI18 CAT F
Main	2161	CR 29.673 0059 Rel-18 Feature negotiation correction	Huawei	WI TEI18 CAT F
Main	2162	CR 29.573 0195 Rel-18 Replacing Roaming Intermediary with RI	Huawei	Moved to 6.3.2	WI TEI18 CAT F
Main	2163	CR 29.536 0129 Rel-18 Miscellaneous corrections	Huawei	WI TEI18 CAT F
Plenary	2164	CR 29.573 0196 Rel-18 Description of N32Purpose, ProblemDetailsMsgForwarding and AdditionInfoMsgForwarding	Huawei	WI TEI18 CAT F
Plenary	2188	CR 29.573 0197 Rel-18 N32-c and N32-f Correlation	Ericsson	WI TEI18 CAT F Overlapping with 2228, 2263, 2283
Plenary	2228	CR 29.573 0200 Rel-18 Update TLS message forwarding to Peer SEPP for N32-f_N32_c correlation	China Mobile	WI TEI18 CAT F
Plenary	2263	CR 29.573 0168 Rel-18 N32-f N32-c correlation	Nokia, Verizon, Vodafone	WI TEI18 CAT F
Plenary	2283	CR 29.573 0193 Rel-18 Correlation of N32-f connection with N32-c connection for TLS security mode	Mavenir	WI TEI18 CAT F
Plenary	2264	LS out Rel-18 Reply LS on N32-f N32-c correlation	Nokia	C4-241016 To: GSMA 5GMRR CC: SA3
Breakout	2201	CR 29.503 1250 Rel-18 Style Corrections of Nudm_SDM API	Huawei	WI TEI18 CAT F
Breakout	2213	CR 29.503 1265 Rel-18 Update on font color	Huawei	WI TEI18 CAT F
Breakout	2214	CR 29.509 0221 Rel-18 Update on incorrect attribute name	Huawei	WI TEI18 CAT F
Breakout	2215	CR 29.515 0178 Rel-18 Add missing condition for conditional parameters	Huawei	WI TEI18 CAT F
Breakout	2216	CR 29.515 0179 Rel-18 Add missing description in the API	Huawei	WI TEI18 CAT F
Breakout	2217	CR 29.515 0180 Rel-18 Updates on naming convention for enumeration	Huawei	WI TEI18 CAT F
Main	2218	CR 29.518 1088 Rel-18 Updates on naming convention for enumeration	Huawei	WI TEI18 CAT F
Breakout	2219	CR 29.541 0040 Rel-18 Style and externalDocs Corrections of Nnef API	Huawei	WI TEI18 CAT F
Breakout	2220	CR 29.555 0024 Rel-18 Style Corrections of N5g-ddnmf_Discovery API	Huawei	WI TEI18 CAT F
Breakout	2221	CR 29.559 0041 Rel-18 Add missing description in the API	Huawei	WI TEI18 CAT F
Breakout	2222	CR 29.572 0268 Rel-18 Add missing condition for conditional parameters	Huawei	WI TEI18 CAT F
Breakout	2223	CR 29.572 0269 Rel-18 Feature negotiation correction	Huawei	WI TEI18 CAT F
Breakout	2224	CR 29.572 0270 Rel-18 Update on reference number	Huawei	WI TEI18 CAT F
Breakout	2225	CR 29.572 0271 Rel-18 Updates on naming convention for enumeration	Huawei	WI TEI18 CAT F
Breakout	2226	CR 29.577 0018 Rel-18 Style Corrections of Nipsmgw and Nrouter API	Huawei	WI TEI18 CAT F
Breakout	2227	CR 29.579 0019 Rel-18 Correct the description of externalDocs	Huawei	WI TEI18 CAT F
Breakout	2233	CR 29.503 1266 Rel-18 Clarification of SOR information in parameter provisioning data type	Ericsson	WI TEI18, eNPN_Ph2 CAT F
Breakout	2234	CR 29.503 1267 Rel-18 Modification of CP-SOR (SOR-SNPN-SI) Information for SNPNs	Ericsson	WI TEI18, eNPN_Ph2 CAT F
Plenary	2258	CR 29.500 0434 Rel-18 Error code on 3gpp-Sbi-Originating-Network-Id mismatch	Nokia	WI TEI18 CAT F
Plenary	2259	CR 29.510 1017 Rel-18 Alignment of NWDAF discovery parameters	Nokia	Merged with C4-242319	WI TEI18, eNA_Ph2 CAT F
2261	CR 29.573 0201 Rel-18 Correct the NfServiceSetId description	Nokia	withdrawn	WI TEI18 CAT F
Plenary	2262	CR 29.573 0202 Rel-18 Correct table references	Nokia	WI TEI18 CAT F
Plenary	2265	CR 29.500 0435 Rel-18 Align the default N32 purpose	Nokia	WI TEI18 CAT F
Plenary	2270	CR 29.571 0563 Rel-18 Correct the NfServiceSetId description	Nokia	WI TEI18 CAT F
6.3.2	Roaming5G	Roaming5G, TEI18
2123	CR 29.573 0193 Rel-18 Correlation of N32-f connection with N32-c connection for TLS security mode	Mavenir	revised to C4-242283	WI Roaming5G CAT F
Plenary	2162	CR 29.573 0195 Rel-18 Replacing Roaming Intermediary with RI	Huawei	WI Roaming5G, TEI18 CAT F
Plenary	2254	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
2264	LS out Rel-18 Reply LS on N32-f N32-c correlation	Nokia	Moved to 6.3.1	C4-241016 To: GSMA 5GMRR CC: SA3
2283	CR 29.573 0193 Rel-18 Correlation of N32-f connection with N32-c connection for TLS security mode	Mavenir	Moved to 6.3.1	WI Roaming5G CAT F
6.3.3	AoB of Rel-18
Breakout	2229	CR 29.504 0270 Rel-18 Feature support	Ericsson	Moved to 6.2.20	WI Ranging_SL, AIMLsys CAT F
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.256 0 Rel18 API version and External doc update	Qualcomm Incorporated	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
Plenary	2129	CR 29.518 1068 Rel-17 Content of JSON Patch requests	Ericsson	WI SBIProtoc17 CAT F
Plenary	2130	CR 29.518 1069 Rel-18 Content of JSON Patch requests	Ericsson	WI SBIProtoc17 CAT A
Plenary	2132	CR 29.510 1010 Rel-17 Corrections to SubscrCond data structure	Ericsson	WI SBIProtoc17 CAT F
Plenary	2133	CR 29.510 1011 Rel-18 Corrections to SubscrCond data structure	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
Plenary	2085	CR 29.510 1002 Rel-17 Add a reference of NsacSai	ZTE	WI eNS_Ph2 CAT F FASMO justified?
Plenary	2086	CR 29.510 1003 Rel-18 Add a reference of NsacSai	ZTE	WI eNS_Ph2 CAT A
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
Plenary	2119	CR 23.007 0396 Rel-17 IEs in Create Session Request/Response during the restoration of a PDN connection after a PGW-C/SMF change	Nokia, Ericsson	WI RPCPSET CAT F
Plenary	2120	CR 23.007 0397 Rel-18 IEs in Create Session Request/Response during the restoration of a PDN connection after a PGW-C/SMF change	Nokia, Ericsson	WI RPCPSET CAT A
Plenary	2121	CR 29.274 2110 Rel-17 IEs in Create Session Request/Response during the restoration of a PDN connection after a PGW-C/SMF change	Nokia, Ericsson	WI RPCPSET CAT F
Plenary	2122	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, Ericsson	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
Main	2037	CR 29.518 1059 Rel-18 Integrity Result	Ericsson	WI 5G_eLCS_ph2 CAT A Revision of CR agreed on CT4#122. Rel-17 version is correct.
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
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
Plenary	2249	CR 29.256 0023 Rel-17 Correction on the policy parameters	CATT	WI ID_UAS CAT F
Plenary	2250	CR 29.256 0024 Rel-18 Correction on the policy parameters	CATT	WI ID_UAS CAT A
Plenary	2251	CR 29.256 0025 Rel-17 Correction on the source of Notification URI	CATT	WI ID_UAS CAT F
Plenary	2252	CR 29.256 0026 Rel-18 Correction on the source of Notification URI	CATT	WI ID_UAS CAT A
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
Main	2165	CR 29.531 0204 Rel-17 NWDAF as consumer of NSSF service	Huawei	WI eNA_Ph2 CAT F
Main	2166	CR 29.531 0205 Rel-18 NWDAF as consumer of NSSF service	Huawei	WI eNA_Ph2 CAT A
7.2.14	System enhancement for redundant PDU session	TEI17_SE_RPS
7.2.15	CT Aspects ofMinimisation of service Interruption	MINT
7.2.16	CT aspects of Architecture Enhancement for NR Reduced Capability Devices	ARCH_NR_REDCAP
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
Plenary	2072	CR 29.553 0031 Rel-17 Non-Standard API Version Specification in Server URL	Orange	WI TEI17 CAT F
Plenary	2073	CR 29.553 0032 Rel-18 Non-Standard API Version Specification in Server URL	Orange	WI TEI17 CAT A
Plenary	2074	CR 29.505 0504 Rel-17 Naming mismatch in the OpenAPI specification	Orange, Nokia	WI TEI17 CAT F
Plenary	2075	CR 29.505 0505 Rel-18 Naming mismatch in the OpenAPI specification	Orange, Nokia	WI TEI17 CAT A
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
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
Plenary	2126	CR 29.598 0077 Rel-16 Corrections to OpenAPI	Ericsson	WI NUDSF CAT F
Plenary	2127	CR 29.598 0078 Rel-17 Corrections to OpenAPI	Ericsson	WI TEI17, NUDSF CAT F
Plenary	2128	CR 29.598 0079 Rel-18 Corrections to OpenAPI	Ericsson	WI TEI17, NUDSF CAT A
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
8.3	AoB for Rel-16 and earlier	TEI16, TEI15, TEI14, …..
8.3.1	TEI16, TEI15…	TEI16, TEI15, TEI14, ….
Plenary	2167	CR 29.531 0206 Rel-16 SMF as consumer of NSSF	Huawei	WI TEI16 CAT F
Plenary	2168	CR 29.531 0207 Rel-17 SMF as consumer of NSSF	Huawei	WI TEI16 CAT A
Plenary	2169	CR 29.531 0208 Rel-18 SMF as consumer of NSSF	Huawei	WI TEI16 CAT A
8.3.2	AoB of Rel-16 and earlier
8.3.3	Open API version and External docs	TEI16, TEI15
29.518 0 Rel16 API version and External doc update	Ericsson	Email approval	CR possibly needed Email approval
29.531 0 Rel16 API version and External doc update	Huawei	Email approval	CR possibly needed Email approval
29.572 0 Rel16 API version and External doc update	Ericsson	Email approval	CR possibly needed Email approval
29.598 0 Rel16 API version and External doc update	CISCO	Email approval	CR possibly needed Email approval
29.673 0 Rel16 API version and External doc update	Ericsson	Email approval	CR possibly needed Email approval
29.572 0 Rel15 API version and External doc update	Ericsson	Email approval	CR possibly needed Email approval
9	Update of the Work Plan
2010	Work Plan Work Plan	CT4 Chair
10	AoB
10.1	Rel-19 Related Discussions
Plenary	2199	discussion Rel-19 Enhancements for using multiple SEPPs in a PLMN	NTT DOCOMO
Plenary	2241	CR 29.501 0156 Rel-19 Usage of GitLab Repository	Ericsson	WI TEI19 CAT B
Plenary	2287	discussion Rel-19 Status of Rel-19 Multi-Access (DualSteer and ATSSS_Ph4) Work in SA2	Apple
10.2	AoB
11	Future meetings
12	Check of Approved Output Documents
2011	other Output Documents	CT4 Chair
13	Closing of the Meeting (16:00 Local time Friday)