8 List of system parameters
24.3863GPPProtocol aspectsRelease 17Stage 3TSUser Equipment (UE) to V2X control function
8.1 General
The description of timers in table 8.2.1 is considered a brief summary. The complete descriptions of the timers are in the procedures defined in subclause 5 and subclause 6.
8.2 Timers of procedures for V2X communication over PC5
Table 8.2.1: V2X communication over PC5 timers – UE side
|
TIMER NUM. |
TIMER VALUE |
CAUSE OF START |
NORMAL STOP |
ON |
|---|---|---|---|---|
|
T5000 |
Default 300 seconds NOTE |
Upon initiating transmission of V2X communication over PC5, as described in subclause 6.1.2.4. Upon receiving an indication from upper layers that the application layer identifier has been changed while performing transmission of V2X communication over PC5, as described in subclause 6.1.2.4. Upon T5000 expiration while while performing transmission of V2X communication over PC5, as described in subclause 6.1.2.4. |
Upon stopping transmission of V2X communication over PC5, as described in subclause 6.1.2.4. |
Change the value of the source Layer-2 ID self-assigned by the UE for V2X communication over PC5. If the V2X message contains IP data, change the value of the source IP address self-assigned by the UE for V2X communication over PC5. Restart T5000. |
|
NOTE: The default value of this timer is used if the V2X control function does not provision another value to the UE as part of the configuration parameters for V2X communication over PC5. |
||||
Annex A (informative):
Documentation of new MIME types and SDP extensions
A.1 vnd.3gpp.v2x MIME type
A.1.1 vnd.3gpp.v2x MIME type registration
Editor’s note: The IANA registration for the vnd.3gpp.v2x application MIME type needs to be initiated by MCC once the V2X-CT Work Item is completed.
Your Name:
<MCC name>
Your Email Address:
<MCC email address>
Media Type Name:
Application
Subtype name:
Vendor tree – vnd.3gpp.v2x
Required parameters:
type parameter.
The type parameter can be set to "IP", or "non-IP".
A content of the application/vnd.3gpp.v2x MIME type with the type parameter set to "IP" contains one V2X message such that the V2X message is an IP packet.
A content of the application/vnd.3gpp.v2x MIME type with the type parameter set to "non-IP" and the v2x-message-family parameter indicating a V2X message family contains one V2X message of the V2X message family.
Optional parameters:
v2x-message-family parameter.
The v2x-message-family parameter shall be included when the type parameter is set to "non-IP". Permissible values of the v2x-message-family parameter are specified in TS 24.386 subclause 7.1.
Encoding considerations:
binary.
Security considerations:
This media type does not include provisions for directives that institute actions on a recipient’s files or other resources.
The information transported in this media type does not include active or executable content.
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.
This media type is not targeted for applications that require some sort of security assurance but don’t provide the necessary security mechanisms themselves. The security assurance is expected to be provided by the environment this media type operates in. When this media type operates in environment described in 3GPP TS 33.185, security mechanisms are described in 3GPP TS 33.185.
Interoperability considerations:
Receiving entity shall ignore any media type parameter not defined in this media type registration.
If a content of the application/vnd.3gpp.v2x MIME type is transported using UDP transport, the UDP message contains one V2X message.
Published specification:
3GPP TS 24.386 (http://www.3gpp.org/ftp/Specs/html-info/24386.htm)
Applications which use this media type:
V2X applications
Fragment identifier considerations:
This media type does not specify how applications interpret fragment identifiers associated with the media type.
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 for V2X communication.
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.2 Mapping vnd.3gpp.v2x MIME parameters into SDP
The information carried in the MIME application type has a specific mapping to fields in SDP.
A vnd.3gpp.v2x connection shall be described by using an SDP m line. According to IETF RFC 4566 [16], the m-line format is the following:
m=<media> <port> <transport> <fmt>
For vnd.3gpp.v2x:
– the media type field shall have a value of "application";
– the port field shall include the transport port for V2X;
– the transport field shall have a value of "udp";
– the format field shall have a value of "vnd.3gpp.v2x".
The following is an example of an m line for a vnd.3gpp.v2x connection:
m=application 1234 udp vnd.3gpp.v2x
The vnd.3gpp.v2x media type parameters are indicated in the <format specific parameters> portion of the SDP "a=fmtp" attribute by a semicolon separated list of parameters as shown in table A.1.2-1.
Table A.1.2-1: ABNF syntax of the <format specific parameters> portion of the SDP "a=fmtp" attribute
format-specific-parameters = param *( ";" param )
param = param-name [ "=" param-value ]
param-name = ALPHA *(ALPHA / DIGIT / "-")
param-value = *( param-char )
param-char = *( %x20-3A / %x3C-FF )
The following is an example of an attribute line for vnd.3gpp.v2x options:
a=fmtp:vnd.3gpp.v2x type=non-IP;v2x-message-family=1
A.2 application/vnd.3gpp-v2x-local-service-information MIME type
A.2.1 application/vnd.3gpp-v2x-local-service-information MIME type registration
Your Name:
<MCC name>
Your Email Address:
<MCC email address>
Media Type Name:
Application
Subtype name:
Vendor Tree – vnd.3gpp-v2x-local-service-information
Required parameters:
None
Optional parameters:
None.
Encoding considerations:
binary.
Security considerations:
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.185.
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 V2X over MBMS bearers. The messages are sent between user equipment and mobile network.
Published specification:
3GPP TS 24.386 (http://www.3gpp.org/ftp/Specs/html-info/24386.htm)
Applications which use this media type:
n/a
Fragment identifier considerations:
The handling in section 5 of IETF RFC 7303 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 for V2X communication. The content of this media type is formatted according to 3GPP TS 24.386 subclause 7.4.
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 |
TSG # |
TSG Doc. |
CR |
Rev |
Subject/Comment |
New |
|
|
2016-10 |
– |
– |
– |
TS skeleton generated for submission at CT1#100 |
0.0.0 |
||
|
2016-10 |
CT1#100 |
– |
– |
– |
Implementation of C1-164402, C1-164496, C1-164743 and C1-164751 |
0.1.0 |
|
|
2016-10 |
CT1#100 |
– |
– |
– |
Editorial changes |
0.1.1 |
|
|
2016-11 |
CT1#101 |
– |
– |
– |
Implementation of C1-165099, C1-165314, C1-165315, C1-165324, C1-165328, C1-165389 and C1-165418 |
0.2.0 |
|
|
2016-11 |
CT-74 |
CP-160705 |
Version 1.0.0 created for presentation for information to CT plenary |
1.0.0 |
|||
|
2017-01 |
CT1#101-bis |
Implementation of C1-170012, C1-170013, C1-170336, C1-170337, C1-170338, C1-170340, C1-170341, C1-170342, C1-170343, C1-170345, C1-170346 and C1-170521 |
1.1.0 |
||||
|
2017-02 |
CT1#102 |
Implementation of C1-170581, C1-170791, C1-170792 and C1-170903 |
1.2.0 |
||||
|
2017-02 |
CT-75 |
CP-170156 |
Version 2.0.0 created for presentation for approval to CT plenary |
2.0.0 |
|||
|
2017-03 |
CT-75 |
Version 14.0.0 created after approval at CT plenary |
14.0.0 |
||||
|
2017-06 |
CT-76 |
CP-171091 |
0001 |
1 |
V2X communication over LTE-Uu – existing unicast routing for V2X messages of a V2X service with a V2X service identifier |
14.1.0 |
|
|
2017-06 |
CT-76 |
CP-171091 |
0002 |
Removal of Editor’s note on V2X control function FQDN format |
14.1.0 |
||
|
2017-06 |
CT-76 |
CP-171091 |
0003 |
Addition of PC5 privacy configurability |
14.1.0 |
||
|
2017-06 |
CT-76 |
CP-171091 |
0005 |
Adding UE operation for non-operator-managed |
14.1.0 |
||
|
2017-06 |
CT-76 |
CP-171091 |
0006 |
1 |
Security support of V2X service |
14.1.0 |
|
|
2017-09 |
CT-77 |
CP-172110 |
0007 |
2 |
Supporting cross-carrier operation for V2X communication over PC5 |
14.2.0 |
|
|
2017-09 |
CT-77 |
CP-172110 |
0008 |
Correction to remove reference to TS 36.101 for "non-operator managed" radio resources |
14.2.0 |
||
|
2017-09 |
CT-77 |
CP-172110 |
0009 |
Correction of ID change for V2X PC5 communication |
14.2.0 |
||
|
2017-09 |
CT-77 |
CP-172110 |
0010 |
2 |
Mapping between service types and V2X frequencies |
14.2.0 |
|
|
2017-09 |
CT-77 |
CP-172110 |
0011 |
1 |
Mapping between service types and V2X frequencies |
14.2.0 |
|
|
2017-12 |
CT-78 |
CP-173056 |
0013 |
2 |
Correction for carrier frequency selection and mapping between V2X service and V2X frequencies |
14.3.0 |
|
|
2017-12 |
CT-78 |
CP-173056 |
0015 |
IANA registration of application/vnd.3gpp-v2x-local-service-information MIME type |
14.3.0 |
||
|
2017-12 |
CT-78 |
CP-173056 |
0016 |
1 |
Update of IANA registration form for vnd.3gpp.v2x application MIME type |
14.3.0 |
|
|
Change history |
|||||||
|
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
2018-06 |
CT-80 |
CP-181070 |
0017 |
B |
Support of reliable transmission over PC5 |
15.0.0 |
|
|
2018-09 |
CT-81 |
CP-182152 |
0018 |
1 |
F |
Correction for reliable transmission over V2X PC5 |
15.1.0 |
|
2018-09 |
CT-81 |
CP-182152 |
0019 |
1 |
B |
Support of V2X over PC5 message transmission using Tx Profiles |
15.1.0 |
|
2018-12 |
CT-82 |
CP-183078 |
0021 |
2 |
A |
Update of specification reference for V2X message family |
15.2.0 |
|
2020-06 |
CT-88e |
CP-201355 |
0026 |
3 |
A |
Adding the new V2X message family |
15.3.0 |
|
2020-06 |
CT-88e |
CP-201116 |
0024 |
2 |
B |
Introducing V2X communications over NR-PC5 in EPC |
16.0.0 |
|
2020-06 |
CT-88e |
CP-201356 |
0027 |
3 |
A |
Adding the new V2X message family |
16.0.0 |
|
2020-09 |
CT-89e |
CP-202157 |
0028 |
F |
Minor correction on V2X over NR-PC5 in EPC |
16.1.0 |
|
|
2020-09 |
CT-89e |
CP-202192 |
0029 |
1 |
F |
Addition of support for V2X services over LTE-Uu interface using TCP |
16.1.0 |
|
2020-12 |
CT-90e |
CP-203188 |
0030 |
F |
V2X message in one or more TCP messages in LTE-Uu |
16.2.0 |
|
|
2020-12 |
CT-90e |
CP-203188 |
0031 |
F |
Application Identifier |
16.2.0 |
|
|
2022-04 |
CT-95e |
– |
– |
– |
– |
Update to Rel-17 version (MCC) |
17.0.0 |
|
2022-12 |
CT-98e |
CP-223126 |
0032 |
1 |
F |
Update of configuration parameters for V2X communication over NR-PC5 in EPC |
17.1.0 |