A.1 IANA registrations for MIME types
24.5543GPPProximity-services (ProSe) in 5G System (5GS) protocol aspectsRelease 17Stage 3TS
A.1.1 General
IETF RFC 4288 [41], clause 9, states the process that applies in case of changes to the registry of media types. Any changes to the format after the registration with IANA would invoke this procedure.
A.1.2 application/vnd.3gpp-prose-pc3a+xml
Your Name:
<MCC name>
Your Email Address:
<MCC email address>
Media Type Name:
Application
Subtype name:
Vendor Tree – vnd.3gpp-prose-pc3a+xml
Required parameters:
None.
Optional parameters:
"charset" the parameter has identical semantics to the charset parameter of the "application/xml" media type as specified in clause 9.1 of IETF RFC 7303 [42].
Encoding considerations:
binary.
Security considerations:
Same as general security considerations for application/xml media type as specified in clause 9.1 of IETF RFC 7303 [42]. The information transported in this media type does not include active or executable content. Mechanisms for privacy and integrity protection of protocol parameters exist. Those mechanisms as well as authentication and further security mechanisms are described in 3GPP TS 33.503 [34].
This media type does not include provisions for directives that institute actions on a recipient’s files or other resources.
This media type does not include provisions for directives that institute actions that, while not directly harmful to the recipient, may result in disclosure of information that either facilitates a subsequent attack or else violates a recipient’s privacy in any way.
This media type does not employ compression.
Interoperability considerations:
The media type allows for interoperability of messages transmitted for 5G ProSe over the PC3a interface. The messages are sent between user equipment and mobile network.
Published specification:
3GPP TS 24.554 (http://www.3gpp.org/ftp/Specs/html-info/24554.htm)
Applications which use this media type:
n/a.
Fragment identifier considerations:
The handling in clause 5 of IETF RFC 7303 [42] applies.
Restrictions on usage:
None.
Provisional registration? (standards tree only):
n/a.
Additional information:
1. Deprecated alias names for this type: n/a
2. Magic number(s): n/a
3. File extension(s): n/a
4. Macintosh File Type Code(s): n/a
5. Object Identifier(s) or OID(s): n/a
Intended usage:
Common.
Other information/general comment:
The media type is intended to be used in 5G proximity service procedures.
Person to contact for further information:
– Name: <MCC name>
– Email: <MCC email address>
– Author/Change controller:
i) Author: 3GPP CT1 Working Group/3GPP_TSG_CT_WG1@LIST.ETSI.ORG
ii) Change controller: <MCC name>/<MCC email address>
A.1.2A application/vnd.3gpp-prose-pc8+xml
Your Name:
<MCC name>
Your Email Address:
<MCC email address>
Media Type Name:
Application
Subtype name:
Vendor Tree – vnd.3gpp-prose-pc8+xml
Required parameters:
None
Optional parameters:
"charset" the parameter has identical semantics to the charset parameter of the "application/xml" media type as specified in clause 9.1 of IETF RFC 7303 [42].
Encoding considerations:
binary.
Security considerations:
Same as general security considerations for application/xml media type as specified in clause 9.1 of IETF RFC 7303 [42]. The information transported in this media type does not include active or executable content. Mechanisms for privacy and integrity protection of protocol parameters exist. Those mechanisms as well as authentication and further security mechanisms are described in 3GPP TS 33.503 [34].
This media type does not include provisions for directives that institute actions on a recipient’s files or other resources.
This media type does not include provisions for directives that institute actions that, while not directly harmful to the recipient, may result in disclosure of information that either facilitates a subsequent attack or else violates a recipient’s privacy in any way.
This media type does not employ compression.
Interoperability considerations:
The media type allows for interoperability of messages transmitted over the PC8 interface. The messages are sent between user equipment and mobile network.
Published specification:
3GPP TS 24.554 (http://www.3gpp.org/ftp/Specs/html-info/24554.htm)
Applications which use this media type:
n/a.
Fragment identifier considerations:
The handling in clause 5 of IETF RFC 7303 [42] applies.
Restrictions on usage:
None.
Provisional registration? (standards tree only):
n/a.
Additional information:
1. Deprecated alias names for this type: n/a.
2. Magic number(s): n/a.
3. File extension(s): n/a.
4. Macintosh File Type Code(s): n/a.
5. Object Identifier(s) or OID(s): n/a.
Intended usage:
Common.
Other information/general comment:
The media type is intended to be used in 5G proximity service procedures.
Person to contact for further information:
– Name: <MCC name>
– Email: <MCC email address>
– Author/Change controller:
i) Author: 3GPP CT1 Working Group/3GPP_TSG_CT_WG1@LIST.ETSI.ORG
ii) Change controller: <MCC name>/<MCC email address>
A.1.3 application/vnd.3gpp-prose-pc3ach+xml
Your Name:
<MCC name>
Your Email Address:
<MCC email address>
Media Type Name:
Application
Subtype name:
Vendor Tree – vnd.3gpp-prose-pc3ach+xml
Required parameters:
None
Optional parameters:
"charset" the parameter has identical semantics to the charset parameter of the "application/xml" media type as specified in clause 9.1 of IETF RFC 7303 [42].
Encoding considerations:
binary.
Security considerations:
Same as general security considerations for application/xml media type as specified in clause 9.1 of IETF RFC 7303 [42]. The information transported in this media type does not include active or executable content. Mechanisms for privacy and integrity protection of protocol parameters exist. Those mechanisms as well as authentication and further security mechanisms are described in 3GPP TS 33.503 [34].
This media type does not include provisions for directives that institute actions on a recipient’s files or other resources.
This media type does not include provisions for directives that institute actions that, while not directly harmful to the recipient, may result in disclosure of information that either facilitates a subsequent attack or else violates a recipient’s privacy in any way.
This media type does not employ compression.
Interoperability considerations:
The media type allows for interoperability of messages transmitted over the PC3ach interface, including those related to transport of the usage information request of proximity services. The messages are sent between user equipment and mobile network.
Published specification:
3GPP TS 24.554 (http://www.3gpp.org/ftp/Specs/html-info/24554.htm)
Applications which use this media type:
n/a
Fragment identifier considerations:
The handling in clause 5 of IETF RFC 7303 [42] applies.
Restrictions on usage:
None
Provisional registration? (standards tree only):
n/a
Additional information:
1. Deprecated alias names for this type: n/a
2. Magic number(s): n/a
3. File extension(s): n/a
4. Macintosh File Type Code(s): n/a
5. Object Identifier(s) or OID(s): n/a
Intended usage:
Common.
Other information/general comment:
The media type is intended to be used in proximity service procedures.
Person to contact for further information:
– Name: <MCC name>
– Email: <MCC email address>
– Author/Change controller:
i) Author: 3GPP CT1 Working Group/3GPP_TSG_CT_WG1@LIST.ETSI.ORG
ii) Change controller: <MCC name>/<MCC email address>
Annex B (informative):
Change history
|
Change history |
|||||||
|
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
2021-02 |
CT1#128e |
C1-211183 |
Draft skeleton provided by the rapporteur. |
0.0.0 |
|||
|
2021-02 |
CT1#128e |
C1-211184 |
Implementing the following p-CR agreed by CT1: Editorial change from the rapporteur. |
0.1.0 |
|||
|
2021-04 |
CT1#129e |
Implementing the following p-CR agreed by CT1: Editorial change from the rapporteur. Correction from the rapporteur. |
0.2.0 |
||||
|
2021-05 |
CT1#130e |
Implementing the following p-CR agreed by CT1: Editorial change from the rapporteur. Correction from the rapporteur. |
0.3.0 |
||||
|
2021-08 |
CT1#131e |
Implementing the following p-CR agreed by CT1: Editorial change from the rapporteur. Correction from the rapporteur. |
0.4.0 |
||||
|
2021-10 |
CT1#132e |
Implementing the following p-CR agreed by CT1: Editorial change from the rapporteur. Correction from the rapporteur. |
0.5.0 |
||||
|
2021-12 |
CT#94-e |
Implementing the following p-CR agreed by CT1: Editorial change from the rapporteur. Correction from the rapporteur. |
1.0.0 |
||||
|
2022-01 |
CT1#133bis-e |
Implementing the following p-CR agreed by CT1: Editorial change from the rapporteur. Correction from the rapporteur. |
1.1.0 |
||||
|
2022-02 |
CT1#134e |
Implementing the following p-CR agreed by CT1: Editorial change from the rapporteur. Correction from the rapporteur. |
1.2.0 |
||||
|
2022-03 |
CT#95e |
TS 24.554 v2.0.0 presented to TSG for approval |
2.0.0 |
||||
|
2022-03 |
CT#95e |
TS 24.554 v17.0.0 created by MCC after CT#95e |
17.0.0 |
||||
|
2022-06 |
CT#96 |
CP-221241 |
0001 |
1 |
B |
DRX configuration parameters and Tx profiles |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221241 |
0003 |
1 |
F |
Privacy timer for U2N relay |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221241 |
0004 |
1 |
F |
Ciphering algorithm exchange between UE and DDNMF |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221209 |
0005 |
2 |
F |
RRC container in L2 relay discovery message |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221241 |
0006 |
1 |
F |
L2 relay not using authentication over PC5 |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221209 |
0007 |
2 |
B |
ProSe remote user key procedure |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221209 |
0008 |
3 |
B |
PC5-S for forwarding EAP message |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221241 |
0010 |
– |
F |
IANA registration for MIMIE types for 5G ProSe |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221210 |
0011 |
2 |
B |
General parts for procedures for PC8 interface |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221242 |
0012 |
1 |
B |
5G ProSe UE-to-network relay discovery security parameters request procedure for PC8 interface |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221210 |
0014 |
3 |
B |
Key request procedure for PC8 interface |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221242 |
0015 |
1 |
B |
Handling of unknown, unforeseen and erroneous protocol data for PC8 interface |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221242 |
0016 |
1 |
B |
Timers for PC8 interface |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221241 |
0017 |
– |
F |
Clarifications on 5G ProSe direct discovery procedure over PC5 interface |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221241 |
0018 |
– |
F |
Resolving Editor’s Notes in match report procedures |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221241 |
0019 |
– |
F |
Corrections for UTC-based counter LSB parameter |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221241 |
0020 |
1 |
F |
Resolving Editor’s Notes in 5G ProSe UE-to-network relay discovery over PC5 procedures |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221241 |
0021 |
1 |
F |
Update to configuration parameters |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221241 |
0022 |
1 |
F |
Update to direct link establishment for 5G ProSe layer 3 relay |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221241 |
0023 |
1 |
F |
Update to Mobility Restrictions for 5G ProSe UE-to-Network Relaying |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221241 |
0024 |
1 |
F |
Update to QoS handling for layer-3 relay with N3IWF |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221242 |
0025 |
1 |
F |
New cause for direct link release |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221242 |
0026 |
1 |
F |
Update to QoS flow handling for L3 U2N relay |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221209 |
0027 |
2 |
F |
Clarification on different source L2 IDs for discovery and communication |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221242 |
0028 |
1 |
B |
Add target user ID in relay discovery solicitation message |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221209 |
0029 |
2 |
F |
Correction on 5G ProSe direct discovery over PC5 when UE not in coverage |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221242 |
0030 |
1 |
F |
Handling of destination layer-2 ID collision for direct discovery and direct communication in the UE |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221242 |
0031 |
1 |
F |
Clarification on the initiating UE stopping passing the same PROSE PC5 DISCOVERY message to lower layers |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221209 |
0039 |
4 |
F |
Changes to Match report message for MIC check |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221241 |
0040 |
– |
F |
PC5 discovery message encoding changes for security protection |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221241 |
0041 |
1 |
B |
ProSe application traffic descriptor introduction |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221209 |
0042 |
2 |
B |
Relay Service Code Privacy Protection |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221241 |
0044 |
1 |
F |
Rejection of 5G ProSe direct link due to unsuccessful PDU session establishment by L3 relay UE |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221241 |
0045 |
1 |
F |
Rejection of PC5 link modification due to lack of packet filters for the PDU session |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221241 |
0046 |
– |
F |
Release of PC5 link by an L2 remote UE due to mobility management back-off timer |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221209 |
0047 |
2 |
B |
Pending indication for PDU session with secondary authentication for remote UE |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221241 |
0048 |
1 |
F |
Clarification on 5G PKMF |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221242 |
0050 |
1 |
F |
Harmonizing the terminologies LSBs of KNRP ID and MSBs of KNRP ID |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221242 |
0051 |
1 |
F |
Unifying the terminologies of 5G ProSe UE-to-network relay UE and 5G ProSe remote UE |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221241 |
0052 |
– |
F |
Correction for the privacy timer of 5G ProSe transmission over PC5 |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221242 |
0053 |
1 |
F |
Security protection of the restricted 5G ProSe Direct Discovery messages over PC5 |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221241 |
0055 |
– |
F |
Replacing configured PC5 security policies with the PC5 security policies received during restricted 5G ProSe direct discovery procedures |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221241 |
0057 |
– |
B |
Signalling integrity protection policy for layer-2 UE-to-network relay |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221241 |
0058 |
– |
B |
Configuring PC5 security policies for layer-2 UE-to-network relay |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221242 |
0059 |
1 |
F |
UE-to-network relay unicast direct communication procedures over PC5 interface |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221242 |
0061 |
1 |
F |
Applicability of 5G ProSe direct link authentication procedure to UE-to-network relay |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221242 |
0062 |
1 |
F |
Resolving the ENs related to possible changes to the 5G ProSe direct link establishment procedure due to the security requirements of UE-to-network relay |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221242 |
0063 |
1 |
B |
Resolving the EN related to possible changes to the 5G ProSe direct link re-keying procedure due to the security requirements of UE-to-network relay |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221241 |
0064 |
– |
F |
Resolving the EN related to possible changes to the 5G ProSe direct link release procedure due to the security requirements of UE-to-network relay |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221210 |
0065 |
3 |
B |
Resolving the EN related to possible changes to the 5G ProSe direct link security mode control procedure due to the security requirements of UE-to-network relay |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221242 |
0066 |
1 |
B |
Introducing KNRP freshness parameter 1 and KNRP freshness parameter 2 |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221242 |
0067 |
1 |
B |
Introducing the GBA Push Info (GPI) in the 5G ProSe direct link security mode control procedure |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221210 |
0068 |
3 |
B |
Handling of synchronization failure for 5G ProSe UE-to-network relay security |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221242 |
0069 |
1 |
B |
Triggering 5G ProSe direct link release procedure due to secondary authentication failure |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221209 |
0071 |
2 |
F |
Authorization to use Model A and Model B for 5G ProSe UE-to-network relay discovery |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221209 |
0072 |
– |
B |
References, definitions and abbreviations for 5G ProSe charging |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221210 |
0074 |
2 |
B |
Transport protocol for PC3ch Control Protocol for 5G ProSe direct communication |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221209 |
0078 |
1 |
B |
Charging information collection for 5G ProSe Direct Discovery |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221209 |
0079 |
– |
B |
IANA registrations for MIME types for 3gpp-5g-prose-pc3ch+xml |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221210 |
0080 |
3 |
F |
Update to configuration by application server |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221210 |
0081 |
1 |
F |
UE not providing SUPI in PC3a messages |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221210 |
0082 |
1 |
B |
PC8 messages XML elements, semantic and parameters |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221210 |
0085 |
1 |
B |
Precedence between the 5G PKMF address provided in the ProSeP by the PCF and by the 5G DDNMF |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221209 |
0086 |
– |
F |
Provisioning of ProSe NR frequencies associated with the ProSe identifier for unicast communication mode to lower layers |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221209 |
0089 |
– |
F |
Correction on indication in L2 relay UE to send SR |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221209 |
0091 |
1 |
D |
Editorial changes |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221210 |
0093 |
2 |
F |
Rejection of 5G ProSe direct link due to congestion at the 5GSM layer in the layer-3 UE to network relay |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221210 |
0094 |
1 |
B |
The impact of NR Tx profile on the transmission and reception of Broadcast and Groupcast modes of 5G ProSe communication |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221210 |
0095 |
1 |
B |
Introducing the validity timer of the security related parameters for discovery |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221210 |
0096 |
1 |
F |
Applicability of Key establishment information container IE to the security of the UE-to-network relay |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221210 |
0097 |
1 |
F |
Some miscellaneous corrections for 5G ProSe |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221209 |
0098 |
– |
F |
Correcting missing implementation related to security preservation for 5G ProSe |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221209 |
0099 |
– |
F |
Correction for the cases of deleting the old security context for 5G ProSe |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221210 |
0100 |
1 |
B |
Rejecting PC5 connection establishment request upon security failure |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221210 |
0101 |
1 |
B |
UE-to-network relay reselection upon security failure |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221210 |
0102 |
1 |
F |
Adding 5G PKMF address request procedure in general clause |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221210 |
0103 |
1 |
F |
Clairification on performing 5G ProSe direct discovery over PC5 |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221210 |
0104 |
1 |
B |
PKMF address request procedure over PC3a interface |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221210 |
0105 |
1 |
F |
Clarification regarding the application identity used in the 5G ProSe direct discovery procedures – ALT. B |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221209 |
0106 |
– |
F |
Remove the default destination layer-2 ID in direct communication when provisioning |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221209 |
0107 |
– |
F |
Some editorial corrections |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221210 |
0108 |
– |
F |
Adding DRX handling for unicast communication procedures |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221072 |
0073 |
2 |
B |
Usage information reporting configuration in the UE |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221073 |
0075 |
2 |
B |
Procedures for PC3ch Control Protocol for 5G ProSe direct communication |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221074 |
0076 |
2 |
B |
Messages transmitted over the PC3ch interface |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221075 |
0077 |
2 |
B |
Formats for messages transmitted over the PC3ch interface |
17.1.0 |
|
2022-09 |
CT#97e |
CP-222144 |
0113 |
– |
F |
PC8 messages XML elements, semantic and parameters |
17.2.0 |
|
2022-09 |
CT#97e |
CP-222144 |
0117 |
– |
F |
Corrections for PC8 interface to remove PC5 security policies from key accept |
17.2.0 |
|
2022-09 |
CT#97e |
CP-222144 |
0120 |
1 |
F |
Correction on L2 relay UE selection |
17.2.0 |
|
2022-09 |
CT#97e |
CP-222144 |
0121 |
1 |
F |
Update match report procedures based on 33.503 |
17.2.0 |
|
2022-09 |
CT#97e |
CP-222144 |
0123 |
1 |
F |
Add the timer for AA message reliable transport procedure |
17.2.0 |
|
2022-09 |
CT#97e |
CP-222144 |
0125 |
1 |
F |
Privacy timer for relay |
17.2.0 |
|
2022-09 |
CT#97e |
CP-222144 |
0127 |
– |
F |
PC5 QoS flows handling initiated by the 5G ProSe layer-3 remote UE |
17.2.0 |
|
2022-09 |
CT#97e |
CP-222144 |
0137 |
– |
F |
Correction on the name of the interface for usage information collection |
17.2.0 |
|
2022-09 |
CT#97e |
CP-222144 |
0138 |
– |
F |
Correction on message names |
17.2.0 |
|
2022-09 |
CT#97e |
CP-222144 |
0147 |
– |
B |
Providing the EAP message in the SMC procedure for the EAP success case |
17.2.0 |
|
2022-09 |
CT#97e |
CP-222144 |
0148 |
– |
B |
Providing the EAP message in the DCR procedure for the EAP failure case |
17.2.0 |
|
2022-09 |
CT#97e |
CP-222144 |
0152 |
– |
F |
Harmonizing the terminologies of 5G ProSe remote UE and 5G ProSe UE-to-network relay UE across the specification |
17.2.0 |
|
2022-09 |
CT#97e |
CP-222144 |
0154 |
– |
B |
Providing the discovery security material for UE-to-network relay from 5G DDNMF |
17.2.0 |
|
2022-09 |
CT#97e |
CP-222144 |
0155 |
– |
F |
Correction to timer numbers that are used for UE-to-network relay discovery security parameters request over PC8 interface |
17.2.0 |
|
2022-09 |
CT#97e |
CP-222144 |
0156 |
– |
F |
The use of UE-to-network relay discovery security parameters request procedure over PC8 interface |
17.2.0 |
|
2022-09 |
CT#97e |
CP-222144 |
0157 |
– |
F |
Correcting the cause code UE authorisation failure and other corrections. |
17.2.0 |
|
2022-09 |
CT#97e |
CP-222144 |
0158 |
– |
F |
Null algorithm is not security deactivation for 5G ProSe |
17.2.0 |
|
2022-09 |
CT#97e |
CP-222145 |
0112 |
1 |
F |
Corrections for PC8 interface to indicate PRUK ID in key accept |
17.2.0 |
|
2022-09 |
CT#97e |
CP-222145 |
0114 |
1 |
F |
Corecting timing of initiation of 5G ProSe remote user key request procedure |
17.2.0 |
|
2022-09 |
CT#97e |
CP-222145 |
0115 |
1 |
F |
Correction for inclusion of HPLMN ID |
17.2.0 |
|
2022-09 |
CT#97e |
CP-222145 |
0119 |
1 |
C |
Remove secondary authentication for U2N relay related context |
17.2.0 |
|
2022-09 |
CT#97e |
CP-222145 |
0124 |
2 |
F |
Security protection on establishment request message for relay |
17.2.0 |
|
2022-09 |
CT#97e |
CP-222145 |
0126 |
1 |
F |
New pre-condition for direct link establishment procedure initiation |
17.2.0 |
|
2022-09 |
CT#97e |
CP-222145 |
0128 |
1 |
F |
Clarification on 5G ProSe direct link release procedure |
17.2.0 |
|
2022-09 |
CT#97e |
CP-222145 |
0129 |
1 |
F |
Protocol data unit type used over user plane for NR PC5 |
17.2.0 |
|
2022-09 |
CT#97e |
CP-222145 |
0130 |
1 |
F |
Non-IP PDU transport procedure |
17.2.0 |
|
2022-09 |
CT#97e |
CP-222145 |
0133 |
1 |
F |
Clarification on 5G DDNMF discovery |
17.2.0 |
|
2022-09 |
CT#97e |
CP-222145 |
0136 |
1 |
F |
Addition of abnormal cases |
17.2.0 |
|
2022-09 |
CT#97e |
CP-222145 |
0141 |
1 |
B |
The determination of using the control plane security solution for the 5G ProSe UE-to-network relay |
17.2.0 |
|
2022-09 |
CT#97e |
CP-222145 |
0159 |
1 |
F |
Defining the abnormal cases and the timer used for 5G ProSe AA message reliable transport procedure |
17.2.0 |
|
2022-09 |
CT#97e |
CP-222145 |
0160 |
1 |
F |
Resolving EN on mapping with the traffic descriptor in the ProSeP |
17.2.0 |
|
2022-09 |
CT#97e |
CP-222146 |
0111 |
2 |
F |
PLMN ID IE definition |
17.2.0 |
|
2022-09 |
CT#97e |
CP-222146 |
0116 |
1 |
F |
Correction of PRUK ID coding |
17.2.0 |
|
2022-09 |
CT#97e |
CP-222146 |
0118 |
1 |
F |
Requesting UE policies for 5G ProSe usage information reporting |
17.2.0 |
|
2022-09 |
CT#97e |
CP-222146 |
0143 |
1 |
F |
Clarification on the condition of including HPLMN ID in the DCR message |
17.2.0 |
|
2022-09 |
CT#97e |
CP-222146 |
0144 |
1 |
F |
Clarifications for the Privacy Protection of Relay Service Code |
17.2.0 |
|
2022-09 |
CT#97e |
CP-222146 |
0145 |
1 |
B |
Introducing the 5GPRUK ID in the DCR procedure |
17.2.0 |
|
2022-09 |
CT#97e |
CP-222146 |
0146 |
1 |
B |
Introducing the 5GPRUK ID in the 5G ProSe direct link re-keying procedure |
17.2.0 |
|
2022-09 |
CT#97e |
CP-222146 |
0149 |
1 |
F |
Clarification on the security procedure for Layer-3 UE-to-Network Relay with N3IWF support |
17.2.0 |
|
2022-09 |
CT#97e |
CP-222146 |
0150 |
1 |
B |
Integrity protection of the DCR message for UE-to-network relay |
17.2.0 |
|
2022-09 |
CT#97e |
CP-222146 |
0151 |
1 |
F |
Corrections related to 5G ProSe layer-3 UE-to-network relay with N3IWF support |
17.2.0 |
|
2022-09 |
CT#97e |
CP-222146 |
0153 |
1 |
F |
The criteria for selecting 5G ProSe layer-3 UE-to-network relay with N3IWF support |
17.2.0 |
|
2022-09 |
CT#97e |
Corrections suggested by the rapporteur done by MCC |
17.2.1 |
||||
|
2022-12 |
CT#98e |
CP-223149 |
0174 |
1 |
F |
Single PC5 link between remote UE and the relay |
17.3.0 |
|
2022-12 |
CT#98e |
CP-223149 |
0175 |
1 |
F |
Correction on some bullet logic and editorial changes |
17.3.0 |
|
2022-12 |
CT#98e |
CP-223148 |
0177 |
3 |
F |
Alignment of Remote UE behaviours on PC5 unicast link establishment |
17.3.0 |
|
2022-12 |
CT#98e |
CP-223148 |
0179 |
1 |
F |
Apply PC5 DRX to Layer-2 relay |
17.3.0 |
|
2022-12 |
CT#98e |
CP-223149 |
0181 |
1 |
F |
Some clarifications related to the security mode control procedure |
17.3.0 |
|
2022-12 |
CT#98e |
CP-223149 |
0185 |
1 |
F |
Correction on cause value #14 |
17.3.0 |
|
2022-12 |
CT#98e |
CP-223148 |
0186 |
2 |
F |
Aligninig the name of control plane security indication |
17.3.0 |
|
2022-12 |
CT#98e |
CP-223148 |
0187 |
1 |
F |
Add broadcast communication security related content |
17.3.0 |
|
2022-12 |
CT#98e |
CP-223148 |
0188 |
1 |
F |
Add groupcast communication security related content |
17.3.0 |
|
2022-12 |
CT#98e |
CP-223149 |
0190 |
1 |
F |
Rename 5GPRUK ID and 5GPRUK in CP based solution and rename PRUK and PRUK ID in UP based solution |
17.3.0 |
|
2022-12 |
CT#98e |
CP-223149 |
0191 |
1 |
F |
MIME types used in PC3a and PC8 and PC3ach |
17.3.0 |
|
2022-12 |
CT#98e |
CP-223149 |
0192 |
1 |
F |
Multiple corrections for 5G ProSe procedures |
17.3.0 |
|
2022-12 |
CT#98e |
CP-223149 |
0193 |
1 |
F |
CP-PRUK is associated with the RSC |
17.3.0 |
|
2022-12 |
CT#98e |
CP-223149 |
0194 |
1 |
F |
Corrections on UE-to-network relay discovery over PC5 interface |
17.3.0 |
|
2022-12 |
CT#98e |
CP-223149 |
0195 |
1 |
F |
Corrections on discoverer UE procedure for group member discovery |
17.3.0 |
|
2022-12 |
CT#98e |
CP-223149 |
0196 |
1 |
F |
Corrections on discoveree UE procedures for group member discovery and U2N relay discovery |
17.3.0 |
|
2022-12 |
CT#98e |
CP-223149 |
0197 |
1 |
F |
Configuration parameters for 5G ProSe remote UE using 5G ProSe layer-3 UE-to-network relay |
17.3.0 |
|
2022-12 |
CT#98e |
CP-223148 |
0198 |
1 |
F |
Clarification on implementation specific means of UE stopping direct discovery procedures |
17.3.0 |
|
2022-12 |
CT#98e |
CP-223148 |
0199 |
1 |
F |
Clarification on announcing procedure for relay discovery additional information |
17.3.0 |
|
2022-12 |
CT#98e |
CP-223149 |
0200 |
1 |
F |
Miscellaneous corrections |
17.3.0 |
|
2022-12 |
CT#98e |
CP-223149 |
0203 |
1 |
F |
IP address of the 5G DDNMF provisioned by the network |
17.3.0 |
|
2022-12 |
CT#98e |
CP-223149 |
0204 |
2 |
F |
Correcting handling of authentication synchronisation error |
17.3.0 |
|
2022-12 |
CT#98e |
CP-223149 |
0205 |
1 |
F |
Correction for <key-request> handling |
17.3.0 |
|
2022-12 |
CT#98e |
CP-223148 |
0206 |
2 |
F |
Clarification on initiating UE behaviors when receiving cause value #15 in DCR reject message |
17.3.0 |
|
2022-12 |
CT#98e |
CP-223149 |
0207 |
1 |
F |
Exclude the relay UE that sends DCR reject with cause value#15 when performing UE-to-network relay reselection procedure |
17.3.0 |
|
2022-12 |
CT#98e |
CP-223148 |
0208 |
1 |
F |
Clarification on supporting of corresponding security procedure when initiating U2N relay discovery over PC5 |
17.3.0 |
|
2022-12 |
CT#98e |
CP-223149 |
0209 |
1 |
F |
Default DRX for direct link establishment |
17.3.0 |
|
2022-12 |
CT#98e |
CP-223149 |
0210 |
2 |
F |
Providing all the mapped NR Tx Profiles for groupcast and broadcast mode 5G ProSe communication |
17.3.0 |
|
2022-12 |
CT#98e |
CP-223149 |
0211 |
1 |
F |
Optional to provision N3IWF selection infomation to the UEt |
17.3.0 |
|
2022-12 |
CT#98e |
CP-223149 |
0213 |
2 |
F |
Clarify on the MOBIKE |
17.3.0 |
|
2022-12 |
CT#98e |
CP-223149 |
0214 |
F |
Clarify on the ProSe restricted code suffix ranges |
17.3.0 |
|
|
2022-12 |
CT#98e |
CP-223149 |
0215 |
F |
Clarify on the 5G ProSe direct link establishment procedure of unicast mode |
17.3.0 |
|
|
2022-12 |
CT#98e |
CP-223149 |
0217 |
F |
Correction on the name of timer 5160 |
17.3.0 |
|
|
2022-12 |
CT#98e |
CP-223149 |
0218 |
1 |
F |
Correction on the Restricted discovery filters revocation procedure |
17.3.0 |
|
2022-12 |
CT#98e |
CP-223149 |
0219 |
1 |
F |
PC5 QoS flow handling in unicast mode 5G ProSe direct communication for U2N relay |
17.3.0 |
|
2022-12 |
CT#98e |
CP-223148 |
0220 |
1 |
F |
5G ProSe direct link modification procedure for U2N relay |
17.3.0 |
|
2022-12 |
CT#98e |
CP-223149 |
0221 |
1 |
F |
PC5 QoS info provisioning during 5G ProSe direct link security mode control procedure |
17.3.0 |
|
2022-12 |
CT#98e |
CP-223149 |
0222 |
F |
Target user info for direct link establishment |
17.3.0 |
|
|
2022-12 |
CT#98e |
CP-223148 |
0223 |
1 |
F |
Clarifications on 5G ProSe U2N relay discovery |
17.3.0 |
|
2022-12 |
CT#98e |
CP-223148 |
0225 |
1 |
F |
5G ProSe direct link establishment and release procedures for U2N relay |
17.3.0 |
|
2022-12 |
CT#98e |
CP-223148 |
0226 |
F |
Adding the missing security parameters in the "restricted-discoverer-response" |
17.3.0 |
|
|
2022-12 |
CT#98e |
CP-223148 |
0227 |
1 |
F |
Clarification on the initiating of a discoveree request procedure. |
17.3.0 |