27.22.11 CALL CONTROL on PDP Context Activation
31.1243GPPMobile Equipment (ME) conformance test specificationRelease 16TSUniversal Subscriber Identity Module Application Toolkit (USAT) conformance test specification
27.22.11.1 Procedure for Mobile Originated calls
27.22.11.1.1 Definition and applicability
See clause 3.2.2.
27.22.11.1.2 Conformance requirement
The ME shall support the CALL CONTROL for PDP Context Activation facility as defined in:
– TSÂ 31.111Â [15] clause 7.3, clause 7.3.1.7, clause 8.72
– TS 24.008 [10], clause 6.1.3.3, 9.5.7 and 9.5.8
– TS 36.508 [33], clause 4.8.4.
27.22.11.1.3 Test purpose
To verify that when the service "call control on GPRS by USIM" is available in the USIM Service Table, then for all PS PDP Context Activation (including those resulting from an OPEN CHANNEL proactive UICC command where UTRAN is selected), the ME shall first pass the corresponding Activate PDP Context 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.11.1.4 Method of tests
27.22.11.1.4.1 Initial conditions
The ME is connected to the USIM Simulator and the USS/SS. Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.
The default GERAN/UTRAN/EPC UICC, the default GERAN/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 GERAN/UTRAN parameters of the system simulator are:
– Mobile Country Code (MCC) = 001;
– Mobile Network Code (MNC) = 01;
– Location Area Code (LAC) = 0001;- Cell Identity Value = 0001;
– The simulator must accept connections requests for APNs: TestGp.rs, Test12.rs and Test13.rs
The elementary files are coded as USIM Application Toolkit default with the following exceptions:
– The call control on GPRS by USIM service is available in the USIM Service Table.
27.22.11.4.2 Procedure
Expected Sequence 1.1 (CALL CONTROL on PDP Context Activation – default PDP 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 PDP establishment during ATTACH procedure |
|
2 |
UICC 🡪 ME |
CALL CONTROL RESULT 1.1.1 |
[Call control result: "Allowed", no modification] |
|
3 |
ME 🡪 USS/SS |
The PDP connection is established successfully without modification |
Same PDP activation parameters used by the ME within the ENVELOPE CALL CONTROL 1.1.1 are used to establish the PDN connection |
ENVELOPE CALL CONTROL 1.1.1
Logically:
Device identities
Source device: ME
Destination device: UICC
PDP Context Activation parameters
Protocol Discriminator: GPRS session management messages
Transaction Identifier: 0
Request PDP context activation message identity: Activate PDP context request
Requested NSAPI: NSAPI 5
Requested LLC SAPI: SAPI 3
Requested QoS: Subscribed QoS parameters
Requested PDP address:
PDP type organisation: as declared by the ME
PDP type: as declared by the ME
Address: as declared by the ME
Access point name: 06 54 65 73 74 47 70 02 72 73 ("TestGp.rs")
Protocol configuration options:
Protocol config. optional contents: content not checked
Location Information
MCC: 001
MNC: 01
Location Area Code: 0001
Cell Identity Value: 0001
Extended Cell Identity Value: RNC-id value (for Rel-4 onwards), see also Note 6
Coding:
|
BER-TLV |
D4 |
Note1 |
02 |
02 |
82 |
81 |
52 |
Note2 |
0A |
41 |
05 |
03 |
0E |
|
00 |
00 |
00 |
00 |
00 |
00 |
00 |
00 |
00 |
00 |
00 |
00 |
00 |
|
|
00 |
Note3 |
28 |
0A |
06 |
54 |
65 |
73 |
74 |
47 |
70 |
02 |
72 |
|
|
73 |
Note4 |
13 |
Note5 |
00 |
F1 |
10 |
00 |
01 |
00 |
01 |
Note6 |
Note1: Length of BER-TLV, dependant of optional fields.
Note2: Length of PDP context activation parameters, dependant of optional fields.
Note3: Requested PDP Address.
Note4: Optional fields.
Note5: Depending on the presence of the Extended Cell Identity Value the length is ’07’ or ’09’
Note6: The Extended Cell Identity Value is present in Rel-4 and onwards implementations, the values of the two bytes shall not be verified.
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 PDP Context Activation – default PDP connection activation, not allowed)
|
Step |
Direction |
Message / Action |
Comments |
|
0 |
USER ï‚® ME |
Set and configure APN "Test.Gp.rs" in the terminal configuration if required |
[see initial conditions] |
|
1 |
ME ï‚® UICC |
ENVELOPE CALL CONTROL 1.1.1 |
For default PDP 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 ï‚® USS/SS |
The ME shall not send the Activate PDP Context 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 PDP Context Activation – default PDP 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 PDP establishment during ATTACH procedure |
|
2 |
UICC 🡪 ME |
CALL CONTROL RESULT 1.3.1 |
[Call control result: "Allowed with modifications"] |
|
3 |
ME 🡪 USS/SS |
The PDP connection is established successfully with modification |
Same PDP activation parameters returned by the UICC within the CALL CONTROL RESULT 1.3.1 are used to establish the PDP connection |
CALL CONTROL RESULT 1.3.1
Logically:
Call control result: ’02’ = Allowed with modifications
Address:
PDP Context Activation parameters
Protocol Discriminator: GPRS session management messages
Transaction Identifier: 0
Request PDP context activation message identity: Activate PDP context request
Requested NSAPI: NSAPI 5
Requested LLC SAPI: SAPI 3
Requested QoS: Subscribed QoS parameters
Requested PDP address:
PDP type organisation: as declared by the ME
PDP type: as declared by the ME
Address: as declared by the ME
Access point name: 06 54 65 73 74 31 32 02 72 73 ("Test12.rs")
Coding:
|
BER-TLV: |
02 |
Note1 |
52 |
Note2 |
0A |
41 |
05 |
03 |
0E |
00 |
00 |
00 |
|
00 |
00 |
00 |
00 |
00 |
00 |
00 |
00 |
00 |
00 |
00 |
Note3 |
|
|
28 |
0A |
06 |
54 |
65 |
73 |
74 |
31 |
32 |
02 |
72 |
73 |
|
|
Note4 |
Note1: Length of BER-TLV, dependant on optional fields.
Note2: Length dependant on optional fields.
Note3: Requested PDP Address.
Note4: Optional fields.
Expected Sequence 1.4 (CALL CONTROL on PDP Context Activation – PDP connection triggered by user, UICC sends 90 00)
|
Step |
Direction |
Message / Action |
Comments |
|
0 |
USER → ME |
Set and configure APN "Test.Gp.rs" in the terminal configuration if required |
[see initial conditions] |
|
1 |
ME → UICC |
ENVELOPE CALL CONTROL 1.1.1 |
For default PDP establishment during ATTACH procedure Same PDP activation parameters used by the ME within 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 perform a PS call to Activate PDP Context Request connection |
[see initial conditions] |
|
4 |
ME → UICC |
ENVELOPE CALL CONTROL 1.4.1 |
|
|
5 |
UICC → ME |
90 00 |
|
|
6 |
ME → USS/SS |
ACTIVATE DEFAULT PDP CONTEXT REQUEST |
[The UTRAN parameters are used] |
|
7 |
USS/SS → ME |
ACTIVATE DEFAULT PDP CONTEXT ACCEPT |
|
|
8 |
ME 🡪 USS/SS |
The PDP connection is established successfully without modification |
Same PDP activation parameters used by the ME within the ENVELOPE CALL CONTROL 1.4.1 are used to establish the PDN connection |
ENVELOPE CALL CONTROL 1.4.1
Logically:
Device identities
Source device: ME
Destination device: UICC
PS PDP connection activation parameters
Protocol Discriminator: GPRS session management messages
Transaction Identifier: 0
Request PDP context activation message identity: Activate PDP context request
Requested NSAPI: NSAPI 5
Requested LLC SAPI: SAPI 3
Requested QoS: Subscribed QoS parameter
Requested PDP address:
PDP type organisation: as declared by the ME
PDP type: as declared by the ME
Address: as declared by the ME
Access Point Name: 06 54 65 73 74 31 32 02 72 73 ( "Test12.rs")
Other Protocol configuration options:
Protocol config. options contents: not checked
Location Information
MCC: 001
MNC: 01
Location Area Code: 0001
Cell Identity Value: 0001
Extended Cell Identity Value: RNC-id value (for Rel-4 onwards), see also Note 6
Coding:
|
BER-TLV |
D4 |
Note1 |
02 |
02 |
82 |
81 |
52 |
Note2 |
0A |
41 |
05 |
03 |
|
 |
0E |
00 |
00 |
00 |
00 |
00 |
00 |
00 |
00 |
00 |
00 |
00 |
|
 |
00 |
00 |
00 |
Note3 |
28 |
0A |
06 |
54 |
65 |
73 |
74 |
31 |
|
 |
32 |
02 |
72 |
73 |
Note4 |
13 |
Note5 |
00 |
F1 |
10 |
00 |
01 |
|
 |
00 |
01 |
Note6 |
Note1: Length of BER-TLV, dependant on optional fields.
Note2: Length of PDP context activation parameters, dependant on optional fields.
Note3: Requested PDP address.
Note4: Optional fields.
Note5: Depending on the presence of the Extended Cell Identity Value the length is ’07’ or ’09’
Note6: The Extended Cell Identity Value is present in Rel-4 and onwards implementations, the values of the two bytes shall not be verified
Expected Sequence 1.5 (CALL CONTROL on PDP Context Activation – PDP connection triggered by user, UICC sends 93 00)
|
Step |
Direction |
Message / Action |
Comments |
|
0 |
USER → ME |
Set and configure APN "Test.Gp.rs" in the terminal configuration if required |
[see initial conditions] |
|
1 |
ME 🡪 UICC |
ENVELOPE CALL CONTROL 1.1.1 |
For default PDP establishment during ATTACH procedure. Same EPS PDN activation parameters used by the ME within 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 perform a PS call to Activate PDP Context Request 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 🡪 USS/SS |
The ME shall not send the Activate PDP Context Request message. |
Expected Sequence 1.6 (CALL CONTROL on PDP Context Activation – PDP 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 PDP establishment during ATTACH procedure Same PDP parameters used by the ME within the ENVELOPE CALL CONTROL 1.1.1 are used to establish the PDP 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 perform a PS call to Activate PDP Context Request 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 🡪 USS/SS |
ACTIVATE PDP CONTEXT REQUEST |
[The UTRAN parameters are used] |
|
7 |
USS/SS → ME |
ACTIVATE PDP CONTEXT ACCEPT |
|
|
8 |
ME 🡪 USS/SS |
The PDP connection is established successfully with modification |
Same PDP parameters returned by the UICC within the CALL CONTROL RESULT 1.6.1 are used to establish the PDP connection. |
CALL CONTROL RESULT 1.6.1
Logically:
Call control result: ’02’ = Allowed with modifications
Address:
PDP Context Activation parameters
Protocol Discriminator: GPRS session management messages
Transaction Identifier: 0
Request PDP context activation message identity: Activate PDP context request
Requested NSAPI: NSAPI 5
Requested LLC SAPI: SAPI 3
Requested QoS: Subscribed QoS parameters
Requested PDP address:
PDP type organisation: as declared by the ME
PDP type: as declared by the ME
Address: as declared by the ME
Access point name: 06 54 65 73 74 31 33 02 72 73 ( "Test13.rs")
Coding:
|
BER-TLV: |
02 |
Note1 |
52 |
Note2 |
0A |
41 |
05 |
03 |
0E |
00 |
00 |
|
00 |
00 |
00 |
00 |
00 |
00 |
00 |
00 |
00 |
00 |
00 |
|
|
00 |
Note3 |
28 |
0A |
06 |
54 |
65 |
73 |
74 |
31 |
33 |
|
|
02 |
72 |
73 |
Note4 |
Note1: Length of BER-TLV, dependant on optional fields.
Note2: Length dependant on optional fields.
Note3: Requested PDP address.
Note4: Optional fields.
Expected Sequence 1.7 (CALL CONTROL on PDP Context Activation – PDP 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 |
UICC → ME |
PROACTIVE COMMAND PENDING: OPEN CHANNEL 1.1.1 |
|
|
2 |
ME → UICC |
FETCH |
|
|
3 |
UICC → ME |
PROACTIVE COMMAND: OPEN CHANNEL 1.1.1 |
|
|
4 |
ME → USER |
The ME may display channel opening information |
|
|
5 |
ME → UICC |
ENVELOPE CALL CONTROL 1.4.1 |
|
|
6 |
UICC → ME |
90 00 |
|
|
7 |
ME → USS/SS |
ACTIVATE DEFAULT PDP CONTEXT REQUEST |
[The UTRAN parameters are used] |
|
8 |
USS/SS → ME |
ACTIVATE DEFAULT PDP CONTEXT ACCEPT |
|
|
9 |
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] |
|
10 |
ME 🡪 USS/SS |
The PDP connection is established successfully without modification |
Same PDP parameters used by the ME within the ENVELOPE CALL CONTROL 1.4.1 are used to establish the PDP 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: 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 |
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 |
47 |
70 |
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: IP (Internet Protocol, IETF STD 5)
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: IP (Internet Protocol, IETF STD 5)
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.11.5 Test requirement
The ME shall operate in the manner defined in expected sequences 1.1 to 1.7.