Enhancing Assistance Information for 5G Networks

SA2#155 pre SA2#155 pre- -meeting CC meeting CC LiMeng

Agenda Agenda General Handling of the documents; Rel-18 Exact name/IEs for assistance information; Including 247 and 502. Way of documenting the procedure; Rel-17 Security architecture for 5MBS (S2-2300071); AoB Location dependent issue for KI#2. Click here to join the meeting

General General Handling of the documents For the documents with the same CR number. The company who is the first author of the document agreed in the last meeting will hold the pen? E.g., 23.247 CR0159R2 (Rel-18, 'B'): Support RRC_INACTIVE UE receiving multicast MBS data Ericsson, [Nokia, Nokia Shanghai-Bell, ZTE, CATT] S2-2302323 Basis? 23.247 CR0159R3 (Rel-18, 'B'): Support RRC_INACTIVE UE receiving multicast MBS dataQualcomm, [Ericsson, Nokia, Nokia Shanghai-Bell, S2-2302939 ZTE, CATT] 23.247 CR0159R5 (Rel-18, 'B'): Support RRC_INACTIVE UE receiving multicast MBS data Nokia, Nokia Shanghai-Bell, [Ericsson, ZTE, CATT] S2-2303003 But of course the content needs to be discussed KI#1: Mobility KI#2: Procedure update

Rel Rel- -18 KI#1: Exact name/IEs for assistance information 18 KI#1: Exact name/IEs for assistance information (TS 23.247) (TS 23.247) SMF RAN UDM SMF AF UDM Document Name IEs Name IEs Name IEs S2-2302323 (Ericsson) MBS assistance information Indication, encoding is left to RAN WG decided MBS assistance information MBS Assistance information A list of GPSIs, MBS session ID MBS Session ID(s) MBS assistance information for the given MBS session S2-2302776 (Huawei) Indication, encoding is left to RAN WG decided MBS assistance information UE list MBS Assistance information A list of GPSIs, MBS session ID MBS Session ID(s) Protocol details require RAN WG feedback, e.g., whether indication is enough S2-2302939 (Qualcomm) MBS assistance information MBS assistance information UE list MBS Assistance information A list of GPSIs, MBS session ID MBS Session ID(s) Protocol details require RAN WG feedback, e.g., whether indication is enough S2-2303003 (Nokia) MBS assistance information MBS assistance information MBS Assistance information A list of GPSIs, MBS session ID(s) MBS Session ID(s) MBS assistance information for the MBS session (that UE joined) (consider to refine?) MBS Session Assistance Information MBS Assistance Information A list of GPSIs, MBS session ID Alt#1: indicates that the UE is preferred to be kept connected when receiving the data ; Alt#2: expresses that the UE is preferred to be kept in RRC_CONNECTED WF: Add a clarification after Alt#1 the description on how the parameters to be used by the RAN node. NG-RAN prefers the UE

Rel Rel- -18 KI#1: Exact name/IEs for assistance information 18 KI#1: Exact name/IEs for assistance information (TS 23.502) (TS 23.502) Table 5.2.3.6.1-2: Parameter Provision data types keys Table 5.2.3.6.1-2: Parameter Provision data types keys Parameter Provision Data Types Expected UE Behaviour parameters Data Key GPSI or External Group ID GPSI External Group Identifier External Group Identifier GPSI Data Sub Key Parameter Provision Data Types Expected UE Behaviour parameters Data Key GPSI or External Group ID GPSI External Group Identifier External Group Identifier GPSI Data Sub Key - - Network Configuration parameters 5G VN group data - - Network Configuration parameters 5G VN group data - - 5G VN group membership management parameters Location Privacy Indication parameters. Enhanced Coverage Restriction Information ECS Address Configuration Information - 5G VN group membership management parameters Location Privacy Indication parameters. Enhanced Coverage Restriction Information ECS Address Configuration Information - - - GPSI - GPSI - GPSI or External Group ID or any UE External Group Identifier External Group ID - GPSI or External Group ID or any UE External Group Identifier External Group ID - Multicast MBS group membership management parameters MBS Session Authorization information MBS Session Assistance Information - Multicast MBS group membership management parameters MBS Session Authorization information UE list MBS Session Assistance Information - - - GPSI MBS Session ID S2-2302324 (Ericsson) S2-2302776 (Huawei) MBS session ID + GPSI(s) GPSI + MBS session ID AF NEF UDM MBS session ID + GPSI(s) MBS session ID + GPSI(s) AF NEF UDM

Rel Rel- -18 KI#2: Way of documenting the procedure 18 KI#2: Way of documenting the procedure Alternatives #1: Using dedicated clause for Rel-18 (S2-2302328) for broadcast session start/stop? #2: Modifying current procedures (S2-2303107) for broadcast session start/stop? Possible Reasons for Alt#1 Possible Reasons for Alt#2 Clear separation between Rel-17 procedure and Rel-18 enhancement; Avoid potential clashing with the CRs updating the same part (e.g., with S2-2302095); Same as what we did for location dependent/local MBS service in rel-17; Easy to get the whole picture of the call-flow; 23.247 CR0197 (Rel-18, 'B'): Procedures for resource sharing across multiple broadcast MBS Sessions during network sharing 23.247 CR0165R1 (Rel-18, 'B'): On resource efficiency for MBS reception in RAN sharing scenario Nokia, Nokia Shanghai-Bell Huawei, HiSilicon, Ericsson S2-2303107 S2-2302328 KI#1: Mobility KI#2: Procedure update

Rel Rel- -17 MBS security (1/2) 17 MBS security (1/2) LS from SA3 (postponed S2-2302189) LS OUT LS OUT LS OUT LS OUT CR CR CR CR [DRAFT] Reply LS on Security architecture for 5G multicast/broadcast services [Draft] Rely on Reply LS on Security architecture for 5G multicast/broadcast services [DRAFT] Reply LS on Security architecture for 5G multicast/broadcast services [DRAFT] Reply LS on Security architecture for 5G multicast/broadcast services 23.247 CR0147R1 (Rel-17, 'F'): Alignment with security functionality 23.247 CR0148R1 (Rel-18, 'A'): Alignment with security functionality 23.247 CR0186 (Rel-17, 'F'): Update on the security in accordance with SA WG3 LS 23.247 CR0187 (Rel-18, 'A'): Update on the security in accordance with SA WG3 LS Nokia Ericsson Huawei Qualcomm Qualcomm Qualcomm Huawei Huawei S2-2302238 S2-2302319 S2-2302674 S2-2302930 S2-2302926 S2-2302928 S2-2302675 S2-2302676 Summarized aspects from LSs: Topic View(s) Side information View 1: MBSSF can be located other than MBSF/MBSTF; View 2: MBSSF can only be located at MBSF/MBSTF; Relationship between MBSSF and MBSF/MBSTF S3-223920: The UE authenticates to the MBSSF (i.e. MBSF or MBSTF) based on the GBA S3-223920: MBSSF can be collocated with either MBSF or MBSTF and the according interfaces are up to the implementation of the deployment options. SA4 is now discussingthe operation and services for supporting MBSSF. View 1: MBSSF will be referred in TS 23.247; View 2: MBSSF is invisible in TS 23.247; Visibility of MBSSF in TS 23.247 User Plane Path between MBSSF and UE (for distributingthe updated key) The MBSSF needs to be inserted into the user plane path for MBS data distribution. Issue:these procedures will not be standardized in rel.17. A UE needs to discover an authentication interface at the MBSSF. View 1: SA2 will not work on related discovery procedures in Rel-17 but leave them to SA3 or implementation. View 2: SA2 expects that SA3 will work with SA4 to document the related information in specifications under SA4 control. SA2 will not work on related discovery procedures in Rel-17 but leave them to SA3 and SA4 to document. UE-MBSSF interaction (discovery/authentication)

Rel Rel- -17 MBS security (2/2) for info 17 MBS security (2/2) for info PCF NRF UDM MBSSF functionality: Per UE: authentication, key distribution; Npcf Nnrf Nudm Per session: key update; Nnef Nmbsmf Naf Namf Nsmf Nmbsf N1 MBSF NEF AF/AS AMF SMF MB-SMF Nmb10 Nmb2 N2 N4 N4mb Uu N3 Nmb9 N19mb Nmb8 UE NG-RAN UPF MB-UPF MBSTF N6mb N3mb

AoB? AoB?