Home SMF

4.2.2.1.1 Priority of UP security policy

Home SMF18.1.0
33515-h00   33515-i00    33515-i10 33515-j00  
Test Name TC_UP_POLICY_PRECEDENCE_SMF
Threat Reference

TR 33.926 [4], clause J.2.2.1 Non-compliant UP security policy handling

Requirement Name

Priority of UP security policy

Requirement Reference

TS 23.501 [1], clause 5.10.3

Requirement Description

User Plane Security Policy from UDM takes precedence over locally configured User Plane Security Policy as specified in TS 23.501 [1], clause 5.10.3

Test Purpose

Verify that the user plane security policy from the UDM takes precedence at the SMF under test over locally configured user plane security policy.

Pre-Conditions

Test environment with AMF and UDM may be simulated.

Both UDM and SMF under test are configured with UP security policy, and the UP security policies are different.

There is no Session Management Subscription data in SMF.

Execution Steps
  1. The tester triggers PDU session establishment procedure by sending Nsmf_PDUSession_CreateSMContext Request message to the SMF.

  2. The SMF under test retrieves the Session Management Subscription data using Nudm_SDM_Get service from UDM, where the Session Management Subscription data includes the user plane security policy stored in UDM.

  3. The tester captures the Namf_Communication_N1N2MessageTransfer message sent from the SMF under test to the AMF.

Expected Results

There is a Security Indication IE in the N2 SM information contained in the Namf_Communication_N1N2MessageTransfer message, which is the same with the UP security policy configured in the UDM.

Expected Format of Evidence

Evidence suitable for the interface, e.g., Screenshot containing the operational results.

PDFs 1ed23fa4f9cfaafd750db5630b79c181

4.2.2.1.3 Security functional requirements on the SMF checking UP security policy

Home SMF18.1.0
33515-h00   33515-i00    33515-i10 33515-j00  
Test Name TC_UP_SECURITY_POLICY _SMF
Threat Reference

TR 33.926 [4], clause J.2.2.4, Unchecked UP security policy.

Requirement Name

UP security policy check.

Requirement Reference

TS 33.501 [8], clause 6.6.1

Requirement Description

According to TS 33.501 [8], clause 6.6.1,the SMF verifies that the UE's UP security policy received from the target ng-eNB/gNB is the same as the UE's UP security policy that the SMF has locally stored. If there is a mismatch, the SMF sends its locally stored UE's UP security policy of the corresponding PDU sessions to the target gNB. This UP security policy information, if included by the SMF, is delivered to the target ng-eNB/gNB in the Path-Switch Acknowledge message. The SMF logs capabilities for this event and may take additional measures, such as raising an alarm.

Test Purpose

Verify that the SMF checks the UP security policy that is sent by the ng-eNB/gNB during handover.

Pre-Conditions

The SMF under test is preconfigured with a UE UP security policy.

Execution Steps
  1. The tester sends the Nsmf_PDUSession_UpdateSMContext Request message to the SMF under test. A UE UP security policy different than the one preconfigured at the SMF under test is included in the Request message.

  2. The tester captures the Nsmf_PDUSession_UpdateSMContext Response message sent from the SMF under test.

Expected Results

The preconfigured UE security policy is contained in the 'n2SmInfo' IE in the captured Response message.

Expected Format of Evidence

Files containing the triggered HTTP messages (e.g. pcap trace).

PDFs 0d682ba8402deb7ef5d7909849895b7b

4.2.2.1.4 Charging ID Uniqueness

Home SMF18.1.0
33515-h00   33515-i00    33515-i10 33515-j00  
Test Name TC_CHARGING_ID_UNIQUENESS_SMF
Threat Reference

TR 33.926 [4], clause J.2.2.3, "Failure to assign unique Charging ID for a session"

Requirement Name

Charing ID uniqueness.

Requirement Reference

TS 32.255 [6], clause 5.1.2

Requirement Description

According to TS 32.255 [6], clause 5.1.2:

  • The SMF supports PDU session charging using service based interface.

  • The SMF collects charging information per PDU session for UEs served under 3GPP access and non-3GPP access.

  • Every PDU session is assigned a unique identity number for billing purposes per PLMN. (i.e. the Charging Id).

Test Purpose

Verify that the charging ID generated by the SMF for each PDU session is unique.

Pre-Conditions

Test environment is set up with a Charging Function (CHF), which may be real or simulated, and the SMF under test. The tester is able to capture the traffic between the SMF under test and the CHF.

Execution Steps
  1. The tester intercepts the traffic between the SMF under test and the CHF.

  2. The tester triggers the establishment of the maximum number of concurrent PDU sessions that the SMF under test can handle.

  3. The tester captures each Charging Data Request [initial] sent from the SMF under test to the CHF, and verifies the charging ID contained in the 'PDU Session Charging Information' IE in each Charging Data Request [initial] is unique.

Expected Results

The charging ID in each Charging Data Request [initial] is unique.

Expected Format of Evidence

Files containing the Charging Data Request [initial] messages (e.g. pcap trace).

PDFs 612a8ef74e221f3afc79181810c3e412