4.4.8 Contents of files at the DF ProSe level
31.1023GPPCharacteristics of the Universal Subscriber Identity Module (USIM) applicationRelease 17TS
4.4.8.1 Introduction
This clause describes the additional files that are used for ProSe purposes.
DFProSe shall be present at the ADFUSIM level if service nº101 is "available" in EFUST .
4.4.8.2 EFPROSE_MON (ProSe Monitoring Parameters)
If service n°1 is "available" in the ProSe Service Table, this file shall be present.
This EF contains the authorized PLMNs for restricted ProSe direct discovery for public safety as described in TS 24.334 [70]. This file shall be used only if the ME is authorized as per content of EFAD or received service authorization from the ProSe Function.
Each record shall be associated with a different PLMN.
|
Identifier: ‘4F01’ |
Structure: linear fixed |
Optional |
||||
|
SFI: ’01’ |
||||||
|
Record size: Z bytes |
Update activity: low |
|||||
|
Access Conditions: READ PIN UPDATE ADM DEACTIVATE ADM ACTIVATE ADM |
||||||
|
Bytes |
Description |
M/O |
Length |
|||
|
1 to Z |
ProSe Discovery monitoring parameters TLV data object |
O |
Z bytes |
|||
ProSe Discovery monitoring parameters information
|
Description |
Value |
M/O/C |
Length (bytes) |
|
ProSe Discovery monitoring parameters TLV |
‘A0’ |
M |
1 |
|
Length |
X |
M |
Note |
|
PLMN Tag |
’80’ |
M |
1 |
|
Length |
L1 |
M |
Note |
|
PLMN value |
— |
M |
L1 |
|
Model Tag |
’82’ |
O |
1 |
|
Length |
1 |
C |
1 |
|
Model value |
— |
C |
1 |
|
Note: The length is coded according to ISO/IEC 8825-1 [35] |
|||
– PLMN
Contents:
As described in TS 24.333 [71], the PLMN code of the operator in which the UE is authorised to use ProSe direct discovery monitoring.
Coding:
As defined for the <X>/MonitoringPolicy/<X>/PLMN leaf in TS 24.333 [71].
– Model
Contents:
Model used for the ProSe direct discovery, as described in TS 24.334 [70].
Coding:
|
b8 |
b7 |
b6 |
b5 |
b4 |
b3 |
b2 |
b1 |
||||||||||||
|
b1 indicates if the UE is authorised for Restricted Model A monitoring policy |
|||||||||||||||||||
|
b2 indicates if the UE is authorised for Restricted Model B discoveree policy. |
|||||||||||||||||||
|
RFU (see TS 31.101 [11]) |
|||||||||||||||||||
If the data object is missing, the UE shall behave as if only Restricted Model A monitoring policy is allowed. All other values are reserved.
Unused bytes shall be set to ‘FF’.
4.4.8.3 EFPROSE_ANN (ProSe Announcing Parameters)
If service n°1 is "available" in the ProSe Service Table, this file shall be present.
This EF contains the authorized PLMNs for restricted ProSe direct discovery for public safety, as described in TS 24.334 [70]. This file shall be used only if the ME is authorized as per content of EFAD or received service authorization from the ProSe Function.
Each record shall be associated with a different PLMN.
|
Identifier: ‘4F02’ |
Structure: linear fixed |
Optional |
||||
|
SFI: ’02’ |
||||||
|
Record size: Z bytes |
Update activity: low |
|||||
|
Access Conditions: READ PIN UPDATE ADM DEACTIVATE ADM ACTIVATE ADM |
||||||
|
Bytes |
Description |
M/O |
Length |
|||
|
1 to Z |
ProSe Discovery announcing parameters TLV data object |
O |
Z bytes |
|||
ProSe Discovery announcing parameters information
|
Description |
Value |
M/O/C |
Length (bytes) |
|
ProSe Discovery announcing parameters TLV |
‘A0’ |
M |
1 |
|
Length |
X |
M |
Note 1 |
|
PLMN Tag |
’80’ |
M |
1 |
|
Length |
L1 |
M |
Note 1 |
|
PLMN value |
— |
M |
L1 |
|
Range Tag (Note 3) |
’81’ |
O |
1 |
|
Length |
L2 |
C |
Note 1 |
|
Range value |
— |
C |
L2 |
|
Model Tag |
’82’ |
O |
1 |
|
Length |
1 |
C |
1 |
|
Model value |
— |
C |
1 |
|
Note 1 : The length is coded according to ISO/IEC 8825-1 [35] Note 2: C; if the Tag is present, this is mandatory. Note 3: The Range data object is obsolete from Rel-13 onwards and shall be ignored if present. |
|||
– PLMN
Contents:
As described in TS 24.333 [71], the PLMN code of the operator in which the UE is authorised to use ProSe direct discovery announcing.
Coding:
As defined for the <X>/AnnouncingPolicy/<X>/PLMN leaf in TS 24.333 [71].
– Model
Contents:
Model used for the ProSe direct discovery, as described in TS 24.334 [70].
Coding:
|
b8 |
b7 |
b6 |
b5 |
b4 |
b3 |
b2 |
b1 |
||||||||||||
|
b1 indicates if the UE is authorised for Restricted Model A announcing policy |
|||||||||||||||||||
|
b2 indicates if the UE is authorised for Restricted Model B discoverer policy. |
|||||||||||||||||||
|
RFU (see TS 31.101 [11]) |
|||||||||||||||||||
If the data object is missing, the UE shall behave as if only Restricted Model A announcing policy is allowed. All other values are reserved.
Unused bytes shall be set to ‘FF’.
4.4.8.4 EFPROSEFUNC (HPLMN ProSe Function)
If service n°2 is "available" in the ProSe Service Table, this file shall be present.
This EF contains the IP address of the HPLMN ProSe Function.
NOTE: only usage of the first record is supported in the current release of the specification.
|
Identifier: ‘4F03’ |
Structure: linear fixed |
Optional |
||||
|
SFI: ’03’ |
||||||
|
File size: Z bytes |
Update activity: low |
|||||
|
Access Conditions: READ PIN UPDATE ADM DEACTIVATE ADM ACTIVATE ADM |
||||||
|
Bytes |
Description |
M/O |
Length |
|||
|
1 to Z |
HPLMN ProSe Function Address TLV data object |
M |
Z bytes |
|||
HPLMN ProSe Function information
|
Description |
Value |
M/O |
Length (bytes) |
|
HPLMN ProSe Function Tag |
’80’ |
M |
1 |
|
Length |
A + 1 |
M |
1 |
|
Address type |
— |
M |
1 |
|
HPLMN ProSe Function Address |
— |
M |
A |
– Address type
Contents:
Type of the HPLMN ProSe Function address.
Coding:
A value of ’00’ indicates FQDN, a value of ’01’ indicates IPv4, a value of ’02’ indicates IPv6. All other values are reserved.
– HPLMN ProSe Function Address
Contents:
Address of the HPLMN ProSe function.
Coding:
Depending on the Address type. When the HPLMN ProSe Function type is set to ’00’, the corresponding HPLMN ProSe Function Address shall be encoded to an octet string according to UTF-8 encoding rules as specified in IETF RFC 3629 [48].
Unused bytes shall be set to ‘FF’.
4.4.8.5 EFPROSE_RADIO_COM (ProSe Direct Communication Radio Parameters)
If service n°3 is "available" in the ProSe Service Table, this file shall be present.
This EF contains the radio paramenters to be used for ProSe direct communication for public safety when the UE is not served by E-UTRAN, as described in TS 24.334 [70]. This file shall be used only if the ME is authorized as per content of EFAD or received service authorization from the ProSe Function.
|
Identifier: ‘4F04’ |
Structure: transparent |
Optional |
||||
|
SFI: ’04’ |
||||||
|
File size: Z bytes |
Update activity: low |
|||||
|
Access Conditions: READ PIN UPDATE ADM DEACTIVATE ADM ACTIVATE ADM |
||||||
|
Bytes |
Description |
M/O |
Length |
|||
|
1 |
ProSe Direct Communication not served by E-UTRAN |
M |
1 byte |
|||
|
2 to Z + 1 |
ProSe Radio parameters TLV data object |
M |
Z bytes |
|||
The file may contain one or more ProSe Radio parameters TLV data objects.
ProSe Direct Communication not served by E-UTRAN:
Contents:
Indicates if the ME is authorized to perform ProSe Direct Communication and/or one-to-one ProSe direct communication when not served by E-UTRAN.
Coding:
|
b8 |
b7 |
b6 |
b5 |
b4 |
b3 |
b2 |
b1 |
||||||||||||
|
b1=0 indicates that the UE is not authorised to perform one-to-many ProSe direct communication when not served by E-UTRAN b1=1 indicates that UE is authorised to perform one-to-many ProSe direct communication when not served by E-UTRAN |
|||||||||||||||||||
|
b2=0 indicates that the UE is not authorised to perform one-to-one ProSe direct communication when not served by E-UTRAN b2=1 indicates that the UE is authorised to perform one-to-one ProSe direct communication when not served by E-UTRAN. |
|||||||||||||||||||
|
RFU (see TS 31.101 [11]) |
|||||||||||||||||||
ProSe Radio parameters information:
|
Description |
Value |
M/O/C |
Length (bytes) |
|
ProSe Direct Communication parameters TLV |
‘A0’ |
M |
1 |
|
Length |
X |
M |
Note 1 |
|
Geographical Area – Polygon Tag |
’80’ |
M |
1 |
|
Length |
L1 |
M |
Note 1 |
|
Geographical Area – Polygon value |
— |
M |
L1 |
|
Radio parameters Tag |
’81’ |
M |
1 |
|
Length |
L2 |
M |
Note 1 |
|
Radio parameters value |
— |
M |
L2 |
|
Note 1 : The length is coded according to ISO/IEC 8825-1 [35] Note 2: C; if the Tag is present, this is mandatory. |
|||
Each ProSe Radio parameters TLV data object shall contain one or more Geographical Area objects and one Radio parameters object.
– Geographical Area – Polygon Tag ’80’
Contents:
A geographical area defined by a polygon with 3 or more points.
Coding:
|
1 to 3 |
Latitude of point 1 |
M |
3 bytes |
|
4 to 6 |
Longitude of point 1 |
M |
3 bytes |
|
7 to 9 |
Latitude of point 2 |
M |
3 bytes |
|
10 to 12 |
Longitude of point 2 |
M |
3 bytes |
|
13 to 15 |
Latitude of point 3 |
M |
3 bytes |
|
16 to 18 |
Longitude of point 3 |
M |
3 bytes |
|
: |
: |
: |
: |
|
(6n-5) to 6n-3 |
Latitude of point n |
M |
3 bytes |
|
(6n-2) to 6n |
Longitude of point n |
M |
3 bytes |
|
Latitude and longitude are coded as defined in clause 6.1 of 3GPP TS 23.032 [75]. |
|||
NOTE: The upper limit of 15 specified in 3GPP TS 23.032 [9] for the number of points in a polygon shape does not apply to the number of coordinates in a geographical area described as a polygon for ProSe communications.
– Radio parameters Tag ’81’
Contents:
The radio parameters used for ProSe Direct Communication
Coding:
Coded as SL-Preconfiguration in 3GPP TS 36.331 [74].
4.4.8.6 EFPROSE_RADIO_MON (ProSe Direct Discovery Monitoring Radio Parameters)
If service n°4 is "available" in the ProSe Service Table, this file shall be present.
This EF contains the radio paramenters to be used for ProSe direct communication for public safety when the UE is not served by E-UTRAN, as described in TS 24.334 [70]. This file shall be used only if the ME is authorized as per content of EFAD or received service authorization from the ProSe Function.
|
Identifier: ‘4F05’ |
Structure: transparent |
Optional |
||||
|
SFI: ’05’ |
||||||
|
File size: Z bytes |
Update activity: low |
|||||
|
Access Conditions: READ PIN UPDATE ADM DEACTIVATE ADM ACTIVATE ADM |
||||||
|
Bytes |
Description |
M/O |
Length |
|||
|
1 |
ProSe Direct Discovery Monitoring not served by E-UTRAN |
M |
1 byte |
|||
|
2 to Z + 1 |
ProSe Radio parameters TLV data object |
M |
Z bytes |
|||
ProSe Direct Discovery monitoring not served by E-UTRAN:
Contents:
Indicates if the ME is authorized to perform restricted ProSe Direct Discovery monitoring when not served by E-UTRAN.
Coding:
|
b8 |
b7 |
b6 |
b5 |
b4 |
b3 |
b2 |
b1 |
||||||||||||
|
b1=0 indicates that the UE is not authorised to perform ProSe direct discovery model A monitoring when not served by E-UTRAN b1=1 indicates that the UE is authorised to perform ProSe direct discovery model A monitoring when not served by E-UTRAN |
|||||||||||||||||||
|
b2=0 indicates that the UE is not authorised to perform ProSe direct discovery model B discoveree operation when not served by E-UTRAN b2=1 indicates that the UE is authorised to perform ProSe direct discovery model B discoveree operation when not served by E-UTRAN. |
|||||||||||||||||||
|
RFU (see TS 31.101 [11]) |
|||||||||||||||||||
ProSe Radio parameters information
|
Description |
Value |
M/O/C |
Length (bytes) |
|
ProSe Radio parameters TLV |
‘A0’ |
M |
1 |
|
Length |
X |
M |
Note 1 |
|
Geographical Area – Polygon Tag |
’80’ |
M |
1 |
|
Length |
L1 |
M |
Note 1 |
|
Geographical Area – Polygon value |
— |
M |
L1 |
|
Radio parameters Tag |
’81’ |
M |
1 |
|
Length |
L2 |
M |
Note 1 |
|
Radio parameters value |
— |
M |
L2 |
|
Note 1 : The length is coded according to ISO/IEC 8825-1 [35] Note 2: C; if the Tag is present, this is mandatory. |
|||
Each ProSe Radio parameters TLV data object shall contain one or more Geographical Area objects and one Radio parameters object.
– Geographical Area – Polygon Tag ’80’
Contents:
A geographical area defined by a polygon with 3 or more points.
Coding:
|
1 to 3 |
Latitude of point 1 |
M |
3 bytes |
|
4 to 6 |
Longitude of point 1 |
M |
3 bytes |
|
7 to 9 |
Latitude of point 2 |
M |
3 bytes |
|
10 to 12 |
Longitude of point 2 |
M |
3 bytes |
|
13 to 15 |
Latitude of point 3 |
M |
3 bytes |
|
16 to 18 |
Longitude of point 3 |
M |
3 bytes |
|
: |
: |
: |
: |
|
(6n-5) to 6n-3 |
Latitude of point n |
M |
3 bytes |
|
(6n-2) to 6n |
Longitude of point n |
M |
3 bytes |
|
Latitude and longitude are coded as defined in clause 6.1 of 3GPP TS 23.032 [75]. |
|||
NOTE: The upper limit of 15 specified in 3GPP TS 23.032 [9] for the number of points in a polygon shape does not apply to the number of coordinates in a geographical area described as a polygon for ProSe communications.
– Radio parameters Tag ’81’
Contents:
The radio parameters used for ProSe Direct Communication
Coding:
Coded as SL-Preconfiguration in 3GPP TS 36.331 [74].
4.4.8.7 EFPROSE_RADIO_ANN (ProSe Direct Discovery Announcing Radio Parameters)
If service n°5 is "available" in the ProSe Service Table, this file shall be present.
This EF contains the radio paramenters to be used for ProSe direct communication for public safety when the UE is not served by E-UTRAN, as described in TS 24.334 [70]. This file shall be used only if the ME is authorized as per content of EFAD or received service authorization from the ProSe Function.
|
Identifier: ‘4F06’ |
Structure: transparent |
Optional |
||||
|
SFI: ’06’ |
||||||
|
File size: Z bytes |
Update activity: low |
|||||
|
Access Conditions: READ PIN UPDATE ADM DEACTIVATE ADM ACTIVATE ADM |
||||||
|
Bytes |
Description |
M/O |
Length |
|||
|
1 |
ProSe Direct Discovery Announcing not served by E-UTRAN |
M |
1 byte |
|||
|
2 to Z + 1 |
ProSe Radio parameters TLV data object |
M |
Z bytes |
|||
ProSe Direct Discovery announcing not served by E-UTRAN:
Contents:
Indicates if the ME is authorized to perform restricted ProSe Direct Discovery announcing when not served by E-UTRAN.
Coding:
|
b8 |
b7 |
b6 |
b5 |
b4 |
b3 |
b2 |
b1 |
||||||||||||
|
b1=0 indicates that the UE is not authorised to perform ProSe direct discovery model A announcing when not served by E-UTRAN b1=1 indicates that the UE is authorised to perform ProSe direct discovery model A announcing when not served by E-UTRAN |
|||||||||||||||||||
|
b2=0 indicates that the UE is not authorised to perform ProSe direct discovery model B discoverer operation when not served by E-UTRAN b2=1 indicates that the UE is authorised to perform ProSe direct discovery model B discoverer operation when not served by E-UTRAN. |
|||||||||||||||||||
|
RFU (see TS 31.101 [11]) |
|||||||||||||||||||
ProSe Radio parameters information
|
Description |
Value |
M/O/C |
Length (bytes) |
|
ProSe Radio parameters TLV |
‘A0’ |
M |
1 |
|
Length |
X |
M |
Note 1 |
|
Geographical Area – Polygon Tag |
’80’ |
M |
1 |
|
Length |
L1 |
M |
Note 1 |
|
Geographical Area – Polygon value |
— |
M |
L1 |
|
Radio parameters Tag |
’81’ |
M |
1 |
|
Length |
L2 |
M |
Note 1 |
|
Radio parameters value |
— |
M |
L2 |
|
Note 1 : The length is coded according to ISO/IEC 8825-1 [35] Note 2: C; if the Tag is present, this is mandatory. |
|||
Each ProSe Radio parameters TLV data object shall contain one or more Geographical Area objects and one Radio parameters object.
– Geographical Area – Polygon Tag ’80’
Contents:
A geographical area defined by a polygon with 3 or more points.
Coding:
|
1 to 3 |
Latitude of point 1 |
M |
3 bytes |
|
4 to 6 |
Longitude of point 1 |
M |
3 bytes |
|
7 to 9 |
Latitude of point 2 |
M |
3 bytes |
|
10 to 12 |
Longitude of point 2 |
M |
3 bytes |
|
13 to 15 |
Latitude of point 3 |
M |
3 bytes |
|
16 to 18 |
Longitude of point 3 |
M |
3 bytes |
|
: |
: |
: |
: |
|
(6n-5) to 6n-3 |
Latitude of point n |
M |
3 bytes |
|
(6n-2) to 6n |
Longitude of point n |
M |
3 bytes |
|
Latitude and longitude are coded as defined in clause 6.1 of 3GPP TS 23.032 [75]. |
|||
NOTE: The upper limit of 15 specified in 3GPP TS 23.032 [9] for the number of points in a polygon shape does not apply to the number of coordinates in a geographical area described as a polygon for ProSe communications.
– Radio parameters Tag ’81’
Contents:
The radio parameters used for ProSe Direct Communication
Coding:
Coded as SL-Preconfiguration in 3GPP TS 36.331 [74].
4.4.8.8 EFPROSE_POLICY (ProSe Policy Parameters)
If service n°6 is "available" in the ProSe Service Table, this file shall be present.
This EF contains the policy paramenters to be used for ProSe direct communication for public safety, as described in TS 24.334 [70]. This file shall be used only if the ME is authorized as per content of EFAD or received service authorization from the ProSe Function.
Each record shall be associated with a different ProSe group.
|
Identifier: ‘4F07’ |
Structure: linear fixed |
Optional |
||||
|
SFI: ’07’ |
||||||
|
Record size: Z bytes |
Update activity: low |
|||||
|
Access Conditions: READ PIN UPDATE ADM DEACTIVATE ADM ACTIVATE ADM |
||||||
|
Bytes |
Description |
M/O |
Length |
|||
|
1 to Z |
ProSe Policy parameters TLV data object |
M |
Z bytes |
|||
ProSe Policy parameters information:
|
Description |
Value |
M/O |
Length (bytes) |
|
ProSe Policy parameters Tag |
‘A0’ |
M |
1 |
|
Length |
X |
M |
Note |
|
ProSe Layer-2 Group ID tag |
’80’ |
M |
1 |
|
Length |
3 |
M |
1 |
|
ProSe Layer-2 Group ID |
— |
M |
3 |
|
ProSe UE ID tag |
’81’ |
M |
1 |
|
Length |
3 |
M |
1 |
|
ProSe UE ID |
— |
M |
3 |
|
ProSe Group IP multicast address tag |
’82’ |
M |
1 |
|
Length |
A |
M |
1 |
|
ProSe Group IP multicast address |
— |
M |
A |
|
Address type tag |
’83’ |
M |
1 |
|
Length |
1 |
M |
1 |
|
Address type |
— |
M |
1 |
|
IPv4 address as source tag |
’84’ |
O |
1 |
|
Length |
4 |
C |
1 |
|
IPv4 address as source |
— |
C |
4 |
|
Group related security tag |
’85’ |
M |
1 |
|
Length |
B |
M |
Note |
|
Group related security contents |
— |
M |
B |
|
Application Layer Group ID tag |
’86’ |
O |
1 |
|
Length |
C |
C |
Note |
|
Application Layer Group ID |
— |
C |
C |
|
Note: The length is coded according to ISO/IEC 8825-1 [35] |
|||
– ProSe Layer-2 Group ID tag ’80’
Contents:
Contains the ProSe Layer-2 Group ID, as defined in TS 23.303 [73]
Coding:
As per TS 33.303 [72]
– ProSe UE ID tag ’81’
Contents:
Contains the ProSe UE ID, equivalent to the layer-2 source address of the sending UE, as defined in TS 23.303 [73]
Coding:
As per TS 33.303 [72]
– ProSe Group IP multicast address tag ’82’
Contents:
IPv4 or IPv6 group IP multicast addressed to be used for ProSe direct communication associated with the corresponding layer-2 group ID.
Coding:
Depending on the Address type
– Address type tag ’83’
Contents:
Type of IP address.
Coding:
A value of ’01’ indicates IPv4, a value of ’02’ indicates IPv6. All other values are reserved.
– IPv4 address as source tag ’84’
Contents:
IPv4 addressed to be used as source, in case of IPv4 address. This TLV shall be ignored if address type is different from IPv4.
Coding:
IPv4 address
– Group related security tag ’85’
Contents:
Parameters related to the group security.
Coding:
|
1 to 32 |
PGK as defined in TS 33.303 [72] |
M |
32 bytes |
|
33 |
PGK Id as defined in TS 33.303 [72]. |
M |
1 byte |
|
34 |
Algorithm Info as defined in TS 33.303 [72] |
M |
1 byte |
|
35 to B |
RFU |
O |
(B-34) bytes |
– Application Layer Group ID ’86’
Contents:
Application layer group that the UE belongs to.
Coding:
As per TS 23.303 [73]
Unused bytes shall be set to ‘FF’.
4.4.8.9 EFPROSE_PLMN (ProSe PLMN Parameters)
If service n°3 is "available" in the ProSe Service Table, this file shall be present.
This EF contains the authorized PLMNs for ProSe direct communication for public safety, as described in TS 24.334 [70]. This file shall be used only if the ME is authorized as per content of EFAD or received service authorization from the ProSe Function.
Each record shall be associated with a different PLMN.
|
Identifier: ‘4F08’ |
Structure: linear fixed |
Optional |
||||
|
SFI: ’08’ |
||||||
|
Record size: Z bytes |
Update activity: low |
|||||
|
Access Conditions: READ PIN UPDATE ADM DEACTIVATE ADM ACTIVATE ADM |
||||||
|
Bytes |
Description |
M/O |
Length |
|||
|
1 to Z |
ProSe PLMN parameters TLV data object |
O |
Z bytes |
|||
ProSe Policy parameters information:
|
Description |
Value |
M/O |
Length (bytes) |
|
ProSe PLMN parameters Tag |
‘A0’ |
M |
1 |
|
Length |
X |
M |
Note |
|
PLMN tag |
’80’ |
M |
1 |
|
Length |
3 |
M |
1 |
|
PLMN |
— |
M |
3 |
|
Direct communication authorisation tag |
’81’ |
O |
1 |
|
Length |
1 |
C |
1 |
|
Direct communication authorisation |
— |
C |
1 |
|
NOTE: The length is coded according to ISO/IEC 8825-1 [35] |
|||
– PLMN tag ’80’
Contents:
Contains the PLMNs in which the UE is authorised to perform ProSe direct communication when served by E-UTRAN
Coding:
According to TS 24.008 [9].
– Direct communication authorisation tag ’81’
Contents:
Indicates if the UE is authorised to use one-to-one and/or one-to-many ProSe direct communication.
Coding:
|
b8 |
b7 |
b6 |
b5 |
b4 |
b3 |
b2 |
b1 |
||||||||||||
|
b1 indicates if the UE is authorised for one-to-many ProSe direct communication |
|||||||||||||||||||
|
b2 indicates if the UE is authorised for one-to-one ProSe direct communication. |
|||||||||||||||||||
|
RFU (see TS 31.101 [11]) |
|||||||||||||||||||
If the data object is missing, the UE shall behave as if only one-to-many ProSe direct communication is authorized in the PLMN. All other values are reserved.
Unused bytes shall be set to ‘FF’.
4.4.8.10 EFPROSE_GC (ProSe Group Counter)
If service n°7 is "available" in the ProSe Service Table, this file shall be present.
This EF contains the PTK ID and Counter associated with the PGK currently in use for a ProSe Group.
|
Identifier: ‘4F09’ |
Structure: Transparent |
Optional |
||||
|
SFI: ’09’ |
||||||
|
File size: X >= 9 bytes |
Update activity: high |
|||||
|
Access Conditions: READ PIN UPDATE PIN DEACTIVATE ADM ACTIVATE ADM |
||||||
|
Bytes |
Description |
M/O |
Length |
|||
|
1 to L |
ProSe Group Counter data object |
O |
L bytes |
|||
|
L+1 to 2xL |
ProSe Group Counter data object |
O |
L bytes |
|||
|
: |
: |
: |
: |
|||
ProSe Group Counter:
|
Description |
Value |
M/O |
Length (bytes) |
|
ProSe Group Counter Tag |
’80’ |
M |
1 |
|
Length |
X >= 7 |
M |
Note |
|
ProSe Layer-2 Group ID |
— |
M |
3 |
|
PTK ID |
— |
M |
2 |
|
Counter |
— |
M |
2 |
|
RFU |
— |
O |
X |
|
Note: The length is coded according to ISO/IEC 8825-1 [35] |
|||
– ProSe Layer-2 Group ID
Contents:
Contains the ProSe Layer-2 Group ID, as defined in TS 23.303 [73]
Coding:
As per TS 33.303 [72]
– PTK ID
Contents:
Contains the PTK value, as defined in TS 33.303 [72]
Coding:
As per TS 33.303 [72]
– Counter
Contents:
Contains the Counter for the PGK used in the group, as defined in TS 33.303 [72]
Coding:
As per TS 33.303 [72]
Unused bytes shall be set to ‘FF’.
4.4.8.11 EFPST (ProSe Service Table)
If service n°101 is "available" in the USIM Service Table, this file shall be present. This EF indicates which ProSe services are available. If a service is not indicated as available in the ProSe Service Table, the ME shall not select this service.
|
Identifier: ‘4F10’ |
Structure: transparent |
Optional |
||||
|
SFI: ’10’ |
||||||
|
File size: X bytes, (X ≥ 1) |
Update activity: low |
|||||
|
Access Conditions: READ PIN UPDATE ADM DEACTIVATE ADM ACTIVATE ADM |
||||||
|
Bytes |
Description |
M/O |
Length |
|||
|
1 |
Services n°1 to n°8 |
M |
1 byte |
|||
|
2 |
Services n°9 to n°16 |
O |
1 byte |
|||
|
etc. |
||||||
|
X |
Services n°(8X‑7) to n°(8X) |
O |
1 byte |
|||
|
‑Services |
||
|
Contents: |
Service n°1: |
ProSe direct discovery parameters |
|
Service n°2: |
HPLMN ProSe Function |
|
|
Service n°3: |
ProSe Direct Communication radio parameters |
|
|
Service n°4: |
ProSe Direct Discovery monitoring radio parameters |
|
|
Service n°5: |
ProSe Direct Discovery announcing radio parameters |
|
|
Service n°6: |
ProSe policy parameters |
|
|
Service n°7: |
ProSe group counter |
|
|
Service n°8: |
ProSe Usage Information Reporting configuration |
|
|
Service n°9: |
UICC ProSe Direct Communication usage information reporting |
|
|
Service n°10 |
ProSe Group Member Discovery parameters |
|
|
Service n°11 |
ProSe Relay parameters |
The EF shall contain at least one byte. Further bytes may be included, but if the EF includes an optional byte, then it is mandatory for the EF to also contain all bytes before that byte. Other services are possible in the future and will be coded on further bytes in the EF.
If service n°9 is "available", then service n°8 shall also be "available".
If service n°10 is "available", then service n°1 shall also be "available".
Coding:
Same as coding of USIM Service Table
4.4.8.12 EFPROSE_UIRC (ProSe UsageInformationReportingConfiguration)
If service n°8 is "available" in the ProSe Service Table, this file shall be present.
This EF contains the description of the configuration to be used by the UE for reporting the usage information for direct communication for public safety, as described in TS 24.334 [70] and TS 32.277 [77]. This file shall be used only if the UE is authorized for direct communication as per content of EFAD or received service authorization from the ProSe Function.
|
Identifier: ‘4F11’ |
Structure: transparent |
Optional |
||||
|
SFI: ’11’ |
||||||
|
File size: Z bytes |
Update activity: low |
|||||
|
Access Conditions: READ PIN UPDATE ADM DEACTIVATE ADM ACTIVATE ADM |
||||||
|
Bytes |
Description |
M/O |
Length |
|||
|
1 to Z |
ProSe UsageInformationReportingConfiguration TLV data objects |
M |
Z bytes |
|||
ProSe UsageInformationReportingConfiguration parameters information:
|
Description |
Value |
M/O |
Length (bytes) |
|---|---|---|---|
|
ProSe ServerAddress tag |
’80’ |
C |
1 |
|
Length |
A |
C |
Note |
|
ProSe ServerAddress |
— |
C |
A |
|
ProSe CollectionPeriod tag |
’81’ |
M |
1 |
|
Length |
3 |
M |
1 |
|
ProSe CollectionPeriod |
— |
M |
3 |
|
ProSe ReportingWindow tag |
’82’ |
M |
1 |
|
Length |
3 |
M |
1 |
|
ProSe ReportingWindow |
— |
M |
3 |
|
ProSe ReportGroupParameters tag |
’83’ |
O |
1 |
|
Length |
1 |
O |
1 |
|
ProSe ReportGroupParameters |
— |
O |
1 |
|
ProSe ReportTimeStampsFirstTransmissionAndReception tag |
’84’ |
O |
1 |
|
Length |
1 |
O |
1 |
|
ProSe ReportTimeStampsFirstTransmissionAndReception |
— |
O |
1 |
|
ProSe ReportDataTransmitted tag |
’85’ |
O |
1 |
|
Length |
1 |
O |
1 |
|
ProSe ReportDataTransmitted |
— |
O |
1 |
|
ProSe ReportDataReceived tag |
’86’ |
O |
1 |
|
Length |
1 |
O |
1 |
|
ProSe ReportDataReceived |
— |
O |
1 |
|
ProSe ReportTimeStampsOutOfCoverage tag |
’87’ |
O |
1 |
|
Length |
1 |
O |
1 |
|
ProSe ReportTimeStampsOutOfCoverage |
— |
O |
1 |
|
ProSe ReportLocationInCoverage tag |
’88’ |
O |
1 |
|
Length |
1 |
O |
1 |
|
ProSe ReportLocationInCoverage |
— |
O |
1 |
|
ProSe ReportRadioParameters tag |
’89’ |
O |
1 |
|
Length |
1 |
O |
1 |
|
ProSe ReportRadioParameters |
— |
O |
1 |
|
NOTE: The length is coded according to ISO/IEC 8825-1 [35] |
|||
– ProSe ServerAddress
Contents:
As described in TS 24.333 [71], used to determine the IPv4 or IPv6 address the UE or the USIM shall use to send the usage report to. If no server address is provided, the UE shall upload the usage information reports to the IP address of the HPLMN ProSe Function. If the USIM supports storage of the usage information, the server address is mandatory.
Coding:
As defined for the ProSe ServerAddress leaf in TS 24.333 [71].
– ProSe CollectionPeriod
Contents:
As described in TS 24.333 [71], contains the time interval, in unit of minutes, at which the UE shall generate the usage information reports. Setting the CollectionPeriod to a value of 0 disables generation of usage information reports at the UE.
Coding:
As defined for the ProSe CollectionPeriod leaf in TS 24.333 [71].
– ProSe ReportingWindow
Contents:
As described in TS 24.333 [71], contains the time window, in units of minutes, during which the UE shall upload the usage information report to the server. Setting the ReportingWindow to a value of 0 disables upload of the usage information reports by the UE.
Coding:
As defined for the ProSe ReportingWindow leaf in TS 24.333 [71].
– ProSe ReportGroupParameters
Contents:
As described in TS 24.333 [71], indicates whether or not the UE shall report the group parameters for one-to-many ProSe direct communication in the usage information. The default value 0 applies if this TLV is not provisioned.
Coding:
As defined for the ProSe ReportGroupParameters leaf in TS 24.333 [71].
– ProSe ReportTimeStampsFirstTransmissionAndReception
Contents:
As described in TS 24.333 [71], indicates whether or not the UE shall report the time stamps of the first transmission/reception during the collection period in the usage information. The default value 0 applies if this TLV is not provisioned
Coding:
As defined for the ProSe ReportTimeStampsFirstTransmissionAndReception leaf in TS 24.333 [71].
– ProSe ReportDataTransmitted
Contents:
As described in TS 24.333 [71], indicates whether or not the UE shall report the amount of data transmitted during the collection period in the usage information, and whether with location information. The default value 1 applies if this TLV is not provisioned
Coding:
As defined for the ProSe ReportDataTransmitted leaf in TS 24.333 [71].
– ProSe ReportDataReceived
Contents:
As described in TS 24.333 [71], indicates whether or not the UE shall report the amount of data received during the collection period in the usage information, and whether with location information. The default value 1 applies if this TLV is not provisioned
Coding:
As defined for the ProSe ReportDataReceived leaf in TS 24.333 [71].
– ProSe ReportTimeStampsOutOfCoverage
Contents:
As described in TS 24.333 [71], indicates whether or not the UE shall report the time stamps when it went in and out of E-UTRAN coverage during the collection period in the usage information. The default value 0 applies if this TLV is not provisioned
Coding:
As defined for the ProSe ReportTimeStampsOutOfCoverage leaf in TS 24.333 [71].
– ProSe ReportLocationInCoverage
Contents:
As described in TS 24.333 [71], indicates whether or not the UE shall report the list of locations of the UE when in E-UTRAN coverage during the collection period in the usage information.
Coding:
As defined for the ProSe ReportLocationInCoverage leaf in TS 24.333 [71].
– ProSe ReportRadioParameters
Contents:
As described in TS 24.333 [71], indicates whether or not the UE shall report the radio parameters used for ProSe direct communication (i.e. indicator of which radio resources used and radio frequency used) during the reporting period in the usage information.
Coding:
As defined for the ProSe ReportRadioParameters leaf in TS 24.333 [71].
4.4.8.12 EFPROSE_GM_DISCOVERY (ProSe Group Member Discovery Parameters)
If service n°10 is "available" in the ProSe Service Table, this file shall be present.
This EF contains the ProSe discovery parameters for public safety, as described in TS 24.334 [70]. This file shall be used only if the ME is authorized as per content of EFAD or received service authorization from the ProSe Function.
|
Identifier: ‘4F12’ |
Structure: linear fixed |
Optional |
||||
|
SFI: ’12’ |
||||||
|
Record size: Z bytes |
Update activity: low |
|||||
|
Access Conditions: READ PIN UPDATE ADM DEACTIVATE ADM ACTIVATE ADM |
||||||
|
Bytes |
Description |
M/O |
Length |
|||
|
1 to Y |
Group member discovery parameters TLV data object |
O |
Y bytes |
|||
Group member discovery parameters information:
|
Description |
Value |
M/O |
Length (bytes) |
|
Group member discovery parameters Tag |
‘A0’ |
M |
1 |
|
Length |
X |
M |
Note |
|
User Info ID tag |
’80’ |
M |
1 |
|
Length |
6 |
M |
1 |
|
User Info ID |
— |
M |
6 |
|
Discovery Group ID tag |
’81’ |
M |
1 |
|
Length |
3 |
M |
1 |
|
Discovery Group ID |
— |
M |
3 |
|
Application Layer Group ID tag |
’82’ |
M |
1 |
|
Length |
Y |
M |
Note |
|
Application Layer Group ID |
— |
M |
Y |
|
NOTE: The length is coded according to ISO/IEC 8825-1 [35] |
|||
Each record shall contain at most one Group member discovery parameters information.
– User Info ID tag ’80’
Contents:
Indicates the user information which is sent by the announcing or discoverer or discoveree UE over the air during Group Member Discovery procedures.
Coding:
As defined in TS 24.334 [70].
– Discovery Group ID tag ’81’
Contents:
Indicates the group ID of the discovery group that the UE belongs to when group member discovery is performed.
Coding:
As defined in TS 24.334 [70].
– Application Layer Group ID tag ’82’
Contents:
Indicates the Application Layer Group ID identifying an application layer group that the UE belongs to.
Coding:
As per TS 23.303 [73]
Unused bytes shall be set to ‘FF’.
4.4.8.13 EFPROSE_RELAY (ProSe Relay Parameters)
If service n°11 is "available" in the ProSe Service Table, this file shall be present.
This EF contains the authorized PLMNs for ProSe UE-to-network relay for public safety, as described in TS 24.334 [70]. This file shall be used only if the ME is authorized as per content of EFAD or received service authorization from the ProSe Function.
Each record shall be associated with a different PLMN.
|
Identifier: ‘4F13’ |
Structure: linear fixed |
Optional |
||||
|
SFI: ’13’ |
||||||
|
Record size: Z bytes |
Update activity: low |
|||||
|
Access Conditions: READ PIN UPDATE ADM DEACTIVATE ADM ACTIVATE ADM |
||||||
|
Bytes |
Description |
M/O |
Length |
|||
|
1 to Z |
ProSe Relay parameters TLV data object |
O |
Z bytes |
|||
ProSe Relay parameters information:
|
Description |
Value |
M/O |
Length (bytes) |
|
ProSe Relay parameters Tag |
‘A0’ |
M |
1 |
|
Length |
X |
M |
Note |
|
PLMN tag |
’80’ |
M |
1 |
|
Length |
3 |
M |
1 |
|
PLMN |
— |
M |
3 |
|
Relay type tag |
’81’ |
M |
1 |
|
Length |
1 |
M |
1 |
|
Relay type |
— |
M |
1 |
|
NOTE: The length is coded according to ISO/IEC 8825-1 [35] |
|||
– PLMN tag ’80’
Contents:
Contains the PLMNs in which the UE is authorised to act as a ProSe UE-to-network relay and/or use a ProSe UE-to-network relay.
Coding:
According to TS 24.008 [9].
– Relay type tag ’81’
Contents:
Indicates if the UE is authorized to act as a ProSe UE-to-network relay and/or use a ProSe UE-to-network relay.
Coding:
|
b8 |
b7 |
b6 |
b5 |
b4 |
b3 |
b2 |
b1 |
||||||||||||
|
b1=0 indicates that the UE is not authorised to act as a ProSe UE-to-network relay. b1=1 indicates that the UE is authorised to act as a ProSe UE-to-network relay. |
|||||||||||||||||||
|
b2=0 indicates that the UE is not authorised to use a ProSe UE-to-network relay. b2=1 indicates that the UE is authorised to use a ProSe UE-to-network relay. |
|||||||||||||||||||
|
RFU (see TS 31.101 [11]) |
|||||||||||||||||||
Unused bytes shall be set to ‘FF’.
4.4.8.14 EFPROSE_RELAY_DISCOVERY (ProSe Relay Discovery Parameters)
If service n°11 is "available" in the ProSe Service Table, this file shall be present.
This EF contains the ProSe direct discovery parameters when it is used for ProSe UE-to-network relay discovery for public safety, as described in TS 24.334 [70]. This file shall be used only if the ME is authorized as per content of EFAD or received service authorization from the ProSe Function.
|
Identifier: ‘4F14’ |
Structure: transparent |
Optional |
||||
|
SFI: ’14’ |
||||||
|
File size: Z bytes (Z > 5 bytes) |
Update activity: low |
|||||
|
Access Conditions: READ PIN UPDATE ADM DEACTIVATE ADM ACTIVATE ADM |
||||||
|
Bytes |
Description |
M/O |
Length |
|||
|
1 to 6 |
User Info ID |
M |
6 bytes |
|||
|
— |
Remote UE parameters TLV data object |
O |
X bytes |
|||
|
— |
Relay parameters TLV data object |
O |
Y bytes |
|||
User Info ID
Contents:
Indicates the user information which is sent by the announcing or discoverer or discoveree UE over the air during Group Member Discovery procedures.
Coding:
As defined in TS 24.334 [70].
Remote UE parameters information:
The EF can contain multiple Remote UE parameters data objects.
|
Description |
Value |
M/O |
Length (bytes) |
|
Remote UE parameters Tag |
‘A0’ |
M |
1 |
|
Length |
X |
M |
Note |
|
Relay Service Code tag |
’80’ |
M |
1 |
|
Length |
3 |
M |
1 |
|
Relay Service Code |
— |
M |
3 |
|
User Info ID of Relay tag |
’81’ |
O |
1 |
|
Length |
6 |
C |
1 |
|
User Info ID of Relay |
— |
C |
6 |
|
IP Versions tag |
’82’ |
M |
1 |
|
Length |
1 |
M |
1 |
|
IP Versions |
— |
M |
1 |
|
Security content tag |
’83’ |
M |
1 |
|
Length |
Y |
M |
Note |
|
Security content |
— |
M |
Y |
|
NOTE: The length is coded according to ISO/IEC 8825-1 [35] |
|||
– Relay Service Code tag ’80’
Contents:
Indicates the connectivity service that the ProSe UE-to-network relay provides to public safety applications.
Coding:
As defined in TS 24.334 [70].
– User Info ID of Relay tag ’81’
Contents:
Indicates the user information of the ProSe UE-to-network relay that the remote UE seeks to discover during ProSe UE-to-network relay discovery procedures.
Coding:
As defined in TS 24.334 [70].
– IP Versions tag ’82’
Contents:
Indicates the IP version(s) that the remote UE can use for the relay traffic associated with the Relay Service Code.
Coding:
A value of ’01’ indicates IPv4, a value of ’02’ indicates IPv6, a value of ’03’ indicates IPv4v6. All other values are reserved.
– Security Content tag ’83’
Contents:
Parameters related to the relay discovery.
Coding:
|
Byte(s) |
Description |
M/O |
Length |
|
1 to 32 |
PSDK as defined in TS 33.303 [72] |
M |
32 bytes |
|
33 |
PSDK Id as defined in TS 33.303 [72]. |
M |
1 byte |
|
34 |
Bitmask of keys: – b1=1 indicates that DUSK is to be used – b2=1 indicates that DUCK is to be used – b3=1 indicates that DUIK is to be used – all other bits are RFU |
M |
1 byte |
|
35 to 57 |
DUCK encryption bitmask, as defined in TS 24.334 [70] (applicable when DUCK is used) |
M |
23 bytes |
|
58 to Y |
RFU |
O |
(Y-57) bytes |
Relay parameters information:
The EF can contain multiple Relay parameters data objects.
|
Description |
Value |
M/O |
Length (bytes) |
|
Relay parameters Tag |
‘A1’ |
M |
1 |
|
Length |
X |
M |
Note |
|
Relay Service Code tag |
’80’ |
M |
1 |
|
Length |
3 |
M |
1 |
|
Relay Service Code |
— |
M |
3 |
|
PDN type tag |
’81’ |
O |
1 |
|
Length |
1 |
C |
1 |
|
PDN type |
— |
C |
1 |
|
APN tag |
’82’ |
O |
1 |
|
Length |
3 |
C |
1 |
|
APN |
— |
C |
3 |
|
ProSe Relay UE ID tag |
’83’ |
M |
1 |
|
Length |
3 |
M |
1 |
|
ProSe Relay UE ID |
— |
M |
3 |
|
Security content tag |
’84’ |
M |
1 |
|
Length |
Y |
M |
Note |
|
Security content |
— |
M |
Y |
|
NOTE: The length is coded according to ISO/IEC 8825-1 [35] |
|||
– Relay Service Code tag ’80’
Contents:
Indicates the connectivity service that the ProSe UE-to-network relay provides to public safety applications.
Coding:
As defined in TS 24.334 [70].
– PDN type tag ’81’
Contents:
Indicates the IP version of the PDN connection to be used for the relayed traffic associated with a Relay Service Code.
Coding:
A value of ’01’ indicates IPv4, a value of ’02’ indicates IPv6. All other values are reserved.
– APN tag ’82’
Contents:
Indicates the PDN connection that the ProSe UE-to-network relay uses for the relayed traffic associated with a Relay Service Code. If this TLV is missing, then the default APN is used for the PDN connectivity.
Coding:
A network access point name
– ProSe Relay UE ID tag ’83’
Contents:
Indicates the link layer identifier used for direct communication associated with a Relay Service Code.
Coding:
As defined in TS 24.334 [70].
– Security Content tag ’84’
Contents:
Parameters related to the relay discovery.
Coding:
|
Byte(s) |
Description |
M/O |
Length |
|
1 to 32 |
PSDK as defined in TS 33.303 [72] |
M |
32 bytes |
|
33 |
PSDK Id as defined in TS 33.303 [72]. |
M |
1 byte |
|
34 |
Bitmask of keys: – b1=1 indicates that DUSK is to be used – b2=1 indicates that DUCK is to be used – b3=1 indicates that DUIK is to be used – all other bits are RFU |
M |
1 byte |
|
35 to 57 |
DUCK encryption bitmask, as defined in TS 24.334 [70] (applicable when DUCK is used) |
M |
23 bytes |
|
58 to Y |
RFU |
O |
(Y-57) bytes |
Unused bytes shall be set to ‘FF’.