A.1 IEEE registration templates
24.1933GPP5G SystemAccess Traffic Steering, Switching and Splitting (ATSSS)Release 17Stage 3TS
A.1.1 IEEE registration templates for ethertype values
A.1.1.1 IEEE registration templates for ethertype value for 3GPP IEEE MAC based protocol family
Editor’s note: MCC is requested to apply in IEEE-RA for allocation of an ethertype value according to this template.
Registration URL:
http://standards.ieee.org/develop/regauth/ethertype/index.html
Registry:
ethertype
Detailed description:
This application requests allocation of an ethertype value for 3GPP IEEE MAC based protocol family, as specified in IEEE 802 [11].
Protocol description:
The MAC client data field of a MAC frame as specified in IEEE 802.3 [12] of the 3GPP IEEE MAC based protocol family is formatted as follows:
– octet 1 of the MAC client data field is the protocol subtype field.
– remaining octets of the MAC client data field are the protocol data field.
The protocol subtype field set to one identifies the performance measurement function protocol specified in 3GPP TS 24.193.
3GPP TS 24.193 enables assignment of further protocols to values of the protocol subtype field.
Assignment quantity:
1
Additional comments:
1) Does the company requesting the assignment have any existing Ethertype assignments?
Yes.
1a) Does the existing use of the original assignment support sub-typing?
No.
1b) Does the current applicant know who is currently responsible for maintenance of the previously assigned Ethertype?
Yes.
1c) Has the company considered using sub-typing of the older Ethertype for the new use under application?
Yes. Sub-typing of the older Ethertype for the new use under application is not possible.
1d) Given the above, why is a new Ethertype needed?
See detailed description for the new use under application.
2) Has the new protocol been developed and tested in accordance with clause 9 and especially clause 9.2.3 and Figure 12 of IEEE Std 802-2014 [11], IEEE Standard for Local and Metropolitan Area Networks: Overview and Architecture?
The 3GPP IEEE MAC based protocol family has been developed as follows:
– the first octet of the MAC client data field of a MAC frame as specified in IEEE 802.3 [12] of the 3GPP IEEE MAC based protocol family contains the protocol subtype field.
– the MAC client data field of the MAC frame of the 3GPP IEEE MAC based protocol family does not contain a protocol version field. If a protocol identified by an existing protocol subtype field value is modified in a backward-compatible way, there is no need to indicate a protocol version. If a protocol identified by an existing protocol subtype field value needs to be modified in a backward-incompatible way, a new protocol subtype field value will be assigned to the modified protocol.
The 3GPP IEEE MAC based protocol family has not been tested.
3) Have the full provisions of Figure 12 for the "Protocol identification field" in the prototype protocol been preserved in the final version of the protocol for which the new EtherType is being requested?
The first octet of the MAC client data field of a MAC frame as specified in IEEE 802.3 [12] of the 3GPP IEEE MAC based protocol family contains the protocol subtype field.
The MAC client data field of the MAC frame of the 3GPP IEEE MAC based protocol family does not contain a protocol version field. If a protocol identified by an existing protocol subtype field value is modified in a backward-compatible way, there is no need to indicate a protocol version. If a protocol identified by an existing protocol subtype field value needs to be modified in a backward-incompatible way, a new protocol subtype field value will be assigned to the modified protocol.
This is preserved in the final version.
4) What provisions have been made for maintaining and assigning sub-types going forward within your company? Please provide an example of the first 10 bytes/octets as an example.
3GPP TS 24.193 enables assignment of protocols to values of the protocol subtype field. A sending entity shall not set the protocol subtype field to a reserved value. A receiving entity shall ignore the MAC client data field, if the protocol subtype field is set to a reserved value. 3GPP TS 24.193 so far contains an assignment for the performance measurement function to value one of the protocol subtype field.
For the performance measurement function protocol:
– value of octet 1 of the MAC client data field is set to one.
– values of octet 2 and octet 3 of the MAC client data field contain the length of the performance measurement function protocol message.
– value of octet 4 of the MAC client data field is set to the message type of the performance measurement function protocol.
– value of octet 5 and octet 6 of the MAC client data field is set to the extended procedure transaction identity of the performance measurement function protocol, enabling distinguishing of procedures running in parallel.
– values of octet 7 and later octets of the MAC client data field depend on the message type of the performance measurement function protocol.
Annex B (informative):
Change history
|
Change history |
||||||||
|
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
|
2019-02 |
CT1#115 |
TS skeleton and scope are provided by C1-191625 and C1-191704 respectively. |
0.0.0 |
|||||
|
2019-04 |
CT1#116 |
Includes the following contributions agreed by CT1 at CT1#116: C1-192468, C1-192471, C1-192472. |
0.1.0 |
|||||
|
2019-05 |
CT1#117 |
Includes the following contributions agreed by CT1 at CT1#117: C1-193488, C1-193489, C1-193769, C1-193770. |
0.2.0 |
|||||
|
2019-09 |
CT1#119 |
Includes the following contributions agreed by CT1 at CT1#119: C1-194735, C1-194736, C1-194738, C1-194740, C1-194934, C1-194938, C1-194941, C1-194975, C1-195119, C1-195123, C1-195161, C1-195162. |
0.3.0 |
|||||
|
2019-10 |
CT1#120 |
Includes the following contributions agreed by CT1 at CT1#120: C1-196191, C1-196712, C1-196746, C1-196748, C1-196749, C1-196750, C1-196751, C1-196752, C1-196753, C1-196947. |
0.4.0 |
|||||
|
2019-11 |
CT1#121 |
Includes the following contributions agreed by CT1 at CT1#121: C1-198239, C1-198709, C1-198712, C1-198713, C1-198714, C1-199036. |
0.5.0 |
|||||
|
2019-12 |
CT#86 |
CP-193150 |
Presentation for information at TSG CT |
1.0.0 |
||||
|
2019-12 |
CT#86 |
CP-192387 |
A title updated |
1.0.1 |
||||
|
2020-03 |
CT1#122-e |
Includes the following contributions agreed by CT1 at CT1#122-e: C1-200461, C1-200630, C1-200789, C1-200807, C1-200928, C1-200929, C1-200988, C1-201000, C1-201009, C1-201014, C1-201036. |
1.1.0 |
|||||
|
2020-05 |
CT1#123-e |
Includes the following contributions agreed by CT1 at CT1#123-e: C1-202124, C1-202533, C1-202642, C1-202661, C1-202679, C1-202818. |
1.2.0 |
|||||
|
2020-06 |
CT1#124-e |
Includes the following contributions agreed by CT1 at CT1#124-e: C1-203050, C1-203051, C1-203075, C1-203076, C1-203077, C1-204002, C1-204015, C1-204016. |
1.3.0 |
|||||
|
2020-06 |
CT#88e |
CP-201173 |
Presentation for approval at TSG CT |
2.0.0 |
||||
|
2020-07 |
CT#88e |
Version 16.0.0 created after approval |
16.0.0 |
|||||
|
2020-09 |
CT#89e |
CP-202153 |
0001 |
1 |
F |
Correction on the necessity of ATSSS Container IE |
16.1.0 |
|
|
2020-09 |
CT#89e |
CP-202153 |
0003 |
1 |
F |
Clarification on whether UP resources are established on 3GPP and non-3GPP accesses |
16.1.0 |
|
|
2020-09 |
CT#89e |
CP-202153 |
0004 |
1 |
F |
Handling of MA PDU session after an inter-system change from N1 mode to S1 mode |
16.1.0 |
|
|
2020-09 |
CT#89e |
CP-202153 |
0005 |
1 |
F |
ATSSS rule with steering functionality not supported by the UE |
16.1.0 |
|
|
2020-09 |
CT#89e |
CP-202153 |
0006 |
1 |
F |
Clarification on MAI for PMFP |
16.1.0 |
|
|
2020-09 |
CT#89e |
CP-202153 |
0007 |
1 |
F |
PMFP messages transported over default QoS flow |
16.1.0 |
|
|
2020-09 |
CT#89e |
CP-202153 |
0008 |
1 |
F |
RFC for draft-ietf-tcpm-converters |
16.1.0 |
|
|
2020-12 |
CT#90e |
CP-203179 |
0010 |
1 |
F |
Clarification on receipt of MA PDU session release command |
16.2.0 |
|
|
2020-12 |
CT#90e |
CP-203179 |
0011 |
3 |
F |
Clarifications on using DRB/IPSecSA as indication to MA PDU session UP resources establishment |
16.2.0 |
|
|
2020-12 |
CT#90e |
CP-203179 |
0012 |
1 |
F |
IEI value for the Padding IE |
16.2.0 |
|
|
2020-12 |
CT#90e |
CP-203179 |
0014 |
F |
Correction for PMFP messages sent via Ethernet PDU session |
16.2.0 |
||
|
2020-12 |
CT#90e |
CP-203179 |
0015 |
1 |
F |
Correction for EPTI length |
16.2.0 |
|
|
2020-12 |
CT#90e |
CP-203179 |
0017 |
F |
Correction for PMFP timer values |
16.2.0 |
||
|
2020-12 |
CT#90e |
CP-203179 |
0018 |
F |
Support of regular expression in ATSSS rules |
16.2.0 |
||
|
2020-12 |
CT#90e |
CP-203179 |
0020 |
1 |
F |
Transport Converter procedure |
16.2.0 |
|
|
2020-12 |
CT#90e |
CP-203179 |
0022 |
F |
Clarification on non-allowed area applied to wireline access |
16.2.0 |
||
|
2020-12 |
CT#90e |
CP-203179 |
0023 |
1 |
F |
Introduction of IP 3-tuple type |
16.2.0 |
|
|
2021-03 |
CT#91e |
CP-210109 |
0026 |
1 |
F |
Numbering the timers used in PMFP |
16.3.0 |
|
|
2021-03 |
CT#91e |
CP-210109 |
0028 |
1 |
F |
Fix support of network-requested UP reactivation |
16.3.0 |
|
|
2021-03 |
CT#91e |
CP-210133 |
0027 |
1 |
D |
Correction on establishing user plane resources |
17.0.0 |
|
|
2021-04 |
CT#91e |
Restoration of corrupted figures |
17.0.1 |
|||||
|
2021-06 |
CT#92e |
CP-211131 |
0040 |
1 |
A |
MA PDU session for LADN not supported |
17.1.0 |
|
|
2021-06 |
CT#92e |
CP-211131 |
0045 |
2 |
A |
Addition of ATSSS Rule ID and individual rule modification |
17.1.0 |
|
|
2021-06 |
CT#92e |
CP-211138 |
0031 |
1 |
B |
Support for MA PDU Session with 3GPP access in EPC |
17.1.0 |
|
|
2021-06 |
CT#92e |
CP-211138 |
0029 |
3 |
B |
Introduction of performance measurement for a certain target QoS flow and UE assistance data provisioning |
17.1.0 |
|
|
2021-06 |
CT#92e |
CP-211138 |
0036 |
1 |
B |
Support of UE assistance data in PMFP |
17.1.0 |
|
|
2021-06 |
CT#92e |
CP-211138 |
0037 |
1 |
B |
PMFP message transport associated with QoS flow |
17.1.0 |
|
|
2021-06 |
CT#92e |
CP-211138 |
0038 |
1 |
F |
EPS interworking if UE supporting 3GPP access leg in EPC of an MA PDU session |
17.10 |
|
|
2021-06 |
CT#92e |
CP-211138 |
0030 |
3 |
B |
Support of packet loss rate measurement |
17.1.0 |
|
|
2021-06 |
CT#92e |
CP-211150 |
0034 |
F |
Enable report the availability and unavailability of an access network |
17.1.0 |
||
|
2021-06 |
CT#92e |
CP-211150 |
0035 |
D |
Correction on EPTI |
17.1.0 |
||
|
2021-06 |
CT#92e |
CP-211150 |
0041 |
F |
5G-RG and hybrid access |
17.1.0 |
||
|
2021-06 |
CT#92e |
CP-211340 |
0047 |
5 |
C |
Introduction of steering mode indicator for load-balancing steering mode |
17.1.0 |
|
|
2021-09 |
CT#93e |
CP-212130 |
0046 |
3 |
C |
Introduction of threshold values |
17.2.0 |
|
|
2021-09 |
CT#93e |
CP-212130 |
0048 |
2 |
B |
Measurement performance per QoS flow |
17.2.0 |
|
|
2021-09 |
CT#93e |
CP-212155 |
0051 |
1 |
D |
Correction of MA PDU session network upgrade is allowed |
17.2.0 |
|
|
2021-09 |
CT#93e |
CP-212140 |
0052 |
1 |
F |
Introduction of MAC address range traffic descriptor component type in ATSSS rule |
17.2.0 |
|
|
2021-09 |
CT#93e |
CP-212130 |
0053 |
1 |
B |
Resolve the EN on negotiation the capability of performance measurement per QoS flow |
17.2.0 |
|
|
2021-09 |
CT#93e |
CP-212130 |
0054 |
1 |
B |
QoS flow recognition for per QoS flow measurements |
17.2.0 |
|
|
2021-09 |
CT#93e |
CP-212130 |
0055 |
2 |
B |
Define UE assistance operation in steering mode indicator |
17.2.0 |
|
|
2021-09 |
CT#93e |
CP-212130 |
0056 |
– |
B |
Non-IP type PDN connection support as 3GPP access leg of MA PDU session |
17.2.0 |
|
|
2021-09 |
CT#93e |
CP-212130 |
0057 |
– |
F |
Alignment of the PMFP procedure name |
17.2.0 |
|
|
2021-12 |
CT#94e |
CP-213038 |
0060 |
– |
F |
Remove the EN on failure of receiving the acknowledgement of restaring counting |
17.3.0 |
|
|
2021-12 |
CT#94e |
CP-213038 |
0061 |
– |
F |
Clarification on source and destination addresses setting for PMFP messages |
17.3.0 |
|
|
2021-12 |
CT#94e |
CP-213038 |
0062 |
– |
D |
Alignment of steering mode additional indicator |
17.3.0 |
|
|
2021-12 |
CT#94e |
CP-213038 |
0063 |
1 |
F |
UE-assistance operation |
17.3.0 |
|
|
2021-12 |
CT#94e |
CP-213038 |
0064 |
4 |
F |
Termination of UE assistance mode |
17.3.0 |
|
|
2021-12 |
CT#94e |
CP-213038 |
0065 |
4 |
F |
Updates to threshold values |
17.3.0 |
|
|
2021-12 |
CT#94e |
CP-213048 |
0066 |
1 |
F |
Reference corrections |
17.3.0 |
|
|
2021-12 |
CT#94e |
CP-213038 |
0067 |
1 |
F |
Update of QoS flow list |
17.3.0 |
|
|
2022-03 |
CT#95e |
CP-220228 |
0084 |
2 |
F |
Clarification on the steering functionality included in an ATSSS rule |
17.4.0 |
|
|
2022-03 |
CT#95e |
0082 |
2 |
F |
Resolution of editor’s note on UE assistance data termination procedure |
17.4.0 |
||
|
2022-03 |
CT#95e |
CP-220239 |
0078 |
1 |
F |
Add UAT as one of PMPF procedures |
17.4.0 |
|
|
2022-03 |
CT#95e |
CP-220239 |
0069 |
1 |
F |
Signal deactivation of an MA PDU session with PDN leg |
17.4.0 |
|
|
2022-03 |
CT#95e |
CP-220239 |
0070 |
1 |
B |
A/Gb mode or Iu mode Interworking for PDN leg |
17.4.0 |
|
|
2022-03 |
CT#95e |
CP-220239 |
0071 |
1 |
F |
Clarification on establishing PDN leg |
17.4.0 |
|
|
2022-03 |
CT#95e |
CP-220239 |
0074 |
1 |
F |
Clarification on PLR measurement procedure abnormal handling |
17.4.0 |
|
|
2022-03 |
CT#95e |
CP-220239 |
0075 |
– |
B |
ATSSS parameters provisioned and modified through EPS procedure – 24193 Part |
17.4.0 |
|
|
2022-03 |
CT#95e |
CP-220239 |
0076 |
1 |
F |
CIoT EPS optimizations is not applicable for the PDN leg |
17.4.0 |
|
|
2022-03 |
CT#95e |
CP-220239 |
0077 |
1 |
F |
Clarifications on PMFP used on the user planes via 3GPP access in EPC and non-3GPP access in 5GC |
17.4.0 |
|
|
2022-03 |
CT#95e |
CP-220239 |
0079 |
1 |
F |
UE assistance operation is disabled after UAD provisioning procedue |
17.4.0 |
|
|
2022-03 |
CT#95e |
CP-220239 |
0081 |
2 |
F |
Addition of UE assistance data termination procedure supervision |
17.4.0 |
|
|
2022-03 |
CT#95e |
CP-220239 |
0083 |
– |
F |
Clarification of message retransmission requirements for Access availability or unavailability report procedure |
17.4.0 |
|
|
2022-03 |
CT#95e |
CP-220239 |
0072 |
2 |
F |
Abnormal handling for adding PDN leg to an MA PDU session already with non-3GPP leg |
17.4.0 |
|
|
2022-03 |
CT#95e |
CP-220239 |
0068 |
3 |
B |
Re-activation of user-plane resources for an MA PDU session with PDN leg |
17.4.0 |
|
|
2022-03 |
CT#95e |
Editorial corrections |
17.4.1 |
|||||
|
2022-06 |
CT#96e |
CP-221204 |
0085 |
3 |
F |
Completion of PLR measurement procedure |
17.5.0 |
|
|
2022-06 |
CT#96e |
CP-221204 |
0087 |
1 |
F |
Correction on Additional request |
17.5.0 |
|
|
2022-06 |
CT#96e |
CP-221204 |
0088 |
1 |
F |
Correction on ATSSS rule encoding |
17.5.0 |
|
|
2022-06 |
CT#96e |
CP-221204 |
0089 |
– |
F |
Correction on several errors of ATSSS |
17.5.0 |
|
|
2022-06 |
CT#96e |
CP-221204 |
0092 |
1 |
F |
Modify Additional request IE |
17.5.0 |
|
|
2022-06 |
CT#96e |
CP-221204 |
0095 |
1 |
F |
Clarification regarding SMF handling during A/Gb mode or Iu mode Interworking |
17.5.0 |
|
|
2022-06 |
CT#96e |
CP-221204 |
0096 |
1 |
F |
Addition of UE assistance data provisioning procedure supervision |
17.5.0 |
|
|
2022-09 |
CT#97e |
CP-222138 |
0097 |
1 |
F |
Support MAC address range type in ATSSS container |
17.6.0 |
|
|
2022-12 |
CT#98e |
CP-223119 |
0098 |
1 |
F |
Resolution of editor’s note on optional backoff timer for PMFP UAD |
17.7.0 |
|
|
2022-12 |
CT#98e |
CP-223119 |
0100 |
1 |
F |
Removing Editor’s note |
17.7.0 |
|