27.22.13 CALL CONTROL on PDU Session Establishment for NG-RAN

31.1243GPPMobile Equipment (ME) conformance test specificationRelease 16TSUniversal Subscriber Identity Module Application Toolkit (USAT) conformance test specification

27.22.13.1 Procedure for Mobile Originated calls

27.22.13.1.1 Definition and applicability

See clause 3.2.2.

27.22.13.1.2 Conformance requirement

The ME shall support the CALL CONTROL facility as defined in:

– 3GPP TS 31.111 [15] clause 7.3.1.6, clause 7.3.1.10, clause 8.143

– 3GPP TS 24.501 [40], clause 6.4.1, 8.3.1, 9.11.4.6 and 9.11.4.15.

27.22.13.1.3 Test purpose

To verify that when the service 128 "Call Control on PDU Session by USIM" is available in the USIM Service Table, then for all PDU Session Establishment Requests (including those resulting from an OPEN CHANNEL proactive command where NG-RAN is selected), the ME shall first pass the corresponding PDU Session Establishment Request message to the UICC, using the ENVELOPE (CALL CONTROL) command. The ME shall also pass to the UICC in the ENVELOPE (CALL CONTROL) command the current serving cell.

To verify the PDU Session Establishment Request parameters are used in the ENVELOPE (CALL CONTROL), as defined in 3GPP TS 24.501 [40].

To verify UICC/ME CALL CONTROL modify only the following parameters:

– SM PDU DN request container; and

– operator specific parameters in Extended Protocol configuration options,

included in the PDU SESSION ESTABLISHMENT REQUEST message

To verify that the ME interpret the UICC returns response correctly.

27.22.13.1.4 Method of tests

27.22.13.1.4.1 Initial conditions

The ME is connected to the USIM Simulator and the NG-SS. Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.

The default NG-RAN UICC, the default NG-RAN parameters and the following parameters are used:

Always-on PDU session:

DNN: TestGp.rs

PDU Session Type: IPv4v6

UICC/ME interface transport level

Transport format: TCP

Port number: 44444

Data destination address: 01.01.01.01 (as an example)

The NG-RAN parameters of the system simulator are:

– Mobile Country Code (MCC) = 001;

– Mobile Network Code (MNC) = 01;

– Tracking Area Code (TAC) = 000001;

– NG-RAN Cell Id = 0001 (36 bits).

The elementary files are coded as USIM Application Toolkit default with the following exceptions:

– The call control on PDU session by USIM service is available in the USIM Service Table.

27.22.13.1.4.2 Procedure

Expected Sequence 1.1 (CALL CONTROL on PDU Session for NG-RAN, always-on PDU Session Establishment, allowed without modification)

Step

Direction

Message / Action

Comments

0

USER ME

Set and configure DNN as "TestGp.rs" in the terminal configuration for Always-on if required

[see initial conditions]

1

ME UICC

ENVELOPE CALL CONTROL 1.1.1

For Always-on PDU Session establishment

2

UICC ME

CALL CONTROL RESULT 1.1.1

[Call control result: "Allowed", no modification]

3

ME NG-SS

The PDU Session Establishment is successfully without modification

Same PDU Session Establishment parameters used by the ME within the ENVELOPE CALL CONTROL are used to establish the PDU Session.

ENVELOPE CALL CONTROL 1.1.1

Logically:

Device identities:

Source device: ME

Destination device: UICC

PDU Session Establishment parameters:

DNN: TestGp.rs

Extended Protocol Discriminator: 5GS Session Management messages (2E)

PDU Session identity: Any valid value in the range of 1 to 15

Procedure Transaction Identity: Any valid value in the range of 1 to 254

5GS Session message identity: PDU session establishment request (C1)

PDU Session Type: IPv4v6

Extended Protocol configuration options:

Extended Protocol config. optional contents: content not checked

Location Information:

Mobile Country Codes (MCC): 001

Mobile Network Codes (MNC): 01

Tracking Area Code (TAC): 000001

NG-RAN Cell Identifier (NCI): 0001 (36 bits)

Coding:

BER-TLV:

D4

Note 1

02

02

82

81

0C

Note 2

25

0A

06

54

65

73

74

47

70

02

72

73

2E

Note 5

Note 6

C1

Note 3

Note 3

93

Note 4

13

0B

00

F1

10

00

00

01

00

00

00

00

1F

Note 1: The length of the BER-TLV is present here.

Note 2: Length of PDU session establishment parameters, dependent of optional fields.

Note 3: Integrity protection maximum data rate

Note 4: Optional fields / extended protocol configuration options. (byte 27 to 27+n if available)

Note 5: PDU session identity

Note 6: Procedure transaction identity

CALL CONTROL RESULT 1.1.1

Logically:

Call control result: ’00’ = Allowed, no modification

Coding:

BER-TLV:

00

00

Expected Sequence 1.2 (CALL CONTROL on PDU Session for NG-RAN, always-on PDU Session Establishment, Not allowed)

Step

Direction

Message / Action

Comments

0

USER ME

Set and configure DNN as "TestGp.rs" in the terminal configuration for Always-on if required

[see initial conditions]

1

ME UICC

ENVELOPE CALL CONTROL 1.1.1

For Always-on PDU Session establishment

2

UICC ME

CALL CONTROL RESULT 1.2.1

[Call control result: "Not Allowed"]

3

ME NG-SS

ME shall not send PDU Session Establishment Request.

No Always-on PDU Session is established.

CALL CONTROL RESULT 1.2.1

Logically:

Call control result: ’01’ = Not Allowed

Coding:

BER-TLV:

01

00

Expected Sequence 1.3 (CALL CONTROL on PDU Session for NG-RAN, PDU Session Establishment triggered by user, UICC sends 90 00)

Step

Direction

Message / Action

Comments

0

USER ME

Set and configure DNN as "TestGp.rs" in the terminal configuration for Always-on if required

[see initial conditions]

1

ME UICC

ENVELOPE CALL CONTROL 1.1.1

For Always-on PDU Session establishment

2

UICC ME

90 00

3

USER ME

Set and configure DNN as "Test12.rs" in the terminal configuration for a new PDU Session if required and trigger ME to establish the PDU Session.

[PDU Session triggered by the user]

4

ME  UICC

ENVELOPE CALL CONTROL 1.3.1

5

UICC  ME

90 00

6

ME NG-SS

PDU SESSION ESTABLISHMENT REQUEST

Same PDU Session Establishment parameters within the CALL CONTROL ENVELOPE in step 4 are used to establish the PDU Session.

7

NG-SS ME

PDU SESSION ESTABLISHMENT ACCEPT

8

ME NG-SS

The PDU Session is established successfully without modification

ENVELOPE CALL CONTROL 1.3.1

Logically:

Device identities:

Source device: ME

Destination device: UICC

PDU Session Establishment parameters:

DNN: Test12.rs

Extended Protocol Discriminator: 5GS Session Management messages (2E)

PDU Session identity: Any valid value in the range of 1 to 15

Procedure Transaction Identity: Any valid value in the range of 1 to 254

5GS Session message identity: PDU session establishment request (C1)

PDU Session Type: IPv4v6

Extended Protocol configuration options:

Extended Protocol config. optional contents: content not checked

Location Information:

Mobile Country Codes (MCC): 001

Mobile Network Codes (MNC): 01

Tracking Area Code (TAC): 000001

NG-RAN Cell Identifier (NCI): 0001 (36 bits)

Coding:

BER-TLV:

D4

Note 1

02

02

82

81

0C

Note 2

25

0A

06

54

65

73

74

31

32

02

72

73

2E

Note 5

Note 6

C1

Note 3

Note 3

93

Note 4

13

0B

00

F1

10

00

00

01

00

00

00

00

1F

Note 1: The length of the BER-TLV is present here.

Note 2: Length of PDU session establishment parameters, dependent of optional fields.

Note 3: Integrity protection maximum data rate

Note 4: Optional fields / extended protocol configuration options. (byte 27 to 27+n if available).

Note 5: PDU session identity

Note 6: Procedure transaction identity

Expected Sequence 1.4 (CALL CONTROL on PDU Session for NG-RAN, PDU Session Establishment triggered by user, UICC sends 93 00)

Step

Direction

Message / Action

Comments

0

USER ME

Set and configure DNN as "TestGp.rs" in the terminal configuration for Always-on if required

[see initial conditions]

1

ME UICC

ENVELOPE CALL CONTROL 1.1.1

For Always-on PDU Session establishment

2

UICC ME

90 00

3

USER ME

Set and configure DNN as "Test12.rs" in the terminal configuration for a new PDU Session if required and trigger ME to establish the PDU Session.

[PDU Session triggered by the user]

4

ME  UICC

ENVELOPE CALL CONTROL 1.3.1

5

UICC  ME

93 00

6

ME NG-SS

ME shall not sent PDU SESSION ESTABLISHMENT REQUEST

The ME may retry to send the command.

Expected Sequence 1.5 (CALL CONTROL on PDU Session for NG-RAN, PDU Session Establishment triggered by user, allowed with modification of SM PDU DN request container)

Step

Direction

Message / Action

Comments

0

USER ME

Set and configure DNN as "TestGp.rs" in the terminal configuration for Always-on if required

[see initial conditions]

1

ME UICC

ENVELOPE CALL CONTROL 1.1.1

[For Always-on PDU Session establishment]

2

UICC ME

90 00

3

USER ME

Set and configure DNN as "Test12.rs" and DN-Specific Identity as 0123456789@Test.org in the terminal configuration for a new PDU Session if required and trigger ME to establish the PDU Session.

[PDU Session triggered by the user]

4

ME  UICC

ENVELOPE CALL CONTROL 1.5.1

5

UICC  ME

CALL_CONTROL_RESULT 1.5.1

[Call control result: "Allowed with modifications", DN-Specific Identity is modified to 0123456789@Test3gpp.org]

NOTE:

DNN is also modified to Test34.rs

6

ME NG-SS

PDU SESSION ESTABLISHMENT REQUEST

[The modified SM PDU DN request container and rest of the same PDU Session Establishment parameters within the CALL CONTROL ENVELOP in step 4 are used to establish the PDU Session.]

7

NG-SS ME

PDU SESSION ESTABLISHMENT ACCEPT

8

ME NG-SS

The PDU Session is established successfully with modified SM PDU DN request container (DN-Specific Identity).

NOTE:

DNN should be same as the DNN in CALL CONTROL ENVELOP, Test12.rs.

ENVELOPE CALL CONTROL 1.5.1

Logically:

Device identities:

Source device: ME

Destination device: UICC

PDU Session Establishment parameters:

DNN: Test12.rs

Extended Protocol Discriminator: 5GS Session Management messages (2E)

PDU Session identity: Any valid value in the range of 1 to 15

Procedure Transaction Identity: Any valid value in the range of 1 to 254

5GS Session message identity: PDU session establishment request (C1)

PDU Session Type: IPv4v6

SM PDU DN request container 0123456789@Test.org

Extended Protocol config:

Extended Protocol configuration options:

Extended Protocol config. optional contents: content not checked

Location Information:

Mobile Country Codes (MCC): 001

Mobile Network Codes (MNC): 01

Tracking Area Code (TAC): 000001

NG-RAN Cell Identifier (NCI): 0001 (36 bits)

Coding:

BER-TLV:

D4

Note 1

02

02

82

81

0C

Note 2

25

0A

06

54

65

73

74

31

32

02

72

73

2E

Note5

Note 6

C1

Note 3

Note3

93

Note 4

39

13

30

31

32

33

34

35

36

37

38

39

40

54

65

73

74

2E

6F

72

67

Note 4

13

0B

00

F1

10

00

00

01

00

00

00

00

1F

Note 1: The length of the BER-TLV is present here.

Note 2: Length of PDU session establishment parameters, dependent of optional fields.

Note 3: Integrity protection maximum data rate

Note 4: Optional fields / extended protocol configuration options. (byte 27 to 27+n if available, second Note 4 is handled accordingly).

Note 5: PDU session identity

Note 6: Procedure transaction identity

CALL CONTROL RESULT 1.5.1

Logically:

Call control result: ’02’ = Allowed, with modification

PDU Session Establishment parameters:

DNN: Test34.rs

Extended Protocol Discriminator: 5GS Session Management messages (2E)

PDU Session identity: Same PSI as used in ENVELOPE CALL CONTROL 1.5.1

Procedure Transaction Identity: Same PTI as used in ENVELOPE CALL CONTROL 1.5.1

5GS Session message identity: PDU session establishment request (C1)

PDU Session Type: IPv4v6

SM PDU DN request container: 0123456789@Test3gpp.org

Extended Protocol configuration options:

Extended Protocol config. optional contents: content not checked

Coding:

BER-TLV:

02

Note 1

0C

Note 2

25

0A

06

54

65

73

74

33

34

02

72

73

2E

Note 6

Note 7

C1

Note 3

Note 3

93

Note 4

39

17

30

31

32

33

34

35

36

37

38

39

40

54

65

73

74

33

67

70

70

2E

6F

72

67

Note 5

Note 1: The length of the BER-TLV is present here.

Note 2: Length of PDU session establishment parameters, dependent of optional fields.

Note 3: Integrity protection maximum data rate (same as received in ENVELOPE)

Note 4: Optional fields / extended protocol configuration options (same as received in ENVELOPE)

Note 5: Optional fields (if available in ENVELOPE)

Note 6: PDU session identity (same as received in ENVELOPE)

Note 7: Procedure transaction identity (same as received in ENVELOPE)

Expected Sequence 1.6 (CALL CONTROL on PDU Session for NG-RAN, PDU Session Establishment triggered by user, allowed with modification of ePCO)

Step

Direction

Message / Action

Comments

0

USER ME

Set and configure DNN as "TestGp.rs" in the terminal configuration for Always-on if required

[see initial conditions]

1

ME UICC

ENVELOPE CALL CONTROL 1.1.1

[For Always-on PDU Session establishment]

2

UICC ME

90 00

3

USER ME

Set and configure DNN as "Test12.rs" and the terminal is configured to include any ePCO containers in PDU Session Establishment if required and trigger ME to establish the PDU Session.

[PDU Session triggered by the user]

4

ME  UICC

ENVELOPE CALL CONTROL 1.6.1

5

UICC  ME

CALL_CONTROL_RESULT 1.6.1

[Call control result: "Allowed with modifications", include rfc1877_primary_dns_server IPv4 Address as 192.168.3.3 in IPCP container]

NOTE:

DNN is also modified to Test34.rs

6

ME NG-SS

PDU SESSION ESTABLISHMENT REQUEST

[The modified SM PDU DN request container and rest of the same PDU Session Establishment parameters within the CALL CONTROL ENVELOP in step 4 are used to establish the PDU Session.]

7

NG-SS ME

PDU SESSION ESTABLISHMENT ACCEPT

8

ME NG-SS

The PDU Session is established successfully with modified ePCO as included in the CALL_CONTROL_RESULT 1.6.1).

NOTE:

DNN should be same as the DNN in CALL CONTROL ENVELOP, Test12.rs.

ENVELOPE CALL CONTROL 1.6.1

Logically:

Device identities

Source device: ME

Destination device: UICC

PDU Session Establishment parameters

DNN: Test12.rs

Extended Protocol Discriminator: 5GS Session Management messages (2E)

PDU Session identity: Any valid value in the range of 1 to 15

Procedure Transaction Identity: Any valid value in the range of 1 to 254

5GS Session message identity: PDU session establishment request (C1)

PDU Session Type: IPv4v6

Extended Protocol configuration options:

Extended Protocol config. optional contents: content not checked

Location Information:

Mobile Country Codes (MCC): 001

Mobile Network Codes (MNC): 01

Tracking Area Code (TAC): 000001

NG-RAN Cell Identifier (NCI): 0001 (36 bits)

Coding:

BER-TLV:

D4

Note 1

02

02

82

81

0C

Note 2

25

0A

06

54

65

73

74

31

32

02

72

73

2E

Note 7

Note 8

C1

Note 3

Note 3

93

Note 4

7B

Note 5

Note 5

Note 6

Note 4

13

0B

00

F1

10

00

00

01

00

00

00

00

1F

Note 1: The length of the BER-TLV is present here

Note 2: Length of PDU session establishment parameters, dependent on optional fields

Note 3: Integrity protection maximum data rate

Note 4: Optional fields / extended protocol configuration options. (byte 27 to 27+n if available, second Note 4 is handled accordingly)

Note 5: Length of the ePCO (2 bytes)

Note 6: Data of extended protocol configuration fields

Note 7: PDU session identity

Note 8: Procedure transaction identity

CALL CONTROL RESULT 1.6.1

Logically:

Call control result: ’02’ = Allowed, with modification

PDU Session Establishment parameters:

DNN: Test34.rs

Extended Protocol Discriminator: 5GS Session Management messages (2E)

PDU Session identity: Same value as used in ENVELOPE CALL CONTROL 1.6.1

Procedure Transaction Identity: Same value as used in ENVELOPE CALL CONTROL 1.6.1

5GS Session message identity: PDU session establishment request (C1)

PDU Session Type: IPv4v6

Extended Protocol configuration options:

Protocol or Container: IPCP

rfc1332_conf_req

rfc1877_primary_dns_server_IPv4_address: 192.168.3.3

Additional protocol and container data as provided in ENVELOPE

Coding:

BER-TLV:

02

Note 1

0C

Note 2

25

0A

06

54

65

73

74

33

34

02

72

73

2E

Note 9

Note 10

C1

Note 3

Note 3

93

Note 4

7B

Note 5

Note 5

80

80

21

Note 6

01

00

Note 7

Note 7

81

06

C0

A8

03

03

Note 8

Note 1: The length of the BER-TLV is present here

Note 2: Length of PDU session establishment parameters, dependent of optional fields

Note 3: Integrity protection maximum data rate (same as received in ENVELOPE)

Note 4: Optional fields / extended protocol configuration options (same as received in ENVELOPE)

Note 5: Length of the ePCO (2 bytes)

Note 6: Length of the IPCP content

Note 7: Length of rfc1332_conf_req

Note 8: Additional protocol and container data as provided in ENVELOPE

Note 9: PDU session identity (same as received in ENVELOPE)

Note 10: Procedure transaction identity (same as received in ENVELOPE)

Expected Sequence 1.7 (CALL CONTROL on PDU Session for NG-RAN, PDU Session Establishment triggered by OPEN CHANNEL, UICC sends 90 00)

Step

Direction

Message / Action

Comments

0

USER ME

Set and configure DNN as "TestGp.rs" in the terminal configuration for Always-on if required

[see initial conditions]

1

ME UICC

ENVELOPE CALL CONTROL 1.1.1

For Always-on PDU Session establishment

2

UICC ME

90 00

3

USER ME

Set and configure DNN as "Test12.rs" in the terminal configuration for a new PDU Session by the OPEN CHANNEL if required.

4

UICC ME

PROACTIVE COMMAND PENDING: OPEN CHANNEL 1.7.1

[PDU Session triggered by the proactive command OPEN CHENNEL with Bearer Type 0x0C]

5

ME UICC

FETCH

6

ME USER

The ME may display channel opening information

7

ME  UICC

ENVELOPE CALL CONTROL 1.3.1

8

UICC  ME

90 00

9

ME NG-SS

PDU SESSION ESTABLISHMENT REQUEST

Same PDU Session Establishment parameters within the CALL CONTROL ENVELOPE in step 4 are used to establish the PDU Session.

10

NG-SS ME

PDU SESSION ESTABLISHMENT ACCEPT

11

ME UICC

TERMINAL RESPONSE: OPEN CHANNEL 1.7.1

[Command performed successfully]

12

ME NG-SS

The PDU Session is established successfully without modification

PROACTIVE COMMAND: OPEN CHANNEL 1.7.1

Logically:

Command details:

Command number: 1

Command type: OPEN CHANNEL

Command qualifier: immediate link establishment

Device identities:

Source device: UICC

Destination device: ME

Bearer description:

Bearer type: NG-RAN

Bearer parameter:

PDU Session Type: IPv4v6

Buffer:

Buffer size: 1400

Network access name: TestGp.rs

Text String: "UserLog" (User login)

Text String: "UserPwd" (User password)

UICC/ME interface transport level

Transport format: TCP

Port number: 44444

Data destination address 01.01.01.01

Coding:

BER-TLV:

D0

3D

81

03

01

40

01

82

02

81

82

35

02

0C

93

39

02

05

78

47

0A

06

54

65

73

74

31

32

02

72

73

0D

08

F4

55

73

65

72

4C

6F

67

0D

08

F4

55

73

65

72

50

77

64

3C

03

02

AD

9C

3E

05

21

01

01

01

01

TERMINAL RESPONSE: OPEN CHANNEL 1.7.1

Logically:

Command details:

Command number: 1

Command type: OPEN CHANNEL

Command qualifier: immediate link establishment

Device identities:

Source device: ME

Destination device: UICC

Result:

General Result: Command performed successfully

Channel status Channel identifier 1 and link established, or PDP context activated or PDU Session established

Bearer description:

Bearer type: NG-RAN

Bearer parameter:

PDU Session Type: IPv4v6

Buffer:

Buffer size: 1400

Coding:

BER-TLV:

81

03

01

40

01

82

02

82

81

83

01

00

38

02

81

00

35

02

0C

93

39

02

05

78

27.22.13.1.5 Test requirement

The ME shall operate in the manner defined in expected sequences 1.1 to 1.7.