J.2 Request types and parameters
33.1803GPPRelease 17Security of the Mission Critical (MC) serviceTS
J.2.1 General
This clause defines the information elements that provide details of the authenticated request within an EAR payload.
J.2.2 Request Information element
This subclause defines the contents of a Request. The EAR provides details of the request and associates that request with an authenticated identity. The EAR shall be signed using the mechanism defined in Clause 8.5.5. For the contents of the EAR see Table J.1.2-1.
Message type: REQUEST PAYLOAD
Direction: Attached to a signalling request as defined in Clause 9.6.2.
Table J.2.2-1: REQUEST PAYLOAD message content
|
IEI |
Information Element |
Type/Reference |
Presence |
Format |
Length |
|
Request type |
Request type |
M |
V |
1 |
|
|
Request ID |
Request ID J.2.5 |
O |
TV |
3 |
|
|
Request Expiry |
Request Expiry J.2.4 |
O |
TV |
6 |
J.2.3 Request type
The purpose of the Request Type information element is to identify the type of the request.
The value part of the Request Type information element is coded as shown in Table J.2.3-1.
The Request Type information element is a type 3 information element with a length of 1 octet.
Table J.2.3-1: Request Types
|
Bits |
|||||||||
|
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
|
0 |
0 |
0 |
0 |
0 |
0 |
0 |
1 |
PRIVILEDGED SIGNALLING |
|
|
0 |
0 |
0 |
0 |
0 |
0 |
1 |
0 |
INTERWORKING SIGNALLING |
|
|
0 |
0 |
0 |
0 |
0 |
0 |
1 |
1 |
GROUP SIGNALLING |
|
|
0 |
0 |
0 |
0 |
0 |
1 |
0 |
1 |
MIGRATION SIGNALLING |
|
|
0 |
0 |
0 |
0 |
0 |
1 |
1 |
0 |
OFF-NETWORK SIGNALLING |
|
|
All other values are reserved. |
|||||||||
J.2.4 Request expiry
The Request expiry information element is used to indicate the UTC time when the request shall no longer be considered valid. After this time, all events (e.g. calls) caused by the request shall be terminated.
The Request expiry information element is coded as shown in Figure J.2.4-1 and Table J.2.4-1.
The Request expiry information element is a type 3 information element with a length of 6 octets.
|
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
|
Request expiry IEI |
octet 1 |
|||||||
|
Request expiry value |
octet 2 octet 6 |
|||||||
Figure J.2.4-1: Request expiry value
Table J.2.4-1: Request expiry value
|
Request expiry value (octet 1 to 5) The Request expiry value is an unsigned integer containing UTC time of the time when actions resulting from the request shall be terminated, in seconds since midnight UTC of January 1, 1970 (not counting leap seconds). |
J.2.5 Request IDs
J.2.5.1 Format
The Request ID information element is used to indicate the exact request made by a MC entity. Only Request IDs are defined for Priviledged signalling and off-network signalling Request Types. Request ID payload shall not be used for other request types.
The Request ID information element is coded as shown in Figure J.2.5.1-1. The contents are coded as described in subsequent subclauses.
The Request expiry information element is a type 3 information element with a length of 3 octets.
|
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
|
Request ID IEI |
octet 1 |
|||||||
|
Request ID value |
octet 2 octet 3 |
|||||||
Figure J.2.5.1-1: Request ID value
J.2.5.2 Request ID values for priviledged signalling
Table J.2.5.2-1: Request ID values for priviledged signalling
|
Byte 1 |
Byte 2 |
Privileged signalling request |
|
00000001 |
0000001 |
MCPTT Private call request in automatic commencement mode (TS 23.379). |
|
00000001 |
0000010 |
MCPTT Ambient listening call request (TS 23.379). |
|
00000001 |
0000011 |
MCPTT Remotely initiated MCPTT call request, in unnotified mode (TS 23.379). |
|
00000001 |
0000100 |
MCVideo Private call request (including private call, video pull and video push) in automatic commencement mode (TS 23.281). |
|
00000001 |
0000101 |
MCVideo Remote video push request in automatic commencement mode (TS 23.281). |
|
00000001 |
0000110 |
MCVideo Ambient viewing call request (TS 23.281). |
|
00000001 |
0000111 |
MCData standalone data request for application consumption (TS 23.282). |
|
00000001 |
0001000 |
MCData standalone session data request for application consumption (TS 23.282). |
|
00000001 |
0001001 |
MCData session data request for application consumption (TS 23.282). |
|
00000001 |
0001010 |
MCData group standalone data request for application consumption (TS 23.282). |
|
00000001 |
0001011 |
MCData group data request for application consumption (TS 23.282). |
|
00000001 |
0001100 |
MCData FD request with mandatory indication (TS 23.282). |
|
00000001 |
0001101 |
MCData group standalone FD request with mandatory indication (TS 23.282). |
J.2.5.3 Request IDs for off-network signalling
Table J.2.5.3-1: Request ID values for off-network
|
Byte 1 |
Byte 2 |
Off-network signalling request |
|
10000000 |
0000001 |
MCPTT Group call announcement (TS 23.379). |
|
10000000 |
0000010 |
MCPTT emergency alert announcement (TS 23.379). |
|
10000000 |
0000011 |
MCPTT Call setup request (TS 23.379). |
|
10000000 |
0000100 |
MCVideo Group communication announcement (TS 23.281). |
|
10000000 |
0000101 |
MCVideo emergency alert announcement (TS 23.281). |
|
10000000 |
0000110 |
MCVideo Private communication request (TS 23.281). |
|
10000000 |
0000111 |
MCVideo Capability request (TS 23.281). |
|
10000000 |
0001000 |
MCVideo Activity request (TS 23.281). |
|
10000000 |
0001001 |
MCData standalone data request (Clause 7.4.3.3.2, TS 23.282). |
|
10000000 |
0001010 |
MCData group standalone data request (Clause 7.4.3.4.2, TS 23.282). |