7.1 NAS Protocol Procedures
37.571-23GPPPart 2: Protocol conformanceRelease 16TSUser Equipment (UE) conformance specification for UE positioning
7.1.1 UE Network Capability
7.1.1.1 Test Purpose (TP)
(1)
with { the UE having received an RRCConnectionSetup message. }
ensure that {
when { the UE transmits ATTACH REQUEST }
then { the UE correctly sets UE Network Capability IE values for LCS and LPP }
}
7.1.1.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 24.171 clause 4.2.1 and TS 24.301 clause 9.9.3.3.
[TS 24.171, clause 4.2.1]
The UE announces to the network its ability to support LCS notification mechanism and/or LPP messages using the UE Network Capability IE defined in 3GPP TS 24.301.
[TS 24.301, clause 9.9.3.3]
The purpose of the UE network capability information element is to provide the network with information concerning aspects of the UE related to EPS or interworking with GPRS. The contents might affect the manner in which the network handles the operation of the UE. The UE network capability information indicates general UE characteristics and it shall therefore, except for fields explicitly indicated, be independent of the frequency band of the channel it is sent on.
…
7.1.1.3 Test description
7.1.1.3.1 Pre-test conditions
System Simulator:
– Cell 1.
– Satellite signals switched off or not present
UE:
–
Preamble:
– the UE is in state Switched OFF (state 1) according to 3GPP 36.508 [8].
Related PICS/PIXIT Statements:
–
7.1.1.3.2 Test procedure sequence
Table 7.1.1.3.2-1: Main behaviour
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
U – S |
Message |
||||
1 |
<– |
RRC: SYSTEM INFORMATION (BCCH) |
– |
– |
|
1a |
UE is switched on. |
||||
2 |
UE transmits an RRCConnectionRequest message. |
–> |
RRC: RRCConnectionRequest |
– |
– |
3 |
SS transmits an RRCConnectionSetup message. |
<– |
RRC: RRCConnectionSetup |
– |
– |
4 |
The UE transmits an RRCConnectionSetupComplete message to confirm the successful completion of the connection establishment and to initiate the Attach procedure by including the ATTACH REQUEST message. The PDN CONNECTIVITY REQUEST message is piggybacked in ATTACH REQUEST |
–> |
RRC: RRCConnectionSetupComplete NAS: ATTACH REQUEST NAS: PDN CONNECTIVITY REQUEST |
1 |
P |
5 to 17 |
Steps 5 to 17 of the registration procedure described in TS 36.508 subclause 4.5.2.3 are performed. NOTE: The UE performs registration and the RRC connection is released. |
7.1.1.3.3 Specific message contents
Table 7.1.1.3.3-1: ATTACH REQUEST (step 4, Table 7.1.1.3.2-1)
Derivation Path: 24.301 clause 8.2.4 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
Protocol discriminator |
EMM |
|||
Security header type |
‘0000’B |
Plain NAS message, not security protected |
||
Attach request message identity |
‘0100 0001’B |
Attach request |
||
EPS attach type |
‘0001’B |
EPS attach |
EPS_only |
|
‘0010’B |
combined EPS/IMSI attach |
combined_EPS_IMSI |
||
NAS key set identifier |
Any allowed value |
|||
Old GUTI or IMSI |
Any allowed value |
|||
UE network capability |
Set according to Table 7.1.1.3.3-2 |
|||
ESM message container |
PDN CONNECTIVITY REQUEST message to request PDN connectivity to the default PDN |
|||
Old P-TMSI signature |
Not present or any allowed value |
|||
Additional GUTI |
Not present or any allowed value |
|||
Last visited registered TAI |
Not present or any allowed value |
|||
DRX parameter |
Not present or any allowed value |
|||
MS network capability |
Not present or any allowed value |
|||
Old location area identification |
Not present or any allowed value |
|||
TMSI status |
Not present or any allowed value |
|||
Mobile station classmark 2 |
Not present or any allowed value |
|||
Mobile station classmark 3 |
Not present or any allowed value |
|||
Supported Codecs |
Not present or any allowed value |
|||
Additional update type |
Not present |
EPS_only |
||
Additional update type |
Not present or any allowed value |
combined_EPS_IMSI |
Condition |
Explanation |
EPS_only |
See the definition below table 4.7.2-1 in TS 36.508. |
combined_EPS_IMSI |
See the definition below table 4.7.2-1 in TS 36.508. |
NOTE: This message is sent integrity protected when a valid security context exists and without integrity protection otherwise.
Table 7.1.1.3.3-2: UE network capability (step 4, Table 7.1.1.3.2-1)
Derivation Path: 24.301 clause 9.9.3.34 |
||||
Information Element Contents |
Value/remark |
Comment |
Condition |
|
Octet 7, bit 3 |
Set according to pc_MT_LR_loc_notif |
Location services (LCS) notification mechanisms capability |
||
Octet 7, bit 4 |
1 (LPP supported) |
LTE Positioning Protocol (LPP) capability |
||
All other octets/bits |
Any allowed value |