27.22.10 CALL CONTROL on EPS PDN Connection

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

27.22.10.1 Procedure for Mobile Originated calls

27.22.10.1.1 Definition and applicability

See clause 3.2.2.

27.22.10.1.2 Conformance requirement

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

– TS 31.111 [15] clause 7.3, clause 7.3.1.8, clause 8.98

– TS 24.301 [32], clause 6.4.3.2 and 6.5.4

– TS 36.508 [33], clause 6.6.1.

27.22.10.1.3 Test purpose

To verify that when the service "call control on EPS PDN connection by USIM" is available in the USIM Service Table, then for all EPS PDN connection activation (including those resulting from a OPEN CHANNEL proactive UICC command where E-UTRAN is selected), the ME shall first pass the corresponding PDN Connectivity 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 that the ME interpret the UICC returns response correctly.

27.22.10.1.4 Method of tests

27.22.10.1.4.1 Initial conditions

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

The default E-UTRAN/EPC UICC, the default E-UTRAN parameters and the following parameters are used:

Network access name: TestGp.rs

User login: UserLog

User password: UserPwd

UICC/ME interface transport level

Transport format: TCP

Port number: 44444

Data destination address: 01.01.01.01 (as an example)

The E-USS parameters of the system simulator are:

– Mobile Country Code (MCC) = 001;

– Mobile Network Code (MNC) = 01;

– Tracking Area Code (TAC) = 0001;

– E-UTRAN Cell Id = 0001.

The NB-SS parameters of the system simulator are:

– Mobile Country Code (MCC) = 001;

– Mobile Network Code (MNC) = 01;

– Tracking Area Code (TAC) = 0001;

– NB-IoT Cell Id = 0001.

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

– The call control on EPS PDN connection by USIM service is available in the USIM Service Table.

27.22.10.1.4.2 Procedure

Expected Sequence 1.1 (CALL CONTROL on EPS PDN for E-UTRAN – default PDN connection activation, allowed without modification)

Step

Direction

Message / Action

Comments

0

USER ME

Set and configure APN "TestGp.rs" in the terminal configuration if required

[see initial conditions]

1

ME UICC

ENVELOPE CALL CONTROL 1.1.1

For default PDN establishment during ATTACH procedure

2

UICC ME

CALL CONTROL RESULT 1.1.1

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

3

ME E-USS/NB-SS

The PDN connection is established successfully without modification

Same EPS PDN activation parameters used by the ME within the ENVELOPE CALL CONTROL are used to establish the PDN connection

ENVELOPE CALL CONTROL 1.1.1

Logically:

Device identities

Source device: ME

Destination device: UICC

EPS PDN connection activation parameters

Protocol Discriminator: EPS session management messages

EPS bearer identity: No EPS bearer identity assigned

Procedure Transaction Identity: 1

PDN connectivity request message identity: PDN connectivity request

Request type: Initial request

PDN Type: IPv4 and/or IPv6

Access Point Name: TestGp.rs

Protocol configuration options:

Protocol config. optional contents: content not checked

Capability configuration parameters 1

This parameter is optional. If present, the contents shall not be checked.

Location Information

Mobile Country Codes (MCC) 001

Mobile Network Codes (MNC) 01

Tracking Area Code (TAC): 0001

E-UTRAN Cell Identifier (ECI): 000000001

Capability configuration parameters 2

This parameter is optional. If present, the contents shall not be checked.

Coding:

Coding:

BER-TLV:

D4

Note1

02

02

82

81

7C

Note 2

02

01

D0

X1 Note 3

D1

28

0A

09

54

65

73

74

47

70

2E

72

73

Note 4

13

09

00

F1

10

00

01

00

00

00

1F

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

Note 2: Length of EPS PDN connection activation parameters, dependent of optional fields.

Note 3: X is the PDN Type.

Note 4: Optional fields.

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 EPS PDN for E-UTRAN – default PDN connection activation, not allowed)

Step

Direction

Message / Action

Comments

0

USER ME

Set and configure APN "TestGp.rs" in the terminal configuration if required

[see initial conditions]

1

ME  UICC

ENVELOPE CALL CONTROL 1.1.1

For default PDN establishment during ATTACH procedure

2

UICC  ME

CALL CONTROL RESULT 1.2.1

[Call control result: " not Allowed", ]

The ME may retry to send the command.

3

ME E-USS/NB-SS

The ME shall not send the PDN Connectivity Request message.

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 EPS PDN for E-UTRAN – default PDN connection activation, allowed with modification)

Step

Direction

Message / Action

Comments

0

USER ME

Set and configure APN "TestGp.rs" in the terminal configuration if required

[see initial conditions]

1

ME UICC

ENVELOPE CALL CONTROL 1.1.1

For default PDN establishment during ATTACH procedure

2

UICC ME

CALL CONTROL RESULT 1.3.1

[Call control result: "Allowed with modifications"]

3

ME E-USS/NB-SS

The PDN connection is established successfully with modification

Same EPS PDN activation parameters returned by the UICC in the CALL CONTROL RESULT 1.3.1 are used to establish the PDN connection.

CALL CONTROL RESULT 1.3.1

Logically:

Call control result: ’02’ = Allowed with modifications

Address:

EPS PDN connection activation parameters

Protocol Discriminator: EPS session management messages

EPS bearer identity: No EPS bearer identity assigned

Procedure Transaction Identity: 1

PDN connectivity request message identity: PDN connectivity request

Request type: Initial request

PDN Type: same PDN Type in step 1)

Access Point Name: Test12.rs

Coding:

BER-TLV:

02

Note 1

7C

Note 2

02

01

D0

X1 Note 3

28

0A

09

54

65

73

74

31

32

2E

72

73

Note 4

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

Note 2: Length of EPS PDN context activation parameters, dependant of optional fields.

Note 3: X is the PDN Type.

Note 4: Optional fields, same as in ENVELOPE CALL CONTROL 1.1.1.

Expected Sequence 1.4 (CALL CONTROL on EPS PDN for E-UTRAN – PDN connection triggered by user, UICC sends 90 00)

Step

Direction

Message / Action

Comments

0

USER ME

Set and configure APN "TestGp.rs" in the terminal configuration if required

[see initial conditions]

1

ME UICC

ENVELOPE CALL CONTROL 1.1.1

For default PDN establishment during ATTACH procedure

Same EPS PDN activation parameters used by the ME within the ENVELOPE CALL CONTROL in are used to establish the PDN connection

2

UICC ME

90 00

3

USER ME

Set and configure APN "Test12.rs" in the terminal configuration if required, and trigger the ME to establish a PDN connection

[see initial conditions]

4

ME  UICC

ENVELOPE CALL CONTROL 1.4.1

5

UICC  ME

90 00

6

ME E-USS

PDN CONNECTIVITY REQUEST

7

E-USS ME

ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST

[The E-UTRAN parameters are used]

8

ME E-USS

ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT

9

ME E-USS

The PDN connection is established successfully without modification

Same EPS PDN activation parameters used by the ME within the ENVELOPE CALL CONTROL in step 5 are used to establish the PDN connection

ENVELOPE CALL CONTROL 1.4.1

Logically:

Device identities

Source device: ME

Destination device: UICC

EPS PDN connection activation parameters

Protocol Discriminator: EPS session management messages

EPS bearer identity: No EPS bearer identity assigned

Procedure Transaction Identity: 2

PDN connectivity request message identity: PDN connectivity request

Request type: Initial request

PDN Type: IPv4 and/or IPv6

Access Point Name: Test12.rs

Other Protocol configuration options:

Protocol config. options contents: not checked

Location Information

Mobile Country Codes (MCC) 001

Mobile Network Codes (MNC) 01

Tracking Area Code (TAC): 0001

E-UTRAN Cell Identifier (ECI): 000000001

Coding:

BER-TLV:

D4

Note 1

02

02

82

81

7C

Note 2

02

01

D0

Note 3

D1

28

0A

09

54

65

73

74

31

32

2E

72

73

Note 4

13

09

00

F1

10

00

01

00

01

00

01

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

Note 2: Length of EPS PDN connection activation parameters, dependant of optional fields.

Note 3: X is the PDN Type.

Note 4: Optional fields.

Expected Sequence 1.5 (CALL CONTROL on EPS PDN for E-UTRAN – PDN connection triggered by user, UICC sends 93 00)

Step

Direction

Message / Action

Comments

1

ME UICC

ENVELOPE CALL CONTROL 1.1.1

For default PDN establishment during ATTACH procedure

Same EPS PDN activation parameters used by the ME within the ENVELOPE CALL CONTROL are used to establish the PDN connection.

2

UICC  ME

90 00

3

USER ME

Set and configure APN "Test12.rs" in the terminal configuration if required, and trigger the ME to establish a PDN connection

[see initial conditions]

4

ME UICC

ENVELOPE CALL CONTROL 1.4.1

5

UICC  ME

93 00

The ME may retry to send the command.

6

ME E-USS

The ME shall not send the PDN Connectivity Request message.

Expected Sequence 1.6 (CALL CONTROL on EPS PDN for E-UTRAN – PDN connection triggered by user, allowed with modification)

Step

Direction

Message / Action

Comments

0

USER ME

Set and configure APN "TestGp.rs" in the terminal configuration if required

[see initial conditions]

1

ME UICC

ENVELOPE CALL CONTROL 1.1.1

For default PDN establishment during ATTACH procedure

Same EPS PDN activation parameters used by the ME in the ENVELOPE CALL CONTROL 1.1.1 are used to establish the PDN connection

2

UICC ME

90 00

3

USER ME

Set and configure APN "Test12.rs" in the terminal configuration if required, and trigger the ME to establish a PDN connection

[see initial conditions]

4

ME UICC

ENVELOPE CALL CONTROL 1.4.1

.

5

UICC ME

CALL CONTROL RESULT 1.6.1

[Call control result: "Allowed with modifications", ]

6

ME E-USS

PDN CONNECTIVITY REQUEST

7

E-USS ME

ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST

[The E-UTRAN parameters are used]

8

ME E-USS

ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT

9

ME E-USS

The PDN connection is established successfully with modification

Same EPS PDN activation parameters returned by the UICC in the CALL CONTROL RESULT 1.6.1 are used to establish the PDN connection.

CALL CONTROL RESULT 1.6.1

Logically:

Call control result: ’02’ = Allowed with modifications

Address:

EPS PDN connection activation parameters

Protocol Discriminator: EPS session management messages

EPS bearer identity: No EPS bearer identity assigned

Procedure Transaction Identity: 2

PDN connectivity request message identity: PDN connectivity request

Request type: Initial request

PDN Type: same PDN Type in step 5)

Access Point Name: Test13.rs

Coding:

BER-TLV:

02

Note 1

7C

Note 2

02

02

D0

X1

Note 3

28

0A

09

54

65

73

74

31

33

2E

72

73

Note 4

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

Note 2: Length of EPS PDN context activation parameters, dependant of optional fields.

Note 3: X is the PDN Type.

Note 4: Optional fields, same as in ENVELOPE CALL CONTROL 1.4.1.

Expected Sequence 1.7 (CALL CONTROL on EPS PDN – PDN connection activation from OPEN CHANNEL command)

Step

Direction

Message / Action

Comments

0

USER ME

Set and configure APN "TestGp.rs" in the terminal configuration if required

[see initial conditions]

1

ME UICC

ENVELOPE CALL CONTROL 1.1.1

For default PDN establishment during ATTACH procedure

Same EPS PDN activation parameters used by the ME within the ENVELOPE CALL CONTROL are used to establish the PDN connection

2

UICC ME

90 00

3

USER ME

Set and configure APN "Test12.rs" in the terminal configuration if required

[see initial conditions]

4

UICC ME

PROACTIVE COMMAND PENDING: OPEN CHANNEL 1.1.1

5

ME UICC

FETCH

6

UICC ME

PROACTIVE COMMAND: OPEN CHANNEL 1.1.1

7

ME USER

The ME may display channel opening information

8

ME  UICC

ENVELOPE CALL CONTROL 1.4.1

9

UICC  ME

90 00

10

ME E-USS

PDN CONNECTIVITY REQUEST

The UE may request IPv4 or IPv4v6 as PDN type

11

E-USS ME

ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST

[The E-UTRAN parameters are used]

12

ME E-USS

ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT

13

ME UICC

TERMINAL RESPONSE: OPEN CHANNEL 1.1.1A

OR

TERMINAL RESPONSE: OPEN CHANNEL 1.1.1B

[Command performed successfully

OR

Command performed with modifications]

14

ME E-USS

The PDN connection is established successfully without modification

Same EPS PDN activation parameters returned by the ME within the ENVELOPE CALL CONTROL in step 8 are used to establish the PDN connection.

PROACTIVE COMMAND: OPEN CHANNEL 1.1.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

Bearer type: GPRS / UTRAN packet service / E-UTRAN

Precedence Class: 03

Delay Class: 04

Reliability Class: 02

Peak throughput class: 09

Mean throughput class: 31

Packet data protocol: 02 (IP)

Buffer

Buffer size: 1400

Network access name: Test12.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

42

81

03

01

40

01

82

02

81

82

35

07

02

03

04

02

09

1F

02

39

02

05

78

47

0A

06

54

65

73

74

30

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.1.1A

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

Bearer description

Bearer type: GPRS / UTRAN packet service / E-UTRAN

Bearer parameter:

Precedence Class: 03

Delay Class: 04

Reliability Class: 02

Peak throughput class: 09

Mean throughput class: 31

Packet data protocol: 02 (IP)

Buffer

Buffer size: 1400

Coding:

BER-TLV:

81

03

01

40

01

82

02

82

81

83

01

00

38

02

81

00

35

07

02

03

04

02

09

1F

02

39

02

05

78

TERMINAL RESPONSE: OPEN CHANNEL 1.1.1B

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 with modifications

Channel status Channel identifier 1 and link established or PDP context activated

Bearer description

Bearer type: GPRS / UTRAN packet service / E-UTRAN

Bearer parameter:

Precedence Class: 03

Delay Class: 04

Reliability Class: 02

Peak throughput class: 09

Mean throughput class: 31

Packet data protocol: 02 (IP)

Buffer

Buffer size: 1400

Coding:

BER-TLV:

81

03

01

40

01

82

02

82

81

83

01

07

38

02

81

00

35

07

02

03

04

02

09

1F

02

39

02

05

78

27.22.10.1.5 Test requirement

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