WO2022142835A1 - 一种数据传输方法、装置、计算机可读存储介质、电子设备及计算机程序产品 - Google Patents

一种数据传输方法、装置、计算机可读存储介质、电子设备及计算机程序产品 Download PDF

Info

Publication number
WO2022142835A1
WO2022142835A1 PCT/CN2021/131399 CN2021131399W WO2022142835A1 WO 2022142835 A1 WO2022142835 A1 WO 2022142835A1 CN 2021131399 W CN2021131399 W CN 2021131399W WO 2022142835 A1 WO2022142835 A1 WO 2022142835A1
Authority
WO
WIPO (PCT)
Prior art keywords
strong
sub
data
data packet
data packets
Prior art date
Application number
PCT/CN2021/131399
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 腾讯科技（深圳）有限公司
Priority to EP21913577.9A priority Critical patent/EP4240053A4/en
Priority to KR1020237010755A priority patent/KR20230058469A/ko
Priority to JP2023530057A priority patent/JP7484024B2/ja
Publication of WO2022142835A1 publication Critical patent/WO2022142835A1/zh
Priority to US17/989,301 priority patent/US20230083441A1/en

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/04—Error control
    • 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/0289—Congestion control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/0078—Avoidance of errors by organising the transmitted data in a format specifically designed to deal with errors, e.g. location
    • H04L1/0083—Formatting with frames or packets; Protocol or part of protocol for error control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/32—Flow control; Congestion control by discarding or delaying data units, e.g. packets or frames
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/60—Network streaming of media packets
    • H04L65/75—Media network packet handling
    • H04L65/752—Media network packet handling adapting media to network capabilities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/80—Responding to QoS
    • 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/0252—Traffic management, e.g. flow control or congestion control per individual bearer or channel
    • 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/0284—Traffic management, e.g. flow control or congestion control detecting congestion or overload during communication
    • 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/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
    • H04W28/065—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information using assembly or disassembly of packets
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0453—Resources in frequency domain, e.g. a carrier in FDMA
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/53—Allocation or scheduling criteria for wireless resources based on regulatory allocation policies
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/22—Manipulation of transport tunnels

Definitions

  • the present application relates to the field of computer and communication technologies, and relates to a data transmission method, an apparatus, a computer-readable storage medium, an electronic device, and a computer program product.
  • high-bandwidth and strongly interactive services are important types of services, such as cloud gaming (Cloud Gaming), virtual reality ( Virtual Reality (VR), Augmented Reality (AR), Mixed Reality (MR), Extended Reality (XR), Cinematic Reality (CR), etc.; these strong interactive services are not only for
  • cloud gaming Cloud Gaming
  • virtual reality Virtual Reality (VR)
  • Augmented Reality AR
  • Mixed Reality MR
  • XR Extended Reality
  • Cinematic Reality CR
  • these strong interactive services are not only for
  • the timeliness of transmission is required to be very high, and with the improvement of resolution, frame rate, degree of freedom and other indicators, the amount of data generated by the application layer increases greatly, which brings a great load to network transmission.
  • the data packets are usually divided into a large number of sub-data packets for transmission;
  • the transmission of the sub-packet fails, the content of the entire data packet cannot be recovered and presented in real time at the receiving end, which cannot meet the high-bandwidth and low-latency requirements of strong interaction.
  • Embodiments of the present application provide a data transmission method, apparatus, computer-readable storage medium, electronic device, and computer program product, which can reduce data packet transmission delay and transmission resource consumption.
  • the embodiment of the present application provides a data transmission method, including:
  • Access and Mobility Management Function AMF
  • AMF Access and Mobility Management Function
  • GTP-U General Packet Radio Service Tunnel Protocol User
  • DRB Data Radio Bearer
  • the sub-data packet obtained by splitting the strong-interaction type data packet In the process of sending the packet to the user equipment based on the DRB, according to the access stratum context information, detect the sending situation of the sub-data packet obtained by splitting the strong-interaction type data packet;
  • the embodiment of the present application provides another data transmission method, including:
  • Protocol Data Unit Protocol Data Unit
  • Session Management Function Session Management Function
  • the sub-data packets obtained by splitting the received strong interaction type data packets of different types are respectively transmitted to the base station equipment in different GTP-U tunnels, and the strong interaction type is detected.
  • the embodiment of the present application provides another data transmission method, including:
  • URSP User Equipment Routing Policy
  • the embodiment of the present application provides yet another data transmission method, including:
  • GTP-U tunnel configuration information for the strongly interactive data packets sent by the application function (Application Function, AF), where the GTP-U tunnel configuration information is used to indicate that the strongly interactive data packets of different types are in different GTP-U
  • the transmission is carried out in the U tunnel and carried by the same DRB;
  • User equipment routing policy URSP rules and protocol data unit PDU session management policy information are generated according to the GTP-U tunnel configuration information, where the URSP rules and the PDU session management policy information are used to indicate different types of the strong interaction type Data packets are respectively transmitted in different said GTP-U tunnels, and said strong interaction type data packets of different types are carried by the same said DRB;
  • the URSP rules Forward the URSP rules to the user equipment through the access and AMF, and configure access stratum context information to the base station equipment according to the URSP rules, where the access stratum context information is used to indicate different types of the strongly interactive data Packets are transmitted in different GTP-U tunnels respectively, and the strong interaction type data packets of different types are carried by the same DRB;
  • the PDU session management policy information is configured to the user plane functional entity through the SMF.
  • the embodiment of the present application provides a data transmission device, including:
  • the first receiving unit is configured to receive the access stratum context information sent by the AMF, where the access stratum context information is used to indicate that different types of strongly interactive data packets are respectively transmitted in different GTP-U tunnels, and are transmitted through the same A DRB is carried;
  • the first detection unit is configured to, when identifying that the data packet sent by the user plane functional entity through the GTP-U tunnel belongs to the sub-data packet obtained by splitting the strong-interaction type data packet, In the process of sending the sub-data packet obtained by packet splitting to the user equipment based on the DRB, according to the access layer context information, detecting the sending situation of the sub-data packet obtained by splitting the strong-interaction type data packet;
  • a first processing unit configured to stop sending all sub-data packets of the specified type to the user equipment when it is detected that the sub-packets obtained by splitting the strong-interaction type data packets of the specified type fail to be sent to the user equipment; The remaining sub-packets obtained by splitting the above-mentioned strong-interaction type packet.
  • the embodiment of the present application provides another data transmission device, including:
  • the second receiving unit is configured as the PDU session management policy information sent by the SMF, where the PDU session management policy information is used to indicate that different types of strongly interactive data packets are transmitted in different GTP-U tunnels, and pass through the same GTP-U tunnel.
  • DRB to carry;
  • the second detection unit is configured to, according to the PDU session management policy information, transmit sub-data packets obtained by splitting the received strong interaction type data packets of different types to the base station equipment in different GTP-U tunnels respectively. , and detect the sending situation of the sub-packets obtained by splitting the strongly interactive data packets;
  • the second processing unit is configured to stop sending all sub-data packets of the specified type to the base station device when it is detected that the sub-data packets obtained by splitting the strong-interaction type data packets of the specified type fail to be sent to the base station device. The remaining sub-packets obtained by splitting the above-mentioned strong-interaction type packet.
  • the embodiment of the present application provides another data transmission device, including:
  • the third receiving unit is configured to receive the user equipment routing policy URSP rule sent by the AMF, where the URSP rule is used to indicate that different types of strongly interactive data packets are transmitted in different GTP-U tunnels, and pass through the same GTP-U tunnel. DRB to carry;
  • the third detection unit is configured to, when recognizing that the data packet sent by the base station device based on the DRB belongs to the sub-data packet obtained by splitting the strong-interaction type data packet, receive the sub-data packet obtained by splitting the strong-interaction type data packet In the process of the sub-data packet, according to the URSP rule, detect the reception situation of all sub-data packets obtained by the splitting of the strong interaction type data packet;
  • the third processing unit is configured to detect that when all the data packets obtained by splitting the strong-interaction type data packets of the specified type are not completely received within a set period of time, send the strong-interaction type data packets of the specified type to The application server of the data packet sends transmission failure information, where the transmission failure information is used to indicate to the application server that the transmission of the strong interaction type data packet of the specified type fails.
  • the embodiment of the present application provides yet another data transmission device, including:
  • the fourth receiving unit is configured to receive the GTP-U tunnel configuration information sent by the AF for the strong interaction type data packet, where the GTP-U tunnel configuration information is used to indicate that the strong interaction type data packets of different types are respectively in different GTP-U tunnels.
  • the transmission is carried out in the U tunnel and carried by the same DRB;
  • the generating unit is configured to generate user equipment routing policy URSP rules and PDU session management policy information according to the GTP-U tunnel configuration information, where the URSP rules and the PDU session management policy information are used to indicate different types of the strong
  • the interactive data packets are transmitted in different GTP-U tunnels respectively, and are carried by the same DRB;
  • a first sending unit configured to forward the URSP rule to the user equipment through access and AMF, and configure access stratum context information to the base station equipment according to the URSP rule, where the access stratum context information is used to indicate different types of
  • the strongly interactive data packets are transmitted in different GTP-U tunnels respectively, and are carried by the same DRB;
  • the second sending unit is configured to configure the PDU session management policy information to the user plane functional entity through the SMF.
  • Embodiments of the present application provide a computer-readable storage medium on which a computer program is stored, and when the computer program is executed by one or more processors, implements the data transmission method provided by the embodiments of the present application.
  • the embodiment of the present application provides an electronic device, including:
  • processors one or more processors
  • the storage device is configured to store one or more programs, and when the one or more programs are executed by the one or more processors, the data transmission method provided by the embodiments of the present application is implemented.
  • An embodiment of the present application provides a computer program product, where the computer program product includes a computer program or computer instructions, and when the computer program or computer instructions are executed by one or more processors, realizes the data provided by the embodiments of the present application transfer method.
  • the embodiments of the present application have at least the following beneficial effects: by splitting a strongly interactive data packet (that is, a data packet of a strongly interactive service) into sub-data packets and classifying the sub-data packets, the sub-data packets can be sent to the user equipment in the sub-data packets.
  • a strongly interactive data packet that is, a data packet of a strongly interactive service
  • the sub-data packets can be sent to the user equipment in the sub-data packets.
  • sending fails stop sending the remaining sub-data packets obtained by splitting the specified type of strong-interaction data packets to the user equipment; that is, in the case of failure to send sub-data packets, it can stop sending invalid sub-data packets in time; Therefore, the data packet transmission delay and transmission resource consumption can be reduced.
  • FIG. 1 shows a schematic diagram of an exemplary system architecture of an embodiment of the present application
  • FIG. 2 shows a schematic diagram of a transmission process of a strongly interactive data packet according to an embodiment of the present application
  • FIG. 3 shows a flowchart of a data transmission method according to an embodiment of the present application
  • FIG. 4 shows a schematic diagram of a division structure of a strongly interactive data packet according to an embodiment of the present application
  • FIG. 5 shows a flowchart of another data transmission method according to an embodiment of the present application.
  • FIG. 6 shows a flowchart of another data transmission method according to an embodiment of the present application.
  • FIG. 7 shows a flowchart of still another data transmission method according to an embodiment of the present application.
  • FIG. 8 shows a schematic diagram of a transmission process of another strongly interactive data packet according to an embodiment of the present application.
  • FIG. 9 shows a configuration flowchart of a control plane according to an embodiment of the present application.
  • FIG. 10 shows a schematic flowchart of an exemplary data transmission method provided by an embodiment of the present application.
  • FIG. 11 shows a schematic flowchart of another exemplary data transmission method provided by an embodiment of the present application.
  • FIG. 12 shows a schematic flowchart of another exemplary data transmission method provided by an embodiment of the present application.
  • FIG. 13 shows a block diagram of a data transmission apparatus according to an embodiment of the present application.
  • FIG. 14 shows a block diagram of another data transmission apparatus according to an embodiment of the present application.
  • FIG. 15 shows a block diagram of another data transmission apparatus according to an embodiment of the present application.
  • FIG. 16 shows a block diagram of still another data transmission apparatus according to an embodiment of the present application.
  • FIG. 17 shows a schematic structural diagram of an electronic device according to an embodiment of the present application.
  • the cloud server 101 is used to run the cloud game, the cloud server 101 can render the game screen, encode the audio signal and the rendered image, and finally obtain The encoded data is transmitted to each game client through the network (game client 1-21, game client 1-22, game client 1-23, and game client 1-24 are exemplarily shown).
  • the game client can be a User Equipment (UE) with basic streaming media playback capabilities, human-computer interaction capabilities, and communication capabilities, such as smart phones, tablet computers, notebook computers, desktop computers, smart TVs, set-top boxes, Smart vehicle devices, portable music players, personal digital assistants, dedicated messaging devices, portable game devices, smart speakers, etc.; or the game client can also be an application program running in a terminal device, such as a native program in an operating system Or a software module, a native application (APP, Application), that is, a program (game APP) that needs to be installed in the operating system to run; a small program, that is, a program that can be run only by downloading it into the browser environment, A small program that can be embedded into any APP.
  • UE User Equipment
  • the game client can decode the encoded data transmitted by the cloud server 101 to obtain analog audio and video signals, and play them.
  • FIG. 1 is only an exemplary system architecture representing the cloud game system, and does not limit the specific architecture of the cloud game system; for example, the cloud game system may also include a background server for scheduling, and so on.
  • the cloud server 101 may be an independent physical server, a server cluster or a distributed system composed of multiple physical servers, or a cloud service, cloud database, cloud computing, cloud function, cloud storage, network service, cloud Cloud servers for basic cloud computing services such as communications, middleware services, domain name services, security services, Content Delivery Network (CDN), and big data and artificial intelligence platforms.
  • the game client and the cloud server 101 can be directly or indirectly connected through wired or wireless communication, which is not limited in this application.
  • the user plane mainly includes an application server, a user plane function (UPF), a base station (next generation NodeB, gNB for short), and user equipment.
  • the transmission of strongly interactive data packets is mainly in the downlink direction for some service scenarios, such as from the application server to the UPF, and then sent to the UE through the gNB.
  • the strongly interactive data packet 2-1 is split at the application layer of the application server, and the split sub-packet 2-2 is sent from the application server to the UPF as an Internet Protocol (IP) packet.
  • IP Internet Protocol
  • the 5G system transmits the sub-packets to the UE through the PDU session, and the application layer on the UE side submits them from the protocol stack level by level and reorganizes them (the figure shows the sub-packets 2-3 before the reorganization) to recover the Strong Interaction Packet 2-1.
  • the application server includes L1 layer, L2 layer and IP layer; user plane functions include L1 layer, L2 layer, User Datagram Protocol (User Datagram Protocol, UDP)/IP, General Packet Radio User plane and IP layer of service tunneling protocol; base station includes L1 layer, L2 layer, UDP/IP, GTP-U, physical layer (Physical, PHY), media access control layer (Media Access Control, MAC), radio link control layer Protocol layer (Radio Link Control, RLC), Packet Data Convergence Protocol (PDCP), Service Data Adaptation Protocol (Service Data Adaptation Protocol, SDAP) and IP layer; user equipment includes PHY layer, MAC layer , RLC layer, PDCH layer, SDAP layer and IP layer;
  • user equipment includes PHY layer, MAC layer , RLC layer, PDCH layer, SDAP layer and IP layer.
  • the L1 layer refers to the physical layer, which is used to ensure that the original data can be transmitted on various physical media
  • the L2 layer refers to the data link layer
  • the data link layer provides services to the network based on the services provided by the physical layer.
  • Layer provides services
  • IP layer is the network layer, which is used to realize data transfer between two end systems.
  • the strongly-interactive data packets generated by the application layer need to be divided into a large number of sub-data packets with very low delay and transmitted in segments. Once the transmission of one of the sub-data packets does not meet the transmission requirements , the entire strongly interactive data packet cannot be recovered and presented in real time at the receiving end, thus failing to meet the requirements of the highly interactive high-bandwidth service. In this case, the transmission of a large number of sub-packet fragments is actually a waste of network resources.
  • a strongly interactive data packet is split into 10 sub-packets (or even more sub-packets), and the probability of successful transmission of each sub-packet is 0.99, then the probability of successful transmission of all 10 sub-packets is 0.99 10 , which is 0.904. It can be seen that when a strong interactive data packet is split into multiple sub-data packets, even if each sub-data packet has a high probability of successful transmission, all sub-data packets obtained from the split of the entire strong interactive data packet are transmitted successfully. The probability will also be greatly reduced. Moreover, if the transmission of a sub-packet fails, the receiver cannot recover the strong-interaction packet.
  • the embodiments of the present application provide a data transmission method, apparatus, computer-readable storage medium, electronic device, and computer program product, which can reduce the transmission delay of data packets and the consumption of transmission resources.
  • FIG. 3 shows a flowchart of a data transmission method according to an embodiment of the present application, and the data transmission method may be performed by a base station device.
  • the data transmission method includes at least S310 to S330, and each step will be described below.
  • the access stratum context information sent by the AMF is received, and the access stratum context information is used to indicate that different types of strongly interactive data packets are transmitted in different GTP-U tunnels respectively, and are carried by the same DRB.
  • the base station is separated from the control plane and the user plane, that is, the base station is separated into a base station centralized unit (gNB Centralized Unit, gNB-CU) and a base station distributed unit (gNB Distributed Unit, gNB-DU), and gNB-
  • gNB Centralized Unit gNB-CU
  • gNB Distributed Unit gNB-DU
  • gNB-DU base station distributed unit
  • gNB- The CU is used as the control plane and the gNB-DU is used as the user plane, so the base station equipment in this embodiment of the present application may be the gNB-DU.
  • the type of the strongly interactive data packet may be determined according to the type and priority of the service content to be transmitted.
  • the types of strongly interactive data packets may include key frames and non-key frames, where the key frame may be an intra-frame coded frame (Intra Picture, I frame), and the non-key frame may be a forward predictive frame (Predictive Frame, P frame) and/or Bi-Directional Interpolated Prediction Frame (Bi-Directional Interpolated Prediction Frame, B frame).
  • the transmission of multiple types of strongly interactive data packets in different GTP-U tunnels may be as follows: one type of strongly interactive data packets is transmitted in one GTP-U tunnel, and Different types of strongly interactive data packets use different GTP-U tunnels during transmission.
  • the sub-data packet obtained by splitting the strong-interaction type data packet is based on In the process of sending the DRB to the user equipment, according to the context information of the access layer, the sending situation of the sub-data packet obtained by splitting the strong-interaction type data packet is detected.
  • the user plane functional entity transmits different types of strongly-interactive data packets in different GTP-U tunnels, that is, different types of strongly-interactive data packets are transmitted using different GTP-U tunnels .
  • the base station equipment can receive the data packets sent by the user plane functional entity in different GTP-U tunnels, and after receiving the data packets, can also identify whether the data packets are sub-data packets obtained by splitting the strong-interaction data packets.
  • the base station device can also identify which type of strongly interactive data packet it is according to the GTP-U tunnel of the sub-packet obtained by receiving the splitting of the strongly interactive data packet, for example, the identification information of the GTP-U tunnel can be used.
  • the identification information of the GTP-U tunnel Corresponding to the type of the strong interaction type data packet, and then according to the identification information of the GTP-U tunnel of the sub-data packet obtained by receiving the strong interaction type data packet, it is determined which type of strong interaction type data packet is received.
  • the strongly interactive data packets corresponding to key frames there are two types of strongly interactive data packets, that is, the strongly interactive data packets corresponding to key frames and the strongly interactive data packets corresponding to non-key frames.
  • These two types of strongly interactive data packets are transmitted in the GTP-U tunnel respectively; it can be a sub-packet obtained by transmitting the strong interactive data packet corresponding to the key frame in one GTP-U tunnel, and in another GTP-U tunnel
  • the sub-data packets obtained by splitting the strong interactive data packets corresponding to non-key frames are transmitted in the U tunnel.
  • the multiple sub-data packets obtained by splitting the strong-interaction type data packet include a start data packet and an end data packet.
  • the start data packet contains first indication information, and the first indication information is used to indicate that the start data packet is the first transmitted sub-data packet in the plurality of sub-data packets;
  • the end data packet contains second indication information, the first sub-data packet is transmitted.
  • the second indication information is used to indicate that the end data packet is the last transmitted sub-data packet among the multiple sub-data packets.
  • the base station device determines whether to receive a sub-data packet obtained by splitting a strong-interaction type data packet by identifying the start data packet and the end data packet. For example, if the base station device recognizes the start data packet according to the first indication information contained in the start data packet, then the data packets received from the start data packet to the end data packet belong to the splitting of strong interaction type data packets. sub-packets.
  • the base station device may identify whether the received data packet belongs to a sub-data packet obtained by splitting a strong-interaction type data packet according to the indication information contained in the protocol field of the received data packet.
  • the start data packet in the multiple sub-data packets obtained by splitting the strong interaction type data packet is added with indication information to indicate that it is the start data packet in the protocol field, and the end data packet is added in the protocol field. It is the indication information indicating that it is the end data packet; then after the base station device recognizes the start data packet according to the protocol field of the data packet, the data packets received from the start data packet to the end data packet belong to the strong interaction type.
  • the sub-packets obtained from packet splitting is obtained from packet splitting.
  • the base station device may identify whether the received data packet belongs to a sub-data packet obtained by splitting a strongly interactive data packet according to the indication information contained in the payload information of the received data packet.
  • the start data packet in the multiple sub-data packets obtained by splitting the strong interaction type data packet is added with indication information to indicate that it is the start data packet in the payload information, and the end data packet is added in the payload information.
  • Add the indication information to indicate that it is the end data packet then after the start data packet is identified according to the payload information of the data packet, the data packets from the start data packet to the end data packet belong to strong interaction data. Subpackets obtained from packet splitting.
  • the base station device detects that the sub-data packet obtained by splitting the strong-interaction type data packet of the specified type is the sub-data packet that fails to be sent to the user equipment, then if it continues to send the strong-interaction type of the specified type at this time.
  • the remaining sub-data packets obtained by splitting the specified type of data packets cannot recover the specified type of strong-interaction type data packets. Therefore, the base station equipment can stop sending the remaining sub-data packets to the user equipment, so as to reduce the occupation of bandwidth, which is conducive to reducing Occupation of transmission resources by strongly interactive data packets during transmission.
  • the strong-interaction type data packet is a specified type of strong-interaction type data packet.
  • a strongly-interactive packet of the specified type is a strongly-interactive packet with sub-packets that fail to send.
  • the specified type is any one of multiple types.
  • the two types of strongly-interactive data packets are the strongly-interactive data packets corresponding to the key frame and the Strong interactive data packets corresponding to non-key frames. If the strong interactive data packet corresponding to the non-key frame has sub-data packets that fail to send, then the strong interactive data packet corresponding to the non-key frame is a strong interactive data packet of the specified type; if the strong interactive data packet corresponding to the key frame If there are sub-packets that fail to be sent when the interactive data packet is sent, the strong interactive data packet corresponding to the key frame is the specified type of strong interactive data packet.
  • the base station equipment when the base station device detects whether the sub-data packets obtained by splitting the strong-interaction data packets are sub-data packets that fail to be sent to the user equipment, the base station equipment can split the strong-interaction data packets to obtain the sub-data packets of various types.
  • the sub-data packets are detected separately, and the detection process of the sub-data packets obtained by splitting multiple types of strong interaction data packets does not affect each other.
  • the transmission process of sub-packets obtained by splitting multiple types of strong-interaction packets can also be independent of each other; for example, if a sub-packet obtained by splitting a certain type of strong-interaction If the sending of the device fails, you can stop sending the remaining sub-packets obtained by splitting the specified type of strong-interaction data packets to the user equipment, but this process does not affect the sub-packets obtained by splitting other types of strong-interaction packets.
  • the sending of data packets that is, the sub-data packets obtained by splitting other types of strong interactive data packets can continue to be sent.
  • the base station device may also discard the received strongly-interactive data of the specified type.
  • the sub-data package obtained by the package split to reduce the occupation of storage resources.
  • the base station device may send first feedback information to the user plane functional entity, the first The feedback information is used to instruct the user plane functional entity to stop transmitting the remaining sub-data packets obtained by splitting the strong-interaction type data packets of the specified type.
  • the base station equipment can send the first feedback information to the user plane functional entity to indicate the user plane
  • the functional entity stops transmitting the remaining sub-data packets obtained by splitting the specified type of strong interaction type data packets, so as to reduce the occupation of transmission resources.
  • the base station device sends the first feedback information to the user plane functional entity under the condition that all sub-data packets obtained by splitting the strong-interaction data packet of the specified type are not completely received; If all sub-data packets obtained by splitting the specified type of strong-interaction data packets are completely received, there is no need to send the first feedback information to the user plane functional entity.
  • the base station equipment if it does not completely receive all sub-data packets obtained by splitting the strong-interaction type data packets of the specified type sent by the user plane functional entity within the set time period, it stops sending the specified type of data packets to the user equipment. The remaining sub-packets obtained by splitting the strong-interaction data packet of the specified type are discarded, and the sub-packets obtained by splitting the received strong-interaction data packet of the specified type are discarded.
  • the strongly interactive data packet can be a data packet with a time limit. If the base station equipment does not fully receive the specified type of strong interactive data packet sent by the user plane functional entity within the set time period, all the sub-data packets, it means that the specified type of strong-interaction data packets has exceeded the time limit. At this time, the base station equipment no longer needs to transmit the remaining sub-data packets obtained by splitting the specified type of strong-interaction data packets to the user equipment. Of course, if all sub-packets obtained by splitting the specified type of strongly interactive data packets sent by the user plane functional entity are not fully received within the set period of time, it may also be because the user plane functional entity detects that there are sub-packets transmitted.
  • the base station equipment does not need to transmit the remaining sub-data packets obtained by splitting the specified type of strong interactive data packet to the user equipment. In this case, it can also stop sending the specified
  • the remaining sub-packets obtained by splitting the strong-interaction data packet of the specified type can be discarded, and the sub-packets obtained by splitting the received strong-interaction data packet of the specified type can be discarded.
  • various types of strongly interactive data packets 4-1 may include: strong interactive data packets corresponding to key frames (ie, I frames shown in FIG. 4 ) and non-interactive data packets The strong interaction type data packet corresponding to the key frame (ie, the P frame shown in FIG. 4 ).
  • the base station equipment detects that the transmission of sub-data packets obtained by splitting the strong-interaction data packets corresponding to the key frames to the user equipment fails, it will stop the transmission. Sending strong interaction data packets corresponding to non-key frames associated with the specified key frames to the user equipment, and/or discarding received strong interaction data packets corresponding to non-key frames associated with the specified key frames.
  • the base station device when the sub-data packet obtained by splitting the strong-interaction data packet corresponding to the key frame fails to be sent, the base station device not only stops transmitting the remaining sub-data packets obtained by splitting the strong-interactive data packet corresponding to the key frame, but also And stop the strong interaction data packets corresponding to the non-key frames associated with the specified key frame; that is, the base station equipment stops the strong interaction data packets corresponding to the non-key frames associated with the key frame. Transmission of the remaining sub-data packets; in this way, the bandwidth occupation of invalid sub-data packets can be reduced, which is beneficial to reduce the occupation of transmission resources during transmission of strong interaction data packets.
  • FIG. 3 illustrates the data transmission method of the embodiment of the present application from the perspective of a base station device, and the following describes the data transmission method of the embodiment of the present application from the perspective of a user plane functional entity.
  • FIG. 5 shows a flowchart of another data transmission method according to an embodiment of the present application, and the data transmission method may be executed by a user plane functional entity.
  • the data transmission method includes at least S510 to S530, and each step is described below.
  • the PDU session management policy information sent by the SMF is received, and the PDU session management policy information is used to indicate that different types of strongly interactive data packets are respectively transmitted in different GTP-U tunnels and carried by the same DRB.
  • the type of the strongly interactive data packet may be determined according to the type and priority of the service content to be transmitted.
  • the types of the strongly interactive data packets may include key frames and non-key frames, wherein the key frames may be I frames, and the non-key frames may be P frames and/or B frames.
  • the received sub-data packets obtained by splitting different types of strong-interaction data packets are respectively transmitted to the base station equipment in different GTP-U tunnels, and the strong-interaction data packets are detected.
  • the sending status of sub-packets obtained from packet splitting is
  • the multiple sub-data packets obtained by splitting the strong-interaction type data packet include a start data packet and an end data packet.
  • the start data packet contains first indication information, and the first indication information is used to indicate that the start data packet is the first transmitted sub-data packet in the plurality of sub-data packets;
  • the end data packet contains second indication information, the first sub-data packet is transmitted.
  • the second indication information is used to indicate that the end data packet is the last transmitted sub-data packet among the multiple sub-data packets.
  • the user plane functional entity determines whether to receive the sub-packet obtained by splitting the strong-interaction type data packet by identifying the start data packet and the end data packet. For example, if the user plane functional entity identifies the start data packet according to the first indication information contained in the start data packet, then the data packets from the start data packet to the end data packet belong to the splitting of strong interaction type data packets. subpackets.
  • the user plane functional entity may identify whether the received data packet belongs to a sub-data packet obtained by splitting a strong-interaction type data packet according to the indication information contained in the protocol field of the received data packet.
  • the start data packet in the multiple sub-data packets obtained by splitting the strong interaction type data packet is added with indication information to indicate that it is the start data packet in the protocol field, and the end data packet is added in the protocol field. It is the indication information indicating that it is the end data packet; then after the user plane functional entity identifies the start data packet according to the protocol field of the data packet, the data packets received from the start data packet to the end data packet belong to strong A sub-packet obtained by splitting an interactive packet.
  • the user plane functional entity may identify whether the received data packet belongs to a sub-data packet obtained by splitting a strong-interaction type data packet according to the indication information contained in the payload information of the received data packet.
  • the start data packet in the multiple sub-data packets obtained by splitting the strong interaction type data packet is added with indication information to indicate that it is the start data packet in the payload information, and the end data packet is added in the payload information.
  • Add the indication information to indicate that it is the end data packet then after the start data packet is identified according to the payload information of the data packet, the data packets received from the start data packet to the end data packet belong to the strong A sub-packet obtained by splitting an interactive packet.
  • the user plane functional entity detects that the sub-packet obtained by splitting the strong-interaction data packet of a specified type is a sub-packet that fails to be sent to the base station device, then if it continues to send the specified type of sub-packet
  • the remaining sub-packets obtained by splitting the strong-interaction data packets are meaningless; therefore, the user plane functional entity can stop sending the remaining sub-packets to the base station equipment to reduce bandwidth occupation, which is beneficial to reducing the strong-interaction data packets. Occupation of transmission resources during transmission.
  • the user plane functional entity detects that the sub-packet obtained by splitting the strong-interaction data packet of the specified type is a sub-packet that fails to be sent to the base station device, it can also discard the received sub-packet.
  • the sub-packets obtained by splitting the strong-interaction type packets can reduce the occupation of storage resources.
  • the user plane functional entity detects that the sub-packet obtained by splitting the strong-interaction type data packet of the specified type is the sub-packet that fails to be sent to the base station device, it can send the second feedback information to the application server.
  • the second feedback information is used to instruct the application server to stop transmitting the remaining sub-data packets obtained by splitting the strong-interaction type data packet.
  • the user plane functional entity when it detects that there is a sub-packet that fails to send in the process of sending the specified type of strong interaction type data packet to the base station device, it can send the second feedback information to the application server to indicate the application server. Stop transmitting the remaining sub-packets to reduce the occupation of transmission resources.
  • the user plane function entity sends the second feedback information to the application server under the condition that all sub-data packets obtained by splitting the strong-interaction data packet of the specified type are not completely received; If all sub-data packets obtained by splitting the specified type of strong-interaction data packets are completely received, there is no need to send the second feedback information to the application server.
  • the user plane functional entity if it does not completely receive all sub-data packets obtained by splitting the strong-interaction data packets of the specified type sent by the application server within the set time period, it stops sending the specified type of data packets to the base station device. The remaining sub-packets obtained by splitting the strong-interaction data packet of the specified type are discarded, and the sub-packets obtained by splitting the received strong-interaction data packet of the specified type are discarded.
  • the strongly interactive data packet can be a data packet with a time limit. If the user plane functional entity does not completely receive all the sub-data packets obtained by splitting the strong interactive data packet sent by the application server within the set time period. , then it means that the strong interaction data packet has exceeded the time limit, and at this time, the user plane functional entity no longer needs to transmit the remaining sub-data packets to the base station equipment. Of course, if the user plane functional entity does not completely receive all sub-packets obtained by splitting the specified type of strong-interaction data packets sent by the application server within the set time period, it may also be because the application server detects that there are sub-packets transmitted. The error and then stop sending.
  • the user plane function entity does not need to transmit the remaining sub-data packets to the base station equipment.
  • the user plane function entity can also stop sending the specified type of strong interaction data to the base station equipment.
  • the remaining sub-packets obtained by packet splitting can be discarded, and the sub-packets obtained by splitting the received strong interactive data packets of the specified type can be discarded.
  • FIG. 6 shows a flowchart of another data transmission method according to an embodiment of the present application, and the data transmission method may be executed by a user equipment.
  • the data transmission method includes at least S610 to S630, and each step will be described below.
  • the URSP rule sent by the AMF is received, and the URSP rule is used to indicate that different types of strongly interactive data packets are transmitted in different GTP-U tunnels respectively, and are carried by the same DRB.
  • the multiple sub-data packets obtained by splitting the strong-interaction type data packet include a start data packet and an end data packet.
  • the start data packet contains first indication information, and the first indication information is used to indicate that the start data packet is the first transmitted sub-data packet in the plurality of sub-data packets;
  • the end data packet contains second indication information, the first sub-data packet is transmitted.
  • the second indication information is used to indicate that the end data packet is the last transmitted sub-data packet among the multiple sub-data packets.
  • the user equipment determines whether to receive a sub-data packet obtained by splitting the strong-interaction type data packet by identifying the start data packet and the end data packet. For example, if the user equipment identifies the start data packet according to the first indication information contained in the start data packet, then the data packets from the start data packet to the end data packet belong to the sub-data obtained by splitting the strong interaction type data packet Bag.
  • the user equipment can identify whether the received data packet belongs to a sub-data packet obtained by splitting a strong-interaction type data packet according to the indication information contained in the protocol field of the received data packet.
  • the start data packet in the multiple sub-data packets obtained by splitting the strong interaction type data packet is added with indication information to indicate that it is the start data packet in the protocol field, and the end data packet is added in the protocol field. It is the indication information indicating that it is the end data packet; after the user equipment identifies the start data packet according to the protocol field of the data packet, the data packets received from the start data packet to the end data packet belong to strong interaction data. Subpackets obtained from packet splitting.
  • the user equipment may identify whether the received data packet belongs to a sub-data packet obtained by splitting a strong-interaction type data packet according to the indication information contained in the payload information of the received data packet.
  • the start data packet in the multiple sub-data packets obtained by splitting the strong interaction type data packet is added with indication information to indicate that it is the start data packet in the payload information, and the end data packet is added in the payload information.
  • Add the indication information to indicate that it is the end data packet then after the start data packet is identified according to the payload information of the data packet, the data packets received from the start data packet to the end data packet belong to the strong A sub-packet obtained by splitting an interactive packet.
  • the user equipment when the user equipment performs integration processing on all sub-data packets obtained by splitting the strong-interaction data packets of a specified type, the user equipment may perform integration in the order of these sub-data packets, and finally obtain a complete strong interaction type data package.
  • the user equipment may discard the strong-interaction type packet of the specified type that has been received.
  • the sub-packets obtained from packet splitting may discard the strong-interaction type packet of the specified type that has been received.
  • the strongly interactive data packet can be a data packet with a time limit. If the user equipment does not completely receive all the sub-data packets obtained by splitting the strong interactive data packet of the specified type within the set time period, then it indicates that The specified type of strongly interactive data packet has exceeded the time limit, and the user equipment no longer needs to receive and integrate the remaining sub-data packets obtained by splitting the specified type of strongly interactive data packet; therefore, the user equipment can Discard the sub-packets obtained by splitting the received strong-interaction packets of the specified type.
  • the base station equipment detects that there is a sub-packet transmission error and then stops sending.
  • the user plane functional entity may discard the sub-packets obtained by splitting the received strong-interaction type packets of the specified type.
  • the user equipment if the user equipment does not completely receive all sub-data packets obtained by splitting the strong-interaction data packets of the specified type within the set time period, the user equipment sends the strong-interaction data packets of the specified type to the application server that sends the strong-interaction data packets of the specified type. Transmission failure information is sent to indicate that the strong-interaction packet transmission failed.
  • the technical solution of this embodiment enables the user equipment to send a transmission failure to the application server when it detects that all sub-data packets obtained by splitting a specified type of strong-interaction data packet are not completely received within a set period of time. information to indicate to the application server that the transmission of the specified type of strongly interactive data packets fails, so that the application server can confirm whether to resend.
  • PCF Policy Control Function
  • FIG. 7 shows a flowchart of still another data transmission method according to an embodiment of the present application, and the data transmission method may be executed by a PCF.
  • the data transmission method includes at least S710 to S740, and each step will be described below.
  • the AF may directly send the GTP-U tunnel configuration information for the strongly interactive data packets to the PCF, or the AF may also use the Network Exposure Function (NEF) to send the strongly interactive data packets to the PCF.
  • the GTP-U tunnel configuration information is sent to the PCF.
  • URSP rules and PDU session management policy information are generated according to the GTP-U tunnel configuration information, and the URSP rules and PDU session management policy information are used to indicate that different types of strongly interactive data packets are processed in different GTP-U tunnels respectively. It is transmitted and carried through the same DRB.
  • the URSP rule is forwarded to the user equipment through the AMF, and the access stratum context information is configured to the base station equipment according to the URSP rule, and the access stratum context information is used to indicate that different types of strong interaction data packets are in different It is transmitted in the GTP-U tunnel, and is carried through the same DRB.
  • the AMF may directly forward the URSP rule to the user equipment; at the same time, the AMF may generate the access stratum context information configured to the base station equipment according to the URSP rule, and send it to the base station equipment.
  • the SMF may directly forward the PDU session management policy information to the user plane functional entity.
  • the PCF configures the PDU session management policy information to the user plane functional entity.
  • the user plane functional entity detects the sub-packets obtained by splitting the specified type of strongly interactive data packets according to the PDU session management policy information.
  • the PCF forwards the URSP rules to the user equipment. In this way, according to the URSP rules, when the user equipment detects that it has not completely received all the data packets split from the specified type of strong interaction data packets within the set time period, it sends the specified type of data packets to the user equipment.
  • the application server of the strongly interactive data packet sends transmission failure information to reduce the occupation of transmission resources.
  • the PCF forwards the access stratum context information to the base station equipment.
  • the base station equipment detects that the transmission of the sub-packets obtained by splitting the specified type of strongly interactive data packets to the user equipment fails, and stops the transmission.
  • the application server may classify the strongly interactive data packets into two types at the application layer (two types are used as an example, and there may be more than two types), such as I frames and P frames; in this case, the two types are
  • the strongly interactive data packets are the I-frame stream and the P-frame stream; here, the application server transmits the I-frame stream and the P-frame stream respectively.
  • the classification information is placed in the packet header.
  • the division may not be based on the I frame and the P frame, but may be classified based on other rules, for example, based on the priority of the audio and video stream content.
  • the AF may interact with the PCF, and then the PCF interacts with each network element (eg, AMF, SMF, etc.) to configure the GTP-U tunnel for the two flows.
  • each network element eg, AMF, SMF, etc.
  • the strongly interactive data packets 8-11 of the I frame and the strongly interactive data packets 8-12 of the P frame which are differentiated by the application layer, are placed in different GTP-U tunnels (tunnels) after being split.
  • 8-21 and tunnel 8-22 after reaching the gNB, the same DRB bearer is used for downlink transmission, and the same DRB bearer has a uniform data packet number.
  • the gNB when the gNB schedules data transmission, it prioritizes the transmission of I-frame streams (that is, multiple sub-packets obtained by splitting the strong-interaction data packets of I-frames), and stops sending I-frames to the user equipment if the I-frame stream is lost.
  • the sub-packets obtained by splitting the strong-interaction data packets of the received I frame, and discarding the sub-packets obtained by splitting the strong-interaction data packets of the received I frame, and the subsequent strong-interaction data packets of the P frame are split out. (if the I frame is lost, the picture recovery cannot be performed even if the P frame is received).
  • the start and end of the sub-packets obtained by splitting the strongly interactive data packet of the type may be marked. Based on the marked start subpackets (called start packets) and end subpackets (called end packets), if there are some subpackets in the N subpackets split from a strong interaction type packet If the sending fails, the subsequent sub-packets do not need to be sent, and can be discarded; where N is a positive integer greater than 1.
  • the configuration process of the control plane needs to be performed, so that the UE and each network element can obtain the transmission parameters of the strongly interactive data packet, as shown in FIG. 9 . , including S901 to S906.
  • the AF configures GTP-U tunnel parameters (referred to as GTP-U tunnel configuration information) to the PCF.
  • the AF may configure the GTP-U tunnel parameters by configuring the PDU session policy of the strongly interactive data packet to the PCF.
  • the AF can directly send the PDU session policy of the strongly interactive data packet to the PCF, or the AF can also send the PDU session policy of the strongly interactive data packet to the PCF through the NEF.
  • the GTP-U tunnel parameter means that different types of strongly interactive data packets are transmitted in different GTP-U tunnels respectively, and are carried by the same DRB.
  • the PCF configures the URSP rule to the AMF.
  • the URSP rules configured by the PCF to the AMF are related to the PDU session policy, which means that different types of strongly interactive data packets are transmitted in different GTP-U tunnels respectively, and are transmitted through the same DRB. bear.
  • the AMF configures the URSP rule to the UE.
  • the URSP rules configured by the AMF to the UE include: different types of strongly interactive data packets are transmitted in different GTP-U tunnels respectively, and are carried by the same DRB.
  • the AMF configures the access stratum context (access stratum context information) to the gNB.
  • the Access Stratum (AS) context (Context) configured by the AMF to the gNB is related to the PDU session policy, which means that different types of strongly interactive data packets are stored in different GTP-U The policy is to transmit in the tunnel and carry it through the same DRB.
  • the PCF configures a PDU session management policy (referred to as PDU session management policy information) to the SMF.
  • PDU session management policy information a PDU session management policy
  • the PDU session management policy includes a policy that different types of strongly interactive data packets are transmitted in different GTP-U tunnels respectively, and are carried by the same DRB.
  • the SMF configures the PDU session management policy to the UPF.
  • IP sub-packets called multiple sub-packets
  • the IP sub-packets that have been successfully sent should be discarded even if they have been received by the receiver; if there are still some IP sub-packets that have not been sent yet , the sender should also stop sending and start sending the next strong interaction data packet as soon as possible.
  • the application server or the user equipment retransmits the strongly interactive data packet at the application layer, the retransmitted strongly interactive data packet can be determined as a new strongly interactive data packet for transmission.
  • the specific transmission method This is consistent with the data transmission method provided in the embodiment of the present application.
  • a schematic flowchart of an exemplary data transmission method provided by the embodiment of the present application may include S1010 to S1080.
  • the strong interaction type data packet is split on the application server side.
  • the application server may determine the sub-packet size according to information such as the set sub-packet size or the state of the network, and then split the strongly interactive data packets according to the sub-packet size to obtain multiple sub-packets.
  • indication information may be added to the start data packet and the end data packet to indicate which sub-data packet is the start data packet and which sub-data packet is the end data packet.
  • the indication information may be added in the protocol field or payload information of the sub-packet, for example, in the field of the GTP-U tunneling protocol.
  • the UPF identifies the start and end of the sub-data packets, and puts different types of sub-data packets into different GTP-U tunnels at the same time.
  • the UPF when the application server transmits the split sub-data packets to the UPF, the UPF can identify the start data packet and the end data packet.
  • the sub-data packet transmission arrives at the gNB, and the gNB sends it.
  • the UPF after receiving the sub-data packet sent by the application server, the UPF transmits the sub-data packet to the gNB, and then the gNB sends the sub-data packet to the user equipment.
  • the gNB needs to be enhanced to be able to identify the indication information in the sub-data packets, and then determine the start data packet and the end data packet, so as to identify a series of sub-data packets obtained by splitting the strongly interactive data packets.
  • the gNB puts different types of sub-packets received from different GTP-U tunnels into the same DRB and sends them to the user equipment.
  • the gNB sends the mth sub-data packet to the user equipment.
  • m is a positive integer variable.
  • the gNB judges whether the m-th sub-packet is sent successfully; if so, execute S1060; if not, execute S1070. In addition, the gNB can also judge whether the mth sub-packet meets the delay requirement; if so, execute S1060; if not, execute S1070.
  • the gNB may send the sub-data packet to the user equipment through the air interface (Uu interface).
  • the success and failure of data transmission can be judged through protocols such as PDCP and RLC of the Uu interface.
  • the user equipment detects that the strong interaction type data packet fails to be transmitted, and sends feedback from the application layer to the application server.
  • the user equipment does not completely receive all sub-packets of a specified type of strong-interaction data packet within a certain time limit (referred to as a set duration), it may be determined that the transmission of the strong-interaction type data packet fails.
  • the information fed back to the application server is used to indicate that the specified type of strong interaction data packet has failed to be transmitted.
  • the data transmission method shown in FIG. 10 describes the process in which the user equipment indicates the failure of the strong interaction type data packet transmission from the application layer to the application server.
  • the gNB may also indicate to the UPF the transmission situation of the strong interaction type data packet.
  • the data transmission method includes S1110 to S1180.
  • the strong interaction type data packet is split on the application server side.
  • the application server may determine the sub-packet size according to information such as the set sub-packet size or the state of the network, and then split the strongly interactive data packets according to the sub-packet size to obtain multiple sub-packets.
  • indication information may be added to the start data packet and the end data packet to indicate which sub-data packet is the start data packet and which sub-data packet is the end data packet.
  • the indication information may be added in the protocol field or payload information of the data packet, for example, in the field of the GTP-U tunneling protocol.
  • the UPF identifies the start and end of the sub-data packets, and puts different types of sub-data packets into different GTP-U tunnels at the same time.
  • the UPF when the application server transmits the split sub-data packets to the UPF, the UPF can identify the start data packet and the end data packet.
  • the sub-data packet transmission arrives at the gNB, and the gNB sends it.
  • the UPF after receiving the sub-data packet sent by the application server, the UPF transmits the sub-data packet to the gNB, and then the gNB sends the sub-data packet to the user equipment.
  • the gNB needs to be enhanced to be able to identify the indication information in the sub-data packets, and then determine the start data packet and the end data packet, so as to identify a series of sub-data packets obtained by splitting the strongly interactive data packets.
  • the gNB puts different types of sub-data packets received from different GTP-U tunnels into the same DRB and sends them to the user equipment.
  • the gNB sends the mth sub-data packet to the user equipment.
  • the gNB judges whether the m-th sub-packet is sent successfully; if so, execute S1160; if not, execute S1170. In addition, the gNB can also judge whether the m-th sub-packet meets the delay requirement; if so, execute S1160; if not, execute S1170.
  • the gNB may send the sub-data packet to the user equipment through the Uu interface.
  • the success and failure of data transmission can be judged through the protocols of the Uu interface (such as PDCP and RLC, etc.).
  • the gNB provides feedback information (referred to as first feedback information) to the UPF, and notifies the UPF to stop sending the remaining sub-data packets to the gNB.
  • first feedback information referred to as first feedback information
  • the gNB if the gNB has completely received all the sub-data packets obtained by splitting the strong-interaction type data packet, it does not need to provide feedback information to the UPF.
  • the data processing methods shown in FIG. 10 and FIG. 11 can also be combined, that is, when the user equipment detects that the transmission of the strongly interactive data packet fails, it sends feedback from the application layer to the application server, while the gNB is in the After it is determined that the transmission fails, feedback information may also be provided to the UPF to notify the UPF to stop sending sub-data packets to the gNB.
  • the interaction flow between the application server, the UPF, the gNB and the user equipment includes S1201 to S1205 .
  • the application server splits the strong interaction type data packet, and marks the start data packet and the end data packet.
  • indication information may be added to the start data packet and the end data packet to indicate which sub-data packet is the start data packet and which sub-data packet is the end data packet.
  • the indication information may be added in the protocol field or payload information of the data packet, for example, in the field of the GTP-U tunneling protocol.
  • the application server sends a sub-data packet to the UPF.
  • the UPF when the application server transmits the split sub-data packets to the UPF, the UPF can identify the start data packet and the end data packet.
  • the UPF sends the sub-data packet to the gNB.
  • the UPF can put different types of sub-data packets into different GTP-U tunnels for transmission to the gNB.
  • the process of UPF sending sub-data packets to gNB and the process of application server sending sub-data packets to UPF can be performed synchronously; ), the sub-data packet can be sent to the gNB, which can reduce the delay of the sub-data packet reaching the user equipment.
  • UPF can also send sub-data packets to gNB after receiving all the sub-data packets sent by the application server. In this way, UPF can reduce the number of invalid sub-data packets sent to gNB when errors occur during the receiving process. number, thereby reducing the consumption of transmission resources.
  • the UPF in the process of sending the sub-data packets obtained by splitting the strongly interactive data packets to the gNB, if the UPF detects that a certain type (referred to as a specified type) of the strongly interactive data packets is split and obtained by splitting If the transmission of the sub-packet fails or detects that the transmission of the sub-packet exceeds the delay requirement, the UPF can stop sending the remaining sub-packets of the strong-interaction data packet of this type to the gNB, and reduce the number of invalid sub-packets sent, thereby reducing the number of invalid sub-packets sent. The consumption of transmission resources can be reduced.
  • the UPF can also delete the received sub-packets obtained by splitting the strong-interaction packet of this type, and the UPF can also notify the application server to stop transmitting the strong-interaction packet splitting of this type to the UPF. The remaining sub-packets obtained are divided.
  • the UPF may also stop sending the strong interaction type to the gNB when all sub-packets obtained by splitting a certain type of strong interaction type transmitted by the application server are not received within a set period of time.
  • the remaining sub-packets obtained by splitting the type data packets, and the UPF can also delete the received sub-packets obtained by splitting the strong-interaction type packets of this type, and the UPF can also notify the application server to stop transmitting this type to the UPF.
  • the remaining sub-packets obtained by splitting the strong-interaction packet may also stop sending the strong interaction type to the gNB when all sub-packets obtained by splitting a certain type of strong interaction type transmitted by the application server are not received within a set period of time.
  • the gNB sends the sub-data packet to the user equipment.
  • the gNB may transmit sub-data packets obtained by splitting different types of strong-interaction data packets to the user equipment through the same DRB bearer.
  • the process of sending the sub-data packets to the user equipment by the gNB and the process of sending the sub-data packets to the gNB by the UPF may be performed synchronously; completed), the sub-data packets can be sent to the user equipment, which can reduce the delay of the sub-data packets reaching the user equipment.
  • the gNB can also send the sub-data packets to the user equipment after receiving all the sub-data packets sent by the UPF. In this way, when an error occurs in the receiving process, the UPF can reduce the number of invalid sub-data packets sent to the gNB. number, thereby reducing the consumption of transmission resources.
  • the gNB in the process of sending the sub-data packet obtained by splitting the strong-interaction type data packet to the user equipment, if the gNB detects that the sub-data packet obtained by splitting the strong-interaction type data packet of a certain type fails to transmit Or detecting that the sub-packet transmission exceeds the delay requirement, then the gNB can stop sending the remaining sub-packets obtained by splitting the strong-interaction type packet of this type to the user equipment, reducing the number of invalid sub-packets sent, so as to be able to Reduce transmission resource score consumption.
  • the gNB can also delete the received sub-packets obtained by splitting the strong-interaction data packets of this type, and the gNB can also notify the UPF to stop transmitting the strong-interaction packet splitting of this type to the gNB. The remaining sub-packets obtained.
  • the gNB may also stop sending the strong interaction type to the user equipment when the sub-packets obtained by splitting a certain type of strong interaction type data packets transmitted by the UPF are not all received within the set period of time.
  • the remaining sub-packets obtained by splitting the type data packets, and the gNB can also delete the received sub-packets obtained by splitting the strong-interaction type data packets of this type, and the gNB can also notify the UPF to stop transmitting the type of data packets to the gNB.
  • the remaining sub-packets obtained by splitting the strongly interactive packet may also stop sending the strong interaction type to the user equipment when the sub-packets obtained by splitting a certain type of strong interaction type data packets transmitted by the UPF are not all received within the set period of time.
  • the user equipment if it detects that a certain type of strong interaction type data packet fails to be transmitted, it can send feedback from the application layer to the application server.
  • transmission failure information is used to indicate that the strong interaction type data packet of this type has failed to be transmitted.
  • the data transmission method of the embodiment of the present application can transmit different types of strongly interactive data packets in different GTP-U tunnels, respectively, and correspond to the same DRB bearer, thereby enabling the transmission of multiple types of strongly interactive data packets.
  • the impact on the protocol side is reduced.
  • the transmission of the remaining sub-packets to the next-level node can be stopped in time, which can reduce the occupation of bandwidth and thus reduce the strong-interaction type. Occupation of transmission resources by data packets during transmission.
  • the data transmission apparatus provided in the embodiment of the present application may be used to execute the data transmission method in the embodiment of the present application.
  • FIG. 13 shows a block diagram of a data transmission apparatus according to an embodiment of the present application, and the data transmission apparatus may be set inside a base station device.
  • the data transmission apparatus 1300 includes: a first receiving unit 1302 , a first detecting unit 1304 and a first processing unit 1306 .
  • the first receiving unit 1302 is configured to receive access stratum context information sent by the AMF, where the access stratum context information is used to indicate that different types of strongly interactive data packets are transmitted in different GTP-U tunnels, respectively, And it is carried through the same DRB;
  • the first detection unit 1304 is configured to, when identifying that the data packet sent by the user plane functional entity through the GTP-U tunnel belongs to the sub-packet obtained by splitting the strong-interaction type data packet, In the process of sending the sub-data packet obtained by splitting the data packet to the user equipment based on the DRB, according to the access layer context information, detecting the sending situation of the sub-data packet obtained by splitting the strong-interaction type data packet;
  • the first processing unit 1306 is configured to stop sending the specified type of sub-packets to the user equipment when it is detected that the sub-packets obtained by splitting the strong-interaction data packets of the specified type fail to be sent to the user equipment. The remaining sub-data packets obtained by splitting the strong-interaction type data packet.
  • the first processing unit 1306 is further configured to, when detecting that the sub-packet obtained by splitting the strong-interaction type packet of the specified type fails to be sent to the user equipment, discard the A sub-data packet obtained by splitting the received strong interaction type data packet of the specified type.
  • the first processing unit 1306 is further configured to, when detecting that the sub-packet obtained by splitting the strong-interaction type packet of the specified type fails to be sent to the user equipment, send the packet to the user equipment.
  • the user plane functional entity sends first feedback information, where the first feedback information is used to instruct the user plane functional entity to stop transmitting the strong interaction type data packet of the specified type and split to obtain the remaining sub-data packets.
  • the first processing unit 1306 is configured to send the first processing unit 1306 to the user plane functional entity when all sub-data packets obtained by splitting the specified type of strong-interaction data packets are not fully received. a feedback.
  • the multiple sub-data packets obtained by splitting the strong-interaction type data packet include a start data packet and an end data packet; the start data packet includes first indication information, and the first indication information uses to indicate that the start data packet is the first sub-data packet transmitted in the plurality of sub-data packets; the end data packet includes second indication information, and the second indication information is used to indicate that the end data packet is The last transmitted sub-packet among the plurality of sub-packets.
  • the first detection unit 1304 is further configured to receive the data packet sent by the user plane functional entity through the GTP-U tunnel; identify the data packet according to the indication information in the protocol field of the data packet Whether the data packet belongs to a sub-data packet obtained by splitting the strong interaction type data packet.
  • the first detection unit 1304 is further configured; or, according to the indication information in the payload information of the data packet, identify whether the data packet belongs to the subsection obtained by splitting the strong-interaction type data packet data pack.
  • the first processing unit 1306 is further configured to split all the data packets obtained by splitting the strong-interaction type data packet of the specified type sent by the user plane functional entity and not completely received within a set period of time.
  • a sub-data package is used, stop sending the remaining sub-data packets obtained by splitting the strong-interaction data packet of the specified type to the user equipment, and discard the strong-interaction data of the specified type that has been received. Subpackets obtained from packet splitting.
  • different types of strong interaction data packets include: strong interaction data packets corresponding to key frames and strong interaction data packets corresponding to non-key frames, and the strong interaction data packets of the specified type are: the strong interaction data packet corresponding to the key frame; the first processing unit 1306 is further configured to send a sub-data packet obtained by splitting the strong interaction type data packet corresponding to the key frame to the user equipment When the sending of the key frame fails, perform at least one of the following processing: stop sending the strong-interaction data packet corresponding to the non-key frame associated with the key frame to the user equipment, discard the received the strongly interactive data packet corresponding to the non-key frame associated with the key frame.
  • FIG. 14 shows a block diagram of another data transmission apparatus according to an embodiment of the present application, where the data transmission apparatus may be set inside a user plane functional entity.
  • a data transmission apparatus 1400 includes: a second receiving unit 1402 , a second detecting unit 1404 and a second processing unit 1406 .
  • the second receiving unit 1402 is configured to receive the protocol data unit PDU session management policy information sent by the session management function SMF, where the PDU session management policy information is used to indicate that different types of strongly interactive data packets are respectively in different general packets
  • the wireless service tunneling protocol is transmitted in the user plane GTP-U tunnel, and is carried by the same data radio bearer DRB;
  • the second detection unit 1404 is configured to, according to the PDU session management policy information, transmit sub-data packets obtained by splitting the received strong interaction type data packets of different types to the base station in different GTP-U tunnels respectively. equipment, and detect the sending situation of the sub-data packets obtained by splitting the strong-interaction type data packets;
  • the second processing unit 1406 is configured to stop sending the specified type of sub-packets to the base station equipment when it is detected that the sub-packets obtained by splitting the strong-interaction data packets of the specified type fail to be sent to the base station equipment. The remaining sub-data packets obtained by splitting the strong-interaction type data packet.
  • the second processing unit 1406 is further configured to, when detecting that the sub-data packets obtained by splitting the strong-interaction type data packets of the specified type fail to be sent to the base station device, discard the A sub-data packet obtained by splitting the received strong interaction type data packet of the specified type.
  • the second processing unit 1406 is further configured to, when it is detected that the sub-data packets obtained by splitting the strong-interaction type data packets of the specified type fail to be sent to the base station device, send a message to the application
  • the server sends second feedback information, where the second feedback information is used to instruct the application server to stop transmitting the strong interaction type data packet of the specified type and split to obtain the remaining sub-data packets.
  • the second processing unit 1406 is configured to send the application server to the application server when all sub-data packets obtained by splitting the strong-interaction data packets of the specified type are not completely received. Second feedback information.
  • the second processing unit 1406 is further configured to stop sending all the sub-data packets obtained by splitting the strong-interaction type data packet of the specified type without completely receiving within a set period of time.
  • the base station device sends the remaining sub-data packets obtained by splitting the strong-interaction data packets of the specified type, and discards the received sub-data obtained by splitting the strong-interaction data packets of the specified type. Bag.
  • the different types of the strongly interactive data packets include: the strongly interactive data packets corresponding to key frames and the strongly interactive data packets corresponding to non-key frames, all the specified types of data packets.
  • the strong interaction data packet is the strong interaction data packet corresponding to the key frame;
  • the second processing unit 1406 is further configured to perform at least one of the following processing when detecting that the sub-packet obtained by splitting the strong-interaction type data packet corresponding to the key frame fails to be sent to the base station device: Stop sending the strong-interaction data packet corresponding to the non-key frame associated with the key frame to the base station device, and discard the received non-key frame associated with the key frame. corresponding to the strong interaction type data packet.
  • FIG. 15 shows a block diagram of yet another data transmission apparatus according to an embodiment of the present application, and the data transmission apparatus may be set inside the user equipment.
  • a data transmission apparatus 1500 includes: a third receiving unit 1502 , a third detecting unit 1504 , and a third processing unit 1506 .
  • the third receiving unit 1502 is configured to receive a user equipment routing policy URSP rule sent by the access and mobility management function AMF, where the URSP rule is used to indicate that different types of strongly interactive data packets are stored in different general packet
  • the wireless service tunneling protocol is transmitted in the user plane GTP-U tunnel, and is carried by the same data radio bearer DRB;
  • the third detection unit 1504 is configured to, when identifying that the data packet sent by the base station device based on the DRB belongs to the sub-data packet obtained by splitting the strong-interaction type data packet, receive the sub-data packet obtained by splitting the strong-interaction type data packet In the process of the sub-data packet, according to the URSP rule, detect the reception situation of all sub-data packets obtained by the splitting of the strong interaction type data packet;
  • the third processing unit 1506 is configured to, when it is detected that all the data packets obtained by splitting the strong interaction type data packets of the specified type are not completely received within a set period of time, send the strong interaction type of the specified type to The application server of the type data packet sends transmission failure information, where the transmission failure information is used to indicate to the application server that the transmission of the specified type of the strong interaction type data packet fails.
  • the third processing unit 1506 is further configured to detect that all sub-data packets obtained by splitting the strong-interaction type data packet of the specified type are not completely received within the set period of time , discard the received sub-packets obtained by splitting the strong-interaction type packets of the specified type.
  • the third processing unit 1506 is further configured to, when completely receiving all the data packets obtained by splitting the strong interaction type data packets of the specified type, perform a All the data packets obtained by splitting the interactive data packets are integrated and processed to obtain the strong interactive data packets of the specified type.
  • the different types of the strongly interactive data packets include: the strongly interactive data packets corresponding to key frames and the strongly interactive data packets corresponding to non-key frames, all the specified types of data packets.
  • the strong interaction data packet is the strong interaction data packet corresponding to the key frame.
  • FIG. 16 shows a block diagram of still another data transmission apparatus according to an embodiment of the present application, and the data transmission apparatus may be set inside the PCF.
  • a data transmission apparatus 1600 includes: a fourth receiving unit 1602 , a generating unit 1604 , a first sending unit 1606 and a second sending unit 1608 .
  • the fourth receiving unit 1602 is configured to receive GTP-U tunnel configuration information on the user plane of the General Packet Radio Service Tunneling Protocol for strongly interactive data packets sent by the application function AF, where the GTP-U tunnel configuration information is used to indicate that no Types of strongly interactive data packets are transmitted in different GTP-U tunnels, and are carried by the same data radio bearer DRB;
  • the generating unit 1604 is configured to generate user equipment routing policy URSP rules and protocol data unit PDU session management policy information according to the GTP-U tunnel configuration information, where the URSP rules and the PDU session management policy information are used to indicate different types
  • the strongly interactive data packets are transmitted in different GTP-U tunnels respectively, and are carried by the same DRB;
  • the first sending unit 1606 is configured to forward the URSP rule to the user equipment through the access and mobility management function AMF, and configure access stratum context information to the base station equipment according to the URSP rule, the access stratum context information is used to indicate that the strong interaction type data packets of different types are transmitted in different GTP-U tunnels respectively, and are carried by the same DRB;
  • the second sending unit 1608 is configured to configure the PDU session management policy information to the user plane functional entity through the session management function SMF.
  • the different types of the strongly interactive data packets include: the strongly interactive data packets corresponding to key frames and the strongly interactive data packets corresponding to non-key frames, the strong interactive data packets of a specified type
  • the interaction data packet is the strong interaction data packet corresponding to the key frame.
  • FIG. 17 shows a schematic structural diagram of an electronic device according to an embodiment of the present application.
  • a computer system 1700 includes a Central Processing Unit (CPU) 1701 (referred to as one or more processors), which may be stored in a Read-Only Memory (ROM) 1702 according to The program from the storage part 1708 or the program loaded into the random access memory (Random Access Memory, RAM) 1703 from the storage part 1708 executes various appropriate actions and processes, such as executing the methods described in the above embodiments. In the RAM 1703, various programs and data necessary for system operation are also stored.
  • the CPU 1701, the ROM 1702, and the RAM 1703 are connected to each other through a bus 1704.
  • An Input/Output (I/O) interface 1705 is also connected to the bus 1704 .
  • I/O Input/Output
  • the following components are connected to the I/O interface 1705: an input section 1706 including a keyboard, a mouse, etc.; an output section 1707 including a cathode ray tube (CRT) and a liquid crystal display (LCD), etc., and a speaker, etc. ; a storage part 1708 including a hard disk and the like; and a communication part 1709 including a network interface card such as a LAN (Local Area Network) card and a modem.
  • the communication section 1709 performs communication processing via a network such as the Internet.
  • Drivers 1710 are also connected to I/O interface 1705 as needed.
  • Removable media 1711 such as magnetic disks, optical disks, magneto-optical disks, and semiconductor memories, etc., are mounted on the drive 1710 as needed so that computer programs read therefrom are installed into the storage section 1708 as needed.
  • the data processing methods provided by the embodiments of the present application may be implemented as computer software programs.
  • the embodiments of the present application include a computer program product, which includes a computer program carried on a computer-readable storage medium, where the computer program includes a computer program for executing the data processing method provided by the embodiments of the present application.
  • the computer program can be downloaded and installed from the network through the communication section 1709, and/or installed from the removable medium 1711.
  • the central processing unit (CPU) 1701 the data processing methods provided by the embodiments of the present application are executed.
  • Computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or device, or any combination of the above.
  • Computer readable storage media may include, but are not limited to, electrical connections with one or more wires, portable computer disks, hard disks, random access memory (RAM), read only memory (ROM), erasable programmable read only memory ( Erasable Programmable Read Only Memory, EPROM), flash memory, optical fiber, portable compact disk read-only memory (Compact Disc Read-Only Memory, CD-ROM), optical storage device, magnetic storage device, or any suitable combination of the above.
  • the computer-readable storage medium may be any tangible medium containing or storing a program, and the program may be used by or in combination with an instruction execution system, apparatus, or device.
  • the computer-readable storage medium may also be a computer-readable signal medium, that is, a data signal included in a baseband or propagated as part of a carrier wave, and carrying a computer-readable computer program. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the foregoing.
  • a computer-readable storage medium can be any computer-readable medium that can transmit, propagate, or transport a program for use by or in connection with the instruction execution system, apparatus, or device.
  • a computer program embodied on a computer-readable storage medium may be transmitted using any suitable medium, including, but not limited to, wireless and wired, and the like, or any suitable combination of the foregoing.
  • each block in the flowchart or block diagram may represent a module, program segment, or part of code, and the above-mentioned module, program segment, or part of code contains one or more executables for realizing the specified logical function instruction.
  • the functions noted in the blocks may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved.
  • the units involved in the embodiments of the present application may be implemented in a software manner, or may be implemented in a hardware manner, and the described units may also be provided in a processor. Among them, the names of these units do not constitute a limitation on the unit itself under certain circumstances.
  • Embodiments of the present application also provide a computer-readable storage medium, which may be included in the electronic device described in the foregoing embodiments; or may exist alone without being assembled into the electronic device .
  • the aforementioned computer-readable medium carries one or more programs, and when the aforementioned one or more programs are executed by an electronic device, the electronic device enables the electronic device to implement the data transmission method described in the embodiments of the present application.
  • modules or units of the electronic device for action execution are mentioned in the description of the embodiments of the present application, such division is not mandatory.
  • the features and functions of two or more modules or units described in the embodiments of the present application may be embodied in one module or unit.
  • the features and functions of a module or unit described in the embodiments of this application may be further divided into multiple modules or units to be embodied.
  • the data processing method provided according to the embodiment of the present application may be embodied in the form of a software product, and the software product may be stored in a non-volatile storage medium (which may be a CD-ROM, a USB flash drive, a mobile hard disk, etc. ) or on the network, including several instructions to cause a computing device (which may be a personal computer, a server, a touch terminal, or a network device, etc.) to execute the data processing method provided by the embodiments of the present application.
  • a non-volatile storage medium which may be a CD-ROM, a USB flash drive, a mobile hard disk, etc.
  • a computing device which may be a personal computer, a server, a touch terminal, or a network device, etc.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)

Abstract

一种数据传输方法、装置、计算机可读存储介质、电子设备及计算机程序产品。该数据传输方法包括：接收AMF发送的接入层上下文信息，接入层上下文信息用于指示不同类型的强交互型数据包分别在不同的GTP-U隧道中进行传输，且通过同一个DRB进行承载；当识别到用户面功能实体通过GTP-U隧道发送的数据包属于强交互型数据包拆分得到的子数据包时，在将强交互型数据包拆分得到的子数据包基于DRB发送至用户设备的过程中，根据接入层上下文信息，当检测到指定类型的强交互型数据包拆分得到的子数据包向用户设备的发送失败时，停止向用户设备发送指定类型的强交互型数据包拆分得到的其余子数据包。

Description

一种数据传输方法、装置、计算机可读存储介质、电子设备及计算机程序产品
相关申请的交叉引用
本申请基于申请号为202110004590.5、申请日为2021年01月04日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此引入本申请作为参考。
技术领域
本申请涉及计算机及通信技术领域，涉及一种数据传输方法、装置、计算机可读存储介质、电子设备及计算机程序产品。
背景技术
在通信领域中，比如，第五代移动通信技术(5th-Generation，5G)以及演进5G系统中，高带宽的强交互型业务是重要的业务类型，诸如云游戏(Cloud Gaming)、虚拟现实(Virtual Reality，VR)、增强现实(Augmented Reality，AR)、混合现实(Mixed Reality，MR)、扩展现实(Extended Reality，XR)、影像现实(Cinematic Reality，CR)等；这些强交互型业务不仅对传输的时效性要求很高，而且随着分辨率、帧率和自由度等指标的提高，应用层产生的数据量极大增长，给网络传输带来很大的负荷。
一般来说，为了传输强交互型业务的应用层生成的数据包，通常将数据包切割成大量子数据包分段传输；然而，上述传输强交互型业务的数据包的过程中，当其中一个子数据包的传输失败时，则整个数据包内容就无法在接收端进行实时的恢复和呈现，从而对无法满足强交互型的高带宽和低时延的需求。
发明内容
本申请实施例提供了一种数据传输方法、装置、计算机可读存储介质、电子设备及计算机程序产品，能够降低数据包的传输时延和传输资源消耗。
本申请实施例提供了一种数据传输方法，包括：
接收接入与移动性管理功能(Access and Mobility Management Function，AMF)发送的接入层上下文信息，所述接入层上下文信息用于指示不同类型的强交互型数据包分别在不同的通用分组无线业务隧道协议用户面(General Packet Radio Service Tunnel Protocol User，GTP-U)隧道中进行传输，且通过同一个数据无线承载(Data Radio Bearer，DRB)进行承载；
当识别到用户面功能实体通过所述GTP-U隧道发送的数据包属于所述强交互型数据包拆分得到的子数据包时，在将所述强交互型数据包拆分得到的子数据包基于所述DRB发送至用户设备的过程中，根据所述接入层上下文信息，检测所述强交互型数据包拆分得到的子数据包的发送情况；
当检测到指定类型的所述强交互型数据包拆分得到的子数据包向所述用户设备的发送失败时，停止向所述用户设备发送所述指定类型的所述强交互型数据包拆分得到的 其余子数据包。
本申请实施例提供了另一种数据传输方法，包括：
接收会话管理功能(Session Management Function，SMF)发送的协议数据单元(Protocol Data Unit，PDU)会话管理策略信息，所述PDU会话管理策略信息用于指示不同类型的强交互型数据包分别在不同的GTP-U隧道中进行传输，且通过同一个DRB进行承载；
根据PDU会话管理策略信息，将接收到的不同类型的所述强交互型数据包拆分得到的子数据包分别在不同的所述GTP-U隧道中传输至基站设备，并检测所述强交互型数据包拆分得到的子数据包的发送情况；
当检测到指定类型的所述强交互型数据包拆分得到的子数据包向所述基站设备的发送失败时，停止向所述基站设备发送所述指定类型的所述强交互型数据包拆分得到的其余子数据包。
本申请实施例提供了又一种数据传输方法，包括：
接收AMF发送的用户设备路由选择策略(UE Route Selection Policy，URSP)规则，所述URSP规则用于指示不同类型的强交互型数据包分别在不同的GTP-U隧道中进行传输，且通过同一个DRB进行承载；
当识别到基站设备基于所述DRB发送的数据包属于所述强交互型数据包拆分得到的子数据包时，在接收所述强交互型数据包拆分得到的子数据包的过程中，根据所述URSP规则，检测所述强交互型数据包拆分得到的所有子数据包的接收情况；
当检测到在设定时长内未完整接收到指定类型的所述强交互型数据包拆分得到的所有数据包时，向发送所述指定类型的所述强交互型数据包的应用服务器发送传输失败信息，所述传输失败信息用于向所述应用服务器指示所述指定类型的所述强交互型数据包的传输失败。
本申请实施例提供了再一种数据传输方法，包括：
接收应用功能(Application Function，AF)发送的针对强交互型数据包的GTP-U隧道配置信息，所述GTP-U隧道配置信息用于指示不类型的强交互型数据包分别在不同的GTP-U隧道中进行传输，且通过同一个DRB进行承载；
根据所述GTP-U隧道配置信息生成用户设备路由选择策略URSP规则和协议数据单元PDU会话管理策略信息，所述URSP规则和所述PDU会话管理策略信息用于指示不同类型的所述强交互型数据包分别在不同的所述GTP-U隧道中进行传输，且不同类型的所述强交互型数据包通过同一个所述DRB进行承载；
将所述URSP规则通过接入与AMF转发至用户设备，并根据所述URSP规则向基站设备配置接入层上下文信息，所述接入层上下文信息用于指示不同类型的所述强交互型数据包分别在不同的所述GTP-U隧道中进行传输，且不同类型的所述强交互型数据包通过同一个所述DRB进行承载；
将所述PDU会话管理策略信息通过SMF配置给用户面功能实体。
本申请实施例提供了一种数据传输装置，包括：
第一接收单元，配置为接收AMF发送的接入层上下文信息，所述接入层上下文信息用于指示不同类型的强交互型数据包分别在不同的GTP-U隧道中进行传输，且通过同一个DRB进行承载；
第一检测单元，配置为当识别到用户面功能实体通过所述GTP-U隧道发送的数据包属于所述强交互型数据包拆分得到的子数据包时，在将所述强交互型数据包拆分得到的子数据包基于所述DRB发送至用户设备的过程中，根据所述接入层上下文信息，检测所述强交互型数据包拆分得到的子数据包的发送情况；
第一处理单元，配置为当检测到指定类型的所述强交互型数据包拆分得到的子数据包向所述用户设备的发送失败时，停止向所述用户设备发送所述指定类型的所述强交互型数据包拆分得到的其余子数据包。
本申请实施例提供了另一种数据传输装置，包括：
第二接收单元，配置为SMF发送的PDU会话管理策略信息，所述PDU会话管理策略信息用于指示不同类型的强交互型数据包分别在不同的GTP-U隧道中进行传输，且通过同一个DRB进行承载；
第二检测单元，配置为根据PDU会话管理策略信息，将接收到的不同类型的所述强交互型数据包拆分得到的子数据包分别在不同的所述GTP-U隧道中传输至基站设备，并检测所述强交互型数据包拆分得到的子数据包的发送情况；
第二处理单元，配置为当检测到指定类型的所述强交互型数据包拆分得到的子数据包向所述基站设备的发送失败时，停止向所述基站设备发送所述指定类型的所述强交互型数据包拆分得到的其余子数据包。
本申请实施例提供了又一种数据传输装置，包括：
第三接收单元，配置为接收AMF发送的用户设备路由选择策略URSP规则，所述URSP规则用于指示不同类型的强交互型数据包分别在不同的GTP-U隧道中进行传输，且通过同一个DRB进行承载；
第三检测单元，配置为当识别到基站设备基于所述DRB发送的数据包属于所述强交互型数据包拆分得到的子数据包时，在接收所述强交互型数据包拆分得到的子数据包的过程中，根据所述URSP规则，检测所述强交互型数据包拆分得到的所有子数据包的接收情况；
第三处理单元，配置为检测到当在设定时长内未完整接收到指定类型的所述强交互型数据包拆分得到的所有数据包时，向发送所述指定类型的所述强交互型数据包的应用服务器发送传输失败信息，所述传输失败信息用于向所述应用服务器指示所述指定类型的所述强交互型数据包的传输失败。
本申请实施例提供了再一种数据传输装置，包括：
第四接收单元，配置为接收AF发送的针对强交互型数据包的GTP-U隧道配置信息，所述GTP-U隧道配置信息用于指示不类型的强交互型数据包分别在不同的GTP-U隧道中进行传输，且通过同一个DRB进行承载；
生成单元，配置为根据所述GTP-U隧道配置信息生成用户设备路由选择策略URSP规则和PDU会话管理策略信息，所述URSP规则和所述PDU会话管理策略信息用于指示不同类型的所述强交互型数据包分别在不同的所述GTP-U隧道中进行传输，且通过同一个所述DRB进行承载；
第一发送单元，配置为将所述URSP规则通过接入与AMF转发至用户设备，并根据所述URSP规则向基站设备配置接入层上下文信息，所述接入层上下文信息用于指示不同类型的所述强交互型数据包分别在不同的所述GTP-U隧道中进行传输，且通过同一个所述DRB进行承载；
第二发送单元，配置为将所述PDU会话管理策略信息通过SMF配置给用户面功能实体。
本申请实施例提供了一种计算机可读存储介质，其上存储有计算机程序，所述计算机程序被一个或多个处理器执行时，实现本申请实施例提供的数据传输方法。
本申请实施例提供了一种电子设备，包括：
一个或多个处理器；
存储装置，用于存储一个或多个程序，当所述一个或多个程序被所述一个或多个处 理器执行时，实现本申请实施例提供的数据传输方法。
本申请实施例提供了一种计算机程序产品，所述计算机程序产品包括计算机程序或计算机指令，所述算机程序或计算机指令被一个或多个处理器执行时，实现本申请实施例提供的数据传输方法。
本申请实施例至少具有以下有益效果：通过将强交互型数据包(即为强交互型业务的数据包)拆分为子数据包并对子数据包进行分类，以在子数据包向用户设备发送失败时，停止向用户设备发送指定类型的强交互型数据包拆分得到的其余子数据包；也就是说，在存在子数据包发送失败的情况下，能够及时停止发送无效子数据包；因此，能够降低数据包传输时延和传输资源消耗。
附图说明
图1示出了本申请实施例的示例性系统架构的示意图；
图2示出了本申请实施例的一个强交互型数据包的传输过程示意图；
图3示出了本申请实施例的一个数据传输方法的流程图；
图4示出了本申请实施例的强交互型数据包的划分结构示意图；
图5示出了本申请实施例的另一个数据传输方法的流程图；
图6示出了本申请实施例的又一个数据传输方法的流程图；
图7示出了本申请实施例的再一个数据传输方法的流程图；
图8示出了本申请实施例的另一个强交互型数据包的传输过程示意图；
图9示出了本申请实施例的控制面的配置流程图；
图10示出了本申请实施例提供的一种示例性的的数据传输方法的流程示意图；
图11示出了本申请实施例提供的另一种示例性的的数据传输方法的流程示意图；
图12示出了本申请实施例提供的又一种示例性的的数据传输方法的流程示意图；
图13示出了本申请实施例的一个数据传输装置的框图；
图14示出了本申请实施例的另一个数据传输装置的框图；
图15示出了本申请实施例的又一个数据传输装置的框图；
图16示出了本申请实施例的再一个数据传输装置的框图；
图17示出了本申请实施例的电子设备的结构示意图。
具体实施方式
需要说明的是，在本申请实施例中提及的“多个”是指两个或两个以上。“和/或”描述关联对象的关联关系，表示可以存在三种关联关系，例如，A和/或B可以表示：单独存在A，同时存在A和B，单独存在B这三种关联关系。字符“/”一般表示前后关联对象是一种“或”的关系。
随着通信领域(比如，4G(4th-Generation，第四代移动通信技术)，5G，等等)的发展，使得许多要求大数据量和短时延的业务得到了应用。比如云游戏业务、VR、AR、MR、XR和CR等交互业务，也可以称之为强交互服务(Advanced Interactive Service，AIS)业务，并在本申请实施例中将强交互服务业务的数据包称为强交互型数据包。
比如，在图1所示的云游戏场景中，云端服务器101用于运行云游戏，云端服务器101可以对游戏画面进行渲染，并将音频信号及渲染后的图像进行编码处理，最后将编码处理得到的编码数据通过网络传输至各个游戏客户端(示例性地示出了游戏客户端1-21、游戏客户端1-22、游戏客户端1-23和游戏客户端1-24)。游戏客户端可以是具有 基本的流媒体播放能力、人机交互能力以及通信能力等的用户设备(User Equipment，UE)，例如，智能手机、平板电脑、笔记本电脑、台式计算机、智能电视、机顶盒、智能车载设备、便携式音乐播放器、个人数字助理、专用消息设备、便携式游戏设备和智能音箱等；或者该游戏客户端还可以是运行于终端设备中的应用程序，比如，操作系统中的原生程序或软件模块，本地(Native)应用程序(APP，Application)，即需要在操作系统中安装才能运行的程序(游戏APP)；小程序，即只需要下载到浏览器环境中就可以运行的程序，能够嵌入至任意APP中的小程序。
在本申请实施例中，游戏客户端可以将云端服务器101传输的编码数据进行解码，得到模拟音视频信号，并进行播放。应理解的是，图1中只是示例性的表征云游戏系统的系统架构，并不对云游戏系统的具体架构进行限定；例如，云游戏系统中还可以包括用于调度的后台服务器，等等。并且云端服务器101可以是独立的物理服务器，也可以是多个物理服务器构成的服务器集群或者分布式系统，还可以是提供云服务、云数据库、云计算、云函数、云存储、网络服务、云通信、中间件服务、域名服务、安全服务、内容分发网络(Content Delivery Network，CDN)、以及大数据和人工智能平台等基础云计算服务的云服务器。游戏客户端以及云端服务器101可以通过有线或无线通信方式进行直接或间接地连接，本申请在此不做限制。
在各种强交互业务的应用场景中，由于强交互型数据包巨大，因此在传输时需要拆分为多个子数据包。也就是说，如图2所示，比如，在5G系统中，用户面主要包括应用服务器、用户面功能(User Plane Function，UPF)、基站(next generation NodeB，简称gNB)和用户设备。强交互型数据包的传输对于一些业务场景主要在下行方向，比如从应用服务器到UPF，然后再通过gNB发送给UE。在进行传输时，强交互型数据包2-1在应用服务器的应用层进行拆分，拆分后的子数据包2-2，作为网际互联协议(Internet Protocol，IP)包从应用服务器到达UPF后，5G系统通过PDU会话把子数据包传输到UE端，在UE端的应用层从协议栈逐级向上递交并进行重组(图中示出了重组前的子数据包2-3)恢复出该强交互型数据包2-1。
其中，在图2所示的系统中，应用服务器包括L1层、L2层和IP层；用户面功能包括L1层、L2层、用户数据报协议(User Datagram Protocol，UDP)/IP、通用分组无线业务隧道协议用户面和IP层；基站包括L1层、L2层、UDP/IP、GTP-U、物理层(Physical，PHY)、媒体访问控制层(Media Access Control，MAC)、无线链路控制层协议层(Radio Link Control，RLC)、分组数据汇聚协议层(Packet Data Convergence Protocol，PDCP)、服务数据适配协议层(Service Data Adaptation Protocol，SDAP)和IP层；用户设备包括PHY层、MAC层、RLC层、PDCH层、SDAP层和IP层。其中，L1层是指物理层，其用于确保原始的数据可在各种物理媒体上传输；L2层指的是数据链路层，数据链路层在物理层提供的服务的基础上向网络层提供服务；IP层即为网络层，用于实现两个端系统之间的数据传送。
在各种强交互业务的应用场景中，应用层生成的强交互型数据包需要以很低的时延和切割成大量子数据包分段传输，一旦其中一个子数据包的传输未满足传输要求，则整个强交互型数据包就无法在接收端进行实时的恢复和呈现，从而无法满足强交互性高带宽业务的需求。在这种情况下，大量子数据包分段的传输其实是浪费了网络资源。比如，一个强交互型数据包被拆分为10个子数据包(甚至更多个子数据包)，每个子数据包传输成功的概率为0.99，那么这10个子数据包全部传输成功的概率为0.99 10，即为0.904。可见，在将一个强交互型数据包拆分为多个子数据包时，即便每个子数据包传输成功的概率很大，那么整个强交互型数据包拆分得到的所有子数据包都传输成功的概率也会大打折扣。而且，如果某个子数据包传输失败，那么将导致接收方不能恢复出强交互型数 据包，在这种情况下，继续传输强交互型数据包拆分得到的子数据包已经没有意义了，基于此，本申请实施例提供了一种数据传输方法、装置、计算机可读存储介质、电子设备及计算机程序产品，能够降低数据包的传输时延和传输资源消耗。
图3示出了本申请实施例的一个数据传输方法的流程图，该数据传输方法可以由基站设备来执行。参照图3所示，该数据传输方法至少包括S310至S330，下面对各步骤分别进行说明。
在S310中，接收AMF发送的接入层上下文信息，接入层上下文信息用于指示不同类型的强交互型数据包分别在不同的GTP-U隧道中进行传输，且通过同一个DRB进行承载。
需要说明的是，如果基站是由控制面与用户面分离的，即基站分离为基站集中单元(gNB Centralized Unit，gNB-CU)和基站分布单元(gNB Distributed Unit，gNB-DU)，且gNB-CU作为控制面，gNB-DU作为用户面，那么本申请实施例中的基站设备可以是gNB-DU。
在本申请实施例中，强交互型数据包的类型可以是根据需要传输的业务内容的类型和优先级等来确定的。比如，强交互型数据包的类型可以包括关键帧和非关键帧，其中，关键帧可以是帧内编码帧(Intra Picture，I帧)，非关键帧可以是前向预测编码帧(Predictive Frame，P帧)和/或双向预测内插编码帧(Bi-Directional Interpolated Prediction Frame，B帧)。
在本申请实施例中，多种类型的强交互型数据包分别在不同的GTP-U隧道中进行传输可以是：一种类型的强交互型数据包在一个GTP-U隧道中进行传输，并且不同类型的强交互型数据包在传输时采用的GTP-U隧道不相同。
在S320中，当识别到用户面功能实体通过GTP-U隧道发送的数据包属于强交互型数据包拆分得到的子数据包时，在将强交互型数据包拆分得到的子数据包基于DRB发送至用户设备的过程中，根据接入层上下文信息，检测强交互型数据包拆分得到的子数据包的发送情况。
在本申请实施例中，用户面功能实体在不同的GTP-U隧道中传输不同类型的强交互型数据包，即不同类型的强交互型数据包在传输时所采用的GTP-U隧道不相同。基站设备可以在不同的GTP-U隧道中接收用户面功能实体发送的数据包，并且在接收到数据包之后还可以识别出该数据包是否是强交互型数据包拆分得到的子数据包。可选地，基站设备还可以根据接收到强交互型数据包拆分得到的子数据包的GTP-U隧道来识别是哪个类型的强交互型数据包，比如可以将GTP-U隧道的标识信息与强交互型数据包的类型进行对应，然后根据接收到强交互型数据包拆分得到的子数据包的GTP-U隧道的标识信息，确定接收到的是哪个类型的强交互型数据包。
在本申请实施例中，假设有两种类型的强交互型数据包，即关键帧对应的强交互型数据包和非关键帧对应的强交互型数据包，那么用户面功能实体可以在两个GTP-U隧道中分别传输这两种类型的强交互型数据包；可以是在一个GTP-U隧道中传输关键帧对应的强交互型数据包拆分得到的子数据包，在另一个GTP-U隧道中传输非关键帧对应的强交互型数据包拆分得到的子数据包。
在本申请实施例中，强交互型数据包拆分得到的多个子数据包中包含有开始数据包和结束数据包。开始数据包中包含有第一指示信息，该第一指示信息用于指示开始数据包是多个子数据包中第一个传输的子数据包；结束数据包中包含有第二指示信息，该第二指示信息用于指示结束数据包是多个子数据包中最后一个传输的子数据包。
在本申请实施例中，基站设备通过对开始数据包和结束数据包的识别来确定是否接收到强交互型数据包拆分得到的子数据包。比如，若基站设备根据开始数据包中包含的 第一指示信息识别到该开始数据包，那么从开始数据包到结束数据包之间所接收到的数据包都属于强交互型数据包拆分得到的子数据包。
在本申请实施例中，基站设备可以根据接收到的数据包的协议字段中包含的指示信息，识别接收到的数据包是否属于强交互型数据包拆分得到的子数据包。
需要说明的是，强交互型数据包拆分得到的多个子数据包中的开始数据包在协议字段中添加有用于指示其为开始数据包的指示信息，而结束数据包在协议字段中添加有用于指示其为结束数据包的指示信息；那么基站设备在根据数据包的协议字段识别到该开始数据包之后，从开始数据包到结束数据包之间所接收到的数据包都属于强交互型数据包拆分得到的子数据包。
在本申请实施例中，基站设备可以根据接收到的数据包的净荷信息中包含的指示信息，识别接收到的数据包是否属于强交互型数据包拆分得到的子数据包。
需要说明的是，比如强交互型数据包拆分得到的多个子数据包中的开始数据包在净荷信息中添加有用于指示其为开始数据包的指示信息，而结束数据包在净荷信息中添加有用于指示其为结束数据包的指示信息，那么在根据数据包的净荷信息识别到该开始数据包之后，从开始数据包到结束数据包之间的数据包都属于强交互型数据包拆分得到的子数据包。
继续参照图3，在S330中，当检测到指定类型的强交互型数据包拆分得到的子数据包向用户设备的发送失败时，停止向用户设备发送指定类型的强交互型数据包拆分得到的其余子数据包。
在本申请实施例中，如果基站设备检测到指定类型的强交互型数据包拆分得到的子数据包为向用户设备发送失败的子数据包，那么此时如果继续发送该指定类型的强交互型数据包拆分得到的其余子数据包也不能恢复出该指定类型的强交互型数据包，因此，基站设备可以停止向用户设备发送其余子数据包，以降低对带宽的占用，有利于减少强交互型数据包在传输时对传输资源的占用。
在本申请实施例中，如果一个强交互型数据包拆分得到的子数据包为向用户设备发送失败的子数据包，那么这个强交互型数据包即为指定类型的强交互型数据包。换句话说，指定类型的强交互型数据包就是存在发送失败的子数据包的强交互型数据包。其中，指定类型为多种类型中的任意一种类型。
在本申请实施例中，当不同类型的强交换型数据包包括两种类型的强交互型数据包时，且两种类型的强交互型数据包即为关键帧对应的强交互型数据包和非关键帧对应的强交互型数据包。如果非关键帧对应的强交互型数据包在发送时存在发送失败的子数据包，那么非关键帧对应的强交互型数据包即为指定类型的强交互型数据包；如果关键帧对应的强交互型数据包在发送时存在发送失败的子数据包，那么关键帧对应的强交互型数据包即为指定类型的强交互型数据包。
在本申请实施例中，基站设备在检测强交互型数据包拆分得到的子数据包是否是向用户设备发送失败的子数据包时，可以针对多种类型的强交互型数据包拆分得到的子数据包分别进行检测，并且多种类型的强交互型数据包拆分得到的子数据包的检测过程相互之间不影响。同时，多种类型的强交互型数据包拆分得到的子数据包的传输过程也可以是相互不影响的；比如，如果某个类型的强交互型数据包拆分得到的子数据包向用户设备的发送失败，那么可以停止向用户设备发送该指定类型的强交互型数据包拆分得到的其余子数据包，但是这个过程并不影响对其它类型的强交互型数据包拆分得到的子数据包的发送，也就是说，其它类型的强交互型数据包拆分得到的子数据包可以继续发送。
在本申请实施例中，基站设备如果检测到指定类型的强交互型数据包拆分得到的子数据包向用户设备的发送失败，那么还可以丢弃已经接收到的该指定类型的强交互型数 据包拆分得到的子数据包，以降低存储资源的占用。
在本申请实施例中，基站设备如果检测到指定类型的强交互型数据包拆分得到的子数据包向用户设备的发送失败，那么可以向用户面功能实体发送第一反馈信息，该第一反馈信息用于指示用户面功能实体停止传输指定类型的强交互型数据包拆分得到的其余子数据包。
可以理解的是，基站设备在检测到向用户设备发送指定类型的强交互型数据包的过程中存在发送失败的子数据包时，可以向用户面功能实体发送第一反馈信息，以指示用户面功能实体停止传输指定类型的强交互型数据包拆分得到的其余子数据包，以减少对传输资源的占用。
在本申请实施例中，基站设备向用户面功能实体发送第一反馈信息是在未完整接收到该指定类型的强交互型数据包拆分得到的所有子数据包的情况下进行的；如果已经完整接收到指定类型的强交互型数据包拆分得到的所有子数据包，那么无需再向用户面功能实体发送第一反馈信息。
在本申请实施例中，基站设备如果在设定时长内未完整接收到用户面功能实体发送的指定类型的强交互型数据包拆分得到的所有子数据包，则停止向用户设备发送该指定类型的强交互型数据包拆分得到的其余子数据包，并丢弃已经接收到的该指定类型的强交互型数据包拆分得到的子数据包。
需要说明的是，强交互型数据包可以是具有时限要求的数据包，基站设备如果在设定时长内没有完整接收到用户面功能实体发送的指定类型的强交互型数据包拆分得到的所有子数据包，那么说明指定类型的强交互型数据包已经超过了时限要求，此时基站设备已经没有必要再传输指定类型的强交互型数据包拆分得到的其余子数据包给用户设备了。当然，如果在设定时长内没有完整接收到用户面功能实体发送的指定类型的强交互型数据包拆分得到的所有子数据包，还可能是由于用户面功能实体检测到有子数据包传输错误然后停止发送了，此时也说明基站设备没有必要再传输指定类型的强交互型数据包拆分得到的其余子数据包给用户设备了，在这种情况下也可以停止向用户设备发送指定类型的强交互型数据包拆分得到的其余子数据包，并且可以丢弃已经接收到的指定类型的强交互型数据包拆分得到的子数据包。
在本申请实施例中，如图4所示，多种类型的强交互型数据包4-1可以包括：关键帧(即图4中所示的I帧)对应的强交互型数据包和非关键帧(即图4中所示的P帧)对应的强交互型数据包。
需要说明的是，由于非关键帧的恢复需要依赖于关键帧，因此，基站设备如果检测到关键帧对应的强交互型数据包所拆分得到的子数据包向用户设备的发送失败，则停止向用户设备发送与指定关键帧相关联的非关键帧所对应的强交互型数据包，和/或丢弃已经接收到的与指定关键帧相关联的非关键帧所对应的强交互型数据包。
可以理解的是，基站设备在关键帧对应的强交互型数据包拆分得到的子数据包发送失败时，不仅停止传输该关键帧对应的强交互型数据包拆分得到的其余子数据包，而且停止与该指定关键帧相关联的非关键帧所对应的强交互型数据包；也就是说，基站设备停止该关键帧相关联的非关键帧所对应的强交互型数据包拆分得到的其余子数据包的传输；如此，可以降低无效子数据包对带宽的占用，有利于减少强交互型数据包在传输时对传输资源的占用。
图3是从基站设备的角度对本申请实施例的数据传输方法进行了阐述，以下从用户面功能实体的角度对本申请实施例的数据传输方法进行说明。
图5示出了本申请实施例的另一个数据传输方法的流程图，该数据传输方法可以由用户面功能实体来执行。参照图5所示，该数据传输方法至少包括S510至S530，下面 对各步骤分别进行说明。
在S510中，接收SMF发送的PDU会话管理策略信息，PDU会话管理策略信息用于指示不同类型的强交互型数据包分别在不同的GTP-U隧道中进行传输，且通过同一个DRB进行承载。
在本申请实施例中，强交互型数据包的类型可以是根据需要传输的业务内容的类型和优先级等来确定的。比如，强交互型数据包的类型可以包括关键帧和非关键帧，其中，关键帧可以是I帧，非关键帧可以是P帧和/或B帧。
在S520中，根据PDU会话管理策略信息，将接收到的不同类型的强交互型数据包拆分得到的子数据包分别在不同的GTP-U隧道中传输至基站设备，并检测强交互型数据包拆分得到的子数据包的发送情况。
在本申请实施例中，强交互型数据包拆分得到的多个子数据包中包含有开始数据包和结束数据包。开始数据包中包含有第一指示信息，该第一指示信息用于指示开始数据包是多个子数据包中第一个传输的子数据包；结束数据包中包含有第二指示信息，该第二指示信息用于指示结束数据包是多个子数据包中最后一个传输的子数据包。
可以理解的是，用户面功能实体通过对开始数据包和结束数据包的识别来确定是否接收到强交互型数据包拆分得到的子数据包。比如，若用户面功能实体根据开始数据包中包含的第一指示信息识别到该开始数据包，那么从开始数据包到结束数据包之间的数据包都属于强交互型数据包拆分得到的子数据包。
在本申请实施例中，用户面功能实体可以根据接收到的数据包的协议字段中包含的指示信息，识别接收到的数据包是否属于强交互型数据包拆分得到的子数据包。
需要说明的是，强交互型数据包拆分得到的多个子数据包中的开始数据包在协议字段中添加有用于指示其为开始数据包的指示信息，而结束数据包在协议字段中添加有用于指示其为结束数据包的指示信息；那么用户面功能实体在根据数据包的协议字段识别到该开始数据包之后，从开始数据包到结束数据包之间所接收到的数据包都属于强交互型数据包拆分得到的子数据包。
在本申请实施例中，用户面功能实体可以根据接收到的数据包的净荷信息中包含的指示信息，识别接收到的数据包是否属于强交互型数据包拆分得到的子数据包。
需要说明的是，比如强交互型数据包拆分得到的多个子数据包中的开始数据包在净荷信息中添加有用于指示其为开始数据包的指示信息，而结束数据包在净荷信息中添加有用于指示其为结束数据包的指示信息，那么在根据数据包的净荷信息识别到该开始数据包之后，从开始数据包到结束数据包之间所接收到的数据包都属于强交互型数据包拆分得到的子数据包。
在S530中，当检测到指定类型的强交互型数据包拆分得到的子数据包向基站设备的发送失败时，停止向基站设备发送指定类型的强交互型数据包拆分得到的其余子数据包。
在本申请实施例中，用户面功能实体如果检测到指定类型的强交互型数据包拆分得到的子数据包为向基站设备发送失败的子数据包，那么此时如果继续发送该指定类型的强交互型数据包拆分得到的其余子数据包已经没有意义了；因此，用户面功能实体可以停止向基站设备发送其余子数据包，以降低对带宽的占用，有利于减少强交互型数据包在传输时对传输资源的占用。
在本申请实施例中，用户面功能实体如果检测到指定类型的强交互型数据包拆分得到的子数据包为向基站设备发送失败的子数据包，那么还可以丢弃已经接收到的该指定类型的强交互型数据包拆分得到的子数据包，以降低存储资源的占用。
在本申请实施例中，用户面功能实体如果检测到指定类型的强交互型数据包拆分得 到的子数据包为向基站设备发送失败的子数据包，那么可以向应用服务器发送第二反馈信息，该第二反馈信息用于指示应用服务器停止传输强交互型数据包拆分得到的其余子数据包。
可以理解的是，用户面功能实体在检测到向基站设备发送指定类型的强交互型数据包的过程中存在发送失败的子数据包时，可以向应用服务器发送第二反馈信息，以指示应用服务器停止传输其余的子数据包，以减少对传输资源的占用。
在本申请实施例中，用户面功能实体向应用服务器发送第二反馈信息是在未完整接收到该指定类型的强交互型数据包拆分得到的所有子数据包的情况下进行的；如果已经完整接收到指定类型的强交互型数据包拆分得到的所有子数据包，那么无需再向应用服务器发送第二反馈信息。
在本申请实施例中，用户面功能实体如果在设定时长内未完整接收到应用服务器发送的指定类型的强交互型数据包拆分得到的所有子数据包，则停止向基站设备发送该指定类型的强交互型数据包拆分得到的其余子数据包，并丢弃已经接收到的该指定类型的强交互型数据包拆分得到的子数据包。
需要说明的是，强交互型数据包可以是具有时限要求的数据包，用户面功能实体如果在设定时长内没有完整接收到应用服务器发送的强交互型数据包拆分得到的所有子数据包，那么说明强交互型数据包已经超过了时限要求，此时用户面功能实体已经没有必要再传输其余子数据包给基站设备了。当然，用户面功能实体如果在设定时长内没有完整接收到应用服务器发送的指定类型的强交互型数据包拆分得到的所有子数据包，还可能是由于应用服务器检测到有子数据包传输错误然后停止发送了，此时也说明用户面功能实体没有必要再传输其余子数据包给基站设备了，在这种情况下用户面功能实体也可以停止向基站设备发送指定类型的强交互型数据包拆分得到的其余子数据包，并且可以丢弃已经接收到的指定类型的强交互型数据包拆分得到的子数据包。
在本申请实施例中，如果不同类型的强交互型数据包包括关键帧对应的强交互型数据包和非关键帧对应的强交互型数据包，由于非关键帧的恢复需要依赖于关键帧，因此如果检测到指定关键帧对应的强交互型数据包所拆分得到的子数据包为向基站设备发送失败的子数据包，则停止向基站设备发送与指定关键帧相关联的非关键帧所对应的强交互型数据包，和/或丢弃已经接收到的与指定关键帧相关联的非关键帧所对应的强交互型数据包。
可以理解的是，在关键帧对应的强交互型数据包拆分得到的多个子数据包中有发送失败的子数据包时，不仅停止传输该指定关键帧对应的强交互型数据包拆分得到的其余子数据包，而且也停止与该指定关键帧相关联的非关键帧所对应的强交互型数据包，即停止该相关联的非关键帧所对应的强交互型数据包拆分得到的其余子数据包的传输；如此，可以降低无效数据包对带宽的占用，有利于减少强交互型数据包在传输时对传输资源的占用。
以下从用户设备的角度对本申请实施例的数据传输方法进行说明。
图6示出了本申请实施例的又一个数据传输方法的流程图，该数据传输方法可以由用户设备来执行。参照图6所示，该数据传输方法至少包括S610至S630，下面对各步骤分别进行说明。
在S610中，接收AMF发送的URSP规则，URSP规则用于指示不同类型的强交互型数据包分别在不同的GTP-U隧道中进行传输，且通过同一个DRB进行承载。
在S620中，当识别到基站设备基于DRB发送的数据包属于强交互型数据包拆分得到的子数据包时，在接收强交互型数据包拆分得到的子数据包的过程中，根据URSP规则，检测强交互型数据包拆分得到的所有子数据包的接收情况。
在本申请实施例中，强交互型数据包拆分得到的多个子数据包中包含有开始数据包和结束数据包。开始数据包中包含有第一指示信息，该第一指示信息用于指示开始数据包是多个子数据包中第一个传输的子数据包；结束数据包中包含有第二指示信息，该第二指示信息用于指示结束数据包是多个子数据包中最后一个传输的子数据包。
可以理解的是，用户设备通过对开始数据包和结束数据包的识别来确定是否接收到强交互型数据包拆分得到的子数据包。比如，用户设备若根据开始数据包中包含的第一指示信息识别到该开始数据包，那么从开始数据包到结束数据包之间的数据包都属于强交互型数据包拆分得到的子数据包。
在本申请实施例中，用户设备可以根据接收到的数据包的协议字段中包含的指示信息，识别接收到的数据包是否属于强交互型数据包拆分得到的子数据包。
需要说明的是，强交互型数据包拆分得到的多个子数据包中的开始数据包在协议字段中添加有用于指示其为开始数据包的指示信息，而结束数据包在协议字段中添加有用于指示其为结束数据包的指示信息；用户设备在根据数据包的协议字段识别到该开始数据包之后，从开始数据包到结束数据包之间所接收到的数据包都属于强交互型数据包拆分得到的子数据包。
在本申请实施例中，用户设备可以根据接收到的数据包的净荷信息中包含的指示信息，识别接收到的数据包是否属于强交互型数据包拆分得到的子数据包。
需要说明的是，比如强交互型数据包拆分得到的多个子数据包中的开始数据包在净荷信息中添加有用于指示其为开始数据包的指示信息，而结束数据包在净荷信息中添加有用于指示其为结束数据包的指示信息，那么在根据数据包的净荷信息识别到该开始数据包之后，从开始数据包到结束数据包之间所接收到的数据包都属于强交互型数据包拆分得到的子数据包。
在S630中，当检测到在设定时长内未完整接收到指定类型的强交互型数据包拆分得到的所有数据包时，向发送指定类型的强交互型数据包的应用服务器发送传输失败信息，传输失败信息用于向应用服务器指示指定类型的强交互型数据包的传输失败。
在本申请实施例中，用户设备在对指定类型的强交互型数据包拆分得到的所有子数据包进行整合处理时，可以按照这些子数据包的顺序依次进行整合，最后得到完整的强交互型数据包。
在本申请实施例中，如果用户设备在设定时长内未完整接收到指定类型的强交互型数据包拆分得到的所有子数据包，则可以丢弃已经接收到的该指定类型的强交互型数据包拆分得到的子数据包。
需要说明的是，强交互型数据包可以是具有时限要求的数据包，用户设备如果在设定时长内没有完整接收到指定类型的强交互型数据包拆分得到的所有子数据包，那么说明指定类型的强交互型数据包已经超过了时限要求，此时用户设备已经没有必要再接收指定类型的强交互型数据包拆分得到的其余子数据包并进行整合处理了；因此，用户设备可以丢弃到已经接收到的指定类型的强交互型数据包拆分得到的子数据包。当然，如果在设定时长内没有完整接收到指定类型的强交互型数据包拆分得到的所有子数据包，还可能是由于基站设备检测到有子数据包传输错误然后停止发送了，此时用户面功能实体可以丢弃已经接收到的指定类型的强交互型数据包拆分得到的子数据包。
在本申请实施例中，用户设备如果在设定时长内未完整接收到指定类型的强交互型数据包拆分得到的所有子数据包，则向发送指定类型的强交互型数据包的应用服务器发送传输失败信息，以指示强交互型数据包传输失败。
可以理解的是，该实施例的技术方案使得用户设备检测到在设定时长内未完整接收到指定类型的强交互型数据包拆分得到的所有子数据包时，可以向应用服务器发送传输 失败信息，以向应用服务器指示指定类型的强交互型数据包传输失败，以便于应用服务器确认是否重新发送。
以下从策略控制功能(Policy Control Function，PCF)的角度对本申请实施例的数据传输方法进行说明：
图7示出了本申请实施例的再一个数据传输方法的流程图，该数据传输方法可以由PCF来执行。参照图7所示，该数据传输方法至少包括S710至S740，下面对各步骤分别进行说明。
在S710中，接收AF发送的针对强交互型数据包的GTP-U隧道配置信息，该GTP-U隧道配置信息用于指示不同类型的强交互型数据包分别在不同的GTP-U隧道中进行传输，且通过同一个DRB进行承载。
在本申请实施例中，AF可以直接将针对强交互型数据包的GTP-U隧道配置信息发送给PCF，或者AF也可以通过网络开放功能(Network Exposure Function，NEF)将针对强交互型数据包的GTP-U隧道配置信息发送给PCF。
在S720中，根据GTP-U隧道配置信息生成URSP规则和PDU会话管理策略信息，URSP规则和PDU会话管理策略信息用于指示不同类型的强交互型数据包分别在不同的GTP-U隧道中进行传输，且通过同一个DRB进行承载。
在S730中，将URSP规则通过AMF将URSP规则转发至用户设备，并根据URSP规则向基站设备配置接入层上下文信息，接入层上下文信息用于指示不同类型的强交互型数据包分别在不同的GTP-U隧道中进行传输，且通过同一个DRB进行承载。
在本申请实施例中，AMF可以直接将URSP规则转发给用户设备；同时AMF可以根据该URSP规则生成向基站设备配置的接入层上下文信息，并发送给基站设备。
在S740中，将PDU会话管理策略信息通过SMF配置给用户面功能实体。
在本申请实施例中，SMF可以直接将PDU会话管理策略信息转发给用户面功能实体。
需要说明的是，PCF通过将PDU会话管理策略信息配置给用户面功能实体，如此，用户面功能实体根据PDU会话管理策略信息，检测到指定类型的强交互型数据包拆分得到的子数据包向基站设备的发送失败时，停止向基站设备发送指定类型的强交互型数据包拆分得到的其余子数据包，以减少对传输资源的占用。PCF通过将URSP规则转发给用户设备，如此，用户设备根据URSP规则，检查到设定时长内未完整接收到指定类型的强交互型数据包拆分得到的所有数据包时，向发送指定类型的强交互型数据包的应用服务器发送传输失败信息，以减少对传输资源的占用。PCF通过将接入层上下文信息转发给基站设备，如此，基站设备根据接入层上下文信息，检测到指定类型的强交互型数据包拆分得到的子数据包向用户设备的发送失败时，停止向用户设备发送指定类型的强交互型数据包拆分得到的其余子数据包，以减少对传输资源的占用。
以上分别从用户面功能实体、基站设备、用户设备和PCF的角度对本申请实施例的数据传输方法进行了阐述，以下从各个实体之间交互的角度阐述本申请实施例的数据传输方法。
在本申请实施例中，应用服务器可以在应用层把强交互型数据包分类为两类(以两类作为示例，也可以是两类以上)，比如I帧和P帧；此时，两类强交互型数据包为I帧流和P帧流；这里，应用服务器对I帧流和P帧流这两个流分别进行传输。通过层间交互机制，把分类信息放在报文头中。在本申请实施例中，也可以不基于I帧和P帧进行划分，而是基于其它规则，比如基于音视频流内容的优先级等进行分类。
在本申请实施例中，AF可以与PCF进行交互，然后PCF与各网元(如AMF、SMF等)进行交互，为两个流进行GTP-U隧道的配置。如图8所示，经过应用层区分的I 帧的强交互型数据包8-11和P帧的强交互型数据包8-12在拆分之后，分别放在不同的GTP-U隧道(隧道8-21和隧道8-22)中，到达gNB之后使用同一个DRB承载进行下行传输，并且在同一个DRB承载中具有统一的数据包编号。同时，gNB在调度数据传输时，优先保证I帧流(即I帧的强交互型数据包拆分得到的多个子数据包)传输，如果I帧流发生丢失，则停止向用户设备发送I帧的强交互型数据包拆分得到的子数据包，并丢弃已经接收到的I帧的强交互型数据包拆分得到的子数据包，以及后续的P帧的强交互型数据包拆分出来的子数据包(如果I帧丢失，那么P帧即使收到也无法进行画面恢复)。
在本申请实施例中，在对任一类型的强交互型数据包进行拆分之后，可以对该类型的强交互型数据包拆分得到的子数据包进行开始和结束的标示。基于标示出的开始子数据包(称为开始数据包)和结束子数据包(称为结束数据包)，如果一个强交互型数据包拆分出来的N个子数据包中，有部分子数据包发送失败，那么后续的子数据包则无需再进行发送，可以进行丢弃处理；其中，N为大于1的正整数。
在本申请实施例中，在对子数据包的传输过程进行管理之前，需要进行控制面的配置过程，使得UE和各个网元都获取到强交互型数据包的传输参数，如图9所示，包括S901至S906。
S901，AF向PCF配置GTP-U隧道参数(称为GTP-U隧道配置信息)。
在本申请实施例中，AF可以通过向PCF配置强交互型数据包的PDU会话策略来配置GTP-U隧道参数。这里，AF可以直接将强交互型数据包的PDU会话策略发送给PCF，或者AF也可以通过NEF将强交互型数据包的PDU会话策略发送给PCF。其中，GTP-U隧道参数是指不同类型的强交互型数据包分别在不同的GTP-U隧道中进行传输，且通过同一个DRB进行承载。
S902，PCF向AMF配置URSP规则。
在本申请实施例中，PCF向AMF配置的URSP规则是与PDU会话策略相关的，是指不同类型的强交互型数据包分别在不同的GTP-U隧道中进行传输，且通过同一个DRB进行承载。
S903，AMF向UE配置URSP规则。
在本申请实施例中，AMF向UE配置的URSP规则包括：不同类型的强交互型数据包分别在不同的GTP-U隧道中进行传输，且通过同一个DRB进行承载。
S904，AMF向gNB配置接入层上下文(接入层上下文信息)。
在本申请实施例中，AMF向gNB配置的接入层(Access Stratum，AS)上下文(Context)是与PDU会话策略相关的，是指不同类型的强交互型数据包分别在不同的GTP-U隧道中进行传输，且通过同一个DRB进行承载的策略。
S905，PCF向SMF配置PDU会话管理策略(称为PDU会话管理策略信息)。
在本申请实施例中，PDU会话管理策略中包含了不同类型的强交互型数据包分别在不同的GTP-U隧道中进行传输，且通过同一个DRB进行承载的策略。
S906，SMF向UPF配置PDU会话管理策略。
在控制面配置完成之后，强交互型数据包的分段传输(即拆分为子数据包进行传输)需要遵循以下原则：对于巨大IP包(即强交互型数据包)拆解后形成的多个IP子包(称为多个子数据包)，如果部分IP子包发送失败，那么已成功发送的IP子包即使已被接收端收到，也应该丢弃；如果仍然有部分IP子包尚未发送，则发送端也应该停止发送，尽快启动下一个强交互型数据包的发送。
需要说明的是，如果应用服务器或者用户设备在应用层重传强交互型数据包，那么可以将重传的强交互型数据包确定为一个新的强交互型数据包进行传输，具体的传输方 式与本申请实施例提供的数据传输的方式一致。
在本申请实施例中，如图10所示，本申请实施例提供的一种示例性的的数据传输方法的流程示意图，可以包括S1010至S1080。
S1010，强交互型数据包在应用服务器侧完成拆分。
在本申请实施例中，应用服务器可以根据设定的子数据包大小或者网络的状态等信息来确定出分包大小，然后根据分包大小来对强交互型数据包进行拆分处理，得到多个子数据包。
S1020，对拆分得到的子数据包进行开始数据包和结束数据包的标示。
在本申请实施例中，可以在开始数据包和结束数据包中添加指示信息，以标示出哪个子数据包是开始数据包，哪个子数据包是结束数据包。这里，可以在子数据包的协议字段或者净荷信息中添加该指示信息，如在GTP-U隧道协议的字段中添加该指示信息。
S1030，UPF识别子数据包的开始和结束，同时把不同类型的子数据包放入不同的GTP-U隧道内。
在本申请实施例中，当应用服务器把拆分得到的子数据包传输给UPF的过程中，UPF可以识别其中的开始数据包和结束数据包。
S1040，子数据包传输到达gNB，gNB进行发送。
在本申请实施例中，UPF在接收到应用服务器发送的子数据包之后，将子数据包传输给gNB，然后gNB将子数据包发送给用户设备。其中，gNB需要进行增强以能够识别出子数据包中的指示信息，进而来确定开始数据包和结束数据包，以便于识别出强交互型数据包拆分得到的一系列子数据包。同时，gNB把从不同GTP-U隧道接收到的不同类型的子数据包放入同一个DRB发送给用户设备。
S1050，gNB向用户设备发送第m个子数据包。
这里，m为正整数变量。以及，gNB判断第m个子数据包是否发送成功；如果是则执行S1060；如果否，则执行S1070。另外，gNB还可以判断第m个子数据包是否符合延迟要求；如果是则执行S1060；如果否，则执行S1070。
在本申请实施例中，gNB可以通过空中接口(Uu接口)将子数据包发送给用户设备。同时，可以通过Uu接口的协议如PDCP、RLC等进行数据发送成功和失败的判断。
S1060，继续发送下一个子数据包，直到拆分出来的子数据包全部发送完成。
S1070，在gNB侧丢弃已经接收到的子数据包。此时也不再将UPF发送过来的其余子数据包发送给用户设备。如果发送失败的第m个子数据包是I帧的强交互型数据包，那么也丢弃相关联的P帧的强交互型数据包拆分得到的子数据包。
S1080，用户设备探测到强交互型数据包传输失败，从应用层向应用服务器进行反馈。可选地，如果用户设备在一定时限(称为设定时长)内没有完全接收到指定类型的强交互型数据包的所有子数据包，则可以确定强交互型数据包传输失败。其中向应用服务器反馈的信息用于指示该指定类型的强交互型数据包已经传输失败。
图10所示的数据传输方法描述了用户设备从应用层向应用服务器指示强交互型数据包传输失败的过程。在本申请实施例中，gNB还可以向UPF指示强交互型数据包的传输情况，如图11所示，数据传输方法包括S1110至S1180。
S1110，强交互型数据包在应用服务器侧完成拆分。
在本申请实施例中，应用服务器可以根据设定的子数据包大小或者网络的状态等信息来确定出分包大小，然后根据分包大小来对强交互型数据包进行拆分处理，得到多个子数据包。
S1120，对拆分得到的子数据包进行开始数据包和结束数据包的标示。
在本申请实施例中，可以在开始数据包和结束数据包中添加指示信息，以标示出哪 个子数据包是开始数据包，哪个子数据包是结束数据包。这里，可以在数据包的协议字段或者净荷信息中添加该指示信息，如在GTP-U隧道协议的字段中添加该指示信息。
S1130，UPF识别子数据包的开始和结束，同时把不同类型的子数据包放入不同的GTP-U隧道中。
在本申请实施例中，当应用服务器把拆分得到的子数据包传输给UPF的过程中，UPF可以识别其中的开始数据包和结束数据包。
S1140，子数据包传输到达gNB，gNB进行发送。
在本申请实施例中，UPF在接收到应用服务器发送的子数据包之后，将子数据包传输给gNB，然后gNB将子数据包发送给用户设备。其中，gNB需要进行增强以能够识别出子数据包中的指示信息，进而来确定开始数据包和结束数据包，以便于识别出强交互型数据包拆分得到的一系列子数据包。同时，gNB把从不同的GTP-U隧道接收到的不同类型的子数据包放入同一个DRB发送给用户设备。
S1150，gNB向用户设备发送第m个子数据包。
这里，gNB判断第m个子数据包是否发送成功；如果是则执行S1160；如果否，则执行S1170。另外，gNB还可以判断第m个子数据包是否符合延迟要求；如果是则执行S1160；如果否，则执行S1170。
在本申请实施例中，gNB可以通过Uu接口将子数据包发送给用户设备。同时，可以通过Uu接口的协议(如PDCP和RLC等)进行数据发送成功和失败的判断。
S1160，继续发送下一个子数据包，直到拆分出来的子数据包全部发送完成。
S1170，在gNB侧丢弃已经接收到的子数据包。此时也不再将UPF发送过来的其余子数据包发送给用户设备。如果发送失败的第m个子数据包是I帧的强交互型数据包，那么也丢弃相关联的P帧的强交互型数据包拆分得到的子数据包。
S1180，gNB向UPF提供反馈信息(称为第一反馈信息)，通知UPF停止向gNB发送其余子数据包。
需要说明的是，如果gNB已经完整接收了强交互型数据包拆分得到的所有子数据包，那么无需再向UPF提供反馈信息。
在本申请实施例中，图10和图11所示的数据处理方法也可以进行结合，即用户设备在探测到强交互型数据包传输失败时，从应用层向应用服务器进行反馈，而gNB在确定发送失败之后，也可以向UPF提供反馈信息，通知UPF停止向gNB发送子数据包。
在本申请实施例中，当各节点配置强交互型数据包的传输参数之后，如图12所示为应用服务器、UPF、gNB和用户设备之间的交互流程，包括S1201至S1205。
S1201，应用服务器拆分强交互型数据包，并标示出开始数据包和结束数据包。
在本申请实施例中，可以在开始数据包和结束数据包中添加指示信息，以标示出哪个子数据包是开始数据包，哪个子数据包是结束数据包。这里，可以在数据包的协议字段或者净荷信息中添加该指示信息，如在GTP-U隧道协议的字段中添加该指示信息。
S1202，应用服务器向UPF发送子数据包。
在本申请实施例中，当应用服务器把拆分得到的子数据包传输给UPF的过程中，UPF可以识别其中的开始数据包和结束数据包。
S1203，UPF向gNB发送子数据包。
在本申请实施例中，UPF可以将不同类型的子数据包放入不同的GTP-U隧道传输给gNB。
需要说明的是，UPF向gNB发送子数据包的过程与应用服务器向UPF发送子数据包的过程可以是同步进行的；比如UPF在接收到应用服务器发送的子数据包之后(还未全部接收完成)，就可以向gNB发送子数据包，这种方式可以降低子数据包到达用户 设备的延迟。当然，UPF也可以在全部接收到应用服务器发送的子数据包之后，再向gNB发送子数据包，如此，可以使得UPF在接收过程中出现错误时，减少向gNB发送的无效的子数据包的数量，从而能够降低传输资源的消耗。
在本申请实施例中，UPF在向gNB发送强交互型数据包拆分得到的子数据包的过程中，如果检测到某个类型(称为指定类型)的强交互型数据包拆分得到的子数据包传输失败或者检测到子数据包传输超过延迟要求，那么UPF可以停止向gNB发送该类型的强交互型数据包的其余子数据包，减少所发送的无效的子数据包的数量，从而能够降低传输资源的消耗。在这种情况下，UPF也可以删除已经接收到的该类型的强交互型数据包拆分得到的子数据包，同时UPF也可以通知应用服务器停止向UPF传输该类型的强交互型数据包拆分得到的其余子数据包。
在本申请实施例中，UPF也可以在设定时长内未全部接收到应用服务器传输的某个类型的强交互型数据包拆分得到的子数据包时，停止向gNB发送该类型的强交互型数据包拆分得到的其余子数据包，并且UPF也可以删除已经接收到的该类型的强交互型数据包拆分得到的子数据包，同时UPF也可以通知应用服务器停止向UPF传输该类型的强交互型数据包拆分得到的其余子数据包。
S1204，gNB向用户设备发送子数据包。
在本申请实施例中，gNB可以通过同一个DRB承载将不同类型的强交互型数据包拆分得到的子数据包传输给用户设备。
在本申请实施例中，gNB向用户设备发送子数据包的过程与UPF向gNB发送子数据包的过程可以是同步进行的；比如gNB在接收到UPF发送的子数据包之后(还未全部接收完成)，就可以向用户设备发送子数据包，这种方式可以降低子数据包到达用户设备的延迟。当然，gNB也可以在全部接收到UPF发送的子数据包之后，再向用户设备发送子数据包，如此，可以使得UPF在接收过程中出现错误时，减少向gNB发送的无效的子数据包的数量，从而能够降低传输资源的消耗。
在本申请实施例中，gNB在向用户设备发送强交互型数据包拆分得到的子数据包的过程中，如果检测到某个类型的强交互型数据包拆分得到的子数据包传输失败或者检测到子数据包传输超过延迟要求，那么gNB可以停止向用户设备发送该类型的强交互型数据包拆分得到的其余子数据包，减少所发送的无效的子数据包的数量，从而能够降低传输资源得分消耗。在这种情况下，gNB也可以删除已经接收到的该类型的强交互型数据包拆分得到的子数据包，同时gNB也可以通知UPF停止向gNB传输该类型的强交互型数据包拆分得到的其余子数据包。
在本申请实施例中，gNB也可以在设定时长内未全部接收到UPF传输的某个类型的强交互型数据包拆分得到的子数据包时，停止向用户设备发送该类型的强交互型数据包拆分得到的其余子数据包，并且gNB也可以删除已经接收到的该类型的强交互型数据包拆分得到的子数据包，同时gNB也可以通知UPF停止向gNB传输该类型的强交互型数据包拆分得到的其余子数据包。
S1205，用户设备若成功接收所有子数据包，则进行重组恢复出强交互型数据包。
在本申请实施例中，如果用户设备探测到某个类型的强交互型数据包传输失败，则可以从应用层向应用服务器进行反馈。
在本申请实施例中，如果用户设备在一定时限内没有完全接收到某个类型的强交互型数据包的所有子数据包，则可以确定该类型的强交互型数据包传输失败。其中，向应用服务器反馈的信息(称为传输失败信息)用于指示该类型的强交互型数据包已经传输失败。
本申请实施例的数据传输方法可以将不同类型的强交互型数据包分别在不同的 GTP-U隧道中进行传输、且对应于同一个DRB承载，从而使得在支持传输多种类型的强交互型数据包的前提下，降低对协议侧的影响。同时可以在强交互型数据包拆分得到的子数据包发送失败或者发送超过延迟要求时，及时停止向下一级节点发送其余子数据包，能够减少对带宽的占用，从而能够减少强交互型数据包在传输时对传输资源的占用。
需要说明的是，本申请实施例提供的数据传输装置可以用于执行本申请实施例中的数据传输方法。
图13示出了本申请实施例的一个数据传输装置的框图，该数据传输装置可以设置在基站设备内部。
参照图13所示，本申请实施例的数据传输装置1300，包括：第一接收单元1302、第一检测单元1304和第一处理单元1306。
其中，第一接收单元1302，配置为接收AMF发送的接入层上下文信息，所述接入层上下文信息用于指示不同类型的强交互型数据包分别在不同的GTP-U隧道中进行传输，且通过同一个DRB进行承载；
第一检测单元1304，配置为当识别到用户面功能实体通过所述GTP-U隧道发送的数据包属于所述强交互型数据包拆分得到的子数据包时，在将所述强交互型数据包拆分得到的子数据包基于所述DRB发送至用户设备的过程中，根据所述接入层上下文信息，检测所述强交互型数据包拆分得到的子数据包的发送情况；
第一处理单元1306，配置为当检测到指定类型的所述强交互型数据包拆分得到的子数据包向所述用户设备的发送失败时，停止向所述用户设备发送所述指定类型的所述强交互型数据包拆分得到的其余子数据包。
在本申请实施例中，第一处理单元1306，还配置为当检测到所述指定类型的所述强交互型数据包拆分得到的子数据包向所述用户设备的发送失败时，丢弃已经接收到的所述指定类型的所述强交互型数据包拆分得到的子数据包。
在本申请实施例中，第一处理单元1306，还配置为当检测到所述指定类型的所述强交互型数据包拆分得到的子数据包向所述用户设备的发送失败时，向所述用户面功能实体发送第一反馈信息，所述第一反馈信息用于指示所述用户面功能实体停止传输所述指定类型的所述强交互型数据包拆分得到其余子数据包。
在本申请实施例中，第一处理单元1306配置为当未完整接收到所述指定类型的强交互型数据包拆分得到的所有子数据包时，向所述用户面功能实体发送所述第一反馈信息。
在本申请实施例中，所述强交互型数据包拆分得到的多个子数据包中包括开始数据包和结束数据包；所述开始数据包包括第一指示信息，所述第一指示信息用于指示所述开始数据包是所述多个子数据包中第一个传输的子数据包；所述结束数据包包括第二指示信息，所述第二指示信息用于指示所述结束数据包是所述多个子数据包中最后一个传输的子数据包。
在本申请实施例中，第一检测单元1304还配置为接收所述用户面功能实体通过所述GTP-U隧道发送的所述数据包；根据所述数据包的协议字段中的指示信息，识别所述数据包是否属于所述强交互型数据包拆分得到的子数据包。
在本申请实施例中，第一检测单元1304还配置；或根据所述的数据包的净荷信息中的指示信息，识别所述数据包是否属于所述强交互型数据包拆分得到的子数据包。
在本申请实施例中，第一处理单元1306还配置为当在设定时长内未完整接收到所述用户面功能实体发送的所述指定类型的所述强交互型数据包拆分得到的所有子数据包时，停止向所述用户设备发送所述指定类型的所述强交互型数据包拆分得到的其余子数据包，并丢弃已经接收到的所述指定类型的所述强交互型数据包拆分得到的子数据包。
在本申请实施例中，不同类型的强交互型数据包包括：关键帧对应的强交互型数据包和非关键帧对应的强交互型数据包，所述指定类型的所述强交互数据包为所述关键帧对应的所述强交互数据包；第一处理单元1306还配置为当检测到所述关键帧对应的所述强交互型数据包所拆分得到的子数据包向所述用户设备的发送失败时，执行以下至少一种处理：停止向所述用户设备发送与所述关键帧相关联的所述非关键帧所对应的所述强交互型数据包，丢弃已经接收到的与所述关键帧相关联的所述非关键帧所对应的所述强交互型数据包。
图14示出了本申请实施例的另一个数据传输装置的框图，该数据传输装置可以设置在用户面功能实体内部。
参照图14，本申请实施例的数据传输装置1400，包括：第二接收单元1402、第二检测单元1404和第二处理单元1406。
其中，第二接收单元1402，配置为接收会话管理功能SMF发送的协议数据单元PDU会话管理策略信息，所述PDU会话管理策略信息用于指示不同类型的强交互型数据包分别在不同的通用分组无线业务隧道协议用户面GTP-U隧道中进行传输，且通过同一个数据无线承载DRB进行承载；
第二检测单元1404，配置为根据PDU会话管理策略信息，将接收到的不同类型的所述强交互型数据包拆分得到的子数据包分别在不同的所述GTP-U隧道中传输至基站设备，并检测所述强交互型数据包拆分得到的子数据包的发送情况；
第二处理单元1406，配置为当检测到指定类型的所述强交互型数据包拆分得到的子数据包向所述基站设备的发送失败时，停止向所述基站设备发送所述指定类型的所述强交互型数据包拆分得到的其余子数据包。
在本申请实施例中，第二处理单元1406，还配置为当检测到所述指定类型的所述强交互型数据包拆分得到的子数据包向所述基站设备的发送失败时，丢弃已经接收到的所述指定类型的所述强交互型数据包拆分得到的子数据包。
在本申请实施例中，第二处理单元1406，还配置为当检测到所述指定类型的所述强交互型数据包拆分得到的子数据包向所述基站设备的发送失败时，向应用服务器发送第二反馈信息，所述第二反馈信息用于指示所述应用服务器停止传输所述指定类型的所述强交互型数据包拆分得到其余子数据包。
在本申请实施例中，第二处理单元1406，配置为当未完整接收到所述指定类型的所述强交互型数据包拆分得到的所有子数据包时，向所述应用服务器发送所述第二反馈信息。
在本申请实施例中，第二处理单元1406，还配置为当在设定时长内未完整接收到所述指定类型的所述强交互型数据包拆分得到的所有子数据包时，停止向所述基站设备发送所述指定类型的所述强交互型数据包拆分得到的其余子数据包，并丢弃已经接收到的所述指定类型的所述强交互型数据包拆分得到的子数据包。
在本申请实施例中，不同类型的所述强交互型数据包包括：关键帧对应的所述强交互型数据包和非关键帧对应的所述强交互型数据包，所述指定类型的所述强交互数据包为所述关键帧对应的所述强交互数据包；
第二处理单元1406，还配置为当检测到所述关键帧对应的所述强交互型数据包所拆分得到的子数据包向所述基站设备的发送失败时，执行以下至少一种处理：停止向所述基站设备发送与所述关键帧相关联的所述非关键帧所对应的所述强交互型数据包，丢弃已经接收到的与所述关键帧相关联的所述非关键帧所对应的所述强交互型数据包。
图15示出了本申请实施例的又一个数据传输装置的框图，该数据传输装置可以设置在用户设备内部。
参照图15，本申请实施例的数据传输装置1500，包括：第三接收单元1502、第三检测单元1504和第三处理单元1506。
其中，第三接收单元1502，配置为接收接入与移动性管理功能AMF发送的用户设备路由选择策略URSP规则，所述URSP规则用于指示不同类型的强交互型数据包分别在不同的通用分组无线业务隧道协议用户面GTP-U隧道中进行传输，且通过同一个数据无线承载DRB进行承载；
第三检测单元1504，配置为当识别到基站设备基于所述DRB发送的数据包属于所述强交互型数据包拆分得到的子数据包时，在接收所述强交互型数据包拆分得到的子数据包的过程中，根据所述URSP规则，检测所述强交互型数据包拆分得到的所有子数据包的接收情况；
第三处理单元1506，配置为当检测到在设定时长内未完整接收到指定类型的所述强交互型数据包拆分得到的所有数据包时，向发送所述指定类型的所述强交互型数据包的应用服务器发送传输失败信息，所述传输失败信息用于向所述应用服务器指示所述指定类型的所述强交互型数据包的传输失败。
在本申请实施例中，第三处理单元1506，还配置为当检测到在所述设定时长内未完整接收到所述指定类型的所述强交互型数据包拆分得到的所有子数据包时，丢弃已经接收到的所述指定类型的强交互型数据包拆分得到的子数据包。
在本申请实施例中，第三处理单元1506，还配置为当完整接收到所述指定类型的所述强交互型数据包拆分得到的所有数据包时，对所述指定类型的所述强交互型数据包拆分得到的所有数据包进行整合处理，得到所述指定类型的所述强交互型数据包。
在本申请实施例中，不同类型的所述强交互型数据包包括：关键帧对应的所述强交互型数据包和非关键帧对应的所述强交互型数据包，所述指定类型的所述强交互数据包为所述关键帧对应的所述强交互数据包。
图16示出了本申请实施例的再一个数据传输装置的框图，该数据传输装置可以设置在PCF内部。
参照图16，本申请实施例的数据传输装置1600，包括：第四接收单元1602、生成单元1604、第一发送单元1606和第二发送单元1608。
其中，第四接收单元1602，配置为接收应用功能AF发送的针对强交互型数据包的通用分组无线业务隧道协议用户面GTP-U隧道配置信息，所述GTP-U隧道配置信息用于指示不类型的强交互型数据包分别在不同的GTP-U隧道中进行传输，且通过同一个数据无线承载DRB进行承载；
生成单元1604，配置为根据所述GTP-U隧道配置信息生成用户设备路由选择策略URSP规则和协议数据单元PDU会话管理策略信息，所述URSP规则和所述PDU会话管理策略信息用于指示不同类型的所述强交互型数据包分别在不同的所述GTP-U隧道中进行传输，且通过同一个所述DRB进行承载；
第一发送单元1606，配置为将所述URSP规则通过接入与移动性管理功能AMF转发至用户设备，并根据所述URSP规则向基站设备配置接入层上下文信息，所述接入层上下文信息用于指示不同类型的所述强交互型数据包分别在不同的所述GTP-U隧道中进行传输，且通过同一个所述DRB进行承载；
第二发送单元1608，配置为将所述PDU会话管理策略信息通过会话管理功能SMF配置给用户面功能实体。
在本申请实施例中，不同类型的所述强交互型数据包包括：关键帧对应的所述强交互型数据包和非关键帧对应的所述强交互型数据包，指定类型的所述强交互数据包为所述关键帧对应的所述强交互数据包。
图17示出了本申请实施例的电子设备的结构示意图。
需要说明的是，图17示出的电子设备的计算机系统1700仅是一个示例，不应对本申请实施例的功能和使用范围带来任何限制。
如图17所示，计算机系统1700包括中央处理单元(Central Processing Unit，CPU)1701(称为一个或多个处理器)，其可以根据存储在只读存储器(Read-Only Memory，ROM)1702中的程序或者从存储部分1708加载到随机访问存储器(Random Access Memory，RAM)1703中的程序而执行各种适当的动作和处理，例如执行上述实施例中所述的方法。在RAM 1703中，还存储有系统操作所需的各种程序和数据。CPU 1701、ROM 1702以及RAM 1703通过总线1704彼此相连。输入/输出(Input/Output，I/O)接口1705也连接至总线1704。
以下部件连接至I/O接口1705：包括键盘和鼠标等的输入部分1706；包括诸如阴极射线管(Cathode Ray Tube，CRT)和液晶显示器(Liquid Crystal Display，LCD)等以及扬声器等的输出部分1707；包括硬盘等的存储部分1708；以及包括诸如LAN(Local Area Network，局域网)卡和调制解调器等的网络接口卡的通信部分1709。通信部分1709经由诸如因特网的网络执行通信处理。驱动器1710也根据需要连接至I/O接口1705。可拆卸介质1711，诸如磁盘、光盘、磁光盘和半导体存储器等等，根据需要安装在驱动器1710上，以便于从其上读出的计算机程序根据需要被安装入存储部分1708。
在本申请实施例中，本申请实施例提供的数据处理方法可以被实现为计算机软件程序。例如，本申请实施例包括一种计算机程序产品，其包括承载在计算机可读存储介质上的计算机程序，该计算机程序包含用于执行本申请实施例提供的数据处理方法的计算机程序。此时，该计算机程序可以通过通信部分1709从网络上被下载和安装，和/或从可拆卸介质1711被安装。在该计算机程序被中央处理单元(CPU)1701执行时，执行本申请实施例提供的数据处理方法。
需要说明的是，本申请实施例提供的计算机可读存储介质例如可以是——但不限于——电、磁、光、电磁、红外线、或半导体的系统、装置或器件，或者任意以上的组合。计算机可读存储介质可以包括但不限于：具有一个或多个导线的电连接、便携式计算机磁盘、硬盘、随机访问存储器(RAM)、只读存储器(ROM)、可擦式可编程只读存储器(Erasable Programmable Read Only Memory，EPROM)、闪存、光纤、便携式紧凑磁盘只读存储器(Compact Disc Read-Only Memory，CD-ROM)、光存储器件、磁存储器件、或者上述的任意合适的组合。在本申请实施例中，计算机可读存储介质可以是任何包含或存储程序的有形介质，该程序可以被指令执行系统、装置或者器件使用或者与其结合使用。而在本申请实施例中，计算机可读存储介质还可以为计算机可读的信号介质，即为包括在基带中或者作为载波一部分传播的数据信号，并承载了计算机可读的计算机程序。这种传播的数据信号可以采用多种形式，包括但不限于电磁信号、光信号或上述的任意合适的组合。计算机可读存储介质可以是任何计算机可读介质，该计算机可读存储介质可以发送、传播或者传输用于由指令执行系统、装置或者器件使用或者与其结合使用的程序。计算机可读存储介质上包含的计算机程序可以用任何适当的介质传输，包括但不限于：无线和有线，等等，或者上述的任意合适的组合。
本申请实施例提供的附图中的流程图和框图，图示了按照本申请实施例的系统、方法和计算机程序产品的可能实现的体系架构、功能和操作。其中，流程图或框图中的每个方框可以代表一个模块、程序段、或代码的一部分，上述模块、程序段、或代码的一部分包含一个或多个用于实现规定的逻辑功能的可执行指令。也应当注意，在有些作为替换的实现中，方框中所标注的功能也可以以不同于附图中所标注的顺序发生。例如，两个接连地表示的方框实际上可以基本并行地执行，它们有时也可以按相反的顺序执行， 这依所涉及的功能而定。也要注意的是，框图或流程图中的每个方框、以及框图或流程图中的方框的组合，可以用执行规定的功能或操作的专用的基于硬件的系统来实现，或者可以用专用硬件与计算机指令的组合来实现。
本申请实施例中所涉及到的单元可以通过软件的方式实现，也可以通过硬件的方式来实现，所描述的单元也可以设置在处理器中。其中，这些单元的名称在某种情况下并不构成对该单元本身的限定。
本申请实施例还提供了一种计算机可读存储介质，该计算机可读存储介质可以是上述实施例中描述的电子设备中所包含的；也可以是单独存在，而未装配入该电子设备中。上述计算机可读介质承载有一个或者多个程序，当上述一个或者多个程序被一个该电子设备执行时，使得该电子设备实现本申请实施例中所述的数据传输方法。
应当注意，尽管在本申请实施例的描述中提及了用于动作执行的电子设备的若干模块或者单元，但是这种划分并非强制性的。实际上，根据本申请实施例的实施方式，本申请实施例描述的两个或更多模块或者单元的特征和功能可以在一个模块或者单元中具体化。反之，本申请实施例描述的一个模块或者单元的特征和功能可以进一步划分为由多个模块或者单元来具体化。
通过本申请实施例的描述，本领域的技术人员易于理解，这里描述的示例实施方式可以通过软件实现，也可以通过软件结合必要的硬件的方式来实现。因此，根据本申请实施例提供的数据处理方法可以以软件产品的形式体现出来，该软件产品可以存储在一个非易失性存储介质(可以是CD-ROM，优盘(U盘)，移动硬盘等)中或网络上，包括若干指令以使得一台计算设备(可以是个人计算机、服务器、触控终端、或者网络设备等)执行根据本申请实施例提供的数据处理方法。

Claims (27)

  1. 一种数据传输方法，包括：
    接收接入与移动性管理功能AMF发送的接入层上下文信息，所述接入层上下文信息用于指示不同类型的强交互型数据包分别在不同的通用分组无线业务隧道协议用户面GTP-U隧道中进行传输，且通过同一个数据无线承载DRB进行承载；
    当识别到用户面功能实体通过所述GTP-U隧道发送的数据包属于所述强交互型数据包拆分得到的子数据包时，在将所述强交互型数据包拆分得到的子数据包基于所述DRB发送至用户设备的过程中，根据所述接入层上下文信息，检测所述强交互型数据包拆分得到的子数据包的发送情况；
    当检测到指定类型的所述强交互型数据包拆分得到的子数据包向所述用户设备的发送失败时，停止向所述用户设备发送所述指定类型的所述强交互型数据包拆分得到的其余子数据包。
  2. 根据权利要求1所述的数据传输方法，其中，所述数据传输方法还包括：
    当检测到所述指定类型的所述强交互型数据包拆分得到的子数据包向所述用户设备的发送失败时，丢弃已经接收到的所述指定类型的所述强交互型数据包拆分得到的子数据包。
  3. 根据权利要求1所述的数据传输方法，其中，所述数据传输方法还包括：
    当检测到所述指定类型的所述强交互型数据包拆分得到的子数据包向所述用户设备的发送失败时，向所述用户面功能实体发送第一反馈信息，所述第一反馈信息用于指示所述用户面功能实体停止传输所述指定类型的所述强交互型数据包拆分得到其余子数据包。
  4. 根据权利要求3所述的数据传输方法，其中，所述向所述用户面功能实体发送第一反馈信息，包括：
    当未完整接收到所述指定类型的强交互型数据包拆分得到的所有子数据包时，向所述用户面功能实体发送所述第一反馈信息。
  5. 根据权利要求1所述的数据传输方法，其中，所述强交互型数据包拆分得到的多个子数据包包括开始数据包和结束数据包；
    所述开始数据包包括第一指示信息，所述第一指示信息用于指示所述开始数据包是所述多个子数据包中第一个传输的子数据包；
    所述结束数据包包括第二指示信息，所述第二指示信息用于指示所述结束数据包是所述多个子数据包中最后一个传输的子数据包。
  6. 根据权利要求1所述的数据传输方法，其中，所述数据传输方法还包括：
    接收所述用户面功能实体通过所述GTP-U隧道发送的所述数据包；
    根据所述数据包的协议字段中的指示信息，识别所述数据包是否属于所述强交互型数据包拆分得到的子数据包；或
    根据所述的数据包的净荷信息中的指示信息，识别所述数据包是否属于所述强交互型数据包拆分得到的子数据包。
  7. 根据权利要求1所述的数据传输方法，其中，所述数据传输方法还包括：
    当在设定时长内未完整接收到所述用户面功能实体发送的所述指定类型的所述强交互型数据包拆分得到的所有子数据包时，停止向所述用户设备发送所述指定类型的所述强交互型数据包拆分得到的其余子数据包，并丢弃已经接收到的所述指定类型的所述强交互型数据包拆分得到的子数据包。
  8. 根据权利要求1至7中任一项所述的数据传输方法，其中，不同类型的所述强交互型数据包包括：关键帧对应的所述强交互型数据包和非关键帧对应的所述强交互型数据包，所述指定类型的所述强交互数据包为所述关键帧对应的所述强交互数据包；
    所述数据传输方法还包括：
    当检测到所述关键帧对应的所述强交互型数据包所拆分得到的子数据包向所述用户设备的发送失败时，执行以下至少一种处理：
    停止向所述用户设备发送与所述关键帧相关联的所述非关键帧所对应的所述强交互型数据包，丢弃已经接收到的与所述关键帧相关联的所述非关键帧所对应的所述强交互型数据包。
  9. 一种数据传输方法，包括：
    接收会话管理功能SMF发送的协议数据单元PDU会话管理策略信息，所述PDU会话管理策略信息用于指示不同类型的强交互型数据包分别在不同的通用分组无线业务隧道协议用户面GTP-U隧道中进行传输，且通过同一个数据无线承载DRB进行承载；
    根据PDU会话管理策略信息，将接收到的不同类型的所述强交互型数据包拆分得到的子数据包分别在不同的所述GTP-U隧道中传输至基站设备，并检测所述强交互型数据包拆分得到的子数据包的发送情况；
    当检测到指定类型的所述强交互型数据包拆分得到的子数据包向所述基站设备的发送失败时，停止向所述基站设备发送所述指定类型的所述强交互型数据包拆分得到的其余子数据包。
  10. 根据权利要求9所述的数据传输方法，其中，所述数据传输方法还包括：
    当检测到所述指定类型的所述强交互型数据包拆分得到的子数据包向所述基站设备的发送失败时，丢弃已经接收到的所述指定类型的所述强交互型数据包拆分得到的子数据包。
  11. 根据权利要求9所述的数据传输方法，其中，所述数据传输方法还包括：
    当检测到所述指定类型的所述强交互型数据包拆分得到的子数据包向所述基站设备的发送失败时，向应用服务器发送第二反馈信息，所述第二反馈信息用于指示所述应用服务器停止传输所述指定类型的所述强交互型数据包拆分得到其余子数据包。
  12. 根据权利要求11所述的数据传输方法，其中，所述向应用服务器发送第二反馈信息，包括：
    当未完整接收到所述指定类型的所述强交互型数据包拆分得到的所有子数据包时，向所述应用服务器发送所述第二反馈信息。
  13. 根据权利要求9所述的数据传输方法，其中，所述数据传输方法还包括：
    当在设定时长内未完整接收到所述指定类型的所述强交互型数据包拆分得到的所有子数据包时，停止向所述基站设备发送所述指定类型的所述强交互型数据包拆分得到的其余子数据包，并丢弃已经接收到的所述指定类型的所述强交互型数据包拆分得到的子数据包。
  14. 根据权利要求9至13中任一项所述的数据传输方法，其中，不同类型的所述强交互型数据包包括：关键帧对应的所述强交互型数据包和非关键帧对应的所述强交互型数据包，所述指定类型的所述强交互数据包为所述关键帧对应的所述强交互数据包；
    所述数据传输方法还包括：
    当检测到所述关键帧对应的所述强交互型数据包所拆分得到的子数据包向所述基站设备的发送失败时，执行以下至少一种处理：
    停止向所述基站设备发送与所述关键帧相关联的所述非关键帧所对应的所述强交互型数据包，丢弃已经接收到的与所述关键帧相关联的所述非关键帧所对应的所述强交互型数据包。
  15. 一种数据传输方法，包括：
    接收接入与移动性管理功能AMF发送的用户设备路由选择策略URSP规则，所述URSP规则用于指示不同类型的强交互型数据包分别在不同的通用分组无线业务隧道协议用户面GTP-U隧道中进行传输，且通过同一个数据无线承载DRB进行承载；
    当识别到基站设备基于所述DRB发送的数据包属于所述强交互型数据包拆分得到的子数据包时，在接收所述强交互型数据包拆分得到的子数据包的过程中，根据所述URSP规则，检测所述强交互型数据包拆分得到的所有子数据包的接收情况；
    当检测到在设定时长内未完整接收到指定类型的所述强交互型数据包拆分得到的所有数据包时，向发送所述指定类型的所述强交互型数据包的应用服务器发送传输失败信息，所述传输失败信息用于向所述应用服务器指示所述指定类型的所述强交互型数据包的传输失败。
  16. 根据权利要求15所述的数据传输方法，其中，所述数据传输方法还包括：
    当检测到在所述设定时长内未完整接收到所述指定类型的所述强交互型数据包拆分得到的所有子数据包时，丢弃已经接收到的所述指定类型的强交互型数据包拆分得到的子数据包。
  17. 根据权利要求15所述的数据传输方法，其中，所述数据传输方法还包括：
    当完整接收到所述指定类型的所述强交互型数据包拆分得到的所有数据包时，对所述指定类型的所述强交互型数据包拆分得到的所有数据包进行整合处理，得到所述指定类型的所述强交互型数据包。
  18. 根据权利要求15至17中任一项所述的数据传输方法，其中，不同类型的所述强交互型数据包包括：关键帧对应的所述强交互型数据包和非关键帧对应的所述强交互型数据包，所述指定类型的所述强交互数据包为所述关键帧对应的所述强交互数据包。
  19. 一种数据传输方法，包括：
    接收应用功能AF发送的针对强交互型数据包的通用分组无线业务隧道协议用户面GTP-U隧道配置信息，所述GTP-U隧道配置信息用于指示不类型的强交互型数据包分别在不同的GTP-U隧道中进行传输，且通过同一个数据无线承载DRB进行承载；
    根据所述GTP-U隧道配置信息生成用户设备路由选择策略URSP规则和协议数据单元PDU会话管理策略信息，所述URSP规则和所述PDU会话管理策略信息用于指示不同类型的所述强交互型数据包分别在不同的所述GTP-U隧道中进行传输，且通过同一个所述DRB进行承载；
    将所述URSP规则通过接入与移动性管理功能AMF转发至用户设备，并根据所述URSP规则向基站设备配置接入层上下文信息，所述接入层上下文信息用于指示不同类型的所述强交互型数据包分别在不同的所述GTP-U隧道中进行传输，且通过同一个所述DRB进行承载；
    将所述PDU会话管理策略信息通过会话管理功能SMF配置给用户面功能实体。
  20. 根据权利要求19所述的数据传输方法，其中，不同类型的所述强交互型数据包包括：关键帧对应的所述强交互型数据包和非关键帧对应的所述强交互型数据包。
  21. 一种数据传输装置，包括：
    第一接收单元，配置为接收接入与移动性管理功能AMF发送的接入层上下文信息，所述接入层上下文信息用于指示不同类型的强交互型数据包分别在不同的通用分组无 线业务隧道协议用户面GTP-U隧道中进行传输，且通过同一个数据无线承载DRB进行承载；
    第一检测单元，配置为当识别到用户面功能实体通过所述GTP-U隧道发送的数据包属于所述强交互型数据包拆分得到的子数据包时，在将所述强交互型数据包拆分得到的子数据包基于所述DRB发送至用户设备的过程中，根据所述接入层上下文信息，检测所述强交互型数据包拆分得到的子数据包的发送情况；
    第一处理单元，配置为当检测到指定类型的所述强交互型数据包拆分得到的子数据包向所述用户设备的发送失败时，停止向所述用户设备发送所述指定类型的所述强交互型数据包拆分得到的其余子数据包。
  22. 一种数据传输装置，包括：
    第二接收单元，配置为接收会话管理功能SMF发送的协议数据单元PDU会话管理策略信息，所述PDU会话管理策略信息用于指示不同类型的强交互型数据包分别在不同的通用分组无线业务隧道协议用户面GTP-U隧道中进行传输，且通过同一个数据无线承载DRB进行承载；
    第二检测单元，配置为根据PDU会话管理策略信息，将接收到的不同类型的所述强交互型数据包拆分得到的子数据包分别在不同的所述GTP-U隧道中传输至基站设备，并检测所述强交互型数据包拆分得到的子数据包的发送情况；
    第二处理单元，配置为当检测到指定类型的所述强交互型数据包拆分得到的子数据包向所述基站设备的发送失败时，停止向所述基站设备发送所述指定类型的所述强交互型数据包拆分得到的其余子数据包。
  23. 一种数据传输装置，包括：
    第三接收单元，配置为接收接入与移动性管理功能AMF发送的用户设备路由选择策略URSP规则，所述URSP规则用于指示不同类型的强交互型数据包分别在不同的通用分组无线业务隧道协议用户面GTP-U隧道中进行传输，且通过同一个数据无线承载DRB进行承载；
    第三检测单元，配置为当识别到基站设备基于所述DRB发送的数据包属于所述强交互型数据包拆分得到的子数据包时，在接收所述强交互型数据包拆分得到的子数据包的过程中，根据所述URSP规则，检测所述强交互型数据包拆分得到的所有子数据包的接收情况；
    第三处理单元，配置为当检测到在设定时长内未完整接收到指定类型的所述强交互型数据包拆分得到的所有数据包时，向发送所述指定类型的所述强交互型数据包的应用服务器发送传输失败信息，所述传输失败信息用于向所述应用服务器指示所述指定类型的所述强交互型数据包的传输失败。
  24. 一种数据传输装置，包括：
    第四接收单元，配置为接收应用功能AF发送的针对强交互型数据包的通用分组无线业务隧道协议用户面GTP-U隧道配置信息，所述GTP-U隧道配置信息用于指示不类型的强交互型数据包分别在不同的GTP-U隧道中进行传输，且通过同一个数据无线承载DRB进行承载；
    生成单元，配置为根据所述GTP-U隧道配置信息生成用户设备路由选择策略URSP规则和协议数据单元PDU会话管理策略信息，所述URSP规则和所述PDU会话管理策略信息用于指示不同类型的所述强交互型数据包分别在不同的所述GTP-U隧道中进行传输，且通过同一个所述DRB进行承载；
    第一发送单元，配置为将所述URSP规则通过接入与移动性管理功能AMF转发至用户设备，并根据所述URSP规则向基站设备配置接入层上下文信息，所述接入层上下 文信息用于指示不同类型的所述强交互型数据包分别在不同的所述GTP-U隧道中进行传输，且通过同一个所述DRB进行承载；
    第二发送单元，配置为将所述PDU会话管理策略信息通过会话管理功能SMF配置给用户面功能实体。
  25. 一种计算机可读存储介质，其上存储有计算机程序，所述计算机程序被一个或多个处理器执行时，实现如权利要求1至8中任一项所述的数据传输方法；或实现如权利要求9至14中任一项所述的数据传输方法；或实现如权利要求15至18中任一项所述的数据传输方法；或实现如权利要求19和20所述的数据传输方法。
  26. 一种电子设备，包括：
    一个或多个处理器；
    存储装置，用于存储一个或多个程序，当所述一个或多个程序被所述一个或多个处理器执行时，实现如权利要求1至8中任一项所述的数据传输方法；或实现如权利要求9至14中任一项所述的数据传输方法；或实现如权利要求15至18中任一项所述的数据传输方法；或实现如权利要求19和20所述的数据传输方法。
  27. 一种计算机程序产品，所述计算机程序产品包括计算机程序或计算机指令，所述算机程序或计算机指令被一个或多个处理器执行时，实现本申请实施例提供的数据传输方法。
PCT/CN2021/131399 2021-01-04 2021-11-18 一种数据传输方法、装置、计算机可读存储介质、电子设备及计算机程序产品 WO2022142835A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
EP21913577.9A EP4240053A4 (en) 2021-01-04 2021-11-18 DATA TRANSMISSION METHOD AND APPARATUS, COMPUTER-READABLE STORAGE MEDIUM, ELECTRONIC DEVICE AND COMPUTER PROGRAM PRODUCT
KR1020237010755A KR20230058469A (ko) 2021-01-04 2021-11-18 데이터 송신 방법 및 장치, 컴퓨터로 판독 가능한 저장 매체, 전자 디바이스, 그리고 컴퓨터 프로그램 제품
JP2023530057A JP7484024B2 (ja) 2021-01-04 2021-11-18 データ伝送方法、装置、電子機器、及びコンピュータプログラム
US17/989,301 US20230083441A1 (en) 2021-01-04 2022-11-17 Managing subpacket transmission and reception for advanced interactive services

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110004590.5A CN112804711B (zh) 2021-01-04 2021-01-04 数据传输方法、装置、计算机可读介质及电子设备
CN202110004590.5 2021-01-04

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/989,301 Continuation US20230083441A1 (en) 2021-01-04 2022-11-17 Managing subpacket transmission and reception for advanced interactive services

Publications (1)

Publication Number Publication Date
WO2022142835A1 true WO2022142835A1 (zh) 2022-07-07

Family

ID=75808009

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/131399 WO2022142835A1 (zh) 2021-01-04 2021-11-18 一种数据传输方法、装置、计算机可读存储介质、电子设备及计算机程序产品

Country Status (6)

Country Link
US (1) US20230083441A1 (zh)
EP (1) EP4240053A4 (zh)
JP (1) JP7484024B2 (zh)
KR (1) KR20230058469A (zh)
CN (1) CN112804711B (zh)
WO (1) WO2022142835A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024055692A1 (zh) * 2022-09-14 2024-03-21 华为技术有限公司 通信方法、通信装置和通信系统

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3935895A4 (en) * 2019-03-08 2022-03-02 Telefonaktiebolaget LM Ericsson (publ.) METHOD AND APPARATUS FOR PROCESSING FAILURES AND RESTORES OF USER PLANE PATHS
CN112804710B (zh) * 2021-01-04 2024-05-07 腾讯科技（深圳）有限公司 数据传输方法、装置、计算机可读介质及电子设备
CN112804711B (zh) * 2021-01-04 2024-05-07 腾讯科技（深圳）有限公司 数据传输方法、装置、计算机可读介质及电子设备
US20230069008A1 (en) * 2021-09-02 2023-03-02 Apple Inc. Quality of Service Framework Enhancements for 5G Service
WO2023115477A1 (en) * 2021-12-23 2023-06-29 Lenovo (Beijing) Limited Methods and apparatuses for supporting a packet discarding operation in rlc layer due to a packet loss
CN116567657A (zh) * 2022-01-28 2023-08-08 腾讯科技（深圳）有限公司 数据传输方法、装置、计算机可读介质及电子设备
CN117459994A (zh) * 2022-07-18 2024-01-26 维沃移动通信有限公司 数据包处理方法、终端及网络侧设备
WO2024065542A1 (zh) * 2022-09-29 2024-04-04 北京小米移动软件有限公司 一种发送数据包的方法、装置、电子设备及可读存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015106444A1 (zh) * 2014-01-17 2015-07-23 华为技术有限公司 一种数据包的传输方法和传输设备
US20170054528A1 (en) * 2015-08-18 2017-02-23 Gn Resound A/S Method of exchanging data packages between first and second portable communication devices
CN110769380A (zh) * 2019-10-31 2020-02-07 联想(北京)有限公司 视频分发方法及装置
CN112804711A (zh) * 2021-01-04 2021-05-14 腾讯科技（深圳）有限公司 数据传输方法、装置、计算机可读介质及电子设备

Family Cites Families (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1553501B1 (en) 2002-10-16 2009-07-08 Panasonic Corporation Ic card, data transfer device, data transfer method, and data transfer method program
JP2006165733A (ja) 2004-12-03 2006-06-22 Matsushita Electric Ind Co Ltd 無線映像伝送装置
CN108419275B (zh) 2017-02-10 2022-01-14 华为技术有限公司 一种数据传输方法、通信设备、终端和基站
CN110546975B (zh) * 2017-03-17 2021-06-04 三星电子株式会社 无线电接入网络通知区域更新失败
US11039495B2 (en) * 2017-03-20 2021-06-15 Lg Electronics Inc. Method interlayer interaction method in wireless communication system and apparatus therefor
WO2018175974A1 (en) * 2017-03-24 2018-09-27 Intel Corporation Systems and methods for group based services provisioning
US10862620B2 (en) 2017-09-25 2020-12-08 Dolby Laboratories Licensing Corporation Systems and methods to optimize the load of multipath data transportation
EP3753373B1 (en) * 2018-02-14 2023-07-19 Telefonaktiebolaget LM Ericsson (publ) Handling qos mobility and dual connectivity in nr
CN110351030B (zh) * 2018-04-03 2022-07-12 华为技术有限公司 报文传输方法、装置和系统
US10681607B2 (en) * 2018-06-22 2020-06-09 Intel Corporation Receive-side scaling for wireless communication devices
US11399304B2 (en) * 2018-09-28 2022-07-26 Ofinno, Llc Packet duplication by core network
CN109218995B (zh) * 2018-10-08 2021-08-20 腾讯科技（深圳）有限公司 通信方法、装置、计算机可读介质及电子设备
CN114885385A (zh) * 2018-11-19 2022-08-09 华为技术有限公司 一种通信方法及装置
US20220312510A1 (en) * 2019-06-26 2022-09-29 Telefonaktiebolaget Lm Ericsson (Publ) Session Establishment with a Local Serving Network

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015106444A1 (zh) * 2014-01-17 2015-07-23 华为技术有限公司 一种数据包的传输方法和传输设备
US20170054528A1 (en) * 2015-08-18 2017-02-23 Gn Resound A/S Method of exchanging data packages between first and second portable communication devices
CN110769380A (zh) * 2019-10-31 2020-02-07 联想(北京)有限公司 视频分发方法及装置
CN112804711A (zh) * 2021-01-04 2021-05-14 腾讯科技（深圳）有限公司 数据传输方法、装置、计算机可读介质及电子设备

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
See also references of EP4240053A4 *
ZTE: "(TP for NR BL CR for TS 38.413): Discussion on AMF initiated two GTP-U tunnel establishment", 3GPP TSG-RAN WG3 NR ADHOC 1807 ; R3-183668, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), SOPHIA-ANTIPOLIS CEDEX ; FRANCE, 22 June 2018 (2018-06-22), Montreal, Canada; 20180702 - 20180706, XP051503765 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024055692A1 (zh) * 2022-09-14 2024-03-21 华为技术有限公司 通信方法、通信装置和通信系统

Also Published As

Publication number Publication date
EP4240053A4 (en) 2024-03-13
CN112804711B (zh) 2024-05-07
US20230083441A1 (en) 2023-03-16
JP2023549908A (ja) 2023-11-29
KR20230058469A (ko) 2023-05-03
CN112804711A (zh) 2021-05-14
EP4240053A1 (en) 2023-09-06
JP7484024B2 (ja) 2024-05-15

Similar Documents

Publication Publication Date Title
WO2022142835A1 (zh) 一种数据传输方法、装置、计算机可读存储介质、电子设备及计算机程序产品
WO2022142516A1 (zh) 数据传输方法、装置、计算机可读介质及电子设备
WO2022142517A1 (zh) 数据传输方法、装置、计算机可读介质及电子设备
WO2022095795A1 (zh) 通信方法、装置、计算机可读介质及电子设备
WO2022142676A1 (zh) 数据传输方法、装置、计算机可读介质及电子设备
WO2022142885A1 (zh) 一种数据传输方法、装置、计算机可读存储介质、电子设备及计算机程序产品
CN113037440B (zh) 数据重传处理方法、装置、计算机设备和存储介质
US11792130B2 (en) Audio/video communication method, terminal, server, computer device, and storage medium
CN112953850B (zh) 数据传输方法、装置、计算机可读介质及电子设备
WO2023217188A1 (zh) 一种直播数据传输方法、装置、系统、设备和介质
CN117062043A (zh) 数据处理方法、装置、计算机可读介质及终端设备
Zeydan et al. Enhancing the capabilities of mobile backhaul: A user plane perspective
WO2023142592A1 (zh) 数据传输方法、装置、计算机可读介质及电子设备、计算机程序产品
WO2023213086A1 (zh) 数据处理方法、装置、计算机可读介质及电子设备
WO2024007572A1 (zh) 报文处理方法及其装置、存储介质、程序产品
WO2024066362A1 (zh) 数据传输方法、装置、计算机可读介质及电子设备
WO2024067365A1 (zh) 数据传输方法及装置
WO2023098695A1 (zh) 数据包的处理方法、装置及终端
WO2024001451A1 (zh) 业务数据包的处理方法、装置、介质及电子设备
WO2024066652A1 (zh) 数据传输方法、装置、计算机可读介质及电子设备
WO2024056200A1 (en) Early termination of transmission of pdu sets generated by al-fec in a wireless communication network
CN117082566A (zh) 数据传输方法、装置及通信设备

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

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 20237010755

Country of ref document: KR

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 2023530057

Country of ref document: JP

ENP Entry into the national phase

Ref document number: 2021913577

Country of ref document: EP

Effective date: 20230601

NENP Non-entry into the national phase

Ref country code: DE