WO2018006249A1 - Procédé de régulation de qos dans un système de communication 5g et dispositif associé - Google Patents

Procédé de régulation de qos dans un système de communication 5g et dispositif associé Download PDF

Info

Publication number
WO2018006249A1
WO2018006249A1 PCT/CN2016/088444 CN2016088444W WO2018006249A1 WO 2018006249 A1 WO2018006249 A1 WO 2018006249A1 CN 2016088444 W CN2016088444 W CN 2016088444W WO 2018006249 A1 WO2018006249 A1 WO 2018006249A1
Authority
WO
WIPO (PCT)
Prior art keywords
data packet
qos
radio bearer
queue
uplink data
Prior art date
Application number
PCT/CN2016/088444
Other languages
English (en)
Chinese (zh)
Inventor
熊春山
韦安妮
吴义壮
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to PCT/CN2016/088444 priority Critical patent/WO2018006249A1/fr
Publication of WO2018006249A1 publication Critical patent/WO2018006249A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling

Definitions

  • 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.
  • wireless networks have become an infrastructure.
  • 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. .
  • QoS Quality of Service
  • the wireless resource request for downloading the file does not occupy the wireless resource of the call service.
  • 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.
  • 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.
  • 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).
  • eNodeB base station
  • S1-MME Serving Gateway
  • HSS Home Subscriber Server
  • S6a Diameter Type Protocol
  • S3 interface between the MME and the S4-SGSN (Serving GPRS Support Node, GPRS, General Packet Radio System).
  • S4-SGSN Serving GPRS Support Node, GPRS, General Packet Radio System
  • the MME is connected to other MMEs through an S10 interface.
  • GTP GPRS Tunneling Protocol
  • 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).
  • PGW Packet Data Network
  • the EPS system uses the indirect QoS guarantee mechanism to provide QoS guarantee for various Internet Protocol (IP) services.
  • IP Internet Protocol
  • 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.
  • SDFs Service Data Flows
  • Flow Filters IP data flow filter templates
  • 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).
  • EPS 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.
  • 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.
  • LTE Long Term Evolution
  • 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.
  • 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.
  • EPC Evolved Packet Core
  • the terminal can have multiple default bearers and IP addresses at the same time.
  • 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.
  • QCI QoS Class Identifier
  • ARP Allocation and Retention Priority
  • 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.
  • TFT Traffic Flow Template
  • TEID Tunnel Endpoint Identifier
  • 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:
  • IPv4 Protocol Number
  • IPv6 Next Header
  • IPv6 Local Address and Mask
  • Local Port Range Local Port Range
  • SPI IPSec Security Parameter Index
  • IPv4 Type of Service
  • IPv6 Traffic Class
  • IPv6 Traffic Class
  • IPv6 Traffic Class
  • 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.
  • PCC Policy and Charging Control
  • 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.
  • the Maximum Bit Rate is the maximum bit rate of the GBR.
  • Aggregate Maximum Bit Rate is classified into Access Point Name (APN)-AMBR and UE-AMBR.
  • 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.
  • 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.
  • an embodiment of the present invention provides a QoS control method for a QoS in a 5G communication system, including:
  • 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 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.
  • 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.
  • the determining, by the UE, the QoS level identifier corresponding to the uplink data packet according to the QoS rule including:
  • 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.
  • the QoS level identifier is used to indicate a scheduling priority of the uplink data packet on the radio bearer.
  • 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 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.
  • the sending, by the UE, the uplink data packet by using the radio bearer includes:
  • the UE 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 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 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 UE 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 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.
  • the method further includes:
  • an uplink data packet carrying a different PPI in a packet data unit PDU session is mapped to a different radio bearer;
  • Uplink packets carrying different PQIs in a packet data unit PDU session are mapped to different radio bearers;
  • Uplink packets carrying different FPIs in a packet data unit PDU session are mapped to different radio bearers;
  • Uplink packets carrying different FQIs in one packet data unit PDU session are mapped to different radio bearers.
  • 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. .
  • 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.
  • the NAS message carries the QoS rule;
  • 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.
  • 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;
  • 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 RAN node sends the uplink data packet that carries the transmission priority identifier, including:
  • 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 QoS class identifier is located in a tunnel header of the uplink data packet.
  • the transmission priority identifier is located in an IP header field outside the tunnel of the uplink data packet.
  • 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 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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 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.
  • 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.
  • 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.
  • the CN node is a user plane function node of the core network
  • the QoS rule is sent by the control plane function node of the core network to the user plane function node.
  • 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.
  • the CN node 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 QoS class identifier is located in a tunnel header of the downlink data packet.
  • the transmission priority identifier is located in an IP header field outside the tunnel of the downlink data packet.
  • the QoS level identifier is used to indicate a scheduling priority of the downlink data packet on the core network bearer.
  • 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 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.
  • 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.
  • 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;
  • 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 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.
  • the method further includes:
  • the RAN node deletes a tunnel header of the downlink data packet.
  • 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 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.
  • 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 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
  • the RAN node 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
  • the RAN node 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
  • the RAN node 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 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.
  • the method further includes:
  • 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.
  • 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.
  • 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
  • a sending module configured to send the uplink data packet by using the radio bearer.
  • 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.
  • 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 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.
  • the QoS level identifier is used to indicate a scheduling priority of the uplink data packet on the radio bearer.
  • 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 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.
  • the sending module is specifically configured to:
  • 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,
  • 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,
  • 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,
  • 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 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 sending module is further configured to:
  • 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.
  • an uplink data packet carrying a different PPI in a packet data unit PDU session is mapped to a different radio bearer;
  • Uplink packets carrying different PQIs in a packet data unit PDU session are mapped to different radio bearers;
  • Uplink packets carrying different FPIs in a packet data unit PDU session are mapped to different radio bearers;
  • Uplink packets carrying different FQIs in one packet data unit PDU session are mapped to different radio bearers.
  • 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.
  • 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;
  • 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.
  • 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.
  • the sending module is specifically configured to:
  • 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.
  • the QoS class identifier is located in a tunnel header of the uplink data packet.
  • the transmission priority identifier is located in an IP header field outside the tunnel of the uplink data packet.
  • 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 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.
  • 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;
  • 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.
  • 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.
  • the processing module is specifically configured to:
  • 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.
  • 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 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
  • a sending module configured to send the downlink data packet by using the core network bearer determined by the determining module.
  • the CN node is a user plane function node of the core network
  • the QoS rule is sent by the control plane function node of the core network to the user plane function node.
  • 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.
  • processing module is further configured to:
  • 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.
  • the QoS class identifier is located in a tunnel header of the downlink data packet.
  • the transmission priority identifier is located in an IP header field outside the tunnel of the downlink data packet.
  • the QoS level identifier is used to indicate a scheduling priority of the downlink data packet on the core network bearer.
  • 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 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.
  • 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
  • a processing module configured to determine a radio bearer corresponding to a core network where the downlink data packet is located
  • 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 processing module is further configured to: delete a tunnel header of the downlink data packet.
  • 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 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.
  • the sending module is specifically configured to:
  • 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
  • the RAN node 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
  • the RAN node 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 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 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.
  • 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 .
  • FIG. 1 is a schematic diagram of a 3GPP EPS network architecture
  • FIG. 2 is a schematic structural diagram of a user plane protocol stack of a 3GPP network node
  • FIG. 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
  • FIG. 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. 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
  • FIG. 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.
  • FIG. 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.
  • FIG. 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. 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
  • FIG. 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. 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.
  • FIG. 22 is a schematic structural diagram of a RAN node according to a ninth embodiment of the present invention.
  • FIG. 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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 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.
  • 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.
  • PDU Packet Data Unit
  • Session Connection Establish Request Session Connection Establish Request
  • Step 802 The control plane function (CPF) node of the core network acquires the subscription data after receiving the PDU session connection establishment request.
  • CPF control plane function
  • 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 is the protocol used to transport 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.
  • 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;
  • PCRF Policy Control and Charging Rules Function
  • 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.
  • Radio Bearer Request Radio Bearer Request
  • NAS non-access stratum
  • 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;
  • RRC Reconfiguration Request RRC
  • RRC Radio Resource Control
  • 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.
  • Radio Bearer Response Radio Bearer Response
  • 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.
  • 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.
  • V-CPF Visit-Control Plan Function
  • 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
  • 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.
  • the network policy control entity such as a PCRF
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • PDCP Packet Data Convergence Protocol
  • RLC Radio Link Control
  • MAC Medium Access Control
  • Step 1003 The UE sends an uplink data packet by using a radio bearer.
  • 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.
  • 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.
  • 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).
  • PPI Packet Priority Indicator
  • PQI Packet Qos identifier
  • FPI flow priority indicator
  • Flow Qos flow QoS identifier
  • PPI and PQI are defined based on data packets
  • FPI and FQI are defined based on data streams.
  • PPI and PQI are defined based on data packets
  • FPI and FQI are defined based on data streams.
  • 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.
  • 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.
  • the UE sends multiple uplink data packets through the radio bearer, including but not limited to the following:
  • the same radio bearer corresponds to multiple queues, and one PPI or PQI or FPI or FQI corresponds to one queue.
  • 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 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 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.
  • uplink packets with the same PPI 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).
  • PPI or PQI or FPI or FQI
  • 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.
  • 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
  • the data priority of the queue is ABABAB.
  • the same radio bearer corresponds to one queue.
  • 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.
  • 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.
  • the uplink data packet to be discarded is determined according to the PDPI carried in each uplink data packet in the queue.
  • 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.
  • an uplink data packet carrying a different PPI in a Packet Data Unit (PDU) session is mapped to a different radio bearer.
  • uplink packets carrying different PQIs in one PDU session are mapped to different radio bearers.
  • uplink packets carrying different FPIs in one PDU session are mapped to different radio bearers.
  • 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.
  • the RRC reconfiguration request has at least two specific obtaining manners:
  • the process of obtaining the RRC reconfiguration request is as follows:
  • the RAN node 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.
  • the RAN node 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the QoS class identifier is located in the tunnel header of the uplink data packet.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the QoS class identifier is used to indicate the scheduling priority of the downlink data packet on the core network bearer.
  • the QoS class identifier is one of QoS parameters.
  • 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.
  • the QoS level identifier includes PPI, PQI, FPI, FQI, and PDPI. At least one of them.
  • 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.
  • 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.
  • the CN node before transmitting the downlink data packet, 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 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.
  • 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 is not limited to the packet.
  • the tunnel header of the downlink data packet is deleted.
  • the UE routes the downlink data packet to the corresponding application according to the IP header of the received downlink data packet.
  • the specific implementation manner of the RAN node sending the downlink data packet includes multiple types, including but not limited to the following:
  • the same radio bearer corresponds to multiple queues, and one PPI or PQI or FPI or FQI corresponds to one queue.
  • 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.
  • the RAN node 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 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.
  • the downlink data packet to be discarded is determined according to the PDPI carried in each downlink data packet in the congested queue.
  • downlink packets with the same PPI 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).
  • the radio bearer corresponds to a queue.
  • 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.
  • the downlink data packet that needs to be discarded is determined according to the PDPI carried in each downlink data packet in the queue.
  • 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.
  • 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.
  • uplink data packets carrying different PPIs (or PQIs or FPIs or FQIs) in the same core network are mapped to different radio bearers.
  • FIG. 12 is a schematic diagram of mapping, by the UE, uplink data to different bearers according to an uplink filtering template.
  • 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.
  • 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 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.
  • 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.
  • 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 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.
  • 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.
  • 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 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.
  • FIG. 16 is a schematic diagram of mapping, by a CN node, downlink data to different bearers according to a downlink filtering template.
  • 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.
  • 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.
  • 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.
  • a UE is provided.
  • 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.
  • a sixth embodiment of the present invention provides a RAN node.
  • 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.
  • 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.
  • an eighth embodiment of the present invention provides a CN node.
  • 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.
  • 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;
  • 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.
  • a UE is provided.
  • 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:
  • the radio bearer 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.
  • a RAN node is provided.
  • 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:
  • the radio bearer in which the received uplink data packet is located 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;
  • 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
  • the communication interface 2403 is mainly used to complete the sending module in the sixth embodiment.
  • a CN node is provided.
  • 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:
  • 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.
  • a thirteenth embodiment of the present invention provides a CN node.
  • 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:
  • 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.
  • 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:
  • 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.
  • 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 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne un procédé de régulation de QoS dans un système de communication 5G et un dispositif associé permettant de fournir une régulation de QoS plus raffinée et plus souple pour un réseau de communication mobile 5G. Le procédé comprend les étapes suivantes : un UE terminal détermine, selon une règle de QoS, une porteuse radio mappée sur un paquet de données de liaison montante et une identification de classe de QoS correspondant au paquet de données de liaison montante ; l'UE transporte l'identification de classe de QoS dans le paquet de données de liaison montante ; et l'UE envoie le paquet de données de liaison montante par la porteuse radio.
PCT/CN2016/088444 2016-07-04 2016-07-04 Procédé de régulation de qos dans un système de communication 5g et dispositif associé WO2018006249A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/088444 WO2018006249A1 (fr) 2016-07-04 2016-07-04 Procédé de régulation de qos dans un système de communication 5g et dispositif associé

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/088444 WO2018006249A1 (fr) 2016-07-04 2016-07-04 Procédé de régulation de qos dans un système de communication 5g et dispositif associé

Publications (1)

Publication Number Publication Date
WO2018006249A1 true WO2018006249A1 (fr) 2018-01-11

Family

ID=60901505

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/088444 WO2018006249A1 (fr) 2016-07-04 2016-07-04 Procédé de régulation de qos dans un système de communication 5g et dispositif associé

Country Status (1)

Country Link
WO (1) WO2018006249A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110351202A (zh) * 2019-07-09 2019-10-18 北京锐安科技有限公司 5g核心网流量分组方法、装置、设备和计算机存储介质
CN112153662A (zh) * 2019-06-26 2020-12-29 中国电信股份有限公司 数据的传输方法、装置、系统和用户面功能装置
WO2022081832A3 (fr) * 2020-10-14 2022-07-07 Ofinno, Llc Réseau de communication

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1859300A (zh) * 2006-01-19 2006-11-08 华为技术有限公司 为移动终端用户传输多服务质量业务流的方法
WO2007079773A1 (fr) * 2006-01-10 2007-07-19 Telefonaktiebolaget L M Ericsson (Publ) Procede et dispositifs de filtrage de paquet de donnees dans une transmission
CN102238743A (zh) * 2010-05-05 2011-11-09 联芯科技有限公司 一种多路承载管理方法和装置
CN102612096A (zh) * 2012-03-06 2012-07-25 电信科学技术研究院 一种ip数据包的传输方法和设备
CN103312441A (zh) * 2012-03-15 2013-09-18 华为技术有限公司 数据包传输方法及系统、发送端设备与接收端设备
US20140101303A1 (en) * 2012-10-08 2014-04-10 Cisco Technology, Inc. System and method for throttling downlink data notifications in a network environment
US20140376563A1 (en) * 2013-06-25 2014-12-25 Qualcomm Incorporated Selectively transferring high-priority non-audio data over a quality of service channel

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2007079773A1 (fr) * 2006-01-10 2007-07-19 Telefonaktiebolaget L M Ericsson (Publ) Procede et dispositifs de filtrage de paquet de donnees dans une transmission
CN1859300A (zh) * 2006-01-19 2006-11-08 华为技术有限公司 为移动终端用户传输多服务质量业务流的方法
CN102238743A (zh) * 2010-05-05 2011-11-09 联芯科技有限公司 一种多路承载管理方法和装置
CN102612096A (zh) * 2012-03-06 2012-07-25 电信科学技术研究院 一种ip数据包的传输方法和设备
CN103312441A (zh) * 2012-03-15 2013-09-18 华为技术有限公司 数据包传输方法及系统、发送端设备与接收端设备
US20140101303A1 (en) * 2012-10-08 2014-04-10 Cisco Technology, Inc. System and method for throttling downlink data notifications in a network environment
US20140376563A1 (en) * 2013-06-25 2014-12-25 Qualcomm Incorporated Selectively transferring high-priority non-audio data over a quality of service channel

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
SAMSUNG: "Consideration for Flow based QoS Framework", 3GPP TSG-RAN WG3 MEETING #92 R3-161231, 27 May 2016 (2016-05-27), XP051094791 *
ZTE: "Further discussion on the RAN QoS control", 3GPP TSG-RAN WG2 MEETING #94 R2-163746, 27 May 2016 (2016-05-27), XP051095709 *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112153662A (zh) * 2019-06-26 2020-12-29 中国电信股份有限公司 数据的传输方法、装置、系统和用户面功能装置
CN110351202A (zh) * 2019-07-09 2019-10-18 北京锐安科技有限公司 5g核心网流量分组方法、装置、设备和计算机存储介质
CN110351202B (zh) * 2019-07-09 2023-01-20 北京锐安科技有限公司 5g核心网流量分组方法、装置、设备和计算机存储介质
WO2022081832A3 (fr) * 2020-10-14 2022-07-07 Ofinno, Llc Réseau de communication

Similar Documents

Publication Publication Date Title
US10966222B2 (en) Method, device, and system for processing reflective QoS characteristics
KR102423098B1 (ko) 무선 통신 네트워크에서 데이터 통신을 관리하는 방법 및 장치
RU2706178C1 (ru) Способ и устройство для управления qos
WO2020177764A1 (fr) Procédé de garantie de transmission de données et dispositif de communication
US20210204164A1 (en) Method and apparatus for microslicing wireless communication networks with device groups, service level objectives, and load/admission control
WO2020143788A1 (fr) Procédé de support d'une qualité de service d'une communication sensible au temps et dispositif de communication
US20090016344A1 (en) Method and apparatus for controlling bearers of service data flows
JP2018533328A (ja) 無線通信システムにおけるデータを送受信するための方法及びこれを支援する装置
WO2013131458A1 (fr) Procédé et dispositif de transmission de paquets de données ip
WO2017201677A1 (fr) Procédé et dispositif de transmission de données
JP7477661B2 (ja) データ伝送方法および装置
WO2012092888A2 (fr) Procédé, dispositif et système de contrôle de la qualité de service
CN108024284B (zh) 无线通信方法、用户设备接入网设备、和核心网设备
WO2014101505A1 (fr) Procédé pour aligner la qos d'un réseau wlan et la qos d'un réseau central à commutation de paquets
US20190239113A1 (en) Data transmission method and apparatus thereof
WO2018120183A1 (fr) Procédé et dispositif de transmission de données
WO2014071881A1 (fr) Procédé et dispositif de gestion du support d'un réseau de raccordement
WO2011120222A1 (fr) Procédé, dispositif et système pour l'activation et la désactivation d'un service prioritaire
WO2018006249A1 (fr) Procédé de régulation de qos dans un système de communication 5g et dispositif associé
WO2022012361A1 (fr) Procédé et appareil de communication
KR20210054976A (ko) 통신 시스템에서 릴레이를 사용한 통신 방법
WO2018171639A1 (fr) Procédé de communication sans fil, terminal, dispositif de réseau d'accès et système de réseau
Guo et al. Quality of service control
JP5855171B2 (ja) 改善されたサービス品質処理のための通信方法、通信プロトコル及び通信装置
Karthik et al. QoS in LTE and 802.16

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16907754

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16907754

Country of ref document: EP

Kind code of ref document: A1