Patent Description:
The present disclosure relates to wireless communications, and specifically relates to quality of service (QoS) management in a 3rd Generation Partnership Project (3GPP) 5th generation (<NUM>) system.

Quality of service (QoS) refers to traffic prioritization and resource reservation control mechanisms. QoS enables traffic classification and service differentiation such that different types of traffics or users may receive different services. QoS flow is the finest granularity for QoS management in a <NUM> wireless system. A proposal for precedence order of derived QoS rules is known from document D1: <NPL>. Another example of the prior art can be found in document D2: <NPL>.

Aspects of the disclosure provide a method for reflective quality of service (QoS) control and management at a user equipment (UE). The method includes creating a derived QoS rule belonging to a session and having a QoS flow identifier (QFI). The derived QoS rule includes a precedence value that is set to one of a precedence value associated with a session identifier (ID) of the session received from a core network (CN) of a wireless communication system during a session establishment procedure for establishing the session, a precedence value associated with the QFI received from the CN during the session establishment procedure for establishing the session or when a downlink QoS flow having the QFI is added to the session, or a precedence value that is defined by an operator of the wireless communication system.

The method includes receiving a message from the CN indicating the session ID of the session and a first reflective QoS (RQ) timer value. An RQ timer associated with the derived QoS rule is set to the first RQ timer value and started when a UE derived QoS rule is created. The method further includes receiving a message from the CN indicating the session ID of the session, a set of QFIs and a second RQ timer value that is different from the first RQ value. When a second UE derived QoS rule is created with one of the set of OFIs, a timer is set to the second RQ timer value.

In an aspect, the method can further include receiving a message from the CN including the session ID of the session, and an operation code of modification or deletion, and modifying or deleting derived QoS rules of the session as a response to receiving the message.

In an aspect, the method can further include receiving a message indicating whether the CN supports reflective QoS or not, and as a response to receiving the message, starting a monitoring operation for reflective QoS when the CN supports reflective QoS. In one example, the message is received from the CN, and specifies the session ID of the session, and/or the QFI. In one example, the message is received from an access network (AN) of the wireless communication system, and specifies the session ID of the session, the QFI, and/or a radio bearer ID.

In an aspect, the method can further include receiving a message to indicate supporting or not supporting reflective QoS. Once not supporting Reflective QoS is received, the UE will stop monitoring the reflective QoS indication (RQI) carried in downlink packets. In one example, supporting of reflective QoS may be set as on by default at the CN, and the UE may transmit a session modification request to request the CN to stop supporting reflective QoS.

Aspects of the disclosure provide a UE for QoS control and management. The UE includes circuitry configured to create a derived QoS rule belonging to a session and having a QoS flow identifier (QFI). The precedence value of the derived QoS rule is set to one of a precedence value associated with a session identifier (ID) of the session received from a core network (CN) of a wireless communication system during a session establishment procedure for establishing the session, a precedence value associated with the QFI received from the CN during the session establishment procedure for establishing the session or when a downlink QoS flow having the QFI is added to the session, or a precedence value that is defined by an operator of the wireless communication system.

Aspects of the disclosure provide a non-transitory computer-readable medium storing instructions that, when executed by one or more processors, cause the one or more processors to perform the method for reflective QoS control and management at a UE.

Various embodiments of this disclosure that are proposed as examples will be described in detail with reference to the following figures, wherein like numerals reference like elements, and wherein:.

<FIG> shows an example wireless communication system <NUM> according to an embodiment of the disclosure. The system <NUM> can include user equipment (UE) <NUM>, an access network (AN) <NUM>, and a core network (CN) <NUM>. Those components <NUM>-<NUM> are coupled together as shown in <FIG>. In one example, the system <NUM> can be a system compliant with the 5th Generation (<NUM>) system standards developed by 3rd Generation Partnership Project (3GPP). Accordingly, structure and functions of the system <NUM> can be similar to that defined by the 3GPP <NUM> system standards.

The UE <NUM> can be a mobile phone, a vehicle, a camera, a portable computer, and the like. The AN <NUM> can be a base station implementing radio access technologies specified by 3GPP New Radio standards or evolved Long Term Evolution (LTE) standards. Alternatively, the AN <NUM> can be a general base station implementing a non-3GPP access technology, such as Wi-Fi.

The CN <NUM> can include a plurality of functional elements, referred to as Network Functions (NFs). Each NF can be implemented either as a network element on a dedicated hardware, as a software instance running on a dedicated hardware, or as a virtualized function instantiated on an appropriate platform, such as a cloud infrastructure. Two NFs are shown in <FIG>: a user plane function (UDF) <NUM>, and a session management function (SMF) <NUM>. The CN <NUM> can include other NFs although not shown in <FIG>. The CN <NUM> can be separated into two parts: a user plane and a control plane. The user plane carries user traffic while the control plane carries signaling. The UPF <NUM> is in the user plane, and other NFs of the CN <NUM> are in the control plane.

The UPF <NUM> can include at least the following functionality: providing connection between the UE <NUM> and a data network (DN) <NUM> via the AN <NUM> for transmission of user plane traffic (downlink or uplink traffic); packet routing and forwarding; and quality of service (QoS) handling, such as uplink/downlink rate enforcement, reflective QoS marking in downlink, and the like. The DN <NUM> can be the Internet, or a third party wireless or wired network.

The SMF <NUM> is responsible for session management, such as establishment, modification, or release of a session. A session <NUM> is shown in <FIG>. The session <NUM> is a logical connection between the UE <NUM> and the DN <NUM> crossing the AN <NUM> and the CN <NUM>. A session is referred to as a protocol data unit (PDU) session in 3GPP standards. Similarly, a session is referred to as a PDU session in this disclosure. The PDU session <NUM> can be an IPv4 session, an IPv6 session, or an Ethernet session, and the like. The PDU session <NUM> can include packet flows, referred to as QoS flows. For example, uplink or downlink traffic in the PDU session <NUM> can be classified into different QoS flows each marked with a QoS flow identifier (QFI), for example, based on traffic types, user subscription information, and network configurations, or other factors. Different QoS flows can then be treated differently according to the OFIs when passing through the components of the system <NUM> along the PDU session <NUM>.

The PDU session <NUM> can be established (upon request of the UE <NUM>), modified (upon request of the UE <NUM> or the CN <NUM>), and released (upon request of the UE <NUM> or the CN <NUM>) using non-access stratum (NAS) session management signaling or messages exchanged between the UE <NUM> and the SMF <NUM>. While the SMF <NUM> is shown to be directly connected with the UE <NUM> and the AN <NUM> in <FIG>, messages between the SMF <NUM> and the UE <NUM> or the AN <NUM> can be transferred via other components of the system <NUM>, such as an intermediate NF not shown in <FIG>. Generally, due to structure of radio access network protocol stacks of an LTE or <NUM> system, messages between the UE <NUM> and components of the CN <NUM> (such as the SMF <NUM>) are referred to as NAS messages, while messages between the UE <NUM> and the AN <NUM> are referred to access stratum (AS) messages. An AS message can be used as a carrier for delivery of a NAS message between the UE <NUM> and the CN <NUM>.

In one example, the UE <NUM> can transmit a PDU session establishment request to initiate a PDU session establishment procedure. Alternatively, an application server in the DN <NUM> can send a request to the CN <NUM> that in response can send a trigger message to the UE <NUM> specifying a specific application in the UE <NUM>. The UE <NUM> can pass the trigger message to the identified application in the UE <NUM>. The identified application can then initiate a session establishment procedure. The PDU session establishment request may include a PDU session identifier (ID) and a destination DN, such as the DN <NUM>. The PDU session ID can be unique per UE <NUM> and used to uniquely identify one of the UE <NUM>'s multiple PDU sessions.

In one example, during the session establishment procedure, the SMF <NUM> can be selected from multiple SMFs of the system <NUM>. The SMF <NUM> can then select the UPF <NUM> for establishing the PDU session <NUM> from candidate UPFs. Subsequently, the SMF <NUM> can provide session context information to the UE <NUM>, the AN <NUM>, and the UPF <NUM>, and allocate an IP address to the UE <NUM>. Based on the session context information, the UE <NUM>, the AN <NUM>, and the UPF <NUM> can perform session related operations accordingly to support the PDU session <NUM>.

In one example, QoS related context information can be provided by the SMF <NUM> to support QoS related operations at the UE <NUM>, the AN <NUM>, and the UPF <NUM>. For example, one or more QoS profiles each corresponding to a QoS flow can be provided to the AN <NUM>. One or more QoS rules can be provided to the UE <NUM>. One or more packet filter sets can be provided to the UPF <NUM>. Based on the QoS related context information, uplink or downlink traffic can be mapped to QoS flows, and processed accordingly. Specifically, the QoS rules provided to the UE <NUM> enable uplink QoS flow mapping at the UE <NUM>. The filter sets provided to the UPF <NUM> enable downlink QoS flow mapping at the UPF <NUM>.

In one example, the PDU session <NUM> can be modified after being established during a PDU session modification procedure. For example, a new QoS flow can be added by adding a QoS rule to the UE <NUM>, or an existing QoS flow can be deleted by removing an existing QoS rule in the UE <NUM>, when requested by the UE <NUM>. One or more parameters related with the PDU session <NUM> or QoS flows of the PDU session <NUM> can be changed.

Particularly, in one example, during establishment or operation of the PDU session <NUM>, a QoS feature, referred to as reflective QoS in 3GPP <NUM> system standards, can be enabled. For example, the SMF <NUM> can control the UPF <NUM> to associate a reflective QoS indication (RQI) with packets of a specific downlink QoS flow. The UE <NUM> can continuously monitor downlink traffic, and detect a packet carrying the RQI, and accordingly derive a QoS rule based on the detected packet. Then an uplink QoS flow corresponding to the downlink QoS flow can be identified and marked based on the derived QoS rule.

<FIG> shows an example packet mapping process <NUM> according to an embodiment of the disclosure. The process <NUM> can take place at the UE <NUM> in <FIG> after the session <NUM> and QoS flows of the session <NUM> are established. The process <NUM> can include two levels of mapping. With respect to user plane protocol stack at the UE <NUM>, the first level mapping can be operated in non-access stratum (NAS) <NUM>, while the second level mapping can be operated in access stratum (AS). Specifically, the AS mapping operation can be performed by a service data adaptation protocol (SDAP) layer. SDAP is a new user plane protocol added to AS as specified in 3GPP <NUM> system standards.

During the first level NAS mapping, uplink traffic is mapped to QoS flows. As shown, traffic <NUM> (such as IP packets or Ethernet packets, depending on a session type), is generated from applications <NUM>. Then, packet filters <NUM> A-E are employed to classify packets of the traffic <NUM> into QoS flows <NUM> F1-F3. The packet filters <NUM> can be specified in a group of QoS rules, for example, provided by the SMF <NUM> when the session <NUM> is established. Each of the QoS packet flows <NUM> can be associated with a QFI according to the QoS rules. Thus, after the classification, each packet is associated with a QFI, which is referred to as a marking operation. The QFI can be referred to as a marker. Carrying a marker, a packet can be treated accordingly to receive a certain level of service corresponding to the marker.

During the second level AS mapping, the QoS flows <NUM> are further mapped to data radio bearers <NUM> B1-B2. For example, the SDAP layer can perform a data radio bearer mapping <NUM> to map each packet to a data radio bearer <NUM>. Each data radio bearer <NUM> is a logical connection between the UE <NUM> and the AN <NUM>. Different data radio bearers can receive differentiated radio transmission services. In addition, the SDAP layer may encapsulate a packet with an SDAP header. The QFI associated with this IP packet can be carried in this SDAP header.

<FIG> shows an example mapping table <NUM> according to an embodiment of the disclosure. The mapping table <NUM> can be stored in the UE <NUM>, and used to perform the NAS mapping in <FIG> example. The mapping table <NUM> includes a set of QoS rules each included in a row <NUM>-<NUM> of the mapping table <NUM>. Each QoS rule includes a set of parameters listed in each column <NUM>-<NUM> of the table <NUM>. The set of parameters can be a QoS rule ID which is unique within a PDU session, a precedence value, a set of packet filters for identify an associated QoS flow, a QFI of the associated QoS flow. The QoS rule with ID of <NUM> is a default QoS rule and does not include a packet filter in <FIG> example. In <FIG> example, the mapping table <NUM> is associated with a PDU session of IP type. Thus, the set of packet filters in column <NUM> are created using <NUM> tuples of IP packets. In various examples, packets of different types of PDU sessions may have different packet formats. Accordingly, packet filters can be created in different ways.

The QoS rule precedence value determines an order in which a QoS rule is evaluated. For example, during the NAS mapping, the UE <NUM> evaluates the uplink packets against the packet filters included in the mapping table <NUM> based on the precedence values in increasing order until a matching QoS rule is found. For example, the QoS rules with IDs of <NUM>-<NUM> and precedence values of <NUM>, <NUM>, <NUM>, <NUM>, respectively will be evaluated in the following order (represented with the QoS rule IDs): <NUM>, <NUM>, <NUM>, and <NUM>. The default QoS rule does not have a packet filter and is evaluated as the last one. When no matching QoS rule is found for a packet and the default QoS rule includes a packet filter, the packet is discarded.

In one example, the QoS rules in the mapping table <NUM> can be explicitly provided to the UE <NUM>, for example, using a PDU session establishment or modification procedure. In another example, the QoS rules can be preconfigured in the UE <NUM>. In a further example, the QoS rules can be implicitly derived by the UE <NUM> by applying reflective QoS.

<FIG> shows an example process <NUM> for creating a derived QoS rule based on downlink traffic according to an embodiment of the disclosure. Reflective QoS enables the UE <NUM> to create derived QoS rules for mapping uplink traffic to QoS flows without the SMF <NUM> providing QoS rules. In this way, signaling cost for providing QoS rules to the UE <NUM> can be saved. When the CN <NUM> determines to use reflective QoS for a QoS flow, the SMF <NUM> can control the UPF <NUM> to mark RQIs on downlink packets of this QoS flow. The UE <NUM> can monitor downlink traffic to detect packets that carry the RQIs, and accordingly create derived QoS rules based on detected packets. When the CN <NUM> determines to stop using reflective QoS for this QoS flow, the SMF <NUM> can control the UPF <NUM> to stop marking of the RQIs.

In <FIG>, a downlink packet <NUM> includes a SDAP header <NUM> and a packet <NUM> (such as an IP packet or Ethernet packet). The packet <NUM> can include a packet header <NUM> and a packet payload <NUM>. The SDAP header <NUM> carries a QFI indicating a QoS flow to which the packet <NUM> belongs. The SDAP header <NUM> also carries an RQI indicating reflective QoS is enabled for uplink traffic corresponding to the downlink QoS flow to which the packet <NUM> belongs.

The UE <NUM> can inspect the SAP header <NUM> to detect the RQI while monitoring downlink traffic, and create a derived QoS rule <NUM> based on the downlink packet <NUM>. The derived QoS rule <NUM> can include a QoS rule ID <NUM>, a precedence value <NUM>, a packet filter <NUM>, and a QFI <NUM>. The QFI <NUM> can be set to the QFI carried in the SDAP header <NUM>. The packet filter <NUM> can be created based, for example, <NUM> tuples carried in the packet header <NUM>. In addition, a timer <NUM> can be associated with the derived QoS rule <NUM>, and triggered. The timer <NUM> can be initiated with a reflective QoS (RQ) timer value that is provided from the CN <NUM>, such as the SMF <NUM>. Alternatively, the timer <NUM> can be set to a default RQ timer value.

In one example, when the downlink packet <NUM> is detected to carry the RQI, the UE <NUM> can first create the packet filter <NUM>, and search existing QoS rules in the UE <NUM> to see if a QoS rule having the packet filter <NUM> has been created already. If not, the UE <NUM> can create the derived QoS rule <NUM> in the above described way. If the derived QoS rule <NUM> has been created before, the UE <NUM> can restart the timer <NUM>. In addition, if the RQI carried in the downlink packet <NUM> is different from that of the previously created QoS rule, the RQI of the previously created QoS rule will be updated. When the timer <NUM> expires, the derived QoS rule <NUM> is removed.

The precedence value <NUM> can be provided in different ways in various examples. In a first example, a reflective QoS precedence value for a PDU session is provided when the PDU session is established. For example, the SMF <NUM> transmits a message during a session establishment procedure indicating a precedence value for this session. For example, the indicated precedence value is associated with a session ID of the PDU session and can be used for each derived QoS rule of this PDU session.

In a second example, a reflective QoS precedence value is provided for a downlink QoS flow when the downlink QoS flow is established. For example, the SMF <NUM> can transmit a message indicating a precedence value for a downlink QoS flow when the respective downlink QoS flow is established. The precedence value can be associated with a QFI, and used for a derived QoS rule including the QFI. A downlink QoS flow can be established during a PDU session establishment procedure, or be added to the established PDU session later during a PDU session modification procedure. Alternatively, in the above first and second examples, the reflective QoS precedence value can be provided when reflective QoS is enabled by the SMF <NUM>.

In a further example, an operator defined value can be used as the precedence value <NUM> for a PDU session or a QoS flow. For example, the operator defined precedence value can be stored in a subscriber identity module (SIM), or storage of the UE <NUM>, and extracted when needed. Alternatively, the operator defined precedence value can be provided from the AN <NUM>, for example, by radio resource control (RRC) signaling, medium access control (MAC) layer signaling, broadcasted system information, and the like. The operator defined value can be provided from the AN <NUM> when the respective PDU session or the QoS flow is established, or when reflective QoS is enabled.

Derived QoS rules can be modified (e.g., changing a precedence value or QFI) or removed once the derived QoS rules are not needed. In various examples, there are different control schemes to realize modification or deletion of derived QoS rules.

A first scheme is by using a timer initiated with an RQ timer value and associated with a respective QoS rule, as described above. When no RQI is detected for a QoS flow for a time period equal to the RQ timer value, the timer expires, and the respective QoS rule can be removed. In one example, an RQ timer value for a PDU session can be provided to the UE <NUM> when the PDU session is established or when reflective QoS is enabled for the PDU session. For example, the SMF <NUM> can transmit a message indicating the RQ timer value (a life time of derived QoS rules) and an associated PDU session ID. Accordingly, a derived QoS rule of the PDU session can use the RQ timer value to set a timer or update the timer. In addition, in one example, the SMF <NUM> can transmit a message indicating a new RQ timer value for the PDU session to replace the previous RQ timer value while the PDU session being maintained.

A second scheme is by transmitting a dedicated message, for example, from the SMF <NUM> to modify or remove derived QoS rules of a PDU session. For example, the SMF <NUM> can transmit a message to the UE <NUM> indicating a session ID of the PDU session, and an operation code of modification or deletion. The UE <NUM> can receive the message, and accordingly modify or delete the derived QoS rules of the PDU session. For example, for modification, the UE <NUM> can update precedence values and/or QFIs of the derived QoS rules. Alternatively, the SMF <NUM> can transmit a message to the UE <NUM> indicating the session ID, a set of QFIs, and an operation code of modification or deletion. Accordingly, the UE <NUM> can perform modification or deletion on derived QoS rules corresponding to the indicated QFIs.

A third scheme is that the UE <NUM> can request the SMF <NUM> to remove existing derived QoS rules of a PDU session. For example, the UE <NUM> can transmit a session modification message to the SMF <NUM>. The message can indicate a session ID of the PDU session, thus the SMF <NUM> can disable reflective QoS for QoS flows corresponding to the existing derived QoS rules, for example, stopping to insert RQI to downlink packets of those QoS flows. Alternatively, the message can specify the session ID and a set of QFIs corresponding to a set of derived QoS rules. As a result, the SMF <NUM> can disable reflective QoS for QoS flows corresponding to the specified set of QFIs. Subsequently, respective existing derived QoS rules can be removed when associated timers expires. Alternatively, the SMF <NUM> may reply with a message to accept the request. The UE <NUM> can remove the respective existing derived QoS rules after receiving the accept message even associated timers do not expire.

As described above, reflective QoS is controlled on per-packet basis by associating an RQI with a packet. The UE <NUM> continuously monitors each downlink packet of the respective PDU session in order to detect a packet marked with an RQI, which is a burden for the UE <NUM>. To release the UE <NUM> from the burden, a message can be transmitted to the UE <NUM> to start or stop the monitoring operation for reflective QoS, according to aspects of the disclosure.

For example, when the SMF <NUM> is going to enable reflective QoS, the SMF <NUM> can transmit a message informing the UE <NUM> to start the monitoring operation. The message may specify one or more PDU session IDs, and/or one or more QFIs corresponding to respective PDU session IDs. The UE <NUM> receives the message and accordingly starts to monitor traffic corresponding to specified PDU sessions, or QoS flows. When the SMF <NUM> disables previously enabled reflective QoS of a session, or a QoS flow, the SMF <NUM> can transmit a message to the UE <NUM> indicating the respective session, or QoS flow. The UE <NUM> may accordingly stop respective monitoring operations.

In alternative examples, the message for starting or stopping the monitoring operation for reflective QoS can be transmitted from the AN <NUM>. For example, the SMF <NUM> may inform the AN <NUM> about the enabling or disabling of reflective QoS in order to control QoS operations performed at the AN <NUM>. The AN <NUM> can subsequently inform the UE <NUM> the start or end of reflective QoS. The message from the AN <NUM> can similarly specify which PDU sessions, QoS flows, and/or radio bearers are going to be enabled or disabled with reflective QoS. The message from the AN <NUM> can be in the form of RRC signaling, packet data convergence protocol (PDCP) control data unit, system information, broadcast information, and the like.

An alternative scheme for controlling the reflective QoS monitoring operations is that the SMF <NUM> can transmit a message indicating whether the CN <NUM> supports reflective QoS or not. For example, the CN <NUM> may be configured not to support reflective QoS, or the CN <NUM> determines not to support reflective QoS for certain PDU sessions. The message indicating whether the CN <NUM> supports reflective QoS or not can be transmitted to the UE <NUM> when a session is established. Alternatively, the message can be transmitted to the UE <NUM> in advance of establishment of a session, for example, when the UE <NUM> is connected to the CN <NUM>.

In one example, the UE <NUM> can be configured by default to start to perform reflective QoS monitoring for detection of an RQI in downlink packets when a PDU session is established. When the UE <NUM> receives a message from the CN <NUM> indicating the CN <NUM> does not support reflective QoS, the UE <NUM> can stop the monitoring operation. In one example, the UE <NUM> does not start a reflective QoS monitoring when a PDU session is established. When the UE <NUM> receives a message from the CN <NUM> indicating the CN <NUM> supports reflective QoS for the respective PDU session, the UE <NUM> can start to perform reflective QoS monitoring for the respective PDU session. Later, when the UE <NUM> receives a message from the CN <NUM> indicating the CN <NUM> does not support reflective QoS for the PDU session anymore, the UE <NUM> can stop the reflective QoS monitoring for the PDU session.

In a further scheme for controlling the reflective QoS monitoring operations, the UE <NUM> can initiate to request the CN <NUM> to stop supporting reflective QoS for one or more PDU sessions. For example, the UE <NUM> can transmit a PDU session modification message specifying a set of PDU session IDs for stopping reflective QoS support. Alternatively, the UE <NUM> can transmit a PDU session modification message indicating stopping reflective QoS support for all sessions. The SMF <NUM> may reply a message to accept the request of the UE <NUM>. Upon receiving the accept message, the UE <NUM> can stop reflective QoS monitoring operations for respective PDU sessions or all PDU sessions.

<FIG> shows a flowchart of an example reflective QoS control and management process <NUM> according to some embodiments of the disclosure. During the process <NUM>, messages are transmitted between the SFM <NUM> and the UE <NUM>.

At S511, the UE <NUM> receives QoS rules for uplink traffic classification and marking. S511 can be part of a PDU session establishment procedure <NUM> for establishment of a PDU session.

At S512, the UE <NUM> receives a message indicating whether reflective QoS is supported for the session by the CN <NUM>. If reflective QoS is not supported for the session, the UE <NUM> will not start reflective QoS monitoring. If the UE <NUM> is configured to start reflective QoS monitoring by default when the session is established, the UE <NUM> will stop the default monitoring upon receiving the message. If reflective QoS is supported for the session, the UE <NUM> will start to monitor downlink traffic of the session as indicated at S515.

At S513, the UE <NUM> receives precedence values(s) for reflective QoS. The precedence value can be assigned for this PDU session. Thus, reflective QoS rules of the PDU session can use the precedence value when created. Alternatively, the precedence values can be assigned for QoS flows and are associated with QFIs of the QoS flows. When a reflective QoS rule including one of the QFIs is created, a respective precedence value is used. In other examples, a precedence value defined for a QoS flow can be provided by the SMF <NUM> when the QoS flow is added to an existing PDU session during a PDU session modification procedure.

Also at S513, the UE <NUM> receives an RQ timer value for the session established during the session establishment procedure <NUM>. For example, the CN <NUM> supports reflective QoS, and subsequently transmits a message including the RQ timer value. Similarly, S512 and S513 can be performed during the session establishment procedure <NUM>.

AS514, the UE <NUM> performs classification and marking based on the received QoS rules to map uplink traffic to respective QoS flows.

At <NUM>, the UE <NUM> continuously monitors downlink traffic of the PDU session or QoS flows indicated at S514 to detect packets carrying an RQI.

At S516, the UE <NUM> creates a derived QoS rule as a result of detecting a downlink packet carrying an RQI, and starts a timer associated with the derived QoS rule. The precedence value received at S511 can be set as the precedence of the derived QoS rule, and the RQ timer value received at S513 can be set as the initial value of the timer.

At S517, the UE <NUM> can update the derived QoS rules when another downlink packet carrying the same RQI is detected. The timer can be restarted.

At S518, the UE <NUM> can remove the derived QoS rules when the timer expires.

At S519, the UE <NUM> can create one or more derived QoS rules after detecting downlink packets carrying RQIs.

At S520, the UE <NUM> can receive a message for modifying or removing the one or more derived QoS rules created at S519. For example, the message may specify the PDU session ID, and an operation code of modification or deletion.

At S521, the UE <NUM> can modify or remove the one or more derived QoS rules based on the message received at S520.

At S522, the UE <NUM> can initiate to transmit a message for removing derived QoS rules. For example, after S521, one or more derived QoS rules are created. The UE <NUM> can specify the PDU session ID of the session, or the PDU session ID of the session and a set of QFIs in the message. By receiving the message, the SMF <NUM> can stop RQI insertion operations performed on packets of the session, or packets of QoS flows corresponding to the specified QFIs. Additionally, the SMF <NUM> can reply an accept message. The UE <NUM> can remove the respective derived QoS rules upon receiving the accept message.

At <NUM>, the UE <NUM> can receive a message for stopping a monitoring operation performed on a QoS flow. For example, the message can specify a PDU session ID of the PDU session and a QFI of the QoS flow.

At S524, the UE <NUM> can stop the respective monitoring operation according to the message received at S522.

At S525, the UE <NUM> can initiate to transmit a message for stopping reflective QoS support for the session established during the session establishment procedure <NUM>. Upon receiving the message, the CN <NUM> may stop reflective QoS operations for the session accordingly.

At S526, the UE <NUM> can receive a message from the CN <NUM> accepting the request at S525.

At S527, the UE <NUM> can stop the reflective QoS monitoring for the session. The process <NUM> can then terminated.

<FIG> shows an exemplary block diagram of a UE <NUM> according to an embodiment of the disclosure. The UE <NUM> can be configured to implement various embodiments of the disclosure described herein. The UE <NUM> can include a processor <NUM>, a memory <NUM>, and a radio frequency (RF) module <NUM> that are coupled together as shown in <FIG>. In different examples, the UE <NUM> can be a mobile phone, a tablet computer, a desktop computer, a vehicle carried device, and the like.

The processor <NUM> can be configured to perform various functions of the UE <NUM> as described above with reference to <FIG>. The processor <NUM> can include signal processing circuitry operating according to communication protocols specified in, for example, 3GPP LTE and <NUM> system standards. Additionally, the processor <NUM> may execute program instructions, for example, stored in the memory <NUM>, to perform functions related with different communication protocols. The processor <NUM> can be implemented with suitable hardware, software, or a combination thereof. For example, the processor <NUM> can be implemented with application specific integrated circuits (ASIC), field programmable gate arrays (FPGA), and the like, that includes circuitry. The circuitry can be configured to perform various functions of the processor <NUM>.

In one example, the memory <NUM> can store program instructions that, when executed by the processor <NUM>, cause the processor <NUM> to perform various functions as described herein. The memory <NUM> can include a read only memory (ROM), a random access memory (RAM), a flash memory, a solid state memory, a hard disk drive, and the like.

The RF module <NUM> can be configured to receive a digital signal from the processor <NUM> and accordingly transmit a signal to a base station in a wireless communication network via an antenna <NUM>. In addition, the RF module <NUM> can be configured to receive a wireless signal from a base station and accordingly generate a digital signal which is provided to the processor <NUM>. The RF module <NUM> can include digital to analog/analog to digital converters (DAC/ADC), frequency down/up converters, filters, and amplifiers for reception and transmission operations. For example, the RF module <NUM> can include converter circuits, filter circuits, amplification circuits, and the like, for processing signals on different carriers or bandwidth parts.

The UE <NUM> can optionally include other components, such as input and output devices, additional CPU or signal processing circuitry, and the like. Accordingly, the UE <NUM> may be capable of performing other additional functions, such as executing application programs, and processing alternative communication protocols.

The processes and functions described herein can be implemented as a computer program which, when executed by one or more processors, can cause the one or more processors to perform the respective processes and functions. The computer program may be stored or distributed on a suitable medium, such as an optical storage medium or a solid-state medium supplied together with, or as part of, other hardware. The computer program may also be distributed in other forms, such as via the Internet or other wired or wireless telecommunication systems. For example, the computer program can be obtained and loaded into an apparatus, including obtaining the computer program through physical medium or distributed system, including, for example, from a server connected to the Internet.

Claim 1:
A method for reflective quality of service, QoS control and management for a user equipment, UE (<NUM>), the method comprising:
receiving, by the UE, a downlink packet in a session, the downlink packet including a QoS flow identifier, QFI;
deriving, by the UE, a first QoS rule according to the QFI, wherein the downlink packet is marked with the QFI, and the first QoS rule derived by the UE is for the session and having the QFI; setting a precedence value of the first QoS rule derived by the UE to:
a precedence value associated with a session identifier, ID, of the session received from a core network, CN (<NUM>), of a wireless communication system during a session establishment procedure for establishing the session, or a predefined precedence value, or
a precedence value associated with the QFI received from the CN (<NUM>) during the session establishment procedure for establishing the session, or when a downlink QoS flow having the QFI is added to the session, or a precedence value that is defined by an operator of the wireless communication system;
receiving a message from the CN (<NUM>) indicating the session ID of the session and a first reflective QoS, RQ, timer value; and
starting a timer associated with the derived first QoS rule, the timer set to the first RQ timer value indicating a life time of the derived first QoS rule;
wherein the precedence value corresponds to an order for evaluating the first QoS rule derived by the UE for transmitting an uplink packet in the session when at least one other QoS rule for the session is available.