The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in IETF BCP14 (RFC2119 & RFC8174)
Copyright (c) 2023 General Motors GTO LLC Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to you under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. SPDX-FileType: DOCUMENTATION SPDX-FileCopyrightText: 2023 General Motors GTO LLC SPDX-License-Identifier: Apache-2.0
Prioritization is used to control QoS at uP-L1 between devices. This document will follow RFC4594 Configuration Guidelines for DiffServ Service Classes.
-
All messages MUST be assigned a priority
-
Every topic MUST have a priority code associated with it.
-
Default priority when not assigned MUST be CS1
| Class | Description | Use Case |
|---|---|---|
CS0 |
Low Priority. No bandwidth assurance |
File Transfer |
CS1 |
Standard, undifferentiated application |
General (unclassified) |
CS2 |
Operations, Administration, and Management |
Streamer messages (sub, connect, etc…) |
CS3 |
Multimedia streaming |
Video Streaming |
CS4 |
Real-time interactive |
High priority (rpc events) |
CS5 |
Signaling |
Important |
CS6 |
Network control |
Safety Critical |
|
Note
|
Please see uP-L2 Specifications for values used per message type. |