WO2017198132A1 - 数据发送方法及装置 - Google Patents

数据发送方法及装置 Download PDF

Info

Publication number
WO2017198132A1
WO2017198132A1 PCT/CN2017/084390 CN2017084390W WO2017198132A1 WO 2017198132 A1 WO2017198132 A1 WO 2017198132A1 CN 2017084390 W CN2017084390 W CN 2017084390W WO 2017198132 A1 WO2017198132 A1 WO 2017198132A1
Authority
WO
WIPO (PCT)
Prior art keywords
flow label
data unit
application
qos
flow
Prior art date
Application number
PCT/CN2017/084390
Other languages
English (en)
French (fr)
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 中兴通讯股份有限公司
Publication of WO2017198132A1 publication Critical patent/WO2017198132A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/24—Negotiating SLA [Service Level Agreement]; Negotiating QoS [Quality of Service]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/08—Load balancing or load distribution

Definitions

  • the present invention relates to the field of communications, and in particular to a data transmission method and apparatus.
  • the fourth generation mobile communication technology (Four Generation, 4G) mobile communication system
  • data flows with the same Quality of Service (QoS) requirements are aggregated into bearers, and user plane network elements such as base stations and gateways are used for QoS.
  • QoS Quality of Service
  • the processing is all based on bearer as the minimum granularity.
  • the main network elements involved in the QoS scheme of the 4G system are as shown in Figure 1.
  • the user equipment (User Equipment, UE for short), the base station, and the Mobility Management Entity (MME) are also the core network control plane entities.
  • UE User Equipment
  • MME Mobility Management Entity
  • PCRF Policy and Charging Rules Function
  • the 4G QoS parameters include: QCI (QoS Class Identifier) and Allocation and Retention Priority (ARP).
  • QCI QoS Class Identifier
  • ARP Allocation and Retention Priority
  • the QoS parameters can uniquely identify a bearer.
  • the QCI is a standardized identifier.
  • Each QCI corresponds to a set of QoS parameters, including: Guaranteed Bit Rate (GBR) or non-GBR, priority, Packet Delay Budget, and packet loss. Parameters such as Packet Error Loss Rate.
  • GBR Guaranteed Bit Rate
  • non-GBR priority
  • Packet Delay Budget Packet Delay Budget
  • Parameters such as Packet Error Loss Rate.
  • the ARP identifier is used to indicate the priority of the bearer to be deleted or retained when overloaded.
  • the QoS parameters include: Aggregate Maximum Bit Rate (AMBR).
  • AMBR includes: UE-AMBR (the maximum bit rate of all non-GBR bearers aggregated by the UE) and APN-AMBR (the maximum bit rate of the non-GBR bearers aggregated by the user on the Access Point Name (APN)).
  • APN Access Point Name
  • the QoS parameters can be adopted.
  • the radio bearers on the air interface, the S1 interface bearer, and the S5/S8 interface bearer are respectively 1:1:1 mapping;
  • the bearers on the S1 interface and the S5/S8 interface adopt the segmented user-level GPRS tunneling protocol ( The GPRS Tunnelling Protocol for the user plane (GTP-U) tunnel is transmitted in a manner.
  • GTP-U The GPRS Tunnelling Protocol for the user plane
  • the QoS parameters include: Maximum Bit Rate (MBR) and Guaranteed Bit Rate (GBR).
  • the existing QoS guarantee mechanism requires the network or terminal to identify a service data packet according to the service filter, thereby applying corresponding QoS to the identified data packet.
  • this method often cannot notify the UE of the QoS parameters of the uplink data, and specifically has the following problems: a) different service data streams for the same application, although they have the same QoS, but have different service filters, in order to be able to notify the UE.
  • the uplink QoS of the service data flow requires interaction between the network and the terminal, thereby generating unnecessary signaling.
  • IP Internet Protocol
  • Embodiments of the present invention provide a data sending method and apparatus, to at least solve related technologies The problem of large signaling load of data transmission when performing QoS control.
  • a data sending method including: receiving a downlink data unit of a service carrying a flow label sent by a user plane function entity, where the flow label is used in a protocol data unit (Protocol Data Unit)
  • the PDU is a data stream that uniquely identifies the application in the session; the downlink data unit is sent to the user equipment UE by the radio bearer corresponding to the flow label.
  • the method before receiving the downlink data unit of the application carrying the flow label sent by the user plane function entity, the method further includes: the user plane function entity receiving the service quality QoS carried by the policy function entity for the application and carrying the flow label The user plane function entity marks the flow label in the downlink data unit of the received application according to the QoS policy; the user plane function entity sends the downlink data unit marked with the flow label to the access network.
  • the QoS policy further carries at least one of the following information: an upstream description and/or a downstream description, a QoS parameter, where the QoS parameter includes at least a QoS category identifier QCI.
  • the QoS parameter further includes at least one of the following information: an allocation hold priority ARP, and a guaranteed bandwidth GBR.
  • the uplink description or the downlink description includes at least one of the following: an Ethernet frame header, a packet switching label, an IP triplet, an IP quintuple, and a Uniform Resource Locator (URL). ); operator-defined application identifier.
  • the user plane function entity marking the flow label in the downlink data unit of the received application according to the QoS policy includes: the user plane function entity determines the downlink data unit according to the downlink description, and marks the flow in the downlink data unit. label.
  • the method before the downlink data unit is sent to the user equipment UE by using the radio bearer corresponding to the flow label, the method further includes: receiving the QoS policy carried by the policy function entity for the application and carrying the flow label; establishing according to the QoS policy or Modify the radio bearer and save the correspondence between the stream tag and the radio bearer.
  • the downlink data unit includes at least one of the following: an IP data packet; Non-IP PDU; Ethernet frame.
  • a data sending method including: receiving an uplink data unit of an application carrying a flow label sent by an access network AN, where the flow label is used in a protocol data unit PDU session A data stream that uniquely identifies the application; determines whether to send the upstream data unit to the data network based on the flow label.
  • determining whether to send the uplink data unit to the data network according to the flow label includes: receiving the service quality QoS policy carried by the policy function entity for the application and carrying the flow label; and determining the flow label carried by the uplink data unit For the flow label or the equivalent flow label carried in the QoS policy, the uplink data unit is sent to the data network, where the equivalent flow label is a flow label in the QoS policy with the same QoS parameter as the QoS policy.
  • the method before receiving the uplink data unit of the application carrying the flow label sent by the access network AN, the method further includes: the AN receiving the uplink data unit sent by the user equipment UE by using the radio bearer; and the AN being in the uplink data unit. Marking a flow label or an equal flow label corresponding to the radio bearer, wherein the equal stream label is a flow label in a QoS policy having the same QoS parameter as the QoS policy received by the AN; the AN will be marked with a flow label or an equivalent flow label
  • the uplink data unit is sent to the user plane function entity.
  • the method before the AN receives the uplink data unit sent by the user equipment UE by using the radio bearer, the method further includes: determining, by the UE, the radio bearer corresponding to the uplink data unit according to the obtained QoS policy of the application; The uplink data unit is sent to the AN.
  • the method before receiving, by the access network AN, the uplink data unit of the application carrying the flow label, the method further includes: receiving, by the AN, the uplink data unit that carries the flow label sent by the user equipment UE by using the radio bearer; The AN determines that the outflow label is a flow label or an equal flow label corresponding to the radio bearer, and the AN sends the uplink data unit marked with the flow label to the user plane function entity, where the equivalent stream label is corresponding to the application received by the AN.
  • the QoS policy has flow labels in the QoS policy with the same QoS parameters.
  • the QoS policy further carries at least one of the following information: an upstream description and/or a downstream description, a QoS parameter, where the QoS parameter includes at least a QoS category label. Know QCI.
  • the uplink description or the downlink description includes at least one of the following: an Ethernet frame header, a packet switching label, an IP triplet, an IP quintuple, a uniform resource locator URL, and an operator-defined application. logo.
  • the QoS parameter further includes at least one of the following information: an allocation hold priority ARP, and a guaranteed bandwidth GBR.
  • the uplink data unit includes at least one of the following: an IP data packet; a non-IP PDU; an Ethernet frame.
  • a data transmitting apparatus including: a first receiving module, configured to receive a downlink data unit of a service carrying a flow label sent by a user plane function entity, where the flow label is used The data stream is uniquely identified in the protocol data unit PDU session; the sending module is configured to send the downlink data unit to the user equipment UE by using the radio bearer corresponding to the flow label.
  • a data transmitting apparatus including: a second receiving module, configured to receive an uplink data unit of an application carrying a flow label sent by an access network AN, where the flow label is used for The data stream of the application is uniquely identified in the protocol data unit PDU session; the determining module is configured to determine whether to send the uplink data unit to the data network based on the flow label.
  • a storage medium comprising a stored program, wherein the program is executed to perform the method of any of the above.
  • a processor for running a program wherein the program is executed to perform the method of any of the above.
  • the AN receives the downlink data unit of the application carrying the flow label sent by the user plane function entity, and sends the downlink data unit to the user equipment UE by using the radio bearer corresponding to the flow label, thereby implementing the core network without bearer and wireless air interface.
  • Pre-configuration and dynamic adjustment of the QoS guarantee mechanism of the QoS configuration parameters effectively solve the problems of high signaling load and communication delay in data transmission during QoS control in the related art.
  • FIG. 1 is a schematic diagram of a QoS control system of a 4G system in the related art
  • FIG. 2 is a schematic diagram of a next generation wireless communication system in the related art
  • FIG. 3 is a flowchart of a data sending method according to an embodiment of the present invention.
  • FIG. 5 is a flowchart of QoS authorization and guarantee for an application according to an embodiment of the present invention.
  • FIG. 6 is a flowchart of UP sending downlink data according to an embodiment of the present invention.
  • FIG. 7 is a flowchart of a UE transmitting uplink data according to an embodiment of the present invention.
  • FIG. 8 is a structural block diagram of a data transmitting apparatus according to an embodiment of the present invention.
  • FIG. 9 is a block diagram showing the structure of another data transmitting apparatus according to an embodiment of the present invention.
  • FIG. 3 is a flowchart of a data sending method according to an embodiment of the present invention. As shown in FIG. 3, the process includes the following steps:
  • Step S302 the access network AN receives the downlink data unit of the application carrying the flow label sent by the user plane function entity, where the flow label is used to uniquely identify the data stream of the application in the protocol data unit PDU session;
  • Step S304 the AN sends the downlink data unit to the radio bearer corresponding to the flow label.
  • User equipment UE User equipment
  • the AN sends the downlink data unit to the UE by using the radio bearer corresponding to the flow label, and implements the QoS guarantee mechanism for the core network without bearer, the wireless air interface pre-configuration, and the dynamic adjustment of the QoS configuration parameter, which effectively solves the related technologies.
  • the signaling load of data transmission is high, and there is a problem of communication delay.
  • the method before the access network AN receives the downlink data unit of the application carrying the flow label sent by the user plane function entity, the method further includes: the user plane function entity receiving the policy function entity to carry the application for the application A quality of service QoS policy with a flow label; the user plane function entity marks the flow label in the downlink data unit of the received application according to the QoS policy; the user plane function entity sends the downlink data unit marked with the flow label to the AN.
  • the QoS policy further carries at least one of the following: an uplink description and/or a downstream description, a QoS parameter, where the QoS parameter includes at least a QoS category identifier QCI.
  • the QoS parameter further includes at least one of the following: an allocation hold priority ARP, a guaranteed bandwidth GBR.
  • the upstream description or the downstream description includes at least one of the following: an Ethernet frame header; a packet switched label; an IP triplet; an IP quintuple; a uniform resource locator URL; The defined application ID.
  • the user plane function entity marking the flow label in the downlink data unit of the received application according to the QoS policy includes: the user plane function entity determines the downlink data unit according to the downlink description, and is in the downlink data unit. Mark the stream label.
  • the method before the AN sends the downlink data unit to the user equipment UE by using the radio bearer corresponding to the flow label, the method further includes: the AN receiving the QoS policy carried by the policy function entity for the application and carrying the flow label; The AN establishes or modifies the radio bearer according to the QoS policy, and saves the correspondence between the flow label and the radio bearer.
  • the flow label and the radio bearer may be in a many-to-one relationship.
  • the downlink data unit includes at least one of the following: an IP number. Packet; non-IP PDU; Ethernet frame.
  • FIG. 4 is a flowchart of another data sending method according to an embodiment of the present invention. As shown in FIG. 4, the process includes the following steps:
  • Step S402 the user plane function entity receives an uplink data unit of the application carrying the flow label sent by the access network AN, where the flow label is used to uniquely identify the data stream of the application in the protocol data unit PDU session;
  • Step S404 the user plane function entity determines whether to send the uplink data unit to the data network according to the flow label.
  • the user plane function entity receives the uplink data unit of the application carrying the flow label sent by the access network AN, and determines whether to send the uplink data unit to the data network according to the flow label, so that the core network has no bearer.
  • the wireless air interface pre-configuration and the QoS guarantee mechanism for dynamically adjusting the QoS configuration parameters effectively solve the problems of high signaling load and communication delay in data transmission during QoS control in the related art.
  • determining, by the user plane function entity, whether to send the uplink data unit to the data network according to the flow label includes: the user plane function entity receiving the service quality QoS policy for the application and carrying the flow label for the application If the user plane function entity determines that the flow label carried by the uplink data unit is a flow label or an equivalent flow label carried in the QoS policy, the user plane function entity sends the uplink data unit to the data network, where the equivalent flow label is A flow label in a QoS policy with the same QoS parameters as the QoS policy.
  • the method before the user plane function entity receives the uplink data unit of the application that carries the label label sent by the access network AN, the method further includes: the AN receiving the uplink data unit sent by the user equipment UE by using the radio bearer.
  • the AN marks the flow label or the equivalent flow label corresponding to the radio bearer in the uplink data unit, where the equivalent flow label is a flow label in the QoS policy having the same QoS parameter as the QoS policy received by the AN; the AN will be marked with The upstream data unit of the flow label or the equivalent flow label is sent to the user plane function entity.
  • the user equipment UE is received by the AN and sent by the radio bearer.
  • the uplink data unit is further configured to: determine, by the UE, the radio bearer corresponding to the uplink data unit according to the obtained QoS policy corresponding to the application, and send the uplink data unit to the AN by using the radio bearer.
  • the method before the user plane function entity receives the uplink data unit that is sent by the access network AN and carries the labeling application, the method further includes: the AN receiving the carried stream sent by the user equipment UE by using the radio bearer.
  • the uplink data unit of the label if the AN determines that the flow label is a flow label or an equivalent flow label corresponding to the radio bearer, the AN sends the uplink data unit marked with the flow label to the user plane function entity, where the equivalent stream label is
  • the QoS policy corresponding to the application received by the AN has a flow label in the QoS policy with the same QoS parameter.
  • the QoS policy further carries at least one of the following: an uplink description and/or a downstream description, a QoS parameter, where the QoS parameter includes at least a QoS category identifier QCI.
  • the uplink description or the downlink description includes at least one of the following: an Ethernet frame header, a packet switching label, an IP triplet, an IP quintuple, a uniform resource locator URL, and an operator-defined application. logo.
  • the QoS parameter further includes at least one of the following: an allocation hold priority ARP, a guaranteed bandwidth GBR.
  • the foregoing uplink data unit includes at least one of the following: an IP data packet; a non-IP PDU; an Ethernet frame.
  • the policy function entity carries the corresponding flow label in the QoS policy formulated for the application, and provides the same to the user plane function entity, the AN and the UE, and the user plane function entity applies the downlink data according to the QoS policy.
  • the unit marks the flow label (or the AN label flow label), the AN sends the data to the UE according to the flow label by using the corresponding radio bearer, and the AN marks the flow label corresponding to the radio bearer in the uplink data unit of the application, and the UP passes the QoS policy check. Whether the flow label of the uplink data unit is correct to determine whether to forward the uplink data unit to the data network.
  • the QoS control of the core network without bearer, the wireless air interface pre-configuration, and the dynamic adjustment of the QoS configuration parameters can be implemented, thereby effectively solving the communication delay and signaling existing in the related art. High load problems.
  • the following provides a method for performing QoS authorization and guarantee for an application in the control of quality of service according to an embodiment of the present invention.
  • the process of performing QoS authorization and guarantee for the application as shown in FIG. 5, mainly includes the following steps:
  • Step S501 the UE establishes a PDU session with the network.
  • the control plane function entity CP authorizes the default QoS parameters for the PDU session, including the QoS Class Identifier (QCI) and the Allocation and Retention Priority (ARP (optional)).
  • QCI is used to indicate an indicator for providing specific data forwarding behavior (such as packet loss rate, delay, etc.) to the application service flow.
  • the ARP parameter may be a value, or a set of values, indicating that the application resource may be used by other
  • the application preempts the application to preempt the resources and/or priorities of other applications.
  • a tunnel is established between the AN and the user plane function entity UP, and a default radio bearer corresponds to the tunnel.
  • the QoS of the radio bearer is the default.
  • QCI and ARP (optional).
  • step S502a the AF service information is provided and confirmed: the UE interacts with the application layer of the application to negotiate the application to be initiated, and the application function entity AF provides service information to the core network CP function entity, where the service information includes the flow description and the requested QoS. parameter.
  • the stream description may be layer 2, layer 3 or layer 4 filter information, or more than 4 layers of stream description information.
  • Step S502b application information report and confirmation: UP performs application detection on the user plane data, and provides application information description to the CP, where the application information description carries flow description information, where the flow description information may be layer 2, layer 3 or Layer filter information or stream description information of more than 4 layers.
  • Step S502c Resource request of the UE: The UE sends a resource request message to the CP, where the message carries the flow description information and the requested QoS parameter, where the flow description information may be Layer 2, Layer 3 or 4 layers of filter information.
  • the Layer 2 filter information may be an Ethernet frame header or a packet switched label; the Layer 3 or Layer 4 filter information is an IP triplet and an IP quintuple; and the Layer 4 or more stream description information may be a Uniform Resource Locator URL or Is the application ID Application Id defined by the operator.
  • the Application Id provided by the UE to the network is the Application Id that the CP provides to the UE after the UE accesses the network.
  • the Application Id identifies the correspondence between the Application Id and the operating system application identifier provided by the CP to the UE after the UE accesses the network, the correspondence between the Application Id and the server IP address of the third-party application, the IP triplet, or Application Id and The correspondence of URLs of third-party applications.
  • the Application Id is used to identify the application information detected by the packet detection mechanism based on the network configuration on the UP.
  • the UE in the embodiment of the present invention, before the UE sends the resource request message, the UE first checks whether the application Id corresponding to the application already has a corresponding radio bearer (that is, whether the Application Id has the corresponding network side authorized QoS). information). If not, the UE performs step S502c; if yes, the UE further checks whether the radio bearer is a GBR bearer (ie, whether there is a GBR parameter in the QoS information authorized by the network side). If yes, the UE performs step S502c.
  • the radio bearer is a GBR bearer (ie, whether there is a GBR parameter in the QoS information authorized by the network side). If yes, the UE performs step S502c.
  • the UE does not need to further check whether the radio bearer is a GBR bearer, that is, the UE only needs to check whether the corresponding radio bearer exists in the Application Id. If not, the UE performs step S502c.
  • Step S503 Policy decision: The Policy Function entity (policy function entity) performs policy decision, that is, formulates a QoS policy for the application, where the QoS policy includes a flow description, a flow label, and a QoS parameter.
  • the flow label uniquely identifies the data flow of the application in the PDU session.
  • the QoS parameters include QCI and ARP (ARP is optional). Wherein, if it is the QCI of the GBR, the QoS policy also carries the GBR.
  • the flow description includes a downstream description and/or an upstream description.
  • Step S504 the Policy Function entity sends a QoS policy to the core network CP functional entity.
  • the QoS policy carries a flow description, a flow label, and a QoS parameter.
  • Step S505 confirming that the CP function entity returns an acknowledgement message.
  • Step S506 The CP provides a QoS policy to the UP, where the QoS policy carries a flow description, a flow label, and a QoS parameter.
  • step S507 UP returns a confirmation message.
  • Step S508 the Policy Function entity sends the QoS policy to the access network AN, where the QoS policy carries a flow description, a flow label, and a QoS parameter.
  • step S509 the AN returns an acknowledgement message.
  • Step S510 the wireless air interface operation: the AN (including the base station) interacts with the UE, and establishes or modifies the radio bearer (ie, the wireless logical channel) according to the QoS policy, and in this process, the flow description, the flow label (optional), the QoS parameter, and Wireless logical channel information is provided to the UE.
  • the UE determines a flow description, a radio bearer (ie, a wireless logical channel) corresponding to the flow label (optional). If the AN determines that the QoS parameters (QCI and ARP (optional)) in the QoS policy do not have corresponding radio bearers, the AN establishes a radio bearer; otherwise, the AN modifies the radio bearer.
  • the radio bearer ie, the wireless logical channel
  • the AN also performs a resource reservation process.
  • the base station will perform resource reservation according to the same GBR corresponding to the same QCI and ARP (ARP optional) in the PDU session.
  • the UE determines a correspondence between the flow description and the wireless logical channel.
  • the AN maintains the correspondence between the flow label and the radio bearer. Since there may be multiple data streams with the same QCI and ARP (optional), one radio bearer may correspond to multiple flow labels.
  • the AN to UP tunnel also corresponds to one or more radio bearers of the PDU session.
  • Step S511 in the embodiment of the present invention, the Policy Function entity provides the flow description, the flow label (optional), and the QoS parameter to the UE.
  • Step S512 in the embodiment of the present invention, the UE returns an acknowledgement message. If there is no GBR in the QoS parameters authorized by the Policy Function, that is, the AN does not need to perform the resource reservation process, then step S510 may not be performed, but S511 and S512 are performed.
  • the UE dynamically pre-configures or dynamically sends a correspondence between the wireless logical channel parameter information and the QoS parameters before the network.
  • the wireless logical channel parameter information and QoS parameters are also pre-configured on the AN. In this way, when the UE wants to send uplink data, the UE can negotiate with the AN according to the wireless logical channel parameter information, and perform wireless logical channel configuration to establish a radio bearer (ie, a wireless logical channel).
  • a method for sending downlink data by an UP according to an embodiment of the present invention includes the following steps:
  • step S601 the UP receives a downlink IP data packet, a non-IP PDU, or an Ethernet frame (collectively referred to herein as a downlink data unit).
  • Step S602 the UP matches the downlink data unit according to the flow description, and executes a corresponding policy, and performs data unit marking according to the QoS policy.
  • step S603 the UP sends downlink data to the AN, and marks the flow label in the downlink data unit.
  • Step S604 the AN determines a corresponding wireless logical channel (ie, a radio bearer) according to the value of the flow label.
  • Step S605 the AN sends the downlink data unit to the UE by using the radio bearer.
  • the AN may provide the UP tag's flow label and the downlink data unit to the UE, or may not provide it.
  • Step S606 the UE sends the received downlink data unit to the terminal application.
  • a method for a UE to send uplink data includes the following steps:
  • Step S701 When the UE needs to send an uplink data unit (including an IP data packet, a non-IP PDU, or an Ethernet frame), determine, according to the obtained uplink description, the radio bearer (ie, the wireless logical channel) corresponding to the uplink data unit.
  • an uplink data unit including an IP data packet, a non-IP PDU, or an Ethernet frame
  • Step S702 The UE sends an uplink data unit by using a corresponding radio bearer.
  • the UE may mark the flow label in each uplink data unit, or may not perform flow label marking on the data unit.
  • Step S703 If the flow label is marked in the uplink data unit, the AN performs verification according to the correspondence between the saved flow label and the wireless logical channel. If the verification is successful, step S704 is performed. If the stream tag is not marked in the data unit, the AN will mark the wireless transmission of the data in the data unit. A flow label corresponding to a logical channel (ie, a radio bearer).
  • the AN determines whether the saved flow label is one of the flow labels corresponding to the radio bearer, and if yes, performs step S704.
  • step S704 the AN sends an uplink data unit to the user plane (UP), and the uplink data unit carries the flow label.
  • UP user plane
  • Step S705 The UP performs flow label marking on the uplink data unit to perform verification according to the flow description. That is, the UP determines whether the data flow is marked with the correct flow label according to the QoS policy (including the flow description, the flow description, and the QoS parameter) delivered by the Control Plane (CP) (that is, the UP is described according to the upstream flow) Matching the uplink data unit to determine the corresponding QoS policy, and then determining whether the flow label of the QoS policy is consistent with the flow label carried by the uplink data unit; if yes, forwarding the uplink data unit to the data network; if not, discarding.
  • the QoS policy including the flow description, the flow description, and the QoS parameter delivered by the Control Plane (CP)
  • CP Control Plane
  • the UP may also determine whether the uplink data unit is marked with an equivalent flow label (ie, The flow label marked by the uplink data unit and the flow label in the QoS policy determined by the UP according to the flow description have the same QoS parameters).
  • the AN may not mark the flow label, but mark the QoS corresponding to the radio bearer (such as QCI and ARP (optional)).
  • the UP may be determined according to the policy delivered by the CP. Whether the QCI and ARP (optional) marked by the upstream data unit are correct.
  • the method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course, by hardware, but in many cases, the former is A better implementation.
  • the technical solution of the present invention which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a storage medium (such as ROM/RAM, disk,
  • the optical disc includes a number of instructions for causing a terminal device (which may be a cell phone, a computer, a server, or a network device, etc.) to perform the methods described in various embodiments of the present invention.
  • a data transmitting apparatus is further provided, which is used to implement the foregoing embodiments and preferred embodiments, and is not described again.
  • the term "module” may implement a combination of software and/or hardware of a predetermined function.
  • the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.
  • FIG. 8 is a structural block diagram of a data transmitting apparatus according to an embodiment of the present invention. As shown in FIG. 8, the apparatus includes:
  • the first receiving module 82 is configured to receive a downlink data unit of the application carrying the flow label sent by the user plane function entity, where the flow label is used to uniquely identify the data stream of the application in the protocol data unit PDU session;
  • the sending module 84 is configured to send the downlink data unit to the user equipment UE by using the radio bearer corresponding to the flow label.
  • the data sending device may be an access network AN.
  • the sending module 84 sends the downlink data unit to the UE by using the radio bearer corresponding to the flow label, and implements the QoS guarantee mechanism of the core network without bearer, the wireless air interface pre-configuration, and the dynamic adjustment of the QoS configuration parameter, thereby effectively solving the related In the technology, when the QoS control is performed, the signaling load of the data transmission is high, and there is a problem of communication delay.
  • a data transmitting apparatus as shown in FIG. 9, the apparatus comprising:
  • the second receiving module 92 is configured to receive an uplink data unit of the application carrying the flow label sent by the access network AN, where the flow label is used to uniquely identify the data stream of the application in the protocol data unit PDU session;
  • the determining module 94 is configured to determine whether to send the uplink data unit to the data network based on the flow label.
  • the data sending device may be a user plane function entity.
  • the second receiving module 92 receives the carried flow label sent by the access network AN.
  • the uplink data unit of the signed application determines whether the uplink data unit is sent to the data network according to the flow label, and implements the QoS guarantee mechanism for the core network without bearer, the wireless air interface pre-configuration, and the dynamic adjustment of the QoS configuration parameter, which effectively solves the problem.
  • problems such as high signaling load of data transmission and communication delay in performing QoS control.
  • each of the above modules may be implemented by software or hardware.
  • the foregoing may be implemented by, but not limited to, the foregoing modules are all located in the same processor; or, the above modules are in any combination.
  • the forms are located in different processors.
  • Embodiments of the present invention also provide a storage medium including a stored program, wherein the program described above executes the method of any of the above.
  • the foregoing storage medium may include, but is not limited to, a USB flash drive, a Read-Only Memory (ROM), and a Random Access Memory (RAM).
  • ROM Read-Only Memory
  • RAM Random Access Memory
  • Embodiments of the present invention also provide a processor for running a program, wherein the program is executed to perform the steps of any of the above methods.
  • modules or steps of the present invention described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.
  • the steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated as a single integrated circuit module.
  • the invention is not limited to any specific combination of hardware and software.
  • the AN receives the downlink data unit of the application carrying the flow label sent by the user plane function entity, and sends the downlink data unit to the user equipment UE by using the radio bearer corresponding to the flow label.
  • the QoS guarantee mechanism of the core network without bearer, wireless air interface pre-configuration and dynamic adjustment of QoS configuration parameters effectively solves the problems of high signaling load and communication delay in data transmission during QoS control in related technologies.

Landscapes

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

Abstract

本发明提供了一种数据发送方法及装置。该方法包括：接入网AN接收用户面功能实体发送的携带有流标签的应用的下行数据单元，其中，流标签用于在协议数据单元PDU会话中唯一标识应用的数据流；AN通过流标签对应的无线承载将下行数据单元包发送给用户设备UE。通过本发明，解决了相关技术中在进行服务质量的控制时数据传输的信令负荷高的问题。

Description

数据发送方法及装置 技术领域
本发明涉及通信领域，具体而言，涉及一种数据发送方法及装置。
背景技术
在第四代移动通信技术(Four Generation，简称4G)移动通信系统中，将具有相同服务质量(Quality of Service，简称QoS)要求的数据流聚合成承载，用户面网元比如基站、网关对QoS的处理都是以承载作为最小粒度。4G系统QoS方案涉及的主要网元如图1所示，包括：终端(User Equipment，简称为UE)，基站，移动管理实体(Mobility Management Entity，简称为MME)也即核心网控制面实体，服务网关(Serving Gateway，简称为SGW)：也即核心网用户面功能实体，分组数据网网关(PDN GW，简称为PGW)，也即核心网用户面功能实体，策略控制实体(Policy and Charging Rules Function，简称为PCRF)，也即策略与计费规则功能单元等。
4G QoS参数包括：QCI(QoS Class Identifier，QoS类别标识)和分配和保留优先级(Allocation and Retention Priority，简称ARP)，QoS参数可以唯一标识一个承载。QCI是一个标准化标识，每个QCI都对应一组QoS参数，包括：承载类型保证速率(Guaranteed Bit Rate，简称GBR)或non GBR、优先级(priority)、延迟要求(Packet Delay Budget)以及丢包率(Packet Error Loss Rate)等参数。ARP标识用于当过负荷的时候，指示本承载被删除或保留的优先级。
针对non GBR承载，QoS参数还包括：聚合最大比特率(Aggregate Maximum Bit Rate，简称AMBR)。AMBR包括：UE-AMBR(UE的所有non GBR承载聚合最大比特率)和APN-AMBR(用户在接入点名字(Access Point Name，简称APN)上对应的non GBR承载聚合最大比特率)。
4G系统QoS方案中，在建立、修改承载的时候，可以通过QoS参数 指示承载的QoS要求；空口上无线承载、S1接口承载以及S5/S8接口承载分别是1:1:1映射；S1接口和S5/S8接口上的承载采用分段的用户层面的GPRS隧道协议(GPRS Tunnelling Protocol for the user plane，简称GTP-U)隧道的方式传输。
针对GBR承载，QoS参数还包括：最大比特率(Maximum Bit Rate，简称MBR)和保证比特率(Guaranteed Bit Rate，简称GBR)。
但是目前，4G系统的QoS方案还存在下述问题：
1)现有的QoS保障机制要求网络或终端根据业务过滤器识别一个业务的数据包，从而对识别出的数据包应用相应的QoS。然而这种方式往往无法通知UE上行数据的QoS参数，具体存在以下问题：a)对于同一个应用的不同业务数据流，尽管他们具有相同的QoS，但具有不同的业务过滤器，为了能够通知UE该业务数据流的上行QoS，则需要网络和终端之间进行交互，从而产生了不必要的信令。b)当终端运行一类不可推倒(non-deducible)，也即不能获得稳定业务过滤器的应用时，比如对等网络(Peer to Peer，简称为P2P)业务时，由于网络无法将业务过滤器与承载的绑定关系通知给终端，所以无法让终端获知这类应用的上行QoS参数。目前对这类应用的处理方式是将其放到默认承载上。
2)当用户访问的业务需要QoS保障时，首先需要从网络侧发起承载创建或修改的信令，这样带来大量的信令负荷，并且对于突发业务，将产生一定的延迟。
3)目前的QoS保障机制，只能处理网络之间互连的协议(Internet Protocol，简称IP)分组数据包，不能针对非IP的数据单元或以太帧。
针对如图2所示的下一代无线通讯系统，在进行QoS控制时相关技术中存在的数据传输的信令负荷较大的问题，目前尚未提出有效的解决方案。
发明内容
本发明实施例提供了一种数据发送方法及装置，以至少解决相关技术 中在进行QoS控制时数据传输的信令负荷较大的问题。
根据本发明的一个实施例，提供了一种数据发送方法，包括：接收用户面功能实体发送的携带有流标签的应用的下行数据单元，其中，流标签用于在协议数据单元(Protocol Data Unit，简称PDU)会话中唯一标识应用的数据流；通过流标签对应的无线承载将下行数据单元发送给用户设备UE。
在本发明实施例中，在接收用户面功能实体发送的携带有流标签的应用的下行数据单元之前，还包括：用户面功能实体接收策略功能实体为应用制定的携带有流标签的服务质量QoS策略；用户面功能实体根据QoS策略在接收到的应用的下行数据单元中标记流标签；用户面功能实体将标记有流标签的下行数据单元发送至接入网。
在本发明实施例中，QoS策略中还携带有以下信息至少之一：上行流描述和/或下行流描述、QoS参数，其中，QoS参数至少包括QoS类别标识QCI。
在本发明实施例中，QoS参数还包括以下信息至少之一：分配保持优先级ARP、保障带宽GBR。
在本发明实施例中，上行流描述或下行流描述包括以下至少之一：以太帧头部；分组交换标签；IP三元组；IP五元组；统一资源定位符(Uniform Resource Locator，简称URL)；运营商定义的应用标识。
在本发明实施例中，用户面功能实体根据QoS策略在接收到的应用的下行数据单元中标记流标签包括：用户面功能实体根据下行流描述确定下行数据单元，并在下行数据单元中标记流标签。
在本发明实施例中，在通过流标签对应的无线承载将下行数据单元发送给用户设备UE之前，还包括：接收策略功能实体为应用制定的携带有流标签的QoS策略；根据QoS策略建立或者修改无线承载，并保存流标签和无线承载之间的对应关系。
在本发明实施例中，上述下行数据单元包括以下至少之一：IP数据包； 非IP PDU；以太帧。
根据本发明的另一个实施例，提供了一种数据发送方法，包括：接收接入网AN发送的携带有流标签的应用的上行数据单元，其中，流标签用于在协议数据单元PDU会话中唯一标识应用的数据流；根据流标签确定是否将上行数据单元发送至数据网络。
在本发明实施例中，根据流标签确定是否将上行数据单元发送至数据网络包括：接收策略功能实体为应用制定的携带有流标签的服务质量QoS策略；若判断出上行数据单元携带的流标签为QoS策略中携带的流标签或等价流标签，则将上行数据单元发送至数据网络，其中，等价流标签是与QoS策略具有相同QoS参数的QoS策略中的流标签。
在本发明实施例中，在接收接入网AN发送的携带有流标签的应用的上行数据单元之前，还包括：AN接收用户设备UE通过无线承载发送的上行数据单元；AN在上行数据单元中标记无线承载对应的流标签或等价流标签，其中，等价流标签是与AN接收到的QoS策略具有相同QoS参数的QoS策略中的流标签；AN将标记有流标签或者等价流标签的上行数据单元发送给用户面功能实体。
在本发明实施例中，在AN接收用户设备UE通过无线承载发送的上行数据单元之前，还包括：UE根据获得的应用对应的QoS策略确定上行数据单元所对应的无线承载；UE通过无线承载将上行数据单元发送给AN。
在本发明实施例中，在接收接入网AN发送的携带有流标签的应用的上行数据单元之前，还包括：AN接收用户设备UE通过无线承载发送的携带有流标签的上行数据单元；若AN判断出流标签为无线承载对应的流标签或等价流标签，则AN将标记有流标签的上行数据单元发送给用户面功能实体，其中，等价流标签是与AN接收到的应用对应的QoS策略具有相同QoS参数的QoS策略中的流标签。
在本发明实施例中，QoS策略中还携带有以下信息至少之一：上行流描述和/或下行流描述、QoS参数，其中，QoS参数至少包括QoS类别标 识QCI。
在本发明实施例中，上行流描述或下行流描述包括以下至少之一：以太帧头部；分组交换标签；IP三元组；IP五元组；统一资源定位符URL；运营商定义的应用标识。
在本发明实施例中，QoS参数还包括以下信息至少之一：分配保持优先级ARP、保障带宽GBR。
在本发明实施例中，上行数据单元包括以下至少之一：IP数据包；非IP PDU；以太帧。
根据本发明的另一个实施例，提供了一种数据发送装置，包括：第一接收模块，设置为接收用户面功能实体发送的携带有流标签的应用的下行数据单元，其中，流标签用于在协议数据单元PDU会话中唯一标识应用的数据流；发送模块，设置为通过流标签对应的无线承载将下行数据单元发送给用户设备UE。
根据本发明的另一个实施例，提供了一种数据发送装置，包括：第二接收模块，设置为接收接入网AN发送的携带有流标签的应用的上行数据单元，其中，流标签用于在协议数据单元PDU会话中唯一标识应用的数据流；确定模块，设置为根据流标签确定是否将上行数据单元发送至数据网络。
根据本发明的又一个实施例，还提供了一种存储介质，所述存储介质包括存储的程序，其中，所述程序运行时执行上述任一项所述的方法。
根据本发明的又一个实施例，还提供了一种处理器，所述处理器用于运行程序，其中，所述程序运行时执行上述任一项所述的方法。
通过本发明，AN接收用户面功能实体发送的携带有流标签的应用的下行数据单元，并通过流标签对应的无线承载将下行数据单元发送给用户设备UE，实现了核心网无承载、无线空口预配置以及动态调整QoS配置参数的QoS保障机制，有效解决了相关技术中进行QoS控制时数据传输的信令负荷高、存在通信时延等问题。
附图说明
此处所说明的附图用来提供对本发明的进一步理解，构成本申请的一部分，本发明的示意性实施例及其说明用于解释本发明，并不构成对本发明的不当限定。在附图中：
图1是相关技术中4G系统的QoS控制系统的示意图；
图2是相关技术中下一代无线通讯系统的示意图；
图3是根据本发明实施例的一种数据发送方法的流程图；
图4是根据本发明实施例的另一种数据发送方法的流程图；
图5是根据本发明实施例的为应用进行QoS授权和保障的流程图；
图6是根据本发明实施例的UP发送下行数据的流程图；
图7是根据本发明实施例的UE发送上行数据的流程图；
图8是根据本发明实施例的一种数据发送装置的结构框图；
图9是根据本发明实施例的另一种数据发送装置的结构框图。
具体实施方式
下文中将参考附图并结合实施例来详细说明本发明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。
需要说明的是，本发明的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。
在本实施例中提供了一种数据发送方法，图3是根据本发明实施例的一种数据发送方法的流程图，如图3所示，该流程包括如下步骤：
步骤S302，接入网AN接收用户面功能实体发送的携带有流标签的应用的下行数据单元，其中，流标签用于在协议数据单元PDU会话中唯一标识应用的数据流；
步骤S304，AN通过流标签对应的无线承载将下行数据单元发送给用 户设备UE。
在该实施例中，AN通过流标签对应的无线承载将下行数据单元发送给UE，实现了核心网无承载、无线空口预配置以及动态调整QoS配置参数的QoS保障机制，有效解决了相关技术中在进行QoS控制时数据传输的信令负荷高、存在通信时延等问题。
在一种可选的实施例中，在接入网AN接收用户面功能实体发送的携带有流标签的应用的下行数据单元之前，还包括：用户面功能实体接收策略功能实体为应用制定的携带有流标签的服务质量QoS策略；用户面功能实体根据QoS策略在接收到的应用的下行数据单元中标记流标签；用户面功能实体将标记有流标签的下行数据单元发送至AN。
在一种可选的实施例中，QoS策略中还携带有以下信息至少之一：上行流描述和/或下行流描述、QoS参数，其中，QoS参数至少包括QoS类别标识QCI。
在一种可选的实施例中，QoS参数还包括以下信息至少之一：分配保持优先级ARP、保障带宽GBR。
在一种可选的实施例中，上行流描述或下行流描述包括以下至少之一：以太帧头部；分组交换标签；IP三元组；IP五元组；统一资源定位符URL；运营商定义的应用标识。
在一种可选的实施例中，用户面功能实体根据QoS策略在接收到的应用的下行数据单元中标记流标签包括：用户面功能实体根据下行流描述确定下行数据单元，并在下行数据单元中标记流标签。
在一种可选的实施例中，在AN通过流标签对应的无线承载将下行数据单元发送给用户设备UE之前，还包括：AN接收策略功能实体为应用制定的携带有流标签的QoS策略；AN根据QoS策略建立或者修改无线承载，并保存流标签和无线承载之间的对应关系。
在本发明实施例中，流标签与无线承载可以是多对1的关系。
在一种可选的实施例中，上述下行数据单元包括以下至少之一：IP数 据包；非IP PDU；以太帧。
根据本发明的另一实施例，还提供了一种数据发送方法，图4是根据本发明实施例的另一种数据发送方法的流程图，如图4所示，该流程包括如下步骤：
步骤S402，用户面功能实体接收接入网AN发送的携带有流标签的应用的上行数据单元，其中，流标签用于在协议数据单元PDU会话中唯一标识应用的数据流；
步骤S404，用户面功能实体根据流标签确定是否将上行数据单元发送至数据网络。
在该实施例中，用户面功能实体接收接入网AN发送的携带有流标签的应用的上行数据单元，并根据流标签确定是否将上行数据单元发送至数据网络，实现了核心网无承载、无线空口预配置以及动态调整QoS配置参数的QoS保障机制，有效解决了相关技术中在进行QoS控制时数据传输的信令负荷高、存在通信时延等问题。
在一种可选的实施例中，用户面功能实体根据流标签确定是否将上行数据单元发送至数据网络包括：用户面功能实体接收策略功能实体为应用制定的携带有流标签的服务质量QoS策略；若用户面功能实体判断出上行数据单元携带的流标签为QoS策略中携带的流标签或等价流标签，则用户面功能实体将上行数据单元发送至数据网络，其中，等价流标签是与QoS策略具有相同QoS参数的QoS策略中的流标签。
在一种可选的实施例中，在用户面功能实体接收接入网AN发送的携带有流标签的应用的上行数据单元之前，还包括：AN接收用户设备UE通过无线承载发送的上行数据单元；AN在上行数据单元中标记无线承载对应的流标签或等价流标签，其中，等价流标签是与AN接收到的QoS策略具有相同QoS参数的QoS策略中的流标签；AN将标记有流标签或者等价流标签的上行数据单元发送给用户面功能实体。
在一种可选的实施例中，在AN接收用户设备UE通过无线承载发送 的上行数据单元之前，还包括：UE根据获得的上述应用对应的QoS策略确定上行数据单元所对应的无线承载；UE通过无线承载将上行数据单元发送给AN。
在一种可选的实施例中，在用户面功能实体接收接入网AN发送的携带有流标签的应用的上行数据单元之前，还包括：AN接收用户设备UE通过无线承载发送的携带有流标签的上行数据单元；若AN判断出流标签为无线承载对应的流标签或等价流标签，则AN将标记有流标签的上行数据单元发送给用户面功能实体，其中，等价流标签是与AN接收到的应用对应的QoS策略具有相同QoS参数的QoS策略中的流标签。
在一种可选的实施例中，QoS策略中还携带有以下信息至少之一：上行流描述和/或下行流描述、QoS参数，其中，QoS参数至少包括QoS类别标识QCI。
在本发明实施例中，上行流描述或下行流描述包括以下至少之一：以太帧头部；分组交换标签；IP三元组；IP五元组；统一资源定位符URL；运营商定义的应用标识。
在一种可选的实施例中，QoS参数还包括以下信息至少之一：分配保持优先级ARP、保障带宽GBR。
在一种可选的实施例中，上述的上行数据单元包括以下至少之一：IP数据包；非IP PDU；以太帧。
上述实施例中，策略功能实体在为应用制定的QoS策略中携带对应的流标签，并将其提供给用户面功能实体、AN和UE，用户面功能实体根据所述QoS策略在应用的下行数据单元中标记流标签(或者AN标记流标签)，AN根据流标签采用对应的无线承载发送数据给UE，以及AN在应用的上行数据单元中标记无线承载对应的流标签，UP通过QoS策略校验上行数据单元的流标签是否正确以判断是否将上行数据单元转发至数据网络。通过上述实施例，可实现核心网无承载、无线空口预配置和动态调整QoS配置参数的QoS控制，从而有效解决了相关技术中存在的通信时延、信令 负荷高等问题。
下面通过3个具体的实施例来进一步说明本发明的服务质量的控制方法。
实施例一
下面根据本发明实施例提供了一种服务质量的控制中为应用进行QoS授权和保障的方法。在下一代无线通信系统中，终端建立协议数据单元(Protocol Data Unit，PDU)会话后，为应用进行QoS授权和保障的流程，如图5所示，主要包括以下的步骤：
步骤S501，UE和网络建立PDU会话。
PDU会话建立后，控制面功能实体CP为该PDU会话授权默认的QoS参数，包括QoS类别标识(QoS Class Identifier，简称为QCI)和分配保持优先级(Allocation and Retention Priority，ARP(可选)，其中，QCI用于表示对应用的业务流提供特定数据转发行为(如丢包率，延迟等)的指标。ARP参数可为一个取值，或一组取值，表示该应用的资源可以被其他应用抢占、该应用可以抢占其他应用的资源和/或优先级。AN和用户面功能实体UP之间会建立一个隧道，一个默认的无线承载跟该隧道对应。其中，无线承载的QoS为默认的QCI和ARP(可选)。
步骤S502a，AF业务信息提供和确认：UE与应用的应用层交互，为要发起的应用进行协商，应用功能实体AF向核心网CP功能实体提供业务信息，该业务信息包括流描述和请求的QoS参数。其中，流描述可以是2层、3层或4层过滤器信息，或是4层以上的流描述信息。
步骤S502b，应用信息报告和确认：UP对用户面数据执行应用检测，并向CP提供应用信息描述，其中，应用信息描述中携带流描述信息，其中流描述信息可以是2层、3层或4层过滤器信息或是4层以上的流描述信息。
步骤S502c，UE的资源请求：UE向CP发送资源请求消息，消息中携带流描述信息和请求的QoS参数，其中流描述信息可以是2层、3层或 4层过滤器信息。
上述2层过滤器信息可以是以太帧头部、分组交换标签；3层或4层过滤器信息为IP三元组、IP五元组；4层以上流描述信息可以是统一资源定位符URL或是运营商定义的应用标识Application Id。其中，在步骤S502a和步骤S502c中，UE向网络提供的Application Id是之前UE接入网络后，CP向UE提供的Application Id。该Application Id标识了CP在UE接入网络后向UE提供的Application Id和操作系统应用标识的对应关系、Application Id和第三方应用的服务器IP地址、IP三元组的对应关系，或Application Id和第三方应用的URL的对应关系。在步骤S502b中，Application Id用于标识基于网络配置在UP上的采用包检测机制检测出的应用信息。
在本发明实施例中，在该步骤S502c中，在UE发送资源请求消息之前，UE首先检查应用对应的Application Id是否已经存在一个对应的无线承载(即Application Id是否有对应的网络侧授权的QoS信息)。若不存在，则UE执行步骤S502c；若存在，则UE进一步检查无线承载是否是GBR承载(即网络侧授权的QoS信息中是否有GBR参数)。若是，则UE执行步骤S502c。若在下一代通信系统中，不存在GBR参数，那么UE不需要进一步检查无线承载是否是GBR承载，即UE只要检查Application Id是否存在对应的无线承载，若不存在，则UE执行步骤S502c。
步骤S503，策略决策：Policy Function实体(策略功能实体)执行策略决策，即为应用制定QoS策略，其中，该QoS策略中包含流描述、流标签、QoS参数。流标签在该PDU会话中唯一标识该应用的数据流。其中，QoS参数中包括QCI、ARP(ARP为可选)。其中，若是GBR的QCI，那么QoS策略中还携带GBR。流描述包括下行流描述和/或上行流描述。
步骤S504，Policy Function实体向核心网CP功能实体发送QoS策略。其中，该QoS策略中携带有流描述、流标签、QoS参数。
步骤S505，确认：CP功能实体返回确认消息。
步骤S506，CP向UP提供QoS策略，其中，该QoS策略中携带有流描述、流标签和QoS参数。
步骤S507，UP返回确认消息。
步骤S508，Policy Function实体向接入网AN发送该QoS策略，其中，QoS策略中携带有流描述、流标签和QoS参数。
步骤S509，AN返回确认消息。
步骤S510，无线空口操作：AN(其中包含基站)与UE交互，根据QoS策略建立或修改无线承载(即无线逻辑信道)，在这个过程中将流描述、流标签(可选)、QoS参数以及无线逻辑信道信息提供给UE。UE确定流描述、流标签(可选)对应的无线承载(即无线逻辑信道)。若AN判断QoS策略中的QoS参数(QCI和ARP(可选))没有对应的无线承载，则AN建立无线承载；否则，AN修改无线承载。
其中，若QoS参数携带GBR，AN还会执行资源预留过程。在资源预留过程中，基站将根据该PDU会话中相同QCI和ARP(ARP可选)对应的累计GBR进行资源预留。UE确定流描述和无线逻辑信道的对应关系。同时AN保持流标签和无线承载的对应关系。由于可能存在多个具有相同QCI和ARP(可选)的数据流，因此，一个无线承载可能对应多个流标签。此外，AN到UP的隧道也对应PDU会话的一个或多个无线承载。
步骤S511，在本发明实施例中，Policy Function实体将流描述、流标签(可选)、QoS参数提供给UE。
步骤S512，在本发明实施例中，UE返回确认消息。若Policy Function授权的QoS参数中没有GBR，即AN不需要执行资源预留过程，那么S510步可不执行，而是执行S511和S512。在这种情况下，UE会预配置或是网络之前动态下发无线逻辑信道参数信息和QoS参数之间的对应关系。同时AN上也会预配置无线逻辑信道参数信息和QoS参数。这样，当UE要发送上行数据时，UE就可以根据无线逻辑信道参数信息与AN进行协商，进行无线逻辑信道配置建立无线承载(即无线逻辑信道)。
实施例二
下面根据本发明实施例，提供了一种基于本发明实施例的UP发送下行数据的方法。如图6所示，该方法包括以下的步骤：
步骤S601，UP收到下行IP数据包、非IP PDU或以太帧(这里统称为下行数据单元)。
步骤S602，UP根据流描述匹配下行数据单元，并执行相应的策略，并根据QoS策略进行数据单元标记。
步骤S603，UP向AN发送下行数据，在下行数据单元中标记流标签。
步骤S604，AN根据流标签的取值确定对应的无线逻辑信道(即无线承载)。
步骤S605，AN通过无线承载将下行数据单元发送给UE。
其中，AN可将UP标记的流标签和下行数据单元一起提供给UE，也可以不提供。
步骤S606，UE将收到的下行数据单元发送给终端应用。
实施例三
下面根据本发明实施例，提供了一种基于本发明实施例的UE发送上行数据的方法。如图7所示，该方法包括以下的步骤：
步骤S701，UE在需要发送上行数据单元(包括IP数据包、非IP PDU或以太帧)时，根据获得的上行流描述，确定该上行数据单元对应的无线承载(即无线逻辑信道)。
步骤S702，UE采用对应的无线承载发送上行数据单元。其中，UE可以在每个上行数据单元中标记流标签，也可以不对数据单元进行流标签标记。
步骤S703，若上行数据单元中标记了流标签，那么AN将根据保存的流标签和无线逻辑信道的对应关系进行校验，若校验成功则执行步骤S704。若数据单元中未标记流标签，则AN将在数据单元中标记数据传输的无线 逻辑信道(即无线承载)对应的一个流标签。
其中，若该无线承载对应多个流标签，且UE进行了流标签标记，则AN判断保存的流标签是否是无线承载对应的流标签中的一个，若是则执行步骤S704。
步骤S704，AN向用户面(User Plane，简称UP)发送上行数据单元，该上行数据单元中携带有流标签。
步骤S705，UP根据流描述对上行数据单元是否正确进行了流标签标记进行校验。也即，UP根据控制面(Control Plane，简称CP)下发的QoS策略(其中包括流描述、流描述和QoS参数)判断数据流是否标记了正确的流标签(也即，UP根据上行流描述匹配上行数据单元确定对应的QoS策略，再判断QoS策略的流标签与上行数据单元携带的流标签是否一致)；若是，则向数据网络转发该上行数据单元；若否，则丢弃。
其中，对于AN标记流标签的情况，UP除了判断上行数据单元是否正确标记了流标签(即流描述与流标签对应)之外，还可判断上行数据单元是否标记了等价的流标签(即上行数据单元标记的流标签和UP根据流描述确定的QoS策略中的流标签是否具有相同的QoS参数)。
在本发明实施例中，AN也可以不标记流标签，而是标记无线承载对应的QoS(如QCI和ARP(可选))，这样，在步骤S505中，UP可根据CP下发的策略判断上行数据单元标记的QCI和ARP(可选)是否正确。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到根据上述实施例的方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本发明的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，或者网络设备等)执行本发明各个实施例所述的方法。
在本实施例中还提供了一种数据发送装置，该装置用于实现上述实施例及优选实施方式，已经进行过说明的不再赘述。如以下所使用的，术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
图8是根据本发明实施例的一种数据发送装置的结构框图，如图8所示，该装置包括：
第一接收模块82，设置为接收用户面功能实体发送的携带有流标签的应用的下行数据单元，其中，流标签用于在协议数据单元PDU会话中唯一标识应用的数据流；
发送模块84，设置为通过流标签对应的无线承载将下行数据单元发送给用户设备UE。
在本发明实施例中，该数据发送装置可以是接入网AN。
在该实施例中，发送模块84通过流标签对应的无线承载将下行数据单元发送给UE，实现了核心网无承载、无线空口预配置以及动态调整QoS配置参数的QoS保障机制，有效解决了相关技术中在进行QoS控制时数据传输的信令负荷高、存在通信时延等问题。
根据本发明的另一个实施例，还提供了一种数据发送装置，如图9所示，该装置包括：
第二接收模块92，设置为接收接入网AN发送的携带有流标签的应用的上行数据单元，其中，流标签用于在协议数据单元PDU会话中唯一标识应用的数据流；
确定模块94，设置为根据流标签确定是否将上行数据单元发送至数据网络。
在本发明实施例中，该数据发送装置可以是用户面功能实体。
在该实施例中，第二接收模块92接收接入网AN发送的携带有流标 签的应用的上行数据单元，确定模块94根据流标签确定是否将上行数据单元发送至数据网络，实现了核心网无承载、无线空口预配置以及动态调整QoS配置参数的QoS保障机制，有效解决了相关技术中在进行QoS控制时数据传输的信令负荷高、存在通信时延等问题。
需要说明的是，上述各个模块是可以通过软件或硬件来实现的，对于后者，可以通过以下方式实现，但不限于此：上述模块均位于同一处理器中；或者，上述各个模块以任意组合的形式分别位于不同的处理器中。
本发明的实施例还提供了一种存储介质，该存储介质包括存储的程序，其中，上述程序运行时执行上述任一项所述的方法。
可选地，在本实施例中，上述存储介质可以包括但不限于：U盘、只读存储器(Read-Only Memory，简称为ROM)、随机存取存储器(Random Access Memory，简称为RAM)、移动硬盘、磁碟或者光盘等各种可以存储程序代码的介质。
本发明的实施例还提供了一种处理器，该处理器用于运行程序，其中，该程序运行时执行上述任一项方法中的步骤。
可选地，本实施例中的具体示例可以参考上述实施例及可选实施方式中所描述的示例，本实施例在此不再赘述。
显然，本领域的技术人员应该明白，上述的本发明的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本发明不限制于任何特定的硬件和软件结合。
以上所述仅为本发明的优选实施例而已，并不用于限制本发明，对于 本领域的技术人员来说，本发明可以有各种更改和变化。凡在本发明的原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。
工业实用性
基于本发明实施例提供的上述技术方案，AN接收用户面功能实体发送的携带有流标签的应用的下行数据单元，并通过流标签对应的无线承载将下行数据单元发送给用户设备UE，实现了核心网无承载、无线空口预配置以及动态调整QoS配置参数的QoS保障机制，有效解决了相关技术中进行QoS控制时数据传输的信令负荷高、存在通信时延等问题。

Claims (21)

  1. 一种数据发送方法，包括：
    接收用户面功能实体发送的携带有流标签的应用的下行数据单元，其中，所述流标签用于在协议数据单元PDU会话中唯一标识所述应用的数据流；
    通过所述流标签对应的无线承载将所述下行数据单元发送给用户设备UE。
  2. 根据权利要求1所述的方法，其中，在接收用户面功能实体发送的携带有流标签的应用的下行数据单元之前，还包括：
    所述用户面功能实体接收策略功能实体为所述应用制定的携带有流标签的服务质量QoS策略；
    所述用户面功能实体根据所述QoS策略在接收到的所述应用的下行数据单元中标记所述流标签；
    所述用户面功能实体将标记有所述流标签的下行数据单元发送至接入网。
  3. 根据权利要求2所述的方法，其中，所述QoS策略中还携带有以下信息至少之一：上行流描述和/或下行流描述、QoS参数，其中，所述QoS参数至少包括QoS类别标识QCI。
  4. 根据权利要求3所述方法，其中，所述QoS参数还包括以下信息至少之一：分配保持优先级ARP、保障带宽GBR。
  5. 根据权利要求3所述的方法，其中，所述上行流描述或所述下行流描述包括以下至少之一：以太帧头部；分组交换标签；IP三元组；IP五元组；统一资源定位符URL；运营商定义的应用标识。
  6. 根据权利要求3所述的方法，其中，所述用户面功能实体根据所述QoS策略在接收到的所述应用的下行数据单元中标记所述流 标签包括：
    所述用户面功能实体根据所述下行流描述确定所述下行数据单元，并在所述下行数据单元中标记所述流标签。
  7. 根据权利要求1所述的方法，其中，在通过所述流标签对应的无线承载将所述下行数据单元发送给用户设备UE之前，还包括：
    接收策略功能实体为所述应用制定的携带有所述流标签的QoS策略；
    根据所述QoS策略建立或者修改所述无线承载，并保存所述流标签和所述无线承载之间的对应关系。
  8. 根据权利要求1-7中任一项所述的方法，其中，所述下行数据单元包括以下至少之一：IP数据包；非IP PDU；以太帧。
  9. 一种数据发送方法，包括：
    接收接入网AN发送的携带有流标签的应用的上行数据单元，其中，所述流标签用于在协议数据单元PDU会话中唯一标识所述应用的数据流；
    根据所述流标签确定是否将所述上行数据单元发送至数据网络。
  10. 根据权利要求9所述的方法，其中，根据所述流标签确定是否将所述上行数据单元发送至数据网络包括：
    接收策略功能实体为所述应用制定的携带有流标签的服务质量QoS策略；
    若判断出所述上行数据单元携带的流标签为所述QoS策略中携带的流标签或等价流标签，则将所述上行数据单元发送至所述数据网络，其中，所述等价流标签是与所述QoS策略具有相同QoS参数的QoS策略中的流标签。
  11. 根据权利要求9所述的方法，其中，在接收接入网AN发送的携带有流标签的应用的上行数据单元之前，还包括：
    所述AN接收用户设备UE通过无线承载发送的所述上行数据单元；
    所述AN在所述上行数据单元中标记所述无线承载对应的流标签或等价流标签，其中，所述等价流标签是与所述AN接收到的所述应用对应的QoS策略具有相同QoS参数的QoS策略中的流标签；
    所述AN将标记有所述流标签或者所述等价流标签的上行数据单元发送给所述用户面功能实体。
  12. 根据权利要求11所述的方法，其中，在所述AN接收用户设备UE通过无线承载发送的所述上行数据单元之前，还包括：
    所述UE根据获得的所述应用对应的QoS策略确定所述上行数据单元所对应的无线承载；
    所述UE通过所述无线承载将所述上行数据单元发送给所述AN。
  13. 根据权利要求9所述的方法，其中，在接收接入网AN发送的携带流标签的应用的上行数据单元之前，还包括：
    所述AN接收用户设备UE通过无线承载发送的携带有所述流标签的上行数据单元；
    若所述AN判断出所述流标签为所述无线承载对应的流标签或等价流标签，则所述AN将标记有所述流标签的上行数据单元发送给所述用户面功能实体，其中，所述等价流标签是与所述AN接收到的所述应用对应的QoS策略具有相同QoS参数的QoS策略中的流标签。
  14. 根据权利要求10-13中任一项所述的方法，其中，所述QoS策略中还携带有以下信息至少之一：上行流描述和/或下行流描述、QoS参数，其中，所述QoS参数至少包括QoS类别标识QCI。
  15. 根据权利要求14所述的方法，其中，所述上行流描述或所述下行流描述包括以下至少之一：以太帧头部；分组交换标签；IP三元组；IP五元组；统一资源定位符URL；运营商定义的应用标识。
  16. 根据权利要求14所述方法，其中，所述QoS参数还包括以下信息至少之一：分配保持优先级ARP、保障带宽GBR。
  17. 根据权利要求9-16中任一项所述的方法，其中，所述上行数据单元包括以下至少之一：IP数据包；非IP PDU；以太帧。
  18. 一种数据发送装置，包括：
    第一接收模块，设置为接收用户面功能实体发送的携带有流标签的应用的下行数据单元，其中，所述流标签用于在协议数据单元PDU会话中唯一标识所述应用的数据流；
    发送模块，设置为通过所述流标签对应的无线承载将所述下行数据单元发送给用户设备UE。
  19. 一种数据发送装置，包括：
    第二接收模块，设置为接收接入网AN发送的携带有流标签的应用的上行数据单元，其中，所述流标签用于在协议数据单元PDU会话中唯一标识所述应用的数据流；
    确定模块，设置为根据所述流标签确定是否将所述上行数据单元发送至数据网络。
  20. 一种存储介质，所述存储介质包括存储的程序，其中，所述程序运行时执行权利要求1至17中任一项所述的方法。
  21. 一种处理器，所述处理器用于运行程序，其中，所述程序运行时执行权利要求1至17中任一项所述的方法。
PCT/CN2017/084390 2016-05-17 2017-05-15 数据发送方法及装置 WO2017198132A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610327473.1 2016-05-17
CN201610327473.1A CN107396401A (zh) 2016-05-17 2016-05-17 数据发送方法及装置

Publications (1)

Publication Number Publication Date
WO2017198132A1 true WO2017198132A1 (zh) 2017-11-23

Family

ID=60325648

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/084390 WO2017198132A1 (zh) 2016-05-17 2017-05-15 数据发送方法及装置

Country Status (2)

Country Link
CN (1) CN107396401A (zh)
WO (1) WO2017198132A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111972005A (zh) * 2018-04-13 2020-11-20 Oppo广东移动通信有限公司 建立传输路径的方法和设备
US11212230B2 (en) * 2017-05-24 2021-12-28 Huawei Technologies Co., Ltd. Quality of service control method, device, and system
WO2022267652A1 (zh) * 2021-06-24 2022-12-29 华为技术有限公司 一种通信方法、通信装置及通信系统

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109995836B (zh) * 2017-12-29 2021-12-03 华为技术有限公司 缓存决策方法及装置
CN116709593A (zh) 2018-02-14 2023-09-05 华为技术有限公司 确定协议数据单元会话服务网元的方法和装置
CN117651306A (zh) 2018-05-21 2024-03-05 华为技术有限公司 在会话中建立GBR QoS流的方法和装置
CN110557786B (zh) * 2018-05-31 2022-04-05 华为技术有限公司 一种无线承载建立、业务流的监测方法及装置
US11297530B2 (en) 2018-11-02 2022-04-05 Huawei Technologies Co., Ltd. Method and system for using policy to handle packets

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102804705A (zh) * 2009-04-02 2012-11-28 瑞典爱立信有限公司 用于处理网络通信的技术
WO2013174422A1 (en) * 2012-05-23 2013-11-28 Nokia Siemens Networks Oy Methods, computer program products and apparatuses enabling symmetric bearer enforcement
WO2014101062A1 (zh) * 2012-12-27 2014-07-03 华为技术有限公司 用户面数据传输方法、移动管理网元、演进型基站及系统
CN104010332A (zh) * 2013-02-21 2014-08-27 中兴通讯股份有限公司 承载绑定方法及系统
WO2016003805A1 (en) * 2014-06-30 2016-01-07 Intel IP Corporation An apparatus and method enhancing quality of service architecture for lte

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102804705A (zh) * 2009-04-02 2012-11-28 瑞典爱立信有限公司 用于处理网络通信的技术
WO2013174422A1 (en) * 2012-05-23 2013-11-28 Nokia Siemens Networks Oy Methods, computer program products and apparatuses enabling symmetric bearer enforcement
WO2014101062A1 (zh) * 2012-12-27 2014-07-03 华为技术有限公司 用户面数据传输方法、移动管理网元、演进型基站及系统
CN104010332A (zh) * 2013-02-21 2014-08-27 中兴通讯股份有限公司 承载绑定方法及系统
WO2016003805A1 (en) * 2014-06-30 2016-01-07 Intel IP Corporation An apparatus and method enhancing quality of service architecture for lte

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11212230B2 (en) * 2017-05-24 2021-12-28 Huawei Technologies Co., Ltd. Quality of service control method, device, and system
CN111972005A (zh) * 2018-04-13 2020-11-20 Oppo广东移动通信有限公司 建立传输路径的方法和设备
CN111972005B (zh) * 2018-04-13 2022-10-18 Oppo广东移动通信有限公司 建立传输路径的方法和设备
WO2022267652A1 (zh) * 2021-06-24 2022-12-29 华为技术有限公司 一种通信方法、通信装置及通信系统

Also Published As

Publication number Publication date
CN107396401A (zh) 2017-11-24

Similar Documents

Publication Publication Date Title
WO2017198132A1 (zh) 数据发送方法及装置
KR102499481B1 (ko) 무선 통신 네트워크에서 데이터 통신을 관리하는 방법 및 장치
KR101792378B1 (ko) 모바일 통신 시스템에서 서비스 품질 제어의 지원
CN109314710B (zh) 用于通信网络中的服务质量监测、策略执行和计费的系统和方法
CN107079015B (zh) 用于移动环境下的基于流的寻址的系统及方法
JP5579564B2 (ja) データ伝送制御方法及びデバイス
CN110099370B (zh) 服务层南向接口和服务质量
WO2017167203A1 (zh) 一种服务质量的控制方法和装置
WO2018006773A1 (zh) 信息、数据发送方法及装置、接入网和系统
JP2020501416A (ja) 基地局装置及び無線区間のＱｏＳ制御方法
WO2013131458A1 (zh) 一种ip数据包的传输方法和设备
JP7477661B2 (ja) データ伝送方法および装置
WO2013117126A1 (zh) 业务速率控制方法和系统以及设备
CN108064058B (zh) 拥塞控制方法及装置、基站
CN108024284B (zh) 无线通信方法、用户设备接入网设备、和核心网设备
KR20140041310A (ko) 패킷 처리 방법 및 장치
WO2017177753A1 (zh) 一种基于流的承载管理方法、数据传输方法及装置
US11882513B2 (en) Transporting MTNC-ID over SRV6-enabled dataplane for 5G transport
WO2014075359A1 (zh) 一种带宽调整方法、设备及系统
US9877258B2 (en) Method and device for transferring data traffic
KR20060119783A (ko) 이종망 환경에서 종단간 서비스 품질 연동장치 및 그 방법
WO2017084042A1 (zh) 一种业务流的传输方法及装置
US11647419B2 (en) Adjusting window size based on quality of experience
CN107396356A (zh) 数据发送方法及装置
WO2020192250A1 (zh) 无线承载建立方法及装置

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

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

Ref document number: 17798695

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 17798695

Country of ref document: EP

Kind code of ref document: A1