name: RQoS
full_form: Reflective Quality of Service
context: The following figure shows an example message flow when RQoS is used for a new QoS flow. In this example, the gNB receives from UPF a first downlink packet associated with a QFI for which the QoS parameters are known from the PDU session establishment, but for which there is no association to any DRB yet in AS. Figure A.2-1: DL data with new QFI sent over existing DRB 0. PDU session and DRB(s) have been already established. 1. gNB receives a downlink packet with a new QFI from UPF. 2. gNB decides to send the new QoS flow over an existing DRB. NOTE: If gNB decides to send it over a new DRB, it needs to establish the DRB first. 3. gNB sends the DL packet over the selected DRB with the new QFI and RDI set in the SDAP header. 4. UE identifies the QFI and RDI in the received DL packet and the DRB on which the packet was received. The AS mapping rules are then updated accordingly. 5. User Plane Data for the new QoS flow can then be exchanged between UE and gNB over the DRB according to the updated mapping rules and between UPF and gNB over the tunnel for the PDU session.
description: Reflective Quality of Service (RQoS) is a procedure utilized in the context of establishing and managing Quality of Service (QoS) flows within the 5G network architecture. It involves a series of steps initiated when a new QoS flow is detected, such as updating AS mapping rules based on received QFI and RDI information, to ensure that user plane data for the new QoS flow can be correctly exchanged between the UE and gNB over the designated DRB, and between UPF and gNB over the tunnel for the PDU session.
explanation: RQoS is classified as a Procedure because it outlines a specific sequence of operations (steps) that are followed to manage QoS flows in the network. This includes receiving downlink packets with new QFI from UPF, deciding on the DRB for transmission, updating AS mapping rules at the UE, and exchanging user plane data according to these updated rules.
section_title: A.2 New QoS Flow with RQoS
biotag_Context: O,O,O,O,O,O,O,O,O,B-Procedure,O,O,O,O,O,B-Measurement,O,O,O,O,O,B-Network Function,O,O,B-Network Function,O,O,O,O,O,O,O,B-Parameter,O,O,O,B-Measurement,O,O,O,O,O,B-Connection,O,O,O,O,O,O,O,O,O,O,O,B-Connection,O,O,O,O,O,B-Connection,O,O,O,B-Parameter,O,O,O,B-Connection,O,B-Connection,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,B-Parameter,O,O,O,B-Network Function,O,O,O,O,O,B-Measurement,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Connection,O,O,B-Network Function,O,O,B-Connection,O,O,O,O,B-Connection,O,O,O,B-Parameter,O,B-Parameter,O,O,O,B-Protocol,O,O,B-Device,O,O,B-Parameter,O,B-Parameter,O,O,O,B-Connection,O,O,O,B-Connection,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,B-Protocol,I-Protocol,O,O,O,O,B-Measurement,O,O,O,O,O,O,B-Device,O,B-Network Function,O,O,B-Connection,O,O,O,O,O,O,O,O,B-Network Function,O,B-Network Function,O,O,O,O,O,B-Connection,O
biotag_Description: B-Procedure,I-Procedure,I-Procedure,I-Procedure,O,O,O,O,O,O,O,O,O,O,O,O,B-Measurement,I-Measurement,I-Measurement,O,O,O,O,B-Technology,O,O,O,O,O,O,O,O,O,O,O,O,B-Measurement,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,B-Parameter,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,B-Measurement,O,O,O,O,O,O,O,B-Device,O,B-Network Function,O,O,O,O,O,O,B-Network Function,O,B-Network Function,O,O,O,O,O,B-Connection,O