CN117014368A - Multi-label processing of QOS rules and packet filters - Google Patents

Abstract

Packet filter elements that derive QoS rules and methods of evaluating packets are presented when there are multiple C-tags and/or S-tags in the ethernet frame header. In one novel aspect, for derived QoS rules, when a DL packet carries multiple C-tags or S-tags, the UE derives the packet filter element of the QoS rule from the outermost C-tag and/or the outermost S-tag of the DL packet. In another novel aspect, when the UE/NW evaluates a packet carrying multiple C-tags or S-tags, the UE/NW evaluates the outermost C-tag and/or the outermost S-tag of the packet and then the UE/NW sends the data packet using the corresponding QoS rules of the matched packet filter.

Description

Multi-label processing of QOS rules and packet filters

Technical Field

The disclosed embodiments relate generally to wireless communications, and more particularly, to a method of handling multiple tags for deriving or transmitting quality of service (Quality of Service, qoS) rules or traffic flow templates (Traffic Flow Template, TFT) and packet filters in Long Term Evolution (LTE) systems and fifth generation mobile communication technology (5 th Generation Mobile Communication Technology, 5G) New Radio (NR) systems.

Background

Wireless communication networks have grown exponentially over the years. Long-term Evolution (LTE) systems offer high peak data rates, low latency, improved system capacity, and low operating costs with simplified network architecture. In LTE systems, the evolved universal terrestrial radio access network (evolved universal terrestrial radio access network, E-UTRAN) includes a plurality of evolved Node-bs (enodebs or enbs) that communicate with a plurality of mobile stations (referred to as User Equipment (UE)) the third generation partnership project (the third generation partner project, 3 GPP) network typically includes a hybrid of 2G/3G/4G systems.

Quality of service (Quality of Service, qoS for short) refers to performance from the perspective of the network user. In LTE evolved packet system (Evolved Packet System, EPS for short), qoS is managed based on EPS bearers in evolved packet core (Evolved Packet Core EPC for short) and radio access network (Radio Access Network RAN for short). In 5G networks, qoS flows are the finest granularity of QoS management (finest granularity), making QoS control more flexible. The concept of QoS flows is similar to EPS bearers. 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 policy, queue management policy, rate shaping policy, RLC configuration, etc.). Providing different QoS forwarding treatments requires separate 5G QoS flows. Each QoS flow may include a plurality of QoS rules that consist of QoS profiles (profiles), packet filters, and priorities. The QoS profile includes QoS parameters and QoS tags. Packet filters are used to bind QoS flows to specific QoS markers. The priority indicates a priority to adapt QoS rules to QoS flows. The UE performs classification and tagging of Uplink (UL) user plane traffic (user plane traffic), i.e. UL traffic is associated to QoS flows according to QoS rules.

In 5G, PDU session establishment is a parallel procedure to the PDN connectivity procedure in 4G. The PDU session defines an association between the UE and a data network providing the PDU connectivity service. Each PDU session is identified by a PDU session ID and may include a plurality of QoS flows and QoS rules. Each QoS flow is identified by a QoS flow identifier (QoS flow identifier, QFI flow ID) that is unique within the PDU session. Each QoS rule is identified by a QoS rule ID (QRI for short). The same QoS flow may have multiple QoS rules. For each PDU session establishment, a default QoS rule needs to be sent to the UE and it is associated with the QoS flow. In one PDU session, there should be only one default QoS rule.

In the current 5G non-access stratum (NAS) specification, qoS rules and packet filters can be created, modified and deleted by PDU session and PDN connection establishment, modification and release procedures using NAS signaling for QoS operations, which is called QoS rules. In addition, qoS rules and packet filters may be derived from Downlink (DL) packets with a reflected QoS indication (Reflective QoS Indication, RQI for short), which is a field in the service data adaptation protocol (service data adaption protocol, SDAP) header. This is called a derived QoS rule. For each DL SDAP data PDU with received RQI set to 1, the SDAP entity should send RQI and QFI to the NAS layer. If the UE receives a DL user packet marked with QFI and RQI, the DL user packet belongs to a PDU session of IPv4, IPv6, IPv4v6 or ethernet PDU session type, the UE has no derived QoS rule, wherein the packet filter of UL direction is the same as the packet filter of UL direction derived from the DL user packet, and the UE should create a new derived QoS rule and packet filter.

When there are multiple C-tags and/or S-tags in the ethernet frame header of a DL packet, it is unclear which C-tags and/or S-tags should be derived for QoS rules derived in a DL packet with RQI. Furthermore, when there are multiple C-tags and/or S-tags in the Ethernet frame header of the UL/DL data, it is unclear which C-tags and/or S-tags should be evaluated for the QoS rules or packet filters that are sent or derived.

The solution is sought.

Disclosure of Invention

A packet filter element and method of evaluating packets that derive QoS rules when there are multiple C-tags and/or S-tags in the Ethernet frame header is presented. In one novel aspect, for derived QoS rules, when a DL packet carries multiple C-tags or S-tags, the UE derives the packet filter element of the QoS rule from the outermost C-tag and/or the outermost S-tag of the DL packet. In another novel aspect, when a UE evaluates an UL data packet carrying multiple C-tags or S-tags, the UE evaluates the outermost C-tag and/or the outermost S-tag of the UL data packet and then the UE transmits the UL data packet using the corresponding QoS rules of the matched packet filter. When evaluating a DL data packet carrying multiple C-tags or S-tags, the network evaluates the outermost C-tag and/or the outermost S-tag of the DL data packet and then the network sends the DL data packet using the corresponding QoS rules of the matched packet filter.

In one embodiment, a UE establishes a protocol data unit (protocol data unit, abbreviated PDU) session in a 5G mobile communication network. The UE receives a Downlink (DL) data packet containing a QoS Flow ID (QFI), a reflective QoS indicator (reflective QoS indicator, RQI) and a plurality of C-tags or S-tags. The UE derives a packet filter element from a plurality of C-tags or S-tags, wherein the packet filter element is derived from an outermost C-tag or S-tag. The UE evaluates the packet header of the upstream data packet for a matching packet filter element of the QoS rule of the packet header. The UE sends the uplink data packet using the matched QoS rules.

In another embodiment, the UE establishes a protocol data unit (protocol data unit, abbreviated PDU) session or packet data network (Packet data network, abbreviated PDN) connection in the mobile communication network. The UE obtains a QoS rule configuration for a PDU session or PDN connection, where the QoS rule configuration includes a plurality of packet filters with packet filter elements. The UE evaluates a header of an uplink data packet carrying a plurality of C-tags or S-tags, wherein the UE evaluates an outermost C-tag or S-tag of the uplink data packet according to the QoS rule configuration. The UE sends the uplink data packet using the matched QoS rules.

In yet another embodiment, a network entity establishes a protocol data unit (protocol data unit, PDU) session or packet data network (Packet data network, PDN) connection with a User Equipment (UE) through the network entity. The network entity obtains a QoS rule configuration for a PDU session or PDN connection, where the QoS rule configuration includes a plurality of packet filters with packet filter elements. The network entity evaluates the header of the downstream data packet carrying a plurality of C-tags or S-tags, wherein the network entity evaluates the outermost C-tag or S-tag of the downstream data packet according to the QoS rule configuration. The network entity sends the downlink data packet to the UE using the matched QoS rules.

Other embodiments and advantages are described in the detailed description that follows. This summary is not intended to define the invention. The invention is defined by the claims.

Drawings

The accompanying drawings illustrate embodiments of the invention in which like numerals refer to like elements.

Fig. 1 illustrates an exemplary EPS/5GS network for supporting quality of service (QoS) rule management, derivation of derived QoS rules packet filter elements, and evaluation of packets when multiple C-tags and/or S-tags are present in an ethernet frame header, in accordance with a novel aspect.

Fig. 2 shows a simplified block diagram of a User Equipment (UE) according to an embodiment of the invention.

Fig. 3 shows an example of a packet header with an SDAP header, an ethernet frame, and multiple TPIDs of C-tags and S-tags.

Fig. 4 illustrates a first embodiment of a packet filter element and evaluating uplink packets in accordance with a novel aspect of deriving QoS rules from a UE perspective.

Fig. 5 illustrates a second embodiment of evaluating downlink packets from an NW perspective in accordance with a novel aspect.

Fig. 6 illustrates a flow chart of a method of a packet filter element of derived QoS rules from a UE perspective in accordance with a novel aspect.

Fig. 7 illustrates a flow chart of a method of evaluating uplink packets from a UE perspective in accordance with a novel aspect.

Fig. 8 illustrates a flow chart of a method of evaluating downlink packets from an NW perspective in accordance with a novel aspect.

Detailed Description

Reference will now be made in detail to some embodiments of the invention, examples of which are illustrated in the accompanying drawings.

Fig. 1 illustrates an exemplary EPS/5GS network for supporting quality of service (QoS) rule management, derivation of derived QoS rules packet filter elements, and evaluation of packets when multiple C-tags and/or S-tags are present in an ethernet frame header, in accordance with a novel aspect. The LTE/NR network 100 includes an application server 111 that provides various services by communicating with a plurality of User Equipments (UEs) including UEs 114. In the example of fig. 1, an application server 111 and a packet data network gateway (PDN GW or P-GW) 113 are part of the core network CN 110. UE 114 and its serving base station BS/gNB 115 are part of a radio access network RAN 120. The RAN 120 provides radio access to the UE 114 via a radio access technology (radio access technology, RAT for short). The application server 111 communicates with the UE 114 through the PDN GW 113, the serving GW 116 and the BS/gNB 115. A mobility management entity (mobility management entity, MME for short) or access and mobility management function (mobility management function, AMF for short) 117 communicates with BS/gNB 115, serving GW 116 and PDN GW 113 for access and mobility management of wireless access devices in LTE/NR network 100. The UE 114 may be equipped with a Radio Frequency (RF) transceiver or multiple RF transceivers to apply to different application services via different RATs/CNs. UE 114 may be a smart phone, a wearable device, an internet of things (Internet of Things, ioT) device, and a tablet computer, among others.

The EPS and 5GS networks are packet-switched (PS) internet protocol (Internet Protocol IP) networks. This means that the network transmits all data traffic in the form of IP packets and provides IP connectivity for the user. When a UE joins an EPS/5GS network, a packet data network (Packet Data Network, PDN for short) address (i.e., an address that can be used on the PDN) is allocated to the UE to connect to the PDN. The EPS refers to the "IP access connection" of the UE as an evolved packet system (evolved packet system, EPS for short) bearer, which is a connection between the UE and the P-GW. The P-GW is the default gateway for the UE to access IP. EPS has defined a preset EPS bearer to provide IP connectivity.

In 5G, PDU session establishment is a parallel procedure to the PDN connectivity procedure in 4G. The PDU session defines an association between the UE and a data network providing the PDU connectivity service. Each PDU session is identified by a PDU session ID and may include a plurality of QoS flows and QoS rules. Each QoS flow is identified by a QoS Flow ID (QFI), which is unique within the PDU session. Each QoS rule is identified by a QoS Rule ID (QRI). The same QoS flow may have multiple QoS rules. For each PDU session establishment, a default QoS rule needs to be sent to the UE and associated with the QoS flow. In one PDU session there should be and only one default QoS rule.

In the current 5G non-access stratum (NAS) specification, qoS rules and packet filters can be created, modified and deleted using NAS signaling for QoS operations, which is called a transmitted QoS rule, through PDU session and PDN connection establishment, modification and release procedures. In addition, qoS rules and packet filters may be derived from Downlink (DL) packets with a reflected QoS indication (reflective QoS indication, RQI for short), which is a field in the service data adaptation protocol (service data adaptive protocol, SDAP) header. This is called a derived QoS rule. For each DL SDAP data PDU with the received RQI set to 1, the SDAP entity should inform the NAS layer of the RQI and QFI. If the UE receives a DL user data packet marked with QFI and RQI, the DL user data packet belongs to a PDU session of IPv4, IPv6, IPv4v6 or ethernet PDU session type, the UE has no derived QoS rule, wherein the packet filter of UL direction is the same as the packet filter of UL direction derived from the DL user packet, and the UE should create a new derived QoS rule and packet filter.

It is unclear which C-tags and/or S-tags should be derived for QoS rules derived in DL packets with RQI when there are multiple C-tags and/or S-tags in the ethernet frame header of DL packets and furthermore, it is unclear which C-tags and/or S-tag packets should be evaluated for QoS rules or packet filters sent or derived when there are multiple C-tags and/or S-tags in the ethernet frame header of UL/DL data. According to one novel aspect, a packet filter element and method of evaluating packets is presented that derives derived QoS rules when multiple C-tags and/or S-tags are present in an ethernet frame header. In one novel aspect as depicted at 140, for derived QoS rules, when a DL packet carries multiple C-tags or S-tags, the UE derives packet filter elements for QoS rules that are derived from the outermost C-tag and/or the outermost S-tag of the DL data packet. In another novel aspect, as shown at 150, in evaluating an UL data packet carrying multiple C-tags or S-tags, the UE evaluates the outermost C-tag and/or the outermost S-tag of the UL data packet and then the UE sends the UL data packet using the corresponding QOS rules of the matched packet filter. When evaluating a DL data packet carrying multiple C-tags or S-tags, the network evaluates the outermost C-tag and/or the outermost S-tag of the DL data packet and then the network sends the DL data packet using the corresponding QOS of the matched packet filter.

Fig. 2 shows a simplified block diagram of a wireless device, e.g., UE 201 and network entity 211, according to an embodiment of the invention. The network entity 211 may be a base station combined with an MME or an AMF. The network entity 211 has an antenna 215 that sends and receives radio signals. A radio frequency RF transceiver module 214 coupled to the antenna receives RF signals from the antenna 215, converts them to baseband signals and sends them to the processor 213. The RF transceiver 214 also converts the baseband signal received from the processor 213 into an RF signal and transmits to the antenna 215. The processor 213 processes the received baseband signal and invokes different functional modules to perform the features in the base station 211. Memory 212 stores program instructions and data 220 to control the operation of base station 211. In the example of fig. 2, network entity 211 also includes a set of control function modules and circuits 290. The PDU session process circuit 231 processes the PDU session establishment and modification procedure. QoS flows and rules management circuit 232 creates, modifies, and deletes QoS flows and QoS rules for the UE. The configuration and control circuit 233 provides different parameters to configure and control the UE.

Similarly, the UE 201 includes a memory 202, a processor 203, and a Radio Frequency (RF) transceiver module 204. The RF transceiver 204 is coupled to the antenna 205, receives RF signals from the antenna 205, converts them to baseband signals, and transmits them to the processor 203. The RF transceiver 204 also converts the baseband signal received from the processor 203 into an RF signal and transmits to the antenna 205. The processor 203 processes the received baseband signals and invokes various functional modules and circuits to perform the features in the UE 201. The memory 202 stores data and program instructions 210 to be executed by the processor to control the operation of the UE 201. Suitable processors include, by way of example, a special purpose processor, a digital signal processor (digital signal processor), a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, a controller, a microcontroller, an application specific integrated circuit (application specific integrated circuit, ASIC), document programmable gate array (file programmable gate array, FPGA) circuits, and other types of integrated circuits (integrated circuit, IC), and/or state machines. A processor associated with the software may be used to implement and configure features of the UE 201.

The UE 201 also includes a set of functional modules and control circuitry to perform the functional tasks of the UE 201. The protocol stack 260 includes a Non-Access-Stratum (NAS) layer (to communicate with MME or AMF entities connected to the core network), a radio resource control (Radio Resource Control, RRC) layer for higher layer configuration and control, a packet data convergence protocol/radio link control (Packet Data Convergence Protocol/Radio Link Control, PDCP/RLC) layer, a medium Access control (Meida Access Control, MAC) layer, and a Physical (PHY) layer. The system modules and circuitry 270 may be implemented and configured by software, firmware, hardware, and/or combinations thereof. The functional modules and circuits cooperate when executed by the processor via program instructions contained in memory to allow the UE 201 to perform embodiments and functional tasks and features in the network. In one example, the system module and circuitry 270 includes PDU session processing circuitry 221 for performing PDU session establishment and modification procedures with the network; qoS rule management circuitry 222 for handling QoS rule management by creating, modifying, deleting QoS rules and packet filters; and configuration and control circuitry 223 for handling QoS flows and rule configurations, as well as other control parameters, and evaluating data packets.

Fig. 3 shows an example of a Downlink (DL) data PDU with an SDAP header, an ethernet frame, and a plurality of TPIDs of C-tag and S-tag. The DL data PDU 300 includes a Reflected QoS Indication (RQI), which is a field in the Service Data Adaptation Protocol (SDAP) header. For each DL SDAP data PDU with the received RQI set to 1, the SDAP entity should inform the NAS layer of the RQI and QFI. The ethernet frame 310 is contained in a data field of the DL data PDU 300. The Ethernet frame 310 includes a plurality of tag protocol identifications (Tag Protocol Identifications, TPID), e.g., the TPID of the C-tag is 0x8100 and the TPID of the S-tag is 0x88a8. The plurality of TPIDs occupy Oct 21-Oct20+4N. Fig. 3 also shows an example of a C-tag TCI format and an S-tag TCI format. The C-tag or S-tag may be plural, i.e., N >1.

Fig. 4 illustrates a first embodiment of a packet filter element and evaluating uplink packets in accordance with a novel aspect of deriving QoS rules from a UE perspective. In step 411, UE 401 and network 402 establish a PDU session via a PDU session establishment procedure. The PDU session is established to include one or more QoS rules, including a default QoS rule. The network and the UE support a reflected QoS for PDU sessions. In step 421, UE 401 receives a downlink data packet, wherein RQI is set to 1, and RQI is a field in a service data adaptation protocol (service data adaption protocol, abbreviated SDAP) header of a DL data packet. This is called a derived QoS rule. The DL data packets include more than one C-tag and/or S-tag. In step 431, UE 401 derives new QoS rules and derives packet filter elements corresponding to the derived QoS rules. In a novel aspect, there are multiple C-tags and/or S-tags, and UE 401 derives a packet filter element from the outermost C-tag and the outermost S-tag. In step 441, UE 401 applies the evaluation to the uplink data packet. The UE attempts to match the header of the packet with the packet filter of the QoS rules. If there are multiple C-tags/S-tags in the Ethernet frame header of the UL data packet, the outermost C-tag/S-tag is evaluated. In step 451, if a match is found, UE 401 will send UL data packets on the corresponding QoS flow of the QoS rule.

Fig. 5 illustrates a second embodiment of evaluating downlink packets from an NW perspective in accordance with a novel aspect. In step 511, the UE 501 and the network 502 establish a PDU session through a PDU session establishment procedure (in 5G) or a PDN connection through a PDN connection procedure (in 4G). In 5G, each PDU session is identified by a PDU session ID and may include multiple QoS flows and QoS rules. In 4G, there are one or more EPS bearers per PDN connection, each EPS bearer being configured with a traffic flow template (Traffic Flow Template, TFT for short) corresponding to QoS rules for one PDU session. A PDU session or PDN connection is established to include a Traffic Flow Template (TFT)/or one or more QoS rules, including a default QoS rule. TFT and QoS rules and packet filters may be created, modified or deleted later by NAS signaling (QoS rules sent). For example, in step 512, the network 502 sends a PDU session modification command message to the UE 501. The command message is used for the UE to perform certain QoS operations on the PDU session, such as modifying existing QoS rules and creating/deleting packet filters. This is called the QoS rule for the transmission. In one example, the network may provide a QoS rule IE to the UE that includes a list of QoS rules. Each QoS rule, as shown at 550 of fig. 5, includes a QoS rule identifier (QoS rule identifier, QRI for short), a length of the QoS rule, a rule operation code, a Default QoS Rule (DQR) bit, a plurality of packet filters, a packet filter list, a QoS rule priority, and a QoS flow identifier (QoS flow identifier, QFI for short). Since the QFI identifies the corresponding QoS flow, qoS rules with a particular QFI are associated with QoS flows with the same particular QFI.

In step 521, the network entity (e.g., UPF) obtains QoS rules and QoS flow parameters or TFTs of the UE, including one or more packet filters. In step 531, the network entity (UPF) attempts to match the header of the downlink data packet with QoS rules or packet filters of the TFT. If there are multiple C-tags/S-tags in the Ethernet frame header of the DL data packet, the outermost C-tag/S-tag is evaluated. In step 541, if a match is found, the network entity (e.g., UPF) will transmit DL data packets on the corresponding QoS flows of the QoS rules or the corresponding bearers of the TFT.

Fig. 6 is a flow diagram of a method of deriving packet filter components of derived QoS rules from a UE perspective in accordance with a novel aspect. In step 601, the UE establishes a protocol data unit (protocol data unit, abbreviated PDU) session in a 5G mobile communication network. In step 602, the UE receives a Downlink (DL) data packet including a QoS Flow ID (QFI), a Reflective QoS Indicator (RQI), and a plurality of C-tags or S-tags. In step 603, the UE derives a packet filter element from a plurality of C-tags or S-tags, wherein the packet filter element is derived from the outermost C-tag or S-tag. In step 604, the UE evaluates the packet header of the uplink data packet and finds a matching packet filter of the QoS rules of the packet header. In step 605, the UE transmits an uplink data packet using the matched QoS rules.

Fig. 7 illustrates a flow chart of a method of evaluating uplink packets from a UE perspective in accordance with a novel aspect. In step 701, the UE establishes a Protocol Data Unit (PDU) session or a Packet Data Network (PDN) connection in a mobile communication network. In step 702, the UE obtains a TFT/QoS rule configuration for a PDU session or PDN connection, wherein the TFT or QoS rule configuration includes a plurality of packet filters with packet filter elements. In step 703, the UE evaluates the header of the upstream data packet carrying a plurality of C-tags or S-tags, wherein the UE evaluates the outermost C-tag or S-tag of the upstream data packet according to the TFT/QoS rule configuration. In step 704, the UE transmits an uplink data packet using the matched TFT/QoS rules.

Fig. 8 illustrates a flow chart of a method of evaluating downlink packets from an NW perspective in accordance with a novel aspect. In step 801, a network entity establishes a Protocol Data Unit (PDU) session or Packet Data Network (PDN) connection with a User Equipment (UE). In step 802, a network entity obtains a TFT/QoS rule configuration for a PDU session or PDN connection, wherein the TFT/QoS rule configuration includes a plurality of packet filters with packet filter elements. In step 803, the network entity evaluates the header of the downstream data packet carrying a plurality of C-tags or S-tags, wherein the network entity evaluates the outermost C-tag or S-tag of the downstream data packet according to the TFT/QoS rule configuration. In step 804, the network entity sends downlink data packets to the UE using the matched TFT/QoS rules.

Although the present invention has been described in connection with the specified embodiments for instructional purposes, the present invention is not limited thereto. Accordingly, various modifications, adaptations, and combinations of the various features of the described embodiments can be practiced without departing from the scope of the invention as set forth in the claims.

Claims (18)

1. A multi-tag processing method comprising:

establishing, by the user equipment, a protocol data unit session in the 5G mobile communication network;

receiving a downlink data packet, the downlink data packet including a quality of service flow identifier, a reflected quality of service indicator, and a plurality of C-tags or S-tags;

deriving a packet filter element from the plurality of C-tags or S-tags, wherein the packet filter element is derived from an outermost C-tag or S-tag;

evaluating a packet header of an upstream data packet, and finding a packet filter of a quality of service rule matched with the packet header; and

the uplink data packets are transmitted using the quality of service rules that match.

2. The multi-label processing method of claim 1 wherein the downlink data packet is a protocol data unit, the protocol data unit comprising a header portion and a data portion, and wherein the data portion further comprises an ethernet frame header.

3. The multi-label processing method of claim 2 wherein the header portion comprises a service data adaptation protocol header, the service data adaptation protocol header further comprising the reflected quality of service indicator and the quality of service flow identifier.

4. The multi-tag processing method of claim 2, wherein the ethernet frame header includes one or more tag protocol identification fields.

5. The multi-tag processing method of claim 4, wherein the one or more tag protocol identification fields carry a plurality of C-tags or S-tags in the ethernet frame header.

6. The multi-tag processing method of claim 1, wherein the derivation of the packet filter element involves creating the packet filter element from an outermost C-tag or S-tag value.

7. The multi-label processing method of claim 1 wherein evaluating the packet header of the upstream data packet comprises finding a packet filter from a plurality of quality of service rules that matches a packet filter of the upstream data packet.

8. The multi-label processing method of claim 1 wherein the packet header of the upstream data packet carries a plurality of C-labels or S-labels, and wherein the user equipment evaluates the outermost C-label or S-label of the upstream data packet.

9. A multi-tag processing method comprising:

establishing a protocol data unit session or packet data network connection in a mobile communication network by a user equipment;

obtaining a quality of service rule configuration for the protocol data unit session or a traffic flow template configuration for the packet data network connection, wherein the quality of service rule configuration or the traffic flow template configuration comprises a plurality of packet filters having a plurality of packet filter elements;

evaluating a header of an uplink data packet, wherein the uplink data packet carries a plurality of C-tags or S-tags, and the user equipment evaluates an outermost C-tag or S-tag of the uplink data packet according to the service quality rule or the traffic flow template configuration; and

the upstream data packets are transmitted using either a matching quality of service rule or a matching traffic flow template.

10. The multi-label processing method of claim 9 wherein the uplink data packet is a protocol data unit, the protocol data unit comprising a header portion and a data portion, and wherein the data portion further comprises an ethernet frame header.

11. The multi-tag processing method of claim 10, wherein the ethernet frame header includes one or more tag protocol identification fields for carrying the plurality of C-tags or S-tags.

12. The multi-label processing method of claim 9 wherein the evaluating involves the user device finding a packet filter from the quality of service rule or the traffic flow template configuration that matches a plurality of packet filter elements associated with the C-label or S-label of the outermost layer of the uplink data packet.

13. The multi-label processing method of claim 9 wherein the quality of service rules or the traffic flow template configuration are provided from a network via non-access stratum signaling.

14. The multi-label processing method of claim 9 wherein the quality of service rule or the traffic flow template configuration is derived by the user device from a downlink data packet.

15. A multi-tag processing method comprising:

establishing a protocol data unit session or packet data network connection with the user equipment by the network entity;

obtaining a quality of service rule configuration for the protocol data unit session or a traffic flow template configuration for the packet data network connection, wherein the quality of service rule configuration or the traffic flow template configuration comprises a plurality of packet filters having a plurality of packet filter elements;

evaluating a header of a downlink data packet, the downlink data packet carrying a plurality of C-tags or S-tags, wherein the network entity evaluates an outermost C-tag or S-tag of the downlink data packet according to the quality of service rule or the traffic flow template configuration; and

and transmitting the downlink data packet to the user equipment by using the matched service quality rule or the matched traffic flow template.

16. The multi-label processing method of claim 15 wherein the downlink data packet is a protocol data unit, the protocol data unit comprising a header portion and a data portion, and wherein the data portion further comprises an ethernet frame header.

17. The multi-tag processing method of claim 16, wherein the ethernet frame header includes one or more tag protocol identification fields for carrying the plurality of C-tags or S-tags.

18. The multi-label processing method of claim 15 wherein the evaluating involves the network entity finding a packet filter from the quality of service rule or the traffic flow template configuration that matches a plurality of packet filter elements associated with the C-label or S-label of the outermost layer of the downlink data packet.