WO2020007202A1 - 一种数据传输方法、装置及系统 - Google Patents

一种数据传输方法、装置及系统 Download PDF

Info

Publication number
WO2020007202A1
WO2020007202A1 PCT/CN2019/092142 CN2019092142W WO2020007202A1 WO 2020007202 A1 WO2020007202 A1 WO 2020007202A1 CN 2019092142 W CN2019092142 W CN 2019092142W WO 2020007202 A1 WO2020007202 A1 WO 2020007202A1
Authority
WO
WIPO (PCT)
Prior art keywords
data packet
app
network element
information
qfi
Prior art date
Application number
PCT/CN2019/092142
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 WO2020007202A1 publication Critical patent/WO2020007202A1/zh

Links

Images

Classifications

    • 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/0268—Traffic management, e.g. flow control or congestion control using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M1/00—Substation equipment, e.g. for use by subscribers
    • H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
    • H04M1/724—User interfaces specially adapted for cordless or mobile telephones
    • H04M1/72403—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M1/00—Substation equipment, e.g. for use by subscribers
    • H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
    • H04M1/725—Cordless telephones
    • 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

Definitions

  • the present application relates to the field of mobile communication technology, and in particular, to a data transmission method, device, and system.
  • QoS Quality of Service
  • the purpose of the QoS solution is to provide network services with different quality of services for different business needs. Especially when the network is congested, the service quality of the users or services with high priority is guaranteed first.
  • End-to-end QoS guarantee is implemented by terminals, access devices, and user plane network elements that transmit user data. It can be divided into the next generation (NG) user plane on the core network side between the access device and the user plane network elements. There are two parts: a tunnel (NG-U Tunnel) and a data radio bearer (DRB) on the wireless side between the terminal and the access device.
  • NG-U Tunnel next generation
  • DRB data radio bearer
  • the terminal When the uplink service flow occurs, the terminal implements the mapping of the uplink service flow to the QoS flow and the mapping of the QoS flow to the DRB according to the pre-configured QoS policy, and carries the service of the mapped QoS flow in the encapsulation header of the uplink packet of the uplink service flow Quality flow identifier (QFI).
  • QFI Quality flow identifier
  • the QoS policy of the terminal includes a mapping relationship between quintuple information and QFI.
  • the quintuple information includes a source address, a destination address, a source port, a destination port, and a protocol type.
  • the terminal needs to analyze the uplink data packet of the uplink service flow, obtain the quintuple information therein, and determine the QFI corresponding to the quintuple information according to the QoS policy, so as to map the uplink service flow to the QoS flow.
  • the user plane network element can map the downlink service flow to another QoS flow in the same manner as the terminal side.
  • the user plane network element may further analyze the characteristics of the L4-L7 (layer 4-layer 7) protocol in the downlink service data packet of the downlink service flow based on the quintuple information of the downlink service flow. Perform protocol identification and obtain valuable information such as the seven-layer protocol type or resource locator (URL), so as to achieve more accurate business identification.
  • L4-L7 layer 4-layer 7
  • This application provides a data transmission method, device, and system to implement fast and accurate identification of business flows, so as to facilitate timely processing of business flows.
  • the present application provides a data transmission method.
  • the method includes: a user plane network element receives an uplink data packet of a service flow from an APP of a terminal, the uplink data packet includes a QFI and first indication information, the QFI is used to identify a QoS flow, and the first indication information is used to indicate the user plane network element Use the reflective QoS function for APP service flows; the user plane network element maps the first downlink data packet of the APP's service flow to the QoS flow according to the first instruction information to obtain the second downlink data packet; the user plane network element forwards the terminal Send a second downlink data packet.
  • the terminal maps the uplink data packet of the APP to the QoS flow corresponding to the APP, and sends it to the user plane network element.
  • the user plane network element uses the first instruction information to map the user plane network element.
  • the received first downlink data packet generated by the APP is mapped to the QoS flow corresponding to the first uplink data packet, and a second downlink data packet is obtained.
  • the second downlink data packet includes the QFI, that is, the uplink data packet and Downstream packets are transmitted using the same QoS stream.
  • the user plane network element transmits uplink data packets and downlink data packets based on the granularity of the APP.
  • the service flows of the same APP will be identified as the traffic of the APP, so the service identification is accurate; In-depth analysis of upstream or downstream data packets is required, that is, it is not necessary to read the contents of the IP packet payload to perform reorganization analysis of the application layer information in the seven-layer protocol, which is conducive to improving the speed of identification and encryption. Business flows can also be accurately identified.
  • the user plane network element receives the first policy information from the session management network element, the first policy information includes QFI and second indication information, and the second indication information is used to indicate a corresponding QoS flow identified by the QFI.
  • Business is APP business.
  • the user plane network element can obtain the first policy information from the session management network element. Based on the first policy information, the user plane network element determines which QFI services corresponding to the identified QoS flows of the first policy information are APP services. .
  • the first policy information includes QFI and second instruction information, and specifically includes: the first policy information includes a packet detection rule (Packet Detection Rule, PDR), and the PDR includes QFI and second instruction information. That is, the session management network element sends the first policy information to the user plane network element in the form of a PDR.
  • PDR Packet Detection Rule
  • the user plane network element maps the first downlink data packet of the APP's service flow to the QoS flow to obtain a second downlink data packet, and specifically includes: the user plane network element according to the first A packet filter to determine the second packet filter, where the source address of the second packet filter is the same as the destination address of the first packet filter, and the destination address of the second packet filter is the same as the source address of the first packet filter , The source port number of the second packet filter is the same as the destination port number of the first packet filter, and the destination port number of the second packet filter is the same as the source port number of the first packet filter;
  • the packet filter maps the first downlink data packet of the APP's service flow to the QoS flow to obtain a second downlink data packet.
  • an implementation method maps the first downlink data packet of an APP to the QoS flow mapped by the uplink data packet of the APP, and obtains the second downlink data packet, thereby realizing the use of the same QoS. Stream the uplink service flow and downlink service flow of the same APP.
  • the present application provides a data transmission method.
  • the method includes: the terminal maps a first uplink data packet of a service flow generated on the terminal's APP to a QoS flow according to the APP information, to obtain a second uplink data packet, where the second uplink data packet includes QFI and first indication information, QFI is used to identify the QoS flow, and the first indication information is used to instruct the user plane network element to use the reflected QoS function for the service flow of the APP; the terminal sends a second uplink data packet to the user plane network element.
  • the terminal maps the uplink service flow generated by the APP to the QoS flow corresponding to the APP, and then sends it to the user plane network element, and instructs the user plane network element to use the same QoS stream to transmit the downlink service flow of the APP.
  • This solution is based on the granularity of the APP to transmit uplink data packets and downlink data packets.
  • the service flow of the same APP will be identified as the traffic of the APP, so the service identification is accurate; and because no uplink data packets or Downstream data packets are analyzed in depth, that is, it is not necessary to read the contents of the IP packet payload to restructure and analyze the application layer information in the seven-layer protocol, which is conducive to improving the speed of identification and accurately identifying encrypted business flows. come out.
  • the terminal may further receive second policy information from the session management network element, and the second policy information includes QFI, APP information, and first indication information.
  • the second policy information is a QoS rule.
  • the QoS rule is used to guide the terminal to identify the uplink service flow and the mapping of the uplink service flow to the QoS flow.
  • the information of the APP includes an identifier of the APP; or, the information of the APP includes an identifier of the APP and an identifier of an operating system (OS) corresponding to the APP.
  • OS operating system
  • the present application provides a device, which may be a terminal, a user plane network element, or a chip.
  • the device has a function of implementing any one of the first aspect or the second aspect described above. This function can be realized by hardware, and can also be implemented by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • an apparatus including: a processor and a memory; the memory is configured to store a computer execution instruction, and when the apparatus is running, the processor executes the computer execution instruction stored in the memory, so that the apparatus executes The data transmission method according to the first aspect or any one of the first aspects, or to cause the device to execute the data transmission method according to the second aspect or any one of the second aspects.
  • the present application provides a data transmission system.
  • the method includes: a session management network element, configured to send first policy information to a user plane network element, where the first policy information includes QFI and second indication information, the QFI is used to identify a quality of service QoS flow, and the second indication information is used to: Indicates that the service corresponding to the QoS flow identified by the QFI is an application APP service; a user plane network element is configured to receive an uplink data packet of the service flow of the APP from the terminal, and the uplink data packet includes the QFI and first indication information ,
  • the first instruction information is used to instruct the user plane network element to use the reflection QoS function for the service flow of the APP; according to the first instruction information, the first downlink data packet of the service flow of the APP is mapped to all
  • the QoS flow is described, and a second downlink data packet is obtained, where the second downlink data packet includes the QFI; and the second downlink data packet is sent to the terminal.
  • the present application provides another data transmission system. Including, the user plane network element of the first aspect and any one of the first aspect and the terminal of any of the second aspect and any one of the second aspect.
  • the present application further provides a computer-readable storage medium, where the computer-readable storage medium has instructions stored therein, which when run on a computer, causes the computer to execute the method described in the first aspect; or, Perform the method described in the second aspect above.
  • the present application further provides a computer program product including instructions, which when executed on a computer, causes the computer to execute the method described in the first aspect; or, executes the method described in the second aspect.
  • FIG. 1 (a) is a schematic diagram of a possible system provided by this application.
  • FIG. 1 (b) is another schematic diagram of a possible system provided by the present application.
  • FIG. 2 is a schematic diagram of another possible system provided by the present application.
  • FIG. 3 is a flowchart of a data transmission method provided by the present application.
  • FIG. 5 is a schematic diagram of a device provided by this application.
  • FIG. 6 is a schematic diagram of another device provided by the present application.
  • FIG. 1 (a) it is a schematic diagram of a possible system applicable to this application.
  • the system includes user plane network elements. Further, the system may further include a session management network element. Further, the system may further include a policy control network element. Further, the system may further include an access device. Further, the system may further include a mobility management network element.
  • a network element in the system shown in FIG. 1 (a) can implement the following functions:
  • a user plane network element is configured to receive an uplink data packet of a service flow of the APP from the terminal, where the uplink data packet includes the QFI and first indication information, and the first indication information is used to indicate the user plane
  • the network element uses the reflection QoS function for the APP's service flow; according to the first instruction information, the first downlink data packet of the APP's business flow is mapped to the QoS flow to obtain a second downlink data packet, so The second downlink data packet includes the QFI; and sending the second downlink data packet to a terminal.
  • a session management network element is configured to send first policy information to a user plane network element, where the first policy information includes QFI and second indication information, and the QFI is used to identify a QoS flow,
  • the second indication information is used to indicate that a service corresponding to the QoS flow identified by the QFI is an APP service.
  • the user plane network element maps a first downlink data packet of a service flow of the APP to the QoS flow according to the first instruction information to obtain a second downlink data packet. , Specifically, determining a second packet filter according to a first packet filter of the uplink data packet, wherein a source address of the first packet filter is the same as a destination address of the second packet filter, the The destination address of the first packet filter is the same as the source address of the second packet filter, and the source port number of the first packet filter is the same as the destination port number of the second packet filter.
  • the destination port number of the packet filter is the same as the source port number of the second packet filter; the user plane network element sends the first downstream of the APP service flow according to the second packet filter.
  • the data packet is mapped to the QoS flow to obtain a second downlink data packet.
  • the session management network element is further configured to send second policy information to the terminal, where the second policy information includes the QFI, the APP information, and the first Instructions.
  • the session management network element is further configured to send third policy information to an access device, where the third policy information includes the QFI and third indication information, and the third indication The information is used by the access device to allow the uplink service flow of the APP to carry the first indication information.
  • the session management network element is further configured to receive QoS policy information from a policy control network element, where the QoS policy information includes fourth indication information and information of the APP, and the first The four indication information is used to instruct the service flow of the APP to use the reflection QoS function; and the first policy information is generated according to the QoS policy information.
  • the policy control network element is configured to receive a request message from the session management network element, where the request message is used to request acquisition of policy information of the terminal; from a data management network element Acquiring subscription data of the terminal, where the subscription data includes information of an APP of the terminal; generating the QoS policy information according to the subscription data; and sending the QoS policy information to the session management network element.
  • the access device is configured to receive the third policy information from the session management network element.
  • the access device is further configured to receive an uplink data packet of a service flow of the APP from the terminal; and send the uplink data packet to all the uplink data packets according to the third instruction information.
  • the user plane network element is described.
  • FIG. 1 (b) it is a schematic diagram of another system provided by the present application.
  • the system includes a terminal and a session management network element.
  • a network element in the system shown in FIG. 1 (b) can implement the following functions:
  • a session management network element configured to send second policy information to a terminal, where the second policy information includes QFI, APP information, and first indication information, the QFI is used to identify the QoS flow, and the first indication information It is used to instruct the user plane network element to use the reflective QoS function for the service flow of the APP.
  • the terminal is configured to map a first uplink data packet of a service flow generated on the APP of the terminal to a QoS flow according to the information of the APP to obtain a second uplink data packet, where the second uplink data packet includes QFI and first indication information; And sending the second uplink data packet to a user plane network element.
  • FIG. 2 it is a schematic diagram of another system provided by the present application.
  • This system is a 5th generation (5G) architecture diagram, and the system can be used as a specific implementation of the system shown in FIG. 1 (a) or FIG. 1 (b).
  • the 5G architecture includes a terminal, a radio access network (RAN) device, a user plane function (UPF) network element, a session management function (SMF), and a policy control function. (PCF) network element, access and mobility management function (AMF) network element, Unified Data Repository (UDR), Network Open Function (NEF) network element, etc.
  • RAN radio access network
  • UPF user plane function
  • SMF session management function
  • PCF policy control function
  • AMF access and mobility management function
  • UDR Unified Data Repository
  • NEF Network Open Function
  • the interface between the terminal and the AMF network element is the N1 interface
  • the interface between the AMF network element and the RAN device is the N2 interface
  • the interface between the RAN device and the UPF network element is the N3 interface
  • the SMF network element and the UPF network element The interface between them is N4 interface
  • the interface between SMF network element and PCF network element is N7 interface
  • the interface between AMF network element and SMF network element is N11 interface
  • the interface between AMF network element and PCF network element is N15 interface.
  • the names of the aforementioned network elements may change, and the interface names between the various network elements may also change.
  • the user plane network element in this application may be a UPF network element shown in FIG. 2 in 5G communication, and is mainly responsible for processing user packets, such as forwarding, billing, and legal interception.
  • future communications such as 6th generation (6G) communications
  • the user plane network element may still be a UPF network element or have another name, which is not limited in this application.
  • the session management network element in this application may be an SMF network element shown in FIG. 2 in 5G communication, and is mainly used for session management in a mobile network, such as session establishment, modification, and release. Specific functions include terminal assignment of Internet protocol (IP) addresses, selection of user plane network elements that provide message forwarding functions, and the like. In future communications such as 6G communications, the session management network element may still be an SMF network element or have another name, which is not limited in this application.
  • IP Internet protocol
  • the policy control network element in this application may be a PCF network element shown in FIG. 2 in 5G communication, which includes a user subscription data management function, a policy control function, a charging policy control function, and a quality of service (QoS). ) Control, etc.
  • the policy control network element may still be a PCF network element or have another name, which is not limited in this application.
  • the mobility management network element of this application may be an AMF network element shown in FIG. 2 in 5G communication, which is mainly used for the process of terminal attachment, mobility management, and tracking area update in a mobile network.
  • the mobility management network element Terminates non-access stratum (NAS) messages, completes registration management, connection management, and reachability management, assigns tracking area lists (TA lists), and mobility management, and transparently routes session management ( session management (SM) message to the session management network element.
  • NAS non-access stratum
  • TA lists tracking area lists
  • SM session management
  • the mobility management network element may still be an AMF network element or have another name, which is not limited in this application.
  • the access device of the present application may be a RAN device shown in FIG. 2 in 5G communication, and is a device that provides a terminal with a wireless communication function.
  • the access equipment includes, but is not limited to, a next-generation base station (gNB), an evolved node B (eNB), a radio network controller (RNC), and a node B (node) in 5G. B, NB), base station controller (BSC), base transceiver station (BTS), home base station (e.g., home nodeB, or home node B, HNB), baseband unit (baseBand unit, BBU), transmission point (TRP), transmission point (TP), transmission point (TP), mobile switching center, etc.
  • gNB next-generation base station
  • eNB evolved node B
  • RNC radio network controller
  • node B node B
  • BSC base station controller
  • BTS base transceiver station
  • home base station e.g., home nodeB, or home node B, HNB
  • the terminal of this application is a device with wireless transceiver function, which can be deployed on land, including indoor or outdoor, handheld or vehicle-mounted; it can also be deployed on the water (such as a ship, etc.); it can also be deployed in the air (such as an aircraft, Balloons and satellites).
  • the terminal may be a mobile phone, a tablet, a computer with a wireless transmitting and receiving function, a virtual reality (VR) terminal, an augmented reality (AR) terminal, or an industrial control.
  • the data transmission method provided in this application can be used to solve the above problems.
  • FIG. 3 it is a flowchart of a data transmission method provided by the present application.
  • the method includes uplink data transmission and downlink data transmission.
  • APP data flow occurs first in the upstream direction. That is, the terminal initiates the transmission of the upstream data stream of the APP, and then the UPF initiates the transmission of the downstream data stream of the APP. These are explained separately below.
  • the method includes:
  • Step 301 The terminal maps the first uplink data packet of the service flow generated on the APP of the terminal to the QoS flow according to the information of the APP to obtain a second uplink data packet.
  • the second uplink data packet includes QFI and first indication information, where the QFI is used to identify a QoS flow, and the first indication information is used to instruct the UPF to use the reflected QoS function for the service flow of the APP.
  • the first indication information may be, for example, a reflective QoS indication (Reflective QoS Indication, RQI).
  • the terminal can send the service flow generated on the APP to the UPF, and the UPF processes the service flow, such as charging the service flow and controlling bandwidth.
  • the terminal obtains information of the APP.
  • the information of the APP may be, for example, an identifier of the APP, or may also be an identifier of the APP and an OS identifier.
  • the information of the APP is used to identify the APP.
  • the terminal determines the QFI of the QoS flow to which the service flow of the APP is mapped according to the correspondence between the information of the APP and the QFI stored in advance.
  • the correspondence between the information of the APP and the QFI may be part of the policy information of the terminal (in this application, the policy information of the terminal may also be referred to as the second policy information).
  • the second policy information includes the correspondence between the information of the APP and the QFI. It may further include the first indication information, and further may include the priority information of the second policy information.
  • the second policy information may be sent to the terminal by the SMF.
  • the second policy information may be sent by the SMF to the terminal in the form of a QoS rule, which is used to instruct the terminal to identify the uplink service flow and to map the uplink service flow to the QoS flow.
  • QoS rules can also include other information, which is not limited in this application.
  • the following uses the form of a table as an example to specifically describe the second policy information of the terminal.
  • An example of the second policy information is shown in Table 1.
  • the information of the APP includes the ID of the APP.
  • the terminal can obtain the information of APP5, that is, APPid5, and then determine the QFI corresponding to APPid5 according to the second policy information of the terminal. For example, if priority information is not included in the second policy information, the QoS rules can be matched one by one according to the stored order, until the QFI corresponding to APP ID5 is matched, or after all the matching is failed. If the second policy information further includes priority information, matching may be started from a QoS rule with a higher priority according to the priority, until the QFI corresponding to the APP ID5 is matched, or after all matching is failed.
  • APP ID5 is successfully matched in the QoS rule, and QFI3 corresponding to APP ID5 is determined. Therefore, the data packets of the service flow of APP5 will be mapped to the QoS flow corresponding to QFI3.
  • Table 2 it is another example of the policy information.
  • the information of the APP includes the identifier of the APP and the identifier of the OS.
  • the APP information in Table 2 includes the identifier of the APP and the identifier of the OS.
  • the information of the APP corresponding to a QoS rule includes the same OS.
  • the information of the APP corresponding to QoS rule1 includes OS1
  • the information of the APP corresponding to QoS rule2 includes OS1
  • the information of the APP corresponding to QoS rule3 includes OS2.
  • the information of the APP corresponding to a QoS rule may also include different OSs.
  • the APP information corresponding to QoS rule1 includes (OS1, APP id1), (OS2, APP id2), (OS2, APP id3), and so on.
  • the terminal can obtain the information of APP5, that is, APPID5 or (OS2, APPID5), and then determine the QFI corresponding to APP5 information according to the terminal's second policy information . For example, if the priority information is not included in the second policy information, the QoS rules can be matched one by one according to the stored order until the QFI corresponding to the information of APP5 is matched, or it fails after all matching is completed. If the second policy information also includes priority information, the matching can be started from the QoS rule with a higher priority according to the priority, until the QFI corresponding to the information of APP5 is matched, or it fails after all matching is completed.
  • Table 1 also includes QoS rule 5, which includes QFI, APP information, priority information, and indication information: QFI 5, APP ID 2, 5, and first indication information.
  • QoS rule 5 includes QFI, APP information, priority information, and indication information: QFI 5, APP ID 2, 5, and first indication information.
  • the QoS rules may or may not carry priority information.
  • the service flow generated on the terminal's APP is sent in the form of a data packet.
  • the any uplink data packet may be referred to as a first uplink data packet, and the first uplink data packet is mapped to a QoS flow corresponding to the QFI to obtain a second uplink data packet.
  • the two uplink data packets include QFI and first indication information, and the first indication information is used to instruct the UPF to use the reflection QoS function for the service flow of the APP.
  • Step 302 The terminal sends the second uplink data packet to the UPF. Accordingly, the UPF can receive the third uplink data packet.
  • the terminal may send the second uplink data packet to the RAN device through the DRB corresponding to the QoS flow, and the RAN device updates the encapsulation header of the second uplink data packet according to the second uplink data packet to obtain the third uplink data. Packet, and sends a third uplink data packet to the UPF.
  • the third uplink data packet includes QFI and first indication information.
  • the terminal may send the second uplink data packet to the RAN device through a DRB corresponding to the QoS flow, and the RAN device performs the first step according to locally stored policy information (the policy information may be referred to as third policy information). Scheduling and QoS guarantee of the two uplink data packets, obtaining a third uplink data packet and sending the third uplink data packet to the UPF.
  • the third policy information of the RAN device may be sent by the SMF to the RAN device.
  • the third policy information includes QFI and third indication information, and the third indication information is used to instruct the RAN device to allow the uplink service flow of the APP to carry the third policy information.
  • An instruction message is used to instruct the RAN device to allow the uplink service flow of the APP to carry the third policy information.
  • the third policy information may include information such as QFI and QoS profile, and the QoS profile may include third indication information.
  • the third indication information may be, for example, a reflective QoS attribute (RQA).
  • the QoS profile can also include 5QI (5G, QoS, Identifier), allocation retention priority (ARP), etc.
  • ARP allocation retention priority
  • the QoS profile can also include guarantee Flow bit rate (Guaranteed Flow Bit Rate, GFBR), Maximum flow bit rate (Maximum Flow Bit Rate, MFBR), etc.
  • the RAN device can also offload the radio resources and channels for the QFI in the third policy information according to the third policy information, and establish a DRB corresponding to the QFI. Among them, one DRB may correspond to one or more QFIs.
  • the first uplink data packet generated by the APP is actual application data
  • the second uplink data packet includes the first uplink data packet, the QFI, and the first indication information, where the QFI and the first indication information are carried in In the encapsulation header of the second uplink data packet.
  • the RAN device forwards the data between the wireless side and the core network. Because the interface between the RAN device and the terminal (such as the Uu interface) is different from the interface between the RAN device and the UPF (such as the N3 interface), the RAN device needs to Data such as QFI in the encapsulation header of the uplink data packet is re-encapsulated to obtain a third uplink data packet.
  • the RAN device checks the encapsulation header of the second uplink data packet. If it is found that the encapsulation header of the second uplink data packet has only QFI and no first indication information, the RAN device encapsulates the encapsulation header of the second uplink data packet to obtain a new one.
  • the third upstream data packet includes a new encapsulation header and the first upstream data packet, and the new encapsulation header includes QFI. If it is found that the encapsulation header of the second uplink data packet has QFI and the first indication information, the RAN device needs to determine whether there is third indication information in the third policy information received previously.
  • the RAN device encapsulates the encapsulation header of the second uplink data packet to obtain a new encapsulation header, the third uplink data packet includes the new encapsulation header and the first uplink data packet, and the new encapsulation header includes QFI and First indication information; if there is no third indication information in the third policy information, the RAN device encapsulates the encapsulation header of the second uplink data packet to obtain a new encapsulation header, and the third uplink data packet includes the new encapsulation header and the first An upstream data packet.
  • the new encapsulation header includes QFI.
  • the RAN device then sends the third uplink data packet to the UPF.
  • the format of the encapsulation header of the second uplink data packet is different from the format of the new encapsulation header of the third uplink data packet and / or the protocol used.
  • the UPF After receiving the third uplink data packet, the UPF performs corresponding accounting, bandwidth and other control according to the first policy information corresponding to the QFI in the third uplink data packet.
  • uplink data packets of APP service flows are sent to the UPF in the uplink direction.
  • the terminal maps the uplink data packet of the APP's service flow to the QoS flow, it does not need to identify the uplink data packet of the APP's service flow, for example, it is not necessary to identify the uplink data packet by identifying the quintuple information of the uplink data packet.
  • the QFI corresponding to the data packet is determined by the QFI corresponding to the uplink data packet of the service flow according to the information of the APP that generated the service flow. Therefore, the uplink data packet of the service flow can be quickly and accurately identified and mapped to Corresponding QoS flow.
  • the UPF is at the granularity of the APP, when the UPF receives the uplink data packet of the service flow, only the QFI in the uplink data packet can be used to identify the corresponding uplink data packet.
  • APP to perform billing and bandwidth control operations on the service flow.
  • the method includes:
  • Step 303 The UPF maps the first downlink data packet of the APP service flow to the QoS flow according to the first instruction information, and obtains the second downlink data packet.
  • the UPF After the UPF receives the uplink data packet of the service flow sent by the terminal, for example, after receiving the above-mentioned second uplink data packet, the second uplink data packet includes the first indication information and the QFI, so the UPF can obtain the second uplink data packet The first instructions and QFI. According to the first instruction information, the UPF can determine that the downlink data packet of the APP's service flow can be sent to the terminal through the second uplink data packet corresponding to the QoS flow, that is, the uplink data packet of the APP's business flow and the APP's business flow. The downlink data packets are transmitted through the same QoS stream.
  • the downlink data packet of the service flow for example, the first downlink data packet is mapped to the above QoS flow to obtain a second downlink data packet.
  • the second downlink data packet includes QFI, which is used to identify the aforementioned QoS flow.
  • the UPF can map the first downlink data packet of the APP's service flow to the QoS flow to obtain the second downlink data packet by the following method:
  • the UPF receives the uplink data packet of the APP's service flow, such as After the second uplink data packet, the QFI and first indication information of the second uplink data packet are obtained, and a first packet filter of the second uplink data packet is further obtained.
  • the first packet filter includes Five-tuple information: source address, source port number, destination address, destination port number, and protocol type.
  • the UPF determines a second packet filter according to the first packet filter.
  • the second packet filter also includes five-tuple information: source address, source port number, destination address, destination port number, and protocol type.
  • the source address of the second packet filter is the same as the destination address of the first packet filter
  • the destination address of the second packet filter is the same as the source address of the first packet filter
  • the source port number of the second packet filter is the same as The destination port number of the first packet filter is the same
  • the destination port number of the second packet filter is the same as the source port number of the first packet filter
  • the protocol type of the second packet filter is the same as that of the first packet filter. Same model.
  • the quintuple information included in the first packet filter of the second uplink data packet is (source address: IP1, source port number: port1, destination address: IP2, destination port number: port2, protocol type: p1)
  • the quintuple information included in the second packet filter determined by the UPF is (source address: IP2, source port number: port2, destination address: IP1, destination port number: port1, protocol type: p1).
  • the UPF can record the correspondence between the QFI and the quintuple information of the second packet filter.
  • the UPF receives the downlink data packet of the APP's service flow, such as the first downlink data packet, it can identify the first downlink data packet according to the second packet filter.
  • the quintuple information in a downlink data packet matches the quintuple information in the second packet filter, then mapping the first downstream data packet to the QoS flow identified by the QFI corresponding to the second packet filter, That is, the QFI is added to the first downlink data packet to obtain a second downlink data packet.
  • the UPF may further receive policy information from the SMF.
  • the policy information may be referred to as first policy information.
  • the first policy information includes QFI and second instruction information.
  • the service corresponding to the QoS flow indicated by the QFI identifier is an APP service, and the QFI is the same as the QFI in the second policy information sent by the SMF to the terminal. That is, through the first policy information, the UPF learns that the service corresponding to the QoS flow identified by the QFI is an APP service.
  • the first policy information may include a PDR, and the PDR includes QFI and second indication information. Further, the PDR may further include a QoS enforcement rule (QoS Enforcement Rule, QER). The PDR is used for Indication is used for packet inspection. The QER may include parameters of a Qos policy, parameters such as bandwidth. After receiving the PDR, UPF installs the rules and performs QFI resource management.
  • QFI QoS Enforcement Rule
  • Step 304 The UPF sends a second downlink data packet to the terminal. Accordingly, the terminal may receive a third downlink data packet.
  • the UPF sends a second downlink data packet to the terminal.
  • the UPF also controls the downlink service flow based on the first policy information corresponding to the QFI, and controls the bandwidth and bandwidth.
  • the second downlink data packet includes an encapsulation header and the first downlink data packet, and the encapsulation header includes QFI.
  • the UPF can send the second downlink data packet to the RAN device through the N3 interface.
  • the RAN device re-encapsulates QFI and other data in the encapsulation header of the second downlink data packet to obtain a new encapsulation header.
  • the RAN device sends a third A downlink data packet, the third downlink data packet includes the new encapsulation header and a first downlink data packet, and the new encapsulation header includes QFI.
  • the format of the encapsulation header of the second downlink data packet is different from the format of the new encapsulation header of the third downlink data packet and / or the protocol used.
  • the UPF can send the downlink data packet of the APP's service flow to the terminal through the QoS flow corresponding to the uplink data packet of the APP's service flow.
  • the UPF does not need to identify the downlink data packets of the service flow in depth, but only needs to determine that the downlink data packet corresponds to the QFI, and the QFI is also the QFI corresponding to the uplink data packet. Therefore, the UPF can quickly and accurately transfer the APP's Downstream packets of the service flow are mapped to QoS flows.
  • the APP server encrypts the APP's business flow
  • the UPF since the UPF does not need to identify the downstream data packets of the APP's business flow in depth, although the business flow is encrypted, it does not affect UPF's downstream of the business flow.
  • the data packet is mapped to the QoS flow, thereby realizing accurate and fast processing of the encrypted service flow.
  • the third-party business flow that is linked into the APP can also be accurately identified as the APP's traffic. For example, for JD applications that are opened through a link in WeChat, that is, access to JD on a page in WeChat, it can be accurately identified as WeChat. Traffic, realizes accurate identification and control of APP traffic.
  • a QoS policy allocation method is introduced below.
  • policy information can be allocated to a terminal and a UPF in the embodiment shown in FIG. 3, and further, policy information can be allocated to a RAN device.
  • the QoS policy allocation method provided for this application. The method includes the following steps:
  • Step 401 The terminal sends a session establishment request message to the SMF. Accordingly, the SMF can receive the session establishment request message.
  • the session establishment request message is used to request establishment of a session.
  • the session establishment request message may also have other names, such as a session establishment message, a request message, a establishment request message, a first message, and so on.
  • Step 402 The SMF sends a request message to the PCF. Accordingly, the PCF can receive the request message.
  • the request message is used to request to obtain the policy information of the terminal.
  • Step 403 The PCF obtains the subscription data of the terminal from the data management network element.
  • the data management network element may be, for example, a UDR as shown in FIG. 2.
  • the contract data of the terminal obtained by the PCF from the data management network element includes information of the APP of the terminal, and the information of the APP includes the identifier of the APP, or the information of the APP includes the identifier of the APP and the identifier of the OS.
  • Step 404 The PCF generates QoS policy information according to the subscription data.
  • the QoS policy information generated by the PCF includes fourth indication information and APP information, and the fourth indication information is used to instruct the service flow of the APP to use the reflection QoS function.
  • the fourth indication information may be a reflective QoS indication.
  • the above steps 401 to 404 are optional steps, that is, the reason for triggering the PCF to send QoS policy information to the SMF (that is, the following step 405) may be based on the terminal's session establishment request message and the SMF request message (that is, the above Steps 401 to 404), or other reasons.
  • the PCF may actively perform the above steps 403 to 404, that is, the above steps 401 to 402 are not performed, and Only the above steps 403 to 404 are performed.
  • the PCF can receive the QoS parameters from the NEF network element and generate QoS policy information according to the QoS parameters. That is, the foregoing steps 401 to 404 are not performed, where the terminal is using the service of the application server.
  • Step 405 The PCF sends QoS policy information to the SMF. Accordingly, the SMF can receive the QoS policy information.
  • Step 406 The SMF generates first policy information, second policy information, and third policy information according to the QoS policy information.
  • the SMF generates a QFI according to the policy information, and the QFI is used to identify the QoS flow.
  • the QFI corresponds to the information of the APP.
  • one QFI may correspond to the information of one APP one by one, or may correspond to the information of multiple APPs.
  • the QFI can only be assigned to identify a QoS flow corresponding to a service flow of an APP. It can be understood that the QFI is not used to identify a QoS flow corresponding to a non-APP service flow.
  • the first policy information generated by the SMF includes the above-mentioned QFI and second instruction information, and the second instruction information is used to indicate that the service corresponding to the QoS flow identified by the QFI is an application APP service.
  • the second policy information generated by the SMF includes the aforementioned QFI, APP information, and first indication information.
  • the first indication information is used to instruct the UPF to use the reflection QoS function for the service flow of the APP.
  • the third policy information generated by the SMF includes the above-mentioned QFI and third indication information, and the third indication information is used for the RAN device to allow the uplink service flow of the APP to carry the first indication information.
  • the generation of the first instruction information and the third instruction information are related to the fourth instruction information.
  • Step 407 The SMF sends third policy information to the RAN device. Accordingly, the RAN device may receive the third policy information.
  • Step 408 The SMF sends the first policy information to the UPF. Accordingly, the UPF may receive the first policy information.
  • Step 409 The SMF sends the second policy information to the terminal. Accordingly, the terminal may receive the second policy information.
  • the SMF generates the first policy information, the second policy information, and the third policy information according to the QoS policy information received from the PCF, and sends them to the UFP, the terminal, and the RAN device respectively, so that the UPF, the terminal, and the RAN The device processes the uplink data packet and the downlink data packet according to the first policy information, the second policy information, and the third policy information, respectively.
  • the terminal and the UPF can realize fast and accurate identification of the uplink data packet and the downlink data packet. For the encrypted data flow packet, the corresponding QoS flow can be identified quickly and accurately without deep identification, thereby improving the data transmission effectiveness.
  • the names of the policy information used in the foregoing embodiments of the present application are not limited, and policy information of other names that have the same function as a certain policy information may also be considered to be substantially the same as the policy information.
  • the same message As an example, the first policy information in the foregoing embodiments may also be referred to as a first policy or policy information, and the second policy information in the foregoing embodiments may also be referred to as a second policy or policy information.
  • the third policy information in the embodiments may also be referred to as a third policy or policy information.
  • each network element includes a hardware structure and / or a software module corresponding to each function.
  • the present invention can be implemented in the form of hardware or a combination of hardware and computer software by combining the units and algorithm steps of each example described in the embodiments disclosed herein. Whether a certain function is performed by hardware or computer software-driven hardware depends on the specific application and design constraints of the technical solution. A person skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the present invention.
  • a schematic diagram of a device provided by this application may be a terminal, or a user plane network element, or a chip, and the terminal, or the user in any of the foregoing embodiments may be executed. Method implemented by the network element.
  • the device 500 includes at least one processor 501, a communication line 502, a memory 503, and at least one communication interface 504.
  • the processor 501 may be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrations for controlling the execution of the program program of the present application. Circuit.
  • CPU central processing unit
  • ASIC application-specific integrated circuit
  • the communication line 502 may include a path for transmitting information between the aforementioned components.
  • the communication interface 504 uses any device such as a transceiver to communicate with other devices or communication networks, such as Ethernet, radio access network (RAN), wireless local area networks (WLAN), Wired access network, etc.
  • RAN radio access network
  • WLAN wireless local area networks
  • Wired access network etc.
  • the memory 503 may be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM) or other type that can store information and instructions
  • the dynamic storage device can also be electrically erasable programmable read-only memory (electrically server-programmable read-only memory (EEPROM)), compact disc (read-only memory (CD-ROM) or other optical disk storage, Optical disc storage (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program code in the form of instructions or data structures and can Any other media accessed by the computer, but not limited to this.
  • the memory may exist independently, and is connected to the processor through the communication line 502. The memory can also be integrated with the processor.
  • the memory 503 is configured to store a computer execution instruction for executing the solution of the present application, and the execution is controlled by the processor 501.
  • the processor 501 is configured to execute computer execution instructions stored in the memory 503, so as to implement the data transmission method and the policy allocation method provided by the foregoing embodiments of the present application.
  • the computer-executable instructions in the embodiments of the present application may also be referred to as application program codes, which are not specifically limited in the embodiments of the present application.
  • the processor 501 may include one or more CPUs, such as CPU0 and CPU1 in FIG. 5.
  • the apparatus 500 may include multiple processors, such as the processor 501 and the processor 508 in FIG. 5. Each of these processors can be a single-CPU processor or a multi-CPU processor.
  • a processor herein may refer to one or more devices, circuits, and / or processing cores for processing data (such as computer program instructions).
  • the chip When the device shown in FIG. 5 is a chip, for example, a chip of a terminal or a chip of a user-side network element, the chip includes a processor 501 (also may include a processor 508), a communication line 502, a memory 503, and a communication Interface 504.
  • the communication interface 504 may be an input interface, a pin, or a circuit.
  • the memory 503 may be a register, a cache, or the like.
  • the processor 501 and the processor 508 may be a general-purpose CPU, a microprocessor, an ASIC, or one or more integrated circuits for controlling the program execution of the data transmission method and / or the policy allocation method of any of the above embodiments.
  • each functional module may be divided corresponding to each function, or two or more functions may be integrated into one processing module.
  • the above integrated modules can be implemented in the form of hardware or software functional modules. It should be noted that the division of the modules in this application is schematic, and is only a logical function division. In actual implementation, there may be another division manner.
  • FIG. 6 shows a schematic diagram of a device.
  • the device 600 may be a user plane network element involved in the foregoing embodiment, or be a terminal or a user plane. A chip in a network element or a chip in a terminal.
  • the device 600 includes a receiving unit 601, a sending unit 602, and a processing unit 603.
  • the device 600 may implement the following operations: a receiving unit for receiving an uplink data packet of a service flow from an application APP of a terminal, and the uplink data packet includes QFI and The first indication information, QFI is used to identify the QoS flow, the first indication information is used to instruct the user plane network element to use the reflective QoS function for the service flow of the APP; the processing unit is configured to use The first downlink data packet is mapped to the QoS flow to obtain a second downlink data packet, where the second downlink data packet includes the QFI; and a sending unit is configured to send a downlink data packet to the terminal.
  • the receiving unit is further configured to receive first policy information from the session management network element, where the first policy information includes QFI and second indication information, and the second indication information is used to indicate that the service corresponding to the QoS flow identified by the QFI is: APP business.
  • the processing unit is specifically configured to determine a second packet filter according to the first packet filter of the uplink data packet, where the source address of the second packet filter is the same as the destination address of the first packet filter, and the first The destination address of the second packet filter is the same as the source address of the first packet filter.
  • the source port number of the second packet filter is the same as the destination port number of the first packet filter.
  • the destination port number of the second packet filter is the same as the destination port number of the first packet filter.
  • the source port number of a packet filter is the same; according to the second packet filter, the first downlink data packet of the APP's service flow is mapped to the QoS flow to obtain the second downlink data packet.
  • the device 600 may implement the following operations: a processing unit configured to map a first uplink data packet of a service flow generated on the terminal's APP to a QoS flow according to information of an application APP, A second uplink data packet is obtained.
  • the second uplink data packet includes QFI and first indication information.
  • QFI is used to identify the QoS flow.
  • the first indication information is used to instruct the user plane network element to use the reflected QoS function for the service flow of the APP; the sending unit , For sending a second uplink data packet to the user plane network element.
  • the receiving unit is configured to receive second policy information from the session management network element.
  • the second policy information includes QFI, APP information, and first indication information.
  • apparatus 600 may be used to implement the steps performed by the terminal or the user plane network element in the method of the embodiment of the present invention.
  • the apparatus 600 may be used to implement the steps performed by the terminal or the user plane network element in the method of the embodiment of the present invention.
  • the user plane network element is presented in the form of dividing each functional module in an integrated manner.
  • the "module” herein may refer to a specific ASIC, a circuit, a processor and a memory executing one or more software or firmware programs, an integrated logic circuit, and / or other devices that can provide the above functions.
  • the user plane network element may adopt the form shown in FIG. 6.
  • the processor 501 in FIG. 5 may cause a user plane network element to execute the method in the foregoing method embodiment by calling a computer execution instruction stored in the memory 503.
  • the terminal is presented in the form of dividing each functional module in an integrated manner. In a simple embodiment, those skilled in the art may think that the terminal may adopt the form shown in FIG. 6.
  • the processor 501 in FIG. 5 may cause a terminal to execute the method in the foregoing method embodiment by calling a computer execution instruction stored in the memory 503.
  • the function / implementation process of the receiving unit 601, the processing unit 603, and the sending unit 602 in FIG. 6 may be implemented by the processor 501 in FIG. 5 calling a computer execution instruction stored in the memory 503.
  • the function / implementation process of the processing unit 603 in FIG. 6 may be implemented by the processor 501 in FIG. 5 calling a computer execution instruction stored in the memory 503, and the function / implementation of the receiving unit 601 and the sending unit 602 in FIG. 6
  • the process may be implemented through the communication interface 504 in FIG. 5.
  • the function / implementation process of the receiving unit 601 and the sending unit 602 may also be implemented through pins or circuits.
  • the memory 603 may be a storage unit in the chip, such as a register, a cache, and the like.
  • the memory 603 may be a storage unit located outside the chip in the user plane network element or terminal, which is not specifically limited in this embodiment of the present application.
  • the computer program product includes one or more computer instructions.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.
  • the computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be from a website site, a computer, a server, or a data center.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, a data center, or the like that includes one or more available medium integration.
  • the available medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk (Solid State Disk, SSD)), and the like.
  • Various illustrative logic units and circuits described in the embodiments of the present application may be implemented by a general-purpose processor, a digital signal processor, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices. Discrete gate or transistor logic, discrete hardware components, or any combination of the above are designed to implement or operate the described functions.
  • the general-purpose processor may be a microprocessor. Alternatively, the general-purpose processor may also be any conventional processor, controller, microcontroller, or state machine.
  • the processor may also be implemented by a combination of computing devices, such as a digital signal processor and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a digital signal processor core, or any other similar configuration. achieve.
  • a software unit may be stored in a RAM memory, a flash memory, a ROM memory, an EPROM memory, an EEPROM memory, a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium in the art.
  • the storage medium may be connected to the processor, so that the processor can read information from the storage medium and can write information to the storage medium.
  • the storage medium may be integral to the processor.
  • the processor and the storage medium may be provided in an ASIC, and the ASIC may be provided in a terminal device. Alternatively, the processor and the storage medium may also be provided in different components in the terminal device.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device, so that a series of steps can be performed on the computer or other programmable device to produce a computer-implemented process, which can be executed on the computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more flowcharts and / or one or more blocks of the block diagrams.

Landscapes

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

Abstract

本申请提供一种数据传输方法、装置及系统。该方法包括：终端将APP的上行数据包映射至APP对应的QoS流，并发送给用户面网元，用户面网元在接收到上行数据包后，根据第一指示信息，将该APP产生的下行数据包映射到该上行数据包对应的QoS流，即上行数据包和下行数据包使用同一个QoS流传输。该方案中，用户面网元是基于APP的粒度对上行数据包和下行数据包进行传输的，对于同一个APP的业务流均会识别为该APP的流量，因而业务识别准确；由于不需要对上行数据包或下行数据包进行深度分析，即不需要深入读取IP包载荷的内容来对七层协议中的应用层信息进行重组分析，有利于提升识别的速度，对于加密的业务流也可以准确识别。

Description

一种数据传输方法、装置及系统
本申请要求于2018年7月6日提交中国国家知识产权局、申请号为201810737409.X、发明名称为“一种数据传输方法、装置及系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及移动通信技术领域，尤其涉及一种数据传输方法、装置及系统。
背景技术
移动通信网络中，运营商能够为用户提供语音、数据、视频等更多丰富多彩的业务。由于不同的业务对时延、带宽等要求各不相同，通过引入服务质量(Quality of Service，QoS)方案，实现各种业务的差异化，为高速数据业务提供了保障，增强了用户的网络体验。QoS方案的目的是针对各种不同的业务需求，提供不同服务质量的网络服务。尤其是在网络拥塞时，优先保障优先级高的用户或业务的服务质量。端到端的QoS保障是由传输用户数据的终端、接入设备、用户面网元实现，可分为接入设备与用户面网元间的核心网侧的下一代(next generation，NG)用户面隧道(NG-U Tunnel)和终端与接入设备间的无线侧的数据无线承载(data radio bearer，DRB)两部分。
上行业务流发生时，终端根据预先配置的QoS策略实现上行业务流到QoS流的映射以及QoS流到DRB的映射，并在上行业务流的上行数据包的封装头中携带映射的QoS流的服务质量流标识(QoS flow indicator，QFI)。其中，终端的QoS策略中包括五元组信息与QFI的映射关系，五元组信息包括源地址、目的地址、源端口、目的端口以及协议类型。因此，终端需要对上行业务流的上行数据包进行分析，获取其中的五元组信息，并根据QoS策略确定该五元组信息对应的QFI，从而实现将上行业务流映射至QoS流。下行业务流发生时，用户面网元可以采用与终端侧相同的方式，将下行业务流映射至另一个QoS流。或者，用户面网元还可以在分析下行业务流的五元组信息的基础上，进一步还深度分析下行业务流的下行业务数据包中的L4-L7(层4-层7)协议的特征，进行协议识别并获取七层协议类型或资源定位符(Uniform Resoure Locator，URL)等有价值信息，从而实现更精准的业务识别。
因此，不管是上行业务流到QoS流的映射，还是下行业务流到QoS流的映射，都需要对业务流的数据包进行识别，尤其是使用协议类型或URL等L7内容进行描述的业务，则比较依赖于用户面网元的业务识别能力。然而当前流行的移动数据业务很多都以应用(APP)形式发布，运营商或APP的所有者为吸引用户会适时推出针对特定APP的数据业务套餐，对该APP的流量免费或优惠，或对QoS体验进行提升或保障。若采用现有的QoS保障方案对APP的业务进行QoS保障，则需要终端及用户面网元对APP的业务流进行识别，可能会存在业务识别不及时、不准确的问题。
发明内容
本申请提供数据传输方法、装置及系统，用以实现对业务流进行快速和准确的识别，以便于及时处理业务流。
第一方面，本申请提供一种数据传输方法。该方法包括：用户面网元接收来自终端的APP的业务流的上行数据包，上行数据包包括QFI和第一指示信息，QFI用于标识QoS流，第一指示信息用于指示用户面网元对APP的业务流使用反射QoS功能；用户面网元根据第一指示信息，将APP的业务流的第一下行数据包映射至QoS流，得到第二下行数据包；用户面网元向终端发送第二下行数据包。基于该方案，终端将APP的上行数据包映射至APP对应的QoS流，并发送给用户面网元，用户面网元在接收到上行数据包后，根据第一指示信息，将用户面网元接收到的该APP产生的第一下行数据包映射到该第一上行数据包对应的QoS流，得到第二下行数据包，所述第二下行数据包包括所述QFI，即上行数据包和下行数据包使用同一个QoS流传输。该方案中，用户面网元是基于APP的粒度对上行数据包和下行数据包进行传输的，对于同一个APP的业务流均会识别为该APP的流量，因而业务识别准确；并且，由于不需要对上行数据包或下行数据包进行深度分析，即不需要深入读取IP包载荷的内容来对七层协议中的应用层信息进行重组分析，因而有利于提升识别的速度，以及对于加密的业务流也可以准确识别出来。
在一种可能的实现方式中，用户面网元接收来自会话管理网元的第一策略信息，第一策略信息包括QFI和第二指示信息，第二指示信息用于指示QFI标识的QoS流对应的业务为APP业务。基于该方案，用户面网元可以从会话管理网元获取到第一策略信息，用户面网元根据该第一策略信息，确定第一策略信息哪些QFI对标识的QoS流对应的业务为APP业务。
在一种可能的实现方式中，第一策略信息包括QFI和第二指示信息，具体包括：第一策略信息包括数据包检测规则(Packet Detection Rule，PDR)，PDR包括QFI和第二指示信息。即会话管理网元以PDR的形式向用户面网元发送第一策略信息。
在一种可能的实现方式中，用户面网元将APP的业务流的第一下行数据包映射至QoS流，得到第二下行数据包，具体包括：用户面网元根据上行数据包的第一包过滤器，确定第二包过滤器，其中第二包过滤器的源地址与第一包过滤器的目的地址相同，第二包过滤器的目的地址与第一包过滤器的源地址相同，第二包过滤器的源端口号与第一包过滤器的目的端口号相同，第二包过滤器的目的端口号与第一包过滤器的源端口号相同；用户面网元根据第二包过滤器，将APP的业务流的第一下行数据包映射至QoS流，得到第二下行数据包。基于该方案，给出了一种实现将APP的第一下行数据包映射至该APP的上行数据包所映射的QoS流，得到第二下行数据包的实现方式，进而实现了使用同一个QoS流传输同一个APP的上行业务流和下行业务流。
第二方面，本申请提供一种数据传输方法。该方法包括：终端根据APP的信息，将终端的APP上产生的业务流的第一上行数据包映射至QoS流，得到第二上行数据包，第二上行数据包包括QFI和第一指示信息，QFI用于标识QoS流，第一指示信息用于指示用户面网元对APP的业务流使用反射QoS功能；终端向用户面网元发送第二上行数据包。基于该方案，终端将APP产生的上行业务流映射至该APP对应的QoS流，然后发送至用户面网元，并指示用户面网元使用同样的QoS流传输该APP的下行业务流。该方案是基于APP的粒度对上行数据包和下行数据包进行传输的，对于同一个APP的业务流均会识别为该APP的流量，因而业务识别准确；并且，由于不需要对上行数据包或下行数据包进行深度分析，即不需要深入读取IP包载荷的内容来对七层协议中的应用层信息进行重组分析，因而有利于提升识别的速度，以及对于加密的业务流也可以准确识别出来。
在一种可能的实现方式中，终端还可以接收来自会话管理网元的第二策略信息，第二策 略信息包括QFI、APP的信息和第一指示信息。在一种可能的实现方式中，第二策略信息为QoS rule。QoS rule用于指导终端对上行业务流进行识别，以及对上行业务流到QoS流的映射。
在一种可能的实现方式中，APP的信息包括APP的标识；或者，APP的信息包括APP的标识和APP对应的操作系统(operation system，OS)的标识。
第三方面，本申请提供一种装置，该装置可以是终端、或用户面网元，还可以是芯片。该装置具有实现上述第一方面、或者第二方面中任一实施例的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第四方面，提供了一种装置，包括：处理器和存储器；该存储器用于存储计算机执行指令，当该装置运行时，该处理器执行该存储器存储的该计算机执行指令，以使该装置执行如上述第一方面或第一方面中任一所述的数据传输方法、或者以使该装置执行如上述第二方面或第二方面中任一所述的数据传输方法。
第五方面，本申请提供一种数据传输系统。包括：会话管理网元，用于向用户面网元发送第一策略信息，该第一策略信息包括QFI和第二指示信息，该QFI用于标识服务质量QoS流，该第二指示信息用于指示该QFI标识的该QoS流对应的业务为应用APP业务；用户面网元，用于接收来自终端的所述APP的业务流的上行数据包，该上行数据包包括该QFI和第一指示信息，该第一指示信息用于指示该用户面网元对所述APP的业务流使用反射QoS功能；根据所述第一指示信息，将该APP的业务流的第一下行数据包映射至所述QoS流，得到第二下行数据包，该第二下行数据包包括该QFI；向该终端发送该第二下行数据包。
第六方面，本申请提供了另一种数据传输系统。包括，第一方面以及第一方面任一的用户面网元和第二方面以及第二方面任一的终端。
第七方面，本申请还提供一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机执行上述第一方面所述的方法；或，执行上述第二方面所述的方法。
第八方面，本申请还提供一种包括指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述第一方面所述的方法；或，执行上述第二方面所述的方法。
本申请的这些方面或其他方面在以下实施例的描述中会更加简明易懂。
附图说明
图1(a)为本申请提供的一种可能的系统示意图；
图1(b)为本申请提供的又一种可能的系统示意图；
图2为本申请提供的又一种可能的系统示意图；
图3为本申请提供的一种数据传输方法流程图；
图4为本申请提供的一种QoS策略的分配方法流程图；
图5为本申请提供的一种装置示意图；
图6为本申请提供的又一种装置示意图。
具体实施方式
为了使本申请的目的、技术方案和优点更加清楚，下面将结合附图对本申请作进一步地详细描述。方法实施例中的具体操作方法也可以应用于装置实施例或系统实施例中。其中，在本申请的描述中，除非另有说明，“多个”的含义是两个或两个以上。
如图1(a)所示，为本申请适用的一种可能的系统示意图。该系统包括用户面网元。进一步地，该系统还可以包括会话管理网元。进一步地，该系统还可以包括策略控制网元。进一步地，该系统还可以包括接入设备。进一步地，该系统还可以包括移动性管理网元。
本申请中，图1(a)所示的系统中的网元可以实现以下功能：
用户面网元，用于接收来自终端的所述APP的业务流的上行数据包，所述上行数据包包括所述QFI和第一指示信息，所述第一指示信息用于指示所述用户面网元对所述APP的业务流使用反射QoS功能；根据所述第一指示信息，将所述APP的业务流的第一下行数据包映射至所述QoS流得到第二下行数据包，所述第二下行数据包包括所述QFI；向终端发送所述第二下行数据包。
在一种可能的实现方式中，会话管理网元，用于向用户面网元发送第一策略信息，所述第一策略信息包括QFI和第二指示信息，所述QFI用于标识QoS流，所述第二指示信息用于指示所述QFI标识的所述QoS流对应的业务为APP业务。
在一种可能的实现方式中，所述用户面网元根据所述第一指示信息，将所述APP的业务流的第一下行数据包映射至所述QoS流，得到第二下行数据包，具体包括：根据所述上行数据包的第一包过滤器，确定第二包过滤器，其中所述第一包过滤器的源地址与所述第二包过滤器的目的地址相同，所述第一包过滤器的目的地址与所述第二包过滤器的源地址相同，所述第一包过滤器的源端口号与所述第二包过滤器的目的端口号相同，所述第一包过滤器的目的端口号与所述第二包过滤器的源端口号相同；所述用户面网元根据所述第二包过滤器，将所述APP的业务流的所述第一下行数据包映射至所述QoS流，得到第二下行数据包。
在一种可能的实现方式中，所述会话管理网元，还用于向所述终端发送第二策略信息，所述第二策略信息包括所述QFI、所述APP的信息和所述第一指示信息。
在一种可能的实现方式中，所述会话管理网元，还用于向接入设备发送第三策略信息，所述第三策略信息包括所述QFI和第三指示信息，所述第三指示信息用于所述接入设备允许所述APP的上行业务流携带所述第一指示信息。
在一种可能的实现方式中，所述会话管理网元，还用于接收来自策略控制网元的QoS策略信息，所述QoS策略信息包括第四指示信息和所述APP的信息，所述第四指示信息用于指示对所述APP的业务流使用反射QoS功能；根据所述QoS策略信息，生成所述第一策略信息。
在一种可能的实现方式中，所述策略控制网元用于：接收来自所述会话管理网元的请求消息，所述请求消息用于请求获取所述终端的策略信息；从数据管理网元获取所述终端的签约数据，所述签约数据包括所述终端的APP的信息；根据所述签约数据生成所述QoS策略信息；向所述会话管理网元发送所述QoS策略信息。
在一种可能的实现方式中，所述接入设备，用于接收来自所述会话管理网元的所述第三策略信息。
在一种可能的实现方式中，所述接入设备，还用于接收来自所述终端的所述APP的业务流的上行数据包；根据第三指示信息，将所述上行数据包发送至所述用户面网元。
如图1(b)所示，为本申请提供的又一系统示意图。该系统包括终端和会话管理网元。
本申请中，图1(b)所示的系统中的网元可以实现以下功能：
会话管理网元，用于向终端发送第二策略信息，所述第二策略信息包括QFI、APP的信息和第一指示信息，所述QFI用于标识所述QoS流，所述第一指示信息用于指示用户面网元对所述APP的业务流使用反射QoS功能。
终端，用于根据APP的信息，将终端的APP上产生的业务流的第一上行数据包映射至QoS流得到第二上行数据包，所述第二上行数据包包括QFI和第一指示信息；以及向用户面网元发送所述第二上行数据包。
如图2所示，为本申请提供的又一系统示意图。该系统为第5代(5th generation，5G)架构图，该系统可以作为图1(a)或图1(b)所示的系统的一种具体实现。该5G架构包括终端、无线接入网(radio access network，RAN)设备、用户面功能(user plane function，UPF)网元、会话管理功能(session management function，SMF)、策略控制功能(policy control function，PCF)网元、接入与移动性管理功能(access and mobility management function，AMF)网元、统一数据仓库(Unified Data Repository，UDR)、网络开放功能(Network Exposure Function，NEF)网元等。其中，终端与AMF网元之间的接口为N1接口，AMF网元与RAN设备之间的接口为N2接口，RAN设备与UPF网元之间的接口为N3接口，SMF网元与UPF网元之间的接口为N4接口，SMF网元与PCF网元之间的接口为N7接口，AMF网元与SMF网元之间的接口为N11接口，AMF网元与PCF网元之间的接口为N15接口。
当然，随着通信制式的演变，上述网元的名称可能会发生改变，各个网元之间的接口名称也可能会发生改变。
本申请的用户面网元，在5G通信中，可以是图2所示的UPF网元，主要负责对用户报文进行处理，如转发、计费、合法监听等。在未来通信如第6代(6th generation，6G)通信中，用户面网元仍可以是UPF网元，或有其它的名称，本申请不做限定。
本申请的会话管理网元，在5G通信中，可以是图2所示的SMF网元，主要用于移动网络中的会话管理，如会话建立、修改、释放。具体功能包括终端分配互联网协议(internet protocol，IP)地址、选择提供报文转发功能的用户面网元等。在未来通信如6G通信中，会话管理网元仍可以是SMF网元，或有其它的名称，本申请不做限定。
本申请的策略控制网元，在5G通信中，可以是图2所示的PCF网元，其包含用户签约数据管理功能，策略控制功能，计费策略控制功能，服务质量(quality of service，QoS)控制等。在未来通信如6G通信中，策略控制网元仍可以是PCF网元，或有其它的名称，本申请不做限定。
本申请的移动性管理网元，在5G通信中，可以是图2所示的AMF网元，主要用于移动网络中的终端的附着、移动性管理、跟踪区更新流程，移动性管理网元终结了非接入层(nonaccess stratum，NAS)消息、完成注册管理、连接管理以及可达性管理、分配跟踪区域列表(track area list，TA list)以及移动性管理等，并且透明路由会话管理(session management，SM)消息到会话管理网元。在未来通信如6G通信中，移动性管理网元仍可以是AMF网元，或者有其它名称，本申请对此不作限定。
本申请的接入设备，在5G通信中，可以是图2所示的RAN设备，是一种为终端提供无线通信功能的设备。接入设备例如包括但不限于：5G中的下一代基站(g nodeB，gNB)、演进型节点B(evolved node B，eNB)、无线网络控制器(radio network controller，RNC)、节点B(node B，NB)、基站控制器(base station controller，BSC)、基站收发台(base transceiver station，BTS)、家庭基站(例如，home evolved nodeB，或home node B，HNB)、基带单元 (baseBand unit，BBU)、传输点(transmitting and receiving point，TRP)、发射点(transmitting point，TP)、移动交换中心等。
本申请的终端是一种具有无线收发功能的设备，可以部署在陆地上，包括室内或室外、手持或车载；也可以部署在水面上(如轮船等)；还可以部署在空中(例如飞机、气球和卫星上等)。所述终端可以是手机(mobile phone)、平板电脑(pad)、带无线收发功能的电脑、虚拟现实(virtual reality，VR)终端、增强现实(augmented reality，AR)终端、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程医疗(remote medical)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端等。
由于基于APP业务的一些业务流可能使用协议类型或URL等L7内容描述，因此，若采用如背景技术所述的业务流的传输方法，则可能存在业务识别不及时、不准确的问题。具体地，UPF需深入读取网络之间互连的协议(Internet Protocol，IP)包载荷的内容来对七层协议中的应用层信息进行重组分析，有时可能还需分析多个报文后才能识别出业务流，导致业务识别不及时，无法及时提供QoS保障。并且，APP中可能存在链入的第三方业务，这些第三方业务的数据流虽然在终端上的APP中产生消耗，但用户面网元难以区分这些数据流属于APP的业务流量还是第三方业务的流量，导致用户面网元无法准确识别业务。进一步地，由于越来越多的服务商通过应用层加密协议传输数据以保证数据的安全性，因此，对于APP中加密的业务流，用户面网元难以获取IP包载荷的内容中的URL等信息，导致无法准确识别业务。
本申请提供的数据传输方法，可用于解决以上问题。如图3所示，为本申请提供的一种数据传输方法流程图。该方法包括上行方向的数据传输和下行方向的数据传输。APP的数据流，均为上行方向先发生。即由终端先发起APP的上行数据流的传输，然后UPF再发起该APP的下行数据流的传输。下面分别说明。
在上行方向，该方法包括：
步骤301，终端根据APP的信息，将终端的APP上产生的业务流的第一上行数据包映射至QoS流，得到第二上行数据包。
其中，第二上行数据包包括QFI和第一指示信息，该QFI用于标识QoS流，该第一指示信息用于指示UPF对APP的业务流使用反射QoS功能。作为一种具体的实现方式，该第一指示信息例如可以是反射QoS指示(Reflective QoS Indication，RQI)。
例如，当用户使用APP时，可以点击APP，例如可以在APP上访问视频、图片、文字等应用。终端在检测到用户发起的应用后，终端可以将APP上产生的业务流发送至UPF，由UPF处理该业务流，例如对该业务流进行计费、带宽控制等。终端获取该APP的信息，该APP的信息例如可以是APP的标识，或者还可以是APP的标识和OS标识，该APP的信息用于标识APP。然后，终端根据预先存储的APP的信息与QFI的对应关系，确定该APP的业务流将要映射的QoS流的QFI。
作为一种实现方式，APP的信息与QFI的对应关系可以是作为终端的策略信息(本申请中，终端的策略信息还可以称为第二策略信息)的一部分。该第二策略信息包括APP的信息与QFI的对应关系，进一步的还可以包括第一指示信息，进一步的还可以包括该第二策略信息的优先级信息等。该第二策略信息可以是由SMF发送给终端的。在具体实现中，该第二策略信息可以是SMF以QoS rule的形式发送给终端的，QoS rule用于指示终端对上行业务流 进行识别，以及指示将上行业务流映射到QoS流。当然，QoS rule中还可以包括其它信息，本申请不作限定。
下面以表格的形式为例，对终端的第二策略信息进行具体说明。如表1，为第二策略信息一种示例。其中，APP的信息包括APP的标识。
表1
Figure PCTCN2019092142-appb-000001
如表1所示，当用户点击终端的APP5，需要通过APP5发起业务时，则终端可以获取到APP5的信息，即APP id5，然后根据终端的第二策略信息，确定APP id5对应的QFI。例如，若第二策略信息中不包括优先级信息，则可以根据存储的顺序逐一匹配QoS rule，直到匹配到APP id5对应的QFI，或者全部匹配完之后失败。若第二策略信息中还包括优先级信息，则可以根据优先级，从优先级高的QoS rule开始匹配，直到匹配到APP id5对应的QFI，或者全部匹配完之后失败。在表1中，APP id5在QoS rule中匹配成功，确定APP id5对应的QFI3。因此，APP5的业务流的数据包将会映射至QFI3对应的QoS流。如表2，为策略信息又一种示例。其中，APP的信息包括APP的标识和OS的标识。
表2
Figure PCTCN2019092142-appb-000002
表2与表1的区别在于，表2中的APP的信息包括APP的标识和OS的标识。一般地，一个QoS rule对应的APP的信息包括的OS是相同的，比如QoS rule1对应的APP的信息包括OS1，QoS rule2对应的APP的信息包括OS1，QoS rule3对应的APP的信息包括OS2等。当然，一个QoS rule对应的APP的信息包括的OS也可以不相同。比如QoS rule1对应的APP的信息包括(OS1、APP id1)、(OS2、APP id2)、(OS2、APP id3)等。
当用户点击终端的APP5，需要通过APP5发起业务时，则终端可以获取到APP5的信息，即APP id5或(OS2、APP id5)，然后根据终端的第二策略信息，确定APP5的信息对应的QFI。例如，若第二策略信息中不包括优先级信息，则可以根据存储的顺序逐一匹配QoS rule，直到匹配到APP5的信息对应的QFI，或者全部匹配完之后失败。若第二策略信息中还包括优先级信息，则可以根据优先级，从优先级高的QoS rule开始匹配，直到匹配到APP5的信息对 应的QFI，或者全部匹配完之后失败。在表1或表2中，APP5的信息在QoS rule中匹配成功，确定APP5的信息对应的QFI3。因此，APP5的业务流的上行数据包将会映射至QFI3对应的QoS流。
需要说明的是，在实际应用中，若不同的QoS rule中的APP的信息可以重复，则QoS rule中需要携带优先级信息。以表1为例，比如，在表1中还包括QoS rule5，该QoS rule5包括的QFI、APP的信息、优先级信息和指示信息分别为：QFI5，APP id2，5，第一指示信息。当用户点击终端的APP2，需要通过APP2发起业务时，则终端根据QoS rule1，确定APP id2对应的QFI为QFI1。该示例中，虽然QoS rule5中也包括APP id2，但由于QoS rule5的优先级低于QoS rule1的优先级，因此终端会根据QoS rule1匹配到QFI1。
若不同的QoS rule中的APP的信息不可以重复，则QoS rule中可以携带优先级信息，也可以不携带优先级信息。
针对终端的APP上产生的业务流，是以数据包的形式发送的。比如针对其中的任一上行数据包，该任一上行数据包可以称为第一上行数据包，将该第一上行数据包映射至QFI对应的QoS流，得到第二上行数据包，其中，第二上行数据包包括QFI和第一指示信息，该第一指示信息用于指示UPF对APP的业务流使用反射QoS功能。
步骤302，终端向UPF发送该第二上行数据包。相应地，UPF可以接收到第三上行数据包。
例如，终端可以将第二上行数据包通过该QoS流对应的DRB发送至RAN设备，RAN设备根据该第二上行数据包，对该第二上行数据包的封装头进行更新，得到第三上行数据包，并将第三上行数据包发送至UPF。该第三上行数据包包括QFI和第一指示信息。
在一种实现方式中，终端可以将该第二上行数据包通过该QoS流对应的DRB发送至RAN设备，RAN设备根据本地存储的策略信息(该策略信息可以称为第三策略信息)进行第二上行数据包的调度和QoS保障，得到第三上行数据包并将该第三上行数据包发送至UPF。例如，RAN设备的第三策略信息可以是由SMF发送给RAN设备的，该第三策略信息包括QFI和第三指示信息，该第三指示信息用于指示RAN设备允许APP的上行业务流携带第一指示信息。在一种具体的实现中，第三策略信息可以包括QFI和QoS profile等信息，QoS profile可以包括第三指示信息。作为一种实现方式，该第三指示信息例如可以是反射QoS属性(Reflective QoS Attribute，RQA)。可选的，QoS profile还可以包括5QI(5G QoS Identifier)、分配保留优先级(allocation and retention priority，ARP)等，对于保证比特率(Guaranteed Bit Rate，GBR)QoS流，QoS profile还可以包括保证流比特率(Guaranteed Flow Bit Rate，GFBR)、最大流比特率(Maximum Flow Bit Rate，MFBR)等。进一步地，RAN设备还可以根据第三策略信息为第三策略信息中的QFI分流无线资源和信道，建立该QFI对应的DRB。其中，一个DRB可以对应一个或多个QFI。
作为一种具体的实现方式，APP产生的第一上行数据包为实际应用数据，第二上行数据包包括第一上行数据包、QFI和第一指示信息，其中，QFI和第一指示信息携带在第二上行数据包的封装头中。RAN设备进行无线侧数据和核心网侧数据间的转发，由于RAN设备和终端间的接口(比如Uu接口)与RAN设备和UPF间接口(比如N3接口)不同，因此，RAN设备需要对第二上行数据包的封装头中的QFI等数据重新封装，得到第三上行数据包。具体的，RAN设备查看第二上行数据包的封装头，如果发现第二上行数据包的封装头只有QFI，没有第一指示信息，则RAN设备对第二上行数据包的封装头进行封装得到新的封装头，该第三上行数据包包括新的封装头和第一上行数据包，该新的封装头中包括QFI。如果发现第二上行数 据包的封装头有QFI，并且有第一指示信息，则RAN设备需要确定之前收到的第三策略信息中是否有第三指示信息，若第三策略信息中有第三指示信息，则RAN设备对第二上行数据包的封装头进行封装得到新的封装头，第三上行数据包包括该新的封装头和第一上行数据包，该新的封装头中包括QFI和第一指示信息；若第三策略信息中没有第三指示信息，则RAN设备对第二上行数据包的封装头进行封装得到新的封装头，第三上行数据包包括该新的封装头和第一上行数据包，该新的封装头中包括QFI。然后RAN设备将第三上行数据包发送至UPF。其中，第二上行数据包的封装头与第三上行数据包的新的封装头的格式和/或使用的协议不同。
UPF在接收到第三上行数据包后，根据第三上行数据包中的QFI对应的第一策略信息，进行相应的计费、带宽等控制。
通过上述步骤301和步骤302，实现了在上行方向，将APP的业务流的上行数据包发送至UPF。并且，终端在将APP的业务流的上行数据包映射至QoS流时，不需要对APP的业务流的上行数据包进行识别，比如不需要通过识别上行数据包的五元组信息以确定该上行数据包对应的QFI，而是根据产生该业务流的APP的信息，确定该业务流的上行数据包所对应的QFI，因而可以实现对业务流的上行数据包的快速和准确识别，并映射至相应的QoS流。并且即使对该业务流进行加密，但由于UPF是以APP的粒度则UPF在接收到该业务流的上行数据包时，只需要通过上行数据包中的QFI即可识别出该上行数据包所对应的APP，从而完成对该业务流执行计费、带宽控制等操作。
可选的，作为一种实现方式，在下行方向，该方法包括：
步骤303，UPF根据第一指示信息，将APP的业务流的第一下行数据包映射至QoS流，得到第二下行数据包。
UPF在接收到终端发送的业务流的上行数据包，比如接收到上述第二上行数据包之后，该第二上行数据包包括第一指示信息和QFI，因此UPF可以获取到该第二上行数据包的第一指示信息和QFI。UPF根据该第一指示信息，可以确定该APP的业务流的下行数据包可以通过该第二上行数据包对应QoS流发送给终端，即该APP的业务流的上行数据包和该APP的业务流的下行数据包是通过同一个QoS流传输的。
因此，若在下行方向，APP服务器产生了业务流，则将该业务流的下行数据包，比如第一下行数据包映射至上述QoS流得到第二下行数据包，该第二下行数据包包括QFI，该QFI用于标识上述QoS流。
作为一种实现方式，UPF可以通过以下方法，将APP的业务流的第一下行数据包映射至QoS流，得到第二下行数据包：UPF在接收到APP的业务流的上行数据包，如上述第二上行数据包后，获取该第二上行数据包的QFI和第一指示信息，进一步的还获取该第二上行数据包第一包过滤器(packet filter),该第一包过滤器包括五元组信息：源地址、源端口号、目的地址、目的端口号和协议类型。UPF根据该第一包过滤器确定第二包过滤器，该第二包过滤器也包括五元组信息：源地址、源端口号、目的地址、目的端口号和协议类型。并且，第二包过滤器的源地址与第一包过滤器的目的地址相同，第二包过滤器的目的地址与第一包过滤器的源地址相同，第二包过滤器的源端口号与第一包过滤器的目的端口号相同，第二包过滤器的目的端口号与第一包过滤器的源端口号相同，以及第二包过滤器的协议类型与第一包过滤器的协议类型号相同。例如，若第二上行数据包的第一包过滤器包括的五元组信息为(源地址：IP1、源端口号：port1、目的地址：IP2、目的端口号：port2、协议类型：p1)，则UPF确定的第二包过滤器包括的五元组信息为(源地址：IP2、源端口号：port2、目的地址： IP1、目的端口号：port1、协议类型：p1)。然后，UPF可以记录QFI与第二包过滤器的五元组信息之间的对应关系。后续，当UPF接收到该APP的业务流的下行数据包，如上述第一下行数据包时，则可以根据该第二包过滤器，对该第一下行数据包进行识别，若确定第一下行数据包中的五元组信息与第二包过滤器的五元组信息匹配，则将该第一下行数据包映射至该第二包过滤器对应的QFI所标识的QoS流，即在第一下行数据包中添加该QFI，得到第二下行数据包。
作为一种实现方式，在上述步骤303之前，UPF还可以从SMF接收策略信息，该策略信息可以称为第一策略信息，该第一策略信息包括QFI和第二指示信息，该第二指示信息用于指示QFI标识的QoS流对应的业务为APP业务，该QFI与SMF发送给终端的第二策略信息中的QFI相同。即通过该第一策略信息，使得UPF获知该QFI标识的QoS流对应的业务为APP业务。
作为一种具体实现方式，该第一策略信息可以包括PDR，该PDR包括QFI和第二指示信息，进一步的，该PDR中还可以包括QoS执行规则(QoS Enforcement Rule，QER)，该PDR用于指示用于做数据包的检测。该QER中可以包括Qos策略的参数，带宽等参数。UPF接收到PDR后安装规则，并进行QFI资源管理。
步骤304，UPF向终端发送第二下行数据包。相应地，该终端可以接收到第三下行数据包。
一方面，UPF向终端发送第二下行数据包，另一方面，UPF还根据QFI对应的第一策略信息对下行业务流进行计费、带宽等控制。
在一种实现方式中，第二下行数据包包括封装头和第一下行数据包，该封装头包括QFI。UPF可以将该第二下行数据包通过N3接口发送至RAN设备，RAN设备对第二下行数据包的封装头中的QFI等数据重新封装，得到新的封装头，然后RAN设备向终端发送第三下行数据包，该第三下行数据包包括该新的封装头和第一下行数据包，该新的封装头包括QFI。其中，第二下行数据包的封装头与第三下行数据包的新的封装头的格式和/或使用的协议不同。
通过上述步骤303-步骤304，UPF可以将APP的业务流的下行数据包通过该APP的业务流的上行数据包所对应的QoS流发送至终端。一方面，UPF不需要对该业务流的下行数据包进行深度识别，而只需要确定该下行数据包对应QFI，且该QFI也是上行数据包对应的QFI，因而UPF可以快速及准确地将APP的业务流的下行数据包映射至QoS流。进一步的，若APP服务器对APP的业务流进行加密，由于UPF不需要对该APP的业务流的下行数据包进行深度识别，因而虽然该业务流加密了，但不影响UPF将该业务流的下行数据包映射至QoS流，从而实现了对加密的业务流的准确及快速处理。进一步的，对于链入APP的第三方业务流流量也可以准确识别为该APP的流量，比如对于通过微信内的链接打开的京东应用，即在微信内的页面访问京东，可以准确识别为微信的流量，实现了对APP的流量的准确识别与控制处理。
作为一种实现方式，下面介绍一种QoS策略分配方法，通过该方法可以向图3所示的实施例中的终端、UPF分配策略信息，进一步的还可以向RAN设备分配策略信息。如图4所示，为本申请提供的QoS策略分配方法。该方法包括以下步骤：
步骤401，终端向SMF发送会话建立请求消息。相应地，SMF可以接收到该会话建立请求消息。
该会话建立请求消息用于请求建立会话。
需要说明的是，该会话建立请求消息也可以有其他名称，例如称为会话建立消息、请求 消息、建立请求消息、第一消息等等。
步骤402，SMF向PCF发送请求消息。相应地，PCF可以接收到该请求消息。
该请求消息用于请求获取终端的策略信息。
步骤403，PCF从数据管理网元获取终端的签约数据。
该数据管理网元例如可以是如图2所示的UDR。
PCF从数据管理网元获取的终端的签约数据包括该终端的APP的信息，该APP的信息包括APP的标识，或者该APP的信息包括APP的标识和OS的标识。
步骤404，PCF根据签约数据生成QoS策略信息。
PCF生成的QoS策略信息包括第四指示信息和APP的信息，该第四指示信息用于指示对APP的业务流使用反射QoS功能。
作为一种实现方式，该第四指示信息可以是一个反射(Reflective)QoS指示。
需要说明的是，上述步骤401-步骤404为可选步骤，即触发PCF向SMF发送QoS策略信息(即以下步骤405)的原因可以是基于终端的会话建立请求消息和SMF的请求消息(即上述步骤401-步骤404)，也可以是其他原因。比如，当终端已经建立了PDU会话后，当该终端签约了一个适用于该PDU会话的业务策略时，则PCF可以主动执行上述步骤403-步骤404，即不执行上述步骤401-步骤402，而只执行上述步骤403-步骤404。再比如，当该终端已经建立了一个PDU会话后，应用服务器通过NEF网元向PCF请求业务的QoS保障时，则PCF可以从NEF网元接收到QoS参数，并根据QoS参数生成QoS策略信息，即不执行上述步骤401-步骤404，其中，该终端正在使用该应用服务器的服务。
步骤405，PCF向SMF发送QoS策略信息。相应地，SMF可以接收到该QoS策略信息。
步骤406，SMF根据QoS策略信息，生成第一策略信息、第二策略信息和第三策略信息。
SMF根据策略信息，生成QFI，QFI用于标识QoS流。该QFI与该APP的信息对应。本申请中，一个QFI可以与一个APP的信息一一对应，也可以与多个APP的信息对应。并且该QFI只能被分配用于标识APP的业务流对应的QoS流，可以理解为该用于该QFI不会被用于标识非APP的业务流对应的QoS流。
SMF生成的第一策略信息包括上述QFI和第二指示信息，第二指示信息用于指示QFI标识的QoS流对应的业务为应用APP业务。
SMF生成的第二策略信息包括上述QFI、APP的信息和第一指示信息。第一指示信息用于指示UPF对APP的业务流使用反射QoS功能。
SMF生成的第三策略信息包括上述QFI和第三指示信息，第三指示信息用于RAN设备允许APP的上行业务流携带第一指示信息。
其中，第一指示信息和第三指示信息的生成均与第四指示信息有关。
步骤407，SMF向RAN设备发送第三策略信息。相应地，RAN设备可以接收到该第三策略信息。
步骤408，SMF向UPF发送第一策略信息。相应地，UPF可以接收到该第一策略信息。
步骤409，SMF向终端发送第二策略信息。相应地，终端可以接收到该第二策略信息。
上述步骤407、步骤408、步骤409之间没有严格的执行顺序，可根据实际需要设定。
通过上述方法，可实现由SMF根据从PCF接收到的QoS策略信息生成第一策略信息、第二策略信息和第三策略信息，并分别发送给UFP、终端和RAN设备，使得UPF、终端和RAN设备分别根据第一策略信息、第二策略信息和第三策略信息处理上行数据包和下行数据包。并 且，可以实现终端和UPF对上行数据包和下行数据包的快速准确的识别，对于加密的数据流的数据包，无需深度识别即可快速准确识别其对应的QoS流，因而可以提升数据传输的效率。
需要说明的是，本申请上述各实施例中所使用的策略信息的名称并不限定，对于与某个策略信息具有相同功能的其他名称的策略信息，也可以认为是与该策略信息是实质上相同的消息。作为示例，上述各实施例中的第一策略信息也可以称为第一策略、或策略信息等，上述各实施例中的第二策略信息也可以称为第二策略、或策略信息等，上述各实施例中的第三策略信息也可以称为第三策略、或策略信息等。
上述主要从各个网元之间交互的角度对本申请提供的方案进行了介绍。可以理解的是，上述实现各网元为了实现上述功能，其包括了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本发明能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本发明的范围。
基于相同的发明构思，如图5所示，为本申请提供的一种装置示意图，该装置可以是终端、或用户面网元、或芯片，可执行上述任一实施例中由终端、或用户面网元执行的方法。
该装置500包括至少一个处理器501，通信线路502，存储器503以及至少一个通信接口504。
处理器501可以是一个通用中央处理器(central processing unit，CPU)，微处理器，特定应用集成电路(application specific integrated circuit，ASIC)，或一个或多个用于控制本申请方案程序执行的集成电路。
通信线路502可包括一通路，在上述组件之间传送信息。
通信接口504，使用任何收发器一类的装置，用于与其他设备或通信网络通信，如以太网，无线接入网(radio access network，RAN)，无线局域网(wireless local area networks，WLAN)，有线接入网等。
存储器503可以是只读存储器(read-only memory，ROM)或可存储静态信息和指令的其他类型的静态存储设备，随机存取存储器(random access memory，RAM)或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器(electrically er服务器able programmable read-only memory，EEPROM)、只读光盘(compact disc read-only memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器可以是独立存在，通过通信线路502与处理器相连接。存储器也可以和处理器集成在一起。
其中，存储器503用于存储执行本申请方案的计算机执行指令，并由处理器501来控制执行。处理器501用于执行存储器503中存储的计算机执行指令，从而实现本申请上述实施例提供的数据传输方法和策略分配方法。
可选的，本申请实施例中的计算机执行指令也可以称之为应用程序代码，本申请实施例对此不作具体限定。
在具体实现中，作为一种实施例，处理器501可以包括一个或多个CPU，例如图5中的 CPU0和CPU1。
在具体实现中，作为一种实施例，装置500可以包括多个处理器，例如图5中的处理器501和处理器508。这些处理器中的每一个可以是一个单核(single-CPU)处理器，也可以是一个多核(multi-CPU)处理器。这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。
当图5所示的装置为芯片时，例如可以是终端的芯片、或用户面网元的芯片，则该芯片包括处理器501(还可以包括处理器508)、通信线路502、存储器503和通信接口504。具体地，通信接口504可以是输入接口、管脚或电路等。存储器503可以是寄存器、缓存等。处理器501和处理器508可以是一个通用的CPU，微处理器，ASIC，或一个或多个用于控制上述任一实施例的数据传输方法和/或策略分配方法的程序执行的集成电路。
本申请可以根据上述方法示例对装置进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。比如，在采用对应各个功能划分各个功能模块的情况下，图6示出了一种装置示意图，该装置600可以是上述实施例中所涉及的用户面网元、或者为终端、或者为用户面网元中的芯片、或者为终端中的芯片，该装置600包括接收单元601、发送单元602和处理单元603。
在一种实现方式中：
若该装置是用户面网元或用户面网元的芯片，则该装置600可实现以下操作：接收单元，用于接收来自终端的应用APP的业务流的上行数据包，上行数据包包括QFI和第一指示信息，QFI用于标识QoS流，第一指示信息用于指示用户面网元对APP的业务流使用反射QoS功能；处理单元，用于根据第一指示信息，将APP的业务流的第一下行数据包映射至QoS流，得到第二下行数据包，所述第二下行数据包包括所述QFI；发送单元，用于向终端发送下行数据包。
可选的，接收单元，还用于接收来自会话管理网元的第一策略信息，第一策略信息包括QFI和第二指示信息，第二指示信息用于指示QFI标识的QoS流对应的业务为APP业务。
可选的，处理单元，具体用于：根据上行数据包的第一包过滤器，确定第二包过滤器，其中第二包过滤器的源地址与第一包过滤器的目的地址相同，第二包过滤器的目的地址与第一包过滤器的源地址相同，第二包过滤器的源端口号与第一包过滤器的目的端口号相同，第二包过滤器的目的端口号与第一包过滤器的源端口号相同；根据第二包过滤器，将APP的业务流的第一下行数据包映射至QoS流，得到第二下行数据包。
在又一种实现方式中：
若该装置是终端或终端的芯片，则该装置600可实现以下操作：处理单元，用于根据应用APP的信息，将终端的APP上产生的业务流的第一上行数据包映射至QoS流，得到第二上行数据包，第二上行数据包包括QFI和第一指示信息，QFI用于标识QoS流，第一指示信息用于指示用户面网元对APP的业务流使用反射QoS功能；发送单元，用于向用户面网元发送第二上行数据包。
可选的，接收单元，用于接收来自会话管理网元的第二策略信息，第二策略信息包括QFI、APP的信息和第一指示信息。
应理解，该装置600可以用于实现本发明实施例的方法中由终端或用户面网元执行的步骤，相关特征可以参照上文，此处不再赘述。
若该装置是用户面网元，则用户面网元以采用集成的方式划分各个功能模块的形式来呈现。这里的“模块”可以指特定ASIC，电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。在一个简单的实施例中，本领域的技术人员可以想到该用户面网元可以采用图6所示的形式。
比如，图5中的处理器501可以通过调用存储器503中存储的计算机执行指令，使得用户面网元执行上述方法实施例中的方法。
若该装置是终端，则终端以采用集成的方式划分各个功能模块的形式来呈现。在一个简单的实施例中，本领域的技术人员可以想到该终端可以采用图6所示的形式。
比如，图5中的处理器501可以通过调用存储器503中存储的计算机执行指令，使得终端执行上述方法实施例中的方法。
具体的，图6中的接收单元601、处理单元603、以及发送单元602的功能/实现过程可以通过图5中的处理器501调用存储器503中存储的计算机执行指令来实现。或者，图6中的处理单元603的功能/实现过程可以通过图5中的处理器501调用存储器503中存储的计算机执行指令来实现，图6中的接收单元601和发送单元602的功能/实现过程可以通过图5中的通信接口504来实现。
可选的，当该装置600是芯片或电路时，则接收单元601和发送单元602的功能/实现过程还可以通过管脚或电路等来实现。可选地，当该装置600是芯片时，存储器603可以为芯片内的存储单元，如寄存器、缓存等。
当然，当该装置600是用户面网元或终端时，存储器603可以是用户面网元或终端内的位于芯片外部的存储单元，本申请实施例对此不作具体限定。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本发明实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘(Solid State Disk，SSD))等。
本申请实施例中所描述的各种说明性的逻辑单元和电路可以通过通用处理器，数字信号处理器，专用集成电路(ASIC)，现场可编程门阵列(FPGA)或其它可编程逻辑装置，离散门或晶体管逻辑，离散硬件部件，或上述任何组合的设计来实现或操作所描述的功能。通用处理器可以为微处理器，可选地，该通用处理器也可以为任何传统的处理器、控制器、微控制器或状态机。处理器也可以通过计算装置的组合来实现，例如数字信号处理器和微处理器， 多个微处理器，一个或多个微处理器联合一个数字信号处理器核，或任何其它类似的配置来实现。
本申请实施例中所描述的方法或算法的步骤可以直接嵌入硬件、处理器执行的软件单元、或者这两者的结合。软件单元可以存储于RAM存储器、闪存、ROM存储器、EPROM存储器、EEPROM存储器、寄存器、硬盘、可移动磁盘、CD-ROM或本领域中其它任意形式的存储媒介中。示例性地，存储媒介可以与处理器连接，以使得处理器可以从存储媒介中读取信息，并可以向存储媒介存写信息。可选地，存储媒介还可以集成到处理器中。处理器和存储媒介可以设置于ASIC中，ASIC可以设置于终端设备中。可选地，处理器和存储媒介也可以设置于终端设备中的不同的部件中。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
尽管结合具体特征及其实施例对本发明进行了描述，显而易见的，在不脱离本发明的精神和范围的情况下，可对其进行各种修改和组合。相应地，本说明书和附图仅仅是所附权利要求所界定的本发明的示例性说明，且视为已覆盖本发明范围内的任意和所有修改、变化、组合或等同物。显然，本领域的技术人员可以对本发明进行各种改动和变型而不脱离本发明的精神和范围。这样，倘若本发明的这些修改和变型属于本发明权利要求及其等同技术的范围之内，则本发明也意图包含这些改动和变型在内。

Claims (27)

  1. 一种数据传输方法，其特征在于，包括：
    用户面网元接收来自终端的应用APP的业务流的上行数据包，所述上行数据包包括服务质量流标识QFI和第一指示信息，所述QFI用于标识服务质量QoS流，所述第一指示信息用于指示所述用户面网元对所述APP的业务流使用反射QoS功能；
    所述用户面网元根据所述第一指示信息，将所述APP的业务流的第一下行数据包映射至所述QoS流，得到第二下行数据包，所述第二下行数据包包括所述QFI；
    所述用户面网元向所述终端发送所述第二下行数据包。
  2. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    所述用户面网元接收来自会话管理网元的第一策略信息，所述第一策略信息包括所述QFI和第二指示信息，所述第二指示信息用于指示所述QFI标识的所述QoS流对应的业务为APP业务。
  3. 根据权利要求1或2所述的方法，其特征在于，所述用户面网元将所述APP的业务流的第一下行数据包映射至所述QoS流，得到第二下行数据包，包括：
    所述用户面网元根据所述上行数据包的第一包过滤器，确定第二包过滤器，其中所述第二包过滤器的源地址与所述第一包过滤器的目的地址相同，所述第二包过滤器的目的地址与所述第一包过滤器的源地址相同，所述第二包过滤器的源端口号与所述第一包过滤器的目的端口号相同，所述第二包过滤器的目的端口号与所述第一包过滤器的源端口号相同；
    所述用户面网元根据所述第二包过滤器，将所述APP的业务流的所述第一下行数据包映射至所述QoS流，得到所述第二下行数据包。
  4. 一种数据传输方法，其特征在于，包括：
    终端根据应用APP的信息，将所述终端的所述APP上产生的业务流的第一上行数据包映射至服务质量QoS流，得到第二上行数据包，所述第二上行数据包包括服务质量流标识QFI和第一指示信息，所述QFI用于标识所述QoS流，所述第一指示信息用于指示用户面网元对所述APP的业务流使用反射QoS功能；
    所述终端向所述用户面网元发送所述第二上行数据包。
  5. 根据权利要求4所述的方法，其特征在于，所述方法还包括：
    所述终端接收来自会话管理网元的第二策略信息，所述第二策略信息包括所述QFI、所述APP的信息和所述第一指示信息。
  6. 根据权利要求4或5所述的方法，其特征在于，所述APP的信息包括所述APP的标识；或者，所述APP的信息包括所述APP的标识和所述APP对应的操作系统OS的标识。
  7. 一种装置，其特征在于，包括：
    接收单元，用于接收来自终端的应用APP的业务流的上行数据包，所述上行数据包包括服务质量流标识QFI和第一指示信息，所述QFI用于标识服务质量QoS流，所述第一指示信息用于指示所述用户面网元对所述APP的业务流使用反射QoS功能；
    处理单元，用于根据所述第一指示信息，将所述APP的业务流的第一下行数据包映射至所述QoS流，得到第二下行数据包，所述第二下行数据包包括所述QFI；
    发送单元，用于向所述终端发送所述第二下行数据包。
  8. 根据权利要求7所述的装置，其特征在于，所述接收单元，还用于接收来自会话管理 网元的第一策略信息，所述第一策略信息包括所述QFI和第二指示信息，所述第二指示信息用于指示所述QFI标识的所述QoS流对应的业务为APP业务。
  9. 根据权利要求7或8所述的装置，其特征在于，所述处理单元，具体用于：
    根据所述上行数据包的第一包过滤器，确定第二包过滤器，其中所述第二包过滤器的源地址与所述第一包过滤器的目的地址相同，所述第二包过滤器的目的地址与所述第一包过滤器的源地址相同，所述第二包过滤器的源端口号与所述第一包过滤器的目的端口号相同，所述第二包过滤器的目的端口号与所述第一包过滤器的源端口号相同；
    根据所述第二包过滤器，将所述APP的业务流的所述第一下行数据包映射至所述QoS流，得到所述第二下行数据包。
  10. 一种装置，其特征在于，包括：
    处理单元，用于根据应用APP的信息，将终端的所述APP上产生的业务流的第一上行数据包映射至服务质量QoS流，得到第二上行数据包，所述第二上行数据包包括服务质量流标识QFI和第一指示信息，所述QFI用于标识所述QoS流，所述第一指示信息用于指示用户面网元对所述APP的业务流使用反射QoS功能；
    发送单元，用于向所述用户面网元发送所述第二上行数据包。
  11. 根据权利要求10所述的装置，其特征在于，所述装置还包括接收单元，用于接收来自会话管理网元的第二策略信息，所述第二策略信息包括所述QFI、所述APP的信息和所述第一指示信息。
  12. 一种系统，其特征在于，包括：
    会话管理网元，用于向用户面网元发送第一策略信息，所述第一策略信息包括服务质量流标识QFI和第二指示信息，所述QFI用于标识服务质量QoS流，所述第二指示信息用于指示所述QFI标识的所述QoS流对应的业务为应用APP业务；
    用户面网元，用于接收来自终端的所述APP的业务流的上行数据包，所述上行数据包包括所述QFI和第一指示信息，所述第一指示信息用于指示所述用户面网元对所述APP的业务流使用反射QoS功能；根据所述第一指示信息，将所述APP的业务流的第一下行数据包映射至所述QoS流，得到第二下行数据包，所述第二下行数据包包括所述QFI；向所述终端发送所述第二下行数据包。
  13. 根据权利要求12所述的系统，其特征在于，所述用户面网元根据所述第一指示信息，将所述APP的业务流的第一下行数据包映射至所述QoS流，得到第二下行数据包，具体包括：
    根据所述上行数据包的第一包过滤器，确定第二包过滤器，其中所述第二包过滤器的源地址与所述第一包过滤器的目的地址相同，所述第二包过滤器的目的地址与所述第一包过滤器的源地址相同，所述第二包过滤器的源端口号与所述第一包过滤器的目的端口号相同，所述第二包过滤器的目的端口号与所述第一包过滤器的源端口号相同；
    所述用户面网元根据所述第二包过滤器，将所述APP的业务流的所述第一下行数据包映射至所述QoS流，得到所述第二下行数据包。
  14. 根据权利要求12或13所述的系统，其特征在于，所述会话管理网元，还用于向所述终端发送第二策略信息，所述第二策略信息包括所述QFI、所述APP的信息和所述第一指示信息。
  15. 根据权利要求12-14中任一所述的系统，其特征在于，所述会话管理网元，还用于向接入设备发送第三策略信息，所述第三策略信息包括所述QFI和第三指示信息，所述第三 指示信息用于所述接入设备允许所述APP的上行业务流携带所述第一指示信息。
  16. 根据权利要求12-15中任一所述的系统，其特征在于，所述会话管理网元，还用于接收来自策略控制网元的QoS策略信息，所述QoS策略信息包括第四指示信息和所述APP的信息，所述第四指示信息用于指示对所述APP的业务流使用反射QoS功能；根据所述QoS策略信息，生成所述第一策略信息。
  17. 根据权利要求16所述的系统，其特征在于，所述系统还包括所述策略控制网元，所述策略控制网元用于：
    接收来自所述会话管理网元的请求消息，所述请求消息用于请求获取所述终端的策略信息；
    从数据管理网元获取所述终端的签约数据，所述签约数据包括所述终端的APP的信息；
    根据所述签约数据生成所述QoS策略信息；
    向所述会话管理网元发送所述QoS策略信息。
  18. 根据权利要求15所述的系统，其特征在于，所述系统还包括接入设备，用于接收来自所述终端的所述APP的业务流的上行数据包；根据所述第三指示信息，将所述上行数据包发送至所述用户面网元。
  19. 一种用户面网元，其特征在于，包括：处理器和存储器；所述存储器用于存储计算机执行指令，当所述用户面网元运行时，所述处理器执行所述存储器存储的所述计算机执行指令，以使所述用户面网元执行如权利要求1-3任一项所述的数据传输方法。
  20. 一种通信装置，其特征在于，包括：处理器和存储器；所述存储器用于存储计算机执行指令，当所述通信装置运行时，所述处理器执行所述存储器存储的所述计算机执行指令，以使所述通信装置执行如权利要求4-6任一项所述的数据传输方法。
  21. 一种处理装置，其特征在于，包括：
    存储器，用于存储计算机程序；
    处理器，用于从所述存储器调用并运行所述计算机程序，以执行如权利要求1-3任一项，或权利要求4-6任一项所述的数据传输方法。
  22. 一种处理器，其特征在于，用于执行如权利要求求1-3任一项，或权利要求4-6任一项所述的数据传输方法。
  23. 一种芯片系统，其特征在于，包括：
    存储器，用于存储计算机程序；
    处理器，用于从所述存储器调用并运行所述计算机程序，使得安装有所述芯片系统的设备执行如权利要求求1-3任一项，或权利要求4-6任一项所述的数据传输方法。
  24. 一种计算机可读存储介质，包括计算机程序，当其在计算机上运行时，使得所述计算机执行如权利要求求1-3任一项，或权利要求4-6任一项所述的数据传输方法。
  25. 一种计算机程序产品，所述计算机程序产品包括计算机程序，当所述计算机程序在计算机上运行时，使得计算机执行如权利要求求1-3任一项，或权利要求4-6任一项所述的数据传输方法。
  26. 一种用来执行权利要求1-3任一项所述的数据传输方法的装置。
  27. 一种用来执行权利要求4-6任一项所述的数据传输方法的装置。
PCT/CN2019/092142 2018-07-06 2019-06-20 一种数据传输方法、装置及系统 WO2020007202A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810737409.X 2018-07-06
CN201810737409.XA CN110691370B (zh) 2018-07-06 2018-07-06 一种数据传输方法、装置及系统

Publications (1)

Publication Number Publication Date
WO2020007202A1 true WO2020007202A1 (zh) 2020-01-09

Family

ID=69059829

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/092142 WO2020007202A1 (zh) 2018-07-06 2019-06-20 一种数据传输方法、装置及系统

Country Status (2)

Country Link
CN (1) CN110691370B (zh)
WO (1) WO2020007202A1 (zh)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113543230A (zh) * 2020-04-16 2021-10-22 华为技术有限公司 一种数据传输的方法及通信装置
CN113938920A (zh) * 2021-09-06 2022-01-14 中国联合网络通信集团有限公司 一种重耕影响的预测方法及装置
CN114362891A (zh) * 2020-09-28 2022-04-15 华为技术有限公司 一种通信方法和装置
CN114363830A (zh) * 2020-09-28 2022-04-15 中国移动通信有限公司研究院 多播数据的处理方法、核心网网关、业务服务器及终端
CN114651449A (zh) * 2020-04-26 2022-06-21 华为技术有限公司 一种流媒体参数动态自适应网络的调整方法及装置
CN115668863A (zh) * 2020-08-19 2023-01-31 华为技术有限公司 数据传输方法及装置

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113162788B (zh) * 2020-01-23 2022-12-27 华为技术有限公司 报告信息的发送方法和通信装置以及通信系统
CN113498215A (zh) * 2020-04-08 2021-10-12 中国移动通信有限公司研究院 一种网络信息开放的方法及设备
CN113543232A (zh) * 2020-04-21 2021-10-22 中国移动通信有限公司研究院 一种数据传输方法、终端、用户面功能实体及服务器
WO2021212439A1 (zh) * 2020-04-23 2021-10-28 华为技术有限公司 一种通信方法及装置
CN113676924B (zh) * 2020-05-15 2023-10-13 华为技术有限公司 通信方法、装置及系统
CN113784392A (zh) * 2020-06-10 2021-12-10 华为技术有限公司 通信方法、装置及系统
CN113938904A (zh) * 2020-06-29 2022-01-14 华为技术有限公司 数据传输的方法和装置
CN112566164B (zh) * 2020-12-09 2022-11-25 广州虎牙科技有限公司 一种通信系统及服务质量控制方法
WO2023272632A1 (zh) * 2021-06-30 2023-01-05 Oppo广东移动通信有限公司 信息传输方法、第一网元、第二网元、芯片和存储介质
WO2023010359A1 (zh) * 2021-08-04 2023-02-09 Oppo广东移动通信有限公司 数据传输方法、装置、设备及存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107018542A (zh) * 2017-03-27 2017-08-04 中兴通讯股份有限公司 网络系统中状态信息的处理方法、装置及存储介质
US20170359749A1 (en) * 2016-06-10 2017-12-14 Huawei Technologies Co., Ltd. Systems and method for quality of service monitoring, policy enforcement, and charging in a communications network
WO2018097599A1 (ko) * 2016-11-27 2018-05-31 엘지전자(주) 무선 통신 시스템에서의 등록 해제 방법 및 이를 위한 장치

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9578647B2 (en) * 2013-08-29 2017-02-21 Telefonaktiebolaget Lm Ericsson (Publ) 3GPP bearer-based QoS model support on WiFi
CN107493590B (zh) * 2017-06-15 2021-08-03 苏州智行畅联科技有限公司 数据传输方法及装置、基站及计算机可读存储介质

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170359749A1 (en) * 2016-06-10 2017-12-14 Huawei Technologies Co., Ltd. Systems and method for quality of service monitoring, policy enforcement, and charging in a communications network
WO2018097599A1 (ko) * 2016-11-27 2018-05-31 엘지전자(주) 무선 통신 시스템에서의 등록 해제 방법 및 이를 위한 장치
CN107018542A (zh) * 2017-03-27 2017-08-04 中兴通讯股份有限公司 网络系统中状态信息的处理方法、装置及存储介质

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
HUAWEI ET AL.: "A New Protocol Layer for QoS Flow to DRB Mapping", 3GPP TSG-RAN2 MEETING AD HOC, R2-1700088, 19 January 2017 (2017-01-19), XP051203840 *

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113543230A (zh) * 2020-04-16 2021-10-22 华为技术有限公司 一种数据传输的方法及通信装置
CN114651449A (zh) * 2020-04-26 2022-06-21 华为技术有限公司 一种流媒体参数动态自适应网络的调整方法及装置
CN114651449B (zh) * 2020-04-26 2023-09-29 华为技术有限公司 一种流媒体参数动态自适应网络的调整方法及装置
CN115668863A (zh) * 2020-08-19 2023-01-31 华为技术有限公司 数据传输方法及装置
CN114362891A (zh) * 2020-09-28 2022-04-15 华为技术有限公司 一种通信方法和装置
CN114363830A (zh) * 2020-09-28 2022-04-15 中国移动通信有限公司研究院 多播数据的处理方法、核心网网关、业务服务器及终端
CN114363830B (zh) * 2020-09-28 2023-09-05 中国移动通信有限公司研究院 多播数据的处理方法、核心网网关、业务服务器及终端
CN113938920A (zh) * 2021-09-06 2022-01-14 中国联合网络通信集团有限公司 一种重耕影响的预测方法及装置
CN113938920B (zh) * 2021-09-06 2023-08-22 中国联合网络通信集团有限公司 一种重耕影响的预测方法及装置

Also Published As

Publication number Publication date
CN110691370B (zh) 2021-02-09
CN110691370A (zh) 2020-01-14

Similar Documents

Publication Publication Date Title
WO2020007202A1 (zh) 一种数据传输方法、装置及系统
WO2020187052A1 (zh) 一种网络切片选择方法及装置
WO2019085853A1 (en) Method and system for supporting multiple qos flows for unstructured pdu sessions
EP3836577B1 (en) Session management method and device for user groups
CN114173374A (zh) 多接入管理服务分组分类和优先级排定技术
EP3952213B1 (en) Communication method, apparatus, and system
CN114189905A (zh) 一种报文处理方法及相关设备
WO2017067007A1 (zh) 服务质量的控制方法、设备及系统
JP2021516462A (ja) データ伝送制御方法および関連製品
US20220263879A1 (en) Multicast session establishment method and network device
KR102397750B1 (ko) 앵커리스 백홀의 지원을 위한 gtp 터널
CN115915196A (zh) 一种链路状态检测方法、通信装置及通信系统
CN110999349B (zh) 处理无锚移动网络中的移动设备管理
US11032389B1 (en) Applying application-based policy rules using a programmable application cache
US10743173B2 (en) Virtual anchoring in anchorless mobile networks
WO2021042381A1 (zh) 一种通信方法、装置及系统
US12040979B2 (en) Communications method, apparatus, and system
WO2023030077A1 (zh) 一种通信方法、通信装置及通信系统
US20240155418A1 (en) Method and apparatus for connecting qos flow based terminal in wireless communication system
WO2023056784A1 (zh) 数据收集方法、通信装置及通信系统
RU2783350C2 (ru) Способ управления сеансом группы пользователей и устройство
WO2024016801A1 (zh) 基站算力编排方法、装置、电子设备及存储介质
WO2023280107A1 (zh) 一种检测数据传输的质量的方法以及相关装置
WO2022068336A1 (zh) 路由信息更新方法、通信装置及存储介质
WO2023049076A1 (en) Methods and apparatus for bandwidth efficient configuration of time synchronization services in 5g systems

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: 19829880

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: 19829880

Country of ref document: EP

Kind code of ref document: A1