19.1.8 ProSe Direct Communication/Security Aspects / Release of PDN Connection used to receive MIKEY Messages/ Correct Key Request Message/ MIKEY Verification Message

36.523-13GPPEvolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet Core (EPC)Part 1: Protocol conformance specificationRelease 17TSUser Equipment (UE) conformance specification

19.1.8.1 Test Purpose (TP)

(1)

with { UE served by E-UTRAN PLMN supporting ProSe and intending to use One-to-many ProSe direct communication }

ensure that {

when { the UE received MIKEY message on additional PDN and UE is triggered to initiate deactivation of the additional PDN }

then { the UE shall not send PDN DISCONNECT REQUEST }

}

(2)

with { the UE has informed the ProSe Key Management Function that it no longer requires PGK }

ensure that {

when { the UE is triggered to initiate deactivation of the additional PDN }

then { the UE shall send PDN DISCONNECT REQUEST }

}

19.1.8.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 33.303, clause 6.2.3.3.2.2

[TS 33.303, clause 6.2.3.3.2.2]

…

The UE shall not release the PDN connection used to receive MIKEY messages containing PGKs until the UE has informed the ProSe Key Management Function that it no longer requires PGKs. This is to ensure that the ProSe Key Management Function is aware of the correct UE IP address for the purpose of performing PGK deliveries as specified in clause 6.2.3.3.2.3.

…

19.1.8.3 Test description

19.1.8.3.1 Pre-test conditions

System Simulator:

– Cell 1

– System information combination 23 as defined in TS 36.508 [18] clause 4.4.3.1 is used in E-UTRA Cell 1.

UE:

– The UE is authorised to perform ProSe Direct Communication.

– The UE has pre-configured radio parameters (preconfigComm) as defined in TS 36.508 with an associated geographical area and a UICC with all values equal to the default profile given inTS 36.508 [18], section 4.9.3.1 except for those listed in Table 19.1.8.3.1-1.

Table 19.1.8.3.1-1: USIM configuration

USIM field

Priority

Value

EFPROSE_RADIO_COM

Is present

EFUST

Service 101 is supported

EFAD

UE is authorized to use pre-configured parameters for ProSe

EFPROSE_PLMN

PLMN of Cell 1

EFPST

Service n°3 and service n°6 are supported

EFPROSE_POLICY

Group ID = ‘0000 0000 0000 0000 0000 0000’ [BIN]

ProSe UE ID = ‘0000 0000 0000 0000 0000 0001’ [BIN]

Preamble:

– The UE is in state Registered, Idle mode (state 2) according to [18].

19.1.8.3.2 Test procedure sequence

Table 19.1.8.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

Trigger the UE to send the KEY_REQUEST. (Note 1)

–

–

–

–

2-12

TS 36.508 clause 4.5A.22: Step 1-11 of Communication with the ProSe Function procedure is completed.

TS 36.508 Table 4.5A.22.3-2: Step 1a1 to 9 is only executed

–

–

–

–

13

UE sends KEY_REQUEST message to the ProSe Key Management Function

–>

HTTP Request containing KEY_REQUEST

–

–

14

SS transmits a KEY_RESPONSE message

<–

HTTP Response containing KEY_RESPONSE

–

–

15

SS transmits a MIKEY message containing PGK

<–

MIKEY message containing Key Delivery message

–

–

16

UE sends MIKEY verification message

–>

MIKEY message containing verification message

–

–

17

Initiate the deactivation of the additional PDN in UE. (see Note 2)

–

–

–

–

18

Check: Does the UE transmit PDN DISCONNECT REQUEST message?

–>

PDN DISCONNECT REQUEST

–

F

19

Trigger the UE to send KEY_REQUEST message to the ProSe Key Management Function to inform that UE no longer requires PGK. (Note 3)

–>

HTTP Request containing KEY_REQUEST

–

–

20

SS transmits a KEY_RESPONSE message

<–

HTTP Response containing KEY_RESPONSE

–

–

21

Initiate the deactivation of the additional PDN in UE. (see Note 2)

–

–

–

–

22

Check: Does the UE transmit PDN DISCONNECT REQUEST message?

–>

PDN DISCONNECT REQUEST

–

P

23

Deactivation of the additional PDN is triggered in UE. The additional PDN shall be released as specified in steps 10-13 of TS 36.508 subclause 4.5A.17.

–

–

–

–

Note 1: The trigger in step 1 is the same as in the generic procedure in 36.508 clause 4.5A.22

Note 2: Deactivation of the additional PDN is initiated by MMI or AT command

Note 3: Trigger is initiated by MMI or AT command

19.1.8.3.3 Specific message contents:

Table 19.1.8.3.3-1: KEY_REQUEST (step 19, table 19.1.8.3.2-1)

Derivation path: 36.508 Table 4.7F.3-1

Field

Value/remark

Comment

Condition

transaction-ID

Any

GroupKeyReq

Not Present

GroupKeyStop

One entry

GroupId

Same as the GroupId sent in Step 13

Table 19.1.8.3.3-2: KEY_RESPONSE (step 20, table 19.1.8.3.2-1)

Derivation path: 36.508 Table 4.7F.3-2

Field

Value/remark

Comment

Condition

transaction-ID

Same as in Step 19

GroupNotSupported

One entry

GroupId

Same as the GroupId sent in Step 19

Error-Code

4

UE requested to stop receiving PGKs for this group

GroupResponse

Not Present

Key-info

Not Present