WO2018006249A1 - Qos control method in 5g communication system and related device - Google Patents

Abstract

A QoS control method in a 5G communication system and a related device for providing more refined and more flexible QoS control for a 5G mobile communication network. The method comprises: a terminal UE determining, according to a QoS rule, a radio bearer mapped to an uplink data packet and a QoS class identification corresponding to the uplink data packet; the UE carrying the QoS class identification in the uplink data packet; and the UE sending the uplink data packet via the radio bearer.

Description

QoS control method and related device in 5G communication system Technical field

The present invention relates to the field of communications technologies, and in particular, to a QoS control method and related device in a 5G communication system.

Background technique

At present, more and more services are carried on wireless networks, and wireless networks have become an infrastructure. As a basic network architecture, wireless networks have clear requirements for service assurance, and wireless networks, as bearer networks, must support various basic essential services as well as various value-added and data services.

The characteristics of the service, the requirements, and the scarcity of the radio resources determine the behavior of the network. The behavior of the network is defined in advance by the QoS Rules (QoS, Quality of Service) to implement access control, resource guarantee, and scheduling. . For example, it is required to ensure that the voice call service has a higher priority of wireless resource allocation and use than the downloaded file service. When the wireless resource is insufficient, the wireless resource request for downloading the file does not occupy the wireless resource of the call service. As another example, it is desirable to ensure that the wireless resources of the voice call are always secured during the call, rather than being shared. However, the wireless resources for services such as file downloading can be shared by multiple similar services and multiple users, and will not greatly affect the user experience. Similarly, in the event of a public emergency, if there is insufficient radio resources, the public alarm system will preempt the communication resources of ordinary users. It can be seen that services with a higher priority than voice calls have higher priority in resource preemption and allocation.

It can be seen that when multiple users and multiple services access the same base station or the same network device, access control needs to be performed between different users and different services to ensure that critical users or key services are guaranteed.

FIG. 1 is a schematic diagram of a 3GPP Evolved Packet Core (EPS) network architecture, where a solid line indicates a control plane and a broken line indicates a data plane. The Mobile Management Entity (MME) is the primary network element on the control plane and is connected to the base station (eNodeB). There is a control plane interface S1-MME, and there is an S11 interface between the Serving Gateway (S-GW) and an interface between the Home Subscriber Server (HSS) and S6a (Diameter Type Protocol). There is an S3 interface between the MME and the S4-SGSN (Serving GPRS Support Node, GPRS, General Packet Radio System). There is an SGs interface between the MME and the Mobile Switching Center (MSC). The MME is connected to other MMEs through an S10 interface.

Taking the 3GPP EPS wireless system as an example, the QoS management mode of the wireless network is described. Here, the GPRS Tunneling Protocol (GTP) of the S5/8 interface in the 3GPP is taken as an example. 2 is a schematic structural diagram of a user plane protocol stack of each 3GPP network node located between a UE and a PGW (PDN Gateway, PDN, Packet Data Network, Packet Data Network).

The EPS system uses the indirect QoS guarantee mechanism to provide QoS guarantee for various Internet Protocol (IP) services. The IP service may be identified by one or more Service Data Flows (SDFs) that transmit the IP service data, and the SDF is identified by one or more IP data flow filter templates (Flow Filters), and one SDF is passed through one EPS bearers to transmit. It can be seen that the QoS of the EPS bearer can be realized by realizing the QoS of the EPS bearer, thereby realizing the QoS of the IP service. The EPS bearer is a logical transmission channel between the UE and the PGW. Figure 3 is a schematic diagram of the SDF binding bearer in the uplink (UL) and the downlink (DL).

The EPS bearer is established between the UE and the PGW, and the EPS Bearer=Radio Bearer (RB)+S1 Bearer+S5/S8 Bearer.

The basic granularity of QoS control in the EPS system is EPS bearer. The data flows on the same EPS bearer enjoy the same QoS guarantee, such as scheduling policy, queue management policy, rate adjustment policy, and radio link control (RLC). Configuration, etc. According to different QoS parameters, EPS bearers can be classified into Guaranteed Bit Rate (GBR) bearer and Non-GBR (NGBR) bearer. GBR bearer means that dedicated network resources are permanently allocated when bearer is established/modified, and the rate can be guaranteed even when network resources are tight. The Non-GBR bearer is the opposite. It is a bearer with no guaranteed rate. When the network resources are tight, the service rate will be reduced.

An EPS bearer is established when the terminal is connected to a PDN, and the EPS bearer is reserved during the entire PDN connection, that is, the terminal is provided with a persistent IP connection to the PDN, that is, long-term evolution ( The default bearer introduced in the Long Term Evolution (LTE) system. The user's "always on" function is implemented by the default bearer, which reduces the delay of service establishment and effectively improves the user experience. Normally, the default bearer is a Non-GBR bearer and does not occupy fixed resources for a long time. The initial bearer-level QoS parameters of the default bearer are allocated by the network side based on the subscriber's subscription data. The other EPS bearers established by the terminal on the same PDN are called dedicated bearers, and the dedicated bearers may be GBR bearers or Non-GBR bearers. The function of establishing or modifying a dedicated bearer can only be performed by an Evolved Packet Core (EPC), and the bearer level QoS parameters are allocated by the EPC. When the terminal is connected to multiple PDNs at the same time, the terminal can have multiple default bearers and IP addresses at the same time.

In this way, the QoS guarantee of the IP service is transformed into the QoS guarantee of the EPS bearer. An SDF is mapped to an EPS bearer of a specific QOS, and multiple SDFs with the same QoS (these SDFs are from different IP services) can be simultaneously mapped to EPS bearers with the same QoS parameter, for example, having the same quality of service identifier. (QoS Class Identifier, QCI) and EPS bearer of Allocation and Retention Priority (ARP). That is, multiple SDFs mapped to the same EPS bearer will get the same bearer level data forwarding process; if two SDFs require different bearer level QoS processing, then a separate EPS bearer needs to be established for each SDF. Different service data streams mapped to the same EPS bearer must have the same QCI and ARP. The process of mapping the SDF of a particular QOS to the EPS bearer of a particular QOS is called the Binding process. Multiple service flows within a bearer receive the same QoS processing within the EPS and are no longer distinguishable.

The data stream and the bearer are associated and mapped by a Traffic Flow Template (TFT), and the TFT is associated with the RB-ID and the Tunnel Endpoint Identifier (TEID) in the wireless and core networks, respectively. The association of the upstream data stream and the TFT is performed by the UE, and the association of the downstream data stream and the TFT is performed by the PGW.

SDF defines parameters for data detection; each SDF contains an indeterminate number of IPs Flower Filters, specifically the combination of the following parameters:

Remote Address and Subnet Mask; Protocol Number (IPv4) or Next Header (IPv6); Local Address and Mask; Local Port Range (Local Port Range); Remote Port Range; IPSec Security Parameter Index (SPI); Type of Service (TOS) (IPv4) or Traffic Class (IPv6) And Mask (Flow Label) (IPv6).

It should be noted that wildcards are allowed for each of the preceding parameters.

The EPS carried by the EPS is a collection of IP Flow Filters of each SDF installed in the bearer. Since there may be many SDFs and multiple EPS bearers, each IP Flow Filter has its own priority. Therefore, when the PGW or the Policy and Charging Enforcement Function (PCEF) receives a downlink IP packet, the IP packet is matched with the IP Flow Filter according to the IP Flow Filter. The priority determines in turn which SDF the received IP packet belongs to. The IP data packet belongs to the SDF of the first matching IP Flow Filter. If the strobe status of the Policy and Charging Control (PCC) rule (Rules) corresponding to the SDF is open, the SDF is calculated. The fee is charged by the rule, and the EPS bearer is determined to be transmitted in the bearer binding process by the SDF; otherwise, if the strobe state is off, the downlink IP data packet is discarded. If the received IP packet cannot match any IP Flow Filter, the downstream IP packet will be discarded. One possible scenario is to include an all-wildcard IP Flower Filter in the default bearer so that unsuccessfully matched IP packets can be transmitted over the default bearer.

The SDF detection in the uplink direction and the downlink direction is performed independently, wherein the downlink direction is performed in the PGW/PCEF and the uplink direction is performed in the UE. The IP Flower Filter rule on the UE is determined by the PCC to be transmitted to the UE through the PGW according to the PCC rule.

The mapping between the SDF, the TFT, and the bearer is as shown in FIG. 4, and the association between the uplink SDF and the TFT is performed by the UE, and the association between the downlink SDF and the TFT is performed by the PGW, and different services are filtered by the TFT according to different QoS requirements. The bearer is transmitted on.

Figure 5 shows the relationship between EPS bearers and QoS parameters. The Maximum Bit Rate (MBR) is the maximum bit rate of the GBR. Aggregate Maximum Bit Rate (AMBR) is classified into Access Point Name (APN)-AMBR and UE-AMBR. The APN-AMBR, which is the subscription parameter in the HSS, refers to the maximum bit rate of aggregation of all Non-GBR bearers in all PDN connections in the APN. The uplink APN-AMBR process is performed on the UE and the PGW, and the downlink APN-AMBR process is performed on the PGW. UE-AMBR refers to the aggregated maximum bit rate of all Non-GBR bearers in the UE. Both uplink and downlink UE-AMBR processing is performed on the eNB.

How to implement finer and more flexible QoS control in the fifth generation (5G) mobile communication network is a problem to be solved.

Summary of the invention

Embodiments of the present invention provide a QoS control method and related device in a 5G communication system, which are used to provide finer and more flexible QoS control for a 5G mobile communication network.

The specific technical solutions provided by the embodiments of the present invention are as follows:

In a first aspect, an embodiment of the present invention provides a QoS control method for a QoS in a 5G communication system, including:

Determining, by the terminal UE, the radio bearer mapped by the uplink data packet and the QoS class identifier corresponding to the uplink data packet according to the QoS rule;

The UE carries the QoS class identifier in the uplink data packet;

The UE sends the uplink data packet by using the radio bearer.

Based on the foregoing technical solution, in the embodiment of the present invention, for the uplink data packet mapped to the NGBR bearer, the radio bearer mapped by the uplink data packet and the QoS level identifier corresponding to the uplink data packet are determined according to the QoS rule, and the uplink data packet is in the uplink data packet. The QoS class identifier is carried in, so that the uplink data packet is scheduled according to the QoS class identifier carried in the uplink data packet on the radio bearer, so that different QoS control is performed on multiple uplink data packets transmitted on the NGBR bearer, and the QoS control is implemented in the 5G. Mobile communication networks are more refined and more flexible QoS control.

In a possible implementation manner, the QoS rule includes: at least one of an uplink filtering template and a QoS class identifier, an uplink filtering template, and a Qos parameter.

In a possible implementation manner, the determining, by the UE, the QoS level identifier corresponding to the uplink data packet according to the QoS rule, including:

Determining, by the UE, an uplink filtering template that matches the uplink data packet in the QoS rule, and determining, according to a correspondence between an uplink filtering template and a QoS class identifier in the QoS rule, that the uplink data packet matches The QoS class identifier corresponding to the uplink filtering template.

In a possible implementation manner, the QoS class identifier is located in an Internet Protocol IP header field of the uplink data packet, a packet data convergence protocol PDCP header field, a radio link control RLC header field, a medium access control MAC header field, or an L1 layer. Header field.

In a possible implementation manner, the QoS level identifier is used to indicate a scheduling priority of the uplink data packet on the radio bearer; and/or

The QoS level identifier includes at least one of a scheduling priority, a delay, a reliability, and a drop priority indication in the QoS parameter.

In a possible implementation manner, the QoS class identifier includes at least one of a packet priority indication PPI, a packet QoS identification PQI, a flow priority indication FPI, a flow QoS identifier FQI, and a packet drop priority indication PDPI.

In a possible implementation, the sending, by the UE, the uplink data packet by using the radio bearer includes:

And the UE, according to the PPI carried in the uplink data packet, placing the uplink data packet into a queue corresponding to the PPI in at least two queues corresponding to the radio bearer, by using the radio bearer transmission station The uplink data packet in the queue, where one PPI corresponds to one queue; or

The UE, according to the PQI carried in the uplink data packet, puts the uplink data packet into a queue corresponding to the PQI in at least two queues corresponding to the radio bearer, by using the radio bearer transmission station. The uplink data packet in the queue, where one PQI corresponds to one queue; or,

The UE, according to the FPI carried in the uplink data packet, puts the uplink data packet into a queue corresponding to the FPI in at least two queues corresponding to the radio bearer, by using the radio bearer transmission station. The uplink data packet in the queue, where one FPI corresponds to one queue; or

The UE, according to the FQI carried in the uplink data packet, puts the uplink data packet into a queue corresponding to the FQI in at least two queues corresponding to the radio bearer, by using the radio bearer transmission station. The uplink data packet in the queue, where one FQI corresponds to one queue.

In a possible implementation, the sending, by the UE, the uplink data packet by using the radio bearer includes:

The UE puts the uplink data packet into a queue corresponding to the radio bearer, and transmits the uplink data packet in the queue by using the radio bearer, where the radio bearer corresponds to one queue.

In a possible implementation manner, the method further includes:

And determining, by the UE, that the queue is congested, determining, according to the PDPI carried in each of the uplink data packets in the queue that is congested, an uplink data packet to be discarded.

In a possible implementation, an uplink data packet carrying a different PPI in a packet data unit PDU session is mapped to a different radio bearer; or

Uplink packets carrying different PQIs in a packet data unit PDU session are mapped to different radio bearers; or

Uplink packets carrying different FPIs in a packet data unit PDU session are mapped to different radio bearers; or

Uplink packets carrying different FQIs in one packet data unit PDU session are mapped to different radio bearers.

In a possible implementation, the QoS rule is obtained after the UE receives the radio resource control RRC reconfiguration request sent by the radio access network RAN node, and obtains the non-access stratum NAS message carried in the RRC reconfiguration request. .

In a possible implementation, the RRC reconfiguration request is sent to the RAN node after receiving the radio bearer request sent by the control plane function node of the core network and the NAS message. The UE, the radio bearer request and the NAS message are sent to the RAN node by the control plane function node of the core network, after the receiving network policy control node returns a create session response according to the create session request, where the session response is generated. And the NAS message carries the QoS rule;

or,

The RRC reconfiguration request is sent by the RAN node to the UE after receiving the radio bearer request and the NAS message sent by the first control plane function node, where the radio bearer request and the NAS message are Receiving, by the first control plane function node, a create session response returned by the second control plane function node, and sending the session response to the RAN node, where the create session response is that the second control plane function node receives the first control plane function And sending the session request sent by the node, and sending the QoS rule from the network policy control node according to the create session request, where the create session response and the NAS message carry the QoS rule.

In a second aspect, an embodiment of the present invention provides a QoS control method for a QoS in a 5G communication system, including:

The radio access network RAN node receives the uplink data packet of the terminal UE;

Determining, by the RAN node, a radio bearer in which the uplink data packet is located or a transport priority identifier corresponding to the QoS level identifier carried in the uplink data packet, and carrying the transport priority identifier in the uplink data packet, where The transmission priority identifier is used to indicate a transmission priority of the uplink data packet between routers between the RAN node and the core network;

The RAN node sends the uplink data packet carrying the transmission priority identifier, and the routers located between the RAN node and the core network perform the uplink according to the transmission priority identifier carried in the uplink data packet. The data packet is transmitted to the core network.

In a possible implementation manner, the RAN node sends the uplink data packet that carries the transmission priority identifier, including:

Mapping, by the RAN node, the radio bearer in which the uplink data packet is located to a core network bearer between the RAN node and the core network CN node corresponding to the transmission priority identifier, where the core network bears the The uplink data packet is transmitted to the core network, wherein one of the core network bearer mappings has at least one radio bearer.

In a possible implementation manner, the QoS class identifier is located in a tunnel header of the uplink data packet.

In a possible implementation manner, the transmission priority identifier is located in an IP header field outside the tunnel of the uplink data packet.

In a possible implementation manner, the QoS level identifier includes at least one of a scheduling priority, a delay, a reliability, and a drop priority indication in the QoS parameter.

In a possible implementation manner, the QoS class identifier includes at least one of a packet priority indication PPI, a packet QoS identifier PQI, a flow priority indication FPI, a flow QoS identifier FQI, and a packet drop priority indication PDPI.

In a third aspect, an embodiment of the present invention provides a QoS control method for a QoS in a 5G communication system, including:

The core network CN node receives the uplink data packet of the terminal UE through the radio access network RAN node;

The CN node determines, according to the QoS rule of the UE, that the QoS level identifier carried in the uplink data packet is valid.

In a possible implementation manner, the QoS rule includes: a correspondence between an uplink filtering template and a QoS class identifier, a correspondence between a downlink filtering template and a QoS class identifier, an uplink filtering template, a downlink filtering template, and at least a Qos parameter. One.

In a possible implementation manner, the CN node determines, according to the QoS rule of the UE, that the QoS level identifier carried in the uplink data packet is valid, and includes:

The CN node determines, according to the uplink filtering template in the QoS rule of the UE, that the QoS level identifier carried in the uplink data packet is valid.

In a possible implementation manner, the QoS rule of the UE is obtained from a create session response returned by the network policy control node according to a create session request sent by a control plane function node of the core network to the control plane function node.

In a possible implementation manner, the QoS level identifier includes at least one of a scheduling priority, a delay, a reliability, and a drop priority indication in the QoS parameter.

In a possible implementation manner, the QoS class identifier includes a scheduling priority indication PPI, a packet QoS identifier PQI, a flow priority indication FPI, a flow QoS identifier FQI, and a packet drop priority indication PDPI. At least one of them.

In a fourth aspect, an embodiment of the present invention provides a QoS control method for a QoS in a 5G communication system, including:

The core network CN node determines, according to the QoS rule corresponding to the terminal UE, the core network bearer mapped by the downlink data packet and the QoS level identifier corresponding to the downlink data packet of the UE;

The CN node carries the QoS class identifier in the downlink data packet;

The CN node sends the downlink data packet by using the core network bearer.

Based on the foregoing technical solution, in the embodiment of the present invention, for the downlink data packet mapped to the NGBR bearer, the network bearer mapped by the downlink data packet and the QoS level identifier corresponding to the downlink data packet are determined according to the QoS rule, where the downlink data packet is in the downlink data packet. The QoS class identifier is carried, so that different QoS control can be performed on the NGBR bearer according to the QoS class identifiers carried by the plurality of uplink data packets transmitted, thereby realizing more refined and more flexible QoS control in the 5G mobile communication network.

In a possible implementation manner, the CN node is a user plane function node of the core network, and the QoS rule is sent by the control plane function node of the core network to the user plane function node.

In a possible implementation manner, the QoS rule includes: a correspondence between an uplink filtering template and a QoS class identifier, a correspondence between a downlink filtering template and a QoS class identifier, an uplink filtering template, a downlink filtering template, and at least a Qos parameter. One.

In a possible implementation manner, before the sending, by the CN node, the downlink data packet, the following:

Determining, by the CN node, the QoS class identifier or the transmission priority identifier corresponding to the core network bearer, where the transport priority identifier is used to indicate that the downlink data packet is between the core network and the RAN node Transmission priority between routers;

The CN node carries the transmission priority identifier in the downlink data packet.

In a possible implementation manner, the QoS class identifier is located in a tunnel header of the downlink data packet.

In a possible implementation manner, the transmission priority identifier is located in an IP header field outside the tunnel of the downlink data packet.

In a possible implementation manner, the QoS level identifier is used to indicate a scheduling priority of the downlink data packet on the core network bearer; and/or

The QoS level identifier includes at least one of a scheduling priority, a delay, a reliability, and a drop priority indication in the QoS parameter.

In a possible implementation manner, the QoS class identifier includes at least one of a packet priority indication PPI, a packet QoS identifier PQI, a flow priority indication FPI, a flow QoS identifier FQI, and a packet drop priority indication PDPI.

In a possible implementation manner, the QoS rule corresponding to the UE is obtained from a create session response returned by the network policy control node according to a create session request sent by the control plane function node of the core network to the control plane function node.

In a fifth aspect, an embodiment of the present invention provides a QoS control method for a QoS in a 5G communication system, including:

The radio access network RAN node receives the downlink data packet sent by the core network CN node to the terminal UE;

Determining, by the RAN node, a radio bearer corresponding to the QoS class identifier carried in the downlink data packet, and sending the downlink data packet to the UE by using the radio bearer; or

The RAN node determines a radio bearer corresponding to the core network in which the downlink data packet is located, and sends the downlink data packet to the UE according to the QoS class identifier by using the radio bearer.

In a possible implementation, the RAN node sends the downlink data packet to the UE by using the radio bearer, or sends the downlink data packet to the device according to the QoS class identifier by using the radio bearer. Before the UE, the method further includes:

The RAN node deletes a tunnel header of the downlink data packet.

In a possible implementation manner, the QoS level identifier includes at least one of a scheduling priority, a delay, a reliability, and a drop priority indication in the QoS parameter.

In a possible implementation manner, the QoS class identifier includes at least one of a packet priority indication PPI, a packet QoS identifier PQI, a flow priority indication FPI, a flow QoS identifier FQI, and a packet drop priority indication PDPI.

In a possible implementation manner, the RAN node sends the downlink data packet to the UE by using the radio bearer, or sends, by using the radio bearer, the downlink data packet to the UE, including:

And the RAN node, according to the PPI carried in the downlink data packet, placing the downlink data packet into a queue corresponding to the PPI in at least two queues corresponding to the radio bearer, and transmitting by using the radio bearer The downlink data packet in the queue, where one PPI corresponds to one queue; or

And the RAN node, according to the PQI carried in the downlink data packet, placing the downlink data packet into a queue corresponding to the PQI in at least two queues corresponding to the radio bearer, and transmitting by using the radio bearer The downlink data packet in the queue, where one PQI corresponds to one queue; or

And the RAN node, according to the FPI carried in the downlink data packet, placing the downlink data packet into a queue corresponding to the FPI in at least two queues corresponding to the radio bearer, and transmitting by using the radio bearer The downlink data packet in the queue, wherein one FPI corresponds to one queue; or

And the RAN node, according to the FQI carried in the downlink data packet, placing the downlink data packet into a queue corresponding to the FQI in at least two queues corresponding to the radio bearer, and transmitting by using the radio bearer The downlink data packet in the queue, wherein one FQI corresponds to one queue.

In a possible implementation manner, the RAN node sends the downlink data packet to the UE by using the radio bearer, or sends, by using the radio bearer, the downlink data packet to the UE, including:

The RAN node puts the downlink data packet into a queue corresponding to the radio bearer, and transmits the downlink data packet in the queue by using the radio bearer, where the radio bearer corresponds to one queue.

In a possible implementation manner, the method further includes:

If the RAN node determines that the queue is congested, the downlink data packet that needs to be discarded is determined according to the PDPI carried in each downlink packet in the queue that is congested.

In a possible implementation, one of the core network bearers corresponds to at least one radio bearer;

Determining, by the RAN node, a radio bearer corresponding to the core network where the downlink data packet is located, include:

The RAN node determines a radio bearer corresponding to the PPI or PQI or FPI or FQI carried in the downlink data packet in at least one radio bearer corresponding to the core network bearer in which the downlink data packet is located.

In a sixth aspect, an embodiment of the present invention provides a terminal UE, including:

a determining module, configured to determine, according to the QoS rule, a radio bearer mapped by the uplink data packet and a QoS class identifier corresponding to the uplink data packet;

a processing module, configured to carry, in the uplink data packet, the QoS level identifier determined by the determining module;

And a sending module, configured to send the uplink data packet by using the radio bearer.

In a possible implementation manner, the QoS rule includes: at least one of an uplink filtering template and a QoS class identifier, an uplink filtering template, and a Qos parameter.

In a possible implementation manner, the determining module is specifically configured to:

Determining an uplink filtering template that matches the uplink data packet in the QoS rule, and determining, according to a correspondence between an uplink filtering template and a QoS class identifier in the QoS rule, the uplink that matches the uplink data packet Filters the QoS class identifier corresponding to the template.

In a possible implementation manner, the QoS class identifier is located in an Internet Protocol IP header field of the uplink data packet, a packet data convergence protocol PDCP header field, a radio link control RLC header field, a medium access control MAC header field, or an L1 layer. Header field.

In a possible implementation manner, the QoS level identifier is used to indicate a scheduling priority of the uplink data packet on the radio bearer; and/or

The QoS level identifier includes at least one of a scheduling priority, a delay, a reliability, and a drop priority indication in the QoS parameter.

In a possible implementation manner, the QoS class identifier includes at least one of a packet priority indication PPI, a packet QoS identification PQI, a flow priority indication FPI, a flow QoS identifier FQI, and a packet drop priority indication PDPI.

In a possible implementation manner, the sending module is specifically configured to:

And the uplink data packet is placed in a queue corresponding to the PPI in at least two queues corresponding to the radio bearer according to the PPI carried in the uplink data packet, and the queue is transmitted by using the radio bearer. The uplink data packet, wherein one PPI corresponds to one queue; or,

And the uplink data packet is placed in a queue corresponding to the PQI in at least two queues corresponding to the radio bearer according to the PQI carried in the uplink data packet, and the queue is transmitted by using the radio bearer. The uplink data packet, wherein one PQI corresponds to one queue; or,

And the uplink data packet is placed in a queue corresponding to the FPI in at least two queues corresponding to the radio bearer according to the FPI carried in the uplink data packet, and the queue is transmitted by using the radio bearer. The uplink data packet, wherein one FPI corresponds to one queue; or,

And the uplink data packet is placed in a queue corresponding to the FQI in at least two queues corresponding to the radio bearer according to the FQI carried in the uplink data packet, and the queue is transmitted by using the radio bearer. The uplink data packet, wherein one FQI corresponds to one queue.

In a possible implementation manner, the sending module is specifically configured to:

The uplink data packet is placed in a queue corresponding to the radio bearer, and the uplink data packet in the queue is transmitted by using the radio bearer, where the radio bearer corresponds to one queue.

In a possible implementation manner, the sending module is further configured to:

If it is determined that the queue is congested, the uplink data packet that needs to be discarded is determined according to the PDPI carried in each of the uplink data packets in the queue that is congested.

In a possible implementation, an uplink data packet carrying a different PPI in a packet data unit PDU session is mapped to a different radio bearer; or

Uplink packets carrying different PQIs in a packet data unit PDU session are mapped to different radio bearers; or

Uplink packets carrying different FPIs in a packet data unit PDU session are mapped to different radio bearers; or

Uplink packets carrying different FQIs in one packet data unit PDU session are mapped to different radio bearers.

In a possible implementation manner, the QoS rule is that the UE receives a radio access network RAN node. After the transmitted radio resource controls the RRC reconfiguration request, it is obtained from the non-access stratum NAS message carried in the RRC reconfiguration request.

In a possible implementation, the RRC reconfiguration request is sent by the RAN node to the UE after receiving the radio bearer request and the NAS message sent by the control plane function node of the core network, where the radio bearer request and The NAS message is sent to the RAN node by the control plane function node of the core network after the receiving network policy control node returns a create session response according to the create session request, where the create session response and the NAS message carry QoS rules;

or,

The RRC reconfiguration request is sent by the RAN node to the UE after receiving the radio bearer request and the NAS message sent by the first control plane function node, where the radio bearer request and the NAS message are Receiving, by the first control plane function node, a create session response returned by the second control plane function node, and sending the session response to the RAN node, where the create session response is that the second control plane function node receives the first control plane function And sending the session request sent by the node, and sending the QoS rule from the network policy control node according to the create session request, where the create session response and the NAS message carry the QoS rule.

In a seventh aspect, an embodiment of the present invention provides a radio access network RAN node, including:

a receiving module, configured to receive an uplink data packet of the terminal UE;

a processing module, configured to determine a radio bearer in which the uplink data packet is received by the receiving module, or a transmission priority identifier corresponding to a QoS class identifier carried in the uplink data packet, and carry the identifier in the uplink data packet a transmission priority identifier, where the transmission priority identifier is used to indicate a transmission priority of the uplink data packet between routers between the RAN node and a core network;

a sending module, configured to send the uplink data packet carrying the transmission priority identifier, where the routers located between the RAN node and the core network according to the transmission priority identifier carried in the uplink data packet The uplink data packet is transmitted to the core network.

In a possible implementation manner, the sending module is specifically configured to:

Mapping the radio bearer where the uplink data packet is located to the corresponding location of the transmission priority identifier On the core network bearer between the RAN node and the core network CN node, the uplink data packet is transmitted to the core network by using the core network bearer, where one core network bearer maps at least one radio bearer.

In a possible implementation manner, the QoS class identifier is located in a tunnel header of the uplink data packet.

In a possible implementation manner, the transmission priority identifier is located in an IP header field outside the tunnel of the uplink data packet.

In a possible implementation manner, the QoS level identifier includes at least one of a scheduling priority, a delay, a reliability, and a drop priority indication in the QoS parameter.

In a possible implementation manner, the QoS class identifier includes at least one of a packet priority indication PPI, a packet QoS identifier PQI, a flow priority indication FPI, a flow QoS identifier FQI, and a packet drop priority indication PDPI.

In an eighth aspect, an embodiment of the present invention provides a core network CN node, including:

a receiving module, configured to receive, by using a radio access network RAN node, an uplink data packet of the terminal UE;

And a processing module, configured to determine, according to the QoS rule of the UE, that the QoS level identifier carried in the uplink data packet is valid.

In a possible implementation manner, the QoS rule includes: a correspondence between an uplink filtering template and a QoS class identifier, a correspondence between a downlink filtering template and a QoS class identifier, an uplink filtering template, a downlink filtering template, and at least a Qos parameter. One.

In a possible implementation manner, the processing module is specifically configured to:

Determining, according to the uplink filtering template in the QoS rule of the UE, that the QoS level identifier carried in the uplink data packet is valid.

In a possible implementation manner, the QoS rule of the UE is obtained from a create session response returned by the network policy control node according to a create session request sent by a control plane function node of the core network to the control plane function node.

In a possible implementation manner, the QoS level identifier includes at least one of a scheduling priority, a delay, a reliability, and a drop priority indication in the QoS parameter.

In a possible implementation manner, the QoS level identifier includes a scheduling priority indication PPI, and a packet QoS. At least one of an identification PQI, a flow priority indication FPI, a flow QoS identity FQI, and a packet drop priority indication PDPI.

A ninth aspect, the embodiment of the present invention provides a core network CN node, including:

a determining module, configured to determine, according to a QoS rule corresponding to the terminal UE, a core network bearer mapped by the downlink data packet and a QoS level identifier corresponding to the downlink data packet of the UE;

a processing module, configured to carry, in the downlink data packet, the QoS class identifier determined by the determining module;

And a sending module, configured to send the downlink data packet by using the core network bearer determined by the determining module.

In a possible implementation manner, the CN node is a user plane function node of the core network, and the QoS rule is sent by the control plane function node of the core network to the user plane function node.

In a possible implementation manner, the QoS rule includes: a correspondence between an uplink filtering template and a QoS class identifier, a correspondence between a downlink filtering template and a QoS class identifier, an uplink filtering template, a downlink filtering template, and at least a Qos parameter. One.

In a possible implementation, the processing module is further configured to:

Determining, by the sending module, the QoS class identifier or the transmission priority identifier corresponding to the core network bearer, where the transmission priority identifier is used to indicate that the downlink data packet is in a core a transmission priority between the network and the routers between the RAN nodes; the transmission priority identifier is carried in the downlink data packet.

In a possible implementation manner, the QoS class identifier is located in a tunnel header of the downlink data packet.

In a possible implementation manner, the transmission priority identifier is located in an IP header field outside the tunnel of the downlink data packet.

In a possible implementation manner, the QoS level identifier is used to indicate a scheduling priority of the downlink data packet on the core network bearer; and/or

The QoS level identifier includes at least one of a scheduling priority, a delay, a reliability, and a drop priority indication in the QoS parameter.

In a possible implementation manner, the QoS class identifier includes a packet priority indication PPI, and a packet QoS. At least one of an identification PQI, a flow priority indication FPI, a flow QoS identity FQI, and a packet drop priority indication PDPI.

In a possible implementation manner, the QoS rule corresponding to the UE is obtained from a create session response returned by the network policy control node according to a create session request sent by the control plane function node of the core network to the control plane function node.

The tenth aspect of the present invention provides a radio access network RAN node, including:

a receiving module, configured to receive a downlink data packet sent by the core network CN node to the terminal UE;

a processing module, configured to determine a radio bearer corresponding to the QoS class identifier carried in the downlink data packet;

a sending module, configured to send the downlink data packet to the UE by using the radio bearer determined by the processing module;

or,

a processing module, configured to determine a radio bearer corresponding to a core network where the downlink data packet is located;

And a sending module, configured to send, by using the radio bearer, the downlink data packet to the UE according to the QoS class identifier.

In a possible implementation, the processing module is further configured to: delete a tunnel header of the downlink data packet.

In a possible implementation manner, the QoS level identifier includes at least one of a scheduling priority, a delay, a reliability, and a drop priority indication in the QoS parameter.

In a possible implementation manner, the QoS class identifier includes at least one of a packet priority indication PPI, a packet QoS identifier PQI, a flow priority indication FPI, a flow QoS identifier FQI, and a packet drop priority indication PDPI.

In a possible implementation manner, the sending module is specifically configured to:

And the downlink data packet is placed in a queue corresponding to the PPI in at least two queues corresponding to the radio bearer according to the PPI carried in the downlink data packet, and the queue is transmitted by using the radio bearer. The downlink data packet, wherein one PPI corresponds to one queue; or,

The RAN node performs the downlink data according to the PQI carried in the downlink data packet. The packet is placed in a queue corresponding to the PQI in at least two queues corresponding to the radio bearer, and the downlink data packet in the queue is transmitted by the radio bearer, where one PQI corresponds to one queue; or

And the RAN node, according to the FPI carried in the downlink data packet, placing the downlink data packet into a queue corresponding to the FPI in at least two queues corresponding to the radio bearer, and transmitting by using the radio bearer The downlink data packet in the queue, wherein one FPI corresponds to one queue; or

And the RAN node, according to the FQI carried in the downlink data packet, placing the downlink data packet into a queue corresponding to the FQI in at least two queues corresponding to the radio bearer, and transmitting by using the radio bearer The downlink data packet in the queue, wherein one FQI corresponds to one queue.

In a possible implementation manner, the sending module is specifically configured to:

The downlink data packet is placed in a queue corresponding to the radio bearer, and the downlink data packet in the queue is transmitted by using the radio bearer, where the radio bearer corresponds to one queue.

In a possible implementation manner, the sending module is further configured to: if it is determined that the queue is congested, determine, according to the PDPI carried in each downlink packet in the queue that is congested, a downlink data packet to be discarded.

In a possible implementation, one of the core network bearers corresponds to at least one radio bearer;

The processing module is specifically configured to: determine, in the at least one radio bearer corresponding to the core network bearer where the downlink data packet is located, the radio bearer corresponding to the PPI or PQI or FPI or FQI carried in the downlink data packet .

DRAWINGS

1 is a schematic diagram of a 3GPP EPS network architecture;

2 is a schematic structural diagram of a user plane protocol stack of a 3GPP network node;

3 is a schematic diagram of an SDF binding bearer in an uplink and a downlink;

4 is a schematic diagram of mapping relationships between SDFs, TFTs, and bearers;

Figure 5 is a schematic diagram of the relationship between EPS bearers and QoS parameters;

6 is a schematic diagram of a 1+N QoS bearer architecture according to an embodiment of the present invention;

FIG. 7 is a schematic diagram of system interaction based on a 1+N QoS architecture according to an embodiment of the present invention; FIG.

FIG. 8 is a schematic diagram of a process of establishing an NGBR bearer in a non-roaming scenario according to the first embodiment of the present invention;

9 is a schematic diagram of a process of establishing an NGBR bearer in a roaming scenario according to a second embodiment of the present invention;

10 is a schematic flowchart of performing QoS control on an uplink data packet on an NGBR bearer according to a third embodiment of the present invention;

11 is a schematic flowchart of performing QoS control on a downlink data packet on an NGBR bearer according to a fourth embodiment of the present invention;

FIG. 12 is a schematic diagram of mapping, by an UE, uplink data to different bearers according to an uplink filtering template according to an embodiment of the present disclosure;

FIG. 13 is a schematic diagram of an uplink data transmission process according to a first embodiment of the present invention; FIG.

14 is a schematic diagram of an uplink data transmission process in a second embodiment of the present invention;

FIG. 15 is a schematic diagram of an uplink data transmission process according to a third embodiment of the present invention; FIG.

FIG. 16 is a schematic diagram of mapping, by a CN node, downlink data to different bearers according to a downlink filtering template according to an embodiment of the present disclosure;

17 is a schematic diagram of a downlink data transmission process in a fourth embodiment of the present invention;

FIG. 18 is a schematic structural diagram of a UE according to a fifth embodiment of the present invention; FIG.

FIG. 19 is a schematic structural diagram of a RAN node according to a sixth embodiment of the present invention; FIG.

20 is a schematic structural diagram of a CN node in a seventh embodiment of the present invention;

21 is a schematic structural diagram of a CN node in an eighth embodiment of the present invention;

22 is a schematic structural diagram of a RAN node according to a ninth embodiment of the present invention;

23 is a schematic structural diagram of a UE in a tenth embodiment of the present invention;

Figure 24 is a schematic structural diagram of a RAN node in an eleventh embodiment of the present invention;

25 is a schematic structural diagram of a CN node in a twelfth embodiment of the present invention;

26 is a schematic structural diagram of a CN node in a thirteenth embodiment of the present invention;

FIG. 27 is a schematic structural diagram of a RAN node according to a fourteenth embodiment of the present invention.

detailed description

The present invention will be further described in detail with reference to the accompanying drawings, in which FIG. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.

In order to enable a more refined and more flexible QoS control in a 5G mobile communication network, a 1+N QoS bearer architecture as shown in FIG. 6 is proposed in the embodiment of the present invention, based on the QoS bearer architecture. The UE and the Core Network (CN) establish logical channels for services with different QoS requirements, and use different logical channels to transmit data to implement QoS control for different services. Where N is an integer greater than one.

The QoS bearer architecture includes one NGBR bearer and N GBR bearers.

The network reservation resource is not needed for one NGBR bearer, and the network provides best-effort service for the NGBR bearer. The main task of processing the data packet carried by the NGBR is to carry the QoS class identifier in the packet header. During the subsequent transmission process, each node performs QoS control of different data packets or data flows through the QoS class identifier carried in the packet header. The NGBR bearer is used for QoS control based on each data stream or packet.

For the N GBR bearers, the network needs to reserve resources when the bearer is established, and the network guarantees the QoS requirements of the services carried by the GBR. During the data transmission process, the network performs QoS control on different GBR bearers by maintaining the bearer context, and different GBR bearers correspond to different QoS requirements. The GBR bearer implements bearer-based QoS control.

Figure 7 is a schematic diagram of system interaction based on a 1+N-based QoS architecture. The UE maps uplink data packets (or uplink data flows) to GBR bearers or NGBR bearers according to an uplink filter template (UL filter) in the QoS rule. The uplink data packet (or uplink data stream) transmitted on a GBR bearer adopts the same QoS control, and the NGBR bearer transmits multiple uplink data packets (or uplink data streams), and the NGBR carries multiple uplink data packets transmitted on the bearer ( Or upstream data flow) using dynamic QoS control. And the user plane function (UPF) node on the core network side maps the downlink data packet (or downlink data stream) to the GBR bearer or the NGBR bearer by using a downlink filter template (DL filter), where one GBR bearer transmits The downlink data packet (or downlink data stream) adopts the same QoS control, and the NGBR bearer transmits multiple downlink data packets (or downlink data streams), and multiple downlink data packets (or downlink data streams) transmitted on the NGBR bearer are adopted. Dynamic QoS control.

The QoS control mode for the GBR bearer in the embodiment of the present invention is similar to the QoS control mode of the existing EPS bearer, and is not described in detail herein.

The following embodiments mainly describe how to perform different QoS control on multiple data packets or data flows carried by the NGBR.

Based on the above system architecture, in the first embodiment of the present invention, the establishment process of the NGBR bearer in the non-roaming scenario is as shown in FIG. 8 , and the details are as follows:

Step 801: The UE sends a Packet Data Unit (PDU) Session Connection Establish Request (Session Connection Establish Request) to the network.

Step 802: The control plane function (CPF) node of the core network acquires the subscription data after receiving the PDU session connection establishment request.

Step 803: The CPF node and the UPF node of the core network obtain the bearer ID (Bearer ID) and the uplink information of the NG3 interface through the information exchange. The NG3 interface is the interface between the RAN node and the UPF node, and the uplink information of the NG3 interface is the uplink of the NG3 interface. Tunnel identification;

Step 804: The CPF node sends a Create Session Request to the network policy control entity (such as a Policy Control and Charging Rules Function (PCRF)), where the created session request carries the bearer identifier. And current Radio Access Technology (RAT) information;

Step 805: The CPF node receives a create session response (Create Session Response) returned by the network policy control entity, where the create session response carries the bearer identifier and the QoS rule corresponding to the bearer identifier, where the QoS rule includes an uplink filtering template and One of the correspondence between the QoS parameters, the correspondence between the downlink filtering template and the QoS parameters, the uplink filtering template, the downlink filtering template, the Reflective QoS Indication (RQI), the AMBR, and the like. Or multiple;

Step 806: The CPF node sends a radio bearer setup request (Radio Bearer Request) and a non-access stratum (NAS) message to the RAN node, where the radio bearer setup request carries the bearer identifier, the RQI in the QoS rule, and The NG3 interface carries the uplink information, and the NAS message carries a default bearer request, where the default bearer request carries the bearer identifier and the QoS rule.

Step 807: The RAN node establishes a radio bearer by sending a radio resource control reconfiguration request (RRC Reconfiguration Request; RRC, Radio Resource Control) to the UE, and forwards the NAS message to the UE by using the RRC reconfiguration request, where the RRC reconfiguration request Carrying the NAS message;

Step 808: The UE acquires a QoS rule from the NAS message carried in the RRC reconfiguration request.

Step 809: The UE sends an RRC Reconfiguration Response to the RAN node.

Step 810: The RAN node returns a radio bearer setup response (Radio Bearer Response) to the CPF interface, where the radio bearer setup response carries the downlink information of the NG3 interface, and the downlink information of the NG3 interface is the downlink tunnel identifier of the NG3 interface.

Step 811: The UE sends a Create Bearer Response to the CPF node.

Step 812: The CPF node sends the NG3 interface downlink information and the QoS rule to the UPF node.

In the second embodiment of the present invention, the establishment process of the NGBR bearer in the roaming scenario is as shown in FIG. 9 , and the details are as follows:

Step 901: The UE sends a PDU session connection establishment request to the visited network.

Step 902: The Visit-Control Plan Function (V-CPF) node of the visited network acquires the subscription data after receiving the PDU session connection establishment request.

Step 903: The V-CPF and the Visit-User Plane (V-UPF) node of the visited network share the bearer identifier, the uplink information of the NG3 interface, and the downlink information of the S5 interface, where the NG3 interface is the RAN. The interface between the V-UPF and the V-UPF, the upstream information of the NG3 interface is the upstream tunnel identifier of the NG3 interface, and the S5 interface is the V-UPF and the home network user plane function. The downlink information of the interface S5 interface between the nodes of the Home-User plane Function (H-UPF) is the downlink tunnel identifier of the S5 interface.

Step 904: The V-CPF sends a create session request to the H-CPF, where the create session request carries the bearer identifier, the current RAT, and the downlink information of the S5 interface.

Step 905: The H-CPF and the H-UPF obtain the uplink information of the S5 interface and the downlink information of the S5 interface through the message exchange. The uplink information of the S5 interface is the uplink tunnel identifier of the S5 interface, and the downlink information of the S5 interface is the downlink tunnel identifier of the S5 interface.

Step 906: The H-CPF sends a create session request to the network policy control entity (such as a PCRF), where the create session request carries the bearer identifier and the current RAT.

Step 907: The PCRF specifies a Qos rule for the bearer identifier according to the create session request sent by the H-CPF, and returns a create session response to the H-CPF, where the create session response carries the Qos rule corresponding to the bearer identifier.

Step 908: The H-CPF and the H-UPF complete the correspondence between the bearer and the QoS rule on the H-UPF through message interaction.

Step 909: The H-CPF sends a session response to the V-CPF, where the session response carries the bearer identifier, the QoS rule, and the uplink information of the S5 interface.

Step 910: The V-CPF sends a radio bearer setup request and a NAS message to the RAN node, where the radio bearer setup request carries the bearer identifier, the RQI in the QoS rule, and the uplink information of the NG3 interface, and the NAS message carries the default bearer request. The default bearer request carries the bearer identifier and the QoS rule;

Step 911: The RAN node establishes a radio bearer by sending an RRC reconfiguration request to the UE, and forwards the NAS message to the UE by using the RRC reconfiguration request, where the RRC reconfiguration request carries the NAS message.

Step 912: The UE acquires a QoS rule from the NAS message carried in the RRC reconfiguration request.

Step 913: The UE sends an RRC reconfiguration response to the RAN node.

Step 914: The RAN node sends a radio bearer setup response to the V-CPF, where the radio bearer setup response carries the downlink information of the NG3 interface, and the downlink information of the NG3 interface is the downlink tunnel of the NG3 interface. Identification

Step 915: The UE returns a create bearer response to the V-CPF.

Step 916: The V-CPF sends the downlink information of the NG3 interface, the uplink information of the S5 interface, and the QoS rule to the V-UPF.

It should be noted that, for a scenario in which multiple CPFs and multiple UPFs are deployed in the same network, the process of establishing an NGBR bearer may refer to the process shown in Figure 9. The V-CPF and the H-CPF need to be replaced with the deployed in the network. Any two CPFs, and replacing the V-UPF and the H-UPF with any two UPFs deployed in the network, the any two CPFs can be represented as a first CPF and a second CPF, and the any two UPFs can represent It is the first UPF and the second UPF.

Based on the established NGBR bearer, in the third embodiment of the present invention, the detailed method flow of performing QoS control on the uplink data packet on the NGBR bearer in the 5G communication system is as shown in FIG. 10, and the details are as follows:

Step 1001: The UE determines, according to the QoS rule, the radio bearer mapped by the uplink data packet and the QoS class identifier corresponding to the uplink data packet.

The QoS rule on the UE side includes, but is not limited to, at least one of a correspondence between an uplink filtering template and a QoS class identifier, an uplink filtering template, and a Qos parameter.

Specifically, the UE determines to map the uplink data packet to the NGBR bearer according to the uplink filtering template in the QoS rule, and determines the radio bearer corresponding to the QoS class identifier according to the correspondence between the uplink filtering template and the QoS class identifier in the QoS rule. The radio bearer is used as a radio bearer mapped by the uplink data packet.

In a specific implementation, the process of determining, by the UE, the radio bearer according to the QoS rule is as follows: the UE maintains the correspondence between the uplink filtering template and the radio bearer in the QoS rule, and matches the uplink data packet with the uplink filtering template in the QoS rule, Determine the radio bearer of the uplink packet mapping.

In a specific implementation, the process of determining, by the UE, the radio bearer according to the QoS class identifier is as follows: the UE maintains the correspondence between the uplink filtering template, the QoS class identifier, and the radio bearer in the QoS rule, by using the uplink data packet and the QoS rule. The uplink filtering template performs matching to determine a QoS class identifier, and the radio bearer mapped by the uplink packet is determined by the QoS class identifier.

Specifically, the UE determines an uplink filtering mode that matches the uplink data packet in the QoS rule. And determining, according to the correspondence between the uplink filtering template and the QoS level identifier in the QoS rule, the QoS level identifier corresponding to the uplink filtering template that is matched by the uplink data packet.

Step 1002: The UE carries the QoS class identifier in an uplink data packet.

On the UE side, the QoS class identifier can be located in the IP header field of the uplink data packet, the Packet Data Convergence Protocol (PDCP) header field, the Radio Link Control (RLC) header field, and the medium access control. (Medium Access Control, MAC) header field or L1 layer header field.

Step 1003: The UE sends an uplink data packet by using a radio bearer.

Optionally, before the UE sends the uplink data packet, the QoS level identifier is carried in the uplink data packet.

The QoS class identifier carried in the uplink data packet is used to indicate the QoS level of the uplink data packet.

The QoS class identifier indicates a scheduling priority of the uplink data packet on the radio bearer. Specifically, the QoS class identifier is one of the QoS parameters.

In a specific implementation, the QoS class identifier includes, but is not limited to, any one of a scheduling priority, a delay, a reliability, and a drop priority indication in the QoS parameter, or a combination of any two or more.

In a specific implementation, the QoS class identifier includes a Packet Priority Indicator (PPI), a packet Qos identifier (PQI), a flow priority indicator (FPI), and a flow QoS identifier (Flow Qos). At least one of identifier, FQI) and Packet Discard Priority Indicator (PDPI).

Among them, PPI and PQI are defined based on data packets, and FPI and FQI are defined based on data streams. When all the packets in a data stream have the same PPI, the FPI is equivalent to the PPI. When all the packets in a data stream have the same PQI, the FQI is equivalent to the PQI.

The PQI and the FPI are used in a similar manner to the QCI of the EPS. The PQI indicates the combination of multiple Qos parameters such as scheduling priority, delay, and reliability of the data packet, and the FPI indicates the scheduling priority of the data flow. A combination of multiple QoS parameters such as level, delay, and reliability.

The PQI refers to a combination of multiple QOS parameters based on a packet, for example, a combination of a priority, a delay, and a packet loss rate of a defined packet is a PQI.

Wherein, the FQI refers to a combination of multiple QOS parameters based on the flow, such as the priority and delay of the flow. The combination of the packet loss rate is FQI.

In a specific embodiment, the UE sends multiple uplink data packets through the radio bearer, including but not limited to the following:

First, the same radio bearer corresponds to multiple queues, and one PPI or PQI or FPI or FQI corresponds to one queue.

In the implementation manner, the UE puts the uplink data packet into a queue corresponding to the PPI carried in the uplink data packet in at least two queues corresponding to the radio bearer according to the PPI carried in the uplink data packet, and transmits the queue through the radio bearer. Upstream packets, one of which corresponds to a queue; or,

The UE, according to the PQI carried in the uplink data packet, puts the uplink data packet into a queue corresponding to the PQI in at least two queues corresponding to the radio bearer, and transmits, by using the radio bearer, an uplink data packet in the queue, where, a PQI Corresponding to a queue; or,

The UE adds the uplink data packet to the queue corresponding to the FPI in at least two queues corresponding to the radio bearer according to the FPI carried in the uplink data packet, and transmits the uplink data packet in the queue through the radio bearer, where one FPI corresponds to a queue; or,

The UE, according to the FQI carried in the uplink data packet, puts the uplink data packet into a queue corresponding to the FQI in at least two queues corresponding to the radio bearer, and transmits, by using the radio bearer, an uplink data packet in the queue, where, an FQI Corresponds to a queue.

In this implementation, uplink packets with the same PPI (or PQI or FPI or FQI) are queued on a first in, first out basis. The radio bearer is scheduled according to the PPI (or PQI or FPI or FQI) carried by each data packet, and preferentially transmits data of a queue with a high PPI (or PQI or FPI or FQI). However, for fairness, in the case where the data of the PPI (or PQI or FPI or FQI) high queue is not transmitted, it is also possible to transmit the data of the queue with a low PPI (or PQI or FPI or FQI) to ensure the PPI (or PQI or FPI or FQI) low queue data will not lose the transmission opportunity. That is, PPI (or PQI or FPI or FQI) is an important reference factor in the scheduling algorithm.

In this implementation manner, when the same radio bearer simultaneously transmits uplink data packets of multiple UEs, scheduling is performed according to the PPI (or PQI or FPI or FQI) carried in each uplink data packet, and at the same time Consider openness.

In this implementation manner, if the UE determines that one of the at least two queues corresponding to the radio bearer is congested, the uplink data packet to be discarded is determined according to the PDPI carried in each uplink data packet in the congested queue.

The process of dropping a data packet is exemplified as follows: in a queue of a data buffer, consider the received data packets ready to enter the queue, starting from the end of the queue, according to the PDPI carried by each data packet and according to the first Drop the packet after the principle of dropping. For example, suppose a queue is expressed in order: ABCABC, where A, B, and C respectively represent the PDPI of the data packet, and the PDPI of the data packet represented by A, B, and C is from low to high, and the queue is full, assuming In addition, there are three packets whose PDPIs are A, B, and C need to enter the queue. Three packets need to be discarded. After the packets are discarded according to PDPI, the data priority of the queue is ABABAB.

Second, the same radio bearer corresponds to one queue.

In this implementation manner, the UE puts the uplink data packet into a queue corresponding to the radio bearer, and transmits the uplink data packet in the queue through the radio bearer.

In this implementation manner, the UE puts the uplink data packet into the queue corresponding to the radio bearer according to the principle of first in first out. The radio bearer sequentially schedules each uplink packet in the queue according to the principle of first in, first out, regardless of the PPI (or PQI or FPI or FQI) carried in the uplink packet.

In this implementation manner, if the UE determines that the queue corresponding to the radio bearer is congested, the uplink data packet to be discarded is determined according to the PDPI carried in each uplink data packet in the queue.

In this implementation manner, the PPI (or PQI or FPI or FQI) carried in the uplink data packet is used for scheduling priority determination of uplink data packets between multiple radio bearers.

In a specific implementation, an uplink data packet carrying a different PPI in a Packet Data Unit (PDU) session is mapped to a different radio bearer. Alternatively, uplink packets carrying different PQIs in one PDU session are mapped to different radio bearers. Alternatively, uplink packets carrying different FPIs in one PDU session are mapped to different radio bearers. Alternatively, uplink packets carrying different FQIs in one PDU session are mapped to different radio bearers.

The establishment process of the NGBR bearer according to the first embodiment and the second embodiment, on the UE side The QoS rule is that after receiving the RRC reconfiguration request sent by the RAN node, the UE obtains the NAS message carried in the RRC reconfiguration request.

Specifically, according to the number of control plane function nodes in which the core network participates in the NGBR bearer setup process, the RRC reconfiguration request has at least two specific obtaining manners:

First, in the case that the number of control plane function nodes participating in the NGBR bearer establishment process is one, the process of obtaining the RRC reconfiguration request is as follows:

After receiving the radio bearer request and the NAS message sent by the control plane function node of the core network, the RAN node sends the RRC reconfiguration request to the UE.

The radio bearer request and the NAS message are sent to the RAN node by the control plane function node of the core network after the receiving network policy control node returns a session response according to the create session request, and the session response and the NAS message carry the QoS rule.

Second, in the case where the number of control plane function nodes participating in the NGBR bearer establishment process is two, the process of obtaining the RRC reconfiguration request is as follows:

After receiving the radio bearer request and the NAS message sent by the first control plane function node, the RAN node sends the RRC reconfiguration request to the UE.

Specifically, the radio bearer request and the NAS message are sent to the RAN node after the first control plane function node receives the create session response returned by the second control plane function node. The session response is created and the QoS rule is carried in the NAS message.

Specifically, the second control plane function node receives the create session request sent by the first control plane function node, and obtains the QoS rule from the network policy control node according to the create session request, and then sends the create session response to the RAN node.

Step 1004: The RAN node receives an uplink data packet of the UE.

Specifically, the RAN node receives the uplink data packet of the UE by using the radio bearer.

Step 1005: The RAN node determines a radio bearer in which the uplink data packet is located or a transport priority identifier corresponding to the QoS level identifier carried in the uplink data packet, and carries the transport priority identifier in the uplink data packet.

The transmission priority identifier is used to indicate that the uplink data packet is between the RAN node and the core network. The priority of transmission between routers.

Step 1006: The RAN node sends an uplink data packet carrying the transmission priority identifier, and each router located between the RAN node and the core network transmits the uplink data packet to the core network according to the transmission priority identifier carried in the uplink data packet.

In a specific implementation, the RAN node maps the radio bearer in which the uplink data packet is located to the core network bearer between the RAN node and the CN node corresponding to the transmission priority identifier carried by the uplink data packet, and the core network bearer is The uplink data packet is transmitted to the core network, wherein one core network bearer map has at least one radio bearer.

In a specific implementation, on the RAN node side, the QoS class identifier is located in the tunnel header of the uplink data packet.

In a specific implementation, on the RAN node side, the transmission priority identifier is located in an IP header field outside the tunnel of the uplink data packet.

Step 1007: The CN node receives the uplink data packet of the UE through the RAN node.

Step 1008: The CN node determines, according to the QoS rule of the UE, that the QoS level identifier carried in the uplink data packet is valid.

In a specific implementation, the specific process of the CN node determining whether the QoS class identifier carried in the uplink data packet is valid is as follows: the CN node acquires the QoS class identifier corresponding to the uplink filtering template in the QoS rule of the saved UE, and the QoS class identifier is The QoS class carried in the uplink data packet indicates that the QoS class identifier carried in the uplink data packet is valid. If the two are consistent, it is determined that the QoS class identifier carried in the uplink data packet is invalid.

In the application, if the CN node determines that the QoS class identifier carried in the uplink data packet is invalid, and determines that the uplink data packet transmitted by the same core network bearer transmits the uplink data packet with the QoS class identifier invalid, the proportion of the uplink data packet that is invalid exceeds the preset threshold, The core network carries or issues a warning to the network management system.

The QoS rule of the UE that is saved by the CN node includes, but is not limited to, the correspondence between the uplink filtering template and the QoS level identifier, the correspondence between the downlink filtering template and the QoS level identifier, the uplink filtering template, and the downlink filtering. At least one of a template and a Qos parameter.

Specifically, the CN node determines the uplink data according to the uplink filtering template in the QoS rule of the UE. Whether the QoS class identifier carried in the packet is valid.

According to the establishment process of the NGBR bearer described in the first embodiment and the second embodiment, the manner in which the CN node obtains the QoS rule of the UE is: the network policy control node sends a session request according to the control node function node of the core network, The control plane function node returns a create session response, where the create session response carries the QoS rule of the UE.

Based on the established NGBR bearer, in the fourth embodiment of the present invention, the detailed method flow for performing QoS control on the downlink data packet on the NGBR bearer in the 5G communication system is as shown in FIG. 11 , and the details are as follows:

Step 1101: The CN node determines, according to the QoS rule corresponding to the UE, the core network bearer mapped by the downlink data packet and the QoS level identifier corresponding to the downlink data packet of the UE.

In a specific implementation, the process of determining, by the CN node, the core network bearer according to the QoS rule corresponding to the UE is as follows: the CN node maintains a correspondence between the downlink filtering template and the core network bearer in the QoS rule corresponding to the UE, and the downlink data packet is The downlink filtering template in the QoS rule is matched to determine the core network bearer of the downlink data packet mapping.

In a specific implementation, the process of determining, by the CN node, the QoS class identifier corresponding to the downlink data packet is as follows: the CN node maintains a correspondence between the downlink filtering template and the QoS class identifier in the QoS rule corresponding to the UE, by using the downlink data packet and the QoS. The downlink filtering template in the rule performs matching to determine the QoS class identifier.

The QoS rule corresponding to the UE saved on the CN side includes, but is not limited to, the correspondence between the uplink filtering template and the QoS level identifier, the correspondence between the downlink filtering template and the QoS level identifier, the uplink filtering template, and the downlink. Filter at least one of a template and a Qos parameter.

Step 1102: The CN node carries the QoS class identifier in the downlink data packet.

The QoS class identifier may be located in the tunnel header of the downlink data packet on the CN node side.

In implementation, the QoS class identifier is used to indicate the scheduling priority of the downlink data packet on the core network bearer. Specifically, the QoS class identifier is one of QoS parameters.

In a specific implementation, the QoS class identifier includes, but is not limited to, any one of a scheduling priority, a delay, a reliability, and a drop priority indication in the QoS parameter, or a combination of any two or more.

In a specific implementation, the QoS level identifier includes PPI, PQI, FPI, FQI, and PDPI. At least one of them.

According to the establishment process of the NGBR bearer described in the first embodiment and the second embodiment, the manner in which the CN node obtains the QoS rule corresponding to the UE is: the network policy control node creates a session request according to the control node function node of the core network, And returning a create session response to the control plane function node, where the create session response carries the QoS rule corresponding to the UE.

According to the establishment process of the NGBR bearer described in the first embodiment and the second embodiment, the manner in which the CN node obtains the QoS rule corresponding to the UE is: if the CN node is a user plane function node of the core network, the QoS rule is determined by the core. The control plane function node of the network is sent to the user plane function node.

Step 1103: The CN node sends the downlink data packet by using the core network bearer.

In a specific implementation, before transmitting the downlink data packet, the CN node determines the QoS class identifier or the transmission priority identifier corresponding to the core network bearer, where the transport priority identifier is used to indicate that the downlink data packet is in the core network and the RAN. The priority of transmission between routers between nodes;

The CN node carries the transmission priority identifier in the downlink data packet.

The transmission priority identifier may be located in an IP header field outside the tunnel of the downlink data packet.

Step 1104: The RAN node receives a downlink data packet sent by the CN node to the UE.

Step 1105: The RAN node determines the radio bearer corresponding to the QoS class identifier carried in the downlink data packet, and sends the downlink data packet to the UE by using the radio bearer; or the RAN node determines the radio corresponding to the core network bearer where the downlink data packet is located. And transmitting, by the radio bearer, the downlink data packet to the UE according to the QoS class identifier.

The core network bearer corresponds to at least one radio bearer. In a specific implementation, the RAN node determines, as the transmission of the downlink, the radio bearer corresponding to the PPI or the PQI or the FPI or the FQI carried in the downlink data packet, in the at least one radio bearer corresponding to the core network bearer in which the downlink data packet is located. The radio bearer of the packet.

In a specific implementation, before the RAN node sends the downlink data packet, the tunnel header of the downlink data packet is deleted.

In implementation, the UE routes the downlink data packet to the corresponding application according to the IP header of the received downlink data packet.

In a specific implementation, the specific implementation manner of the RAN node sending the downlink data packet includes multiple types, including but not limited to the following:

First, the same radio bearer corresponds to multiple queues, and one PPI or PQI or FPI or FQI corresponds to one queue.

In the implementation manner, the RAN node is configured to put the downlink data packet into a queue corresponding to the PPI in at least two queues corresponding to the radio bearer according to the PPI carried in the downlink data packet, and transmit the downlink data in the queue by using the radio bearer. a package in which one PPI corresponds to a queue; or,

The RAN node, according to the PQI carried in the downlink data packet, puts the downlink data packet into a queue corresponding to the PQI in at least two queues corresponding to the radio bearer, and transmits the downlink data packet in the queue by using the radio bearer, where One PQI corresponds to one queue; or,

The RAN node transmits the downlink data packet to the queue corresponding to the FPI in at least two queues corresponding to the radio bearer according to the FPI carried in the downlink data packet, and transmits the downlink data packet in the queue by using the radio bearer, where One FPI corresponds to one queue; or,

The RAN node, according to the FQI carried in the downlink data packet, puts the downlink data packet into a queue corresponding to the FQI in at least two queues corresponding to the radio bearer, and transmits the downlink data packet in the queue by using the radio bearer, where One FQI corresponds to one queue.

In this implementation, if it is determined that one of the at least two queues corresponding to the radio bearer is congested, the downlink data packet to be discarded is determined according to the PDPI carried in each downlink data packet in the congested queue.

In this implementation, downlink packets with the same PPI (or PQI or FPI or FQI) are queued on a first in, first out basis. The radio bearer performs scheduling according to the PPI (or PQI or FPI or FQI) carried by each downlink data packet, and preferentially transmits data of a queue with a high PPI (or PQI or FPI or FQI). However, for fairness, in the case where the data of the PPI (or PQI or FPI or FQI) high queue is not transmitted, it is also possible to transmit the data of the queue with a low PPI (or PQI or FPI or FQI) to ensure the PPI (or PQI or FPI or FQI) low queue data loses the opportunity to send.

In this implementation manner, when the same radio bearer transmits downlink packets of multiple UEs at the same time, scheduling is performed according to the PPI (or PQI or FPI or FQI) carried in each downlink data packet, and at the same time Consider openness.

Second, the radio bearer corresponds to a queue.

In this implementation manner, the RAN node puts the downlink data packet into a queue corresponding to the radio bearer, and transmits the downlink data packet in the queue through the radio bearer.

In this implementation manner, if the RAN node determines that the queue corresponding to the radio bearer is congested, the downlink data packet that needs to be discarded is determined according to the PDPI carried in each downlink data packet in the queue.

In this implementation manner, the downlink data packet is placed in a queue corresponding to the radio bearer according to the principle of first in first out. The radio bearer sequentially schedules each downlink packet in the queue according to the principle of first in first out, regardless of the PPI (or PQI or FPI or FQI) carried in the downlink packet.

In this implementation manner, the PPI (or PQI or FPI or FQI) carried in the downlink data packet is used for scheduling priority determination of downlink data packets between multiple radio bearers.

In this implementation manner, uplink data packets carrying different PPIs (or PQIs or FPIs or FQIs) in the same core network are mapped to different radio bearers.

The process of performing QoS control on a NGBR bearer on a NGBR bearer will be specifically described below through four specific embodiments.

FIG. 12 is a schematic diagram of mapping, by the UE, uplink data to different bearers according to an uplink filtering template. During the uplink data transmission, the UE maps the uplink data packet to different bearers through the uplink filtering template. The uplink data packets mapped to the GBR bearer are distinguished by the bearer identifier. The uplink data packets corresponding to different GBR bearers receive different QoS control, and the data packets carried by the same GBR receive the same QoS control. The uplink data packet carried by the NGBR is mapped, and the QoS parameter is identified in the uplink data packet by the QoS class identifier, and different QoS control is implemented according to different QoS class identifiers carried in the uplink data packet.

In the first embodiment, the process of uplink data transmission is as shown in FIG. 13, and the details are as follows:

Step 1301: The UE uses the uplink filtering template in the QoS rule to determine the radio bearer corresponding to the uplink data packet from the application layer, and carries the QoS class identifier corresponding to the uplink filtering template in the QoS rule in the uplink data packet, where The QoS class identifier may be carried in an IP header field, a PDCP header field, an RLC header field, a MAC header field, or an L1 header field of the uplink data packet;

Step 1302: The UE maps the uplink data packet to the radio bearer according to the QoS class identifier carried in the uplink filtering template or the uplink data packet in the QoS rule, and requests the RAN node to schedule the uplink data packet.

Step 1303: The RAN node allows the uplink data packet to be scheduled on the radio bearer.

Step 1304: The UE transmits the uplink data packet to the RAN node according to the data scheduling manner corresponding to the radio bearer.

Step 1305: The RAN node determines a transmission priority identifier corresponding to the radio bearer or the QoS class identifier, and carries the transmission priority identifier in the uplink data packet, where if there is a tunnel, the IP outside the tunnel of the uplink data packet The transport priority identifier is carried in the header field;

Step 1306: The transmission network between the RAN node and the CN node, that is, each IP router, determines the transmission priority of the transport layer according to the transmission priority identifier carried in the uplink data packet, and transmits the uplink data packet to the transmission priority according to the transmission priority. CN node;

Step 1307: The CN node verifies whether the QoS class identifier carried in the uplink data packet is valid according to the saved uplink filtering template in the QoS rule corresponding to the UE, so as to prevent the UE side from carrying the QoS class identifier maliciously.

In the second specific embodiment, the process of uplink data transmission is as shown in FIG. 14 , and the details are as follows:

Step 1401: The UE acquires the QoS class identifier corresponding to the uplink filtering template in the QoS rule, and carries the QoS class identifier in the IP header field, the PDCP header field, the RLC header field, the MAC header field, or the L1 header field of the uplink data packet. ;

Step 1402: The UE maps the uplink data packet to the radio bearer according to the QoS class identifier carried in the uplink data packet, and requests the RAN node to schedule the uplink data packet.

Step 1403: The RAN node allows the uplink data packet to be scheduled on the radio bearer.

Step 1404: The UE transmits the uplink data packet to the RAN node according to the data scheduling manner corresponding to the radio bearer.

Step 1405: The RAN node determines a transmission priority identifier corresponding to the radio bearer or the QoS class identifier, and carries the transmission priority identifier in the uplink data packet, where if there is a tunnel, the IP outside the tunnel of the uplink data packet The transport priority identifier is carried in the header field;

Step 1406: The transmission network between the RAN node and the CN node, that is, each IP router, determines the transmission priority of the transport layer according to the transmission priority identifier carried in the uplink data packet, and transmits the uplink data packet to the transmission priority according to the transmission priority. CN node;

Step 1407: The CN node verifies whether the QoS class identifier carried in the uplink data packet is valid according to the saved uplink filtering template in the QoS rule corresponding to the UE, so as to prevent the UE side from carrying the QoS class identifier maliciously.

In a third specific embodiment,

The process of uplink data transmission is shown in Figure 15, as follows:

Step 1501: The UE uses an uplink filtering template in the QoS rule to determine a radio bearer corresponding to an uplink data packet from the application layer.

Step 1502: The UE maps an uplink data packet to the radio bearer, and requests the RAN node to schedule the uplink data packet.

Step 1503: The RAN node allows the uplink data packet to be scheduled on the radio bearer.

Step 1504: The UE transmits the uplink data packet to the RAN node according to the data scheduling manner corresponding to the radio bearer.

Step 1505: The RAN node determines a transmission priority identifier corresponding to the radio bearer, and carries the transmission priority identifier in the uplink data packet. If the tunnel exists, the RAN node carries the IP header field outside the tunnel of the uplink data packet. The transmission priority identifier;

Step 1506: The transmission network between the RAN node and the CN node, that is, each IP router, determines the transmission priority of the transport layer according to the transmission priority identifier carried in the uplink data packet, and transmits the uplink data packet to the transmission priority according to the transmission priority. CN node.

FIG. 16 is a schematic diagram of mapping, by a CN node, downlink data to different bearers according to a downlink filtering template. During the downlink data transmission, the CN node maps the downlink data packet to different bearers through the downlink filtering template. The downlink data packets mapped to the GBR bearer distinguish different QoS control by the bearer identifier. The downlink data packet that is filtered to the NGBR bearer identifies the QoS parameter to the downlink data packet by using the QoS class identifier, and implements different QoS control according to different QoS class identifiers carried in the downlink data packet.

In the fourth specific embodiment, the process of downlink data transmission is as shown in FIG. 17, and the details are as follows:

Step 1701: The CN node uses the downlink filtering template in the QoS rule corresponding to the UE to determine the QoS class identifier corresponding to the downlink data packet sent by the application layer, and carries the QoS class identifier in the IP header field or tunnel header of the downlink data packet. Domain

Step 1702: The CN node determines a transmission priority identifier corresponding to the QoS level identifier, and carries the transmission priority identifier in an IP header field outside the tunnel of the downlink data packet.

Step 1703: The transmission network between the RAN node and the CN node, that is, each IP router determines the transmission priority of the downlink data packet at the transport layer according to the transmission priority identifier carried in the downlink data packet, and according to the transmission priority The downlink data packet is transmitted to the RAN node;

Step 1704: The RAN node determines the radio bearer according to the QoS class identifier carried in the downlink data packet, and transmits the downlink data packet to the UE by using a data scheduling manner corresponding to the radio bearer.

Step 1705: The UE routes the downlink data packet to the corresponding application according to the IP header of the downlink data packet.

In the fifth embodiment of the present invention, a UE is provided. For a specific implementation of the UE, refer to the description of the UE in the third embodiment of the present invention, and the repeated description is not repeated, as shown in FIG. The UE mainly includes:

a determining module 1801, configured to determine, according to the QoS rule, a radio bearer mapped by the uplink data packet and a QoS class identifier corresponding to the uplink data packet;

The processing module 1802 is configured to carry, in the uplink data packet, the QoS class identifier determined by the determining module;

The sending module 1803 is configured to send the uplink data packet by using the radio bearer.

Based on the same inventive concept, a sixth embodiment of the present invention provides a RAN node. For the specific implementation of the RAN node, refer to the description of the RAN node in the third embodiment, and the repeated description is not repeated, as shown in FIG. The RAN node mainly includes:

The receiving module 1901 is configured to receive an uplink data packet of the terminal UE.

The processing module 1902 is configured to determine, by the receiving module, the radio bearer where the uplink data packet is located or the transmission priority identifier corresponding to the QoS level identifier carried in the uplink data packet, where And carrying the transmission priority identifier in the uplink data packet, where the transmission priority identifier is used to indicate that the uplink data packet is preferentially transmitted between routers between the RAN node and the core network. level;

The sending module 1903 is configured to send the uplink data packet carrying the transmission priority identifier, and the routers located between the RAN node and the core network according to the transmission priority identifier carried in the uplink data packet The uplink data packet is transmitted to the core network.

A seventh embodiment of the present invention provides a CN node. For a specific implementation of the CN node, refer to the description of the CN node in the third embodiment, and the repeated description is not repeated, as shown in FIG. 20 . The CN node mainly includes:

The receiving module 2001 is configured to receive, by using a radio access network RAN node, an uplink data packet of the terminal UE;

The processing module 2002 is configured to determine, according to the QoS rule of the UE, that the QoS level identifier carried in the uplink data packet is valid.

Based on the same inventive concept, an eighth embodiment of the present invention provides a CN node. For the specific implementation of the CN node, refer to the description of the CN node in the fourth embodiment, and the repeated description is not repeated, as shown in FIG. The CN node mainly includes:

a determining module 2101, configured to determine, according to a QoS rule corresponding to the terminal UE, a core network bearer mapped by the downlink data packet and a QoS level identifier corresponding to the downlink data packet of the UE;

The processing module 2102 is configured to carry, in the downlink data packet, the QoS level identifier determined by the determining module;

The sending module 2103 is configured to send the downlink data packet by using the core network bearer determined by the determining module.

The ninth embodiment of the present invention provides a RAN node. For a specific implementation of the RAN node, refer to the description of the RAN node in the fourth embodiment, and the repeated description is not repeated, as shown in FIG. 22 . The RAN node mainly includes:

The receiving module 2201 is configured to receive a downlink data packet that is sent by the core network CN node to the terminal UE.

The processing module 2202 is configured to determine, according to the QoS class identifier carried in the downlink data packet, Radio bearer

The sending module 2203 is configured to send, by using the radio bearer determined by the processing module, the downlink data packet to the UE;

or,

The processing module 2202 is configured to determine, according to the core network where the downlink data packet is located, a radio bearer corresponding to the bearer;

The sending module 2203 is configured to send, by using the radio bearer, the downlink data packet to the UE according to the QoS class identifier.

In the tenth embodiment of the present invention, a UE is provided. For a specific implementation of the UE, refer to the description of the UE in the third embodiment of the present invention, and the repeated description is not repeated, as shown in FIG. The UE mainly includes a processor 2301 and a transceiver 2302, wherein the transceiver 2302 is configured to receive and transmit data under the control of the processor, and the processor 2301 is mainly configured to:

Determining, by the QoS rule, the radio bearer mapped by the uplink data packet and the QoS class identifier corresponding to the uplink data packet; carrying the QoS class identifier determined by the determining module in the uplink data packet; and instructing the transceiver 2302 to pass the The radio bearer transmits the uplink data packet.

The processor 2301 is configured to perform the functions of the determining module and the processing module in the fifth embodiment, and the transceiver 2302 is configured to complete the function of the sending module in the fifth embodiment under the control of the processor.

In the eleventh embodiment of the present invention, a RAN node is provided. For a specific implementation of the RAN node, refer to the description of the RAN node in the third embodiment of the present invention. As shown in FIG. 24, the RAN node mainly includes a processor 2401, a transceiver 2402, and a communication interface 2403. The transceiver 2402 and the communication interface 2403 are configured to receive and transmit data under the control of a processor. The processor 2401 is mainly used to:

Receiving, by the transceiver 2402, an uplink data packet of the terminal UE;

Determining, by the radio bearer in which the received uplink data packet is located, a transmission priority identifier corresponding to the QoS class identifier carried in the uplink data packet, and carrying the transmission priority identifier in the uplink data packet, where The transmission priority identifier is used to indicate a transmission priority of the uplink data packet between routers between the RAN node and the core network;

Transmitting, by the communication interface 2403, the uplink data packet carrying the transmission priority identifier, where the routers located between the RAN node and the core network perform the uplink according to the transmission priority identifier carried in the uplink data packet. The data packet is transmitted to the core network.

The processor 2401 is mainly used to complete the function of the processing module in the sixth embodiment, the transceiver 2402 is mainly used to complete the function of the receiving module in the sixth embodiment, and the communication interface 2403 is mainly used to complete the sending module in the sixth embodiment. The function of 1903.

Based on the same inventive concept, in a twelfth embodiment of the present invention, a CN node is provided. For a specific implementation of the CN node, refer to the description of the CN node in the third embodiment of the present invention. As shown in FIG. 25, the CN node mainly includes a processor 2501 and a communication interface 2502. The communication interface 2502 is configured to receive and transmit data under the control of a processor. The processor 2501 is mainly used to:

Instructing the communication interface 2502 to receive an uplink data packet of the terminal UE through the radio access network RAN node;

Determining, according to the QoS rule of the UE, that the QoS class identifier carried in the uplink data packet is valid.

The communication interface 2501 is configured to complete the function of the receiving module in the seventh embodiment under the control of the processor, and the processor 2501 is configured to complete the functions of the processing module in the seventh embodiment.

Based on the same inventive concept, a thirteenth embodiment of the present invention provides a CN node. For details of the CN node, refer to the description of the CN node in the fourth embodiment of the present invention. As shown in FIG. 26, the CN node mainly includes a processor 2601 and a communication interface 2602. The communication interface 2602 is configured to receive and transmit data under the control of a processor. The processor 2601 is mainly used to:

Determining, according to a QoS rule corresponding to the terminal UE, a core network bearer mapped by the downlink data packet and a QoS level identifier corresponding to the downlink data packet of the UE;

Carrying the QoS class identifier in the downlink data packet;

Instructing the communication interface 2602 to send the downlink data packet through the core network bearer.

The processor 2601 is configured to complete the functions of the determining module and the processing module in the eighth embodiment. The communication interface 2602 is configured to perform the function of the transmitting module in the eighth embodiment under the control of the processor 2601.

In the fourteenth embodiment of the present invention, a RAN node is provided. For a specific implementation of the RAN node, reference may be made to the description of the RAN node in the fourth embodiment of the present invention. As shown in FIG. 27, the RAN node mainly includes a processor 2701, a communication interface 2702, and a transceiver 2703. The communication interface 2702 and the transceiver 2703 are configured to receive and transmit data under the control of a processor. The processor 2701 is mainly used to:

Receiving, by the communication interface 2702, a downlink data packet sent by the core network CN node to the terminal UE;

Determining a radio bearer corresponding to the QoS class identifier carried in the downlink data packet, and instructing the transceiver 2703 to send the downlink data packet to the UE by using the radio bearer; or

Determining, by the core network, the radio bearer corresponding to the downlink data packet, and instructing the transceiver 2703 to send the downlink data packet to the UE according to the QoS class identifier by using the radio bearer.

The communication interface 2702 is used to complete the function of the receiving module 2201 in the ninth embodiment under the control of the processor, the processor 2701 is used to complete the function of the processing module in the ninth embodiment, and the transceiver 2703 is used in the processor. The function of the transmitting module in the ninth embodiment is completed under control.

Those skilled in the art will appreciate that embodiments of the present invention can be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware. Moreover, the invention can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) including computer usable program code.

The present invention has been described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (system), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flowchart illustrations and/or FIG. These computer program instructions can be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing device to produce a machine for the execution of instructions for execution by a processor of a computer or other programmable data processing device. In the implementation of the stream A device that is a process or a plurality of processes and/or a block diagram of a function specified in a block or blocks.

The computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device. The apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.

These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device. The instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

It is apparent that those skilled in the art can make various modifications and variations to the invention without departing from the spirit and scope of the invention. Thus, it is intended that the present invention cover the modifications and modifications of the invention

Claims (51)

A QoS control method for a QoS in a 5G communication system, comprising: Determining, by the terminal UE, the radio bearer mapped by the uplink data packet and the QoS class identifier corresponding to the uplink data packet according to the QoS rule; The UE carries the QoS class identifier in the uplink data packet; The UE sends the uplink data packet by using the radio bearer. The method according to claim 1, wherein the QoS rule comprises: at least one of a correspondence between an uplink filtering template and a QoS class identifier, an uplink filtering template, and a Qos parameter. The method according to claim 2, wherein the determining, by the UE, the QoS class identifier corresponding to the uplink data packet according to the QoS rule comprises: Determining, by the UE, an uplink filtering template that matches the uplink data packet in the QoS rule, and determining, according to a correspondence between an uplink filtering template and a QoS class identifier in the QoS rule, that the uplink data packet matches The QoS class identifier corresponding to the uplink filtering template. The method according to any one of claims 1 to 3, wherein the QoS class identifier is located in an Internet Protocol IP header field of the uplink data packet, a packet data convergence protocol PDCP header field, and a radio link control RLC header. Domain, medium access control MAC header domain or L1 layer header domain. The method according to any one of claims 1 to 4, wherein the QoS level identifier is used to indicate a scheduling priority of the uplink data packet on the radio bearer; and/or The QoS level identifier includes at least one of a scheduling priority, a delay, a reliability, and a drop priority indication in the QoS parameter. The method according to claim 5, wherein the QoS class identifier comprises at least a packet priority indication PPI, a packet QoS identification PQI, a flow priority indication FPI, a flow QoS identifier FQI, and a packet drop priority indication PDPI. One. The method of claim 6, wherein the transmitting, by the UE, the uplink data packet by using the radio bearer comprises: And the UE, according to the PPI carried in the uplink data packet, placing the uplink data packet into a queue corresponding to the PPI in at least two queues corresponding to the radio bearer, by using the radio bearer transmission station The uplink data packet in the queue, where one PPI corresponds to one queue; or The UE, according to the PQI carried in the uplink data packet, puts the uplink data packet into a queue corresponding to the PQI in at least two queues corresponding to the radio bearer, by using the radio bearer transmission station. The uplink data packet in the queue, where one PQI corresponds to one queue; or, The UE, according to the FPI carried in the uplink data packet, puts the uplink data packet into a queue corresponding to the FPI in at least two queues corresponding to the radio bearer, by using the radio bearer transmission station. The uplink data packet in the queue, where one FPI corresponds to one queue; or The UE, according to the FQI carried in the uplink data packet, puts the uplink data packet into a queue corresponding to the FQI in at least two queues corresponding to the radio bearer, by using the radio bearer transmission station. The uplink data packet in the queue, where one FQI corresponds to one queue. The method of claim 6, wherein the transmitting, by the UE, the uplink data packet by using the radio bearer comprises: The UE puts the uplink data packet into a queue corresponding to the radio bearer, and transmits the uplink data packet in the queue by using the radio bearer, where the radio bearer corresponds to one queue. The method of claim 7 or 8, wherein the method further comprises: And determining, by the UE, that the queue is congested, determining, according to the PDPI carried in each of the uplink data packets in the queue that is congested, an uplink data packet to be discarded. The method according to claim 6, wherein an uplink data packet carrying a different PPI in a packet data unit PDU session is mapped to a different radio bearer; or Uplink packets carrying different PQIs in a packet data unit PDU session are mapped to different radio bearers; or Uplink packets carrying different FPIs in a packet data unit PDU session are mapped to different Wireless bearer; or, Uplink packets carrying different FQIs in one packet data unit PDU session are mapped to different radio bearers. A QoS control method for a QoS in a 5G communication system, comprising: The radio access network RAN node receives the uplink data packet of the terminal UE; Determining, by the RAN node, a radio bearer in which the uplink data packet is located or a transport priority identifier corresponding to the QoS level identifier carried in the uplink data packet, and carrying the transport priority identifier in the uplink data packet, where The transmission priority identifier is used to indicate a transmission priority of the uplink data packet between routers between the RAN node and the core network; The RAN node sends the uplink data packet carrying the transmission priority identifier, and the routers located between the RAN node and the core network perform the uplink according to the transmission priority identifier carried in the uplink data packet. The data packet is transmitted to the core network. The method of claim 11, wherein the RAN node sends the uplink data packet carrying the transmission priority identifier, including: Mapping, by the RAN node, the radio bearer in which the uplink data packet is located to a core network bearer between the RAN node and the core network CN node corresponding to the transmission priority identifier, where the core network bears the The uplink data packet is transmitted to the core network, wherein one of the core network bearer mappings has at least one radio bearer. The method of claim 11 or 12, wherein the QoS class identifier is located in a tunnel header of the upstream data packet. The method according to any one of claims 11 to 13, wherein the transmission priority identifier is located in an IP header field outside the tunnel of the uplink data packet. The method according to any one of claims 11 to 14, wherein the QoS level identifier comprises at least one of a scheduling priority, a delay, a reliability, and a drop priority indication in the QoS parameter. The method according to claim 15, wherein the QoS class identifier comprises a packet priority indication PPI, a packet QoS identifier PQI, a flow priority indication FPI, and a flow QoS identifier FQI. And at least one of the packet drop priority indication PDPI. A QoS control method for a QoS in a 5G communication system, comprising: The core network CN node determines, according to the QoS rule corresponding to the terminal UE, the core network bearer mapped by the downlink data packet and the QoS level identifier corresponding to the downlink data packet of the UE; The CN node carries the QoS class identifier in the downlink data packet; The CN node sends the downlink data packet by using the core network bearer. The method of claim 17, wherein the CN node is a user plane function node of the core network, and the QoS rule is sent by the control plane function node of the core network to the user plane function node. The method according to claim 17 or 18, wherein the QoS rule includes a correspondence between an uplink filtering template and a QoS class identifier, a correspondence between a downlink filtering template and a QoS class identifier, an uplink filtering template, At least one of a downstream filtering template and a Qos parameter. The method according to any one of claims 17 to 19, wherein before the CN node sends the downlink data packet, the method includes: Determining, by the CN node, the QoS class identifier or the transmission priority identifier corresponding to the core network bearer, where the transport priority identifier is used to indicate that the downlink data packet is between the core network and the RAN node Transmission priority between routers; The CN node carries the transmission priority identifier in the downlink data packet. The method according to any one of claims 17 to 20, wherein the QoS class identifier is located in a tunnel header of the downlink data packet. The method of claim 21, wherein the transmission priority identifier is located in an IP header field outside the tunnel of the downlink data packet. The method according to any one of claims 17 to 22, wherein the QoS level identifier is used to indicate a scheduling priority of the downlink data packet on the core network bearer; and/or The QoS level identifier includes at least one of a scheduling priority, a delay, a reliability, and a drop priority indication in the QoS parameter. The method of claim 23, wherein the QoS class identifier comprises at least a packet priority indication PPI, a packet QoS identifier PQI, a flow priority indication FPI, a flow QoS identifier FQI, and a packet drop priority indication PDPI One. The method according to any one of claims 17 to 22, wherein the QoS rule corresponding to the UE is a function of creating a session sent from a network policy control node according to a control plane function node of the core network to the control plane function. The node returns the created session response obtained. A QoS control method for a QoS in a 5G communication system, comprising: The radio access network RAN node receives the downlink data packet sent by the core network CN node to the terminal UE; Determining, by the RAN node, a radio bearer corresponding to the QoS class identifier carried in the downlink data packet, and sending the downlink data packet to the UE by using the radio bearer; or The RAN node determines a radio bearer corresponding to the core network in which the downlink data packet is located, and sends the downlink data packet to the UE according to the QoS class identifier by using the radio bearer. The method according to claim 26, wherein the RAN node sends the downlink data packet to the UE by using the radio bearer, or the radio bearer identifies the QoS class according to the QoS class. Before the downlink data packet is sent to the UE, the method further includes: The RAN node deletes a tunnel header of the downlink data packet. The method according to claim 26 or 27, wherein the QoS level identifier comprises at least one of a scheduling priority, a delay, a reliability, and a drop priority indication in the QoS parameter. The method of claim 28, wherein the QoS class identifier comprises at least a packet priority indication PPI, a packet QoS identifier PQI, a flow priority indication FPI, a flow QoS identifier FQI, and a packet drop priority indication PDPI One. The method according to claim 29, wherein the RAN node transmits the downlink data packet to the UE by using the radio bearer, or the radio bearer according to the QoS class identifier The downlink data packet is sent to the UE, including: The RAN node performs the downlink data according to the PPI carried in the downlink data packet. The packet is placed in a queue corresponding to the PPI in at least two queues corresponding to the radio bearer, and the downlink data packet in the queue is transmitted by the radio bearer, where one PPI corresponds to one queue; or And the RAN node, according to the PQI carried in the downlink data packet, placing the downlink data packet into a queue corresponding to the PQI in at least two queues corresponding to the radio bearer, and transmitting by using the radio bearer The downlink data packet in the queue, where one PQI corresponds to one queue; or And the RAN node, according to the FPI carried in the downlink data packet, placing the downlink data packet into a queue corresponding to the FPI in at least two queues corresponding to the radio bearer, and transmitting by using the radio bearer The downlink data packet in the queue, wherein one FPI corresponds to one queue; or And the RAN node, according to the FQI carried in the downlink data packet, placing the downlink data packet into a queue corresponding to the FQI in at least two queues corresponding to the radio bearer, and transmitting by using the radio bearer The downlink data packet in the queue, wherein one FQI corresponds to one queue. The method according to claim 30, wherein the RAN node transmits the downlink data packet to the UE by using the radio bearer, or the radio bearer according to the QoS class identifier The downlink data packet is sent to the UE, including: The RAN node puts the downlink data packet into a queue corresponding to the radio bearer, and transmits the downlink data packet in the queue by using the radio bearer, where the radio bearer corresponds to one queue. The method of claim 30 or 31, wherein the method further comprises: If the RAN node determines that the queue is congested, the downlink data packet that needs to be discarded is determined according to the PDPI carried in each downlink packet in the queue that is congested. The method of claim 29, wherein one of the core network bearers corresponds to at least one radio bearer; Determining, by the RAN node, a radio bearer corresponding to the core network where the downlink data packet is located, include: The RAN node determines a radio bearer corresponding to the PPI or PQI or FPI or FQI carried in the downlink data packet in at least one radio bearer corresponding to the core network bearer in which the downlink data packet is located. A terminal UE, comprising: a determining module, configured to determine, according to the QoS rule, a radio bearer mapped by the uplink data packet and a QoS class identifier corresponding to the uplink data packet; a processing module, configured to carry, in the uplink data packet, the QoS level identifier determined by the determining module; And a sending module, configured to send the uplink data packet by using the radio bearer. The UE according to claim 34, wherein the QoS rule comprises: at least one of a correspondence between an uplink filtering template and a QoS class identifier, an uplink filtering template, and a Qos parameter. The UE according to claim 35, wherein the determining module is specifically configured to: Determining an uplink filtering template that matches the uplink data packet in the QoS rule, and determining, according to a correspondence between an uplink filtering template and a QoS class identifier in the QoS rule, the uplink that matches the uplink data packet Filters the QoS class identifier corresponding to the template. The UE according to any one of claims 34 to 36, wherein the QoS class identifier comprises a packet priority indication PPI, a packet QoS identification PQI, a flow priority indication FPI, a flow QoS identifier FQI, and a packet drop priority. Indicates at least one of the PDPIs. The UE according to claim 37, wherein the sending module is specifically configured to: And the uplink data packet is placed in a queue corresponding to the PPI in at least two queues corresponding to the radio bearer according to the PPI carried in the uplink data packet, and the queue is transmitted by using the radio bearer. The uplink data packet, wherein one PPI corresponds to one queue; or, And the uplink data packet is placed in a queue corresponding to the PQI in at least two queues corresponding to the radio bearer according to the PQI carried in the uplink data packet, and the queue is transmitted by using the radio bearer. The uplink data packet, wherein one PQI corresponds to one queue; or, And the uplink data packet is placed in a queue corresponding to the FPI in at least two queues corresponding to the radio bearer according to the FPI carried in the uplink data packet, and the queue is transmitted by using the radio bearer. The uplink data packet, wherein one FPI corresponds to one queue; or, And the uplink data packet is placed in a queue corresponding to the FQI in at least two queues corresponding to the radio bearer according to the FQI carried in the uplink data packet, and the queue is transmitted by using the radio bearer. The uplink data packet, wherein one FQI corresponds to one queue. The UE according to claim 37, wherein the sending module is specifically configured to: The uplink data packet is placed in a queue corresponding to the radio bearer, and the uplink data packet in the queue is transmitted by using the radio bearer, where the radio bearer corresponds to one queue. The UE according to claim 37 or 38, wherein the sending module is further configured to: If it is determined that the queue is congested, the uplink data packet that needs to be discarded is determined according to the PDPI carried in each of the uplink data packets in the queue that is congested. A radio access network RAN node, comprising: a receiving module, configured to receive an uplink data packet of the terminal UE; a processing module, configured to determine a radio bearer in which the uplink data packet is received by the receiving module, or a transmission priority identifier corresponding to a QoS class identifier carried in the uplink data packet, and carry the identifier in the uplink data packet a transmission priority identifier, where the transmission priority identifier is used to indicate a transmission priority of the uplink data packet between routers between the RAN node and a core network; a sending module, configured to send the uplink data packet carrying the transmission priority identifier, where the routers located between the RAN node and the core network according to the transmission priority identifier carried in the uplink data packet The uplink data packet is transmitted to the core network. The RAN node according to claim 41, wherein the sending module is specifically configured to: Mapping the radio bearer in which the uplink data packet is located to the core network bearer between the RAN node and the core network CN node corresponding to the transmission priority identifier, and transmitting the uplink data packet by using the core network bearer To the core network, wherein one of the core network bearer mappings has at least one Wireless bearer. A core network CN node, characterized in that it comprises: a determining module, configured to determine, according to a QoS rule corresponding to the terminal UE, a core network bearer mapped by the downlink data packet and a QoS level identifier corresponding to the downlink data packet of the UE; a processing module, configured to carry, in the downlink data packet, the QoS class identifier determined by the determining module; And a sending module, configured to send the downlink data packet by using the core network bearer determined by the determining module. The CN node according to claim 43, wherein the processing module is further configured to: Determining, by the sending module, the QoS class identifier or the transmission priority identifier corresponding to the core network bearer, where the transmission priority identifier is used to indicate that the downlink data packet is in a core a transmission priority between the network and the routers between the RAN nodes; the transmission priority identifier is carried in the downlink data packet. A radio access network RAN node, comprising: a receiving module, configured to receive a downlink data packet sent by the core network CN node to the terminal UE; a processing module, configured to determine a radio bearer corresponding to the QoS class identifier carried in the downlink data packet; a sending module, configured to send the downlink data packet to the UE by using the radio bearer determined by the processing module; or, a processing module, configured to determine a radio bearer corresponding to a core network where the downlink data packet is located; And a sending module, configured to send, by using the radio bearer, the downlink data packet to the UE according to the QoS class identifier. The RAN node according to claim 45, wherein the processing module is further configured to: delete a tunnel header of the downlink data packet. The RAN node according to claim 45 or 46, wherein the QoS class identifier comprises a packet priority indication PPI, a packet QoS identifier PQI, a flow priority indication FPI, a flow QoS label At least one of the FQI and the packet drop priority indication PDPI. The RAN node according to claim 47, wherein the sending module is specifically configured to: And the downlink data packet is placed in a queue corresponding to the PPI in at least two queues corresponding to the radio bearer according to the PPI carried in the downlink data packet, and the queue is transmitted by using the radio bearer. The downlink data packet, wherein one PPI corresponds to one queue; or, And the RAN node, according to the PQI carried in the downlink data packet, placing the downlink data packet into a queue corresponding to the PQI in at least two queues corresponding to the radio bearer, and transmitting by using the radio bearer The downlink data packet in the queue, where one PQI corresponds to one queue; or And the RAN node, according to the FPI carried in the downlink data packet, placing the downlink data packet into a queue corresponding to the FPI in at least two queues corresponding to the radio bearer, and transmitting by using the radio bearer The downlink data packet in the queue, wherein one FPI corresponds to one queue; or And the RAN node, according to the FQI carried in the downlink data packet, placing the downlink data packet into a queue corresponding to the FQI in at least two queues corresponding to the radio bearer, and transmitting by using the radio bearer The downlink data packet in the queue, wherein one FQI corresponds to one queue. The RAN node according to claim 48, wherein the sending module is specifically configured to: The downlink data packet is placed in a queue corresponding to the radio bearer, and the downlink data packet in the queue is transmitted by using the radio bearer, where the radio bearer corresponds to one queue. The RAN node according to claim 48 or 49, wherein the sending module is further configured to: if it is determined that the queue is congested, according to each of the downlink data packets in the queue that is congested The PDPI determines the downstream packets that need to be discarded. The RAN node according to claim 47, wherein one of said core network bearers corresponds to at least one radio bearer; The processing module is specifically configured to: determine, in the at least one radio bearer corresponding to the core network bearer where the downlink data packet is located, the radio bearer corresponding to the PPI or PQI or FPI or FQI carried in the downlink data packet .

Images