4.7F Default ProSe messages

36.5083GPPCommon test environments for User Equipment (UE) conformance testingEvolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet Core (EPC)Release 17TS

4.7F.1 ProSe discovery messages

– DISCOVERY_REQUEST

This message is sent by the UE to the SS.

Table 4.7F.1-1: DISCOVERY_REQUEST

Derivation path: 24.334 [57], clause 11.2.4.2.

Information Element

Value/remark

Comment

Condition

discovery-request[1] {

transaction-ID

Any allowed value

command

2

monitor

1

announce

UE-identity

IMSI

ProSe-Application-ID

px_ProSeMonApplicationIdentity1

application-identity

Any allowed value

}

discovery-request[N]{}

Any allowed value if present

A UE can include one or multiple transactions in one DISCOVERY_REQUEST message for one or more ProSe Application IDs

– DISCOVERY_RESPONSE

This message is sent by the SS to the UE.

Table 4.7F.1-2: DISCOVERY_RESPONSE

Derivation path: 24.334 [57], clause 11.2.4.3.

Information Element

Value/remark

Comment

Condition

Current-time

Current UTC time

Max-Offset

32

32 seconds

response-announce[1] {

transaction-ID

Same as that included by UE in the relevant DISCOVERY_REQUEST message and the relevant discovery-request

ProSe Application Code[1] {

184 bits

See TS 23.003 [2], section 24.3.

PLMN ID {

24 bits

The PLMN ID of the ProSe Function that assigned the ProSe Application Code, i.e. Mobile Country Code (MCC) and Mobile Network Code (MNC).

Scope

’10’

"country-specific scope", i.e. only MNC is wild carded

Spare

‘0’

E

‘1’

For Rel-12 MCC and the MNC of the ProSe Function that has assigned the ProSe Application Code are included in the PLMN ID in ProSe Application Code

MCC

The MCC part of the The PLMN ID of the ProSe Function that assigned the ProSe Application Code (the relevant PLMN will be set in the TC)

fixed length of 10 bits and shall be coded as the binary representation of their decimal value

MNC

The MNC part of the The PLMN ID of the ProSe Function that assigned the ProSe Application Code (the relevant PLMN will be set in the TC)

fixed length of 10 bits and shall be coded as the binary representation of their decimal value

}

TemporaryID

1111111100000000

0000000000000000

0000000000000000

0000000000000000

0000000000000000

0000000000000000

0000000000000000

0000000000000000

0000000000000000

0000000011111111

160 bits – see setting of bit ‘E’ above.

A temporary identity that corresponds to the ProSe Application ID Name.

}

validity-timer-T4000

5

Indicating the time during which the Application Code is valid

Integer in the 1-525600 range representing the timer value in unit of minutes

discovery-key

1000100000001000

0100010000001000

0010001000001000

0001000100001000

0000100010001000

0000010001001000

0000001000101000

0000000100011000

128-bit

As defined in TS 33.303 [60] and TS 33.220 [61]

}

response-monitor[1] {

transaction-ID

Same as that included by UE in the relevant DISCOVERY_REQUEST message and the relevant discovery-request

discovery-filter[1] {

ProSe Application Code {

184 bits

See TS 23.003 [2], section 24.3.

PLMN ID {

24 bits

The PLMN ID of the ProSe Function that assigned the ProSe Application Code, i.e. Mobile Country Code (MCC) and Mobile Network Code (MNC).

Scope

’10’

"country-specific scope", i.e. only MNC is wild carded

Spare

‘0’

E

‘1’

For Rel-12 MCC and the MNC of the ProSe Function that has assigned the ProSe Application Code are included in the PLMN ID in ProSe Application Code

MCC

The MCC part of the The PLMN ID of the ProSe Function that assigned the ProSe Application Code (the relevant PLMN will be set in the TC)

fixed length of 10 bits and shall be coded as the binary representation of their decimal value

MNC

The MNC part of the The PLMN ID of the ProSe Function that assigned the ProSe Application Code (the relevant PLMN will be set in the TC)

fixed length of 10 bits and shall be coded as the binary representation of their decimal value

}

TemporaryID

1111111100000000

0000000000000000

0000000000000000

0000000000000000

0000000000000000

0000000000000000

0000000000000000

0000000000000000

0000000000000000

0000000011111111

160 bits – see setting of bit ‘E’ above.

A temporary identity that corresponds to the ProSe Application ID Name.

}

ProSe Application Mask[1]

0000111111111100

00000000

1111111111111111

0000000000000000

0000000000000000

0000000000000000

0000000000000000

0000000000000000

0000000000000000

0000000000000000

0000000000000000

0000000000000000

184 bits – The length of the ProSe Application Mask is the same as the length of ProSe Application Code

Full matching for the MCC part is required, as well as for the first 16 bits of the Temporary ID in order a received ProSe Application Code to result in a match

ProSe Application Mask[2]

0000111111111100

00000000

0000000000000000

0000000000000000

0000000000000000

0000000000000000

0000000000000000

0000000000000000

0000000000000000

0000000000000000

0000000000000000

1111111111111111

184 bits – The length of the ProSe Application Mask is as same as the length of ProSe Application Code

Full matching for the MCC part is required, as well as for the last 16 bits of the Temporary ID

TTLTimer T4002

5

Indicating the time during which the filter is valid

Integer in the 1-525600 range representing the timer value in unit of minutes

}

}

response-reject

Not Present

– MATCH_REPORT

This message is sent by the UE to the SS.

Table 4.7F.1-3: MATCH_REPORT

Derivation path: 24.334 [57], clause 11.2.4.4.

Information Element

Value/remark

Comment

Condition

transaction-ID

a new transaction ID

ProSe-Application-Code

A code received in a PC5_DISCOVERY message for which there was a match event and for which the UE does not have an associated ProSe Application ID

The expected value will be set in the relevant TC.

UE-identity

IMSI

Monitored-PLMN-id

The monitored in the TC PLMN

The expected value will be set in the relevant TC.

VPLMN-id

Not included

MIC

MIC of the PC5_DISCOVERY message that contained the ProSe Application Code for which there was a match event

UTC-based Counter

– the 28 most significant bits of the UTC-based counter shall be set to the 28 most significant bits of the UTC time provided by the lower layers for the PC5_DISCOVERY message that contained the ProSe Application Code for which there was a match event encoded as specified in TS 24.334 [57], subclause 12.2.2.18; and

– the 4 least significant bits of the UTC-based counter shall be set to the 4 least significant bits of the UTC-based counter contained in the PC5_DISCOVERY message that contained the ProSe Application Code for which there was a match event, as specified in 3GPP TS 33.303 [60]

The UTC is expressed in unit of seconds and coded in binary format as the 32 least significant bits of the Coordinated Universal Time as defined in 3GPP TS 36.331 [17]

metadata-flag

Any allowed value

– MATCH_REPORT_ACK

This message is sent by the SS to the UE.

Table 4.7F.1-4: MATCH_REPORT_ACK

Derivation path: 24.334 [57], clause 11.2.4.5.

Information Element

Value/remark

Comment

Condition

Current-Time

Current UTC time

match-ack {

transaction-ID

the transaction ID received in the MATCH_REPORT

ProSe-Application-ID

a ProSe Application ID which the UE does not have

validity-timer-T4004

4

4 min

metadata

Not Present

match-report-refresh-timer-T4006

1

1 min

}

– PC5_DISCOVERY

This message is sent by the UE or by the SS-UE.

Table 4.7F.1-5: PC5_DISCOVERY for open ProSe direct discovery

Derivation path: 24.334 [57], Table 11.2.5.1.1.

Information Element

Value/remark

Comment

Condition

ProSe Application Code {

PLMN ID

Same as the PLMN ID provided in the DISCOVERY_RESPONSE message sent during the latest Monitor request procedure

TemporaryID

Same as the TemporaryID provided in the DISCOVERY_RESPONSE message sent during the latest Monitor request procedure

}

MIC

Computed by UE based on Message Type, discovery-key and ProSe Application Code included by SS in DISCOVERY_RESPONSE sent during the latest Monitor request procedure, and UTC-based counter associated with the discovery slot. See TS 33.303 [60], A.2.

The 32 least significant bits of the output of the KDF, TS 33.220 [61], Annex B.

UTC-based Counter LSB

four least significant bits of the UTC-based counter associated with the discovery slot

The UTC is expressed in unit of seconds and coded in binary format as the 32 least significant bits of the Coordinated Universal Time as defined in 3GPP TS 36.331 [17]

Table 4.7F.1-5A: PC5_DISCOVERY for Group Member Discovery Announcement

Derivation path: 24.334 [57], Table 11.2.5.1.7.

Information Element

Value/remark

Comment

Condition

Message Type {

Discovery type

’01’B

"Restricted discovery"

Content type

‘0110’

"Group Member Discovery Announcement or Group Member Discovery Response"

Discovery model

’01’

"Model A"

}

Discovery Group ID

The configured Discovery Group ID parameter identifying the discovery group to be announced

24-bit long bit string

User Info ID

The configured User Info ID for the group member discovery parameter

Announcer Info

48-bit long bit string

ProSe UE ID

The configured Layer 2 ID used for unicast communication

24-bit long bit string

Spare

The length of this parameter is variable and is indicated in a message where this parameter is included

MIC

Computed in accordance with TS 33.303 [60], A.2.

UTC-based Counter LSB

Set to the eight least significant bits of the UTC-based counter

The UTC is expressed in unit of seconds and coded in binary format as the 32 least significant bits of the Coordinated Universal Time as defined in 3GPP TS 36.331 [17]

Table 4.7F.1-5B: PC5_DISCOVERY for Group Member Discovery Solicitation

Derivation path: 24.334 [57], Table 11.2.5.1.8.

Information Element

Value/remark

Comment

Condition

Message Type {

Discovery type

’01’B

"Restricted discovery"

Content type

‘0111’

"Group Member Discovery Solicitation"

Discovery model

’10’

"Model B"

}

Discovery Group ID

The configured Discovery Group ID parameter identifying the discovery group to be solicited

24-bit long bit string

User Info ID

The configured User Info ID for the group member discovery parameter

Discoverer Info

48-bit long bit string

GMDS Composition {

TUII

Any value

TGII

Any value

}

Target User Info

IF TUII=’1′ THEN

the User Info ID of the targeted discoveree user – 48-bit long bit string

ELSE Not present

Target Group Info

IF TGII=’1′ THEN

ProSe Layer 2 Group ID – 24-bit long bit string

ELSE Not present

Spare

The length of this parameter is variable and is indicated in a message where this parameter is included

MIC

Computed in accordance with TS 33.303 [60], A.2.

UTC-based Counter LSB

Set to the eight least significant bits of the UTC-based counter

The UTC is expressed in unit of seconds and coded in binary format as the 32 least significant bits of the Coordinated Universal Time as defined in 3GPP TS 36.331 [17]

Table 4.7F.1-5C: PC5_DISCOVERY for Group Member Discovery Response

Derivation path: 24.334 [57], Table 11.2.5.1.9.

Information Element

Value/remark

Comment

Condition

Message Type {

Discovery type

’01’B

"Restricted discovery"

Content type

‘0110’

"Group Member Discovery Announcement or Group Member Discovery Response"

Discovery model

’10’

"Model B"

}

Discovery Group ID

The received Discovery Group ID parameter of the PC5_DISCOVERY message for Group Member Discovery Solicitation

24-bit long bit string

User Info ID

The configured User Info ID for the group member discovery parameter

Discoveree Info

48-bit long bit string

ProSe UE ID

The configured Layer 2 ID used for unicast communication

24-bit long bit string

Spare

The length of this parameter is variable and is indicated in a message where this parameter is included

MIC

Computed in accordance with TS 33.303 [60], A.2.

UTC-based Counter LSB

Set to the eight least significant bits of the UTC-based counter

The UTC is expressed in unit of seconds and coded in binary format as the 32 least significant bits of the Coordinated Universal Time as defined in 3GPP TS 36.331 [17]

4.7F.2 Messages transmitted over the PC3ch interface

– USAGE_INFORMATION_REPORT_LIST

This message is sent by the UE to the SS.

Table 4.7F.2-1: USAGE_INFORMATION_REPORT_LIST

Derivation path: 24.334 [57], clause 11.3.4.2.

Information Element

Value/remark

Comment

Condition

transaction-ID

Any allowed value

UE-identity

IMSI

usage-information-report[1] {

1 Report

sequence-number

1

First report after power up

coverage {

in-coverage

FALSE

The UE was out of E-UTRAN coverage

timestamp

Not Present or Any allowed Value

location[1]

Not Present

UE was out of coverage i.e. the UE was not camping on nor the UE was in the EMM-CONNECTED mode on any E-UTRA cell

}

group[1] {

The UE is configured to report the group parameters, see EFPROSE_UIRC

prose-layer2-group-ID

As preconfigured in EFPROSE_POLICY

prose-group-IP-multicast-address

As preconfigured in EFPROSE_POLICY

first-transmission-timestamp

Any allowed Value

first-reception-timestamp

Any allowed Value

UE-source-IP-address

Any allowed Value

prose-UE-id

As preconfigured in EFPROSE_POLICY

transmitter {

source-IP-address

Any allowed Value

prose-UE-id

Any allowed value

}

transmission {

in-coverage

FALSE

ECGI

Not Present

amount

Any allowed Value

timestamp

Any allowed Value

radio-resources-ind

2

the configured radio resources were used

radio-frequency

carrierFreq-r12, Table 6.8.1.1-1

the configured radio frequency

}

reception {

in-coverage

FALSE

ECGI

Not Present

amount

Any allowed Value

timestamp

Any allowed Value

radio-resources-ind

2

the configured radio resources

radio-frequency

carrierFreq-r12, Table 6.8.1.1-1

the configured radio frequency

}

..}

radio-parameter-set {

2 entries in any order refering to SL-Preconfiguration-r12, Table 6.8.1.1-1 SLCONF1 and SLCONF2

{

Entry 1

params

the radio parameters used for ProSe direct communication, see SL-Preconfiguration-r12, Table 6.8.1.1-1 cond SLCONF1

timestamp

Any allowed Value

}

{

Entry 2

params

the radio parameters used for ProSe direct communication, see SL-Preconfiguration-r12, Table 6.8.1.1-1 cond SLCONF2

timestamp

Any allowed Value

}

}

app-specific-info

Any allowed Value

– USAGE_INFORMATION_REPORT_LIST_RESPONSE

This message is sent by the SS to the UE.

Table 4.7F.2-2: USAGE_INFORMATION_REPORT_LIST_RESPONSE

Derivation path: 24.334 [57], clause 11.3.4.3.

Information Element

Value/remark

Comment

Condition

response-accept {

transaction-ID

The value of the transaction ID of the related USAGE_INFORMATION_REPORT_LIST message

}

response-reject {

Not present

transaction-ID

cause-value

}

4.7F.3 ProSe Direct Communication Messages

– DIRECT_COMMUNICATION_ACCEPT

This message can be sent by the UE or the SS.

Table 4.7F.3-0A: DIRECT_COMMUNICATION_ACCEPT

Derivation path: 24.334 [57], clause 11.4.3.1.1.

Information Element

Value/remark

Comment

Condition

Sequence Number

0

incremented for each outgoing new PC5 Signalling message

IP Address Config

Any allowed value

Link Local IPv6 Address

Present if the IP Address Config IE is set to ‘address allocation not support’

Not Present otherwise

128-bit IPv6 address

– DIRECT_COMMUNICATION_KEEPALIVE

This message can be sent by the UE or the SS.

Table 4.7F.3-0B: DIRECT_COMMUNICATION_KEEPALIVE

Derivation path: 24.334 [57], clause 11.4.5.1.1.

Information Element

Value/remark

Comment

Condition

Sequence Number

The Sequence number used in the previously sent PC5 Signalling message + 1

Keepalive Counter

0 if this is the first keepalive message being sent

otherwise

– the value sent in the preceeding acknowledged DIRECT_COMMUNICATION_KEEPALIVE message + 1,or,

– the same value if this is a retransmission

Maximum Inactivity Period

Any allowed value or Not present

– DIRECT_COMMUNICATION_KEEPALIVE_ACK

This message can be sent by the UE or the SS.

Table 4.7F.3-0C: DIRECT_COMMUNICATION_KEEPALIVE_ACK

Derivation path: 24.334 [57], clause 11.4.6.1.1.

Information Element

Value/remark

Comment

Condition

Sequence Number

The Sequence number used in the previously sent PC5 Signalling message + 1

Keepalive Counter

the same value as the one received in the preceeding DIRECT_COMMUNICATION_KEEPALIVE message

– DIRECT_COMMUNICATION_RELEASE

This message can be sent by the UE or the SS.

Table 4.7F.3-0D: DIRECT_COMMUNICATION_RELEASE

Derivation path: 24.334 [57], clause 11.4.7.1.1.

Information Element

Value/remark

Comment

Condition

Sequence Number

The Sequence number used in the previously sent PC5 Signalling message + 1

Release Reason

Any allowed value

– DIRECT_COMMUNICATION_RELEASE_ACCEPT

This message can be sent by the UE or the SS.

Table 4.7F.3-0E: DIRECT_COMMUNICATION_RELEASE_ACCEPT

Derivation path: 24.334 [57], clause 11.4.8.1.1.

Information Element

Value/remark

Comment

Condition

Sequence Number

The Sequence number used in the previously sent PC5 Signalling message + 1

– DIRECT_COMMUNICATION_REQUEST

This message can be sent by the UE or the SS.

Table 4.7F.3-0F: DIRECT_COMMUNICATION_REQUEST

Derivation path: 24.334 [57], clause 11.4.2.1.1.

Information Element

Value/remark

Comment

Condition

Sequence Number

0

incremented for each outgoing new PC5 Signalling message

User Info {

Type of User Info

Any allowed value

Odd/even indication

Any allowed value

Reflecting the number of identity digits

Identity digits

Any allowed value

}

IP Address Config

Any allowed value

Maximum Inactivity Period

Any allowed value

Nonce_1

Any allowed value

128-bit nonce value generated by the UE which initiated the procedure

UE Security Capabilities

Any allowed value

MSB of KD-sess ID

Any allowed value

the 8 most significant bits of the KD-sess ID

KD ID

Any allowed value

Relay Service Code

Not present

Signature

Any allowed value

ECCSI signature

content structure is specified in 3GPP TS 33.303 [60]

IETF RFC 6507

Link Local IPv6 Address

Present if the IP Address Config IE is set to ‘address allocation not support’

Not Present otherwise

128-bit IPv6 address

– DIRECT_SECURITY_MODE_COMMAND

This message can be sent by the UE or the SS.

Table 4.7F.3-0G: DIRECT_SECURITY_MODE_COMMAND

Derivation path: 24.334 [57], clause 11.4.12.1.1.

Information Element

Value/remark

Comment

Condition

Sequence Number

The Sequence number used in the previously sent PC5 Signalling message + 1

UE Security Capabilities

Any allowed value

Nonce 2

Any allowed value

128-bit nonce value generated by the UE which initiated the procedure

Chosen Algorithms

Any allowed value

LSB of KD-sess ID

Any allowed value

the 8 least significant bits of the KD-sess ID.

MSB of KD ID

Any allowed value or Not included

the 8 most significant bits of the KD-sess ID

KD Freshness

Any allowed value or Not included

128-bit nonce value generated by initiating PKMF to ensure that any calculated KD is fresh

GPI

Any allowed value or Not included

the GBA Push Information as defined in 3GPP TS 33.223

User Info {

Type of User Info

Any allowed value

Odd/even indication

Any allowed value

Reflecting the number of identity digits

Identity digits

Any allowed value

}

Signature

Any allowed value

ECCSI signature

content structure is specified in 3GPP TS 33.303 [60]

IETF RFC 6507

Encrypted Payload

Any allowed value

encrypted data encapsulating the shared secret key to be used for the established link

The exact content structure is specified in 3GPP TS 33.303 [60]

– DIRECT_SECURITY_MODE_COMPLETE

This message can be sent by the UE or the SS.

Table 4.7F.3-0H: DIRECT_SECURITY_MODE_COMPLETE

Derivation path: 24.334 [57], clause 11.4.13.1.

Information Element

Value/remark

Comment

Condition

Sequence Number

The Sequence number used in the previously sent PC5 Signalling message + 1

LSB of KD ID

Any allowed value or Not present

Optional

16 least significant bits of KD ID

– KEY_REQUEST

This message is sent by the UE to the SS.

Table 4.7F.3-1: KEY_REQUEST

Derivation path: 33.303 [60], clause E.4.2.

Information Element

Value/remark

Comment

Condition

transaction-ID

Any allowed value

AlgorithmAvailable

Any allowed value

Encryption algorithm the UE supports for one-to-many communications

GroupKeyReq {

One entry

GroupId

Any allowed value

Group that the UE is requesting keys for (Range 0-167777215)

PGKId

0

UE does not have any PGKs for this group

anyExt

Not Present

}

PRUKId

Not Present

KDRequest

Not Present

Key Exchange Payload

Not Present

GroupKeyStop

Not Present

PSDiscoverySecurityCapabilities

Not Present

RelayDiscoveryKeyRequest

Not Present

RelayDiscoveryKeyStop

Not Present

GroupMemberDiscoveryKeyRequest

Not Present

GroupMemberDiscoveryKeyStop

Not Present

anyExt

Not Present

– KEY_RESPONSE

This message is sent by the SS to the UE.

Table 4.7F.3-2: KEY_RESPONSE

Derivation path: 33.303 [60], clause E.4.3.

Information Element

Value/remark

Comment

Condition

transaction-ID

Same as that received in KEY_REQUEST

GroupNotSupported

Not Present

GroupResponse {

One entry

GroupId

Same as that received in KEY_REQUEST

GroupMemberID

1

AlgorithmInfo

‘001’B

EPS encryption algorithm 128-EEA1

}

Key-info {

One entry

PMK-ID

‘0000000000000001’H

PMK

‘00000000000000000000000000000001’H

}

PRUKinfo

Not Present

PRUKError

Not Present

KDResponse

Not Present

KDError

Not Present

RelayNotSupported

Not Present

RelayResponse

Not Present

GroupMemberDiscoveryNotSupported

Not Present

GroupMemberDiscoveryResponse

Not Present

CurrentTime

Not Present

MaxOffset

Not Present

anyExt

Not Present

– MIKEY Key Delivery Message

This message is sent by the SS to the UE.

Table 4.7F.3-3: MIKEY Key Delivery Message

Derivation path: 33.303 [60], clause D.3.

Information Element

Value/remark

Comment

Condition

MIKEY Common Header {

version

‘00000001’B

data type

‘00000000’B

Pre-shared key message

Next payload

‘00000101’B

Next payload is timestamp

V

‘1’B

Response expected

PRF func

‘0000000’B

CSB ID

Random number

Any 32 bit random number

#CS

‘00000000’B

CS ID map type

‘00000001’B

Empty map

CS ID map Info

FFS

}

Timestamp Payload {

Next payload

‘00001011’B

Next payload is RAND

TS Type

‘00000010’B

Value 2 corresponds to Counter

TS Value

‘00000000000000000000000000000001’B

Replay counter.

}

RAND Payload {

Next payload

‘00000110’B

Next payload is ID

RAND len

‘00010000’B

16 Bytes RAND

RAND

128-bit random number

}

IDi payload {

Next payload

‘00000110’B

Next payload is ID

ID Type

0

ID len

Length of ID Data

ID data

Group Identity || PGK ID @ FQDN of the ProSe Key Management Function

}

IDr payload {

Next payload

‘00000001’B

Next payload is KEMAC

ID Type

0

ID len

Length of ID Data

ID data

PMK identity of the PMK used to protect the MIKEY message @ the FQDN of the ProSe Key Management Function

}

KEMAC Payload {

Next payload

‘00000000’B

This is the last payload

Encr alg

‘00000001’B

AES-CM-128

Encr data len

Length of Encr Data

Encr Data {

Key Data payload is encrypted and carried

Next payload

‘00000000’B

This is the last payload

Type

‘0000’B

TEK

KV

‘0010’B

The key has a start and expiration time

Key data len

‘0000000010000000’B

128 bits

Key data

‘0000 0000 0000 0000 0000 0000 0000 0001’[OCT]

PGK

KV data {

VF length

FFS

Valid from

FFS

VT length

FFS

Valid to

FFS

}

}

Mac alg

‘00000001’B

HMAC-SHA-1-160

MAC

Message Authentication Code of the message

}

– MIKEY Verification Message

This message is sent by the UE to the SS.

Table 4.7F.3-4: MIKEY Verification Message

Derivation path: 33.303 [60], clause D.3.

Information Element

Value/remark

Comment

Condition

MIKEY Common Header {

version

‘00000001’B

data type

‘00000000’B

Pre-shared key message

Next payload

‘00000101’B

Next payload is timestamp

V

‘0’B

PRF func

‘0000001’B

CSB ID

Same as sent by ProSe Function in the MIKEY message carrying PGK

#CS

‘00000000’B

CS ID map type

‘00000001’B

Empty map

CS ID map Info

FFS

}

Timestamp Payload {

Next payload

‘00001011’B

Next payload is RAND

TS Type

‘00000010’B

Value 2 corresponds to Counter

TS Value

‘00000000000000000000000000000001’B

Replay counter.

}

IDr payload {

Next payload

‘00001001’B

Next payload is Verification Payload

ID Type

0

ID len

Length of ID data

ID data

PMK identity of the PMK used to protect the MIKEY message @ the FQDN of the ProSe Key Management Function

}

Verification Message Payload {

Next payload

‘00000000’B

This is the last payload

Auth alg

‘00000001’B

AES-CM-128

Verification data

Message Authentication Code

}