0% found this document useful (0 votes)

43 views680 pages

S2-2504485 S2-168 Draft Report v006 RM

The draft report for the S2 meeting #S2-168, held from April 7-11, 2025, in Goteborg, Sweden, outlines discussions and decisions made regarding various aspects of 3GPP standards, including maintenance for different releases and enhancements for 5G technologies. Key topics include inclusive language, network automation, support for IoT, and architectural enhancements for advanced services. The document serves as a comprehensive record of the meeting's agenda and outcomes, pending approval.

Uploaded by

ushha2

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as DOCX, PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

43 views680 pages

S2-2504485 S2-168 Draft Report v006 RM

Uploaded by

ushha2

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as DOCX, PDF, TXT or read online on Scribd

You are on page 1/ 680

Report of meeting S2-168

SA WG2 Meeting #169 S2-2504485

19 - 23 May, 2025, Fukuoka, Japan

S2 Meeting #S2-168 DRAFT REPORT

Delegates are asked to take note that they are thereby invited:

- to investigate whether their organization or any other organization owns IPRs which were, or were
likely to become Essential in respect of the work of 3GPP.

- to notify their respective Organizational Partners of all potential IPRs, e.g., for ETSI, by means of the
IPR Information Statement and the Licensing declaration forms.

Antitrust policy Reminder:

I also draw your attention to the fact that 3GPP activities are subject to all applicable antitrust and
competition laws and that compliance with said laws is therefore required of any participant of this
TSG/WG/SWG meeting including the Chair and Vice Chairs. In case of question I recommend that you
contact your legal counsel.

The leadership shall conduct the present meeting with impartiality and in the interests of 3GPP.

Furthermore, I would like to remind you that timely submission of work items in advance of TSG/WG/SWG
meetings is important to allow for full and fair consideration of such matters.

3GPP
Report of meeting S2-168

1.1 Opening of the meeting

The SA WG2 Chair, Andy Bennett (Samsung) opened the meeting.

The SA WG2 Chair welcomed delegates to the meeting in Goteborg, Sweden. The Secretary and Vice
Chairs introduced themselves. The Vice Chairs were Dario Serafino Tonesi (Qualcomm) and Wanqiang
Zhang (Huawei). The Secretary was Maurice Pope (ETSI MCC).

Mr. Stefan Rommer (Ericsson) welcomed delegates on behalf of the Hosts and provided information about
Goteborg and local amenities and sites of interest. Domestic information about the meeting were also
provided in the slides.

The SA WG2 Chair then read the IPR Call and Antitrust reminder shown above.

2 Agenda
S2-2502789 (AGENDA) SA2#168 meeting Agenda (Source: SA WG2 Chair)
Document for: Approval
Abstract:
The meeting agenda.
Plenary Discussion:

The agenda was reviewed and approved.

Status: Approved.

S2-2502790 (AGENDA) SA WG2#168 meeting schedule (Source: SA WG2 Chair)

Document for: Information
Abstract:
Meeting schedule.
Plenary Discussion:

The session plan was provided in the local drafts area and will be updated throughout the meeting with the
timing and room allocation for the topics as they progress. The starting version was rev15. This was
endorsed and the final version will be uploaded at the end of the meeting. This was revised, to contain the
final version, to S2-2504482.

This was noted.

Status: Noted.

S2-2503115 (AGENDA) Plan for the meeting (Source: SA WG2 Chair)

Document for: Endorsement
Abstract:
Plenary Discussion:

The meeting planning was reviewed and endorsed.

Status: Endorsed.

2.1 IPR Call and Antitrust Reminder

The SA WG2 Chair read out the IPR and Anti-trust Reminders as shown above.

3GPP
Report of meeting S2-168

3 SA2#167 Meeting report

S2-2502791 (REPORT) Draft Report of SA WG2 meeting #167 (Source: SA WG2 Secretary)
Document for: Approval
Abstract:
Draft Report of SA WG2 meeting #167 for approval.
Plenary Discussion:

The report was reviewed and approved. This will be updated to accept revision marks and uploaded to the
FTP server as version 1.0.0.

Status: Approved.

4 General
4.1 Common issues and Incoming LSs

Status: Noted.

Inclusion of NTN intended service area in the Service Announcement

S2-2502823 (LS IN) LS from RAN WG2: Inclusion of NTN intended service area in the Service
Announcement (Source: RAN WG2 (R2-2501583))
Document for: Information
Abstract:
RAN WG2 is working on a solution to provide UEs with geographical information of where within an NTN cell
an MBS broadcast service is applicable. This area is called the 'intended service area' (ISA) whose
geographical definition is provided to the UE via SIB and is associated with an identifier (ISA ID). The
attached CR includes the changes introduced by SA WG2 to adopt the ISA for NTN access. RAN WG2
would like to ask whether including the ISA in the Service Announcement would impact in SA WG4
specifications and would kindly request SA WG4 to confirm this can be supported within the Rel-19
timeframe.
Comment: Response drafted in S2-2502898.

Plenary Discussion:

The proposed reply was reviewed. No response was considered necessary and this was noted.

Status: Noted.

S2-2502898 (LS OUT) [DRAFT] Reply LS on Inclusion of NTN intended service area in the Service
Announcement (Source: Nokia)
Document for: Approval
Abstract:
To: SA WG4. CC: SA WG2.
Comment: Response to S2-2502823.

Plenary Discussion:

Qualcomm suggested postponing this. Ericsson did not think there was a need for a response. LGE agreed
with Ericsson and Qualcomm and suggested postponing the LS. OPPO supported Nokia in informing SA
WG4 on this topic. Huawei considered that SA WG4 already have sufficient information on this. This LS was
then noted.

Status: Noted.

3GPP
Report of meeting S2-168

ETSI NFV group report on architectural support for NFV evolution

S2-2502848 (LS IN) LS from ETSI ISG NFV: Publication of ETSI NFV group report on architectural support
for NFV evolution (Source: ETSI ISG NFV (NFV(25)000019r2))
Document for: Action
Abstract:
The ETSI ISG NFV would like to inform 3GPP that ETSI GR NFV-IFA 054 (Release 6 group report on
architectural support for NFV evolution) has been published. The publication of ETSI GR NFV-IFA 054
(v6.1.1) is available at the following location:
https://www.etsi.org/deliver/etsi_gr/NFV-IFA/001_099/054/06.01.01_60/gr_nfv-ifa054v060101p.pdf {. . .}
Actions: ETSI ISG NFV kindly requests your organization to - Take the above information into account when
proceeding future architecture of mobile communication network in the timeline of 3GPP Release 20; -
Provide feedback to the published ETSI GR NFV-IFA 054 document; - Furthermore, consider to arrange joint
workshop during NFV#50 meeting for exchanging information and views on future mobile communication
network and telco cloud.
Plenary Discussion:

This LS was reviewed and noted.

Status: Noted.

Next Generation eCall

S2-2502798 (LS IN) LS from CEN TC 278 WG 15: LS on Next Generation eCall (Source: CEN TC 278 WG
15 (3GPP_LS_reply_2025-02-05))
Document for: Action
Abstract:
CEN/TC 278/WG 15 would like to thank SA WG1, SA WG2, CT WG1, TSG SA, TSG CT and ETSI TC MSG
for the received replies to the CEN LS on Next Generation eCall. We noticed the rapid progress of the work
by SA WG1, SA WG2, CT WG1, TSG SA and TSG CT in relation to the LS from CEN on Next Generation
eCall. The CEN LS on Next Generation eCall contained in total 9 cases. It seems as if currently only the
cases 1 to 5 have been considered by 3GPP for the alignment of affected 3GPP specifications. Is the
alignment of the cases 6 to 9 also foreseen in 3GPP Release 19? CEN considers these cases as a
worthwhile improvement and would appreciate if 3GPP would check feasibility of implementing them. Action:
SA WG1, SA WG2, CT WG1 , TSG SA and TSG CT are kindly asked to also take into consideration the
cases 6 to 9 from the initial CEN LS on Next Generation eCall in 3GPP Release 19.
Comment: Revision of S2-2501381.

Plenary Discussion:

Qualcomm suggested that this be either noted or postponed until the CT WG1 work progress is known. This
LS was then postponed.

Status: Postponed.

3GPP
Report of meeting S2-168

OSAppID usage by AppToken use case

S2-2502797 (LS IN) LS from GSMA TSGNS: OSAppID usage by AppToken use case (Source: GSMA
TSGNS (TSGNS44_003v6))
Document for: Information
Abstract:
GSMA TSGNS is a working group of GSMA in charge of maintaining PRD TS.62 'UE requirements related to
Network Slicing using URSP'. PRD TS.62 provides requirements to the mobile industry on the design,
development, and implementation of network slicing using URSP in 5G UEs. In the context of the wider
activity on network slicing, GSMA recently approved the specification of the App Token. App Token was
introduced in PRD TS.43 'Service Entitlement' which defines the MNOs Entitlement Server procedures. An
Entitlement Server builds the interface between an MNO and a devices OS, and is used globally for e.g.,
eSIM activation, VoLTE/VoWiFi configuration, DataPlan Info, and more configuration data. A device is
expected to interact with its home MNO's Entitlement Server, also when roaming or in wifi, using HTTP
REST. The App Token is a piece of information that the UE OS can obtain from specific applications and
allows to uniquely identify an application across the complete ecosystem (application developer, MNO,
subscriber UE) whilst protecting the end user privacy. This means that the UE OS does not need to use the
information it has about the identity of an application when comparing against the OSAppID field from the
URSP rules received from the MNO, but to use an anonymous identifier received from the MNO through
TS.43 interface for that comparison. GSMA TSGNS is currently working to define in TS.62 how UE OS
should behave when managing App Tokens with applications. The proposed end-to-end flow is as follows
(boxes in green reflects standard procedures already defined by 3GPP or by GSMA in TS.43, red box is the
CR to TS.62 being discussed in GSMA TSGNS): {. . .}.
Comment: Revision of S2-2501377. Responses drafted in S2-2502926, S2-2503081, S2-2503424, S2-
2503617, S2-2503747, S2-2503855.

Plenary Discussion:

The related discussion papers and response proposals were reviewed. An LS to TSG SA for a consolidated
response to GSMA was agreed in S2-2504468. This was then noted.

Status: Noted.

S2-2502927 (DISCUSSION) Discussion paper on GSMA TSGNS AppToken use case. (Source: Telefonica
S.A., Verizon, Deutsche Telekom, KDDI, Ericsson, Nokia)
Document for: Discussion
Abstract:
The paper provides clarifications about various questions raised related to the AppToken functionality of
GSMA TSGNS group.
Plenary Discussion:

Telefonica reported that Orange and China Mobile had also indicated their support for this contribution.
Google agreed with the general response to Q1 but suggested reducing the amount of detail. ZTE
commented that there had been concerns in using the URSP token mechanism due to User privacy issues.
Apple also had reservations on how the uniqueness of the OS App ID can be guaranteed without creating a
new mechanism to do this. The related LS was used as a basis for the reply and this was then noted.

Status: Noted.

3GPP
Report of meeting S2-168

S2-2502926 (LS OUT) [DRAFT] Reply LS on OSAppID usage by AppToken use case (Source: Telefonica
Germany GmbH)
Document for: Approval
Abstract:
Reply LS on OSAppID usage by AppToken use case.
Comment: Response to S2-2502797.

Plenary Discussion:

This was taken as a basis for update and was left for off-line discussion and revised, merging S2-2503424,
S2-2503617, S2-2503747 and S2-2503855, to S2-2504094.

Some issues were raised. The SA WG2 Chair asked for some compromise to be reached to provide the
necessary feedback to progress the work. This was left for off-line discussion and revised to S2-2504393.

Parallel Discussion:

Status: Merged.

3GPP
Report of meeting S2-168

S2-2503747 (LS OUT) [DRAFT] Reply LS on OSAppID usage by AppToken use case (Source: Samsung)
Document for: Approval
Abstract:
To: SA. CC: SA WG3.
Comment: Response to S2-2502797.

Plenary Discussion:

Merged into S2-2504094.

Status: Merged.

S2-2503855 (LS OUT) [DRAFT] Reply LS on OSAppID usage by AppToken use case (Source: Google
Korea LLC)
Document for: Approval
Abstract:
To: SA. CC: SA WG3.
Comment: Response to S2-2502797.

Plenary Discussion:

Merged into S2-2504094.

Status: Merged.

Generation of AF specific UE ID

S2-2502845 (LS IN) LS from SA WG6: LS on Generation of AF specific UE ID (Source: SA WG6 (S6-
250286))
Document for: Action
Abstract:
As part of the EDGEAPP work item, SA WG6 in 23.558 clause 8.6.5 defined the 'UE Identifier API' which
resulted in having SA WG2 specify NEF's 'AF specific UE ID retrieval' procedure in 23.502 clause 4.15.10
(and associated Nnef_UEId_Get operation). SA WG6 have noted that Step 10 of the 'AF specific UE ID
retrieval' procedure doesn't specify the case where UDM may not be able to find the AF specific UE ID in the
subscriber's record. '10. The UDM responds to the NEF with an AF specific UE Identifier represented as an
External Identifier for the UE which is uniquely associated with the Application Port ID, MTC Provider
Information or AF Identifier.' On the other hand, stage 3 in 29.522 clause 4.4.32.2 'Retrieve AF specific UE
ID service operation' states that UDM would reply to NEF with a '404 Not Found' error status code if AF
specific UE ID is not available (see related paragraph from clause 4.4.32.2 copy/pasted below): 'If the UDM
indicates that the requested UE Identifier is not available in the subscription data, the NEF shall respond to
the AF with a '404 Not Found' error status code.' Based on this observation, SA WG6 asks SA WG2 to
provide insight into the assignment of the AF specific UE ID, for instance whether support is provided for its
dynamic generation in scenarios in which the UDM is unable to find it. Action: SA WG6 asks SA WG2 to
kindly provide insight into the assignment of AF Specific UE IDs.
Comment: Responses drafted in S2-2502871, S2-2502924, S2-2502951, S2-2503091, S2-2503620.

Plenary Discussion:

The related discussion documents and proposed replies were reviewed.

Final response in S2-2504396.

Status: Replied to.

3GPP
Report of meeting S2-168

S2-2502870 (DISCUSSION) Generation of AF specific UE Identifier . (Source: Apple)

Document for: Discussion
Abstract:
This discussion paper analyzes the generation of AF Specific UE identifier in 5GC.
Plenary Discussion:

This was noted.

Status: Noted.

S2-2502871 (LS OUT) [DRAFT] Reply LS on generation of AF specific UE ID (Source: Apple)

Document for: Approval
Abstract:
To: SA WG6. CC: CT WG3.
Comment: Response to S2-2502845.

Plenary Discussion:

This was taken as a basis for reply and left for off-line discussion and revised, merging S2-2502924, S2-
2503091, S2-2503620 and S2-2502951, to S2-2504095.

Parallel discussion:

The AF specific UE ID should be 'stored' rather than 'defined'. This was revised, also to remove draft and
clean up revisions, to S2-2504396.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2502924 (LS OUT) [DRAFT] Reply LS on generation of AF specific UE ID (Source: Samsung)

Document for: Approval
Abstract:
To: SA WG6. CC: CT WG3, CT WG4. Attachments: TBD (CR6174, CR5398).
Comment: Response to S2-2502845.

Plenary Discussion:

Merged into S2-2504095.

Status: Merged.

S2-2503091 (LS OUT) [DRAFT] LS on Generation of AF specific UE ID (Source: Nokia)

Document for: Approval
Abstract:
[draft] LS on Generation of AF specific UE ID.
Comment: Response to S2-2502845.

Plenary Discussion:

Merged into S2-2504095.

Status: Merged.

3GPP
Report of meeting S2-168

S2-2503620 (LS OUT) [DRAFT] LS Response on Generation of AF specific UE ID (Source: ZTE)

Document for: Approval
Abstract:
To: SA WG6. CC: CT WG3.
Comment: Response to S2-2502845.

Plenary Discussion:

Merged into S2-2504095.

Status: Merged.

S2-2502951 (LS OUT) [DRAFT] LS Reply on Generation of AF specific UE ID (Source: Ericsson)

Document for: Approval
Abstract:
LS Reply on Generation of AF specific UE ID.
Comment: Response to S2-2502845.

Plenary Discussion:

Merged into S2-2504095.

Status: Merged.

S2-2502953 (CR) 23.501 CR6168 (Rel-19, 'C'): Handling of AF Specific UE IDs (Source: Ericsson, AT&T,
Nokia, Deutsche Telekom, KPN, NTT DOCOMO)
Document for: Approval
Abstract:
Summary of change: It is proposed to include an alternative for UDM to generate, via implementation specific
means, an AF specific UE ID when there is no AF specific UE ID defined in UDR for the SUPI and if the
requesting AF is authorized. In this case, the UDM generates the AF specific UE ID via implementation
specific means so that it is also possible for the UDM to also translate the generated AF specific UE ID to its
corresponding SUPI. This way, only UDM business logic is impacted, and thus, the CR is proposed for the
Rel-19 of the TS as no other NF or API is impacted.
Plenary Discussion:

This was taken as a basis and left for off-line discussion and revised, merging S2-2503024, to S2-2504096.

Parallel discussion:

The cover sheet revisions should be cleaned. Huawei asked to clarify that the UE identifier is generated by
the UDM. Huawei suggested removing 'for this subscriber'. Ericsson clarified that this is received in the
existing signalling and is re-used when generating the identifier. This was revised to S2-2504394.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

3GPP
Report of meeting S2-168

S2-2503092 (CR) 23.502 CR5413 (Rel-19, 'F'): Generation of AF specific UE ID (Source: Nokia, AT&T, KPN,
NTT DOCOMO, Deutsche Telekom)
Document for: Approval
Abstract:
Summary of change: If there is no available AF specific UE Identifier matching the AF information provided
by the NEF to the UDM in step 9 of clause 4.15.10, based on the operator's policy associated with the AF,
the UDM can generate an AF specific UE Identifier, store it and provide it back to the AF.
Plenary Discussion:

This was taken as a basis and left for off-line discussion and revised, merging S2-2503025, to S2-2504097.

Parallel discussion:

Samsung and Ericsson asked to be added to the sources. The 'i' in the note should be revision marked. This
was revised to S2-2504395.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503024 (CR) 23.501 CR6174 (Rel-19, 'C'): AF specific UE ID generation (Source: Samsung)
Document for: Approval
Abstract:
Summary of change: Support generation of the AF specific UE ID.
Plenary Discussion:

Merged into S2-2504096.

Status: Merged.

S2-2503025 (CR) 23.502 CR5398 (Rel-19, 'C'): AF specific UE ID generation (Source: Samsung)
Document for: Approval
Abstract:
Summary of change: Support generation of the AF specific UE ID.
Plenary Discussion:

Merged into S2-2504097.

Status: Merged.

Optimizations to UPF event subscriptions and reporting

S2-2502849 (LS IN) LS from CT WG4: LS on Optimizations to UPF event subscriptions and reporting
(Source: CT WG4 (C4-250455))
Document for: Action
Abstract:
CT WG4 started a study on Protocol for AI Data Collection from UPF and one of the key issues is to address:
{. . .} Action: CT WG4 kindly requests SA WG2 and CT WG3 to review solutions #2, #4 and #5 and provide
their feedback.
Comment: Responses drafted in S2-2503095, S2-2503739, S2-2503769.

Plenary Discussion:

The proposed responses were reviewed.

Final response in S2-2504469.

Status: Replied to.

3GPP
Report of meeting S2-168

S2-2503095 (LS OUT) [DRAFT] LS on Optimizations to UPF event subscriptions and reporting (Source:
Nokia)
Document for: Approval
Abstract:
[draft] LS on Optimizations to UPF event subscriptions and reporting.
Comment: Response to S2-2502849.

Plenary Discussion:

This was taken as a basis and left for off-line discussion and revised, merging S2-2503739 and S2-2503769,
to S2-2504098.

Parallel discussion:

Huawei commented that CT WG1 should look at other solutions. Nokia replied that there were other
solutions evaluated in the TR so we should not tell CT WG4 to further study solutions. Huawei suggested
removing the final bullet. this was left for off-line discussion and revised to S2-2504397.

Ericsson asked to add 'and signalling' to Solution #2/#5 and remove the last half of the sentence. The last
bullet was also modified. The revisions should be cleaned up and 'draft' removed. This was revised to S2-
2504469.

This was agreed in parallel session.

Plenary Discussion:

Status: OPEN

This was then noted.

Status: Noted.

4.2 P-CRs/CRs related to use of inclusive language in 3GPP

There were no contributions to this agenda item.

3GPP
Report of meeting S2-168

5 Pre-Rel-17 Maintenance (excluding all 5G topics)

This agenda item was convened by Andy Bennett (Samsung).

5.1 3GPP Packet Access Maintenance

There were no contributions to this agenda item.

5.2 QoS and PCC Maintenance

There were no contributions to this agenda item.

5.3 Non-3GPP Access Maintenance

There were no contributions to this agenda item.

5.4 IMS and IMS-Related Maintenance

There were no contributions to this agenda item.

6 Rel-15/Rel-16 Maintenance for 5G (only related to

5GS_Ph1 Work Item)
This agenda item was convened by Andy Bennett (Samsung).

6.1 General aspects, concepts and reference models

There were no contributions to this agenda item.

6.2 Common Access Control, RM and CM functions and

procedure flows
S2-2503084 (CR) 23.502 CR5411 (Rel-16, 'C'): AMF reselection via NAS reroute based on Routing Indicator
(Source: Jio Platforms Ltd (JPL))
Document for: Approval
Abstract:
Summary of change: AMF has built-in logic that keeps a mapping of the Routing Indicator (RI) against
different AMF Sets. During the Registration Request from UE, the AMF receives the RI present in SUCI.
Based on the built-in logic, the AMF derives the specific AMF Set pertaining to the received RI. AMF reroutes
the Registration request to the destined AMF via the RAN using the NAS reroute procedure. This step comes
before the Authentication and Subscriber Profile Retrieval procedure.
Plenary Discussion:

Not handled.

Status: Not treated.

3GPP
Report of meeting S2-168

S2-2503401 (CR) 23.502 CR5440 (Rel-18, 'F'): Registration handling during the mobility from non-3GPP
access to 3GPP access (Source: Huawei, Hisilicon)
Document for: Approval
Abstract:
Summary of change: The new AMF(3GPP access) does not update the UE context at the non-3GPP AN
node. The new AMF only accept the registration at 3GPP access. The 5GS registration result indicates
whether the UE is registered to 3GPP access and/or non-3GPP access.
Parallel discussion:

Nokia suggested that this could be added as an informative note, but should not be included as normative
text. LGE suggested placing such a note in a more appropriate place. This was left for off-line discussion and
revised to S2-2504363.

ZTE raised some issues and Nokia asked for clarification on how this works. This was left for off-line
discussion and revised to S2-2504410.

Nokia suggested an improvement to the last sentence in step 18. MCC asked to replace 'per' with 'according
to'. This was revised to S2-2504472.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503402 (CR) 23.502 CR5441 (Rel-19, 'F'): Registration handling during the mobility from non-3GPP
access to 3GPP access (Source: Huawei, Hisilicon)
Document for: Approval
Abstract:
Summary of change: The new AMF(3GPP access) does not update the UE context at the non-3GPP AN
node. The registration at non-3GPP access is either kept or not accepted. The 5GS registration result
indicates whether the UE is registered to 3GPP access and/or non-3GPP access.
Parallel discussion:

Some clarifications were requested and this was left for off-line discussion and revised to S2-2504364.

This should be updated as a mirror CR and was revised, as a Cat 'A' CR, to S2-2504411.

This was revised, to align with the changes to the Rel-18 CR, to S2-2504473.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503729 (CR) 23.501 CR6253 (Rel-19, 'C'): Radio capability assignment in case of equivalent PLMNs.
(Source: NEC)
Document for: Approval
Abstract:
Summary of change: Specify that the UCMF of the selected PLMN will be chosen in case of AMF is shared
by equivalent PLMNs.
Parallel discussion:

A number of issues were raised and this was discussed and noted in parallel session.

Status: Noted.

3GPP
Report of meeting S2-168

6.3 Session management and continuity functions and flows

S2-2502983 (CR) 23.502 CR4501R1 (Rel-19, 'F'): Synchronizing status of QoS Flow(s) between H-SMF or
anchor SMF and UE (Source: Ericsson)
Document for: Approval
Abstract:
Summary of change: When PDU Session Modification Command message for QoS Flow deletion cannot
reach the UE (e.g., due to no paging response): Both V-SMF and H-SMF mark the status of one or more
QoS Flows are deleted in the 5GC but not synchronized with the UE yet. For the case without V-SMF
change, at the next UP activation, if the V-SMF has marked that the status of one or more QoS Flows are
deleted in the 5GC but not synchronized with the UE yet, the V-SMF sends 'UP activated' to H-SMF which
then initiates PDU Session Modification procedure to remove the QoS Flow(s) that are marked to be
synchronized with the UE. For cases with V-SMF change/insertion/removal, the H-SMF initiates PDU
Session Modification to handle the pending QoS Flow deletion towards the UE when the H-SMF is aware of
those procedures.
Comment: Revision of (Unhandled) S2-2310691 from SA2#159.

Parallel discussion:

Huawei raised some issues and this was left for off-line discussion and revised to S2-2504365 (withdrawn).
S2-2502983 was postponed in parallel session.

Status: Postponed.

6.4 Security related functions and flows

There were no contributions to this agenda item.

6.5 QoS concept and functionality

There were no contributions to this agenda item.

6.6 Policy and charging control

S2-2503085 (CR) 23.502 CR5412 (Rel-16, 'C'): Rel-16 CR TS 23.502 Type Allocation Code (TAC) based
AMF local configuration for establishment of UE policy association. (Source: Jio Platform Limited (JPL))
Document for: Approval
Abstract:
Summary of change: This CR proposes to define an operator policy to utilize the Type Allocation Code (TAC)
in AMF local configuration to initiate UE policy association in the absence of UE policy container indication
from UE.
Plenary Discussion:

Not handled.

Status: Not treated.

3GPP
Report of meeting S2-168

S2-2503506 (CR) 23.503 CR1541 (Rel-19, 'D'): Simplification of clause 6.2.1.2 (Source: Huawei, HiSilicon)
Document for: Approval
Abstract:
Summary of change: Removal of parameter lists for all the NFs for which an interaction with the PCF has
been defined. Extension of the references to TS 23.502 by mentioning the relevant services and procedures.
Movement of AF Application Identifier description to clause 6.1.3.6.
Parallel discussion:

This was reviewed and agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

6.7 3GPP access specific functionality and flows

There were no contributions to this agenda item.

6.8 Specific services support

There were no contributions to this agenda item.

6.9 Interworking and Migration

There were no contributions to this agenda item.

6.10 Non-3GPP access specific functionality and flows

There were no contributions to this agenda item.

6.11 Framework functions

There were no contributions to this agenda item.

7 Rel-16 Maintenance for 5G (excluding 5GS_Ph1)

This agenda item was convened by Andy Bennett (Samsung).

7.1 Architecture enhancements for 3GPP support of advanced

V2X services (eV2XARC)
There were no contributions to this agenda item.

3GPP
Report of meeting S2-168

7.2 Wireless and Wireline Convergence for the 5G system

architecture (5WWC)
There were no contributions to this agenda item.

7.3 Access Traffic Steering, Switch and Splitting support in the

5G system architecture (ATSSS)
There were no contributions to this agenda item.

7.4 Cellular IoT support and evolution for the 5G System

(5G_CIoT)
There were no contributions to this agenda item.

7.5 Enablers for Network Automation for 5G (eNA)

There were no contributions to this agenda item.

7.6 Enhancement to the 5GC Location Services (5G_eLCS)

There were no contributions to this agenda item.

7.7 5GS Enhanced support of Vertical and LAN Services

(Vertical_LAN)
S2-2503719 (DISCUSSION) Discussion on the epoch issue for 5G Residence time calculation (Source: ZTE)
Document for: Discussion
Abstract:
Discussion on the epoch issue for 5G Residence time calculation.
Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503746 (DISCUSSION) Ensuring the same epoch for timestamping for gPTP (Source: Qualcomm)
Document for: Agreement
Abstract:
Ensuring the same epoch for timestamping for gPTP.
Plenary Discussion:

Not handled.

Status: Not treated.

3GPP
Report of meeting S2-168

S2-2503720 (CR) 23.501 CR6104R1 (Rel-16, 'F'): Epoch for 5G Residence time calculation (Source: ZTE)
Document for: Approval
Abstract:
Summary of change: Clarifying epoch used by DS-TT and NW-TT for the TSi/TSe calculation.
Comment: Revision of (Postponed) S2-2501749.

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503721 (CR) 23.501 CR6105R1 (Rel-17, 'F'): Epoch for 5G Residence time calculation (Source: ZTE)
Document for: Approval
Abstract:
Summary of change: Clarifying epoch used by DS-TT and NW-TT for the TSi/TSe calculation.
Comment: Revision of (Postponed) S2-2501750.

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503722 (CR) 23.501 CR6106R1 (Rel-18, 'F'): Epoch for 5G Residence time calculation (Source: ZTE)
Document for: Approval
Abstract:
Summary of change: Clarifying epoch used by DS-TT and NW-TT for the TSi/TSe calculation.
Comment: Revision of (Postponed) S2-2501751.

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503723 (CR) 23.501 CR6107R1 (Rel-19, 'A'): Epoch for 5G Residence time calculation (Source: ZTE)
Document for: Approval
Abstract:
Rel-19 mirror CR: Summary of change: Clarifying epoch used by DS-TT and NW-TT for the TSi/TSe
calculation.
Comment: Revision of (Postponed) S2-2501752.

Plenary Discussion:

Not handled.

Status: Not treated.

3GPP
Report of meeting S2-168

S2-2503862 (CR) 23.501 CR6268 (Rel-18, 'F'): 5GS common time reference traceable to UTC (Source:
Nokia)
Document for: Approval
Abstract:
Summary of change: It is proposed that the user plane nodes are synchronized to the reference time shall
have a common reference time that is traceable to UTC.
Comment: Check Acronym. Vertical_LAN is Rel-16, IIoT is Rel-17!

Parallel discussion:

A draft v4 of this document from off-line discussions was provided in the Drafts folder:
https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_168_Goteborg_2025-04/INBOX/DRAFTS/S2-2503862-
CR%2023501%205GS%20common%20time%20reference-v4.docx

Qualcomm commented that this could be agreed at this meeting and further updated at the next meeting if
further changes are found to be needed. The new note should be removed. This was revised to S2-
2504366.

This was endorsed in parallel session for further work at the next meeting.

Status: Endorsed.

S2-2503863 (CR) 23.501 CR6269 (Rel-19, 'A'): 5GS common time reference traceable to UTC (Source:
Nokia)
Document for: Approval
Abstract:
Rel-19 mirror CR: Summary of change: It is proposed that the user plane nodes are synchronized to the
reference time shall have a common reference time that is traceable to UTC.
Comment: Check Acronym. Vertical_LAN is Rel-16, IIoT is Rel-17!

Parallel discussion:

This was revised, to align with the Rel-18 CR, to S2-2504367.

This was endorsed in parallel session for further work at the next meeting.

Status: Endorsed.

7.8 Enhancements to the Service-Based 5G System

Architecture (5G_eSBA)
There were no contributions to this agenda item.

7.9 Architecture enhancements for the support of Integrated

access and backhaul (IABARC)
There were no contributions to this agenda item.

7.10 Enhancement of URLLC supporting in 5GC (5G_URLLC)

There were no contributions to this agenda item.

7.11 Enhancement of Network Slicing (eNS)

There were no contributions to this agenda item.

3GPP
Report of meeting S2-168

7.12 Optimisations on UE radio capability signalling (RACS)

There were no contributions to this agenda item.

7.13 Enhanced IMS to 5GC Integration (eIMS5G_SBA)

S2-2503088 (CR) 23.228 CR1615 (Rel-16, 'B'): Service restoration by IMS when the UE is unresponsive but
reachable (Source: Jio Platforms Ltd (JPL))
Document for: Approval
Abstract:
Summary of change: IMS network initiated UE detach so as to restore the service experience.
Plenary Discussion:

Not handled.

Status: Not treated.

7.14 User Data Interworking and Coexistence (UDICoM)

There were no contributions to this agenda item.

7.15 Enhancing Topology of SMF and UPF in 5G Networks

(ETSUN)
There were no contributions to this agenda item.

7.16 5GS Transfer of Policies for Background Data Transfer

(xBDT)
There were no contributions to this agenda item.

7.17 Single radio voice continuity from 5GS to 3G (5G_SRVCC)

There were no contributions to this agenda item.

3GPP
Report of meeting S2-168

8 Rel-17 Maintenance
This agenda item was convened by Andy Bennett (Samsung).

8.1 Enablers for Network Automation for 5G - phase 2

(eNA_Ph2)
S2-2503350 (CR) 23.288 CR1438 (Rel-18, 'F'): Correlate the Slice Load to an AOI when location is provided
(Source: Verizon, Oracle, CATT)
Document for: Approval
Abstract:
Summary of change: Add optional spatial validity attribute to the slice load statistics and prediction.
Parallel discussion:

It was clarified that this had already been agreed and implemented into Rel-19. The WI Code should be
'TEI18, eNA_Ph2' in the database. The revision field should be filled in. This was revised to S2-2504368.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503361 (CR) 23.288 CR1439 (Rel-19, 'F'): Attribute Level Change (Source: Verizon, Oracle, CATT)
Document for: Approval
Abstract:
Summary of change: Add '>' to the spatial validity attribute.
Parallel discussion:

The WI Code should be 'TEI19, eNA_Ph2'. A space should be added after the '>'. The revision field should
be filled in. This was revised to S2-2504369.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

8.2 Enhanced support of Non-Public Networks (eNPN)

There were no contributions to this agenda item.

8.3 Enhancement of support for Edge Computing in 5GC

(eEDGE_5GC)
There were no contributions to this agenda item.

8.4 Enhancement of Network Slicing Phase 2 (eNS_Ph2)

There were no contributions to this agenda item.

3GPP
Report of meeting S2-168

8.5 Enhanced support of Industrial IoT - TSC/URLLC

enhancements (IIoT)
There were no contributions to this agenda item.

8.6 Access Traffic Steering, Switch and Splitting support in the

5G system architecture Phase 2 (ATSSS_Ph2)
There were no contributions to this agenda item.

8.7 Support of Aerial Systems Connectivity, Identification, and

Tracking (ID_UAS)
There were no contributions to this agenda item.

8.8 System enhancement for Proximity based Services in 5GS

(5G_ProSe)
There were no contributions to this agenda item.

8.9 Architectural enhancements for 5G multicast-broadcast

services (5MBS)
There were no contributions to this agenda item.

8.10 System enablers for multi-USIM devices (MUSIM)

There were no contributions to this agenda item.

3GPP
Report of meeting S2-168

8.11 Architecture aspects for using satellite access in 5G

(5GSAT_ARCH)
S2-2502803 (LS IN) LS from CT WG1: LS on stage 1 requirements for the support for PWS over satellite
NGRAN in Rel-17 (Source: CT WG1 (C1-250715))
Document for: Information
Abstract:
SA WG1 has agreed to introduce a new requirement for the support for PWS over satellite NG-RAN
(CR#0081 to TS 22.268 in S1-244777) from Rel-17. CT WG1 has discussed the stage 2 aspects of this
requirement and determined that this requirement would have UE impacts that would create backward
compatibility issues (e.g. country-specific duplicate detection timers for PLMNs using non-country specific
PLMN ID with MCC 9xx over satellite access). Consequently, CT WG1 has decided to introduce the support
for PWS over satellite NG-RAN in Rel-19. This work will be done under the new CT-wide Rel-19 work item
on the support for PWS over satellite E-UTRAN and satellite NG-RAN. CT WG1 kindly asks SA WG1 to align
their specifications accordingly.
Parallel discussion:

Qualcomm commented that there may be a need to align SA WG2 TSs with the CT WG1 TSs. This LS was
postponed in parallel session.

Status: Postponed.

8.12 Architecture enhancements for 3GPP support of advanced

V2X services - Phase 2 (eV2XARC_Ph2)
There were no contributions to this agenda item.

8.13 5G System Enhancement for Advanced Interactive Services

(5G_AIS)
There were no contributions to this agenda item.

8.14 Enhancement to the 5GC LoCation Services-Phase 2

(5G_eLCS_Ph2)
S2-2502813 (LS IN) LS from CT WG4: LS on New port number for LCS-UPP (Source: CT WG4 (C4-
250590))
Document for: Information
Abstract:
CT WG4 thanks CT WG1 for the LS on Requesting allocation of new TCP port for Location Services User
Plane Protocol (LCS-UPP). CT WG4 has taken the requirements mentioned in the LS and has agreed on the
attached CR from Release 18.
Parallel discussion:

This LS was reviewed and noted in parallel session.

Status: Noted.

8.15 Multimedia Priority Service (MPS) Phase 2 (MPS2)

There were no contributions to this agenda item.

3GPP
Report of meeting S2-168

8.16 Dynamic management of group-based event monitoring

(TEI17_GEM)
There were no contributions to this agenda item.

8.17 N7/N40 Interfaces Enhancements to Support GERAN and

UTRAN (TEI17_NIESGU)
There were no contributions to this agenda item.

8.18 System enhancement for Redundant PDU Session

(TEI17_SE_RPS)
There were no contributions to this agenda item.

8.19 IMS Optimization for HSS Group ID in an SBA environment

(TEI17_IMSGID)
There were no contributions to this agenda item.

8.20 Support for Signed Attestation for Priority and Emergency

Sessions (TEI17_SAPES)
There were no contributions to this agenda item.

8.21 Dynamically Changing AM Policies in the 5GC

(TEI17_DCAMP)
There were no contributions to this agenda item.

8.22 IP address pool information from UDM (TEI17_IPU)

There were no contributions to this agenda item.

8.23 Same PCF selection for AMF and SMF (TEI17-SPSFAS)

There were no contributions to this agenda item.

3GPP
Report of meeting S2-168

8.24 Support of different slices over different Non-3GPP access

(TEI17_N3SLICE)
There were no contributions to this agenda item.

8.25 Minimization of Service Interruption (MINT)

There were no contributions to this agenda item.

8.26 Architecture Enhancement for NR Reduced Capability

Devices (ARCH_NR_REDCAP)
There were no contributions to this agenda item.

8.27 Architecture support for NB-IoT/eMTC Non-Terrestrial

Networks in EPS (IoT_SAT_ARCH_EPS)
There were no contributions to this agenda item.

8.28 Rel-17 CAT B/C alignment CR(s) due to the work led by
other 3GPP Working Groups
There were no contributions to this agenda item.

9 Rel-18 WIDs
There were no contributions to this agenda item.

9.1.2 5G System with Satellite Backhaul (5GSATB)

There were no contributions to this agenda item.

9.2.2 Satellite access Phase 2 (5GSAT_Ph2)

There were no contributions to this agenda item.

9.3.2 Personal IoT Networks (5G_PIN)

There were no contributions to this agenda item.

3GPP
Report of meeting S2-168

9.4.2 Phase 2 for UAS, UAV and UAM (UAS_Ph2)

There were no contributions to this agenda item.

9.5.2 Ranging based services and sidelink positioning (Ranging_SL)

There were no contributions to this agenda item.

9.6.2 5GC LoCation Services Phase 3 (eLCS_Ph3)

This agenda item was convened by Wanqiang Zhang (Huawei).

Change Sequence of a Procedure

S2-2503492 (CR) 23.273 CR0717 (Rel-18, 'F'): Clarification and correction on modification of UP connection
between UE and LMF (Source: Huawei, HiSilicon)
Document for: Approval
Abstract:
Summary of change: Revise the procedure of Modification of User Plane Connection between UE and LMF
to make the connection termination logic clearer. Revise the procedure of Modification of User Plane
Connection to support interaction between the source LMF and the target LMF for UP connection relocation
negotiation, by using the Nlmf_Location_LocationContextTransfer service operation.
Nlmf_Location_LocationContextTransfer service operation updated to cover UE identifier and additionly
support inidiaction of LMF relocation for User Plane Connection.
Parallel discussion:

Revised in parallel session to S2-2504043.

Revised in parallel session to S2-2504086.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503493 (CR) 23.273 CR0718 (Rel-19, 'A'): Clarification and correction on modification of UP connection
between UE and LMF (Source: Huawei, HiSilicon)
Document for: Approval
Abstract:
Rel-19 mirror CR: Summary of change: Revise the procedure of Modification of User Plane Connection
between UE and LMF to make the connection termination logic clearer. Revise the procedure of Modification
of User Plane Connection to support interaction between the source LMF and the target LMF for UP
connection relocation negotiation, by using the Nlmf_Location_LocationContextTransfer service operation.
Nlmf_Location_LocationContextTransfer service operation updated to cover UE identifier and additionly
support inidiaction of LMF relocation for User Plane Connection.
Plenary Discussion:

Not handled.

Status: Not treated.

3GPP
Report of meeting S2-168

Number of User plane connections: One in Rel-18

S2-2503171 (DISCUSSION) Discussion on single LCS-UPP connection maintenance. (Source: OPPO)

Document for: Agreement
Abstract:
This contribution proposes questions and alternative solutions on how to maintain single LCS-UPP
connection and provides the way forward.
Comment: Noted in parallel session.

Parallel discussion:

This was noted in parallel session.

Status: Noted.

S2-2502961 (CR) 23.273 CR0703 (Rel-18, 'F'): Solving UE shall have maximum one LCS-UPP (Source:
Ericsson)
Document for: Approval
Abstract:
Summary of change: Adding UE maintains only one LCS-UPP connection Adding text that if UE receives
deferred location trigger via user plane then UE considers to use user plane for sensing event-report Adding
logic that AMF shall reject LMF inititated connection establishment if AMF user plane context for the UE has
already use plane connection Modification of User Plane Connection updated to ensure UE can have
maximom one LCS-UPP connection. AMF allows sending user plane establishment message to UE even
though UE has already LCS-UPP connection since AMF identifies that target LMF requested it. Adding that
Source LMF provides information to Target LMF about Deferred Location session was assigned to user
plane connection. Adding that step 6 in Modification of User Plane Connection is only for termination.
Parallel discussion:

Revised in parallel session to S2-2504042.

Revised in parallel session to S2-2504087.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503173 (CR) 23.273 CR0707 (Rel-18, 'F'): Update on single LCS-UPP connection maintenance
(Source: OPPO)
Document for: Approval
Abstract:
Summary of change: Update LCS-UPP related clauses to support single LCS-UPP connection maintenance.
Plenary Discussion:

Not handled.

Status: Not treated.

3GPP
Report of meeting S2-168

S2-2503726 (CR) 23.273 CR0729 (Rel-18, 'F'): Clarification on the maximum one LCS-UPP connection
restriction (Source: ZTE)
Document for: Approval
Abstract:
Summary of change: The AMF or UE rejects the LCS-UPP connection establish request if it has one LCS-
UPP connection.
Comment: Merged into S2-2504042.

Parallel discussion:

Merged.

Status: Merged.

Number of User plane connections: Multiple in Rel-19

S2-2502962 (CR) 23.273 CR0646R3 (Rel-19, 'C'): Supporting multiple LCS-UPP connections per UE
(Source: Ericsson)
Document for: Approval
Abstract:
Summary of change: Adding that UE shall support several LCS-UPP connection, each towards different
LMF. Updating UE and AMF functionality with multiple LCS-UPP support. Updating user plane modification
procedure.
Comment: Revision of (Postponed) S2-2502330.

Parallel discussion:

This was noted in parallel session.

Status: Noted.

S2-2503724 (CR) 23.273 CR0727 (Rel-18, 'F'): Correction on the Modification of User Plane Connection
between UE and LMF (Source: ZTE)
Document for: Approval
Abstract:
Summary of change: Change the step sequence. The source LMF send the source LMF address to target
LMF in the context transfer. And the target LMF sends both target LMF and source LMF address to UE in the
user plane information.
Comment: Merged into S2-2504043.

Parallel discussion:

Merged.

Status: Merged.

3GPP
Report of meeting S2-168

S2-2503725 (CR) 23.273 CR0728 (Rel-19, 'A'): Correction on the Modification of User Plane Connection
between UE and LMF (Source: ZTE)
Document for: Approval
Abstract:
Rel-19 mirror CR: Summary of change: Change the step sequence. The source LMF send the source LMF
address to target LMF in the context transfer. And the target LMF sends both target LMF and source LMF
address to UE in the user plane information.
Comment: Merged into S2-2504044.

Parallel discussion:

Merged.

Status: Merged.

9.7.2 Proximity-based Services in 5GS Phase 2 (5G_ProSe_Ph2)

There were no contributions to this agenda item.

9.8.2 Generic group management, exposure and communication

enhancements (GMEC)
There were no contributions to this agenda item.

9.9.2 System Support for AI/ML-based Services (AIMLsys)

There were no contributions to this agenda item.

9.10.2 5G multicast-broadcast services Phase 2 (5MBS_Ph2)

There were no contributions to this agenda item.

9.11.2 Network Slicing Phase 3 (eNS_Ph3)

This agenda item was convened by Andy Bennett (Samsung).

3GPP
Report of meeting S2-168

S2-2502874 (CR) 23.503 CR1526 (Rel-18, 'F'): Update network slice replacement PCRT (Source: Oracle,
Verizon)
Document for: Approval
Abstract:
Summary of change: This CR proposes to enhance the description of the PCRT such that it is clear that the
opposite direction of slice replacement is covered as well. In addition, it is made clear what info is provided
by the SMF to the PCF when slice replacement takes place in the opposite direction.
Parallel discussion:

Huawei commented that this is already documented in the paragraph below the table and suggested
generalizing the text to cover both the transfer to Alternative slice and back to the original slice. This was left
for off-line discussion and revised to S2-2504141.

This was reviewed and agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2502875 (CR) 23.503 CR1527 (Rel-19, 'A'): Update network slice replacement PCRT (Source: Oracle,
Verizon)
Document for: Approval
Abstract:
Rel-19 mirror CR: Summary of change: This CR proposes to enhance the description of the PCRT such that
it is clear that the opposite direction of slice replacement is covered as well. In addition, it is made clear what
info is provided by the SMF to the PCF when slice replacement takes place in the opposite direction.
Parallel discussion:

This was left for off-line discussion to align with the Rel-18 CR and revised to S2-2504142.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

Configured NSSAI

S2-2502889 (CR) 23.501 CR6018R2 (Rel-18, 'F'): Clarification on the removal of S-NSSAI from the
Configured NSSAI (Source: Nokia, ZTE)
Document for: Approval
Abstract:
Summary of change: Change the standard to instead use the rejected S-NSSAI. This keeps being rejected
until the S-NSSAI can be used again.
Comment: Revision of (Postponed) S2-2501937.

Parallel discussion:

This was reviewed and left for off-line discussion. Samsung suggested discussing this with the LGE CR
proposal. Nokia commented that the LGE CR is on a different area. LGE commented that a similar approach
should be adopted also for their proposal. LGE objected to this as the current approach is more efficient.
Nokia commented that the current solution does not work. This was left for further off-line discussion and
was revised to S2-2504401.

LGE objected to this CR and it was noted in parallel session.

3GPP
Report of meeting S2-168

LGE statement for their objection:

LGE object to this CR. The issue raised in the CR can be resolved based on existing AMF behaviour e.g.
AMF can update Configured NSSAI if AMF detects that UE requests slice which is not in the Subscribed S-
NSSAIs or whenever validity condition of the slice changes. Therefore, there is no FASMO issue.

Status: Noted.

S2-2502890 (CR) 23.501 CR6019R2 (Rel-19, 'A'): Clarification on the removal of S-NSSAI from the
Configured NSSAI (Source: Nokia, ZTE)
Document for: Approval
Abstract:
Rel-19 mirror CR: Summary of change: Change the standard to instead use the rejected S-NSSAI. This
keeps being rejected until the S-NSSAI can be used again.
Comment: Revision of (Unhandled) S2-2501938.

Parallel discussion:

This was reviewed and left for off-line discussion. LGE had objected to the Rel-18 CR and this was noted in
parallel session.

Status: Noted.

S2-2503298 (CR) 23.501 CR6200 (Rel-18, 'F'): Configured NSSAI exchange between AMFs for Network
Slice Replacement (Source: LG Electronics)
Document for: Approval
Abstract:
Summary of change: Clarify that Configured NSSAI provided to the UE is exchanged between AMFs.
Parallel discussion:

Nokia commented that this was not needed as the configured NSSAI does not need a subscription. ZTE
agreed with Nokia. Huawei suggested adding a note to the Rel-19 TS. This was then noted in parallel
session.

Status: Noted.

S2-2503299 (CR) 23.501 CR6201 (Rel-19, 'A'): Configured NSSAI exchange between AMFs for Network
Slice Replacement (Source: LG Electronics)
Document for: Approval
Abstract:
Rel-19 mirror CR: Summary of change: Clarify that Configured NSSAI provided to the UE is exchanged
between AMFs.
Parallel discussion:

Nokia commented that this was not needed as the configured NSSAI does not need a subscription. ZTE
agreed with Nokia. Huawei suggested adding a note to clarify this. This was left for off-line discussion and
revised to S2-2504143.

Nokia raised concerns over cancelling the mapping without updating the configuration and suggested it is
postponed or noted. This was then postponed in parallel session.

Status: Postponed.

S2-2503300 (CR) 23.502 CR5423 (Rel-18, 'F'): Update on UE Context in AMF to support Network Slice
Replacement (Source: LG Electronics)
Document for: Approval
Abstract:
Summary of change: Add Configured NSSAI to the UE Context in the AMF.
Parallel discussion:

This was no longer needed and was noted in parallel session.

Status: Noted.

3GPP
Report of meeting S2-168

S2-2503301 (CR) 23.502 CR5424 (Rel-19, 'A'): Update on UE Context in AMF to support Network Slice
Replacement (Source: LG Electronics)
Document for: Approval
Abstract:
Rel-19 mirror CR: Summary of change: Add Configured NSSAI to the UE Context in the AMF.
Parallel discussion:

This was no longer needed and was noted in parallel session.

Status: Noted.

S2-2503664 (CR) 23.501 CR6153R1 (Rel-18, 'F'): Clarification on Configured NSSAI for temporary slice
(Source: Samsung)
Document for: Approval
Abstract:
Summary of change: AMF stores the information in UDM related to removal of S-NSSAI from Configured
NSSAI dur to validity time.
Comment: Revision of (Postponed) S2-2502125.

Parallel discussion:

This was reviewed and left for off-line discussion. This was noted in parallel session

Status: Noted.

S2-2503666 (CR) 23.501 CR6154R1 (Rel-19, 'A'): Clarification on Configured NSSAI for temporary slice
(Source: Samsung)
Document for: Approval
Abstract:
Rel-19 mirror CR: Summary of change: AMF stores the information related to removal of S-NSSAI from
Configured NSSAI dur to validity time.
Comment: Revision of (Unhandled) S2-2502126.

Parallel discussion:

This was reviewed and left for off-line discussion. This was noted in parallel session

Status: Noted.

Always on PDU Session

S2-2503821 (DISCUSSION) Discussion on always-on PDU sessions for network slices subject to area
restrictions. (Source: NTT Docomo, Nokia)
Document for: Endorsement
Abstract:
Discuss how to deal with 'always-on PDU sessions' in the network slices subject to area restrictions.
Comment: Revision of S2-2503546. Revision of (Noted) S2-2501575.

Parallel discussion:

ZTE commented that the solution in their proposed CRs (S2-2503615) was preferable. Samsung, Ericsson
and Qualcomm also preferred the ZTE approach. This was then noted in parallel session.

Status: Noted.

3GPP
Report of meeting S2-168

S2-2503615 (CR) 23.501 CR6237 (Rel-18, 'F'): Clarification on always-on PDU Session (Source: ZTE)
Document for: Approval
Abstract:
Summary of change: Clarify that the SMF shall not accept the PDU session as always-on PDU session when
the PDU session is subject to area restriction for the S-NSSAI.
Parallel discussion:

Samsung commented that additional signalling is used to indicate that there are insufficient User Plane
resources and did not see the benefit of this new mechanism. This was left for off-line discussion and revised
to S2-2504144 (withdrawn).S2-2503615 was then postponed in parallel session.

Status: Postponed.

S2-2503616 (CR) 23.501 CR6238 (Rel-19, 'A'): Clarification on always-on PDU Session (Source: ZTE)
Document for: Approval
Abstract:
Rel-19 mirror CR: Summary of change: Clarify that the SMF shall not accept the PDU session as always-on
PDU session when the PDU session is subject to area restriction for the S-NSSAI.
Parallel discussion:

This was left for off-line discussion and revised to S2-2504145 (withdrawn).S2-2503615 was then postponed
in parallel session.

Status: Postponed.

S2-2503548 (CR) 23.501 CR5987R2 (Rel-18, 'F'): Handling of always-on PDU sessions for network slices
subject to area control (Source: NTT DOCOMO, Nokia)
Document for: Approval
Abstract:
Summary of change: The Always-on PDU sessions behaviour is retained as specified in clause 5.6 of TS
23.501, but care needs to be taken to avoid deactivating the always-on PDU sessions in the NG-RAN when
a UE exists in the area of availability and support of a network slice. Hence, the NG-RAN has to be aware of
which PDU sessions of a UE are always-on. The UE is required not to send UL data when it is outside the
area of availability.
Comment: Revision of (Postponed) S2-2501577.

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503550 (CR) 23.501 CR5988R2 (Rel-19, 'A'): Handling of always-on PDU sessions for network slices
subject to area restrictions (Source: NTT DOCOMO, Nokia)
Document for: Approval
Abstract:
Rel-19 mirror CR: Summary of change: The always-on PDU sessions behaviour is retained as specified in
clause 5.6 of TS 23.501, but then care needs to be taken to avoid deactivation of the always-on PDU
sessions in the NG-RAN when a UE exists the area of availability and support of a network slice, hence the
NG-RAN has to be aware of which PDU sessions of a UE are always-on. The UE and SMF are required to
not send UL and respectively DL data when it is outside the area of availability.
Comment: Revision of (Unhandled) S2-2501578.

Plenary Discussion:

Not handled.

Status: Not treated.

3GPP
Report of meeting S2-168

S2-2503551 (CR) 23.502 CR5273R2 (Rel-18, 'F'): Handling of always-on PDU sessions for network slices
subject to area restrictions (Source: NTT DOCOMO, Nokia.)
Document for: Approval
Abstract:
Summary of change: The always-on PDU sessions behaviour is retained as specified in clause 5.6 of TS
23.501, but then care needs to be taken to avouid deactivation of the always-on PDU sessions in the NG-
RAN when a UE exists the area of availability and support of a network slice, hence the NG-RAN has to be
aware of which PDU sessions of a UE are always-on. This is achieved by this CR. Step 1a in the PDU
session modification procedure now includes the potential indication of Slice Area Restritions.
Comment: Revision of (Unhandled) S2-2501579.

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503558 (CR) 23.502 CR5274R2 (Rel-19, 'A'): Handling of always-on PDU sessions for network slices
subject to area control (Source: Nokia)
Document for: Approval
Abstract:
Rel-19 mirror CR: Summary of change: The always-on PDU sessions behaviour is retained as specified in
clause 5.6 of TS 23.501, but then care needs to be taken to avoid deactivation of the always-on PDU
sessions in the NG-RAN when a UE exists the area of availability and support of a network slice, hence the
NG-RAN has to be aware of which PDU sessions of a UE are always-on. This is achieved by this CR. Step
1a in the PDU session modification procedure now includes the potential indication of Slice Area Restritions.
Comment: Revision of (Unhandled) S2-2501580. Confirm Spec version used - CR states 19.2.0!

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503559 (CR) 23.501 CR6231 (Rel-18, 'F'): Handling of always-on PDU sessions for network slices
subject to area control- option B (Source: Nokia, NTT DOCOMO)
Document for: Approval
Abstract:
Summary of change: The Always-on PDU sessions behaviour is retained as specified in clause 5.6 of TS
23.501, but care needs to be taken to ensure that the UL data of always-an PDU session can be sent at any
time inside NS-AoS without requiring SR oif the UE is CM-CONNECTED.
Plenary Discussion:

Revised in parallel session to S2-2503992.

Plenary Discussion:

Noted.

Status: Noted.

S2-2502892 (CR) 23.501 CR6070R2 (Rel-19, 'A'): Clarifications on ECN marking for L4S (Source: Apple)
Document for: Approval
Abstract:
Rel-19 mirror CR: Summary of change: The text in clause 5.37.3.2 is modified to state that QoS Flows
enabled for ECN marking for L4S are used exclusively for carrying L4S enabled IP traffic.Also a NOTE is
added to state that ECN marking for L4S can be enabled for a QoS flow associated with default QoS rule if
only L4S traffic is mapped to that QoS flow. In 5.37.3.1, NOTE 3 is expanded to say that detection of L4S
traffic can be carried out using the usage reporting procedure between SMF and UPF.
Comment: Revision of (Postponed) S2-2501446.

Parallel discussion:

Revised in parallel session to S2-2503895.

Plenary Discussion:

Postponed.

Status: Postponed.

3GPP
Report of meeting S2-168

S2-2503513 (CR) 23.501 CR6135R1 (Rel-18, 'F'): Clarifications and corrections for ECN marking for L4S
and congestion monitoring (Source: Huawei, HiSilicon)
Document for: Approval
Abstract:
Summary of change: Removal of text about activation of ECN marking for L4S based on detection of L4S
traffic at the UPF from note 3 in clause 5.37.3.1. Removal of ECN marking for L4S related statements from
clause 5.45.3. Terminology correction and alignment with stage 3.
Comment: Revision of (Postponed) S2-2501907.

Parallel discussion:

Remove 1st change. Revised in parallel session to S2-2503993.

Plenary Discussion:

Postponed.

Status: Postponed.

S2-2503514 (CR) 23.501 CR6136R1 (Rel-19, 'A'): Clarifications and corrections for ECN marking for L4S
and congestion monitoring (Source: Huawei, HiSilicon)
Document for: Approval
Abstract:
Rel-19 mirror CR: Summary of change: Removal of text about activation of ECN marking for L4S based on
detection of L4S traffic at the UPF from note 3 in clause 5.37.3.1. Removal of ECN marking for L4S related
statements from clause 5.45.3. Terminology correction and alignment with stage 3.
Comment: Revision of (Unhandled) S2-2501908.

Parallel discussion:

Revised in parallel session to S2-2504153.

Withdrawn.

Status: Withdrawn.

S2-2503515 (CR) 23.503 CR1515R1 (Rel-18, 'F'): Clarifications and corrections for ECN marking for L4S
and congestion monitoring (Source: Huawei, HiSilicon)
Document for: Approval
Abstract:
Summary of change: The description of ECN marking for L4S is moved from clause 6.1.3.22 to 6.1.3.27.1. A
note is added to reflect their dependency, i.e. the fact that both cannot be requested/activated at the same
time for a service data flow. Removal of the option to activate ECN marking for L4S based on detection of
L4S traffic.
Comment: Revision of (Unhandled) S2-2501909.

Parallel discussion:

Revised in parallel session to S2-2504154.

Convert NOTE into normative text. Revised in parallel session to S2-2504226.

Revised in parallel session to S2-2504249.

Plenary Discussion:

This was reviewed and approved.

Status: Approved.

3GPP
Report of meeting S2-168

S2-2503516 (CR) 23.503 CR1516R1 (Rel-19, 'A'): Clarifications and corrections for ECN marking for L4S
and congestion monitoring (Source: Huawei, HiSilicon)
Document for: Approval
Abstract:
Rel-19 mirror CR: Summary of change: The description of ECN marking for L4S is moved from clause
6.1.3.22 to 6.1.3.27.1. A note is added to reflect their dependency, i.e. the fact that both cannot be
requested/activated at the same time for a service data flow. Removal of the option to activate ECN marking
for L4S based on detection of L4S traffic.
Comment: Revision of (Unhandled) S2-2501910.

Parallel discussion:

Revised in parallel session to S2-2504155.

Plenary Discussion:

This was approved.

Status: Approved.

Multi-modality services related

S2-2503507 (CR) 23.501 CR5255R7 (Rel-18, 'F'): Clarifications for multi-modal services (Source: Huawei,
HiSilicon, Nokia)
Document for: Approval
Abstract:
Summary of change: In clause 5.37.2, the Multi-modal Service Requirements information description is
clarified and a reference to 23.503 is added. Furthermore, 'data flow' related terminology is clarified and
aligned: In clause 3.1 and clause 5.37.6, 'data flow' becomes 'service data flow' as this is the granularity for
the respective control. In clause 5.37.2, a note is added to clarify the equivalence between 'data flow' and
'media flow'.
Comment: Revision of (Noted) S2-2410783.

Parallel discussion:

Revised in parallel session to S2-2503896.

Revised in parallel session to S2-2504156.

Remove note 1? Revised in parallel session to S2-2504227.

Revised in parallel session to S2-2504250.

Plenary Discussion:

The note should be reinstated as it was not moved to TS 23.503. The other specs affected should be
removed. This was revised to S2-2504480.

This was approved.

Status: Approved.

Plenary Discussion:

S2-2503510 was noted.

Status: Noted.

3GPP
Report of meeting S2-168

S2-2503585 (CR) 23.502 CR4702R7 (Rel-18, 'F'): Clarifications for multi-modal services (Source: Huawei,
HiSilicon)
Document for: Approval
Abstract:
Summary of change: In several places, the description of the Multi-modal Service Requirements information
is extended to better emphasize that existing parameters are re-used and can be provided multiple times.
Comment: Revision of (Postponed at S2#165) S2-2410784.

Parallel discussion:

Revised in parallel session to S2-2503900 (withdrawn). Noted in parallel session.

Withdrawn.

Status: Withdrawn.

S2-2503587 (CR) 23.502 CR4956R3 (Rel-19, 'A'): Clarifications for multi-modal services (Source: Huawei,
HiSilicon)
Document for: Approval
Abstract:
Rel-19 mirror CR: Summary of change: In several places, the description of the Multi-modal Service
Requirements information is extended to better emphasize that existing parameters are re-used and can be
provided multiple times.
Comment: Revision of (Withdrawn at S2#165) S2-2410329.

Parallel discussion:

Revised in parallel session to S2-2503901 (withdrawn). Noted in parallel session.

Withdrawn.

Status: Approved.

9.13.2 RedCap Phase 2 (NR_RedCAP_Ph2)

There were no contributions to this agenda item.

9.14.2 Evolution of IMS multimedia telephony service (NG_RTC)

This agenda item was convened by Dario Tonesi (Qualcomm).

S2-2502804 (LS IN) LS from CT WG1: Reply LS on request for IMS Data Channel related clarifications
(Source: CT WG1 (C1-250819))
Document for: Information
Abstract:
CT WG1 thanks SA WG3-LI for the LS on request for IMS Data Channel related clarifications. CT WG1
would like to reply to the questions in the LS as below: {. . .}.
Comment: Noted in parallel session.

Parallel discussion:

This was noted in parallel session.

Status: Noted.

3GPP
Report of meeting S2-168

S2-2503759 (CR) 23.228 CR1639 (Rel-19, 'F'): Adding event for session establishment cancellation (Source:
China Mobile)
Document for: Approval
Abstract:
Summary of change: Add event about session establishment cancellation.
Comment: Rel-19 reserved, Rel-18 CR provided!

Parallel discussion:

Correct content to a Rel-18 CR. Revised in parallel session to S2-2503978.

Plenary Discussion:

Postponed.

Status: Postponed.

S2-2503760 (CR) 23.228 CR1640 (Rel-19, 'A'): Adding event for session establishment cancellation (Source:
China Mobile)
Document for: Approval
Abstract:
Rel-19 mirror CR: Summary of change: Add event about session establishment cancellation.
Parallel discussion:

Revised in parallel session to S2-2503979.

Plenary Discussion:

Postponed.

Status: Postponed.

S2-2503761 (CR) 23.228 CR1641 (Rel-18, 'F'): Correction on bootstrap DC removal (Source: China Mobile)
Document for: Approval
Abstract:
Summary of change: Correct the description of bootstrap DC removal to clarify the bootstrap DC shall be
removed if a session with bootstrap data channels is diverted to a UE or a IMS network that does not support
IMS data channel.
Comment: Confirm Spec version used - CR states 18.8.0!

Parallel discussion:

Revised in parallel session to S2-2503980.

Add cosigners. Revised in parallel session to S2-2504204.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

3GPP
Report of meeting S2-168

S2-2503762 (CR) 23.228 CR1642 (Rel-19, 'A'): Correction on bootstrap DC removal (Source: China Mobile)
Document for: Approval
Abstract:
Rel-19 mirror CR: Summary of change: Correct the description of bootstrap DC removal to clarify the
bootstrap DC shall be removed if a session with bootstrap data channels is diverted to a UE or a IMS
network that does not support IMS data channel.
Parallel discussion:

Revised in parallel session to S2-2503981.

Add cosigners. Revised in parallel session to S2-2504205.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

9.15.2 Access Traffic Steering, Switching and Splitting support in the 5GS;
Phase 3 (ATSSS_Ph3)
This agenda item was convened by Andy Bennett (Samsung).

S2-2503891 (CR) 23.501 CR6276R1 (Rel-18, 'F'): Alignment with ATSSS Capability IE (Source: Apple)
Document for: Approval
Abstract:
Summary of change: Align UE capability indication for ATSSS with TS 24.501.
Comment: Revision of S2-2503890.

Parallel discussion:

It was commented that there are cases where it is not necessary to align with CT terminology, where it is
consistently understood from the SA WG2 view, as always aligning would mean a full review of all SA WG2
terminology when CT have finished the stage 3. Ericsson commented that this improves alignment and does
not change the allowed combinations. Apple commented that CT have deprecated the old parameter names
and it is beneficial to update SA WG2 terminology in this case. It was suggested that the Rel-19 terminology
will also need to be aligned where this introduces misalignment. This was left for off-line discussion and
revised to S2-2504134.

The second bullet should add 'capability'. This was revised to S2-2504386.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

9.16.2 UPF enhancement for Exposure And SBA (UPEAS)

There were no contributions to this agenda item.

9.17.2 Edge Computing Phase 2 (EDGE_Ph2)

This agenda item was convened by Dario Tonesi (Qualcomm).

3GPP
Report of meeting S2-168

S2-2503852 (CR) 23.502 CR5478 (Rel-19, 'F'): SMF event on simultaneous connectivity failure (Source:
Nokia)
Document for: Approval
Abstract:
Summary of change: Introduces SMF event on simultaneous connectivity failure.
Parallel discussion:

Revised in parallel session to S2-2503919.

Revised in parallel session to S2-2504173 (withdrawn).

Withdrawn.

Status: Withdrawn.

9.18.2 5G Timing Resiliency and TSC & URLLC enhancements

(TRS_URLLC)
There were no contributions to this agenda item.

9.19.2 Vehicle Mounted Relays (VMR)

This agenda item was convened by Andy Bennett (Samsung).

There were no contributions to this agenda item.

9.20.2 Support for 5WWC Phase 3 (5WWC_Ph2)

There were no contributions to this agenda item.

9.21 Stage 2 of MPS_WLAN (MPS_WLAN)

There were no contributions to this agenda item.

9.22.2 5G AM Policy (AMP)

There were no contributions to this agenda item.

9.23.2 Enablers for Network Automation for 5G - Phase 3 (eNA_Ph3)

This agenda item was convened by Andy Bennett (Samsung).

S2-2502853 (CR) 23.288 CR1402 (Rel-18, 'F'): Clarifications on the definition of accuracy (Source: ZTE)
Document for: Approval
Abstract:
Summary of change: Adjust the definition of Analytics/ML Model Accuracy Information to align with stage 3
decision.
Parallel discussion:

It was decided to do this only for Rel-19 and this was noted in parallel session.

Status: Noted.

3GPP
Report of meeting S2-168

S2-2502854 (CR) 23.288 CR1403 (Rel-19, 'A'): Clarifications on the definition of accuracy (Source: ZTE)
Document for: Approval
Abstract:
Rel-19 mirror CR: Summary of change: Adjust the definition of Analytics/ML Model Accuracy Information to
align with stage 3 decision.
Parallel discussion:

This should be a Cat 'F' CR. It was commented that the definition in clause 3 needs to be updated. Making
the number of samples optional needs discussion and the accuracy calculation should be clarified. this was
left for off-line discussion and revised to S2-2504125.

This was reviewed and agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2502855 (CR) 23.288 CR1404 (Rel-18, 'F'): Clarifications on the file address related to ADRF (Source:
ZTE)
Document for: Approval
Abstract:
Summary of change: Adding a note to Clarify the ML model file address listed in the output of
Nadrf_MLModelManagement_RetrievalRequest service operation is the ML model file address allocated by
ADRF, not the one given by NWDAF in the Nadrf_MLModelManagement_StorageRequest service operation,
the consumer may download the ML Model through file address for further uses.
Parallel discussion:

It was decided to consider adding a note to the TS only for Rel-19 and this was noted in parallel session.

Status: Noted.

S2-2502856 (CR) 23.288 CR1405 (Rel-19, 'A'): Clarifications on the file address related to ADRF (Source:
ZTE)
Document for: Approval
Abstract:
Rel-19 mirror CR: Summary of change: Adding a note to Clarify the ML model file address listed in the output
of Nadrf_MLModelManagement_RetrievalRequest service operation is the ML model file address allocated
by ADRF, not the one given by NWDAF in the Nadrf_MLModelManagement_StorageRequest service
operation, the consumer may download the ML Model through file address for further uses.
Parallel discussion:

This should be a Cat 'F' CR. There was a suggestion to make this normal paragraph rather than a note. This
was left for off-line discussion and revised to S2-2504126.

This was reviewed and agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503539 (CR) 23.288 CR1446 (Rel-18, 'F'): Correction on analytics feedback information (Source: Vivo)
Document for: Approval
Abstract:
Summary of change: Correction the name of MFAF data management; Correction on the name of analytics
feedback information in clause 5C.1, and the description of analytics feedback information in clause 6.1.3.
Parallel discussion:

This was not considered essential for Rel-18 and this was noted in parallel session.

Status: Noted.

3GPP
Report of meeting S2-168

S2-2503540 (CR) 23.288 CR1447 (Rel-19, 'F'): Correction on analytics feedback information (Source: Vivo)
Document for: Approval
Abstract:
Summary of change: Correction the name of MFAF data management; Correction on the name of analytics
feedback information in clause 5C.1, and the description of analytics feedback information in clause 6.1.3.
Parallel discussion:

This should be a Cat 'F' CR. This was revised to S2-2504127.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

9.24.2 Enhanced support of Non-Public Networks phase 2 (eNPN_Ph2)

There were no contributions to this agenda item.

9.25.2 Enhancement of 5G UE Policy (eUEPO)

This agenda item was convened by Andy Bennett (Samsung).

S2-2503778 (CR) 23.502 CR5380R1 (Rel-18, 'F'): Correction for BSF invocation in URSP Rule Enforcement
Information procedure (Source: Oracle, Verizon, Ericsson)
Document for: Approval
Abstract:
Summary of change: This CR proposes to fix invocation of BSF Subscribe service operation.
Comment: Revision of S2-2502876.

Parallel discussion:

Oracle suggested adding some text to clarify that the NSSAI is included not only for single invocations of the
SUPI. This was revised to S2-2504114.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

3GPP
Report of meeting S2-168

S2-2503779 (CR) 23.502 CR5381R1 (Rel-19, 'A'): Correction for BSF invocation in URSP Rule Enforcement
Information procedure (Source: Oracle, Verizon)
Document for: Approval
Abstract:
Rel-19 mirror CR: Summary of change: This CR proposes to fix invocation of BSF Subscribe service
operation.
Comment: Revision of S2-2502877.

Parallel discussion:

This was revised, to align with the changes to the Rel-18 CR, to S2-2504115.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

9.26.2 System Enabler for Service Function Chaining (SFC)

There were no contributions to this agenda item.

9.27.2 Extensions to the TSC Framework to support DetNet (DetNet)

There were no contributions to this agenda item.

9.28.2 Seamless UE context recovery (SUECR)

There were no contributions to this agenda item.

9.29 Multiple location report for MT-LR Immediate Location

Request for regulatory services (TEI17_MLR)
There were no contributions to this agenda item.

9.30 Secondary DN Authentication and authorization in EPC

IWK cases (TEI17_SDNAEPC)
There were no contributions to this agenda item.

9.31 MBS support for V2X services (TEI17_MBS4V2X)

There were no contributions to this agenda item.

3GPP
Report of meeting S2-168

9.32 Spending Limits for AM and UE Policies in the 5GC

(TEI17_SLAMUP)
There were no contributions to this agenda item.

9.33 Enhancement of application detection event exposure

(TEI17_ADEE)
There were no contributions to this agenda item.

9.34 General Support of IPv6 Prefix Delegation (TEI17_IPv6PD)

There were no contributions to this agenda item.

9.35 New WID on Dynamically Changing AM Policies in the 5GC

Phase 2 (TEI17_DCAMP_Ph2)
There were no contributions to this agenda item.

9.36 Enhancement of NSAC for maximum number of UEs with at

least one PDU session/PDN connection (eNSAC)
There were no contributions to this agenda item.

9.37 Generic Rel-18 LSs

This topic was not on the agenda for this meeting.

9.38 Rel-18 CAT B/C alignment CR(s) due to the work led by
other 3GPP Working Groups
There were no contributions to this agenda item.

19 Rel-19 SIDs and WIDs

There were no contributions to this agenda item.

3GPP
Report of meeting S2-168

19.1.1 Study on Integration of satellite components in the 5G architecture

Phase 3 (FS_5GSAT_Ph3_ARC)
This topic was not on the agenda for this meeting.

19.1.2 Integration of satellite components in the 5G architecture Phase 3

(5GSAT_Ph3_ARC)
This agenda item was convened by Dario Tonesi (Qualcomm).

Liaisons unrelated to specific key issues

S2-2502822 (LS IN) LS from RAN WG2: Geofencing in ETWS for NR and NB-IoT NTN (Source: RAN WG2
(R2-2501581))
Document for: Information
Abstract:
RAN WG2 has agreed to introduce geographical information in ETWS messages for NTN cells to enable
geofencing. The Warning Area Coordinates IE will be added in the primary and secondary notifications for
NR NTN (SIB6, SIB7) and NB-IoT NTN (SIB10-NB, SIB11-NB) without introducing the need for
segmentation of ETWS primary notification. RAN WG2 understands that there may be an impact in CT WG1
specifications and would kindly request CT WG1 to consider the necessary updates.
Comment: Noted in parallel session.

Parallel discussion:

This was noted in parallel session.

Status: Noted.

S2-2502824 (LS IN) LS from RAN WG2: LS to CT1 and CT4 on maximum warning message size (Source:
RAN WG2 (R2-2501586))
Document for: Information
Abstract:
RAN WG2 introduced the signalling support of the PWS messages in NB-IoT, resulting in the following
summary on the segment limit of a PWS message. With a current maximum of 64 segments for SIB11-NB
and SIB12-NB and a 680-bit Transport Block Size (TBS), RAN WG2 limits the PWS message capacity in
NB-IoT to be less than what is currently specified for LTE. RAN WG2 discussed the feasibility of extending
the segment limit beyond 64, but also identified potential drawbacks including further increases in PWS
message acquisition latency (even with the same segment limit, PWS message acquisition in NB-IoT is
expected to take longer time compared to LTE), as well as susceptibility to mobility-related interruptions.
RAN WG2 respectfully asks CT WG1 and CT WG4 to provide their feedback on whether there is need to
support longer messages than the maximum PWS limit of 5440 octets for NB-IoT (by extending the segment
limit beyond 64), taking into account the potential drawbacks provided in the overall description.
Comment: Noted in parallel session.

Parallel discussion:

This was noted in parallel session.

Status: Noted.

3GPP
Report of meeting S2-168

KI#1 Regenerative payload satellite access

S2-2502829 (LS IN) LS from RAN WG3: Reply LS on OAM requirements to support regenerative payload
transport links (Source: RAN WG3 (R3-250895))
Document for: Action
Abstract:
RAN WG3 thanks SA WG2 and SA WG5 for the reply LS on OAM requirements to support regenerative. The
existing NG signalling procedures for supported TAI list update are expected to work as legacy. However,
some NTN scenarios (e.g. NGSO NTN scenarios) benefit from the RAN WG3 agreements on OAM based
solution. RAN WG3 discussed and would like to provide the following clarifications: - In general, satellite
orbital movement is periodic and predictable; therefore, any resulting change to node parameters will result
in the same information being frequently exchanged over network interfaces at regular intervals. - In the
solution agreed by RAN WG3, both AMF and gNB share the same OAM configuration on supported TAI list
of the on-board gNB, this is considered as an optimization. - NG Setup procedure including the supported
TAs is always expected to take place according to TS38.413. - The solution agreed by RAN WG3 avoids the
need for periodic and frequent RAN Configuration Update procedures. Any potential discrepancy between
OAM configuration and parameters received via NG signalling, if present, is expected to be resolved via
implementation. - With respect to the frequency of updates by OAM, RAN WG3 believes this is in SA WG5
scope. Action: RAN WG3 kindly asks SA WG2 and SA WG5 to take the above information into account.
Comment: Responses drafted in S2-2502929, S2-2502930, S2-2503231, S2-2503706. Postponed in
parallel session.

Plenary Discussion:

Postponed.

Status: Postponed.

S2-2502842 (LS IN) LS from SA WG5: Reply LS to LS on reply to LS on OAM requirements to support
regenerative payload (Source: SA WG5 (S5-250842))
Document for: Action
Abstract:
SA WG5 thanks SA WG2 for the LS S2-2413030 on reply to LS on OAM requirements to support
regenerative payload. SA WG5 has concluded an OAM solution to configure AMF with TAIs supported by
NTN gNB in TR 28.874 clause 5.2.2.3.2. {. .} Action: SA WG5 kindly requests SA WG2 take the above into
consideration.
Comment: Responses drafted in S2-2503231, S2-2503706. Postponed in parallel session.

Plenary Discussion:

Postponed.

Status: Postponed.

S2-2503268 (DISCUSSION) Tracking Area handling for regenerative satellite access. (Source: Ericsson)
Document for: Discussion
Abstract:
This contribution analyses the RAN WG3 agreement to configure AMF with a timetable per TAI and gNB.
Comment: Noted in parallel session.

Parallel discussion:

This was noted in parallel session.

Status: Noted.

3GPP
Report of meeting S2-168

S2-2503224 (DISCUSSION) On TAI configuration in AMF via OAM. (Source: Qualcomm Incorporated,
Vodafone)
Document for: Approval
Abstract:
Discusses the RAN WG3 proposal for TAI configuration in AMF and proposes a way forward.
Comment: Noted in parallel session.

Parallel discussion:

This was noted in parallel session.

Status: Noted.

S2-2503706 (LS OUT) [DRAFT] Reply LS on OAM requirements to support regenerative payload transport
links (Source: CATT)
Document for: Approval
Abstract:
Reply LS on OAM requirements to support regenerative payload transport links.
Comment: Response to S2-2502829 and S2-2502842. Noted in parallel session.

Parallel discussion:

This was noted in parallel session.

Status: Noted.

S2-2502929 (LS OUT) [DRAFT] Reply LS on OAM requirements to support regenerative payload (Source:
ZTE Corporation)
Document for: Approval
Abstract:
To: RAN WG3, SA WG5.
Comment: Response to S2-2502829.

Convenor comment:

Merge into S2-2503706.

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2502930 (LS OUT) [DRAFT] Reply LS on OAM requirements to support regenerative payload (Source:
ZTE Corporation)
Document for: Approval
Abstract:
To: SA WG5, RAN WG3.
Comment: Response to S2-2502829.

Convenor comment:

Duplicated: note?

Plenary Discussion:

Not handled.

Status: Not treated.

3GPP
Report of meeting S2-168

S2-2503231 (LS OUT) [DRAFT] Reply LS on OAM requirements to support regenerative payload transport
links (Source: Qualcomm, Vodafone)
Document for: Approval
Abstract:
To: RAN WG3, SA WG5.
Comment: Response to S2-2502829 and S2-2502842. Noted in parallel session.

Parallel discussion:

This was noted in parallel session.

Status: Noted.

S2-2503416 (CR) 23.501 CR6217 (Rel-19, 'F'): TAIs configured by OAM (Source: Vivo)
Document for: Approval
Abstract:
Summary of change: Capture the descriptions of OAM configured TAIs in regenerative payload.
Convenor comment:

Handle - baseline.

Parallel discussion:

Revised in parallel session to S2-2503911.

Plenary Discussion:

Noted.

Status: Noted.

S2-2503707 (CR) 23.501 CR6250 (Rel-19, 'F'): Configuration of TAI list for regenerative satellite payload
(Source: CATT)
Document for: Approval
Abstract:
Summary of change: Add the description that the AMF is configured with the supported TAI list of the on-
board gNB, to support regenerative satellite payload for NR NTN.
Convenor comment:

Merge into S2-2503416?

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503417 (CR) 23.502 CR5443 (Rel-19, 'F'): TAIs configured by OAM (Source: Vivo)
Document for: Approval
Abstract:
Summary of change: Capture the descriptions of OAM configured TAIs in regenerative payload.
Convenor comment:

Handle.

Parallel discussion:

Revised in parallel session to S2-2503912.

Plenary Discussion:

Noted.

Status: Noted.

3GPP
Report of meeting S2-168

S2-2503710 (CR) 23.501 CR6252 (Rel-19, 'F'): Clarification on 5QI for satellite access (Source: CATT)
Document for: Approval
Abstract:
Summary of change: Clarify that NOTE 17 in Table 5.7.4-1 only applies to satellite access with transparent
payload.
Convenor comment:

Handle.

Parallel discussion:

Revised in parallel session to S2-2503913.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503711 (CR) 23.203 CR1142 (Rel-19, 'F'): Clarification on QCI for satellite access (Source: CATT)
Document for: Approval
Abstract:
Summary of change: Add clarifications on packet delay budget for QCI value 10 considering satellite access
with regenerative payload.
Convenor comment:

Handle.

Parallel discussion:

Revised in parallel session to S2-2503914.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

KI#2 Store and forward satellite operation

KI#2: Liaisons

S2-2502825 (LS IN) LS from RAN WG3: Reply LS on UE Location Information for NB-IoT NTN (Source:
RAN WG3 (R3-250761))
Document for: Action
Abstract:
RAN WG3 thanks SA WG2 for their reply LS on UE Location Information for NB-IoT NTN and sharing the
corresponding SA WG2 CR. RAN WG3 analysed the scenarios mentioned in the SA WG2 LS to add 'Coarse
UE Location Requested' in UL NAS Transport message and in Connection Resume Request. RAN WG3
thinks it is not necessary to add coarse UE location in UL NAS Transport and Connection Resume
procedures. Action: RAN WG3 asks SA WG2 to kindly take the above information into account.
Comment: Noted in parallel session.

Parallel discussion:

This was noted in parallel session.

Status: Noted.

3GPP
Report of meeting S2-168

KI#2: S&F wait timer related

S2-2503071 (CR) 23.401 CR3905 (Rel-19, 'F'): Clarification on S&F Wait Timer (Source: Nokia)
Document for: Approval
Abstract:
Summary of change: Clarification text added on UE behaviour when S&F Wait timer is running.
Convenor comment:

Handle - baseline.

Parallel discussion:

Revised in parallel session to S2-2503915.

Plenary Discussion:

Noted.

Status: Noted.

S2-2503275 (CR) 23.401 CR3909 (Rel-19, 'F'): Clarification on usage of S&F Wait Timer in UE (Source:
China Telecom)
Document for: Approval
Abstract:
Summary of change: Clarification on usage of S&F Wait Timer in UE.
Comment: Noted in parallel session.

Parallel discussion:

This was noted in parallel session.

Status: Noted.

S2-2502879 (CR) 23.401 CR3899 (Rel-19, 'F'): Refinement of UE behavior and S&F wait timer handling
(Source: ZTE)
Document for: Approval
Abstract:
Summary of change: 1) Define the start time of the S&F wait timer. 2) Define the UE behavior during the S&F
wait timer running period. 3) Modify the condition for the MME to determine whether it has a fresh UE
context. 4) Formatting error correction.
Convenor comment:

Partially merge into S2-2503071 Focus on when UE starts timer.

Plenary Discussion:

Not handled.

Status: Not treated.

3GPP
Report of meeting S2-168

S2-2503655 (CR) 23.401 CR3918 (Rel-19, 'F'): Clarification on S&F timer in NAS Accept and NAS Reject
messages (Source: Huawei, HiSilicon)
Document for: Approval
Abstract:
Summary of change: A UE which receives the S&F Wait Timer in NAS reject message does not initiate any
NAS procedure until the timer expires. A UE which receives the S&F Wait Timer in NAS accept message can
continue to send signaling or data via the satellite which provided the timer until coverage lost. The UE does
not initiate signaling after that until the timer expires.
Convenor comment:

Partially merge into S2-2503071 Focus on when UE starts timer.

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503880 (CR) 23.401 CR3922 (Rel-19, 'F'): Handling S&F wait timer. (Source: Samsung)
Document for: Approval
Abstract:
Summary of change: UE does not attempt NAS signalling unless it is served by a satellite which provided
accept message to the UE.
Comment: Merged into S2-2503915.

Parallel discussion:

Merged.

Status: Merged.

KI#2: Other clarifications

S2-2503886 (CR) 23.401 CR3924 (Rel-19, 'F'): Editorial fixes and handling when S&F is not enabled by UE.
(Source: Samsung)
Document for: Approval
Abstract:
Summary of change: 1) Editorial fixes. 2) UE may deprioritize S&F cell.
Convenor comment:

Handle.

Parallel discussion:

Focus only on editorials (keep only change #1) PLMN selection discussion is to be led by CT WG1. Revised
in parallel session to S2-2503916.

Keep only second change. Remove 1st bullet from reason for change. Revised in parallel session to S2-
2504183.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

3GPP
Report of meeting S2-168

S2-2503656 (CR) 23.401 CR3919 (Rel-19, 'F'): Corrections for S&F Support and operation (Source: Huawei,
HiSilicon)
Document for: Approval
Abstract:
Summary of change: Make it clear that UE S&F Support is signalled in UE Network Capability IE, and
normalise the terminology in procedure aspects, removing the depending on exactly when the UE signalled
its support. Clarify that the UE does not need to take into account the SIB indication when signalling support
of S&F. Move existing text about parameters being provided in detach into a suitable location and add in
parameters apply in the same PLMN case.
Convenor comment:

Handle - baseline.

Parallel discussion:

Revised in parallel session to S2-2503917.

UE support vs. UE enabled for S&F? UE always sending capabilities to CN? Revised in parallel session to
S2-2504182.

UE enabled UE always sends capabilities. Revised in parallel session to S2-2504244.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503070 (CR) 23.401 CR3904 (Rel-19, 'F'): TAU and Service Request procedure correction for S&F
(Source: Nokia)
Document for: Approval
Abstract:
Summary of change: Corrections to TAU procedure for S&F UEs Corrections to Service Request procedure
for S&F UEs.
Convenor comment:

Merged into S2-2503656?

Plenary Discussion:

Not handled.

Status: Not treated.

3GPP
Report of meeting S2-168

S2-2503265 (CR) 23.401 CR3906 (Rel-19, 'F'): Clarifications to UE S&F capability and procedures that can
include S&F Monitoring list (Source: Ericsson)
Document for: Approval
Abstract:
Summary of change: 1. It is suggested to change the text to 'For a UE which supports Store and Forward
Satellite operation' so that it can cover both scenarios that UE indicates UE Network Capability using existing
mechanism and the UE's network capability is known by the network based on the stored MM context. 2.
Also add clarification that the network can make use of periodic TAU procedure to provide the UE with S&F
related information. 3. Revert the change from 'UE is enabled for' to 'UE supports', and remove the condition
that the satellite is operating in S&F mode.
Comment: Merged into S2-2503917.

Convenor comment:

Handle.

Parallel discussion:

Merged.

Status: Merged.

S2-2502880 (CR) 23.401 CR3900 (Rel-19, 'F'): Clarify the conditions for MME to provide S&F parameters in
NAS procedure (Source: ZTE)
Document for: Approval
Abstract:
Summary of change: Clarify the conditions for MME to provide S&F parameters in NAS procedures.
Comment: Merged into S2-2503917.

Convenor comment:

Handle.

Parallel discussion:

Merged.

Status: Merged.

S2-2502882 (CR) 23.401 CR3902 (Rel-19, 'F'): Align the condition for UE to indicate the S&F capability
(Source: ZTE)
Document for: Approval
Abstract:
Summary of change: Align the condition for UE to indicate the S&F capability.
Comment: Merged into S2-2503917.

Convenor comment:

Handle.

Parallel discussion:

Merged.

Status: Merged.

3GPP
Report of meeting S2-168

S2-2503415 (CR) 23.401 CR3914 (Rel-19, 'F'): Procedure updates for S&F (Source: Vivo)
Document for: Approval
Abstract:
Summary of change: Add the following descriptions in MT procedure similar to MO process: If the UE had
indicated 'S&F Capability' in the UE Core Network Capability and the MME is operating in S&F Mode, the
MME may optionally provide in the NAS PDU message any of the following: a S&F Wait Timer, a S&F
Monitoring List, an Estimated S&F UL Delivery Time (see clause 4.13.9).
Convenor comment:

Handle.

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503533 (CR) 23.401 CR3916 (Rel-19, 'F'): MT data transport in CP CIoT EPS Optimisation update for
S&F operation (Source: Xiaomi)
Document for: Approval
Abstract:
Summary of change: Supporting S&F operation on MT data transport in Control Plane CIoT EPS
Optimisation.
Comment: Merged into S2-2503917.

Convenor comment:

Handle.

Parallel discussion:

Merged.

Status: Merged.

S2-2502883 (CR) 23.401 CR3903 (Rel-19, 'F'): Update to the GUTI Reallocation procedure (Source: ZTE)
Document for: Approval
Abstract:
Summary of change: Added the reason for updating the network-triggered S&F Wait Timer and S&F
Monitoring List information. 2) Modified the corresponding procedure.
Comment: Noted in parallel session.

Parallel discussion:

This was noted in parallel session.

Status: Noted.

S2-2503708 (CR) 23.401 CR3920 (Rel-19, 'F'): Clarification on the deletion of the previous S&F Monitoring
List (Source: CATT)
Document for: Approval
Abstract:
Summary of change: Add an indication for the UE to delete the previous S&F Monitoring List.
Comment: Noted in parallel session.

Parallel discussion:

This was noted in parallel session.

Status: Noted.

3GPP
Report of meeting S2-168

S2-2502881 (CR) 23.401 CR3901 (Rel-19, 'F'): Enhancement of S&F Monitoring List update (Source: ZTE)
Document for: Approval
Abstract:
Summary of change: Add the S&F Monitoring List Deletion Indication in ATTACH, TAU, CPSR, GUTI
Reallocation procedure.
Convenor comment:

Merge into S2-2503708?

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503276 (CR) 23.401 CR3910 (Rel-19, 'F'): Clarification on Attach reject (Source: China Telecom)
Document for: Approval
Abstract:
Summary of change: Clarification in step2: The MME may perform attach reject after receving the UE Identity
at step4.
Comment: Noted in parallel session.

Parallel discussion:

This was noted in parallel session.

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503495 (CR) 23.401 CR3915 (Rel-19, 'F'): Avoid congestion caused by S&F timer (Source: MediaTek
Inc.)
Document for: Approval
Abstract:
Summary of change: To avoid that large amounts of UEs initiate deferred requests (almost) simultaneously,
the MME should select the S&F Wait timer value so that the deferred requests are not synchronized.
Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503750 (CR) 23.401 CR3921 (Rel-19, 'F'): Procedure updates for S&F operation (Source: LG
Electronics)
Document for: Approval
Abstract:
Summary of change: - It is clarified that the DL NAS PDU message may contain the S&F related parameters
during MT Data Transport procedure. - Align the NOTE in the Reason for changes in Attach and TAU
procedures.
Convenor comment:

Handle.

Plenary Discussion:

Not handled.

Status: Not treated.

3GPP
Report of meeting S2-168

S2-2503414 (CR) 23.401 CR3913 (Rel-19, 'F'): Updates to S&F mode transition (Source: Vivo)
Document for: Approval
Abstract:
Summary of change: Clarify that when transition to S&F mode occurs and UE is in connected state, the MME
may detach the UE with a cause non-specific to S&F Mode.
Convenor comment:

Handle.

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503363 (CR) 23.401 CR3911 (Rel-19, 'F'): Transitioning between operation in S&F mode and normal
mode (Source: LG Electronics)
Document for: Approval
Abstract:
Summary of change: MME-onboard may trigger S1 release procedure with the existing cause 'load
balancing TAU required' when transition between the S&F mode and normal mode.
Convenor comment:

Handle.

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503881 (CR) 23.401 CR3923 (Rel-19, 'F'): Handling S&F not allowed. (Source: Samsung)
Document for: Approval
Abstract:
Summary of change: If network determines to not provide S&F service, it indicates with a reject cause to the
UE.
Convenor comment:

Handle.

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503266 (CR) 23.401 CR3907 (Rel-19, 'F'): Clarify S1-U not supported by split MME (Source: Ericsson)
Document for: Approval
Abstract:
Summary of change: Clarify that the 'user plane' in the example is S1-U user plane. Remove the NOTE in
the procedure clauses.
Convenor comment:

Handle.

Plenary Discussion:

Not handled.

Status: Not treated.

3GPP
Report of meeting S2-168

S2-2503267 (CR) 23.401 CR3908 (Rel-19, 'F'): Clarify PDN connection handling for split MME (Source:
Ericsson)
Document for: Approval
Abstract:
Summary of change: 1. Clarify that it is the PDN connection handling that is up to implementation. Clarify
that the 'initial attach reject + MME onboard interacts with MME ground' can happen 'before and after xxxx'.
2. Change 'supporting' to 'operating'.
Convenor comment:

3GPP
Report of meeting S2-168

S2-2503709 (CR) 23.501 CR6251 (Rel-19, 'F'): Clarification on UE-SAT-UE communication when serving
satellite changes (Source: CATT)
Document for: Approval
Abstract:
Summary of change: Clarified NOTE 1 to explicitly state that the assumption of co-located gNB, UL CL/L-
PSA, IMS-AGW applies to both source and target satellites.
Convenor comment:

Handle.

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2502917 (CR) 23.228 CR1608 (Rel-19, 'F'): Update to Initial Call setup and functional support for UE-
Satellite-UE communication in IMS (Source: Ericsson)
Document for: Approval
Abstract:
Summary of change: Identify event used by P-CSCF as being Access Network Information Notification, and
the PCRT trigger set to Access Network Information report.
Convenor comment:

Handle.

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503712 (CR) 23.228 CR1636 (Rel-19, 'F'): Clarification on UE-Satellite-UE communication procedures
(Source: CATT)
Document for: Approval
Abstract:
Summary of change: Change 'UL CL' to 'UL CL/BP' in UE-Satellite-UE communication procedures. Modify
the description of N5 interface. Editorial modifications.
Convenor comment:

Handle.

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503583 (CR) 23.228 CR1629 (Rel-19, 'F'): Update on early media handling in UE-Satellite-UE scenario
(Source: Vivo)
Document for: Approval
Abstract:
Summary of change: Update AE.5.3.
Convenor comment:

Handle.

Plenary Discussion:

Not handled.

Status: Not treated.

3GPP
Report of meeting S2-168

S2-2503652 (CR) 23.228 CR1630 (Rel-19, 'F'): Clarification on UP path event subscription for UE-satellite-
UE communication (Source: Huawei, HiSilicon)
Document for: Approval
Abstract:
Summary of change: Clarify that 'AF acknowledgment to be expected' is required for subscription to
corresponding SMF events (DNAI change) during call setup procedure.
Convenor comment:

Handle.

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503764 (CR) 23.228 CR1643 (Rel-19, 'F'): Correction on UE-sat-UE communication procedures
(Source: China Mobile)
Document for: Approval
Abstract:
Summary of change: Add descriptions of using Rx interface for event subscription/notification and media
authorization in call setup procedure.
Convenor comment:

Handle.

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2502918 (CR) 23.228 CR1609 (Rel-19, 'F'): Update to Mobility procedures for UE-Satellite-UE
communication (Source: Ericsson)
Document for: Approval
Abstract:
Summary of change: Replace the term positive response with the acknowledgement of notifications about
UP path management events; being the actual terminology used in the 23.502.
Convenor comment:

Handle.

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2502928 (CR) 23.228 CR1611 (Rel-19, 'F'): Update of target satellite ID notification (Source: ZTE)
Document for: Approval
Abstract:
Summary of change: Clarified the capabilities of the PCF. Updated the notification send to UE when the
serving satellite changes.
Convenor comment:

Handle.

Plenary Discussion:

Not handled.

Status: Not treated.

3GPP
Report of meeting S2-168

19.2.1 Study on system architecture for next generation real time

communication services phase 2 (FS_NG_RTC_Ph2)
This topic was not on the agenda for this meeting.

19.2.2 System architecture for next generation real time communication

services phase 2 (NG_RTC_Ph2)
This agenda item was convened by Dario Tonesi (Qualcomm).

Liaisons

S2-2502847 (LS IN) LS from GSMA TSG IMSDCAS: LS to SA WG2 About Requirements Concerning
Automatic Resume Where You have Left Off (Source: GSMA TSG IMSDCAS (IMSDCAS022_005v5))
Document for: Action
Abstract:
GSMA Terminals Steering Group (TSG) and GSMA Network Group (NG) has completed phase 1 of data
channel profiling with the publication of GSMA TS.66 [1] as per information contained in S4-241435. Phase 1
of data channel specifies minimal set of requirements to support both the protocol UNI/NNI interworking and
the application layer API interworking. And currently GSMA members are submitting contributions to update
GSMA PRD NG.134 [2] and GSMA PRD TS.66 [1] so they are in-line with 3GPP Rel-18 features. That work
is expected to be completed by Q1.2025. GSMA TSG IMSDCAS members are now proposing new set of
data channel requirements related to the feature 'Automatic Resume from the point where you have left off'.
This feature is available on the digital platforms, e.g. YouTube, and provides both convenience and
engagement benefits. The feature allows to continue interacting with the service from a last point that the
user left off. People watching video or downloading files are well acquainted with this feature. In the rest of
this text the feature will be referred in short as the Automatic Resumption. The use case details will be
described in the next version of GSMA PRD NG.129. {. . .} Action: Request to SA WG2: GSMA TSG
IMSDCAS kindly requests SA WG2 to help with the following clarifications related to the Automatic
Resumption use cases and the technical feature 1. Confirm whether SA WG2 or SA WG4 has considered
the use cases of the class 'Resume from the point where you have left off' and what was the conclusion on
this topic? 2. Confirm whether the Automatic Resumption technical feature and state preservation might
interact with any other 3GPP specified features? 3. Confirm whether the described feature is in any way
related to the session continuity or might impact the supplementary services? 4. Confirm if SA WG2 plans to
define and capture the requirements related to 'Automatic Resume from the point where you have left off'
and whether SA WG2/SA WG4 plans to specify technical solution for this feature? 5. Advice on the feasibility
of described technical implementation? 6. Advise whether it would be possible to realize such state retention
functionality without the need to introduce SDP modifications or any other modifications to the existing
standards, i.e. by using session cookies, or exchanging the state data as part of application or bootstrap data
channel protocol, including that of consensus? 7. Confirm whether SA WG2 / SA WG4 have considered
scenarios where DCS stores an application context or other application data and DCS sends it as part of
bootstrap process to UE or when a such data is requested by data channel application.
Comment: Response drafted in S2-2503170. Postponed in parallel session.

Plenary Discussion:

Postponed.

Status: Postponed.

3GPP
Report of meeting S2-168

S2-2503170 (LS OUT) [DRAFT] Reply to LS on Automatic Resumption in IMS data channel (Source:
Samsung)
Document for: Approval
Abstract:
To: GSMA TSG IMSDCAS. CC: SA WG4, CT WG1.
Comment: Response to S2-2502847. Postponed in parallel session.

Plenary Discussion:

Postponed.

Status: Postponed.

S2-2502836 (LS IN) LS from SA WG3: LS on Privacy and security aspects regarding DC management by
the network (Source: SA WG3 (S3-251144))
Document for: Action
Abstract:
SA WG2 endorsed a CR (S2-2501099) for detailed call flows of adding application data channel(s) to an
existing IMS session for A2P, P2P, and P2A2P DC. In Annex AG.1 of the CR, a note was added as below:
NOTE: Privacy and security aspects regarding adding, removing, updating data channels by the network are
under SA WG3 responsibility. According to workflows in Annex AG.2.1 of the CR, especially AG.2.1.Y
(Adding P2P application data channel to an existing IMS session), the subscriber of the UE is not aware
whether the DC is added by the DC application server instead of peer UE, hence may be misled to accept or
reject the DC request. Similarly, the user may accept the DC terminating/update request from the DC AS
without being aware of request initiator. This is due to lack of transparency in the IMS DC session control
procedure. It's essential to consider transparency to user during IMS Data Channel session control
exposure. For example, the user may need to be aware that the DC adding, removing, updating request is
initiated by the DC AS instead of the peer UE. SA WG3 kindly requests SA WG2 to take the above
information into account and consider the transparency to user in their Rel-19 work on IMS Data Channel
session control exposure. Action: SA WG3 kindly asks SA WG2 to take the information into account and
consider the transparency to user in their Rel-19 work on IMS Data Channel session control exposure.
Comment: Responses drafted in S2-2503314, S2-2503685.

Plenary Discussion:

Final response in S2-2504207.

Status: Replied to.

S2-2503314 (LS OUT) [DRAFT] Reply LS on Privacy and security aspects regarding DC management by the
network (Source: Qualcomm Incorporated)
Document for: Approval
Abstract:
The attached CR has been agreed in SA WG2 which specifies an indication of data channel initiator to
support transparency to user during IMS Data Channel session control exposure. In addition, SA WG2 kindly
requests SA WG4 to take the above information into account for the Stage 3 specification of data channel
initiator in the media description of SDP.
Comment: Response to S2-2502836.

Plenary Discussion:

Not handled.

Status: Not treated.

3GPP
Report of meeting S2-168

S2-2503308 (CR) 23.228 CR1623 (Rel-19, 'F'): Indication of DC initiator for DC create/update/termination
(Source: Qualcomm Incorporated)
Document for: Approval
Abstract:
Summary of change: A new indication of data channel initiator by IMS AS is added to the SIP INVITE/re-
INVITE to the terminating UE for user awareness.
Comment: Merged into S2-2504206.

Parallel discussion:

Merged.

Status: Merged.

S2-2503685 (LS OUT) [DRAFT] Reply LS on Privacy and security aspects regarding DC management by the
network (Source: ZTE)
Document for: Approval
Abstract:
Reply LS on Privacy and security aspects regarding DC management by the network.
Comment: Response to S2-2502836.

Parallel discussion:

Revised in parallel session to S2-2503983.

CC CT WG1. Remove text in italic. Revised in parallel session to S2-2504207.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503684 (CR) 23.228 CR1635 (Rel-19, 'F'): Additional Information in Adding P2P ADC Procedure
(Source: ZTE)
Document for: Approval
Abstract:
Summary of change: Add some additional information in the re-INVITE sent to UEs in adding P2P ADC
procedure to indicate the data channel is initiated by the DC AS.
Parallel discussion:

Revised in parallel session to S2-2503982.

Revised in parallel session to S2-2504206.

Answer 1: To rectify this issue, SA WG2 has agreed the attached CRs, which allows the PDU SESSION
MODIFICATION REQUEST to optionally have multiple non-3GPP Device Identifiers Answer 2: If any non-
3GPP Device Identifier in the PDU session modification request is not available in the UDR, the SMF will
reject the PDU SESSION MODIFICATION REQUEST without sending the any non-3GPP Device Identifier .
Answer 3: SMF will not send any non-3GPP Device Identifier in the PDU SESSION MODIFICATION
COMMAND message in the scenario that one or more non-3GPP Device Identifier are removed from the
UDR. Revised in parallel session to S2-2504214.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

3GPP
Report of meeting S2-168

S2-2502807 (LS IN) LS from CT WG1: LS on multiplexing capability negotiation (Source: CT WG1 (C1-
250885))
Document for: Action
Abstract:
CT WG1 is now working on support of IMS DC multiplexing feature in Rel-19 NG_RTC_Ph2 and notices the
following requirements of P-CSCF and S-CSCF are specified in TS 23.228 AC.7.10.2.1: {. . .} CT WG1 would
like to ask SA WG2 the following questions: {. . .} Action: CT WG1 kindly asks SA WG2 to provide answers
to the above questions.
Comment: Responses drafted in S2-2503748, S2-2503763.

Plenary Discussion:

Final response in S2-2504209.

Status: Replied to.

S2-2503748 (LS OUT) [DRAFT] Reply LS on multiplexing capability negotiation (Source: Qualcomm
Incorporated)
Document for: Approval
Abstract:
The attached CR has been agreed in SA WG2 to streamline the capability negotiation within the home IMS
network.
Comment: Response to S2-2502807.

Convenor comment:

Handle.

Parallel discussion:

Revised in parallel session to S2-2503985.

Revised in parallel session to S2-2504209.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503763 (LS OUT) [DRAFT] Reply LS on multiplexing capability negotiation (Source: China Mobile)
Document for: Approval
Abstract:
Reply LS to CT1 LS on multiplexing capability negotiation.
Comment: Response to S2-2502807. Noted in parallel session.

Parallel discussion:

This was noted in parallel session.

Status: Noted.

3GPP
Report of meeting S2-168

S2-2503295 (CR) 23.228 CR1622 (Rel-19, 'F'): Correction on DC multiplexing capability negotiation (Source:
Qualcomm Incorporated)
Document for: Approval
Abstract:
Summary of change: Clarify that, if UE doesn't receive the Feature-Caps header field in the response to the
REGISTER request, the UE shall not include the media feature tag in the INVITE request. A Note is added to
clarify that the Feature-Caps header field and media feature tag in the Contact header field are specified in
Stage 3 specifications. Update the functionalities of S-CSCF with supporting the new Feature-Caps header
field.
Convenor comment:

Handle.

Parallel discussion:

Revised in parallel session to S2-2503984.

Undo deletion of third last bullet in AC.7.10.2.1. Revised in parallel session to S2-2504208.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2502796 (LS IN) LS from SA WG4: Reply LS on Clarification of DC Binding Information (Source: SA
WG4 (S4-242111))
Document for: Action
Abstract:
SA WG4 thanks SA WG2 for their liaison on Clarification of DC Binding Information. SA WG4 understands
that this relates to supporting standalone application data channel without any bootstrap data channel, where
it is required that both UEs need to acquire a compatible version of the DC app for such application data
channel to be established. {. .}.
Comment: Revision of S2-2501374. Noted in parallel session.

Parallel discussion:

This was noted in parallel session.

Status: Noted.

3GPP
Report of meeting S2-168

KI#1: IMS events for DC communication

S2-2502909 (CR) 23.228 CR1601 (Rel-19, 'F'): KI#1: Corrections to IMS Subscribe/Notify Framework
Architecture (Source: Ericsson)
Document for: Approval
Abstract:
Summary of change: Remove event category from call flows. Clarified the interworking event. Include AF
Identifier as additional input to the subscribe request by an AS so that NEFand HSS can perform necessary
authorization prior to hanlding the request. Clarify the current status as optional output in subscribe
responses. Alignment with CT WG3 for procedures.
Convenor comment:

Handle.

Parallel discussion:

Revised in parallel session to S2-2503986.

Fix number of steps in note. In AD,2,3,3 remove addition of new sentence on IMS AS rejection. Revised in
parallel session to S2-2504210.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503097 (CR) 23.228 CR1616 (Rel-19, 'F'): NG_RTC_Ph2 KI#1: Subscribe/Notify Procedure correction
(Source: Nokia)
Document for: Approval
Abstract:
Summary of change: Main changes: Remove 'UE performs initial IMS Registration' in clause AD.3.2 In
clauses AD.3.2 and AD.3.3, move the response from NEF to AF after NEF has received response from
HSS/IMS AS. Simplify call flows by removing entities that are not impacted.
Comment: Merged into S2-2503986.

Convenor comment:

Merge into S2-2502909?

Parallel discussion:

Merged.

Status: Merged.

3GPP
Report of meeting S2-168

S2-2503681 (CR) 23.228 CR1634 (Rel-19, 'D'): Correction on IMS Service Definition (Source: ZTE)
Document for: Approval
Abstract:
Summary of change: Modification of IMS service definition.
Convenor comment:

Merge into S2-2502909?

Parallel discussion:

Focus only of the first 3 changes and deletion of MDC1 endpoint address. Revised in parallel session to S2-
2503987.

Revised in parallel session to S2-2504211.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2502919 (CR) 23.502 CR5387 (Rel-19, 'F'): KI#1: Immediate Reporting (Source: Ericsson)
Document for: Approval
Abstract:
Summary of change: The optional output parameter related to the Immediate Reporting Flag is clarified.
Convenor comment:

Handle.

Parallel discussion:

Remove dependency on other CR. Revised in parallel session to S2-2503988.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503552 (CR) 23.228 CR1624 (Rel-19, 'F'): Clarification on Nhss_ImsEE_Subscribe Immediate reporting
(Source: Huawei, HiSilicon)
Document for: Approval
Abstract:
Summary of change: Add a NOTE to clarify that HSS just transfers the immediate reporting from IMS AS, not
generating the immediate reporting by itself in Rel-19.
Comment: Check WI Code Capitalization! Noted in parallel session.

Parallel discussion:

This was noted in parallel session.

Status: Noted.

3GPP
Report of meeting S2-168

S2-2502920 (CR) 23.228 CR1610 (Rel-19, 'F'): KI#1: Event Status Retrieval Procedure (Source: Ericsson)
Document for: Approval
Abstract:
Summary of change: An explicit and optimized procedure for event status retrieval is specified.
Comment: Noted in parallel session.

Parallel discussion:

This was noted in parallel session.

Status: Noted.

S2-2502921 (CR) 23.502 CR5388 (Rel-19, 'F'): KI#1: Event Status Retrieval Procedure (Source: Ericsson)
Document for: Approval
Abstract:
Summary of change: An explicit and optimized procedure for event status retrieval is specified. TS 23.502
defines the corresponding NEF service operation.
Convenor comment:

Handle.

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503758 (CR) 23.228 CR1588R1 (Rel-19, 'F'): Updates on HSS Nhss_ImsEventExposure service
(Source: China Mobile)
Document for: Approval
Abstract:
Summary of change: Add a new service operation Nhss_ImsEE_Notify.
Comment: Revision of (Unhandled) S2-2501738. Postponed in parallel session.

Plenary Discussion:

Postponed.

Status: Postponed.

S2-2503580 (CR) 23.228 CR1544R2 (Rel-19, 'F'): Adding more event filters for ADC media type (Source:
Vivo)
Document for: Approval
Abstract:
Summary of change: Refine the granularity of event filters for ADC media type.
Comment: Revision of (Unhandled) S2-2501663.

Plenary Discussion:

Not handled.

Status: Not treated.

3GPP
Report of meeting S2-168

S2-2503701 (CR) 23.228 CR1576R3 (Rel-19, 'F'): HSS handling for subscription with IMS (Source:
Samsung)
Document for: Approval
Abstract:
Summary of change: HSS does subscription with IMS AS if the IMS DC service is enabled for the IMPU HSS
provides NEF address in the notification end point so that IMS AS can send the notification directly to NEF.
Comment: Revision of (Postponed) S2-2502274.

Convenor comment:

Handle.

Parallel discussion:

Revised in parallel session to S2-2503989.

Plenary Discussion:

Noted.

Status: Noted.

S2-2503754 (CR) 23.228 CR1548R2 (Rel-19, 'F'): Correction of detection criteria for event exposure
(Source: China Mobile)
Document for: Approval
Abstract:
Summary of change: Event detection criteria are updated to include the success of media resource
reservation in the criteria. Editorial changes are proposed.
Comment: Revision of (Unhandled) S2-2501731.

Plenary Discussion:

Not handled.

Status: Not treated.

KI#2: IMS capability exposure for DC session

S2-2502913 (CR) 23.228 CR1604 (Rel-19, 'F'): KI#2: Generalizing Information Retrieval (Source: Ericsson)
Document for: Approval
Abstract:
Summary of change: Make the service generic to retrieve any information stored in HSS.
Convenor comment:

Handle.

Parallel discussion:

Revised in parallel session to S2-2503990.

Revised in parallel session to S2-2504212.

Last sentence moved into a note. Revised in parallel session to S2-2504247.

Plenary Discussion:

Samsung sustained their objection to this CR. This was then noted.

Samsung statement for their objection:

Any other use cases to add new input parameter of this service operation has not been justified.

Status: Noted.

3GPP
Report of meeting S2-168

S2-2503695 (DISCUSSION) Discussion on AsInfoGet service operation. (Source: Samsung)

Document for: Information
Abstract:
For the NG_RTC_Ph2 feature, there is mechanism defined how the DC AS can provide the request to NEF
initiate one standalone bootstrap DC session or adding application DC to an existing IMS session etc. In this
case NEF queries the HSS to know the IMS AS address serving the user (i.e. IMPU) by using the
Nhss_ImsUECM_AsInfoGet service operation.
Convenor comment:

Handle.

Plenary Discussion:

Plenary Discussion:

Not handled.

Status: Not treated.

3GPP
Report of meeting S2-168

S2-2502915 (CR) 23.228 CR1606 (Rel-19, 'F'): KI#2: Corrections to DC AS initiated Standalone ADC
Session Creation (Source: Ericsson)
Document for: Approval
Abstract:
Summary of change: Correct the optionality of some flows. Correct interface. Using correct event name.
Include AF Identifier.
Convenor comment:

Merge into S2-2503098?

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2502916 (CR) 23.228 CR1607 (Rel-19, 'F'): KI#2: Corrections to DC AS initiated IMS Session Update
Procedures (Source: Ericsson)
Document for: Approval
Abstract:
Summary of change: Ensure NEF authorizes an incoming request prior to executing the procedure. Correct
optionality of some flows. Some response are mandatory but shown as optional.
Convenor comment:

Merge into S2-2503098?

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503098 (CR) 23.228 CR1617 (Rel-19, 'F'): KI#2: Correction of procedures in clause AG (Source: Nokia)
Document for: Approval
Abstract:
Summary of change: Main changes: Moving response from NEF to DC AS after response from IMS AS is
received to avoid potential extra notifications from NEF to DC AS in case an error occurs in the network.
Clarify that the UE(s) receive sufficient inforamtion in the SIP INVITE to decide from which BDC to download
the DC application.
Parallel discussion:

Revised in parallel session to S2-2503991.

Step 13 of 1st change. Revised in parallel session to S2-2504213.

Revised in parallel session to S2-2504248.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

3GPP
Report of meeting S2-168

Status: Not treated.

S2-2503167 (CR) 23.228 CR1598R1 (Rel-19, 'F'): KI#3: Updates on the ADC Interworking via DC AS
procedure (Source: Samsung)
Document for: Approval
Abstract:
Summary of change: The DCSF indicates to IMS AS that the P2P ADC needs to be changed to P2A ADC
when the IMS DC interworking action is required. The IMS AS changes the P2P ADC offer from UE to P2A
ADC offer by modifying the endpoint type from 'UE' to 'Server'. The IMS AS provides P2A ADC accept
answer to the UE. When the IMS AS does not support change of ADC session type, then the IMS AS can
reject the P2P ADC request. In step 10, the box extended to cover UE#1.
Comment: Revision of (Unhandled) S2-2502136.

Convenor comment:

Handle.

Plenary Discussion:

Not handled.

Status: Not treated.

3GPP
Report of meeting S2-168

S2-2503755 (CR) 23.228 CR1551R2 (Rel-19, 'F'): Updates on procedure and service of DC interworking via
DC AS (Source: China Mobile)
Document for: Approval
Abstract:
Summary of change: Use Nimsas_MediaControl_MediaInstruction service operation in step 6a with the
indication of DC interworking simultaneously with P2A media resource reservation, to trigger the notification
from the IMS AS to DC AS; Enhance the existing procedure of P2A DC establishment to indicate DC AS that
the DC connection being established is for DC interworking. UE#2 information is included by IMS AS in the
notification to DC AS, not notified by DCSF. Correct step 8 with Nimsas_SessionEventControl_Notify
response. Add interworking indication in Nimsas_MediaControl_MediaInstruction service operation.
Comment: Revision of (Unhandled) S2-2501732.

Convenor comment:

Handle.

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503169 (CR) 23.228 CR1600R1 (Rel-19, 'F'): KI#3: Updates on interworking with MTSI UE procedures
(Source: Samsung)
Document for: Approval
Abstract:
Summary of change: The event ID is corrected to align with clause AD.2.5.2. The event notification steps are
corrected for consistency between AC.7.9.3 and AC.7.9.4. The event description in AD.2.5.2 is updated to
cover the event notification condition of AC.7.9.4 as well.
Comment: Revision of (Unhandled) S2-2502138.

Convenor comment:

Handle.

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503581 (CR) 23.228 CR1465R4 (Rel-19, 'F'): Update on support of DC interworking (Source: Vivo)
Document for: Approval
Abstract:
Summary of change: Add a new description that the new added video media is for sendonly.
Comment: Revision of (Unhandled) S2-2501664.

Convenor comment:

Handle.

Plenary Discussion:

Not handled.

Status: Not treated.

3GPP
Report of meeting S2-168

Not handled.

Status: Not treated.

S2-2503757 (CR) 23.228 CR1638 (Rel-19, 'F'): Clarification on usage of Avatar ID (Source: China Mobile)
Document for: Approval
Abstract:
Summary of change: Clarify the selected Avatar ID is notified from UE to DC AS during Avatar
communication negotiation; Clarify the selected Avatar ID is used for downloading Avatar representation;
Includes Avatar ID in Avatar Media Specification in Nimsas_MediaControl and Nmf_MRM_Create service
operations. Add 'avatar'in Nimsas_MediaControl service operation.
Convenor comment:

Handle.

3GPP
Report of meeting S2-168

General

S2-2503553 (CR) 23.228 CR1625 (Rel-19, 'F'): Update IMS SBA description to align with other specifications
(Source: Huawei, HiSilicon)
Document for: Approval
Abstract:
Summary of change: Update IMS SBA description to align with TS 23.501.
Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503579 (CR) 23.228 CR1543R2 (Rel-19, 'D'): Abbreviations of ADC and BDC (Source: Vivo)
Document for: Approval
Abstract:
Summary of change: Addition of ADC and BDC in clause 3.3.
Comment: Revision of (Unhandled) S2-2501662.

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503683 (CR) 23.228 CR1557R2 (Rel-19, 'B'): Clarification on DC Application Server (Source: ZTE)
Document for: Approval
Abstract:
Summary of change: Add the function description of DC Application Server.
Comment: Revision of (Unhandled) S2-2501950.

Plenary Discussion:

Not handled.

Status: Not treated.

19.3.1 Extended Reality and Media service (XRM) Phase 2

(FS_XRM_Ph2)
This topic was not on the agenda for this meeting.

19.3.2 Extended Reality and Media service (XRM) Phase 2 (XRM_Ph2)

This agenda item was convened by Dario Tonesi (Qualcomm).

3GPP
Report of meeting S2-168

Liaisons

S2-2502814 (LS IN) LS from CT WG4: LS on MoQ Relay Address in UPF Profile (Source: CT WG4 (C4-
250627))
Document for: Action
Abstract:
Clause 5.37.9.2 of TS 23.501 specifies: The SMF may get the address of MoQ Relay during N4 session
management procedure as defined in the clause 4.4.1 of TS 23.502 [3] or the SMF may get MoQ relay
address related to the PSA UPF from the NRF as described in clause 5.2.7.3.2 of TS 23.502 [3]. In the
former case, the SMF indicates the PSA UPF to provide MoQ relay address in N4 Session
Establishment/Modification Request and the PSA UPF returns MoQ relay address in N4 Session
Establishment/Modification Response. CT WG4 thinks if the SMF can retrieve the MoQ relay address during
N4 session management procedure, the solution to get the MoQ relay address related to the PSA UPF from
the NRF is redundant. CT WG4 would like SA WG2 to provide clarification on the usage of the MoQ relay
address registered in UPF profile, e.g. is it needed for SMF to discover a specific UPF supporting a specific
MoQ relay address? If it is exactly same purpose as the MoQ Relay returned in N4 session management
procedure, CT WG4 kindly asked SA WG2 to re-consider NRF solution to avoid multiple options for the same
functionality. Action: CT WG4 kindly asks SA WG2 group to provide the requested clarifications and to
consider updating stage 2 accordingly.
Comment: Responses drafted in S2-2503093, S2-2503782.

Plenary Discussion:

Final response in S2-2503908.

Status: Replied to.

S2-2503093 (LS OUT) [DRAFT] LS on on MoQ Relay Address in UPF Profile (Source: Nokia)
Document for: Approval
Abstract:
[draft] LS on on MoQ Relay Address in UPF Profile.
Comment: Response to S2-2502814.

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503782 (LS OUT) [DRAFT] LS Reply to CT WG4 on MoQ Relay Address in UPF Profile (Source: China
Mobile)
Document for: Approval
Abstract:
To: CT WG4. Attachments: S2-2503784.
Comment: Response to S2-2502814.

Convenor comment:

Handle.

Parallel discussion:

Attach S2-2503907; Refer to 'agreed CR'. Revised in parallel session to S2-2503908.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503339 (LS OUT) [DRAFT] LS Reply on Transport Level Marking on N3/N9 (Source: SAMSUNG)
Document for: Approval
Abstract:
To: CT WG4.
Comment: Response to S2-2502815.

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503438 (LS OUT) [DRAFT] Reply LS on Transport Level Marking based on PDU Set Importance
(Source: Nokia)
Document for: Approval
Abstract:
To: CT WG4. Attachments: TS 23.501 CR6221.
Comment: Response to S2-2502815.

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503547 (LS OUT) [DRAFT] LS out CT WG4 on Transport Level Marking on N3/N9 (Source: Lenovo)
Document for: Approval
Abstract:
To: CT WG4. Attachments: CR6230(TS23.501).
Comment: Response to S2-2502815.

Convenor comment:

Handle - use as baseline. . Content to be adapted to agreement.

Parallel discussion:

Revised in parallel session to S2-2503910.

Revised in parallel session to S2-2504162.

Revised in parallel session to S2-2504230.

Plenary Discussion:

Postponed.

Status: Postponed.

3GPP
Report of meeting S2-168

S2-2503885 (LS OUT) [DRAFT] LS Reply on Transport Level Marking on N3N9 (Source: Xiaomi)
Document for: Approval
Abstract:
To: CT WG4.
Comment: Response to S2-2502815.

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503208 (CR) 23.501 CR6193 (Rel-19, 'F'): Triggering of Transport Level Marking based on PDU Set
Importance in I-SMF (Source: Ericsson)
Document for: Approval
Abstract:
Summary of change: When the I-SMF is notified that PDU Set handling is configured for the QoS flow by the
presence of PDU Set QoS parameters in the QoS profile or a DL PDU Set Information Marking Support
Indication, it may instruct the I-UPF to derive the transport level packet marking of the outgoing N3 downlink
packet based on the one of the incoming N9 downlink packet.
Convenor comment:

Handle - use as baseline. . Content to be adapted to agreement.

Parallel discussion:

Do we want an explicit indication to I-UPF? Revised in parallel session to S2-2503909.

Applicable only to PDU set level marking? Revised in parallel session to S2-2504229.

Plenary Discussion:

Postponed.

Status: Postponed.

S2-2503336 (CR) 23.501 CR6210 (Rel-19, 'F'): Transport level packet marking operation at I-SMF/I-UPF
(Source: Samsung)
Document for: Approval
Abstract:
Summary of change: It is clarified I-SMF/I-UPF operation for transport level packet marking values
considering PDU Set Importance is same as I-SMF/I-UPF.
Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503439 (CR) 23.501 CR6221 (Rel-19, 'F'): Correction on PDU set based DSCP marking (Source:
Nokia)
Document for: Approval
Abstract:
Summary of change: Clarify that the I-UPF transport level marking operation relies simply on what is
received from N9.
Comment: Merged into S2-2503909.

Parallel discussion:

Merged.

Status: Merged.

3GPP
Report of meeting S2-168

S2-2503545 (CR) 23.501 CR6230 (Rel-19, 'F'): Corrections for 23.501 Transport Level Marking on N3/N9
(Source: Lenovo)
Document for: Approval
Abstract:
Summary of change: Remove the following sentence to avioid ambiguity When an I-SMF/I-UPF is inserted in
the PDU Session, the I-SMF may instruct the I-UPF to derive the transport level packet marking of the
outgoing N3 downlink packet based on the transport level packet marking of the incoming N9 downlink
packet.
Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503883 (CR) 23.501 CR6273 (Rel-19, 'F'): XRM_Ph2_KI3 Update of PSI based DSCP Marking (Source:
Xiaomi)
Document for: Approval
Abstract:
Summary of change: Removed the description on I-SMF/I-UPF in 23.501 to avoid the ambiguity.
Plenary Discussion:

Not handled.

Status: Not treated.

S2-2502820 (LS IN) LS from RAN WG2: LS on uplink rate control (Source: RAN WG2 (R2-2501347))
Document for: Action
Abstract:
For XR rate control, RAN WG2 discussed how the gNB gets the information of QoS flows which are subject
to uplink rate control, i.e., whether the information is from CN or UE, and agreed that: RAN WG2 assumes
for XR rate control, the gNB receives QoS flow information from the CN, specifying which QoS flows are
subject to uplink rate control (i.e., Option 2). Send an LS to RAN WG3 and SA WG2. Action: RAN WG2
respectfully asks SA WG2 and RAN WG3 to take the above decision into consideration for further work on
XR uplink rate control and provide feedback.
Comment: Response drafted in S2-2503008, S2-2503148, S2-2503213, S2-2503335, S2-2503393.

Plenary Discussion:

Final response in S2-2504252.

Status: Replied to.

S2-2503008 (LS OUT) [DRAFT] LS reply on uplink rate control for XR service (Source: Lenovo)
Document for: Approval
Abstract:
To: RAN WG2. CC: SA WG4, RAN WG3. Attachments: CR 6173 5395 1531.
Comment: Response to S2-2502820.

Plenary Discussion:

Not handled.

Status: Not treated.

3GPP
Report of meeting S2-168

S2-2503148 (LS OUT) [DRAFT] LS reply on uplink rate control (Source: vivo)
Document for: Approval
Abstract:
Reply to the LS on uplink rate control.
Comment: Response to S2-2502820.

Convenor comment:

Handle - use as baseline. . Content to be adapted to agreement.

Parallel discussion:

Focus on: - indicate we can indicate which QoS flow is subject to UL rate control - new info vs. existing info?
- ask clarifications on scenario and on GBR vs. non- GBR. Revised in parallel session to S2-2503931.

Revised in parallel session to S2-2504163.

Revised in parallel session to S2-2504252.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503213 (LS OUT) [DRAFT] LS Reply on uplink rate control (Source: Ericsson)
Document for: Approval
Abstract:
Response to R2-2501347 LS on uplink rate control.
Comment: Response to S2-2502820.

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503335 (LS OUT) [DRAFT] LS Reply on uplink rate control (Source: SAMSUNG)
Document for: Approval
Abstract:
To: RAN WG2, RAN WG3.
Comment: Response to S2-2502820.

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503393 (LS OUT) [DRAFT] LS reply on uplink rate control (Source: OPPO)
Document for: Approval
Abstract:
Reply LS of S2-2502820.
Comment: Response to S2-2502820.

Plenary Discussion:

Not handled.

Status: Not treated.

3GPP
Report of meeting S2-168

S2-2503005 (CR) 23.501 CR6173 (Rel-19, 'B'): 23.501 Support of uplink rate control for QoS flows at RAN
(Source: Lenovo)
Document for: Approval
Abstract:
Summary of change: Add the descriptions of provisioning the uplink rate control indication associated with
the QoS flows from CN to RAN.
Convenor comment:

Handle - use as baseline. . Content to be adapted to agreement.

Parallel discussion:

Revised in parallel session to S2-2503932.

Plenary Discussion:

Postponed.

Status: Postponed.

S2-2503006 (CR) 23.502 CR5395 (Rel-19, 'B'): 23.502 Support of uplink rate control for QoS flows at RAN
(Source: Lenovo)
Document for: Approval
Abstract:
Summary of change: Add Uplink Rate Control Indication in the procedure from AF to NG-RAN, via PCF and
SMF Modify the procedure, including PDU session establishment, PDU session modification, AF session
with required QoS, PCF and NEF service.
Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503007 (CR) 23.503 CR1531 (Rel-19, 'B'): 23.503 Support of uplink rate control for QoS flows at RAN
(Source: Lenovo)
Document for: Approval
Abstract:
Summary of change: Following enhancements are introduced: Add the uplink rate control indication into the
PCC rules. Add the descriptions of PCF provisioning uplink rate control indication to SMF Align with the
23.501 CR.
Convenor comment:

Handle - use as baseline. . Content to be adapted to agreement.

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503210 (CR) 23.501 CR6194 (Rel-19, 'C'): Indication of Rate-Adaptable QoS Flows to NG-RAN
(Source: Ericsson)
Document for: Approval
Abstract:
Summary of change: Specify that 5GC may provide an indication of rate-adapatable QoS flows to NG-RAN.
Comment: Postponed in parallel session.

Plenary Discussion:

Postponed.

Status: Postponed.

3GPP
Report of meeting S2-168

S2-2503211 (CR) 23.503 CR1535 (Rel-19, 'C'): Indication of Rate-Adaptable QoS Flows to NG-RAN
(Source: Ericsson)
Document for: Approval
Abstract:
Summary of change: Specify that the PCF may provide an indication of service data flows that may be
subject to rate adaptation within the PCC rule, to the SMF.
Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503212 (CR) 23.502 CR5419 (Rel-19, 'C'): Indication of Rate-Adaptable QoS Flows to NG-RAN
(Source: Ericsson)
Document for: Approval
Abstract:
Summary of change: Specify that 5GC may provide an indication of rate-adapatable QoS flows to NG-RAN.
Convenor comment:

Handle - use as baseline. . Content to be adapted to agreement.

Parallel discussion:

Revised in parallel session to S2-2503933.

Note 4 reads as 'The AF can subscribe to reporting for change for the support of QoS monitoring as
described in clause 5.45.1 [...]'. Revised in parallel session to S2-2504164.

Revised in parallel session to S2-2504231.

Revised in parallel session to S2-2504232.

Remove highlights and fix formatting of original text in second change. Revised in parallel session to S2-
2504417.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

3GPP
Report of meeting S2-168

S2-2503519 (CR) 23.501 CR6226 (Rel-19, 'F'): Clarifications for available bitrate exposure (Source: Huawei,
HiSilicon)
Document for: Approval
Abstract:
Summary of change: Addition of details about the conditions for the reporting. Addition of behavior during
handover.
Comment: Merged into S2-2503933.

Parallel discussion:

Merged.

Status: Merged.

S2-2503520 (CR) 23.503 CR1545 (Rel-19, 'F'): Clarifications for available bitrate exposure (Source: Huawei,
HiSilicon)
Document for: Approval
Abstract:
Summary of change: Clarification that the list of thresholds is an ordered list with increasing values.
Clarification of some wording.
Convenor comment:

Handle.

Parallel discussion:

Remove 'and also'? Revised in parallel session to S2-2503935.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503522 (CR) 23.501 CR6227 (Rel-19, 'F'): Clarifications for rate limitation exposure (Source: Huawei,
HiSilicon)
Document for: Approval
Abstract:
Summary of change: The details of the PCF action are replaced by a reference to 23.503. The scenarios are
better described and their limitations are clarified.
Parallel discussion:

Revised in parallel session to S2-2504165.

Revised in parallel session to S2-2504418.

Plenary Discussion:

This was reviewed and approved.

Status: Approved.

3GPP
Report of meeting S2-168

S2-2503523 (CR) 23.503 CR1547 (Rel-19, 'F'): Clarifications for rate limitation exposure (Source: Huawei,
HiSilicon)
Document for: Approval
Abstract:
Summary of change: The conditions for the reporting are clarified in 6.1.3.18 and the determination details
are removed from that clause. The details of the determination are clarified in clause 6.1.3.27.1.
Convenor comment:

Handle.

Parallel discussion:

Revised in parallel session to S2-2503936.

Revised in parallel session to S2-2504166.

Plenary Discussion:

This was left for off-line discussion and revised to S2-2504481.

S2-2503435 (CR) 23.503 CR1538 (Rel-19, 'F'): Indication of PDU Set QoS in Notification Control (Source:
Nokia)
Document for: Approval
Abstract:
Summary of change: Support SMF[/NG-RAN] indication of PDU set QoS support.
Convenor comment:

Handle.

Parallel discussion:

Revised in parallel session to S2-2503938.

Plenary Discussion:

Noted.

Status: Noted.

S2-2503147 (CR) 23.501 CR6185 (Rel-19, 'F'): KI#1, Update to Notification Control and Alternative QoS
profile with PDU Set QoS (Source: Vivo, Nokia)
Document for: Approval
Abstract:
Summary of change: Update the text as: When the NG-RAN has received the PDU Set QoS parameters
PSDB and PSER for UL and/or DL (as described in clause 5.7.7) , If if the NG-RAN determines that only in
one direction the GFBR, the PDB or the PER cannot be fulfilled and PDU Set QoS handling is not applied in
this direction, or only in one direction the GFBR, the PSDB or the PSER cannot be fulfilled and PDU Set QoS
handling is applied in this direction, the NG-RAN shall indicate that 'GFBR can no longer be guaranteed'
together with the corresponding direction.
Convenor comment:

Merge into S2-2503589?

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503206 (CR) 23.503 CR1533 (Rel-19, 'F'): Correction concerning presence of PDU Set Control
information without a Protocol Description (Source: Ericsson)
Document for: Approval
Abstract:
Summary of change: Modify the text to clarify that the Protocol Description can be provided with or without
PDU Set Control Information, instead of stating 'and/or'.
Convenor comment:

Handle.

Parallel discussion:

Revised in parallel session to S2-2503939.

Revised in parallel session to S2-2504167.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

3GPP
Report of meeting S2-168

S2-2503328 (CR) 23.501 CR6206 (Rel-19, 'F'): Alternative QoS profile handling considering PDU Set QoS
parameters (Source: Samsung)
Document for: Approval
Abstract:
Summary of change: NG-RAN's behavior is clarified as, if PDU Set based QoS handling is applied, whether
the GFBR, PSDB and PSER for UL and/or DL can be fulfilled in the respective direction(s) (i.e. for all
Notification control scenarios described in clause 5.7.2.4), the NG-RAN shall also apply the value of the
optional QoS parameter present in an Alternative QoS Profile instead of the corresponding QoS parameter's
value in the QoS Profile.
Convenor comment:

Merge into S2-2503589?

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503329 (CR) 23.501 CR6207 (Rel-19, 'F'): Notification control on use of PDU Set QoS parameters
(Source: Samsung)
Document for: Approval
Abstract:
Summary of change: It is clarified when the PDU Set QoS paramters PSDB and PSER are provisioned to
5GS, SMF notifies the PCF if the PDU Set based QoS handling is not used in the NG-RAN or if it is used
again.
Convenor comment:

Merge into S2-2503433/4?

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503334 (CR) 23.501 CR6209 (Rel-19, 'F'): PDU Set based handling without PDU Set QoS parameters
(Source: Samsung)
Document for: Approval
Abstract:
Summary of change: It is clarified the NOTE is applied only when the PDU Set QoS paramters have been
provisioned.
Convenor comment:

Handle.

Parallel discussion:

Improve wording of NOTE. Revised in parallel session to S2-2503940.

Fix cover page and typos in NOTE. Revised in parallel session to S2-2504168.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

3GPP
Report of meeting S2-168

S2-2503524 (CR) 23.501 CR6228 (Rel-19, 'F'): Clarifications for QoS Notification Control with direction
information (Source: Huawei, HiSilicon)
Document for: Approval
Abstract:
Summary of change: In clause 5.7.1.2a, the description is slightly reworded to improve the readability. In
clause 5.7.2.4.1a, the following changes are done: The description about the sending of direction information
is moved up and slightly reworded to better fit to the existing wording. A description is added to clarify the
scenarios in which a direction information is not sent as it is unnecessary for the AF. A duplicated statement
about how PSDB and PSER have to be used is removed.
Convenor comment:

Merge into S2-2503589?

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503525 (CR) 23.503 CR1548 (Rel-19, 'F'): Clarifications for QoS Notification Control with direction
information (Source: Huawei, HiSilicon)
Document for: Approval
Abstract:
Summary of change: Description about the forwarding of the direction information is added to the event
reporting clauses. The details of the PCF actions are clarified, appropriate terminology is used and the PCC
rule additions are simplified.
Convenor comment:

Handle.

Parallel discussion:

Revised in parallel session to S2-2503942.

Revised in parallel session to S2-2504169.

Revised in parallel session to S2-2504420.

Plenary Discussion:

This was reviewed and approved.

Status: Approved.

3GPP
Report of meeting S2-168

S2-2503589 (CR) 23.501 CR6233 (Rel-19, 'F'): QoS Notification Control of PDU Set QoS with only one
direction (Source: CATT)
Document for: Approval
Abstract:
Summary of change: If the NG-RAN determines that only in one direction the GFBR, the PDB or the PER
cannot be fulfilled (or can be fulfilled again), the NG-RAN shall indicate that 'GFBR can no longer (or can
again) be guaranteed' together with the corresponding direction to the SMF (via the AMF). The SMF
forwards the 'GFBR can no longer (or can again) be guaranteed' together with the corresponding direction in
the Npcf_SMPolicyControl_Update request to the PCF, and the PCF notifies the AF (via the NEF) that the
'GFBR can no longer (or can again) be guaranteed with the corresponding UL or DL direction' in the
Naf_EventExposure or Nnef_EventExposure_Notify service as described in clause 6.1.3.27.4 of TS23.503.
Convenor comment:

Handle - use as baseline.

Parallel discussion:

Revised in parallel session to S2-2503941.

Revised in parallel session to S2-2504170.

Revised in parallel session to S2-2504419.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503590 (CR) 23.503 CR1549 (Rel-19, 'F'): Policy Control on QoS Notification Control of PDU Set QoS
with only one direction (Source: CATT)
Document for: Approval
Abstract:
Summary of change: If the PDU Set QoS Parameters are included in (Alternative) QoS Profile(s), when the
SMF receives an explicit notification from (R)AN indicating that GFBR of the QoS Flow can no longer (or can
again) be guaranteed with UL or DL direction (see clause 5.7.2.4.1a of TS 23.501 [2]), the SMF shall report
that GFBR of the QoS Flow can no longer (or can again) be guaranteed or GFBR of the QoS Flow can no
longer (or can again) be guaranteed with UL or DL direction accordingly to the PCF. The PCF shall report to
the AF the affected media flow and provides the indication that QoS targets can no longer (or can again) be
fulfilled with the corresponding direction.
Convenor comment:

Merge into S2-2503525?

Plenary Discussion:

Not handled.

Status: Not treated.

3GPP
Report of meeting S2-168

3GPP
Report of meeting S2-168

KI#2: PDU Set information identification for end-to-end encrypted XRM traffic

S2-2503096 (CR) 23.501 CR6072R1 (Rel-19, 'F'): Correction on the Support of MoQ (Source: Nokia)
Document for: Approval
Abstract:
Summary of change: Specify the overall set of features that are or that are not specified In this release, how
to deal with the case where the UE acts as a MoQ PUBLISHER is not specified. In this release, how to deal
with the case where the UPF acts as a content cache is not specified. In this release, the mappings between
the MoQ Metadata and the PDU Set Information is not specified and is based on local configuration and
implementations Different MoQ application servers can correspond to a MoQ relay deployed on a PSA UPF.
Comment: Revision of (Unhandled) S2-2501470.

Convenor comment:

Handle.

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503207 (CR) 23.503 CR1534 (Rel-19, 'F'): MoQ missing from the Protocol Description (Source:
Ericsson)
Document for: Approval
Abstract:
Summary of change: Media over QUIC is added to the Protocol Description in the PCC rule information in
Table 6.3.1.
Convenor comment:

Handle.

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503470 (CR) 23.502 CR5453 (Rel-19, 'F'): Update on PDU session establishment procedure for MoQ
(Source: Huawei, HiSilicon)
Document for: Approval
Abstract:
Summary of change: Some clarification on 'If a PCC Rule indicates that Media over QUIC (MoQ) is
requested by setting Protocol Description as Media over QUIC Transport SMF may select a PSA UPF that
supports MoQ relay functionality e.g. using NRF for this selection.' of step 8.
Convenor comment:

Handle.

Plenary Discussion:

Not handled.

Status: Not treated.

3GPP
Report of meeting S2-168

KI#3: Leverage PDU Set QoS information for DSCP marking over N3/N9 in the transport network

S2-2503226 (CR) 23.501 CR6091R1 (Rel-19, 'F'): KI#3: Align the mapping of PSI value to DSPC Drop
Precedence setting (Source: China Mobile)
Document for: Approval
Abstract:
Summary of change: Modify the 'NOTE 1' of 5.8.2.7 to reflect the better mapping alignment between PSI
values and DSPC Drop Precedences.
Comment: Revision of (Unhandled) S2-2501632.

Convenor comment:

Merge into S2-2503526.

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503526 (CR) 23.501 CR6229 (Rel-19, 'F'): Clarifications for PDU Set QoS information based DSCP
marking (Source: Huawei, HiSilicon)
Document for: Approval
Abstract:
Summary of change: Clarifications for the usage of the list of transport level packet marking values by SMF
and UPF.
Convenor comment:

Handle.

Plenary Discussion:

Not handled.

Status: Not treated.

KI#4: Traffic detection and QoS flow mapping for multiplexed data flows

S2-2503228 (CR) 23.501 CR6095R1 (Rel-19, 'F'): KI#4: Resolve the incorrect multiplex support in NOTE
(Source: China Mobile)
Document for: Approval
Abstract:
Summary of change: Modify the 'NOTE 2' of 5.37.5.1 to reflect the support of multiple media flows multiplxed
on the same transport layer connection, but the media-flow multiplexing across different transport protocols
is continuously not supported.
Comment: Revision of (Unhandled) S2-2501641.

Status: Not treated.

Multi Modal Awareness at RAN

S2-2503560 (CR) 23.502 CR5455 (Rel-19, 'F'): Update the procedures with Multi-modal service ID (Source:
Vivo)
Document for: Approval
Abstract:
Summary of change: For the multi-modal services, in order to make the related procedures completed, it is
proposed to add the Multi-modal service ID in the procedures in clauses 4.3.2.2.1,4.15.6.6.
Convenor comment:

Merge into S2-2503785?

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503783 (CR) 23.501 CR6258 (Rel-19, 'F'): Clarification on provisioning Multi-modal Service ID to NG-
RAN (Source: China Mobile)
Document for: Approval
Abstract:
Summary of change: Add clarifications on the support of providing MMSID on UL and/or DL directions.
Convenor comment:

Handle.

Plenary Discussion:

Not handled.

Status: Not treated.

3GPP
Report of meeting S2-168

S2-2503785 (CR) 23.502 CR5474 (Rel-19, 'F'): Support of providing MMSID from 5GC to NG-RAN (Source:
China Mobile)
Document for: Approval
Abstract:
Summary of change: Add descriptions of PCF providing MMSID in PDU Session Modification procedure;
Add clarifications on providing MMSID in UL and/or DL directions.
Convenor comment:

Handle - use as baseline.

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503786 (CR) 23.503 CR1553 (Rel-19, 'F'): Clarification of providing MMSID from 5GC to NG-RAN
(Source: China Mobile)
Document for: Approval
Abstract:
Summary of change: Add clarifications of providing MMSID from PCF to SMF on UL and/or DL directions.
Convenor comment:

Handle.

Plenary Discussion:

Not handled.

Status: Not treated.

19.4.1 Feasibility Study on 5GS Enhancement for Energy Efficiency and

Energy Saving (FS_EnergySys)
This topic was not on the agenda for this meeting.

19.4.2 5GS Enhancement for Energy Efficiency and Energy Saving

(EnergySys)
This agenda item was convened by Wanqiang Zhang (Huawei).

LS In/Out - Renewable energy

S2-2502843 (LS IN) LS from SA WG5: LS reply to LS on energy information collection from OAM to EIF
(Source: SA WG5 (S5-250843))
Document for: Action
Abstract:
SA WG5 thanks SA WG2 for your LS on energy information collection from OAM to EIF. SA WG5 would like
to reply to SA WG2 questions: {. .} Actions: To SA WG2: SA WG5 kindly requests SA WG2 to take the above
information into consideration.
Comment: Noted in parallel session.

Parallel discussion:

This was noted in parallel session.

Status: Noted.

3GPP
Report of meeting S2-168

S2-2502817 (LS IN) LS from TSG CT: LS reply to LS on energy information collection from OAM to EIF
(Source: TSG CT (CP-250253))
Document for: Information
Abstract:
CT thanks SA WG5 for the LS on energy information collection from OAM to EIF. In the SA WG5 reply to SA
WG2 question 3, SA WG5 states: 'SA WG5 would like to highlight that no progress can be achieved on this
topic until the Stage 3 work on EIF is completed in relevant CT WGs.' Further, in LS action, SA WG5 kindly
requests CT TSG to inform SA WG5 of the progress of the Stage 3 work on EIF. In response to the above
request, CT would like to provide the following information: A new CT WID, EnergySys, was approved in
CT#107 which in its objective includes work for CT WG3 and CT WG4. In addition to impact on existing
technical specifications under CT WG3 and CT WG4, a new CT WG3 TS has been created, 3GPP TS
29.566 5G System; Energy Information Function Services; Stage 3. Normative work has started with
approved CRs in CT#107.
Comment: Noted in parallel session.

Parallel discussion:

This was noted in parallel session.

Status: Noted.

S2-2503639 (CR) 23.501 CR6243 (Rel-19, 'F'): Solve the editor s note about the renewable energy
information (Source: Vivo)
Document for: Approval
Abstract:
Summary of change: Remove the EN related with renewable energy information.
Parallel discussion:

Revised in parallel session to S2-2503994.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503806 (CR) 23.501 CR6261 (Rel-19, 'F'): Support of renewable energy information (Source: Samsung)
Document for: Approval
Abstract:
Summary of change: Remove the EN and update the text to include the collection of the renewable energy
information for the RAN and NFs via OAM.
Comment: Noted in parallel session.

Parallel discussion:

This was noted in parallel session.

Status: Noted.

3GPP
Report of meeting S2-168

Energy Information Collection

S2-2503054 (CR) 23.502 CR5406 (Rel-19, 'F'): Update on Energy Consumption information collection
procedure (Source: ETRI)
Document for: Approval
Abstract:
Summary of change: - Steps using Nupf_EventExposure service are additionally included in the existing step
between SMF and UPF to ccollect data volume.
Comment: Noted in parallel session.

Parallel discussion:

This was noted in parallel session.

Status: Noted.

S2-2503586 (DISCUSSION) Discussion on the collection and exposure of data usage. (Source: Nokia)
Document for: Agreement
Abstract:
-
Comment: Noted in parallel session.

Parallel discussion:

This was noted in parallel session.

Status: Noted.

S2-2503588 (CR) 23.502 CR5458 (Rel-19, 'F'): Energy Consumption information collection procedure
clarification (Source: Nokia)
Document for: Approval
Abstract:
Summary of change: this CR clarifies the SMF and the UPF interact via TS 29.244 procedures.
Convenor comment:

Handle (Alt.#2).

Parallel discussion:

Revised in parallel session to S2-2503996.

Revised in parallel session to S2-2504080.

Add more source company. Revised in parallel session to S2-2504297.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

3GPP
Report of meeting S2-168

S2-2503629 (CR) 23.501 CR6240 (Rel-19, 'F'): On the report of SMF to EIF for user-plane energy
consumption calculation (Source: Huawei, HiSilicon)
Document for: Approval
Abstract:
Summary of change: Add the description on how does the SMF provdes EIF the information for user-plane
energy consumption calculation in 4.29.2.
Comment: Confirm Specification Number - CR states 23.502! Updated in parallel session with new TS and
CR number in S2-2503997. Noted in parallel session.

Convenor comment:

Handle (Periodical reporting).

Parallel discussion:

New CR number needed. Updated in parallel session with new TS and CR number in S2-2503997. Noted in
parallel session.

Remove the change on change. Fix the typo. Revised in parallel session to S2-2504298.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503632 (CR) 23.501 CR6242 (Rel-19, 'F'): Clarification on the EventExposure service operation of SMF
(Source: Huawei, HiSilicon)
Document for: Approval
Abstract:
Summary of change: The changes define that SMF and UPF interaction for collecting the Data Volume
information to be provided to EIF is based on current URR N4 mechanism where SMF may also needs to
generate the PDR and the URR, if no PCC rules for the SDF corresponding to the EIF request are already
present.
Convenor comment:

Handle as baseline.

Parallel discussion:

Revised in parallel session to S2-2503998.

Revised in parallel session to S2-2504299.

Plenary Discussion:

Postponed.

Status: Postponed.

3GPP
Report of meeting S2-168

S2-2503628 (CR) 23.501 CR6239 (Rel-19, 'F'): Report of SMF to EIF for user-plane energy consumption
calculation (Source: Huawei, HiSilicon)
Document for: Approval
Abstract:
Summary of change: Add the description on how does the SMF provdes EIF the information for user-plane
energy consumption calculation in 5.51.2.2.2.
Comment: Merged into S2-2503998.

Convenor comment:

Merge into S2-2503632.

Parallel discussion:

Merged.

Status: Merged.

S2-2503457 (CR) 23.501 CR6222 (Rel-19, 'F'): Correction on the granularity description and clause
reference (Source: ZTE)
Document for: Approval
Abstract:
Summary of change: Make alignment in the S-NSSAI of the UE level exposure. Correct the table title.
Parallel discussion:

Revised in parallel session to S2-2503999.

Only keep the second change and undo all the other changes. Revised in parallel session to S2-2504300.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503572 (CR) 23.502 CR5456 (Rel-19, 'F'): Correction on energy consumption information collection and
exposure (Source: CATT)
Document for: Approval
Abstract:
Summary of change: Modify the description on granularities of energy consumption information to align with
TS 23.501. Modify the description on the EIF collecting energy consumption information. Remove 'as Target
of Event Reporting' from Neif_EventExposure service description. Editorial modifications.
Convenor comment:

Handle as baseline.

Parallel discussion:

Revised in parallel session to S2-2504000.

Undo the change on the note in clause 4.29.2. Revised in parallel session to S2-2504301.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

3GPP
Report of meeting S2-168

3GPP
Report of meeting S2-168

S2-2503459 (CR) 23.501 CR6223 (Rel-19, 'F'): Clarification on the OAM input (Source: ZTE)
Document for: Approval
Abstract:
Summary of change: Remove the EN on the renewable energy information. The EIF is is locally configured
with mapping between gNB/UPF ID and DN.
Parallel discussion:

Revised in parallel session to S2-2503995.

Revised in parallel session to S2-2504302.

Revised in parallel session to S2-2504339.

Revised in parallel session to S2-2504348.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

SMF/gNB change, etc.

S2-2503805 (CR) 23.501 CR6260 (Rel-19, 'F'): Energy consumption information collection for new PDU
Session (Source: Samsung)
Document for: Approval
Abstract:
Summary of change: Clarifications of the energy consumption information collection when the PDU session
is established/released.
Convenor comment:

Handle as baseline.

Parallel discussion:

Revised in parallel session to S2-2504001.

Also, the EIF subscribes to the UDM to be notified with the applicable SMFs. Upon release of a PDU
session, the SMF terminates subscriptions related to the PDU session. Revised in parallel session to S2-
2504303.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

3GPP
Report of meeting S2-168

S2-2503630 (CR) 23.501 CR6241 (Rel-19, 'F'): Update on EC collection upon PDU Session management
(Source: Huawei, HiSilicon)
Document for: Approval
Abstract:
Summary of change: Add the details on the procedure upon the change on the PDU Session of the UE for
energy consumption calculation.
Comment: Merged into S2-2504001.

Convenor comment:

Merge into S2-2503805.

Parallel discussion:

Merged.

Status: Merged.

S2-2503807 (CR) 23.501 CR6262 (Rel-19, 'F'): Update on the energy consumption information collection
(Source: Vivo)
Document for: Approval
Abstract:
Summary of change: In clause 5.51.2.2.1, UE level granularity is added. In clause 5.51.2.2.3, the term 'NF
level' is changed to 'node level' for consistency. When the serving gNB and/or the (I-)UPF(s) of the UE are
changed, the serving gNB ID and (I-)UPF ID(s) will be updated to the EIF through SMF(s). It is further
clarified that the EIF will then send the updated serving gNB ID and (I-)UPF ID(s) to the OAM. Other editorial
changes.
Convenor comment:

gNB change.

Parallel discussion:

Revised in parallel session to S2-2504002.

CR type to F KEEP the NF. Revised in parallel session to S2-2504304.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

3GPP
Report of meeting S2-168

S2-2503631 (CR) 23.502 CR5464 (Rel-19, 'F'): On the report of SMF to EIF for user-plane energy
consumption calculation (Source: Huawei, HiSilicon)
Document for: Approval
Abstract:
Summary of change: Add the details on the procedure upon the change on the PDU Session of the UE for
energy consumption calculation.
Convenor comment:

Handle as baseline.

Parallel discussion:

Revised in parallel session to S2-2504003.

Remove the change on change, tidy up. Revised in parallel session to S2-2504305.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503781 (CR) 23.502 CR5473 (Rel-19, 'F'): Energy subscription termination and event exposure in SMF
(Source: China Mobile)
Document for: Approval
Abstract:
Summary of change: Add a new event exposure, and add the procedure that if the PDU session or QoS flow
is released, the subscription can be terminated.
Comment: Merged into S2-2504006.

Convenor comment:

Merge into S2-2503631.

Parallel discussion:

Merged.

Status: Merged.

S2-2503809 (CR) 23.502 CR5475 (Rel-19, 'F'): Collection of energy consumption information for new PDU
session (Source: Samsung)
Document for: Approval
Abstract:
Summary of change: Clarifications of the energy consumption information collection when the PDU session
is established/released.
Comment: Merged into S2-2504003.

Convenor comment:

Merge into S2-2503631.

Parallel discussion:

Merged.

Status: Merged.

3GPP
Report of meeting S2-168

S2-2503737 (CR) 23.501 CR6256 (Rel-19, 'F'): Energy consumption information for access type (Source:
Samsung)
Document for: Approval
Abstract:
Summary of change: Ensure that the energy consumption information is collected only for the 3GPP access.
Parallel discussion:

Revised in parallel session to S2-2504004.

Revised in parallel session to S2-2504306.

Remove the change on change. Remove the other spec impact Tidy up. Revised in parallel session to S2-
2504340.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503740 (CR) 23.502 CR5470 (Rel-19, 'F'): Energy consumption information for access type (Source:
Samsung)
Document for: Approval
Abstract:
Summary of change: Ensure that the energy consumption information is collected only for the 3GPP access.
Parallel discussion:

Revised in parallel session to S2-2504005.

Revised in parallel session to S2-2504317.

Revised in parallel session to S2-2504341.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

3GPP
Report of meeting S2-168

Nsmf_EventExposure

S2-2503593 (CR) 23.502 CR5459 (Rel-19, 'F'): SMF exposure service clarification for Energy Consumption
information collection (Source: Nokia)
Document for: Approval
Abstract:
Summary of change: this CR introduces a new Event ID used for the exposure of usage data based on
caluse 5.51.2 of TS 23.501 requirements.
Convenor comment:

Handle as baseline.

Parallel discussion:

Revised in parallel session to S2-2504006.

Revised in parallel session to S2-2504091.

Convenor comment:

Merge into S2-2503593.

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503736 (CR) 23.502 CR5469 (Rel-19, 'F'): Clarifications on SMF event for information for energy
consumption calculation (Source: Samsung)
Document for: Approval
Abstract:
Summary of change: Add an SMF event ID for information for energy consumption calculation.
Convenor comment:

Merge into S2-2503593.

Plenary Discussion:

Not handled.

Status: Not treated.

Energy Consumption calculation

S2-2503121 (DISCUSSION) Discussion on Energy Consumption model. (Source: NTT DOCOMO)

Document for: Discussion
Abstract:
This paper discuss how the energy consumption model can be more accurate.
Comment: Noted in parallel session.

Parallel discussion:

This was noted in parallel session.

Status: Noted.

S2-2503122 (CR) 23.501 CR6182 (Rel-19, 'F'): Correction of Energy Consumption Model (Source: NTT
DOCOMO)
Document for: Approval
Abstract:
Summary of change: Proposing alternative model for calculation of energy consumption.
Plenary Discussion:

Not handled.

Status: Not treated.

3GPP
Report of meeting S2-168

Energy Information Exposure

S2-2503124 (CR) 23.501 CR6183 (Rel-19, 'F'): Clarification on the reporting period of energy-related
information (Source: NTT DOCOMO)
Document for: Approval
Abstract:
Summary of change: Adding a NOTE to clarify the reporting time window requested by the consumer of EIF
should be in future.
Comment: Agreed in parallel session.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

S2-2503460 (CR) 23.502 CR5449 (Rel-19, 'F'): Resolve the EN in the EIF service (Source: ZTE)
Document for: Approval
Abstract:
Summary of change: Removing the EN in the EIF service.
Parallel discussion:

Revised in parallel session to S2-2504010.

This was agreed in parallel session.

Status: Not treated.

S2-2503780 (CR) 23.502 CR5472 (Rel-19, 'F'): Alignment of Energy indicator in BDT policy (Source: China
Mobile)
Document for: Approval
Abstract:
Summary of change: Adding energy indicator to message flow and adding the clarification sentence in the
procedure to BDT policy determination.
Convenor comment:

Handle as baseline.

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503455 (CR) 23.502 CR5447 (Rel-19, 'F'): Adding Energy indication to BDT procedure and service
operation (Source: ZTE)
Document for: Approval
Abstract:
Summary of change: Adding the energy indicator to the BDT related procedure and service operation.
Convenor comment:

Merge into S2-2503780.

Plenary Discussion:

Not handled.

Status: Not treated.

3GPP
Report of meeting S2-168

S2-2503637 (CR) 23.502 CR5465 (Rel-19, 'F'): Update the procedure for BDT policy decisions (Source:
Vivo)
Document for: Approval
Abstract:
Summary of change: In clause 4.16.7.2, 5.2.5.5.2 and 5.2.6.6.2, it is proposed to add the Energy indicator
and the related descriptions in the procedure and service operations.
Convenor comment:

Merge into S2-2503780.

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503125 (CR) 23.502 CR5240R2 (Rel-19, 'F'): Negotiation for future background data transfer
considering energy (Source: NTT DOCOMO, Toyota, KDDI)
Document for: Approval
Abstract:
Summary of change: - Adding consideration of energy-related information in BDT negotiation in the case of
indication by AF. - Clarifying the interaction between PCF and NWDAF in the procedure figure. - Adding
reference to SA WG5 specification.
Comment: Revision of (Merged and Postponed) S2-2502001.

Plenary Discussion:

Not handled.

Status: Not treated.

19.5.1 Study on MPS for IMS Messaging and SMS services

(FS_MPS4msg)
This topic was not on the agenda for this meeting.

19.5.2 MPS for IMS Messaging and SMS services (MPS4msg)

There were no contributions to this agenda item.

19.6.1 Study on Architecture Enhancements for Vehicle Mounted Relays

Phase 2 (FS_VMR_Ph2)
This topic was not on the agenda for this meeting.

3GPP
Report of meeting S2-168

19.6.2 Architecture Enhancements for Vehicle Mounted Relays Phase 2

(VMR_Ph2)
This agenda item was convened by Andy Bennett (Samsung).

LS from SA WG5 on MWAB-gNB configuration

S2-2502844 (LS IN) LS from SA WG5: LS on MWAB-gNB Configurations (Source: SA WG5 (S5-251090))
Document for: Action
Abstract:
SA WG5 would like to inform SA WG2 that SA WG5 has started discussion on management support for
MWAB. SA WG5 would like to get confirmation on the list of exact (re-)configuration parameters that are
required from OAM server to assist the MWAB-gNB providing information used by MWAB-UE for the BH
PDU Session(s) management via URSP processing. Action: SA WG5 kindly asks SA WG2 to provide
answer to the above questions.
Comment: Responses drafted in S2-2502975, S2-2503817, S2-2503873.

Convenor comment: Replied in S2-2503817.

Parallel discussion:

The proposed replies were reviewed.

Plenary Discussion:

Final response in S2-2504380.

Status: Replied to.

S2-2502975 (LS OUT) [DRAFT] Reply LS on MWAB-gNB Configuration (Source: Ericsson)

Document for: Approval
Abstract:
Provide SA WG2 answers to SA WG5 related to the MWAB-gNB configuration.
Comment: Response to S2-2502844.

Convenor comment: Merge into S2-2503817?

Parallel discussion:

Merged into S2-2504101.

Status: Merged.

3GPP
Report of meeting S2-168

S2-2503817 (LS OUT) [DRAFT] Reply LS on MWAB-gNB Configurations (Source: Qualcomm Incorporated)
Document for: Approval
Abstract:
Reply LS on MWAB-gNB Configurations.
Comment: Response to S2-2502844.

Convenor comment: HANDLE. Use as the baseline.

Parallel discussion:

This was taken as a basis for the reply LS and was left for off-line discussion and revised, merging S2-
2502975 and S2-2503873, to S2-2504101.

The TS numbers should be added for the references to clauses. Nokia asked for more clarification on the
intention and this was left for off-line discussion and revised to S2-2504380.

This was reviewed and agreed in parallel session. (MCC will add attached CRs).

Plenary Discussion:

This was block approved.

Status: Approved.

LS from CT WG1 on PWS support

S2-2502805 (LS IN) LS from CT WG1: LS on PWS enhancements for MWAB and MBSR (Source: CT WG1
(C1-250820))
Document for: Action
Abstract:
{. . .} CT WG1 would like to remind SA WG2 that CT WG1 is responsible for stage-2 for PWS. Thus, any
stage-2 requirements for PWS need to be agreed by CT WG1. Action: Given that CT WG1 is responsible for
stage-2 for PWS, CT WG1 would like to ask SA WG2 to remove the TS 23.502 statements above (1st
statement from TS 23.502 Rel-18 and Rel-19, 2nd statement from TS 23.502 Rel-19).
Comment: Responses drafted in S2-2502976, S2-2503351.

Parallel discussion:

The proposed reply was reviewed.

Plenary Discussion:

Final response in S2-2504383.

Status: Replied to.

3GPP
Report of meeting S2-168

S2-2502976 (LS OUT) [DRAFT] Reply LS on PWS enhancement for MWAB and MBSR (Source: Ericsson)
Document for: Approval
Abstract:
Provide SA WG2 answer to CT WG1 related to the PWS handling.
Comment: Response to S2-2502805.

Convenor comment: HANDLE. Use as the baseline.

Parallel discussion:

Vodafone commented that the RAN WG3 proposal was for Additional ULI for geographical area rather than
cell area information. Qualcomm commented that 4 CRs are needed, for Rel-18 and Rel-19 of TS 23.501
and TS 23.502. Other CRs were reviewed. This was left for off-line discussion and revised to S2-2504019.

The future meeting dates should be corrected. This was revised to S2-2504383.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503351 (LS OUT) [DRAFT] Reply LS on PWS enhancements for MWAB and MBSR (Source: Huawei,
HiSilicon)
Document for: Approval
Abstract:
Responds to CT WG1 and RAN WG3 that SA WG2 has updated the corresponding the specifications.
Comment: Response to S2-2502805.

Convenor comment: Merge into S2-2502976?

Parallel discussion:

Merged into S2-2504109.

Status: Merged.

S2-2502981 (CR) 23.501 CR6171 (Rel-18, 'F'): PWS handling with Additional ULI (Source: Ericsson,
Qualcomm Incorporated)
Document for: Approval
Abstract:
Summary of change: Adding the usage of Additional ULI for PWS in clause 5.35A.6 for MBSR with reference
to TS 23.041.
Convenor comment: Moved to 19.6.2. Merge into S2-2503356?

Parallel discussion:

Merged into S2-2504104.

Status: Merged.

3GPP
Report of meeting S2-168

S2-2503356 (CR) 23.501 CR6211 (Rel-18, 'F'): PWS enhancements for MBSR (Source: Huawei, HiSilicon)
Document for: Approval
Abstract:
Summary of change: PWS enhancements for MBSR.
Convenor comment: HANDLE. Baseline for Rel-18 TS 23.501.

Parallel discussion:

Nokia commented that the PWS information should be kept in the appropriate clause. This was left for off-
line discussion and revised to S2-2504104.

The CN impacts should be ticked. This was revised, to clean up revision marks, to S2-2504381.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2502977 (CR) 23.501 CR6087R1 (Rel-19, 'F'): PWS handling with Additional ULI (Source: Ericsson,
Qualcomm Incorporated)
Document for: Approval
Abstract:
Summary of change: Adding the usage of Additional ULI for PWS in clause 5.35A.6 for MBSR and cluase
5.49.4 for MWAB with reference to TS 23.041.
Comment: Revision of (Postponed) S2-2501597.

Convenor comment: HANDLE. Baseline for Rel-19 TS 23.501.

Parallel discussion:

This was reviewed to determine the best way to document the Additional ULI. Sony commented that this
should be left for CT WG1 to specify rather than updating the Stage 2. This was left for off-line discussion
and revised to S2-2504105.

Nokia asked whether this is better described in the general clause rather than the Additional ULI support
clause. The changes should be included in 5.35a.1 and 5.49.1. Huawei and Samsung should be added to
the sources. This was revised to S2-2504382.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503357 (CR) 23.501 CR6212 (Rel-19, 'F'): PWS enhancements for MBSR and MWAB (Source: Huawei,
HiSilicon)
Document for: Approval
Abstract:
Summary of change: PWS enhancements for MBSR and MWAB.
Convenor comment: Merge into S2-2502977?

Parallel discussion:

Merged into S2-2504105.

Status: Merged.

3GPP
Report of meeting S2-168

S2-2502978 (CR) 23.502 CR5341R1 (Rel-19, 'F'): PWS handling update for VMR (Source: Ericsson,
Qualcomm Incorporated)
Document for: Approval
Abstract:
Summary of change: Remove the current text related to the 'warning Area List NG-RNA' handling.
Comment: Revision of (Postponed) S2-2501598.

Convenor comment: Merge into S2-2503443?

Parallel discussion:

Merged into S2-2504107.

Status: Merged.

S2-2502982 (CR) 23.502 CR5392 (Rel-18, 'F'): PWS handling update for VMR (Source: Ericsson,
Qualcomm Incorporated)
Document for: Approval
Abstract:
Summary of change: Remove the current text related to the 'warning Area List NG-RNA' handling.
Convenor comment: Moved to 19.6.2. Merge into S2-2503184?

Parallel discussion:

Merged into S2-2504106.

Status: Merged.

S2-2503184 (CR) 23.502 CR5416 (Rel-18, 'F'): Removal of text for PWS (Source: Nokia)
Document for: Approval
Abstract:
Summary of change: removal of text as er CT WG1 request above.
Convenor comment: HANDLE. Baseline for Rel-18 TS 23.502.

Parallel discussion:

Nokia commented that the other comments text can be removed as the Samsung CR would be the mirror.
CN impacts should also be marked. This was revised to S2-2504106.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503185 (CR) 23.502 CR5417 (Rel-19, 'F'): Removal of text for PWS (Source: Nokia)
Document for: Approval
Abstract:
Summary of change: removal of text as er CT WG1 request above.
Convenor comment: Merge into S2-2503443?

Parallel discussion:

Merged into S2-2504107.

Status: Merged.

3GPP
Report of meeting S2-168

S2-2503354 (CR) 23.502 CR5434 (Rel-18, 'F'): PWS enhancements for MBSR (Source: Huawei, HiSilicon)
Document for: Approval
Abstract:
Summary of change: PWS enhancements for MBSR.
Convenor comment: Merge into S2-2503184?

Parallel discussion:

Merged into S2-2504106.

Status: Merged.

S2-2503355 (CR) 23.502 CR5435 (Rel-19, 'F'): PWS enhancements for MBSR and MWAB (Source: Huawei,
HiSilicon)
Document for: Approval
Abstract:
Summary of change: PWS enhancements for MBSR and MWAB.
Convenor comment: Merge into S2-2503443?

Parallel discussion:

Merged into S2-2504107.

Status: Merged.

S2-2503440 (CR) 23.502 CR5445 (Rel-18, 'F'): PWS enhancements for MWAB and MBSR (Source:
Samsung)
Document for: Approval
Abstract:
Summary of change: Removing PWS-related change from 23.502 spec.
Convenor comment: Merge into S2-2503184?

Parallel discussion:

Merged into S2-2504106.

Status: Merged.

S2-2503443 (CR) 23.502 CR5446 (Rel-19, 'F'): PWS enhancements for MWAB and MBSR (Source:
Samsung)
Document for: Approval
Abstract:
Summary of change: Removing PWS-related changes from 23.502 spec.
Convenor comment: HANDLE. Baseline for Rel-19 TS 23.502.

Parallel discussion:

PMR should be added and Nokia added as a source company. This was revised to S2-2504107.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

3GPP
Report of meeting S2-168

S2-2502979 (CR) 23.501 CR6169 (Rel-19, 'F'): MWAB-gNB indication to AMF (Source: Ericsson)
Document for: Approval
Abstract:
Summary of change: Adding the possibility for MWAB-gNB to include the MWAB-UE location when the
MWAB-gNB setup (or update) the N2 connection. This MWAB-UE location information can also be used by
CN for the realization of MWAB-gNB.
Convenor comment: HANDLE.

Parallel discussion:

Some issues were raised and this was left for off-line discussion and revised to S2-2504108.

Some clarifications of the text were needed and this was left for off-line discussion and revised to S2-
2504384.

This was reviewed and agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

LS from RAN WG3 on Additional ULI

S2-2502830 (LS IN) LS from RAN WG3: Reply LS on FS_VMR_Ph2 solution impacts to RAN (Additional
ULI) (Source: RAN WG3 (R3-250901))
Document for: Action
Abstract:
RAN WG3 thanks SA WG2 for the LS reply on FS_VMR_Ph2 solution impacts to RAN (Access Control and
Additional ULI) in S2-2501324. {. . .} Action: RAN WG3 would like to call for SA WG2 to take the above RAN
WG3 agreements on additional ULI into account and update their specification(s).
Comment: Responses drafted in S2-2503646, S2-2503816.

Convenor comment: Replied in S2-2503816.

Parallel discussion:

Related CRs and proposed replies were reviewed.

Plenary Discussion:

Final response in S2-2504110.

Status: Replied to.

S2-2503646 (LS OUT) [DRAFT] Reply LS on FS_VMR_Ph2 solution impacts to RAN (Additional ULI)
(Source: CATT)
Document for: Approval
Abstract:
Reply LS on FS_VMR_Ph2 solution impacts to RAN (Additional ULI) (S2-2502830/R3-250901).
Comment: Response to S2-2502830.

Convenor comment: Merge into S2-2503816?

Parallel discussion:

Merged into S2-2504110.

Status: Merged.

3GPP
Report of meeting S2-168

S2-2503816 (LS OUT) [DRAFT] Reply LS on FS_VMR_Ph2 solution impacts to RAN (Additional ULI)
(Source: Qualcomm Incorporated)
Document for: Approval
Abstract:
Reply LS on FS_VMR_Ph2 solution impacts to RAN (Additional ULI).
Comment: Response to S2-2502830.

Convenor comment: HANDLE. Baseline for LS Out.

Parallel discussion:

This was revised to clean up attachments and remove 'draft', to S2-2504110.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503645 (CR) 23.501 CR6244 (Rel-19, 'F'): Additional ULI Update (Source: CATT)
Document for: Approval
Abstract:
Summary of change: Update the Additional ULI to align with RAN WG3 conclusion.
Convenor comment: Merge into S2-2503813?

Parallel discussion:

This was covered by and considered merged into S2-2503813.

Status: Merged.

S2-2503813 (CR) 23.501 CR6264 (Rel-19, 'F'): Correction of the Additional ULI mapping conditions for
MWAB (Source: Qualcomm Incorporated, Ericsson, Nokia, Huawei, HiSilicon, LG Electronics)
Document for: Approval
Abstract:
Summary of change: Correct the MWAB behavior in providing Additional ULI in clause 5.49.4.
Convenor comment: HANDLE. Baseline for CR.

Parallel discussion:

This was reviewed and agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

3GPP
Report of meeting S2-168

LS from RAN WG3 on Location Service support

S2-2502831 (LS IN) LS from RAN WG3: Reply LS on Support of Location Service Involving WAB-Nodes
(Source: RAN WG3 (R3-250902))
Document for: Action
Abstract:
RAN WG3 thanks SA WG2 for the LS on Location service of UEs served by MWAB. For SA WG2's question
on Location services, RAN WG3 concluded that several IEs introduced for mobile IAB can be reused. For
WAB, the new changes to align the SA WG2's conclusion were agreed in the attached TP for WAB BL CR
for TS 38.305 and TP for WAB BL CR for TS 38.455. For SA WG2's question on updating of additional ULI,
RAN WG3 discussed this issue and agreed that 'In case the additional ULI has changed e.g. due to WAB-
node movement, the WAB-gNB derives the new additional ULI and it reports it to the network, if required by
the CN via legacy procedures.' Action: RAN WG3 kindly asks SA WG2 to take the above feedback into
account.
Convenor comment: Reply to S2-2412625. To be NOTED.

Parallel discussion:

This LS was reviewed and noted in parallel session.

Status: Noted.

Misc. corrections

S2-2503183 (CR) 23.501 CR6189 (Rel-19, 'F'): Add MWAB indication to NEF monitoring events (Source:
Nokia)
Document for: Approval
Abstract:
Summary of change: MWAB Indication is added to Table 4.15.3.1-1: List of events for monitoring capability
in clause 4.15.3.1 Monitoring Events.
Comment: Confirm Specification Number - CR states 23.502!

Convenor comment: HANDLE.

Parallel discussion:

This should be a CR to 23.502. This was allocated as 23.502 CR 5479. Some clarifications were needed and
this was left for off-line discussion and revised to S2-2504111.

Ericsson raised a concern and Nokia clarified that this reflects the approved update in TS 23.273 and if there
is an issue then this should be revisited also in TS 23.273. This was then postponed in parallel session.

Status: Postponed.

S2-2503177 (CR) 23.501 CR6187 (Rel-19, 'F'): Clarification of the network slicing clause (Source: Nokia,
China Telecom)
Document for: Approval
Abstract:
Summary of change: It is clarified the text refers to a UE served by the MWAB-gNB, and the wording of
paragraph 2 is improved The right procedure name is used. This is clarified that If the S-NSSAI for the new
BH PDU session to be established is not in MWAB-UE's Allowed NSSAI, the MWAB-UE requests this S-
NSSAI in a Mobility Registration Update procedure before establishing the PDU session.
Convenor comment: HANDLE.

Plenary Discussion:

Not handled.

Status: Not treated.

3GPP
Report of meeting S2-168

S2-2503818 (CR) 23.273 CR0730 (Rel-19, 'F'): Correction of the 5GC-MT-LR procedure involving MWAB
(Source: Qualcomm Incorporated, Nokia)
Document for: Approval
Abstract:
Summary of change: Correct the step 10 of Figure 6.1.5-1 to reflect that the H-GMLC of MWAB-UE is
involved in location information retrieval.
Convenor comment: HANDLE.

Parallel discussion:

This was reviewed and agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2502980 (CR) 23.501 CR6170 (Rel-19, 'F'): MWAB-gNB authorization handling update (Source:
Ericsson)
Document for: Approval
Abstract:
Summary of change: Adding the possibility for releasing the UE. Adding the description of N2/Xn release.
Convenor comment: HANDLE.

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503018 (CR) 23.501 CR6099R1 (Rel-19, 'F'): Clarification on MWAB-UE aspect (Source: LG
Electronics)
Document for: Approval
Abstract:
Summary of change: 5.49.3.2 - Add description about that the MWAB-UE remains in CM-CONNECTED
state for MWAB operation.
Comment: Revision of (Unhandled) S2-2501694.

Convenor comment: HANDLE.

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503168 (CR) 23.501 CR6186 (Rel-19, 'F'): Clarification of mobility clause (Source: Nokia)
Document for: Approval
Abstract:
Summary of change: The text is clarified to state the MWAB-gNB advertising the new value(s) is the new
logical gNB as specified in TS 38.401 [42].
Convenor comment: HANDLE.

Plenary Discussion:

Not handled.

Status: Not treated.

3GPP
Report of meeting S2-168

S2-2503181 (CR) 23.501 CR6188 (Rel-19, 'F'): Handling of BH PDU session in the network (Source: Nokia)
Document for: Approval
Abstract:
Summary of change: Handling of BH PDU session from network side is provided so that re-authorization of
MWAB can be done in timely manner and unnecessary signalling is avoided (assuming the MWAB-UE would
keep trying to have OAM connection).
Comment: Confirm CR Number - CR states xxxx!

Convenor comment: HANDLE.

This was block approved.

Status: Approved.

3GPP
Report of meeting S2-168

S2-2502968 (CR) 23.304 CR0545 (Rel-19, 'F'): Updates to Common identifiers for 5G ProSe UE-to-Network
Relay (Source: Ericsson, AT&T)
Document for: Approval
Abstract:
Summary of change: The main changes to clause 5.8.3.1 include: Updated parameters in Relay Discovery
Additional Information message (using Model A) in clause 5.8.3.1 to align with clause 6.3.2.5.4 step 2.
Convenor comment: Handle.

Parallel discussion:

Some clarifications were needed and this was left for off-line discussion and revised to S2-2504117.

This was reviewed and agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503052 (CR) 23.304 CR0547 (Rel-19, 'F'): Policy/Parameter provisioning to support PWS for 5G ProSe
multi-hop U2N Relay (Source: OPPO)
Document for: Approval
Abstract:
Summary of change: Add PWS parameters in the Policy/Parameter provisioning for 5G ProSe multi-hop UE-
to-Network Relay. And how to use the configured parameters for broadcasting warning messasge is clarified.
Convenor comment: Handle.

Parallel discussion:

Qualcomm commented that RAN WG2 are still discussing how to handle PWS messages and this change
should not be made yet. The final change should be removed and this was revised to S2-2504118.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503141 (CR) 23.304 CR0548 (Rel-19, 'F'): Clarification on Multi-hop U2N and U2U Discovery (Source:
Huawei, HiSilicon)
Document for: Approval
Abstract:
Summary of change: Clarify that the condition for Relay dropping the Solicitation is determined by whether
Hop-Limit is included in the Solicitation. Some textual improvements in discovery procedures and related
communication procedures to reduce ambiguity.
Convenor comment: Handle.

Parallel discussion:

Some corrections were requested and this was left for off-line discussion and revised to S2-2504119.

This was revised, to add Samsung as a source company, to S2-2504390.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

3GPP
Report of meeting S2-168

S2-2503142 (CR) 23.304 CR0549 (Rel-19, 'F'): Clarification on Relay reselection for 5G ProSe Remote UE
with 5G ProSe Multi-hop UE-to-Network Relays (Source: Huawei, HiSilicon)
Document for: Approval
Abstract:
Summary of change: Adding the 'indication that the Root UE-to-Network Relay is changed' in the
enhancement of LMR message.
Comment: Check Affected Clauses (in other comments)!

Status: Approved.

3GPP
Report of meeting S2-168

Layer 2

S2-2503015 (CR) 23.304 CR0546 (Rel-19, 'F'): Introduction of Multi-hop Layer-2 UE-to-Network relaying
(Source: CATT)
Document for: Approval
Abstract:
Summary of change: Add related descriptions of Multi-hop Layer-2 UE-to-Network relaying.
Convenor comment: Handle.

Parallel discussion:

The terminology for multi-hop should be aligned. Other corrections were requested and this was left for off-
line discussion and revised to S2-2504123.

This was reviewed and agreed in parallel session.

Plenary Discussion:

This was block approved.

This was block approved.

Status: Approved.

19.8.1 Study on User Identities and Authentication Architecture

(FS_UIA_ARC)
This topic was not on the agenda for this meeting.

19.8.2 Identifying non-3GPP Devices Connecting behind a UE or 5G-RG

(UIA_ARC)
This agenda item was convened by Wanqiang Zhang (Huawei).

3GPP
Report of meeting S2-168

LS From CT WG1 and Draft Replies

S2-2502806 (LS IN) LS from CT WG1: LS on support for multiple non-3GPP device identifiers (Source: CT
WG1 (C1-250822))
Document for: Action
Abstract:
The agreed SA WG2 CR 5963 (S2-2501225) to 23.501 states: For the traffic of non-3GPP devices requiring
differentiated QoS: - ...(skip text) If the PCF indicates to the SMF that the corresponding Non-3GPP Device
Identifier is not available for the UE as specified in clause 6.1.3.31 of TS 23.503 [45], the SMF rejects the
PDU Session Modification with a cause code to notify the UE that the Non-3GPP Device Identifier is not
available for the UE. From the marked yellow text, there is no consensus in CT WG1 on: - whether the
multiple non-3GPP device identifiers are allowed in a single PDU session modification procedure; - whether
the SMF rejects the Non-3GPP Device Identifier or rejects the whole PDU SESSION MODIFICATION
REQUEST message. {. . .} Given these considerations, CT WG1 requests SA WG2 to provide answers to
the following questions: Q1: Whether the multiple non-3GPP device identifiers are allowed in a single PDU
SESSION MODIFICATION REQUEST message? Q2: For the Non-3GPP device identifier not available
scenario, whether the SMF rejects the Non-3GPP device identifier or rejects the whole PDU SESSION
MODIFICATION REQUEST message? Q3: For the scenario of removal of more than one non-3GPP device
identifier from the subscription in the UDR, whether a single or multiple non-3GPP device identifiers should
be permitted in a single PDU SESSION MODIFICATION COMMAND message? Action: CT WG1 requests
SA WG2 to review the above points and provide answers to above questions.
Comment: Responses drafted in S2-2502872, S2-2502907, S2-2502985, S2-2503053, S2-2503461, S2-
2503604, S2-2503858, S2-2503864.

Convenor comment:

Handle.

Plenary Discussion:

Final response in S2-2504337.

Status: Replied to.

S2-2502872 (LS OUT) [DRAFT] Reply LS on support for multiple non-3GPP device identifiers (Source:
Nokia)
Document for: Approval
Abstract:
Reply LS on support for multiple non-3GPP device identifiers.
Comment: Response to S2-2502806.

Plenary Discussion:

Not handled.

Status: Not treated.

3GPP
Report of meeting S2-168

S2-2502907 (LS OUT) [DRAFT] LS reply on support for multiple non-3GPP device identifiers (Source:
Ericsson will be SA2)
Document for: Approval
Abstract:
Draft LS reply to LS on support for multiple non-3GPP device identifiers from CT WG1.
Comment: Response to S2-2502806.

Convenor comment:

Handle - LS Reply Baseline.

Parallel discussion:

Revised in parallel session to S2-2504026.

Revised in parallel session to S2-2504256.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2502985 (LS OUT) [DRAFT] Reply LS on support for multiple non-3GPP device identifiers (Source:
Google Korea LLC)
Document for: Approval
Abstract:
To: CT WG1. CC: CT WG3.
Comment: Response to S2-2502806.

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503053 (LS OUT) [DRAFT] Reply to LS on support for multiple non-3GPP device identifiers (Source:
Samsung TO BE SA2)
Document for: Approval
Abstract:
To: CT WG1. CC: CT WG3.
Comment: Response to S2-2502806.

Plenary Discussion:

Not handled.

Status: Not treated.

3GPP
Report of meeting S2-168

S2-2503461 (LS OUT) [DRAFT] Reply LS on support for multiple non-3GPP device identifiers (Source: ZTE)
Document for: Approval
Abstract:
Proposes a reply LS on support for multiple non-3GPP device identifiers.
Comment: Response to S2-2502806.

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503604 (LS OUT) [DRAFT] UIA LSout on support for multiple non-3GPP device identifiers (Source:
Huawei, HiSilicon)
Document for: Approval
Abstract:
To answer the LS from CT WG1.
Comment: Response to S2-2502806.

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503858 (LS OUT) [DRAFT] Reply LS on support for multiple non-3GPP device identifiers (Source:
CSCN)
Document for: Approval
Abstract:
To: CT WG1. CC: CT WG3.
Comment: Response to S2-2502806.

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503864 (LS OUT) [DRAFT] LS Reply on support for multiple non-3GPP device identifiers (Source: Intel)
Document for: Approval
Abstract:
To: CT WG1. CC: CT WG3, CT WG4, SA WG3.
Comment: Response to S2-2502806.

Plenary Discussion:

Not handled.

Status: Not treated.

3GPP
Report of meeting S2-168

Addressing the CT WG1 LS - 23.501

S2-2503330 (CR) 23.501 CR6208 (Rel-19, 'F'): Inclusion of several Non-3GPP Device Identifiers (Source:
Nokia, InterDigital Inc., LG Electronics)
Document for: Approval
Abstract:
Summary of change: Session Management policies corresponding to handling of Non-3GPP Devices is
updated to clarify the several case scenario.
Convenor comment:

Handle - 23.501 Baseline.

Parallel discussion:

Last change: If the PCF indicates to the SMF by rejecting the SM Policy Association Modification that any of
the Non-3GPP Device Identifier(s) in the Non-3GPP Device Connection Information is not available in the
UDR for the UE as specified in clause 6.1.3.31 of TS 23.503 [45], the SMF rejects the PDU Session
Modification with a cause code to notify the UE that the Non-3GPP Device Identifier(s) is not available for the
UE. Revised in parallel session to S2-2504022.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503605 (CR) 23.501 CR6236 (Rel-19, 'F'): Clarificaiton on supporting multiple non-3GPP device
identifiers (Source: Huawei, HiSilicon)
Document for: Approval
Abstract:
Summary of change: Add the clarification on supporting multiple non-3GPP Device Identifiers in PDU
SESSION MODIFICATION message and in PDU SESSION MODIFICATION COMMAND message.
Plenary Discussion:

Not handled.

Status: Not treated.

S2-2502986 (CR) 23.501 CR6172 (Rel-19, 'F'): Providing device identifier information in PDU session
modification request (Source: Google)
Document for: Approval
Abstract:
Summary of change: Clarified that the UE includes non-3GPP Device Identifier and user plane address for
each non-3GPP device that is connected (for the corresponding PDU session) in the PDU session
modification request message.
Plenary Discussion:

Not handled.

Status: Not treated.

3GPP
Report of meeting S2-168

S2-2503462 (CR) 23.501 CR6224 (Rel-19, 'F'): Clarification on the non-3gpp device identifier activation and
removal (Source: ZTE, Xiaomi)
Document for: Approval
Abstract:
Summary of change: One non-3GPP device identifier in a single PDU session modification Request
message. Clarify how the SMF indicate UE Non-3GPP device identifier not available. Clarify how the UE and
network remove the Non-3GPP device identifier (s).
Plenary Discussion:

Not handled.

Status: Not treated.

Addressing the CT WG1 LS - 23.502

S2-2502902 (CR) 23.502 CR5383 (Rel-19, 'F'): QoS differention for multiple Non-3GPP devices (Source:
Ericsson, AT&T)
Document for: Approval
Abstract:
Summary of change: The following changes are proposed: - It is indicated that multiple Non-3GPP Device
Identifiers can be added in the PDU Session Modification Request - Non-3GPP Device Connection
Information Status is added to the N1 SM Container from SMF to UE.
Convenor comment:

Handle - 23.501 Baseline.

Parallel discussion:

Revised in parallel session to S2-2504023.

Revised in parallel session to S2-2504254.

Revised in parallel session to S2-2504332.

Revised in parallel session to S2-2504336.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503331 (CR) 23.502 CR5432 (Rel-19, 'F'): Inclusion of several Non-3GPP Device Identifiers (Source:
Nokia, InterDigital Inc., LG Electronics)
Document for: Approval
Abstract:
Summary of change: PDU Session Modification procedure is clarified to indicate the pluarality of
associations to the corresponding Non-3GPP Device Identifers. It is also added with an additional note about
Packet Filter Operation of 'delete'.
Plenary Discussion:

Not handled.

Status: Not treated.

3GPP
Report of meeting S2-168

S2-2503606 (CR) 23.502 CR5462 (Rel-19, 'F'): Clarificaiton on supporting multiple non-3GPP device
identifiers (Source: Huawei, HiSilicon)
Document for: Approval
Abstract:
Summary of change: Clarify that multiple non-3GPP Device Identifiers are allowed in one PDU Session
Modification request. Clarify that the unavailable non-3GPP Device Identifiers are permitted in PDU Session
Modification Command message when there is unavailable non-3GPP device identifiers in the PDU Session
modification request or PCF deletes the PCC rules related to the non-3GPP device identifiers.
Plenary Discussion:

Not handled.

Status: Not treated.

S2-2502987 (CR) 23.502 CR5393 (Rel-19, 'F'): Providing device identifier information in PDU session
modification request (Source: Google)
Document for: Approval
Abstract:
Summary of change: Clarified that the UE includes non-3GPP Device Identifier and user plane address for
each non-3GPP device that is connected (for the corresponding PDU session) in the PDU session
modification request message. Added a NOTE that it is up to UE implementation to determine when a non-
3GPP device is connected and when to update the non-3GPP device connection information. To avoid
signaling overhead, frequently updating non-3GPP device connection information is not recommended.
Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503463 (CR) 23.502 CR5450 (Rel-19, 'F'): Clarification on the non-3gpp device identifier activation and
removal (Source: ZTE, Xiaomi)
Document for: Approval
Abstract:
Summary of change: One non-3GPP device identifier in a single PDU session modification Request
message. Clarify how the SMF indicate UE Non-3GPP device identifier not available. Clarify how the UE and
network remove the Non-3GPP device identifier(s).
Plenary Discussion:

Not handled.

Status: Not treated.

3GPP
Report of meeting S2-168

Addressing the CT WG1 LS - 23.503

S2-2503607 (CR) 23.503 CR1551 (Rel-19, 'F'): Clarificaiton on supporting multiple non-3GPP device
identifiers (Source: Huawei, HiSilicon)
Document for: Approval
Abstract:
Summary of change: Add the clarification on supporting multiple non-3GPP Device Identifiers in PDU
SESSION MODIFICATION message. Clarify that the unavailable non-3GPP Device Identifiers are permitted
in PDU Session Modification Command message when there is unavailable non-3GPP device identifiers in
the PDU Session modification request or PCF deletes the PCC rules related to the non-3GPP device
identifiers.
Convenor comment:

Handle - 23.503 Baseline.

Parallel discussion:

Revised in parallel session to S2-2504024.

Revised in parallel session to S2-2504255.

Change the last sentence: PCF initiated SM Policy Association Modification , in which case the SMF
removes/updates the corresponding QoS and N4 rule(s). Remove the last bullet in the cover page Add more
source companies. Revised in parallel session to S2-2504333.

This was agreed in parallel session.

Plenary Discussion:

There were changes on changes and cover sheet issues. A correction to remove 'list of' and add
'Identifier(s)' was made in clause 6.1.3.31. This was revised to S2-2504477.

This was approved.

Status: Approved.

S2-2502903 (CR) 23.503 CR1528 (Rel-19, 'F'): Results of QoS differention for multiple Non-3GPP devices
(Source: Ericsson, AT&T)
Document for: Approval
Abstract:
Summary of change: The following changes are proposed: - Non-3GPP Device Connection Information
Status is added to PDU session related policy information - the high-level description in clause 6.1.3.31 is
updated to contain removal of Non-3GPP Device Identifiers from UDR.
Comment: Missing Affected Clauses!

Plenary Discussion:

Not handled.

Parallel discussion:

Revised in parallel session to S2-2504025.

Plenary Discussion:

Noted.

Status: Noted.

S2-2503464 (CR) 23.503 CR1540 (Rel-19, 'F'): Clarification on the non-3gpp device identifier activation and
removal (Source: ZTE, Xiaomi)
Document for: Approval
Abstract:
Summary of change: Clarify how the PCF remove the Non-3GPP device identifier (s).
Plenary Discussion:

Not handled.

Status: Not treated.

3GPP
Report of meeting S2-168

How the UE Stops QoS Differentiation for a Device

S2-2503074 (CR) 23.501 CR6180 (Rel-19, 'F'): Clarifications on SM signalling including non-3GPP device
identifiers for QoS differentiation (Source: Apple)
Document for: Approval
Abstract:
Summary of change: Added clarification in clause 5.52.3 that PDU Session Modification for requesting
differentiated QoS includes no other requests from the UE. Added clarification in clause 5.52.2 that when UE
determines that traffic differentiation is no longer required for certain traffic, it requests deletion of associated
packet filters through a PDU Session modification procedure.
Convenor comment:

Handle.

Parallel discussion:

Revised in parallel session to S2-2504027.

Revised in parallel session to S2-2504257.

Add more source companies. Revised in parallel session to S2-2504334.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503075 (CR) 23.502 CR5409 (Rel-19, 'F'): Clarifications for SM signalling including non-3GPP device
identifiers for QoS differentiation (Source: Apple)
Document for: Approval
Abstract:
Summary of change: Added clarification in step 1a of clause 4.3.32 that when UE determines that traffic
differentiation is no longer required for certain traffic, it requests delection of associated packet filters.
Plenary Discussion:

Not handled.

Status: Not treated.

HR Roaming

S2-2503000 (CR) 23.503 CR1530 (Rel-19, 'F'): Adding a Reference to the Home Routed Roaming PDU
Session Modification Procedure (Source: InterDigital Inc., LG Electronics, Samsung, Nokia)
Document for: Approval
Abstract:
Summary of change: Added a reference to clause 4.3.3.3 of TS 23.502.
Comment: Agreed in parallel session.

3GPP
Report of meeting S2-168

Others

S2-2503465 (CR) 23.502 CR5451 (Rel-19, 'F'): Clarification on the subscription to UDR (Source: ZTE)
Document for: Approval
Abstract:
Summary of change: Adding PCF subscribing Non-3GPP Device Identifier Information with UDR.
Convenor comment:

Handle.

Parallel discussion:

Revised in parallel session to S2-2504030.

Revised in parallel session to S2-2504259.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503677 (CR) 23.502 CR5466 (Rel-19, 'F'): Correction about the Non-3GPP Device Connection
Information (Source: China Mobile)
Document for: Approval
Abstract:
Summary of change: This CR proposes to be clarified the statement about non-3GPP device connection
information.
Convenor comment:

Handle.

Parallel discussion:

Revised in parallel session to S2-2504031.

Plenary Discussion:

Merged.

Status: Merged.

3GPP
Report of meeting S2-168

S2-2502906 (CR) 23.502 CR5386 (Rel-19, 'F'): Clarifying port ranges and removing EN (Source: Ericsson)
Document for: Approval
Abstract:
Summary of change: Stating only one port range needed and applies to both TCP and UDP prorts Removing
Editor's note and adding reference to stage 3.
Comment: Missing Affected Clauses!

Convenor comment:

Handle.

Parallel discussion:

Only keep the change port range(s) and remove the EN. Revised in parallel session to S2-2504032.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

NOTE: This was reported as being a CR to TS 23.501 after the meeting and should be withdrawn at the
next meeting and a replacement CR submitted.

Status: Approved.

S2-2503031 (CR) 23.501 CR6175 (Rel-19, 'F'): Clarifications to Session Management aspects for handling
Non-3GPP Device Identifiers (Source: Samsung)
Document for: Approval
Abstract:
Summary of change: IPv4 address is an optional information (e.g. when UE PDU Session has only 1
allocated IP address) Specified the SMF behaviour in case VLAN tag is present Other editorial corrections.
Convenor comment:

Handle.

Parallel discussion:

Revised in parallel session to S2-2504033.

Revised in parallel session to S2-2504258.

Remove the change on change. - MAC address of the non-3GPP device used in PDU session, Add the
request : SMF rejects the PDU Session Modification Request. Revised in parallel session to S2-2504335.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

3GPP
Report of meeting S2-168

S2-2503306 (CR) 23.501 CR6203 (Rel-19, 'F'): Clarification on PDU Session for non-3GPP device (Source:
LG Electronics)
Document for: Approval
Abstract:
Summary of change: When a non-3GPP device is connected to the UE, which PDU Session is used for the
non-3GPP device is up to UE implementation. Terminology alighment (PDU Session).
Convenor comment:

Handle.

Parallel discussion:

Revised in parallel session to S2-2504034.

Revised in parallel session to S2-2504260.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2502894 (CR) 23.316 CR2142R1 (Rel-19, 'F'): Clarification on AF-5GC interaction for provisioning non-
3GPP device identifiers (Source: Apple, Charter Communications)
Document for: Approval
Abstract:
Summary of change: It is clarified in a NOTE that 5G-RG notifies operator portal in AF about completion of
actions in Step 3 through application layer mechanism.
Comment: Revision of (Noted) S2-2500462. Agreed in parallel session.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503597 (CR) 23.501 CR6235 (Rel-19, 'F'): Update definition of non-3GPP device connection information
(Source: Xiaomi)
Document for: Approval
Abstract:
Summary of change: Clarify the definition of non-3GPP device connection information and conatined
parameters to have IP Address or MAC address used in the PDU session as optional parameter.
Comment: Merged into S2-2504033.

Convenor comment:

Handle.

Parallel discussion:

Merged.

Status: Merged.

3GPP
Report of meeting S2-168

SMF Selection

S2-2502900 (CR) 23.501 CR6165 (Rel-19, 'F'): PCF and SMF selection for QoS differentiation for non-3GPP
devices (Source: Ericsson)
Document for: Approval
Abstract:
Summary of change: The following changes are proposed: - Support for QoS differentiation for non-3GPP
device identifiers is added to section 6.3.2 for SMF selection - Support for QoS differentiation for non-3GPP
device identifiers is added to section 6.3.7.1 for PCF selection.
Convenor comment:

Handle.

Parallel discussion:

Revised in parallel session to S2-2504035.

Request to be handled with high priority in the future meetings and encourage companies to do the offline
work.

Plenary Discussion:

Postponed.

Status: Postponed.

S2-2502901 (CR) 23.502 CR5382 (Rel-19, 'F'): Selection mechanisms for SMF and PCF for non-3GPP
devices QoS differentiation (Source: Ericsson)
Document for: Approval
Abstract:
Summary of change: The following changes are proposed: - Non-3GPP QoS Differentiation Indicator is
added to the CreateSMContext Request - UE's susbscription data in UDM is updated. - PCF and SMF
registration in NRF is updated.
Convenor comment:

Handle.

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503337 (CR) 23.501 CR5976R1 (Rel-19, 'F'): Support of SMF selection considering the Non-3GPP
Device Identifier (Source: Huawei, HiSilicon)
Document for: Approval
Abstract:
Summary of change: - The SMF registers its capability to support Device Identifier in the NRF. - During the
PDU Session establishment procedure, when the PDU Session is related to a Device Identifier, the AMF
selects an SMF which supports non-3GPP Device Identifier, and the SMF selects a PCF which supports
non-3GPP Device Identifier.
Comment: Revision of (Noted) S2-2500558.

Convenor comment:

Handle.

Plenary Discussion:

Not handled.

Status: Not treated.

3GPP
Report of meeting S2-168

S2-2503338 (CR) 23.502 CR5275R1 (Rel-19, 'F'): Support of SMF selection for Non-3GPP Device Identifer
(Source: Huawei, HiSilicon)
Document for: Approval
Abstract:
Summary of change: Non-3GPP Identifier is provided to AMF and SMF in the PDU session establishment to
select an appropriate SMF and PCF that support Non-3GPP Device Identifier handling respectively.
Corresponding NRF service is specified to facilitate the selection of SMF and PCF that can handle Non-
3GPP Device Identifiers.
Comment: Revision of (Unhandled) S2-2500709.

Convenor comment:

Handle.

Parallel discussion:

Revised in parallel session to S2-2504036.

Request to be handled with high priority in the future meetings and encourage companies to do the offline
work.

Plenary Discussion:

Postponed.

Status: Postponed.

19.9.1 Study on Enhancement of support for Edge Computing in 5G Core

network - Phase 3 (FS_eEDGE_5GC_Ph3)
This topic was not on the agenda for this meeting.

19.9.2 Enhancement of support for Edge Computing in 5G Core network -

Phase 3 (eEDGE_5GC_Ph3)
This agenda item was convened by Dario Tonesi (Qualcomm).

KI#2: Supporting N6 delay measurement

S2-2502812 (LS IN) LS from CT WG4: LS on Security related protocol-specific parameters for N6 delay
measurement (Source: CT WG4 (C4-250555))
Document for: Information
Abstract:
CT WG4 is designing protocol extensions to support the Rel-19 stage 2 requirements on N6 delay
measurement and reporting. {. . .} CT WG4 would like SA WG3 to provide guidance on the security related
protocol-specific parameters that PFCP should support providing to the UPF over N4, for the indicated
measurement protocols (i.e. TWAMP, OWAMP and STAMP).
Comment: Noted in parallel session.

Parallel discussion:

This was noted in parallel session.

Status: Noted.

3GPP
Report of meeting S2-168

KI#2: I-SMF supporting N6 delay measurement - 548 CR

S2-2503700 (CR) 23.548 CR0310 (Rel-19, 'F'): Clarification on I-SMF operation for N6 Delay Measurement
(Source: Samsung)
Document for: Approval
Abstract:
Summary of change: Add clarification on I-SMF's use of N6 delay measurement for both LOM and non LOM
scenarios.
Parallel discussion:

Keep only first change and confirm it is agreeable. Revised in parallel session to S2-2503920.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

KI#1: Offloading from central SMF

Support of I-SMF Selection - Discussion papers

S2-2503403 (DISCUSSION) Clarification of the selected I-SMF for Local offloading traffic handling . (Source:
Huawei, HiSilicon)
Document for: Approval
Abstract:
This paper clarifies how the I-SMF is selected for local offloading traffic handling.
Comment: Noted in parallel session.

Parallel discussion:

This was noted in parallel session.

Status: Noted.

Support of I-SMF Selection - 548 CRs

S2-2503404 (CR) 23.548 CR0288R1 (Rel-19, 'F'): KI#1: Clarfication on the I-SMF selected for local
offloading managment (Source: Huawei, HiSilicon, Samsung)
Document for: Approval
Abstract:
Summary of change: The AMF selects the I-SMF, which is able to offload traffic when the UE is within the
local offloading management service area.
Comment: Revision of (Postponed) S2-2500611. Check WI Code Capitalization!

Convenor comment:

Competing CR with S2-2502895.

Parallel discussion:

Work on limitation of scope of solution. Revised in parallel session to S2-2503921.

Plenary Discussion:

Postponed.

Status: Postponed.

3GPP
Report of meeting S2-168

S2-2502895 (CR) 23.548 CR0297R1 (Rel-19, 'F'): Clarification on SMF triggered I-SMF insertion or removal
for Local Offloading Management (Source: Nokia)
Document for: Approval
Abstract:
Summary of change: Clarifies SMF triggered I-SMF selection or removal for Local Offloading Management.
Comment: Revision of (Postponed) S2-2501062. Postponed in parallel session.

Plenary Discussion:

Postponed.

Status: Postponed.

S2-2503405 (CR) 23.501 CR5981R1 (Rel-19, 'F'): KI#1: Clarfication on the I-SMF selected for local
offloading managment (Source: Huawei, HiSilicon, Samsung)
Document for: Approval
Abstract:
Summary of change: Refer to TS23.548 about the I-SMF selected for local offloading management.
Comment: Revision of (Postponed) S2-2500612. Noted in parallel session.

Parallel discussion:

This was noted in parallel session.

Status: Noted.

S2-2503406 (CR) 23.502 CR5265R1 (Rel-19, 'F'): KI#1: Clarfication on the I-SMF selected for local
offloading managment (Source: Huawei, HiSilicon, Samsung)
Document for: Approval
Abstract:
Summary of change: No target DNAI sent from SMF if I-SMF based Local Offloading Management applies to
the PDU session.
Comment: Revision of (Postponed) S2-2500613. Postponed in parallel session.

Plenary Discussion:

Postponed.

Status: Postponed.

KI#1: LOM Policy

S2-2503614 (CR) 23.548 CR0308 (Rel-19, 'F'): Clarification for Local offloading management policy (Source:
ZTE)
Document for: Approval
Abstract:
Summary of change: Clarify how the Offload Identifier is used in PCF and SMF.
Parallel discussion:

Revised in parallel session to S2-2503922.

Remove I-SMF? Revised in parallel session to S2-2504174.

Revised in parallel session to S2-2504233.

Fix typo before bullet list. Revised in parallel session to S2-2504246.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

3GPP
Report of meeting S2-168

KI#1: EAS Discovery using IP replacement

S2-2503259 (CR) 23.548 CR0302 (Rel-19, 'F'): KI#1 Clarification on EAS Discovery using IP replacement to
support Local Offloading Management (Source: OPPO)
Document for: Approval
Abstract:
Summary of change: Add description on how to support EAS discovery procedure with EASDF/Local DNS
Server using IP replacement mechanism for Local Offloading Management.
Comment: Check WI Code Capitalization! Noted in parallel session.

Parallel discussion:

This was noted in parallel session.

Status: Noted.

KI#1: NF Profile and AMF configuration

S2-2503498 (CR) 23.501 CR6225 (Rel-19, 'F'): SMF profile enhancement (Source: China Mobile)
Document for: Approval
Abstract:
Summary of change: Adding capability of supporting Local Offloading Management to NF profile of SMF.
Parallel discussion:

Do not add new bullet. Modify existing to read as follows 'Support of Local Offloading Management and the
corresponding service area, in the case of SMF.'. Revised in parallel session to S2-2503923.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503391 (CR) 23.501 CR6215 (Rel-19, 'F'): Clarification on the Local Offloading Management and SMF
Service Area (Source: LG Electronics)
Document for: Approval
Abstract:
Summary of change: 5.34.1 - Clarify that the Local Offloading Management is supported irrespect of
whether the UE is within or outside of the Anchor SMF Service Area since the current description is deemed
ambiguous. 6.2.6.2 - As per description in clause 5.2.7.2.2 and 5.2.7.3.2 of TS 23.502 the SMF may include
the capability of supporting Local Offloading Management in the NF profile which needs to be included as
well in the result of the query.
Comment: Merged into S2-2503923.

Parallel discussion:

Merged.

Status: Merged.

3GPP
Report of meeting S2-168

S2-2503395 (CR) 23.548 CR0303 (Rel-19, 'F'): Clarification on the Local Offloading Management Service
Area (Source: LG Electronics)
Document for: Approval
Abstract:
Summary of change: 6.10.2.2 - Clarify that the AMF may consider service area of the SMFs supporting
Local Offloading Management as the Local Offloading Management service area when there is no Local
Offloading Management service area of those SMFs is configured/registered in the NF profile.
Comment: Noted in parallel session.

Parallel discussion:

The assumption is that LOM service area is always configured if LOM is to be used.

Plenary Discussion:

Noted.

Status: Noted.

KI#1: Other correction CRs

S2-2503499 (CR) 23.548 CR0306 (Rel-19, 'F'): Correction of local offloading management (Source: China
Mobile)
Document for: Approval
Abstract:
Summary of change: Add missing procedure during local offloading management.
Parallel discussion:

Keep only last two changes in step 2b. Revised in parallel session to S2-2503924.

Remove first 3 bullets from reason for changes. Remove added duplicated text in change. Revised in parallel
session to S2-2504175.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503500 (CR) 23.548 CR0307 (Rel-19, 'F'): UE mobility for local offloading management (Source: China
Mobile)
Document for: Approval
Abstract:
Summary of change: Add missing procedure during UE mobility.
Parallel discussion:

Revised in parallel session to S2-2503925.

Revised in parallel session to S2-2504176.

The new note reads 'If the DNS server address discovered by the SMF is the same as the one formerly
provided by the I-SMF, the SMF does not need to include that DNS server address in the PCO.'. Revised in
parallel session to S2-2504181.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

3GPP
Report of meeting S2-168

S2-2503698 (CR) 23.501 CR6249 (Rel-19, 'F'): 23.501 CR6249: Clarification on Local Offloading
Management with URSP (Source: Samsung)
Document for: Approval
Abstract:
Summary of change: Clarification on the support of LOM without I-SMF insertion.
Comment: Wrong WI Code: (FS_) AIML_CN_Ph2 is a FS.

Parallel discussion:

Delete from new note 4 the following text 'without I-SMF insertion as described in 6.10.1 of TS 23.548 [130]
by utilizing URSP and SSC mode' Update reason for change. Revised in parallel session to S2-2503926.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503699 (CR) 23.548 CR0309 (Rel-19, 'F'): Clarification on handling application not matched with LOM
policy (Source: Samsung)
Document for: Approval
Abstract:
Summary of change: Clarification of Local Offloading Management Allowed indication and configuration of
EASDF by I-SMF.
Parallel discussion:

Remove second last added bullet. Revised in parallel session to S2-2503927.

Revised in parallel session to S2-2504177.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503850 (CR) 23.502 CR5477 (Rel-19, 'F'): Clarifications on I-SMF insertion for PDU Session Mobility
(Source: Nokia)
Document for: Approval
Abstract:
Summary of change: Clarifies I-SMF insertion for PDU Session Mobility from EPS to 5G and non-3GPP to
3GPP access.
Parallel discussion:

Check if 1st change is needed. Revised in parallel session to S2-2503928.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

3GPP
Report of meeting S2-168

KI#1: N4 Rule generation and LOM Indication

S2-2503851 (CR) 23.548 CR0311 (Rel-19, 'F'): Corrections on Local Offloading Management related
indications (Source: Nokia)
Document for: Approval
Abstract:
Summary of change: Clarifies the usage of Local Offloading Management 'allowed' and 'support' indications
in clause 6.10.2.2 Editorial correction in clause 6.10.1.
Parallel discussion:

Keep only the first two sentences in the reason for change. Revised in parallel session to S2-2504178.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503407 (DISCUSSION) Interaction between the I-SMF and SMF . (Source: Huawei, HiSilicon)
Document for: Approval
Abstract:
This paper clarifies two issues related to the interaction between SMF and I-SMF for local offloading
management.
Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503408 (CR) 23.548 CR0305 (Rel-19, 'F'): Interaction between SMF and I-SMF (Source: Huawei,
Hisilicon)
Document for: Approval
Abstract:
Summary of change: I-SMF notifies the SDF filter(s) of the offloaded traffic to SMF. Per the received SDF
filter(s), the SMF generates N4 information. When the I-SMF received the LOM Allowed Indication from AMF
and its support LOM, then LOM Supported Indication is sent to SMF. And SMF send back the LOM Allowed
Indication back to I-SMF.
Convenor comment:

SDF/N4 rule discussed in the past. Focus on LOM allowed vs. support ind.

Parallel discussion:

Focus only on last change (note in 6.10.2.4). Revised in parallel session to S2-2503929.

The new text before the NOTE reads as '[...]exchanges with the SMF the information as defined in clause
6.10.2.2'. Revised in parallel session to S2-2504179.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

3GPP
Report of meeting S2-168

S2-2503409 (CR) 23.502 CR5442 (Rel-19, 'F'): Interaction between SMF and I-SMF (Source: Huawei,
Hisilicon)
Document for: Approval
Abstract:
Summary of change: I-SMF notifies the SDF filter(s) of the offloaded traffic to SMF. Per the received SDF
filter(s), the SMF generates N4 information. Remove the LOM Allowed indication from I-SMF to SMF.
Remove the duplicated LOM Allowed indication in the Nsmf_PDUSession_Update service operation.
Convenor comment:

See S2-2503408.

Parallel discussion:

Focus on corrected reference and indication in service operation will align with offline discussion on S2-
2503851. Revised in parallel session to S2-2503930.

Remove first affected clause from cover page and first bullet in consequences if not approved. Revised in
parallel session to S2-2504180.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

KI#1: Concluded issue - AF Traffic Influence

S2-2503397 (CR) 23.548 CR0304 (Rel-19, 'F'): Clarification on the AF trafficInfluence information from SMF
to I-SMF (Source: LG Electronics)
Document for: Approval
Abstract:
Summary of change: 6.10.1 - Propose to clarify that the AF provided traffic influence information is sent from
SMF to the I-SMF.
Comment: Noted in parallel session.

Parallel discussion:

This was noted in parallel session.

Status: Noted.

S2-2503399 (CR) 23.502 CR5439 (Rel-19, 'F'): Clarification on the AF trafficInfluence information from SMF
to I-SMF (Source: LG Electronics)
Document for: Approval
Abstract:
Summary of change: 5.2.8.2.2, 5.2.8.2.3 - Propose to update service operation to include AF provided traffic
influence information is sent from SMF to the I-SMF.
Convenor comment:

See S2-2503397.

Plenary Discussion:

Not handled.

Status: Not treated.

3GPP
Report of meeting S2-168

19.10.1 Study on Phase 3 for UAS, UAV and UAM (FS_UAS_Ph3)

This topic was not on the agenda for this meeting.

19.10.2 Phase 3 for UAS, UAV and UAM (UAS_Ph3)

This agenda item was convened by Andy Bennett (Samsung).

Incoming LS - proposed to note

S2-2502810 (LS IN) LS from CT WG3: Reply LS on Nnef_RetrieveInfoUAVFlight_Get service operation

(Source: CT WG3 (C3-250661))
Document for: Action
Abstract:
CT WG3 thanks SA WG2 for the LS on Clarification of Nnef_RetrieveInfoUAVFlight_Get service operation.
CT WG3 would like to provide feedback on the approach taken by SA WG2 on the
Nnef_RetrieveInfoUAVFlight_Get service operation as following: CT WG3 has discussed and agreed that CT
WG3 is fine with the approach taken by SA WG2 on the request/response semantics as defined in the
Nnef_RetrieveInfoUAVFlight_Get service operation which is separated from the subscribe/update/notify
semantics as defined in the Nnef_UAVFlightAssistance service in TS 23.256. Above CT WG3 conclusion is
based on consideration that in TS 23.256 clause 5.12.2 Procedure for NEF Assisted Pre-flight Planning and
clause 5.13.2 Procedure for USS changeover during a UAV flight, the Nnef_RetrieveInfoUAVFlight_Get
request does not create subscription to any events and is not expected to be used, for instance, for in-flight
monitoring purposes and the step 10 in clause 5.13.2 is initiated by a new USS2 (target USS) which is
different from the original USS1, i.e., USS2 cannot reuse the original USS1 initiated
Nnef_RetrieveInfoUAVFlight service even with the same UAS NF/NEF upon the different USS AF, hence the
discussed subscribe/notify semantics is not applied to the Nnef_RetrieveInfoUAVFlight service. The TS
23.256 defined Nnef_RetrieveInfoUAVFlight_Get service operation with request/response semantics is fine
to be accepted and has been implemented as retrieve custom operation in the new RetrieveInfoUAVFlight
API in TS 29.522 v19.1.0. Action: CT WG3 kindly asks SA WG2 to consider above CT WG3 feedback.
Convenor comment: Reply to S2-2412757.

Parallel discussion:

Ericsson reported that the issue related to CR in S2-2413009 (from the November 2024 meeting) is now
resolved and no additional action needed by SA WG2. This LS was noted in parallel session.

Status: Noted.

3GPP
Report of meeting S2-168

Incoming LS which needs Reply LS and CRs

S2-2502828 (LS IN) LS from RAN WG3: LS on UAV regulation from RAN3 (Source: RAN WG3 (R3-
250876))
Document for: Action
Abstract:
RAN WG3 thanks SA WG2 for the reply LS on UAV regulation. RAN WG3 further discussed the topic based
on the feature provided by SA WG2 regarding the applicability of the 'NEF Assisted In-flight Monitoring' in
clause 5.12.3 of TS 23.256 to implement a network-based solution, which may require a UAV UE to report its
own flight status information, and the NG-RAN then reports the received information to the AMF over NG. It
is RAN WG3 understanding that NG-RAN can provide the UAV UE altitude information to CN. The three
kinds of report type, i.e., periodical, threshold-based, event-based, can be supported to report altitude
information based on NG-RAN node implementation. With regards to the 'node-level signalling' solution
configuration in clause 5.16.2, RAN WG3 would like to ask for further feedback from SA WG2 on whether the
CN needs to indicate derived altitude thresholds and reporting periodicity for the aerial UE's altitude
reporting. Action: RAN WG3 respectfully asks SA WG2 to take the above information into account and
provide corresponding feedback.
Comment: Responses drafted in S2-2502938, S2-2502963, S2-2503441, S2-2503644.

Parallel discussion:

The related CRs and reply LSs were reviewed.

Plenary Discussion:

Final response in S2-2504471.

Status: Replied to.

S2-2502938 (LS OUT) [DRAFT] Reply LS on UAV regulation from RAN WG3 (Source: LG Electronics)
Document for: Approval
Abstract:
[Draft] Reply LS on UAV regulation from RAN WG3.
Comment: Response to S2-2502828.

Parallel discussion:

Merged into S2-2504131.

Status: Merged.

S2-2502963 (LS OUT) [DRAFT] Reply LS on UAV regulation from RAN WG3 (Source: Ericsson)
Document for: Approval
Abstract:
Response to R3-250876, which is response to R3-250022/S2-2413011.
Comment: Response to S2-2502828.

Parallel discussion:

Merged into S2-2504131.

Status: Merged.

3GPP
Report of meeting S2-168

S2-2503441 (LS OUT) [DRAFT] Reply LS on UAV regulation from RAN WG3 (Source: China Mobile Com.
Corporation)
Document for: Approval
Abstract:
To: RAN WG3.
Comment: Response to S2-2502828.

Parallel discussion:

This was used as a basis for response and was left for off-line discussion and revised, merging S2-2502938,
S2-2502963, S2-2503644, to S2-2504131.

Plenary Discussion:

Ericsson commented that the status of the specification of the timestamp needs to be requested from
RAN WG3. Huawei replied that the timestamp has already been defined but with the UE level signalling
added it is unclear whether the timestamp is still needed. Ericsson replied that this is not about message
aggregation, but the timestamp is needed to determine the time that the altitude information was collected.
This was left for off-line discussion and revised to S2-2504378.

Parallel discussion:

Ericsson requested changing the text 'the USS needs to know' to 'the USS can benefit from knowing'. This
was revised, also to clean up revision marks and remove 'draft', to S2-2504471.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503644 (LS OUT) [DRAFT] Reply LS on UAV regulation from RAN WG3 (Source: CATT)
Document for: Approval
Abstract:
Reply LS on UAV regulation from RAN WG3 (S2-2502828/R3-250876).
Comment: Response to S2-2502828.

Parallel discussion:

Merged into S2-2504131.

Status: Merged.

S2-2502937 (CR) 23.256 CR0192 (Rel-19, 'F'): Clarification on procedure for instructing aerial UEs for
altitude reporting (Source: LG Electronics)
Document for: Approval
Abstract:
Summary of change: 5.16.2 - Clarify that altitude thresholds and reporting periodicity provided from AMF to
NG-RAN.
Convenor comment: 5.16.2. Proposed to attach in Reply LS.

Parallel discussion:

Merged into S2-2504128.

Status: Merged.

3GPP
Report of meeting S2-168

S2-2503673 (CR) 23.256 CR0199 (Rel-19, 'F'): The indication on altitude thresholds and reporting periodicity
for the aerial UE's altitude reporting (Source: China Mobile)
Document for: Approval
Abstract:
Summary of change: Clarification is made on indicating altitude thresholds and reporting periodicity for the
aerial UE's altitude reporting to RAN.
Convenor comment: 5.16.2, 5.16.3. Referred by Reply LS.

Parallel discussion:

The N2 message should be kept. It was suggested to remove the Timestamp. It was commented that
RAN WG3 are still considering the timestamp and this could be handled when feedback is available. It was
suggested to add an editor's note to check this. It was commented that the timestamp was not relevant for
AMF. China Mobile commented that it was uncertain that RAN WG3 are discussing this and suggested
adding the question to the proposed response LS. The figure also needed checking. This was left for off-line
discussion and revised, merging S2-2502937, to S2-2504128.

This was revised, to clean up revision marks, to S2-2504377.

It was agreed to change 'and/or' to 'and optionally'. This was revised to S2-2504470.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2502966 (CR) 23.256 CR0194 (Rel-19, 'C'): Instructing a UAV to stop the altitude reporting (Source:
Ericsson)
Document for: Approval
Abstract:
Summary of change: Adding new clause for stop of UAV UE altitude reporting.
Convenor comment: 5.16.X (new). Proposed to attach in Reply LS.

Parallel discussion:

A reference to TS 38.331 should be added to indicate the RAN impact. The title of the new clause should be
clarified to include 'and update'. The terminology in the figure should be aligned. This was left for off-line
discussion and revised to S2-2504129.

It was suggested to replace 'are to be described' with 'are described' in the note. Huawei asked for time to
check the references in step 7b-8b. This was left for off-line review and revised to S2-2504375.

Huawei commented that similarly to their comment on the CATT CR, it was not clear how step 2b is intended
to be handled. Ericsson replied that this will be decided by RAN WG3 whether to use a cause value within
the message or use a new cause value. Huawei was unsure whether we should ask RAN WG3 to define
this. Huawei commented that depending on the method used, this will impact the CATT CR which needs to
specify if the indication comes from the AMF or from the RAN. This should be considered with the CATT
proposed CR. This was then agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

3GPP
Report of meeting S2-168

S2-2503643 (CR) 23.256 CR0198 (Rel-19, 'C'): Altitude reporting cancellation (Source: CATT)
Document for: Approval
Abstract:
Summary of change: Add a new procedure on altitude reporting cancellation to support the UAS NF/NEF
cancels the ongoing altitude reporting.
Convenor comment: 4.4.1.1.3.1, 4.4.1.1.3.3, 4.4.1.1.3.5, 5.16.1, 5.16.x. Proposed to attach in Reply LS.

Parallel discussion:

The fifth change can be removed as it is covered by another CR. The alignment of terminology should be
checked. This was revised to S2-2504130.

Huawei suggested replacing '(4) events' with '(4) event'. Ericsson asked to clarify it is the failure to report that
is the trigger. This was left for off-line discussion and revised to S2-2504376.

This was reviewed and agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

Clarifications

S2-2503182 (CR) 23.256 CR0197 (Rel-19, 'F'): Procedures update (Source: CATT)
Document for: Approval
Abstract:
Summary of change: Update the step 4 in the procedure for NEF Assisted In-flight Monitoring in clause
5.12.3. Update the steps 4 and 8 in the figure 5.13.2-1 in the procedure for UAV changeover in clause
5.13.2.
Convenor comment: 5.12.3, 5.13.2.

Plenary Discussion:

Not handled.

Status: Not treated.

19.11.1 Study on UPF enhancement for Exposure And SBA Phase 2

(FS_UPEAS_Ph2)
This topic was not on the agenda for this meeting.

19.11.2 UPF enhancement for Exposure And SBA Phase 2 (UPEAS_Ph2)

This agenda item was convened by Wanqiang Zhang (Huawei).

S2-2503822 (CR) 23.288 CR1451 (Rel-19, 'B'): An optimized method for AF to obtain the DN-facing UE IP
address (Source: CEWiT)
Document for: Approval
Abstract:
Summary of change: Addition of a new clause 6.2.8.2.4.x which describes the procedure used by AF to
correlate UE data collection and NWDAF request using DN-facing UE IP address regardless of NAT status.
Comment: Noted in parallel session.

Parallel discussion:

This was noted in parallel session.

Status: Noted.

3GPP
Report of meeting S2-168

S2-2502955 (CR) 23.502 CR5390 (Rel-19, 'F'): Corrections on UPF Event Exposure (Source: Ericsson)
Document for: Approval
Abstract:
Summary of change: Following correction: In subscription to UE NAT mapping, Event Filter Information DNN
and S-NSSAI are used to identify the target natted information. The described relation between DNN, S-
NSSAI and AF ID is transparent to UPF and therefore removed.
Parallel discussion:

Remote end, port number of the remote end, DNN and S-NSSAI, and the IP domain. Revised in parallel
session to S2-2504037.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503034 (CR) 23.501 CR6177 (Rel-19, 'F'): Clarification to UPF selection based on specific UPF
functionalities (Source: Samsung)
Document for: Approval
Abstract:
Summary of change: DDOS -> DDOS protection Clarified the note for partially supported feature Clarified
how the required/preferred functionalities are used and how the optional parameter priority can be used.
Other editorial changes.
Comment: Check WI Code Capitalization!

Parallel discussion:

Undo the change on the note. Keep the 'standardized'. Revised in parallel session to S2-2504038.

Revised in parallel session to S2-2504081.

Fix the WI code. Second change, only keep the 'all' and remove the other changes. Revised in parallel
session to S2-2504085.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503036 (CR) 23.502 CR5401 (Rel-19, 'F'): Clarifications to Direct subscription to UPF Events in case of
session release or UPF relocation (Source: Samsung)
Document for: Approval
Abstract:
Summary of change: In clause 4.15.4.5.6, clarified that Remaining Data reporting indication has to be per
event For clause 4.15.4.5.7, updated the wording of the note to clarify UPF relocation/change scenarios.
Comment: Check WI Code Capitalization!

Parallel discussion:

Revised in parallel session to S2-2504039.

Fix the WI code. Revised in parallel session to S2-2504083.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

3GPP
Report of meeting S2-168

S2-2503037 (CR) 23.502 CR5402 (Rel-19, 'F'): Correction to direct subscription of UPF event expsoure
using UE IP address (Source: Samsung)
Document for: Approval
Abstract:
Summary of change: Added NEF in the note and changed 'before Step 1' -> 'before Step 3'.
Comment: Check WI Code Capitalization!

Parallel discussion:

Revised in parallel session to S2-2504040.

Correct the WID code. Fix the highlight. Revised in parallel session to S2-2504082.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503032 (CR) 23.501 CR6176 (Rel-19, 'F'): Clarification to usage of operator configurable UPF
capabilities in LBO roaming scenarios (Source: Samsung)
Document for: Approval
Abstract:
Summary of change: Added a note to clarify the usage of operator configurable UPF capabilities in LBO
scenarios.
Comment: Check WI Code Capitalization!

Parallel discussion:

Summary of change: Added a note to clarify the usage of operator configurable UPF capabilities in roaming
scenarios. Revised in parallel session to S2-2504041.

Summary of change: Added a note to clarify the usage of operator configurable UPF capabilities in roaming
scenarios. Fix the WI code.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

19.12.1 Study on System aspects of 5G NR Femto (FS_5G_Femto)

This topic was not on the agenda for this meeting.

19.12.2 System aspects of 5G NR Femto (5G_Femto)

This agenda item was convened by Andy Bennett (Samsung).

3GPP
Report of meeting S2-168

S2-2502827 (LS IN) LS from RAN WG3: LS on security verification related to NR Femtos (Source: RAN
WG3 (R3-250822))
Document for: Information
Abstract:
RAN WG3 has agreed to have an NR Femto architecture in Rel-19 with an optional NR Femto GW for NG
interface. RAN WG3 would like SA WG3 feedback on whether the following verifications need to be specified
for the NR Femto GW (and AMF, respectively), as outlined below: {. . .}.
Parallel discussion:

This LS was reviewed and noted in parallel session.

Status: Noted.

S2-2503302 (CR) 23.502 CR5425 (Rel-19, 'F'): Clarification on CAG Information Provisioning (Source: LG
Electronics)
Document for: Approval
Abstract:
Summary of change: Removed description on how to update Allowed CAG list and added reference. Clarify
that CAG ID(s) can be updated and if no validity time is present, CAG ID(s) are valid permanently.
Parallel discussion:

Nokia asked for the reason for the first change and commented that the next change should be simplified to
'the CAG can be added or removed', also the use of 'permanently' in the table may be misunderstood that
the time validity cannot be changed later. This was left for off-line discussion and revised to S2-2504136.

The changes in the table should reflect the actual changes to the base version. This was revised to S2-
2504398.

This was reviewed and agreed in parallel session.

Plenary Discussion:

This was block approved.

Parallel discussion:

The related CRs and proposed replies were reviewed. This LS was postponed in parallel session.

Status: Postponed.

S2-2503020 (CR) 23.502 CR5396 (Rel-19, 'F'): Correction for MA PDU Session of type Ethernet with
MPQUIC-E steering functionality for Roaming scenarios (Source: Nokia)
Document for: Approval
Abstract:
Summary of change: It is proposed that when MPQUIC-E steering functionality is used for a MA PDU
session, the H-SMF provides 'Transport Resource Type' IE to the V-SMF (if the V-SMF supports this
feature). The 'Transport Resource Type' IE contains IPv4 or IPv6 or IPv4v6 depending on the type of the
MPQUIC link specific addresses allocated for the MPQUIC connection(s). If the 'Transport Resource Type'
IE is received by the V-SMF, the V-SMF then signals to gNB the PDU session type as per the value received
in 'Transport Resource Type' IE.
Convenor comment: Handle - use as baseline.

Parallel discussion:

Samsung commented that the procedure should be made access agnostic and roaming impacts should be
avoided. CableLabs commented that in this case the procedure does not need to support non-3GPP
accesses. There was some discussion and issues raised and this was left for off-line discussion and revised
to S2-2504353.

LGE proposed postponing this CR in order to check if there are issues with PDU session interactions. A
number of issues were raised and more consideration was needed for this. Ericsson commented that there
appeared to be no common understanding of this mechanism and suggested postponing the topic. Nokia
agreed that if more time is needed this can be postponed until the next meeting. Companies were asked to
discuss this off-line before the next meeting and this was then postponed in parallel session.

Status: Postponed.

3GPP
Report of meeting S2-168

S2-2503076 (CR) 23.502 CR5397R1 (Rel-19, 'F'): Correction to EPS interworking for MA PDU Session of
type Ethernet with MPQUIC-E steering functionality. (Source: Nokia)
Document for: Approval
Abstract:
Summary of change: It is proposed that when MPQUIC-E steering functionality is used for a MA PDU
session, the PGW-C+SMF provides 'Transport Resource Type' IE to the MME. And if this IE is included then
the MME does not set the 'Ethernet Type' IE to eNodeB for the corresponding EPS Bearer. Additionally,
during mobility from EPS to 5GS this information is forwarded by the MME to the SMF.
Comment: Revision of S2-2503021 (Wrong document was uploaded).

Not handled.

Status: Not treated.

S2-2503432 (LS OUT) [DRAFT] LS on Ethernet MA PDU session using MPQUIC-E functionality (Source:
Huawei, HiSilicon)
Document for: Approval
Abstract:
The LS is to reply the LS from CT WG4 about MPQUIC-E functionality.
Comment: Response to S2-2502811.

Convenor comment: Merged into S2-2503022?

Plenary Discussion:

Not handled.

Status: Not treated.

3GPP
Report of meeting S2-168

S2-2503261 (CR) 23.501 CR6197 (Rel-19, 'F'): Handling of MPQUIC-E with EPS interworking (Source:
Ericsson)
Document for: Approval
Abstract:
Summary of change: Clarify how to handle the case where Ethernet PDN Type and MPQUIC-E is supported
by the UE and the network.
Convenor comment: Handle.

Parallel discussion:

This was left for off-line discussion and revised to S2-2504355.

This was postponed in parallel session.

Status: Postponed.

S2-2503262 (CR) 23.502 CR5421 (Rel-19, 'F'): Handling of MPQUIC-E with EPS interworking (Source:
Ericsson)
Document for: Approval
Abstract:
Summary of change: Clarify how to handle the case where Ethernet PDN Type and MPQUIC-E is supported
by the UE and the network.
Convenor comment: Merged into S2-2503076?

Parallel discussion:

LGE did not see any issue with the current handling and did not see the need to add these restrictions. Some
discussion ensued and this was left for off-line discussion and revised to S2-2504354.

This was postponed in parallel session.

Status: Postponed.

S2-2503263 (CR) 23.502 CR5422 (Rel-19, 'F'): Handling of MPQUIC-E in roaming cases (Source: Ericsson)
Document for: Approval
Abstract:
Summary of change: Clarify that H-SMF indicates to V-SMF when the Ethernet PDU Session carries IP
packets.
Convenor comment: Merged into S2-2503020?

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503264 (LS OUT) [DRAFT] Reply LS on Ethernet MA PDU session using MPQUIC-E steering (Source:
Ericsson)
Document for: Approval
Abstract:
Ths paper rpoposes a reply LS to the CT WG4 LS in C4-250554.
Comment: Response to S2-2502811.

Convenor comment: Merged into S2-2503022?

Plenary Discussion:

Not handled.

Status: Not treated.

3GPP
Report of meeting S2-168

Alignments

S2-2503429 (CR) 23.501 CR6218 (Rel-19, 'D'): Terminology alignment for steering functionality(ies) (Source:
Huawei, HiSilicon)
Document for: Approval
Abstract:
Summary of change: Terminology alignment for clause 5.32.2, 5.32.6.1, 5.32.6.2.2.1, 5.32.8.
Convenor comment: Handle.

Parallel discussion:

China Telecom commented that their proposal suggested differentiating the different MPQUIC proxies rather
than removing the '-UDP'. It was commented that it had already been agreed that the use of MPQUIC Proxy
should be used with the understanding that it could be different for different functions. This was left for off-
line discussion and revised, merging S2-2503278, to S2-2504357.

This was reviewed and agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503431 (CR) 23.503 CR1537 (Rel-19, 'D'): Terminology alignment for steering functionality(ies) (Source:
Huawei, HiSilicon)
Document for: Approval
Abstract:
Summary of change: Terminology alignment for clause 6.1.3.20.
Convenor comment: Handle.

Parallel discussion:

This was revised, to correct the CR rev number, to S2-2504358.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503889 (CR) 23.501 CR6275 (Rel-19, 'F'): Alignment with ATSSS Capability IE (Source: Apple)
Document for: Approval
Abstract:
Summary of change: Align UE capability indication for ATSSS with TS 24.501.
Comment: Should this be a mirror CR for S2-2503891?)!

Convenor comment: Handle.

S2-2503309 (CR) 23.502 CR5428 (Rel-19, 'F'): Clarification on IP version used for MPQUIC-E in procedure
(Source: LG Electronics)
Document for: Approval
Abstract:
Summary of change: Clarify how the UE and network determines IP version of MPQUIC link-specific
multipath addresses/prefixex and MPQUIC proxy information.
Convenor comment: Handle.

Plenary Discussion:

Not handled.

Status: Not treated.

3GPP
Report of meeting S2-168

S2-2503751 (CR) 23.501 CR6257 (Rel-19, 'F'): IP version used for MPQUIC-E (Source: Ericsson)
Document for: Approval
Abstract:
Summary of change: Specify that the UPF provides both IPv4 and IPv6 parameters when MPQUIC-E is
used.
Convenor comment: Handle.

Parallel discussion:

CableLabs commented that only a single address should be allocated and used. This was left for off-line
discussion and revised to S2-2504361.

Modification of the change was made. Revision marked should be cleaned up. Samsung, CATT, Apple and
Nokia asked to be added to the sources. This was revised, merging S2-2503738, to S2-2504406.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503752 (CR) 23.502 CR5471 (Rel-19, 'F'): IP version used for MPQUIC-E (Source: Ericsson)
Document for: Approval
Abstract:
Summary of change: Specify that the UPF provides both IPv4 and IPv6 parameters when MPQUIC-E is
used.
Convenor comment: Handle.

Status: Not treated.

S2-2503042 (CR) 23.502 CR5405 (Rel-19, 'F'): Correct Handling of IP version when MPQUIC-E is enabled
(Source: Samsung)
Document for: Approval
Abstract:
Summary of change: specified that, UE provides it's IP stack capabilities in case it indicated support of
MPQUIC-E specificed SMF/UPF behaviour on how to allocate the correct version of link-specific and mpquic
proxy information to UE.
Convenor comment: Handle.

Plenary Discussion:

Not handled.

Status: Not treated.

IP version of the two MPQUIC link-specific multipath addresses

S2-2503249 (DISCUSSION) Discussion on the consideration of IP version of the two MPQUIC link-specific
multipath addresses . (Source: China Mobile)
Document for: Discussion
Abstract:
This document discusses how to select the IP version of the two allocated MPQUIC link-specific multipath
addresses, with the consideration of the MPQUIC proxy information (i.e., address).
Convenor comment: Handle.

Plenary Discussion:

Status: Noted.

S2-2502835 (LS IN) LS from SA WG3: Reply LS on Device Subscription Data (Source: SA WG3 (S3-
251102))
Document for: Action
Abstract:
SA WG3 thanks SA WG2 for the LS on Device Subscription Data. SA WG3 will keep SA WG2 informed if
more progress on credential storage in network side. Action: SA WG2 is kindly requested to take the above
information into account.
Comment: Noted in parallel session.

Parallel discussion:

This was noted in parallel session.

Status: Noted.

S2-2502839 (LS IN) LS from SA WG5: Reply to LS on A-IoT Conclusions in SA WG2 (Source: SA WG5 (S5-
250680))
Document for: Action
Abstract:
SA WG5 thanks SA WG2 for providing the summary of overall progress on Ambient IoT. SA WG5 would also
like to inform the corresponding work plan to SA WG2 and RAN WG3. In Rel-19, SA WG5 will develop OAM
and charging support for the Ambient IoT feature, especially focusing on configuration management and
charging for AIoT service API exposure to align with the architecture definitions established by SA WG2 and
RAN WG3. Actions: To SA WG2, RAN WG3: SA WG5 kindly requests SA WG2 and RAN WG3 to promptly
inform SA WG5 if any specific OAM requirements emerge that need to be addressed.
Comment: Noted in parallel session.

Parallel discussion:

This was noted in parallel session.

Status: Noted.

3GPP
Report of meeting S2-168

Rederence point (clause 4.2, 4.3 and 4.4)

S2-2503200 (P-CR) 23.369: Terminology Alignment. (Source: Ericsson, Huawei, HiSilicon)

Document for: Approval
Abstract:
This pCR proposes some updates for terminology alignment.
Convenor comment:

Handle.

Parallel discussion:

Revised in parallel session to S2-2504011.

One objection. Add: The gNB may only support communication with AIoT devices. Revised in parallel
session to S2-2504319.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503848 (P-CR) 23.369: PCR for TS 23.369: AIoT Reference Point Naming . (Source: Huawei, HiSilicon)
Document for: Approval
Abstract:
The pCR proposed to addressed the editor s notes on AIoT reference point naming.
Convenor comment:

Handle. Reference point naming.

Parallel discussion:

Revised in parallel session to S2-2504012.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503199 (P-CR) 23.369: Clause 4.2.2 & 4.3: Reference Point Definition. (Source: Ericsson)
Document for: Approval
Abstract:
This pCR proposes and updates the reference point names and resolve the relevant ENs.
Convenor comment:

Focus on FFS on Ny interaface. Change on clause 4.3 merge into S2-2503848?

Parallel discussion:

Revised in parallel session to S2-2504013.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

3GPP
Report of meeting S2-168

S2-2503394 (CR) 23.501 CR6216 (Rel-19, 'F'): Reference Points and SBIs for Ambient IoT (Source:
Samsung)
Document for: Approval
Abstract:
Summary of change: Adding TS 23.369 as a new reference and new referfnce points and SBIs that are
newly defined in TS 23.369.
Convenor comment:

Handle, update to 23.501.

Parallel discussion:

Change the category to B. Remove the (Nx, Ny, Na, Nb, Nc, Nd, Ne and Nf) in second change. Revised in
parallel session to S2-2504014.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503390 (P-CR) 23.369: Reference Points. (Source: Samsung)

Document for: Approval
Abstract:
The contribution proposes reference point names for AIoT Architecture.
Comment: Merged into S2-2504012.

Convenor comment:

Merge into S2-2503848?

Parallel discussion:

Merged.

Status: Merged.

S2-2503842 (CR) 23.501 CR6265 (Rel-19, 'B'): Ambient IoT interfaces and reference points (Source:
Huawei, HiSilicon)
Document for: Approval
Abstract:
Summary of change: Add reference to Ambient IoT specifications for Ambient IoT reference points and
service-based interfaces.
Comment: Merged into S2-2504014.

Convenor comment:

Merge into S2-2503394?

Parallel discussion:

Merged.

Status: Merged.

3GPP
Report of meeting S2-168

S2-2503378 (P-CR) 23.369: AIoT RAN Connectivity. (Source: Samsung)

Document for: Approval
Abstract:
The contribution proposes normative text update for AIoT RAN Connectivity.
Comment: Merged into S2-2504013.

Convenor comment:

Merge into S2-2503199?

Parallel discussion:

Merged.

Status: Merged.

S2-2503649 (P-CR) 23.369: Discussion on Nx reference point interface between AIOTF and AIoT RAN.
(Source: Tejas Networks)
Document for: Approval
Abstract:
This contribution is to discuss the choice of reference point interface between AIOTF and AIoT RAN.
Comment: Merged into S2-2504013.

Convenor comment:

Merge into S2-2503199?

Parallel discussion:

Merged.

Status: Merged.

LS from RAN WG3 on reader selection

S2-2502832 (LS IN) LS from RAN WG3: LS on Ambient IoT progress of RAN WG3 (Source: RAN WG3 (R3-
250905))
Document for: Action
Abstract:
RAN WG3 would like to inform SA WG2 and SA WG5 about the following RAN WG3 progress related to
Architecture and OAM aspects: - A-IoT RAN node is an aggregated gNB. And this gNB may or may not only
provide the A-IoT radio. - Support both the direct and indirect communication options between the gNB and
the AIOTF in Topology 1. - Working assumption: Including AIOTF information containers in NGAP, rather
than introducing new protocol carried by NGAP. - It is FFS whether to define a new A-IoT Area, or use
Tracking Area dedicated for A-IoT, to support e.g., the selection of gNBs by the AIOTF. - AIOTF obtains the
A-IoT RAN information (supported Area, served reader ID list) via OAM configuration, FFS on RAN WG3
signalling for the A-IoT RAN information. - AIOTF may also be aware of the other A-IoT RAN information
(location of reader) via OAM configuration, FFS on RAN WG3 signalling for the other A-IoT RAN information.
- In Inventory Request, gNB receives the requested Service Area Information (encoded as Area and/or
reader ID list) from AIOTF. - The gNB always sends the A-IoT device's location at reader ID granularity to the
AIOTF in Inventory Report. - 'Global gNB ID + Reader index' is used to uniquely identify the Reader globally.
Action: RAN WG3 asks SA WG2 and SA WG5 to take above into account. RAN WG3 will further discuss the
FFS aspects in the following meetings and kindly ask SA WG2 and SA WG5 to provide feedback, if any.
Comment: Responses drafted in S2-2503106, S2-2503496.

Plenary Discussion:

Final response in S2-2504288.

Status: Replied to.

3GPP
Report of meeting S2-168

S2-2503106 (LS OUT) [DRAFT] LS Reply on Ambient IoT progress of RAN WG3 (Source: NEC)
Document for: Approval
Abstract:
LS Reply on Ambient IoT progress of RAN WG3 is suggested.
Comment: Response to S2-2502832.

Parallel discussion:

Revised in parallel session to S2-2504271.

Revised in parallel session to S2-2504273.

1. SA WG2 would ask whether the supported Area' is tracking area or new type of area. 2. SA WG2 would
like to ask whether one reader is only part of one supported area or can be part of multiple supported area
Remove SA WG5 in the action, CC to SA WG5. Re.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503496 (LS OUT) [DRAFT] LS Reply on Ambient IoT progress of RAN WG3 (Source: China Mobile
Com. Corporation)
Document for: Approval
Abstract:
To: RAN WG3, SA WG5.
Comment: Response to S2-2502832. Merged into S2-2504273.

Parallel discussion:

Merged.

Status: Merged.

NG-RAN and Reader selection (5.3)

S2-2503475 (P-CR) 23.369: PCR for TS 23.369: AIoT Reader Selection. (Source: China Mobile)
Document for: Approval
Abstract:
Address ENs about AIoT Reader Selection.
Convenor comment:

Handle.

Parallel discussion:

Revised in parallel session to S2-2504015.

Revised in parallel session to S2-2504270.

Change the wording: from the AIoT device context. Revised in parallel session to S2-2504289.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Merged.

Status: Merged.

S2-2503476 (DISCUSSION) AIoT Reader Selection discussion (Source: China Mobile Com. Corporation)
Document for: Information
Abstract:
AIoT Reader Selection discussion.
Comment: Noted in parallel session.

Parallel discussion:

This was noted in parallel session.

Status: Noted.

3GPP
Report of meeting S2-168

NF discovery and selection

S2-2503153 (P-CR) 23.369: AIOTF/AMF selection and NF profile. (Source: Vivo)

Document for: Approval
Abstract:
It proposes the update the RAN selection and introduce AIOTF/AMF selection for AIoT operation.
Convenor comment:

Handle. Focus on AMF selection.

Parallel discussion:

Revised in parallel session to S2-2504017.

Revised in parallel session to S2-2504272.

Change the EN: Editor's note: It is FFS whether and how the procedure is performed between AMF and
AIOTF in order to provide the NG-RAN ID of NG-RAN from the AMF to the AIOTF. Revised in parallel
session to S2-2504290.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503011 (P-CR) 23.369: AIOTF selection and AMF selection. (Source: CATT)
Document for: Approval
Abstract:
This paper adds AIOTF selection and AMF selection to TS 23.369.
Convenor comment:

Handle. Focus on AIOTF selection.

Parallel discussion:

Revised in parallel session to S2-2504016.

Revised in parallel session to S2-2504274.

Add more source companies. Revised in parallel session to S2-2504291.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

3GPP
Report of meeting S2-168

S2-2503792 (P-CR) 23.369: Update to Inventory procedure regarding AIOTF selection . (Source: InterDigital
Inc.)
Document for: Approval
Abstract:
The contribution proposes text to address the AIOTF selection open issue in the Inventory procedure.
Convenor comment:

Handle. Focus on EN on AIOTF selection.

Parallel discussion:

Revised in parallel session to S2-2504018.

Revised in parallel session to S2-2504276.

Only keep the change on step 12 and 13, remove the change on step 2. Revised in parallel session to S2-
2504292.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503197 (P-CR) 23.369: Clause 5.X & 6.2.2 & 6.2.3: AIOTF Discovery and Selection. (Source: Ericsson)
Document for: Approval
Abstract:
This pCR proposes AIOTF discovery and selection mechanism and resolve the relevant EN.
Comment: Merged into S2-2504016.

Convenor comment:

Merge into S2-2503011?

Parallel discussion:

Merged.

Status: Merged.

S2-2503874 (P-CR) 23.369: AIOTF selection. (Source: Samsung)

Document for: Approval
Abstract:
The paper proposes to update clause 5.3 and 7.5.1.
Comment: Merged into S2-2504016.

Convenor comment:

Merge into S2-2503011?

Parallel discussion:

Merged.

Status: Merged.

3GPP
Report of meeting S2-168

S2-2503195 (P-CR) 23.369: Clause 5.X: ADM Discovery and Selection. (Source: Ericsson)
Document for: Approval
Abstract:
This pCR proposes ADM discovery and selection mechanism.
Convenor comment:

Handle. ADM selection.

Parallel discussion:

Revised in parallel session to S2-2504019.

Add the or domain information EN: Editor's Note: The further investigation of factors for the ADM selection
will be needed and other factors are FFS. Revised in parallel session to S2-2504275.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503670 (P-CR) 23.369: ADM selection and related update. (Source: Vivo)
Document for: Approval
Abstract:
It proposes the introduce ADM selection and update to fix ENs for ADM.
Convenor comment:

Merge into S2-2503196?

Plenary Discussion:

Not handled.

Status: Not treated.

Assistance information (5.4)

S2-2502939 (P-CR) 23.369: Clause 5.4 updates. (Source: LG Electronics)

Document for: Approval
Abstract:
The paper proposes to update clause 5.4.
Convenor comment:

Handle.

Parallel discussion:

Revised in parallel session to S2-2504020.

Revised in parallel session to S2-2504277.

Revised in parallel session to S2-2504293.

Add more source companies. Revised in parallel session to S2-2504320.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

3GPP
Report of meeting S2-168

S2-2503833 (P-CR) 23.369: PCR for TS 23.369: Clarification on Assistance Information. (Source: Huawei,
HiSilicon)
Document for: Approval
Abstract:
Clause 5.4 is updated to solve the two Editor s Notes which are related to assistance information provided to
AIOT RAN node.
Comment: Merged into S2-2504277.

Convenor comment:

Merge into S2-2502939?

Parallel discussion:

Merged.

Status: Merged.

S2-2503477 (P-CR) 23.369: PCR for TS 23.369: update on Assistance information provided to AIoT RAN
Node. (Source: China Mobile)
Document for: Approval
Abstract:
This paper proposes an additional parameter AIoT reader ID(s) in the Assistance information provided to
AIoT RAN Node.
Comment: Merged into S2-2504277.

Convenor comment:

Merge into S2-2502939?

Parallel discussion:

Merged.

Status: Merged.

S2-2503381 (P-CR) 23.369: Assistance Information. (Source: Samsung)

Document for: Approval
Abstract:
The contribution proposes normative text for Assistance Information.
Comment: Merged into S2-2504277.

Convenor comment:

Merge into S2-2503196?

Parallel discussion:

Merged.

Status: Merged.

3GPP
Report of meeting S2-168

S2-2503466 (P-CR) 23.369: Text on assistance information to support command procedure. (Source: NTT
DOCOMO, T-Mobile USA)
Document for: Approval
Abstract:
Proposing text to the draft TS regarding assistance data.
Convenor comment:

Handle.

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503442 (DISCUSSION) Discussion on assistance information to support command. (Source: NTT

DOCOMO, T-Mobile USA)
Document for: Discussion
Abstract:
This paper discusses the need for assistance data to support command.
Convenor comment:

Noted?

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503161 (P-CR) 23.369: Update Assistance information for Inventory procedure . (Source: Ofinno)
Document for: Approval
Abstract:
The paper proposes to update clause 5.4.
Convenor comment:

Merge into S2-2503466?

Plenary Discussion:

Not handled.

Status: Not treated.

3GPP
Report of meeting S2-168

S2-2503794 (LS OUT) [DRAFT] LS on the need of indication of follow-up Command procedure in Inventory
request (Source: InterDigital Inc.)
Document for: Approval
Abstract:
SA2 kindly asks RAN1 and RAN2 to provide input on whether an indication (in the Inventory Request) of
follow-up Command procedure would assist or optimize the Inventory and Command procedure in the AIoT
RAN or BS Reader.
Convenor comment:

Handle.

Parallel discussion:

Revised in parallel session to S2-2504021.

Revised in parallel session to S2-2504278.

Change the action to SA WG2 kindly asks RAN WG2 and RAN WG3 to provide feedback. Revised in
parallel session to S2-2504294.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503201 (LS OUT) [DRAFT] LS on Assistance Information for Subsequent Command (Source: Ericsson)
Document for: Approval
Abstract:
This LS asks RAN WG2 the needs of providing subusequent command indicator in assistance information.
Comment: Merged into S2-2504021.

Convenor comment:

Merge into S2-2503794?

Parallel discussion:

Merged.

Status: Merged.

S2-2503691 (LS OUT) [DRAFT] LS on Command Indication in Inventory Request (Source: ZTE)
Document for: Approval
Abstract:
LS on Command Indication in Inventory Request.
Comment: Merged into S2-2504021.

Convenor comment:

Merge into S2-2503794?

Parallel discussion:

Merged.

Status: Merged.

3GPP
Report of meeting S2-168

S2-2503163 (LS OUT) [DRAFT] LS on Assistance information for follow-up Command procedure (Source:
Ofinno, LLC)
Document for: Approval
Abstract:
SA WG2 requests opinions from RAN WG2 and RAN WG3 if the additional assistance information is useful
for AIoT RAN.
Comment: Merged into S2-2504021.

Convenor comment:

Merge into S2-2503794?

Parallel discussion:

Merged.

Status: Merged.

AIoT device data profile management (5.5)

S2-2503841 (P-CR) 23.369: PCR for TS 23.369: Improve AIoT Device Profile Management. (Source:
Huawei, HiSilicon)
Document for: Approval
Abstract:
The paper address open issues for AIoT Device Profile Management, and add the support of permanent
disable.
Parallel discussion:

Revised in parallel session to S2-2504058.

Revised in parallel session to S2-2504279.

Revised in parallel session to S2-2504295.

Remove the new added EN: Editor's note: It is FFS how to stop AF request towards an AIoT device that has
been permanently disabled. Revised in parallel session to S2-2504321.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

3GPP
Report of meeting S2-168

AF authorization (5.6)

S2-2503196 (P-CR) 23.369: Clause 5.6 & 6.2.2 & 6.2.3: Resolve EN on AF Authorization. (Source: Ericsson)
Document for: Approval
Abstract:
This pCR updates AF authorization and resolve the relevant EN.
Convenor comment:

Handle.

Parallel discussion:

Revised in parallel session to S2-2504059.

The authorization of the AF for the AIoT includes two parts: ... AIOTF may perform. Revised in parallel
session to S2-2504280.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503002 (P-CR) 23.369: Addressing EN: AF authorization for Ambient IoT. (Source: Lenovo)
Document for: Approval
Abstract:
This paper proposes to address the EN in the AF authorization clause in TS 23.369 for AIoT.
Comment: Merged into S2-2504280.

Convenor comment:

Merge into S2-2503196?

Parallel discussion:

Merged.

Status: Merged.

S2-2503013 (P-CR) 23.369: Resolve EN on AF authorization. (Source: CATT)

Document for: Approval
Abstract:
This paper proposes to resolve the EN on AF authorization to TS 23.369.
Comment: Merged into S2-2504280.

Convenor comment:

Merge into S2-2503196?

Parallel discussion:

Merged.

Status: Merged.

3GPP
Report of meeting S2-168

S2-2503388 (P-CR) 23.369: AF Authorization. (Source: Samsung)

Document for: Approval
Abstract:
The contribution proposes normative text for AF Authorization Update.
Comment: Merged into S2-2504280.

Convenor comment:

Merge into S2-2503196?

Parallel discussion:

Merged.

Status: Merged.

S2-2503527 (P-CR) 23.369: Updates on AF authorization . (Source: Nokia)

Document for: Approval
Abstract:
This paper proposes to update the AF authorization section in the TS 23.369 for Ambient IoT.
Comment: Merged into S2-2504280.

Convenor comment:

Merge into S2-2503196?

Parallel discussion:

Merged.

Status: Merged.

S2-2503840 (P-CR) 23.369: PCR for TS 23.369: Address ENs for AF authorization. (Source: Huawei,
HiSilicon)
Document for: Approval
Abstract:
Address the EN for AF authorization.
Comment: Merged into S2-2504280.

Convenor comment:

Merge into S2-2503196?

Parallel discussion:

Merged.

Status: Merged.

3GPP
Report of meeting S2-168

AIoT device ID (5.7)

S2-2503845 (P-CR) 23.369: PCR for TS 23.369: Update of Device ID for NID. (Source: Huawei, HiSilicon)
Document for: Approval
Abstract:
The AIoT Device ID can contain an optional NID, but there is no indication it is present.
Convenor comment:

Handle.

Parallel discussion:

Revised in parallel session to S2-2504060.

Revised in parallel session to S2-2504281.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503849 (LS OUT) [DRAFT] LS on AIoT device identifier length (Source: Huawei, HiSilicon)
Document for: Approval
Abstract:
To: CT WG4. CC: CT WG1, RAN WG2, RAN WG3.
Convenor comment:

Handle.

Parallel discussion:

Revised in parallel session to S2-2504061.

Revised in parallel session to S2-2504282.

Change the text: From SA WG2 point of view, in order to achieve an efficient inventory process, the AIoT
Device Permanent Identifier should be designed in a reasonable length, which will be beneficial for
transmission on radio interface. In addition, a sh.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

3GPP
Report of meeting S2-168

S2-2503152 (P-CR) 23.369: PCR to TS 23.xyz: Filtering Information. (Source: Vivo)

Document for: Approval
Abstract:
It proposes to introduce filtering information.
Convenor comment:

Focus on 5.X.

Parallel discussion:

Revised in parallel session to S2-2504062.

Change the EN Editor's note: Whether and how to secure the filtering information is up to SA WG3. Revised
in parallel session to S2-2504283.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503046 (P-CR) 23.369: Update on AIoT Device ID information. (Source: OPPO)

Document for: Approval
Abstract:
This contribution is to update the AIoT Device ID information.
Comment: Noted in parallel session.

Parallel discussion:

This was noted in parallel session.

Status: Noted.

Clasue 6: AIoT service procedure

Inventory and command procedure documentation

S2-2503043 (P-CR) 23.369: Structure for documenting indirect path and Direct path. (Source: OPPO)
Document for: Approval
Abstract:
This contribution is to compare the two different structures for Inventory and Command procedure.
Convenor comment:

Handle. Topic for drafting session.

Parallel discussion:

Revised in parallel session to S2-2504063.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

3GPP
Report of meeting S2-168

S2-2503846 (P-CR) 23.369: PCR for TS 23.369: Procedure for AIOTF and AIoT Reader Communication.
(Source: Huawei, HiSilicon)
Document for: Approval
Abstract:
The procedure for AIOTF and AIoT Reader Communication is added to specify how AIoT Information is
transferred between AIOTF and AIoT Reader.
Comment: Merged into S2-2504063.

Convenor comment:

Handle. Topic for drafting session.

Parallel discussion:

Merged.

Status: Merged.

Inventory procedure update

S2-2503834 (P-CR) 23.369: PCR for TS 23.369: Update Inventory Procedure. (Source: Huawei, HiSilicon)
Document for: Approval
Abstract:
Clause 6.2.2 is updated to add more details about inventory procedure.
Convenor comment:

Handle.

Parallel discussion:

Revised in parallel session to S2-2504064.

Revised in parallel session to S2-2504284.

Step 14: The NEF in the final Nnef_AIoT_Notify message indicates that it is the last report for this operation.
Step 12: 12. Optionally, if the NG-RAN detects that no more AIoT Devices will respond to the inventory
procedure, the NG-RAN informs the AIOTF.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503009 (P-CR) 23.369: Update on Inventory procedure. (Source: CATT)

Document for: Approval
Abstract:
This paper updates the Inventory procedure of TS 23.369.
Comment: Merged into S2-2504064.

Convenor comment:

Merge into S2-2503834?

Parallel discussion:

Merged.

Status: Merged.

3GPP
Report of meeting S2-168

S2-2503048 (P-CR) 23.369: EN Resolution and Clarification in Inventory Procedure. (Source: OPPO)
Document for: Approval
Abstract:
This contribution addresses the storage of mapping between AIoT RAN Reader and AIoT Device ID(s) in
AIOTF and the resolution of the EN on whether an indication about follow-up Command to AIoT RAN from
AIOTF.
Comment: Merged into S2-2504064.

Convenor comment:

Merge into S2-2503834?

Parallel discussion:

Merged.

Status: Merged.

S2-2503149 (P-CR) 23.369: Update AIoT Inventory procedure for Command . (Source: Ofinno)
Document for: Approval
Abstract:
This paper proposes to update an Editor s note appearing in clause 6.2.2, Inventory procedure, in relation to
indicating to the AIoT RAN about whether there will be a follow up command or not.
Comment: Merged into S2-2504064.

Convenor comment:

Merge into S2-2503834?

Parallel discussion:

Merged.

Status: Merged.

S2-2503154 (P-CR) 23.369: Update to inventory procedure. (Source: Vivo)

Document for: Approval
Abstract:
It proposes the update to AIoT Inventory procedure to fix ENs.
Comment: Merged into S2-2504064.

Convenor comment:

Merge into S2-2503834?

Parallel discussion:

Merged.

Status: Merged.

3GPP
Report of meeting S2-168

S2-2503387 (P-CR) 23.369: Inventory Procedure Update. (Source: Samsung)

Document for: Approval
Abstract:
The contribution proposes normative text for Inventory Procedure Update in terms of paramenters.
Comment: Merged into S2-2504064.

Convenor comment:

Merge into S2-2503834?

Parallel discussion:

Parallel discussion:

Merged.

Status: Merged.

3GPP
Report of meeting S2-168

S2-2503045 (P-CR) 23.369: Update on the Aggregation in the Inventory and Command procedure. (Source:
OPPO)
Document for: Approval
Abstract:
This PCR is to update the aggregation in the Inventory and Command Procedure.
Comment: Merged into S2-2504064.

Convenor comment:

Merge into S2-2503834?

Parallel discussion:

Merged.

Status: Merged.

S2-2503843 (DISCUSSION) Discussion on RAN Procedure Interactions. (Source: Huawei, HiSilicon)

Document for: Discussion
Abstract:
Outline of the need and uses for keeping the CN and RAN aligned for when a procedure ends and the ability
to stop the procedure.
Convenor comment:

NOTED?

Plenary Discussion:

Not handled.

Status: Not treated.

Command procedure - AIoT data structure

S2-2503047 (P-CR) 23.369: EN resolution on AIoT data. (Source: OPPO)

Document for: Approval
Abstract:
This contribution is to resolve the EN on the AIoT data.
Comment: Postponed in parallel session.

Plenary Discussion:

Postponed.

Status: Postponed.

S2-2503380 (P-CR) 23.369: Command Type AIoT data. (Source: Samsung)

Document for: Approval
Abstract:
The contribution proposes normative text for Command Type AIoT data.
Convenor comment:

Focus on EN related to AIoT data structure.

Parallel discussion:

Revised in parallel session to S2-2504065.

Revised in parallel session to S2-2504285.

Plenary Discussion:

Postponed.

Status: Postponed.

3GPP
Report of meeting S2-168

Command procedure update - overall

S2-2503010 (P-CR) 23.369: Update on Command procedure. (Source: CATT)

Document for: Approval
Abstract:
This paper updates the Command procedure of TS 23.369.
Convenor comment:

Handle.

Parallel discussion:

Revised in parallel session to S2-2504066.

Revised in parallel session to S2-2504286.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503004 (P-CR) 23.369: Update for Command Procedure: Command failure handling. (Source: Lenovo,
China Telecom)
Document for: Approval
Abstract:
This paper proposes to add the descriptions of how to handle the command failure in the clause 6.2.3 of the
TS 23.369 for Ambient IoT.
Comment: Merged into S2-2504066.

Convenor comment:

Merge into S2-2503010?

Parallel discussion:

Merged.

Status: Merged.

S2-2503155 (P-CR) 23.369: Update to command procedure. (Source: Vivo)

Document for: Approval
Abstract:
It proposes to update to command procedure to fix ENs.
Comment: Merged into S2-2504066.

Convenor comment:

Merge into S2-2503010?

Parallel discussion:

Merged.

Status: Merged.

3GPP
Report of meeting S2-168

S2-2503382 (P-CR) 23.369: Command Procedure Update. (Source: Samsung)

Document for: Approval
Abstract:
The contribution proposes normative text for Command Procedure Update.
Comment: Merged into S2-2504066.

Convenor comment:

Merge into S2-2503010?

Parallel discussion:

Merged.

Status: Merged.

S2-2503469 (P-CR) 23.369: Updates to call flows to support command. (Source: NTT DOCOMO, T-Mobile
USA)
Document for: Approval
Abstract:
Proposing text to the draft TS regarding call flows.
Comment: Merged into S2-2504066.

Convenor comment:

Merge into S2-2503010?

Parallel discussion:

Merged.

Status: Merged.

S2-2503472 (P-CR) 23.369: Update Command Procedure. (Source: Sony)

Document for: Approval
Abstract:
Updates the Command procedure with clarifications and corrections.
Comment: Merged into S2-2504066.

Convenor comment:

Merge into S2-2503010?

Parallel discussion:

Merged.

Status: Merged.

S2-2503835 (P-CR) 23.369: PCR for TS 23.369: Update Command Procedure. (Source: Huawei, HiSilicon)
Document for: Approval
Abstract:
Clause 6.2.3 is updated to add more details for the AIoT command procedure.
Comment: Merged into S2-2504066.

Convenor comment:

Merge into S2-2503010?

Parallel discussion:

Merged.

Status: Merged.

3GPP
Report of meeting S2-168

S2-2503793 (P-CR) 23.369: Update to Command procedure. (Source: InterDigital Inc.)

Document for: Approval
Abstract:
The contribution proposes an update to the Command procedure to address various scenarios of the result
of the Inventory procedure.
Comment: Merged into S2-2504066.

Convenor comment:

Merge into S2-2503010?

Parallel discussion:

Merged.

Status: Merged.

NF description update (clause 4.5)

S2-2503003 (P-CR) 23.369: NF descriptions update for AIOTF and NRF. (Source: Lenovo, China Telecom)
Document for: Approval
Abstract:
This paper proposes to add the descriptions of the functional entities in the clause 4.5 of the TS 23.369 for
Ambient IoT.
Convenor comment:

Handle. for AIOTF and NRF part.

Parallel discussion:

Revised in parallel session to S2-2504067.

Remove the: Initiate and perform the inventory and command procedure by itself when the AF service
request indicated periodic execution. Revised in parallel session to S2-2504287.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503044 (P-CR) 23.369: Update on NF description. (Source: OPPO)

Document for: Approval
Abstract:
This contribution is to update NF description to resolve the ENs.
Convenor comment:

Handle. for AIoT device, and AMF part.

Plenary Discussion:

Not handled.

Status: Not treated.

3GPP
Report of meeting S2-168

S2-2503549 (P-CR) 23.369: Updates on aggregation . (Source: Nokia)

Document for: Approval
Abstract:
This paper proposes to add the descriptions about aggregation in the clause 4.5 of the TS 23.369 for
Ambient IoT.
Convenor comment:

Handle. For NG-RAN part.

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503157 (P-CR) 23.369: Update to Network Functions. (Source: Vivo)

Document for: Approval
Abstract:
It proposes the update the network functions to fix ENs.
Convenor comment:

Merge into S2-2503003?

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503502 (P-CR) 23.369: PCR to TS 23.369 on aggregation aspects. (Source: NTT DOCOMO)
Document for: Approval
Abstract:
Text on the aggregation aspects are proposed.
Convenor comment:

Merge into S2-2503003?

Plenary Discussion:

NF sevices update (7.X)

S2-2503836 (P-CR) 23.369: PCR for TS 23.369: Improve AIoT NF Services. (Source: Huawei, HiSilicon)
Document for: Approval
Abstract:
Address the open issues to support Ambient IoT services on the NFs.
Convenor comment:

Handle.

Plenary Discussion:

Not handled.

Status: Not treated.

3GPP
Report of meeting S2-168

S2-2503156 (P-CR) 23.369: Update to NF Services. (Source: Vivo)

Document for: Approval
Abstract:
It proposes the update services for AIoT operation to fix ENs.
Convenor comment:

Handle.

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503690 (P-CR) 23.369: PCR to TS 23.369: AIOTF and NEF Service Definition Update. (Source: ZTE)
Document for: Approval
Abstract:
The paper updates AIOTF and NEF provided AIoT service definition in clause 7 to address the editor s
notes.
Convenor comment:

Merge into S2-2503836?

Plenary Discussion:

Others

S2-2503609 (P-CR) 23.369: Update to clause 5.7 Identifiers. (Source: HONOR)

Document for: Approval
Abstract:
Update to clause 5.7: Identifiers and add the content about the AIoT device temporary identifier.
Convenor comment:

Device temporay ID. Not for handle.

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503847 (P-CR) 23.369: PCR for TS 23.369: Support of AIoT Device Temporary ID. (Source: Huawei,
HiSilicon)
Document for: Approval
Abstract:
The discussion paper provided observation on SA WG2 scope to support AIoT device temporary ID, and
proposed solution principles to support AIoT device temporary ID.
Convenor comment:

Device temporay ID. Not for handle.

Plenary Discussion:

Not handled.

Status: Not treated.

3GPP
Report of meeting S2-168

S2-2503687 (P-CR) 23.369: PCR to TS 23.369: Clarification on AIoT Device Profile Data. (Source: ZTE)
Document for: Approval
Abstract:
The paper adds AIoT device temporary ID in the profile data for AIoT devices.
Convenor comment:

Device temporay ID. Not for handle.

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503837 (P-CR) 23.369: PCR for TS 23.369: Support of AIoT Device Context Management. (Source:
Huawei, HiSilicon)
Document for: Approval
Abstract:
Add support of AIoT device context management.
Convenor comment:

AIoT device context management.

Plenary Discussion:

Not handled.

Status: Not treated.

Status: Not treated.

19.15.1 Core Network Enhanced Support for Artificial Intelligence

(AI)/Machine Learning (ML) (FS_AIML_CN)
This topic was not on the agenda for this meeting.

3GPP
Report of meeting S2-168

19.15.2 Core Network Enhanced Support for Artificial Intelligence

(AI)/Machine Learning (ML) (AIML_CN)
This agenda item was convened by Dario Tonesi (Qualcomm).

1st Round

KI#1 - AIML support for LMF positioning

KI#1: ML Model provisioning by OAM

S2-2502840 (LS IN) LS from SA WG5: Reply LS on ML Model provisioning by OAM to LMF for UE
positioning (Source: SA WG5 (S5-250826))
Document for: Action
Abstract:
SA WG5 thanks SA WG2 for the LS on ML Model provisioning by OAM to LMF for UE positioning in
document S2-2412890. SA WG5 has concluded the following answers for the questions of the LS as below:
{. .} Action: SA WG5 kindly asks SA WG2 to take the SA WG5's reply above into consideration and
welcomes further cooperation on the provision of ML Model for UE positioning.
Comment: Responses drafted in S2-2502857, S2-2503227, S2-2503340.

Plenary Discussion:

Final response in S2-2504197.

Status: Replied to.

S2-2502857 (LS OUT) [DRAFT] Reply LS on ML Model provisioning by OAM to LMF for UE positioning
(Source: ZTE)
Document for: Approval
Abstract:
To: SA WG5. Attachments: S2-2502818/S2-2502819.
Comment: Response to S2-2502840.

Parallel discussion:

Revised in parallel session to S2-2503963.

Revised in parallel session to S2-2504197.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503227 (LS OUT) [DRAFT] Reply LS on ML Model provisioning by OAM to LMF for UE positioning
(Source: Nokia)
Document for: Approval
Abstract:
To: SA WG5. Attachments: Agreed CR 712 for TS 23.273.
Comment: Response to S2-2502840.

Plenary Discussion:

Not handled.

Status: Not treated.

3GPP
Report of meeting S2-168

S2-2503340 (LS OUT) [DRAFT] Reply LS on ML Model provisioning by OAM to LMF for UE positioning
(Source: Huawei, HiSilicon)
Document for: Approval
Abstract:
It proposes to provide input regarding the data collection mechanisms defined in SA WG2.
Comment: Response to S2-2502840.

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503110 (CR) 23.273 CR0705 (Rel-19, 'F'): ML Model provisioning by OAM for LMF-based AI/ML
Positioning (Source: NTT DOCOMO, Ericsson)
Document for: Approval
Abstract:
Summary of change: Resolving the Editor's note on ML model provisioning by OAM for LMF-based AI/ML
positioning Adding a new clause to clarify the interaction between LMF and OAM.
Parallel discussion:

Revised in parallel session to S2-2503964.

Revised in parallel session to S2-2504198.

This was endorsed in parallel session.

Plenary Discussion:

This was block endorsed.

Status: Endorsed.

KI#1: LCS privacy & User consent

S2-2504199 (DISCUSSION) AIML_CN KI#1: Status and proposal on user consent and privacy profile
(Source: Apple)
Document for: Information
Abstract:
Slides on LCS privacy & User consent.
Comment: NEW PAPER TO HELP DISCUSSION. Noted in parallel session.

Parallel discussion:

To be discussed if SoH needed in May.

Plenary Discussion:

Noted.

Status: Noted.

3GPP
Report of meeting S2-168

S2-2502947 (CR) 23.273 CR0702 (Rel-19, 'F'): Changes on user consent and privacy for AIML-based
positioning (Source: Apple)
Document for: Approval
Abstract:
User consent and privacy updates for AI/ML-based positioning.
Parallel discussion:

Privacy check? User consent? Revised in parallel session to S2-2503965.

Plenary Discussion:

Postponed.

Status: Postponed.

S2-2503216 (CR) 23.273 CR0710 (Rel-19, 'F'): UE LCS privacy check for ground truth data collection and
input data storage for ML model training for AI/ML positioning (Source: Intel)
Document for: Approval
Abstract:
Summary of change: It is proposed to extend the NF that query to check the LCS privacy profile in UDM to
include LMF. The LMF checks if the NWDAF is authorized to retrieve UE location based on the UE privacy
profile stored as part of UE subscription data in the UDM. When authorized, the LMF sends the UE location
data (ground truth data) to the NWDAF.
Parallel discussion:

Merge privacy check part into S2-2503965? Revised in parallel session to S2-2504172.

Plenary Discussion:

Postponed.

Status: Postponed.

S2-2503598 (CR) 23.273 CR0721 (Rel-19, 'F'): Clarification on privacy check for data collection (Source:
Xiaomi)
Document for: Approval
Abstract:
Summary of change: Add clarification for privacy check for the ground truth data collection from UE in clause
5.18.2 and clause 6.22.3. Add LMF as LCS for allowed to locate the particular UE.
Comment: Merged into S2-2503965.

Parallel discussion:

Merged.

Status: Merged.

S2-2503668 (CR) 23.288 CR1449 (Rel-19, 'F'): UE LCS privacy check for AI/ML based positioning (Source:
Qualcomm Incorporated)
Document for: Approval
Abstract:
Summary of change: Clarify that LMF needs to check the user consent and UE LCS privacy in UDM during
the data collection procedure in clause 6.2E.4.
Parallel discussion:

Revised in parallel session to S2-2503966.

Plenary Discussion:

Postponed.

Status: Postponed.

3GPP
Report of meeting S2-168

KI#1: TS 23.273 clause 6.22.2 - case 2b

S2-2502802 (LS IN) LS from RAN WG2: Reply LS to SA WG2 on LMF-based AI/ML Positioning for Case 2b
(Source: RAN WG2 (R2-2501507))
Document for: Action
Abstract:
RAN WG2 thanks SA WG2 for the liaison in R2-2500062 [S2-2501133] to inform about the progress on LMF-
involved AI/ML positioning case 2b. Regarding the inquiry by SA WG2 to provide current progress and future
work plans, RAN WG2 has discussed the liaison, and RAN WG2 would like to provide the following
feedback: - Current progress: As per WID RP-243244, LMF-based AI/ML Positioning for Case 2a and Case
2b are second priority use cases, RAN WG2 has not made any discussion or agreement on Case 2a and
Case 2b. - RAN WG2 future work plan: RAN WG2 does not have any plan to work on Case 2a and Case 2b
in Rel-19. Action: RAN WG2 kindly asks SA WG2 to take the above feedback for AI/ML positioning use
cases into account.
Comment: Revision of S2-2501387. Noted in parallel session.

Parallel discussion:

This was noted in parallel session.

Status: Noted.

S2-2502818 (LS IN) LS from RAN WG1: Reply LS on LMF-based AI/ML Positioning for Case 2b (Source:
RAN WG1 (R1-2501523))
Document for: Action
Abstract:
RAN WG1 thanks SA WG2 for the LS on LMF-based AI/ML Positioning for Case 2b. RAN WG1 would like to
provide the following agreements and working assumptions reached up to RAN WG1#119 related to Case
2b as response to SA WG2 on data types and procedures, with reference to RAN WG1 chairman notes for
each. {. .} RAN WG1 may provide additional input in the future to SA WG2 for Case 2b if any new agreement
reached in RAN WG1. Action: RAN WG1 kindly asks SA WG2 to take the above answer into consideration in
future work.
Comment: Noted in parallel session.

Parallel discussion:

This was noted in parallel session.

Status: Noted.

S2-2502932 (CR) 23.273 CR0700 (Rel-19, 'C'): Removal of requirements related to case 2b (Source: Vivo,
Xiaomi, ZTE, OPPO, Mediatek Inc., Samsung, Nokia)
Document for: Approval
Abstract:
Summary of change: Remove requirements related to case 2b, i.e., UE-assisted/LMF-based positioning with
LMF-side model.
Parallel discussion:

Revised in parallel session to S2-2503967.

Undo first change in step 7 of 6.22.3. Revised in parallel session to S2-2504200.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

3GPP
Report of meeting S2-168

KI#1: TS 23.273 clause 6.22.3 - case 3b

S2-2502819 (LS IN) LS from RAN WG1: Reply LS on LMF-based AI/ML Positioning for Case 3b (Source:
RAN WG1 (R1-2500389))
Document for: Action
Abstract:
RAN WG1 thanks SA WG2 for the LS on LMF-based AI/ML Positioning for Case 3b. RAN WG1 would like to
provide the following agreements and working assumptions reached up to RAN WG1#119 related to Case
3b as response to SA WG2 on data types, with reference to RAN WG1 chairman notes for each. {. . .} RAN
WG1 would continue work and may provide additional input in the future to SA WG2 for Case 3b if any new
agreement reached in RAN WG1. Action: RAN WG1 respectfully asks SA WG2 to take the above reply into
account for their future work.
Comment: Noted in parallel session.

Parallel discussion:

This was noted in parallel session.

Status: Noted.

S2-2502826 (LS IN) LS from RAN WG3: Reply LS on LMF-based AI/ML Positioning for case 3b (Source:
RAN WG3 (R3-250796))
Document for: Action
Abstract:
RAN WG3 thanks SA WG2 for the reply LS on LMF-based AI/ML Positioning for case 3b in R3-250074/ S2-
2501341. The feedback from RAN WG3's perspective is provided separately for each of the following
Editor's Notes. {. .} The corresponding updates on NRPPa Measurement procedures will be available when
the Rel-19 TS 38.455 is published. Action: RAN WG3 kindly asks SA WG2 to take information above into
account.
Comment: Postponed in parallel session.

Plenary Discussion:

Postponed.

Status: Postponed.

S2-2503564 (CR) 23.273 CR0720 (Rel-19, 'F'): Resolve ENs on input data for LMF based AI/ML positioning
(Source: CATT)
Document for: Approval
Abstract:
Summary of change: Resolve the ENs on input data for LMF based AI/ML positioning. Remove the EN on
whether and how the LMF takes the RAN load into account.
Parallel discussion:

References to RAN WG1 or RAN WG3? Second last EN deletion in 6.22.3? Revised in parallel session to
S2-2503968.

Revised in parallel session to S2-2504201.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

3GPP
Report of meeting S2-168

KI#1: TS 23.273, 6.22.4 - data collection by NWDAF

S2-2502933 (CR) 23.273 CR0701 (Rel-19, 'F'): Update on input data collection by NWDAF for LMF-based
AIML positioning (Source: ETRI)
Document for: Approval
Abstract:
Summary of change: - NWDAF includes the 'purpose for data collection' in the procedure for input data
collection from LMF in clause 6.22.4 - Modify Nlmf_DataExposure_Subscribe service operation to include
'purpose for data collection'.
Comment: Noted in parallel session.

Parallel discussion:

This was noted in parallel session.

Status: Noted.

KI#2 - Vertical Federated Learning

KI#2: General

S2-2503319 (CR) 23.288 CR1433 (Rel-19, 'F'): Editor s Note clean up for the VFL (Source: OPPO)
Document for: Approval
Abstract:
Summary of change: Remove all the Editor's note related to the VFL. Add one sentence to clarify NWDAF
containing AnLF determine the VFL server AF during the VFL training phase as described in the clause
6.2H.2.3.2.
Parallel discussion:

Revised in parallel session to S2-2503969.

In NOTE 2 of 6.2H.2.2.1 '[.] UE can be registered to the network [.]'. Revised in parallel session to S2-
2504202.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

3GPP
Report of meeting S2-168

KI#2: VFL training (triggering of training, sample update, accuracy monitoring, etc.)

S2-2502863 (CR) 23.288 CR1411 (Rel-19, 'F'): Optimization of VFL triggers (Source: ZTE, Huawei, Hisilicon,
vivo, OPPO)
Document for: Approval
Abstract:
Summary of change: Introduce the time negotiation mechanism before the starts of VFL training and
inference. Add Analytics ID, VFL correlation ID, VFL server AF ID in the VFL training complete message of
case A. Wording improvements and Editorial corrections.
Parallel discussion:

Revised in parallel session to S2-2503970.

Revised in parallel session to S2-2504215.

Revised in parallel session to S2-2504221.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

3GPP
Report of meeting S2-168

S2-2503193 (CR) 23.288 CR1421 (Rel-19, 'F'): Update triggering Case A and some corrections and
Resolving ENs for VFL (Source: Ericsson, China Telecom)
Document for: Approval
Abstract:
Summary of change: Added details how VFL will be handled in Contents of ML Model Provisioning, clause
6.2A.2 In Training procedures: Resolving the EN Editor's note: When the AnLF determine the VFL server AF
is FFS. For example, during the training phase. by removing it since it is described that the VFL server is
learned in Training procedure. Resolving EN Editor's note: Whether weight of the VFL Client is computed by
VFL server is FFS. by keeping existing text on weights but making it a NOTE, since it only describes
internals of the VFL server Resolving EN Editor's note: Whether VFL server and VFL clients share feature
information is FFS. by removing it since no further feature information is to be shared Fixed errors in case A
and C Fixing duplicated text of starting training via Analytics request by removing case D in training
procedure, since same text is available in Inference procedure. The following NOTE is a duplicate of case A,
so remove NOTE 4: VFL Server can determine to start the training based on local configuration and
agreement among vendors and/or application providers participating in the same group for specific VFL
task(s). The content of Intermediate model training information is already stated in clause 6.2H.3 to not be
specified. So two NOTES 2 and 4 in training procedure are removed together with some text on examples
are removed from the procedure. Same with NOTE 8, which is removed since this info belongs better in
clause 6.2H.3 In the termination request from Server to clients, removing 'the termination message contains
VFL Correlation ID and may contain the intermediate model training information to each of the VFL clients'.
VFL correlation ID is superfluous since each subscription will contain the VFL correlation ID, and it is enough
just using the subscription correlation ID when doing unsubscribe. Also in unsubscribe usually no other
information than subscription correlation ID is sent, and see no reason to extend that in this case. If Server
would like to send 'the intermediate model training information to each of the VFL clients' after it has decided
to terminate the VFL, it can do a last round using subscription request, followed by an unsubscribe. In
Inference procedures: The Following NOTE in Inference procedure seems wrong since we have agreed on
aggregating clients when untrusted AF is server. NOTE 2: In this Release, it is assumed that local
intermediate inference is shared between VFL server and VFL client. So that NOTE is removed In clause
6.2H.3 Changing the heading to state services with a plural s Resolving EN Editor's note: Which parameters
are optional, or mandatory is FFS, the list of parameters also needs to be extended. by adding a few
parameters and also stating which ones are optional. The new parameters are VFL training iteration number,
Feature ID and use case context. Since VFL has the use case context available from AnLF, it can be
forwarded to support the clients to set-up the correct local model. Removing one duplicate parameter,
namely VFL Interoperability Information Adding the parameters for the new services Naf_training and
Nnef_Training In Service operation clauses: In clause 11.5.1 and 12.6.1 Resolving the ENs Editor s note:
Parameters of the service operations are FFS and more will be added when procedures and content of
services are agreed. by adding parameters Also resolving Editor s note: It is ffs whether this service is also
provided by an AF acting as VFL server and enables a consumer to request VFL Training. by removing it,
since we have agreed to use a new service for this.
Parallel discussion:

Revised in parallel session to S2-2503971.

Revised in parallel session to S2-2504220.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

3GPP
Report of meeting S2-168

S2-2503130 (CR) 23.288 CR1417 (Rel-19, 'F'): Alignment of existing mechanisms for accuracy generation
impacted by VFL procedures (Source: Huawei, HiSilicon, ZTE)
Document for: Approval
Abstract:
Summary of change: Updating Clause 6.2D.2 to allow the NWDAF containing AnLF to trigger the VFl
accuracy monitoring to support the selection of VFL Clients for the VFL Inference procedure and differentiate
the calculation of analytics accuracy information when VFL inference is performed. Updating Clause 6.2E.2
to enable the VFL Server to trigger the VFL accuracy monitoring during VFL training. Updating Clause
6.2E.3.1 with a NOTE indicating that this procedure is not required in case of ML Model trained with VFL
Training as VFL NWDAF containing AnLF and NWDAF containing MTLF are in this release of the
specification the same VFL Server.
Parallel discussion:

Revised in parallel session to S2-2503972.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

KI#2: VFL inference

S2-2503234 (CR) 23.288 CR1425 (Rel-19, 'F'): Parameters for vertical federated learning inference
procedure (Source: Nokia)
Document for: Approval
Abstract:
Summary of change: Add parameters as defined for the the analytics request (as defined in Clause 6.1.3 of
TS 23.228) that cannot be handled by the VFL server alone but need to be forwarded to the VFL clients also
to the VFL interence service. Also add the data time window as parameter to the service operations.
Removed resolved ENs.
Parallel discussion:

Revised in parallel session to S2-2503973.

Fix reference to new clause. Delete two last bullet added in 13th change. Revised in parallel session to S2-
2504216.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

3GPP
Report of meeting S2-168

S2-2503250 (CR) 23.288 CR1429 (Rel-19, 'F'): Updates on VFL inference (Source: Interdigital)
Document for: Approval
Abstract:
Summary of change: Analytic service request to the VFL server is clarified and Note is changed into
normative text.
Parallel discussion:

Revised in parallel session to S2-2503974.

Revised in parallel session to S2-2504217.

Revised in parallel session to S2-2504243.

This was agreed in parallel session.

Plenary Discussion:

Wrong document uploaded. Revised to S2-2504476.

This was block approved.

Status: Approved.

KI#2: Intermediate results sharing b/w VFL clients

S2-2503366 (CR) 23.288 CR1441 (Rel-19, 'F'): Clarification on Aggregator NWDAF Client Selection (Source:
LG Electronics)
Document for: Approval
Abstract:
Summary of change: 1. It is clarified that the NEF select any VFL client as an aggregator. 2. Added in a
NOTE that untrusted AF Server knows whether the NEF uses aggregator client by configuration. 3.
Alignment of the descriptions in training and inference procedure. 4. Editorial changes.
Parallel discussion:

To be decide which one is baseline (S2-2503718). Revised in parallel session to S2-2503975 (withdrawn).

Plenary Discussion:

Merged.

Status: Merged.

Withdrawn.

Status: Withdrawn.

S2-2503718 (CR) 23.288 CR1450 (Rel-19, 'F'): Maintenance of VFL model training and inference with client
intermediate results sharing between VFL clients (Source: Samsung)
Document for: Approval
Abstract:
Summary of change: Introduce new parameters to NWDAF and NEF service operations of model training
and inference to support intermediate results sharing between VFL clients. Clarification on model training
and inference procedures. Remove redundant EN from clause 6.2H.2.3.1. Other editorial changes.
Parallel discussion:

To be decide which one is baseline (S2-2503366). Revised in parallel session to S2-2503976.

Revised in parallel session to S2-2504218.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

3GPP
Report of meeting S2-168

KI#3 - NWDAF-assisted policy control and QoS enhancement

S2-2503410 (CR) 23.288 CR1386R1 (Rel-19, 'F'): Enhancements on the input and output of QoS and Policy
Assistance Analytics (Source: China Mobile)
Document for: Approval
Abstract:
Summary of change: RAN performance data collected from the OAM defined in clause 6.6.2 in TS 23.288 is
added as input. Delete 'Applicable duration of QoS and Policy Assistance information' in the output table.
Comment: Revision of (Unhandled) S2-2501699.

Parallel discussion:

Revised in parallel session to S2-2503977.

Revised in parallel session to S2-2504219.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

2nd Round (only if time allows)

Not handled.

Status: Not treated.

S2-2503253 (CR) 23.502 CR5420 (Rel-19, 'B'): AIML_CN KI#4 Resolve issues for event exposure and for
SCP mitigation actions (Source: Nokia)
Document for: Approval
Abstract:
Summary of change: 1. Confirm tentative text for SCP mitigation actions in ENs that are supported by CT
WG4 procedures. 2. Resolve Issues raided by CT WG4 by removing the following input parameters in the
Nnrf_NFManagement_NFStatusSubscribe service operation: - NF load status information, capacity and
priority information of NF and NF Services, etc as described in Table 6.22.2-2 and Table 6.22.2-5 of TS
23.288 [50]. 3. SCP event exposure in clause 5.2.29.2.1 can target specific NF service instances. Reported
'request type' relates to NF service instance if available and otherwise NF service name. 4. Fix identing in
clause 5.2.29.2.1 to clarify that a single event is being defined.
Plenary Discussion:

Not handled.

Status: Not treated.

General: incoming LS

S2-2502793 (LS IN) LS from RAN WG1: LS on signalling feasibility of dataset and parameter sharing
(Source: RAN WG1 (R1-2410922))
Document for: Information
Abstract:
The Rel-19 two-sided AI/ML CSI compression study for AI/ML Air Interface has the following study objectives
(RP-242399; revision of RP-240774) {. . .}.
Comment: Revision of S2-2501364.

Plenary Discussion:

Not Handled. Postponed.

Status: Postponed.

3GPP
Report of meeting S2-168

S2-2502841 (LS IN) LS from SA WG5: Reply LS on AI/ML UE sided data collection (Source: SA WG5 (S5-
250828))
Document for: Information
Abstract:
SA WG5 would like to thank TSG RAN for their LS in RP-243316 on AI/ML UE sided data collection. SA
WG5 has discussed the questions about the feasibility for transfer of data over UP for Solution 3 (UE-> gNB-
>OAM -> Server). SA WG5 has made the following analysis about the termination points of the UP tunnel for
this solution: {. . .}.
Convenor comment:

Reply to RP-243316 (S2-2502795).

Plenary Discussion:

Not Handled. Postponed.

Status: Postponed.

KI#1 - AIML support for LMF positioning

KI#1: Incoming LS

S2-2502792 (LS IN) LS from RAN WG1: Reply LS on data collection to enable ML model training and
inference in 5GC for Direct AI/ML based positioning (Source: RAN WG1 (R1-2405578))
Document for: Information
Abstract:
RAN WG1 thanks SA WG2 for the LS on data collection to enable ML model training and inference in 5GC
for direct AI/ML based positioning. RAN WG1 would like to provide the responses to the following questions
in SA WG2 LS (S2-2405833) based on RAN WG1 progress up to RAN WG1#117 meeting. {. . .}.
Furthermore, RAN WG1 would like to notify SA WG2 of the following: (a) RAN WG1 is still working on further
details of training data collection and model inference of Case 3b and 2b. RAN WG1 may provide additional
input to SA WG2 in the future. (b) For the related RAN work item (NR_AIML_air), Rel-19 WID (RP-240774)
has assigned Case 3b 1st priority, and Case 2b 2nd priority. (c) Note: in RAN WG1 agreement, 'AI/ML based
positioning' by itself refers to all positioning cases, including Case 3b and 2b. (d) Note: the working
assumptions and agreements above are based on RAN WG1 understanding for RAN work item
(NR_AIML_air). Action: RAN WG1 respectfully asks SA WG2 to take the above into account in their future
work.
Comment: Revision of S2-2501357.

Convenor comment:

Reply to S2-2405833.

Plenary Discussion:

Not Handled. Postponed.

Status: Postponed.

S2-2503190 (CR) 23.273 CR0708 (Rel-19, 'F'): LMF checking LCS privacy profile before collecting input
data and ground truth (Source: Ericsson, AT&T)
Document for: Approval
Abstract:
Summary of change: Remove user consent checks at the LMF and replace them for the LMF checking the
LCS privacy profile and related Editor s Notes for the user consent in relation with training and performance
monitoring of a ML Model.
Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503215 (DISCUSSION) Discussion on UE LCS privacy check for ground truth data collection and input
data storage for ML model training for AI/ML positioning . (Source: Intel)
Document for: Discussion
Abstract:
This DP discusses UE LCS privacy check for ground truth data collection at LMF and corresponding
proposal to resolve the issue with respect to ground truth data collection by LMF and storage at ADRF.
Detailed procedures are in S2-2503216, S2-2503217.
Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503217 (CR) 23.288 CR1423 (Rel-19, 'F'): UE LCS privacy check for ground truth data collection
(Source: Intel)
Document for: Approval
Abstract:
Summary of change: Extend the NF that query to check the LCS privacy profile in UDM to include LMF.
Plenary Discussion:

Not handled.

Status: Not treated.

3GPP
Report of meeting S2-168

S2-2503218 (CR) 23.273 CR0711 (Rel-19, 'F'): Input data storage in ADRF for ML model training for AI/ML
positioning (Source: Intel)
Document for: Approval
Abstract:
Summary of change: PLMN class operator client type in the UE LCS privacy profile to includes ADRF in the
LCS client list.
Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503663 (DISCUSSION) Discussion of the user consent and UE LCS privacy check for AI/ML based
positioning. (Source: Qualcomm Incorporated, Xiaomi)
Document for: Information
Abstract:
This discussion paper analyses the user consent procedure and the UE LCS privacy check procedure for
AI/ML based positioning.
Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503665 (CR) 23.273 CR0724 (Rel-19, 'F'): UE LCS privacy check for AI/ML based positioning (Source:
Qualcomm Incorporated)
Document for: Approval
Abstract:
Summary of change: Clarify that LMF will perform UE LCS privacy check in differetn clauses.
Plenary Discussion:

Not handled.

S2-2503693 (CR) 23.273 CR0726 (Rel-19, 'F'): Removal the EN about LMF taking into account RAN load
(Source: Qualcomm Incorporated)
Document for: Approval
Abstract:
Summary of change: Remove the editor's note regarding LMF considering the RAN load in clause 6.22.3.
Plenary Discussion:

Not handled.

Status: Not treated.

KI#1: TS 23.288

S2-2503347 (CR) 23.288 CR1435 (Rel-19, 'F'): Correction on VFL correlation ID handling (Source: Huawei,
HiSilicon)
Document for: Approval
Abstract:
Summary of change: Move the AF action above from preparation to training and align the inference
procedure.
Plenary Discussion:

Not handled.

Status: Not treated.

3GPP
Report of meeting S2-168

KI#2: Registration and discovery

S2-2503131 (CR) 23.288 CR1418 (Rel-19, 'F'): Clarification on registration and discovery for VFL (Source:
Huawei, HiSilicon)
Document for: Approval
Abstract:
Summary of change: 1. Update the discovery and selection for NWDAF as VFL server or NWDAF as VFL
client. 2. Update the discovery and selection for AF as VFL server or AF as VFL client. 3. Update the
Registration and Discovery procedure for VFL.
Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503194 (CR) 23.288 CR1422 (Rel-19, 'F'): Selection of aggregating client in VFL (Source: Ericsson)
Document for: Approval
Abstract:
Summary of change: First Registration and Discovery procedure: When VFL process shall start only one
VFL interoperability indicator is used, therefore removing plural indicators in Discovery, In same sentence
also replacing explicitly mentioned optional parameters with parameters described in clause 5.2. Second
Registration and Discovery procedure: Removed 'NWDAF as VFL client registers to NRF with its NF profile,
it may include those analytics IDs on which it supports to do VFL with AF as VFL server.', since it seems to
indicate some new type of registration, which is not the intention. Resolving following EN Editor's note: How
the NEF assists the VFL training process as well as whether the service operations going via NEF is using
the existing or new service operation are FFS. by adding how the aggregating client used in Training
procedure is selected by the MNO through NEF in clause 6.2H.2.1.2.
Plenary Discussion:

KI#2: VFL services

S2-2503242 (CR) 23.501 CR5676R4 (Rel-19, 'F'): KI#2: VFL services (Source: Nokia)
Document for: Approval
Abstract:
Summary of change: Define the following new services to support VFL: Nnwdaf_VflInference,
Naf_VflTraining, Naf_VflInference, Nnef_VflTraining, Nnef_VflInference.
Comment: Revision of (Unhandled) S2-2501499.

Plenary Discussion:

Not handled.

Status: Not treated.

KI#3 - NWDAF-assisted policy control and QoS enhancement)

S2-2502864 (CR) 23.288 CR1412 (Rel-19, 'F'): Output parameters clarifications in KI#3 (Source: ZTE)
Document for: Approval
Abstract:
Summary of change: Modify note 5 and table heading say it is a statistical data, not a prediction data.
Plenary Discussion:

Not handled.

Status: Not treated.

S2-2502934 (CR) 23.288 CR1416 (Rel-19, 'F'): Corrections on input data for QoS and policy assistance
analytics (Source: ETRI)
Document for: Approval
Abstract:
Summary of change: Add 'QoS Flow change' as an input data for QoS and policy assistance analytics to
align with clause 5.2.8.3.1 of TS 23.502.
Convenor comment:

S2-2503136 (CR) 23.288 CR1420 (Rel-19, 'F'): Adding SCP as data source for NWDAF data collection
(Source: Huawei, HiSilicon)
Document for: Approval
Abstract:
Summary of change: Editorial improvement on data channel procedures in clause 6.2 to supplement the
description on SCP. Remove the redundant signalling description related to the SCP. Correct the numbering
error of referred clause.
Plenary Discussion:

Not handled.

Status: Not treated.

3GPP
Report of meeting S2-168

S2-2503368 (CR) 23.288 CR1442 (Rel-19, 'F'): Clarification on Signalling Storm Analytics (Source: LG
Electronics)
Document for: Approval
Abstract:
Summary of change: 1. Clarify example actions of AMF to mitigate and prevent the signalling storm in Table
6.22.3-3. 2. Editorial changes.
Plenary Discussion:

Not handled.

Status: Not treated.

KI#4: TS 23.501

S2-2503134 (CR) 23.501 CR6184 (Rel-19, 'F'): Correction on usage of signalling storm analytics for
reliability of NF services (Source: Huawei, HiSilicon)
Document for: Approval
Abstract:
Summary of change: Remove the sentence of SCP actions regarding NF service reliability Some editorial
updates in clause 5.21.3.3.
Plenary Discussion:

Not handled.

KI#2: VFL - Others

S2-2503535 (CR) 23.273 CR0719 (Rel-19, 'F'): Address ENs for AI positioning case 3b (Source: Vivo)
Document for: Approval
Abstract:
Summary of change: Address some ENs by adding the Notes about how to collect the input data for case 3b.
Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503536 (CR) 23.288 CR1443 (Rel-19, 'F'): Clarification on VFL Server registration & discovery (Source:
Vivo)
Document for: Approval
Abstract:
Summary of change: - Distinct parameters clearly for VFL registration and VFL discovery correspondingly; -
Move the untrusted AF as VFL server's registration operation to a correct step for procedure of 6.2H.2.1.2. -
Other minor changes.
Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503537 (CR) 23.288 CR1444 (Rel-19, 'B'): Clarification on VFL inference (Source: Vivo)
Document for: Approval
Abstract:
Summary of change: Add a new clause to describe the contents of VFL inference service. Remove ENs in
clause 6.2H.2.4.1 and 6.2H.2.4.2.
Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503538 (CR) 23.288 CR1445 (Rel-19, 'F'): Clarification on VFL training (Source: Vivo)
Document for: Approval
Abstract:
Summary of change: Remove ENs in clause 6.2H.2.3. Wording update to clarify the service operation which
will be used.
Plenary Discussion:

Not handled.

Status: Not treated.

3GPP
Report of meeting S2-168

19.16 Indirect Network Sharing (TEI19_NetShare)

This agenda item was convened by Andy Bennett (Samsung).

S2-2503057 (CR) 23.501 CR6179 (Rel-19, 'F'): Clarification on Indirect Network Sharing (Source: China
Unicom)
Document for: Approval
Abstract:
Summary of change: Refine the wording in the clause 5.4.4.1a.
Parallel discussion:

This was reviewed and agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503876 (CR) 23.501 CR6271 (Rel-19, 'F'): Missing PLMN ID definition in GUAMI. (Source: Samsung)
Document for: Approval
Abstract:
Summary of change: Clarify PLMN-ID in GUAMI is always a selected PLMN ID during assignment from
AMF.
Parallel discussion:

Nokia commented that the whole clause is about GUTI and is not related to the TEI19_NetShare WI and did
not think this CR was really necessary. Samsung replied that they considered this clarification useful as the
use of Selected PLMN and GUAMI is not specified elsewhere in the Stage 2. China Telecom did not think
this was needed as it is covered by the CT WG1 Stage 3 specification. Nokia commented that the definition
of the GUAMI should not be mixed with the AMF procedure. This was left for off-line discussion and revised
to S2-2504135.

Nokia commented that the registered PLMN ID information should be specified elsewhere and questioned
whether this was needed. Samsung commented that the aim of the CR is to be able to understand the
GUAMI parameters when reading this clause. Nokia replied that this should be done in another clause. This
was left for off-line discussion and revised to S2-2504400 (withdrawn). S2-2504135 was postponed in
parallel session.

Status: Postponed.

19.17 Architecture support of roaming value-added services

(TEI19_RVAS)
This agenda item was convened by Andy Bennett (Samsung).

There were no contributions to this agenda item.

19.18 Minimize the Number of Policy Associations

(TEI19_MINPA)
This agenda item was convened by Andy Bennett (Samsung).

There were no contributions to this agenda item.

3GPP
Report of meeting S2-168

19.19 Deferred 5GC-MT-LR Procedure for Periodic Location

Events based NRPPa Periodic Measurement Reports
(TEI19_DLPMR)
This agenda item was convened by Andy Bennett (Samsung).

There were no contributions to this agenda item.

19.20 Providing per-subscriber VLAN instructions from UDM

(TEI19_VLANSUB)
This agenda item was convened by Andy Bennett (Samsung).

There were no contributions to this agenda item.

19.21 Enhancing Parameter Provisioning with static UE IP

address and UP security policy (TEI19_IP_SP_EXP)
This agenda item was convened by Andy Bennett (Samsung).

There were no contributions to this agenda item.

19.22 Spending Limits for UE Policies in Roaming scenario

(TEI19_SLUPiR)
This agenda item was convened by Andy Bennett (Samsung).

There were no contributions to this agenda item.

19.23 Subscription control for reference time distribution in EPS

(TEI19_TIME_SUB_EPS)
This agenda item was convened by Andy Bennett (Samsung).

There were no contributions to this agenda item.

19.24 On-demand broadcast of GNSS assistance data

(TEI19_OBGAD)
This agenda item was convened by Andy Bennett (Samsung).

There were no contributions to this agenda item.

3GPP
Report of meeting S2-168

19.25 QoS monitoring (TEI19_QME)

This agenda item was convened by Andy Bennett (Samsung).

There were no contributions to this agenda item.

19.26 NF discovery and selection by target PLMN

(TEI19_NFsel_by_tPLMN)
This agenda item was convened by Andy Bennett (Samsung).

There were no contributions to this agenda item.

19.27 Roaming traffic offloading via session breakout in HPLMN

(TEI19_HSBO)
This agenda item was convened by Andy Bennett (Samsung).

There were no contributions to this agenda item.

19.28 Multiple Location Procedure for Emergency LCS Routing

(TEI19_MLR4RTR)
This agenda item was convened by Andy Bennett (Samsung).

There were no contributions to this agenda item.

19.29 Support for ProSe services in NPNs (TEI19_ProSe_NPN)

This agenda item was convened by Andy Bennett (Samsung).

There were no contributions to this agenda item.

19.30 MSISDN verification operation support to Nnef_UEId

Service (TEI19_MVOSNS)
This agenda item was convened by Andy Bennett (Samsung).

There were no contributions to this agenda item.

19.31 ATSSS Rule Provisioning via 3GPP access connected to

EPC (TEI19_ARP3E)
This agenda item was convened by Andy Bennett (Samsung).

There were no contributions to this agenda item.

3GPP
Report of meeting S2-168

19.32 Network Controlled Network Slice Selection

(TEI19_SliceSel)
This agenda item was convened by Andy Bennett (Samsung).

LS in

S2-2502808 (LS IN) LS from CT WG3: LS on AF requested network slice replacement (Source: CT WG3
(C3-250572))
Document for: Action
Abstract:
CT WG3 is now working on stage 3 implementation of TEI19_SliceSel WI and notice that the existing
procedure 'AF-triggered dynamically changing access and mobility management policies' is re-used by the
AF to request network slice replacement. As per clauses 6.1.2.6.2 and 6.1.3.18 of TS 23.503, for an implicit
subscription for notification outcome of service area coverage change, the PCF reports the outcome of
service area coverage change using Npcf_EventExposure_Notify. Question 1: Does the PCF also re-use
Npcf_EventExposure_Notify to report the outcome of AF requested Network Slice Replacement?. Action: CT
WG3 kindly asks SA WG2 to answer the above questions and update the SA WG2 specifications
respectively, if necessary.
Comment: Responses drafted in S2-2503126, S2-2503619, S2-2503672.

Parallel discussion:

The related CRs and proposed replies were reviewed.

Plenary Discussion:

Final response in S2-2504147.

This was reviewed and agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503618 (CR) 23.503 CR1552 (Rel-19, 'F'): Clarification on notifying the outcome of network slice
replacement to AF (Source: ZTE)
Document for: Approval
Abstract:
Summary of change: The PCF uses Npcf_EventExposure_Notify service operation to notify the outcome of
network slice replacement to AF Remove duplication sentence in clause 6.1.2.6.1 and 6.1.2.6.2.
Parallel discussion:

Ericsson suggested moving the final added text to the earlier deletions and reinstate the original text. This
was left for off-line discussion and revised to S2-2504146.

Huawei asked why this was necessary as there are references to clause 6.1.3.18 for other features. Nokia
commented that if this clarifies for external readers it does no harm. This was then agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

3GPP
Report of meeting S2-168

Configured NSSAI

S2-2503676 (DISCUSSION) Discussion on removal of Replaced S-NSSAI from Configured NSSAI for AF
triggered slice replacement. (Source: Samsung)
Document for: Information
Abstract:
For the TEI19_SliceSel feature, there is an EN which is yet to be resolved though it was discussed in SA
WG2#166ahe (S2-2500952) and SA WG2#167 (S2-2502097) meeting.
Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503694 (CR) 23.501 CR6248 (Rel-19, 'F'): Addressing EN for AF requested slice selection (Source:
Samsung, LG Electronics)
Document for: Approval
Abstract:
Summary of change: Address the EN by adopting the approach of removing the Replaced S-NSSAI from
Configured NSSAI.
Parallel discussion:

Nokia objected to introducing further errors into the TS and suggested deleting the Editor's note as proposed
in their CR. This was left for off-line discussion. Noted in parallel session.

Status: Noted.

S2-2503187 (CR) 23.501 CR6190 (Rel-19, 'F'): Removal of EN about Configured NSSAI (Source: Nokia)
Document for: Approval
Abstract:
Summary of change: removal of the not necessary EN.
Parallel discussion:

Nokia clarified that they do not believe there is a problem and the Editor's note can be simply removed. This
was left for off-line discussion. This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

Slice replacement termination

S2-2502922 (CR) 23.501 CR6167 (Rel-19, 'F'): Support for Network initiated Slice Replacement Termination
(Source: Ericsson)
Document for: Approval
Abstract:
Summary of change: Both of the above conditions are treated by the AMF in an identical fashion to a UE
requesting termination of a slice replacement.
Parallel discussion:

Nokia questioned why this problem is identified in Rel-19 when it was not an issue in Rel-18. NEC
commented that when this scenario occurs it should return to a normal slice. This was left for off-line
discussion and revised to S2-2504148.

LGE raised an issue with some scenarios. Ericsson replied that this addresses the simple case of successful
slice replacement. Huawei asked for further discussion on this. This was then noted in parallel session.

Status: Noted.

3GPP
Report of meeting S2-168

S2-2503204 (CR) 23.501 CR6192 (Rel-19, 'F'): On the termination of slice replacement (Source: Nokia)
Document for: Approval
Abstract:
Summary of change: The AMF behaviour is clarified.
Parallel discussion:

Huawei asked why the internal behaviour needs to be specified. Nokia clarified that as it is specified to store
the information, it also needs to be specified to remove it. This was left for off-line discussion and revised to
S2-2504149.

An editorial correction was needed and revision marks should be removed from the cover sheet. LGE asked
to remove the final change. Nokia replied that if this change is removed, the information will be left in the
system. This was left for off-line discussion and revised to S2-2504402.

Huawei asked why the information should not always be removed. LGE commented that the information may
be needed by the AMF. Nokia commented that as this is a 'may' LGE can keep the information in the AMF if
they wish. It was decided to change 'may remove' to 'removes'. This was revised, also to clean revision
marks on the cover sheet, to S2-2504467.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503205 (CR) 23.502 CR5418 (Rel-19, 'F'): Clarification of Nnef_AMFInfluence based approach to AF
requested network slice replacement (Source: Nokia)
Document for: Approval
Abstract:
Summary of change: The procedure and the service operation have been updated.
Parallel discussion:

Some issues were raised and the status of CT WG3 discussions needed to be checked. This was left for off-
line discussion and revised to S2-2504150.

The changes on changes should be removed and an editorial corrected. This was revised to S2-2504403.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

3GPP
Report of meeting S2-168

S2-2503127 (CR) 23.503 CR1532 (Rel-19, 'F'): Clarification on AF requested network slice replacement
(Source: Huawei, HiSilicon)
Document for: Approval
Abstract:
Summary of change: Add description that PCF reports the outcome of AF requested Network Slice
Replacement via existing PCF event 'Notification on outcome Network Slice Replacement'.
Comment: Confirm Spec version used - CR states 19.2.0!

Parallel discussion:

Ericsson commented that this can be covered by the CR from ZTE. Huawei replied that the CR does not
describe the termination side. Ericsson preferred to have generic text to handle initiation and termination.
This was left for off-line discussion and revised to S2-2504151.

Some editorial corrections were needed. This was revised to S2-2504404.

This was agreed in parallel session.

Plenary Discussion:

An editorial error in 'replacement' needed correction. This was revised to S2-2504478.

This was approved.

Status: Approved.

Other aspects

S2-2503202 (CR) 23.501 CR6191 (Rel-19, 'F'): Feature interaction resolution (Source: Nokia)
Document for: Approval
Abstract:
Summary of change: The feature interaction is resolved.
Parallel discussion:

Ericsson asked for clarification of the added text as the sentence is difficult to understand. There was some
discussion and clarifications requested. This was left for off-line discussion and revised to S2-2504152.

Ericsson requested to postpone this to the next meeting in order to review other scenarios to be handled.
Huawei asked whether a simpler description can be developed as the multiple conditions are difficult to
understand. This was left for off-line discussion and revised to S2-2504405.

This was postponed in parallel session.

Status: Postponed.

19.33 PRU Usage Extension supported by Core Network

(TEI19_PRUE)
This agenda item was convened by Andy Bennett (Samsung).

There were no contributions to this agenda item.

19.48 Generic Rel-19 CRs

This topic was not on the agenda for this meeting.

3GPP
Report of meeting S2-168

19.49 Generic Rel-19 LSs

This topic was not on the agenda for this meeting.

19.50 Rel-19 CAT B/C alignment CR(s) due to the work led by
other 3GPP Working Groups
This agenda item was convened by Andy Bennett (Samsung).

eDRX and emergency

S2-2502969 (CR) 23.501 CR6084R1 (Rel-17, 'F'): Clarification of eDRX application with emergency service
(Source: Ericsson, AT&T, Qualcomm Incorporated)
Document for: Approval
Abstract:
Summary of change: Add a clarification NOTE in clause 5.31.7.2.1.
Comment: Revision of (Unhandled) S2-2501587. Check WI Code Capitalization (NR_redCap-Core)!

Plenary Discussion:

This was reviewed and left for off-line discussions and revised to S2-2504099.

Parallel discussion:

This should be considered when a response is received from RAN WG3. This was postponed in parallel
session.

Status: Postponed.

S2-2502970 (CR) 23.501 CR6085R1 (Rel-18, 'A'): Clarification of eDRX application with emergency service
(Source: Ericsson, AT&T, Qualcomm Incorporated)
Document for: Approval
Abstract:
Rel-18 mirror CR: Summary of change: Add a clarification NOTE in clause 5.31.7.2.1.
Comment: Revision of (Unhandled) S2-2501588. Check WI Code Capitalization (NR_redCap-Core)!

Parallel discussion:

This should be considered when a response is received from RAN WG3. This was postponed in parallel
session.

Status: Postponed.

S2-2502971 (CR) 23.501 CR6086R1 (Rel-19, 'A'): Clarification of eDRX application with emergency service
(Source: Ericsson, AT&T, Qualcomm Incorporated)
Document for: Approval
Abstract:
Rel-19 mirror CR: Summary of change: Add a clarification NOTE in clause 5.31.7.2.1.
Comment: Revision of (Unhandled) S2-2501589. Check WI Code Capitalization (NR_redCap-Core)!

Plenary Discussion:

Not handled.

Status: Not treated.

3GPP
Report of meeting S2-168

S2-2502972 (CR) 23.502 CR5338R1 (Rel-17, 'F'): Clarification on emergency PDU session release (Source:
Ericsson, AT&T, Qualcomm Incorporated, MediaTek Inc)
Document for: Approval
Abstract:
Summary of change: Add a NOTE in clause 4.3.4.2 to clarify the expected behaviour of emergency PDU
session handling for inactivity.
Comment: Revision of (Unhandled) S2-2501590. Check WI Code Capitalization (NR_redCap-Core)!

Plenary Discussion:

This was reviewed and left for off-line discussions and revised to S2-2504100.

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2502973 (CR) 23.502 CR5339R1 (Rel-18, 'A'): Clarification on emergency PDU session release (Source:
Ericsson, AT&T, Qualcomm Incorporated, MediaTek Inc)
Document for: Approval
Abstract:
Rel-18 mirror CR: Summary of change: Add a NOTE in clause 4.3.4.2 to clarify the expected behaviour of
emergency PDU session handling for inactivity.
Comment: Revision of (Unhandled) S2-2501591. Check WI Code Capitalization (NR_redCap-Core)!

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2502974 (CR) 23.502 CR5340R1 (Rel-19, 'A'): Clarification on emergency PDU session release (Source:
Ericsson, AT&T, Qualcomm Incorporated, MediaTek Inc)
Document for: Approval
Abstract:
Rel-19 mirror CR: Summary of change: Add a NOTE in clause 4.3.4.2 to clarify the expected behaviour of
emergency PDU session handling for inactivity.
Comment: Revision of (Unhandled) S2-2501592. Check WI Code Capitalization (NR_redCap-Core)!

Plenary Discussion:

Not handled.

Status: Not treated.

3GPP
Report of meeting S2-168

PSAP emergency callback

S2-2503854 (CR) 23.501 CR6267 (Rel-19, 'F'): Correction of PSAP call-back terminology (Source:
Vodafone)
Document for: Approval
Abstract:
Summary of change: 5.4.1.3, text changed from: To enable an emergency call back, to To enable a PSAP
to call-back the UE,. 5.16.4.9, Note modified: This releases all emergency call back resources related with
the old emergency PDU Session.
Parallel discussion:

The WI Code should add 5GS_Ph1. This was revised to S2-2504112.

This was reviewed and agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503831 (CR) 23.401 CR3898R1 (Rel-19, 'F'): PSAP emergency callback interaction with PSM (Source:
Vodafone)
Document for: Approval
Abstract:
Summary of change: Text added saying: 'To enable a PSAP to call-back the UE, after the release of an
emergency PDU session the UE should wait for a UE implementation-specific duration of time before
requesting the use of Power Save Mode.'.
Comment: Revision of S2-2502147.

Parallel discussion:

MediaTek did not accept this solution as it is not clear how the UE would implement a suitable wait time
period. Vodafone replied that this is the same as has been used for MIMO for some time. This was left for
off-line discussion. Vodafone clarified that a use case can be seen as an elevator emergency button, which
may initiate a voice call and may also need to be able to receive a call back. This was left for off-line
discussion and revised to S2-2504412.

A number of issues were raised on the need for this and this was postponed in parallel session.

Status: Postponed.

3GPP
Report of meeting S2-168

LP-WUS subgrouping

S2-2502821 (LS IN) LS from RAN WG2: Reply LS on LP-WUS subgrouping (Source: RAN WG2 (R2-
2501388))
Document for: Action
Abstract:
RAN WG2 thanks SA WG2 for the LS in S2-2412876 and provides the following feedback: 1) On the
terminology and naming of 'LP-WUS': It's not necessary that LP-WUS is transmitted with high power. Higher
power is just one possible way to ensure the coverage performance. The terminology has been used since
R18 Study Item on LP-WUS and the terminology is clear in RAN without any misunderstanding. Thus, RAN
WG2 confirmed that the 'LP-WUS' terminology can be used. 2) On the issue of UE radio capability for paging
information, RAN WG2 had the following agreement: Regarding the SA WG2 raised issue on UE Radio
Capability for Paging Information, R2 understand that there is no issue for NW after Release 17 (in which
case the LP-WUS UE-ID based subgrouping UE capability is included in the UE-RadioPagingInfo container).
Whether there is issue for Release 15 gNB and Release 16 gNB and for the other cases (for the features
mentioned by SA WG2 LS R2-2500050) can be further discussed in the coming RAN WG2 meetings based
on company contributions. Action: RAN WG2 respectfully asks SA WG2, RAN WG3, CT WG1 to take the
above answer into account.
Convenor comment: Reply to S2-2412876.

Parallel discussion:

The related CR was reviewed. This was then postponed in parallel session.

Status: Postponed.

S2-2503667 (CR) 23.501 CR6247 (Rel-19, 'F'): Multi-RAN-vendor support for paging of LP-WUS UEs
(Source: Vodafone)
Document for: Approval
Abstract:
Summary of change: gNB check for LP-WUS paging information in the NG-AP INITIAL CONTEXT SETUP
REQUEST added.
Parallel discussion:

Some clarifications were requested and this was left for off-line discussion. Vodafone commented that this
can be handled if a related RAN WG3 LS is received in time. No LS was received in time and this was
postponed in parallel session.

Status: Postponed.

CHF Group ID

S2-2503333 (CR) 23.502 CR5433 (Rel-19, 'F'): CHF Group ID in the needed contexts (Source: Nokia)
Document for: Approval
Abstract:
Summary of change: Contexts at the AMF, SMF and SMSF are updated to have the CHF Group ID as
known at these entities.
Parallel discussion:

The same change should also be added for the AMF data. This was left for off-line discussion and revised to
S2-2504113.

The revisions should be cleaned up on the cover sheet. This was revised to S2-2504413.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

3GPP
Report of meeting S2-168

20 Rel-20 SIDs and WIDs

There were no contributions to this agenda item.

20.1.1 Study on Integration of satellite components in the 5G architecture

Phase 4 (FS_5GSAT_Ph4_ARC)
This agenda item was convened by Dario Tonesi (Qualcomm).

TR Skeleton and TR Scope

S2-2503741 (P-CR) 23.700-19: FS_5GSAT_Ph4_ARC TR Skeleton. (Source: CATT)

Document for: Approval
Abstract:
This contribution aims to introduce the skeleton of the TR 23.700-19 for FS_5GSAT_Ph4_ARC.
Convenor comment:

Handle.

Parallel discussion:

Revised in parallel session to S2-2503943.

Add 'High level principles' clause. Remove 'Overall evaluation'. Revised in parallel session to S2-2504185.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503742 (P-CR) 23.700-19: FS_5GSAT_Ph4_ARC TR Scope. (Source: CATT)

Document for: Approval
Abstract:
This paper proposes the scope of FS_5GSAT_Ph4_ARC.
Convenor comment:

Handle.

Parallel discussion:

Revised in parallel session to S2-2503944.

Revised in parallel session to S2-2504186.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

3GPP
Report of meeting S2-168

Architectural assumptions

S2-2503487 (P-CR) 23.700-19: 23.700-19: Architecture principles and assumptions . (Source: Vivo)
Document for: Approval
Abstract:
This paper is to propose the architecture assumptions for FS_5GSAT_Ph4_ARC WT#1, i.e. to support IMS
voice call over GEO via NB-IoT NTN connecting to EPC, and UE-SAT-UE for 5GLAN services.
Convenor comment:

Handle baseline for WT-1.

Parallel discussion:

Revised in parallel session to S2-2503945.

Revised in parallel session to S2-2503947.

Revised in parallel session to S2-2504187.

This was agreed in parallel session.

Not handled.

Status: Not treated.

S2-2503269 (P-CR) 23.700-19: Architecture assumptions for IMS voice call over NB-IoT (GEO). (Source:
Ericsson)
Document for: Approval
Abstract:
This contribution proposes architecture assumptions for supporting IMS voice call over NB-IoT (GEO).
Convenor comment:

Merge into S2-2503487?

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503657 (P-CR) 23.700-19: [AA] Architecture assumptions. (Source: Huawei, HiSilicon)

Document for: Approval
Abstract:
Architecture Assumptions for 5GSAT_Ph4-ARC based on those used in phase 3.
Convenor comment:

Handle baseline for WT-2. Merge WT-1 part into S2-2503487?

Parallel discussion:

Revised in parallel session to S2-2503946.

Revised in parallel session to S2-2503948.

Revised in parallel session to S2-2504188.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

3GPP
Report of meeting S2-168

S2-2503080 (P-CR) 23.700-19: FS_5GSAT_Ph4_ARC Architecture Assumptions. (Source: Nokia)

Document for: Approval
Abstract:
Architecture assumptions for FS_5GSAT_Ph4_ARC.
Convenor comment:

Merge into S2-2503487 and S2-2503657?

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503362 (P-CR) 23.700-19: Architectural Assumptions. (Source: LG Electronics)

Document for: Approval
Abstract:
This paper proposes to add some descriptions into the clause on Architectural Assumptions of TR 23.700-
19.
Convenor comment:

Merge into S2-2503487 and S2-2503657?

Plenary Discussion:

Not handled.

KI for WT1 (IMS voice call over GEO via NB-IoT NTN connecting to EPC)

S2-2503486 (DISCUSSION) Discussion paper on CP/UP-based solutions (Source: vivo)

Document for: Discussion
Abstract:
Some starting points of CP/UP based solutions.
Convenor comment:

Handle.

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503497 (DISCUSSION) Emergency Call Optimization and IMS Registration optimization needs to be
included in the scope for voice using GEO. (Source: MediaTek Inc.)
Document for: Discussion
Abstract:
This discussion paper discuss why enhancement for Emergency Call for voice using GEO is needed and
why enhancement for IMS Registration is needed.
Convenor comment:

Handle.

Plenary Discussion:

Not handled.

Status: Not treated.

3GPP
Report of meeting S2-168

S2-2503744 (P-CR) 23.700-19: FS_5GSAT_Ph4_ARC Key issues for WT#1. (Source: CATT, vivo)
Document for: Approval
Abstract:
This paper is to propose new key issue for FS_5GSAT_Ph4_ARC.
Convenor comment:

Handle - baseline.

Parallel discussion:

Revised in parallel session to S2-2503949.

Revised in parallel session to S2-2504191.

Revised in parallel session to S2-2504223.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503488 (P-CR) 23.700-19: FS_5GSAT_Ph4-ARC Key issue on Support of IMS voice over NB-IoT
(GEO) satellite access to EPC. (Source: Vivo, MediaTek Inc.)
Document for: Approval
Abstract:
Propose new key issues on support of IMS IP-CAN over NB-IoT (GEO) satellite access to EPC.
Comment: Merged into S2-2504223.

Parallel discussion:

Focus on registration for emergency call.

Plenary Discussion:

Merged.

Status: Merged.

S2-2503077 (P-CR) 23.700-19: FS_5GSAT_Ph4_ARC Key issues for WT#1: Support of IMS voice over
GEO NB-IoT NTN connecting to EPC. (Source: Nokia)
Document for: Approval
Abstract:
This contribution proposes KIs for WT#1 of FS_5GSAT_Ph4_ARC.
Convenor comment:

Merge into S2-2503744?

Plenary Discussion:

Not handled.

Status: Not treated.

3GPP
Report of meeting S2-168

S2-2503389 (P-CR) 23.700-19: 23.700-19: Key issues for QoS aspect of GEO call. (Source: China Telecom)
Document for: Approval
Abstract:
This paper proposes new key issue for QoS aspect of GEO call.
Convenor comment:

Merge into S2-2503744?

Plenary Discussion:

Not handled.

Status: Not treated.

3GPP
Report of meeting S2-168

KI for WT2 (UE-SAT-UE comm. enh. for 5GS under NR NTN NGSO const. w/ feeder link available)

S2-2503166 (P-CR) 23.700-19: Key issue for WT#2: UE-SAT-UE communication enhancement for NR NTN
NGSO constellation with feeder link available. (Source: Samsung)
Document for: Approval
Abstract:
The contribution proposes the key issue for UE-SAT-UE communication enhancement for supporting non-
IMS services.
Convenor comment:

Handle - baseline (presented in CC).

Parallel discussion:

Revised in parallel session to S2-2503950.

Include ' Whether and how to support service/session continuity during the UPF(s) change'? Revised in
parallel session to S2-2504224.

Corrupt document. Revised in parallel session to S2-2504245.

Plenary Discussion:

Noted.

Status: Noted.

S2-2503861 (P-CR) 23.700-19: 23.700-19 Key Issues: UE-SAT-UE communication for non-IMS services.
(Source: TNO)
Document for: Approval
Abstract:
A new key issue is proposed for UE-SAT-UE work task WT#2.2 for the FS_5GSAT_Ph4_ARC.
Comment: Noted in parallel session.

Parallel discussion:

This was noted in parallel session.

Status: Noted.

S2-2503277 (P-CR) 23.700-19: 23.700-19: Key issues for UE-SAT-UE communication for non-IMS services.
(Source: China Telecom)
Document for: Approval
Abstract:
This paper proposes new key issues for UE-SAT-UE communication for non-IMS services.
Comment: Merged into S2-2504224.

Parallel discussion:

Merged.

Status: Merged.

3GPP
Report of meeting S2-168

S2-2503491 (P-CR) 23.700-19: Key issue for WT#2.2. (Source: China Mobile)
Document for: Approval
Abstract:
This paper proposes a key issue for the WT#2.2 of FS_5GSAT_ARCH_Ph4.
Plenary Discussion:

Not handled.

Status: Not treated.

3GPP
Report of meeting S2-168

3GPP
Report of meeting S2-168

Solution for WT1 (Max 2 rounds; Max 1 paper per company per round)

S2-2503019 (P-CR) 23.700-19: New solution of IMS call setup procedure simplification for WT#1 GEO voice
support. (Source: OPPO)
Document for: Approval
Abstract:
This paper proposes a new solution of IMS call setup procedure simplification for WT#1 GEO voice.
Convenor comment:

Handle if time allows.

Parallel discussion:

Revised in parallel session to S2-2503951.

Revised in parallel session to S2-2504225.

Plenary Discussion:

Postponed.

Status: Postponed.

S2-2503220 (P-CR) 23.700-19: WT1: Solution for providing IMS voice over GEO via Control Plane. (Source:
Qualcomm Incorporated)
Document for: Approval
Abstract:
Solution for providing IMS voice over GEO via Control Plane.
Convenor comment:

Handle if time allows.

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503221 (P-CR) 23.700-19: WT1: Solution for providing IMS voice over GEO via User Plane. (Source:
Qualcomm Incorporated)
Document for: Approval
Abstract:
Solution for providing IMS voice over GEO via User Plane.
Convenor comment:

Handle if time allows.

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503311 (P-CR) 23.700-19: WT1: Solution for IMS signaling performance optimization to support voice
over GEO . (Source: Qualcomm Incorporated)
Document for: Approval
Abstract:
This contribution proposed proposes a solution for optimization of IMS signalling performance.
Plenary Discussion:

Not handled.

Status: Not treated.

3GPP
Report of meeting S2-168

S2-2503501 (P-CR) 23.700-19: KI #X: New Solution: CST reduction by pre-negotiate SDP parameters
during SIP registration. (Source: MediaTek Inc.)
Document for: Approval
Abstract:
The contribution proposes a solution to KI #X: XXXXXXX.
Plenary Discussion:

Not handled.

Status: Not treated.

3GPP
Report of meeting S2-168

3GPP
Report of meeting S2-168

S2-2503576 (P-CR) 23.700-19: KI#1: New Sol: Support of capability exchange and NAS timer adjustment for
IMS voice service over GEO satellite. (Source: NTT DOCOMO)
Document for: Approval
Abstract:
This contribution proposes a new solution for KI#1.
Plenary Discussion:

S2-2502943 (P-CR) 23.700-14: TR Skeleton for FS_Sensing_ARC (Source: Apple, Xiaomi)

Document for: Approval
Abstract:
TR Skeleton for FS_Sensing_ARC.
Comment: Skeleton TR.

Convenor comment:

Handle.

Parallel discussion:

Revised in parallel session to S2-2504047.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2502944 (P-CR) 23.700-14: TR Scope for FS_Sensing_ARC . (Source: Apple, Xiaomi)

Document for: Approval
Abstract:
This paper proposes a TR scope for FS_Sensing_ARC.
Convenor comment:

Handle.

Parallel discussion:

Revised in parallel session to S2-2504048.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

3GPP
Report of meeting S2-168

Terms and Definitions

S2-2503798 (P-CR) 23.700-14: Terms of Sensing study. (Source: Huawei, HiSilicon)

Document for: Approval
Abstract:
The architecture assumptions for FS_Sensing_ARC are proposed.
Convenor comment:

Handle - use as baseline.

Parallel discussion:

Revised in parallel session to S2-2504049.

Revised in parallel session to S2-2504261.

Revised in parallel session to S2-2504324.

Revised in parallel session to S2-2504331.

Plenary Discussion:

This was reviewed and approved.

Status: Approved.

S2-2503445 (P-CR) 23.700-14: Adding Definitions and terminologies. (Source: ZTE)

Document for: Approval
Abstract:
This contribution proposes to add Definitions and terminologies for this study.
Comment: Merged into S2-2504261.

Convenor comment:

Merge into S2-2503798.

Parallel discussion:

Merged.

Status: Merged.

S2-2503705 (P-CR) 23.700-14: Terms for the 5GS sensing architecture. (Source: Lenovo)
Document for: Approval
Abstract:
This paper proposes new terms to be used during the study of the sensing architecture in 5GS.
Comment: Merged into S2-2504261.

Convenor comment:

Merge into S2-2503798.

Parallel discussion:

Merged.

Status: Merged.

3GPP
Report of meeting S2-168

S2-2503865 (P-CR) 23.700-14: Terms for FS_Sensing_ARC . (Source: Xiaomi)

Document for: Approval
Abstract:
This paper proposes the terms for FS_Sensing-ARC based on SA WG1 specification (TS 22.137).
Comment: Merged into S2-2504261.

Convenor comment:

Merge into S2-2503798.

Parallel discussion:

Merged.

Status: Merged.

Architectural assumptions and requirements

S2-2502960 (P-CR) 23.700-14: Adding Architecture assumptions and requirements. (Source: Ericsson)
Document for: Approval
Abstract:
This contribution discusses and proposes Architecture assumptions and requirements for sensing
functionality in 5GA study.
Convenor comment:

Handle - use as baseline for architectural requirement.

Parallel discussion:

Revised in parallel session to S2-2504057.

Revised in parallel session to S2-2504262.

Add a new note: Note X: Potential privacy requirements if identified during the study will be considered for
the study of the sensing architecture Second bullet: The core network aspects of Sensing architecture need
to be agnostic to 3GPP radio access tec.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

3GPP
Report of meeting S2-168

S2-2503272 (P-CR) 23.700-14: Architectural Assumptions and Requirements for sensing service. (Source:
China Telecom)
Document for: Approval
Abstract:
The contribution proposes architectural assumptions and principles for sensing service.
Convenor comment:

Handle - use as baseline for architectural assumption.

Parallel discussion:

Revised in parallel session to S2-2504056.

Revised in parallel session to S2-2504263.

Note 1: NOTE 1: LTE and all previous 3GPP access technologies are not in scope Remove the first EN. The
sensing function(s), and sensing entities are within the same PLMN in this study. Revised in parallel session
to S2-2504323.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503771 (P-CR) 23.700-14: Architectural Requirements of ISAC. (Source: Nokia, Nokia Shanghai Bell)
Document for: Approval
Abstract:
This paper proposes Architectural Requirements for the Study on Architecture Enhancement to support
Integrated Sensing and Communication (FS_Sensing_ARC).
Convenor comment:

Handle.

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503704 (P-CR) 23.700-14: Architectural assumptions for the 5GS sensing architecture. (Source:
Lenovo)
Document for: Approval
Abstract:
This paper proposes architectural assumptions for the sensing architecture in 5GS.
Convenor comment:

Handle.

Plenary Discussion:

Not handled.

Status: Not treated.

3GPP
Report of meeting S2-168

S2-2503028 (P-CR) 23.700-14: Architectural Assumptions and Requirements. (Source: LG Electronics)

Document for: Approval
Abstract:
The paper proposes Architectural Assumptions and Requirements for FS_Sensing_ARC.
Comment: Merged into S2-2504263.

Convenor comment:

Merge architectural assumption into S2-2503272, architectural requirement part into S2-2502960.

Parallel discussion:

Merged.

Status: Merged.

S2-2503064 (P-CR) 23.700-14: Architectural Assumptions and Requirements for ISAC. (Source: Vivo)
Document for: Approval
Abstract:
This paper is to add Architectural Assumptions and Requirements for ISAC.
Comment: Merged into S2-2504263.

Convenor comment:

Merge architectural assumption into S2-2503272, architectural requirement part into S2-2502960.

Parallel discussion:

Merged.

Status: Merged.

S2-2503101 (P-CR) 23.700-14: Architecture assumptions and requirements. (Source: OPPO)

Document for: Approval
Abstract:
The contribution proposes the architecture assumptions and requirements to support sensing service.
Comment: Merged into S2-2504263.

Convenor comment:

Merge architectural assumption into S2-2503272, architectural requirement part into S2-2502960.

Parallel discussion:

Merged.

Status: Merged.

S2-2503145 (P-CR) 23.700-14: Architectural Assumptions for Sensing. (Source: Ofinno)

Document for: Approval
Abstract:
This pCR aims to introduce a few key architectural assumptions and requirements, and to propose a key
issue (e.g., KI#1) for WT-1.
Comment: Merged into S2-2504263.

Convenor comment:

Merge architectural assumption into S2-2503272, architectural requirement part into S2-2502960, Key issue
part merge into S2-2503079.

Parallel discussion:

Merged.

Status: Merged.

3GPP
Report of meeting S2-168

S2-2503222 (P-CR) 23.700-14: Architectural Assumptions and Requirements for FS_Sensing. (Source:
Google)
Document for: Approval
Abstract:
The contribution proposes architectural assumptions and requirements.
Comment: Merged into S2-2504263.

Convenor comment:

Merge architectural assumption into S2-2503272, architectural requirement part into S2-2502960.

Parallel discussion:

Merged.

Status: Merged.

S2-2503236 (P-CR) 23.700-14: Architectural Assumptions and Principles for ISAC . (Source: InterDigital
Inc.)
Document for: Approval
Abstract:
The contribution proposes architectural assumptions and principles for Integrated Sensing and
Communication.
Comment: Merged into S2-2504263.

Convenor comment:

Merge architectural assumption into S2-2503272, architectural requirement part into S2-2502960.

Parallel discussion:

Merged.

Status: Merged.

S2-2503413 (DISCUSSION) Discussion on Architecture Assumption for ISAC study. (Source: China Mobile)
Document for: Discussion
Abstract:
This document discusses architecture assumptions for the ISAC study to support sensing service
management and sensing data management.
Convenor comment:

Not handle.

Plenary Discussion:

Not handled.

Status: Not treated.

3GPP
Report of meeting S2-168

S2-2503420 (P-CR) 23.700-14: Architectural assumptions and Architectural Requirements. (Source: China
Mobile)
Document for: Approval
Abstract:
This paper proposes the architectural assumptions and architectural requirements for FS_ ISAC TR 23.700-
14.
Comment: Merged into S2-2504263.

Convenor comment:

Merge architectural assumption into S2-2503272, architectural requirement part into S2-2502960.

Parallel discussion:

Merged.

Status: Merged.

S2-2503444 (P-CR) 23.700-14: ISAC Architectural Assumptions and Requirements. (Source: ZTE)
Document for: Approval
Abstract:
This paper proposes to add the Architectural Assumptions and Requirements to ISAC study.
Comment: Merged into S2-2504263.

Convenor comment:

Merge architectural assumption into S2-2503272, architectural requirement part into S2-2502960.

Parallel discussion:

Merged.

Status: Merged.

S2-2503770 (P-CR) 23.700-14: Architectural Assumptions of ISAC. (Source: Nokia, Nokia Shanghai Bell)
Document for: Approval
Abstract:
This paper proposes Architectural Assumptions for the Study on Architecture Enhancement to support
Integrated Sensing and Communication (FS_Sensing_ARC).
Comment: Merged into S2-2504263.

Convenor comment:

Merge architectural assumption into S2-2503272.

Parallel discussion:

Merged.

Status: Merged.

3GPP
Report of meeting S2-168

S2-2503799 (P-CR) 23.700-14: Architecture assumptions of Sensing study. (Source: Huawei, HiSilicon)
Document for: Approval
Abstract:
This document proposed the architecture for the study.
Comment: Merged into S2-2504263.

Convenor comment:

Merge architectural assumption into S2-2503272, architectural requirement part into S2-2502960.

Parallel discussion:

Merged.

Status: Merged.

S2-2503819 (P-CR) 23.700-14: TR 23.700-14: FS_Sensing-ARC architecture requirements and assumptions

. (Source: Qualcomm Incorporated)
Document for: Approval
Abstract:
This contribution proposed the architecture requirements and assumptions for TS 23.700-14 for study on
Integrated Sensing and Communication (ISAC).
Comment: Merged into S2-2504263.

Convenor comment:

Merge architectural assumption into S2-2503272, architectural requirement part into S2-2502960.

Parallel discussion:

Merged.

Status: Merged.

Key issues related WT#1

S2-2503079 (P-CR) 23.700-14: New Key Issue on Sensing Architecture . (Source: Apple)
Document for: Approval
Abstract:
This pCR proposes a Key Issue description for WT#1 on Sensing Architecture.
Convenor comment:

Handle - use as baseline.

Parallel discussion:

Revised in parallel session to S2-2504051.

Revised in parallel session to S2-2504264.

Remove the note 2 replace the entities by functions. Revised in parallel session to S2-2504325.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

3GPP
Report of meeting S2-168

S2-2503446 (P-CR) 23.700-14: Key issue#1, Architecture enhancement to support ISAC. (Source: ZTE)
Document for: Approval
Abstract:
This contribution proposes a new Key issue on Architecture enhancement to support ISAC.
Convenor comment:

Handle.

Parallel discussion:

Merged.

Status: Merged.

3GPP
Report of meeting S2-168

S2-2503369 (P-CR) 23.700-14: Key issue for WT-1: Architecture and function enhancements to support
sensing. (Source: Samsung)
Document for: Approval
Abstract:
The contribution proposes the key issue for Architecture and function enhancements to support sensing.
Comment: Merged into S2-2504264.

Convenor comment:

Merge into S2-2503079.

Parallel discussion:

Merged.

Status: Merged.

S2-2503421 (P-CR) 23.700-14: Key Issue 1: Architecture and function enhancements. (Source: China
Mobile)
Document for: Approval
Abstract:
This paper proposes the key issue about architecture and function enhancements for FS_ ISAC TR 23.700-
14.
Comment: Merged into S2-2504264.

Convenor comment:

Merge into S2-2503079.

Parallel discussion:

Merged.

Status: Merged.

S2-2503574 (P-CR) 23.700-14: New Key Issue on Supported Sensing Modes . (Source: Apple)
Document for: Approval
Abstract:
This pCR proposes a Key Issue description on Supported Sensing Modes.
Comment: Merged into S2-2504264.

Convenor comment:

Merge into S2-2503079.

Parallel discussion:

Merged.

Status: Merged.

3GPP
Report of meeting S2-168

S2-2503622 (P-CR) 23.700-14: TR 23.700-14: New key issue for WT-1 Architecture and function
enhancements. (Source: ETRI)
Document for: Approval
Abstract:
This contribution proposes a key issue for WT-1: Architecture and function enhancements.
Comment: Merged into S2-2504264.

Convenor comment:

Merge into S2-2503079.

Parallel discussion:

Merged.

Status: Merged.

S2-2503640 (P-CR) 23.700-14: 23.700-14: New KI for FS_Sensing_ARC WT#1. (Source: CATT)
Document for: Approval
Abstract:
This paper is to propose new key issue for FS_Sensing_ARC.
Comment: Merged into S2-2504264.

Convenor comment:

Merge into S2-2503079.

Parallel discussion:

Merged.

Status: Merged.

S2-2503772 (P-CR) 23.700-14: KI#1 Architecture and function enhancements to support sensing. (Source:
Nokia, Nokia Shanghai Bell)
Document for: Approval
Abstract:
This paper proposes Key Issue#1 for the Study on Architecture Enhancement to support Integrated Sensing
and Communication (FS_Sensing_ARC).
Comment: Merged into S2-2504264.

Convenor comment:

Merge into S2-2503079.

Parallel discussion:

Merged.

Status: Merged.

3GPP
Report of meeting S2-168

S2-2503866 (P-CR) 23.700-14: New KI#1 architecture and function enhancement to support ISAC service .
(Source: Xiaomi)
Document for: Approval
Abstract:
This paper proposes a new KI#1 architecture and function enhancement to support ISAC service.
Comment: Merged into S2-2504264.

Convenor comment:

Merge into S2-2503079.

Parallel discussion:

Merged.

Status: Merged.

Key issues related WT#2

S2-2503820 (P-CR) 23.700-14: TR 23.700-14: FS_Sensing-ARC new key issues. (Source: Qualcomm
Incorporated)
Document for: Approval
Abstract:
This contribution proposed the key issues for TS 23.700-14 for study on Integrated Sensing and
Communication (ISAC) based on the approved SID.
Convenor comment:

Handle - use as baseline?

Parallel discussion:

Revised in parallel session to S2-2504052.

Revised in parallel session to S2-2504265.

Add more source companies. Revised in parallel session to S2-2504326.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503370 (P-CR) 23.700-14: Key issue for WT-2: Service authorization and revocation. (Source:
Samsung)
Document for: Approval
Abstract:
The contribution proposes the key issue for Service authorization and revocation.
Convenor comment:

Handle.

Plenary Discussion:

Not handled.

Status: Not treated.

3GPP
Report of meeting S2-168

S2-2503062 (P-CR) 23.700-14: Key issue for WT#2 Service authorization and revocation. (Source: Vivo)
Document for: Approval
Abstract:
This paper is to add a key issue about the sensing service authorization and revocation.
Comment: Merged into S2-2504265.

Convenor comment:

Merge into S2-2503820.

Parallel discussion:

Merged.

Status: Merged.

S2-2503089 (P-CR) 23.700-14: Key issue for WT#2: Sensing service authurization and revocation. (Source:
OPPO)
Document for: Approval
Abstract:
The contribution proposes the key issue for WT#2 on how to support sensing service authurization and
revocation of the consumer.
Comment: Merged into S2-2504265.

Convenor comment:

Merge into S2-2503820.

Parallel discussion:

Merged.

Status: Merged.

S2-2503176 (P-CR) 23.700-14: 23.700-14: Key issue X: Sensing area authorization. (Source: OPPO)
Document for: Approval
Abstract:
The contribution proposes the key issue for WT#2 on Sensing area authorization.
Comment: Merged into S2-2504265.

Convenor comment:

Merge into S2-2503820.

Parallel discussion:

Merged.

Status: Merged.

3GPP
Report of meeting S2-168

S2-2503239 (P-CR) 23.700-14: New KI: KI for WT#2 and WT#5 Service exposure for ISAC . (Source:
InterDigital Inc.)
Document for: Approval
Abstract:
The contribution proposes the KI description corresponding to WT#2 and WT#5 in SP-250067.
Comment: Merged into S2-2504265.

Convenor comment:

Merge KI related WT#2 into S2-2503820 and KI related WT#5 into into S2-2503423.

Parallel discussion:

Merged.

Status: Merged.

S2-2503271 (DISCUSSION) Analysis of issues to be considered for end-to-end sensing service. (Source:
China Telecom)
Document for: Discussion
Abstract:
This paper presents an analysis of the issues that should be considered when designing end-to-end sensing
service architecture, also points out the common aspects that can be studied in Q2.
Convenor comment:

Not handle.

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503273 (P-CR) 23.700-14: TR 23.700-14: Key Issue on sensing configuration, authorization and
revocation. (Source: China Telecom)
Document for: Approval
Abstract:
This contribution proposes a new key issue on sensing configuration, authorization and revocation.
Comment: Merged into S2-2504265.

Convenor comment:

Merge authorization/revocation part into S2-2503820, and configuration part into S2-2503146.

Parallel discussion:

Merged.

Status: Merged.

S2-2503426 (P-CR) 23.700-14: Key Issue 2: Service authorization and revocation. (Source: China Mobile)
Document for: Approval
Abstract:
This paper proposes the key issue about service authorization and revocation for FS_ ISAC TR 23.700-14.
Comment: Merged into S2-2504265.

Convenor comment:

Merge into S2-2503820.

Parallel discussion:

Merged.

Status: Merged.

3GPP
Report of meeting S2-168

S2-2503447 (P-CR) 23.700-14: Key issue#2, Sensing Service authorization and parameter/policy
provisioning. (Source: ZTE)
Document for: Approval
Abstract:
This contribution proposes a new Key issue on ISAC Service authorization and policy/parameter
provisioning.
Comment: Merged into S2-2504265.

Convenor comment:

Merge into S2-2503820.

Parallel discussion:

Merged.

Status: Merged.

S2-2503542 (P-CR) 23.700-14: New KI: service authorization and revocation for sensing services . (Source:
Lenovo)
Document for: Approval
Abstract:
Proposes KI description for service authorization and revocation.
Comment: Merged into S2-2504265.

Convenor comment:

Merge into S2-2503820.

Parallel discussion:

Merged.

Status: Merged.

S2-2503623 (P-CR) 23.700-14: TR 23.700-14: New key issue for WT-2 Service authorization and revocation.
(Source: ETRI)
Document for: Approval
Abstract:
This contribution proposes a key issue for WT-2: Service authorization and revocation.
Comment: Merged into S2-2504265.

Convenor comment:

Merge into S2-2503820.

Parallel discussion:

Merged.

Status: Merged.

3GPP
Report of meeting S2-168

S2-2503773 (P-CR) 23.700-14: KI#2 Service authorization and revocation. (Source: Nokia, Nokia Shanghai
Bell)
Document for: Approval
Abstract:
This paper proposes Key Issue#2 for the Study on Architecture Enhancement to support Integrated Sensing
and Communication (FS_Sensing_ARC).
Comment: Merged into S2-2504265.

Convenor comment:

Merge into S2-2503820.

Parallel discussion:

Merged.

Status: Merged.

S2-2503815 (P-CR) 23.700-14: Key Issue for WT2, WT#3 & WT#4: QoS Mechanism. (Source: OPPO)
Document for: Approval
Abstract:
The contribution proposes the key issue for WT#2,3,4 on QoS mechanism for sensing services.
Comment: Merged into S2-2504265.

Convenor comment:

Merge WT#2 part into S2-2503820, WT#3 part into S2-2503063, WT#4 into S2-2502942.

Parallel discussion:

Merged.

Status: Merged.

S2-2503867 (P-CR) 23.700-14: New KI#2 ISAC Service authorization and revocation . (Source: Xiaomi)
Document for: Approval
Abstract:
This paper proposes a new KI#2: ISAC Service authorization and revocation.
Comment: Merged into S2-2504265.

Convenor comment:

Merge into S2-2503820.

Parallel discussion:

Merged.

Status: Merged.

3GPP
Report of meeting S2-168

Key issues related WT#3

S2-2503063 (P-CR) 23.700-14: Key issue for WT#3 Sensing entities discovery and selection. (Source: Vivo)
Document for: Approval
Abstract:
This paper is to add a key issue about the sensing entities discovery and selection in TR23.700-14 for
FS_Sensing_ARC.
Convenor comment:

Handle - use as baseline.

Parallel discussion:

Revised in parallel session to S2-2504053.

Revised in parallel session to S2-2504266.

Add more source companies. Revised in parallel session to S2-2504327.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503868 (P-CR) 23.700-14: New KI#3 Discovery and selection of sensing entities . (Source: Xiaomi)
Document for: Approval
Abstract:
This paper proposes new KI#3 Discovery and selection of sensing entities.
Convenor comment:

Handle.

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503143 (P-CR) 23.700-14: Key Issue for WT#3 Discovery and selection . (Source: Sony)
Document for: Approval
Abstract:
This contribution proposes a Key Issue according to the corresponding WT.
Comment: Merged into S2-2504266.

Convenor comment:

Merge into S2-2503063.

Parallel discussion:

Merged.

Status: Merged.

3GPP
Report of meeting S2-168

S2-2503174 (P-CR) 23.700-14: 23.700-14: Key issue X: Discovery and Selection of Sensing Function.
(Source: OPPO)
Document for: Approval
Abstract:
The contribution proposes the key issue for WT#3 on Discovery and Selection of Sensing Function.
Comment: Merged into S2-2504266.

Convenor comment:

Merge into S2-2503063.

Parallel discussion:

Merged.

Status: Merged.

S2-2503175 (P-CR) 23.700-14: 23.700-14: Key issue X: Discovery and selection of sensing transmitter and
receiver. (Source: OPPO)
Document for: Approval
Abstract:
The contribution proposes the key issue for WT#3 on Discovery and selection of sensing transmitter and
receiver.
Comment: Merged into S2-2504266.

Convenor comment:

Merge into S2-2503063.

Parallel discussion:

Merged.

Status: Merged.

S2-2503274 (P-CR) 23.700-14: TR 23.700-14: Key Issue on the discovery and selection of sensing entities.
(Source: China Telecom)
Document for: Approval
Abstract:
This contribution proposes a new key issue on the discovery and selection of sensing entities.
Comment: Merged into S2-2504266.

Convenor comment:

Merge into S2-2503063.

Parallel discussion:

Merged.

Status: Merged.

3GPP
Report of meeting S2-168

S2-2503371 (P-CR) 23.700-14: Key issue for WT-3: Discovery and selection of sensing entities . (Source:
Samsung)
Document for: Approval
Abstract:
The contribution proposes the key issue for Discovery and selection of sensing entities.
Comment: Merged into S2-2504266.

Convenor comment:

Merge into S2-2503063.

Parallel discussion:

Merged.

Status: Merged.

S2-2503427 (P-CR) 23.700-14: Key Issue 3: Discovery and selection of sensing entities. (Source: China
Mobile)
Document for: Approval
Abstract:
This paper proposes the key issue about discovery and selection of sensing entities for FS_ ISAC TR
23.700-14.
Comment: Merged into S2-2504266.

Convenor comment:

Merge into S2-2503063.

Parallel discussion:

Merged.

Status: Merged.

S2-2503448 (P-CR) 23.700-14: Key issue#3, Discovery and selection of sensing entities. (Source: ZTE)
Document for: Approval
Abstract:
This contribution proposes a new Key issue on Discovery and selection of sensing entities.
Comment: Merged into S2-2504266.

Convenor comment:

Merge into S2-2503063.

Parallel discussion:

Merged.

Status: Merged.

3GPP
Report of meeting S2-168

S2-2503624 (P-CR) 23.700-14: TR 23.700-14: New key issue for WT-3 Discovery and selection of sensing
entities. (Source: ETRI)
Document for: Approval
Abstract:
This contribution proposes a key issue for WT-3: Discovery and selection of sensing entities.
Comment: Merged into S2-2504266.

Convenor comment:

Merge into S2-2503063.

Parallel discussion:

Merged.

Status: Merged.

S2-2503774 (P-CR) 23.700-14: KI#3 Discovery and selection of sensing entities. (Source: Nokia, Nokia
Shanghai Bell)
Document for: Approval
Abstract:
This paper proposes Key Issue#3 for the Study on Architecture Enhancement to support Integrated Sensing
and Communication (FS_Sensing_ARC).
Comment: Merged into S2-2504266.

Convenor comment:

Merge into S2-2503063.

Parallel discussion:

Merged.

Status: Merged.

S2-2503814 (P-CR) 23.700-14: New KI: KI for WT#3 for discovery and selection of sensing entities .
(Source: InterDigital Inc.)
Document for: Approval
Abstract:
The contribution proposes the KI description corresponding to WT#3 in SP-250067.
Comment: Merged into S2-2504266.

Convenor comment:

Merge into S2-2503063.

Parallel discussion:

Merged.

Status: Merged.

3GPP
Report of meeting S2-168

Key issues related WT#4

S2-2502942 (P-CR) 23.700-14: 23.700-14: Key issue X: Sensing data and the associated information
collection and transport. (Source: OPPO)
Document for: Approval
Abstract:
The contribution proposes the key issue for WT#4 on Sensing data and the associated information collection
and transport.
Convenor comment:

Handle - use as baseline.

Parallel discussion:

Revised in parallel session to S2-2504054.

Revised in parallel session to S2-2504269.

Revised in parallel session to S2-2504328.

Plenary Discussion:

This was reviewed and approved.

Status: Approved.

S2-2503625 (P-CR) 23.700-14: TR 23.700-14: New key issue for WT-4 Sensing data collection and
transport. (Source: ETRI)
Document for: Approval
Abstract:
This contribution proposes a key issue for WT-4: Sensing data collection and transport.
Comment: Merged into S2-2504269.

Convenor comment:

Handle.

Parallel discussion:

Merged.

Status: Merged.

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503230 (P-CR) 23.700-14: WT-4: KI#X-UE data collection for sensing service. (Source: Google)
Document for: Approval
Abstract:
This contribution proposes the KI description for WT#4 on Sensing data and the associated information
collection and transport mechanisms for result calculation.
Comment: Merged into S2-2504269.

Convenor comment:

Merge into S2-2502942.

Parallel discussion:

Merged.

Status: Merged.

3GPP
Report of meeting S2-168

S2-2503372 (P-CR) 23.700-14: Key issue for WT-4: Sensing and associated data collection and derive
sensing result . (Source: Samsung)
Document for: Approval
Abstract:
The contribution proposes the key issue for collection of sensing data and associated information and derive
result.
Comment: Merged into S2-2504269.

Convenor comment:

Merge into S2-2502942.

Parallel discussion:

Merged.

Status: Merged.

S2-2503422 (P-CR) 23.700-14: Key Issue 4: Sensing data collection and transport. (Source: China Mobile)
Document for: Approval
Abstract:
This paper proposes the key issue about sensing data collection and transport for FS_ ISAC TR 23.700-14.
Comment: Merged into S2-2504269.

Convenor comment:

Merge into S2-2502942.

Parallel discussion:

Merged.

Status: Merged.

S2-2503449 (P-CR) 23.700-14: Key issue#4, Sensing data collection and transport. (Source: ZTE)
Document for: Approval
Abstract:
This contribution proposes a new Key issue on Sensing data collection and transport for result calculation.
Comment: Merged into S2-2504269.

Convenor comment:

Merge into S2-2502942.

Parallel discussion:

Merged.

Status: Merged.

3GPP
Report of meeting S2-168

S2-2503543 (P-CR) 23.700-14: New KI: sensing data and associated information collection and
transmission. (Source: Lenovo)
Document for: Approval
Abstract:
Proposes KI description for sensing data and associated information collection and transmission.
Comment: Merged into S2-2504269.

Convenor comment:

Merge into S2-2503063.

Parallel discussion:

Merged.

Status: Merged.

S2-2503641 (P-CR) 23.700-14: 23.700-14: New KI for FS_Sensing_ARC WT#4. (Source: CATT)
Document for: Approval
Abstract:
This paper is to propose new key issue for FS_Sensing_ARC.
Comment: Merged into S2-2504269.

Convenor comment:

Merge into S2-2502942.

Parallel discussion:

Merged.

Status: Merged.

S2-2503775 (P-CR) 23.700-14: KI#4 Sensing data and the associated information collection and transport.
(Source: Nokia, Nokia Shanghai Bell)
Document for: Approval
Abstract:
This paper proposes Key Issue#4 for the Study on Architecture Enhancement to support Integrated Sensing
and Communication (FS_Sensing_ARC).
Comment: Merged into S2-2504269.

Convenor comment:

Merge into S2-2502942.

Parallel discussion:

Merged.

Status: Merged.

3GPP
Report of meeting S2-168

S2-2503869 (P-CR) 23.700-14: New KI#4 Sensing data and associated data collection and result calculation
. (Source: Xiaomi)
Document for: Approval
Abstract:
This paper proposes a new KI#4 Sensing data and associated data collection and result calculation.
Comment: Merged into S2-2504269.

Convenor comment:

Merge into S2-2502942.

Parallel discussion:

Merged.

Status: Merged.

Key issues related WT#5

S2-2503423 (P-CR) 23.700-14: Key Issue 5: Sensing result exposure. (Source: China Mobile)
Document for: Approval
Abstract:
This paper proposes the key issue about sensing result exposure for FS_ ISAC TR 23.700-14.
Convenor comment:

Handle - use as baseline.

Parallel discussion:

Revised in parallel session to S2-2504055.

Revised in parallel session to S2-2504267.

Add more source companies Remove the note 1. Revised in parallel session to S2-2504329.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503642 (P-CR) 23.700-14: 23.700-14: New KI for FS_Sensing_ARC WT#5. (Source: CATT)
Document for: Approval
Abstract:
This paper is to propose new key issue for FS_Sensing_ARC.
Convenor comment:

Handle.

Plenary Discussion:

Not handled.

Status: Not treated.

3GPP
Report of meeting S2-168

S2-2502936 (P-CR) 23.700-14: Key issue for WT#5: Sensing Result Exposure. (Source: OPPO)
Document for: Approval
Abstract:
The contribution proposes the key issue for WT#5 on how to support sensing associated information and
result (including sensing result and contextual information) exposure.
Comment: Merged into S2-2504267.

Convenor comment:

Merge into S2-2503423.

Parallel discussion:

Merged.

Status: Merged.

S2-2503373 (P-CR) 23.700-14: Key issue for WT-5: Mechanisms for providing sensing information and
result . (Source: Samsung)
Document for: Approval
Abstract:
The contribution proposes the key issue for Mechanisms for providing sensing information and result.
Comment: Merged into S2-2504267.

Convenor comment:

Merge into S2-2503423.

Parallel discussion:

Merged.

Status: Merged.

S2-2503450 (P-CR) 23.700-14: Key issue#5, Sensing result exposure. (Source: ZTE)
Document for: Approval
Abstract:
This contribution proposes a new Key issue on Exposure Framework for sensing.
Comment: Merged into S2-2504267.

Convenor comment:

Merge into S2-2503423.

Parallel discussion:

Merged.

Status: Merged.

S2-2503544 (P-CR) 23.700-14: New KI: sensing result exposure. (Source: Lenovo)
Document for: Approval
Abstract:
Proposes KI description for sensing result exposure.
Comment: Merged into S2-2504267.

Convenor comment:

Merge into S2-2503423.

Parallel discussion:

Merged.

Status: Merged.

3GPP
Report of meeting S2-168

S2-2503626 (P-CR) 23.700-14: TR 23.700-14: New key issue for WT-5 Sensing result exposure. (Source:
ETRI)
Document for: Approval
Abstract:
This contribution proposes a key issue for WT-5: Sensing result exposure.
Comment: Merged into S2-2504267.

Convenor comment:

Merge into S2-2503423.

Parallel discussion:

Merged.

Status: Merged.

S2-2503776 (P-CR) 23.700-14: KI#5 sensing associated information and result exposure. (Source: Nokia,
Nokia Shanghai Bell)
Document for: Approval
Abstract:
This paper proposes Key Issue#5 for the Study on Architecture Enhancement to support Integrated Sensing
and Communication (FS_Sensing_ARC).
Comment: Merged into S2-2504267.

Convenor comment:

Merge into S2-2503423.

Parallel discussion:

Merged.

Status: Merged.

S2-2503870 (P-CR) 23.700-14: New KI#5 Sensing associated information and result exposure . (Source:
Xiaomi)
Document for: Approval
Abstract:
This paper proposes new KI#5 Sensing associated information and result exposure.
Comment: Merged into S2-2504267.

Convenor comment:

Merge into S2-2503423.

Parallel discussion:

Merged.

Status: Merged.

3GPP
Report of meeting S2-168

Key issues related WT#6

S2-2503146 (P-CR) 23.700-14: Key Issue for WT#6 Configuration parameter provisioning . (Source: Sony)
Document for: Approval
Abstract:
This contribution proposes a Key Issue according to the corresponding WT.
Convenor comment:

Handle - use as baseline.

Parallel discussion:

Revised in parallel session to S2-2504050.

Revised in parallel session to S2-2504268.

Add more source companies. Revised in parallel session to S2-2504330.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503090 (P-CR) 23.700-14: Key issue for WT#6: Configuration parameters/policy provisioning. (Source:
OPPO)
Document for: Approval
Abstract:
The contribution proposes the key issue for WT#6 on how to support (pre)configuration parameters/policy
provisioning to the transmitter/receiver.
Comment: Merged into S2-2504268.

Convenor comment:

Merge into S2-2503146.

Parallel discussion:

Merged.

Status: Merged.

S2-2503376 (P-CR) 23.700-14: Key issue for WT-6: Configuration parameters/policy provisioning for the
support of ISAC services. (Source: Samsung)
Document for: Approval
Abstract:
The contribution proposes the key issue for Configuration parameters/policy provisioning for the support of
ISAC services.
Comment: Merged into S2-2504268.

Convenor comment:

Merge into S2-2503146.

Parallel discussion:

Merged.

Status: Merged.

3GPP
Report of meeting S2-168

S2-2503425 (P-CR) 23.700-14: Key Issue 6: Configuration parameters and policy provisioning. (Source:
China Mobile)
Document for: Approval
Abstract:
This paper proposes the key issue about configuration parameters and policy provisioning for FS_ ISAC TR
23.700-14.
Comment: Merged into S2-2504268.

Convenor comment:

Merge into S2-2503146.

Parallel discussion:

Merged.

Status: Merged.

S2-2503777 (P-CR) 23.700-14: KI#6 Configuration parameters policy provisioning. (Source: Nokia, Nokia
Shanghai Bell)
Document for: Approval
Abstract:
This paper proposes Key Issue#6 for the Study on Architecture Enhancement to support Integrated Sensing
and Communication (FS_Sensing_ARC).
Comment: Merged into S2-2504268.

Convenor comment:

Merge into S2-2503146.

Parallel discussion:

Merged.

Status: Merged.

Solutions

S2-2503065 (P-CR) 23.700-14: New solution: Enable the 5GS to support sensing services. (Source: Vivo)
Document for: Approval
Abstract:
This paper is trying to provide a common solution to support the sensing services.
Convenor comment:

Not handle.

Plenary Discussion:

Not handled.

Status: Not treated.

3GPP
Report of meeting S2-168

S2-2503800 (P-CR) 23.700-14: Call flow of the sensing study. (Source: Huawei, HiSilicon)
Document for: Approval
Abstract:
Providing on the general call flow of the sensing study for FS_Sensing_ARC is proposed.
Convenor comment:

Not handle.

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503801 (P-CR) 23.700-14: KI#2, New Sol: Service authorisation and revocation. (Source: Huawei,
HiSilicon)
Document for: Approval
Abstract:
The service authorization and revocation for FS_Sensing_ARC are proposed.
Convenor comment:

Not handle.

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503802 (P-CR) 23.700-14: KI#3, New Sol: Discovery and selection of sensing entities. (Source: Huawei,
HiSilicon)
Document for: Approval
Abstract:
The Discovery and selection of sensing entities for FS_Sensing_ARC are proposed.
Convenor comment:

Not handle.

Plenary Discussion:

S2-2503026 (P-CR) 23.700-04: TR Skeleton for FS_AIML_CN_Ph2 (Source: Samsung, vivo)

Document for: Approval
Abstract:
3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on
Core Network Enhanced Support for Artificial Intelligence (AI)/Machine Learning (ML)_Ph2 (Release 20).
Comment: Skeleton TR.

Convenor comment:

Revised.

3GPP
Report of meeting S2-168

S2-2503789: Handle. Revision of S2-2503026. Skeleton TR.

Revised in parallel session to S2-2503953.

Revised in parallel session to S2-2504192.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503027 (P-CR) 23.700-04: Scope for FS_AIML_CN_Ph2. (Source: Samsung (rapporteur), vivo
(rapporteur))
Document for: Approval
Abstract:
The contribution proposes the scope of FS_AIML_CN_Ph2.
Convenor comment:

Handle. See inbox for draft.

Parallel discussion:

Revised in parallel session to S2-2503952.

Revised in parallel session to S2-2504193.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

Architectural Assumptions and Requirements

S2-2503291 (P-CR) 23.700-04: Architectural Assumptions and Requirements for FS_AIML_CN_Ph2.

(Source: Vivo(rapporteur), Samsung(rapporteur))
Document for: Approval
Abstract:
This paper proposes architectural assumptions and requirements for FS_AIML_CN_Ph2.
Convenor comment:

Baseline. See inbox for draft.

Parallel discussion:

Revised in parallel session to S2-2503954.

Include two notes from S2-2503955 under arch. Assumptions. Put 'Option 2' between brackets. Add '- The
existing UPF event exposure should be reused as much as possible.'. Revised in parallel session to S2-
2504195.

This was agreed in parallel session.

S2-2503400 (P-CR) 23.700-04: Architecture Assumption of TR 23.700-04. (Source: China Mobile)

Document for: Approval
Abstract:
This contribution proposes the architecture assumption of the TR 23.700-04 for FS_AIML_CN_Ph2.
Convenor comment:

Merged into baseline.

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503478 (P-CR) 23.700-04: Architectural Assumptions and Requirements for WT#1. (Source: ETRI)
Document for: Approval
Abstract:
The contribution proposes architectural assumptions and requirements for WT#1 of FS_AIML_CN_Ph2.
Convenor comment:

Merged into baseline.

Plenary Discussion:

WT#1 Key Issues

S2-2503290 (P-CR) 23.700-04: New Key Issue for transfer of data over UP for UE data collection. (Source:
Vivo(rapporteur), Samsung(rapporteur))
Document for: Approval
Abstract:
This paper proposed to include a new key issue for transfer of data over UP for UE data collection.
Convenor comment:

Baseline. See rev in inbox.

Parallel discussion:

Revised in parallel session to S2-2503955.

Two notes to be moved to arch. Assumption. Revised in parallel session to S2-2504194.

Revised in parallel session to S2-2504235.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2502949 (P-CR) 23.700-04: New KI: 5GC Support for UE Data Collection over the User Plane . (Source:
Apple)
Document for: Approval
Abstract:
This pCR proposes a Key Issue description for WT#1 on 5GC Support for UE Data Collection over the User
Plane.
Convenor comment:

Merged into baseline.

Plenary Discussion:

Not handled.

Status: Not treated.

3GPP
Report of meeting S2-168

S2-2502940 (P-CR) 23.700-04: Key issue for WT#1: Standardized UE data collection based on UP
connection between UE and 5GC. (Source: OPPO)
Document for: Approval
Abstract:
The contribution proposes the key issue for WT#1 on how to transfer of standardized data over user plane
between the UE and 5GC to support the standardized UE data collection.
Convenor comment:

Merged into baseline.

Plenary Discussion:

Plenary Discussion:

Not handled.

Status: Not treated.

3GPP
Report of meeting S2-168

3GPP
Report of meeting S2-168

3GPP
Report of meeting S2-168

S2-2503396 (P-CR) 23.700-04: FS_AIML_CN_Ph2 New Key Issue for Work Task #1. (Source: China
Mobile)
Document for: Approval
Abstract:
This paper proposes a new Key Issue to cover work task #1 of the FS_AIML_CN_Ph2 SID.
Convenor comment:

Merged into baseline.

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503479 (P-CR) 23.700-04: Key issue for WT#1. (Source: ETRI)

Document for: Approval
Abstract:
The contribution proposes a Key Issue description for WT#1 of FS_AIML_CN_Ph2.
Convenor comment:

Merged into baseline.

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503600 (P-CR) 23.700-04: Key issue for WT#1 UE data transfer via UP for UE-side model training for
AIML NR air interface operation. (Source: Xiaomi)
Document for: Approval
Abstract:
This contribution proposes the KI description for WT#1.
Convenor comment:

Merged into baseline.

Plenary Discussion:

Not handled.

Status: Not treated.

WT#1 Use Cases

S2-2503562 (P-CR) 23.700-04: Use case for WT#1 UE data collection. (Source: CATT)
Document for: Approval
Abstract:
The contribution proposes the description of use case for WT#1 UE data collection for AI/ML for NR air
interface operation with UE-side model training.
Plenary Discussion:

Not handled.

Status: Not treated.

3GPP
Report of meeting S2-168

WT#1 Solutions (Handle following order below. One paper per company. Merged paper(s) get priority)

S2-2503292 (P-CR) 23.700-04: KI#1: New Solution UE data collection via DCCF in CN over UP. (Source:
Vivo)
Document for: Approval
Abstract:
This contribution proposes a solution for KI#1 to support UE data collection via CN over UP.
Parallel discussion:

See rev in inbox. Merges S2-2503728. Revised in parallel session to S2-2503956.

Add high level principles clause. Move definition and EN of UP info to introduction. Remove last EN in
procedure. It is understood that solutions can impact CP signalling in CN. Revised in parallel session to S2-
2504238.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503016 (P-CR) 23.700-04: UP building for UE training data collection. (Source: ZTE)
Document for: Approval
Abstract:
This contribution proposes a way for UP building between NWDAF and UE.
Parallel discussion:

Revised in parallel session to S2-2503957.

Revised in parallel session to S2-2504234.

Revised in parallel session to S2-2504240.

Revised in parallel session to S2-2504422.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503023 (P-CR) 23.700-04: KI#1, New Sol#X: Generalized UE data collection over user plane . (Source:
LG Electronics)
Document for: Approval
Abstract:
This paper proposes to add a new solution for AIML UE data collection over UP in TR 23.700-04.
Parallel discussion:

Revised in parallel session to S2-2503958.

Revised in parallel session to S2-2504241.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

3GPP
Report of meeting S2-168

S2-2503068 (P-CR) 23.700-04: Solution for WT 1 General Framework for data collection from the UE.
(Source: Lenovo)
Document for: Approval
Abstract:
.
Parallel discussion:

Revised in parallel session to S2-2503959.

Revised in parallel session to S2-2504242.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503132 (P-CR) 23.700-04: KI#1: New Sol: CP-instructed UP-based UE data collection. (Source: NTT
DOCOMO)
Document for: Approval
Abstract:
This contribution proposes a solution for KI#1 to collect data from UE via UP where the data collection
instructions are communicated via CP.
Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503139 (P-CR) 23.700-04: New solution to support UE data collection and transfer for AI based
positioning . (Source: Huawei, HiSilicon)
Document for: Approval
Abstract:
A new solution is proposed to support UE data collection and transfer for AI based positioning.
Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503140 (P-CR) 23.700-04: New Solution for UE Data Collection and Transfer over User Plane. (Source:
Huawei, HiSilicon)
Document for: Approval
Abstract:
For training data collection from the UE to the OTT server for UE-side model training, a new solution is
proposed to enable the 5G Core to support UE data collection over User Plane.
Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503189 (P-CR) 23.700-04: KI#1 solution using the generic architecture for collecting and exposing the
collected UE data. (Source: Ericsson)
Document for: Approval
Abstract:
This contribution proposes a solution for KI#1 for FS_AIML_CN_Ph2.
Plenary Discussion:

Not handled.

Status: Not treated.

3GPP
Report of meeting S2-168

S2-2502923 (DISCUSSION) DP for R20 AIML WT#2 UC (Source: SK Telecom)

Document for: Discussion
Abstract:
DP for R20 AIML WT#2 UC.
Plenary Discussion:

Not handled.

Status: Not treated.

S2-2502992 (P-CR) 23.700-04: WT#2 use case AI/ML-assisted UPF traffic pattern and behaviour analytics
to support efficient performance of User Plane. (Source: SK Telecom, China Mobile, China Telecom,
Deutsche Telekom, KPN N.V., LG Uplus, Verizon)
Document for: Approval
Abstract:
This paper proposes a use case to cover Work Task#2 of the FS_AIML_CN_Ph2 SID.
Convenor comment:

Handle - baseline. See rev in inbox.

Parallel discussion:

Revised in parallel session to S2-2503960.

Revised in parallel session to S2-2504196.

Parallel discussion:

Revised in parallel session to S2-2503961.

Revised in parallel session to S2-2504237.

Revised in parallel session to S2-2504239.

Append 'by the NWDAF' in note 3. Revised in parallel session to S2-2504421.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2504222 (LS OUT) [DRAFT] LS on use case for NWDAF based UP performance optimization (Source:
Huawei)
Document for: Approval
Abstract:
-
Comment: Created at meeting. Withdrawn.

Withdrawn.

Status: Withdrawn.

3GPP
Report of meeting S2-168

S2-2503280 (P-CR) 23.700-04: FS_AIML_CN_Ph2 Use case for WT#2. (Source: ZTE)
Document for: Approval
Abstract:
This paper proposes a new use case to cover Work Task#2 of the FS_AIML_CN_Ph2 SID.
Convenor comment:

Merge into S2-2502992.

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503795 (P-CR) 23.700-04: WT#2 use case: Prevention of unexpected service experience degradation.
(Source: Samsung)
Document for: Approval
Abstract:
This paper proposes a use case to cover Work Task#2 of the FS_AIML_CN_Ph2 SID.
Convenor comment:

Merge into S2-2502992.

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503796 (P-CR) 23.700-04: WT#2 use case: Enhancement of analytics for user plane traffic pattern and
characteristic. (Source: Samsung)
Document for: Approval
Abstract:
This paper proposes a use case to cover Work Task#2 of the FS_AIML_CN_Ph2 SID.
Comment: Merged into S2-2503960.

Parallel discussion:

Merged.

Status: Merged.

3GPP
Report of meeting S2-168

WT#2 Key Issues (If use case discussion converges, then open one KI paper as baseline)

S2-2502994 (P-CR) 23.700-04: WT#2 Key Issue AI/ML-assisted UPF traffic pattern and behaviour analytics
to support efficient performance of User Plane. (Source: SK Telecom, China Mobile, China Telecom,
Deutsche Telekom, KPN N.V., LG Uplus, Verizon)
Document for: Approval
Abstract:
This paper proposes a new key case to cover Work Task#2 of the FS_AIML_CN_Ph2 SID.
Convenor comment:

Handle - baseline. See rev in inbox.

S2-2503192 (P-CR) 23.700-04: KI#2 description. (Source: Ericsson)

Document for: Approval
Abstract:
This contribution proposes a description of KI#2 for FS_AIML_CN.
Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503281 (P-CR) 23.700-04: FS_AIML_CN_Ph2 Key issue for WT#2. (Source: ZTE)
Document for: Approval
Abstract:
This paper proposes a new key issue to cover Work Task#2 of the FS_AIML_CN_Ph2 SID.
Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503285 (P-CR) 23.700-04: Key issue for WT#2 Network analytics enhancement for user plane
performance improvement. (Source: CATT)
Document for: Approval
Abstract:
This contribution proposes the KI description for WT#2 on network analytics enhancement for user plane
performance improvement.
Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503398 (P-CR) 23.700-04: FS_AIML_CN_Ph2 New Key Issue for Work Task #2. (Source: China
Mobile, SK Telecom)
Document for: Approval
Abstract:
This paper proposes a new Key Issue to cover work task #2 of the FS_AIML_CN_Ph2 SID.
Convenor comment:

Merge into S2-2502992.

Plenary Discussion:

Not handled.

Status: Not treated.

20.4.1 Study on Energy Efficiency and Energy Saving Phase2

(FS_EnergySys_Ph2)
This agenda item was convened by Wanqiang Zhang (Huawei).

3GPP
Report of meeting S2-168

TR Skeleton and TR Scope

S2-2503120 (P-CR) 23.700-67: TR 23.700-67 Skeleton for FS_EnergySys_Ph2 (Source: China Telecom,
Lenovo (Rapporteur))
Document for: Approval
Abstract:
TR 23.700-67 Skeleton for FS_EnergySys_Ph2.
Comment: Skeleton TR.

Convenor comment:

Handle.

Parallel discussion:

Revised in parallel session to S2-2504068.

Revised in parallel session to S2-2504316.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503123 (P-CR) 23.700-67: FS_EnergySys_Ph2 TR23.700-67 Scope. (Source: China Telecom, Lenovo
(Rapporteur))
Document for: Approval
Abstract:
Scope description for TR23.700-67.
Comment: Agreed in parallel session.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

Architectural Assumptions and Requirement

S2-2502956 (P-CR) 23.700-67: Architecture assumptions. (Source: Vivo)

Document for: Approval
Abstract:
Propose the architecture assumptions for TR 23.700-67.
Comment: Merged into S2-2504069.

Convenor comment:

Merge into S2-2503485?

Parallel discussion:

Merged.

Status: Merged.

3GPP
Report of meeting S2-168

S2-2503451 (P-CR) 23.700-67: Proposal on the architecture assumptions and requirement. (Source: ZTE)
Document for: Approval
Abstract:
This paper proposes to add the architecture assumptions and requirement for this study.
Comment: Merged into S2-2504069.

Convenor comment:

Merge into S2-2503485?

Parallel discussion:

Merged.

Status: Merged.

S2-2503485 (P-CR) 23.700-67: Architectural Assumptions and Principles for Energy Efficiency and Energy
Saving. (Source: China Mobile, Lenovo, China Telecom)
Document for: Approval
Abstract:
The contribution proposes architectural assumptions and principles for Energy Efficiency and Energy Saving
Phase 2.
Convenor comment:

Handle, as baseline.

Parallel discussion:

Revised in parallel session to S2-2504069.

Add the section 4.1 4.1 Architectural Assumptions Fix the typo. Revised in parallel session to S2-2504308.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503566 (P-CR) 23.700-67: Architectural Assumptions and Requirements for FS_EnergySys_Ph2.

(Source: CATT)
Document for: Approval
Abstract:
The contribution proposes architectural assumptions and requirements for the study of Energy Efficiency and
Energy Saving Phase 2.
Comment: Merged into S2-2504069.

Convenor comment:

Merge into S2-2503485?

Parallel discussion:

Merged.

Parallel discussion:

Merged.

Status: Merged.

3GPP
Report of meeting S2-168

S2-2503383 (P-CR) 23.700-67: Key Issue for WT#1: Enhancements in collection, determination and
exposure of energy related information. (Source: NEC)
Document for: Approval
Abstract:
This contribution proposes a key issue for WT#1.
Comment: Merged into S2-2504070.

Convenor comment:

Merge into S2-2503567?

Parallel discussion:

Merged.

Status: Merged.

S2-2503452 (P-CR) 23.700-67: Adding new KI on the collection, determination and exposure of energy
related information. (Source: ZTE)
Document for: Approval
Abstract:
This paper proposes to add a new Key issue for the collection, determination and exposure of energy related
information.
Comment: Merged into S2-2504070.

Convenor comment:

Merge into S2-2503567?

Parallel discussion:

Merged.

Status: Merged.

S2-2503482 (P-CR) 23.700-67: New Key Issue: Enhancement for energy related information collection,
determination, and exposure. (Source: China Mobile)
Document for: Approval
Abstract:
Propose a key issue about WT#1: Enhancement for energy related information collection, determination, and
exposure.
Comment: Merged into S2-2504070.

Convenor comment:

Merge into S2-2503567?

Parallel discussion:

Merged.

Status: Merged.

3GPP
Report of meeting S2-168

S2-2503567 (P-CR) 23.700-67: Key issue for WT#1 - Enhancements on energy related information collection
and exposure. (Source: CATT)
Document for: Approval
Abstract:
The contribution proposes the key issue description for WT#1 Whether and how to enhance the collection,
determination and exposure of energy related information in the 5GS .
Comment: Merged into S2-2504070.

Convenor comment:

Handle, as baseline.

Parallel discussion:

Merged.

Status: Merged.

S2-2503603 (P-CR) 23.700-67: New Key issue for WT#1 On Enhancements of Energy-related information
exposure. (Source: Nokia)
Document for: Approval
Abstract:
The contribution proposes the key issue description for WT#1.
Convenor comment:

Merge into S2-2503567?

Parallel discussion:

Revised in parallel session to S2-2504070.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503717 (P-CR) 23.700-67: New KI: Enhancing collection, determination and exposure of energy related
information. (Source: NTT DOCOMO)
Document for: Approval
Abstract:
The contribution proposes the key issue description for WT#1 in the SID SP-250417.
Comment: Merged into S2-2504070.

Convenor comment:

Merge into S2-2503567?

Parallel discussion:

Merged.

Status: Merged.

3GPP
Report of meeting S2-168

S2-2503879 (P-CR) 23.700-67: KI#1 - Enhancements on energy related information collection, determination
and exposure. (Source: Lenovo)
Document for: Approval
Abstract:
The contribution proposes the key issue 1 description.
Comment: Merged into S2-2504070.

Convenor comment:

Merge into S2-2503567?

Parallel discussion:

Merged.

Status: Merged.

KI Description for WT#2 (service adjustments for the UE)

S2-2502958 (P-CR) 23.700-67: New key issue for WT#2: Service adjustments for network energy saving.
(Source: Vivo)
Document for: Approval
Abstract:
Propose the new key issue for WT#2.
Comment: Merged into S2-2504071.

Convenor comment:

Merge into S2-2503287?

Parallel discussion:

Merged.

Status: Merged.

S2-2503159 (P-CR) 23.700-67: Key issue for WT#2: Support of service adjustments for the UE. (Source:
Samsung)
Document for: Approval
Abstract:
The contribution proposes the key issue for WT#2 on Support of service adjustments for the UE.
Comment: Merged into S2-2504071.

Convenor comment:

Merge into S2-2503287?

Parallel discussion:

Merged.

Status: Merged.

3GPP
Report of meeting S2-168

S2-2503287 (P-CR) 23.700-67: Key issue for WT#2: Support of service adjustments for the UE. (Source:
MediaTek Inc.)
Document for: Approval
Abstract:
The contribution proposes the key issue for WT#2 on Support of service adjustments for the UE.
Convenor comment:

Status: Merged.

3GPP
Report of meeting S2-168

S2-2503568 (P-CR) 23.700-67: Key issue for WT#2 - Service adjustments for the UE to enable energy
saving. (Source: CATT)
Document for: Approval
Abstract:
The contribution proposes the key issue description for WT#2 Whether and how to support service
adjustments for the UE to enable energy saving .
Comment: Merged into S2-2504071.

Convenor comment:

Merge into S2-2503287?

Parallel discussion:

Merged.

Status: Merged.

S2-2503608 (P-CR) 23.700-67: New Key issue for WT#2 - Service adjustments for the UE to enable energy
saving. (Source: Nokia)
Document for: Approval
Abstract:
The contribution proposes the key issue description for WT#2.
Comment: Merged into S2-2504071.

Convenor comment:

Merge into S2-2503287?

Parallel discussion:

Merged.

Status: Merged.

S2-2503727 (P-CR) 23.700-67: New KI: Service adjustment for energy saving. (Source: NTT DOCOMO)
Document for: Approval
Abstract:
The contribution proposes the key issue description for WT#2 in the SID SP-250417.
Comment: Merged into S2-2504071.

Convenor comment:

Merge into S2-2503287?

Parallel discussion:

Merged.

Parallel discussion:

Merged.

Status: Merged.

3GPP
Report of meeting S2-168

S2-2503454 (P-CR) 23.700-67: Adding new KI on support of NF (re)selection and/or UP path adjustment
based on energy related information. (Source: ZTE)
Document for: Approval
Abstract:
This paper proposes to add a new Key issue for support of NF (re)selection and/or UP path adjustment
based on energy related information.
Comment: Merged into S2-2504072.

Convenor comment:

Merge into S2-2503484?

Parallel discussion:

Merged.

Status: Merged.

S2-2503484 (P-CR) 23.700-67: New Key Issue: NF (re)selection and/or UP path adjustment based on
energy related information. (Source: China Mobile, Lenovo, China Telecom)
Document for: Approval
Abstract:
Propose a key issue about WT#3: Whether and how to support NF (re)selection and/or UP path adjustment
based on energy related information.
Convenor comment:

Handle, as baseline.

Parallel discussion:

Remove: 'In Rel-19, the NF (re)selection and/or UP path adjustment based on energy related information,
has been discussed but not concluded. However, this aspect is quite important since the selection of a lower
energy consumption UP or CP NFs, contribut.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503569 (P-CR) 23.700-67: Key issue for WT#3 - NF (re)selection and UP path adjustment for energy
saving. (Source: CATT)
Document for: Approval
Abstract:
The contribution proposes the key issue description for WT#3 Whether and how to support NF (re)selection
and/or UP path adjustment based on energy related information .
Comment: Merged into S2-2504072.

Convenor comment:

Merge into S2-2503484?

Parallel discussion:

Merged.

Status: Merged.

3GPP
Report of meeting S2-168

S2-2503610 (P-CR) 23.700-67: New Key issue for WT#3 - On the support NF (re-)selection and/or UP path
adjustment based on energy related information . (Source: Nokia)
Document for: Approval
Abstract:
The contribution proposes the key issue description for WT#3.
Comment: Merged into S2-2504072.

Convenor comment:

Merge into S2-2503484?

Parallel discussion:

Merged.

Status: Merged.

S2-2503730 (P-CR) 23.700-67: New KI: Enhancing 5GC energy efficiency . (Source: NTT DOCOMO)
Document for: Approval
Abstract:
The contribution proposes the key issue description for WT#3 in the SID SP-250417.
Comment: Merged into S2-2504072.

Convenor comment:

Merge into S2-2503484?

Parallel discussion:

Merged.

Status: Merged.

Solutions for WT#1 (enhance the collection, determination and exposure)

S2-2503612 (P-CR) 23.700-67: KI#1:new solution: P-CR on exposure of UE scoring data. (Source: Nokia)
Document for: Approval
Abstract:
-
Convenor comment:

Handle.

Parallel discussion:

Revised in parallel session to S2-2504073.

Revised in parallel session to S2-2504309.

Revised in parallel session to S2-2504342.

Plenary Discussion:

This was reviewed and approved.

Status: Approved.

3GPP
Report of meeting S2-168

S2-2503634 (P-CR) 23.700-67: WT#1: EC improvement for Passive and dynamic EC. (Source: Huawei,
HiSilicon)
Document for: Approval
Abstract:
A solution, which defines a methodology to improve the evaluation of Energy Consumption taking into
account the passive and dynamic part of energy consumption, is proposed. A second solution proposes to
define a method to consider the contribution of Control Plane and other contribution to the energy
consumption.
Convenor comment:

Handle 2nd round if time permits.

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503635 (P-CR) 23.700-67: WT#1: Renewable energy per UE, PDU session and SDF. (Source: Huawei,
HiSilicon)
Document for: Approval
Abstract:
A summary of what this is about. Don t start it with This contribution.
Convenor comment:

Handle 2nd round if time permits.

Plenary Discussion:

Not handled.

Status: Not treated.

Solutions for WT#2 (service adjustments for the UE)

S2-2502952 (P-CR) 23.700-67: Energy Optimization Trigger for PCF based Policy Control. (Source:
Ericsson)
Document for: Approval
Abstract:
Slice or 5GC level EnC triggers for PCF policy control.
Convenor comment:

Handle.

Parallel discussion:

Revised in parallel session to S2-2504074.

Revised in parallel session to S2-2504310.

Revised in parallel session to S2-2504343.

Plenary Discussion:

Ericsson suggested that the outstanding issue with this can be resolved by adding an note above 6.X.3. This
was revised to S2-2504479.

This was approved.

Status: Approved.

3GPP
Report of meeting S2-168

S2-2503144 (P-CR) 23.700-67: KI#2: New Sol: Energy-aware data transfer policy negotiation. (Source: NTT
DOCOMO)
Document for: Approval
Abstract:
This contribution proposes a solution for KI#2 where AF can negotiate for an energy-aware data transfer
policy.
Convenor comment:

Handle.

Parallel discussion:

Revised in parallel session to S2-2504075.

Add the note: Note: The energy-related information at UE or NF level used in KI#2 and KI#3 should be based
on robust and accurate enough estimates to be fit for purpose. Revised in parallel session to S2-2504311.

Revised in parallel session to S2-2504346.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503288 (P-CR) 23.700-67: Solution for WT#2: Support of QoS adjustments. (Source: MediaTek Inc.)
Document for: Approval
Abstract:
The contribution proposes solution to the key issue for WT#2 on Support of service adjustments for the UE.
Convenor comment:

Handle.

Parallel discussion:

Revised in parallel session to S2-2504077.

Revised in parallel session to S2-2504312.

Revised in parallel session to S2-2504344.

Plenary Discussion:

This was reviewed and approved.

Status: Approved.

S2-2503294 (P-CR) 23.700-67: Solution for WT#2: Support of policy adjustments. (Source: MediaTek Inc.)
Document for: Approval
Abstract:
The contribution proposes solution to the key issue for WT#2 on Support of policy adjustments.
Plenary Discussion:

Not handled.

Status: Not treated.

3GPP
Report of meeting S2-168

S2-2503392 (P-CR) 23.700-67: KI#2, new sol: Service adjustments for network energy saving based on AF
request and energy information. (Source: Vivo)
Document for: Approval
Abstract:
Propose the new solution for KI#2 for TR 23.700-67.
Convenor comment:

Handle.

Parallel discussion:

Revised in parallel session to S2-2504078.

Revised in parallel session to S2-2504313.

Add the note: Note: The energy-related information at UE or NF level used in KI#2 and KI#3 should be
based on robust and accurate enough estimates to be fit for purpose. Change the note 3: is reused. Revised
in parallel session to S2-2504345.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503570 (P-CR) 23.700-67: KI#2 new solution for policy control based on interactions with the EIF.
(Source: CATT)
Document for: Approval
Abstract:
The contribution proposes a new solution for policy control based on interactions with the EIF for KI#2.
Convenor comment:

Handle.

Parallel discussion:

Revised in parallel session to S2-2504079.

Revised in parallel session to S2-2504314.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

3GPP
Report of meeting S2-168

S2-2503713 (P-CR) 23.700-67: New Solution to WT#2: Enabling dynamic QoS handling for energy efficiency
lterby use of Energy Saving QoS Profiles . (Source: Qualcomm Incorporated)
Document for: Approval
Abstract:
This contribution proposes to enable dynamic QoS handling based on whether energy efficiency
mechanisms are being used, by defining an Energy Efficiency QoS profile.
Convenor comment:

Handle.

Parallel discussion:

Revised in parallel session to S2-2504076.

Revised in parallel session to S2-2504315.

This was agreed in parallel session.

Plenary Discussion:

This was block approved.

Status: Approved.

S2-2503788 (P-CR) 23.700-67: KI#2: New Solution on SM policy control based on EIF notification. (Source:
Samsung)
Document for: Approval
Abstract:
The contribution proposes a new solution on SM policy control that the PCF may utilize the notification
including Energy Consumption information from the EIF and update the SM policy for a UE/PDU
Session/QoS flow based on the received information.
Convenor comment:

S2-2503419 (P-CR) 23.700-67: KI #3, New Sol: AMF (re-)selection based on energy related information.
(Source: Vivo)
Document for: Approval
Abstract:
This contribution is trying to provide a sol for KI#X on the AMF selection aspect.
Plenary Discussion:

Not handled.

Status: Not treated.

3GPP
Report of meeting S2-168

S2-2503571 (P-CR) 23.700-67: KI#3 new solution for UP path adjustment based on energy related
information. (Source: CATT)
Document for: Approval
Abstract:
The contribution proposes a new solution for UP path adjustment based on energy related information for
KI#3.
Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503636 (P-CR) 23.700-67: WT#3: NF selection profile and UPF selection. (Source: Huawei, HiSilicon)
Document for: Approval
Abstract:
This document proposed the NF selection as the solution of the KI#3.
Convenor comment:

Handle.

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503856 (P-CR) 23.700-67: KI#3: New solution on NF selection mechanism based on energy related
information. (Source: Samsung)
Document for: Approval
Abstract:
The contribution proposes a new solution on NF selection based on energy related information.
Convenor comment:

Handle 2nd round if time permits.

Plenary Discussion:

Not handled.

Status: Not treated.

30 Project Planning and Management

30.1 New and Revised Study/Work Items
There were no contributions to this agenda item.

30.2 Submissions for TEI20

This topic was not on the agenda for this meeting.

30.3 TR and TS Cover sheets

There were no contributions to this agenda item.

3GPP
Report of meeting S2-168

30.4 SI/WI Status Reports

The status report document numbers were allocated at the close of the meeting for upload to the INBOX
after the meeting.

S2-2504423 (WI STATUS REPORT) WI Status Report for Integration of satellite components in the 5G
architecture Phase 3 (5GSAT_Ph3-ARC) (Source: Rapporteur (CATT))
Document for: Information
Abstract:
WI Status Report for Integration of satellite components in the 5G architecture Phase 3 (5GSAT_Ph3-ARC).
Comment: To be provided after the meeting.

Plenary Discussion:

Noted.

Status: Noted.

S2-2504424 (WI STATUS REPORT) WI Status Report for System architecture for next generation real time
communication services phase 2 (NG_RTC_Ph2) (Source: Rapporteur (ZTE))
Document for: Information
Abstract:
WI Status Report for System architecture for next generation real time communication services phase 2
(NG_RTC_Ph2).
Comment: To be provided after the meeting.

Plenary Discussion:

Noted.

Status: Noted.

S2-2504425 (WI STATUS REPORT) WI Status Report for Extended Reality and Media service (XRM) Phase
2 (XRM_Ph2) (Source: Rapporteur (Nokia))
Document for: Information
Abstract:
WI Status Report for Extended Reality and Media service (XRM) Phase 2 (XRM_Ph2).
Comment: To be provided after the meeting.

Plenary Discussion:

Noted.

Status: Noted.

S2-2504426 (WI STATUS REPORT) WI Status Report for 5GS Enhancement for Energy Efficiency and
Energy Saving (EnergySys) (Source: Rapporteur (Samsung))
Document for: Information
Abstract:
WI Status Report for 5GS Enhancement for Energy Efficiency and Energy Saving (EnergySys).
Comment: To be provided after the meeting.

Plenary Discussion:

Noted.

Status: Noted.

3GPP
Report of meeting S2-168

S2-2504427 (WI STATUS REPORT) WI Status Report for MPS for IMS Messaging and SMS services
(MPS4msg) (Source: Rapporteur (Peraton Labs))
Document for: Information
Abstract:
WI Status Report for MPS for IMS Messaging and SMS services (MPS4msg).
Comment: To be provided after the meeting.

Plenary Discussion:

Withdrawn.

Status: Withdrawn.

Noted.

Status: Noted.

S2-2504428 (WI STATUS REPORT) WI Status Report for Architecture Enhancements for Vehicle Mounted
Relays Phase 2 (VMR_Ph2) (Source: Rapporteur (Qualcomm))
Document for: Information
Abstract:
WI Status Report for Architecture Enhancements for Vehicle Mounted Relays Phase 2 (VMR_Ph2).
Comment: To be provided after the meeting.

Plenary Discussion:

Noted.

Status: Noted.

S2-2504429 (WI STATUS REPORT) WI Status Report for System Enhancement for Proximity-based
Services in 5GS - Phase 3 (5G_ProSe_Ph3) (Source: Rapporteur (TNO))
Document for: Information
Abstract:
WI Status Report for System Enhancement for Proximity-based Services in 5GS - Phase 3
(5G_ProSe_Ph3).
Comment: To be provided after the meeting.

Plenary Discussion:

Noted.

Status: Noted.

S2-2504430 (WI STATUS REPORT) WI Status Report for Identifying non-3GPP Devices Connecting behind
a UE or 5G-RG (UIA_ARC) (Source: Rapporteur (Interdigital))
Document for: Information
Abstract:
WI Status Report for Identifying non-3GPP Devices Connecting behind a UE or 5G-RG (UIA_ARC).
Comment: To be provided after the meeting.

Plenary Discussion:

Noted.

Status: Noted.

3GPP
Report of meeting S2-168

S2-2504431 (WI STATUS REPORT) WI Status Report for Enhancement of support for Edge Computing in
5G Core network - Phase 3 (eEDGE_5GC_Ph3) (Source: Rapporteur (Intel))
Document for: Information
Abstract:
WI Status Report for Enhancement of support for Edge Computing in 5G Core network - Phase 3
(eEDGE_5GC_Ph3).
Comment: To be provided after the meeting.

Plenary Discussion:

Noted.

Status: Noted.

S2-2504432 (WI STATUS REPORT) WI Status Report for Phase 3 for UAS, UAV and UAM (UAS_Ph3)
(Source: Rapporteur (LGE))
Document for: Information
Abstract:
WI Status Report for Phase 3 for UAS, UAV and UAM (UAS_Ph3).
Comment: To be provided after the meeting.

Plenary Discussion:

Noted.

Status: Noted.

S2-2504433 (WI STATUS REPORT) WI Status Report for UPF enhancement for Exposure And SBA Phase
2 (UPEAS_Ph2) (Source: Rapporteur (ZTE))
Document for: Information
Abstract:
WI Status Report for UPF enhancement for Exposure And SBA Phase 2 (UPEAS_Ph2).
Comment: To be provided after the meeting.

Plenary Discussion:

Noted.

Status: Noted.

S2-2504434 (WI STATUS REPORT) WI Status Report for System aspects of 5G NR Femto (5G_Femto)
(Source: Rapporteur (DOCOMO))
Document for: Information
Abstract:
WI Status Report for System aspects of 5G NR Femto (5G_Femto).
Comment: To be provided after the meeting.

Plenary Discussion:

Noted.

Status: Noted.

3GPP
Report of meeting S2-168

S2-2504435 (WI STATUS REPORT) WI Status Report for Multi-Access (ATSSS_Ph4) (MASSS) (Source:
Rapporteur (Apple))
Document for: Information
Abstract:
WI Status Report for Multi-Access (ATSSS_Ph4) (MASSS).
Comment: To be provided after the meeting.

Plenary Discussion:

Noted.

Status: Noted.

S2-2504436 (WI STATUS REPORT) WI Status Report for Architecture support of Ambient power-enabled
Internet of Things (AmbientIoT-ARC) (Source: Rapporteur (Huawei))
Document for: Information
Abstract:
WI Status Report for Architecture support of Ambient power-enabled Internet of Things (AmbientIoT-ARC).
Comment: To be provided after the meeting.

Plenary Discussion:

Noted.

Status: Noted.

S2-2504437 (WI STATUS REPORT) WI Status Report for Core Network Enhanced Support for Artificial
Intelligence (AI)/Machine Learning (ML) (AIML_CN) (Source: Rapporteur (vivo))
Document for: Information
Abstract:
WI Status Report for Core Network Enhanced Support for Artificial Intelligence (AI)/Machine Learning (ML)
(AIML_CN).
Comment: To be provided after the meeting.

Plenary Discussion:

Noted.

Status: Noted.

S2-2504438 (WI STATUS REPORT) WI Status Report for Study on Integration of satellite components in the
5G architecture Phase 4 (FS_5GSAT_Ph4_ARC) (Source: Rapporteur (CATT))
Document for: Information
Abstract:
WI Status Report for Study on Integration of satellite components in the 5G architecture Phase 4
(FS_5GSAT_Ph4_ARC).
Comment: To be provided after the meeting.

Plenary Discussion:

Noted.

Status: Noted.

3GPP
Report of meeting S2-168

S2-2504439 (WI STATUS REPORT) WI Status Report for Study on Architecture Enhancement to support
Integrated Sensing and Communication (FS_Sensing_ARC) (Source: Rapporteur (Xiaomi))
Document for: Information
Abstract:
WI Status Report for Study on Architecture Enhancement to support Integrated Sensing and Communication
(FS_Sensing_ARC).
Comment: To be provided after the meeting.

Plenary Discussion:

Noted.

Status: Noted.

S2-2504440 (WI STATUS REPORT) WI Status Report for Study on Core Network Enhanced Support for
Artificial Intelligence (AI)/Machine Learning (ML)_Ph2 (FS_AIML_CN_Ph2) (Source: Rapporteur (vivo))
Document for: Information
Abstract:
WI Status Report for Study on Core Network Enhanced Support for Artificial Intelligence (AI)/Machine
Learning (ML)_Ph2 (FS_AIML_CN_Ph2).
Comment: To be provided after the meeting.

Plenary Discussion:

Noted.

Status: Noted.

S2-2504441 (WI STATUS REPORT) WI Status Report for Study on Energy Efficiency and Energy Saving
Phase2 (FS_EnergySys_Ph2) (Source: Rapporteur (Lenovo))
Document for: Information
Abstract:
WI Status Report for Study on Energy Efficiency and Energy Saving Phase2 (FS_EnergySys_Ph2).
Comment: To be provided after the meeting.

Plenary Discussion:

Noted.

Status: Noted.

30.5 Review of the Work Plan and planning future meetings

S2-2503112 (WORK PLAN) TU budget for Rel-20 (Source: SA WG2 Chair)
Document for: Endorsement
Abstract:
Plenary Discussion:

This was withdrawn.

Status: Withdrawn.

3GPP
Report of meeting S2-168

S2-2503113 (WORK PLAN) Work Planning slides (Source: SA WG2 Chair)

Document for: Endorsement
Abstract:
Work Planning slides.
Plenary Discussion:

Ericsson expressed concerns with excluding AmbientIoT maintenance from the 4 TD quota in the August
meeting. This was revised to S2-2504388.

This was endorsed with a concern from Ericsson.

Status: Endorsed.

S2-2503114 (WORK PLAN) Work planning spreadsheet (Source: SA WG2 Chair)

Document for: Endorsement
Abstract:
Work planning spreadsheet.
Plenary Discussion:

This was reviewed and Nokia had a concern with giving it endorsed status, so this was then noted.

Status: Noted.

S2-2503116 (OTHER) Way of working guidance proposal (Source: SA WG2 Chair)

Document for: Endorsement
Abstract:
Plenary Discussion:

This was reviewed and comments collected. This was updated off-line and revised to S2-2504389.

This was reviewed and further discussed and updated and was revised to S2-2504416.

It was clarified that this is for guidance and there may be areas (e.g. 6G work) where the guidance is not
completely followed. This was then endorsed.

Status: Endorsed.

S2-2503118 (OTHER) Plan for SA2#168 Friday Plenary (Source: SA WG2 Chair)
Document for: Discussion
Abstract:
TSG SA Guidance to SA WG2 on 5GA studies.
Plenary Discussion:

This was noted.

Status: Noted.

S2-2504475 (OTHER) Plan for SA2#168 Friday Plenary. (Source: SA WG2 Chair)
Document for: Endorsement
Abstract:
This guidance has previously been shared via the SA WG2 email reflector. It gives a high-level plan for when
discussion of each of the Rel-20 topics should take place in Q2 2025.
Plenary Discussion:

Not handled.

Status: Not treated.

30.6 Proposals for Rel-20 5G Advanced Study/Work items

A summary of the drafting sessions was presented.

3GPP
Report of meeting S2-168

https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_168_Goteborg_2025-04/INBOX/DRAFTS/INS_ph2/S2-
250xxxx_Draft_Session_on_SA2_NetShare_ph2-after%20draft%20session.pptx

General

S2-2503118 (OTHER) TSG SA Guidance to SA WG2 on 5GA studies (Source: SA WG2 Chair)
Document for: Information
Abstract:
TSG SA Guidance to SA WG2 on 5GA studies.
Plenary Discussion:

This was not handled.

Status: Not handled.

S2-2504475 (OTHER) Guidance for SA WG2 Rel-20 preparation in Q2 2025. (Source: SA WG2 Chair)
Document for: Discussion
Abstract:
-.
Plenary Discussion:

User Identities and Authentication Architecture.

The feedback from SA WG3 (S2-2502850) indicated that SA WG3 would not be able to evaluate the security
aspects until there is an architecture provided by SA WG2. There were concerns with starting an NWM
moderated discussion on this. Qualcomm commented that there were discussions on this in previous
meetings and no agreement to discuss this in SA WG2 nor any consensus in TSG SA that a moderated
discussion should start. The SA WG2 Chair replied that TSG SA instructed not to start discussions until
SA WG3 had provided input, which they have.

It was commented that this work was already abandoned in Rel-19 due to no consensus to work on this
topic. The SA WG2 Chair asked whether there will be no NWM discussion because there is no agreement on
the WTs to consider or whether we should hold the NWM discussion and make a decision based on the
results of the discussions.

The SA WG2 Chair asked whether an e-mail discussion could be held instead. Qualcomm suggested that
interested companies discuss this and can bring a proposed study item to the next SA WG2 meeting, but did
not think there should be a formal SA WG2 input on this.

Qualcomm would object to the SA WG2 leadership holding an organised e-mail discussion on this with
deadlines, etc. The SA WG2 Chair replied that there was no intention to do this and e-mails can be
exchanged over the normal SA WG2 lists.

SMS to Emergency Centre:

It was suggested to have a simple NWM discussion on the Objective for the SID.

IMS resiliency:

An LS from SACT WG4 indicated that there is nothing for SA WG2 to do at this point. Nokia agreed that the
indications were that the work will be done by CT WGs and there is nothing for SA WG2. Huawei
commented that, for WT#1, this could destabilise the IMS system and did not support working on this.

It was decided that there is no need for SA WG2 to work further on this at this point.

This was noted.

Status: Noted.

3GPP
Report of meeting S2-168

S2-2502850 (LS IN) LS from SA WG3: LS on UIA Rel-20 in response to SA guidance from SA#107 (Source:
SA WG3 (S3-251673))
Document for: Action
Abstract:
SA WG3 would like to provide the following input for the topic of User Identities and Authentication
Architecture (UIA) in relation to TSG SA Guidance on Rel-20 5GA studies in SP-250418. SA WG3 will not be
able to perform a detailed security assessment and study on the potential security mechanisms for the
features until SA WG2 provides some architectural guidance information. Action: SA WG3 kindly asks SA
WG2 and TSG SA to take the above information into account.
Comment: Received at meeting.

Plenary Discussion:

Interdigital commented that this input asks SA WG2 to provide architectural information in order for them to
make a security analysis. Nokia commented that SA WG3 would like to use the User Identities work done by
SA WG2 for Rel 19. Ericsson commented that there is not much to reply on this LS except that it is specified
in TS 23.502, or to note this LS. Qualcomm suggested that the SA WG2 objectives that were not done in
Rel-19 are expected to be provided for Rel-20, but there are objections to including this without SA WG3
request. Companies were asked to see if there is consensus for a basis to hold some NWM discussion after
this meeting on this topic. Postponed.

Status: Postponed.

Indirect Network Sharing phase2

S2-2503060 (SID NEW) New SID on Study on Indirect Network Sharing phase2. (Source: China Unicom
(Moderator))
Document for: Approval
Abstract:
This is SI-1 as per moderator report in S2-2501576, based on initial WTs according to SA plenary outcome.
The document needs to be updated based on any agreements reached during the meeting.
Comment: Bad Acronym, Consider FS_NetShare_Ph2_ARC.

Plenary Discussion:

A draft update was provided in the drafts folder:

https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_168_Goteborg_2025-04/INBOX/DRAFTS/INS_ph2/S2-
25xxxxx_was03060_NEW_SI_NetShare_ph2_Moderator.zip

This was discussed and left for off-line discussion and revised to S2-2504371.

This was discussed in the Thursday Work Planning session. This should be a WID, not a SID. This was and
revised, to contain WT#1 only, to S2-2504415.

Qualcomm commented that the inclusion of the Satellite parent WI was no longer needed and INS_SAT can
be removed. This was revised to S2-2504474.

This new SWID was endorsed.

Status: Endorsed.

3GPP
Report of meeting S2-168

S2-2503066 (SID NEW) New SID on Study on Indirect Network Sharing phase2. (Source: China Unicom)
Document for: Approval
Abstract:
This is SI-1 as per moderator report in S2-2501576, based on initial WTs according to SA plenary outcome.
The document needs to be updated based on any agreements reached during the meeting.
Comment: Bad Acronym, Consider FS_NetShare_Ph2_ARC. Alternative to S2-2503060?

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503715 (SID NEW) New SID on Study on Indirect Network Sharing phase2. (Source: NEC)
Document for: Approval
Abstract:
This is SI-1 as per moderator report in S2-2501576, based on initial WTs according to SA plenary outcome.
The document needs to be updated based on any agreements reached during the meeting.
Comment: Bad Acronym, Consider FS_NetShare_Ph2_ARC. Alternative to S2-2503060?

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503830 (SID NEW) New SID on Study on Indirect Network Sharing phase2. (Source: CableLabs)
Document for: Approval
Abstract:
This is SI-1 as per moderator report in S2-2501576, based on initial WTs according to SA plenary outcome.
The document needs to be updated based on any agreements reached during the meeting.
Comment: Bad Acronym, Consider FS_NetShare_Ph2_ARC. Alternative to S2-2503060?

Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503059 (DISCUSSION) Moderator summary and proposal on: Moderated discussion for Indirect
Network Sharing phase2. (Source: China Unicom (Moderator))
Document for: Decision
Abstract:
Moderator summary and proposal on SA WG2 Rel-20 25Q1 moderated discussion Indirect Network Sharing
Phase2 held between Feb 10 Feb 28, 2025.
Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503069 (DISCUSSION) Indirect Network Sharing phase 2 (Source: China Unicom)

Document for: Discussion
Abstract:
Discussion paper on Indirect Network Sharing phase 2 from China Unicom.
Plenary Discussion:

Not handled.

Status: Not treated.

3GPP
Report of meeting S2-168

XRM Ph3

S2-2503826 (SID NEW) Study on Extended Reality and Media Service (XRM) Phase 3. (Source: Nokia)
Document for: Approval
Abstract:
Study on Extended Reality and Media Service (XRM) Phase 3.
Comment: Consider Acronym: FS_XRM_Ph3_ARC. Alternative to S2-2503592?

Plenary Discussion:

An updated draft r1 was provided in the drafts folder:

https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_168_Goteborg_2025-04/INBOX/DRAFTS/Rel-20-
XRM_Ph3/S2-2503826_XRM_Ph3r1.docx

There were some comments and was left for off-line discussion and revised to S2-2504372.

This was discussed in the Thursday Work Planning session and no consensus could be reached. Further
discussion was recommended until the next meeting, where there will be limited time for further discussion.
This was then postponed.

Status: Postponed.

S2-2503592 (SID NEW) New SID on 5GS XRM Ph3. (Source: CATT)
Document for: Approval
Abstract:
New SID on 5GS XRM Ph3.
Comment: Bad Acronym, Consider FS_XRM_Ph3_ARC.

Plenary Discussion:

Not handled.

https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_168_Goteborg_2025-04/INBOX/DRAFTS/
R20%20FS_NG_RTC_Ph3/draft%20S2-250xxxx%20was%2003767%20FS_NG_RTC_Ph3%20SID
%20update.docx

A number of comments were received and this was left for off-line discussion and revised to S2-2504373

Status: Postponed.

S2-2503768 (REPORT) Moderator report: Moderated discussion on NG_RTC continuation (Source: China
Mobile)
Document for: Information
Abstract:
This contribution provides the summary report of moderated NWM discussion on NG_RTC continuation.
Plenary Discussion:

Not handled.

Status: Not treated.

Mission Critical Services, Multimedia Priority Services

S2-2503243 (REPORT) NWM summary report on Mission Critical Services, Multimedia Priority Services
(Source: Peraton Labs (moderator))
Document for: Discussion
Abstract:
Moderator summary on Mission Critical Services, Multimedia Priority Services features NWM discussions
held between February 10 - February 28, 2025.
Plenary Discussion:

Not handled.

Status: Not treated.

S2-2502946 (DISCUSSION) Ambient IoT scope for Rel-20. (Source: Qualcomm)

Document for: Discussion
Abstract:
This contribution proposes Rel-20 AIoT work to focus on Topology 2 support, building upon the agreements
already reached for Topology 2 in Rel-19 (as documented in TR 23.700-13).
Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503014 (DISCUSSION) Discussion on Rel-20 Ambient IoT Scope. (Source: CATT)

Document for: Discussion
Abstract:
This paper discussed Rel-20 Ambient IoT Scope.
Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503029 (DISCUSSION) LGE View on Rel-20 Ambient IoT study (Source: LG Electronics)
Document for: Discussion
Abstract:
LGE View on Rel-20 Ambient IoT study.
Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503051 (DISCUSSION) Proposed scope of AmbientIoT-ARC Phase 2. (Source: OPPO)

Document for: Discussion
Abstract:
The Rel-20 AIoT scope has being discussed since SA#106. In the Rel-19 study, both RAN WGs and SA
WGs have studied th topology 1 and topology 2. In SA WG2, interim conclusion was also made to topology
2. Since Topology 2 is not pursued in Rel-19 normative phase as per RAN WI in RP-243326, SA WG2 does
not continue the work related to topology 2.
Plenary Discussion:

Not handled.

Status: Not treated.

3GPP
Report of meeting S2-168

S2-2503107 (DISCUSSION) Discussion on Rel-20 AIoT. (Source: NEC)

Document for: Discussion
Abstract:
Discuss the scope and time plan of Rel-20 AIoT.
Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503164 (DISCUSSION) Discussion on Rel-20 Ambient IoT study. (Source: Ofinno)

Document for: Decision
Abstract:
This document proposes scope of Rel-20 AIoT study.
Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503480 (DISCUSSION) Discussion on Release 20 Ambient IoT SID scope. (Source: NTT DOCOMO)
Document for: Discussion
Abstract:
This paper discusses potential scope for Rel-20 Ambient IoT study.
Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503503 (DISCUSSION) Discussion on R20 Ambient IoT SID scope (Source: Nokia Korea)
Document for: Discussion
Abstract:
Discussion on R20 Ambient IoT SID scope.
Plenary Discussion:

Not handled.

IMS resiliency

S2-2503105 (DISCUSSION) Discussion on IMS resiliency study. (Source: KDDI, SK Telecom)

Document for: Discussion
Abstract:
This paper provides background for IMS resiliency study.
Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503797 (SID NEW) Resilient Notification. (Source: EchoStar, Boost Mobile)

Document for: Approval
Abstract:
NewSID: Study on Resilient Notification for 5G Satellite Access.
Comment: Space in Acronym. Consider Acronym FS_5GSAT_Ph4_RN_ARC?

Convenor comment: Moved to 30.6.

Plenary Discussion:

There were a number of comments and some companies considered there was not much study for SA WG2
to do as this could be handled with alignment with the RAN and other WG decisions for priority messaging.
This was left for further consideration by companies and was noted.

Status: Noted.

S2-2502984 (DISCUSSION) Discussion for WT-3 Resilient Notification. (Source: EchoStar, Boost Mobile)
Document for: Agreement
Abstract:
This contribution discusses potential procedure impact to deliver resilient notification to UE when legacy
paging fails.
Convenor comment: Moved to AI 30.6.

Plenary Discussion:

The following was agreed:

SA WG2 is not going to handle a Rel-20 study item based on the SA WG1 requirement on Resilient
Notification Service (see TS 22.261, clause 6.46.2). It is up to RAN whether to initiate any work as
appropriate (subject to RAN planning) and SA WG2 will address any resulting SA WG2 work based on RAN
outcome, if required, subject to SA WG2 planning.

This document was then noted.

Status: Noted.

3GPP
Report of meeting S2-168

Other

S2-2503557 (DISCUSSION) Discussion on enhancement to IMS network capability exposure. (Source:

Huawei, HiSilicon)
Document for: Information
Abstract:
Discusses why the enhancement to IMS network capability exposure to support IMS audio/video call and
messaging need to be studied further in Rel-20.
Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503661 (DISCUSSION) Discussion paper for information on Loop prevention and Multi Domain Support
in the study on Industrial Networks Enhancements. (Source: Nokia)
Document for: Information
Abstract:
This paper explains the need of support at 5GS to support industrial ethernet networks in context to
brownfield deployments, to support loop prevention and multi domains.
Plenary Discussion:

Not handled.

Status: Not treated.

30.7 6G Study Item discussion papers

Drafts considered for general discussion on Monday Q4.

6G SOID preparation

- what do we want out of this week?

- A document that forms the basis of the NWM discussion that will be organized following this
meeting that:
- Identified work areas
- Describes the work areas
- identifies dependencies between was
- identifies dependencies on RAN or other SA WGs.
- The NWM discussion will invite further input from companies on these aspects

Discussion on SA2 6G study v2.docx

https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_168_Goteborg_2025-04/INBOX/DRAFTS/6G%20SID/
Discussion%20on%20SA2%206G%20study%20v2.docx

Areas reviewed and discussed:

- General Architecture
- Migration and interworking
- Native AI
- Common Data framework
- Sensing

This was further discussed (draft v4) on Tuesday Q4 and an updated version allocated to S2-2504139.

3GPP
Report of meeting S2-168

S2-2504139 (OTHER) Rel-20 6G Preparation (Source: Moderator (ZTE))

Document for: Discussion
Abstract:
Rel-20 6G Preparation inputs review and consolidation.
Plenary Discussion:

This was revised, to capture the result of the Tuesday Q4 drafting session, to S2-2504140.

This was discussed in the Thursday Work Planning session and revised to S2-2504414.

AT&T asked whether 'not support' is the same as object to. Ericsson commented that the NWM process is
not a meeting and objections should only be made at the main meetings. Qualcomm commented that this
information is intended to allow the moderator to make an assessment of the acceptability of the different
work areas. Tee moderator was asked to fill in any Conference Call dates and times.

This should be used as a template for the questions by the NWM discussions moderator. This was
then noted.

Status: Noted.

S2-2502869 (DISCUSSION) NTT DOCOMO's views on 6G study (Source: NTT DOCOMO)

Document for: Discussion
Abstract:
NTT DOCOMO's views on 6G SID scope content for architecture requirements.
Plenary Discussion:

Not handled.

Status: Not treated.

S2-2502873 (DISCUSSION) AT&T views on 6G study in SA WG2 (Source: AT&T Services, Inc.)
Document for: Discussion
Abstract:
AT&T views on 6G study in SA WG2.
Plenary Discussion:

Not handled.

Status: Not treated.

S2-2502878 (DISCUSSION) Verizons views on 6G study in SA WG2 (Source: Verizon Spain)

Document for: Discussion
Abstract:
Verizons views on 6G study in SA WG2.
Plenary Discussion:

Not handled.

Status: Not treated.

S2-2502884 (DISCUSSION) China Mobile views about 6G Architecture (Source: China Mobile)
Document for: Information
Abstract:
China Mobile views about 6G Architecture.
Plenary Discussion:

Not handled.

Status: Not treated.

3GPP
Report of meeting S2-168

S2-2502887 (DISCUSSION) KPN N.V. views on 6G Architecture (Source: KPN N.V.)

Document for: Discussion
Abstract:
KPN N.V. views on 6G Architecture.
Plenary Discussion:

Not handled.

Status: Not treated.

S2-2502896 (DISCUSSION) Intel views on 6G study (Source: Intel)

Document for: Information
Abstract:
Intel views on 6G study.
Plenary Discussion:

Not handled.

S2-2502959 (DISCUSSION) Boost Mobile views on 6G study (Source: Boost Mobile Network)
Document for: Discussion
Abstract:
Boost Mobile views on 6G SID scope content.
Plenary Discussion:

Not handled.

Status: Not treated.

3GPP
Report of meeting S2-168

S2-2502989 (DISCUSSION) SK Telecom views on 6G study (Source: SK Telecom)

S2-2503286 (DISCUSSION) China Telecom's View on First 6G Service and Architecture (Source: China
Telecom)
Document for: Discussion
Abstract:
China Telecom's View on First 6G Service and Architecture.
Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503293 (DISCUSSION) Vivo view on 6G system architecture (Source: vivo)

Document for: Information
Abstract:
Some views on 6G system architecture.
Plenary Discussion:

Not handled.

Status: Not treated.

3GPP
Report of meeting S2-168

S2-2503375 (DISCUSSION) Areas of NEC interests in 6G architecture (Source: NEC Corporation)

Document for: Discussion
Abstract:
Areas of NEC interests in 6G architecture.
Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503377 (DISCUSSION) Discussion for 6G Study on Interworking and Migration (Source: Samsung)
Document for: Decision
Abstract:
Discussion for 6G Study on Interworking and Migration.
Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503412 (DISCUSSION) Apple's View on 6G SID Scope (Source: Apple)

Document for: Discussion
Abstract:
Apple's View on 6G SID Scope.
Plenary Discussion:

Not handled.

3GPP
Report of meeting S2-168

S2-2503823 (DISCUSSION) Interdigital's views on SA WG2 6G Study item (Source: InterDigital Canada)
Document for: Discussion
Abstract:
Interdigital's views on SA WG2 6G Study item.
Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503828 (DISCUSSION) MSO View on 6G SID Scope (Source: CableLabs, Charter Communications,
Comcast)
Document for: Presentation
Abstract:
MSO priorities on Rel-20 6G.
Plenary Discussion:

Not handled.

Status: Not treated.

S2-2503859 (DISCUSSION) Charter Communications - 6G System Architecture and Services Priorities

(Source: Charter Communications, Inc)
Document for: Discussion
Abstract:
Charter Communications - 6G System Architecture and Services Priorities.
Plenary Discussion:

Not handled.

The SA WG2 Chair thanked the hosts for inviting SA WG2 to Goteborg, Sweden and for the good facilities.
He thanked the Rapporteurs for convening the drafting sessions, the Vice Chairs for their support before and
during the meeting and the MCC Secretary for his support. He wished delegates safe travels back to their
homes and closed the meeting.

3GPP
Report of meeting S2-168

Item
30.4 S2-2504433 WI WI Status Report for UPF enhancement for Exposure Rapporteur (ZTE) Rel-19 UPEAS_ To be provided after the Noted
STATUS And SBA Phase 2 (UPEAS_Ph2) Ph2 meeting. Noted
REPORT
30.4 S2-2504434 WI WI Status Report for System aspects of 5G NR Rapporteur Rel-19 5G_Femt To be provided after the Noted
STATUS Femto (5G_Femto) (DOCOMO) o meeting. Noted
REPORT
30.4 S2-2504435 WI WI Status Report for Multi-Access (ATSSS_Ph4) Rapporteur (Apple) Rel-19 MASSS To be provided after the Noted
STATUS (MASSS) meeting. Noted
REPORT
30.4 S2-2504436 WI WI Status Report for Architecture support of Ambient Rapporteur (Huawei) Rel-19 AmbientI To be provided after the Noted
STATUS power-enabled Internet of Things (AmbientIoT-ARC) oT-ARC meeting. Noted
REPORT
30.4 S2-2504437 WI WI Status Report for Core Network Enhanced Rapporteur (vivo) Rel-19 AIML_C To be provided after the Noted
STATUS Support for Artificial Intelligence (AI)/Machine N meeting. Noted
REPORT Learning (ML) (AIML_CN)
30.4 S2-2504438 WI WI Status Report for Study on Integration of satellite Rapporteur (CATT) Rel-20 FS_5GS To be provided after the Noted
STATUS components in the 5G architecture Phase 4 AT_Ph4_ meeting. Noted
REPORT (FS_5GSAT_Ph4_ARC) ARC
30.4 S2-2504439 WI WI Status Report for Study on Architecture Rapporteur (Xiaomi) Rel-20 FS_Sens To be provided after the Noted
STATUS Enhancement to support Integrated Sensing and ing_ARC meeting. Noted
REPORT Communication (FS_Sensing_ARC)
30.4 S2-2504440 WI WI Status Report for Study on Core Network Rapporteur (vivo) Rel-20 FS_AIML To be provided after the Noted
STATUS Enhanced Support for Artificial Intelligence _CN_Ph meeting. Noted
REPORT (AI)/Machine Learning (ML)_Ph2 2
(FS_AIML_CN_Ph2)
30.4 S2-2504441 WI WI Status Report for Study on Energy Efficiency and Rapporteur (Lenovo) Rel-20 FS_Ener To be provided after the Noted
STATUS Energy Saving Phase2 (FS_EnergySys_Ph2) gySys_P meeting. Noted
REPORT h2
19.32 S2-2504467 CR 23.501 CR6192R3 (Rel-19, 'F'): On the termination of Nokia Rel-19 TEI19_Sl Revision of S2-2504402. Agreed
slice replacement iceSel Agreed in parallel
session. Block approved
4.1 S2-2504468 LS OUT Reply LS on OSAppID usage by AppToken use case SA WG2 Rel-19 TEI19 Revision of S2-2504393. Approved
Agreed in parallel
session. Block approved
4.1 S2-2504469 LS OUT LS on Optimizations to UPF event subscriptions and SA WG2 Rel-19 FS_PAID Revision of S2-2504397. Approved
reporting C_UPF Agreed in parallel
session. Block approved
19.10. S2-2504470 CR 23.256 CR0199R3 (Rel-19, 'F'): The indication on China Mobile, LG Rel-19 UAS_Ph Revision of S2-2504377. Agreed
2 altitude thresholds and reporting periodicity for the Electronics 3 Agreed in parallel
aerial UE's altitude reporting session. Block approved
19.10. S2-2504471 LS OUT Reply LS on UAV regulation from RAN WG3 SA WG2 Rel-19 Revision of S2-2504378. Approved
2 Agreed in parallel
session. Block approved
6.2 S2-2504472 CR 23.502 CR5440R3 (Rel-18, 'F'): Registration Huawei, Hisilicom Rel-18 TEI18, Revision of S2-2504410. Agreed
handling during the mobility from non-3GPP access 5GS_Ph Agreed in parallel
to 3GPP access 1 session. Block approved

3GPP
Report of meeting S2-168

AI TD Type Title Source Rel Work Comment Decision Revised to

Item
6.2 S2-2504473 CR 23.502 CR5441R3 (Rel-19, 'A'): Registration Huawei, Hisilicom Rel-19 5GS_Ph Revision of S2-2504411. Agreed
handling during the mobility from non-3GPP access 1, Agreed in parallel
to 3GPP access TEI19_N session. Block approved
etShare
30.6 S2-2504474 SWID New WID on Indirect Network Sharing phase2. China Unicom Rel-20 Revision of S2-2504415. Endorsed
NEW (Moderator) Endorsed
30.5 S2-2504475 OTHER Plan for SA2#168 Friday Plenary SA WG2 Chair Noted Noted
19.15. S2-2504476 CR 23.288 CR1429R4 (Rel-19, 'F'): Updates on VFL Interdigital, Samsung Rel-19 AIML_C Revision of S2-2504243. Agreed
2 inference N Agreed in parallel
session. Block approved
19.8.2 S2-2504477 CR 23.503 CR1551R4 (Rel-19, 'F'): Clarificaiton on Huawei, HiSilicon, Rel-19 UIA_AR Revision of S2-2504333. Agreed
supporting multiple non-3GPP device identifiers Samsung, Deutsche C This CR was agreed
Telekom, Nokia, LGE,
Charter
Communications, ZTE
19.32 S2-2504478 CR 23.503 CR1532R3 (Rel-19, 'F'): Clarification on AF Huawei, HiSilicon Rel-19 TEI19_Sl Revision of S2-2504404. Agreed
requested network slice replacement iceSel This CR was agreed
20.4.1 S2-2504479 P-CR Energy Optimization Trigger for PCF based Policy Ericsson Rel-20 FS_Ener Revision of S2-2504343. Approved
Control. gySys_P This P-CR was approved
h2
9.12.2 S2-2504480 CR 23.501 CR5255R12 (Rel-18, 'F'): Clarifications for Huawei, HiSilicon, Rel-18 XRM Revision of S2-2504250. Agreed
multi-modal services Nokia This CR was agreed
19.3.2 S2-2504481 CR 23.503 CR1547R3 (Rel-19, 'F'): Clarifications for rate Huawei, HiSilicon Rel-19 XRM_Ph Revision of S2-2504166. Agreed
limitation exposure 2 This CR was agreed
2 S2-2504482 AGENDA SA WG2#168 meeting schedule SA WG2 Chair Revision of S2-2502790. Noted
Noted
1635 Entries

A.2 List of meeting documents ordered by Agenda Item

Table A.2: List of meeting documents ordered by Agenda Item

Item
30.7 S2-2503594 DISCUSSI Vivo view on 6G AIML vivo Not Handled -
ON
30.7 S2-2503602 DISCUSSI Samsung view on 6G Architecture Samsung Rel-20 Not Handled -
ON
30.7 S2-2503611 DISCUSSI Topics for SA WG2 6G Study Vodafone Rel-20 Not Handled -
ON
30.7 S2-2503613 DISCUSSI ZTE view on 6G scope for Architecture ZTE Not Handled -
ON
30.7 S2-2503669 DISCUSSI Discussion for 6G Study on Service Plane Samsung Rel-20 Not Handled -
ON
30.7 S2-2503675 DISCUSSI CATT views on SA WG2 6G SID CATT Rel-20 Not Handled -
ON
30.7 S2-2503716 DISCUSSI Discussion for 6G study on Native AI Samsung Rel-20 Not Handled -
ON
30.7 S2-2503733 DISCUSSI Discussion for 6G Study on Network Resilience Samsung Rel-20 Not Handled -
ON
30.7 S2-2503749 DISCUSSI Discussion for 6G Study on compact and simple Samsung Electronics Rel-20 Not Handled -
ON network architecture France SA
30.7 S2-2503810 DISCUSSI Thoughts on SA WG2 6G Study Scope MediaTek Inc. Rel-20 Not Handled -
ON
30.7 S2-2503823 DISCUSSI Interdigital's views on SA WG2 6G Study item InterDigital Canada Rel-20 Not Handled -
ON
30.7 S2-2503828 DISCUSSI MSO View on 6G SID Scope CableLabs, Charter Rel-20 Not Handled -
ON Communications,
Comcast
30.7 S2-2503859 DISCUSSI Charter Communications - 6G System Architecture Charter Rel-20 Not Handled -
ON and Services Priorities Communications, Inc
30.7 S2-2503871 DISCUSSI Xiaomi's view on the key areas of 6GC study Xiaomi Rel-20 Not Handled -
ON
30.7 S2-2503875 DISCUSSI Views on Priority Topics for 6G System Architecture Deutsche Telekom Rel-20 Not Handled -
ON SID AG
30.7 S2-2503892 DISCUSSI LGE view on 6G study LG Electronics Rel-20 Not Handled -
ON
1635 Entries

3GPP
Report of meeting S2-168

ANNEX B Change Requests and P-CRs

B.1 List of agreed CRs at meeting S2#168
Table B.1: List of agreed CRs at meeting S2#168

Spec CR R Rel Subject Ca Vsn Mtg TD Source Work U M R C Aff Cl Status OAffS
t Item I E A N p
C N
C
23.203 1142 1 Rel-19 Clarification on QCI for satellite F 19.1.0 S2-168 S2-2503914 CATT 5GSAT_ X 6.1.7.2 Agreed
access Ph3-ARC
23.228 1601 2 Rel-19 KI#1: Corrections to IMS F 19.2.0 S2-168 S2-2504210 Ericsson, Nokia, ZTE, NG_RTC AA.2.1.2.1 Agreed
Subscribe/Notify Framework Huawei _Ph2 ,
Architecture AA.2.1.5.1
, AA.2.2.3,
AA.2.4.5.1
,
AD2.4.5.2,
AA.2.4.5.3
, AD.1,
AD.2.3.2,
AD.2.2.3,
AD.2.4,
AD.2.5.2,
AD.3.1,
AD.3.2,
AD.3.3
23.228 1617 3 Rel-19 KI#2: Correction of procedures F 19.2.0 S2-168 S2-2504248 Nokia, ZTE, Huawei, NG_RTC AG.2.1.1, Agreed
in clause AG HiSilicon _Ph2 AG.2.1.2,
AG.2.1.3,
AG.2.2.1,
AG.2.2.2,
AG2.3
23.228 1622 2 Rel-19 Correction on DC multiplexing F 19.2.0 S2-168 S2-2504208 Qualcomm Incorporated NG_RTC AC.7.10.2. Agreed
capability negotiation _Ph2 1,
AC.2.2.5
23.228 1634 2 Rel-19 Correction on IMS Service F 19.2.0 S2-168 S2-2504211 ZTE NG_RTC X AA.2.4.3.2 Agreed
Definition _Ph2 ,
AA.2.4.4.2
,
AA.2.4.4.3

3GPP
Report of meeting S2-168

Spec CR R Rel Subject Ca Vsn Mtg TD Source Work U M R C Aff Cl Status OAffS
t Item I E A N p
C N
C
23.228 1635 3 Rel-19 Additional Information in Adding F 19.2.0 S2-168 S2-2504214 ZTE, Qualcomm NG_RTC X AG.2.1.0, Agreed
P2P ADC Procedure Incorporated _Ph2 AG.2.1.1,
AG.2.1.2,
AG.2.1.3
23.228 1641 2 Rel-18 Correction on bootstrap DC F 18.9.0 S2-168 S2-2504204 China Mobile, Nokia, NG_RTC AC.7.6, Agreed
removal Huawei, Ericsson AC.1
23.228 1642 2 Rel-19 Correction on bootstrap DC A 19.2.0 S2-168 S2-2504205 China Mobile, Nokia, NG_RTC AC.7.6, Agreed
removal Huawei, Ericsson AC.1
23.256 0193 1 Rel-19 Assigned trajectory event for in- F 19.2.0 S2-168 S2-2504132 Ericsson UAS_Ph 5.12.3 Agreed
flight monitoring 3
23.256 0194 2 Rel-19 Instructing a UAV to stop the C 19.2.0 S2-168 S2-2504375 Ericsson, CATT UAS_Ph 5.16.X Agreed
altitude reporting 3, TEI19 (new)
23.256 0198 2 Rel-19 Altitude reporting cancellation C 19.2.0 S2-168 S2-2504376 CATT, Ericsson UAS_Ph 4.4.1.1.3.1 Agreed
3 ,
4.4.1.1.3.3
,
4.4.1.1.3.5
, 5.16.1
23.256 0199 3 Rel-19 The indication on altitude F 19.2.0 S2-168 S2-2504470 China Mobile, LG UAS_Ph 5.16.2,5.1 Agreed
thresholds and reporting Electronics 3 6.3
periodicity for the aerial UE's
altitude reporting
23.273 0700 2 Rel-19 Removal of requirements C 19.2.0 S2-168 S2-2504200 Vivo, Xiaomi, ZTE, AIML_C 3.1, Agreed
related to case 2b OPPO, Mediatek Inc., N 5.18.0,
Samsung, Nokia, CATT, 5.18.2,
Ericsson, Qualcomm 6.22.2
Incorporated, Huawei, (void),
HiSilicon, ERTI 6.22.3,
6.22.4,
8.3.4.3
23.273 0703 2 Rel-18 Solving UE shall have F 18.9.0 S2-168 S2-2504087 Ericsson, ZTE, CATT 5G_eLC 4.3.5, 5.1, Agreed
maximum one LCS-UPP S_Ph3 6.18.1,
6.18.2
23.273 0717 2 Rel-18 Clarification and correction on F 18.9.0 S2-168 S2-2504086 Huawei, HiSilicon 5G_eLC X 6.18.3, Agreed
modification of UP connection S_Ph3 8.3.2.5
between UE and LMF
23.273 0720 2 Rel-19 Resolve ENs on input data for F 19.2.0 S2-168 S2-2504201 CATT, Ericsson, vivo, AIML_C 5.18.0, Agreed
LMF based AI/ML positioning Huawei, HiSilicon N 6.22.3,
6.22.4,
8.3.4.3
23.273 0722 3 Rel-18 Solve the failure of the user F 18.9.0 S2-168 S2-2504349 CATT, Ericsson 5G_eLC 6.18.3 Agreed
plane connection establishment S_Ph3
23.273 0723 3 Rel-19 Solve the failure of the user A 19.2.0 S2-168 S2-2504350 CATT, Ericsson 5G_eLC 6.18.3 Agreed
plane connection establishment S_Ph3

3GPP
Report of meeting S2-168

Spec CR R Rel Subject Ca Vsn Mtg TD Source Work U M R C Aff Cl Status OAffS
t Item I E A N p
C N
C
23.273 0730 - Rel-19 Correction of the 5GC-MT-LR F 19.2.0 S2-168 S2-2503818 Qualcomm Incorporated, VMR_Ph 6.1.5 Agreed
procedure involving MWAB Nokia 2
23.288 1386 3 Rel-19 Enhancements on the input and F 19.2.0 S2-168 S2-2504219 China Mobile, ETRI, AIML_C 6.23.2, Agreed
output of QoS and Policy Samsung, Huawei N 6.23.3
Assistance Analytics
23.288 1403 1 Rel-19 Clarifications on the definition of F 19.2.0 S2-168 S2-2504125 ZTE eNA_Ph3 5C.1 Agreed
accuracy , TEI19
23.288 1405 1 Rel-19 Clarifications on the file address F 19.2.0 S2-168 S2-2504126 ZTE eNA_Ph3 10.3.4 Agreed
related to ADRF , TEI19
23.288 1411 3 Rel-19 Optimization of VFL triggers F 19.2.0 S2-168 S2-2504221 ZTE, Huawei, Hisilicon, AIML_C 6.2H.2.3.1, Agreed
vivo, OPPO, Nokia, N 6.2H.2.3.2
Futurewei, Samsung,
China Mobile, Interdigital
23.288 1417 1 Rel-19 Alignment of existing F 19.2.0 S2-168 S2-2503972 Huawei, HiSilicon, ZTE AIML_C 6.2D.2, Agreed
mechanisms for accuracy N 6.2E.2,
generation impacted by VFL 6.2E.3.1
procedures
23.288 1421 2 Rel-19 Update triggering Case A and F 19.2.0 S2-168 S2-2504220 Ericsson, China AIML_C 6.2A.2; Agreed
some corrections and Resolving Telecom, ZTE N 6.2H.2.3.1;
ENs for VFL 6.2H.2.3.2;
6.2H.2.4.2;
6.2H.3;
new
6.2H.X,
7.5.2;
7.12.2;
11.5.1;
11.5.2;
12.6.1;
12.6.2;
11.2.1;
11.2.2;
12.2.1 and
12.2.2

3GPP
Report of meeting S2-168

Spec CR R Rel Subject Ca Vsn Mtg TD Source Work U M R C Aff Cl Status OAffS
t Item I E A N p
C N
C
23.288 1425 2 Rel-19 Parameters for vertical F 19.2.0 S2-168 S2-2504216 Nokia, Vivo, Huawei, AIML_C 6.2H.2.4.1, Agreed
federated learning inference Oppo, Samsung N new
procedure 6.2H.2.4.x,
7.13.2,
7.13.4,
7.13.5,
11.3.1,
11.3.2,
11.3.4,
11.3.5,
12.3.1,
12.3.2,
12.3.4,
12.3.5
23.288 1429 4 Rel-19 Updates on VFL inference F 19.2.0 S2-168 S2-2504476 Interdigital, Samsung AIML_C 6.2H.2.4.1 Agreed
N
23.288 1433 2 Rel-19 Editor s Note clean up for the F 19.2.0 S2-168 S2-2504202 OPPO, Nokia AIML_C 6.2H.2.2.1, Agreed
VFL N 6.2H.2.2.2,
6.2H.2.3.1,
6.2H.2.3.2,
6.2H.2.4.2
23.288 1438 1 Rel-18 Correlate the Slice Load to an F 18.9.0 S2-168 S2-2504368 Verizon, Oracle, CATT, TEI18, 6.3.3A Agreed
AOI when location is provided Ericsson eNA_Ph2
23.288 1439 1 Rel-19 Attribute Level Change F 19.2.0 S2-168 S2-2504369 Verizon, Oracle, CATT eNA_Ph2 6.3.3A Agreed
, TEI19
23.288 1447 1 Rel-19 Correction on analytics F 19.2.0 S2-168 S2-2504127 Vivo eNA_Ph3 5A.3.2, Agreed
feedback information 5A.4,
5C.1,
6.1.3.
23.288 1450 2 Rel-19 Maintenance of VFL model F 19.2.0 S2-168 S2-2504218 Samsung, ZTE, Nokia, AIML_C 5.2, Agreed
training and inference with OPPO, LG Electronics, N 6.2H.2.1.2,
client intermediate results Ericsson 6.2H.2.2.2,
sharing between VFL clients 6.2H.2.3.1,
6.2H.2.3.2,
6.2H.2.4.2
23.304 0543 1 Rel-19 Removing QoS EN F 19.3.0 S2-168 S2-2504116 KPN N.V. 5G_ProS 6.5.1.4 Agreed
e_Ph3

3GPP
Report of meeting S2-168

Spec CR R Rel Subject Ca Vsn Mtg TD Source Work U M R C Aff Cl Status OAffS
t Item I E A N p
C N
C
23.304 0544 - Rel-19 Editorial corrections D 19.3.0 S2-168 S2-2502886 KPN N.V. FS_5G_ 4.2.7.1A, Agreed
ProSe_P 4.3.3,
h2 4.3.4,
4.3.5,
4.3.8,
4.3.12.2,
5.1.1,
5.1.1a,
5.1.4.1a,
5.1.4.2.1a,
5.1.4.2.2a,
5.1.5.1a,
5.1.5.2.1a,
5.1.5.2.2a,
5.2.6,
5.6.3.1,
5.8.3.1,
5.8.3.2,
6.3.2.5,
6.3.2.5.1,
6.3.2.5.2,
6.3.2.5.4,
6.3.2.6.3.1
, 6.4.3.8,
6.4.3.8.1,
6.4.3.9.2,
6.4.
23.304 0545 1 Rel-19 Updates to Common identifiers F 19.3.0 S2-168 S2-2504117 Ericsson, AT&T 5G_ProS 5.8.3.1 Agreed
for 5G ProSe UE-to-Network e_Ph3
Relay
23.304 0546 1 Rel-19 Introduction of Multi-hop Layer- F 19.3.0 S2-168 S2-2504123 CATT, LG Electronics 5G_ProS 1, 3.1, Agreed
2 UE-to-Network relaying e_Ph3 4.2.7.2a,
4.3.1,
4.3.3,
4.3.5,
4.3.8,
5.1.1,
5.1.1a,
5.1.4.1a
23.304 0547 1 Rel-19 Policy/Parameter provisioning F 19.3.0 S2-168 S2-2504118 OPPO 5G_ProS 5.1.4.1a, Agreed
to support PWS for 5G ProSe e_Ph3 5.18
multi-hop U2N Relay
23.304 0548 2 Rel-19 Clarification on Multi-hop U2N F 19.3.0 S2-168 S2-2504390 Huawei, HiSilicon, 5G_ProS 6.3.2.5.3, Agreed
and U2U Discovery Samsung e_Ph3 6.3.2.6.3.2
,
6.4.3.10.2

3GPP
Report of meeting S2-168

Spec CR R Rel Subject Ca Vsn Mtg TD Source Work U M R C Aff Cl Status OAffS
t Item I E A N p
C N
C
23.304 0549 2 Rel-19 Clarification on Relay F 19.3.0 S2-168 S2-2504391 Huawei, HiSilicon 5G_ProS 6.4.3.8.1 Agreed
reselection for 5G ProSe e_Ph3
Remote UE with 5G ProSe
Multi-hop UE-to-Network
Relays
23.304 0550 1 Rel-19 Updates to the 5G ProSe Multi- F 19.3.0 S2-168 S2-2504121 Ericsson, AT&T, 5G_ProS 6.3.2.6 Agreed
hop UE-to-UE Relay Discovery FirstNet, Qualcomm, e_Ph3
procedure Samsung
23.304 0551 2 Rel-19 Editorial correction on Multi-hop D 19.3.0 S2-168 S2-2504392 China Telecom 5G_ProS 6.7.5.2, Agreed
UE-to-UE Relay e_Ph3 6.7.5.2.2
23.304 0553 1 Rel-19 End UE RSC-Bounded Routing F 19.3.0 S2-168 S2-2504122 Nokia, Nokia Shanghai 5G_ProS X 5.14.3.2 Agreed
Bell e_Ph3
23.316 2142 1 Rel-19 Clarification on AF-5GC F 19.1.0 S2-168 S2-2502894 Apple, Charter UIA_AR Annex C Agreed
interaction for provisioning non- Communications C
3GPP device identifiers
23.401 3848 3 Rel-19 No Necessity to define UE in F 19.2.0 S2-168 S2-2503494 MediaTek Inc., 5GSAT_ 3.1 Agreed
S&F mode Qualcomm Incorporated Ph3-ARC
23.401 3919 3 Rel-19 Corrections for S&F Support F 19.2.0 S2-168 S2-2504244 Huawei, HiSilicon, 5GSAT_ 4.13.9.1, Agreed
and operation Nokia, Ericsson Ph3-ARC 5.3.2.1,
5.3.3.1,
5.3.3.2,
5.3.4B.2,
5.11.3.
23.401 3924 2 Rel-19 Editorial fixes D 19.2.0 S2-168 S2-2504183 Samsung 5GSAT_ X X 4.13.9.1 Agreed
Ph3-ARC
23.501 5255 1 Rel-18 Clarifications for multi-modal F 18.9.0 S2-168 S2-2504480 Huawei, HiSilicon, Nokia XRM 5.37.2, Agreed
2 services 5.37.6
23.501 5568 4 Rel-19 Clarifications for multi-modal A 19.3.0 S2-168 S2-2503897 Huawei, HiSilicon, Nokia XRM 5.37.2, Agreed
services 5.37.6
23.501 6087 3 Rel-19 PWS handling F 19.3.0 S2-168 S2-2504382 Ericsson, Qualcomm VMR_Ph 5.35A.1, Agreed
Incorporated, Huawei, 2, VMR 5.49.1.1
HiSilicon, Samsung
23.501 6127 3 Rel-19 Backhaul PDU Session F 19.3.0 S2-168 S2-2504385 Huawei, HiSilicon, VMR_Ph 5.49.1.1 Agreed
handling for MWAB Samsung 2
23.501 6168 2 Rel-19 Handling of AF Specific UE IDs C 19.3.0 S2-168 S2-2504394 Ericsson, AT&T, Nokia, EDGEAP 5.20 Agreed
Deutsche Telekom, P
KPN, NTT DOCOMO,
Apple, Samsung
23.501 6169 2 Rel-19 MWAB-gNB indication to AMF F 19.3.0 S2-168 S2-2504384 Ericsson, Huawei, VMR_Ph 5.49.1.1, Agreed
HiSilicon, Nokia 2 5.49.4
23.501 6175 3 Rel-19 Clarifications to Session F 19.3.0 S2-168 S2-2504335 Samsung UIA_AR 5.52.2, Agreed
Management aspects for C 5.52.3
handling Non-3GPP Device
Identifiers

3GPP
Report of meeting S2-168

Spec CR R Rel Subject Ca Vsn Mtg TD Source Work U M R C Aff Cl Status OAffS
t Item I E A N p
C N
C
23.501 6176 2 Rel-19 Clarification to operator F 19.3.0 S2-168 S2-2504084 Samsung UPEAS_ 5.8.2.21 Agreed
configurable UPF capabilities in Ph2
LBO roaming scenarios
23.501 6177 3 Rel-19 Clarification to UPF selection F 19.3.0 S2-168 S2-2504085 Samsung UPEAS_ 5.8.2.21, Agreed
based on specific UPF Ph2 6.3.3.3
functionalities
23.501 6179 - Rel-19 Clarification on Indirect Network F 19.3.0 S2-168 S2-2503057 China Unicom TEI19_N 5.4.4.1a Agreed
Sharing etShare
23.501 6180 3 Rel-19 Clarifications on SM signalling F 19.3.0 S2-168 S2-2504334 Apple, Charter UIA_AR 5.52.3 Agreed
including non-3GPP device Communications, Nokia C
identifiers for QoS
differentiation
23.501 6181 1 Rel-19 Removal of the MoQ Relay F 19.3.0 S2-168 S2-2503907 Nokia, China Mobile XRM_Ph 5.37.9.2 Agreed
Address in UPF Profile 2
23.501 6183 - Rel-19 Clarification on the reporting F 19.3.0 S2-168 S2-2503124 NTT DOCOMO EnergyS 5.51.2.4 Agreed
period of energy-related ys
information
23.501 6190 - Rel-19 Removal of EN about F 19.3.0 S2-168 S2-2503187 Nokia TEI19_Sl 5.15.5.2.2 Agreed
Configured NSSAI iceSel a
23.501 6192 3 Rel-19 On the termination of slice F 19.3.0 S2-168 S2-2504467 Nokia TEI19_Sl 5.15.5.2.2 Agreed
replacement iceSel a
23.501 6195 2 Rel-19 MPQUIC IP-allocation F 19.3.0 S2-168 S2-2504409 China Mobile MASSS 5.32.6.2.2 Agreed
considerations & Some
corrections
23.501 6203 2 Rel-19 Clarification on PDU Session F 19.3.0 S2-168 S2-2504260 LG Electronics UIA_AR 5.52.3 Agreed
for non-3GPP device C
23.501 6204 2 Rel-18 Fix PDU Set based Handling F 18.9.0 S2-168 S2-2504157 Samsung XRM 5.37.5.1, Agreed
description 5.37.5.2,
5.37.5.3,
6.2.3,
6.2.4,
6.2.5.0,
6.2.10
23.501 6205 2 Rel-19 Fix PDU Set based Handling A 19.3.0 S2-168 S2-2504158 Samsung XRM 5.7.2.4.1, Agreed
description 5.7.2.4.1a,
5.8.2.7,
5.37.5.1,
5.37.5.2,
5.37.5.3,
6.2.3,
6.2.4,
6.2.5.0,
6.2.10

3GPP
Report of meeting S2-168

Spec CR R Rel Subject Ca Vsn Mtg TD Source Work U M R C Aff Cl Status OAffS
t Item I E A N p
C N
C
23.501 6208 2 Rel-19 Inclusion of several Non-3GPP F 19.3.0 S2-168 S2-2504253 Nokia, InterDigital Inc., UIA_AR 5.52.3 Agreed
Device Identifiers LG Electronics, C
Samsung, ZTE, Xiaomi
23.501 6209 2 Rel-19 PDU Set based handling F 19.3.0 S2-168 S2-2504168 Samsung XRM_Ph 5.37.5.3 Agreed
without PDU Set QoS 2
parameters
23.501 6211 2 Rel-18 PWS enhancements for MBSR F 18.9.0 S2-168 S2-2504381 Huawei, HiSilicon, VMR 5.35A.1 Agreed
Ericsson
23.501 6214 1 Rel-19 UDM functional description F 19.3.0 S2-168 S2-2504138 Samsung 5G_Femt X 6.2.7 Agreed
update for CAG information o
provisioning
23.501 6216 1 Rel-19 Reference Points and SBIs for B 19.3.0 S2-168 S2-2504014 Samsung, Huawei AmbientI X X 2, 4.2.7, Agreed
Ambient IoT oT-ARC 4.2.6
23.501 6218 1 Rel-19 Terminology alignment for D 19.3.0 S2-168 S2-2504357 Huawei, HiSilicon, ETRI, MASSS 5.32.2, Agreed
steering functionality(ies) China Telecom 5.32.6.1,
5.32.6.2.2.
1, 5.32.8
23.501 6222 2 Rel-19 Correction on the granularity F 19.3.0 S2-168 S2-2504300 ZTE EnergyS 5.51.2.2.2 Agreed
description and clause ys
reference
23.501 6223 4 Rel-19 Clarification on the OAM input F 19.3.0 S2-168 S2-2504348 ZTE, Huawei EnergyS 5.51.2.2.3 Agreed
ys
23.501 6225 1 Rel-19 SMF profile enhancement F 19.3.0 S2-168 S2-2503923 China Mobile eEDGE_ 6.2.6.2 Agreed
5GC_Ph
3
23.501 6227 2 Rel-19 Clarifications for rate limitation F 19.3.0 S2-168 S2-2504418 Huawei, HiSilicon XRM_Ph 5.37.4 Agreed
exposure 2
23.501 6233 3 Rel-19 QoS Notification Control of PDU F 19.3.0 S2-168 S2-2504419 CATT, Huawei, Nokia XRM_Ph 5.7.2.4 Agreed
Set QoS with only one direction 2
23.501 6234 2 Rel-19 EIF exposure serice definition F 19.3.0 S2-168 S2-2504338 Nokia EnergyS X 5.51.2.2.1 Agreed
clarification ys
23.501 6243 1 Rel-19 Solve the editor s note about F 19.3.0 S2-168 S2-2503994 Vivo, ZTE EnergyS 5.51.2.4 Agreed
the renewable energy ys
information
23.501 6245 1 Rel-19 Update on the energy F 19.3.0 S2-168 S2-2504007 Vivo EnergyS 5.51.2.4 Agreed
consumption information ys
exposure
23.501 6249 1 Rel-19 Clarification on Local Offloading F 19.3.0 S2-168 S2-2503926 Samsung AIML_C 5.13 Agreed
Management with URSP N
23.501 6252 1 Rel-19 Clarification on 5QI for satellite F 19.3.0 S2-168 S2-2503913 CATT 5GSAT_ X 5.7.4 Agreed
access Ph3-ARC
23.501 6255 5 Rel-19 Available Bitrate Reporting F 19.3.0 S2-168 S2-2504417 InterDigital Inc. XRM_Ph 5.45.1, Agreed
when the Serving RAN Node 2 5.45.6
Changes

3GPP
Report of meeting S2-168

Spec CR R Rel Subject Ca Vsn Mtg TD Source Work U M R C Aff Cl Status OAffS
t Item I E A N p
C N
C
23.501 6256 3 Rel-19 Energy consumption F 19.3.0 S2-168 S2-2504340 Samsung, NTT EnergyS X 5.51.2.1, Agreed
information for access type DOCOMO ys 5.51.2.2.2
23.501 6257 2 Rel-19 IP version used for MPQUIC-E F 19.3.0 S2-168 S2-2504406 Ericsson, LG MASSS 5.32.6.2.2 Agreed
Electronics, CableLabs,
MediaTek Inc., Apple,
China Mobile, Nokia,
CATT, Samsung,
Deutsche Telekom
23.501 6260 2 Rel-19 Energy consumption F 19.3.0 S2-168 S2-2504303 Samsung EnergyS X 5.51.2.2.2 Agreed
information collection for new ys
PDU Session
23.501 6262 2 Rel-19 Update on the energy F 19.3.0 S2-168 S2-2504304 Vivo EnergyS X 5.51.2.2.3 Agreed
consumption information ys
collection
23.501 6264 - Rel-19 Correction of the Additional ULI F 19.3.0 S2-168 S2-2503813 Qualcomm Incorporated, VMR_Ph 5.49.4 Agreed
mapping conditions for MWAB Ericsson, Nokia, Huawei, 2
HiSilicon, LG Electronics
23.501 6266 1 Rel-19 Clarifications on NR Femto F 19.3.0 S2-168 S2-2504399 Nokia 5G_Femt 5.50.1 Agreed
node deployments o
23.501 6267 1 Rel-19 Correction of PSAP call-back F 19.3.0 S2-168 S2-2504112 Vodafone 5GS_Ph X 5.4.1.3, Agreed
terminology 1, TEI19 5.16.4.9
23.501 6270 2 Rel-19 Clarification on MWAB URSP F 19.3.0 S2-168 S2-2504379 Samsung VMR_Ph X 5.49.2.2 Agreed
processing 2
23.501 6275 1 Rel-19 Alignment with ATSSS F 19.3.0 S2-168 S2-2504359 Apple MASSS X X 5.32.2, Agreed
Capability IE 5.32.5.1,
5.32.6.1
23.501 6276 3 Rel-18 Alignment with ATSSS F 18.9.0 S2-168 S2-2504386 Apple ATSSS_ X X 5.32.2, Agreed
Capability IE Ph3 5.32.5.1,
5.32.6.1
23.502 5380 2 Rel-18 Correction for BSF invocation in F 18.9.0 S2-168 S2-2504114 Oracle, Verizon, TEI18, X 4.16.16.2 Agreed
URSP Rule Enforcement Ericsson eUEPO
Information procedure
23.502 5381 2 Rel-19 Correction for BSF invocation in A 19.3.0 S2-168 S2-2504115 Oracle, Verizon, eUEPO, X 4.16.16.2 Agreed
URSP Rule Enforcement Ericsson TEI19
Information procedure
23.502 5383 4 Rel-19 QoS differention for multiple F 19.3.0 S2-168 S2-2504336 Ericsson, AT&T, Xiaomi, UIA_AR 4.3.3.2 Agreed
Non-3GPP devices Nokia, CableLabs, ZTE C
23.502 5386 1 Rel-19 Clarifying port ranges and F 19.3.0 S2-168 S2-2504032 Ericsson UIA_AR 5.52.3 Agreed
removing EN C
23.502 5387 1 Rel-19 KI#1: Immediate Reporting F 19.3.0 S2-168 S2-2503988 Ericsson NG_RTC 5.2.6.39.2. Agreed
_Ph2 1
23.502 5390 1 Rel-19 Corrections on UPF Event F 19.3.0 S2-168 S2-2504037 Ericsson UPEAS_ 5.2.26.2.1 Agreed
Exposure Ph2

3GPP
Report of meeting S2-168

Spec CR R Rel Subject Ca Vsn Mtg TD Source Work U M R C Aff Cl Status OAffS
t Item I E A N p
C N
C
23.502 5391 1 Rel-19 Updates to Assigned Trajectory F 19.3.0 S2-168 S2-2504133 Ericsson UAS_Ph 5.2.2.3.1 Agreed
Parameters 3
23.502 5394 1 Rel-19 Updating the F 19.3.0 S2-168 S2-2504029 InterDigital Inc., LG UIA_AR 5.2.8.2.3 Agreed
Nsmf_PDUSession_Update Electronics, Samsung, C
service description to account Nokia
for non-3GPP device
connection information
23.502 5401 2 Rel-19 Clarifications to Direct F 19.3.0 S2-168 S2-2504083 Samsung UPEAS_ 4.15.4.5.6 Agreed
subscription to UPF Events in Ph2
case of session release or UPF
relocation
23.502 5402 2 Rel-19 Correction to direct subscription F 19.3.0 S2-168 S2-2504082 Samsung UPEAS_ 4.15.4.5.5 Agreed
of UPF event expsoure using Ph2
UE IP address
23.502 5403 1 Rel-19 Corrections to PDU Session F 19.3.0 S2-168 S2-2504360 Samsung MASSS 4.22.6.3 Agreed
Modification on mobility to 5GS
for Ethernet MA PDU Session
23.502 5413 2 Rel-19 Generation of AF specific UE ID F 19.3.0 S2-168 S2-2504395 Nokia, AT&T, KPN, NTT EDGEAP 4.15.10 Agreed
DOCOMO, Deutsche P
Telekom, Ericsson,
Samsung
23.502 5415 1 Rel-19 Clarification on AF requested F 19.3.0 S2-168 S2-2504370 Huawei, HiSilicon TEI19_Sl 4.15.6.9.2, Agreed
network slice replacement iceSel 4.15.6.9.3
23.502 5416 1 Rel-18 Removal of text for PWS F 18.9.0 S2-168 S2-2504106 Nokia VMR 4.10 Agreed
23.502 5418 2 Rel-19 Clarification of F 19.3.0 S2-168 S2-2504403 Nokia TEI19_Sl 4.15.6.9.3, Agreed
Nnef_AMFInfluence based iceSel 5.2.6.23.2
approach to AF requested
network slice replacement
23.502 5425 2 Rel-19 Clarification on CAG F 19.3.0 S2-168 S2-2504398 LG Electronics 5G_Femt 4.15.6.3h Agreed
Information Provisioning o
23.502 5430 3 Rel-18 N2 SM information to NG-RAN F 18.9.0 S2-168 S2-2504189 Samsung XRM 4.3.3.2 Agreed
23.502 5431 3 Rel-19 N2 SM information to NG-RAN A 19.3.0 S2-168 S2-2504190 Samsung XRM 4.3.3.2 Agreed
23.502 5433 2 Rel-19 CHF Group ID in the needed F 19.3.0 S2-168 S2-2504413 Nokia CHFSeg, 5.2.2.2.2 Agreed
contexts TEI19
23.502 5437 1 Rel-19 Removal of event subscription F 19.3.0 S2-168 S2-2504137 Samsung 5G_Femt X 4.15.6.2 Agreed
for CAG information o
provisioning
23.502 5438 - Rel-19 Adding Layer-2 Multi-hop U2N F 19.3.0 S2-168 S2-2503374 LG Electronics 5G_ProS X 5.2.3.3.1 Agreed
relaying aspects to UE e_Ph3
Subscription data
23.502 5440 3 Rel-18 Registration handling during the F 18.9.0 S2-168 S2-2504472 Huawei, Hisilicom TEI18, 4.2.2.2.2 Agreed
mobility from non-3GPP access 5GS_Ph
to 3GPP access 1

3GPP
Report of meeting S2-168

Spec CR R Rel Subject Ca Vsn Mtg TD Source Work U M R C Aff Cl Status OAffS
t Item I E A N p
C N
C
23.502 5441 3 Rel-19 Registration handling during the A 19.3.0 S2-168 S2-2504473 Huawei, Hisilicom 5GS_Ph 4.2.2.2.2 Agreed
mobility from non-3GPP access 1,
to 3GPP access TEI19_N
etShare
23.502 5442 2 Rel-19 Interaction between SMF and I- F 19.3.0 S2-168 S2-2504180 Huawei, Hisilicon eEDGE_ 4.23.6.2, Agreed
SMF 5GC_Ph 5.2.8.2.2,
3 5.2.8.2.3
23.502 5446 1 Rel-19 PWS enhancements for MWAB F 19.3.0 S2-168 S2-2504107 Samsung, Nokia, VMR_Ph X X 4.10 Agreed
and MBSR Ericsson 2
23.502 5449 1 Rel-19 Resolve the EN in the EIF F 19.3.0 S2-168 S2-2504010 ZTE EnergyS 5.2.28 Agreed
service ys
23.502 5451 2 Rel-19 Clarification on the subscription F 19.3.0 S2-168 S2-2504259 ZTE, Nokia, NEC, UIA_AR 4.16.5.1 Agreed
to UDR Xiaomi C
23.502 5456 2 Rel-19 Correction on energy F 19.3.0 S2-168 S2-2504301 CATT, ZTE, vivo, ETRI EnergyS 4.15.3.1, Agreed
consumption information ys 4.29.0,
collection and exposure 4.29.1,
4.29.2,
5.2.28.2.1
23.502 5458 3 Rel-19 Energy Consumption F 19.3.0 S2-168 S2-2504297 Nokia, CMCC, Huawei, EnergyS X 4.29.2 Agreed
information collection procedure Samsung ys
clarification
23.502 5459 3 Rel-19 SMF exposure service F 19.3.0 S2-168 S2-2504307 Nokia, Huawei, CMCC EnergyS X 5.2.8.3 Agreed
clarification for Energy ys
Consumption information
collection
23.502 5460 1 Rel-19 Update on Non-3GPP Device F 19.3.0 S2-168 S2-2504028 Xiaomi UIA_AR 4.15.6.15, Agreed
Identifier(s) Information C 5.2.5.4.2
provisioning and policy control
23.502 5461 1 Rel-19 EIF exposure service definition F 19.3.0 S2-168 S2-2504009 Nokia EnergyS X 5.2.28.2.2 Agreed
clarification ys
23.502 5464 2 Rel-19 On the report of SMF to EIF for F 19.3.0 S2-168 S2-2504305 Huawei, HiSilicon EnergyS 5.2.3.1 Agreed
user-plane energy consumption ys
calculation
23.502 5470 3 Rel-19 Energy consumption F 19.3.0 S2-168 S2-2504341 Samsung, NTT EnergyS X 4.29.2 Agreed
information for access type DOCOMO ys
23.502 5471 3 Rel-19 IP version used for MPQUIC-E F 19.3.0 S2-168 S2-2504408 Ericsson, LG MASSS 4.22.2.1 Agreed
Electronics, CATT,
MediaTek Inc., China
Mobile, Nokia, Apple,
Samsung, CableLabs,
Deutsche Telekom
23.502 5477 1 Rel-19 Clarifications on I-SMF insertion F 19.3.0 S2-168 S2-2503928 Nokia eEDGE_ X 4.23.13.1, Agreed
for PDU Session Mobility 5GC_Ph 4.23.15
3

3GPP
Report of meeting S2-168

Spec CR R Rel Subject Ca Vsn Mtg TD Source Work U M R C Aff Cl Status OAffS
t Item I E A N p
C N
C
23.502 5480 1 Rel-19 On the report of SMF to EIF for F 19.3.0 S2-168 S2-2504298 Huawei, HiSilicon, NEC EnergyS 4.29.2 Agreed
user-plane energy consumption ys
calculation
23.503 1515 4 Rel-18 Clarifications and corrections F 18.9.0 S2-168 S2-2504249 Huawei, HiSilicon XRM 6.1.3.22, Agreed
for ECN marking for L4S and 6.1.3.27.1
congestion monitoring
23.503 1516 2 Rel-19 Clarifications and corrections A 19.3.0 S2-168 S2-2504155 Huawei, HiSilicon XRM 6.1.3.22, Agreed
for ECN marking for L4S and 6.1.3.27.1
congestion monitoring
23.503 1526 1 Rel-18 Update network slice F 18.9.0 S2-168 S2-2504141 Oracle, Verizon eNS_Ph3 6.1.3.5 Agreed
replacement PCRT , TEI18
23.503 1527 1 Rel-19 Update network slice A 19.3.0 S2-168 S2-2504142 Oracle, Verizon eNS_Ph3 6.1.3.5 Agreed
replacement PCRT , TEI19
23.503 1530 - Rel-19 Adding a Reference to the F 19.3.0 S2-168 S2-2503000 InterDigital Inc., LG UIA_AR 6.1.3.31 Agreed
Home Routed Roaming PDU Electronics, Samsung, C
Session Modification Procedure Nokia
23.503 1532 3 Rel-19 Clarification on AF requested F 19.3.0 S2-168 S2-2504478 Huawei, HiSilicon TEI19_Sl 6.1.2.6.1, Agreed
network slice replacement iceSel 6.1.2.1.1
23.503 1533 2 Rel-19 Correction concerning presence F 19.3.0 S2-168 S2-2504167 Ericsson XRM_Ph 6.1.3.27.4 Agreed
of PDU Set Control information 2
without a Protocol Description
23.503 1537 1 Rel-19 Terminology alignment for D 19.3.0 S2-168 S2-2504358 Huawei, HiSilicon MASSS 6.1.3.20 Agreed
steering functionality(ies)
23.503 1541 - Rel-19 Simplification of clause 6.2.1.2 D 19.3.0 S2-168 S2-2503506 Huawei, HiSilicon 5GS_Ph 6.1.3.6, Agreed
1, TEI19 6.2.1.2
23.503 1545 1 Rel-19 Clarifications for available F 19.3.0 S2-168 S2-2503935 Huawei, HiSilicon XRM_Ph 6.1.3.27.1 Agreed
bitrate exposure 2
23.503 1547 3 Rel-19 Clarifications for rate limitation F 19.3.0 S2-168 S2-2504481 Huawei, HiSilicon XRM_Ph 6.1.3.18, Agreed
exposure 2 6.1.3.27.1
23.503 1548 3 Rel-19 Clarifications for QoS F 19.3.0 S2-168 S2-2504420 Huawei, HiSilicon, Nokia XRM_Ph 6.1.3.5, Agreed
Notification Control with 2 6.1.3.18,
direction information 6.1.3.22,
6.1.3.27.4,
6.3.1
23.503 1550 2 Rel-19 Activation of QoS monitoring for F 19.3.0 S2-168 S2-2504161 CATT, Huawei TEI19, 6.1.3.2.4, Agreed
the GBR service data flow XRM 6.1.3.21
23.503 1551 4 Rel-19 Clarificaiton on supporting F 19.3.0 S2-168 S2-2504477 Huawei, HiSilicon, UIA_AR 6.1.3.31 Agreed
multiple non-3GPP device Samsung, Deutsche C
identifiers Telekom, Nokia, LGE,
Charter
Communications, ZTE
23.503 1552 1 Rel-19 Clarification on notifying the F 19.3.0 S2-168 S2-2504146 ZTE TEI19_Sl X 6.1.2.6.1, Agreed
outcome of network slice iceSel 6.1.2.6.2
replacement to AF

3GPP
Report of meeting S2-168

Spec CR R Rel Subject Ca Vsn Mtg TD Source Work U M R C Aff Cl Status OAffS
t Item I E A N p
C N
C
23.548 0305 2 Rel-19 Interaction between SMF and I- F 19.2.0 S2-168 S2-2504179 Huawei, Hisilicon eEDGE_ 6.10.2.4 Agreed
SMF 5GC_Ph
3
23.548 0306 2 Rel-19 Correction of local offloading F 19.2.0 S2-168 S2-2504175 China Mobile eEDGE_ 6.10.2.2 Agreed
management 5GC_Ph
3
23.548 0307 3 Rel-19 UE mobility for local offloading F 19.2.0 S2-168 S2-2504181 China Mobile eEDGE_ 6.10.2.4 Agreed
management 5GC_Ph
3
23.548 0308 4 Rel-19 Clarification for Local offloading F 19.2.0 S2-168 S2-2504246 ZTE eEDGE_ 6.10.3.2 Agreed
management policy 5GC_Ph
3
23.548 0309 2 Rel-19 Clarification on handling F 19.2.0 S2-168 S2-2504177 Samsung eEDGE_ 6.10.2.3 Agreed
application not matched with 5GC_Ph
LOM policy 3
23.548 0310 1 Rel-19 Clarification on I-SMF operation F 19.2.0 S2-168 S2-2503920 Samsung eEDGE_ 6.9 Agreed
for N6 Delay Measurement 5GC_Ph
3
23.548 0311 1 Rel-19 Corrections on Local Offloading F 19.2.0 S2-168 S2-2504178 Nokia eEDGE_ X 6.10.1, Agreed
Management related indications 5GC_Ph 6.10.2.2
3
151 Entries

B.2 List of All CRs at meeting S2#168

Table B.2: List of All CRs at meeting S2#168

Spec CR R Rel Subject Ca Vsn Mtg TD Source Work Aff Cl Status OAffS
t Item p
23.203 1142 - Rel-19 Clarification on QCI for satellite F 19.1.0 S2-168 S2-2503711 CATT 5GSAT_ 6.1.7.2 Revised
access Ph3-ARC
23.203 1142 1 Rel-19 Clarification on QCI for satellite F 19.1.0 S2-168 S2-2503914 CATT 5GSAT_ 6.1.7.2 Agreed
access Ph3-ARC
23.228 1465 4 Rel-19 Update on support of DC F 19.2.0 S2-168 S2-2503581 Vivo NG_RTC AC.7.9.2 -
interworking _Ph2
23.228 1539 2 Rel-19 KI#3: Update to DC F 19.2.0 S2-168 S2-2502912 Ericsson NG_RTC AC.7.9.0, -
interworking with MTSI UE _Ph2 AC.7.9.1,
AC.7.9.2,
AC.7.9.3,
AC.7.9.4

3GPP
Report of meeting S2-168

Spec CR R Rel Subject Ca Vsn Mtg TD Source Work Aff Cl Status OAffS
t Item p
23.228 1543 2 Rel-19 Abbreviations of ADC and BDC D 19.2.0 S2-168 S2-2503579 Vivo NG_RTC 3.3 -
_Ph2
23.228 1544 2 Rel-19 Adding more event filters for F 19.2.0 S2-168 S2-2503580 Vivo NG_RTC AD.2.5.2 -
ADC media type _Ph2
23.228 1546 2 Rel-19 Modification on general D 19.2.0 S2-168 S2-2503582 Vivo NG_RTC AC.10.1 -
description for standalone IMS _Ph2
DC session
23.228 1548 2 Rel-19 Correction of detection criteria F 19.2.0 S2-168 S2-2503754 China Mobile NG_RTC AD.2.5.2 -
for event exposure _Ph2
23.228 1551 2 Rel-19 Updates on procedure and F 19.2.0 S2-168 S2-2503755 China Mobile NG_RTC AC.7.9.3, -
service of DC interworking via _Ph2 AA.2.4.3.2
DC AS
23.228 1557 2 Rel-19 Clarification on DC Application B 19.2.0 S2-168 S2-2503683 ZTE NG_RTC 3.1, 3.3, -
Server _Ph2 AC.2.2.X(n
ew)
23.228 1576 3 Rel-19 HSS handling for subscription F 19.2.0 S2-168 S2-2503701 Samsung NG_RTC AD.1, Revised
with IMS _Ph2 AD.2.3.2
23.228 1576 4 Rel-19 HSS handling for subscription F 19.2.0 S2-168 S2-2503989 Samsung NG_RTC AD.1, Noted
with IMS _Ph2 AD.2.3.2
23.228 1577 2 Rel-19 MMTel media removal F 19.2.0 S2-168 S2-2503697 Samsung NG_RTC AC.10.2.5 -
clarification _Ph2
23.228 1584 1 Rel-19 De-multiplexing ADC to avoid F 19.2.0 S2-168 S2-2503578 Vivo NG_RTC AC.7.10.1, -
multiplexing ADCs with same _Ph2 AC.7.10.3.
stream ID 1,
AC.7.10.4.
2.1
23.228 1588 1 Rel-19 Updates on HSS F 19.2.0 S2-168 S2-2503758 China Mobile NG_RTC AA.2.1.5.3 Postponed
Nhss_ImsEventExposure _Ph2 (new)
service
23.228 1598 1 Rel-19 KI#3: Updates on the ADC F 19.2.0 S2-168 S2-2503167 Samsung NG_RTC AC.7.9.3 -
Interworking via DC AS _Ph2
procedure
23.228 1600 1 Rel-19 KI#3: Updates on interworking F 19.2.0 S2-168 S2-2503169 Samsung NG_RTC AC.7.9.3, -
with MTSI UE procedures _Ph2 AC.7.9.4,
AD.2.5.2

3GPP
Report of meeting S2-168

Spec CR R Rel Subject Ca Vsn Mtg TD Source Work Aff Cl Status OAffS
t Item p
23.228 1601 - Rel-19 KI#1: Corrections to IMS F 19.2.0 S2-168 S2-2502909 Ericsson NG_RTC AA.2.1.2.1 Revised
Subscribe/Notify Framework _Ph2 ,
Architecture AA.2.1.5.1
, AA.2.2.3,
AA.2.4.5.1
,
AA.2.4.5.3
, AD.1,
AD.2.3.2,
AD.2.2.3,
AD.2.4,
AD.2.5.2,
AD.3.1,
AD.3.2,
AD.3.3
23.228 1601 1 Rel-19 KI#1: Corrections to IMS F 19.2.0 S2-168 S2-2503986 Ericsson NG_RTC AA.2.1.2.1 Revised
Subscribe/Notify Framework _Ph2 ,
Architecture AA.2.1.5.1
, AA.2.2.3,
AA.2.4.5.1
,
AD2.4.5.2,
AA.2.4.5.3
, AD.1,
AD.2.3.2,
AD.2.2.3,
AD.2.4,
AD.2.5.2,
AD.3.1,
AD.3.2,
AD.3.3
23.228 1601 2 Rel-19 KI#1: Corrections to IMS F 19.2.0 S2-168 S2-2504210 Ericsson, Nokia, ZTE, NG_RTC AA.2.1.2.1 Agreed
Subscribe/Notify Framework Huawei _Ph2 ,
Architecture AA.2.1.5.1
, AA.2.2.3,
AA.2.4.5.1
,
AD2.4.5.2,
AA.2.4.5.3
, AD.1,
AD.2.3.2,
AD.2.2.3,
AD.2.4,
AD.2.5.2,
AD.3.1,
AD.3.2,
AD.3.3

3GPP
Report of meeting S2-168

Spec CR R Rel Subject Ca Vsn Mtg TD Source Work Aff Cl Status OAffS
t Item p
23.228 1602 - Rel-19 KI#8: Updates to services and F 19.2.0 S2-168 S2-2502910 Ericsson NG_RTC AA.2.4.3.2 -
operations _Ph2 ,
AA.2.5.2.2
.
23.228 1603 - Rel-19 KI#8: Corrections to Avatar F 19.2.0 S2-168 S2-2502911 Ericsson NG_RTC AC.11.3.2. -
procedures _Ph2 1,
AC.11.3.2.
2,
AC.11.3.3
23.228 1604 - Rel-19 KI#2: Generalizing Information F 19.2.0 S2-168 S2-2502913 Ericsson NG_RTC AA.2.1.1, Revised
Retrieval _Ph2 AA.2.1.2.8
.
23.228 1604 1 Rel-19 KI#2: Generalizing Information F 19.2.0 S2-168 S2-2503990 Ericsson NG_RTC AA.2.1.1, Revised
Retrieval _Ph2 AA.2.1.2.8
.
23.228 1604 2 Rel-19 KI#2: Generalizing Information F 19.2.0 S2-168 S2-2504212 Ericsson NG_RTC AA.2.1.1, Revised
Retrieval _Ph2 AA.2.1.2.8
.
23.228 1604 3 Rel-19 KI#2: Generalizing Information F 19.2.0 S2-168 S2-2504247 Ericsson NG_RTC AA.2.1.1, Noted
Retrieval _Ph2 AA.2.1.2.8
.
23.228 1605 - Rel-19 KI#2: Corrections to DC AS F 19.2.0 S2-168 S2-2502914 Ericsson NG_RTC AG.2.1.4 -
initiated Session Update to add _Ph2
BDC to an existing IMS session
23.228 1606 - Rel-19 KI#2: Corrections to DC AS F 19.2.0 S2-168 S2-2502915 Ericsson NG_RTC AG.2.2.2 -
initiated Standalone ADC _Ph2
Session Creation
23.228 1607 - Rel-19 KI#2: Corrections to DC AS F 19.2.0 S2-168 S2-2502916 Ericsson NG_RTC AG.2.1.1, -
initiated IMS Session Update _Ph2 AG.2.1.2,
Procedures AG.2.1.3,
AG.2.2.1
23.228 1608 - Rel-19 Update to Initial Call setup and F 19.2.0 S2-168 S2-2502917 Ericsson 5GSAT_ AE.1, -
functional support for UE- Ph3-ARC AE.3.2,
Satellite-UE communication in AE.4.2,
IMS AE.5.1
23.228 1609 - Rel-19 Update to Mobility procedures F 19.2.0 S2-168 S2-2502918 Ericsson 5GSAT_ AE.5.2.1, -
for UE-Satellite-UE Ph3-ARC AE.5.2.2
communication

3GPP
Report of meeting S2-168

Spec CR R Rel Subject Ca Vsn Mtg TD Source Work Aff Cl Status OAffS
t Item p
23.228 1610 - Rel-19 KI#1: Event Status Retrieval F 19.2.0 S2-168 S2-2502920 Ericsson NG_RTC AA. 2.1.1; Noted
Procedure _Ph2 AA.
2.1.5.X
(NEW);
AA.2.4.1;
AA.2.4.5.X
(NEW);
AD.1;
AD.2.3;
AD.3.X
(NEW);
AD.3.Y
(NEW)
23.228 1611 - Rel-19 Update of target satellite ID F 19.2.0 S2-168 S2-2502928 ZTE 5GSAT_ AE.3.2, -
notification Ph3-ARC AE.3.3
23.228 1612 - Rel-17 Service restoration by IMS B 17.3.0 S2-168 S2-2503083 Jio FS_eIMS 5.3.2.2.2 Withdrawn
when the UE is unresponsive 5G
but reachable
23.228 1613 - Rel-16 Service restoration by IMS B 16.7.0 S2-168 S2-2503086 Jio Platforms Ltd (JPL) FS_eIMS 5.3.2.2.2 Withdrawn
when the UE is unresponsive 5G
but reachable
23.228 1614 - Rel-16 Service restoration by IMS B 16.7.0 S2-168 S2-2503087 Jio Platforms Ltd (JPL) eIMS5G_ 5.3.2.2.2 Withdrawn
when the UE is unresponsive SBA
but reachable
23.228 1615 - Rel-16 Service restoration by IMS B 16.7.0 S2-168 S2-2503088 Jio Platforms Ltd (JPL) eIMS5G_ 5.3.2.2.2 -
when the UE is unresponsive SBA
but reachable
23.228 1616 - Rel-19 NG_RTC_Ph2 KI#1: F 19.2.0 S2-168 S2-2503097 Nokia NG_RTC AD.3.2, Merged
Subscribe/Notify Procedure _Ph2 AD.3.3
correction
23.228 1617 - Rel-19 KI#2: Correction of procedures F 19.2.0 S2-168 S2-2503098 Nokia NG_RTC AG.2.1.1, Revised
in clause AG _Ph2 AG.2.1.2,
AG.2.1.3,
AG.2.1.4,
AG.2.2.1,
AG.2.2.2,
AG.2.3
23.228 1617 1 Rel-19 KI#2: Correction of procedures F 19.2.0 S2-168 S2-2503991 Nokia, ZTE, Huawei, NG_RTC AG.2.1.1, Revised
in clause AG HiSilicon _Ph2 AG.2.1.2,
AG.2.1.3,
AG.2.1.4,
AG.2.2.1,
AG.2.2.2,
AG.2.3

3GPP
Report of meeting S2-168

Spec CR R Rel Subject Ca Vsn Mtg TD Source Work Aff Cl Status OAffS
t Item p
23.228 1617 2 Rel-19 KI#2: Correction of procedures F 19.2.0 S2-168 S2-2504213 Nokia, ZTE, Huawei, NG_RTC AG.2.1.1, Revised
in clause AG HiSilicon _Ph2 AG.2.1.2,
AG.2.1.3,
AG.2.2.1,
AG.2.2.2,
AG2.3
23.228 1617 3 Rel-19 KI#2: Correction of procedures F 19.2.0 S2-168 S2-2504248 Nokia, ZTE, Huawei, NG_RTC AG.2.1.1, Agreed
in clause AG HiSilicon _Ph2 AG.2.1.2,
AG.2.1.3,
AG.2.2.1,
AG.2.2.2,
AG2.3
23.228 1618 - Rel-19 Clarification of the F 19.2.0 S2-168 S2-2503099 Nokia NG_RTC 2, AF.3 -
NG_RTC_Ph2 KI#4 procedure _Ph2
description
23.228 1619 - Rel-19 Clarification on DC AS URL for F 19.2.0 S2-168 S2-2503178 Samsung NG_RTC AC.11.1 -
downloading Avatar ID List _Ph2
23.228 1620 - Rel-19 Clarification on F 19.2.0 S2-168 S2-2503180 Samsung NG_RTC AA.2.1.1, -
Nhss_ImsUECM_AsInfoGet _Ph2 AA.2.1.2.8
23.228 1621 - Rel-19 MDC2 endpoint indication for F 19.2.0 S2-168 S2-2503289 Qualcomm Incorporated, NG_RTC AA.2.4.3.2 -
Avatar Represenation Ericsson _Ph2 ,
downloading AA.2.5.2.2
23.228 1622 - Rel-19 Correction on DC multiplexing F 19.2.0 S2-168 S2-2503295 Qualcomm Incorporated NG_RTC AC.7.10.2. Revised
capability negotiation _Ph2 1,
AC.2.2.5
23.228 1622 1 Rel-19 Correction on DC multiplexing F 19.2.0 S2-168 S2-2503984 Qualcomm Incorporated NG_RTC AC.7.10.2. Revised
capability negotiation _Ph2 1,
AC.2.2.5
23.228 1622 2 Rel-19 Correction on DC multiplexing F 19.2.0 S2-168 S2-2504208 Qualcomm Incorporated NG_RTC AC.7.10.2. Agreed
capability negotiation _Ph2 1,
AC.2.2.5
23.228 1623 - Rel-19 Indication of DC initiator for DC F 19.2.0 S2-168 S2-2503308 Qualcomm Incorporated NG_RTC AG.2.1.0, Merged
create/update/termination _Ph2 AG.2.1.1,
AG.2.1.2,
AG.2.1.3.
23.228 1624 - Rel-19 Clarification on F 19.2.0 S2-168 S2-2503552 Huawei, HiSilicon NG_RTC AA.2.1.5.1 Noted
Nhss_ImsEE_Subscribe _Ph2
Immediate reporting
23.228 1625 - Rel-19 Update IMS SBA description to F 19.2.0 S2-168 S2-2503553 Huawei, HiSilicon NG_RTC AA.1.1 -
align with other specifications _Ph2
23.228 1626 - Rel-19 Update IMS DC capability F 19.2.0 S2-168 S2-2503554 Huawei, HiSilicon NG_RTC AG.2.2.1 -
exposure procedure with _Ph2 and
detailed description AG.2.3
23.228 1627 - Rel-19 Correction on standalone data F 19.2.0 S2-168 S2-2503555 Huawei, HiSilicon NG_RTC AC.10.1, -
channel description _Ph2 AC.10.2.1,
AC.10.2.2,
AC.10.2.3

3GPP
Report of meeting S2-168

Spec CR R Rel Subject Ca Vsn Mtg TD Source Work Aff Cl Status OAffS
t Item p
23.228 1628 - Rel-19 Update network centric call flow F 19.2.0 S2-168 S2-2503556 Huawei, HiSilicon NG_RTC AC.11.3.3 -
for Avatar Communication _Ph2
23.228 1629 - Rel-19 Update on early media handling F 19.2.0 S2-168 S2-2503583 Vivo 5GSAT_ AE.5.3 -
in UE-Satellite-UE scenario Ph3-ARC
23.228 1630 - Rel-19 Clarification on UP path event F 19.2.0 S2-168 S2-2503652 Huawei, HiSilicon 5GSAT_ AE.5.1 -
subscription for UE-satellite-UE Ph3-ARC
communication
23.228 1631 - Rel-19 Clarification on Adding BDC F 19.2.0 S2-168 S2-2503678 ZTE NG_RTC AG.2.1.0, -
Procedure _Ph2 AG.2.1.4
23.228 1632 - Rel-19 Clarification on Establishing F 19.2.0 S2-168 S2-2503679 ZTE NG_RTC AG.2.2.1 -
IMS Session with Standalone _Ph2
BDC Procedure
23.228 1633 - Rel-19 Clarification on Establishing F 19.2.0 S2-168 S2-2503680 ZTE NG_RTC AG.2.2.2 -
IMS Session with Standalone _Ph2
A2P ADC Procedure
23.228 1634 - Rel-19 Correction on IMS Service D 19.2.0 S2-168 S2-2503681 ZTE NG_RTC AA.2.4.3.2 Revised
Definition _Ph2 ,
AA.2.4.4.2
,
AA.2.4.4.3
,
AA.2.4.5.2
,
AA.2.4.5.3
23.228 1634 1 Rel-19 Correction on IMS Service D 19.2.0 S2-168 S2-2503987 ZTE NG_RTC AA.2.4.3.2 Revised
Definition _Ph2 ,
AA.2.4.4.2
,
AA.2.4.4.3
,
AA.2.4.5.2
,
AA.2.4.5.3
23.228 1634 2 Rel-19 Correction on IMS Service F 19.2.0 S2-168 S2-2504211 ZTE NG_RTC AA.2.4.3.2 Agreed
Definition _Ph2 ,
AA.2.4.4.2
,
AA.2.4.4.3
23.228 1635 - Rel-19 Additional Information in Adding F 19.2.0 S2-168 S2-2503684 ZTE NG_RTC AG.2.1.2 Revised
P2P ADC Procedure _Ph2
23.228 1635 1 Rel-19 Additional Information in Adding F 19.2.0 S2-168 S2-2503982 ZTE NG_RTC AG.2.1.1, Revised
P2P ADC Procedure _Ph2 AG.2.1.2,
AG.2.1.3,
AG.2.1.4

3GPP
Report of meeting S2-168

Spec CR R Rel Subject Ca Vsn Mtg TD Source Work Aff Cl Status OAffS
t Item p
23.228 1635 2 Rel-19 Additional Information in Adding F 19.2.0 S2-168 S2-2504206 ZTE NG_RTC AG.2.1.0, Revised
P2P ADC Procedure _Ph2 AG.2.1.1,
AG.2.1.2,
AG.2.1.3
23.228 1635 3 Rel-19 Additional Information in Adding F 19.2.0 S2-168 S2-2504214 ZTE, Qualcomm NG_RTC AG.2.1.0, Agreed
P2P ADC Procedure Incorporated _Ph2 AG.2.1.1,
AG.2.1.2,
AG.2.1.3
23.228 1636 - Rel-19 Clarification on UE-Satellite-UE F 19.2.0 S2-168 S2-2503712 CATT 5GSAT_ AE.5.2.1, -
communication procedures Ph3-ARC AE.5.2.2
23.228 1637 - Rel-19 Clarification on PSI F 19.2.0 S2-168 S2-2503756 China Mobile NG_RTC AC.10.2.1 -
configuration on UE _Ph2
23.228 1638 - Rel-19 Clarification on usage of Avatar F 19.2.0 S2-168 S2-2503757 China Mobile NG_RTC AC.11.3.3, -
ID _Ph2 AA.2.4.3.2
,
AA.2.5.2.2
23.228 1639 - Rel-19 Adding event for session F 19.2.0 S2-168 S2-2503759 China Mobile NG_RTC AA.2.4.2.2 Revised
establishment cancellation
23.228 1639 1 Rel-18 Adding event for session F 18.9.0 S2-168 S2-2503978 China Mobile NG_RTC AA.2.4.2.2 Postponed
establishment cancellation
23.228 1640 - Rel-19 Adding event for session A 19.2.0 S2-168 S2-2503760 China Mobile NG_RTC AG.2.1.X Revised
establishment cancellation (new)
23.228 1640 1 Rel-19 Adding event for session A 19.2.0 S2-168 S2-2503979 China Mobile NG_RTC AG.2.1.X Postponed
establishment cancellation (new)
23.228 1641 - Rel-18 Correction on bootstrap DC F 18.9.0 S2-168 S2-2503761 China Mobile NG_RTC AC.7.6 Revised
removal
23.228 1641 1 Rel-18 Correction on bootstrap DC F 18.9.0 S2-168 S2-2503980 China Mobile, Nokia NG_RTC AC.7.6, Revised
removal AC.1
23.228 1641 2 Rel-18 Correction on bootstrap DC F 18.9.0 S2-168 S2-2504204 China Mobile, Nokia, NG_RTC AC.7.6, Agreed
removal Huawei, Ericsson AC.1
23.228 1642 - Rel-19 Correction on bootstrap DC A 19.2.0 S2-168 S2-2503762 China Mobile NG_RTC AC.7.6 Revised
removal
23.228 1642 1 Rel-19 Correction on bootstrap DC A 19.2.0 S2-168 S2-2503981 China Mobile, Nokia NG_RTC AC.7.6, Revised
removal AC.1
23.228 1642 2 Rel-19 Correction on bootstrap DC A 19.2.0 S2-168 S2-2504205 China Mobile, Nokia, NG_RTC AC.7.6, Agreed
removal Huawei, Ericsson AC.1
23.228 1643 - Rel-19 Correction on UE-sat-UE F 19.2.0 S2-168 S2-2503764 China Mobile 5GSAT_ AE.5.1 -
communication procedures Ph3-ARC
23.256 0192 - Rel-19 Clarification on procedure for F 19.2.0 S2-168 S2-2502937 LG Electronics TEI19, 5.16.2 Merged
instructing aerial UEs for UAS_Ph
altitude reporting 3
23.256 0193 - Rel-19 Assigned trajectory event for in- F 19.2.0 S2-168 S2-2502964 Ericsson UAS_Ph 5.12.3, Revised
flight monitoring 3 5.16.2
23.256 0193 1 Rel-19 Assigned trajectory event for in- F 19.2.0 S2-168 S2-2504132 Ericsson UAS_Ph 5.12.3 Agreed
flight monitoring 3

3GPP
Report of meeting S2-168

Spec CR R Rel Subject Ca Vsn Mtg TD Source Work Aff Cl Status OAffS
t Item p
23.256 0194 - Rel-19 Instructing a UAV to stop the C 19.2.0 S2-168 S2-2502966 Ericsson UAS_Ph 5.16.X Revised
altitude reporting 3, TEI19 (new)
23.256 0194 1 Rel-19 Instructing a UAV to stop the C 19.2.0 S2-168 S2-2504129 Ericsson, CATT UAS_Ph 5.16.X Revised
altitude reporting 3, TEI19 (new)
23.256 0194 2 Rel-19 Instructing a UAV to stop the C 19.2.0 S2-168 S2-2504375 Ericsson, CATT UAS_Ph 5.16.X Agreed
altitude reporting 3, TEI19 (new)
23.256 0195 - Rel-19 Update to F 19.2.0 S2-168 S2-2502967 Ericsson UAS_Ph - Withdrawn
Nnef_UAVFlightAssistance_Not 3
ify service operation
23.256 0196 - Rel-19 Altitude reporting update F 19.2.0 S2-168 S2-2503179 CATT UAS_Ph 4.1, -
3 4.4.1.1.3.3
23.256 0197 - Rel-19 Procedures update F 19.2.0 S2-168 S2-2503182 CATT UAS_Ph 5.12.3, -
3 5.13.2
23.256 0198 - Rel-19 Altitude reporting cancellation C 19.2.0 S2-168 S2-2503643 CATT UAS_Ph 4.4.1.1.3.1 Revised
3 ,
4.4.1.1.3.3
,
4.4.1.1.3.5
, 5.16.1,
5.16.x
23.256 0198 1 Rel-19 Altitude reporting cancellation C 19.2.0 S2-168 S2-2504130 CATT, Ericsson UAS_Ph 4.4.1.1.3.1 Revised
3 ,
4.4.1.1.3.3
,
4.4.1.1.3.5
, 5.16.1
23.256 0198 2 Rel-19 Altitude reporting cancellation C 19.2.0 S2-168 S2-2504376 CATT, Ericsson UAS_Ph 4.4.1.1.3.1 Agreed
3 ,
4.4.1.1.3.3
,
4.4.1.1.3.5
, 5.16.1
23.256 0199 - Rel-19 The indication on altitude F 19.2.0 S2-168 S2-2503673 China Mobile UAS_Ph 5.16.2,5.1 Revised
thresholds and reporting 3 6.3
periodicity for the aerial UE's
altitude reporting
23.256 0199 1 Rel-19 The indication on altitude F 19.2.0 S2-168 S2-2504128 China Mobile UAS_Ph 5.16.2,5.1 Revised
thresholds and reporting 3 6.3
periodicity for the aerial UE's
altitude reporting
23.256 0199 2 Rel-19 The indication on altitude F 19.2.0 S2-168 S2-2504377 China Mobile, LG UAS_Ph 5.16.2,5.1 Revised
thresholds and reporting Electronics 3 6.3
periodicity for the aerial UE's
altitude reporting

3GPP
Report of meeting S2-168

Spec CR R Rel Subject Ca Vsn Mtg TD Source Work Aff Cl Status OAffS
t Item p
23.256 0199 3 Rel-19 The indication on altitude F 19.2.0 S2-168 S2-2504470 China Mobile, LG UAS_Ph 5.16.2,5.1 Agreed
thresholds and reporting Electronics 3 6.3
periodicity for the aerial UE's
altitude reporting
23.273 0637 2 Rel-19 KI#1: Considering RAN load F 19.2.0 S2-168 S2-2502899 Nokia AIML_C 6.23.2 -
when collecting data to train N
model for positioning
23.273 0646 3 Rel-19 Supporting multiple LCS-UPP C 19.2.0 S2-168 S2-2502962 Ericsson 5G_eLC 4.3.5, Revised
connections per UE S_Ph3, 4.3.7,
TEI19 5.10,
6.18.0,
6.18.1,
6.18.2,
6.18.3
23.273 0646 4 Rel-19 Supporting multiple LCS-UPP C 19.2.0 S2-168 S2-2504044 Ericsson 5G_eLC 4.3.5, Revised
connections per UE S_Ph3, 4.3.7,
TEI19 5.10,
6.18.0,
6.18.1,
6.18.2,
6.18.3
23.273 0646 5 Rel-19 Supporting multiple LCS-UPP C 19.2.0 S2-168 S2-2504088 Ericsson, Huawei 5G_eLC 4.3.5, Endorsed
connections per UE S_Ph3, 4.3.7,
TEI19 5.10,
6.18.0,
6.18.1,
6.18.2,
6.18.3,
8.3.2.5
23.273 0700 - Rel-19 Removal of requirements C 19.2.0 S2-168 S2-2502932 Vivo, Xiaomi, ZTE, AIML_C 3.1, Revised
related to case 2b OPPO, Mediatek Inc., N 5.18.0,
Samsung, Nokia 5.18.2,
6.22.2
(void),
6.22.3,
6.22.4,
8.3.4.3
23.273 0700 1 Rel-19 Removal of requirements C 19.2.0 S2-168 S2-2503967 Vivo, Xiaomi, ZTE, AIML_C 3.1, Revised
related to case 2b OPPO, Mediatek Inc., N 5.18.0,
Samsung, Nokia, CATT 5.18.2,
6.22.2
(void),
6.22.3,
6.22.4,
8.3.4.3

3GPP
Report of meeting S2-168

Spec CR R Rel Subject Ca Vsn Mtg TD Source Work Aff Cl Status OAffS
t Item p
23.273 0700 2 Rel-19 Removal of requirements C 19.2.0 S2-168 S2-2504200 Vivo, Xiaomi, ZTE, AIML_C 3.1, Agreed
related to case 2b OPPO, Mediatek Inc., N 5.18.0,
Samsung, Nokia, CATT, 5.18.2,
Ericsson, Qualcomm 6.22.2
Incorporated, Huawei, (void),
HiSilicon, ERTI 6.22.3,
6.22.4,
8.3.4.3
23.273 0701 - Rel-19 Update on input data collection F 19.2.0 S2-168 S2-2502933 ETRI AIML_C 6.22.4, Noted
by NWDAF for LMF-based N 8.3.4.2
AIML positioning
23.273 0702 - Rel-19 Changes on user consent and F 19.2.0 S2-168 S2-2502947 Apple AIML_C 6.12.1, Revised
privacy for AIML-based N 5.18.0,
positioning 5.18.x
(new),
6.22.3
23.273 0702 1 Rel-19 Changes on user consent and F 19.2.0 S2-168 S2-2503965 Apple, Xiaomi AIML_C 6.12.1, Postponed
privacy for AIML-based N 5.18.0,
positioning 5.18.x
2(new),
6.22.3, 7.1
23.273 0703 - Rel-18 Solving UE shall have F 18.9.0 S2-168 S2-2502961 Ericsson 5G_eLC 4.3.5, 5.1, Revised
maximum one LCS-UPP S_Ph3 5.10,
6.18.1,
6.18.2,
6.18.3
23.273 0703 1 Rel-18 Solving UE shall have F 18.9.0 S2-168 S2-2504042 Ericsson, ZTE 5G_eLC 4.3.5, 5.1, Revised
maximum one LCS-UPP S_Ph3 5.10,
6.18.1,
6.18.2
23.273 0703 2 Rel-18 Solving UE shall have F 18.9.0 S2-168 S2-2504087 Ericsson, ZTE, CATT 5G_eLC 4.3.5, 5.1, Agreed
maximum one LCS-UPP S_Ph3 6.18.1,
6.18.2
23.273 0704 - Rel-19 Remove EN on LMF's F 19.2.0 S2-168 S2-2503030 Samsung AIML_C 6.22.3 -
consideration of RAN load N
23.273 0705 - Rel-19 ML Model provisioning by OAM F 19.2.0 S2-168 S2-2503110 NTT DOCOMO, AIML_C 2, 4.3.8, Revised
for LMF-based AI/ML Ericsson N 4.3.X
Positioning (new)
23.273 0705 1 Rel-19 ML Model provisioning by OAM F 19.2.0 S2-168 S2-2503964 NTT DOCOMO, AIML_C 2, 4.3.8, Revised
for LMF-based AI/ML Ericsson, Nokia, Huawei, N 4.3.X
Positioning HiSilicon (new)
23.273 0705 2 Rel-19 ML Model provisioning by OAM F 19.2.0 S2-168 S2-2504198 NTT DOCOMO, AIML_C 2, 4.3.8 Endorsed
for LMF-based AI/ML Ericsson, Nokia, Huawei, N
Positioning HiSilicon
23.273 0706 - Rel-18 User plane positioning update F 18.9.0 S2-168 S2-2503172 OPPO 5G_eLC 6.18.3 Noted
for LCS-UPP context S_Ph3
synchronization

3GPP
Report of meeting S2-168

Spec CR R Rel Subject Ca Vsn Mtg TD Source Work Aff Cl Status OAffS
t Item p
23.273 0707 - Rel-18 Update on single LCS-UPP F 18.9.0 S2-168 S2-2503173 OPPO 5G_eLC 6.18.1, -
connection maintenance S_Ph3 6.18.2
23.273 0708 - Rel-19 LMF checking LCS privacy F 19.2.0 S2-168 S2-2503190 Ericsson, AT&T AIML_C 5.18.0, -
profile before collecting input N 5.18.2,
data and ground truth 6.22.3
23.273 0709 - Rel-19 Resolution of Editor s Note F 19.2.0 S2-168 S2-2503191 Ericsson AIML_C 5.18.0, -
based on RAN WG1 and RAN 3 N 6.22.3
LS replies.
23.273 0710 - Rel-19 UE LCS privacy check for F 19.2.0 S2-168 S2-2503216 Intel AIML_C 6.12, Revised
ground truth data collection and N 6.22.4
input data storage for ML model
training for AI/ML positioning
23.273 0710 1 Rel-19 UE LCS privacy check for F 19.2.0 S2-168 S2-2504172 Intel AIML_C 6.12, Postponed
ground truth data collection and N 6.22.4,7.1
input data storage for ML model
training for AI/ML positioning
23.273 0711 - Rel-19 Input data storage in ADRF for F 19.2.0 S2-168 S2-2503218 Intel AIML_C 7.1, -
ML model training for AI/ML N 8.3.4.3
positioning
23.273 0712 - Rel-19 KI#1: ML Model training by F 19.2.0 S2-168 S2-2503229 Nokia AIML_C 2, 5.18.0, -
OAM for LMF models for UE N 8.3.1
positioning
23.273 0713 - Rel-19 Update of ML model retrieval F 19.2.0 S2-168 S2-2503341 Huawei, HiSilicon AIML_C 2, 4.3.8 -
from OAM N
23.273 0714 - Rel-19 Update of input data and F 19.2.0 S2-168 S2-2503342 Huawei, HiSilicon AIML_C 5.18.0, -
procedure for LMF-based AIML N 6.22.2,
positioning 6.22.3,
6.22.4,
8.3.4.2,
8.3.4.3
23.273 0715 - Rel-19 Update the procedure of data F 19.2.0 S2-168 S2-2503343 Huawei, HiSilicon AIML_C 6.22.3 -
collection from NG-RAN N
23.273 0716 - Rel-19 Corrections of LMF-based F 19.2.0 S2-168 S2-2503345 Huawei, HiSilicon AIML_C 5.18.0 -
AI/ML positioning indication N
23.273 0717 - Rel-18 Clarification and correction on F 18.9.0 S2-168 S2-2503492 Huawei, HiSilicon 5G_eLC 6.18.3, Revised
modification of UP connection S_Ph3 8.3.2.5
between UE and LMF
23.273 0717 1 Rel-18 Clarification and correction on F 18.9.0 S2-168 S2-2504043 Huawei, HiSilicon 5G_eLC 6.18.3, Revised
modification of UP connection S_Ph3 8.3.2.5
between UE and LMF
23.273 0717 2 Rel-18 Clarification and correction on F 18.9.0 S2-168 S2-2504086 Huawei, HiSilicon 5G_eLC 6.18.3, Agreed
modification of UP connection S_Ph3 8.3.2.5
between UE and LMF
23.273 0718 - Rel-19 Clarification and correction on A 19.2.0 S2-168 S2-2503493 Huawei, HiSilicon 5G_eLC 6.18.3, -
modification of UP connection S_Ph3 8.3.2.5
between UE and LMF

3GPP
Report of meeting S2-168

Spec CR R Rel Subject Ca Vsn Mtg TD Source Work Aff Cl Status OAffS
t Item p
23.273 0719 - Rel-19 Address ENs for AI positioning F 19.2.0 S2-168 S2-2503535 Vivo AIML_C 5.18.0, -
case 3b N 6.22.3.
23.273 0720 - Rel-19 Resolve ENs on input data for F 19.2.0 S2-168 S2-2503564 CATT AIML_C 2, 5.18.0, Revised
LMF based AI/ML positioning N 6.22.3,
6.22.4,
8.3.4.3
23.273 0720 1 Rel-19 Resolve ENs on input data for F 19.2.0 S2-168 S2-2503968 CATT, Ericsson, vivo AIML_C 5.18.0, Revised
LMF based AI/ML positioning N 6.22.3,
6.22.4,
8.3.4.3
23.273 0720 2 Rel-19 Resolve ENs on input data for F 19.2.0 S2-168 S2-2504201 CATT, Ericsson, vivo, AIML_C 5.18.0, Agreed
LMF based AI/ML positioning Huawei, HiSilicon N 6.22.3,
6.22.4,
8.3.4.3
23.273 0721 - Rel-19 Clarification on privacy check F 19.2.0 S2-168 S2-2503598 Xiaomi AIML_C 5.18.0, Merged
for data collection N 5.18.2,
6.22.3, 7.1
23.273 0722 - Rel-18 Solve the failure of the user F 18.9.0 S2-168 S2-2503647 CATT 5G_eLC 6.18.3 Revised
plane connection establishment S_Ph3
23.273 0722 1 Rel-18 Solve the failure of the user F 18.9.0 S2-168 S2-2504045 CATT 5G_eLC 6.18.3 Revised
plane connection establishment S_Ph3
23.273 0722 2 Rel-18 Solve the failure of the user F 18.9.0 S2-168 S2-2504089 CATT, Ericsson 5G_eLC 6.18.3 Revised
plane connection establishment S_Ph3
23.273 0722 3 Rel-18 Solve the failure of the user F 18.9.0 S2-168 S2-2504349 CATT, Ericsson 5G_eLC 6.18.3 Agreed
plane connection establishment S_Ph3
23.273 0723 - Rel-19 Solve the failure of the user A 19.2.0 S2-168 S2-2503648 CATT 5G_eLC 6.18.3 Revised
plane connection establishment S_Ph3
23.273 0723 1 Rel-19 Solve the failure of the user A 19.2.0 S2-168 S2-2504046 CATT 5G_eLC 6.18.3 Revised
plane connection establishment S_Ph3
23.273 0723 2 Rel-19 Solve the failure of the user A 19.2.0 S2-168 S2-2504090 CATT, Ericsson 5G_eLC 6.18.3 Revised
plane connection establishment S_Ph3
23.273 0723 3 Rel-19 Solve the failure of the user A 19.2.0 S2-168 S2-2504350 CATT, Ericsson 5G_eLC 6.18.3 Agreed
plane connection establishment S_Ph3
23.273 0724 - Rel-19 UE LCS privacy check for F 19.2.0 S2-168 S2-2503665 Qualcomm Incorporated AIML_C 5.18.0, -
AI/ML based positioning N 5.18.2,
6.22.3
23.273 0725 - Rel-19 Removal the AI/ML based F 19.2.0 S2-168 S2-2503674 Qualcomm Incorporated AIML_C 5.18.0, -
positioning for case 2b N 5.18.2,
6.22.2,
6.22.4,
8.3.4.2
23.273 0726 - Rel-19 Removal the EN about LMF F 19.2.0 S2-168 S2-2503693 Qualcomm Incorporated AIML_C 6.22.3 -
taking into account RAN load N
23.273 0727 - Rel-18 Correction on the Modification F 18.9.0 S2-168 S2-2503724 ZTE 5G_eLC 6.18.3 Merged
of User Plane Connection S_Ph3
between UE and LMF

3GPP
Report of meeting S2-168

Spec CR R Rel Subject Ca Vsn Mtg TD Source Work Aff Cl Status OAffS
t Item p
23.273 0728 - Rel-19 Correction on the Modification A 19.2.0 S2-168 S2-2503725 ZTE 5G_eLC 6.18.3 Merged
of User Plane Connection S_Ph3
between UE and LMF
23.273 0729 - Rel-18 Clarification on the maximum F 18.9.0 S2-168 S2-2503726 ZTE 5G_eLC 6.18.1, Merged
one LCS-UPP connection S_Ph3 6.18.2
restriction
23.273 0730 - Rel-19 Correction of the 5GC-MT-LR F 19.2.0 S2-168 S2-2503818 Qualcomm Incorporated, VMR_Ph 6.1.5 Agreed
procedure involving MWAB Nokia 2
23.288 1386 1 Rel-19 Enhancements on the input and F 19.2.0 S2-168 S2-2503410 China Mobile AIML_C 6.23.2, Revised
output of QoS and Policy N 6.23.3
Assistance Analytics
23.288 1386 2 Rel-19 Enhancements on the input and F 19.2.0 S2-168 S2-2503977 China Mobile, ETRI AIML_C 6.23.2, Revised
output of QoS and Policy N 6.23.3
Assistance Analytics
23.288 1386 3 Rel-19 Enhancements on the input and F 19.2.0 S2-168 S2-2504219 China Mobile, ETRI, AIML_C 6.23.2, Agreed
output of QoS and Policy Samsung, Huawei N 6.23.3
Assistance Analytics
23.288 1400 1 Rel-19 Correction of NF Signalling F 19.2.0 S2-168 S2-2503119 NTT DOCOMO AIML_C 6.22.2 -
Information for Signalling Storm N
Analytics
23.288 1402 - Rel-18 Clarifications on the definition of F 18.9.0 S2-168 S2-2502853 ZTE eNA_Ph 5C.1 Noted
accuracy 3
23.288 1403 - Rel-19 Clarifications on the definition of A 19.2.0 S2-168 S2-2502854 ZTE eNA_Ph 5C.1 Revised
accuracy 3
23.288 1403 1 Rel-19 Clarifications on the definition of F 19.2.0 S2-168 S2-2504125 ZTE eNA_Ph 5C.1 Agreed
accuracy 3, TEI19
23.288 1404 - Rel-18 Clarifications on the file address F 18.9.0 S2-168 S2-2502855 ZTE eNA_Ph 10.3.4 Noted
related to ADRF 3
23.288 1405 - Rel-19 Clarifications on the file address A 19.2.0 S2-168 S2-2502856 ZTE eNA_Ph 10.3.4 Revised
related to ADRF 3
23.288 1405 1 Rel-19 Clarifications on the file address F 19.2.0 S2-168 S2-2504126 ZTE eNA_Ph 10.3.4 Agreed
related to ADRF 3, TEI19
23.288 1406 - Rel-19 LMF re-selection based on AI F 19.2.0 S2-168 S2-2502858 ZTE AIML_C 4.3.12, -
capability N 6.4.0
23.288 1407 - Rel-19 Clarifications on the time F 19.2.0 S2-168 S2-2502859 ZTE AIML_C 5.2, 5.5 -
interval supporting VFL N
23.288 1408 - Rel-19 Clarifications on VFL inference F 19.2.0 S2-168 S2-2502860 ZTE AIML_C 6.2H.2.4.1 -
N
23.288 1409 - Rel-19 General maintenance of KI#1 F 19.2.0 S2-168 S2-2502861 ZTE AIML_C 7.1 -
N
23.288 1410 - Rel-19 General maintenance of KI#4 F 19.2.0 S2-168 S2-2502862 ZTE AIML_C 4.1 -
N
23.288 1411 - Rel-19 Optimization of VFL triggers F 19.2.0 S2-168 S2-2502863 ZTE, Huawei, Hisilicon, AIML_C 6.2H.2.3.1 Revised
vivo, OPPO N

3GPP
Report of meeting S2-168

Spec CR R Rel Subject Ca Vsn Mtg TD Source Work Aff Cl Status OAffS
t Item p
23.288 1411 1 Rel-19 Optimization of VFL triggers F 19.2.0 S2-168 S2-2503970 ZTE, Huawei, Hisilicon, AIML_C 6.2H.2.3.1, Revised
vivo, OPPO, Nokia, N 6.2H.2.3.2
Futurewei, Samsung,
China Mobile, Interdigital
23.288 1411 2 Rel-19 Optimization of VFL triggers F 19.2.0 S2-168 S2-2504215 ZTE, Huawei, Hisilicon, AIML_C 6.2H.2.3.1, Revised
vivo, OPPO, Nokia, N 6.2H.2.3.2
Futurewei, Samsung,
China Mobile, Interdigital
23.288 1411 3 Rel-19 Optimization of VFL triggers F 19.2.0 S2-168 S2-2504221 ZTE, Huawei, Hisilicon, AIML_C 6.2H.2.3.1, Agreed
vivo, OPPO, Nokia, N 6.2H.2.3.2
Futurewei, Samsung,
China Mobile, Interdigital
23.288 1412 - Rel-19 Output parameters clarifications F 19.2.0 S2-168 S2-2502864 ZTE AIML_C 6.23.3 -
in KI#3 N
23.288 1413 - Rel-19 VFL clients removal during VFL F 19.2.0 S2-168 S2-2502865 ZTE AIML_C 6.2H.2.3.1 -
training N
23.288 1414 - Rel-19 VFL high level description F 19.2.0 S2-168 S2-2502866 ZTE AIML_C 5.4 -
refinements N
23.288 1415 - Rel-19 Removal of requirements C 19.2.0 S2-168 S2-2502931 Vivo AIML_C 5.2, 6.2E.4 -
related to case 2b N
23.288 1416 - Rel-19 Corrections on input data for F 19.2.0 S2-168 S2-2502934 ETRI AIML_C 6.23.2 -
QoS and policy assistance N
analytics
23.288 1417 - Rel-19 Alignment of existing F 19.2.0 S2-168 S2-2503130 Huawei, HiSilicon, ZTE AIML_C 6.2D.2, Revised
mechanisms for accuracy N 6.2E.2,
generation impacted by VFL 6.2E.3.1
procedures
23.288 1417 1 Rel-19 Alignment of existing F 19.2.0 S2-168 S2-2503972 Huawei, HiSilicon, ZTE AIML_C 6.2D.2, Agreed
mechanisms for accuracy N 6.2E.2,
generation impacted by VFL 6.2E.3.1
procedures
23.288 1418 - Rel-19 Clarification on registration and F 19.2.0 S2-168 S2-2503131 Huawei, HiSilicon AIML_C 5.2, 5.5, -
discovery for VFL N 6.2H.2.1.1
23.288 1419 - Rel-19 Clarifying Signalling Storm F 19.2.0 S2-168 S2-2503135 Huawei, HiSilicon AIML_C 6.22.1, -
Analytics N 6.22.3
23.288 1420 - Rel-19 Adding SCP as data source for F 19.2.0 S2-168 S2-2503136 Huawei, HiSilicon AIML_C 6.2.2.1, -
NWDAF data collection N 6.2.2.2,
6.2.2.4,
6.2.2.5,
6.22.2

3GPP
Report of meeting S2-168

Spec CR R Rel Subject Ca Vsn Mtg TD Source Work Aff Cl Status OAffS
t Item p
23.288 1421 - Rel-19 Update triggering Case A and F 19.2.0 S2-168 S2-2503193 Ericsson, China Telecom AIML_C 6.2A.2; Revised
some corrections and Resolving N 6.2H.2.3.1;
ENs for VFL 6.2H.2.3.2;
6.2H.2.4.2;
6.2H.3;
7.5.2;
7.12.2;
11.5.1;
11.5.2;
12.6.1;
12.6.2;
11.2.1;
11.2.2;
12.2.1 and
12.2.2
23.288 1421 1 Rel-19 Update triggering Case A and F 19.2.0 S2-168 S2-2503971 Ericsson, China AIML_C 6.2A.2; Revised
some corrections and Resolving Telecom, ZTE N 6.2H.2.3.1;
ENs for VFL 6.2H.2.3.2;
6.2H.2.4.2;
6.2H.3;
new
6.2H.X,
7.5.2;
7.12.2;
11.5.1;
11.5.2;
12.6.1;
12.6.2;
11.2.1;
11.2.2;
12.2.1 and
12.2.2
23.288 1421 2 Rel-19 Update triggering Case A and F 19.2.0 S2-168 S2-2504220 Ericsson, China AIML_C 6.2A.2; Agreed
some corrections and Resolving Telecom, ZTE N 6.2H.2.3.1;
ENs for VFL 6.2H.2.3.2;
6.2H.2.4.2;
6.2H.3;
new
6.2H.X,
7.5.2;
7.12.2;
11.5.1;
11.5.2;
12.6.1;
12.6.2;
11.2.1;
11.2.2;
12.2.1 and
12.2.2

3GPP
Report of meeting S2-168

Spec CR R Rel Subject Ca Vsn Mtg TD Source Work Aff Cl Status OAffS
t Item p
23.288 1422 - Rel-19 Selection of aggregating client F 19.2.0 S2-168 S2-2503194 Ericsson AIML_C 6.2H.2.1.1; -
in VFL N 6.2H.2.1.2;
6.2H.2.3.1,
6.2H.2.3.2
and 12.4.2
23.288 1423 - Rel-19 UE LCS privacy check for F 19.2.0 S2-168 S2-2503217 Intel AIML_C 6.2E.4 -
ground truth data collection N
23.288 1424 - Rel-19 Update ADRF service F 19.2.0 S2-168 S2-2503219 Intel AIML_C 6.2B.7, -
consumer to include LMF N, 10.1
AIML_C
N
23.288 1425 - Rel-19 Parameters for vertical F 19.2.0 S2-168 S2-2503234 Nokia AIML_C 6.2H.2.4.1, Revised
federated learning inference N 7.13.2,
procedure 7.13.4,
7.13.5,
11.3.1,
11.3.2,
11.3.4,
11.3.5,
12.3.1,
12.3.2,
12.3.4,
12.3.5
23.288 1425 1 Rel-19 Parameters for vertical F 19.2.0 S2-168 S2-2503973 Nokia, Vivo, Huawei AIML_C 6.2H.2.4.1, Revised
federated learning inference N new
procedure 6.2H.2.4.x,
7.13.2,
7.13.4,
7.13.5,
11.3.1,
11.3.2,
11.3.4,
11.3.5,
12.3.1,
12.3.2,
12.3.4,
12.3.5

3GPP
Report of meeting S2-168

Spec CR R Rel Subject Ca Vsn Mtg TD Source Work Aff Cl Status OAffS
t Item p
23.288 1425 2 Rel-19 Parameters for vertical F 19.2.0 S2-168 S2-2504216 Nokia, Vivo, Huawei, AIML_C 6.2H.2.4.1, Agreed
federated learning inference Oppo, Samsung N new
procedure 6.2H.2.4.x,
7.13.2,
7.13.4,
7.13.5,
11.3.1,
11.3.2,
11.3.4,
11.3.5,
12.3.1,
12.3.2,
12.3.4,
12.3.5
23.288 1426 - Rel-19 Parameters for vertical F 19.2.0 S2-168 S2-2503235 Nokia AIML_C 6.2H.2.4.1, -
federated learning inference N 11.4.1,
procedure 11.4.2,
11.4.4,
11.4.5,
12.5.1,
12.5.2,
12.5.4,
12.5.5
23.288 1427 - Rel-19 Correcting triggers for VFL F 19.2.0 S2-168 S2-2503237 Nokia AIML_C 6.2H.2.3.1, -
training N 6.2H.2.3.2
23.288 1428 - Rel-19 Correcting procedures for F 19.2.0 S2-168 S2-2503240 Nokia AIML_C 6.2H.2.1.1, -
Exchanging intermediate results N 6.2H.2.1.2,
between VFL clients 6.2H.2.2.1,
6.2H.2.2.2,
6.2H.2.3.1,
6.2H.2.3.2,
6.2H.2.4.1,
6.2H.2.4.2
23.288 1429 - Rel-19 Updates on VFL inference F 19.2.0 S2-168 S2-2503250 Interdigital AIML_C 6.2H.2.4.1 Revised
N
23.288 1429 1 Rel-19 Updates on VFL inference F 19.2.0 S2-168 S2-2503974 Interdigital, Samsung AIML_C 6.2H.2.4.1 Revised
N
23.288 1429 2 Rel-19 Updates on VFL inference F 19.2.0 S2-168 S2-2504217 Interdigital, Samsung AIML_C 6.2H.2.4.1 Revised
N
23.288 1429 3 Rel-19 Inclusion of several Non-3GPP F 19.2.0 S2-168 S2-2504243 Nokia, InterDigital Inc., AIML_C 5.52.3 Revised
Device Identifiers LG Electronics, N
Samsung, ZTE, Xiaomi
23.288 1429 4 Rel-19 Updates on VFL inference F 19.2.0 S2-168 S2-2504476 Interdigital, Samsung AIML_C 6.2H.2.4.1 Agreed
N
23.288 1430 - Rel-19 Update on VFL training F 19.2.0 S2-168 S2-2503251 Interdigital AIML_C 6.2H.2.3.1, -
N 6.2H.2.3.2
23.288 1431 - Rel-19 Updates on VFL preparation F 19.2.0 S2-168 S2-2503252 Interdigital AIML_C 6.2H.2.2.1, -
N 6.2H.2.2.2

3GPP
Report of meeting S2-168

Spec CR R Rel Subject Ca Vsn Mtg TD Source Work Aff Cl Status OAffS
t Item p
23.288 1432 - Rel-19 AIML_CN KI#4 Resolve issues B 19.2.0 S2-168 S2-2503255 Nokia AIML_C 6.2.2.1, -
for event exposure N 6.22.2
23.288 1433 - Rel-19 Editor s Note clean up for the F 19.2.0 S2-168 S2-2503319 OPPO AIML_C 6.2H.2.2.1, Revised
VFL N 6.2H.2.2.2,
6.2H.2.3.1,
6.2H.2.3.2,
6.2H.2.4.1,
6.2H.2.4.2,
6.2H.3
23.288 1433 1 Rel-19 Editor s Note clean up for the F 19.2.0 S2-168 S2-2503969 OPPO AIML_C 6.2H.2.2.1, Revised
VFL N 6.2H.2.2.2,
6.2H.2.3.1,
6.2H.2.3.2,
6.2H.2.4.1,
6.2H.2.4.2,
6.2H.3
23.288 1433 2 Rel-19 Editor s Note clean up for the F 19.2.0 S2-168 S2-2504202 OPPO, Nokia AIML_C 6.2H.2.2.1, Agreed
VFL N 6.2H.2.2.2,
6.2H.2.3.1,
6.2H.2.3.2,
6.2H.2.4.2
23.288 1434 - Rel-19 Updates of NWDAF discovery F 19.2.0 S2-168 S2-2503344 Huawei, HiSilicon AIML_C 5.2, -
and ML model provisioning for N 6.2A.1,
LMF-based AI/ML Positioning 6.2A.2,
6.2A.3,
7.5.2,
7.5.4,
7.6.2
23.288 1435 - Rel-19 Correction on VFL correlation F 19.2.0 S2-168 S2-2503347 Huawei, HiSilicon AIML_C 6.2H.1, -
ID handling N 6.2H.2.1.2,
6.2H.2.3.2,
6.2H.2.4.2
23.288 1436 - Rel-19 Update to VFL preparation F 19.2.0 S2-168 S2-2503348 Huawei, HiSilicon AIML_C 6.2H.2.2.1, -
procedure N 6.2H.3
23.288 1437 - Rel-19 Update the inference service for F 19.2.0 S2-168 S2-2503349 Huawei, HiSilicon AIML_C 6.2H.2.4.1, -
VFL N 7.13.2,
7.13.4,
7.13.5,
11.3.2,
11.3.4,
11.3.5,
12.3.2,
12.3.4,
12.3.5
23.288 1438 - Rel-18 Correlate the Slice Load to an F 18.9.0 S2-168 S2-2503350 Verizon, Oracle, CATT TEI18, 6.3.3A Revised
AOI when location is provided eNA_Ph
2

3GPP
Report of meeting S2-168

Spec CR R Rel Subject Ca Vsn Mtg TD Source Work Aff Cl Status OAffS
t Item p
23.288 1438 1 Rel-18 Correlate the Slice Load to an F 18.9.0 S2-168 S2-2504368 Verizon, Oracle, CATT, TEI18, 6.3.3A Agreed
AOI when location is provided Ericsson eNA_Ph
2
23.288 1439 - Rel-19 Attribute Level Change F 19.2.0 S2-168 S2-2503361 Verizon, Oracle, CATT TEI19, 6.3.3A Revised
AIML_C
N
23.288 1439 1 Rel-19 Attribute Level Change F 19.2.0 S2-168 S2-2504369 Verizon, Oracle, CATT eNA_Ph 6.3.3A Agreed
2, TEI19
23.288 1440 - Rel-19 Update and Resolve ENs for F 19.2.0 S2-168 S2-2503365 LG Electronics AIML_C 6.2H.2.3.1 -
VFL Training Procedure N
23.288 1441 - Rel-19 Clarification on Aggregator F 19.2.0 S2-168 S2-2503366 LG Electronics AIML_C 6.2H.2.3.2, Merged
NWDAF Client Selection N 6.2H.2.4.2
23.288 1441 1 Rel-19 Clarification on Aggregator F 19.2.0 S2-168 S2-2503975 LG Electronics AIML_C 6.2H.2.3.2, Withdrawn
NWDAF Client Selection N 6.2H.2.4.2
23.288 1442 - Rel-19 Clarification on Signalling Storm F 19.2.0 S2-168 S2-2503368 LG Electronics AIML_C 6.22.3, -
Analytics N 6.22.4
23.288 1443 - Rel-19 Clarification on VFL Server F 19.2.0 S2-168 S2-2503536 Vivo AIML_C 5.2, -
registration & discovery N 6.2H.2.1.1,
6.2H.2.1.2.
23.288 1444 - Rel-19 Clarification on VFL inference B 19.2.0 S2-168 S2-2503537 Vivo AIML_C 6.2H.2.4, -
N 6.2H.2.4.1,
6.2H.2.4.2,
6.2H.X(ne
w).
23.288 1445 - Rel-19 Clarification on VFL training F 19.2.0 S2-168 S2-2503538 Vivo AIML_C 6.2H.2.3.1, -
N 6.2H.2.3.2.
23.288 1446 - Rel-18 Correction on analytics F 18.9.0 S2-168 S2-2503539 Vivo eNA_Ph 5A.3.2, Noted
feedback information 3 5A.4,
5C.1,
6.1.3.
23.288 1447 - Rel-19 Correction on analytics A 19.2.0 S2-168 S2-2503540 Vivo eNA_Ph 5A.3.2, Revised
feedback information 3 5A.4,
5C.1,
6.1.3.
23.288 1447 1 Rel-19 Correction on analytics F 19.2.0 S2-168 S2-2504127 Vivo eNA_Ph 5A.3.2, Agreed
feedback information 3 5A.4,
5C.1,
6.1.3.
23.288 1448 - Rel-19 Further corrections on QoS and F 19.2.0 S2-168 S2-2503565 CATT AIML_C 6.23.1, -
policy assistance analytics N 6.23.2,
6.23.3,
6.23.4
23.288 1449 - Rel-19 UE LCS privacy check for F 19.2.0 S2-168 S2-2503668 Qualcomm Incorporated AIML_C 6.2E.4 Revised
AI/ML based positioning N
23.288 1449 1 Rel-19 UE LCS privacy check for F 19.2.0 S2-168 S2-2503966 Qualcomm Incorporated AIML_C 6.2.2.2, Postponed
AI/ML based positioning N 6.2E.4

3GPP
Report of meeting S2-168

Spec CR R Rel Subject Ca Vsn Mtg TD Source Work Aff Cl Status OAffS
t Item p
23.288 1450 - Rel-19 Maintenance of VFL model F 19.2.0 S2-168 S2-2503718 Samsung AIML_C 6.2H.2.3.1, Revised
training and inference with N 6.2H.2.3.2,
client intermediate results 6.2H.2.4.2,
sharing between VFL clients 7.12.1,
7.12.2,
7.13.1,
7.13.2,
7.13.5,
12.2.2,
12.3.2,
12.3.5
23.288 1450 1 Rel-19 Maintenance of VFL model F 19.2.0 S2-168 S2-2503976 Samsung, ZTE, Nokia, AIML_C 5.2, Revised
training and inference with OPPO, LG Electronics, N 6.2H.2.1.2,
client intermediate results Ericsson 6.2H.2.2.2,
sharing between VFL clients 6.2H.2.3.1,
6.2H.2.3.2,
6.2H.2.4.2
23.288 1450 2 Rel-19 Maintenance of VFL model F 19.2.0 S2-168 S2-2504218 Samsung, ZTE, Nokia, AIML_C 5.2, Agreed
training and inference with OPPO, LG Electronics, N 6.2H.2.1.2,
client intermediate results Ericsson 6.2H.2.2.2,
sharing between VFL clients 6.2H.2.3.1,
6.2H.2.3.2,
6.2H.2.4.2
23.288 1451 - Rel-19 An optimized method for AF to B 19.2.0 S2-168 S2-2503822 CEWiT UPEAS_ 6.2.8.2.4.x Noted
obtain the DN-facing UE IP Ph2
address
23.304 0543 - Rel-19 Removing QoS EN F 19.3.0 S2-168 S2-2502885 KPN N.V. 5G_ProS 6.5.1.4 Revised
e_Ph3
23.304 0543 1 Rel-19 Removing QoS EN F 19.3.0 S2-168 S2-2504116 KPN N.V. 5G_ProS 6.5.1.4 Agreed
e_Ph3

3GPP
Report of meeting S2-168

Spec CR R Rel Subject Ca Vsn Mtg TD Source Work Aff Cl Status OAffS
t Item p
23.304 0544 - Rel-19 Editorial corrections D 19.3.0 S2-168 S2-2502886 KPN N.V. FS_5G_ 4.2.7.1A, Agreed
ProSe_P 4.3.3,
h2 4.3.4,
4.3.5,
4.3.8,
4.3.12.2,
5.1.1,
5.1.1a,
5.1.4.1a,
5.1.4.2.1a,
5.1.4.2.2a,
5.1.5.1a,
5.1.5.2.1a,
5.1.5.2.2a,
5.2.6,
5.6.3.1,
5.8.3.1,
5.8.3.2,
6.3.2.5,
6.3.2.5.1,
6.3.2.5.2,
6.3.2.5.4,
6.3.2.6.3.1
, 6.4.3.8,
6.4.3.8.1,
6.4.3.9.2,
6.4.
23.304 0545 - Rel-19 Updates to Common identifiers F 19.3.0 S2-168 S2-2502968 Ericsson, AT&T 5G_ProS 5.8.3.1 Revised
for 5G ProSe UE-to-Network e_Ph3
Relay
23.304 0545 1 Rel-19 Updates to Common identifiers F 19.3.0 S2-168 S2-2504117 Ericsson, AT&T 5G_ProS 5.8.3.1 Agreed
for 5G ProSe UE-to-Network e_Ph3
Relay
23.304 0546 - Rel-19 Introduction of Multi-hop Layer- F 19.3.0 S2-168 S2-2503015 CATT 5G_ProS 1, 3.1, Revised
2 UE-to-Network relaying e_Ph3 4.2.7.2a,
4.3.1,
4.3.3,
4.3.5,
4.3.8,
5.1.1,
5.1.1a,
5.1.4.1a

3GPP
Report of meeting S2-168

Spec CR R Rel Subject Ca Vsn Mtg TD Source Work Aff Cl Status OAffS
t Item p
23.304 0546 1 Rel-19 Introduction of Multi-hop Layer- F 19.3.0 S2-168 S2-2504123 CATT, LG Electronics 5G_ProS 1, 3.1, Agreed
2 UE-to-Network relaying e_Ph3 4.2.7.2a,
4.3.1,
4.3.3,
4.3.5,
4.3.8,
5.1.1,
5.1.1a,
5.1.4.1a
23.304 0547 - Rel-19 Policy/Parameter provisioning F 19.3.0 S2-168 S2-2503052 OPPO 5G_ProS 5.1.4.1a, Revised
to support PWS for 5G ProSe e_Ph3 5.18
multi-hop U2N Relay
23.304 0547 1 Rel-19 Policy/Parameter provisioning F 19.3.0 S2-168 S2-2504118 OPPO 5G_ProS 5.1.4.1a, Agreed
to support PWS for 5G ProSe e_Ph3 5.18
multi-hop U2N Relay
23.304 0548 - Rel-19 Clarification on Multi-hop U2N F 19.3.0 S2-168 S2-2503141 Huawei, HiSilicon 5G_ProS 6.3.2.5.3, Revised
and U2U Discovery e_Ph3 6.3.2.6.3.2
,
6.4.3.10.2
23.304 0548 1 Rel-19 Clarification on Multi-hop U2N F 19.3.0 S2-168 S2-2504119 Huawei, HiSilicon 5G_ProS 6.3.2.5.3, Revised
and U2U Discovery e_Ph3 6.3.2.6.3.2
,
6.4.3.10.2
23.304 0548 2 Rel-19 Clarification on Multi-hop U2N F 19.3.0 S2-168 S2-2504390 Huawei, HiSilicon, 5G_ProS 6.3.2.5.3, Agreed
and U2U Discovery Samsung e_Ph3 6.3.2.6.3.2
,
6.4.3.10.2
23.304 0549 - Rel-19 Clarification on Relay F 19.3.0 S2-168 S2-2503142 Huawei, HiSilicon 5G_ProS 6.4.3.8.1 Revised
reselection for 5G ProSe e_Ph3
Remote UE with 5G ProSe
Multi-hop UE-to-Network
Relays
23.304 0549 1 Rel-19 Clarification on Relay F 19.3.0 S2-168 S2-2504120 Huawei, HiSilicon, 5G_ProS 6.4.3.8.1 Revised
reselection for 5G ProSe Samsung e_Ph3
Remote UE with 5G ProSe
Multi-hop UE-to-Network
Relays
23.304 0549 2 Rel-19 Clarification on Relay F 19.3.0 S2-168 S2-2504391 Huawei, HiSilicon 5G_ProS 6.4.3.8.1 Agreed
reselection for 5G ProSe e_Ph3
Remote UE with 5G ProSe
Multi-hop UE-to-Network
Relays
23.304 0550 - Rel-19 Updates to the 5G ProSe Multi- F 19.3.0 S2-168 S2-2503203 Ericsson, AT&T, 5G_ProS 6.3.2.6 Revised
hop UE-to-UE Relay Discovery FirstNet, Qualcomm e_Ph3
procedure
23.304 0550 1 Rel-19 Updates to the 5G ProSe Multi- F 19.3.0 S2-168 S2-2504121 Ericsson, AT&T, 5G_ProS 6.3.2.6 Agreed
hop UE-to-UE Relay Discovery FirstNet, Qualcomm, e_Ph3
procedure Samsung

3GPP
Report of meeting S2-168

Spec CR R Rel Subject Ca Vsn Mtg TD Source Work Aff Cl Status OAffS
t Item p
23.304 0551 - Rel-19 Editorial correction on Multi-hop D 19.3.0 S2-168 S2-2503279 China Telecom 5G_ProS 4.2.8A, Revised
UE-to-UE Relay e_Ph3 6.7.5.2,
6.7.5.2.2
23.304 0551 1 Rel-19 Editorial correction on Multi-hop D 19.3.0 S2-168 S2-2504124 China Telecom 5G_ProS 4.2.8A, Revised
UE-to-UE Relay e_Ph3 6.7.5.2,
6.7.5.2.2
23.304 0551 2 Rel-19 Editorial correction on Multi-hop D 19.3.0 S2-168 S2-2504392 China Telecom 5G_ProS 6.7.5.2, Agreed
UE-to-UE Relay e_Ph3 6.7.5.2.2
23.304 0552 - Rel-19 End UE RSC Bounded Routing F 19.3.0 S2-168 S2-2503812 Nokia, Nokia Shanghai 5G_ProS 5.14.3.2 Withdrawn
Bell e_Ph3
23.304 0553 - Rel-19 End UE RSC-Bounded Routing F 19.3.0 S2-168 S2-2503824 Nokia, Nokia Shanghai 5G_ProS 5.14.3.2 Revised
Bell e_Ph3
23.304 0553 1 Rel-19 End UE RSC-Bounded Routing F 19.3.0 S2-168 S2-2504122 Nokia, Nokia Shanghai 5G_ProS 5.14.3.2 Agreed
Bell e_Ph3
23.316 2142 1 Rel-19 Clarification on AF-5GC F 19.1.0 S2-168 S2-2502894 Apple, Charter UIA_AR Annex C Agreed
interaction for provisioning non- Communications C
3GPP device identifiers
23.401 3848 3 Rel-19 No Necessity to define UE in F 19.2.0 S2-168 S2-2503494 MediaTek Inc., 5GSAT_ 3.1 Agreed
S&F mode Qualcomm Incorporated Ph3-ARC
23.401 3898 1 Rel-19 PSAP emergency callback F 19.2.0 S2-168 S2-2503831 Vodafone EMC1, 4.3.22 Revised
interaction with PSM SIMTC,
TEI19
23.401 3898 2 Rel-19 PSAP emergency callback F 19.2.0 S2-168 S2-2504412 Vodafone EMC1, 4.3.22 Postponed
interaction with PSM SIMTC,
TEI19
23.401 3899 - Rel-19 Refinement of UE behavior and F 19.2.0 S2-168 S2-2502879 ZTE 5GSAT_ 4.13.9.1, -
S&F wait timer handling Ph3-ARC 4.13.9.2
23.401 3900 - Rel-19 Clarify the conditions for MME F 19.2.0 S2-168 S2-2502880 ZTE 5GSAT_ 5.3.2.1, Merged
to provide S&F parameters in Ph3-ARC 5.3.3.1,
NAS procedure 5.3.3.2,
5.3.4B.2
23.401 3901 - Rel-19 Enhancement of S&F F 19.2.0 S2-168 S2-2502881 ZTE 5GSAT_ 5.3.2.1, -
Monitoring List update Ph3-ARC 5.3.3.1,
5.3.3.2,
5.3.4B.2,
5.3.4B.3,
5.3.7
23.401 3902 - Rel-19 Align the condition for UE to F 19.2.0 S2-168 S2-2502882 ZTE 5GSAT_ 5.11.3 Merged
indicate the S&F capability Ph3-ARC
23.401 3903 - Rel-19 Update to the GUTI F 19.2.0 S2-168 S2-2502883 ZTE 5GSAT_ 4.13.9.1, Noted
Reallocation procedure Ph3-ARC 5.3.7
23.401 3904 - Rel-19 TAU and Service Request F 19.2.0 S2-168 S2-2503070 Nokia 5GSAT_ 5.3.3.1, -
procedure correction for S&F Ph3-ARC 5.3.3.2,
5.3.4B.2
23.401 3905 - Rel-19 Clarification on S&F Wait Timer F 19.2.0 S2-168 S2-2503071 Nokia 5GSAT_ 4.13.9.1 Revised
Ph3-ARC

3GPP
Report of meeting S2-168

Spec CR R Rel Subject Ca Vsn Mtg TD Source Work Aff Cl Status OAffS
t Item p
23.401 3905 1 Rel-19 Clarification on S&F Wait Timer F 19.2.0 S2-168 S2-2503915 Nokia 5GSAT_ 4.13.9.1 Noted
Ph3-ARC
23.401 3906 - Rel-19 Clarifications to UE S&F F 19.2.0 S2-168 S2-2503265 Ericsson 5GSAT_ 4.13.9.1, Merged
capability and procedures that Ph3-ARC 5.3.3.2,
can include S&F Monitoring list 5.11.3
23.401 3907 - Rel-19 Clarify S1-U not supported by F 19.2.0 S2-168 S2-2503266 Ericsson 5GSAT_ 4.13.9.1, -
split MME Ph3-ARC 5.3.2.1,
5.3.3.1,
5.3.3.2
23.401 3908 - Rel-19 Clarify PDN connection F 19.2.0 S2-168 S2-2503267 Ericsson 5GSAT_ 4.13.9.2, -
handling for split MME Ph3-ARC Annex O.2
23.401 3909 - Rel-19 Clarification on usage of S&F F 19.2.0 S2-168 S2-2503275 China Telecom 5GSAT_ 4.13.9.1 Noted
Wait Timer in UE Ph3-ARC
23.401 3910 - Rel-19 Clarification on Attach reject F 19.2.0 S2-168 S2-2503276 China Telecom 5GSAT_ 5.3.2.1 Noted
Ph3-ARC
23.401 3911 - Rel-19 Transitioning between operation F 19.2.0 S2-168 S2-2503363 LG Electronics 5GSAT_ 4.13.9.2 -
in S&F mode and normal mode Ph3-ARC
23.401 3912 - Rel-19 Procedure updates for S&F F 19.2.0 S2-168 S2-2503364 LG Electronics FS_5GS 5.3.2.1, Withdrawn
operation AT_Ph3_ 5.3.3.1,
ARCH 5.3.3.2,
5.3.4B.3
23.401 3913 - Rel-19 Updates to S&F mode transition F 19.2.0 S2-168 S2-2503414 Vivo 5GSAT_ 4.13.9.2 -
Ph3-ARC
23.401 3914 - Rel-19 Procedure updates for S&F F 19.2.0 S2-168 S2-2503415 Vivo 5GSAT_ 5.3.4B.3 -
Ph3-ARC
23.401 3915 - Rel-19 Avoid congestion caused by F 19.2.0 S2-168 S2-2503495 MediaTek Inc. FS_5GS 4.13.9.1 Revised
S&F timer AT_Ph3_
ARCH
23.401 3915 1 Rel-19 Avoid congestion caused by F 19.2.0 S2-168 S2-2503662 MediaTek Inc. 5GSAT_ 4.13.9.1 -
S&F timer Ph3-ARC
23.401 3916 - Rel-19 MT data transport in CP CIoT F 19.2.0 S2-168 S2-2503533 Xiaomi 5GSAT_ 5.3.4B.3 Merged
EPS Optimisation update for Ph3-ARC
S&F operation
23.401 3917 - Rel-19 Update Support of Attach with F 19.2.0 S2-168 S2-2503654 Huawei, HiSilicon 5GSAT_ O.2 Revised
PDN connection for split MME Ph3-ARC
architecture
23.401 3917 1 Rel-19 Update Support of Attach with F 19.2.0 S2-168 S2-2503918 Huawei, HiSilicon 5GSAT_ O.2 Noted
PDN connection for split MME Ph3-ARC
architecture
23.401 3917 2 Rel-19 Update Support of Attach with F 19.2.0 S2-168 S2-2504184 Huawei, HiSilicon 5GSAT_ O.2 Withdrawn
PDN connection for split MME Ph3-ARC
architecture
23.401 3918 - Rel-19 Clarification on S&F timer in F 19.2.0 S2-168 S2-2503655 Huawei, HiSilicon 5GSAT_ 4.13.9.1 -
NAS Accept and NAS Reject Ph3-ARC
messages

3GPP
Report of meeting S2-168

Spec CR R Rel Subject Ca Vsn Mtg TD Source Work Aff Cl Status OAffS
t Item p
23.401 3919 - Rel-19 Corrections for S&F Support F 19.2.0 S2-168 S2-2503656 Huawei, HiSilicon 5GSAT_ 4.13.9.1, Revised
and operation Ph3-ARC 5.3.2.1,
5.3.3.1,
5.3.3.2,
5.3.4B.2,
5.11.3.
23.401 3919 1 Rel-19 Corrections for S&F Support F 19.2.0 S2-168 S2-2503917 Huawei, HiSilicon 5GSAT_ 4.13.9.1, Revised
and operation Ph3-ARC 5.3.2.1,
5.3.3.1,
5.3.3.2,
5.3.4B.2,
5.11.3.
23.401 3919 2 Rel-19 Corrections for S&F Support F 19.2.0 S2-168 S2-2504182 Huawei, HiSilicon, Nokia 5GSAT_ 4.13.9.1, Revised
and operation Ph3-ARC 5.3.2.1,
5.3.3.1,
5.3.3.2,
5.3.4B.2,
5.11.3.
23.401 3919 3 Rel-19 Corrections for S&F Support F 19.2.0 S2-168 S2-2504244 Huawei, HiSilicon, 5GSAT_ 4.13.9.1, Agreed
and operation Nokia, Ericsson Ph3-ARC 5.3.2.1,
5.3.3.1,
5.3.3.2,
5.3.4B.2,
5.11.3.
23.401 3920 - Rel-19 Clarification on the deletion of F 19.2.0 S2-168 S2-2503708 CATT 5GSAT_ 4.13.9.1 Noted
the previous S&F Monitoring Ph3-ARC
List
23.401 3921 - Rel-19 Procedure updates for S&F F 19.2.0 S2-168 S2-2503750 LG Electronics 5GSAT_ 5.3.2.1, -
operation Ph3-ARC 5.3.3.1,
5.3.3.2,
5.3.4B.3
23.401 3922 - Rel-19 Handling S&F wait timer. F 19.2.0 S2-168 S2-2503880 Samsung 5GSAT_ 4.13.9.1 Merged
Ph3-ARC
23.401 3923 - Rel-19 Handling S&F not allowed. F 19.2.0 S2-168 S2-2503881 Samsung 5GSAT_ 4.13.9.1, -
Ph3-ARC 5.7.1
23.401 3924 - Rel-19 Editorial fixes and handling F 19.2.0 S2-168 S2-2503886 Samsung 5GSAT_ 4.13.9.1 Revised
when S&F is not enabled by Ph3-ARC
UE.
23.401 3924 1 Rel-19 Editorial fixes D 19.2.0 S2-168 S2-2503916 Samsung 5GSAT_ 4.13.9.1 Revised
Ph3-ARC
23.401 3924 2 Rel-19 Editorial fixes D 19.2.0 S2-168 S2-2504183 Samsung 5GSAT_ 4.13.9.1 Agreed
Ph3-ARC
23.501 5255 1 Rel-18 Clarifications for multi-modal F 18.9.0 S2-168 S2-2504227 Huawei, HiSilicon, Nokia XRM 3.1, Revised
0 services 5.37.2,
5.37.6
23.501 5255 1 Rel-18 Clarifications for multi-modal F 18.9.0 S2-168 S2-2504250 Huawei, HiSilicon, Nokia XRM 5.37.2, Revised
1 services 5.37.6

3GPP
Report of meeting S2-168

Spec CR R Rel Subject Ca Vsn Mtg TD Source Work Aff Cl Status OAffS
t Item p
23.501 5255 1 Rel-18 Clarifications for multi-modal F 18.9.0 S2-168 S2-2504480 Huawei, HiSilicon, Nokia XRM 5.37.2, Agreed
2 services 5.37.6
23.501 5255 7 Rel-18 Clarifications for multi-modal F 18.9.0 S2-168 S2-2503507 Huawei, HiSilicon, Nokia XRM 3.1, Revised
services 5.37.2,
5.37.6
23.501 5255 8 Rel-18 Clarifications for multi-modal F 18.9.0 S2-168 S2-2503896 Huawei, HiSilicon, Nokia XRM 3.1, Revised
services 5.37.2,
5.37.6
23.501 5255 9 Rel-18 Clarifications for multi-modal F 18.9.0 S2-168 S2-2504156 Huawei, HiSilicon, Nokia XRM 3.1, Revised
services 5.37.2,
5.37.6
23.501 5568 3 Rel-19 Clarifications for multi-modal A 19.3.0 S2-168 S2-2503508 Huawei, HiSilicon, Nokia XRM 3.1, Revised
services 5.37.2,
5.37.6
23.501 5568 4 Rel-19 Clarifications for multi-modal A 19.3.0 S2-168 S2-2503897 Huawei, HiSilicon, Nokia XRM 5.37.2, Agreed
services 5.37.6
23.501 5676 4 Rel-19 KI#2: VFL services F 19.3.0 S2-168 S2-2503242 Nokia AIML_C 7.2.8, -
N 7.2.12,
7.2.19
23.501 5917 3 Rel-19 Clarifications and corrections on F 19.3.0 S2-168 S2-2503784 China Mobile XRM_Ph 5.37.9.1, Withdrawn
usage of MoQ for encrypted 2 5.37.9.2
media flows
23.501 5976 1 Rel-19 Support of SMF selection F 19.3.0 S2-168 S2-2503337 Huawei, HiSilicon UIA_AR 6.2.6.2, -
considering the Non-3GPP C 6.3.2,
Device Identifier 6.3.7.1
23.501 5981 1 Rel-19 KI#1: Clarfication on the I-SMF F 19.3.0 S2-168 S2-2503405 Huawei, HiSilicon, eEDGE_ 5.34.11 Noted
selected for local offloading Samsung 5GC_Ph
managment 3
23.501 5987 2 Rel-18 Handling of always-on PDU F 18.9.0 S2-168 S2-2503548 NTT DOCOMO, Nokia eNS_Ph 5.15.17, -
sessions for network slices 3 5.15.18
subject to area control
23.501 5988 2 Rel-19 Handling of always-on PDU A 19.3.0 S2-168 S2-2503550 NTT DOCOMO, Nokia eNS_Ph 5.15.17, -
sessions for network slices 3 5.15.18
subject to area restrictions
23.501 6018 2 Rel-18 Clarification on the removal of F 18.9.0 S2-168 S2-2502889 Nokia, ZTE eNS_Ph 5.15.16, Revised
S-NSSAI from the Configured 3 5.15.18.3
NSSAI
23.501 6018 3 Rel-18 Clarification on the removal of F 18.9.0 S2-168 S2-2504401 Nokia, ZTE, Verizon, eNS_Ph 5.15.16, Noted
S-NSSAI from the Configured Qualcomm 3 5.15.18.3
NSSAI
23.501 6019 2 Rel-19 Clarification on the removal of A 19.3.0 S2-168 S2-2502890 Nokia, ZTE eNS_Ph 5.15.16, Noted
S-NSSAI from the Configured 3 5.15.18.3
NSSAI
23.501 6069 2 Rel-18 Clarifications on ECN marking F 18.9.0 S2-168 S2-2502891 Apple XRM 5.37.3.1, Revised
for L4S 5.37.3.2
23.501 6069 3 Rel-18 Clarifications on ECN marking F 18.9.0 S2-168 S2-2503894 Apple XRM 5.37.3.1, Revised
for L4S 5.37.3.2

3GPP
Report of meeting S2-168

Spec CR R Rel Subject Ca Vsn Mtg TD Source Work Aff Cl Status OAffS
t Item p
23.501 6069 4 Rel-18 Clarifications on ECN marking F 18.9.0 S2-168 S2-2503992 Apple XRM 5.37.3.1 Noted
for L4S
23.501 6070 2 Rel-19 Clarifications on ECN marking A 19.3.0 S2-168 S2-2502892 Apple XRM 5.37.3.1, Revised
for L4S 5.37.3.2
23.501 6070 3 Rel-19 Clarifications on ECN marking A 19.3.0 S2-168 S2-2503895 Apple XRM 5.37.3.1, Postponed
for L4S 5.37.3.2
23.501 6072 1 Rel-19 Correction on the Support of F 19.3.0 S2-168 S2-2503096 Nokia XRM_Ph 5.37.9.2 -
MoQ 2
23.501 6084 1 Rel-17 Clarification of eDRX F 17.14.0 S2-168 S2-2502969 Ericsson, AT&T, NR_new 5.31.7.2.1 Revised
application with emergency Qualcomm Incorporated RAT-
service Core,
NR_redc
ap-Core,
5G_CIoT
, TEI17
23.501 6084 2 Rel-17 Clarification of eDRX F 17.14.0 S2-168 S2-2504099 Ericsson, AT&T, NR_new 5.31.7.2.1 Postponed
application with emergency Qualcomm Incorporated RAT-
service Core,
NR_redc
ap-Core,
5G_CIoT
, TEI17
23.501 6085 1 Rel-18 Clarification of eDRX A 18.9.0 S2-168 S2-2502970 Ericsson, AT&T, NR_new 5.31.7.2.1 -
application with emergency Qualcomm Incorporated RAT-
service Core,
NR_redc
ap-Core,
5G_CIoT
, TEI17
23.501 6086 1 Rel-19 Clarification of eDRX A 19.3.0 S2-168 S2-2502971 Ericsson, AT&T, NR_new 5.31.7.2.1 -
application with emergency Qualcomm Incorporated RAT-
service Core,
NR_redc
ap-Core,
5G_CIoT
, TEI17
23.501 6087 1 Rel-19 PWS handling with Additional F 19.3.0 S2-168 S2-2502977 Ericsson, Qualcomm VMR_Ph 5.35A.6, Revised
ULI Incorporated 2, VMR 5.49.4,
5.16.1
23.501 6087 2 Rel-19 PWS handling F 19.3.0 S2-168 S2-2504105 Ericsson, Qualcomm VMR_Ph 5.35A.6, Revised
Incorporated 2, VMR 5.49.4
23.501 6087 3 Rel-19 PWS handling F 19.3.0 S2-168 S2-2504382 Ericsson, Qualcomm VMR_Ph 5.35A.1, Agreed
Incorporated, Huawei, 2, VMR 5.49.1.1
HiSilicon, Samsung
23.501 6091 1 Rel-19 KI#3: Align the mapping of PSI F 19.3.0 S2-168 S2-2503226 China Mobile XRM_Ph 5.8.2.7 -
value to DSPC Drop 2
Precedence setting

3GPP
Report of meeting S2-168

Spec CR R Rel Subject Ca Vsn Mtg TD Source Work Aff Cl Status OAffS
t Item p
23.501 6095 1 Rel-19 KI#4: Resolve the incorrect F 19.3.0 S2-168 S2-2503228 China Mobile XRM_Ph 5.37.5.1 -
multiplex support in NOTE 2
23.501 6099 1 Rel-19 Clarification on MWAB-UE F 19.3.0 S2-168 S2-2503018 LG Electronics VMR_Ph 5.49.3.2 -
aspect 2
23.501 6104 1 Rel-16 Epoch for 5G Residence time F 16.20.0 S2-168 S2-2503720 ZTE Vertical_ 5.27.1.2.2 -
calculation LAN
23.501 6105 1 Rel-17 Epoch for 5G Residence time F 17.14.0 S2-168 S2-2503721 ZTE Vertical_ 5.27.1.2.2. -
calculation LAN 1,
5.27.1.2.2.
2
23.501 6106 1 Rel-18 Epoch for 5G Residence time F 18.9.0 S2-168 S2-2503722 ZTE Vertical_ 5.27.1.2.2. -
calculation LAN 1,
5.27.1.2.2.
2, K.1
23.501 6107 1 Rel-19 Epoch for 5G Residence time A 19.3.0 S2-168 S2-2503723 ZTE Vertical_ 5.27.1.2.2. -
calculation LAN 1,
5.27.1.2.2.
2, K.1
23.501 6108 1 Rel-19 CR for 23.501 AIML_CN SCP F 19.3.0 S2-168 S2-2503282 Vivo AIML_C 4.2.3, -
related alignment N 4.2.6,
4.2.7,
7.2.30
23.501 6127 1 Rel-19 Backhaul PDU Session F 19.3.0 S2-168 S2-2503353 Huawei, HiSilicon VMR_Ph 5.49.1.1, Revised
handling for MWAB 2 5.49.1.2
23.501 6127 2 Rel-19 Backhaul PDU Session F 19.3.0 S2-168 S2-2504103 Huawei, HiSilicon, VMR_Ph 5.49.1.1, Revised
handling for MWAB Samsung 2 5.49.1.2
23.501 6127 3 Rel-19 Backhaul PDU Session F 19.3.0 S2-168 S2-2504385 Huawei, HiSilicon, VMR_Ph 5.49.1.1 Agreed
handling for MWAB Samsung 2
23.501 6128 1 Rel-19 MWAB-UE authorization F 19.3.0 S2-168 S2-2503352 Huawei, HiSilicon VMR_Ph 5.49.3.2 -
2
23.501 6135 1 Rel-18 Clarifications and corrections F 18.9.0 S2-168 S2-2503513 Huawei, HiSilicon XRM 5.37.3.1, Revised
for ECN marking for L4S and 5.37.3.3,
congestion monitoring 5.37.4,
5.45.3
23.501 6135 2 Rel-18 Clarifications and corrections F 18.9.0 S2-168 S2-2503993 Huawei, HiSilicon XRM 5.37.3.3, Postponed
for ECN marking for L4S and 5.37.4,
congestion monitoring 5.45.3
23.501 6136 1 Rel-19 Clarifications and corrections A 19.3.0 S2-168 S2-2503514 Huawei, HiSilicon XRM 5.37.3.1, Revised
for ECN marking for L4S and 5.37.3.3,
congestion monitoring 5.37.4,
5.45.3
23.501 6136 2 Rel-19 Clarifications and corrections A 19.3.0 S2-168 S2-2504153 Huawei, HiSilicon XRM 5.37.3.1, Withdrawn
for ECN marking for L4S and 5.37.3.3,
congestion monitoring 5.37.4,
5.45.3
23.501 6153 1 Rel-18 Clarification on Configured F 18.9.0 S2-168 S2-2503664 Samsung eNS_Ph 5.15.16 Noted
NSSAI for temporary slice 3

3GPP
Report of meeting S2-168

Spec CR R Rel Subject Ca Vsn Mtg TD Source Work Aff Cl Status OAffS
t Item p
23.501 6154 1 Rel-19 Clarification on Configured A 19.3.0 S2-168 S2-2503666 Samsung eNS_Ph 5.15.16 Noted
NSSAI for temporary slice 3
23.501 6164 - Rel-19 LMF re-selection based on AI F 19.3.0 S2-168 S2-2502867 ZTE AIML_C 6.2.6.2 -
capability N
23.501 6165 - Rel-19 PCF and SMF selection for F 19.3.0 S2-168 S2-2502900 Ericsson UIA_AR 6.3.2, Revised
QoS differentiation for non- C 6.3.7.1
3GPP devices
23.501 6165 1 Rel-19 PCF and SMF selection for F 19.3.0 S2-168 S2-2504035 Ericsson, Huawei? UIA_AR 6.3.2, Postponed
QoS differentiation for non- C 6.3.7.1,
3GPP devices 6.2.6.2
23.501 6166 - Rel-19 Corrections on UPF Event F 19.3.0 S2-168 S2-2502908 Ericsson UPEAS_ - Withdrawn
Exposure Ph2
23.501 6167 - Rel-19 Support for Network initiated F 19.3.0 S2-168 S2-2502922 Ericsson TEI19_Sl 5.15.5.2.2 Revised
Slice Replacement Termination iceSel a
23.501 6167 1 Rel-19 Support for Network initiated F 19.3.0 S2-168 S2-2504148 Ericsson TEI19_Sl 5.15.5.2.2 Noted
Slice Replacement Termination iceSel a
23.501 6168 - Rel-19 Handling of AF Specific UE IDs C 19.3.0 S2-168 S2-2502953 Ericsson, AT&T, Nokia, EDGEAP 5.20 Revised
Deutsche Telekom, P
KPN, NTT DOCOMO
23.501 6168 1 Rel-19 Handling of AF Specific UE IDs C 19.3.0 S2-168 S2-2504096 Ericsson, AT&T, Nokia, EDGEAP 5.20 Revised
Deutsche Telekom, P
KPN, NTT DOCOMO,
Apple, Samsung
23.501 6168 2 Rel-19 Handling of AF Specific UE IDs C 19.3.0 S2-168 S2-2504394 Ericsson, AT&T, Nokia, EDGEAP 5.20 Agreed
Deutsche Telekom, P
KPN, NTT DOCOMO,
Apple, Samsung
23.501 6169 - Rel-19 MWAB-gNB indication to AMF F 19.3.0 S2-168 S2-2502979 Ericsson VMR_Ph 5.49.1.1 Revised
2
23.501 6169 1 Rel-19 MWAB-gNB indication to AMF F 19.3.0 S2-168 S2-2504108 Ericsson, Huawei, VMR_Ph 5.49.1.1 Revised
HiSilicon 2
23.501 6169 2 Rel-19 MWAB-gNB indication to AMF F 19.3.0 S2-168 S2-2504384 Ericsson, Huawei, VMR_Ph 5.49.1.1, Agreed
HiSilicon, Nokia 2 5.49.4
23.501 6170 - Rel-19 MWAB-gNB authorization F 19.3.0 S2-168 S2-2502980 Ericsson VMR_Ph 5.49.3.3 -
handling update 2
23.501 6171 - Rel-18 PWS handling with Additional F 18.9.0 S2-168 S2-2502981 Ericsson, Qualcomm VMR 5.35A.6, Merged
ULI Incorporated 5.16.1
23.501 6172 - Rel-19 Providing device identifier F 19.3.0 S2-168 S2-2502986 Google UIA_AR 5.52.3 -
information in PDU session C
modification request
23.501 6173 - Rel-19 23.501 Support of uplink rate B 19.3.0 S2-168 S2-2503005 Lenovo XRM_Ph 5.37.1, Revised
control for QoS flows at RAN 2 5.37.x
23.501 6173 1 Rel-19 23.501 Support of uplink rate B 19.3.0 S2-168 S2-2503932 Lenovo XRM_Ph 5.37.1, Withdrawn
control for QoS flows at RAN 2 5.37.x
23.501 6174 - Rel-19 AF specific UE ID generation C 19.3.0 S2-168 S2-2503024 Samsung EDGEAP 5.20 Merged
P

3GPP
Report of meeting S2-168

Spec CR R Rel Subject Ca Vsn Mtg TD Source Work Aff Cl Status OAffS
t Item p
23.501 6175 - Rel-19 Clarifications to Session F 19.3.0 S2-168 S2-2503031 Samsung UIA_AR 5.52.2, Revised
Management aspects for C 5.52.3
handling Non-3GPP Device
Identifiers
23.501 6175 1 Rel-19 Clarifications to Session F 19.3.0 S2-168 S2-2504033 Samsung UIA_AR 5.52.2, Revised
Management aspects for C 5.52.3
handling Non-3GPP Device
Identifiers
23.501 6175 2 Rel-19 Clarifications to Session F 19.3.0 S2-168 S2-2504258 Samsung UIA_AR 5.52.2, Revised
Management aspects for C 5.52.3
handling Non-3GPP Device
Identifiers
23.501 6175 3 Rel-19 Clarifications to Session F 19.3.0 S2-168 S2-2504335 Samsung UIA_AR 5.52.2, Agreed
Management aspects for C 5.52.3
handling Non-3GPP Device
Identifiers
23.501 6176 - Rel-19 Clarification to usage of F 19.3.0 S2-168 S2-2503032 Samsung UPEAS_ 5.8.2.21 Revised
operator configurable UPF Ph2
capabilities in LBO roaming
scenarios
23.501 6176 1 Rel-19 Clarification to operator F 19.3.0 S2-168 S2-2504041 Samsung UPEAS_ 5.8.2.21 Revised
configurable UPF capabilities in Ph2
LBO roaming scenarios
23.501 6176 2 Rel-19 Clarification to operator F 19.3.0 S2-168 S2-2504084 Samsung UPEAS_ 5.8.2.21 Agreed
configurable UPF capabilities in Ph2
LBO roaming scenarios
23.501 6177 - Rel-19 Clarification to UPF selection F 19.3.0 S2-168 S2-2503034 Samsung UPEAS_ 5.8.2.21, Revised
based on specific UPF Ph2 6.3.3.3
functionalities
23.501 6177 1 Rel-19 Clarification to UPF selection F 19.3.0 S2-168 S2-2504038 Samsung UPEAS_ 5.8.2.21, Revised
based on specific UPF Ph2 6.3.3.3
functionalities
23.501 6177 2 Rel-19 Clarification to UPF selection F 19.3.0 S2-168 S2-2504081 Samsung UPEAS_ 5.8.2.21, Revised
based on specific UPF Ph2 6.3.3.3
functionalities
23.501 6177 3 Rel-19 Clarification to UPF selection F 19.3.0 S2-168 S2-2504085 Samsung UPEAS_ 5.8.2.21, Agreed
based on specific UPF Ph2 6.3.3.3
functionalities
23.501 6178 - Rel-19 Correct Handling of IP version F 19.3.0 S2-168 S2-2503041 Samsung MASSS 5.32.6.2.2 -
when MPQUIC-E is enabled
23.501 6179 - Rel-19 Clarification on Indirect Network F 19.3.0 S2-168 S2-2503057 China Unicom TEI19_N 5.4.4.1a Agreed
Sharing etShare
23.501 6180 - Rel-19 Clarifications on SM signalling F 19.3.0 S2-168 S2-2503074 Apple UIA_AR 5.52.2, Revised
including non-3GPP device C 5.52.3
identifiers for QoS
differentiation

3GPP
Report of meeting S2-168

Spec CR R Rel Subject Ca Vsn Mtg TD Source Work Aff Cl Status OAffS
t Item p
23.501 6180 1 Rel-19 Clarifications on SM signalling F 19.3.0 S2-168 S2-2504027 Apple UIA_AR 5.52.3 Revised
including non-3GPP device C
identifiers for QoS
differentiation
23.501 6180 2 Rel-19 Clarifications on SM signalling F 19.3.0 S2-168 S2-2504257 Apple UIA_AR 5.52.3 Revised
including non-3GPP device C
identifiers for QoS
differentiation
23.501 6180 3 Rel-19 Clarifications on SM signalling F 19.3.0 S2-168 S2-2504334 Apple, Charter UIA_AR 5.52.3 Agreed
including non-3GPP device Communications, Nokia C
identifiers for QoS
differentiation
23.501 6181 - Rel-19 Removal of the MoQ Relay F 19.3.0 S2-168 S2-2503094 Nokia XRM_Ph 5.37.9.2 Revised
Address in UPF Profile 2
23.501 6181 1 Rel-19 Removal of the MoQ Relay F 19.3.0 S2-168 S2-2503907 Nokia, China Mobile XRM_Ph 5.37.9.2 Agreed
Address in UPF Profile 2
23.501 6182 - Rel-19 Correction of Energy F 19.3.0 S2-168 S2-2503122 NTT DOCOMO EnergyS T.3 (New) -
Consumption Model ys
23.501 6183 - Rel-19 Clarification on the reporting F 19.3.0 S2-168 S2-2503124 NTT DOCOMO EnergyS 5.51.2.4 Agreed
period of energy-related ys
information
23.501 6184 - Rel-19 Correction on usage of F 19.3.0 S2-168 S2-2503134 Huawei, HiSilicon AIML_C 5.21.3.3, -
signalling storm analytics for N 5.21.3.4
reliability of NF services
23.501 6185 - Rel-19 KI#1, Update to Notification F 19.3.0 S2-168 S2-2503147 Vivo, Nokia XRM_Ph 5.7.2.4.1a -
Control and Alternative QoS 2
profile with PDU Set QoS
23.501 6186 - Rel-19 Clarification of mobility clause F 19.3.0 S2-168 S2-2503168 Nokia VMR_Ph 5.49.5.3 -
2
23.501 6187 - Rel-19 Clarification of the network F 19.3.0 S2-168 S2-2503177 Nokia, China Telecom VMR_Ph 5.49.1.4 -
slicing clause 2
23.501 6188 - Rel-19 Handling of BH PDU session in F 19.3.0 S2-168 S2-2503181 Nokia VMR_Ph 5.49.1.2 -
the network 2
23.501 6189 - Rel-19 Add MWAB indication to NEF F 19.3.0 S2-168 S2-2503183 Nokia VMR_Ph 4.15.3.1 Revised
monitoring events 2
23.501 6190 - Rel-19 Removal of EN about F 19.3.0 S2-168 S2-2503187 Nokia TEI19_Sl 5.15.5.2.2 Agreed
Configured NSSAI iceSel a
23.501 6191 - Rel-19 Feature interaction resolution F 19.3.0 S2-168 S2-2503202 Nokia TEI19_Sl 5.15.5.2.2 Revised
iceSel a
23.501 6191 1 Rel-19 Feature interaction resolution F 19.3.0 S2-168 S2-2504152 Nokia TEI19_Sl 5.15.5.2.2 Revised
iceSel a
23.501 6191 2 Rel-19 Feature interaction resolution F 19.3.0 S2-168 S2-2504405 Nokia TEI19_Sl 5.15.5.2.2 Postponed
iceSel a
23.501 6192 - Rel-19 On the termination of slice F 19.3.0 S2-168 S2-2503204 Nokia TEI19_Sl 5.15.5.2.2 Revised
replacement iceSel a

3GPP
Report of meeting S2-168

Spec CR R Rel Subject Ca Vsn Mtg TD Source Work Aff Cl Status OAffS
t Item p
23.501 6192 1 Rel-19 On the termination of slice F 19.3.0 S2-168 S2-2504149 Nokia TEI19_Sl 5.15.5.2.2 Revised
replacement iceSel a
23.501 6192 2 Rel-19 On the termination of slice F 19.3.0 S2-168 S2-2504402 Nokia TEI19_Sl 5.15.5.2.2 Revised
replacement iceSel a
23.501 6192 3 Rel-19 On the termination of slice F 19.3.0 S2-168 S2-2504467 Nokia TEI19_Sl 5.15.5.2.2 Agreed
replacement iceSel a
23.501 6193 - Rel-19 Triggering of Transport Level F 19.3.0 S2-168 S2-2503208 Ericsson XRM_Ph 5.8.2.7 Revised
Marking based on PDU Set 2
Importance in I-SMF
23.501 6193 1 Rel-19 Triggering of Transport Level F 19.3.0 S2-168 S2-2503909 Ericsson XRM_Ph 5.8.2.7 Revised
Marking based on PDU Set 2
Importance in I-SMF
23.501 6193 2 Rel-19 Triggering of Transport Level F 19.3.0 S2-168 S2-2504229 Ericsson XRM_Ph 5.8.2.7 Postponed
Marking based on PDU Set 2
Importance in I-SMF
23.501 6194 - Rel-19 Indication of Rate-Adaptable C 19.3.0 S2-168 S2-2503210 Ericsson NR_XR_ 5.37.1, Postponed
QoS Flows to NG-RAN Ph3- 5.37.X
Core (new)
23.501 6195 - Rel-19 MPQUIC IP-allocation F 19.3.0 S2-168 S2-2503257 China Mobile MASSS 5.32.6.2.2 Revised
considerations & Some
corrections
23.501 6195 1 Rel-19 MPQUIC IP-allocation F 19.3.0 S2-168 S2-2504362 China Mobile MASSS 5.32.6.2.2 Revised
considerations & Some
corrections
23.501 6195 2 Rel-19 MPQUIC IP-allocation F 19.3.0 S2-168 S2-2504409 China Mobile MASSS 5.32.6.2.2 Agreed
considerations & Some
corrections
23.501 6196 - Rel-18 MPQUIC IP-allocation A 18.9.0 S2-168 S2-2503258 China Mobile MASSS 5.32.6.2.2 Noted
considerations & Some
corrections
23.501 6197 - Rel-19 Handling of MPQUIC-E with F 19.3.0 S2-168 S2-2503261 Ericsson MASSS 5.32.1 Revised
EPS interworking
23.501 6197 1 Rel-19 Handling of MPQUIC-E with F 19.3.0 S2-168 S2-2504355 Ericsson MASSS 5.32.1 Postponed
EPS interworking
23.501 6198 - Rel-19 Clarification on MPQUIC proxy F 19.3.0 S2-168 S2-2503278 China Telecom MASSS 5.32.2 Merged
23.501 6199 - Rel-19 Clarification on IP version used F 19.3.0 S2-168 S2-2503297 MediaTek Inc. MASSS 5.32.6.2.2 -
for MPQUIC-E
23.501 6200 - Rel-18 Configured NSSAI exchange F 18.9.0 S2-168 S2-2503298 LG Electronics eNS_Ph 5.15.19 Noted
between AMFs for Network 3
Slice Replacement
23.501 6201 - Rel-19 Configured NSSAI exchange A 19.3.0 S2-168 S2-2503299 LG Electronics eNS_Ph 5.15.19 Revised
between AMFs for Network 3
Slice Replacement
23.501 6201 1 Rel-19 Configured NSSAI exchange F 19.3.0 S2-168 S2-2504143 LG Electronics eNS_Ph 5.15.19 Postponed
between AMFs for Network 3
Slice Replacement

3GPP
Report of meeting S2-168

Spec CR R Rel Subject Ca Vsn Mtg TD Source Work Aff Cl Status OAffS
t Item p
23.501 6202 - Rel-19 Clarification on IP version used F 19.3.0 S2-168 S2-2503303 LG Electronics, MASSS 5.32.6.2.2 Revised
for MPQUIC-E CableLabs, Apple
23.501 6202 1 Rel-19 Clarification on IP version used F 19.3.0 S2-168 S2-2503738 LG Electronics, MASSS 5.32.6.2.2 Merged
for MPQUIC-E CableLabs, Apple
23.501 6203 - Rel-19 Clarification on PDU Session F 19.3.0 S2-168 S2-2503306 LG Electronics UIA_AR 5.52.3 Revised
for non-3GPP device C
23.501 6203 1 Rel-19 Clarification on PDU Session F 19.3.0 S2-168 S2-2504034 LG Electronics UIA_AR 5.52.3 Revised
for non-3GPP device C
23.501 6203 2 Rel-19 Clarification on PDU Session F 19.3.0 S2-168 S2-2504260 LG Electronics UIA_AR 5.52.3 Agreed
for non-3GPP device C
23.501 6204 - Rel-18 Fix PDU Set based Handling F 18.9.0 S2-168 S2-2503324 Samsung XRM 5.37.5.1, Revised
description 5.37.5.2,
5.37.5.3,
6.2.3,
6.2.4,
6.2.5.0,
6.2.10
23.501 6204 1 Rel-18 Fix PDU Set based Handling F 18.9.0 S2-168 S2-2503902 Samsung XRM 5.37.5.1, Revised
description 5.37.5.2,
5.37.5.3,
6.2.3,
6.2.4,
6.2.5.0,
6.2.10
23.501 6204 2 Rel-18 Fix PDU Set based Handling F 18.9.0 S2-168 S2-2504157 Samsung XRM 5.37.5.1, Agreed
description 5.37.5.2,
5.37.5.3,
6.2.3,
6.2.4,
6.2.5.0,
6.2.10
23.501 6205 - Rel-19 Fix PDU Set based Handling A 19.3.0 S2-168 S2-2503325 Samsung XRM 5.7.2.4.1, Revised
description 5.7.2.4.1a,
5.8.2.7,
5.37.5.1,
5.37.5.2,
5.37.5.3,
6.2.3,
6.2.4,
6.2.5.0,
6.2.10

3GPP
Report of meeting S2-168

Spec CR R Rel Subject Ca Vsn Mtg TD Source Work Aff Cl Status OAffS
t Item p
23.501 6205 1 Rel-19 Fix PDU Set based Handling A 19.3.0 S2-168 S2-2503903 Samsung XRM 5.7.2.4.1, Revised
description 5.7.2.4.1a,
5.8.2.7,
5.37.5.1,
5.37.5.2,
5.37.5.3,
6.2.3,
6.2.4,
6.2.5.0,
6.2.10
23.501 6205 2 Rel-19 Fix PDU Set based Handling A 19.3.0 S2-168 S2-2504158 Samsung XRM 5.7.2.4.1, Agreed
description 5.7.2.4.1a,
5.8.2.7,
5.37.5.1,
5.37.5.2,
5.37.5.3,
6.2.3,
6.2.4,
6.2.5.0,
6.2.10
23.501 6206 - Rel-19 Alternative QoS profile handling F 19.3.0 S2-168 S2-2503328 Samsung XRM_Ph 5.7.1.2a -
considering PDU Set QoS 2
parameters
23.501 6207 - Rel-19 Notification control on use of F 19.3.0 S2-168 S2-2503329 Samsung XRM_Ph 5.7.2.4.1 -
PDU Set QoS parameters 2
23.501 6208 - Rel-19 Inclusion of several Non-3GPP F 19.3.0 S2-168 S2-2503330 Nokia, InterDigital Inc., UIA_AR 5.52.3 Revised
Device Identifiers LG Electronics C
23.501 6208 1 Rel-19 Inclusion of several Non-3GPP F 19.3.0 S2-168 S2-2504022 Nokia, InterDigital Inc., UIA_AR 5.52.3 Revised
Device Identifiers LG Electronics, C
Samsung
23.501 6208 2 Rel-19 Inclusion of several Non-3GPP F 19.3.0 S2-168 S2-2504253 Nokia, InterDigital Inc., UIA_AR 5.52.3 Agreed
Device Identifiers LG Electronics, C
Samsung, ZTE, Xiaomi
23.501 6209 - Rel-19 PDU Set based handling F 19.3.0 S2-168 S2-2503334 Samsung XRM_Ph 5.37.5.3 Revised
without PDU Set QoS 2
parameters
23.501 6209 1 Rel-19 PDU Set based handling F 19.3.0 S2-168 S2-2503940 Samsung XRM_Ph 5.37.5.3 Revised
without PDU Set QoS 2
parameters
23.501 6209 2 Rel-19 PDU Set based handling F 19.3.0 S2-168 S2-2504168 Samsung XRM_Ph 5.37.5.3 Agreed
without PDU Set QoS 2
parameters
23.501 6210 - Rel-19 Transport level packet marking F 19.3.0 S2-168 S2-2503336 Samsung XRM_Ph 5.8.2.7 -
operation at I-SMF/I-UPF 2
23.501 6211 - Rel-18 PWS enhancements for MBSR F 18.9.0 S2-168 S2-2503356 Huawei, HiSilicon VMR 5.35A.1 Revised
23.501 6211 1 Rel-18 PWS enhancements for MBSR F 18.9.0 S2-168 S2-2504104 Huawei, HiSilicon, VMR 5.35A.1 Revised
Ericsson

3GPP
Report of meeting S2-168

Spec CR R Rel Subject Ca Vsn Mtg TD Source Work Aff Cl Status OAffS
t Item p
23.501 6211 2 Rel-18 PWS enhancements for MBSR F 18.9.0 S2-168 S2-2504381 Huawei, HiSilicon, VMR 5.35A.1 Agreed
Ericsson
23.501 6212 - Rel-19 PWS enhancements for MBSR F 19.3.0 S2-168 S2-2503357 Huawei, HiSilicon VMR_Ph 5.35A.1, Merged
and MWAB 2 5.49.1.1
23.501 6213 - Rel-19 UDM functional description F 19.3.0 S2-168 S2-2503358 SAMSUNG 5G_Femt - Withdrawn
update for CAG information o
provisioning
23.501 6214 - Rel-19 UDM functional description F 19.3.0 S2-168 S2-2503367 Samsung 5G_Femt 6.2.7 Revised
update for CAG information o
provisioning
23.501 6214 1 Rel-19 UDM functional description F 19.3.0 S2-168 S2-2504138 Samsung 5G_Femt 6.2.7 Agreed
update for CAG information o
provisioning
23.501 6215 - Rel-19 Clarification on the Local F 19.3.0 S2-168 S2-2503391 LG Electronics eEDGE_ 5.34.1, Merged
Offloading Management and 5GC_Ph 6.2.6.2
SMF Service Area 3
23.501 6216 - Rel-19 Reference Points and SBIs for F 19.3.0 S2-168 S2-2503394 Samsung AmbientI 2, 4.2.7, Revised
Ambient IoT oT-ARC 4.2.6
23.501 6216 1 Rel-19 Reference Points and SBIs for B 19.3.0 S2-168 S2-2504014 Samsung, Huawei AmbientI 2, 4.2.7, Agreed
Ambient IoT oT-ARC 4.2.6
23.501 6217 - Rel-19 TAIs configured by OAM F 19.3.0 S2-168 S2-2503416 Vivo 5GSAT_ 5.4.11.9 Revised
Ph3-ARC
23.501 6217 1 Rel-19 TAIs configured by OAM F 19.3.0 S2-168 S2-2503911 Vivo 5GSAT_ 5.4.11.9 Noted
Ph3-ARC
23.501 6218 - Rel-19 Terminology alignment for D 19.3.0 S2-168 S2-2503429 Huawei, HiSilicon MASSS 5.32.2, Revised
steering functionality(ies) 5.32.6.1,
5.32.6.2.2.
1, 5.32.8
23.501 6218 1 Rel-19 Terminology alignment for D 19.3.0 S2-168 S2-2504357 Huawei, HiSilicon, ETRI, MASSS 5.32.2, Agreed
steering functionality(ies) China Telecom 5.32.6.1,
5.32.6.2.2.
1, 5.32.8
23.501 6219 - Rel-19 Support Alternative QoS profile F 19.3.0 S2-168 S2-2503433 Nokia XRM_Ph 5.7.1.2a; Noted
with PDU Set QoS and 2 5.7.2.4.1
Notification Control with explicit
NG-RAN indication Alt-1
23.501 6219 1 Rel-19 Support Alternative QoS profile F 19.3.0 S2-168 S2-2503937 Nokia XRM_Ph 5.7.1.2a; Withdrawn
with PDU Set QoS and 2 5.7.2.4.1
Notification Control with explicit
NG-RAN indication Alt-1
23.501 6220 - Rel-19 Support Alternative QoS profile F 19.3.0 S2-168 S2-2503434 Nokia XRM_Ph 5.7.1.2a; Noted
with PDU Set QoS and 2 5.7.2.4.1
Notification Control with explicit
SMF indication Alt-2
23.501 6221 - Rel-19 Correction on PDU set based F 19.3.0 S2-168 S2-2503439 Nokia XRM_Ph 5.8.2.7 Merged
DSCP marking 2

3GPP
Report of meeting S2-168

Spec CR R Rel Subject Ca Vsn Mtg TD Source Work Aff Cl Status OAffS
t Item p
23.501 6222 - Rel-19 Correction on the granularity F 19.3.0 S2-168 S2-2503457 ZTE EnergyS 5.51.2.1, Revised
description and clause ys 5.51.2.2.2,
reference 5.51.2.2.3,
5.51.2.3
23.501 6222 1 Rel-19 Correction on the granularity F 19.3.0 S2-168 S2-2503999 ZTE EnergyS 5.51.2.1, Revised
description and clause ys 5.51.2.2.2,
reference 5.51.2.3,
5.51.2.4
23.501 6222 2 Rel-19 Correction on the granularity F 19.3.0 S2-168 S2-2504300 ZTE EnergyS 5.51.2.2.2 Agreed
description and clause ys
reference
23.501 6223 - Rel-19 Clarification on the OAM input F 19.3.0 S2-168 S2-2503459 ZTE EnergyS 5.51.2.2.3, Revised
ys 5.51.2.4
23.501 6223 1 Rel-19 Clarification on the OAM input F 19.3.0 S2-168 S2-2503995 ZTE EnergyS 5.51.2.2.3 Revised
ys
23.501 6223 2 Rel-19 Clarification on the OAM input F 19.3.0 S2-168 S2-2504302 ZTE, Huawei EnergyS 5.51.2.2.3 Revised
ys
23.501 6223 3 Rel-19 Clarification on the OAM input F 19.3.0 S2-168 S2-2504339 ZTE, Huawei EnergyS 5.51.2.2.3 Revised
ys
23.501 6223 4 Rel-19 Clarification on the OAM input F 19.3.0 S2-168 S2-2504348 ZTE, Huawei EnergyS 5.51.2.2.3 Agreed
ys
23.501 6224 - Rel-19 Clarification on the non-3gpp F 19.3.0 S2-168 S2-2503462 ZTE, Xiaomi UIA_AR 5.52.3 -
device identifier activation and C
removal
23.501 6225 - Rel-19 SMF profile enhancement F 19.3.0 S2-168 S2-2503498 China Mobile eEDGE_ 6.2.6.2 Revised
5GC_Ph
3
23.501 6225 1 Rel-19 SMF profile enhancement F 19.3.0 S2-168 S2-2503923 China Mobile eEDGE_ 6.2.6.2 Agreed
5GC_Ph
3
23.501 6226 - Rel-19 Clarifications for available F 19.3.0 S2-168 S2-2503519 Huawei, HiSilicon XRM_Ph 5.45.6 Merged
bitrate exposure 2
23.501 6227 - Rel-19 Clarifications for rate limitation F 19.3.0 S2-168 S2-2503522 Huawei, HiSilicon XRM_Ph 5.37.4 Revised
exposure 2
23.501 6227 1 Rel-19 Clarifications for rate limitation F 19.3.0 S2-168 S2-2504165 Huawei, HiSilicon XRM_Ph 5.37.4 Revised
exposure 2
23.501 6227 2 Rel-19 Clarifications for rate limitation F 19.3.0 S2-168 S2-2504418 Huawei, HiSilicon XRM_Ph 5.37.4 Agreed
exposure 2
23.501 6228 - Rel-19 Clarifications for QoS F 19.3.0 S2-168 S2-2503524 Huawei, HiSilicon XRM_Ph 5.7.1.2a, -
Notification Control with 2 5.7.2.4.1a
direction information
23.501 6229 - Rel-19 Clarifications for PDU Set QoS F 19.3.0 S2-168 S2-2503526 Huawei, HiSilicon XRM_Ph 5.8.2.7, -
information based DSCP 2 5.8.5.6
marking

3GPP
Report of meeting S2-168

Spec CR R Rel Subject Ca Vsn Mtg TD Source Work Aff Cl Status OAffS
t Item p
23.501 6230 - Rel-19 Corrections for 23.501 F 19.3.0 S2-168 S2-2503545 Lenovo XRM_Ph 5.8.2.7 -
Transport Level Marking on 2
N3/N9
23.501 6231 - Rel-18 Handling of always-on PDU F 18.9.0 S2-168 S2-2503559 Nokia, NTT DOCOMO eNS_Ph 5.15.17, -
sessions for network slices 3 5.15.18
subject to area control- option B
23.501 6232 - Rel-19 Handling of always-on PDU A 19.3.0 S2-168 S2-2503573 Nokia, NTT DOCOMO eNS_Ph 5.15.17, -
sessions for network slices 3 5.15.18
subject to area control- option B
23.501 6233 - Rel-19 QoS Notification Control of PDU F 19.3.0 S2-168 S2-2503589 CATT XRM_Ph 5.7.2.4 Revised
Set QoS with only one direction 2
23.501 6233 1 Rel-19 QoS Notification Control of PDU F 19.3.0 S2-168 S2-2503941 CATT XRM_Ph 5.7.2.4 Revised
Set QoS with only one direction 2
23.501 6233 2 Rel-19 QoS Notification Control of PDU F 19.3.0 S2-168 S2-2504170 CATT, Huawei, Nokia XRM_Ph 5.7.2.4 Revised
Set QoS with only one direction 2
23.501 6233 3 Rel-19 QoS Notification Control of PDU F 19.3.0 S2-168 S2-2504419 CATT, Huawei, Nokia XRM_Ph 5.7.2.4 Agreed
Set QoS with only one direction 2
23.501 6234 - Rel-19 EIF exposure serice definition F 19.3.0 S2-168 S2-2503595 Nokia EnergyS 5.51.2.2.1 Revised
clarification ys
23.501 6234 1 Rel-19 EIF exposure serice definition F 19.3.0 S2-168 S2-2504008 Nokia EnergyS 5.51.2.2.1 Revised
clarification ys
23.501 6234 2 Rel-19 EIF exposure serice definition F 19.3.0 S2-168 S2-2504338 Nokia EnergyS 5.51.2.2.1 Agreed
clarification ys
23.501 6235 - Rel-19 Update definition of non-3GPP F 19.3.0 S2-168 S2-2503597 Xiaomi UIA_AR 5.52.3 Merged
device connection information C
23.501 6236 - Rel-19 Clarificaiton on supporting F 19.3.0 S2-168 S2-2503605 Huawei, HiSilicon UIA_AR 5.52.3 -
multiple non-3GPP device C
identifiers
23.501 6237 - Rel-18 Clarification on always-on PDU F 18.9.0 S2-168 S2-2503615 ZTE eNS_Ph 5.6.13,5.1 Postponed
Session 3 5.17,5.15.
18.2
23.501 6237 1 Rel-18 Clarification on always-on PDU F 18.9.0 S2-168 S2-2504144 ZTE eNS_Ph 5.6.13,5.1 Withdrawn
Session 3 5.17,5.15.
18.2
23.501 6238 - Rel-19 Clarification on always-on PDU A 19.3.0 S2-168 S2-2503616 ZTE eNS_Ph 5.6.13,5.1 Postponed
Session 3 5.17,5.15.
18.2
23.501 6238 1 Rel-19 Clarification on always-on PDU A 19.3.0 S2-168 S2-2504145 ZTE eNS_Ph 5.6.13,5.1 Withdrawn
Session 3 5.17,5.15.
18.2
23.501 6239 - Rel-19 Report of SMF to EIF for user- F 19.3.0 S2-168 S2-2503628 Huawei, HiSilicon EnergyS 5.51.2.2.2 Merged
plane energy consumption ys
calculation
23.501 6240 - Rel-19 On the report of SMF to EIF for F 19.3.0 S2-168 S2-2503629 Huawei, HiSilicon EnergyS 4.29.2 Noted
user-plane energy consumption ys
calculation

3GPP
Report of meeting S2-168

Spec CR R Rel Subject Ca Vsn Mtg TD Source Work Aff Cl Status OAffS
t Item p
23.501 6241 - Rel-19 Update on EC collection upon F 19.3.0 S2-168 S2-2503630 Huawei, HiSilicon EnergyS 5.51.2.2.2 Merged
PDU Session management ys
23.501 6242 - Rel-19 Clarification on the F 19.3.0 S2-168 S2-2503632 Huawei, HiSilicon EnergyS 5.51.2.2.2 Revised
EventExposure service ys
operation of SMF
23.501 6242 1 Rel-19 Clarification on the F 19.3.0 S2-168 S2-2503998 Huawei, HiSilicon EnergyS 5.51.2.2.2 Revised
EventExposure service ys
operation of SMF
23.501 6242 2 Rel-19 Clarification on the F 19.3.0 S2-168 S2-2504299 Huawei, HiSilicon EnergyS 5.51.2.2.2 Postponed
EventExposure service ys
operation of SMF
23.501 6243 - Rel-19 Solve the editor s note about F 19.3.0 S2-168 S2-2503639 Vivo EnergyS 5.51.2.4 Revised
the renewable energy ys
information
23.501 6243 1 Rel-19 Solve the editor s note about F 19.3.0 S2-168 S2-2503994 Vivo, ZTE EnergyS 5.51.2.4 Agreed
the renewable energy ys
information
23.501 6244 - Rel-19 Additional ULI Update F 19.3.0 S2-168 S2-2503645 CATT VMR_Ph 5.49.4 Merged
2
23.501 6245 - Rel-19 Update on the energy F 19.3.0 S2-168 S2-2503651 Vivo EnergyS 5.51.2.4 Revised
consumption information ys
exposure
23.501 6245 1 Rel-19 Update on the energy F 19.3.0 S2-168 S2-2504007 Vivo EnergyS 5.51.2.4 Agreed
consumption information ys
exposure
23.501 6246 - Rel-19 Clarification and correction on F 19.3.0 S2-168 S2-2503653 Huawei, HiSilicon 5GSAT_ 5.4.14.3 -
UP path event report for UE- Ph3-ARC
satellite-UE communication
23.501 6247 - Rel-19 Multi-RAN-vendor support for F 19.3.0 S2-168 S2-2503667 Vodafone NR_LPW 5.4.4.3 Postponed
paging of LP-WUS UEs US
23.501 6248 - Rel-19 Addressing EN for AF F 19.3.0 S2-168 S2-2503694 Samsung, LG TEI19_Sl 5.15.5.2.2 Noted
requested slice selection Electronics iceSel a
23.501 6249 - Rel-19 23.501 CR6249: Clarification on F 19.3.0 S2-168 S2-2503698 Samsung AIML_C 5.13 Revised
Local Offloading Management N
with URSP
23.501 6249 1 Rel-19 Clarification on Local Offloading F 19.3.0 S2-168 S2-2503926 Samsung AIML_C 5.13 Agreed
Management with URSP N
23.501 6250 - Rel-19 Configuration of TAI list for F 19.3.0 S2-168 S2-2503707 CATT 5GSAT_ 5.4.11.9 -
regenerative satellite payload Ph3-ARC
23.501 6251 - Rel-19 Clarification on UE-SAT-UE F 19.3.0 S2-168 S2-2503709 CATT 5GSAT_ 5.4.14.3 -
communication when serving Ph3-ARC
satellite changes
23.501 6252 - Rel-19 Clarification on 5QI for satellite F 19.3.0 S2-168 S2-2503710 CATT 5GSAT_ 5.7.4 Revised
access Ph3-ARC
23.501 6252 1 Rel-19 Clarification on 5QI for satellite F 19.3.0 S2-168 S2-2503913 CATT 5GSAT_ 5.7.4 Agreed
access Ph3-ARC

3GPP
Report of meeting S2-168

Spec CR R Rel Subject Ca Vsn Mtg TD Source Work Aff Cl Status OAffS
t Item p
23.501 6253 - Rel-19 Radio capability assignment in C 19.3.0 S2-168 S2-2503729 NEC TEI19 5.4.4.1a Noted
case of equivalent PLMNs. and 6.3.15
23.501 6254 - Rel-19 EIF discvoery and selection F 19.3.0 S2-168 S2-2503731 Samsung EnergyS 6.3.27 -
ys
23.501 6255 - Rel-19 Available Bitrate Reporting F 19.3.0 S2-168 S2-2503732 InterDigital Inc. XRM_Ph 5.45.6 Revised
when the Serving RAN Node 2
Changes
23.501 6255 1 Rel-19 Available Bitrate Reporting F 19.3.0 S2-168 S2-2503933 InterDigital Inc. XRM_Ph 5.45.1, Revised
when the Serving RAN Node 2 5.45.6
Changes
23.501 6255 2 Rel-19 Available Bitrate Reporting F 19.3.0 S2-168 S2-2504164 InterDigital Inc. XRM_Ph 5.45.1, Revised
when the Serving RAN Node 2 5.45.6
Changes
23.501 6255 3 Rel-19 Available Bitrate Reporting F 19.3.0 S2-168 S2-2504231 InterDigital Inc. XRM_Ph 5.45.6 Withdrawn
when the Serving RAN Node 2
Changes
23.501 6255 4 Rel-19 Available Bitrate Reporting F 19.3.0 S2-168 S2-2504232 InterDigital Inc. XRM_Ph 5.45.1, Revised
when the Serving RAN Node 2 5.45.6
Changes
23.501 6255 5 Rel-19 Available Bitrate Reporting F 19.3.0 S2-168 S2-2504417 InterDigital Inc. XRM_Ph 5.45.1, Agreed
when the Serving RAN Node 2 5.45.6
Changes
23.501 6256 - Rel-19 Energy consumption F 19.3.0 S2-168 S2-2503737 Samsung EnergyS 5.51.2.2.1, Revised
information for access type ys 5.51.2.2.2
23.501 6256 1 Rel-19 Energy consumption F 19.3.0 S2-168 S2-2504004 Samsung EnergyS 5.51.2.1, Revised
information for access type ys 5.51.2.2.2
23.501 6256 2 Rel-19 Energy consumption F 19.3.0 S2-168 S2-2504306 Samsung EnergyS 5.51.2.1, Revised
information for access type ys 5.51.2.2.2
23.501 6256 3 Rel-19 Energy consumption F 19.3.0 S2-168 S2-2504340 Samsung, NTT EnergyS 5.51.2.1, Agreed
information for access type DOCOMO ys 5.51.2.2.2
23.501 6257 - Rel-19 IP version used for MPQUIC-E F 19.3.0 S2-168 S2-2503751 Ericsson MASSS 5.32.6.2.2 Revised
23.501 6257 1 Rel-19 IP version used for MPQUIC-E F 19.3.0 S2-168 S2-2504361 Ericsson, LG MASSS 5.32.6.2.2 Revised
Electronics, CableLabs,
Mediatek
23.501 6257 2 Rel-19 IP version used for MPQUIC-E F 19.3.0 S2-168 S2-2504406 Ericsson, LG MASSS 5.32.6.2.2 Agreed
Electronics, CableLabs,
MediaTek Inc., Apple,
China Mobile, Nokia,
CATT, Samsung,
Deutsche Telekom
23.501 6258 - Rel-19 Clarification on provisioning F 19.3.0 S2-168 S2-2503783 China Mobile XRM_Ph 5.37.1, -
Multi-modal Service ID to NG- 2 5.37.2
RAN
23.501 6259 - Rel-19 Add missing XRM condition on F 19.3.0 S2-168 S2-2503804 Nokia XRM_Ph 5.7.2.4.1a -
PDU Set QoS Notification 2
control

3GPP
Report of meeting S2-168

Spec CR R Rel Subject Ca Vsn Mtg TD Source Work Aff Cl Status OAffS
t Item p
23.501 6260 - Rel-19 Energy consumption F 19.3.0 S2-168 S2-2503805 Samsung EnergyS 5.51.2.2.2 Revised
information collection for new ys
PDU Session
23.501 6260 1 Rel-19 Energy consumption F 19.3.0 S2-168 S2-2504001 Samsung EnergyS 5.51.2.2.2 Revised
information collection for new ys
PDU Session
23.501 6260 2 Rel-19 Energy consumption F 19.3.0 S2-168 S2-2504303 Samsung EnergyS 5.51.2.2.2 Agreed
information collection for new ys
PDU Session
23.501 6261 - Rel-19 Support of renewable energy F 19.3.0 S2-168 S2-2503806 Samsung EnergyS 5.51.2.1, Noted
information ys 5.51.2.2.3,
5.51.2.4
23.501 6262 - Rel-19 Update on the energy F 19.3.0 S2-168 S2-2503807 Vivo EnergyS 5.51.2.2.1, Revised
consumption information ys 5.51.2.2.3
collection
23.501 6262 1 Rel-19 Update on the energy D 19.3.0 S2-168 S2-2504002 Vivo EnergyS 5.51.2.2.3 Revised
consumption information ys
collection
23.501 6262 2 Rel-19 Update on the energy F 19.3.0 S2-168 S2-2504304 Vivo EnergyS 5.51.2.2.3 Agreed
consumption information ys
collection
23.501 6263 - Rel-19 Collection of energy F 19.3.0 S2-168 S2-2503808 Samsung EnergyS 4.29.2, Withdrawn
consumption information for ys 5.2.8.3.2
new PDU session
23.501 6264 - Rel-19 Correction of the Additional ULI F 19.3.0 S2-168 S2-2503813 Qualcomm Incorporated, VMR_Ph 5.49.4 Agreed
mapping conditions for MWAB Ericsson, Nokia, Huawei, 2
HiSilicon, LG Electronics
23.501 6265 - Rel-19 Ambient IoT interfaces and B 19.3.0 S2-168 S2-2503842 Huawei, HiSilicon AmbientI 4.2.6, Merged
reference points oT-ARC 4.2.7
23.501 6266 - Rel-19 Clarifications on NR Femto F 19.3.0 S2-168 S2-2503853 Nokia 5G_Femt 5.50.1 Revised
node deployments o
23.501 6266 1 Rel-19 Clarifications on NR Femto F 19.3.0 S2-168 S2-2504399 Nokia 5G_Femt 5.50.1 Agreed
node deployments o
23.501 6267 - Rel-19 Correction of PSAP call-back F 19.3.0 S2-168 S2-2503854 Vodafone TEI19 5.4.1.3, Revised
terminology 5.16.4.9
23.501 6267 1 Rel-19 Correction of PSAP call-back F 19.3.0 S2-168 S2-2504112 Vodafone 5GS_Ph 5.4.1.3, Agreed
terminology 1, TEI19 5.16.4.9
23.501 6268 - Rel-18 5GS common time reference F 18.9.0 S2-168 S2-2503862 Nokia IIoT, 5.27.1.2.1 Revised
traceable to UTC Vertical_
LAN
23.501 6268 1 Rel-18 5GS common time reference F 18.9.0 S2-168 S2-2504366 Nokia IIoT, 5.27.1.2.1, Endorsed
traceable to UTC Vertical_ 5.27.1.2.2
LAN
23.501 6269 - Rel-19 5GS common time reference A 19.3.0 S2-168 S2-2503863 Nokia IIoT, 5.27.1.2.1 Revised
traceable to UTC Vertical_
LAN

3GPP
Report of meeting S2-168

Spec CR R Rel Subject Ca Vsn Mtg TD Source Work Aff Cl Status OAffS
t Item p
23.501 6269 1 Rel-19 5GS common time reference A 19.3.0 S2-168 S2-2504367 Nokia IIoT, 5.27.1.2.1, Endorsed
traceable to UTC Vertical_ 5.27.1.2.2
LAN
23.501 6270 - Rel-19 Clarification on MWAB URSP F 19.3.0 S2-168 S2-2503872 Samsung VMR_Ph 5.9.4 Revised
processing 2
23.501 6270 1 Rel-19 Clarification on MWAB URSP F 19.3.0 S2-168 S2-2504102 Samsung VMR_Ph 5.49.2.24 Revised
processing 2
23.501 6270 2 Rel-19 Clarification on MWAB URSP F 19.3.0 S2-168 S2-2504379 Samsung VMR_Ph 5.49.2.2 Agreed
processing 2
23.501 6271 - Rel-19 Missing PLMN ID definition in F 19.3.0 S2-168 S2-2503876 Samsung TEI19_N 5.9.4 Revised
GUAMI. etShare
23.501 6271 1 Rel-19 Missing PLMN ID definition in F 19.3.0 S2-168 S2-2504135 Samsung 5GS_Ph 5.9.4 Postponed
GUAMI. 1, TEI19
23.501 6271 2 Rel-19 Missing PLMN ID definition in F 19.3.0 S2-168 S2-2504400 Samsung 5GS_Ph 5.9.4 Withdrawn
GUAMI. 1, TEI19
23.501 6272 - Rel-19 XRM_Ph2_KI1 Update of PDU F 19.3.0 S2-168 S2-2503882 Xiaomi XRM_Ph 5.37.5.2; -
Set Information Marking witout 2
DL Set QoS
23.501 6273 - Rel-19 XRM_Ph2_KI3 Update of PSI F 19.3.0 S2-168 S2-2503883 Xiaomi XRM_Ph 5.37.5.2; -
based DSCP Marking 2
23.501 6274 - Rel-19 Ph2_KI1 Update of QNC with F 19.3.0 S2-168 S2-2503888 Xiaomi XRM_Ph 5.7.2.4.1b Revised
AQP including PDU Set QoS 2
23.501 6274 1 Rel-19 Ph2_KI1 Update of QNC with F 19.3.0 S2-168 S2-2504171 Xiaomi XRM_Ph 5.7.2.4.1b Postponed
AQP including PDU Set QoS 2
23.501 6275 - Rel-19 Alignment with ATSSS F 19.3.0 S2-168 S2-2503889 Apple MASSS 5.32.2, Revised
Capability IE 5.32.5.1,
5.32.6.1
23.501 6275 1 Rel-19 Alignment with ATSSS F 19.3.0 S2-168 S2-2504359 Apple MASSS 5.32.2, Agreed
Capability IE 5.32.5.1,
5.32.6.1
23.501 6276 - Rel-18 Alignment with ATSSS F 18.9.0 S2-168 S2-2503890 Apple MASSS 5.32.2, Revised
Capability IE 5.32.5.1,
5.32.6.1
23.501 6276 1 Rel-18 Alignment with ATSSS F 18.9.0 S2-168 S2-2503891 Apple ATSSS_ 5.32.2, Revised
Capability IE Ph3 5.32.5.1,
5.32.6.1
23.501 6276 2 Rel-18 Alignment with ATSSS F 18.9.0 S2-168 S2-2504134 Apple ATSSS_ 5.32.2, Revised
Capability IE Ph3 5.32.5.1,
5.32.6.1
23.501 6276 3 Rel-18 Alignment with ATSSS F 18.9.0 S2-168 S2-2504386 Apple ATSSS_ 5.32.2, Agreed
Capability IE Ph3 5.32.5.1,
5.32.6.1
23.502 4501 1 Rel-19 Synchronizing status of QoS F 19.3.0 S2-168 S2-2502983 Ericsson 5GS_Ph 4.2.3.2, Postponed
Flow(s) between H-SMF or 1, TEI19 4.3.3.3
anchor SMF and UE

3GPP
Report of meeting S2-168

Spec CR R Rel Subject Ca Vsn Mtg TD Source Work Aff Cl Status OAffS
t Item p
23.502 4501 2 Rel-19 Synchronizing status of QoS F 19.3.0 S2-168 S2-2504365 Ericsson 5GS_Ph 4.2.3.2, Withdrawn
Flow(s) between H-SMF or 1, TEI19 4.3.3.3
anchor SMF and UE
23.502 4702 7 Rel-18 Clarifications for multi-modal F 18.9.0 S2-168 S2-2503585 Huawei, HiSilicon XRM 4.15.6.6, Noted
services 4.15.6.6a,
5.2.5.3.2,
5.2.5.3.3,
5.2.6.9.2,
5.2.6.9.5
23.502 4702 8 Rel-18 Clarifications for multi-modal F 18.9.0 S2-168 S2-2503900 Huawei, HiSilicon XRM 4.15.6.6, Withdrawn
services 4.15.6.6a,
5.2.5.3.2,
5.2.5.3.3,
5.2.6.9.2,
5.2.6.9.5
23.502 4956 3 Rel-19 Clarifications for multi-modal A 19.3.0 S2-168 S2-2503587 Huawei, HiSilicon XRM 4.15.6.6, Noted
services 4.15.6.6a,
5.2.5.3.2,
5.2.5.3.3,
5.2.6.9.2,
5.2.6.9.5
23.502 4956 4 Rel-19 Clarifications for multi-modal A 19.3.0 S2-168 S2-2503901 Huawei, HiSilicon XRM 4.15.6.6, Withdrawn
services 4.15.6.6a,
5.2.5.3.2,
5.2.5.3.3,
5.2.6.9.2,
5.2.6.9.5
23.502 5238 2 Rel-19 Exposure of control plane F 19.3.0 S2-168 S2-2503111 NTT DOCOMO AIML_C 4.15.4.X -
signalling information from NFs N (new),
5.2.2.3.1,
5.2.5.7.1,
5.2.8.3.1,
5.2.29.2.1
23.502 5240 2 Rel-19 Negotiation for future F 19.3.0 S2-168 S2-2503125 NTT DOCOMO, Toyota, EnergyS 2, 4.16.7.2 -
background data transfer KDDI ys
considering energy
23.502 5265 1 Rel-19 KI#1: Clarfication on the I-SMF F 19.3.0 S2-168 S2-2503406 Huawei, HiSilicon, eEDGE_ 4.23.5.4 Postponed
selected for local offloading Samsung 5GC_Ph
managment 3
23.502 5273 2 Rel-18 Handling of always-on PDU F 18.9.0 S2-168 S2-2503551 NTT DOCOMO, Nokia. eNS_Ph 4.3.2.2.1, -
sessions for network slices 3 4.3.3.2
subject to area restrictions
23.502 5274 2 Rel-19 Handling of always-on PDU A 19.3.0 S2-168 S2-2503558 Nokia eNS_Ph 4.3.2.2.1, -
sessions for network slices 3 4.3.3.2
subject to area control
23.502 5275 1 Rel-19 Support of SMF selection for F 19.3.0 S2-168 S2-2503338 Huawei, HiSilicon UIA_AR 4.3.2.2.1, Revised
Non-3GPP Device Identifer C 5.2.7.3.2

3GPP
Report of meeting S2-168

Spec CR R Rel Subject Ca Vsn Mtg TD Source Work Aff Cl Status OAffS
t Item p
23.502 5275 2 Rel-19 Support of SMF selection for F 19.3.0 S2-168 S2-2504036 Huawei, HiSilicon UIA_AR 4.3.2.2.1, Postponed
Non-3GPP Device Identifer C 5.2.3.3.1,
5.2.7.2.2,
5.2.7.3.2
23.502 5288 2 Rel-19 Clarification on the F 19.3.0 S2-168 S2-2503633 Huawei, HiSilicon EnergyS 5.2.8.1, -
EventExposure service ys 5.2.8.3.1
operation of SMF
23.502 5338 1 Rel-17 Clarification on emergency PDU F 17.14.0 S2-168 S2-2502972 Ericsson, AT&T, NR_new 4.3.4.2 Revised
session release Qualcomm Incorporated, RAT-
MediaTek Inc Core,
NR_redc
ap-Core,
5G_CIoT
, TEI17
23.502 5338 2 Rel-17 Clarification on emergency PDU F 17.14.0 S2-168 S2-2504100 Ericsson, AT&T, NR_new 4.3.4.2 Postponed
session release Qualcomm Incorporated, RAT-
MediaTek Inc Core,
NR_redc
ap-Core,
5G_CIoT
, TEI17
23.502 5339 1 Rel-18 Clarification on emergency PDU A 18.9.0 S2-168 S2-2502973 Ericsson, AT&T, NR_new 4.3.4.2 -
session release Qualcomm Incorporated, RAT-
MediaTek Inc Core,
NR_redc
ap-Core,
5G_CIoT
, TEI17
23.502 5340 1 Rel-19 Clarification on emergency PDU A 19.3.0 S2-168 S2-2502974 Ericsson, AT&T, NR_new 4.3.4.2 -
session release Qualcomm Incorporated, RAT-
MediaTek Inc Core,
NR_redc
ap-Core,
5G_CIoT
, TEI17
23.502 5341 1 Rel-19 PWS handling update for VMR F 19.3.0 S2-168 S2-2502978 Ericsson, Qualcomm VMR_Ph 4.10 Merged
Incorporated 2, VMR
23.502 5350 1 Rel-19 NF discovery for signaling data F 19.3.0 S2-168 S2-2503411 China Mobile AIML_C 5.2.7.3.2 -
collection related to signaling N
storm analytics
23.502 5352 1 Rel-19 Update on SMF services F 19.3.0 S2-168 S2-2503650 Vivo EnergyS 5.2.8.3.2 -
ys
23.502 5379 - Rel-19 LMF re-selection based on AI F 19.3.0 S2-168 S2-2502868 ZTE AIML_C 5.2.7.2.2, -
capability N 5.2.7.3.2
23.502 5380 - Rel-18 Correction for BSF invocation in F 18.9.0 S2-168 S2-2502876 Oracle, Verizon TEI18, 4.16.16.2 Revised
URSP Rule Enforcement eUEPO
Information procedure

3GPP
Report of meeting S2-168

Spec CR R Rel Subject Ca Vsn Mtg TD Source Work Aff Cl Status OAffS
t Item p
23.502 5380 1 Rel-18 Correction for BSF invocation in F 18.9.0 S2-168 S2-2503778 Oracle, Verizon, TEI18, 4.16.16.2 Revised
URSP Rule Enforcement Ericsson eUEPO
Information procedure
23.502 5380 2 Rel-18 Correction for BSF invocation in F 18.9.0 S2-168 S2-2504114 Oracle, Verizon, TEI18, 4.16.16.2 Agreed
URSP Rule Enforcement Ericsson eUEPO
Information procedure
23.502 5381 - Rel-19 Correction for BSF invocation in A 19.3.0 S2-168 S2-2502877 Oracle, Verizon eUEPO, 4.16.16.2 Revised
URSP Rule Enforcement TEI19
Information procedure
23.502 5381 1 Rel-19 Correction for BSF invocation in A 19.3.0 S2-168 S2-2503779 Oracle, Verizon, eUEPO, 4.16.16.2 Revised
URSP Rule Enforcement Ericsson TEI19
Information procedure
23.502 5381 2 Rel-19 Correction for BSF invocation in A 19.3.0 S2-168 S2-2504115 Oracle, Verizon, eUEPO, 4.16.16.2 Agreed
URSP Rule Enforcement Ericsson TEI19
Information procedure
23.502 5382 - Rel-19 Selection mechanisms for SMF F 19.3.0 S2-168 S2-2502901 Ericsson UIA_AR 4.3.2.2.1, -
and PCF for non-3GPP devices C 5.2.3.3.1,
QoS differentiation 5.2.7.2.2,
5.2.8.2.5
23.502 5383 - Rel-19 QoS differention for multiple F 19.3.0 S2-168 S2-2502902 Ericsson, AT&T UIA_AR 4.3.3.2 Revised
Non-3GPP devices C
23.502 5383 1 Rel-19 QoS differention for multiple F 19.3.0 S2-168 S2-2504023 Ericsson UIA_AR 4.3.3.2 Revised
Non-3GPP devices C
23.502 5383 2 Rel-19 QoS differention for multiple F 19.3.0 S2-168 S2-2504254 Ericsson, AT&T, Xiaomi UIA_AR 4.3.3.2 Revised
Non-3GPP devices C
23.502 5383 3 Rel-19 QoS differention for multiple F 19.3.0 S2-168 S2-2504332 Ericsson, AT&T, Xiaomi, UIA_AR 4.3.3.2 Revised
Non-3GPP devices Nokia, CableLabs C
23.502 5383 4 Rel-19 QoS differention for multiple F 19.3.0 S2-168 S2-2504336 Ericsson, AT&T, Xiaomi, UIA_AR 4.3.3.2 Agreed
Non-3GPP devices Nokia, CableLabs, ZTE C
23.502 5384 - Rel-19 Removing Non-3GPP Device F 19.3.0 S2-168 S2-2502904 Ericsson UIA_AR 5.2.5.4.2 -
Connection Information from C
SM policy control create
23.502 5385 - Rel-19 Handling removal of Non-3GPP F 19.3.0 S2-168 S2-2502905 Ericsson, AT&T UIA_AR 4.3.3.2 Revised
Device Identifiers from UDR C
23.502 5385 1 Rel-19 Handling removal of Non-3GPP C 19.3.0 S2-168 S2-2504025 Ericsson UIA_AR 4.3.3.2 Noted
Device Identifiers from UDR C
23.502 5386 - Rel-19 Clarifying port ranges and F 19.3.0 S2-168 S2-2502906 Ericsson UIA_AR 5.52.3 Revised
removing EN C
23.502 5386 1 Rel-19 Clarifying port ranges and F 19.3.0 S2-168 S2-2504032 Ericsson UIA_AR 5.52.3 Agreed
removing EN C
23.502 5387 - Rel-19 KI#1: Immediate Reporting F 19.3.0 S2-168 S2-2502919 Ericsson NG_RTC 5.2.6.39.2. Revised
_Ph2 1
23.502 5387 1 Rel-19 KI#1: Immediate Reporting F 19.3.0 S2-168 S2-2503988 Ericsson NG_RTC 5.2.6.39.2. Agreed
_Ph2 1

3GPP
Report of meeting S2-168

Spec CR R Rel Subject Ca Vsn Mtg TD Source Work Aff Cl Status OAffS
t Item p
23.502 5388 - Rel-19 KI#1: Event Status Retrieval F 19.3.0 S2-168 S2-2502921 Ericsson NG_RTC 5.2.6.1; -
Procedure _Ph2 5.2.6.39.1;
5.2.6.39.2.
X (NEW)
23.502 5389 - Rel-19 Handling of AF Specific UE IDs C 19.3.0 S2-168 S2-2502954 Ericsson EDGEAP - Withdrawn
P
23.502 5390 - Rel-19 Corrections on UPF Event F 19.3.0 S2-168 S2-2502955 Ericsson UPEAS_ 5.2.26.2.1 Revised
Exposure Ph2
23.502 5390 1 Rel-19 Corrections on UPF Event F 19.3.0 S2-168 S2-2504037 Ericsson UPEAS_ 5.2.26.2.1 Agreed
Exposure Ph2
23.502 5391 - Rel-19 Updates to Assigned Trajectory F 19.3.0 S2-168 S2-2502965 Ericsson UAS_Ph 5.2.2.3.1 Revised
Parameters 3
23.502 5391 1 Rel-19 Updates to Assigned Trajectory F 19.3.0 S2-168 S2-2504133 Ericsson UAS_Ph 5.2.2.3.1 Agreed
Parameters 3
23.502 5392 - Rel-18 PWS handling update for VMR F 18.9.0 S2-168 S2-2502982 Ericsson, Qualcomm VMR 4.10 Merged
Incorporated
23.502 5393 - Rel-19 Providing device identifier F 19.3.0 S2-168 S2-2502987 Google UIA_AR 4.3.3.2 -
information in PDU session C
modification request
23.502 5394 - Rel-19 Updating the F 19.3.0 S2-168 S2-2503001 InterDigital Inc., LG UIA_AR 5.2.8.2.3 Revised
Nsmf_PDUSession_Update Electronics, Samsung, C
service description to account Nokia
for non-3GPP device
connection information
23.502 5394 1 Rel-19 Updating the F 19.3.0 S2-168 S2-2504029 InterDigital Inc., LG UIA_AR 5.2.8.2.3 Agreed
Nsmf_PDUSession_Update Electronics, Samsung, C
service description to account Nokia
for non-3GPP device
connection information
23.502 5395 - Rel-19 23.502 Support of uplink rate B 19.3.0 S2-168 S2-2503006 Lenovo XRM_Ph 4.3.2.2.1, -
control for QoS flows at RAN 2 4.3.3.2,
4.15.6.6,
4.15.6.6a,
5.2.5.3.2,
5.2.5.3.3,
5.2.6.9.2,
5.2.6.9.5
23.502 5396 - Rel-19 Correction for MA PDU Session F 19.3.0 S2-168 S2-2503020 Nokia MASSS 4.22.2.2.1, Revised
of type Ethernet with MPQUIC- 4.22.2.2.2
E steering functionality for
Roaming scenarios
23.502 5396 1 Rel-19 Correction for MA PDU Session F 19.3.0 S2-168 S2-2504353 Nokia MASSS 4.22.2.2.1, Postponed
of type Ethernet with MPQUIC- 4.22.2.2.2
E steering functionality for
Roaming scenarios

3GPP
Report of meeting S2-168

Spec CR R Rel Subject Ca Vsn Mtg TD Source Work Aff Cl Status OAffS
t Item p
23.502 5397 - Rel-19 LS on Next Generation eCall. F 19.3.0 S2-168 S2-2503021 CEN/TC 278/WG 15 MASSS 4.22.2.3.2, Revised
eSafety 4.22.6.2.1,
4.22.6.2.2,
4.22.6.2.5,
4.22.6.2.x
1(new),
4.22.6.2.x
2 (new)
23.502 5397 1 Rel-19 Correction to EPS interworking F 19.3.0 S2-168 S2-2503076 Nokia MASSS 4.22.2.3.2, -
for MA PDU Session of type 4.22.6.2.1,
Ethernet with MPQUIC-E 4.22.6.2.2,
steering functionality 4.22.6.2.5,
4.22.6.2.x
1(new),
4.22.6.2.x
2 (new)
23.502 5398 - Rel-19 AF specific UE ID generation C 19.3.0 S2-168 S2-2503025 Samsung EDGEAP 4.15.10 Merged
P
23.502 5399 - Rel-19 23.502 Clarifications to Session F 19.3.0 S2-168 S2-2503033 Samsung UIA_AR - Withdrawn
Management aspects for C
handling multiple Non-3GPP
Device Identifiers
23.502 5400 - Rel-19 23.501 Clarification to usage of F 19.3.0 S2-168 S2-2503035 Samsung UPEAS_ - Withdrawn
Operator configurable UPF Ph2
capabilties in roaming scenarios
23.502 5401 - Rel-19 Clarifications to Direct F 19.3.0 S2-168 S2-2503036 Samsung UPEAS_ 4.15.4.5.6, Revised
subscription to UPF Events in Ph2 4.15.4.5.7
case of session release or UPF
relocation
23.502 5401 1 Rel-19 Clarifications to Direct F 19.3.0 S2-168 S2-2504039 Samsung UPEAS_ 4.15.4.5.6 Revised
subscription to UPF Events in Ph2
case of session release or UPF
relocation
23.502 5401 2 Rel-19 Clarifications to Direct F 19.3.0 S2-168 S2-2504083 Samsung UPEAS_ 4.15.4.5.6 Agreed
subscription to UPF Events in Ph2
case of session release or UPF
relocation
23.502 5402 - Rel-19 Correction to direct subscription F 19.3.0 S2-168 S2-2503037 Samsung UPEAS_ 4.15.4.5.5 Revised
of UPF event expsoure using Ph2
UE IP address
23.502 5402 1 Rel-19 Correction to direct subscription F 19.3.0 S2-168 S2-2504040 Samsung UPEAS_ 4.15.4.5.5 Revised
of UPF event expsoure using Ph2
UE IP address
23.502 5402 2 Rel-19 Correction to direct subscription F 19.3.0 S2-168 S2-2504082 Samsung UPEAS_ 4.15.4.5.5 Agreed
of UPF event expsoure using Ph2
UE IP address

3GPP
Report of meeting S2-168

Spec CR R Rel Subject Ca Vsn Mtg TD Source Work Aff Cl Status OAffS
t Item p
23.502 5403 - Rel-19 Corrections to PDU Session F 19.3.0 S2-168 S2-2503038 Samsung MASSS 4.22.6.3 Revised
Modification on mobility to 5GS
for Ethernet MA PDU Session
23.502 5403 1 Rel-19 Corrections to PDU Session F 19.3.0 S2-168 S2-2504360 Samsung MASSS 4.22.6.3 Agreed
Modification on mobility to 5GS
for Ethernet MA PDU Session
23.502 5404 - Rel-19 Clarification to HR-SBO F 19.3.0 S2-168 S2-2503040 Samsung MASSS 4.22.2.2.1, -
scenarios for supporting 4.22.2.2.2
MPQUIC-E
23.502 5405 - Rel-19 Correct Handling of IP version F 19.3.0 S2-168 S2-2503042 Samsung MASSS 4.22.2.1 -
when MPQUIC-E is enabled
23.502 5406 - Rel-19 Update on Energy Consumption F 19.3.0 S2-168 S2-2503054 ETRI EnergyS 4.29.2 Noted
information collection procedure ys
23.502 5407 - Rel-19 Update on SMF event exposure F 19.3.0 S2-168 S2-2503055 ETRI EnergyS 5.2.8.3.1 -
to support Energy Consumption ys
information
23.502 5408 - Rel-19 Editorial update on Energy D 19.3.0 S2-168 S2-2503056 ETRI EnergyS 4.29 -
Consumption information ys
collection and exposure
23.502 5409 - Rel-19 Clarifications for SM signalling F 19.3.0 S2-168 S2-2503075 Apple UIA_AR 4.3.3.2 -
including non-3GPP device C
identifiers for QoS
differentiation
23.502 5410 - Rel-16 AMF reselection via NAS C 16.19.0 S2-168 S2-2503082 Jio Platforms Ltd (JPL) 5GS_Ph 4.2.2.2.3 Withdrawn
reroute based on Routing 1
Indicator
23.502 5411 - Rel-16 AMF reselection via NAS C 16.19.0 S2-168 S2-2503084 Jio Platforms Ltd (JPL) 5GS_Ph 4.2.2.2.3 -
reroute based on Routing 1
Indicator
23.502 5412 - Rel-16 Rel-16 CR TS 23.502 Type C 16.19.0 S2-168 S2-2503085 Jio Platform Limited 5GS_Ph 4.16.11 -
Allocation Code (TAC) based (JPL) 1
AMF local configuration for
establishment of UE policy
association.
23.502 5413 - Rel-19 Generation of AF specific UE ID F 19.3.0 S2-168 S2-2503092 Nokia, AT&T, KPN, NTT EDGEAP 4.15.10 Revised
DOCOMO, Deutsche P
Telekom
23.502 5413 1 Rel-19 Generation of AF specific UE ID F 19.3.0 S2-168 S2-2504097 Nokia, AT&T, KPN, NTT EDGEAP 4.15.10 Revised
DOCOMO, Deutsche P
Telekom
23.502 5413 2 Rel-19 Generation of AF specific UE ID F 19.3.0 S2-168 S2-2504395 Nokia, AT&T, KPN, NTT EDGEAP 4.15.10 Agreed
DOCOMO, Deutsche P
Telekom, Ericsson,
Samsung
23.502 5414 - Rel-19 Aligning MF selection criteria F 19.3.0 S2-168 S2-2503100 Nokia NG_RTC 5.2.7.3.2 -
with 23.228 _Ph2

3GPP
Report of meeting S2-168

Spec CR R Rel Subject Ca Vsn Mtg TD Source Work Aff Cl Status OAffS
t Item p
23.502 5415 - Rel-19 Clarification on AF requested F 19.3.0 S2-168 S2-2503128 Huawei, HiSilicon TEI19_Sl 4.15.6.9.2, Revised
network slice replacement iceSel 4.15.6.9.3
23.502 5415 1 Rel-19 Clarification on AF requested F 19.3.0 S2-168 S2-2504370 Huawei, HiSilicon TEI19_Sl 4.15.6.9.2, Agreed
network slice replacement iceSel 4.15.6.9.3
23.502 5416 - Rel-18 Removal of text for PWS F 18.9.0 S2-168 S2-2503184 Nokia VMR 4.10 Revised
23.502 5416 1 Rel-18 Removal of text for PWS F 18.9.0 S2-168 S2-2504106 Nokia VMR 4.10 Agreed
23.502 5417 - Rel-19 Removal of text for PWS F 19.3.0 S2-168 S2-2503185 Nokia VMR, 4.10 Merged
VMR_Ph
2
23.502 5418 - Rel-19 Clarification of F 19.3.0 S2-168 S2-2503205 Nokia TEI19_Sl 4.15.6.9.3, Revised
Nnef_AMFInfluence based iceSel 5.2.6.23.2,
approach to AF requested 5.2.6.23.3
network slice replacement
23.502 5418 1 Rel-19 Clarification of F 19.3.0 S2-168 S2-2504150 Nokia TEI19_Sl 4.15.6.9.3, Revised
Nnef_AMFInfluence based iceSel 5.2.6.23.2,
approach to AF requested 5.2.6.23.3
network slice replacement
23.502 5418 2 Rel-19 Clarification of F 19.3.0 S2-168 S2-2504403 Nokia TEI19_Sl 4.15.6.9.3, Agreed
Nnef_AMFInfluence based iceSel 5.2.6.23.2
approach to AF requested
network slice replacement
23.502 5419 - Rel-19 Indication of Rate-Adaptable C 19.3.0 S2-168 S2-2503212 Ericsson NR_XR_ 4.3.3.2, -
QoS Flows to NG-RAN Ph3- 4.15.6.6,
Core 4.15.6.6a,
5.2.5.3.2,
5.2.5.3.3,
5.2.6.9.2,
5.2.6.9.5
23.502 5420 - Rel-19 AIML_CN KI#4 Resolve issues B 19.3.0 S2-168 S2-2503253 Nokia AIML_C 4.17.9, -
for event exposure and for SCP N 5.2.7.2.5,
mitigation actions 5.2.29.2.1
23.502 5421 - Rel-19 Handling of MPQUIC-E with F 19.3.0 S2-168 S2-2503262 Ericsson MASSS 4.22.2.3.1, Revised
EPS interworking 4.22.2.3.2
23.502 5421 1 Rel-19 Handling of MPQUIC-E with F 19.3.0 S2-168 S2-2504354 Ericsson MASSS 4.22.2.3.1, Postponed
EPS interworking 4.22.2.3.2
23.502 5422 - Rel-19 Handling of MPQUIC-E in F 19.3.0 S2-168 S2-2503263 Ericsson MASSS 4.22.2.2.1, -
roaming cases 4.22.2.2.2
23.502 5423 - Rel-18 Update on UE Context in AMF F 18.9.0 S2-168 S2-2503300 LG Electronics eNS_Ph 5.2.2.2.2 Noted
to support Network Slice 3
Replacement
23.502 5424 - Rel-19 Update on UE Context in AMF A 19.3.0 S2-168 S2-2503301 LG Electronics eNS_Ph 5.2.2.2.2 Noted
to support Network Slice 3
Replacement
23.502 5425 - Rel-19 Clarification on CAG F 19.3.0 S2-168 S2-2503302 LG Electronics 5G_Femt 4.15.6.3h Revised
Information Provisioning o
23.502 5425 1 Rel-19 Clarification on CAG F 19.3.0 S2-168 S2-2504136 LG Electronics 5G_Femt 4.15.6.3h Revised
Information Provisioning o

3GPP
Report of meeting S2-168

Spec CR R Rel Subject Ca Vsn Mtg TD Source Work Aff Cl Status OAffS
t Item p
23.502 5425 2 Rel-19 Clarification on CAG F 19.3.0 S2-168 S2-2504398 LG Electronics 5G_Femt 4.15.6.3h Agreed
Information Provisioning o
23.502 5426 - Rel-19 Clarification on PDU Session F 19.3.0 S2-168 S2-2503305 LG Electronics MASSS 4.22.2.1, -
Type setting in case of V/I-SMF 4.22.2.2.1
23.502 5427 - Rel-19 Clarification on IP version used F 19.3.0 S2-168 S2-2503307 MediaTek Inc. MASSS 4.22.2.1 -
for MPQUIC-E
23.502 5428 - Rel-19 Clarification on IP version used F 19.3.0 S2-168 S2-2503309 LG Electronics MASSS 4.22.2.1 -
for MPQUIC-E in procedure
23.502 5429 - Rel-19 Generlization of MF capabilities F 19.3.0 S2-168 S2-2503310 Qualcomm Incorporated NG_RTC 5.2.7.2.2, -
registration and discovery _Ph2 5.2.7.3.2
23.502 5430 - Rel-18 N2 SM information to NG-RAN F 18.9.0 S2-168 S2-2503326 Samsung XRM 4.3.3.2 Revised
23.502 5430 1 Rel-18 N2 SM information to NG-RAN F 18.9.0 S2-168 S2-2503904 Samsung XRM 4.3.3.2 Revised
23.502 5430 2 Rel-18 N2 SM information to NG-RAN F 18.9.0 S2-168 S2-2504159 Samsung XRM 4.3.3.2 Revised
23.502 5430 3 Rel-18 N2 SM information to NG-RAN F 18.9.0 S2-168 S2-2504189 Samsung XRM 4.3.3.2 Agreed
23.502 5431 - Rel-19 N2 SM information to NG-RAN A 19.3.0 S2-168 S2-2503327 Samsung XRM 4.3.3.2 Revised
23.502 5431 1 Rel-19 N2 SM information to NG-RAN A 19.3.0 S2-168 S2-2503905 Samsung XRM 4.3.3.2 Revised
23.502 5431 2 Rel-19 N2 SM information to NG-RAN A 19.3.0 S2-168 S2-2504160 Samsung XRM 4.3.3.2 Revised
23.502 5431 3 Rel-19 N2 SM information to NG-RAN A 19.3.0 S2-168 S2-2504190 Samsung XRM 4.3.3.2 Agreed
23.502 5432 - Rel-19 Inclusion of several Non-3GPP F 19.3.0 S2-168 S2-2503331 Nokia, InterDigital Inc., UIA_AR 4.3.3.2 -
Device Identifiers LG Electronics C
23.502 5433 - Rel-19 CHF Group ID in the needed F 19.3.0 S2-168 S2-2503333 Nokia CHFSeg, 5.2.2.2.2, Revised
contexts TEI19 5.2.3.3.1
23.502 5433 1 Rel-19 CHF Group ID in the needed F 19.3.0 S2-168 S2-2504113 Nokia CHFSeg, 5.2.2.2.2, Revised
contexts TEI19 5.2.3.3.1
23.502 5433 2 Rel-19 CHF Group ID in the needed F 19.3.0 S2-168 S2-2504413 Nokia CHFSeg, 5.2.2.2.2 Agreed
contexts TEI19
23.502 5434 - Rel-18 PWS enhancements for MBSR F 18.9.0 S2-168 S2-2503354 Huawei, HiSilicon VMR 4.10 Merged
23.502 5435 - Rel-19 PWS enhancements for MBSR F 19.3.0 S2-168 S2-2503355 Huawei, HiSilicon VMR_Ph 4.10 Merged
and MWAB 2
23.502 5436 - Rel-19 Removal of event subscription F 19.3.0 S2-168 S2-2503359 SAMSUNG 5G_Femt - Withdrawn
for CAG information o
provisioning
23.502 5437 - Rel-19 Removal of event subscription F 19.3.0 S2-168 S2-2503360 Samsung 5G_Femt 4.15.6.2 Revised
for CAG information o
provisioning
23.502 5437 1 Rel-19 Removal of event subscription F 19.3.0 S2-168 S2-2504137 Samsung 5G_Femt 4.15.6.2 Agreed
for CAG information o
provisioning
23.502 5438 - Rel-19 Adding Layer-2 Multi-hop U2N F 19.3.0 S2-168 S2-2503374 LG Electronics 5G_ProS 5.2.3.3.1 Agreed
relaying aspects to UE e_Ph3
Subscription data
23.502 5439 - Rel-19 Clarification on the AF F 19.3.0 S2-168 S2-2503399 LG Electronics eEDGE_ 5.2.8.2.2, -
trafficInfluence information from 5GC_Ph 5.2.8.2.3
SMF to I-SMF 3

3GPP
Report of meeting S2-168

Spec CR R Rel Subject Ca Vsn Mtg TD Source Work Aff Cl Status OAffS
t Item p
23.502 5440 - Rel-18 Registration handling during the F 18.9.0 S2-168 S2-2503401 Huawei, Hisilicon TEI18, 4.2.2.2.2 Revised
mobility from non-3GPP access 5GS_Ph
to 3GPP access 1
23.502 5440 1 Rel-18 Registration handling during the F 18.9.0 S2-168 S2-2504363 Huawei, Hisilicom TEI18, 4.2.2.2.2 Revised
mobility from non-3GPP access 5GS_Ph
to 3GPP access 1
23.502 5440 2 Rel-18 Registration handling during the F 18.9.0 S2-168 S2-2504410 Huawei, Hisilicom TEI18, 4.2.2.2.2 Revised
mobility from non-3GPP access 5GS_Ph
to 3GPP access 1
23.502 5440 3 Rel-18 Registration handling during the F 18.9.0 S2-168 S2-2504472 Huawei, Hisilicom TEI18, 4.2.2.2.2 Agreed
mobility from non-3GPP access 5GS_Ph
to 3GPP access 1
23.502 5441 - Rel-19 Registration handling during the F 19.3.0 S2-168 S2-2503402 Huawei, Hisilicon 5GS_Ph 4.2.2.2.2 Revised
mobility from non-3GPP access 1,
to 3GPP access TEI19_N
etShare
23.502 5441 1 Rel-19 Registration handling during the A 19.3.0 S2-168 S2-2504364 Huawei, Hisilicom 5GS_Ph 4.2.2.2.2 Revised
mobility from non-3GPP access 1,
to 3GPP access TEI19_N
etShare
23.502 5441 2 Rel-19 Registration handling during the A 19.3.0 S2-168 S2-2504411 Huawei, Hisilicom 5GS_Ph 4.2.2.2.2 Revised
mobility from non-3GPP access 1,
to 3GPP access TEI19_N
etShare
23.502 5441 3 Rel-19 Registration handling during the A 19.3.0 S2-168 S2-2504473 Huawei, Hisilicom 5GS_Ph 4.2.2.2.2 Agreed
mobility from non-3GPP access 1,
to 3GPP access TEI19_N
etShare
23.502 5442 - Rel-19 Interaction between SMF and I- F 19.3.0 S2-168 S2-2503409 Huawei, Hisilicon eEDGE_ 4.23.9.0, Revised
SMF 5GC_Ph 4.23.6.2,
3 5.2.8.2.2,
5.2.8.2.3
23.502 5442 1 Rel-19 Interaction between SMF and I- F 19.3.0 S2-168 S2-2503930 Huawei, Hisilicon eEDGE_ 4.23.9.0, Revised
SMF 5GC_Ph 4.23.6.2,
3 5.2.8.2.2,
5.2.8.2.3
23.502 5442 2 Rel-19 Interaction between SMF and I- F 19.3.0 S2-168 S2-2504180 Huawei, Hisilicon eEDGE_ 4.23.6.2, Agreed
SMF 5GC_Ph 5.2.8.2.2,
3 5.2.8.2.3
23.502 5443 - Rel-19 TAIs configured by OAM F 19.3.0 S2-168 S2-2503417 Vivo 5GSAT_ 4.2.7.1 Revised
Ph3-ARC
23.502 5443 1 Rel-19 TAIs configured by OAM F 19.3.0 S2-168 S2-2503912 Vivo 5GSAT_ 4.2.7.1 Noted
Ph3-ARC

3GPP
Report of meeting S2-168

Spec CR R Rel Subject Ca Vsn Mtg TD Source Work Aff Cl Status OAffS
t Item p
23.502 5444 - Rel-19 Clarification on MPQUIC F 19.3.0 S2-168 S2-2503430 Huawei, HiSilicon MASSS 4.22.2.1, -
functionality 4.22.2.2.1,
4.22.2.3.2,
4.22.3.3,
4.22.3.4
23.502 5445 - Rel-18 PWS enhancements for MWAB F 18.9.0 S2-168 S2-2503440 Samsung VMR_Ph 4.10 Merged
and MBSR 2
23.502 5446 - Rel-19 PWS enhancements for MWAB F 19.3.0 S2-168 S2-2503443 Samsung VMR_Ph 4.10 Revised
and MBSR 2
23.502 5446 1 Rel-19 PWS enhancements for MWAB F 19.3.0 S2-168 S2-2504107 Samsung, Nokia, VMR_Ph 4.10 Agreed
and MBSR Ericsson 2
23.502 5447 - Rel-19 Adding Energy indication to F 19.3.0 S2-168 S2-2503455 ZTE EnergyS 4.16.7.2, -
BDT procedure and service ys 5.2.5.5.2,
operation 5.2.6.6.2
23.502 5448 - Rel-19 Procedure Correction on the F 19.3.0 S2-168 S2-2503458 ZTE EnergyS 4.29.2 -
Energy Consumption ys
information collection
23.502 5449 - Rel-19 Resolve the EN in the EIF F 19.3.0 S2-168 S2-2503460 ZTE EnergyS 5.2.28 Revised
service ys
23.502 5449 1 Rel-19 Resolve the EN in the EIF F 19.3.0 S2-168 S2-2504010 ZTE EnergyS 5.2.28 Agreed
service ys
23.502 5450 - Rel-19 Clarification on the non-3gpp F 19.3.0 S2-168 S2-2503463 ZTE, Xiaomi UIA_AR 4.3.3.2, -
device identifier activation and C 4.16.5.2
removal
23.502 5451 - Rel-19 Clarification on the subscription F 19.3.0 S2-168 S2-2503465 ZTE UIA_AR 4.16.5.1 Revised
to UDR C
23.502 5451 1 Rel-19 Clarification on the subscription F 19.3.0 S2-168 S2-2504030 ZTE, Nokia UIA_AR 4.16.5.1 Revised
to UDR C
23.502 5451 2 Rel-19 Clarification on the subscription F 19.3.0 S2-168 S2-2504259 ZTE, Nokia, NEC, UIA_AR 4.16.5.1 Agreed
to UDR Xiaomi C
23.502 5452 - Rel-19 Update on change of BP/ULCL F 19.3.0 S2-168 S2-2503467 ETRI 5GSAT_ 4.3.5.7, -
and UP notification procedures Ph3-ARC 4.3.6.3
for UE-Satellite-UE
communication
23.502 5453 - Rel-19 Update on PDU session F 19.3.0 S2-168 S2-2503470 Huawei, HiSilicon XRM_Ph 4.3.2.2.1 -
establishment procedure for 2
MoQ
23.502 5454 - Rel-19 Clarifications for multiplexed F 19.3.0 S2-168 S2-2503518 Huawei, HiSilicon XRM_Ph 4.15.6.6, -
media traffic 2 4.15.6.6a
23.502 5455 - Rel-19 Update the procedures with F 19.3.0 S2-168 S2-2503560 Vivo XRM_Ph 4.3.2.2.1,4 -
Multi-modal service ID 2 .15.6.6
23.502 5456 - Rel-19 Correction on energy F 19.3.0 S2-168 S2-2503572 CATT EnergyS 4.15.3.1, Revised
consumption information ys 4.29.0,
collection and exposure 4.29.1,
4.29.2,
5.2.28.2.1

3GPP
Report of meeting S2-168

Spec CR R Rel Subject Ca Vsn Mtg TD Source Work Aff Cl Status OAffS
t Item p
23.502 5456 1 Rel-19 Correction on energy F 19.3.0 S2-168 S2-2504000 CATT, ZTE, vivo, ETRI EnergyS 4.15.3.1, Revised
consumption information ys 4.29.0,
collection and exposure 4.29.1,
4.29.2,
5.2.28.2.1
23.502 5456 2 Rel-19 Correction on energy F 19.3.0 S2-168 S2-2504301 CATT, ZTE, vivo, ETRI EnergyS 4.15.3.1, Agreed
consumption information ys 4.29.0,
collection and exposure 4.29.1,
4.29.2,
5.2.28.2.1
23.502 5457 - Rel-19 Addition of NOTE to user F 19.3.0 S2-168 S2-2503577 Apple AIML_C 5.2.3.3.1 -
consent purpose N
23.502 5458 - Rel-19 Energy Consumption F 19.3.0 S2-168 S2-2503588 Nokia EnergyS 4.29.2 Revised
information collection procedure ys
clarification
23.502 5458 1 Rel-19 Energy Consumption F 19.3.0 S2-168 S2-2503996 Nokia EnergyS 4.29.2 Revised
information collection procedure ys
clarification
23.502 5458 2 Rel-19 Energy Consumption F 19.3.0 S2-168 S2-2504080 Nokia EnergyS 4.29.2 Revised
information collection procedure ys
clarification
23.502 5458 3 Rel-19 Energy Consumption F 19.3.0 S2-168 S2-2504297 Nokia, CMCC, Huawei, EnergyS 4.29.2 Agreed
information collection procedure Samsung ys
clarification
23.502 5459 - Rel-19 SMF exposure service F 19.3.0 S2-168 S2-2503593 Nokia EnergyS 5.2.8.3 Revised
clarification for Energy ys
Consumption information
collection
23.502 5459 1 Rel-19 SMF exposure service F 19.3.0 S2-168 S2-2504006 Nokia EnergyS 5.2.8.3 Revised
clarification for Energy ys
Consumption information
collection
23.502 5459 2 Rel-19 SMF exposure service F 19.3.0 S2-168 S2-2504091 Nokia EnergyS 5.2.8.3 Revised
clarification for Energy ys
Consumption information
collection
23.502 5459 3 Rel-19 SMF exposure service F 19.3.0 S2-168 S2-2504307 Nokia, Huawei, CMCC EnergyS 5.2.8.3 Agreed
clarification for Energy ys
Consumption information
collection
23.502 5460 - Rel-19 Update on Non-3GPP Device F 19.3.0 S2-168 S2-2503596 Xiaomi UIA_AR 4.15.6.15, Revised
Identifier(s) Information C 5.2.5.4.2
provisioning and policy control
23.502 5460 1 Rel-19 Update on Non-3GPP Device F 19.3.0 S2-168 S2-2504028 Xiaomi UIA_AR 4.15.6.15, Agreed
Identifier(s) Information C 5.2.5.4.2
provisioning and policy control

3GPP
Report of meeting S2-168

Spec CR R Rel Subject Ca Vsn Mtg TD Source Work Aff Cl Status OAffS
t Item p
23.502 5461 - Rel-19 EIF exposure service definition F 19.3.0 S2-168 S2-2503601 Nokia EnergyS 5.2.28.2.2 Revised
clarification ys
23.502 5461 1 Rel-19 EIF exposure service definition F 19.3.0 S2-168 S2-2504009 Nokia EnergyS 5.2.28.2.2 Agreed
clarification ys
23.502 5462 - Rel-19 Clarificaiton on supporting F 19.3.0 S2-168 S2-2503606 Huawei, HiSilicon UIA_AR 4.3.3.2, -
multiple non-3GPP device C 4.16.5.1
identifiers
23.502 5463 - Rel-19 Update the procedure and EIF F 19.3.0 S2-168 S2-2503621 Vivo EnergyS 4.29.2, -
service ys 5.2.28.2.2
23.502 5464 - Rel-19 On the report of SMF to EIF for F 19.3.0 S2-168 S2-2503631 Huawei, HiSilicon EnergyS 4.29.2, Revised
user-plane energy consumption ys 5.2.3.1
calculation
23.502 5464 1 Rel-19 On the report of SMF to EIF for F 19.3.0 S2-168 S2-2504003 Huawei, HiSilicon EnergyS 4.29.2, Revised
user-plane energy consumption ys 5.2.3.1
calculation
23.502 5464 2 Rel-19 On the report of SMF to EIF for F 19.3.0 S2-168 S2-2504305 Huawei, HiSilicon EnergyS 5.2.3.1 Agreed
user-plane energy consumption ys
calculation
23.502 5465 - Rel-19 Update the procedure for BDT F 19.3.0 S2-168 S2-2503637 Vivo EnergyS 4.16.7.2, -
policy decisions ys 5.2.5.5.2,
5.2.6.6.2
23.502 5466 - Rel-19 Correction about the Non-3GPP F 19.3.0 S2-168 S2-2503677 China Mobile UIA_AR 4.3.3.2 Revised
Device Connection Information C
23.502 5466 1 Rel-19 Correction about the Non-3GPP F 19.3.0 S2-168 S2-2504031 China Mobile UIA_AR 4.3.3.2 Merged
Device Connection Information C
23.502 5467 - Rel-19 Clarification on NRF Service F 19.3.0 S2-168 S2-2503682 ZTE NG_RTC 5.2.7.2.2, -
Related to MF _Ph2 5.2.7.3.2
23.502 5468 - Rel-19 EIF discvoery and selection F 19.3.0 S2-168 S2-2503735 Samsung EnergyS 5.2.7.2.2, -
ys 5.2.7.3.2
23.502 5469 - Rel-19 Clarifications on SMF event for F 19.3.0 S2-168 S2-2503736 Samsung EnergyS 5.2.8.3.1 -
information for energy ys
consumption calculation
23.502 5470 - Rel-19 Energy consumption F 19.3.0 S2-168 S2-2503740 Samsung EnergyS 4.29.2 Revised
information for access type ys
23.502 5470 1 Rel-19 Energy consumption F 19.3.0 S2-168 S2-2504005 Samsung EnergyS 4.29.2 Revised
information for access type ys
23.502 5470 2 Rel-19 Energy consumption F 19.3.0 S2-168 S2-2504317 Samsung EnergyS 4.29.2 Revised
information for access type ys
23.502 5470 3 Rel-19 Energy consumption F 19.3.0 S2-168 S2-2504341 Samsung, NTT EnergyS 4.29.2 Agreed
information for access type DOCOMO ys
23.502 5471 - Rel-19 IP version used for MPQUIC-E F 19.3.0 S2-168 S2-2503752 Ericsson MASSS 4.22.2.1 Revised
23.502 5471 1 Rel-19 IP version used for MPQUIC-E F 19.3.0 S2-168 S2-2504387 Ericsson MASSS 4.22.2.1 Revised
23.502 5471 2 Rel-19 IP version used for MPQUIC-E F 19.3.0 S2-168 S2-2504407 Ericsson, LGE, CATT, MASSS 4.22.2.1 Revised
Mediatek?, China
Mobile, Nokia, Apple

3GPP
Report of meeting S2-168

Spec CR R Rel Subject Ca Vsn Mtg TD Source Work Aff Cl Status OAffS
t Item p
23.502 5471 3 Rel-19 IP version used for MPQUIC-E F 19.3.0 S2-168 S2-2504408 Ericsson, LG MASSS 4.22.2.1 Agreed
Electronics, CATT,
MediaTek Inc., China
Mobile, Nokia, Apple,
Samsung, CableLabs,
Deutsche Telekom
23.502 5472 - Rel-19 Alignment of Energy indicator in F 19.3.0 S2-168 S2-2503780 China Mobile EnergyS 5.2.6.6.2, -
BDT policy ys 5.2.5.5.2,
4.16.7.2
23.502 5473 - Rel-19 Energy subscription termination F 19.3.0 S2-168 S2-2503781 China Mobile EnergyS 4.29.2, Merged
and event exposure in SMF ys 5.2.8.3.1
23.502 5474 - Rel-19 Support of providing MMSID F 19.3.0 S2-168 S2-2503785 China Mobile XRM_Ph 4.3.3.2 -
from 5GC to NG-RAN 2
23.502 5475 - Rel-19 Collection of energy F 19.3.0 S2-168 S2-2503809 Samsung EnergyS 4.29.2, Merged
consumption information for ys 5.2.8.3.2
new PDU session
23.502 5476 - Rel-19 Correcting references to TS F 19.3.0 S2-168 S2-2503825 Nokia XRM_Ph 4.3.3.2, -
23.501 clauses 2 4.15.6.6a
23.502 5477 - Rel-19 Clarifications on I-SMF insertion F 19.3.0 S2-168 S2-2503850 Nokia eEDGE_ 4.23.12.1, Revised
for PDU Session Mobility 5GC_Ph 4.23.13.1,
3 4.23.15
23.502 5477 1 Rel-19 Clarifications on I-SMF insertion F 19.3.0 S2-168 S2-2503928 Nokia eEDGE_ 4.23.13.1, Agreed
for PDU Session Mobility 5GC_Ph 4.23.15
3
23.502 5478 - Rel-19 SMF event on simultaneous F 19.3.0 S2-168 S2-2503852 Nokia EDGE_P 4.3.6.3, Revised
connectivity failure h2 5.2.8.3.1
23.502 5478 1 Rel-19 SMF event on simultaneous F 19.3.0 S2-168 S2-2503919 Nokia EDGE_P 4.3.6.3, Noted
connectivity failure h2 5.2.8.3.1
23.502 5478 2 Rel-19 SMF event on simultaneous F 19.3.0 S2-168 S2-2504173 Nokia EDGE_P 4.3.6.3, Withdrawn
connectivity failure h2 5.2.8.3.1
23.502 5479 - Rel-19 Add MWAB indication to NEF F 19.3.0 S2-168 S2-2504111 Nokia VMR_Ph 4.15.3.1 Postponed
monitoring events 2
23.502 5480 - Rel-19 On the report of SMF to EIF for F 19.3.0 S2-168 S2-2503997 Huawei, HiSilicon EnergyS 4.29.2 Revised
user-plane energy consumption ys
calculation
23.502 5480 1 Rel-19 On the report of SMF to EIF for F 19.3.0 S2-168 S2-2504298 Huawei, HiSilicon, NEC EnergyS 4.29.2 Agreed
user-plane energy consumption ys
calculation
23.503 1251 1 Rel-18 Clarifications for multi-modal F 18.9.0 S2-168 S2-2504251 Huawei, HiSilicon, Nokia XRM 3.1, Noted
0 services 6.1.3.27.3
23.503 1251 7 Rel-18 Clarifications for multi-modal F 18.9.0 S2-168 S2-2503509 Huawei, HiSilicon, XRM 3.1, Revised
services Nokia, ZTE 6.1.3.27.3
23.503 1251 8 Rel-18 Clarifications for multi-modal F 18.9.0 S2-168 S2-2503898 Huawei, HiSilicon, XRM 3.1, Revised
services Nokia, ZTE 6.1.3.27.3
23.503 1251 9 Rel-18 Clarifications for multi-modal F 18.9.0 S2-168 S2-2504228 Huawei, HiSilicon, XRM 3.1, Revised
services Nokia, ZTE 6.1.3.27.3

3GPP
Report of meeting S2-168

Spec CR R Rel Subject Ca Vsn Mtg TD Source Work Aff Cl Status OAffS
t Item p
23.503 1357 3 Rel-19 Clarifications for multi-modal A 19.3.0 S2-168 S2-2503510 Huawei, HiSilicon, Nokia XRM 3.1, Noted
services 6.1.3.27.3
23.503 1357 4 Rel-19 Clarifications for multi-modal A 19.3.0 S2-168 S2-2503899 Huawei, HiSilicon, Nokia XRM 3.1, Withdrawn
services 6.1.3.27.3
23.503 1492 4 Rel-19 Corrections for energy saving F 19.3.0 S2-168 S2-2503627 Huawei, HiSilicon, NTT EnergyS 6.1.2.4 -
related AF input on BDT policy DOCOMO, KDDI ys
negotiation
23.503 1515 1 Rel-18 Clarifications and corrections F 18.9.0 S2-168 S2-2503515 Huawei, HiSilicon XRM 6.1.3.22, Revised
for ECN marking for L4S and 6.1.3.27.1
congestion monitoring
23.503 1515 2 Rel-18 Clarifications and corrections F 18.9.0 S2-168 S2-2504154 Huawei, HiSilicon XRM 6.1.3.22, Revised
for ECN marking for L4S and 6.1.3.27.1
congestion monitoring
23.503 1515 3 Rel-18 Clarifications and corrections F 18.9.0 S2-168 S2-2504226 Huawei, HiSilicon XRM 6.1.3.22, Revised
for ECN marking for L4S and 6.1.3.27.1
congestion monitoring
23.503 1515 4 Rel-18 Clarifications and corrections F 18.9.0 S2-168 S2-2504249 Huawei, HiSilicon XRM 6.1.3.22, Agreed
for ECN marking for L4S and 6.1.3.27.1
congestion monitoring
23.503 1516 1 Rel-19 Clarifications and corrections A 19.3.0 S2-168 S2-2503516 Huawei, HiSilicon XRM 6.1.3.22, Revised
for ECN marking for L4S and 6.1.3.27.1
congestion monitoring
23.503 1516 2 Rel-19 Clarifications and corrections A 19.3.0 S2-168 S2-2504155 Huawei, HiSilicon XRM 6.1.3.22, Agreed
for ECN marking for L4S and 6.1.3.27.1
congestion monitoring
23.503 1526 - Rel-18 Update network slice F 18.9.0 S2-168 S2-2502874 Oracle, Verizon eNS_Ph 6.1.3.5 Revised
replacement PCRT 3, TEI18
23.503 1526 1 Rel-18 Update network slice F 18.9.0 S2-168 S2-2504141 Oracle, Verizon eNS_Ph 6.1.3.5 Agreed
replacement PCRT 3, TEI18
23.503 1527 - Rel-19 Update network slice A 19.3.0 S2-168 S2-2502875 Oracle, Verizon eNS_Ph 6.1.3.5 Revised
replacement PCRT 3, TEI19
23.503 1527 1 Rel-19 Update network slice A 19.3.0 S2-168 S2-2504142 Oracle, Verizon eNS_Ph 6.1.3.5 Agreed
replacement PCRT 3, TEI19
23.503 1528 - Rel-19 Results of QoS differention for F 19.3.0 S2-168 S2-2502903 Ericsson, AT&T UIA_AR 6.1.3.31, -
multiple Non-3GPP devices C 6.4
23.503 1529 - Rel-19 Providing device identifier F 19.3.0 S2-168 S2-2502988 Google UIA_AR 6.1.3.5, -
information in PDU session C 6.1.3.31
modification request
23.503 1530 - Rel-19 Adding a Reference to the F 19.3.0 S2-168 S2-2503000 InterDigital Inc., LG UIA_AR 6.1.3.31 Agreed
Home Routed Roaming PDU Electronics, Samsung, C
Session Modification Procedure Nokia
23.503 1531 - Rel-19 23.503 Support of uplink rate B 19.3.0 S2-168 S2-2503007 Lenovo XRM_Ph 6.1.3.2.4, -
control for QoS flows at RAN 2 6.1.3.27.X,
6.3.1

3GPP
Report of meeting S2-168

Spec CR R Rel Subject Ca Vsn Mtg TD Source Work Aff Cl Status OAffS
t Item p
23.503 1532 - Rel-19 Clarification on AF requested F 19.3.0 S2-168 S2-2503127 Huawei, HiSilicon TEI19_Sl 6.1.2.6.1, Revised
network slice replacement iceSel 6.1.2.6.2,
6.1.3.18
23.503 1532 1 Rel-19 Clarification on AF requested F 19.3.0 S2-168 S2-2504151 Huawei, HiSilicon TEI19_Sl 6.1.2.6.1, Revised
network slice replacement iceSel 6.1.2.1.1
23.503 1532 2 Rel-19 Clarification on AF requested F 19.3.0 S2-168 S2-2504404 Huawei, HiSilicon TEI19_Sl 6.1.2.6.1, Revised
network slice replacement iceSel 6.1.2.1.1
23.503 1532 3 Rel-19 Clarification on AF requested F 19.3.0 S2-168 S2-2504478 Huawei, HiSilicon TEI19_Sl 6.1.2.6.1, Agreed
network slice replacement iceSel 6.1.2.1.1
23.503 1533 - Rel-19 Correction concerning presence F 19.3.0 S2-168 S2-2503206 Ericsson XRM_Ph 6.1.3.27.4 Revised
of PDU Set Control information 2
without a Protocol Description
23.503 1533 1 Rel-19 Correction concerning presence F 19.3.0 S2-168 S2-2503939 Ericsson XRM_Ph 6.1.3.27.4 Revised
of PDU Set Control information 2
without a Protocol Description
23.503 1533 2 Rel-19 Correction concerning presence F 19.3.0 S2-168 S2-2504167 Ericsson XRM_Ph 6.1.3.27.4 Agreed
of PDU Set Control information 2
without a Protocol Description
23.503 1534 - Rel-19 MoQ missing from the Protocol F 19.3.0 S2-168 S2-2503207 Ericsson XRM_Ph 6.3.1 -
Description 2
23.503 1535 - Rel-19 Indication of Rate-Adaptable C 19.3.0 S2-168 S2-2503211 Ericsson NR_XR_ 5.37.1, -
QoS Flows to NG-RAN Ph3- 5.37.X
Core (new)
23.503 1536 - Rel-19 Inclusion of several Non-3GPP F 19.3.0 S2-168 S2-2503332 Nokia, InterDigital Inc., UIA_AR 6.1.3.31 -
Device Identifiers LG Electronics C
23.503 1537 - Rel-19 Terminology alignment for D 19.3.0 S2-168 S2-2503431 Huawei, HiSilicon MASSS 6.1.3.20 Revised
steering functionality(ies)
23.503 1537 1 Rel-19 Terminology alignment for D 19.3.0 S2-168 S2-2504358 Huawei, HiSilicon MASSS 6.1.3.20 Agreed
steering functionality(ies)
23.503 1538 - Rel-19 Indication of PDU Set QoS in F 19.3.0 S2-168 S2-2503435 Nokia XRM_Ph 6.1.3.5; Revised
Notification Control 2 6.1.3.18;
6.1.3.22
23.503 1538 1 Rel-19 Indication of PDU Set QoS in F 19.3.0 S2-168 S2-2503938 Nokia XRM_Ph 6.1.3.5; Withdrawn
Notification Control 2 6.1.3.18;
6.1.3.22
23.503 1539 - Rel-19 Clarification on the BDT policy F 19.3.0 S2-168 S2-2503456 ZTE EnergyS 6.1.2.4, -
decision ys 6.2.1.6
23.503 1540 - Rel-19 Clarification on the non-3gpp F 19.3.0 S2-168 S2-2503464 ZTE, Xiaomi UIA_AR 6.1.3.31 -
device identifier activation and C
removal
23.503 1541 - Rel-19 Simplification of clause 6.2.1.2 D 19.3.0 S2-168 S2-2503506 Huawei, HiSilicon 5GS_Ph 6.1.3.6, Agreed
1, TEI19 6.2.1.2
23.503 1542 - Rel-18 Clarifications for multi-modal F 18.9.0 S2-168 S2-2503511 Huawei, HiSilicon XRM - Withdrawn
services
23.503 1543 - Rel-19 Clarifications for multi-modal A 19.3.0 S2-168 S2-2503512 Huawei, HiSilicon XRM - Withdrawn
services

3GPP
Report of meeting S2-168

Spec CR R Rel Subject Ca Vsn Mtg TD Source Work Aff Cl Status OAffS
t Item p
23.503 1544 - Rel-19 Clarifications for multiplexed F 19.3.0 S2-168 S2-2503517 Huawei, HiSilicon XRM_Ph 6.1.3.27.7 -
media traffic 2
23.503 1545 - Rel-19 Clarifications for available F 19.3.0 S2-168 S2-2503520 Huawei, HiSilicon XRM_Ph 6.1.3.27.1 Revised
bitrate exposure 2
23.503 1545 1 Rel-19 Clarifications for available F 19.3.0 S2-168 S2-2503935 Huawei, HiSilicon XRM_Ph 6.1.3.27.1 Agreed
bitrate exposure 2
23.503 1546 - Rel-19 Clarifications for control of F 19.3.0 S2-168 S2-2503521 Huawei, HiSilicon XRM_Ph 6.1.3.27.9, -
expedited data transfer 2 6.3.1
23.503 1547 - Rel-19 Clarifications for rate limitation F 19.3.0 S2-168 S2-2503523 Huawei, HiSilicon XRM_Ph 6.1.3.18, Revised
exposure 2 6.1.3.27.1
23.503 1547 1 Rel-19 Clarifications for rate limitation F 19.3.0 S2-168 S2-2503936 Huawei, HiSilicon XRM_Ph 6.1.3.18, Revised
exposure 2 6.1.3.27.1
23.503 1547 2 Rel-19 Clarifications for rate limitation F 19.3.0 S2-168 S2-2504166 Huawei, HiSilicon XRM_Ph 6.1.3.18, Revised
exposure 2 6.1.3.27.1
23.503 1547 3 Rel-19 Clarifications for rate limitation F 19.3.0 S2-168 S2-2504481 Huawei, HiSilicon XRM_Ph 6.1.3.18, Agreed
exposure 2 6.1.3.27.1
23.503 1548 - Rel-19 Clarifications for QoS F 19.3.0 S2-168 S2-2503525 Huawei, HiSilicon XRM_Ph 6.1.3.5, Revised
Notification Control with 2 6.1.3.18,
direction information 6.1.3.22,
6.1.3.27.4,
6.3.1
23.503 1548 1 Rel-19 Clarifications for QoS F 19.3.0 S2-168 S2-2503942 Huawei, HiSilicon XRM_Ph 6.1.3.5, Revised
Notification Control with 2 6.1.3.18,
direction information 6.1.3.22,
6.1.3.27.4,
6.3.1
23.503 1548 2 Rel-19 Clarifications for QoS F 19.3.0 S2-168 S2-2504169 Huawei, HiSilicon XRM_Ph 6.1.3.5, Revised
Notification Control with 2 6.1.3.18,
direction information 6.1.3.22,
6.1.3.27.4,
6.3.1
23.503 1548 3 Rel-19 Clarifications for QoS F 19.3.0 S2-168 S2-2504420 Huawei, HiSilicon, Nokia XRM_Ph 6.1.3.5, Agreed
Notification Control with 2 6.1.3.18,
direction information 6.1.3.22,
6.1.3.27.4,
6.3.1
23.503 1549 - Rel-19 Policy Control on QoS F 19.3.0 S2-168 S2-2503590 CATT XRM_Ph 6.1.3.5, -
Notification Control of PDU Set 2 6.1.3.18,
QoS with only one direction 6.1.3.27.4
23.503 1550 - Rel-19 Activation of QoS monitoring for F 19.3.0 S2-168 S2-2503591 CATT TEI19, 6.1.3.21 Revised
the GBR service data flow XRM
23.503 1550 1 Rel-19 Activation of QoS monitoring for F 19.3.0 S2-168 S2-2503906 CATT TEI19, 6.1.3.2.4, Revised
the GBR service data flow XRM 6.1.3.21
23.503 1550 2 Rel-19 Activation of QoS monitoring for F 19.3.0 S2-168 S2-2504161 CATT, Huawei TEI19, 6.1.3.2.4, Agreed
the GBR service data flow XRM 6.1.3.21

3GPP
Report of meeting S2-168

Spec CR R Rel Subject Ca Vsn Mtg TD Source Work Aff Cl Status OAffS
t Item p
23.503 1551 - Rel-19 Clarificaiton on supporting F 19.3.0 S2-168 S2-2503607 Huawei, HiSilicon UIA_AR 6.1.3.31 Revised
multiple non-3GPP device C
identifiers
23.503 1551 1 Rel-19 Clarificaiton on supporting F 19.3.0 S2-168 S2-2504024 Huawei, HiSilicon UIA_AR 6.1.3.31 Revised
multiple non-3GPP device C
identifiers
23.503 1551 2 Rel-19 Clarificaiton on supporting F 19.3.0 S2-168 S2-2504255 Huawei, HiSilicon, UIA_AR 6.1.3.31 Revised
multiple non-3GPP device Samsung C
identifiers
23.503 1551 3 Rel-19 Clarificaiton on supporting F 19.3.0 S2-168 S2-2504333 Huawei, HiSilicon, UIA_AR 6.1.3.31 Revised
multiple non-3GPP device Samsung, Deutsche C
identifiers Telekom, Nokia, LGE,
Charter, ZTE
23.503 1551 4 Rel-19 Clarificaiton on supporting F 19.3.0 S2-168 S2-2504477 Huawei, HiSilicon, UIA_AR 6.1.3.31 Agreed
multiple non-3GPP device Samsung, Deutsche C
identifiers Telekom, Nokia, LGE,
Charter
Communications, ZTE
23.503 1552 - Rel-19 Clarification on notifying the F 19.3.0 S2-168 S2-2503618 ZTE TEI19_Sl 6.1.2.6.1, Revised
outcome of network slice iceSel 6.1.2.6.2,
replacement to AF 6.1.3.18
23.503 1552 1 Rel-19 Clarification on notifying the F 19.3.0 S2-168 S2-2504146 ZTE TEI19_Sl 6.1.2.6.1, Agreed
outcome of network slice iceSel 6.1.2.6.2
replacement to AF
23.503 1553 - Rel-19 Clarification of providing F 19.3.0 S2-168 S2-2503786 China Mobile XRM_Ph 6.1.3.2.4, -
MMSID from 5GC to NG-RAN 2 6.1.3.27.3,
6.3.1
23.503 1554 - Rel-19 XRM_Ph2_Clarification on the F 19.3.0 S2-168 S2-2503884 Xiaomi XRM_Ph 6.1.3.27.4 -
DL Protocol Description 2
23.548 0288 1 Rel-19 KI#1: Clarfication on the I-SMF F 19.2.0 S2-168 S2-2503404 Huawei, HiSilicon, eEDGE_ 6.10.1 Revised
selected for local offloading Samsung 5GC_Ph
managment 3
23.548 0288 2 Rel-19 KI#1: Clarfication on the I-SMF F 19.2.0 S2-168 S2-2503921 Huawei, HiSilicon, eEDGE_ 6.10.1 Postponed
selected for local offloading Samsung 5GC_Ph
managment 3
23.548 0297 1 Rel-19 Clarification on SMF triggered I- F 19.2.0 S2-168 S2-2502895 Nokia eEDGE_ 6.10.2.x Postponed
SMF insertion or removal for 5GC_Ph (new)
Local Offloading Management 3
23.548 0302 - Rel-19 KI#1 Clarification on EAS F 19.2.0 S2-168 S2-2503259 OPPO eEDGE_ 6.10.2.X Noted
Discovery using IP replacement 5GC_Ph
to support Local Offloading 3
Management
23.548 0303 - Rel-19 Clarification on the Local F 19.2.0 S2-168 S2-2503395 LG Electronics eEDGE_ 6.10.2.2 Noted
Offloading Management 5GC_Ph
Service Area 3

3GPP
Report of meeting S2-168

Spec CR R Rel Subject Ca Vsn Mtg TD Source Work Aff Cl Status OAffS
t Item p
23.548 0304 - Rel-19 Clarification on the AF F 19.2.0 S2-168 S2-2503397 LG Electronics eEDGE_ 6.10.1 Noted
trafficInfluence information from 5GC_Ph
SMF to I-SMF 3
23.548 0305 - Rel-19 Interaction between SMF and I- F 19.2.0 S2-168 S2-2503408 Huawei, Hisilicon eEDGE_ 6.10.1, Revised
SMF 5GC_Ph 6.10.2.3,
3 6.10.2.4
23.548 0305 1 Rel-19 Interaction between SMF and I- F 19.2.0 S2-168 S2-2503929 Huawei, Hisilicon eEDGE_ 6.10.2.4 Revised
SMF 5GC_Ph
3
23.548 0305 2 Rel-19 Interaction between SMF and I- F 19.2.0 S2-168 S2-2504179 Huawei, Hisilicon eEDGE_ 6.10.2.4 Agreed
SMF 5GC_Ph
3
23.548 0306 - Rel-19 Correction of local offloading F 19.2.0 S2-168 S2-2503499 China Mobile eEDGE_ 6.10.2.2 Revised
management 5GC_Ph
3
23.548 0306 1 Rel-19 Correction of local offloading F 19.2.0 S2-168 S2-2503924 China Mobile eEDGE_ 6.10.2.2 Revised
management 5GC_Ph
3
23.548 0306 2 Rel-19 Correction of local offloading F 19.2.0 S2-168 S2-2504175 China Mobile eEDGE_ 6.10.2.2 Agreed
management 5GC_Ph
3
23.548 0307 - Rel-19 UE mobility for local offloading F 19.2.0 S2-168 S2-2503500 China Mobile eEDGE_ 6.10.2.4 Revised
management 5GC_Ph
3
23.548 0307 1 Rel-19 UE mobility for local offloading F 19.2.0 S2-168 S2-2503925 China Mobile eEDGE_ 6.10.2.4 Revised
management 5GC_Ph
3
23.548 0307 2 Rel-19 UE mobility for local offloading F 19.2.0 S2-168 S2-2504176 China Mobile eEDGE_ 6.10.2.4 Revised
management 5GC_Ph
3
23.548 0307 3 Rel-19 UE mobility for local offloading F 19.2.0 S2-168 S2-2504181 China Mobile eEDGE_ 6.10.2.4 Agreed
management 5GC_Ph
3
23.548 0308 - Rel-19 Clarification for Local offloading F 19.2.0 S2-168 S2-2503614 ZTE eEDGE_ 6.10.3.2 Revised
management policy 5GC_Ph
3
23.548 0308 1 Rel-19 Clarification for Local offloading F 19.2.0 S2-168 S2-2503922 ZTE eEDGE_ 6.10.3.2 Revised
management policy 5GC_Ph
3
23.548 0308 2 Rel-19 Clarification for Local offloading F 19.2.0 S2-168 S2-2504174 ZTE eEDGE_ 6.10.3.2 Revised
management policy 5GC_Ph
3
23.548 0308 3 Rel-19 Clarification for Local offloading F 19.2.0 S2-168 S2-2504233 ZTE eEDGE_ 6.10.3.2 Revised
management policy 5GC_Ph
3

3GPP
Report of meeting S2-168

Spec CR R Rel Subject Ca Vsn Mtg TD Source Work Aff Cl Status OAffS
t Item p
23.548 0308 4 Rel-19 Clarification for Local offloading F 19.2.0 S2-168 S2-2504246 ZTE eEDGE_ 6.10.3.2 Agreed
management policy 5GC_Ph
3
23.548 0309 - Rel-19 Clarification on handling F 19.2.0 S2-168 S2-2503699 Samsung eEDGE_ 6.10.2.3 Revised
application not matched with 5GC_Ph
LOM policy 3
23.548 0309 1 Rel-19 Clarification on handling F 19.2.0 S2-168 S2-2503927 Samsung eEDGE_ 6.10.2.3 Revised
application not matched with 5GC_Ph
LOM policy 3
23.548 0309 2 Rel-19 Clarification on handling F 19.2.0 S2-168 S2-2504177 Samsung eEDGE_ 6.10.2.3 Agreed
application not matched with 5GC_Ph
LOM policy 3
23.548 0310 - Rel-19 Clarification on I-SMF operation F 19.2.0 S2-168 S2-2503700 Samsung eEDGE_ 6.9 Revised
for N6 Delay Measurement 5GC_Ph
3
23.548 0310 1 Rel-19 Clarification on I-SMF operation F 19.2.0 S2-168 S2-2503920 Samsung eEDGE_ 6.9 Agreed
for N6 Delay Measurement 5GC_Ph
3
23.548 0311 - Rel-19 Corrections on Local Offloading F 19.2.0 S2-168 S2-2503851 Nokia eEDGE_ 6.10.1, Revised
Management related indications 5GC_Ph 6.10.2.2
3
23.548 0311 1 Rel-19 Corrections on Local Offloading F 19.2.0 S2-168 S2-2504178 Nokia eEDGE_ 6.10.1, Agreed
Management related indications 5GC_Ph 6.10.2.2
3
23.682 0498 - Rel-19 Clarify the S&F event is sent F 19.2.0 S2-168 S2-2503753 Ericsson 5GSAT_ 5.6.3.10 -
from SCEF to SCS/AS Ph3-ARC
23.682 0499 - Rel-19 Align the terms. F 19.2.0 S2-168 S2-2503887 Samsung 5GSAT_ 5.6.3.10 -
Ph3-ARC
840 Entries

B.3 List of approved P-CRs

Table B.3: List of approved P-CRs

Mtg Spec Rel Subject TD Source Work Item Status

S2-168 23.369 Rel-19 PCR for TS 23.369: Update of Device ID for NID. S2-2504281 Huawei, HiSilicon AmbientIoT- Approved
ARC
S2-168 23.369 Rel-19 PCR for TS 23.369: AIoT Reference Point Naming . S2-2504012 Huawei, HiSilicon, Ericsson AmbientIoT- Approved
ARC
S2-168 23.369 Rel-19 AIOTF selection. S2-2504291 CATT, Samsung, Ericsson, Lenovo, vivo AmbientIoT- Approved
ARC

3GPP
Report of meeting S2-168

Mtg Spec Rel Subject TD Source Work Item Status

S2-168 23.369 Rel-19 Terminology Alignment. S2-2504319 Ericsson, Huawei, HiSilicon, OPPO, Deutsche AmbientIoT- Approved
Telekom ARC
S2-168 23.369 Rel-19 AMF selection. S2-2504290 Vivo, Samsung AmbientIoT- Approved
ARC
S2-168 23.369 Rel-19 PCR for TS 23.369: AIoT Reader Selection. S2-2504289 China Mobile, ZTE, Futurewei, Samsung, AmbientIoT- Approved
Lenovo, Interdigital, CATT, NEC ARC
S2-168 23.369 Rel-19 Clause 4.2.2 & 4.3: Reference Point Definition. S2-2504013 Ericsson, Tejas Networks, CEWiT, Samsung AmbientIoT- Approved
ARC
S2-168 23.369 Rel-19 PCR to TS 23.xyz: Filtering Information. S2-2504283 Vivo, Futurewei AmbientIoT- Approved
ARC
S2-168 23.369 Rel-19 Update to Inventory procedure regarding AIOTF selection . S2-2504292 InterDigital Inc. AmbientIoT- Approved
ARC
S2-168 23.369 Rel-19 Clause 5.X: ADM Discovery and Selection. S2-2504275 Ericsson, Vivo AmbientIoT- Approved
ARC
S2-168 23.369 Rel-19 Clause 5.6 & 6.2.2 & 6.2.3: Resolve EN on AF Authorization. S2-2504280 Ericsson, Huawei, HiSilicon AmbientIoT- Approved
ARC
S2-168 23.369 Rel-19 Update on Command procedure. S2-2504286 CATT, Lenovo, vivo, Samsung, NTT AmbientIoT- Approved
DOCOMO INC., Sony, Huawei, InterDigital ARC
Inc., OPPO
S2-168 23.369 Rel-19 PCR for TS 23.369: Update Inventory Procedure. S2-2504318 Huawei, HiSilicon, CATT, OPPO AmbientIoT- Approved
ARC
S2-168 23.369 Rel-19 PCR for TS 23.369: Improve AIoT Device Profile Management. S2-2504321 Huawei, HiSilicon, Samsung AmbientIoT- Approved
ARC
S2-168 23.369 Rel-19 Clause 5.4 updates. S2-2504320 LG Electronics, Futurewei, NTT DOCOMO, AmbientIoT- Approved
InterDigital, Ericsson, ZTE, Lenovo, OPPO, ARC
CATT, Huawei, Nokia, MediaTek Inc., vivo,
Samsung, CEWiT, NEC, China Mobile
S2-168 23.369 Rel-19 NF descriptions update for AIOTF and NRF. S2-2504287 Lenovo, China Telecom, NTT DOCOMO, AmbientIoT- Approved
Futurewei, Nokia ARC
S2-168 23.369 Rel-19 Structure for documenting indirect path and Direct path. S2-2504063 OPPO AmbientIoT- Approved
ARC
S2-168 23.700-04 Rel-20 Scope for FS_AIML_CN_Ph2. S2-2504193 Samsung (rapporteur), vivo (rapporteur) FS_AIML_C Approved
N_Ph2
S2-168 23.700-04 Rel-20 WT#2 Key Issue AI/ML-assisted user plane traffic pattern and S2-2504203 SK Telecom, China Mobile, China Telecom, FS_AIML_C Approved
behaviour analysis to support efficient performance of User Plane. Deutsche Telekom, KPN N.V., LG Uplus, N_Ph2
Verizon, Rakuten Mobile, NTT DOCOMO,
ETRI, ZTE, Huawei, Nokia, Samsung,
Ericsson
S2-168 23.700-04 Rel-20 Architectural Assumptions and Requirements for S2-2504195 Vivo(rapporteur), Samsung(rapporteur) FS_AIML_C Approved
FS_AIML_CN_Ph2. N_Ph2
S2-168 23.700-04 Rel-20 Solution for WT 1 General Framework for data collection from the S2-2504242 Lenovo FS_AIML_C Approved
UE. N_Ph2
S2-168 23.700-04 Rel-20 WT#2 use case AI/ML-assisted user plane traffic pattern and S2-2504236 SK Telecom, China Mobile, China Telecom, FS_AIML_C Approved
behaviour analysis to support efficient performance of User Plane. Deutsche Telekom, KPN N.V., LG Uplus, N_Ph2
Verizon, Rakuten Mobile, NTT DOCOMO,
ETRI, ZTE, Huawei, Nokia, Samsung,
Ericsson

3GPP
Report of meeting S2-168

Mtg Spec Rel Subject TD Source Work Item Status

S2-168 23.700-04 Rel-20 KI#1: New Solution UE data collection via DCCF in CN over UP. S2-2504238 Vivo, Samsung FS_AIML_C Approved
N_Ph2
S2-168 23.700-04 Rel-20 TR Skeleton for FS_AIML_CN_Ph2 S2-2504192 Samsung, vivo FS_AIML_C Approved
N_Ph2
S2-168 23.700-04 Rel-20 UP building for UE training data collection. S2-2504422 ZTE FS_AIML_C Approved
N_Ph2
S2-168 23.700-04 Rel-20 New use case for WT2: user plane performance optimization with S2-2504421 Huawei, HiSilicon, CMCC, SK Telecom, ZTE FS_AIML_C Approved
assistance of NWDAF. N_Ph2
S2-168 23.700-04 Rel-20 New Key Issue for transfer of data over UP for UE data collection. S2-2504235 Vivo(rapporteur), Samsung(rapporteur) FS_AIML_C Approved
N_Ph2
S2-168 23.700-04 Rel-20 KI#1, New Sol#X: Generalized UE data collection over user plane . S2-2504241 LG Electronics FS_AIML_C Approved
N_Ph2
S2-168 23.700-14 Rel-20 New Key Issue on Sensing Architecture . S2-2504325 Apple, LG Electronics, Xiaomi, NTT FS_Sensing_ Approved
DOCOMO, Nokia, Nokia Shanghai Bell, ZTE, ARC
CeWIT
S2-168 23.700-14 Rel-20 TR Scope for FS_Sensing_ARC . S2-2504048 Apple, Xiaomi FS_Sensing_ Approved
ARC
S2-168 23.700-14 Rel-20 23.700-14: Key issue X: Sensing data and the associated S2-2504328 OPPO, ZTE, Xiaomi, ETRI, Lenovo, Intel, FS_Sensing_ Approved
information collection and transport. NTT Docomo, Futurewei, Nokia, Nokia ARC
Shanghai Bell, CATT, Huawei, HiSilicon,
CEWiT
S2-168 23.700-14 Rel-20 Terms of Sensing study. S2-2504331 Huawei, HiSilicon, Ofinno, Lenovo, Deutsche FS_Sensing_ Approved
Telekom, Apple, Nokia, Nokia Shanghai Bell, ARC
CEWiT, NTT DOCOMO
S2-168 23.700-14 Rel-20 TR 23.700-14: FS_Sensing-ARC new key issues. S2-2504326 Qualcomm Incorporated, Futurewei, China FS_Sensing_ Approved
Telecom, Xiaomi, vivo, Apple, Samsung, NTT ARC
DOCOMO, ETRI, ZTE, InterDigital, Nokia,
Nokia Shanghai Bell. Huawei, HiSilicon,
CEWiT
S2-168 23.700-14 Rel-20 Adding Architecture requirements. S2-2504322 Ericsson, NTT DOCOMO, Samsung, Nokia, FS_Sensing_ Approved
Nokia Shanghai Bell, LG Electronics, ZTE, ARC
Xiaomi, Google, Ofinno, CEWiT, InterDigital
Inc., Apple, CATT
S2-168 23.700-14 Rel-20 Key Issue 5: Sensing result exposure. S2-2504329 China Mobile, CATT, Apple, Nokia, Nokia FS_Sensing_ Approved
Shanghai Bell, Huawei, HiSilicon, Samsung, ARC
ZTE, vivo, InterDigital, ETRI, NTT DOCOMO,
Futurewei, CEWiT, Xiaomi, Lenovo
S2-168 23.700-14 Rel-20 Key Issue for WT#6 Configuration parameter provisioning . S2-2504330 Sony, OPPO, Samsung, China Mobile Com. FS_Sensing_ Approved
Corporation, Nokia, Nokia Shanghai Bell, NTT ARC
DOCOMO, CEWiT, Futurewei, DT
S2-168 23.700-14 Rel-20 Architectural Assumptions for sensing service. S2-2504323 China Telecom, LG Electronics, Huawei, ZTE, FS_Sensing_ Approved
Ericsson, OPPO, China Mobile, Xiaomi, ARC
Samsung, Nokia, Nokia Shanghai Bell,
Ofinno, CATT, Deutsche Telekom, Futurewei,
NTT DOCOMO, Lenovo, vivo, Apple, CEWiT,
MTK
S2-168 23.700-14 Rel-20 TR Skeleton for FS_Sensing_ARC S2-2504047 Apple, Xiaomi FS_Sensing_ Approved
ARC

3GPP
Report of meeting S2-168

Mtg Spec Rel Subject TD Source Work Item Status

S2-168 23.700-14 Rel-20 Key issue for WT#3 Sensing entities discovery and selection. S2-2504327 Vivo, China Mobile, Xiaomi, Sony, OPPO, FS_Sensing_ Approved
Qualcomm Incorporated, China Telecom, ARC
Huawei, HiSilicon, ZTE, ETRI, Nokia, Nokia
Shanghai Bell, InterDigital Inc, Apple,
Futurewei, NTT DOCOMO, Ofinno, CEWiT
S2-168 23.700-19 Rel-20 FS_5GSAT_Ph4_ARC Key issues for WT#1. S2-2504223 CATT, vivo, SAMSUNG, TNO FS_5GSAT_ Approved
Ph4_ARC
S2-168 23.700-19 Rel-20 FS_5GSAT_Ph4_ARC TR Skeleton. S2-2504185 CATT FS_5GSAT_ Approved
Ph4_ARC
S2-168 23.700-19 Rel-20 FS_5GSAT_Ph4_ARC TR Scope. S2-2504186 CATT FS_5GSAT_ Approved
Ph4_ARC
S2-168 23.700-19 Rel-20 [AA] Architecture assumptions. S2-2504188 Huawei, HiSilicon, TNO, Samsung FS_5GSAT_ Approved
Ph4_ARC
S2-168 23.700-19 Rel-20 23.700-19: Architecture principles and assumptions for WT-1 . S2-2504187 Vivo, Qualcomm, CATT, CSCN, Xiaomi, FS_5GSAT_ Approved
Ericsson, Huawei, HiSilicon, Nokia, LG Ph4_ARC
Electronics, TNO, Samsung, OPPO, NTT
DOCOMO, China Telecom,
S2-168 23.700-67 Rel-20 Energy Optimization Trigger for PCF based Policy Control. S2-2504479 Ericsson FS_EnergyS Approved
ys_Ph2
S2-168 23.700-67 Rel-20 FS_EnergySys_Ph2 TR23700-67 Skeleton. S2-2504316 China Telecom, Lenovo (Rapporteur) FS_EnergyS Approved
ys_Ph2
S2-168 23.700-67 Rel-20 KI#2 new solution for policy control based on interactions with the S2-2504314 CATT FS_EnergyS Approved
EIF. ys_Ph2
S2-168 23.700-67 Rel-20 Solution for WT#2: Support of QoS adjustments. S2-2504344 MediaTek Inc., vivo FS_EnergyS Approved
ys_Ph2
S2-168 23.700-67 Rel-20 Architectural Assumptions and Principles for Energy Efficiency and S2-2504308 China Mobile, Lenovo, China Telecom FS_EnergyS Approved
Energy Saving. ys_Ph2
S2-168 23.700-67 Rel-20 KI#2, new sol: Service adjustments for network energy saving S2-2504345 Vivo FS_EnergyS Approved
based on AF request and energy information. ys_Ph2
S2-168 23.700-67 Rel-20 New Key issue for WT#1 On Enhancements of Energy-related S2-2504070 Nokia FS_EnergyS Approved
information exposure. ys_Ph2
S2-168 23.700-67 Rel-20 KI#2: New Sol: Energy-aware data transfer policy negotiation. S2-2504346 NTT DOCOMO FS_EnergyS Approved
ys_Ph2
S2-168 23.700-67 Rel-20 New Solution to WT#2: Enabling dynamic QoS handling for energy S2-2504347 Qualcomm Incorporated, vivo FS_EnergyS Approved
efficiency lterby use of Energy Saving QoS Profiles . ys_Ph2
S2-168 23.700-67 Rel-20 Key issue for WT#2: Support of service adjustments for the UE. S2-2504071 MediaTek Inc., Samsung, vivo FS_EnergyS Approved
ys_Ph2
S2-168 23.700-67 Rel-20 KI#1: new solution: P-CR on exposure of UE scoring data. S2-2504342 Nokia FS_EnergyS Approved
ys_Ph2
S2-168 23.700-67 Rel-20 New Key Issue: NF (re)selection and/or UP path adjustment based S2-2504072 China Mobile, Lenovo, China Telecom, NTT FS_EnergyS Approved
on energy related information. DOCOMO, InterDigital ys_Ph2
S2-168 23.700-67 Rel-20 FS_EnergySys_Ph2 TR23.700-67 Scope. S2-2503123 China Telecom, Lenovo (Rapporteur) FS_EnergyS Approved
ys_Ph2
57 Entries

3GPP
Report of meeting S2-168

ANNEX C List of Liaison Statements

C.1 Incoming liaison statements
Table C.1: Incoming liaison statements

TD From Title Orig_TD To CC Attachments Reply TD Status

S2-2502792 RAN WG1 LS from RAN WG1: Reply LS on data collection to R1-2405578 SA WG2 RAN WG2, RAN Postponed
enable ML model training and inference in 5GC for WG3.
Direct AI/ML based positioning
S2-2502793 RAN WG1 LS from RAN WG1: LS on signalling feasibility of R1-2410922 RAN WG2 SA WG2, SA Postponed
dataset and parameter sharing WG3
S2-2502794 RAN WG2 LS from RAN WG2: Reply LS on Application-Layer R2-2411002 SA WG2 SA WG4. Noted
FEC Awareness at RAN Attachments: -
S2-2502795 TSG RAN LS from TSG RAN: LS on AI/ML UE sided data RP-243316 TSG SA, SA RAN WG2 S2-2503563 Postponed
collection WG2
S2-2502796 SA WG4 LS from SA WG4: Reply LS on Clarification of DC S4-242111 SA WG2. Noted
Binding Information Attachments: -
S2-2502797 GSMA TSGNS LS from GSMA TSGNS: OSAppID usage by TSGNS44_003v6 SA WG2, SA S2-2504468 Noted
AppToken use case WG3
S2-2502798 CEN TC 278 WG LS from CEN TC 278 WG 15: LS on Next Generation 3GPP_LS_reply_ SA WG1, SA Postponed
15 eCall 2025-02-05 WG2, CT WG1,
TSG SA, TSG
CT, ETSI TC
MSG
S2-2502799 SA WG3 LS from SA WG3: Reply LS on security aspects of S3-251055 SA WG2 RAN WG2 S3-251048 Noted
Ambient IoT
S2-2502800 RAN WG3 LS from RAN WG3: Reply LS on FS_XRM Ph2 for R3-250806 SA WG2 Noted
available data rate report
S2-2502801 RAN WG2 LS from RAN WG2: Reply LS on Time R2-2501509 SA WG4, SA Noted
Synchronization for MBS WG2
S2-2502802 RAN WG2 LS from RAN WG2: Reply LS to SA WG2 on LMF- R2-2501507 SA WG2 RAN WG1, RAN Noted
based AI/ML Positioning for Case 2b WG3
S2-2502803 CT WG1 LS from CT WG1: LS on stage 1 requirements for the C1-250715 SA WG1 SA WG2, CT Postponed
support for PWS over satellite NGRAN in Rel-17 WG4, RAN WG2
S2-2502804 CT WG1 LS from CT WG1: Reply LS on request for IMS Data C1-250819 SA WG3-LI SA WG2, SA Noted
Channel related clarifications WG4
S2-2502805 CT WG1 LS from CT WG1: LS on PWS enhancements for C1-250820 SA WG2 RAN WG3 S2-2504383 Replied to
MWAB and MBSR
S2-2502806 CT WG1 LS from CT WG1: LS on support for multiple non- C1-250822 SA WG2 CT WG3 S2-2504337 Replied to
3GPP device identifiers
S2-2502807 CT WG1 LS from CT WG1: LS on multiplexing capability C1-250885 SA WG2 S2-2504209 Replied to
negotiation

3GPP
Report of meeting S2-168

TD From Title Orig_TD To CC Attachments Reply TD Status

S2-2502808 CT WG3 LS from CT WG3: LS on AF requested network slice C3-250572 SA WG2 S2-2504147 Replied to
replacement
S2-2502809 CT WG3 LS from CT WG3: LS reply on FS_IMS_RES C3-250657 CT WG4 CT WG1 Noted
outcome and future work plan
S2-2502810 CT WG3 LS from CT WG3: Reply LS on C3-250661 SA WG2 Noted
Nnef_RetrieveInfoUAVFlight_Get service operation
S2-2502811 CT WG4 LS from CT WG4: LS on Ethernet MA PDU session C4-250554 SA WG2 CT WG1 Postponed
using MPQUIC-E steering
S2-2502812 CT WG4 LS from CT WG4: LS on Security related protocol- C4-250555 SA WG3 CT WG3 Noted
specific parameters for N6 delay measurement
S2-2502813 CT WG4 LS from CT WG4: LS on New port number for LCS- C4-250590 CT WG1 TSG CT Noted
UPP
S2-2502814 CT WG4 LS from CT WG4: LS on MoQ Relay Address in UPF C4-250627 SA WG2 S2-2503908 Replied to
Profile
S2-2502815 CT WG4 LS from CT WG4: LS on Transport Level Marking on C4-250629 SA WG2 S2-2503209 Postponed
N3/N9
S2-2502816 CT WG4 LS from CT WG4: LS on Questions on stage 2 C4-250630 SA WG2 CT WG3 Postponed
requirements for AIML_CN
S2-2502817 TSG CT LS from TSG CT: LS reply to LS on energy CP-250253 SA WG5 TSG SA, SA Noted
information collection from OAM to EIF WG2, CT WG3
S2-2502818 RAN WG1 LS from RAN WG1: Reply LS on LMF-based AI/ML R1-2501523 SA WG2 RAN WG2 Noted
Positioning for Case 2b
S2-2502819 RAN WG1 LS from RAN WG1: Reply LS on LMF-based AI/ML R1-2500389 SA WG2 RAN WG2 Noted
Positioning for Case 3b
S2-2502820 RAN WG2 LS from RAN WG2: LS on uplink rate control R2-2501347 SA WG2 S2-2504252 Replied to
S2-2502821 RAN WG2 LS from RAN WG2: Reply LS on LP-WUS R2-2501388 SA WG2, RAN RAN WG1 Postponed
subgrouping WG3
S2-2502822 RAN WG2 LS from RAN WG2: Geofencing in ETWS for NR and R2-2501581 CT WG1 RAN WG3 Noted
NB-IoT NTN
S2-2502823 RAN WG2 LS from RAN WG2: Inclusion of NTN intended R2-2501583 SA WG4 SA WG2 S2-2502898 Noted
service area in the Service Announcement
S2-2502824 RAN WG2 LS from RAN WG2: LS to CT1 and CT4 on maximum R2-2501586 CT WG1 RAN WG3 Noted
warning message size
S2-2502825 RAN WG3 LS from RAN WG3: Reply LS on UE Location R3-250761 SA WG2 RAN WG2 Noted
Information for NB-IoT NTN
S2-2502826 RAN WG3 LS from RAN WG3: Reply LS on LMF-based AI/ML R3-250796 SA WG2 RAN WG1 Postponed
Positioning for case 3b
S2-2502827 RAN WG3 LS from RAN WG3: LS on security verification R3-250822 SA WG3 SA WG2 Noted
related to NR Femtos
S2-2502828 RAN WG3 LS from RAN WG3: LS on UAV regulation from R3-250876 SA WG2 S2-2504471 Replied to
RAN3
S2-2502829 RAN WG3 LS from RAN WG3: Reply LS on OAM requirements R3-250895 SA WG2 S2-2503231 Postponed
to support regenerative payload transport links
S2-2502830 RAN WG3 LS from RAN WG3: Reply LS on FS_VMR_Ph2 R3-250901 SA WG2 RAN WG2 S2-2504110 Replied to
solution impacts to RAN (Additional ULI)

3GPP
Report of meeting S2-168

TD From Title Orig_TD To CC Attachments Reply TD Status

S2-2502831 RAN WG3 LS from RAN WG3: Reply LS on Support of Location R3-250902 SA WG2 RAN WG2 Noted
Service Involving WAB-Nodes
S2-2502832 RAN WG3 LS from RAN WG3: LS on Ambient IoT progress of R3-250905 SA WG2 S2-2504288 Replied to
RAN WG3
S2-2502835 SA WG3 LS from SA WG3: Reply LS on Device Subscription S3-251102 SA WG2 Noted
Data
S2-2502836 SA WG3 LS from SA WG3: LS on Privacy and security S3-251144 SA WG2 S2-2504207 Replied to
aspects regarding DC management by the network
S2-2502838 SA WG4 LS from SA WG4: LS on Advanced Media Delivery S4-250412 CT WG3 SA WG2 Noted
S2-2502839 SA WG5 LS from SA WG5: Reply to LS on A-IoT Conclusions S5-250680 SA WG2 TSG SA Noted
in SA WG2
S2-2502840 SA WG5 LS from SA WG5: Reply LS on ML Model S5-250826 SA WG2 S2-2504197 Replied to
provisioning by OAM to LMF for UE positioning
S2-2502841 SA WG5 LS from SA WG5: Reply LS on AI/ML UE sided data S5-250828 TSG RAN TSG SA, SA Postponed
collection WG2
S2-2502842 SA WG5 LS from SA WG5: Reply LS to LS on reply to LS on S5-250842 SA WG2 RAN WG3 S2-2503231 Postponed
OAM requirements to support regenerative payload
S2-2502843 SA WG5 LS from SA WG5: LS reply to LS on energy S5-250843 SA WG2 TSG SA Noted
information collection from OAM to EIF
S2-2502844 SA WG5 LS from SA WG5: LS on MWAB-gNB Configurations S5-251090 SA WG2 RAN WG3 S2-2504380 Replied to
S2-2502845 SA WG6 LS from SA WG6: LS on Generation of AF specific S6-250286 SA WG2 CT WG3 S2-2504396 Replied to
UE ID
S2-2502846 TSG SA LS from TSG SA: Reply LS on support of multiple SP-250329 GSMA NG SA WG1, SA Noted
access technologies based on the IMS service type WG2
S2-2502847 GSMA TSG LS from GSMA TSG IMSDCAS: LS to SA WG2 IMSDCAS022_00 SA WG2 SA WG4, CT S2-2503170 Postponed
IMSDCAS About Requirements Concerning Automatic Resume 5v5 WG1
Where You have Left Off
S2-2502848 ETSI ISG NFV LS from ETSI ISG NFV: Publication of ETSI NFV NFV(25)000019r2 SA WG2, SA TSG SA Noted
group report on architectural support for NFV WG5
evolution
S2-2502849 CT WG4 LS from CT WG4: LS on Optimizations to UPF event C4-250455 SA WG2, CT TR 29.889-v0.4.0 S2-2504469 Replied to
subscriptions and reporting WG3
S2-2502850 SA WG3 LS from SA WG3: LS on UIA Rel-20 in response to S3-251673 SA WG2, TSG Postponed
SA guidance from SA#107 SA
56 Entries

3GPP
Report of meeting S2-168

C.2 Approved Outgoing liaison statements

Table C.2: Approved Outgoing liaison statements

TD Title To CC Attachments Reply to TD Status

S2-2503908 LS Reply to CT WG4 on MoQ Relay Address in UPF CT WG4 S2-2503907(CR6181) S2-2502814 Approved
Profile (C4-250627)
S2-2504110 Reply LS on FS_VMR_Ph2 solution impacts to RAN RAN WG3 RAN WG2 CR 6264 to TS 23.501 (S2- S2-2502830 Approved
(Additional ULI) 2503813) (R3-250901)
S2-2504147 LS Response on AF requested network slice CT WG3 TS 23.502 CR 5415 (S2- S2-2502808 Approved
replacement 2504370), TS 23.503 CR (C3-250572)
1552 (S2-2504146)
S2-2504197 Reply LS on ML Model provisioning by OAM to LMF SA WG5 S2-2502818/S2-2502819 S2-2502840 Approved
for UE positioning (S5-250826)
S2-2504207 Reply LS on Privacy and security aspects regarding SA WG3 CT WG1 TS 23.228 CR#1635 (S2- S2-2502836 Approved
DC management by the network 2504214) (S3-251144)
S2-2504209 Reply LS on multiplexing capability negotiation CT WG1 CR 1622 vs TS 23.228 (S2- S2-2502807 Approved
2504208) (C1-250885)
S2-2504252 LS reply on uplink rate control RAN WG2 RAN WG3, SA S2-2502820 Approved
WG4 (R2-2501347)
S2-2504288 LS Reply on Ambient IoT progress of RAN WG3 RAN WG3 SA WG5 S2-2502832 Approved
(R3-250905)
S2-2504294 LS on the need of indication of follow-up Command RAN WG2, RAN RAN WG1 Approved
procedure in Inventory request WG3
S2-2504296 LS on AIoT device identifier length CT WG4 RAN WG2, RAN S2-2504281 Approved
WG3
S2-2504337 LS reply on support for multiple non-3GPP device CT WG1 CT WG3 S2-2504253: TS 23.501 CR# S2-2502806 Approved
identifiers 6208, S2-2504336: TS (C1-250822)
23.502 CR# 5383, S2-
2504477: TS 23.503 CR#
1551
S2-2504380 Reply LS on MWAB-gNB Configurations SA WG5 RAN WG3 CR 6270 to TS 23.501 S2-2502844 Approved
(S5-251090)
S2-2504383 Reply LS on PWS enhancement for MWAB and CT WG1 RAN WG3 Rel-18: 23.501 CR6211, S2-2502805 Approved
MBSR 23.502 CR5416; Rel-19: (C1-250820)
23.501 CR6087, 23.502
CR5446
S2-2504396 Reply LS on generation of AF specific UE ID SA WG6 CT WG3 23.501 CR 6168, 23.502 CR S2-2502845 Approved
5413 (S6-250286)
S2-2504468 Reply LS on OSAppID usage by AppToken use case TSG SA SA WG3 S2-2502797 Approved
(TSGNS44_0
03v6)
S2-2504469 LS on Optimizations to UPF event subscriptions and CT WG4 CT WG3 S2-2502849 Approved
reporting (C4-250455)
S2-2504471 Reply LS on UAV regulation from RAN WG3 RAN WG3 TS 23.256 CR#0199, S2-2502828 Approved
CR#0194 (R3-250876)

3GPP
Report of meeting S2-168

17 Entries

Ms. Leyi Zhang ZONSON CCSA 3GPPMEMBER
Ms. Ling Zhang Siemens AG ETSI 3GPPMEMBER
Mr. Wanqiang Zhang HuaWei Technologies Co., Ltd CCSA 3GPPMEMBER
Miss Weiyin Zhang CTSI CCSA 3GPPMEMBER
Dr. Zhuoyun Zhang vivo Mobile Communication (S) CCSA 3GPPMEMBER
Mr. Song Zhao Chinatelecom Cloud CCSA 3GPPMEMBER
Dr. Lizhuo Zheng Beijing Lenovo Software Ltd. CCSA 3GPPMEMBER
Mr. Runze Zhou HiSilicon Technologies Co. Ltd CCSA 3GPPMEMBER
Mr. Chunhui Zhu NEC Telecom MODUS Ltd. ETSI 3GPPMEMBER
Mr. Fenqin Zhu HUAWEI Technologies Japan K.K. ARIB 3GPPMEMBER
Mr. Jinguo Zhu ZTE TSDSI 3GPPMEMBER
Mr. Qianghua Zhu Huawei Technologies (Korea) TTA 3GPPMEMBER
Mr. Haris Zisimopoulos Qualcomm Sweden ETSI 3GPPMEMBER
262 Entries

H.2 List of On-line registered participants

Table H.2: List of On-line registered participants

T Name Representing Partner Membership Status

Mr. Godson Antony Tejas Network Limited TSDSI 3GPPMEMBER
Mr. Apoorva Khamesra Apoorva Jio ETSI 3GPPMEMBER
Dr. Paventhan Arumugam ERNET India TSDSI 3GPPMEMBER
Miss Xueqian Bai China Mobile Com. Corporation CCSA 3GPPMEMBER
Mr. raghvendra bhushan Jio ETSI 3GPPMEMBER
Mr. Sungduck Chun Ofinno, LLC ATIS 3GPPMEMBER
Dr. Josep Colom Ikuno Telekom Deutschland GmbH ETSI 3GPPMEMBER
Mr. Tao Cui Sony Group Corporation ARIB 3GPPMEMBER
Mr. Nairit Das IIT, Kharagpur TSDSI 3GPPMEMBER
Mr. Shuangxing Deng CSCN CCSA 3GPPMEMBER
Mr. OMKAR DHARMADHIKARI CableLabs ETSI 3GPPMEMBER
Mr. Dimitrios Dimopoulos Motorola Mobility España SA ETSI 3GPPMEMBER
Mr. Thomas Dodds OTD_US ATIS 3GPPMEMBER
Mr. Jisi Dong Huawei Technologies Sweden AB ETSI 3GPPMEMBER
Mr. Stephen Edge Qualcomm Technologies ATIS 3GPPMEMBER
Mr. Peretz Feder Verizon Switzerland AG ETSI 3GPPMEMBER
Mr. Fabio Felici Oracle Corporation ETSI 3GPPMEMBER
Mr. Francis Fernandes Bell Mobility ETSI 3GPPMEMBER
Mr. Ramon Ferrus Sateliot ETSI 3GPPMEMBER
Ms. Maria Pia Galante TELECOM ITALIA S.p.A. ETSI 3GPPMEMBER

3GPP
Report of meeting S2-168

T Name Representing Partner Membership Status

Mr. Jainam Gandhi Jio ETSI 3GPPMEMBER
Mr. Gaurav Goel Reliance Jio TSDSI 3GPPMEMBER
Mr. Jason Graham OTD_US ATIS 3GPPMEMBER
Mr. Xiaofei Gu CATT CCSA 3GPPMEMBER
Mr. Boren Guo Hangzhou Mengyuxiang CCSA 3GPPMEMBER
Ms. Yali Guo Shenzhen Heytap CCSA 3GPPMEMBER
Mr. Aditya Gupta Jio ETSI 3GPPMEMBER
Mr. Rounak Gupta Jio ETSI 3GPPMEMBER
Mr. Vivek Gupta Apple Inc ATIS 3GPPMEMBER
Mr. Lufeng Han Spreadtrum CCSA 3GPPMEMBER
Mr. Masaharu Hattori KDDI Corporation ARIB 3GPPMEMBER
Mr. Changzheng Huang China Telecom Corporation Ltd. CCSA 3GPPMEMBER
Mr. John Ing Public Safety Canada ETSI 3GPPMEMBER
Mr. Bibekananda Jena Jio ETSI 3GPPMEMBER
Miss Mengzhen Jian China Telecom Corporation Ltd. CCSA 3GPPMEMBER
Mr. Hongyan Jin China Mobile Com. Corporation CCSA 3GPPMEMBER
Mr. James Jin vivo Mobile Communication Co., CCSA 3GPPMEMBER
Mr. Jiwon Kang LG Electronics Inc. TTA 3GPPMEMBER
Dr. Gil Kedar Ceragon Networks AS ETSI 3GPPMEMBER
Dr. Wonjung Kim LG Uplus TTA 3GPPMEMBER
Mr. lalit kotecha Verizon Switzerland AG ETSI 3GPPMEMBER
Mr. Vikram Krishnakumar CEWiT TSDSI 3GPPMEMBER
Mr. Rinku Kumar NEC Corporation. TTC 3GPPMEMBER
Mr. Vinay Kumar Jio ETSI 3GPPMEMBER
Mr. Amit Kushwaha Jio ETSI 3GPPMEMBER
Mr. Nidhin L CEWiT TSDSI 3GPPMEMBER
Ms. Ankita Lachhwani CEWiT TSDSI 3GPPMEMBER
Mrs. Su Lanrong GEESPACE CCSA 3GPPMEMBER
Mr. SeongJun Lee SK Telecom TTA 3GPPMEMBER
Mr. Xiaoyang Lee CISA ECD ATIS 3GPPMEMBER
Miss Jiahui LI China Telecom Corporation Ltd. CCSA 3GPPMEMBER
Miss Yinjie LIANG China Unicom CCSA 3GPPMEMBER
Mr. Junle Liao IPLOOK CCSA 3GPPMEMBER
Miss Jiayifan Liu China Telecommunications Corp. CCSA 3GPPMEMBER
Miss Jie Liu Chinatelecom Cloud CCSA 3GPPMEMBER
Mr. Le Liu China Mobile Com. Corporation CCSA 3GPPMEMBER
Miss Yubing Liu China Telecommunications Corp. CCSA 3GPPMEMBER
Mr. Biao Long China Telecom Corporation Ltd. CCSA 3GPPMEMBER
Mr. Daniel Lönnblad Ericsson LM ETSI 3GPPMEMBER
Miss Jie Lu Fiberhome Technologies Group CCSA 3GPPMEMBER
Dr. Jonathan Lu FCC ATIS 3GPPMEMBER
Miss wei lu China Unicom CCSA 3GPPMEMBER
Mrs. Haley Luo Lenovo Information Technology CCSA 3GPPMEMBER

3GPP
Report of meeting S2-168

T Name Representing Partner Membership Status

Mr. Huazhang Lyu China Mobile Com. Corporation CCSA 3GPPMEMBER
Mr. Antony Mampilly CEWiT TSDSI 3GPPMEMBER
Miss Yoko Masuda SHARP Corporation ARIB 3GPPMEMBER
Mr. Shiro Mazawa NICT ARIB 3GPPMEMBER
Mr. Achref Methenni InterDigital Communications ATIS 3GPPMEMBER
Mr. Chandan C Mishra IIT Bombay TSDSI 3GPPMEMBER
Mr. Tanmoy Mondal Jio ETSI 3GPPMEMBER
Ms. Hala Mowafy Peraton Labs ATIS 3GPPMEMBER
Dr. Sandra Murphy Comcast ATIS 3GPPMEMBER
Mr. Arpan Nanda Jio ETSI 3GPPMEMBER
Mr. Vijay Nangia Motorola Mobility UK Ltd. ETSI 3GPPMEMBER
Mr. Peter Nas F5 ETSI 3GPPMEMBER
Mr. Ashok Kumar Nayak Samsung Guangzhou Mobile R&D CCSA 3GPPMEMBER
Dr. Akshatha Nayak Manjeshwar Tejas Network Limited TSDSI 3GPPMEMBER
Mr. Anupkumar Pandey Jio ETSI 3GPPMEMBER
Mr. Frank Patry Omnispace ATIS 3GPPMEMBER
Mr. Sriganesh Rajendran Tejas Network Limited TSDSI 3GPPMEMBER
Mr. Chi Ren China Unicom CCSA 3GPPMEMBER
Mr. Ralf Rossbach Apple GmbH ETSI 3GPPMEMBER
Ms. Jinsook Ryu Ofinno, LLC ATIS 3GPPMEMBER
Mrs. Aswathy S CEWiT TSDSI 3GPPMEMBER
Dr. Xiao Shao TOYOTA MOTOR CORPORATION TTC 3GPPMEMBER
Mr. Gaurav Sharma Reliance Jio TSDSI 3GPPMEMBER
Mr. Lin Shu HuaWei Technologies Co., Ltd CCSA 3GPPMEMBER
Miss Chen Shuzhen China Telecommunications ETSI 3GPPMEMBER
Dr. Yaqin Song CATT CCSA 3GPPMEMBER
Dr. Yishen Sun NIST ATIS 3GPPMEMBER
Miss Yue Sun China Telecom Corporation Ltd. CCSA 3GPPMEMBER
Mr. Tomohiko Takahashi ITOCHU Techno-Solutions Corp TTC 3GPPMEMBER
Mr. Tsuyoshi Takakura NTT DOCOMO INC. TTC 3GPPMEMBER
Miss Yuan Tao CICT Mobile CCSA 3GPPMEMBER
Mr. Pranay Thaker Jio ETSI 3GPPMEMBER
Mrs. Carol-lyn Thorpe-Taylor CISA ECD ATIS 3GPPMEMBER
Dr. Yolanda Tsang ASTRI ETSI 3GPPMEMBER
Miss Yu-Ching Tung MediaTek Beijing Inc. CCSA 3GPPMEMBER
Miss Harini Shree Velmurugan CEWiT TSDSI 3GPPMEMBER
Mr. Pierre VISA CANON Research Centre France ETSI 3GPPMEMBER
Mr. Baixiao Wang CATT CCSA 3GPPMEMBER
Mr. Nick Wang MediaTek (Hefei) Inc. CCSA 3GPPMEMBER
Dr. Yaxin Wang OPPO Beijing CCSA 3GPPMEMBER
Mr. Curt Wong Facebook Japan G.K. ARIB 3GPPMEMBER
Ms. Ling XU HiSilicon Technologies Co. Ltd CCSA 3GPPMEMBER
Mr. Fei Yang Comtech Telecommunications Cor ATIS 3GPPMEMBER

3GPP
Report of meeting S2-168

T Name Representing Partner Membership Status

Ms. Wenle Yang Pengcheng laboratory CCSA 3GPPMEMBER
Mr. Hang Yu vivo Mobile Com. (Chongqing) CCSA 3GPPMEMBER
Dr. Robert Zaus Apple (UK) Limited ETSI 3GPPMEMBER
Mr. Justin Zhang vivo Mobile Communication Co., CCSA 3GPPMEMBER
Mr. Pengfei Zhang China Mobile Com. Corporation CCSA 3GPPMEMBER
Miss Yuying Zhang China Telecom Corporation Ltd. CCSA 3GPPMEMBER
Mr. Yinhui Zhao NTT DOCOMO INC.. ARIB 3GPPMEMBER
Miss Jiaying Zong China Telecom Corporation Ltd. CCSA 3GPPMEMBER
114 Entries

3GPP

S2-2504484 - SA2-169-Session Plan - r10
No ratings yet
S2-2504484 - SA2-169-Session Plan - r10
3 pages
S2-2504483 - SA2#169 Meeting Agenda - r2
No ratings yet
S2-2504483 - SA2#169 Meeting Agenda - r2
13 pages
RepS3 01 V100 Approved
No ratings yet
RepS3 01 V100 Approved
13 pages
RP-091353 Report RAN 45 Seville
No ratings yet
RP-091353 Report RAN 45 Seville
155 pages
3GPP Release 8 and Beyond
100% (33)
3GPP Release 8 and Beyond
178 pages
3GPP2 Technology Webinar Agenda
No ratings yet
3GPP2 Technology Webinar Agenda
1 page
Rel-10 Description 20130630
No ratings yet
Rel-10 Description 20130630
149 pages
3GPP Rel-9 Beyond Feb 2010
100% (1)
3GPP Rel-9 Beyond Feb 2010
240 pages
A5-3 Encryption Algorithms Documents X
No ratings yet
A5-3 Encryption Algorithms Documents X
38 pages
List SA1 99e Agreed Approveddocx
No ratings yet
List SA1 99e Agreed Approveddocx
3 pages
g20
No ratings yet
g20
76 pages
Highlight Issue 2 FLIP BOOK
No ratings yet
Highlight Issue 2 FLIP BOOK
28 pages
RP-170477 TR38.804v1.0.0 Presentation
No ratings yet
RP-170477 TR38.804v1.0.0 Presentation
1 page
3GPP TR 22.868
No ratings yet
3GPP TR 22.868
15 pages
3GPP/3GPP2 Harmonization Workshop Summary
No ratings yet
3GPP/3GPP2 Harmonization Workshop Summary
7 pages
23 502 - 5G 业务流程
No ratings yet
23 502 - 5G 业务流程
576 pages
3GPP TR 23.715: Technical Report
No ratings yet
3GPP TR 23.715: Technical Report
39 pages
5G Standardization Update
No ratings yet
5G Standardization Update
14 pages
New Radio Access Tech Study Report
No ratings yet
New Radio Access Tech Study Report
1 page
3GPP TS 38.213
No ratings yet
3GPP TS 38.213
278 pages
3GPP Rel16
No ratings yet
3GPP Rel16
157 pages
RAN4 Meeting #104bis-e Agenda
No ratings yet
RAN4 Meeting #104bis-e Agenda
14 pages
3GPP Highlights Issue 9 WEB Download
No ratings yet
3GPP Highlights Issue 9 WEB Download
32 pages
3GPP 5G Standards Summit 2015
No ratings yet
3GPP 5G Standards Summit 2015
23 pages
3GPP TR 21.917
No ratings yet
3GPP TR 21.917
148 pages
38874-g00 Study On Integrated Access and Backhaul
No ratings yet
38874-g00 Study On Integrated Access and Backhaul
111 pages
3GPP Release
100% (1)
3GPP Release
149 pages
Qos and Security in 4G Networks: January 2004
No ratings yet
Qos and Security in 4G Networks: January 2004
7 pages
3GPP 36425-I00
No ratings yet
3GPP 36425-I00
17 pages
3GPP TR 22.912
No ratings yet
3GPP TR 22.912
16 pages
Release 18 Features tsg95 v03
No ratings yet
Release 18 Features tsg95 v03
1 page
I00
No ratings yet
I00
228 pages
3GPP TR 30.818
No ratings yet
3GPP TR 30.818
93 pages
3GPP TS 23.167
No ratings yet
3GPP TS 23.167
66 pages
MOM-Indonesia XLSmart Project EJ-20250417
No ratings yet
MOM-Indonesia XLSmart Project EJ-20250417
2 pages
S2-174004 Network Data Analytics (NWDA) Automation in 5G Phase 1 - ATT Et Al WG2 SA 121
No ratings yet
S2-174004 Network Data Analytics (NWDA) Automation in 5G Phase 1 - ATT Et Al WG2 SA 121
3 pages
RCR Webinar - A Closer Look at 5G Advanced Release 18 - Juan Montojo
No ratings yet
RCR Webinar - A Closer Look at 5G Advanced Release 18 - Juan Montojo
39 pages
3GPP TR 37.910
No ratings yet
3GPP TR 37.910
150 pages
3GPP TS 23.502
No ratings yet
3GPP TS 23.502
551 pages
Final Minutes Report RAN1#97 v100
No ratings yet
Final Minutes Report RAN1#97 v100
166 pages
3GPP TR 22.826
No ratings yet
3GPP TR 22.826
62 pages
2G Network Optimization - Sothearith
No ratings yet
2G Network Optimization - Sothearith
16 pages
3GPP TS 03.22
No ratings yet
3GPP TS 03.22
21 pages
Vision, Requirements, and Technology Trend of 6G - How To Tackle The Challenges of System Coverage, Capacity, User Data-Rate and Movement Speed
No ratings yet
Vision, Requirements, and Technology Trend of 6G - How To Tackle The Challenges of System Coverage, Capacity, User Data-Rate and Movement Speed
11 pages
3ORW-250001 3GPP O-RAN Joint Workshop Agenda v1
No ratings yet
3ORW-250001 3GPP O-RAN Joint Workshop Agenda v1
4 pages
5g Standard Itu
No ratings yet
5g Standard Itu
21 pages
RP-170377 38802-200
No ratings yet
RP-170377 38802-200
132 pages
Energy Efficients
No ratings yet
Energy Efficients
28 pages
3GPP TR 37.817: Technical Report
No ratings yet
3GPP TR 37.817: Technical Report
23 pages
3GPP TS 36.423
No ratings yet
3GPP TS 36.423
811 pages
Vocabulario para Las Especificaciones de 3GPP
No ratings yet
Vocabulario para Las Especificaciones de 3GPP
68 pages
3GPP RAN2 Meeting #120 Agenda
No ratings yet
3GPP RAN2 Meeting #120 Agenda
20 pages
4gwireless Networks: Opportunities and Challenges: Sudhir Kumar, Ajay Kumar Yadav
No ratings yet
4gwireless Networks: Opportunities and Challenges: Sudhir Kumar, Ajay Kumar Yadav
4 pages
Cleanup of TS 23.503 Specification
No ratings yet
Cleanup of TS 23.503 Specification
68 pages
3GPP TSG-RAN WG1 Meeting #117 R1-2405578 Fukuoka City, Fukuoka, Japan, May 20 - 24, 2024
No ratings yet
3GPP TSG-RAN WG1 Meeting #117 R1-2405578 Fukuoka City, Fukuoka, Japan, May 20 - 24, 2024
5 pages
Shame, Internalized Homophobia, Identity Formation, Attachment Style, and The Connection To Relationship Status in Gay Men
100% (1)
Shame, Internalized Homophobia, Identity Formation, Attachment Style, and The Connection To Relationship Status in Gay Men
10 pages
Sexual Orientation Identity and Romantic Relations PDF
No ratings yet
Sexual Orientation Identity and Romantic Relations PDF
17 pages
"S W P O ":: Ometimes E ARE Rejudiced Against Urselves
No ratings yet
"S W P O ":: Ometimes E ARE Rejudiced Against Urselves
22 pages
Internalised Homophobia PDF
No ratings yet
Internalised Homophobia PDF
4 pages
Internalized Homophobia and Health Issues Affecting Lesbians and Gay Men
No ratings yet
Internalized Homophobia and Health Issues Affecting Lesbians and Gay Men
11 pages
Streamedge™: Product Features
No ratings yet
Streamedge™: Product Features
2 pages
Instruction Manual: Digital Proportional Radio Control System
No ratings yet
Instruction Manual: Digital Proportional Radio Control System
34 pages
Steve Evolution of Computer
No ratings yet
Steve Evolution of Computer
1 page
LDM ZJKT - 6040 Batusari Condet
No ratings yet
LDM ZJKT - 6040 Batusari Condet
1 page
Odd Semester Exam Guide 2021-2022
No ratings yet
Odd Semester Exam Guide 2021-2022
4 pages
Multi-Service IP DSLAM For Broadband IP Access
No ratings yet
Multi-Service IP DSLAM For Broadband IP Access
6 pages
Class XII Networking Concepts
No ratings yet
Class XII Networking Concepts
3 pages
Layer by Layer Troubleshooting With A Cisco Router
No ratings yet
Layer by Layer Troubleshooting With A Cisco Router
5 pages
IoT Growth Insights for Industry Leaders
No ratings yet
IoT Growth Insights for Industry Leaders
12 pages
Helipad Antenna Specification Sheet
No ratings yet
Helipad Antenna Specification Sheet
2 pages
MELCOBEMS Installation Manual Instruction Book 1
No ratings yet
MELCOBEMS Installation Manual Instruction Book 1
39 pages
3 - Computer Network - Basic Concepts
50% (2)
3 - Computer Network - Basic Concepts
35 pages
Beolab 18
No ratings yet
Beolab 18
66 pages
JDY 16 V1.5 (English Manual
50% (2)
JDY 16 V1.5 (English Manual
41 pages
Digital Lifestyle of Connected Nigerians
No ratings yet
Digital Lifestyle of Connected Nigerians
14 pages
MATLAB Basics for Electrical Engineers
No ratings yet
MATLAB Basics for Electrical Engineers
87 pages
LTE 850/CDMA Interference in GSM 900 MHz
No ratings yet
LTE 850/CDMA Interference in GSM 900 MHz
5 pages
Wi Fi Analyzer User Guide
No ratings yet
Wi Fi Analyzer User Guide
14 pages
3102007-En R03 FSB-PC2 and FSB-PCLW Communication Bridge Installation Sheet - 20160310102310
0% (1)
3102007-En R03 FSB-PC2 and FSB-PCLW Communication Bridge Installation Sheet - 20160310102310
6 pages
TDQ 230v 156A - Module Datasheet
No ratings yet
TDQ 230v 156A - Module Datasheet
10 pages
2marks WSN
No ratings yet
2marks WSN
8 pages
Design and Analysis of A 28 GHZ Micro Strip Patch Antenna For 5G Wireless Communications
No ratings yet
Design and Analysis of A 28 GHZ Micro Strip Patch Antenna For 5G Wireless Communications
6 pages
APN and BGP Configuration Guide
No ratings yet
APN and BGP Configuration Guide
6 pages
Nte 7157
No ratings yet
Nte 7157
2 pages
EE 442 Homework #4: MT T T CT T
No ratings yet
EE 442 Homework #4: MT T T CT T
6 pages
CN 6
No ratings yet
CN 6
2 pages
NTTP 6-02 Tactical Radios
No ratings yet
NTTP 6-02 Tactical Radios
88 pages
Wireless Control System For DC Motor To Position A Dish Antenna Using Microcomputer
No ratings yet
Wireless Control System For DC Motor To Position A Dish Antenna Using Microcomputer
7 pages
Unit 4 - QB (AutoRecovered)
No ratings yet
Unit 4 - QB (AutoRecovered)
8 pages
Amateur Radio End-Fed Antenna Guide
No ratings yet
Amateur Radio End-Fed Antenna Guide
14 pages