10 Message functional definitions and contents

24.5543GPPProximity-services (ProSe) in 5G System (5GS) protocol aspectsRelease 17Stage 3TS

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

10.1 Overview

This clause contains the definition and contents of the messages used in the procedures described in the present document.

10.2 5G ProSe direct discovery messages

10.2.1 Message definition

This message is sent by the UE over the PC5 interface for open 5G ProSe direct discovery and restricted 5G ProSe direct discovery. See table 10.2.1.1, table 10.2.1.2, table 10.2.1.3, table 10.2.1.4, table 10.2.1.5, table 10.2.1.6, table 10.2.1.7, table 10.2.1.8, table 10.2.1.9, table 10.2.1.10 and table 10.2.1.11.

Message type: PROSE PC5 DISCOVERY

Significance: dual

Direction: UE to peer UE

Table 10.2.1.1: PROSE PC5 DISCOVERY message content for open 5G ProSe direct discovery announcement

IEI	Information Element	Type/Reference	Presence	Format	Length
	ProSe direct discovery PC5 message type (NOTE)	ProSe direct discovery PC5 message type 11.2.1	M	V	1
	UTC-based counter LSB	UTC-based counter LSB 11.2.14	M	V	1
	MIC	MIC 11.2.4	M	V	4
	ProSe application code	ProSe application code 11.2.2	M	V	23
7A	Metadata	Metadata 11.2.13	O	TLV-E	4-8195
NOTE: The discovery type is set to "Open discovery" and the content type is set to "Announcement".

Table 10.2.1.2: PROSE PC5 DISCOVERY message content for restricted 5G ProSe direct discovery announcement

IEI	Information Element	Type/Reference	Presence	Format	Length
	ProSe direct discovery PC5 message type (NOTE)	ProSe direct discovery PC5 message type 11.2.1	M	V	1
	UTC-based counter LSB	UTC-based counter LSB 11.2.14	M	V	1
	MIC	MIC 11.2.4	M	V	4
	ProSe restricted code	ProSe restricted code 11.2.3	M	V	23
7A	Metadata	Metadata 11.2.13	O	TLV-E	4-8195
NOTE: The discovery type is set to "Restricted discovery" and the content type is set to "Announcement".

Table 10.2.1.3: PROSE PC5 DISCOVERY message content for restricted 5G ProSe direct discovery solicitation

IEI	Information Element	Type/Reference	Presence	Format	Length
	ProSe direct discovery PC5 message type (NOTE)	ProSe direct discovery PC5 message type 11.2.1	M	V	1
	UTC-based counter LSB	UTC-based counter LSB 11.2.14	M	V	1
	MIC	MIC 11.2.4	M	V	4
	ProSe query code	ProSe restricted code 11.2.3	M	V	23
NOTE: The discovery type is set to "Restricted discovery" and the content type is set to "Solicitation".

Table 10.2.1.4: PROSE PC5 DISCOVERY message content for restricted 5G ProSe direct discovery response

IEI	Information Element	Type/Reference	Presence	Format	Length
	ProSe direct discovery PC5 message type (NOTE)	ProSe direct discovery PC5 message type 11.2.1	M	V	1
	UTC-based counter LSB	UTC-based counter LSB 11.2.14	M	V	1
	MIC	MIC 11.2.4	M	V	4
	ProSe response code	ProSe restricted code 11.2.3	M	V	23
7A	Metadata	Metadata 11.2.13	O	TLV-E	4-8195
NOTE: The discovery type is set to "Restricted discovery" and the content type is set to "response".

Table 10.2.1.5: PROSE PC5 DISCOVERY message for group member discovery announcement

IEI	Information Element	Type/Reference	Presence	Format	Length
	ProSe direct discovery PC5 message type (NOTE)	ProSe direct discovery PC5 message type 11.2.1	M	V	1
	UTC-based counter LSB	UTC-based counter LSB 11.2.14	M	V	1
	MIC	MIC 11.2.4	M	V	4
	Application layer group ID	Application layer group ID 11.2.6	M	LV	2-257
	Announcer info	User info ID 11.2.7	M	V	6
7A	Metadata	Metadata 11.2.13	O	TLV-E	4-8195
NOTE: The discovery type is set to "Restricted discovery", the content type is set to "Group member discovery announcement/group member discovery response" and the discovery model is set to "Model A".

Table 10.2.1.6: PROSE PC5 DISCOVERY message for group member discovery solicitation

IEI	Information Element	Type/Reference	Presence	Format	Length
	ProSe direct discovery PC5 message type (NOTE)	ProSe direct discovery PC5 message type 11.2.1	M	V	1
	UTC-based counter LSB	UTC-based counter LSB 11.2.14	M	V	1
	MIC	MIC 11.2.4	M	V	4
	Application layer group ID	Application layer group ID 11.2.6	M	LV	2-256
	Discoverer info	User info ID 11.2.7	M	V	6
28	Target user info	User info ID 11.2.7	O	TV	7
NOTE: The discovery type is set to "Restricted discovery", the content type is set to "Group member discovery solicitation" and the discovery model is set to "Model B".

Table 10.2.1.7: PROSE PC5 DISCOVERY message for group member discovery response

IEI	Information Element	Type/Reference	Presence	Format	Length
	ProSe direct discovery PC5 message type (NOTE)	ProSe direct discovery PC5 message type 11.2.1	M	V	1
	UTC-based counter LSB	UTC-based counter LSB 11.2.14	M	V	1
	MIC	MIC 11.2.4	M	V	4
	Application layer group ID	Application layer group ID 11.2.6	M	LV	2-256
	Discoveree info	User info ID 11.2.7	M	V	6
7A	Metadata	Metadata 11.2.13	O	TLV-E	4-8195
NOTE: The discovery type is set to "Restricted discovery", the content type is set to "Group member discovery announcement/group member discovery response" and the discovery model is set to "Model B".

Table 10.2.1.8: PROSE PC5 DISCOVERY message for UE-to-network relay discovery announcement

IEI	Information Element	Type/Reference	Presence	Format	Length
	ProSe direct discovery PC5 message type (NOTE 1)	ProSe direct discovery PC5 message type 11.2.1	M	V	1
	UTC-based counter LSB	UTC-based counter LSB 11.2.11	M	V	1
	MIC	MIC 11.2.4	M	V	4
	Announcer info	User info ID 11.2.7	M	V	6
	Relay service code (NOTE 2)	Relay service code 11.2.8	M	V	3
	Status indicator	Status indicator 11.2.9	M	V	1
52	NCGI	NCGI 11.2.12	O	TV	9
63	RRC container	RRC container 11.2.14	O	TLV	3-257
NOTE 1: The discovery type is set to "Restricted discovery", the content type is set to "UE-to-network relay discovery announcement/UE-to-network relay discovery response" and the discovery model is set to "Model A". NOTE 2: If the announcing UE works as a 5G ProSe Layer-3 UE-to-network relay UE, the S-NSSAI associated with the relay service code belongs to the allowed NSSAI of the UE.

Table 10.2.1.9: PROSE PC5 DISCOVERY message for UE-to-network relay discovery solicitation

IEI	Information Element	Type/Reference	Presence	Format	Length
	ProSe direct discovery PC5 message type (NOTE)	ProSe direct discovery PC5 message type 11.2.1	M	V	1
	UTC-based counter LSB	UTC-based counter LSB 11.2.11	M	V	1
	MIC	MIC 11.2.4	M	V	4
	Discoverer info	User info ID 11.2.7	M	V	6
	Relay service code	Relay service code 11.2.8	M	V	3
29	Target discoveree info	User info ID 11.2.7	O	TV	7
NOTE: The discovery type is set to "Restricted discovery", the content type is set to "UE-to-network relay discovery solicitation" and the discovery model is set to "Model B".

Table 10.2.1.10: PROSE PC5 DISCOVERY message for UE-to-network relay discovery response

IEI	Information Element	Type/Reference	Presence	Format	Length
	ProSe direct discovery PC5 message type (NOTE 1)	ProSe direct discovery PC5 message type 11.2.1	M	V	1
	UTC-based counter LSB	UTC-based counter LSB 11.2.11	M	V	1
	MIC	MIC 11.2.4	M	V	4
	Discoveree info	User info ID 11.2.7	M	V	6
	Relay service code (NOTE 2)	Relay service code 11.2.8	M	V	3
	Status indicator	Status indicator 11.2.9	M	V	1
52	NCGI	NCGI 11.2.12	O	TV	9
63	RRC container	RRC container 11.2.14	O	TLV	3-257
NOTE 1: The discovery type is set to "Restricted discovery", the content type is set to "UE-to-network relay discovery announcement/UE-to-network relay discovery response" and the discovery model is set to "Model B". NOTE 2: If the discoveree UE works as a 5G ProSe Layer-3 UE-to-network relay UE, the S-NSSAI associated with the relay service code belongs to the allowed NSSAI of the UE.

Table 10.2.1.11: PROSE PC5 DISCOVERY message for relay discovery additional information

IEI	Information Element	Type/Reference	Presence	Format	Length
	ProSe direct discovery PC5 message type (NOTE)	ProSe direct discovery PC5 message type 11.2.1	M	V	1
	UTC-based counter LSB	UTC-based counter LSB 11.2.11	M	V	1
	MIC	MIC 11.2.4	M	V	4
	Relay service code	Relay service code 11.2.8	M	V	3
	Announcer info	User info ID 11.2.7	M	V	1
52	NCGI	NCGI 11.2.12	O	TV	9
51	Relay TAI	TAI 11.2.10	O	TV	4
NOTE: The discovery type is set to "Restricted discovery", the content type is set to "Relay discovery additional information" and the discovery model is set to "Model A".

10.2.2 Relay TAI

The information element may be included in PROSE PC5 DISCOVERY message for relay discovery additional information as in table 10.2.1.11 to indicate the tracking area identity corresponding to the serving cell of the 5G ProSe layer-3 UE-to-network relay for discoveree UEs supporting N3IWF discovery procedure.

10.2.3 NCGI

The NCGI information element shall be included in:

a) PROSE PC5 DISCOVERY message for UE-to-network relay discovery announcement as in table 10.2.1.8; or

b) PROSE PC5 DISCOVERY message for UE-to-network relay discovery response as in table 10.2.1.10;

to indicate the NCGI of the serving cell if the UE acts as a 5G ProSe layer-2 UE-to-network relay UE.

When the UE acts as a 5G ProSe layer-3 UE-to-network relay UE, the UE may include the NCGI information element in PROSE PC5 DISCOVERY message for relay discovery additional information as in table 10.2.1.11 to indicate the NCGI of the serving cell.

10.2.4 Target user info

The target user info IE shall be included in PROSE PC5 DISCOVERY message for group member discovery solicitation in as in table 10.2.1.6 if the target information is provided by the upper layers to identify a specific group member of the application layer group identified by the configured application layer group ID.

10.2.5 Metadata

The Metadata information element may be included:

a) to provide the application layer metadata information in the following messages:

1) the PROSE PC5 DISCOVERY message for open 5G ProSe direct discovery announcement as in table 10.2.1.1;

2) the PROSE PC5 DISCOVERY message for restricted 5G ProSe direct discovery announcement as in table 10.2.1.2; and

3) the PROSE PC5 DISCOVERY message for restricted 5G ProSe direct discovery response as in table 10.2.1.4; or

b) to provide the application layer discovery message in the following messages:

1) the PROSE PC5 DISCOVERY message for group member discovery announcement as in table 10.2.1.5; and

2) the PROSE PC5 DISCOVERY message for group member discovery response as in table 10.2.1.7.

NOTE 1: The format of the application layer metadata information and the application layer discovery message are out of scope of this specification.

NOTE 2: Possible impact on the performance of the 5G ProSe direct discovery procedure is to be considered if the resulted Metadata information element size is too big, e.g., longer delay and lower reliability.

10.2.6 RRC container

The RRC container information element shall be included in:

a) PROSE PC5 DISCOVERY message for UE-to-network relay discovery announcement as in table 10.2.1.8; or

b) PROSE PC5 DISCOVERY message for UE-to-network relay discovery response as in table 10.2.1.10;

to indicate the RRC container information if it is received from the lower layers and the UE acts as a 5G ProSe layer-2 UE-to-network relay UE.

10.2.7 Target discoveree info

The target discoveree info IE shall be included in PROSE PC5 DISCOVERY message for UE-to-network relay discovery solicitation as in table 10.2.1.9 if the target discoveree info is provided by the application layer.

10.3 PC5 signalling messages

10.3.1 ProSe direct link establishment request

10.3.1.1 Message definition

This message is sent by a UE to another peer UE to establish a direct link. See table 10.3.1.1.1.

Message type: PROSE DIRECT LINK ESTABLISHMENT REQUEST

Significance: dual

Direction: UE to peer UE

Table 10.3.1.1.1: PROSE DIRECT LINK ESTABLISHMENT REQUEST message content

IEI	Information Element	Type/Reference	Presence	Format	Length
	PROSE DIRECT LINK ESTABLISHMENT REQUEST message identity	ProSe PC5 signalling message type 11.3.1	M	V	1
	Sequence number	Sequence number 11.3.2	M	V	1
	Source user info	Application layer ID 11.3.4	M	LV	2-256
	UE security capabilities	UE security capabilities 11.3.11	M	LV	3-9
	UE PC5 unicast signalling security policy	UE PC5 unicast signalling security policy 11.3.12	M	V	1
4F	MIC	MIC 11.3.y	O	TV	5
7B	ProSe identifiers	ProSe identifier 11.3.3	O	TLV-E	21-65538
74	Key establishment information container	Key establishment information container 11.3.9	O	TLV-E	4-65538
56	Nonce_1	Nonce 11.3.10	O	TV	17
5C	MSB of K_NRP-sess ID	MSB of K_NRP-sess ID 11.3.13	O	TV	2
28	Target user info	Application layer ID 11.3.4	O	TLV	3-257
58	K_NRP ID	K_NRP ID 11.3.14	O	TV	5
54	Relay service code	Relay service code 11.3.26	O	TV	4
7D	UE identity	5GS mobile identity 11.3.30	O	TLV-E	4-n
64	User security key ID	User security key ID 11.3.32	O	TLV	3-n
2A	HPLMN ID	PLMN ID 11.3.33	O	TLV	5
2B	UTC-based counter LSB	UTC-based counter LSB 11.2.14	O	TV	2

10.3.1.2 Target user info

The UE shall include this IE if the target UE’s application layer ID is received from upper layers or known based on the unicast layer-2 ID of target UE (i.e. destination layer-2 ID) as described in clause 5.8.2.4 of 3GPP TS 23.304 [3], or if the UE receives the user info ID of the 5G ProSe UE-to-network relay UE during the 5G ProSe UE-to-network relay discovery procedure.

10.3.1.3 Key establishment information container

The UE shall include this IE if the UE PC5 unicast signalling security policy is set to "Signalling integrity protection required" or "Signalling integrity protection preferred".

10.3.1.4 Nonce_1

The UE shall include this IE if the UE PC5 unicast signalling security policy is set to "Signalling integrity protection required" or "Signalling integrity protection preferred" and the 5G ProSe direct link is not for direct communication between the 5G ProSe remote UE and the 5G ProSe UE-to-network relay UE.

NOTE: When the 5G ProSe direct link establishment procedure is between the 5G ProSe remote UE and the 5G ProSe UE-to-network relay UE and the security procedure over user plane is used as specified in 3GPP TS 33.503 [34], the "Nonce_1" is called "K_NRP freshness parameter 1" as specified in 3GPP TS 33.503 [34].

10.3.1.5 MSB of K_NRP-sess ID

The UE shall include this IE if the UE PC5 unicast signalling security policy is set to "Signalling integrity protection required" or "Signalling integrity protection preferred".

10.3.1.6 K_NRP ID

The UE may include this IE if it has an existing K_NRP for the target UE.

10.3.1.7 Relay service code

The UE shall include this IE if the 5G ProSe direct link establishment procedure is for direct communication between the 5G ProSe remote UE and the 5G ProSe UE-to-network relay UE.

10.3.1.8 ProSe identifiers

The UE shall include this IE if the 5G ProSe direct link establishment procedure is not for 5G ProSe direct communication between the 5G ProSe remote UE and the 5G ProSe UE-to-network relay UE.

10.3.1.9 UE identity

The UE shall include this IE if the 5G ProSe direct link establishment procedure is for direct communication between the 5G ProSe layer-3 remote UE and the 5G ProSe layer-3 UE-to-network relay UE.

10.3.1.10 User security key ID

The UE shall include this IE if the 5G ProSe direct link establishment procedure is for direct communication between the 5G ProSe remote UE and the 5G ProSe UE-to-network relay UE, and:

a) the security procedure over user plane for 5G ProSe UE-to-network relay is used as specified in 3GPP TS 33.503 [34] and the UE has a valid UP-PRUK; or

b) the security procedure over control plane for 5G ProSe UE-to-network relay is used as specified in 3GPP TS 33.503 [34] and the UE has a valid CP-PRUK associated with the relay service code of the target UE.

10.3.1.11 HPLMN ID

The UE shall include this IE if the the UP-PRUK ID of the UE is included and is not in NAI format (see 3GPP TS 33.503 [34]).

10.3.1.12 UTC-based counter LSB

The UE shall include this IE if the 5G ProSe direct link establishment procedure is for direct communication between the 5G ProSe remote UE and the 5G ProSe UE-to-network relay UE.

10.3.1.13 MIC

The UE shall include this IE if the 5G ProSe direct link establishment procedure is for direct communication between the 5G ProSe remote UE and the 5G ProSe UE-to-network relay UE and the UE has the DUIK.

10.3.2 ProSe direct link establishment accept

10.3.2.1 Message definition

This message is sent by a UE to another peer UE to accept the received PROSE DIRECT LINK ESTABLISHMENT REQUEST message. See table 10.3.2.1.1.

Message type: PROSE DIRECT LINK ESTABLISHMENT ACCEPT

Significance: dual

Direction: UE to peer UE

Table 10.3.2.1.1: PROSE DIRECT LINK ESTABLISHMENT ACCEPT message content

IEI	Information Element	Type/Reference	Presence	Format	Length
	PROSE DIRECT LINK ESTABLISHMENT ACCEPT message identity	ProSe PC5 signalling message type 11.3.1	M	V	1
	Sequence number	Sequence number 11.3.2	M	V	1
	Source user info	Application layer ID 11.3.4	M	LV	2-256
	Configuration of UE PC5 unicast user plane security protection	Configuration of UE PC5 unicast user plane security protection 11.3.23	M	V	1
79	QoS flow descriptions	PC5 QoS flow descriptions 11.3.5	O	TLV-E	6-65538
7C	QoS rules	PC5 QoS rules 11.3.29	O	TLV-E	7-65538
62	IP address configuration	IP address configuration 11.3.6	O	TV	2
61	Target link local IPv6 address	Link local IPv6 address 11.3.7	O	TV	17

10.3.2.2 IP address configuration

The UE shall include this IE if IP communication is used.

10.3.2.3 Target link local IPv6 address

The UE shall include this IE if IP communication is used and the IP address configuration is set to "address allocation not supported".

10.3.2.4 QoS flow descriptions

The UE shall include this IE if:

a) the 5G ProSe direct link establishment procedure is not for 5G ProSe direct communication between the 5G ProSe remote UE and the 5G ProSe UE-to-network relay UE; or

b) the 5G ProSe direct link establishment procedure is for 5G ProSe direct communication between the 5G ProSe layer-3 remote UE and the 5G ProSe layer-3 UE-to-network relay UE.

10.3.2.5 QoS rules

The UE may include this IE to indicate the PC5 QoS rules for the established PC5 QoS flow(s).

10.3.3 ProSe direct link establishment reject

10.3.3.1 Message definition

This message is sent by the UE to another peer UE to indicate that the link establishment request is not accepted. See table 10.3.3.1.1.

Message type: PROSE DIRECT LINK ESTABLISHMENT REJECT

Significance: dual

Direction: UE to peer UE

Table 10.3.3.1.1: PROSE DIRECT LINK ESTABLISHMENT REJECT message content

IEI	Information Element	Type/Reference	Presence	Format	Length
	PROSE DIRECT LINK ESTABLISHMENT REJECT message identity	ProSe PC5 signalling message type 11.3.1	M	V	1
	Sequence number	Sequence number 11.3.2	M	V	1
	PC5 signalling protocol cause	PC5 signalling protocol cause 11.3.8	M	V	1
5E	Back-off value	GPRS timer 11.3.27	O	TV	2
XY	EAP message	EAP message 11.3.31	O	TLV-E	7-1503

10.3.3.2 Back-off value

The UE may include this IE when it needs to indicate a back-off timer to another peer UE for congestion control purpose.

10.3.3.3 EAP message

The EAP message IE is included if received from the network according to the security procedure over control plane as specified in 3GPP TS 33.503 [34], when the direct communication is between the 5G ProSe remote UE and the 5G ProSe UE-to-network relay UE:

10.3.4 ProSe direct link release request

10.3.4.1 Message definition

This message is sent by the UE to another peer UE to initiate the direct link release procedure. See table 10.3.4.1.1.

Message type: PROSE DIRECT LINK RELEASE REQUEST

Significance: dual

Direction: UE to peer UE

Table 10.3.4.1.1: PROSE DIRECT LINK RELEASE REQUEST message content

IEI	Information Element	Type/Reference	Presence	Format	Length
	PROSE DIRECT LINK RELEASE REQUEST message identity	ProSe PC5 signalling message type 11.3.1	M	V	1
	Sequence number	Sequence number 11.3.2	M	V	1
	PC5 signalling protocol cause	PC5 signalling protocol cause 11.3.8	M	V	1
	MSBs of K_NRP ID	MSBs of K_NRP ID 11.3.16	M	V	2
5E	Back-off value	GPRS timer 11.3.27	O	TV	2

10.3.4.2 Back-off value

The UE may include this IE when it needs to indicate a back-off timer to another peer UE for congestion control purpose.

10.3.5 ProSe direct link release accept

10.3.5.1 Message definition

This message is sent by the UE to another peer UE to indicate that the link release request is accepted. See table 10.3.5.1.1.

Message type: PROSE DIRECT LINK RELEASE ACCEPT

Significance: dual

Direction: UE to peer UE

Table 10.3.5.1.1: PROSE DIRECT LINK RELEASE ACCEPT message content

IEI	Information Element	Type/Reference	Presence	Format	Length
	PROSE DIRECT LINK RELEASE ACCEPT message identity	ProSe PC5 signalling message type 11.3.1	M	V	1
	Sequence number	Sequence number 11.3.2	M	V	1
	LSBs of K_NRP ID	LSBs of K_NRPID 11.3.17	M	V	2

10.3.6 ProSe direct link modification request

10.3.6.1 Message definition

This message is sent by the UE to another peer UE to initiate the direct link modification procedure. See table 10.3.6.1.1.

Message type: PROSE DIRECT LINK MODIFICATION REQUEST

Significance: dual

Direction: UE to peer UE

Table 10.3.6.1.1: PROSE DIRECT LINK MODIFICATION REQUEST message content

IEI	Information Element	Type/Reference	Presence	Format	Length
	PROSE DIRECT LINK MODIFICATION REQUEST message identity	ProSe PC5 signalling message type 11.3.1	M	V	1
	Sequence number	Sequence number 11.3.2	M	V	1
	Link modification operation code	Link modification operation code 11.3.19	M	V	1
	QoS flow descriptions	PC5 QoS flow descriptions 11.3.5	M	LV-E	5-65537
7C	QoS rules	PC5 QoS rules 11.3.29	O	TLV-E	7-65538

10.3.6.2 QoS rules

The UE may include this IE to indicate the PC5 QoS rules for the PC5 QoS flow(s) to be added or modified.

10.3.7 ProSe direct link modification accept

10.3.7.1 Message definition

This message is sent by the UE to another peer UE to indicate that the link modification request is accepted. See table 10.3.7.1.1.

Message type: PROSE DIRECT LINK MODIFICATION ACCEPT

Significance: dual

Direction: UE to peer UE

Table 10.3.7.1.1: PROSE DIRECT LINK MODIFICATION ACCEPT message content

IEI	Information Element	Type/Reference	Presence	Format	Length
	PROSE DIRECT LINK MODIFICATION ACCEPT message identity	ProSe PC5 signalling message type 11.3.1	M	V	1
	Sequence number	Sequence number 11.3.2	M	V	1
79	QoS flow descriptions	PC5 QoS flow descriptions 11.3.5	O	TLV-E	6-65538
7C	QoS rules	PC5 QoS rules 11.3.29	O	TLV-E	7-65538

10.3.7.2 QoS flow descriptions

The UE shall include this IE if the 5G ProSe direct link modification procedure is to:

a) add new PC5 QoS flow(s) to the existing 5G ProSe direct link;

b) modify PC5 QoS parameters of the existing PC5 QoS flow(s);

c) associate new ProSe application(s) with existing PC5 QoS flow(s); or

d) remove ProSe application(s) from existing PC5 QoS flow(s).

10.3.7.3 QoS rules

The UE may include this IE to indicate the PC5 QoS rules for the PC5 QoS flow(s) to be added or modified.

10.3.8 ProSe direct link keepalive request

10.3.8.1 Message definition

This message is sent by a UE to another peer UE when a 5G ProSe direct link keep-alive procedure is initiated. See table 10.3.8.1.1.

Message type: PROSE DIRECT LINK KEEPALIVE REQUEST

Significance: dual

Direction: UE to peer UE

Table 10.3.8.1.1: PROSE DIRECT LINK KEEPALIVE REQUEST message content

IEI	Information Element	Type/Reference	Presence	Format	Length
	PROSE DIRECT LINK KEEPALIVE REQUEST message identity	ProSe PC5 signalling message type 11.3.1.	M	V	1
	Sequence number	Sequence number 11.3.2	M	V	1
	Keep-alive counter	Keep-alive counter 11.3.20	M	V	4
5F	Maximum inactivity period	Maximum inactivity period 11.3.21	O	TV	5

10.3.8.2 Maximum inactivity period

The UE may include this IE to indicate its maximum inactivity period to the peer UE.

10.3.9 ProSe direct link keepalive response

10.3.9.1 Message definition

This message is sent by a UE to another peer UE to respond to a PROSE DIRECT LINK KEEPALIVE REQUEST message. See table 10.3.9.1.1.

Message type: PROSE DIRECT LINK KEEPALIVE RESPONSE

Significance: dual

Direction: UE to peer UE

Table 10.3.9.1.1: PROSE DIRECT LINK KEEPALIVE RESPONSE message content

IEI	Information Element	Type/Reference	Presence	Format	Length
	PROSE DIRECT LINK KEEPALIVE RESPONSE message identity	ProSe PC5 signalling message type 11.3.1.	M	V	1
	Sequence number	Sequence number 11.3.2	M	V	1
	Keep-alive counter	Keep-alive counter 11.3.20	M	V	4

10.3.10 ProSe direct link authentication request

10.3.10.1 Message definition

This message is sent by a UE to another peer UE when a 5G ProSe direct link authentication procedure is initiated. See table 10.3.10.1.1.

Message type: PROSE DIRECT LINK AUTHENTICATION REQUEST

Significance: dual

Direction: UE to peer UE

Table 10.3.10.1.1: PROSE DIRECT LINK AUTHENTICATION REQUEST message content

IEI	Information Element	Type/Reference	Presence	Format	Length
	PROSE DIRECT LINK AUTHENTICATION REQUEST message identity	ProSe PC5 signalling message type 11.3.1.	M	V	1
	Sequence number	Sequence number 11.3.2	M	V	1
	Key establishment information container	Key establishment information container 11.3.9	M	LV-E	3-65537

10.3.11 ProSe direct link authentication response

10.3.11.1 Message definition

This message is sent by a UE to another peer UE to respond to a PROSE DIRECT LINK AUTHENTICATION REQUEST message. See table 10.3.11.1.1.

Message type: PROSE DIRECT LINK AUTHENTICATION RESPONSE

Significance: dual

Direction: UE to peer UE

Table 10.3.11.1.1: PROSE DIRECT LINK AUTHENTICATION RESPONSE message content

IEI	Information Element	Type/Reference	Presence	Format	Length
	PROSE DIRECT LINK AUTHENTICATION RESPONSE message identity	ProSe PC5 signalling message type 11.3.1.	M	V	1
	Sequence number	Sequence number 11.3.2	M	V	1
	Key establishment information container	Key establishment information container 11.3.9	M	LV-E	3-65537

10.3.12 ProSe direct link authentication reject

10.3.12.1 Message definition

This message is sent by a UE to another peer UE to reject a PROSE DIRECT LINK AUTHENTICATION REQUEST message. See table 10.3.12.1.1.

Message type: PROSE DIRECT LINK AUTHENTICATION REJECT

Significance: dual

Direction: UE to peer UE

Table 10.3.12.1.1: PROSE DIRECT LINK AUTHENTICATION REJECT message content

IEI	Information Element	Type/Reference	Presence	Format	Length
	PROSE DIRECT LINK AUTHENTICATION REJECT message identity	ProSe PC5 signalling message type 11.3.1.	M	V	1
	Sequence number	Sequence number 11.3.2	M	V	1
	PC5 signalling protocol cause	PC5 signalling protocol cause 11.3.8	M	V	1

10.3.13 ProSe direct link security mode command

10.3.13.1 Message definition

This message is sent by a UE to another peer UE when a 5G ProSe direct link security mode control procedure is initiated. See table 10.3.13.1.1.

Message type: PROSE DIRECT LINK SECURITY MODE COMMAND

Significance: dual

Direction: UE to peer UE

Table 10.3.13.1.1: PROSE DIRECT LINK SECURITY MODE COMMAND message content

IEI	Information Element	Type/Reference	Presence	Format	Length
	PROSE DIRECT LINK SECURITY MODE COMMAND message identity	ProSe PC5 signalling message type 11.3.1.	M	V	1
	Sequence number	Sequence number 11.3.2	M	V	1
	Selected security algorithms	Selected security algorithms 11.3.22	M	V	1
	UE security capabilities	UE security capabilities 11.3.11	M	LV	3-9
59	UE PC5 unicast signalling security policy	UE PC5 unicast signalling security policy 11.3.12	O	TV	2
57	Nonce_2	Nonce 11.3.10	O	TV	17
5D	LSB of K_NRP-sess ID	LSB of K_NRP-sess ID 11.3.15	O	TV	2
74	Key establishment information container	Key establishment information container 11.3.9	O	TLV-E	4-65538
5A	MSBs of K_NRP ID	MSBs of K_NRP ID 11.3.16	O	TV	3
7A	GPI	GPI 11.3.35	O	TLV-E	n-65538
ZY	EAP message	EAP message 11.3.31	O	TLV-E	7-1503

10.3.13.2 Nonce_2

The UE shall include this IE if the selected integrity protection algorithms is not the null integrity protection algorithm.

NOTE: When the 5G ProSe direct link establishment procedure is between the 5G ProSe remote UE and the 5G ProSe UE-to-network relay UE and the security procedure over user plane is used as specified in 3GPP TS 33.503 [34], the "Nonce_2" is called "K_NRP freshness parameter 2" as specified in 3GPP TS 33.503 [34].

10.3.13.3 LSB of KNRP-sess ID

The UE shall include this IE if the selected integrity protection algorithms is not the null integrity protection algorithm.

10.3.13.4 Key establishment information container

The UE shall include this IE if the UE has derived a new K_NRP and the authentication method used to generate K_NRP requires sending information to complete the authentication procedure and the 5G ProSe direct link is not for direct communication between the 5G ProSe remote UE and the 5G ProSe UE-to-network relay UE.

10.3.13.5 MSBs of K_NRP ID

The UE shall include this IE if the UE has derived a new K_NRP.

10.3.13.6 UE PC5 unicast signalling security policy

The UE shall include this IE if the PROSE DIRECT LINK SECURITY MODE COMMAND message is triggered by the PROSE DIRECT LINK ESTABLISHMENT REQUEST message. The content of the IE is the same as the content of UE PC5 unicast signalling security policy IE in the received PROSE DIRECT LINK ESTABLISHMENT REQUEST message in order to provide protection against bidding down attacks.

10.3.13.7 GPI

The UE shall include this IE if received from the 5G PKMF according to the security procedure over user plane as specified in 3GPP TS 33.503 [34], when the direct communication is between the 5G ProSe remote UE and the 5G ProSe UE-to-network relay UE.

10.3.13.8 EAP message

10.3.14 ProSe direct link security mode complete

10.3.14.1 Message definition

This message is sent by a UE to another peer UE to respond to a PROSE DIRECT LINK SECURITY MODE COMMAND message. See table 10.3.14.1.1.

Message type: PROSE DIRECT LINK SECURITY MODE COMPLETE

Significance: dual

Direction: UE to peer UE

Table 10.3.14.1.1: PROSE DIRECT LINK SECURITY MODE COMPLETE message content

IEI	Information Element	Type/Reference	Presence	Format	Length
	PROSE DIRECT LINK SECURITY MODE COMPLETE message identity	ProSe PC5 signalling message type 11.3.1.	M	V	1
	Sequence number	Sequence number 11.3.2	M	V	1
	UE PC5 unicast user plane security policy	UE PC5 unicast user plane security policy 11.3.23	M	V	1
79	QoS flow descriptions	PC5 QoS flow descriptions 11.3.5	O	TLV-E	6-65538
62	IP address configuration	IP address configuration 11.3.6	O	TV	2
61	Target link local IPv6 address	Link local IPv6 address 11.3.7	O	TV	17
5B	LSBs of K_NRP ID	LSBs of K_NRP ID 11.3.17	O	TV	3
7C	QoS rules	PC5 QoS rules 11.3.29	O	TLV-E	7-65538

10.3.14.2 IP address configuration

The UE shall include this IE if IP communication is used and the 5G ProSe direct link security mode control procedure was triggered during a 5G ProSe direct link establishment procedure.

10.3.14.3 Target link local IPv6 address

The UE shall include this IE if IP communication is used, the IP address configuration is set to "address allocation not supported" and the 5G ProSe direct link security mode control procedure was triggered during a 5G ProSe direct link establishment procedure.

10.3.14.4 LSBs of K_NRP ID

The UE shall include this IE if a new K_NRP was derived.

10.3.14.5 QoS rules

The UE may include this IE to indicate the PC5 QoS rules for the PC5 QoS flow(s) to be added.

10.3.14.6 QoS flow descriptions

The UE shall include this IE if:

a) the 5G ProSe direct link security mode control procedure was triggered during a 5G ProSe direct link establishment procedure and is not for 5G ProSe direct communication between a 5G ProSe remote UE and a 5G ProSe UE-to-network relay UE.

The UE may include this IE if:

a) the 5G ProSe direct link security mode control procedure was triggered during a 5G ProSe direct link establishment procedure and is for 5G ProSe direct communication between the 5G ProSe layer-3 remote UE and the 5G ProSe layer-3 UE-to-network relay UE.

10.3.15 ProSe direct link security mode reject

10.3.15.1 Message definition

This message is sent by a UE to another peer UE to reject a PROSE DIRECT LINK SECURITY MODE COMMAND message. See table 10.3.15.1.1.

Message type: PROSE DIRECT LINK SECURITY MODE REJECT

Significance: dual

Direction: UE to peer UE

Table 10.3.15.1.1: PROSE DIRECT LINK SECURITY MODE REJECT message content

IEI	Information Element	Type/Reference	Presence	Format	Length
	PROSE DIRECT LINK SECURITY MODE REJECT message identity	ProSe PC5 signalling message type 11.3.1.	M	V	1
	Sequence number	Sequence number 11.3.2	M	V	1
	PC5 signalling protocol cause	PC5 signalling protocol cause 11.3.8	M	V	1
2B	RAND	RAND 11.3.36	O	TV	17
2C	AUTS	AUTS 11.3.37	O	TV	15

10.3.15.2 RAND

The UE shall include this IE if there is a synchronisation error and the 5G ProSe direct link security mode control procedure is for direct communication between the 5G ProSe remote UE and the 5G ProSe UE-to-network relay UE.

10.3.15.3 AUTS

10.3.16 ProSe direct link rekeying request

10.3.16.1 Message definition

This message is sent by a UE to another peer UE when a 5G ProSe direct link re-keying procedure is initiated. See table 10.3.16.1.1.

Message type: PROSE DIRECT LINK REKEYING REQUEST

Significance: dual

Direction: UE to peer UE

Table 10.3.16.1.1: PROSE DIRECT LINK REKEYING REQUEST message content

IEI	Information Element	Type/Reference	Presence	Format	Length
	PROSE DIRECT LINK REKEYING REQUEST message identity	ProSe PC5 signalling message type 11.3.1.	M	V	1
	Sequence number	Sequence number 11.3.2	M	V	1
	UE security capabilities	UE security capabilities 11.3.11	M	LV	3-9
74	Key establishment information container	Key establishment information container 11.3.9	O	TLV-E	4-65538
56	Nonce_1	Nonce 11.3.10	O	TV	17
5C	MSB of K_NRP-sess ID	MSB of K_NRP-sess ID 11.3.13	O	TV	2
55	Re-authentication indication	Re-authentication indication 11.3.24	O	TV	2
64	User security key ID	User security key ID 11.3.32	O	TLV	3-n
2A	HPLMN ID	HPLMN ID 11.3.bb	O	TLV	5

10.3.16.2 Key establishment information container

The UE shall include this IE if the null integrity protection algorithm is not in use and the 5G ProSe direct link is not for direct communication between the 5G ProSe remote UE and the 5G ProSe UE-to-network relay UE.

10.3.16.3 Nonce_1

The UE shall include this IE if the null integrity protection algorithm is not in use.

NOTE 2: When the 5G ProSe direct link re-keying procedure is between the 5G ProSe remote UE and the 5G ProSe UE-to-network relay UE and the security procedure over user plane is used as specified in 3GPP TS 33.503 [34], the "Nonce_1" is called "K_NRP freshness parameter 1" as specified in 3GPP TS 33.503 [34].

10.3.16.4 MSB of KNRP-sess ID

The UE shall include this IE if the null integrity protection algorithm is not in use.

10.3.16.5 Re-authentication indication

The UE shall include this IE if the UE wants to derive a new K_NRP.

10.3.16.6 User security key ID

The UE shall include this IE if the 5G ProSe direct link re-keying procedure is for direct communication between the 5G ProSe remote UE and the 5G ProSe UE-to-network relay UE, and:

a) the security procedure over user plane as specified in 3GPP TS 33.503 [34] is used and the UE has a valid UP-PRUK; or

b) the security procedure over control plane as specified in 3GPP TS 33.503 [34] is used and the UE has a valid CP-PRUK associated with the relay service code of the target UE.

10.3.16.7 HPLMN ID

The UE shall include this IE if the UP-PRUK ID is included and is not in NAI format (see 3GPP TS 33.503 [34]).

10.3.17 ProSe direct link rekeying response

10.3.17.1 Message definition

This message is sent by a UE to another peer UE to respond to a PROSE DIRECT LINK REKEYING REQUEST message. See table 10.3.17.1.1.

Message type: PROSE DIRECT LINK REKEYING RESPONSE

Significance: dual

Direction: UE to peer UE

Table 10.3.17.1.1: PROSE DIRECT LINK REKEYING RESPONSE message content

IEI

Information Element

Type/Reference

Presence

Format

Length

PROSE DIRECT LINK REKEYING RESPONSE message identity

ProSe PC5 signalling message type

11.3.1.

Sequence number

11.3.2

10.3.18 ProSe direct link identifier update request

10.3.18.1 Message definition

This message is sent by a UE to another peer UE to initiate the direct link identifier procedure. See table 10.3.18.1.1.

Message type: PROSE DIRECT LINK IDENTIFIER UPDATE REQUEST

Significance: dual

Direction: UE to peer UE

Table 10.3.18.1.1: PROSE DIRECT LINK IDENTIFIER UPDATE REQUEST message content

IEI	Information Element	Type/Reference	Presence	Format	Length
	PROSE DIRECT LINK IDENTIFIER UPDATE REQUEST message identity	ProSe PC5 signalling message type 11.3.1	M	V	1
	Sequence number	Sequence number 11.3.2	M	V	1
	MSB of K_NRP-sess ID	MSB of K_NRP-sessID 11.3.13	M	V	1
	Source layer-2 ID	Layer-2 ID 11.3.25	M	V	3
27	Source user info	Application layer ID 11.3.4	O	TLV	3-257
60	Source link local IPv6 address	Link local IPv6 address 11.3.7	O	TV	17

10.3.18.2 Source user info

This IE is included when the initiating UE receives a new application layer ID.

10.3.18.3 Source link local IPv6 address

This IE is included when the link local IPv6 address changes at the initiating UE and the 5G ProSe direct link is not for 5G ProSe direct communication between 5G ProSe layer-2 remote UE and 5G ProSe layer-2 UE-to-network relay UE.

10.3.19 ProSe direct link identifier update accept

10.3.19.1 Message definition

This message is sent by the UE to another peer UE to indicate that the link identifier update request is accepted. See table 10.3.19.1.1.

Message type: PROSE DIRECT LINK IDENTIFIER UPDATE ACCEPT

Significance: dual

Direction: UE to peer UE

Table 10.3.19.1.1: PROSE DIRECT LINK IDENTIFIER UPDATE ACCEPT message content

IEI	Information Element	Type/Reference	Presence	Format	Length
	PROSE DIRECT LINK IDENTIFIER UPDATE ACCEPT message identity	ProSe PC5 signalling message type 11.3.1	M	V	1
	Sequence number	Sequence number 11.3.2	M	V	1
	LSB of K_NRP-sess ID	LSB of K_NRP-sessID 11.3.15	M	V	1
	MSB of K_NRP-sess ID	MSB of K_NRP-sessID 11.3.13	M	V	1
	Source layer-2 ID	Layer-2 ID 11.3.25	M	V	3
	Target layer-2 ID	Layer-2 ID 11.3.25	M	V	3
28	Target user info	Application layer ID 11.3.4	O	TLV	3-257
61	Target link local IPv6 address	Link local IPv6 address 11.3.7	O	TV	17
27	Source user info	Application layer ID 11.3.4	O	TLV	3-257
60	Source link local IPv6 address	Link local IPv6 address 11.3.7	O	TV	17

10.3.19.2 Target user info

This IE is included if the target UE receives the Source user info IE in the PROSE DIRECT LINK IDENTIFIER UPDATE REQUEST message.

10.3.19.3 Target link local IPv6 address

This IE is included if the target UE receives the Source link local IPv6 address IE in the PROSE DIRECT LINK IDENTIFIER UPDATE REQUEST message.

10.3.19.4 Source user info

This IE is included when the application layer ID changes at the target UE and the target UE receives a new application layer ID from the upper layers.

10.3.19.5 Source link local IPv6 address

This IE is included when the link local IPv6 address changes at the target UE and the target UE receives a new Link local IPv6 address from the upper layers and the 5G ProSe direct link is not for 5G ProSe direct communication between 5G ProSe layer-2 remote UE and 5G ProSe layer-2 UE-to-network relay UE.

10.3.20 ProSe direct link identifier update ack

10.3.20.1 Message definition

This message is sent by the initiating UE to target UE to indicate that the initiating UE has received target UE’s accept message. See table 10.3.20.1.1.

Message type: PROSE DIRECT LINK IDENTIFIER UPDATE ACK

Significance: dual

Direction: UE to peer UE

Table 10.3.20.1.1: PROSE DIRECT LINK IDENTIFIER UPDATE ACK message content

IEI	Information Element	Type/Reference	Presence	Format	Length
	PROSE DIRECT LINK IDENTIFIER UPDATE ACK message identity	ProSe PC5 signalling message type 11.3.1	M	V	1
	Sequence number	Sequence number 11.3.2	M	V	1
	LSB of K_NRP-sess ID	LSB of K_NRP-sessID 11.3.15	M	V	1
	Target layer-2 ID	Layer-2 ID 11.3.25	M	V	3
28	Target user info	Application layer ID 11.3.4	O	TLV	3-257
61	Target link local IPv6 address	Link local IPv6 address 11.3.7	O	TV	17

10.3.20.2 Target user info

This IE is included when the initiating UE receives the Source user info IE in the PROSE DIRECT LINK IDENTIFIER UPDATE ACCEPT message.

10.3.20.3 Target link local IPv6 address

This IE is included when the initiating UE receives the Source link local IPv6 address IE in the PROSE DIRECT LINK IDENTIFIER UPDATE ACCEPT message.

10.3.21 ProSe direct link identifier update reject

10.3.21.1 Message definition

This message is sent by the target UE to initiating UE to indicate that the link identifier update request is not accepted. See table 10.3.21.1.1.

Message type: PROSE DIRECT LINK IDENTIFIER UPDATE REJECT

Significance: dual

Direction: UE to peer UE

Table 10.3.21.1.1: PROSE DIRECT LINK IDENTIFIER UPDATE REJECT message content

IEI	Information Element	Type/Reference	Presence	Format	Length
	PROSE DIRECT LINK IDENTIFIER UPDATE REJECT message identity	ProSe PC5 signalling message type 11.3.1	M	V	1
	Sequence number	Sequence number 11.3.2	M	V	1
	PC5 signalling protocol cause	PC5 signalling protocol cause 11.3.8	M	V	1

10.3.22 ProSe direct link modification reject

10.3.22.1 Message definition

This message is sent by the UE to another peer UE to indicate that the link modification request is not accepted. See table 10.3.22.1.1.

Message type: PROSE DIRECT LINK MODIFICATION REJECT

Significance: dual

Direction: UE to peer UE

Table 10.3.22.1.1: PROSE DIRECT LINK MODIFICATION REJECT message content

IEI	Information Element	Type/Reference	Presence	Format	Length
	PROSE DIRECT LINK MODIFICATION REJECT message identity	ProSe PC5 signalling message type 11.3.1	M	V	1
	Sequence number	Sequence number 11.3.2	M	V	1
	PC5 signalling protocol cause	PC5 signalling protocol cause 11.3.8	M	V	1

10.3.23 ProSe direct link authentication failure

10.3.23.1 Message definition

This message is sent by a UE to another peer UE to reject a PROSE DIRECT LINK AUTHENTICATION RESPONSE message. See table 10.3.23.1.1.

Message type: PROSE DIRECT LINK AUTHENTICATION FAILURE

Significance: dual

Direction: UE to peer UE

Table 10.3.23.1.1: PROSE DIRECT LINK AUTHENTICATION FAILURE message content

IEI	Information Element	Type/Reference	Presence	Format	Length
	PROSE DIRECT LINK AUTHENTICATION FAILURE message identity	ProSe PC5 signalling message type 11.3.1.	M	V	1
	Sequence number	Sequence number 11.3.2	M	V	1
74	Key establishment information container	Key establishment information container 11.3.9	O	TLV-E	4-65538

10.3.23.2 Key establishment information container

The UE shall include this IE if it is provided by upper layers.

10.3.24 ProSe additional parameters announcement request

10.3.24.1 Message definition

This message is sent by the 5G ProSe layer-3 remote UE to 5G ProSe layer-3 UE-to-network relay UE to initiate the ProSe additional parameters announcement request procedure. See table 10.3.24.1.1.

Message type: PROSE ADDITIONAL PARAMETERS ANNOUNCEMENT REQUEST

Significance: dual

Direction: UE to peer UE

Table 10.3.24.1.1: PROSE ADDITIONAL PARAMETERS ANNOUNCEMENT REQUEST content

IEI

Information Element

Type/Reference

Presence

Format

Length

PROSE ADDITIONAL PARAMETERS ANNOUNCEMENT REQUEST identity

ProSe PC5 signalling message type

11.3.1

Sequence Number

11.3.2

10.3.25 ProSe additional parameters announcement response

10.3.25.1 Message definition

This message is sent by the 5G ProSe layer-3 UE-to-network relay UE to the 5G ProSe layer-3 remote UE to acknowledge and respond to the ProSe additional parameters announcement request. See table 10.3.25.1.1.

Message type: PROSE ADDITIONAL PARAMETERS ANNOUNCEMENT RESPONSE

Significance: dual

Direction: UE to peer UE

Table 10.3.25.1.1: PROSE ADDITIONAL PARAMETERS ANNOUNCEMENT RESPONSE content

IEI	Information Element	Type/Reference	Presence	Format	Length
	PROSE ADDITIONAL PARAMETERS ANNOUNCEMENT RESPONSE identity	ProSe PC5 signalling message type 11.3.1	M	V	1
	Sequence Number	Sequence number 11.3.2	M	V	1
	Additional parameters announcement request refresh timer T5106	Binary 11.3.28	M	V	2

10.3.26 ProSe AA message transport request

10.3.26.1 Message definition

This message is sent by the 5G ProSe layer-3 UE-to-network relay UE to the 5G ProSe layer-3 remote UE to forward the EAP message. See table 10.3.26.1.1.

Message type: PROSE AA MESSAGE TRANSPORT REQUEST

Significance: dual

Direction: UE to peer UE

Table 10.3.26.1.1: PROSE AA MESSAGE TRANSPORT REQUEST content

IEI	Information Element	Type/Reference	Presence	Format	Length
	PROSE AA MESSAGE TRANSPORT REQUEST identity	ProSe PC5 signalling message type 11.3.1	M	V	1
	Sequence Number	Sequence number 11.3.2	M	V	1
70	EAP message	EAP message 11.3.31	O	TLV-E	7-1503

10.3.26.2 EAP message

The EAP message IE is included if the PROSE AA MESSAGE TRANSPORT REQUEST message is used in an EAP based authentication procedure.

10.3.27 ProSe AA message transport response

10.3.27.1 Message definition

This message is sent by the 5G ProSe layer-3 remote UE to the 5G ProSe layer-3 UE-to-network relay UE to forward the EAP message. See table 10.3.27.1.1.

Message type: PROSE AA MESSAGE TRANSPORT RESPONSE

Significance: dual

Direction: UE to peer UE

Table 10.3.27.1.1: PROSE AA MESSAGE TRANSPORT RESPONSE content

IEI	Information Element	Type/Reference	Presence	Format	Length
	PROSE AA MESSAGE TRANSPORT RESPONSE identity	ProSe PC5 signalling message type 11.3.1	M	V	1
	Sequence Number	Sequence number 11.3.2	M	V	1
70	EAP message	EAP message 11.3.31	O	TLV-E	7-1503

10.3.27.2 EAP message

The EAP message IE is included if the PROSE AA MESSAGE TRANSPORT RESPONSE message is used in an EAP based authentication procedure.

10.4 Provisioning of 5G ProSe configuration information signalling messages

10.4.1 UE policy provisioning request

The UE POLICY PROVISIONING REQUEST message is sent by the UE to the PCF to request the PCF to manage ProSeP, see 3GPP TS 24.587 [18] clause 7.2.1 for the message definition.

10.4.2 UE policy provisioning reject

The UE POLICY PROVISIONING REJECT message is sent by the PCF to the UE to report that the PCF rejects the request to manage ProSeP, see 3GPP TS 24.587 [18] clause 7.2.2 for the message definition.

10.5 5G ProSe discovery and security messages over PC3a

10.5.1 General

This clause defines the XML schema and MIME type related to 5G ProSe direct discovery messages.

10.5.2 application/vnd.3gpp-prose-pc3a+xml

The MIME type is used to carry information related to the 5G ProSe discovery operation. It shall be coded as an XML document containing one of the following 5G ProSe discovery messages:

a) DISCOVERY_REQUEST;

b) DISCOVERY_RESPONSE;

c) MATCH_REPORT;

d) MATCH_REPORT_ACK;

e) DISCOVERY_UPDATE_REQUEST;

f) DISCOVERY_UPDATE_RESPONSE;

g) ANNOUNCING_ALERT_REQUEST;

h) ANNOUNCING_ALERT_RESPONSE;

i) PROSE_5GPKMF_ADDRESS_REQUEST;

j) PROSE_5GPKMF_ADDRESS_RESPONSE;

k) PROSE_SECURITY_MATERIAL_REQUEST; or

l) PROSE_SECURITY_MATERIAL_RESPONSE

Each of those messages is presented in the XML document as an XML element named after the corresponding message.

10.5.3 XML schema

Implementations in compliance with the present document shall implement the XML schema defined below for messages used in 5G ProSe direct discovery procedures over PC3a interface.

<?xml version="1.0" encoding="UTF-8"?>

<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"

xmlns="urn:3GPP:ns:5GProSe:Discovery:2021"

elementFormDefault="qualified"

targetNamespace="urn:3GPP:ns:5GProSe:Discovery:2021">

<xs:annotation>

<xs:documentation>

Info for 5G ProSe Discovery Control Messages Syntax

</xs:documentation>

</xs:annotation>

<!– Complex types defined for parameters with complicated structure –>

<xs:complexType name="AppID-info">

<xs:sequence>

<xs:element name="OS-ID">

<xs:simpleType>

<xs:restriction base="xs:hexBinary">

<xs:length value="16"/>

</xs:restriction>

</xs:simpleType>

</xs:element>

<xs:element name="OS-App-ID" type="xs:string"/>

<xs:any namespace="##any" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="PLMN-info">

<xs:sequence>

<xs:element name="mcc" type="xs:integer"/>

<xs:element name="mnc" type="xs:integer"/>

<xs:any namespace="##any" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="DiscFilter-info">

<xs:sequence>

<xs:element name="ProSe-Application-Code" type="xs:hexBinary"/>

<xs:element name="ProSe-Application-Mask" type="xs:hexBinary" maxOccurs="unbounded"/>

<xs:element name="TTL-timer-T5064" type="xs:integer"/>

<xs:any namespace="##any" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="MatchingFilter-info">

<xs:sequence>

<xs:element name="Code" type="xs:hexBinary"/>

<xs:element name="Mask" type="xs:hexBinary" maxOccurs="unbounded"/>

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="DUCK-info">

<xs:sequence>

<xs:element name="discovery-user-confidentiality-key" type="xs:hexBinary"/>

<xs:element name="encrypted-bitmask" type="xs:hexBinary"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="RestrictedDiscFilter-info">

<xs:sequence>

<xs:element name="filter" type="MatchingFilter-info" maxOccurs="unbounded"/>

<xs:element name="TTL-timer-T5066" type="xs:integer"/>

<xs:element name="RPAUID" type="xs:string" minOccurs="0" />

<xs:element name="metadata-indicator" type="xs:integer" minOccurs="0"/>

<xs:element name="metadata" type="xs:string" minOccurs="0"/>

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="RestrictedCodeSuffixRange-info">

<xs:sequence>

<xs:element name="beginning-suffix-code" type="xs:hexBinary" />

<xs:element name="ending-suffix-code" type="xs:hexBinary" minOccurs="0"/>

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="RestrictedMonitoringUpdate-info">

<xs:sequence>

<xs:element name="updated-filter" type="RestrictedDiscFilter-info" maxOccurs="unbounded"/>

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="RestrictedAnnouncingUpdate-info">

<xs:sequence>

<xs:element name="ProSe-Restricted-Code" type="xs:hexBinary" />

<xs:element name="validity-timer-T5062" type="xs:integer" />

<xs:any namespace="##any" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="MonitoringUpdate-info">

<xs:sequence>

<xs:element name="updated-filter" type="DiscFilter-info" maxOccurs="unbounded"/>

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="AnnouncingUpdate-info">

<xs:sequence>

<xs:element name="ProSe-Application-Code" type="xs:hexBinary" />

<xs:element name="validity-timer-T5060" type="xs:integer" />

<xs:any namespace="##any" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="Update-Option-info">

<xs:choice>

<xs:element name="update-info-restricted-announce" type="RestrictedAnnouncingUpdate-info" />

<xs:element name="update-info-restricted-monitor" type="RestrictedMonitoringUpdate-info" />

<xs:element name="update-info-open-annnounce" type="AnnouncingUpdate-info" />

<xs:element name="update-info-open-monitor" type="MonitoringUpdate-info"/>

<xs:element name="anyExt" type="anyExtType" />

<xs:any namespace="##other" processContents="lax"/>

</xs:choice>

</xs:complexType>

<xs:complexType name="Restricted-Code-Option-info">

<xs:choice>

<xs:element name="ProSe-Restricted-Code" type="xs:hexBinary" />

<xs:element name="ProSe-Response-Code" type="xs:hexBinary" />

<xs:element name="anyExt" type="anyExtType" />

<xs:any namespace="##other" processContents="lax"/>

</xs:choice>

</xs:complexType>

<xs:complexType name="Subquery-info">

<xs:sequence>

<xs:element name="ProSe-Rquery-Code" type="xs:hexBinary" />

<xs:element name="response-filter" type="MatchingFilter-info" maxOccurs="unbounded"/>

<xs:element name="validity-timer-T5070" type="xs:integer"/>

<xs:element name="code-sending-security-parameter" type="Restricted-Security-info" />

<xs:element name="code-receiving-security-parameter" type="Restricted-Security-info" minOccurs="0" />

<xs:element name="RPAUID" type="xs:string" minOccurs="0" />

<xs:element name="metadata" type="xs:string" minOccurs="0"/>

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="Restricted-Security-info">

<xs:sequence>

<xs:element name="DUSK" type="xs:hexBinary" minOccurs="0" />

<xs:element name="DUIK" type="xs:hexBinary" minOccurs="0" />

<xs:element name="DUCK" type="DUCK-info" minOccurs="0" />

<xs:element name="MIC-check-indicator" type="xs:boolean" minOccurs="0" />

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="ApplicationCodeSuffixRange-info">

<xs:sequence>

<xs:element name="beginning-suffix-code" type="xs:hexBinary" />

<xs:element name="ending-suffix-code" type="xs:hexBinary" minOccurs="0"/>

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="ProSeApplicationCodeACE-info">

<xs:sequence>

<xs:element name=" ProSe-Application-Code-Prefix" type="xs:hexBinary" />

<xs:element name=" ProSe-Application-Code-Suffix-Range" type="ApplicationCodeSuffixRange-info" maxOccurs="unbounded" />

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="PC5-Security-Policies-info">

<xs:sequence>

<xs:element name="signalling-integrity-protection-policy" type="xs:integer"/>

<xs:element name="signalling-ciphering-policy" type="xs:integer"/>

<xs:element name="user-plane-integrity-protection-policy" type="xs:integer"/>

<xs:element name="user-plane-ciphering-policy" type="xs:integer"/>

<xs:any namespace="##any" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<!– Complex types defined for transaction-level –>

<xs:complexType name="AnnounceRsp-info">

<xs:sequence>

<xs:element name="transaction-ID" type="xs:integer"/>

<xs:element name="ProSe-Application-Code" type="xs:hexBinary" minOccurs="0" maxOccurs="unbounded"/>

<xs:element name="ProSe-Application-Code-ACE" type="ProSeApplicationCodeACE-info" minOccurs="0"/>

<xs:element name="validity-timer-T5060" type="xs:integer" minOccurs="0" />

<xs:element name="discovery-key" type="xs:hexBinary" minOccurs="0" />

<xs:element name="discovery-entry-ID" type="xs:integer" minOccurs="0" />

<xs:element name="ACE-enabled-indicator" type="xs:integer" minOccurs="0"/>

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="MonitorRsp-info">

<xs:sequence>

<xs:element name="transaction-ID" type="xs:integer"/>

<xs:element name="discovery-filter" type="DiscFilter-info" minOccurs="0" maxOccurs="unbounded"/>

<xs:element name="discovery-entry-ID" type="xs:integer" minOccurs="0" />

<xs:element name="ACE-enabled-indicator" type="xs:integer" minOccurs="0"/>

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="DiscReq-info">

<xs:sequence>

<xs:element name="transaction-ID" type="xs:integer"/>

<xs:element name="command" type="xs:integer"/>

<xs:element name="ProSe-Application-ID" type="xs:string"/>

<xs:element name="application-identity" type="AppID-info"/>

<xs:element name="discovery-entry-ID" type="xs:integer" minOccurs="0" />

<xs:element name="Requested-Timer" type="xs:integer" minOccurs="0" />

<xs:element name="metadata" type="xs:string" minOccurs="0"/>

<xs:element name="Announcing-PLMN-ID" type="PLMN-info" minOccurs="0" />

<xs:element name="ACE-enabled-indicator" type="xs:integer" minOccurs="0"/>

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="RestrictedDiscReq-info">

<xs:sequence>

<xs:element name="transaction-ID" type="xs:integer"/>

<xs:element name="command" type="xs:integer"/>

<xs:element name="RPAUID" type="xs:string"/>

<xs:element name="application-identity" type="AppID-info"/>

<xs:element name="discovery-type" type="xs:integer"/>

<xs:element name="PC5-UE-ciphering-algorithm-capability" type="xs:integer"/>

<xs:element name="ACE-enabled-indicator" type="xs:integer" minOccurs="0"/>

<xs:element name="announcing-type" type="xs:integer" minOccurs="0"/>

<xs:element name="application-level-container" type="xs:hexBinary" minOccurs="0"/>

<xs:element name="discovery-model" type="xs:integer" minOccurs="0"/>

<xs:element name="Announcing-PLMN-ID" type="PLMN-info" minOccurs="0" />

<xs:element name="discovery-entry-ID" type="xs:integer"/>

<xs:element name="Requested-Timer" type="xs:integer" minOccurs="0" />

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="RestrictedAnnounceRsp-info">

<xs:sequence>

<xs:element name="transaction-ID" type="xs:integer"/>

<xs:element name="ProSe-Restricted-Code" type="xs:hexBinary" minOccurs="0"/>

<xs:element name="ProSe-Restricted-Code-Suffix-Range" type="RestrictedCodeSuffixRange-info" minOccurs="0"/>

<xs:element name="validity-timer-T5062" type="xs:integer" minOccurs="0"/>

<xs:element name="ACE-enabled-indicator" type="xs:integer" minOccurs="0" />

<xs:element name="code-sending-security-parameter" type="Restricted-Security-info" />

<xs:element name="selected-PC5-ciphering-algorithm" type="xs:integer"/>

<xs:element name="on-demand-announcing-enabled-indicator" type="xs:boolean" minOccurs="0" />

<xs:element name="discovery-entry-ID" type="xs:integer"/>

<xs:element name="PC5-security-policies" type="xs:PC5-Security-Policies-info" minOccurs="0" />

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="RestrictedMonitorRsp-info">

<xs:sequence>

<xs:element name="transaction-ID" type="xs:integer"/>

<xs:element name="restricted-discovery-filter" type="RestrictedDiscFilter-info" minOccurs="0" maxOccurs="unbounded"/>

<xs:element name="ACE-enabled-indicator" type="xs:integer" minOccurs="0" />

<xs:element name="application-level-container" type="xs:hexBinary"/>

<xs:element name="code-receiving-security-parameter" type="Restricted-Security-info" minOccurs="0" />

<xs:element name="selected-PC5-ciphering-algorithm" type="xs:integer"/>

<xs:element name="discovery-entry-ID" type="xs:integer"/>

<xs:element name="PC5-security-policies" type="xs:PC5-Security-Policies-info" minOccurs="0" />

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="RestrictedDiscovereeRsp-info">

<xs:sequence>

<xs:element name="transaction-ID" type="xs:integer"/>

<xs:element name="ProSe-Response-Code" type="xs:hexBinary" />

<xs:element name="query-filter" type="MatchingFilter-info" maxOccurs="unbounded"/>

<xs:element name="validity-timer-T5068" type="xs:integer"/>

<xs:element name="code-sending-security-parameter" type="Restricted-Security-info" />

<xs:element name="code-receiving-security-parameter" type="Restricted-Security-info" minOccurs="0" />

<xs:element name="selected-PC5-ciphering-algorithm" type="xs:integer"/>

<xs:element name="discovery-entry-ID" type="xs:integer"/>

<xs:element name="PC5-security-policies" type="xs:PC5-Security-Policies-info" minOccurs="0" />

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="RestrictedDiscovererRsp-info">

<xs:sequence>

<xs:element name="transaction-ID" type="xs:integer"/>

<xs:element name="subquery-result" type="Subquery-info" minOccurs="1" maxOccurs="unbounded"/>

<xs:element name="code-sending-security-parameter" type="Restricted-Security-info" />

<xs:element name="code-receiving-security-parameter" type="Restricted-Security-info" minOccurs="0" />

<xs:element name="selected-PC5-ciphering-algorithm" type="xs:integer"/>

<xs:element name="discovery-entry-ID" type="xs:integer"/>

<xs:element name="PC5-security-policies" type="xs:PC5-Security-Policies-info" minOccurs="0" />

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="RejectRsp-info">

<xs:sequence>

<xs:element name="transaction-ID" type="xs:integer"/>

<xs:element name="PC3a-control-protocol-cause-value" type="xs:integer"/>

<xs:any namespace="##any" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="UE-RejectRsp-info">

<xs:sequence>

<xs:element name="DDNMF-transaction-ID" type="xs:integer"/>

<xs:element name="PC3a-control-protocol-cause-value" type="xs:integer"/>

<xs:any namespace="##any" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="MatchRep-info">

<xs:sequence>

<xs:element name="transaction-ID" type="xs:integer"/>

<xs:element name="ProSe-PC5-discovery-message" type="xs:hexBinary"/>

<xs:element name="Monitored-PLMN-ID" type="PLMN-info"/>

<xs:element name="VPLMN-ID" type="PLMN-info" minOccurs="0"/>

<xs:element name="UTC-based-counter" type="xs:hexBinary"/>

<xs:element name="Metadata-flag" type="xs:boolean"/>

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="RestrictedMatch-info">

<xs:sequence>

<xs:element name="transaction-ID" type="xs:integer"/>

<xs:element name="discovery-type" type="xs:integer"/>

<xs:element name="application-identity" type="AppID-info"/>

<xs:element name="RPAUID" type="xs:string"/>

<xs:element name="Restricted-Code-Discovered" type="Restricted-Code-Option-info" minOccurs="0"/>

<xs:element name="ProSe-PC5-discovery-message" type="xs:hexBinary" minOccurs="0"/>

<xs:element name="UTC-based-counter" type="xs:hexBinary" minOccurs="0"/>

<xs:element name="Metadata-flag" type="xs:boolean" />

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="MatchAck-info">

<xs:sequence>

<xs:element name="transaction-ID" type="xs:integer"/>

<xs:element name="ProSe-Application-ID" type="xs:string"/>

<xs:element name="validity-timer-T5072" type="xs:integer"/>

<xs:element name="UTC-based-counter" type="xs:hexBinary"/>

<xs:element name="metadata" type="xs:string" minOccurs="0"/>

<xs:element name="metadata-index-mask" type="xs:hexBinary" minOccurs="0"/>

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:attribute name="match-report-refresh-timer-T5074" type="xs:integer"/>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="RestrictedMatchAck-info">

<xs:sequence>

<xs:element name="transaction-ID" type="xs:integer"/>

<xs:element name="application-identity" type="AppID-info"/>

<xs:element name="RPAUID" type="xs:string"/>

<xs:element name="validity-timer-T5076" type="xs:integer"/>

<xs:element name="UTC-based-counter" type="xs:hexBinary"/>

<xs:element name="metadata" type="xs:string" minOccurs="0"/>

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:attribute name="match-report-refresh-timer-T5077" type="xs:integer"/>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="MatchReject-info">

<xs:sequence>

<xs:element name="transaction-ID" type="xs:integer"/>

<xs:element name="PC3a-control-protocol-cause-value" type="xs:integer"/>

<xs:any namespace="##any" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="DiscUpdateReq-info">

<xs:sequence>

<xs:element name="DDNMF-transaction-ID" type="xs:integer"/>

<xs:element name="discovery-entry-ID" type="xs:integer"/>

<xs:element name="update-info" type="Update-Option-info" minOccurs="0"/>

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="DiscUpdateRsp-info">

<xs:sequence>

<xs:element name="DDNMF-transaction-ID" type="xs:integer"/>

<xs:element name="discovery-entry-ID" type="xs:integer"/>

<xs:any namespace="##any" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="AnnouncingAlertReq-info">

<xs:sequence>

<xs:element name="DDNMF-transaction-ID" type="xs:integer"/>

<xs:element name="RPAUID" type="xs:string"/>

<xs:element name="discovery-entry-ID" type="xs:integer"/>

<xs:element name="ProSe-Restricted-Code" type="xs:hexBinary"/>

<xs:element name="ProSe-Restricted-Code-Suffix-Range" type="RestrictedCodeSuffixRange-info" minOccurs="0" maxOccurs="unbounded"/>

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="AnnouncingAlertRsp-info">

<xs:sequence>

<xs:element name="DDNMF-transaction-ID" type="xs:integer"/>

<xs:any namespace="##any" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="PKMFAddrReq-info">

<xs:sequence>

<xs:element name="transaction-ID" type="xs:integer"/>

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="PKMFAddrRsp-info">

<xs:sequence>

<xs:element name="transaction-ID" type="xs:integer"/>

<xs:element name="PKMF-address" type="xs:string"/>

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<!– Complex types defined for Message-level –>

<xs:complexType name="prose-direct-discovery-request">

<xs:sequence>

<xs:element name="discovery-request" type="DiscReq-info" minOccurs="0" maxOccurs="unbounded"/>

<xs:element name="restricted-discovery-request" type="RestrictedDiscReq-info" minOccurs="0" maxOccurs="unbounded"/>

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:attribute name="network-initiated-transaction-method" type="xs:integer"/>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="prose-direct-discovery-response">

<xs:sequence>

<xs:element name="Current-Time" type="xs:dateTime"/>

<xs:element name="Max-Offset" type="xs:integer"/>

<xs:element name="response-announce" type="AnnounceRsp-info" minOccurs="0" maxOccurs="unbounded"/>

<xs:element name="response-monitor" type="MonitorRsp-info" minOccurs="0" maxOccurs="unbounded"/>

<xs:element name="restricted-announce-response" type="RestrictedAnnounceRsp-info" minOccurs="0" maxOccurs="unbounded"/>

<xs:element name="restricted-monitor-response" type="RestrictedMonitorRsp-info" minOccurs="0" maxOccurs="unbounded"/>

<xs:element name="restricted-discoveree-response" type="RestrictedDiscovereeRsp-info" minOccurs="0" maxOccurs="unbounded"/>

<xs:element name="restricted-discoverer-response" type="RestrictedDiscovererRsp-info" minOccurs="0" maxOccurs="unbounded"/>

<xs:element name="response-reject" type="RejectRsp-info" minOccurs="0" maxOccurs="unbounded"/>

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:attribute name="network-initiated-transaction-method" type="xs:integer"/>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="prose-direct-discovery-update-request">

<xs:sequence>

<xs:element name="discovery-update-request" type="DiscUpdateReq-info" maxOccurs="unbounded"/>

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="prose-direct-discovery-update-response">

<xs:sequence>

<xs:element name="response-update" type="DiscUpdateRsp-info" minOccurs="0" maxOccurs="unbounded"/>

<xs:element name="response-reject" type="UE-RejectRsp-info" minOccurs="0" maxOccurs="unbounded"/>

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="prose-direct-discovery-match-report">

<xs:sequence>

<xs:element name="match-report" type="MatchRep-info" minOccurs="0" maxOccurs="unbounded"/>

<xs:element name="restricted-match" type="RestrictedMatch-info" minOccurs="0" maxOccurs="unbounded"/>

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="prose-direct-discovery-match-report-ack">

<xs:sequence>

<xs:element name="Current-Time" type="xs:dateTime"/>

<xs:element name="match-ack" type="MatchAck-info" minOccurs="0" maxOccurs="unbounded"/>

<xs:element name="match-reject" type="MatchReject-info" minOccurs="0" maxOccurs="unbounded"/>

<xs:element name="restricted-match-ack" type="RestrictedMatchAck-info" minOccurs="0" maxOccurs="unbounded"/>

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="prose-direct-discovery-announcing-alert-request">

<xs:sequence>

<xs:element name="announcing-alert-request" type="AnnouncingAlertReq-info" maxOccurs="unbounded"/>

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="prose-direct-discovery-announcing-alert-response">

<xs:sequence>

<xs:element name="announcing-alert-response" type="AnnouncingAlertRsp-info" maxOccurs="unbounded"/>

<xs:element name="response-reject" type="UE-RejectRsp-info" minOccurs="0" maxOccurs="unbounded"/>

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="prose-5gpkmf-address-request">

<xs:sequence>

<xs:element name="PKMF-address-request" type="PKMFAddrReq-info" minOccurs="0" maxOccurs="unbounded"/>

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="prose-5gpkmf-address-response">

<xs:sequence>

<xs:element name="PKMF-address-response" type="PKMFAddrRsp-info" minOccurs="0" maxOccurs="unbounded"/>

<xs:element name="PKMF-address-reject" type="RejectRsp-info" minOccurs="0" maxOccurs="unbounded"/>

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<!– extension allowed –>

<xs:complexType name="DiscMsgExtType">

<xs:sequence>

<xs:any namespace="##any" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<!– XML attribute for any future extensions –>

<xs:complexType name="anyExtType">

<xs:sequence>

<xs:any namespace="##any" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

</xs:complexType>

<!– Top levelDiscovery Message definition –>

<xs:element name="prose-discovery-message">

<xs:complexType>

<xs:choice>

<xs:element name="DISCOVERY_REQUEST" type="prose-direct-discovery-request"/>

<xs:element name="DISCOVERY_RESPONSE" type="prose-direct-discovery-response"/>

<xs:element name="MATCH_REPORT" type="prose-direct-discovery-match-report"/>

<xs:element name="MATCH_REPORT_ACK" type="prose-direct-discovery-match-report-ack"/>

<xs:element name="DISCOVERY_UPDATE_REQUEST" type="prose-direct-discovery-update-request"/>

<xs:element name="DISCOVERY_UPDATE_RESPONSE" type="prose-direct-discovery-update-response"/>

<xs:element name="ANNOUNCING_ALERT_REQUEST" type="prose-direct-discovery-announcing-alert-request"/>

<xs:element name="ANNOUNCING_ALERT_RESPONSE" type="prose-direct-discovery-announcing-alert-response"/>

<xs:element name="PROSE_5GPKMF_ADDRESS_REQUEST" type="prose-5gpkmf-address-request"/>

<xs:element name="PROSE_5GPKMF_ADDRESS_RESPONSE" type="prose-5gpkmf-address-response"/>

<xs:element name="message-ext" type="DiscMsgExtType"/>

<xs:any namespace="##other" processContents="lax"/>

</xs:choice>

</xs:complexType>

</xs:element>

</xs:schema>

An entity receiving the XML body ignores any unknown XML element and any unknown XML attribute.

10.5.4 Semantics

10.5.4.1 General

The <prose-discovery-message> element is the root element of this XML document and it can be one of the following elements:

a) <DISCOVERY_REQUEST>;

b) <DISCOVERY_RESPONSE>;

c) <MATCH_REPORT>;

d) <MATCH_REPORT_ACK>;

e) <DISCOVERY_UPDATE_REQUEST>;

f) <DISCOVERY_UPDATE_RESPONSE>

g) <ANNOUNCE_ALERT_REQUEST>;

h) <ANNOUNCE_ALERT_RESPONSE>;

i) <PROSE_5GPKMF_ADDRESS_REQUEST>;

j) <PROSE_5GPKMF_ADDRESS_RESPONSE>;

k) <PROSE_SECURITY_MATERIAL_REQUEST>;

l) <PROSE_SECURITY_MATERIAL_RESPONSE>;

m) <message-ext> element containing other discovery message defined in future releases; or

n) an element from other namespaces defined in future releases.

10.5.4.2 Semantics of <DISCOVERY_REQUEST>

The <DISCOVERY_REQUEST> element contains one or more of the following elements:

a) zero, one or more <discovery-request> element which contains transactions sent from the UE to the 5G DDNMF as announcing or monitoring requests for open 5G ProSe direct discovery. Each <discovery-request> consists of:

1) a <transaction-ID> element containing the parameter defined in clause 11.4.2.1;

2) a <command> element containing the parameter defined in clause 11.4.2.2;

3) a <Prose-Application-ID> element containing the parameter defined in clause 11.4.2.4;

4) an <application-identity> element containing the parameter defined in clause 11.4.2.5;

5) a <Discovery-Entry-ID> element containing the parameter defined in clause 11.4.2.26;

6) an optional <Requested-Timer> element containing the parameter defined in clause 11.4.2.20;

7) an optional <metadata> element containing the parameter defined in clause 11.4.2.15;

8) an optional <Announcing-PLMN-ID> element containing the parameter defined in clause 11.4.2.43;

9) zero or one <ACE-enabled-indicator> element containing the parameter defined in clause 11.4.2.31;

10) zero or one <anyExt> element containing elements defined in future releases;

11) zero, one or more elements from other namespaces defined in future releases; and

12) zero, one or more attributes defined in future releases;

b) zero, one, or more <restricted-discovery-request> element which contains transactions sent from the UE to the 5G DDNMF as announcing or monitoring requests for restricted 5G ProSe directed discovery model A or transactions sent from the UE to the 5G DDNMF as discoveree or discoverer requests for restricted 5G ProSe directed discovery model B. Each <restricted-discovery-request> consists of:

1) a <transaction-ID> element containing the parameter defined in clause 11.4.2.1;

2) a <command> element containing the parameter defined in clause 11.4.2.2;

3) a <RPAUID> element containing the parameter defined in clause 11.4.2.23;

4) an <application-identity> element containing the parameter defined in clause 11.4.2.5;

5) a <discovery-type> element containing the parameter defined in clause 11.4.2.18;

6) zero or one <ACE-enabled-indicator> element containing the parameter defined in clause 11.4.2.31;

7) an <announcing-type> element containing the parameter defined in clause 11.4.2.24;

8) an <application-level-container> element containing the parameter defined in clause 11.4.2.25;

9) zero or one <discovery-model> element containing the parameter defined in clause 11.4.2.34;

10) zero or one <Announcing-PLMN-ID> element containing the parameter defined in clause 11.4.2.43;

11) a <discovery-entry-id> element containing the parameter defined in clause 11.4.2.26;

12) an optional <Requested-Timer> element containing the parameter defined in clause 11.4.2.20;

13) a <PC5-UE-ciphering-algorithm-capability> element containing the parameter defined in clause 11.4.2.50;

14) zero or one <anyExt> element containing elements defined in future releases;

15) zero, one or more elements from other namespaces defined in future releases; and

16) zero, one or more attributes defined in future releases;

c) zero or one <anyExt> element containing elements defined in future releases;

d) zero, one or more elements from other namespaces defined in future releases;

e) an optional "network-initiated transaction method" attribute containing the parameter defined in clause 11.4.2.42; and

f) zero, one or more attributes defined in future releases.

10.5.4.3 Semantics of <DISCOVERY_RESPONSE>

The <DISCOVERY_RESPONSE> element contains one or more of the following elements:

a) a <Current-Time> element containing the parameter defined in clause 11.4.2.16;

b) a <Max-Offset> element containing the parameter defined in clause 11.4.2.17;

c) zero, one or more <response-announce> element which contains transactions sent from the 5G DDNMF to the UE as a response to an announcing request if the 5G DDNMF accepts the request. Each <response-announce> consists of:

1) a <transaction-ID> element containing the parameter defined in clause 11.4.2.1;

2) zero, one or more <ProSe-Application-Code> elements containing the parameter defined in clause 11.4.2.6;

3) zero or one <ProSe application code-ACE> element containing the parameter defined in clause 11.4.2.45;

4) zero, or one <validity-timer-T5060> element containing the parameter defined in 11.4.2.7;

5) zero, or, one <discovery-key> element containing the parameter defined in clause 11.4.2.48;

6) a <discovery-entry-ID> element containing the parameter defined in clause 11.4.2.26;

7) zero or one <ACE-enabled-indicator> element containing the parameter defined in clause 11.4.2.31;

8) zero or one <anyExt> element containing elements defined in future releases;

9) zero, one or more elements from other namespaces defined in future releases; and

10) zero, one or more attributes defined in future releases;

d) zero, one or more <response-monitor> element which contains transactions sent from the 5G DDNMF to the UE as a response to a monitoring request if the 5G DDNMF accepts the request. Each <response-monitor> consists of:

1) a <transaction-ID> element containing the parameter defined in clause 11.4.2.1;

2) zero, one or more <discovery-filter> elements containing the parameter defined in clause 11.4.2.9;

3) a <discovery-entry-ID> element containing the parameter defined in clause 11.4.2.26;

4) zero or one <ACE-enabled-indicator> element containing the parameter defined in clause 11.4.2.31;

5) zero or one <anyExt> element containing elements defined in future releases;

6) zero, one or more elements from other namespaces defined in future releases; and

7) zero, one or more attributes defined in future releases;

e) zero, one or more <restricted-announce-response> element which contains transactions sent from the 5G DDNMF to the UE as a response to an announcing request for restricted 5G ProSe direct discovery model A if the 5G DDNMF accepts the request. Each <restricted-announce-response> consists of:

1) a <transaction-ID> element containing the parameter defined in clause 11.4.2.1;

2) zero or one <ProSe-Restricted-Code> element containing the parameter defined in clause 11.4.2.27;

3) zero, one or more <ProSe-Restricted-Code-Suffix-Range> element containing the parameter defined in clause 11.4.2.28;

4) zero or one <validity-timer-T5062> element containing the parameter defined in 11.4.2.32;

5) zero or one <ACE-enabled-indicator> element containing the parameter defined in clause 11.4.2.31;

6) a <code-sending-security-parameter> element containing the parameter defined in clause 11.4.2.33;

7) zero or one <on-demand-announcing-enabled-indicator> element containing the parameter defined in clause 11.4.2.29;

8) a <discovery-entry-id> element containing the parameter defined in clause 11.4.2.26;

9) a <selected-PC5-ciphering-algorithm> element containing the parameter defined in clause 11.4.2.51;

10) zero or one <PC5-security-policies> element containing the parameter defined in clause 11.4.2.49;

11) zero or one <anyExt> element containing elements defined in future releases;

12) zero, one or more elements from other namespaces defined in future releases; and

13) zero, one or more attributes defined in future releases;

f) zero, one or more <restricted-monitor-response> element which contains transactions sent from the 5G DDNMF to the UE as a response to a monitoring request for restricted 5G ProSe direct discovery model A if the 5G DDNMF accepts the request. Each <restricted-monitor-response> consists of:

1) a <transaction-ID> element containing the parameter defined in clause 11.4.2.1;

2) one or more <restricted-discovery-filter> elements containing the parameter defined in clause 11.4.2.30;

3) zero or one <ACE-enabled-indicator> element containing the parameter defined in clause 11.4.2.31

4) a <discovery-entry-id> element containing the parameter defined in clause 11.4.2.26;

5) an <application-level-container> element containing the parameter defined in clause 11.4.2.25;

6) one or more <code-receiving-security-parameter> element containing the parameter defined in clause 11.4.2.33;

7) a <selected-PC5-ciphering-algorithm> element containing the parameter defined in clause 11.4.2.51;

8) zero or one <PC5-security-policies> element containing the parameter defined in clause 11.4.2.49;

9) zero or one <anyExt> element containing elements defined in future releases;

10) zero, one or more elements from other namespaces defined in future releases; and

11) zero, one or more attributes defined in future releases;

g) zero, one or more <restricted-discoveree-response> element which contains transactions sent from the 5G DDNMF to the UE as a response to a discoveree UE’s request for restricted 5G ProSe direct discovery model B if the 5G DDNMF accepts the request. Each <restricted-discoveree-response> consists of:

1) a <transaction-ID> element containing the parameter defined in clause 11.4.2.1;

2) a <ProSe-Response-Code> element containing the element defined in clause11.4.2.35;

3) one or more <query-filter> elements containing the parameter defined in clause 11.4.2.36;

4) a <validity-timer-T5068> element containing the parameter defined in clause 11.4.2.37;

5) a <code-sending-security-parameter > element containing the parameter defined in clause 11.4.2.33;

6) one or more <code-receiving-security-parameter> element containing the parameter defined in clause 11.4.2.33;

7) a <discovery-entry-id> element containing the parameter defined in clause 11.4.2.26;

8) zero or one <PC5-security-policies> element containing the parameter defined in clause 11.4.2.49;

9) a <selected-PC5-ciphering-algorithm> element containing the parameter defined in clause 11.4.2.51;

10) zero or one <anyExt> element containing elements defined in future releases;

11) zero, one or more elements from other namespaces defined in future releases; and

12) zero, one or more attributes defined in future releases;

h) zero, one or more <restricted-discoverer-response> element which contains transactions sent from the 5G DDNMF to the UE as a response to a discoverer UE’s request for restricted 5G ProSe direct discovery model B if the 5G DDNMF accepts the request. Each <restricted-discoverer-response> consists of:

1) a <transaction-ID> element containing the parameter defined in clause 11.4.2.1;

2) one or more <subquery-result> elements containing the parameter defined in clause 11.4.2.38;

3) a <code-sending-security-parameter> element containing the parameter defined in clause 11.4.2.33;

4) one or more <code-receiving-security-parameter> element containing the parameter defined in clause 11.4.2.33;

5) a <discovery-entry-id> element containing the parameter defined in clause 11.4.2.26;

6) zero or one <PC5-security-policies> element containing the parameter defined in clause 11.4.2.49;

7) a <selected-PC5-ciphering-algorithm> element containing the parameter defined in clause 11.4.2.51;

8) zero or one <anyExt> element containing elements defined in future releases;

9) zero, one or more elements from other namespaces defined in future releases; and

10) zero, one or more attributes defined in future releases;

i) zero, one or more <response-reject> element which contains transactions sent from the 5G DDNMF to the UE as a response to an announcing or monitoring requests if the 5G DDNMF cannot accept the request. Each <response-reject> consists of:

1) a <transaction-ID> element containing the parameter defined in clause 11.4.2.1;

2) a <PC3a-control-protocol-cause-value> element containing the parameter defined in clause 11.4.2.8.

3) zero, one or more elements defined in future releases; and

4) zero, one or more attributes defined in future releases;

j) zero or one <anyExt> element containing elements defined in future releases;

k) zero, one or more elements from other namespaces defined in future releases;

l) an optional "network-initiated transaction method" attribute containing the parameter defined in clause 11.4.2.42; and

m) zero, one or more attributes defined in future releases.

10.5.4.4 Semantics of <MATCH_REPORT>

The <MATCH_REPORT> element contains one or more of the following elements:

a) zero, one or more <match-report> element which contains transactions sent from the UE to the 5G DDNMF to report a matching of the direct discovery. Each <match-report> consists of:

1) a <transaction-ID> element containing the parameter defined in clause 11.4.2.1;

2) a <ProSe-PC5-discovery-message> element containing the parameter defined in clause 11.4.2.52;

3) a <Monitored-PLMN-id> element containing the parameter defined in clause 11.4.2.10;

4) an optional <VPLMN-id> element containing the parameter defined in clause 11.4.2.11;

5) a <UTC-based-counter> element containing the parameter defined in clause 11.4.2.12;

6) a <metadata-flag> element containing the parameter defined in clause 11.4.2.14;

7) zero or one <anyExt> element containing elements defined in future releases;

8) zero, one or more elements from other namespaces defined in future releases; and

9) zero, one or more attributes defined in future releases;

b) zero, one or more <restricted-match> element which contain transactions sent from the UE to the 5G DDNMF to report a matching of the restricted direct discovery model A or model B. Each <restricted-match> consists of:

1) a <transaction-ID> element containing the parameter defined in clause 11.4.2.1;

2) a <discovery-type> element containing the parameter defined in clause 11.4.2.18

3) an <application-identity> element containing the parameter defined in clause 11.4.2.5

4) an <RPAUID> element containing the parameter defined in clause 11.4.2.23;

5) zero or one <ProSe-PC5-discovery-message> element containing the parameter defined in clause 11.4.2.52, if it is required to check the MIC via the match report procedure;

6) zero or one <Restricted-Code-Discovered> element containing the ProSe Restricted Code parameter defined in clause 11.4.2.27 or ProSe Response Code parameter defined in clause 11.4.2.35, if it is not required to check the MIC via the match report procedure;

7) a <UTC-based-counter> element containing the parameter defined in clause 11.4.2.12, if it is required to check the MIC via the match report procedure;

8) a <metadata-flag> element containing the parameter defined in clause 11.4.2.14;

9) zero or one <anyExt> element containing elements defined in future releases;

10) zero, one or more elements from other namespaces defined in future releases; and

11) zero, one or more attributes defined in future releases.

c) zero or one <anyExt> element containing elements defined in future releases;

d) zero, one or more elements from other namespaces defined in future releases; and

e) zero, one or more attributes defined in future releases.

10.5.4.5 Semantics of <MATCH_REPORT_ACK>

The <MATCH_REPORT_ACK> element contains one or more of the following elements:

a) a <Current-Time> element containing the parameter defined in clause 11.4.2.16;

b) zero, one or more <match-ack> element which contains transactions sent from the 5G DDNMF to the UE as a response to a match report if the 5G DDNMF accepts the report. Each <match-ack> consists of:

1) a <transaction-ID> element containing the parameter defined in clause 11.4.2.1;

2) a <ProSe-Application-ID> element containing the parameter defined in clause 11.4.2.4;

3) a <validity-timer-T5072> element containing the parameter defined in clause 11.4.2.13;

4) an optional <metadata> element containing the parameter defined in clause 11.4.2.15;

5) an optional <metadata-index-mask> element containing the parameter defined in clause 11.4.2.41;

6) a mandatory "match-report-refresh-timer-T5074" attribute containing the parameter defined in clause 11.4.2.19;

7) zero or one <anyExt> element containing elements defined in future releases;

8) zero, one or more elements from other namespaces defined in future releases; and

9) zero, one or more attributes defined in future releases;

c) zero, one or more <restricted-match-ack> element which contain transactions sent from the 5G DDNMF to the UE as a response to a match report if the 5G DDNMF accepts the report. Each <restricted-match-ack> consists of:

1) a <transaction-ID> element containing the parameter defined in clause 11.4.2.1;

2) an <application-identity> element containing the parameter defined in clause 11.4.2.5;

3) an <RPAUID> element containing the parameter defined in clause 11.4.2.23;

4) a <validity-timer-T5076> element containing the parameter defined in clause 11.4.2.39;

5) an optional <metadata> element containing the parameter defined in clause 11.4.2.15;

6) zero or one <anyExt> element containing elements defined in future releases;

7) zero, one or more elements from other namespaces defined in future releases;

8) an optional "match-report-refresh-timer-T5077" attribute containing the parameter defined in clause 11.4.2.40; and

9) zero, one or more attributes defined in future releases;

d) zero, one or more <match-reject> element which contains transactions sent from the 5G DDNMF to the UE as a response to a match report if the 5G DDNMF cannot accept the match report. Each <match-reject> consists of:

1) a <transaction-ID> element containing the parameter defined in clause 11.4.2.1;

2) a <PC3a-control-protocol-cause-value> element containing the parameter defined in clause 11.4.2.8;

3) zero, one or more elements defined in future releases; and

4) zero, one or more attributes defined in future releases;

e) zero or one <anyExt> element containing elements defined in future releases;

f) zero, one or more elements from other namespaces defined in future releases; and

g) zero, one or more attributes defined in future releases.

10.5.4.6 Semantics of < DISCOVERY_UPDATE_REQUEST>

The < DISCOVERY_UPDATE_REQUEST> element contains one or more of the following elements:

a) One or more <discovery-update-request> element which contains transactions sent from the 5G DDNMF to the UE as announcing or monitoring requests. Each <discovery-update-request> consists of:

1) a <DDNMF-transaction-ID> element containing the parameter defined in clause 11.4.2.21;

2) a <discovery-entry-id> element containing the parameter defined in clause 11.4.2.26;

3) an optional <update-info> element containing the parameter defined in clause 11.4.2.22;

4) zero or one <anyExt> element containing elements defined in future releases;

5) zero, one or more elements defined in future releases; and

6) zero, one or more attributes defined in future releases;

b) zero or one <anyExt> element containing elements defined in future releases;

c) zero, one or more elements from other namespaces defined in future releases; and

d) zero, one or more attributes defined in future releases.

10.5.4.7 Semantics of < DISCOVERY_UPDATE_RESPONSE>

The < DISCOVERY_UPDATE _RESPONSE> element contains one or more of the following elements:

a) one or more <response-update> element which contains transactions sent from the UE to the 5G DDNMF as a response if the UE accepts the request. Each <discovery-update-response> consists of:

1) a <DDNMF-transaction-ID> element containing the parameter defined in clause 11.4.2.21;

2) a <discovery-entry-id> element containing the parameter defined in clause 11.4.2.26;

3) zero, one or more elements defined in future releases; and

4) zero, one or more attributes defined in future releases;

b) zero, one or more <response-reject> element which contains transactions sent from the UE to the 5G DDNMF as a response if the UE cannot accept the request. Each <response-reject> consists of:

1) a <DDNMF-transaction-ID> element containing the parameter defined in clause 11.4.2.21;

2) a <PC3a-control-protocol-cause-value> element containing the parameter defined in clause 11.4.2.8.

3) zero, one or more elements defined in future releases; and

4) zero, one or more attributes defined in future releases;

c) zero or one <anyExt> element containing elements defined in future releases;

d) zero, one or more elements from other namespaces defined in future releases; and

e) zero, one or more attributes defined in future releases.

10.5.4.8 Semantics of <ANNOUNCING_ALERT_REQUEST>

The <ANNOUNCING_ALERT_REQUEST> element contains one or more of the following elements:

a) One or more <announcing-alert-request> element which contains transactions sent from the UE to the 5G DDNMF as announcing or monitoring requests. Each <announcing-alert-request> consists of:

1) a <DDNMF-transaction-ID> element containing the parameter defined in clause 11.4.2.21;

2) a <RPAUID> element containing the parameter defined in clause 11.4.2.23;

3) a <Discovery-Entry-ID> element containing the parameter defined in clause 11.4.2.26;

4) a <ProSe-Restricted-Code> element containing the parameter defined in clause 11.4.2.27;

5) zero, one or more <ProSe-Restricted-Code-Suffix-Range> element containing the parameter defined in clause 11.4.2.28;

6) zero or one <anyExt> element containing elements defined in future releases;

7) zero, one or more elements from other namespaces defined in future releases; and

8) zero, one or more attributes defined in future releases;

b) zero or one <anyExt> element containing elements defined in future releases;

c) zero, one or more elements from other namespaces defined in future releases; and

d) zero, one or more attributes defined in future releases.

10.5.4.9 Semantics of < ANNOUNCING_ALERT_RESPONSE >

The <ANNOUNCING_ALERT_RESPONSE> element contains one or more of the following elements:

a) One or more <announcing-alert-response> element which contains transactions sent from the UE to the 5G DDNMF as announcing or monitoring requests. Each <announcing-alert-response> consists of:

1) a <DDNMF-transaction-ID> element containing the parameter defined in clause 11.4.2.21;

2) zero, one or more elements defined in future releases; and

3) zero, one or more attributes defined in future releases;

b) zero, one or more <response-reject> element which contains transactions sent from the UE to the 5G DDNMF as a response if the UE cannot accept the request. Each <response-reject> consists of:

1) a <DDNMF-transaction-ID> element containing the parameter defined in clause 11.4.2.21;

2) a <PC3a-control-protocol-cause-value> element containing the parameter defined in clause 11.4.2.8.

3) zero, one or more elements defined in future releases; and

4) zero, one or more attributes defined in future releases;

c) zero or one <anyExt> element containing elements defined in future releases;

d) zero, one or more elements from other namespaces defined in future releases; and

e) zero, one or more attributes defined in future releases.

10.5.4.10 Semantics of <PROSE_5GPKMF_ADDRESS_REQUEST>

The <PROSE_5GPKMF_ADDRESS_REQUEST> element contains one or more of the following elements:

a) zero, one or more <PKMF-address-request> element which contains transactions sent from the UE to the 5G DDNMF. Each <PKMF-address-request> consists of:

1) a <transaction-ID> element containing the parameter defined in clause 11.4.2.1;

2) zero or one <anyExt> element containing elements defined in future releases;

3) zero, one or more elements from other namespaces defined in future releases; and

4) zero, one or more attributes defined in future releases;

b) zero or one <anyExt> element containing elements defined in future releases;

c) zero, one or more elements from other namespaces defined in future releases; and

d) zero, one or more attributes defined in future releases.

10.5.4.11 Semantics of <PROSE_5GPKMF_ADDRESS_RESPONSE>

The <PROSE_5GPKMF_ADDRESS_RESPONSE> element contains one or more of the following elements:

a) zero, one or more <PKMF-address-response> element which contains transactions sent from the 5G DDNMF to the UE. Each < PKMF-address-response> consists of:

1) a <transaction-ID> element containing the parameter defined in clause 11.4.2.1;

2) a <PKMF-address> element containing the parameter defined in clause 11.4.2.53;

3) zero or one <anyExt> element containing elements defined in future releases;

4) zero, one or more elements from other namespaces defined in future releases; and

5) zero, one or more attributes defined in future releases;

b) zero, one or more <PKMF-address-reject> element which contains transactions sent from the 5G DDNMF to the UE as a response if the 5G DDNMF cannot accept the request. Each <PKMF-address-reject> consists of:

1) a <transaction-ID> element containing the parameter defined in clause 11.4.2.1;

2) a <PC3a-control-protocol-cause-value> element containing the parameter defined in clause 11.4.2.8.

3) zero, one or more elements defined in future releases; and

4) zero, one or more attributes defined in future releases;

c) zero or one <anyExt> element containing elements defined in future releases;

d) zero, one or more elements from other namespaces defined in future releases; and

e) zero, one or more attributes defined in future releases.

10.5.4.12 Semantics of <PROSE_SECURITY_MATERIAL_REQUEST>

The semantics of <PROSE_SECURITY_MATERIAL_REQUEST> is same as the semantics of <PROSE_SECURITY_PARAM_REQUEST> defined in clause 10.6.4.2, where 5G PKMF is replaced by 5G DDNMF.

10.5.4.13 Semantics of <PROSE_SECURITY_MATERIAL_RESPONSE>

The semantics of <PROSE_SECURITY_MATERIAL_RESPONSE> is same as the semantics of <PROSE_SECURITY_PARAM_RESPONSE> defined in clause 10.6.4.3, where 5G PKMF is replaced by 5G DDNMF.

10.6 5G ProSe security messages over PC8

10.6.1 General

This clause defines the XML schema and MIME type related to 5G ProSe security messages.

10.6.2 application/vnd.3gpp-prose-pc8+xml

The MIME type is used to carry information related to the 5G ProSe security operation. It shall be coded as an XML document containing one of the following 5G ProSe security messages:

a) a PROSE_SECURITY_PARAM_REQUEST message;

b) a PROSE_SECURITY_PARAM_RESPONSE message;

c) a PROSE_PRUK_REQUEST message;

d) a PROSE_PRUK_RESPONSE message;

e) a PROSE_KEY_REQUEST message; or

f) a PROSE_KEY_RESPONSE message.

Each of those messages is presented in the XML document as an XML element named after the corresponding message.

10.6.3 XML schema

Implementations in compliance with the present document shall implement the XML schema defined below for messages used in 5G ProSe security procedures over PC8 interface.

<?xml version="1.0" encoding="UTF-8"?>

<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"

xmlns="urn:3GPP:ns:5GProSe:Security:2022"

elementFormDefault="qualified"

targetNamespace="urn:3GPP:ns:5GProSe:Security:2022">

<xs:annotation>

<xs:documentation>

Info for 5G ProSe Security Control Messages Syntax

</xs:documentation>

</xs:annotation>

<xs:complexType name="empty-type"/>

<xs:complexType name="requested-for-type">

<xs:sequence>

<xs:element name="remote-UE" type="empty-type" minOccurs="0"/>

<xs:element name="UNR" type="empty-type" minOccurs="0"/>

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="PLMN-type">

<xs:sequence>

<xs:element name="mcc" type="xs:integer"/>

<xs:element name="mnc" type="xs:integer"/>

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="PLMN-list-type">

<xs:sequence>

<xs:element name="PLMN" type="PLMN-type" maxOccurs="unbounded"/>

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="model-type">

<xs:sequence>

<xs:element name="model-A" type="empty-type" minOccurs="0"/>

<xs:element name="model-B" type="empty-type" minOccurs="0"/>

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="DUCK-type">

<xs:sequence>

<xs:element name="discovery-user-confidentiality-key" type="xs:hexBinary"/>

<xs:element name="encrypted-bitmask" type="xs:hexBinary"/>

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="code-sending-or-receiving-security-parameters-type">

<xs:sequence>

<xs:element name="DUSK" type="xs:hexBinary" minOccurs="0" />

<xs:element name="DUIK" type="xs:hexBinary" minOccurs="0" />

<xs:element name="DUCK" type="DUCK-type" minOccurs="0" />

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="security-parameters-per-relay-service-code-for-remote-UE-type">

<xs:sequence>

<xs:element name="relay-service-code" type="xs:integer"/>

<xs:element name="code-receiving-security-parameters-for-model-A" type="code-sending-or-receiving-security-parameters-type" minOccurs="0"/>

<xs:element name="code-receiving-security-parameters-for-model-B" type="code-sending-or-receiving-security-parameters-type" minOccurs="0"/>

<xs:element name="code-sending-security-parameters-for-model-B" type="code-sending-or-receiving-security-parameters-type" minOccurs="0"/>

<xs:element name="selected-PC5-ciphering-algorithm" type="xs:integer"/>

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="security-parameters-per-relay-service-code-for-UNR-type">

<xs:sequence>

<xs:element name="relay-service-code" type="xs:integer"/>

<xs:element name="code-sending-security-parameters-for-model-A" type="code-sending-or-receiving-security-parameters-type" minOccurs="0"/>

<xs:element name="code-receiving-security-parameters-for-model-B" type="code-sending-or-receiving-security-parameters-type" minOccurs="0"/>

<xs:element name="code-sending-security-parameters-for-model-B" type="code-sending-or-receiving-security-parameters-type" minOccurs="0"/>

<xs:element name="selected-PC5-ciphering-algorithm" type="xs:integer"/>

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="list-of-security-parameters-per-relay-service-code-for-remote-UE-type">

<xs:sequence>

<xs:element name="security-parameters-per-relay-service-code" type="security-parameters-per-relay-service-code-for-remote-UE-type" maxOccurs="unbounded"/>

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="list-of-security-parameters-per-relay-service-code-for-UNR-type">

<xs:sequence>

<xs:element name="security-parameters-per-relay-service-code" type="security-parameters-per-relay-service-code-for-UNR-type" maxOccurs="unbounded"/>

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="security-parameters-for-remote-UE-type">

<xs:sequence>

<xs:element name="expiration-timer" type="xs:integer"/>

<xs:element name="list-of-security-parameters-per-relay-service-code" type="list-of-security-parameters-per-relay-service-code-for-remote-UE-type"/>

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="security-parameters-for-UNR-type">

<xs:sequence>

<xs:element name="expiration-timer" type="xs:integer"/>

<xs:element name="list-of-security-parameters-per-relay-service-code" type="list-of-security-parameters-per-relay-service-code-for-UNR-type"/>

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="PC5-security-policies-type">

<xs:sequence>

<xs:element name="signalling-ciphering-policy" type="xs:integer"/>

<xs:element name="user-plane-integrity-protection-policy" type="xs:integer"/>

<xs:element name="user-plane-ciphering-policy" type="xs:integer"/>

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="PC5-security-policies-per-relay-service-code-type">

<xs:sequence>

<xs:element name="relay-service-code" type="xs:integer"/>

<xs:element name="PC5-security-policies" type="PC5-security-policies-type"/>

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="list-of-PC5-security-policies-per-relay-service-code-type">

<xs:sequence>

<xs:element name="PC5-security-policies-per-relay-service-code" type="PC5-security-policies-per-relay-service-code-type" maxOccurs="unbounded"/>

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<!– Complex types defined for transaction-level –>

<xs:complexType name="UNR-discovery-security-parameters-request-type">

<xs:sequence>

<xs:element name="transaction-ID" type="xs:integer"/>

<xs:element name="requested-for" type="requested-for-type"/>

<xs:element name="PC5-UE-security-capabilities" type="xs:integer"/>

<xs:element name="VPLMN-list" type="PLMN-list-type" minOccurs="0"/>

<xs:element name="model" type="model-type" minOccurs="0"/>

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="UNR-discovery-security-parameters-accept-type">

<xs:sequence>

<xs:element name="transaction-ID" type="xs:integer"/>

<xs:element name="security-parameters-for-remote-UE" type="security-parameters-for-remote-UE-type" minOccurs="0"/>

<xs:element name="list-of-PC5-security-policies-per-relay-service-code-for-remote-UE" type="list-of-PC5-security-policies-per-relay-service-code-type" minOccurs="0"/>

<xs:element name="security-parameters-for-UNR" type="security-parameters-for-UNR-type" minOccurs="0"/>

<xs:element name="list-of-PC5-security-policies-per-relay-service-code-for-UNR" type="list-of-PC5-security-policies-per-relay-service-code-type" minOccurs="0"/>

<xs:element name="Current-Time" type="xs:dateTime"/>

<xs:element name="Max-Offset" type="xs:integer"/>

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="PRUK-request-type">

<xs:sequence>

<xs:element name="transaction-ID" type="xs:integer"/>

<xs:element name="UP-PRUK-ID" type="xs:string" minOccurs="0" />

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="PRUK-accept-type">

<xs:sequence>

<xs:element name="transaction-ID" type="xs:integer"/>

<xs:element name="UP-PRUK-ID" type="xs:string"/>

<xs:element name="UP-PRUK" type="xs:hexBinary"/>

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="key-request-type">

<xs:sequence>

<xs:element name="transaction-ID" type="xs:integer"/>

<xs:element name="relay-service-code" type="xs:integer"/>

<xs:element name="SUCI" type="xs:string" minOccurs="0"/>

<xs:element name="UP-PRUK-ID" type="xs:string" minOccurs="0"/>

<xs:element name="Knrp-freshness-parameter-1" type="xs:hexBinary"/>

<xs:element name="HPLMN" type="PLMN-type" minOccurs="0"/>

<xs:element name="AUTS" type="xs:hexBinary" minOccurs="0"/>

<xs:element name="RAND" type="xs:hexBinary" minOccurs="0"/>

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="key-accept-type">

<xs:sequence>

<xs:element name="transaction-ID" type="xs:integer"/>

<xs:element name="UP-PRUK-ID" type="xs:string"/>

<xs:element name="Knrp" type="xs:hexBinary"/>

<xs:element name="Knrp-freshness-parameter-2" type="xs:hexBinary"/>

<xs:element name="GPI" type="xs:hexBinary" minOccurs="0"/>

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="reject-type">

<xs:sequence>

<xs:element name="transaction-ID" type="xs:integer"/>

<xs:element name="PC8-control-protocol-cause-value" type="xs:integer"/>

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<!– Complex types defined for Message-level –>

<xs:complexType name="PROSE_SECURITY_PARAM_REQUEST-type">

<xs:sequence>

<xs:element name="UNR-discovery-security-parameters-request" type="UNR-discovery-security-parameters-request-type" minOccurs="0" maxOccurs="unbounded"/>

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="PROSE_SECURITY_PARAM_RESPONSE-type">

<xs:sequence>

<xs:element name="UNR-discovery-security-parameters-accept" type="UNR-discovery-security-parameters-accept-type" minOccurs="0" maxOccurs="unbounded"/>

<xs:element name="UNR-discovery-security-parameters-reject" type="reject-type" minOccurs="0" maxOccurs="unbounded"/>

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="PROSE_PRUK_REQUEST-type">

<xs:sequence>

<xs:element name="PRUK-request" type="PRUK-request-type" minOccurs="0" maxOccurs="unbounded"/>

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="PROSE_PRUK_RESPONSE-type">

<xs:sequence>

<xs:element name="PRUK-accept" type="PRUK-accept-type" minOccurs="0" maxOccurs="unbounded"/>

<xs:element name="PRUK-reject" type="reject-type" minOccurs="0" maxOccurs="unbounded"/>

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="PROSE_KEY_REQUEST-type">

<xs:sequence>

<xs:element name="key-request" type="key-request-type" minOccurs="0" maxOccurs="unbounded"/>

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="PROSE_KEY_RESPONSE-type">

<xs:sequence>

<xs:element name="key-accept" type="key-accept-type" minOccurs="0" maxOccurs="unbounded"/>

<xs:element name="key-reject" type="reject-type" minOccurs="0" maxOccurs="unbounded"/>

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<!– extension allowed –>

<xs:complexType name="DiscMsgExtType">

<xs:sequence>

<xs:any namespace="##any" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<!– XML attribute for any future extensions –>

<xs:complexType name="anyExtType">

<xs:sequence>

<xs:any namespace="##any" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

</xs:complexType>

<!– Top level Security Message definition –>

<xs:element name="prose-security-message">

<xs:complexType>

<xs:choice>

<xs:element name="PROSE_SECURITY_PARAM_REQUEST" type="PROSE_SECURITY_PARAM_REQUEST-type"/>

<xs:element name="PROSE_SECURITY_PARAM_RESPONSE" type="PROSE_SECURITY_PARAM_RESPONSE-type"/>

<xs:element name="PROSE_PRUK_REQUEST" type="PROSE_PRUK_REQUEST-type"/>

<xs:element name="PROSE_PRUK_RESPONSE" type="PROSE_PRUK_RESPONSE-type"/>

<xs:element name="PROSE_KEY_REQUEST" type="PROSE_KEY_REQUEST-type"/>

<xs:element name="PROSE_KEY_RESPONSE" type="PROSE_KEY_RESPONSE-type"/>

<xs:element name="message-ext" type="DiscMsgExtType"/>

<xs:any namespace="##other" processContents="lax"/>

</xs:choice>

</xs:complexType>

</xs:element>

</xs:schema>

An entity receiving the XML body ignores any unknown XML element and any unknown XML attribute.

10.6.4 Semantics

10.6.4.1 General

The <prose-security-message> element is the root element of this XML document and it contains one of the following elements:

a) a <PROSE_SECURITY_PARAM_REQUEST> element;

b) a <PROSE_SECURITY_PARAM_RESPONSE> element;

c) a <PROSE_PRUK_REQUEST> element;

d) a <PROSE_PRUK_RESPONSE> element;

e) a <PROSE_KEY_REQUEST> element;

f) a <PROSE_KEY_RESPONSE> element;

g) <message-ext> element containing other discovery message defined in future releases; or

h) an element from other namespaces defined in future releases.

10.6.4.2 Semantics of <PROSE_SECURITY_PARAM_REQUEST> element

The <PROSE_SECURITY_PARAM_REQUEST> element contains:

a) zero or more <UNR-discovery-security-parameters-request> elements which contain transactions sent from the UE to the 5G PKMF;

b) zero or one <anyExt> element containing elements defined in future releases;

c) zero or more elements from other namespaces defined in future releases; and

d) zero or more attributes defined in future releases.

The <UNR-discovery-security-parameters-request> contains:

a) a <transaction-ID> element containing the parameter defined in clause 11.6.2.1;

b) a <requested-for> element;

c) a <PC5-UE-security-capabilities> element containing the parameter defined in clause 11.6.2.4;

d) zero or one <VPLMN-list> element;

e) zero or one <model> element;

f) zero or one <anyExt> element containing elements defined in future releases;

g) zero or more elements from other namespaces defined in future releases; and

h) zero or more attributes defined in future releases.

The <requested-for> element contains:

a) the following:

1) a <remote-UE> element indicating that the 5G ProSe UE-to-network relay discovery security parameters for 5G ProSe remote UE are requested;

2) a <UNR> element indicating that the 5G ProSe UE-to-network relay discovery security parameters for 5G ProSe UE-to-network relay UE are requested; or

3) both;

b) zero or one <anyExt> element containing elements defined in future releases;

c) zero or more elements from other namespaces defined in future releases; and

d) zero or more attributes defined in future releases.

The <VPLMN-list> element contains:

a) one or more <PLMN> elements;

b) zero or one <anyExt> element containing elements defined in future releases;

c) zero or more elements from other namespaces defined in future releases; and

d) zero or more attributes defined in future releases.

The <PLMN> element contains:

a) an <mcc> elements containing the parameter defined in clause 11.6.2.5;

b) an <mnc> elements containing the parameter defined in clause 11.6.2.6;

c) zero or one <anyExt> element containing elements defined in future releases;

d) zero or more elements from other namespaces defined in future releases; and

e) zero or more attributes defined in future releases.

The <model> element contains:

a) a <model-A> elements indicating that security parameters are requested for 5G ProSe UE-to-network relay discovery over PC5 interface model A or an <model-B> elements indicating that security parameters are requested for 5G ProSe UE-to-network relay discovery over PC5 interface model B;

b) zero or one <anyExt> element containing elements defined in future releases;

c) zero or more elements from other namespaces defined in future releases; and

d) zero or more attributes defined in future releases.

10.6.4.3 Semantics of <PROSE_SECURITY_PARAM_RESPONSE> element

The <PROSE_SECURITY_PARAM_RESPONSE> element sent from the 5G PKMF to the UE contains:

a) zero or more <UNR-discovery-security-parameters-accept> elements which contain accepted transactions;

b) zero or more <UNR-discovery-security-parameters-reject> elements which contain rejected transactions;

c) zero or one <anyExt> element containing elements defined in future releases;

d) zero or more elements from other namespaces defined in future releases; and

e) zero or more attributes defined in future releases.

The <UNR-discovery-security-parameters-accept> contains:

a) a <transaction-ID> element containing the parameter defined in clause 11.6.2.1;

b) zero or one <security-parameters-for-remote-UE> element indicating the 5G ProSe UE-to-network relay discovery security parameters for 5G ProSe remote UE;

c) zero or one <list-of-PC5-security-policies-per-relay-service-code-for-remote-UE> element indicating the PC5 security policies per relay service code for 5G ProSe remote UE;

d) zero or one <security-parameters-for-UNR> element indicating the 5G ProSe UE-to-network relay discovery security parameters for 5G ProSe UE-to-network relay UE;

e) zero or one <list-of-PC5-security-policies-per-relay-service-code-for-UNR> element indicating the PC5 security policies per relay service code for 5G ProSe UE-to-network relay UE;

f) a <Current-Time> element containing the parameter defined in clause 11.6.2.7;

g) a <Max-Offset> element containing the parameter defined in clause 11.6.2.8;

h) zero or one <anyExt> element containing elements defined in future releases;

i) zero or more elements from other namespaces defined in future releases; and

j) zero or more attributes defined in future releases.

The <security-parameters-for-remote-UE> element contains:

a) an <expiration-timer> element containing the parameter defined in clause 11.6.2.9;

b) a <list-of-security-parameters-per-relay-service-code> element;

c) zero or one <anyExt> element containing elements defined in future releases;

d) zero or more elements from other namespaces defined in future releases; and

e) zero or more attributes defined in future releases.

The <list-of-security-parameters-per-relay-service-code> element included in the <security-parameters-for-remote-UE> element contains:

a) one or more <security-parameters-per-relay-service-code> elements;

b) zero or one <anyExt> element containing elements defined in future releases;

c) zero or more elements from other namespaces defined in future releases; and

d) zero or more attributes defined in future releases.

The <security-parameters-per-relay-service-code> element included in the <list-of-security-parameters-per-relay-service-code> element included in the <security-parameters-for-remote-UE> element contains:

a) a <relay-service-code> element containing the parameter defined in clause 11.6.2.10;

b) optionally a <code-receiving-security-parameters-for-model-A> element;

c) optionally a <code-receiving-security-parameters-for-model-B> element;

d) optionally a <code-sending-security-parameters-for-model-B> element;

e) a <selected-PC5-ciphering-algorithm> element containing the parameter defined in clause 11.6.2.11;

f) zero or one <anyExt> element containing elements defined in future releases;

g) zero or more elements from other namespaces defined in future releases; and

h) zero or more attributes defined in future releases.

The <code-receiving-security-parameters-for-model-A> element, the <code-sending-security-parameters-for-model-A> element, the <code-receiving-security-parameters-for-model-B> element and the <code-sending-security-parameters-for-model-B> element contain:

a) optionally a <DUSK> element containing the parameter defined in clause 11.6.2.12;

b) optionally a <DUIK> element containing the parameter defined in clause 11.6.2.13;

c) optionally a <DUCK> element;

d) zero or one <anyExt> element containing elements defined in future releases;

e) zero or more elements from other namespaces defined in future releases; and

f) zero or more attributes defined in future releases.

The <DUCK> element contains:

a) a <discovery-user-confidentiality-key> element containing the parameter defined in clause 11.6.2.14;

b) an <encrypted-bitmask> element containing the parameter defined in clause 11.6.2.15;

c) zero or one <anyExt> element containing elements defined in future releases;

d) zero or more elements from other namespaces defined in future releases; and

e) zero or more attributes defined in future releases.

The <list-of-PC5-security-policies-per-relay-service-code-for-remote-UE> element and the <list-of-PC5-security-policies-per-relay-service-code-for-UNR> element contain:

a) one or more <PC5-security-policies-per-relay-service-code> elements;

b) zero or one <anyExt> element containing elements defined in future releases;

c) zero or more elements from other namespaces defined in future releases; and

d) zero or more attributes defined in future releases.

The <PC5-security-policies-per-relay-service-code> element contains:

a) a <relay-service-code> element containing the parameter defined in clause 11.6.2.10;

b) a <PC5-security-policies> element;

c) zero or one <anyExt> element containing elements defined in future releases;

d) zero or more elements from other namespaces defined in future releases; and

e) zero or more attributes defined in future releases.

The <PC5-security-policies> element contains:

a) a <signalling-ciphering-policy> element containing the parameter defined in clause 11.6.2.17;

b) a <user-plane-integrity-protection-policy> element containing the parameter defined in clause 11.6.2.18;

c) a <user-plane-ciphering-policy> element containing the parameter defined in clause 11.6.2.19;

d) zero or one <anyExt> element containing elements defined in future releases;

e) zero or more elements from other namespaces defined in future releases; and

f) zero or more attributes defined in future releases.

The <security-parameters-for-UNR> element contains:

a) an <expiration-timer> element containing the parameter defined in clause 11.6.2.9;

b) a <list-of-security-parameters-per-relay-service-code> element; and

c) zero or one <anyExt> element containing elements defined in future releases;

d) zero or more elements from other namespaces defined in future releases; and

e) zero or more attributes defined in future releases.

The <list-of-security-parameters-per-relay-service-code> element included in the <security-parameters-for-UNR> element contains:

a) one or more <security-parameters-per-relay-service-code> elements;

b) zero or one <anyExt> element containing elements defined in future releases;

c) zero or more elements from other namespaces defined in future releases; and

d) zero or more attributes defined in future releases.

The <security-parameters-per-relay-service-code> element included in the <list-of-security-parameters-per-relay-service-code> element included in the <security-parameters-for-UNR> element contains:

a) a <relay-service-code> element containing the parameter defined in clause 11.6.2.10;

b) optionally a <code-sending-security-parameters-for-model-A> element;

c) optionally a <code-receiving-security-parameters-for-model-B> element;

d) optionally a <code-sending-security-parameters-for-model-B> element;

e) a <selected-PC5-ciphering-algorithm> element containing the parameter defined in clause 11.6.2.11;

f) zero or one <anyExt> element containing elements defined in future releases;

g) zero or more elements from other namespaces defined in future releases; and

h) zero or more attributes defined in future releases.

The <UNR-discovery-security-parameters-reject> element contains:

a) a <transaction-ID> element containing the parameter defined in clause 11.6.2.1;

b) a <PC8-control-protocol-cause-value> element containing the parameter defined in clause 11.6.2.20;

c) zero or one <anyExt> element containing elements defined in future releases;

d) zero or more elements from other namespaces defined in future releases; and

e) zero or more attributes defined in future releases.

10.6.4.4 Semantics of <PROSE_PRUK_REQUEST>

The <PROSE_PRUK_REQUEST> element contains:

a) zero or more <PRUK-request> elements which contain transactions sent from the UE to the 5G PKMF;

b) zero or one <anyExt> element containing elements defined in future releases;

c) zero or more elements from other namespaces defined in future releases; and

d) zero or more attributes defined in future releases.

The <PRUK-request> element contains:

a) a <transaction-ID> element containing the parameter defined in clause 11.6.2.1;

b) zero or one <UP-PRUK-ID> element containing the parameter defined in clause 11.6.2.3;

c) zero or one <anyExt> element containing elements defined in future releases;

d) zero or more elements from other namespaces defined in future releases; and

e) zero or more attributes defined in future releases;

10.6.4.5 Semantics of <PROSE_PRUK_RESPONSE>

The <PROSE_PRUK_RESPONSE> element contains:

a) zero or more <PRUK-accept> elements which contain the accepted transactions;

b) zero or more <PRUK-reject> elements which contain the rejected transactions;

c) zero or one <anyExt> element containing elements defined in future releases;

d) zero or more elements from other namespaces defined in future releases; and

e) zero or more attributes defined in future releases.

The <PRUK-accept> element contains:

a) a <transaction-ID> element containing the parameter defined in clause 11.6.2.1;

b) a <UP-PRUK-ID> element containing the parameter defined in clause 11.6.2.3;

c) a <UP-PRUK> element containing the parameter defined in clause 11.6.2.2;

d) zero or one <anyExt> element containing elements defined in future releases;

e) zero or more elements from other namespaces defined in future releases; and

f) zero or more attributes defined in future releases.

The <PRUK-reject> element contains:

a) a <transaction-ID> element containing the parameter defined in clause 11.6.2.1;

b) a <PC8-control-protocol-cause-value> element containing the parameter defined in clause 11.6.2.20;

c) zero or one <anyExt> element containing elements defined in future releases;

d) zero or more elements from other namespaces defined in future releases; and

e) zero or more attributes defined in future releases.

10.6.4.6 Semantics of <PROSE_KEY_REQUEST> element

The <PROSE_KEY_REQUEST> element contains:

a) zero or more <key-request> elements which contain transactions sent from the UE to the 5G PKMF.

b) zero or one <anyExt> element containing elements defined in future releases;

c) zero or more elements from other namespaces defined in future releases; and

d) zero or more attributes defined in future releases.

The <key-request> element contains:

a) a <transaction-ID> element containing the parameter defined in clause 11.6.2.1;

b) a <relay-service-code> element containing the parameter defined in clause 11.6.2.10;

c) zero or one <SUCI> element containing the parameter defined in clause 11.6.2.21;

d) zero or one <UP-PRUK-ID> element containing the parameter defined in clause 11.6.2.3;

e) a <Knrp-freshness-parameter-1> element containing the parameter defined in clause 11.6.2.22;

f) zero or one <HPLMN> element;

g) zero or one <AUTS> element containing the parameter defined in clause 11.6.2.23;

h) zero or one <RAND> element containing the parameter defined in clause 11.6.2.24;

i) zero or one <anyExt> element containing elements defined in future releases;

j) zero or more elements from other namespaces defined in future releases; and

k) zero or more attributes defined in future releases.

The <HPLMN> element contains:

a) an <mcc> elements containing the parameter defined in clause 11.6.2.5;

b) an <mnc> elements containing the parameter defined in clause 11.6.2.6;

c) zero or one <anyExt> element containing elements defined in future releases;

d) zero or more elements from other namespaces defined in future releases; and

e) zero or more attributes defined in future releases.

10.6.4.7 Semantics of <PROSE_KEY_RESPONSE> element

The <PROSE_KEY_RESPONSE> element sent from the 5G PKMF to the UE contains:

a) zero or more <key-accept> elements which contain accepted transactions;

b) zero or more <key-reject> elements which contain rejected transactions;

c) zero or one <anyExt> element containing elements defined in future releases;

d) zero or more elements from other namespaces defined in future releases; and

e) zero or more attributes defined in future releases.

The <key-accept> contains:

a) a <transaction-ID> element containing the parameter defined in clause 11.6.2.1;

b) a <UP-PRUK-ID> element containing the parameter defined in clause 11.6.2.3;

c) a <Knrp> element containing the parameter defined in clause 11.6.2.25;

d) a <Knrp-freshness-parameter-2> element containing the parameter defined in clause 11.6.2.26;

e) zero or one <GPI> element containing the parameter defined in clause 11.6.2.16;

f) zero or one <anyExt> element containing elements defined in future releases;

g) zero or more elements from other namespaces defined in future releases; and

h) zero or more attributes defined in future releases.

The <key-reject> element contains:

a) a <transaction-ID> element containing the parameter defined in clause 11.6.2.1;

b) a <PC8-control-protocol-cause-value> element containing the parameter defined in clause 11.6.2.20;

c) zero or one <anyExt> element containing elements defined in future releases;

d) zero or more elements from other namespaces defined in future releases; and

e) zero or more attributes defined in future releases.

10.7 Messages transmitted over the PC3ach interface

10.7.1 General

This clause defines XML schema and MIME type related to messages transmitted over the PC3ach interface.

10.7.2 application/vnd.3gpp-prose-pc3ach+xml

The MIME type is used to carry information related to message transmitted over the PC3ach interface. It shall be coded as an XML document compliant to the XML schema in clause 10.7.3 containing one of the following messages:

– PROSE_USAGE_INFORMATION_REPORT_LIST; or

– PROSE_USAGE_INFORMATION_REPORT_LIST_RESPONSE.

Each of those messages is presented in the XML document as an XML element named after the corresponding message.

10.7.3 XML Schema

<?xml version="1.0" encoding="UTF-8"?>

<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"

xmlns="urn:3GPP:ns:5GProSe:PC3ach:2022"

elementFormDefault="qualified"

targetNamespace="urn:3GPP:ns:5GProSe:PC3ach:2022">

<xs:annotation>

<xs:documentation>

Syntax of messages transmitted over the PC3ach interface

</xs:documentation>

</xs:annotation>

<!– Types defined for parameters with complicate structure –>

<xs:simpleType name="IPAddress-type">

<xs:restriction base="xs:string"/>

</xs:simpleType>

<xs:simpleType name="Layer2Id-type">

<xs:restriction base="xs:hexBinary"/>

</xs:simpleType>

<xs:simpleType name="NCGI-type">

<xs:restriction base="xs:hexBinary"/>

</xs:simpleType>

<xs:simpleType name="AppSpecificInfo-type">

<xs:restriction base="xs:hexBinary"/>

</xs:simpleType>

<xs:simpleType name="RadioResourcesIndicator-type">

<xs:restriction base="xs:integer"/>

</xs:simpleType>

<xs:simpleType name="RadioFrequency-type">

<xs:restriction base="xs:hexBinary"/>

</xs:simpleType>

<!– XML attribute for any future extensions –>

<xs:complexType name="anyExtType">

<xs:sequence>

<xs:any namespace="##any" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

</xs:complexType>

<xs:complexType name="UsageInformationReportList-Info">

<xs:sequence>

<xs:element name="transaction-ID" type="xs:integer"/>

<xs:element name="usage-information-report" type="UsageInformationReport-Info"

minOccurs="1" maxOccurs="unbounded"/>

<xs:element name="app-specific-info" type="AppSpecificInfo-type" minOccurs="0" maxOccurs="unbounded"/>

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="UsageInformationReport-Info">

<xs:sequence>

<xs:element name="coverage" type="Coverage-info" minOccurs="0" maxOccurs="unbounded"/>

<xs:element name="group" type="Group-info" minOccurs="0" maxOccurs="unbounded"/>

<xs:element name="unicast" type="Unicast-info" minOccurs="0" maxOccurs="unbounded"/>

<xs:element name="radio-parameter-set" type="RadioParameterSet-info" minOccurs="0" maxOccurs="unbounded"/>

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:attribute name="sequence-number" type="xs:integer"/>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="Coverage-info">

<xs:sequence>

<xs:element name="location" type="Location-info" minOccurs="0" maxOccurs="unbounded"/>

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:attribute name="in-coverage" type="xs:boolean"/>

<xs:attribute name="timestamp" type="xs:dateTime" use="optional"/>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="Location-info">

<xs:sequence>

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:attribute name="NCGI" type="NCGI-type" use="optional"/>

<xs:attribute name="timestamp" type="xs:dateTime" use="optional"/>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="RadioParameterSet-info">

<xs:sequence>

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:attribute name="timestamp" type="xs:dateTime" use="required"/>

<xs:attribute name="params" type="xs:hexBinary"/>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="Group-info">

<xs:sequence>

<xs:element name="UE-source-IP-address" type="IPAddress-type"/>

<xs:element name="UE-source-layer2-id" type="Layer2Id-type"/>

<xs:element name="transmitter" type="Transmitter-info" minOccurs="0" maxOccurs="unbounded"/>

<xs:element name="transmission" type="Transmission-info" minOccurs="0" maxOccurs="unbounded"/>

<xs:element name="reception" type="Reception-info" minOccurs="0" maxOccurs="unbounded"/>

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:element name="qos-flow" type="QoSFlow-info" minOccurs="0" maxOccurs="unbounded"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:attribute name="prose-layer2-group-ID" type="Layer2Id-type"/>

<xs:attribute name="prose-group-IP-multicast-address" type="IPAddress-type"/>

<xs:attribute name="first-transmission-timestamp" type="xs:dateTime" use="optional"/>

<xs:attribute name="first-reception-timestamp" type="xs:dateTime" use="optional"/>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="Unicast-info">

<xs:sequence>

<xs:element name="UE-source-IP-address" type="IPAddress-type"/>

<xs:element name="UE-source-layer2-id" type="Layer2Id-type"/>

<xs:element name="transmitter" type="Transmitter-info" minOccurs="0" maxOccurs="unbounded"/>

<xs:element name="receiver" type="Receiver-info" minOccurs="0" maxOccurs="unbounded"/>

<xs:element name="transmission" type="Transmission-info" minOccurs="0" maxOccurs="unbounded"/>

<xs:element name="reception" type="Reception-info" minOccurs="0" maxOccurs="unbounded"/>

<xs:element name="relay-UE" type="RelayUE-info" minOccurs="0" maxOccurs="unbounded"/>

<xs:element name="relay" type="Relay-info" minOccurs="0" maxOccurs="unbounded"/>

<xs:element name="qos-flow" type="QoSFlow-info" minOccurs="0" maxOccurs="unbounded"/>

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:attribute name="first-transmission-timestamp" type="xs:dateTime" use="optional"/>

<xs:attribute name="first-reception-timestamp" type="xs:dateTime" use="optional"/>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="Transmitter-info">

<xs:sequence>

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:attribute name="source-IP-address" type="IPAddress-type"/>

<xs:attribute name="source-layer2-id" type="Layer2Id-type"/>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="Transmission-info">

<xs:sequence>

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:attribute name="in-coverage" type="xs:boolean"/>

<xs:attribute name="NCGI" type="NCGI-type" use="optional"/>

<xs:attribute name="amount" type="xs:integer"/>

<xs:attribute name="timestamp" type="xs:dateTime" use="optional"/>

<xs:attribute name="radio-resources-ind" type="RadioResourcesIndicator-type" use="optional"/>

<xs:attribute name="radio-frequency" type="RadioFrequency-type" use="optional"/>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="Reception-info">

<xs:sequence>

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:attribute name="in-coverage" type="xs:boolean"/>

<xs:attribute name="NCGI" type="NCGI-type" use="optional"/>

<xs:attribute name="amount" type="xs:integer"/>

<xs:attribute name="timestamp" type="xs:dateTime" use="optional"/>

<xs:attribute name="radio-resources-ind" type="RadioResourcesIndicator-type" use="optional"/>

<xs:attribute name="radio-frequency" type="RadioFrequency-type" use="optional"/>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="Receiver-info">

<xs:sequence>

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:attribute name="target-IP-address" type="IPAddress-type"/>

<xs:attribute name="target-layer2-id" type="Layer2Id-type"/>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="RelayUE-info">

<xs:sequence>

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:attribute name="relay-UE-IP-address" type="IPAddress-type"/>

<xs:attribute name="relay-UE-layer2-id" type="Layer2Id-type"/>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="Relay-info">

<xs:sequence>

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:attribute name="NCGI" type="NCGI-type" use="optional"/>

<xs:attribute name="amount" type="xs:integer"/>

<xs:attribute name="timestamp" type="xs:dateTime" use="optional"/>

<xs:attribute name="radio-resources-ind" type="RadioResourcesIndicator-type" use="optional"/>

<xs:attribute name="radio-frequency" type="RadioFrequency-type" use="optional"/>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="QoSFlow-info">

<xs:sequence>

<xs:element name="qos-parameter-set" type="QosParameterSet-info" minOccurs="0" maxOccurs="unbounded"/>

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:attribute name="timestamp" type="xs:dateTime" use="optional"/>

<xs:attribute name="qos-flow-id" type="xs:hexBinary" minOccurs="0" maxOccurs="unbounded"/>

<xs:attribute name="amount" type="xs:integer"/>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="QosParameterSet-info">

<xs:sequence>

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:attribute name="pqi" type="xs:hexBinary"/>

<xs:attribute name="gfbr" type="xs:hexBinary"/>

<xs:attribute name="mfbr" type="xs:hexBinary"/>

<xs:attribute name="averaging-window" type="xs:hexBinary"/>

<xs:attribute name="Resource-type" type="xs:hexBinary"/>

<xs:attribute name="default-priority-level" type="xs:hexBinary"/>

<xs:attribute name="packet-delay-budget" type="xs:hexBinary"/>

<xs:attribute name="packet-error-rate" type="xs:hexBinary"/>

<xs:attribute name="default-maximum-data-burst-volume" type="xs:hexBinary"/>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="UsageInformationReportListResponse-Info">

<xs:sequence>

<xs:element name="response-accept" type="UsageInformationReportListResponseAccept-Info" minOccurs="0"/>

<xs:element name="response-reject" type="UsageInformationReportListResponseReject-Info" minOccurs="0"/>

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="UsageInformationReportListResponseAccept-Info">

<xs:sequence>

<xs:element name="transaction-ID" type="xs:integer"/>

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:complexType name="UsageInformationReportListResponseReject-Info">

<xs:sequence>

<xs:element name="transaction-ID" type="xs:integer"/>

<xs:element name="cause-value" type="xs:integer"/>

<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<xs:element name="prose-pC3ach-message">

<xs:complexType>

<xs:choice>

<xs:element name="PROSE_USAGE_INFORMATION_REPORT_LIST" type="UsageInformationReportList-Info"/>

<xs:element name="PROSE_USAGE_INFORMATION_REPORT_LIST_RESPONSE" type="UsageInformationReportListResponse-Info"/>

<xs:element name="anyExt" type="anyExtType"/>

<xs:any namespace="##other" processContents="lax"/>

</xs:choice>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

</xs:element>

</xs:schema>

10.7.4 Semantics

10.7.4.1 General

The <prose-pC3ach-message> element is the root element of this XML document.

The <prose-pC3ach-message> element contains one of the following:

a) <PROSE_USAGE_INFORMATION_REPORT_LIST> element;

b) <PROSE_USAGE_INFORMATION_REPORT_LIST_RESPONSE> element;

c) <anyExt> element containing elements defined in future releases; or

d) one or more elements from other namespace defined in future releases.

The <prose-pC3ach-message> element contains zero, one or more attributes defined in future releases.

10.7.4.2 Semantics of <PROSE_USAGE_INFORMATION_REPORT_LIST>

The <PROSE_USAGE_INFORMATION_REPORT_LIST> element contains:

a) a <transaction-ID> element containing the parameter defined in clause 11.6.2.1;

b) one or more <usage-information-report> elements;

c) zero, one or more <app-specific-info> element;

d) zero or one <anyExt> element containing elements defined in future releases;

e) zero, one or more elements from other namespaces defined in future releases; and

f) zero, one or more attributes defined in future releases.

The <usage-information-report> element carries one usage information report. The <usage-information-report> element contains:

a) mandatory "sequence-number" attribute containing the parameter defined in clause 11.6.2.2;

b) zero, one or more <coverage> elements;

c) zero, one or more <group> element;

d) zero, one or more <unicast> element;

e) zero, one or more <radio-parameter-set> elements;

f) zero or one <anyExt> element containing elements defined in future releases;

g) zero, one or more elements from other namespaces defined in future releases; and

h) zero, one or more attributes defined in future releases.

The <coverage> element carries information whether the UE was in NG-RAN coverage or out of NG-RAN coverage. The <coverage> element contains:

a) mandatory "in-coverage" attribute containing the parameter defined in clause 11.6.2.3;

b) optional "timestamp" attribute containing the parameter defined in clause 11.6.2.7 indicating date and time when the information given in the element start being valid;

c) if the UE was in NG-RAN coverage, zero, one or more <location> elements;

d) zero or one <anyExt> element containing elements defined in future releases;

e) zero, one or more elements from other namespaces defined in future releases; and

f) zero, one or more attributes defined in future releases.

The <location> element carries information about an NG-RAN cell where the UE was camping on or which the UE used in the 5GMM-CONNECTED mode. The <location> element contains:

a) an optional "NCGI" attribute containing the parameter defined in clause 11.6.2.4;

b) an optional "timestamp" attribute containing the parameter defined in clause 11.6.2.7 indicating date and time when the information given in the element start being valid;

c) zero or one <anyExt> element containing elements defined in future releases;

d) zero, one or more elements from other namespaces defined in future releases; and

e) zero, one or more attributes defined in future releases.

The <radio-parameter-set> element carries information about the configured radio parameters for the ProSe direct communication applicable in the geographical area of the UE. The <radio-parameter-set> element contains:

a) a mandatory "params" attribute containing the parameter defined in clause 11.6.2.5;

b) a mandatory "timestamp" attribute containing the parameter defined in clause 11.6.2.7 indicating date and time when the information given in the element start being valid;

c) zero or one <anyExt> element containing elements defined in future releases;

d) zero, one or more elements from other namespaces defined in future releases; and

e) zero, one or more attributes defined in future releases.

The <group> element carries information about a 5G ProSe group. The <group> element contains:

a) a mandatory "prose-layer2-group-ID" attribute containing the parameter defined in clause 11.6.2.8;

b) a mandatory "prose-group-IP-multicast-address" attribute containing the parameter defined in clause 11.6.2.10;

c) an optional "first-transmission-timestamp" attribute containing the parameter defined in clause 11.6.2.7 indicating date and time of the first transmission to the ProSe Group IP multicast address in the collection period;

d) an optional "first-reception-timestamp" attribute containing the parameter defined in clause 11.6.2.7 indicating date and time of the first reception from the ProSe Group IP multicast address in the collection period;

e) a <UE-source-IP-address> element containing the parameter defined in clause 11.6.2.10, of the UE;

f) a <UE-source-layer2-id> element containing the parameter defined in clause 11.6.2.11, of the UE;

g) zero, one or more <transmitter> element;

h) zero, one or more <transmission> element;

i) zero, one or more <reception> element;

j) zero, one or more <qos-flow> elements;

k) zero or one <anyExt> element containing elements defined in future releases;

l) zero, one or more elements from other namespaces defined in future releases; and

m) zero, one or more attributes defined in future releases.

The <unicast> element carries information about an unicast mode 5G ProSe direct communication. The <unicast> element contains:

a) an optional "first-transmission-timestamp" attribute containing the parameter defined in clause 11.6.2.7 indicating date and time of the first transmission in the unicast mode 5G ProSe direct communication in the collection period;

b) an optional "first-reception-timestamp" attribute containing the parameter defined in clause 11.6.2.7 indicating date and time of the first reception in the unicast mode 5G ProSe direct communication in the collection period;

c) a <UE-source-IP-address> element containing the parameter defined in clause 11.6.2.10, of the UE;

d) a <UE-source-layer2-id> element containing the parameter defined in clause 11.6.2.11, of the UE;

e) zero, one or more <transmitter> element;

f) zero, one or more <receiver> element;

g) zero, one or more <transmission> element;

h zero, one or more <reception> element;

i) zero, one or more <relay-UE> element;

j) zero, one or more < relay> element;

k) zero, one or more <qos-flow> elements;

l) zero or one <anyExt> element containing elements defined in future releases;

m) zero, one or more elements from other namespaces defined in future releases; and

n) zero, one or more attributes defined in future releases.

The <transmitter> element carries information about a transmitter in a 5G ProSe group or in an unicast mode 5G ProSe direct communication. The <transmitter> element contains:

a) a mandatory "source-IP-address" attribute containing the parameter defined in clause 11.6.2.10, of the transmitter;

b) a mandatory "source-layer2-id" attribute containing the parameter defined in clause 11.6.2.11, of the transmitter;

c) zero or one <anyExt> element containing elements defined in future releases;

d) zero, one or more elements from other namespaces defined in future releases; and

e) zero, one or more attributes defined in future releases.

The <receiver> element carries information about a receiver in an unicast mode 5G ProSe direct communication. The <receiver> element contains:

a) a mandatory "target-IP-address" attribute containing the parameter defined in clause 11.6.2.10, of the receiver;

b) a mandatory "target-layer2-id" attribute containing the parameter defined in clause 11.6.2.11, of the receiver;

c) zero or one <anyExt> element containing elements defined in future releases;

d) zero, one or more elements from other namespaces defined in future releases; and

e) zero, one or more attributes defined in future releases.

The <transmission> element carries information about a transmission in a ProSe group or in an unicast mode 5G ProSe direct communication. The <transmission> element contains:

a) a mandatory "in-coverage" attribute containing the parameter defined in clause 11.6.2.3;

b) if the UE was in NG-RAN coverage when transmitting the data, an optional "NCGI" attribute containing the parameter defined in clause 11.6.2.5, indicating NG-RAN Cell Global Identification of the NG-RAN cell where the UE was camping on or which the UE used in the 5GMM-CONNECTED mode when transmitting the data;

c) if the UE was in NG-RAN coverage and the "NCGI" attribute is included:

1) a mandatory "amount" attribute containing the parameter defined in clause 11.6.2.12 indicating the amount of octets transmitted to the ProSe group or in an unicast mode 5G ProSe direct communication:

– when the UE was camping on a cell identified by the "NCGI" attribute when transmitting the data; or

– when the UE used in the 5GMM-CONNECTED mode a cell identified by the "NCGI" attribute when transmitting the data; and

2) an optional "timestamp" attribute containing the parameter defined in clause 11.6.2.7 indicating date and time of the first transmission in the NG-RAN cell;

d) if the UE was in NG-RAN coverage and the "NCGI" attribute is not included:

2) an optional "timestamp" attribute containing the parameter defined in clause 11.6.2.7 indicating date and time of the first transmission during the in NG-RAN coverage period;

e) if the UE was out of NG-RAN coverage:

2) an optional "timestamp" attribute containing the parameter defined in clause 11.6.2.7 indicating date and time of the first transmission during the out of NG-RAN coverage period;

f) an optional "radio-resources-ind" attribute containing the parameter defined in clause 11.6.2.13;

g) an optional "radio-frequency" attribute containing the parameter defined in clause 11.6.2.14;

h) zero or one <anyExt> element containing elements defined in future releases;

i) zero, one or more elements from other namespaces defined in future releases; and

j) zero, one or more attributes defined in future releases.

The <reception> element carries information about a reception in a ProSe group or in an unicast mode 5G ProSe direct communication. The <reception> element contains:

a) a mandatory "in-coverage" attribute containing the parameter defined in clause 11.6.2.3 indicating whether the UE was in NG-RAN coverage when receiving the data;

b) if the UE was in NG-RAN coverage when receiving the data, an optional "NCGI" attribute containing the parameter defined in clause 11.6.2.4 indicating NG-RAN Cell Global Identification of the NG-RAN cell where the UE was camping on or which the UE used in the 5GMM-CONNECTED mode when receiving the data;

c) if the UE was in NG-RAN coverage and the "NCGI" attribute is included:

1) a mandatory "amount" attribute containing the parameter defined in clause 11.6.2.12 indicating the amount of octets received from the ProSe group or in an unicast mode 5G ProSe direct communication:

– when the UE was camping on a cell identified by the "NCGI" attribute when receiving the data; or

– when the UE used in the 5GMM-CONNECTED mode a cell identified by the "NCGI" attribute when receiving the data; and

2) an optional "timestamp" attribute containing the parameter defined in clause 11.6.2.7 indicating date and time of the first reception in the NG-RAN cell;

d) if the UE was in NG-RAN coverage and the "NCGI" attribute is not included:

2) an optional "timestamp" attribute containing the parameter defined in clause 11.6.2.7 indicating date and time of the first reception during the in NG-RAN coverage period;

e) if the UE was out of NG-RAN coverage:

2) an optional "timestamp" attribute containing the parameter defined in clause 11.6.2.7 indicating date and time of the first reception during the out of NG-RAN coverage period;

f) an optional "radio-resources-ind" attribute containing the parameter defined in clause 11.6.2.13;

g) an optional "radio-frequency" attribute containing the parameter defined in clause 11.6.2.14;

h) zero or one <anyExt> element containing elements defined in future releases;

i) zero, one or more elements from other namespaces defined in future releases; and

j) zero, one or more attributes defined in future releases.

The <relay-UE> element carries information about a 5G ProSe UE-to-network relay UE. The <relay-UE> element contains:

a) a mandatory "relay-UE-IP-address" attribute containing the parameter defined in clause 11.6.2.10, of the 5G ProSe UE-to-network relay UE;

b) a mandatory "relay-UE-id" attribute containing the parameter defined in clause 11.6.2.11, of the 5G ProSe UE-to-network relay UE;

c) zero or one <anyExt> element containing elements defined in future releases;

d) zero, one or more elements from other namespaces defined in future releases; and

e) zero, one or more attributes defined in future releases.

The <relay> element carries information about a data relay in an unicast mode 5G ProSe direct communication between the 5G ProSe remote UE and the 5G ProSe UE-to-network relay UE,. The <relay> element contains:

a) a mandatory "NCGI" attribute containing the parameter defined in clause 11.6.2.4, indicating NG-RAN Cell Global Identification of the NG-RAN cell where the UE was camping on or which the UE used in the 5GMM-CONNECTED mode when relaying the data;

b a mandatory "amount" attribute containing the parameter defined in clause 11.6.2.12 indicating the amount of octets relayed by the UE used in the 5GMM-CONNECTED mode a cell identified by the "NCGI" attribute when relaying the data;

c) a mandatory "timestamp" attribute containing the parameter defined in clause 11.6.2.7 indicating date and time of the first data relay in the NG-RAN cell;

d) an optional "radio-resources-ind" attribute containing the parameter defined in clause 11.6.2.13;

e) an optional "radio-frequency" attribute containing the parameter defined in clause 11.6.2.14;

f) zero or one <anyExt> element containing elements defined in future releases;

g) zero, one or more elements from other namespaces defined in future releases; and

h) zero, one or more attributes defined in future releases.

The <app-specific-info> element contains an application specific data received from upper layers during the collection period.

The <qos-flow> element carries information of PC5 QoS flows used by the UE for 5G ProSe direct communication. The <qos-flow> element contains:

a) a mandatory "qos-flow-id" attribute containing the parameter defined in clause 11.6.2.15;

b) zero, one or more "<qos-parameter-set>" element;

c) an optional "timestamp" attribute containing the parameter defined in clause 11.6.2.7 indicating date and time when the information given in the element start being valid;

d) an optional "timestamp" attribute containing the parameter defined in clause 11.6.2.7 indicating date and time when the information given in the element stop being valid;

e) a mandatory "amount" attribute containing the parameter defined in clause 11.6.2.12 indicating the amount of octets of the QoS flow transmitted or received;

f) zero or one <anyExt> element containing elements defined in future releases;

g) zero, one or more elements from other namespaces defined in future releases; and

h) zero, one or more attributes defined in future releases.

The <qos-parameter-set> element carries information of QoS parameters for the PC5 QoS flows used by the UE for 5G ProSe direct communication. The <qos-parameter-set> element contains:

a) a mandatory "pqi" attribute containing the parameter defined in clause 11.6.2.16;

b) an optional "gfbr" attribute containing the parameter defined in clause 11.6.2.17;

c) an optional "mfbr" attribute containing the parameter defined in clause 11.6.2.18;

d) an optional "averaging-window" attribute containing the parameter defined in clause 11.6.2.19;

e) an optional "Resource-type" attribute containing the parameter defined in clause 11.6.2.20;

f) an optional "default-priority-level" attribute containing the parameter defined in clause 11.6.2.21;

g) an optional "packet-delay-budget" attribute containing the parameter defined in clause 11.6.2.22;

h) an optional "packet-error-rate" attribute containing the parameter defined in clause 11.6.2.23;

i) an optional "default-maximum-data-burst-volume" attribute containing the parameter defined in clause 11.6.2.24;

j) zero or one <anyExt> element containing elements defined in future releases;

k) zero, one or more elements from other namespaces defined in future releases; and

l) zero, one or more attributes defined in future releases.

10.7.4.3 Semantics of <PROSE_USAGE_INFORMATION_REPORT_LIST_RESPONSE>

The <PROSE_USAGE_INFORMATION_REPORT_LIST_RESPONSE> element contains:

a) one of <response-accept> element and <response-reject> element;

b) zero or one <anyExt> element containing elements defined in future releases;

c) zero, one or more elements from other namespaces defined in future releases; and

d) zero, one or more attributes defined in future releases.

The <response-accept> element indicates that a related PROSE_USAGE_INFORMATION_REPORT_LIST message was accepted. The <response-accept> element contains:

a) <transaction-ID> element containing the parameter defined in clause 11.6.2.1 indicating the value of the transaction ID of the related PROSE_USAGE_INFORMATION_REPORT_LIST message;

b) zero or one <anyExt> element containing elements defined in future releases;

c) zero, one or more elements from other namespaces defined in future releases; and

d) zero, one or more attributes defined in future releases.

The <response-reject> element indicates that a related PROSE_USAGE_INFORMATION_REPORT_LIST message was rejected. The <response-reject> element contains:

a) <transaction-ID> element containing the parameter defined in clause 11.6.2.1 indicating the value of the transaction ID of the related PROSE_USAGE_INFORMATION_REPORT_LIST message;

b) <cause-value> element containing the parameter defined in clause 11.6.2.6;

c) zero or one <anyExt> element containing elements defined in future releases;

d) zero, one or more elements from other namespaces defined in future releases; and

e) zero, one or more attributes defined in future releases.

10.1 Overview

10.2 5G ProSe direct discovery messages

10.2.1 Message definition

10.2.2 Relay TAI

10.2.3 NCGI

10.2.4 Target user info

10.2.5 Metadata

10.2.6 RRC container

10.2.7 Target discoveree info

10.3 PC5 signalling messages

10.3.1 ProSe direct link establishment request

10.3.1.1 Message definition

10.3.1.2 Target user info

10.3.1.3 Key establishment information container

10.3.1.4 Nonce_1

10.3.1.5 MSB of KNRP-sess ID

10.3.1.6 KNRP ID

10.3.1.7 Relay service code

10.3.1.8 ProSe identifiers

10.3.1.9 UE identity

10.3.1.10 User security key ID

10.3.1.11 HPLMN ID

10.3.1.12 UTC-based counter LSB

10.3.1.13 MIC

10.3.2 ProSe direct link establishment accept

10.3.2.1 Message definition

10.3.2.2 IP address configuration

10.3.2.3 Target link local IPv6 address

10.3.2.4 QoS flow descriptions

10.3.2.5 QoS rules

10.3.3 ProSe direct link establishment reject

10.3.3.1 Message definition

10.3.3.2 Back-off value

10.3.3.3 EAP message

10.3.4 ProSe direct link release request

10.3.4.1 Message definition

10.3.4.2 Back-off value

10.3.5 ProSe direct link release accept

10.3.5.1 Message definition

10.3.6 ProSe direct link modification request

10.3.6.1 Message definition

10.3.6.2 QoS rules

10.3.7 ProSe direct link modification accept

10.3.7.1 Message definition

10.3.7.2 QoS flow descriptions

10.3.7.3 QoS rules

10.3.8 ProSe direct link keepalive request

10.3.8.1 Message definition

10.3.8.2 Maximum inactivity period

10.3.9 ProSe direct link keepalive response

10.3.9.1 Message definition

10.3.10 ProSe direct link authentication request

10.3.10.1 Message definition

10.3.11 ProSe direct link authentication response

10.3.11.1 Message definition

10.3.12 ProSe direct link authentication reject

10.3.12.1 Message definition

10.3.13 ProSe direct link security mode command

10.3.13.1 Message definition

10.3.13.2 Nonce_2

10.3.13.3 LSB of KNRP-sess ID

10.3.13.4 Key establishment information container

10.3.13.5 MSBs of KNRP ID

10.3.13.6 UE PC5 unicast signalling security policy

10.3.13.7 GPI

10.3.13.8 EAP message

10.3.14 ProSe direct link security mode complete

10.3.14.1 Message definition

10.3.14.2 IP address configuration

10.3.14.3 Target link local IPv6 address

10.3.14.4 LSBs of KNRP ID

10.3.14.5 QoS rules

10.3.14.6 QoS flow descriptions

10.3.15 ProSe direct link security mode reject

10.3.15.1 Message definition

10.3.15.2 RAND

10.3.15.3 AUTS

10.3.16 ProSe direct link rekeying request

10.3.16.1 Message definition

10.3.16.2 Key establishment information container

10.3.1.5 MSB of K_NRP-sess ID

10.3.1.6 K_NRP ID

10.3.13.5 MSBs of K_NRP ID

10.3.14.4 LSBs of K_NRP ID