Atendence list: ZTE, NEC, Huawei, China Mobile, China Telecom, Lenovo, Nokia, Ericsson, AT&T, LGE, Samsung, T-Mobile, OPPO, Apple, CATT, Telecom Italia, infoblox, NTT Docomo, China Unicom, Tencent, FirstNet, Vodafone, 
If I missed someone please let me know.

We discussed the following input papers:

1. Huawei: S2-210xxxx DP Network Slice Access Control Functionalities and Services_v1.1
Fenqin presents the paper.
Some companies believe this paper is the PCF solution in the TR and have strong objections. 
Fenqin reconsideres whether to submit this paper at next meeting. 

2. NEC: S2-20xxxxx TS23.501 Network Slice Quota Control Function (NSQCF) definition v04
Iskren presents the paper. This is paper for push option.
The NSACF may need to store the UE ID in order to check whether the UE has been registered in the slice.
Interaction with CHF and SA5 progress will be taken into account. 
When and how the AMF triggers the request towords the NSACF will be addressed.
The function name and clause title should be changed without word "quota". 
On the text whether to describe the quota handling will be discussed further.

3. Lenovo: S2-210xxxx_DP_Principles-for-NSQAC_v01
Genadi presents the paper. This is paper for pull option
This solution is considered by some companies as a new solution and the details are not studied in the TR.
When the quota is about to reach the maximum, how does it work is unclear.
It is possible that the AMF reports the quota at each UE registration/deregistration. 
The UE ID in NSACF is not needed in this solution. 
Additional functionality in the AMF should be described to maintain the UE registration status and check the quota.

There are discussion which option(pull or push) is prefered, both options have cons and pros.
The option should have high accuracy on the control enforcement and reporting.
It seems push option has high accuracy than the pull option as it is controlled per UE or per PDU session.
The details of pull option are not described and may have more impact on the system.
The rapporteur proposes to use NEC paper as basis for 501 CR push option. More early feedback/suggestion can be provided offline. 
Further work offline on the pull option is still possible and comparision of these two options may be needed in order to make final decision at SA2#143E. 

4. ZTE: eNS_Ph2 open issues r02
Clarification on whether this feature can be applied to all network slices or not.
For KI#2, rapporteur will prepare a comparision table on whether AMF or SMF to perform the admission check for PDU session. MA-PDU session may need to be taken into account.
The name of new NF is recommended to be Network Slice Admission Control Function(NSACF)
For the NSACF deployment option, both per PLMN or per slice should be supported by standard so the operator can select based on scenarios. For per slice option the slice information can be used for NSACF discovery input parameter. Other input parameters are FFS. Whether distributed deployment can be supported is FFS
On roaming issue, it is recommended to defer the discussion until the solution on non roaming solution is available. The VPLMN may have policy for all roamers, not per slice. For roaming case it is unclear the policy from which PLMN should be used for the NSAC. More input from GSMA is expected. The CR without roaming part can be endorsed for the first meeting instead of approved.

The following papers are not discusse due to time issue. It is encouraged to further work offline.

5. Huawei: S2-210xxxx DP Architectural support for Network SLice Access Control functionalities_v1.1
6. NEC_S2-20xxxxx TS23.502 Network Slice Quota Control Function (NSQCF) service definition v02
7. ZTE S2-20xxxxx TS23.501 functionalities for NSSAC
8. S2-210xxxx - eNS_Ph2_TSs_workplan_v3