Default quality of service rule management method and user equipment

Abstract

This invention proposes a method and user equipment (UE) for managing default QoS rules for PDU sessions. A PDU session defines the association between the UE and the data network providing PDU connection services. Each PDU session is identified by a PDU session ID and includes multiple QoS flows and QoS rules. More than one QoS rule may exist associated with the same QoS flow. For each PDU session establishment, a default QoS rule needs to be sent to the UE, and this rule is associated with a QoS flow. There should be one and only one default QoS rule in a PDU session. According to a novel aspect, UE behavior and error handling for appropriate QoS rule management are defined for the PDU session establishment and modification process to enforce the policy of having one and only one default QoS rule.

Description

[0001] Cross-referencing

[0002] This invention claims priority to the following U.S. Provisional Patent Application No. 62 / 655,137, filed April 9, 2018, entitled "5GSM Enhancement on Interworking", which is incorporated herein by reference. Technical Field

[0003] This invention generally relates to wireless communication, and more specifically, to a method for managing Quality of Service (QoS) rules in 5th Generation (5G) new radio (NR) systems. Background Technology

[0004] Over the years, wireless communication networks have grown exponentially. Long-Term Evolution (LTE) systems offer high peak data rates, low latency, improved system capacity, and low operating costs due to their simple network architecture. LTE systems, also known as 4th Generation (4G) systems, also provide seamless integration with older networks such as Global System for Mobile Communications (GSM), Code Division Multiple Access (CDMA), and Universal Mobile Telecommunications System (UMTS). In LTE systems, the evolved universal terrestrial radio access network (E-UTRAN) comprises multiple evolved Node-Bs (eNodeBs or eNBs) that communicate with multiple mobile stations called user equipment (UEs). The 3rd Generation Partnership Project (3GPP) rd Generation Partner Project (3GPP) networks typically include a mix of 2nd Generation (2G), 3rd Generation (3G), and 4G systems. The Next Generation Mobile Network (NGMN) Board has decided to focus future NGMN activities on defining the end-to-end requirements for 5G NR systems.

[0005] QoS indicates performance from the network user's perspective. In LTE Evolved Packet System (EPS), QoS is managed based on EPS bearers in the Evolved Packet Core (EPC) and Radio Access Network (RAN). In 5G networks, QoS flows represent the optimal granularity for QoS management, enabling more flexible QoS control. The concept of a QoS flow is similar to that of an EPS bearer. All types of traffic mapped to the same LTE EPS bearer or the same 5G QoS flow receive the same level of packet forwarding processing (e.g., scheduling policies, queue management policies, rate shaping policies, Radio Link Control (RLC) configuration, etc.). It is assumed that different QoS forwarding processes require their own 5G QoS flows. Each QoS flow includes multiple QoS rules, which consist of a QoS profile, packet filters, and priorities. The QoS profile includes QoS parameters and QoS tags. Packet filters are used to bind QoS flows to specific QoS tags. Priorities represent the priority at which QoS rules adapt to QoS flows. The UE classifies and labels uplink (UL) user plane traffic, that is, it associates UL traffic with QoS flow based on QoS rules.

[0006] In 5G, Protocol Data Unit (PDU) session establishment is a parallel process to the Packet Data Network (PDN) connection process in 4G. A PDU session defines the association between the UE and the data network providing PDU connection services. Each PDU session is identified by a PDU session identification (ID) and includes multiple QoS flows and QoS rules. Each QoS flow is identified by a unique QoS flow ID (QFI) within the PDU session. Each QoS rule is identified by a QoS rule ID (QRI). More than one QoS rule can exist associated with the same QoS flow. For each PDU session establishment, a default QoS rule needs to be sent to the UE, and this rule is associated with a QoS flow.

[0007] In a PDU session, there should be one and only one default QoS rule. However, the network may send multiple QoS rules to the UE as the default QoS rule, the network may want to delete the default QoS rule, and the network may want to modify the default QoS rule. Therefore, for proper QoS rule management, UE behavior and error handling need to be defined. Summary of the Invention

[0008] A method for managing default QoS rules for PDU sessions is proposed. A PDU session defines the association between the UE and the data network providing PDU connectivity services. Each PDU session is identified by a PDU session ID and includes multiple QoS flows and QoS rules. Each QoS flow is identified by a unique QFI within the PDU session. Each QoS rule is identified by a QRI. More than one QoS rule can exist associated with the same QoS flow. For each PDU session establishment, a default QoS rule needs to be sent to the UE, and this rule is associated with a QoS flow. There should be one and only one default QoS rule in a PDU session. UE behavior and error handling are defined for the PDU session establishment and modification process to enforce the policy of having one and only one default QoS rule for appropriate QoS rule management.

[0009] In one embodiment, the UE sends a PDU session establishment request in a mobile communication network. The UE receives a PDU session establishment acceptance from the network. The PDU session establishment acceptance instructs the UE to establish a PDU session and create one or more QoS rules and one or more QoS flows. When the UE determines that the network has set more than one QoS rule as the default QoS rule for the PDU session, the UE releases the PDU session.

[0010] In another embodiment, the UE establishes a PDU session in the mobile communication network. The PDU session is associated with a default QoS rule. The UE receives a PDU session modification command from the network. The PDU session modification command includes a command to modify the default QoS rule of the PDU session. The UE determines whether the PDU session modification command will cause a conflict with the default QoS rule policy. When a conflict with the default QoS rule policy is determined, the UE rejects the PDU session modification command or releases the PDU session. In one example, the PDU session modification command is used to instruct the UE to add another QoS rule as the default QoS rule. The UE rejects the PDU session modification command by sending a PDU session modification command rejection message with an error code. In another example, the PDU session modification command is used to instruct the UE to delete the default QoS rule, delete all packet filters in the default QoS rule, or change the default QoS rule (DQR) setting. The UE releases the PDU session by sending a PDU session release request.

[0011] The default QoS rule management method of the present invention and the user equipment executing the method can enforce one and only one default QoS rule in a protocol data unit session to avoid UE and network behavior errors.

[0012] Other embodiments and advantages are described in the following detailed description. This summary is not intended to define the invention. The invention is defined by the claims. Attached Figure Description

[0013] The accompanying drawings illustrate embodiments of the invention, wherein the same numbers denote the same components.

[0014] Figure 1 An exemplary EPS / 5G system (5GS) network supporting QoS rule management based on novel aspects is described.

[0015] Figure 2 A simplified block diagram of a UE and network entities according to embodiments of the present invention is described.

[0016] Figure 3 A first embodiment of QoS rule management for the PDU session establishment process based on novel aspects is described.

[0017] Figure 4 A second embodiment of QoS rule management for the PDU session establishment process based on novel aspects is described.

[0018] Figure 5 A first embodiment of QoS rule management for a PDU session modification process that adds default QoS rules based on novel aspects is described.

[0019] Figure 6 A second embodiment of QoS rule management for a PDU session modification process that adds default QoS rules based on novel aspects is described.

[0020] Figure 7 A first embodiment of QoS rule management for a PDU session modification process that deletes default QoS rules based on novel aspects is described.

[0021] Figure 8 A second embodiment of QoS rule management for a PDU session modification process that deletes default QoS rules based on novel aspects is described.

[0022] Figure 9 This is a flowchart illustrating the method for managing QoS rules based on novel aspects of PDU sessions.

[0023] Figure 10 This is a flowchart of a method for managing QoS rules based on novel aspects of PDU sessions. Detailed Implementation

[0024] Reference will now be made in detail to some embodiments of the present invention, examples of which are shown in the accompanying drawings.

[0025] Figure 1 An exemplary LTE / NR network (also referred to as an EPS and 5GS network) 100 supporting QoS rule management based on novel aspects is described. The LTE / NR network 100 includes an application server 111, which provides various services by communicating with multiple UEs, including UE 114. Figure 1 In the example, application server 111 and packet data network gateway (PDN-GW or P-GW) 113 are part of core network (CN) 110. UE 114 and its serving base station (BS) 115 are part of RAN 120. RAN 120 provides radio access to UE 114 via radioaccess technology (RAT). Application server 111 communicates with UE 114 through PDN GW 113, serving GW 116, and BS 115. Mobility management entity (MME) or access and mobility management function (AMF) 117 communicates with BS 115, serving GW 116, and PDN GW 113 for access and mobility management of radio access devices in LTE / NR network 100. The UE114 is configured with one or more radio frequency (RF) transceivers to provide different application services through different RAT / CNs. The UE114 can be a smartphone, wearable device, Internet of Things (IoT) device, tablet computer, etc.

[0026] EPS and 5GS networks are packet-switched (PS) Internet Protocol (IP) networks. This means the network sends all data traffic in IP packets and provides users with always-on IP connectivity. When a UE joins an EPS / 5GS network, a PDN address (i.e., an address that can be used on the PDN) can be assigned to the UE, enabling it to connect to the PDN. EPS refers to the UE's "IP access connection" as the EPS bearer, which is the connection between the UE and the P-GW. The P-GW is the default gateway for the UE's IP access. EPS has defined a default EPS bearer to provide always-on IP connectivity.

[0027] In 5G, PDU session establishment is a parallel process to the PDN connection process in 4G. A PDU session defines the association between the UE and the data network providing PDU connection services. Each PDU session is identified by a PDU session ID and includes multiple QoS flows and QoS rules. Each QoS flow is identified by a unique QFI within the PDU session. Each QoS rule is identified by a QRI. More than one QoS rule can exist associated with the same QoS flow. For each PDU session establishment, a default QoS rule needs to be sent to the UE, and this rule is associated with the QoS flow.

[0028] In a PDU session, there should be one and only one default QoS rule. However, the network may send multiple QoS rules to the UE as the default QoS rule, the network may want to delete the default QoS rule, and the network may want to modify the default QoS rule. According to a novel aspect, for proper QoS rule management, UE behavior and error handling need to be defined for the PDU session establishment process and the PDU session modification process. Figure 1 In the examples, UE 114 performs a PDU session establishment or modification process with the network via non-access stratum (NAS) signaling 130. During PDU session establishment or modification, UE 114 performs QoS rule management as shown in box 140. In the first example, if a new QoS rule is added as the default QoS rule, UE 114 rejects the PDU session modification command. In the second example, if more than one QoS rule is set as the default QoS rule for the PDU session, UE 114 releases the newly established QoS session. In the third example, if the default QoS rule of the PDU session is to be deleted by the PDU session modification command, UE 114 releases the existing PDU session.

[0029] Figure 2A simplified block diagram of a wireless device 200 (e.g., UE 201 and network entity 211) according to an embodiment of the present invention is described. Network entity 211 may be a base station combined with an MME or AMF. Network entity 211 has an antenna 215 that transmits and receives radio signals. An RF transceiver 214 is coupled to the antenna 215, receives RF signals from the antenna 215, converts them into baseband signals, and sends them to a processor 213. The RF transceiver 214 also converts baseband signals received from the processor 213, converts them into RF signals, and sends them to the antenna 215. The processor 213 processes the received baseband signals and invokes different functional modules to perform functions within network entity 211. Memory 212 stores program instructions and data 220 to control the operation of network entity 211. Protocol stack 280 includes a NAS layer for communicating with MME or AMF entities connected to the core network, a Radio Resource Control (RRC) layer for higher-level configuration and control, a Packet Data Convergence Protocol / Radio Link Control (PDCP / RLC) layer, a Media Access Control (MAC) layer, and a Physical (PHY) layer. Figure 2 In the example, network entity 211 also includes a set of control function modules and circuitry 290. PDU session processing circuitry 231 handles the PDU session establishment and modification process. QoS flow and rule management circuitry 232 creates, modifies, and deletes QoS flows and QoS rules for the UE. Configuration and control circuitry 233 provides various parameters to configure and control the UE.

[0030] Similarly, UE 201 has memory 202, processor 203, and RF transceiver 204. RF transceiver 204 is coupled to antenna 205, receives RF signals from antenna 205, converts them into baseband signals, and sends them to processor 203. RF transceiver 204 also converts baseband signals received from processor 203 into RF signals and sends them to antenna 205. Processor 203 processes the received baseband signals and invokes different functional modules and circuits to perform functions in UE 201. Memory 202 stores program instructions and data 210 for the processor to control the operation of UE 201. Suitable processors include, for example, special purpose processors, digital signal processors (DSPs), multiple microprocessors, one or more microprocessors associated with a DSP core, controllers, microcontrollers, application-specific integrated circuits (ASICs), file-programmable gate arrays (FPGAs), and other types of integrated circuits (ICs) and / or state machines. The features of UE 201 can be implemented and configured using a software-associated processor.

[0031] UE 201 also includes a set of functional modules and control circuits that perform UE 201 functional tasks. Protocol stack 260 includes a NAS layer for communicating with MME or AMF entities connected to the core network, an RRC layer for higher-level configuration and control, a PDCP / RLC layer, a MAC layer, and a PHY layer. System modules and circuits 270 can be implemented and configured by hardware, firmware, software, or any combination thereof. When the processor executes functional modules and circuits via program instructions in memory, they cooperate to enable UE 201 to perform implementation schemes, functional tasks, and features within the network. In one example, system modules and circuits 270 include PDU session processing circuitry 221 that performs the PDU session establishment and modification process with the network, QoS rule management circuitry 222 that determines any conflicts with default QoS rules and handles QoS rule management, and configuration and control circuitry 223 that handles configuration and control parameters.

[0032] Figure 3A first embodiment of QoS rule management for a PDU session establishment process based on novel aspects is described. In step 311, UE 301 sends a PDU session establishment request to network 302. A PDU session is defined as an association between the UE and the data network providing PDU connectivity services. In step 321, UE 301 receives a PDN session establishment acceptance from network 302. This acceptance message includes instructions instructing UE 301 to create one or more QoS flows and one or more QoS rules for the PDU session. In a 5G network, all types of traffic mapped to the same 5G QoS flow receive the same level of packet forwarding processing (e.g., scheduling policies, queue management policies, rate forming policies, RLC configuration, etc.). It is assumed that different QoS forwarding processes require their own 5G QoS flows. Each QoS flow includes multiple QoS rules, which consist of QoS profiles, packet filters, and priorities. The UE classifies and labels UL user plane traffic, i.e., associating UL traffic with QoS flows based on QoS rules.

[0033] Each PDU session is identified by a PDU session ID and includes multiple QoS flows and QoS rules. Each QoS flow is identified by a unique QFI within the PDU session. Each QoS rule is identified by a QRI. More than one QoS rule can exist associated with the same QoS flow. For each PDU session establishment, a default QoS rule needs to be sent to the UE, and this rule is associated with a QoS flow. When establishing a PDU session and creating different QoS flows and QoS rules, each QoS rule has a DQR indicator indicating whether "this QoS rule is the default QoS rule". There should be one and only one default QoS rule in a PDU session.

[0034] However, in step 321, UE 301 may receive multiple QoS rules for the PDU session, with DQR indicators set to "this QoS rule is the default QoS rule," which conflicts with the default QoS rule policy (each PDU session should have one and only one default QoS rule). In step 331, UE 301 evaluates the PDU session establishment accept message and determines whether the network has instructed the UE to create multiple default QoS rules. If there is no conflict, the established PDU session is fine. Otherwise, if there is a conflict between the default QoS rule policy and the multiple default QoS rules to be created for the PDU session, then in step 341, UE 301 needs to decide how to handle the established PDU session. For example, UE 301 can establish and then release the PDU session, or ignore the PDU session establishment and release the PDU session locally, or send a 5GSM message to the network with an appropriate reason (e.g., PDU#N DQR mismatch or PDU#N DQR error).

[0035] Figure 4 A second embodiment of QoS rule management for the PDU session establishment process, based on novel aspects, is described. For the PDU session establishment process, Figure 4 Steps 411-431 and Figure 3 Similar to steps 311-331. In step 431, UE 401 determines that network 402 has instructed the UE to create multiple default QoS rules for the PDU session, which creates a conflict with the default QoS rule policy. Figure 4 In this embodiment, UE 401 explicitly releases the established PDU session to resolve the conflict. In step 441, UE 401 sends a PDU session release request to network 402. In step 451, UE 401 receives a PDU session release command from network 402. In step 461, the UE releases the PDU session and confirms the release by sending a PDU session release completion message to network 402. Note that the PDU session can be released implicitly, for example, locally within the UE. Optionally, the UE can initiate a registration update process to network 402 (e.g., by sending a registration request message) to synchronize the PDU session state.

[0036] Figure 5 A first embodiment of QoS rule management for a PDU session modification process that adds default QoS rules based on novel aspects is described. In step 510, UE 501 sends a PDU session modification request to network 502. The PDU session modification request includes a UE action (UE proposal) to create, modify, or delete one or more QoS flows and / or one or more QoS rules. In step 511, network 502 determines QoS parameters based on the UE action and based on network policies and states. In step 521, network 502 sends a PDU session modification command to UE 501. Figure 5 In this embodiment, the PDU session modification command includes one or more QoS rules with a DQR indication, wherein the DQR indication is set to "this QoS rule is the default QoS rule". Figure 5In another embodiment, the PDU session modification command includes modifying the DQR indication of an existing QoS rule from "this QoS rule is not the default QoS rule" to "this QoS rule is the default QoS rule". In step 531, when the PDU session modification command is received, UE 501 evaluates the command and checks whether the command will cause any conflict with the default QoS rule policy. When the UE determines that the command carries a new QoS rule with a DQR indication set to "this QoS rule is the default QoS rule", or modifies the DQR indication of an existing QoS rule from "this QoS rule is not the default QoS rule" to "this QoS rule is the default QoS rule", the UE knows that the command will create more than one default QoS rule and thus cause a conflict. In step 541, UE 501 sends a PDU session modification command rejection back to network 502, providing an appropriate reason (e.g., semantic error in QoS operation, DQR mismatch, or DQR error) to resolve the DQR conflict. In another embodiment of step 541, UE 501 sends a PDU session release request to network 502 with a suitable reason (e.g., a semantic error in QoS operation).

[0037] Figure 6 A second embodiment of QoS rule management for a PDU session modification process that adds default QoS rules based on novel aspects is described. Figure 6 and Figure 5 Similar. However, in Figure 6 In this embodiment, the PDU session modification process is initiated by the network, not the UE. In step 611, the network 602 determines QoS parameters based on network policies and states. In step 621, the network 602 sends a PDU session modification command to the UE 601. Figure 6 In this embodiment, the PDU session modification command includes one or more QoS rules with a DQR indication, wherein the DQR indication is set to "this QoS rule is the default QoS rule". Figure 6In another embodiment, the PDU session modification command includes modifying the DQR indication of an existing QoS rule from "this QoS rule is not the default QoS rule" to "this QoS rule is the default QoS rule". In step 631, when the PDU session modification command is received, UE 601 evaluates the command and checks whether the command will cause any conflict with the default QoS rule policy. When the UE determines that the command carries a new QoS rule with a DQR indication set to "this QoS rule is the default QoS rule", or modifies the DQR indication of an existing QoS rule from "this QoS rule is not the default QoS rule" to "this QoS rule is the default QoS rule", the UE knows that the command will create more than one default QoS rule and thus cause a conflict. In step 641, UE 601 sends a PDU session modification command rejection back to network 602, providing an appropriate reason (e.g., semantic error in QoS operation, DQR mismatch, or DQR error) to resolve the DQR conflict. In another embodiment of step 641, UE 601 sends a PDU session release request to network 602 with a suitable reason (e.g., a semantic error in QoS operation).

[0038] Figure 7 A first embodiment of QoS rule management for a PDU session modification process that deletes default QoS rules according to novel aspects is described. In step 710, UE 701 sends a PDU session modification request to network 702. The PDU session modification request includes UE operations such as creating, modifying, or deleting one or more QoS flows and / or one or more QoS rules. In step 711, network 702 determines QoS parameters based on the UE operation and based on network policies and states. In step 721, network 702 sends a PDU session modification command to UE 701. Figure 7In the embodiments described, the PDU session modification command includes QoS rule operations for deleting the default QoS rule, deleting all packet filters in the default QoS rule, or modifying the default QoS rule to change the DQR setting (i.e., setting the rule to a non-default QoS rule). In step 731, when the PDU session modification command is received, UE 701 evaluates the command and checks whether the command will cause any conflict with the default QoS rule policy. When the UE determines that the command carries a QoS rule operation that can effectively delete the existing default QoS rule, the UE knows that the command will cause a conflict for one and only one DRQ policy. That is, when the default QoS rule of the PDU session is deleted, a conflict can be determined to have occurred. In step 741, UE 701 sends a PDU session release request to network 702. In step 751, UE 701 receives a PDU session release command from network 702. In step 761, UE 701 sends a PDU session release completion message to network 702. In another embodiment of step 741, UE 701 sends a PDU session modification command rejection back to network 702, with an appropriate reason (e.g., semantic error in QoS operation).

[0039] Figure 8 A second embodiment of QoS rule management for a PDU session modification process that deletes default QoS rules based on novel aspects is described. Figure 8 and Figure 7 Similar. However, in Figure 8 In this embodiment, the PDU session modification process is initiated by the network, not the UE. In step 811, network 802 determines QoS parameters based on network policies and states. In step 821, network 802 sends a PDU session modification command to UE 801. Figure 8In one embodiment, the PDU session modification command includes QoS rule operations for deleting the default QoS rule, deleting all packet filters in the default QoS rule, or modifying the default QoS rule to change the DQR setting (i.e., setting the rule as a non-default QoS rule). In step 831, when the PDU session modification command is received, UE 801 evaluates the command and checks whether the command will cause any conflict with the default QoS rule policy. When the UE determines that the command carries a QoS rule operation that can effectively delete the existing default QoS rule, the UE knows that the command will cause a conflict for one and only one DRQ policy. In step 841, UE 801 sends a PDU session release request to network 802. In step 851, UE 801 receives the PDU session release command from network 802. In step 861, UE 801 sends a PDU session release completion message to network 802. In another embodiment of step 841, UE 801 sends a PDU session modification command rejection message back to network 802, giving an appropriate reason (e.g., a semantic error in the QoS operation).

[0040] Figure 9 This is a flowchart of a method for managing QoS rules based on a novel aspect of PDU session establishment. In step 901, the UE sends a PDU session establishment request in the mobile communication network. In step 902, the UE receives a PDU session establishment acceptance from the network. The PDU session establishment acceptance instructs the UE to establish a PDU session and create one or more QoS rules and one or more QoB flows. In step 903, when the UE determines that the network has set more than one QoS rule as the default QoS rule for the PDU session, the UE releases the PDU session.

[0041] Figure 10This is a flowchart of a method for managing QoS rules based on novel aspects of PDU session modification. In step 1001, the UE establishes a PDU session in the mobile communication network. The PDU session is associated with a default QoS rule. In step 1002, the UE receives a PDU session modification command from the network. The PDU session modification command includes a command to modify the default QoS rule of the PDU session. In step 1003, the UE determines whether the PDU session modification command will cause a conflict with the default QoS rule policy. In step 1004, when a conflict with the default QoS rule policy is determined, the UE rejects the PDU session modification command or releases the PDU session. In one example, the PDU session modification command is used to instruct the UE to add another QoS rule as the default QoS rule. The UE rejects the PDU session modification command by sending a PDU session modification command rejection message with an error code. In another example, the PDU session modification command is used to instruct the UE to delete the default QoS rule, delete all packet filters in the default QoS rule, or change the DQR settings. The UE releases the PDU session by sending a PDU session release request.

[0042] Although the invention has been described in conjunction with certain specific embodiments for guiding purposes, the invention is not limited thereto. Therefore, various modifications, adaptations, and combinations of various features of the described embodiments can be made without departing from the scope of the invention as set forth in the claims.

Claims

1. A default quality of service rule management method, characterized by, comprising: establishing, by a user equipment, a protocol data unit session in a mobile communication network, wherein the protocol data unit session is associated with a default quality of service rule; receiving a protocol data unit session modification command from the mobile communication network, wherein the protocol data unit session modification command comprises a command to perform a quality of service rule operation associated with the default quality of service rule of the protocol data unit session; determining whether the protocol data unit session modification command will result in a conflict with a default quality of service rule policy, wherein the conflict is determined when the quality of service rule operation comprises deleting the default quality of service rule; and releasing the protocol data unit session when the conflict with the default quality of service rule policy is determined.

2. The default quality of service rule management method of claim 1, further comprising: sending a protocol data unit session modification request to the mobile communication network and receiving the protocol data unit session modification command in response.

3. The default quality of service rule management method of claim 2, wherein, the protocol data unit session modification request comprises a user equipment operation associated with creating, modifying, or deleting a quality of service rule.

4. The default quality of service rule management method of claim 1, wherein, the default quality of service rule policy enforces exactly one default quality of service rule per established protocol data unit session.

5. The default quality of service rule management method of claim 1, wherein, the user equipment releases the protocol data unit session by sending a protocol data unit session release request.

6. A default quality of service rule management method characterized by, comprising: establishing, by a user equipment, a protocol data unit session in a mobile communication network, wherein the protocol data unit session is associated with a default quality of service rule; receiving a protocol data unit session modification command from the mobile communication network, wherein the protocol data unit session modification command comprises a command to perform a quality of service rule operation associated with the default quality of service rule of the protocol data unit session; determining whether the protocol data unit session modification command will result in a conflict with a default quality of service rule policy, wherein the conflict is determined when the quality of service rule operation comprises deleting all packet filters within the default quality of service rule; and releasing the protocol data unit session when the conflict with the default quality of service rule policy is determined.

7. The default quality of service rule management method of claim 6, further comprising: sending a protocol data unit session modification request to the mobile communication network and receiving the protocol data unit session modification command in response.

8. The default quality of service rule management method of claim 7, wherein, the protocol data unit session modification request comprises a user equipment operation associated with creating, modifying, or deleting a quality of service rule.

9. The default quality of service rule management method of claim 6, wherein, the default quality of service rule policy enforces exactly one default quality of service rule per established protocol data unit session.

10. The default quality of service rule management method of claim 6, wherein, the user equipment releases the protocol data unit session by sending a protocol data unit session release request.

11. A default quality of service rule management method, characterized by, comprising: establishing, by a user equipment, a protocol data unit session in a mobile communication network, wherein the protocol data unit session is associated with a default quality of service rule; receiving a protocol data unit session modification command from the mobile communication network, wherein the protocol data unit session modification command comprises a command to perform a quality of service rule operation associated with the default quality of service rule of the protocol data unit session; determining whether the protocol data unit session modification command will result in a conflict with a default quality of service rule policy, wherein the conflict is determined when the quality of service rule operation comprises changing a default quality of service rule setting; and releasing the protocol data unit session when the conflict with the default quality of service rule policy is determined.

12. The default quality of service rule management method of claim 11, further comprising: sending a protocol data unit session modification request to the mobile communication network and receiving the protocol data unit session modification command in response.

13. The default quality of service rule management method of claim 12, wherein, the protocol data unit session modification request comprises a user equipment operation related to creating, modifying, or deleting a quality of service rule.

14. The default quality of service rule management method of claim 11, wherein, the default quality of service rule policy enforces exactly one default quality of service rule per established protocol data unit session.

15. The default quality of service rule management method of claim 11, wherein, the user equipment releases the protocol data unit session by sending a protocol data unit session release request.

16. A user equipment for default quality of service rule management, the user equipment comprising: the user equipment comprises a processor configured to perform the steps of the default quality of service rule management method of any of claims 1-15.

Images