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

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

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 EF_{PROSE_UIRC}
prose-layer2-group-ID	As preconfigured in EF_{PROSE_POLICY}
prose-group-IP-multicast-address	As preconfigured in EF_{PROSE_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 EF_{PROSE_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
}