WO2018202102A1 - 数据传输方法及通信设备 - Google Patents

数据传输方法及通信设备 Download PDF

Info

Publication number
WO2018202102A1
WO2018202102A1 PCT/CN2018/085514 CN2018085514W WO2018202102A1 WO 2018202102 A1 WO2018202102 A1 WO 2018202102A1 CN 2018085514 W CN2018085514 W CN 2018085514W WO 2018202102 A1 WO2018202102 A1 WO 2018202102A1
Authority
WO
WIPO (PCT)
Prior art keywords
indication
data
flow
flow identifier
data stream
Prior art date
Application number
PCT/CN2018/085514
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 EP18794474.9A priority Critical patent/EP3611865B1/en
Publication of WO2018202102A1 publication Critical patent/WO2018202102A1/zh
Priority to US16/670,066 priority patent/US11252095B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • 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
    • 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/24—Traffic characterised by specific attributes, e.g. priority or QoS
    • H04L47/2483—Traffic characterised by specific attributes, e.g. priority or QoS involving identification of individual flows
    • 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/24—Traffic characterised by specific attributes, e.g. priority or QoS
    • 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/24—Traffic characterised by specific attributes, e.g. priority or QoS
    • H04L47/2408—Traffic characterised by specific attributes, e.g. priority or QoS for supporting different services, e.g. a differentiated services [DiffServ] type of service
    • 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/24—Traffic characterised by specific attributes, e.g. priority or QoS
    • H04L47/2491—Mapping quality of service [QoS] requirements between different networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/50—Queue scheduling
    • H04L47/62—Queue scheduling characterised by scheduling criteria
    • H04L47/6215—Individual queue per QOS, rate or priority
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/80—Actions related to the user profile or the type of traffic
    • H04L47/805—QOS or priority aware
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/22—Parsing or analysis of headers
    • 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/0268—Traffic management, e.g. flow control or congestion control using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/24—Negotiating SLA [Service Level Agreement]; Negotiating QoS [Quality of Service]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/02—Communication route or path selection, e.g. power-based or shortest path routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/02—Data link layer protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08—Access point devices

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a data transmission method and a communication device.
  • an end-to-end Quality of Service mechanism is implemented based on a bearer.
  • next generation mobile communication system e.g., a fifth-generation mobile communication (5 th -Generation, 5G)
  • 5G next generation mobile communication
  • the data may be based on QoS flow manner in a core network (Core Network, CN), and Passed on the interface between the CN and the Access Network (AN).
  • CN Core Network
  • AN Access Network
  • the inclusion of an air interface within the AN preserves the concept of bearers, and one or more QoS flows can be mapped to the same bearer.
  • the UPF User Plane Function
  • NG-RAN NodeB next-generation access network base station
  • gNB next-generation access network base station
  • the application provides a data transmission method and a communication device, in order to complete the processing of the data stream.
  • An aspect of the present application provides a data transmission method, including: a sender device processes a data stream, where the processing includes: adding the data stream to a service data adaptation protocol layer SDAP header, where The SDAP header includes a flow identifier indication, the flow identifier indication is used to indicate whether a flow identifier is included, and the sender device sends the processed data stream.
  • a service data adaptation protocol layer header is defined, and the data stream is processed by adding a service data adaptation protocol layer header, and the processed data is sent; after receiving the data stream, the data stream is removed.
  • the service data adaptation protocol layer header in the data stream completes the processing of the data stream; and the flow identifier indication is used to indicate whether the flow identifier is included, and if the flow identifier indication indicates that the flow identifier is not included, the SDAP header does not need to be a flow. Identifies configuration bytes, which saves air interface overhead.
  • the sending end device includes a base station; the flow identifier indication is further used to indicate whether the SDAP header includes an access layer data flow reflection indication; the method further includes: the base station sending the first information The first signaling includes a non-access stratum data flow reflection indication.
  • the sending end device includes a base station, where the flow identifier indication is further used to indicate whether the SDAP header includes a non-access stratum data flow reflection indication; the method further includes: sending, by the base station, The second signaling, wherein the second signaling comprises an access layer data flow reflection indication.
  • the flow identifier indication may also be used to implicitly indicate whether the SDAP header includes an access layer data flow reflection indication or a non-access layer data flow reflection indication, which may save the overhead of the SDAP header; transmission.
  • the sending end device includes a base station; the method further includes: the base station sending an access layer data flow reflection indication by using radio resource control signaling; and the base station forwarding the non-connected from the core network Inbound data flow reflection indication.
  • the access layer data flow reflection indication and the non-access layer data flow reflection indication can be transmitted through signaling, and the overhead of the SDAP header can be saved.
  • the method further includes: the sending end device receiving the data stream; and the sending end device removing the SDAP header in the data stream. In this implementation manner, when the sending end device receives the data stream, the service data adaptation protocol layer header in the data stream is removed, and the data stream is processed.
  • a data transmission method including: a receiving end device receiving a data stream, where the data stream includes a service data adaptation protocol layer SDAP header, where the SDAP header includes a flow identifier indication, where The flow identifier indication is used to indicate whether the flow identifier is included; the receiving device removes the SDAP header in the data flow.
  • a service data adaptation protocol layer header is defined. After receiving the data stream, the service data adaptation protocol layer header in the data stream is removed, and the data stream is processed.
  • the SDAP header further includes a flow identifier, the flow identifier being located at a first byte and/or a second byte of the SDAP header.
  • the SDAP header needs to include the stream identifier, and part of the content of the stream identifier may be located in the first byte of the SDAP header to save the overhead of the SDAP header;
  • the length of the identifier is long, and the stream identifier can be located in the first byte and the second byte, or even more bytes.
  • the flow identifier indication is further used to indicate whether the SDAP header includes an access layer data flow reflection indication ARI and a non-access layer data flow reflection indication. NRI.
  • the flow identifier indication may also be used to implicitly indicate whether the SDAP header includes an access layer data flow reflection indication and a non-access layer data flow reflection indication, which may save the overhead of the SDAP header.
  • the SDAP header further includes an indication of data information/control information.
  • the control information may be, for example, an access layer data flow reflection indication and a non-access layer data flow reflection indication, if the data information/control information is indicated.
  • the SDAP header includes data information, and the SDAP header does not need to include an access layer data flow reflection indication and a non-access layer data flow reflection indication; if the data information/control information indicates that the SDAP header includes control information,
  • the SDAP header needs to include an access layer data flow reflection indication and a non-access layer data flow reflection indication, so that the SDAP header overhead can be saved to some extent.
  • the SDAP header further includes an uplink/downlink indication.
  • an uplink/downlink indication is added to the SDAP header, and the uplink layer transmission may not carry the access layer data flow reflection indication and the non-access layer data flow reflection indication. Therefore, if the uplink/downlink indication indicates the time The transmission is an uplink transmission, and the SDAP header does not need to include an access layer data flow reflection indication and a non-access layer data flow reflection indication; if the uplink/downlink indication indicates that the transmission is a downlink transmission, the SDAP header may include an access layer. The data flow reflection indication and the non-access layer data flow reflection indication. This can save the overhead of the SDAP header to some extent.
  • a communication device having a function of implementing the behavior of a communication device in the above method.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the communication device includes: a processor, configured to: process the data stream, where the processing includes: adding the data stream to a service data adaptation protocol layer SDAP header, where the SDAP header includes a flow identifier indication, The flow identifier indication is used to indicate whether a flow identifier is included, and a transmitter is configured to send the processed data flow.
  • a processor configured to: process the data stream, where the processing includes: adding the data stream to a service data adaptation protocol layer SDAP header, where the SDAP header includes a flow identifier indication, The flow identifier indication is used to indicate whether a flow identifier is included, and a transmitter is configured to send the processed data flow.
  • the principle and the beneficial effects of the device can be seen in the above-mentioned method embodiments of the present application and the beneficial effects thereof. Therefore, the implementation of the device can be referred to the implementation of the method. No longer.
  • a communication device having a function of implementing the behavior of a communication device in the above method.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the communication device includes: a receiver, configured to receive a data stream, where the data stream includes a service data adaptation protocol layer SDAP header, where the SDAP header includes a flow identifier indication, where the flow identifier indication is used to indicate whether to include a stream identifier; a processor, configured to remove the SDAP header in the data stream.
  • the principle and the beneficial effects of the device can be seen in the above-mentioned method embodiments of the present application and the beneficial effects thereof. Therefore, the implementation of the device can be referred to the implementation of the method, and the method is repeated. I won't go into details here.
  • a still further aspect of the present application provides a data transmission method, including: a sending end device processing a data stream, where the processing includes: adding a flow identifier indication to the data flow, where the flow identifier indication is used for Indicate whether a flow identifier is included; the sender device sends the processed data stream.
  • a flow identifier indication is added to the data flow, and the flow identifier indication is used to indicate whether the flow identifier is included, and the data flow is transmitted according to the flow identifier indication, thereby completing the processing of the data flow; Indicates whether the flow identifier is included.
  • the processing specifically includes adding the flow identification indication at the head or end of the Service Data Adaptation Protocol Layer Protocol Data Unit SDAP PDU.
  • the flow identification indication can be added at the head or end of the newly added SDAP PDU.
  • the processing specifically includes adding the flow identification indication in a packet data mapping protocol PDCP header.
  • the flow identifier indication may be added to the PDCP header. If the flow identifier is not included, the SDAP header may not be needed, so the transmission overhead may be further saved.
  • the sending end device includes a base station, and the flow identifier indication is further used to indicate whether the data stream includes an access layer data flow reflection indication.
  • the method further includes: sending, by the base station, A signaling, wherein the first signaling includes a non-access stratum data flow reflection indication.
  • the sending end device includes a base station, where the flow identifier indication is further used to indicate whether the data flow includes a non-access stratum data flow reflection indication
  • the method further includes: sending, by the base station, The second signaling, wherein the second signaling comprises an access layer data flow reflection indication.
  • the flow identifier indication may also be used to implicitly indicate whether the access layer data flow reflection indication or the non-access layer data flow reflection indication is included in the data flow, which may save the overhead of the SDAP header or the PDCP header; Then it is transmitted by signaling.
  • the sending end device includes a base station; the method further includes: the base station sending an access layer data flow reflection indication by using radio resource control signaling; and the base station forwarding the non-connected from the core network Inbound data flow reflection indication.
  • the access layer data flow reflection indication and the non-access layer data flow reflection indication can be transmitted through signaling, and the overhead of the SDAP header can be saved.
  • the method further includes: the sending end device receiving the data flow; and the sending end device acquiring the flow identification indication.
  • the sending end device after receiving the data flow, the sending end device obtains the flow identification indication, and can learn to transmit several data flows, so as to perform subsequent processing on the data flow.
  • the method further includes: the sending end device removing the SDAP header in the SDAP PDU.
  • the sending end device receives the data stream, the service data adaptation protocol layer header in the data stream is removed, and the data stream is processed.
  • a further aspect of the present application provides a data transmission method, including: receiving, by a receiving device, a data stream, where the data stream includes a flow identifier indication, the flow identifier indication is used to indicate whether a flow identifier is included, and the receiving end The device acquires the flow identifier indication.
  • the receiving end device obtains the flow identification indication, and can learn to transmit several data flows, so as to perform subsequent processing on the data flow.
  • the flow identification indication is located at the head or end of the Service Data Adaptation Protocol layer protocol data unit SDAP PDU; or the flow identification indication is located in a Packet Data Mapping Protocol (PDCP) header.
  • PDCP Packet Data Mapping Protocol
  • the method further includes: the receiving end device removing the SDAP header in the SDAP PDU.
  • a service data adaptation protocol layer header is defined. After receiving the data stream, the service data adaptation protocol layer header in the data stream is removed, and the data stream is processed.
  • the SDAP header further includes a flow identifier, the flow identifier being located at a first byte and/or a second byte of the SDAP header.
  • the SDAP header needs to include the stream identifier, and part of the content of the stream identifier may be located in the first byte of the SDAP header to save the overhead of the SDAP header;
  • the length of the identifier is long, and the stream identifier can be located in the first byte and the second byte, or even more bytes.
  • the flow identifier indication is further used to indicate whether the data layer includes an access layer data flow reflection indication and a non-access layer data flow reflection indication.
  • the flow identifier indication may also be used to implicitly indicate whether the access layer data flow reflection indication and the non-access layer data flow reflection indication are included in the data flow, which may save signaling overhead.
  • the data stream further includes an indication of data information/control information.
  • the control information may be, for example, an access layer data flow reflection indication and a non-access layer data flow reflection indication, if the data information/control information is indicated.
  • the data stream includes data information, and the data stream does not need to include an access layer data flow reflection indication and a non-access layer data flow reflection indication; if the data information/control information indicates that the data flow includes control information, The data stream needs to include an access layer data flow reflection indication and a non-access layer data flow reflection indication, so that the signaling overhead can be saved to some extent.
  • the data stream further includes an uplink/downlink indication.
  • an uplink/downlink indication is added to the data stream, and the uplink layer transmission may not carry the access layer data flow reflection indication and the non-access layer data flow reflection indication. Therefore, if the uplink/downlink indication indicates the time If the transmission is an uplink transmission, the data stream does not need to include an access layer data flow indication indication and a non-access layer data flow reflection indication; if the uplink/downlink indication indicates that the transmission is a downlink transmission, the data stream may include an access layer. The data flow reflection indication and the non-access layer data flow reflection indication. This can save signaling overhead to some extent.
  • a communication device having a function of implementing the behavior of a communication device in the above method.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the communication device includes: a processor, configured to process a data stream, where the processing includes: adding a flow identifier indication to the data flow, the flow identifier indication is used to indicate whether a flow identifier is included; Used to send the processed data stream.
  • the principle and the beneficial effects of the device can be seen in the above-mentioned method embodiments of the present application and the beneficial effects thereof. Therefore, the implementation of the device can be referred to the implementation of the method. No longer.
  • a communication device having a function of implementing the behavior of a communication device in the above method.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the communication device includes: a receiver, configured to receive a data stream, where the data stream includes a flow identifier indication, the flow identifier indication is used to indicate whether a flow identifier is included, and a processor is configured to acquire the flow identifier.
  • the principle and the beneficial effects of the device can be seen in the above-mentioned method embodiments of the present application and the beneficial effects thereof. Therefore, the implementation of the device can be referred to the implementation of the method, and the method is repeated. I won't go into details here.
  • Yet another aspect of the present application provides a computer readable storage medium having instructions stored therein that, when executed on a computer, cause the computer to perform the methods described in the above aspects.
  • Yet another aspect of the present application provides a communication chip in which instructions are stored that, when run on a communication device, cause the computer to perform the methods described in the various aspects above.
  • Yet another aspect of the present application provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the methods described in the various aspects above.
  • FIG. 1 is a schematic diagram of a user plane protocol stack architecture of a next generation mobile communication network
  • FIG. 2 is a schematic structural diagram of a communication system according to an embodiment of the present invention.
  • FIG. 3 is a schematic diagram of interaction of a data transmission method according to an embodiment of the present invention.
  • FIG. 4 is a schematic structural diagram of a SDAP layer
  • FIG. 5 is a schematic diagram of interaction of an exemplary data transmission method
  • 6a-6k are schematic structural diagrams of an exemplary SDAP header
  • FIG. 7 is a schematic diagram of a communications device according to an embodiment of the present invention.
  • FIG. 8 is a schematic diagram of another communication device according to an embodiment of the present disclosure.
  • FIG. 9 is a schematic diagram of a communication device according to an embodiment of the present invention.
  • FIG. 2 is a schematic structural diagram of a communication system according to an embodiment of the present invention.
  • the communication system includes a base station and a terminal device.
  • the communication system may be a Global System for Mobile Communication (GSM), a Code Division Multiple Access (CDMA) system, a Wideband Code Division Multiple Access (WCDMA) system, or a global system.
  • GSM Global System for Mobile Communication
  • CDMA Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • WiMAX Worldwide Interoperability for Microwave Access
  • LTE long term evolution
  • 5G communication system such as new radio (NR) system
  • NR new radio
  • communication system with multiple communication technologies For example, a communication system in which LTE technology and NR technology are integrated, or a subsequent evolved communication system.
  • the terminal device in the present application is a device having a wireless communication function, and may be a handheld device having a wireless communication function, an in-vehicle device, a wearable device, a computing device, or other processing device connected to a wireless modem.
  • Terminal devices in different networks may be called different names, such as: User Equipment (UE), access terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user.
  • SIP Session Initiation Protocol
  • WLL Wireless Local Loop
  • PDA Personal Digital Assistant
  • the network device in the present application is a device deployed in a radio access network to provide wireless communication functions, including but not limited to: a base station (for example, a BTS (Base Transceiver Station, BTS), a Node B (NodeB, NB), Evolved Node B (eNB or eNodeB), a transmission node in a NR system, or a transmission reception point (TRP or TP) or a next generation Node B (gNB), a base station in a future communication network Or network equipment), relay stations, access points, in-vehicle devices, wearable devices, Wireless-Fidelity (Wi-Fi) sites, wireless backhaul nodes, small stations, micro stations, and so on.
  • a base station for example, a BTS (Base Transceiver Station, BTS), a Node B (NodeB, NB), Evolved Node B (eNB or eNodeB), a transmission node in a NR system, or a
  • base station 102 can include multiple antenna groups.
  • Each antenna group may include one or more antennas, for example, one antenna group may include antennas 104 and 106, another antenna group may include antennas 108 and 110, and may additionally include additional groups, and additional groups may include antennas 112 and 114 .
  • Different antenna groups in high frequency communication can be combined into different antenna panels. For example, one antenna group forms one beam, pointing in one direction, and the other antenna group forms another beam, pointing in the other direction, and With different device capabilities, more antennas may be needed. Therefore, depending on the device capabilities, additional groups can be set with different antenna numbers. Illustratively, 2 antennas are shown in Figure 2 for each antenna group, although more or fewer antennas may be used for each group.
  • Base station 102 can additionally include a transmitter chain and a receiver chain, as will be understood by those of ordinary skill in the art, which can include various components associated with signal transmission and reception, such as processors, modulators, multiplexers, demodulation , demultiplexer or antenna.
  • Base station 102 can communicate with one or more terminal devices, such as terminal device 116 and terminal device 122. However, it will be appreciated that base station 102 can communicate with any number of terminal devices similar to terminal device 116 or 122. As shown in FIG. 2, terminal device 116 is in communication with antennas 112 and 114, wherein antennas 112 and 114 transmit information to terminal device 116 over forward link 118 and receive information from terminal device 116 over reverse link 120. In addition, terminal device 122 is in communication with antennas 104 and 106, wherein antennas 104 and 106 transmit information to terminal device 122 over forward link 124 and receive information from terminal device 122 over reverse link 126.
  • the forward link 118 can utilize a different frequency band than that used by the reverse link 120, and the forward link 124 can utilize the reverse link 126. Different frequency bands used.
  • the forward link 118 and the reverse link 120 can use a common frequency band, and the forward link 124 and the reverse link 126 can use a common frequency band.
  • each set of antennas designed for communication and/or the area covered by the transmission is referred to as the sector of base station 102.
  • the antenna group can be designed to communicate with terminal devices in sectors of the coverage area of base station 102.
  • the transmit antenna of base station 102 may utilize beamforming to improve the signal to noise ratio of forward links 118 and 124.
  • the base station 102 uses beamforming to transmit signals to the randomly dispersed terminal devices 116 and 122 in the relevant coverage area, the base station 102 uses the beamforming to transmit signals to all of its access terminal devices. Mobile nodes are subject to less interference.
  • base station 102, terminal device 116 or terminal device 122 may be a wireless communication transmitting device and/or a wireless communication receiving device.
  • the wireless communication transmitting device can encode the data for transmission.
  • the wireless communication transmitting device may acquire, for example, generate, receive from another communication device, or save in a memory, etc., a certain number of data bits to be transmitted to the wireless communication receiving device through the channel.
  • Such data bits may be included in a transport block or a plurality of transport blocks of data, and the transport blocks may be segmented to produce a plurality of code blocks.
  • FIG. 1 is a schematic diagram of a user plane protocol stack architecture of a next-generation mobile communication network.
  • a service data adaptation protocol layer (Service Data Adaptation Protocol) is newly added on the basis of the LTE user plane protocol stack architecture.
  • SDAP Service Data Adaptation Protocol
  • LTE user plane protocol stack architecture includes: Packet Data Convergence Protocol (PDCP) layer, Radio Link Control Protocol (RLC) layer, Media Access Control Protocol (Media) Access Control Protocol (MAC) layer and Physical Layer Protocol (PHY) layer).
  • PDCP Packet Data Convergence Protocol
  • RLC Radio Link Control Protocol
  • Media Media Access Control Protocol
  • PHY Physical Layer Protocol
  • An embodiment of the present invention provides a data transmission method and a communication device, by adding a flow identifier indication to a data flow, where the flow identifier indication is used to indicate whether a flow identifier is included, and the data flow is transmitted according to the flow identifier indication, thereby completing the data.
  • Stream processing by adding a flow identifier indication to a data flow, where the flow identifier indication is used to indicate whether a flow identifier is included, and the data flow is transmitted according to the flow identifier indication, thereby completing the data.
  • FIG. 3 is a schematic diagram of interaction of a data transmission method according to an embodiment of the present invention.
  • the method may include the following steps:
  • the sender device processes the data stream.
  • the data stream may be an uplink transmission or a downlink transmission.
  • the sender device may be a base station or a terminal device, and the receiver device may also be a terminal device or a base station.
  • the data can be transmitted between the sender device and the receiver device through the air interface.
  • the transmitting device receives the data stream that is transmitted through the stream, and then transmits the data stream through the bearer, or the data stream that the transmitting device transmits through the bearer needs to be streamed. Therefore, mapping between the stream and the bearer is required. Therefore, the embodiment of the present invention adds an SDAP layer between the Transmission Control Protocol/Internet Protocol (TCP/IP) layer and the PDCP layer to facilitate data transmission.
  • TCP/IP Transmission Control Protocol/Internet Protocol
  • the SDAP layer is a protocol layer located between the TCP/IP layer and the PDCP layer, and the SDAP may be other names as long as the protocol layer located between the TCP/IP layer and the PDCP layer can be understood as The SDAP layer of this patent application is not limited herein.
  • the SDAP layer includes a SDAP header 401 and a SDAP Service Data Unit (SDU) 402.
  • the TCP/IP layer transmits an IP packet or data stream (IP Packet) to the SDAP layer, and the SDAP layer adds a SDAP header 401 to the data stream.
  • IP Packet IP packet or data stream
  • the above data stream can be regarded as a SDAP SDU.
  • the SDAP layer then transmits the data stream with the SDAP header to the PDCP layer, and the PDCP layer performs similar processing.
  • the PDCP header 404 plus the data stream of the SDAP header can be regarded as the PDCP SDU.
  • the data stream plus the PDCP header can be retransmitted to the next layer.
  • the subsequent processing can refer to the prior art, and details are not described herein again.
  • the processing of the nth IP packet and the n+1th IP packet is illustrated in FIG.
  • the size of the SDAP header cannot be known before processing the data stream, and the size of the SDAP header is mainly determined by the flow identifier (FID). Therefore, the flow identification of each data stream needs to be indicated to the receiving device.
  • FID flow identifier
  • a flow identifier indication is included in the SDAP header, and the flow identifier indication is used to indicate whether the flow identifier is included.
  • a flow identifier corresponds to a data flow, and one or more data flows can be mapped to one bearer. If the core network transmits to the source device or the sender device sends a data stream to the core network, the stream identifier may not be included. If the data stream is multiple data streams, the stream identifier needs to be included.
  • the identifier of the flow identifier may be 1 bit, and the value indicated by the flow identifier may be “1” and “0”.
  • the “1” indicates that the SDAP header includes the flow identifier
  • the “0” indicates that the SDAP header does not include the flow identifier.
  • “1” indicates that the SDAP header does not include the flow identifier
  • "0” indicates that the SDAP header includes the flow identifier.
  • the SDAP header can be located in front of the SDAP SDU or at the end of the SDAP SDU. If the SDAP header is located at the end of the SDAP SDU, it is convenient to apply the Robust Header Compression Protocol (RoHC) function.
  • RoHC Robust Header Compression Protocol
  • the flow identification indication can also be included in the PDCP header.
  • Not including the flow identifier can save transmission overhead.
  • the flow identifier indication in the PDCP header if the flow identifier is not included, the SDAP header may not be needed, so the transmission overhead may be further saved.
  • RoHC supports limited header compression for upper layer protocols such as TCP/IP and User Datagram Protocol (UDP)/IP. Therefore, the newly introduced SDAP protocol header will not be recognized by the RoHC protocol.
  • the PDCP can know the exact length of the SDAP header of each data flow. Therefore, the PDCP can extract the SDAP header before RoHC compression and compress it in RoHC. Then add back to the PDCP header. In this application, the sender only needs to add the flow identifier indication to the data stream, either at the SDAP header or at the end of the SDAP.
  • the sending end device sends the processed data stream.
  • the transmitting device After processing by the protocol stack, the transmitting device sends the processed data stream to the receiving device.
  • the receiving device receives the data stream.
  • the receiving end device acquires a flow identifier indication in the data flow.
  • the receiving device After receiving the data flow, the receiving device obtains the flow identifier indication, and can learn to transmit several data flows, so as to perform subsequent processing on the data flow.
  • the receiving end device removes the SDAP header in the SDAP PDU. After receiving the processed data stream, the receiving device adds the data stream of the SDAP header, and needs to remove the SDAP header to obtain the net data in the SDAP SDU. Or you need to transmit by streaming. For streaming, you need to remove the SDAP header and directly transfer data.
  • An embodiment of the present invention provides a data transmission method, by adding a flow identifier indication to a data flow, the flow identifier indication is used to indicate whether a flow identifier is included, and the data flow is transmitted according to the flow identifier indication, thereby completing the data flow. deal with.
  • FIG. 5 is an interaction diagram of an exemplary data transmission method.
  • Figure 5 includes signaling and data interaction between the UE, the base station, and the UPF.
  • the data transmission method includes the following steps: 501.
  • IP stream A downlink IP data stream (hereinafter referred to as "IP stream") reaches a UPF of a core network, and the UPF maps an IP data stream into a QoS data stream (hereinafter referred to as "QoS flow”. ").
  • QoS flow a QoS data stream
  • the UPF sends the QoS flow to the gNB (through streaming) through the interface between the access network and the core network, and the base station receives the QoS flow. 503.
  • gNB processes the QoS flow, that is, adds the SDAP header (of course, including processing of other protocol layers, refer to the prior art, and is not described herein), and maps the streamed QoS flow to the bearer. 504.
  • the GW transmits the QoS flow to the UE through the bearer, and the UE receives the QoS flow. 505.
  • the UE performs deheading processing on the received QoS data stream; at this point, the downlink transmission is completed. 506.
  • the UE may also perform uplink QoS data stream transmission. 507.
  • the UE processes the QoS data stream, that is, adds a SDAP header, and maps the QoS flow to the bearer. 508.
  • the UE transmits the QoS flow to the gNB through the bearer, and the gNB receives the QoS flow. After the 509.gNB receives the processed QoS flow and needs to stream to the core network, the QoS flow needs to be removed. 510.
  • the gNB streams the demarcated QoS flow to the UPF, and the UPF receives the QoS flow.
  • the base station in Figure 5 can be a gNB.
  • the FII indicator bit is located in the first byte.
  • the byte occupied by the SDAP header (Octal, Oct) is aligned with the byte in the SDAP SDU, the FII indicator bit is located in Oct1, and the FII indicator bit occupies 1 bit.
  • the other bits of the section are reserved (Reserved, R) to facilitate forward compatibility.
  • the flow identifier may be included in the second byte. It should be noted that if the length of the flow identifier is long, the third byte of the SDAP header and the following bytes can still be occupied as needed.
  • the stream identification is located in the second byte Oct2 and the third byte Oct3.
  • the flow identifier may also be located in the first byte occupied by the FII indicator bit.
  • part of the content of the FID is located in Oct1
  • the remaining part of the FID is located in Oct2 and Oct3. This saves the overhead of the SDAP header. If the stream identifier has a long length, it can continue to occupy the third byte of the SDAP header and the following bytes as needed. In the example of Figure 6b, the flow identifier is located in the first byte to the third byte of the SDAP header.
  • the UE may transmit in a manner of Reflective QoS.
  • the reflection QoS is a method for the UE to acquire the uplink data transmission IP flow to the QoS flow and the QoS flow to the bearer mapping manner.
  • the basic idea is that the UE transmits the IP flow to the QoS flow according to the downlink data, and the QoS flows to the bearer.
  • the mapping information is used to derive a mapping manner of the uplink data transmission QoS flow to the bearer.
  • the UPF will include a Reflective QoS Indication (RQI) in the header of the data stream.
  • RQI Reflective QoS Indication
  • the RQI includes an Access Stratum Reflective QoS Indication (ARI) and a Non-Access Stratum Reflective QoS Indication (NRI).
  • ARI Access Stratum Reflective QoS Indication
  • NRI Non-Access Stratum Reflective QoS Indication
  • a schematic diagram of another SDAP header includes a FII, an ARI, and an NRI.
  • the SDAP header further includes a flow identifier, where the FII, the ARI, and the The order of arrangement of NRIs is not limited.
  • ARI and NRI occupy 1 bit respectively.
  • the ARI value of "1" indicates that the QoS is used in the data stream transmission of the access layer
  • the ARI value of "0" indicates that the method of reflecting QoS is not used in the data stream transmission of the access layer
  • FIG. 6d is a schematic structural diagram of still another SDAP header, and FIG. 6d is different from FIG. 6c in that Oct1 further includes a part of the FID.
  • the above described scenario is that the same SDAP header is used for the uplink and downlink.
  • the uplink and downlink can also adopt different SDAP headers, that is, the uplink only needs to include the FII, and does not need to include the ARI and the NRI.
  • the structure of the uplink SDAP header is as shown in FIG. 6a. And Figure 6b.
  • the SDAP header includes the FII
  • the FII is further configured to indicate whether the SDAP header includes the ARI and the NRI. If the FII indication includes the flow identifier, the SDAP header further includes the flow identifier.
  • the FII implicitly indicates whether the SDAP header includes ARI and NRI, that is, for example, if the value of FII is "1", it implicitly indicates that the SDAP header includes ARI and NRI, if FII is taken. If the value is "0", it means that the SDAP header does not contain ARI and NRI. Otherwise, if the value of FII is "1”, it implies that the SDAP header does not contain ARI and NRI. If the value of FII is “0” implies that the SDAP header contains ARI and NRI. This saves the overhead of the SDAP header and facilitates forward compatibility.
  • the SDAP header includes the FII, and the FII is further configured to indicate whether the SDAP header includes the ARI. If the FII indication includes the flow identifier, the SDAP header further includes the flow identifier.
  • the configuration of another SDAP header is used to indicate whether the SDAP header includes an ARI, and when the transmitting device is a base station, the base station sends a first signaling, where the first signaling includes an NRI; The difference from FIG. 6e is that the content of the FID is also included in Oct1. This saves the overhead of the SDAP header and facilitates forward compatibility.
  • the SDAP header includes the FII, and the FII is further configured to indicate whether the SDAP header includes the NRI. If the FII indication includes the flow identifier, the SDAP header further includes the flow identifier.
  • Figure 6g a schematic diagram of another SDAP header is used. The FII is further configured to indicate whether the SDAP header includes an NRI, and when the transmitting device is a base station, the base station sends a second signaling, where the second signaling includes an ARI; The difference from FIG. 6g is that the content of the FID is also included in Oct1.
  • the SDAP header includes the FII, and if the FII indication includes the flow identifier, the SDAP header further includes the flow identifier.
  • the base station may send radio resource control (RRC) signaling to the UE, where the RRC signaling includes an ARI; and the base station forwards the NRI from the core network to the UE. That is, the base station is only transparent transmission between the core network element and the UE.
  • RRC radio resource control
  • the SDAP header includes a FII and a data information/control information indicator bit (D/C). If the FII indicator includes a flow identifier, the SDAP header further includes a flow identifier. Among them, ARI and NRI can be regarded as control information. Thus, the SDAP header carrying the ARI/NRI indication information can be expressed as: [C, FII, ARI, NRI, R, R, R, R]; the SDAP header that does not carry the ARI/NRI indication information can be expressed as: [ D, FII, R, R, R, R, R, R]. That is, as shown in the structural diagram of another SDAP header as illustrated in FIG.
  • the indication bits of the ARI and the NRI can be multiplexed.
  • the control information may also be other control information than ARI and NRI.
  • the difference between FIG. 6j and FIG. 6i is that the content of the stream identifier can also be included in Oct1.
  • the SDAP header includes a FII and a downlink/uplink indicator bit (D/U). If the FII indicator includes a flow identifier, the SDAP header further includes a flow identifier.
  • the SDAP header can be expressed as: [D, FII, ARI, NRI, R, R, R, R]; if it is uplink transmission, the SDAP header can be expressed as: [U, FII, R, R , R, R, R, R]. That is, the indication bits of ARI and NRI can be reused. This saves the overhead of the SDAP header and facilitates forward compatibility.
  • the SDAP header may be located before the SDAP SDU; in order to reduce the impact on the PDCP Header Compression (RoHC), the SDAP header may also be added at the end of the SDAP SDU.
  • the SDAP header is placed at the end of the SDAP SDU, and the FII indicator bit is aligned from the back end.
  • FIG. 7 is a schematic diagram of a module of a communication device according to an embodiment of the present invention.
  • the communication device 7000 may include: a processor 71 and a transmitter 72.
  • the processor 71 is configured to process the data stream, where the processing includes: adding a flow identifier indication to the data flow, where the flow identifier indication is used to indicate whether the flow identifier is included;
  • the transmitter 72 is configured to send the processed data stream.
  • the processing specifically includes adding the flow identification indication at the head or end of the Service Data Adaptation Protocol Layer Protocol Data Unit SDAP PDU.
  • the processing specifically includes adding the flow identification indication in a packet data mapping protocol PDCP header.
  • the communication device includes a base station
  • the flow identifier indication is further configured to indicate whether the access layer data flow reflection indication is included in the data flow
  • the transmitter 72 is further configured to send the first signaling, where the first signaling includes a non-access stratum data flow reflection indication NRI;
  • the flow identifier indication is further used to indicate whether the data flow includes a non-access stratum data flow reflection indication
  • the transmitter 72 is further configured to send the second signaling, where the second signaling includes the access layer data flow reflection indication.
  • the communication device includes a base station
  • the transmitter 72 is further configured to send an access layer data flow reflection indication by using radio resource control signaling;
  • the transmitter 72 is further configured to forward a non-access stratum data flow reflection indication from the core network.
  • the communication device 7000 further includes: a receiver (not shown);
  • the receiver is configured to receive the data stream
  • the processor is further configured to obtain the flow identifier indication.
  • the processor is further configured to remove a SDAP header in the SDAP PDU in the data stream.
  • the SDAP header further includes a flow identifier, the flow identifier being located at a first byte and/or a second byte of the SDAP header.
  • the flow identifier indication is further configured to indicate whether the access layer data flow reflection indication and the non-access layer data flow reflection indication are included in the data flow.
  • the data stream further includes an indication of the data information/control information.
  • a communication device by adding a flow identifier indication in a data flow, the flow identifier indication is used to indicate whether a flow identifier is included, and the data flow is transmitted according to the flow identifier indication, thereby completing the processing of the data flow.
  • FIG. 8 is a schematic block diagram of another communication device according to an embodiment of the present invention.
  • the communication device 8000 includes a receiver 81 and a processor 82.
  • a receiver configured to receive a data stream, where the data stream includes a flow identifier indication, where the flow identifier indication is used to indicate whether the flow identifier is included;
  • the processor is configured to obtain the flow identifier indication.
  • the flow identification indication is located at the head or end of the Service Data Adaptation Protocol layer protocol data unit SDAP PDU; or the flow identification indication is located in a Packet Data Mapping Protocol (PDCP) header.
  • PDCP Packet Data Mapping Protocol
  • the processor is further configured to remove a SDAP header in the SDAP PDU.
  • the SDAP header further includes a flow identifier, where the flow identifier is located in a first byte and/or a second byte of the SDAP header.
  • the flow identifier indication is further used to indicate whether the access layer data flow reflection indication and the non-access layer data flow reflection indication are included in the data flow.
  • the data stream further includes an indication of the data information/control information.
  • a communication device by adding a flow identifier indication in a data flow, the flow identifier indication is used to indicate whether a flow identifier is included, and the data flow is transmitted according to the flow identifier indication, thereby completing the processing of the data flow.
  • the embodiment of the present invention further provides a communication device, which can adopt the hardware architecture shown in FIG. 9.
  • the communication device can be a base station or a terminal device.
  • the communication device can include a receiver, a transmitter, a memory, and a processor, the receiver, transmitter, memory, and processor being interconnected by a bus.
  • the memory includes, but is not limited to, a random access memory (RAM), a read-only memory (ROM), an Erasable Programmable Read Only Memory (EPROM), or a portable Compact Disc Read-Only Memory (CD-ROM), which is used for related instructions and data.
  • RAM random access memory
  • ROM read-only memory
  • EPROM Erasable Programmable Read Only Memory
  • CD-ROM portable Compact Disc Read-Only Memory
  • the receiver is for receiving data and/or signals
  • the transmitter is for transmitting data and/or signals.
  • the transmitter and receiver can be separate devices or an integral device such as a transceiver.
  • the processor may include one or more processors, for example, including one or more central processing units (CPUs).
  • CPUs central processing units
  • the CPU may be a single-core CPU, or may be Multi-core CPU.
  • the memory is used to store program code and data for the communication device and can be a separate device or integrated into the processor.
  • the above various devices can be implemented in a chip integrated, for example, integrated in a baseband chip.
  • the processor performs the following operations:
  • the data stream is processed, where the processing includes: adding a flow identifier indication to the data flow, where the flow identifier indication is used to indicate whether the flow identifier is included;
  • the processed data stream is transmitted by the transmitter.
  • the processing specifically includes adding the flow identification indication at the head or end of the Service Data Adaptation Protocol Layer Protocol Data Unit SDAP PDU.
  • the processing specifically includes adding the flow identification indication in a packet data mapping protocol PDCP header.
  • the communication device includes a base station
  • the flow identifier indication is further configured to indicate whether the access layer data flow reflection indication is included in the data flow
  • the flow identifier indication is further used to indicate whether the data flow includes a non-access stratum data flow reflection indication
  • the communication device includes a base station
  • the non-access stratum data flow reflection indication from the core network is forwarded by the transmitter.
  • the processor is further configured to:
  • the processor after the processor performs the receiving of the data stream by the receiver, the processor further performs the operation of removing the SDAP header in the data stream.
  • the SDAP header further includes a flow identifier, where the flow identifier is located in a first byte and/or a second byte of the SDAP header.
  • the flow identifier indication is further configured to indicate whether the access layer data flow reflection indication and the non-access layer data flow reflection indication are included in the data flow.
  • the data stream further includes an indication of the data information/control information.
  • Figure 9 only shows a simplified design of the communication device.
  • the communication device may also include other necessary components, including but not limited to any number of transceivers, processors, controllers, memories, etc., and all communication devices that can implement the embodiments of the present invention are in the present invention. Within the scope of protection.
  • a communication device by adding a flow identifier indication in a data flow, the flow identifier indication is used to indicate whether a flow identifier is included, and the data flow is transmitted according to the flow identifier indication, thereby completing the processing of the data flow.
  • the embodiment of the present invention further provides a communication device, which may be a communication device in the foregoing communication system, for example, may be a base station or a terminal device.
  • the communication device can adopt the hardware architecture shown in FIG.
  • the communication device can include a receiver, a transmitter, a memory, and a processor, the receiver, transmitter, memory, and processor being interconnected by a bus.
  • the memory includes, but is not limited to, RAM, ROM, EPROM, CD-ROM, which is used for related instructions and data.
  • the receiver is for receiving data and/or signals
  • the transmitter is for transmitting data and/or signals.
  • the transmitter and receiver can be separate devices or an integral device such as a transceiver.
  • the processor may include one or more processors, for example including one or more CPUs.
  • the processor may be a single core CPU or a multi-core CPU.
  • the memory is used to store program code and data for the communication device and can be a separate device or integrated into the processor.
  • the above various devices can be implemented in a chip integrated, for example, integrated in a baseband chip.
  • the processor performs the following operations:
  • the flow identification indication is located at the head or end of the Service Data Adaptation Protocol layer protocol data unit SDAP PDU; or the flow identification indication is located in a Packet Data Mapping Protocol (PDCP) header.
  • PDCP Packet Data Mapping Protocol
  • the processor is further configured to: remove the SDAP header in the SDAP PDU.
  • the SDAP header further includes a flow identifier, where the flow identifier is located in a first byte and/or a second byte of the SDAP header.
  • the flow identifier indication is further configured to indicate whether the access layer data flow reflection indication and the non-access layer data flow reflection indication are included in the data flow.
  • the data stream further includes an indication of the data information/control information.
  • Figure 9 only shows a simplified design of the communication device.
  • the communication device may also include other necessary components, including but not limited to any number of transceivers, processors, controllers, memories, etc., and all communication devices that can implement the present invention are protected by the present invention.
  • the communication device may also include other necessary components, including but not limited to any number of transceivers, processors, controllers, memories, etc., and all communication devices that can implement the present invention are protected by the present invention.
  • a communication device by adding a flow identifier indication in a data flow, the flow identifier indication is used to indicate whether a flow identifier is included, and the data flow is transmitted according to the flow identifier indication, thereby completing the processing of the data flow.
  • the disclosed systems, devices, and methods may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above embodiments it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • software it may be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions.
  • the computer program instructions When the computer program instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present invention are generated in whole or in part.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions can be stored in or transmitted by a computer readable storage medium.
  • the computer instructions can be from a website site, computer, server or data center to another website site by wire (eg, coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (eg, infrared, wireless, microwave, etc.) Transfer from a computer, server, or data center.
  • the computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media.
  • the usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (such as a Solid State Disk (SSD)) or the like.
  • the program can be stored in a computer readable storage medium, when the program is executed
  • the flow of the method embodiments as described above may be included.
  • the foregoing storage medium includes various media that can store program codes, such as a ROM or a random access memory RAM, a magnetic disk, or an optical disk.

Landscapes

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

Abstract

本申请公开了一种数据传输方法及通信设备。其中的方法包括：发送端设备将数据流进行处理，其中，所述处理包括：将所述数据流添加流标识指示，所述流标识指示用于指示是否包括流标识；所述发送端设备发送所述经过处理的数据流。还公开了相应的通信设备。采用本申请的技术方案，通过在数据流中添加流标识指示，流标识指示用于指示是否包含流标识，根据该流标识指示进行数据流的传输，从而完成了数据流的处理。

Description

数据传输方法及通信设备
本申请要求于2017年5月5日提交中国专利局、申请号为CN201710313752.7、发明名称为“数据传输方法及通信设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本发明涉及通信技术领域，尤其涉及一种数据传输方法及通信设备。
背景技术
在现有的长期演进(Long Term Evolution，LTE)通信系统中，基于承载(bearer)实现端到端的服务质量(Quality of Service)机制。而在下一代移动通信系统(例如，第五代移动通信(5 th-Generation，5G))中引入了QoS流的概念，数据可以用基于QoS流的方式在核心网(Core Network，CN)以及CN和接入网(Access Network，AN)之间的接口上传递。而在AN内部包括空口保留了承载的概念，一个或多个QoS流可以映射到同一个承载。
和LTE中端到端的演进分组系统(Evolved Packet System，EPS)的承载概念不同，在5G网络的QoS架构中存在两层映射。以下行为例，当下行网络协议(Internet Protocol，IP)数据流到达核心网的用户面功能网元(User Plane Function，UPF)时，UPF先把IP数据流映射到QoS流，然后把QoS流数据通过接入网与核心网间的接口发送到下一代接入网基站(NG-RAN NodeB，gNB)，然后gNB把QoS流映射到承载。目前LTE的用户面协议栈架构不能完成数据流的处理。
发明内容
本申请提供了一种数据传输方法及通信设备，以期完成数据流的处理。
本申请的一方面，提供了一种数据传输方法，包括：发送端设备将数据流进行处理，其中，所述处理包括：将所述数据流添加服务数据适配协议层SDAP头，其中，所述SDAP头包括流标识指示，所述流标识指示用于指示是否包括流标识；所述发送端设备发送所述经过处理的数据流。在该实现方式中，定义了服务数据适配协议层头，通过将数据流添加服务数据适配协议层头，对数据流进行处理，发送经过处理的数据；在接收到该数据流后，去掉数据流中的服务数据适配协议层头，完成了数据流的处理；且通过流标识指示用于指示是否包含流标识，如果流标识指示是指示不包含流标识，则SDAP头中无需为流标识配置字节，从而可以节省空口开销。在一个实现方式中，所述发送端设备包括基站；所述流标识指示还用于指示所述SDAP头是否包含接入层数据流反射指示；所述方法还包括：所述基站发送第一信令，其中，所述第一信令包括非接入层数据流反射指示。或者在一个实现方式中，所述发送端设备包括基站，所述流标识指示还用于指示所述SDAP头是否包含非接入层数据流反射指示；所述方法还包括：所述基站发送第二信令，其中，所述第二信令包括接入层数据流反射指示。在该实现方式中，流标识指示还可用于隐含指示SDAP头 是否包含接入层数据流反射指示或非接入层数据流反射指示，可以节省SDAP头的开销；另一个指示则通过信令传输。
在另一个实现方式中，所述发送端设备包括基站；所述方法还包括：所述基站通过无线资源控制信令发送接入层数据流反射指示；以及所述基站转发来自核心网的非接入层数据流反射指示。在该实现方式中，接入层数据流反射指示和非接入层数据流反射指示可通过信令传输，可以节省SDAP头的开销。
在又一个实现方式中，所述方法还包括：所述发送端设备接收所述数据流；所述发送端设备去掉所述数据流中的所述SDAP头。在该实现方式中，发送端设备接收到数据流时，去掉数据流中的服务数据适配协议层头，完成了数据流的处理。
本申请的另一方面，提供了一种数据传输方法，包括：接收端设备接收数据流，所述数据流包括服务数据适配协议层SDAP头，其中，所述SDAP头包括流标识指示，所述流标识指示用于指示是否包括流标识；所述接收端设备去掉所述数据流中的所述SDAP头。在该实现方式中，定义了服务数据适配协议层头，在接收到该数据流后，去掉数据流中的服务数据适配协议层头，完成了数据流的处理。
结合本申请的一方面和另一方面，在一个实现方式中，所述SDAP头还包括流标识，所述流标识位于所述SDAP头的第一字节和/或第二字节。在该实现方式中，若通过流传输多个数据流映射到承载，则SDAP头需包括流标识，流标识的部分内容可位于SDAP头的第一字节，以节省SDAP头的开销；若流标识的长度较长，流标识可以位于第一字节和第二字节，甚至更多的字节中。
结合本申请的一方面和另一方面，在另一个实现方式中，所述流标识指示还用于指示所述SDAP头是否包含接入层数据流反射指示ARI和非接入层数据流反射指示NRI。在该实现方式中，流标识指示还可用于隐含指示SDAP头是否包含接入层数据流反射指示和非接入层数据流反射指示，可以节省SDAP头的开销。
结合本申请的一方面和另一方面，在又一个实现方式中，所述SDAP头还包括数据信息/控制信息的指示。在该实现方式中，通过在SDAP头中添加数据信息/控制信息的指示，控制信息例如可以是接入层数据流反射指示和非接入层数据流反射指示，如果数据信息/控制信息的指示该SDAP头包括的是数据信息，则SDAP头中无需包括接入层数据流反射指示和非接入层数据流反射指示；如果数据信息/控制信息的指示该SDAP头包括的是控制信息，则SDAP头中需包括接入层数据流反射指示和非接入层数据流反射指示，这样可以一定程度上节省SDAP头的开销。
结合本申请的一方面和另一方面，在又一个实现方式中，所述SDAP头还包括上行/下行指示。在该实现方式中，在SDAP头中添加上行/下行指示，由于上行传输时可以不携带接入层数据流反射指示和非接入层数据流反射指示，因此，如果上行/下行指示指示该次传输为上行传输，则SDAP头中无需包括接入层数据流反射指示和非接入层数据流反射指示；如果上行/下行指示指示该次传输为下行传输，则SDAP头中可以包括接入层数据流反射指示和非接入层数据流反射指示。这样可以一定程度上节省SDAP头的开销。
本申请的又一方面，提供了一种通信设备，该通信设备具有实现上述方法中通信设备行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬 件或软件包括一个或多个与上述功能相对应的模块。
所述通信设备包括：处理器，用于将数据流进行处理，其中，所述处理包括：将所述数据流添加服务数据适配协议层SDAP头，其中，所述SDAP头包括流标识指示，所述流标识指示用于指示是否包括流标识；发送器，用于发送所述经过处理的数据流。
基于同一发明构思，由于该装置解决问题的原理以及有益效果可以参见上述本申请的一方面的方法实施方式以及所带来的有益效果，因此该装置的实施可以参见该方法的实施，重复之处不再赘述。
本申请的又一方面，提供了一种通信设备，该通信设备具有实现上述方法中通信设备行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
所述通信设备包括：接收器，用于接收数据流，所述数据流包括服务数据适配协议层SDAP头，其中，所述SDAP头包括流标识指示，所述流标识指示用于指示是否包括流标识；处理器，用于去掉所述数据流中的所述SDAP头。
基于同一发明构思，由于该装置解决问题的原理以及有益效果可以参见上述本申请的另一方面的方法实施方式以及所带来的有益效果，因此该装置的实施可以参见该方法的实施，重复之处不再赘述。
本申请的又一方面，提供了一种数据传输方法，包括：发送端设备将数据流进行处理，其中，所述处理包括：将所述数据流添加流标识指示，所述流标识指示用于指示是否包括流标识；所述发送端设备发送所述经过处理的数据流。在该实现方式中，数据流中添加流标识指示，流标识指示用于指示是否包含流标识，根据该流标识指示进行数据流的传输，从而完成了数据流的处理；且通过流标识指示用于指示是否包含流标识，如果流标识指示是指示不包含流标识，则SDAP头中无需为流标识配置字节，从而可以节省空口开销。在一个实现方式中，所述处理具体包括在服务数据适配协议层协议数据单元SDAP PDU的头部或末尾添加所述流标识指示。在该实现方式中，流标识指示可以添加在新增加的SDAP PDU的头部或末尾。
在另一个实现方式中，所述处理具体包括在分组数据映射协议PDCP头中添加所述流标识指示。在该实现方式中，流标识指示可以添加在PDCP头，如果不包括流标识，则可以不需要SDAP头，所以可以进一步节省传输开销。
在又一个实现方式中，所述发送端设备包括基站；所述流标识指示还用于指示所述数据流中是否包含接入层数据流反射指示；所述方法还包括：所述基站发送第一信令，其中，所述第一信令包括非接入层数据流反射指示。或者在一个实现方式中，所述发送端设备包括基站，所述流标识指示还用于指示所述数据流中是否包含非接入层数据流反射指示；所述方法还包括：所述基站发送第二信令，其中，所述第二信令包括接入层数据流反射指示。在该实现方式中，流标识指示还可用于隐含指示数据流中是否包含接入层数据流反射指示或非接入层数据流反射指示，可以节省SDAP头或PDCP头的开销；另一个指示则通过信令传输。
在又一个实现方式中，所述发送端设备包括基站；所述方法还包括：所述基站通过无线资源控制信令发送接入层数据流反射指示；以及所述基站转发来自核心网的非接入层数 据流反射指示。在该实现方式中，接入层数据流反射指示和非接入层数据流反射指示可通过信令传输，可以节省SDAP头的开销。
在又一个实现方式中，所述方法还包括：所述发送端设备接收所述数据流；所述发送端设备获取所述流标识指示。在该实现方式中，发送端设备接收到数据流后，获取流标识指示，可以了解传输了几个数据流，从而对数据流进行后续的处理。
在又一个实现方式中，所述发送端设备接收所述数据流之后，所述方法还包括：所述发送端设备去掉所述SDAP PDU中的SDAP头。在该实现方式中，发送端设备接收到数据流时，去掉数据流中的服务数据适配协议层头，完成了数据流的处理。
本申请的又一方面，提供了一种数据传输方法，包括：接收端设备接收数据流，所述数据流包括流标识指示，所述流标识指示用于指示是否包括流标识；所述接收端设备获取所述流标识指示。在该实现方式中，接收端设备接收到数据流后，获取流标识指示，可以了解传输了几个数据流，从而对数据流进行后续的处理。
在一个实现方式中，所述流标识指示位于服务数据适配协议层协议数据单元SDAP PDU的头部或末尾；或所述流标识指示位于分组数据映射协议PDCP头中。
在另一个实现方式中，所述接收端设备接收数据流之后，所述方法还包括：所述接收端设备去掉所述SDAP PDU中的SDAP头。在该实现方式中，定义了服务数据适配协议层头，在接收到该数据流后，去掉数据流中的服务数据适配协议层头，完成了数据流的处理。
结合本申请的一方面和另一方面，在一个实现方式中，所述SDAP头还包括流标识，所述流标识位于所述SDAP头的第一字节和/或第二字节。在该实现方式中，若通过流传输多个数据流映射到承载，则SDAP头需包括流标识，流标识的部分内容可位于SDAP头的第一字节，以节省SDAP头的开销；若流标识的长度较长，流标识可以位于第一字节和第二字节，甚至更多的字节中。
结合本申请的一方面和另一方面，在另一个实现方式中，所述流标识指示还用于指示所述数据流中是否包含接入层数据流反射指示和非接入层数据流反射指示。在该实现方式中，流标识指示还可用于隐含指示数据流中是否包含接入层数据流反射指示和非接入层数据流反射指示，可以节省信令开销。
结合本申请的一方面和另一方面，在又一个实现方式中，所述数据流中还包括数据信息/控制信息的指示。在该实现方式中，通过在数据流中添加数据信息/控制信息的指示，控制信息例如可以是接入层数据流反射指示和非接入层数据流反射指示，如果数据信息/控制信息的指示该数据流包括的是数据信息，则数据流中无需包括接入层数据流反射指示和非接入层数据流反射指示；如果数据信息/控制信息的指示该数据流包括的是控制信息，则数据流中需包括接入层数据流反射指示和非接入层数据流反射指示，这样可以一定程度上节省信令的开销。
结合本申请的一方面和另一方面，在又一个实现方式中，所述数据流还包括上行/下行指示。在该实现方式中，在数据流中添加上行/下行指示，由于上行传输时可以不携带接入层数据流反射指示和非接入层数据流反射指示，因此，如果上行/下行指示指示该次传输为上行传输，则数据流中无需包括接入层数据流反射指示和非接入层数据流反射指示；如果上行/下行指示指示该次传输为下行传输，则数据流中可以包括接入层数据流反射指示和非 接入层数据流反射指示。这样可以一定程度上节省信令的开销。
本申请的又一方面，提供了一种通信设备，该通信设备具有实现上述方法中通信设备行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
所述通信设备包括：处理器，用于将数据流进行处理，其中，所述处理包括：将所述数据流添加流标识指示，所述流标识指示用于指示是否包括流标识；发送器，用于发送所述经过处理的数据流。
基于同一发明构思，由于该装置解决问题的原理以及有益效果可以参见上述本申请的一方面的方法实施方式以及所带来的有益效果，因此该装置的实施可以参见该方法的实施，重复之处不再赘述。
本申请的又一方面，提供了一种通信设备，该通信设备具有实现上述方法中通信设备行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
所述通信设备包括：接收器，用于接收数据流，所述数据流包括流标识指示，所述流标识指示用于指示是否包括流标识；处理器，用于获取所述流标识。
基于同一发明构思，由于该装置解决问题的原理以及有益效果可以参见上述本申请的另一方面的方法实施方式以及所带来的有益效果，因此该装置的实施可以参见该方法的实施，重复之处不再赘述。
本申请的又一方面提供了一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机执行上述各方面所述的方法。
本申请的又一方面提供了一种通信芯片，其中存储有指令，当其在通信设备上运行时，使得计算机执行上述各方面所述的方法。
本申请的又一方面提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述各方面所述的方法。
附图说明
为了更清楚地说明本发明实施例或背景技术中的技术方案，下面将对本发明实施例或背景技术中所需要使用的附图进行说明。
图1为下一代移动通信网络的用户面协议栈架构示意图；
图2为本发明实施例涉及的一种通信系统架构示意图；
图3为本发明实施例提供的一种数据传输方法的交互示意图；
图4为SDAP层结构示意图；
图5为示例的一种数据传输方法的交互示意图；
图6a～图6k为示例的SDAP头的结构示意图；
图7为本发明实施例提供的一种通信设备的示意图；
图8为本发明实施例提供的另一种通信设备的示意图；
图9为本发明实施例提供的一种通信设备的示意图。
具体实施方式
下面结合本发明实施例中的附图对本发明实施例进行描述。
请参阅图2，图2为本发明实施例涉及的一种通信系统架构示意图。该通信系统包括基站和终端设备。该通信系统可以是全球移动通信系统(Global System for Mobile Communication，GSM)、码分多址(Code Division Multiple Access，CDMA)系统、宽带码分多址(Wideband Code Division Multiple Access，WCDMA)系统、全球微波互联接入(Worldwide Interoperability for Microwave Access，WiMAX)系统、长期演进(long term evolution，LTE)系统、5G通信系统(例如新空口(new radio，NR)系统、多种通信技术融合的通信系统(例如LTE技术和NR技术融合的通信系统)、或者后续演进通信系统。
本申请中的终端设备是一种具有无线通信功能的设备，可以是具有无线通信功能的手持设备、车载设备、可穿戴设备、计算设备或连接到无线调制解调器的其它处理设备等。在不同的网络中终端设备可以叫做不同的名称，例如：用户设备(User Equipment，UE)、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置、蜂窝电话、无绳电话、会话启动协议(Session Initiation Protocol，SIP)电话、无线本地环路(Wireless Local Loop，WLL)站、个人数字处理(Personal Digital Assistant，PDA)、5G网络或未来演进网络中的终端设备等。
本申请中的网络设备是一种部署在无线接入网用以提供无线通信功能的设备，包括但不限于：基站(例如：BTS(Base Transceiver Station，BTS)、节点B(NodeB，NB)、演进型基站B(Evolutional Node B，eNB或eNodeB)、NR系统中的传输节点或收发点(transmission reception point，TRP或者TP)或者下一代节点B(generation nodeB，gNB)、未来通信网络中的基站或网络设备)、中继站、接入点、车载设备、可穿戴设备、无线保真(Wireless-Fidelity，Wi-Fi)的站点、无线回传节点、小站、微站等等。
具体地，在图2中，基站102可包括多个天线组。每个天线组可以包括一个或多个天线，例如，一个天线组可包括天线104和106，另一个天线组可包括天线108和110，另外还可以包括附加组，附加组可包括天线112和114。高频通信中不同的天线组可以组合成不同的天线面(panel)，例如，其中的一个天线组形成一个波束，指向一个方向，另一个天线组形成另外一个波束，指向另一个方向，而为了配合不同的设备能力，可能需要更多的天线，因此，根据不同的设备能力，附加组可以设置有不同的天线数。示例性地，图2中对于每个天线组示出了2个天线，然而可对于每个组使用更多或更少的天线。基站102可附加地包括发射机链和接收机链，本领域普通技术人员可以理解，它们均可包括与信号发送和接收相关的多个部件，例如处理器、调制器、复用器、解调器、解复用器或天线等。
基站102可以与一个或多个终端设备，例如终端设备116和终端设备122通信。然而，可以理解，基站102可以与类似于终端设备116或122的任意数目的终端设备通信。如图2所示，终端设备116与天线112和114通信，其中天线112和114通过前向链路118向终端设备116发送信息，并通过反向链路120从终端设备116接收信息。此外，终端设备122与天线104和106通信，其中天线104和106通过前向链路124向终端设备122发送信息，并通过反向链路126从终端设备122接收信息。在频分双工(Frequency Division Duplex，FDD)系统中，例如，前向链路118可利用与反向链路120所使用的不同频带， 前向链路124可利用与反向链路126所使用的不同频带。此外，在时分双工(Time Division Duplex，TDD)系统中，前向链路118和反向链路120可使用共同频带，前向链路124和反向链路126可使用共同频带。
被设计用于通信的每组天线覆盖的区域和/或发射覆盖的区域称为基站102的扇区。例如，可将天线组设计为与基站102覆盖区域的扇区中的终端设备通信。在基站102通过前向链路118和124分别与终端设备116和122进行通信的过程中，基站102的发射天线可利用波束成形来改善前向链路118和124的信噪比。此外，与基站通过单个天线向它所有的接入终端设备发送信号的方式相比，在基站102利用波束成形向相关覆盖区域中随机分散的终端设备116和122发送信号时，相邻小区中的移动节点会受到较少的干扰。
在给定时间，基站102、终端设备116或终端设备122可以是无线通信发送装置和/或无线通信接收装置。当发送数据时，无线通信发送装置可对数据进行编码以用于传输。具体地，无线通信发送装置可获取，例如生成、从其它通信装置接收、或在存储器中保存等，要通过信道发送至无线通信接收装置的一定数目的数据比特。这种数据比特可包含在数据的传输块或多个传输块中，传输块可被分段以产生多个码块。
如图1所示的下一代移动通信网络的用户面协议栈架构示意图，在下一代移动通信中，在LTE的用户面协议栈架构的基础上新加入服务数据适配协议层(Service Data Adaptation Protocol，SDAP)(LTE的用户面协议栈架构包括：分组数据映射协议(Packet Data Convergence Protocol，PDCP)层、无线链路控制层协议(Radio Link Control Protocol，RLC)层、介质接入控制协议(Media Access Control Protocol，MAC)层和物理层协议(Physical Layer Protocol，PHY)层)。然而，目前并没有对SDAP层的包头的定义，不能完成数据流的处理，进行数据流的传输。
本发明实施例提供一种数据传输方法及通信设备，通过在数据流中添加流标识指示，流标识指示用于指示是否包含流标识，根据该流标识指示进行数据流的传输，从而完成了数据流的处理。
请参阅图3，图3为本发明实施例提供的一种数据传输方法的交互示意图，该方法可包括以下步骤：
S301、发送端设备将数据流进行处理。
本实施例中，数据流可以是上行传输，也可以是下行传输。发送端设备可以是基站或终端设备，接收端设备也可以是终端设备或基站。发送端设备与接收端设备之间可以是通过空口承载进行数据传输。发送端设备接收通过流传输的数据流，然后通过承载传输该数据流，或者发送端设备通过承载传输的数据流需要进行流传输，因此，需要进行流与承载之间的映射。因此，本发明实施例在传输控制协议/因特网互联协议(Transmission Control Protocol/Internet Protocol，TCP/IP)层与PDCP层之间添加了SDAP层，以方便数据传输。需要说明的是，SDAP层是位于TCP/IP层与PDCP层之间的一个协议层，SDAP还可以是其它的名称，只要位于TCP/IP层与PDCP层之间的协议层，都可以理解为本专利申请的SDAP层，在此不作限定。
如图4所示的SDAP层结构示意图，SDAP层包括SDAP头(SDAP Head)401和SDAP服务数据单元(Service Data Unit，SDU)402。在图4中，TCP/IP层将IP数据包或称数据 流(IP Packet)传输至SDAP层，SDAP层在数据流上加上SDAP头401。上述数据流可以看做是SDAP SDU。SDAP层然后将加上SDAP头的数据流传输给PDCP层，PDCP层作类似的处理，加上PDCP头404，加上SDAP头的数据流可以被看做是PDCP SDU。加上PDCP头的数据流可以被再传输至下一层。后面的处理可参考现有技术，在此不再赘述。图4中示例了第n个IP包和第n+1个IP包的处理。
在NR中，当接收端设备接收到数据流时，在处理数据流前无法知道SDAP头的大小，并且SDAP头的大小主要决定于流标识(Flow ID，FID)。因此，每个数据流的流标识需要指示给接收端设备。
在一个实现方式中，在SDAP头中包括流标识指示(Flow ID Indication，FII)，所述流标识指示用于指示是否包括流标识。一个流标识对应一个数据流，可以一个或多个数据流映射到一个承载上。如果核心网传输给发送端设备或者发送端设备向核心网发送的是一个数据流，则可以不包括该流标识，如果是多个数据流，则需要包括该流标识。该流标识指示可以是1比特，该流标识指示的取值可以是“1”和“0”，例如用“1”表示SDAP头包括流标识，用“0”表示SDAP头不包括流标识；或者反之，用“1”表示SDAP头不包括流标识，用“0”表示SDAP头包括流标识。该SDAP头可以位于SDAP SDU的前面，也可以位于SDAP SDU的末尾。如果SDAP头位于SDAP SDU的末尾，可以方便应用健壮性报头压缩协议(RoHC)功能。
在另一个实现方式中，也可以在PDCP头中包括该流标识指示。
如果在PDCP头中包括该流标识指示，可以具有如下技术效果：
1)节省传输开销
不包括流标识可以节省传输开销。对于在PDCP头中包括流标识指示的方式，如果不包括流标识，则可以不需要SDAP头，所以可以进一步节省传输开销。
2)方便应用健壮性报头压缩协议(RoHC)功能
RoHC支持有限的上层协议的头压缩，例如TCP/IP和用户数据报协议(User Datagram Protocol，UDP)/IP。因此，新引入的SDAP协议头不会被RoHC协议识别。对于在PDCP头中包括流标识指示的方式，由于流标识指示位于PDCP中，PDCP可以知道每个数据流的SDAP头的确切长度，因此，PDCP可以在RoHC压缩前提取SDAP头，并在RoHC压缩后加回到PDCP头中。本申请中，发送端只要将流标识指示添加到数据流即可，可以在SDAP头，也可以在SDAP末尾。
S302、所述发送端设备发送所述经过处理的数据流。
经过协议栈的处理后，发送端设备发送经过处理的数据流到接收端设备。接收端设备接收该数据流。
S303、接收端设备获取所述数据流中的流标识指示。
接收端设备接收到数据流后，获取流标识指示，可以了解传输了几个数据流，从而对数据流进行后续的处理。
进一步地，接收端设备去掉所述SDAP PDU中的SDAP头。接收端设备接收到经过处理的数据流后，即添加了SDAP头的数据流，需要去掉该SDAP头，以获得SDAP SDU中的净数据。或者需要通过流传输进行传输，进行流传输也需要去掉SDAP头，直接进行数 据传输。
根据本发明实施例提供一种数据传输方法，通过在数据流中添加流标识指示，流标识指示用于指示是否包含流标识，根据该流标识指示进行数据流的传输，从而完成了数据流的处理。
下面以下行传输和上行传输对上述数据传输流程分别进行描述。在下行传输中，则发送端设备是基站，接收端设备是终端设备；在上行传输中，则发送端设备是终端设备，接收端设备是基站。因而，当发送端设备接收数据流，该方法进一步还可包括：接收所述数据流；去掉所述数据流中的所述SDAP头。请参阅图5，图5为示例的一种数据传输方法的交互示意图。图5包括了UE、基站和UPF之间的信令和数据交互。如图5所示，该数据传输方法包括如下步骤：501.下行IP数据流(以下简称“IP流”)到达核心网的UPF，UPF把IP数据流映射成QoS数据流(以下简称“QoS流”)。502.UPF把QoS流通过接入网与核心网间的接口发送给gNB(通过流传输)，基站接收QoS流。503.gNB对QoS流进行处理，即添加SDAP头(当然还包括进行其它协议层的处理，可参考现有技术，这里不作赘述)，将经过流传输的QoS流映射到承载。504.gNB将QoS流通过承载传输给UE，UE接收QoS流。505.UE将接收到的QoS数据流进行去头处理；至此，即完成了下行传输。506.UE也可以进行上行QoS数据流传输。507.UE将QoS数据流进行处理，即添加SDAP头，将QoS流映射到承载。508.UE将QoS流通过承载传输给gNB，gNB接收QoS流。509.gNB接收到经过处理的QoS流后，需要通过流传输至核心网，则需要对QoS流去头。510.gNB将去头后的QoS流通过流传输至UPF，UPF接收QoS流。图5中的基站可以是gNB。
对于SDAP头的定义，下面通过一些具体的实现方式进行描述：
在一个实现方式中，FII指示位位于第一字节中。如图6a示例的一个SDAP头的结构示意图，SDAP头所占用的字节(Octal，Oct)与SDAP SDU中的字节对齐，FII指示位位于Oct1中，FII指示位占用1个比特，该字节的其它比特作为保留位(Reserved，R)，以方便进行前向兼容。若FII指示SDAP头中包含流标识，则可以在第二字节中包含该流标识。需要说明的是，如果流标识的长度较长，仍可以根据需要继续占据SDAP头的第三字节以及其后的字节。在图6a的示例中，流标识位于第二字节Oct2和第三字节Oct3。
在另一个实现方式中，流标识也可以位于FII指示位所占用的第一字节中。如图6b示例的另一个SDAP头的结构示意图，FID的部分内容位于Oct1中，FID的剩下的部分位于Oct2和Oct3中。这样可以节省SDAP头的开销。如果流标识的长度较长，可以根据需要继续占据SDAP头的第三字节以及其后的字节。在图6b的示例中，流标识位于所述SDAP头的第一字节至第三字节。
在UE与gNB的上行传输过程中，UE可以采用反射QoS(Reflective QoS)的方式传输。反射QoS是一种UE获取上行数据传输IP流到QoS流，以及QoS流到承载的映射方式的一种方法，基本思想是UE根据下行数据传输的IP流到QoS流、以及QoS流到承载的映射信息来推导出上行数据传输QoS流到承载的映射方式。
如果网络确定在上行采用反射QoS的方式，那么UPF会在数据流的包头包含反射QoS指示(Reflective QoS Indication，RQI)。当数据流到达UE之后，如果数据包的包头包含有RQI，则UE在传输上行数据流时，会按照和刚刚收到的下行数据流一样的QoS指示进 行数据传输。
具体地，在本实施例中，RQI又包括接入层数据流反射指示(Access Stratum Reflective QoS Indication，ARI)和非接入层数据流反射指示(Non-Access Stratum Reflective QoS Indication，NRI)。ARI用于指示在接入层的数据流传输中是否采用反射QoS的方式。NRI用于指示在非接入层的数据流传输中是否采用反射QoS的方式。
在又一个实现方式中，如图6c示例的又一个SDAP头的结构示意图，SDAP头包括FII、ARI和NRI，若FII指示包含流标识，则SDAP头还包含流标识，其中，FII、ARI和NRI的排列顺序不作限定。ARI和NRI分别占1个比特。例如，ARI取值为“1”表示在接入层的数据流传输中采用反射QoS的方式，ARI取值为“0”表示在接入层的数据流传输中不采用反射QoS的方式；反之亦可。又例如，NRI取值为“1”表示在非接入层的数据流传输中采用反射QoS的方式，NRI取值为“0”表示在非接入层的数据流传输中不采用反射QoS的方式；反之亦可。图6d为示例的又一个SDAP头的结构示意图，图6d与图6c的区别在于，Oct1中还包括FID的部分内容。上述描述的情形是上行和下行采用相同的SDAP头，然而，上行和下行也可以采用不同的SDAP头，即上行只需包含FII，而无需包含ARI和NRI，上行的SDAP头的结构如图6a和图6b所示。
在又一个实现方式中，SDAP头包括FII，且FII还用于指示SDAP头是否包含ARI和NRI，若FII指示包含流标识，则SDAP头还包含流标识。如图6a和图6b所示，FII通过隐含指示SDAP头是否包含ARI和NRI，即例如，若FII的取值为“1”，则隐含表示SDAP头包含ARI和NRI，若FII的取值为“0”，则隐含表示SDAP头不包含ARI和NRI；反之亦可，若FII的取值为“1”，则隐含表示SDAP头不包含ARI和NRI，若FII的取值为“0”，则隐含表示SDAP头包含ARI和NRI。这样可以节省SDAP头的开销，并便于进行前向兼容。
在又一个实现方式中，SDAP头包括FII，且FII还用于指示SDAP头是否包含ARI，若FII指示包含流标识，则SDAP头还包含流标识。如图6e示例的又一个SDAP头的结构示意图，FII还用于指示SDAP头是否包含ARI，且发送端设备为基站时，则基站发送第一信令，该第一信令包括NRI；图6f与图6e的区别在于，在Oct1中还包含FID的内容。这样可以节省SDAP头的开销，并便于进行前向兼容。
在又一个实现方式中，SDAP头包括FII，且FII还用于指示SDAP头是否包含NRI，若FII指示包含流标识，则SDAP头还包含流标识。如图6g示例的又一个SDAP头的结构示意图，FII还用于指示SDAP头是否包含NRI，且发送端设备为基站时，则基站发送第二信令，该第二信令包括ARI；图6h与图6g的区别在于，在Oct1中还包含FID的内容。
在又一个实现方式中，SDAP头包括FII，若FII指示包含流标识，则SDAP头还包含流标识。若发送端设备为基站，接收端设备为UE，则基站可以发送无线资源控制(Radio Resource Control，RRC)信令给UE，该RRC信令中包括ARI；以及基站转发来自核心网的NRI给UE，即基站仅作核心网网元与UE之间的透传。
在又一个实现方式中，SDAP头包括FII和数据信息/控制信息指示位(D/C)，若FII指示包含流标识，则SDAP头还包含流标识。其中，ARI、NRI可以被看做是控制信息。这样，对于携带有ARI/NRI指示信息的SDAP头可以表示为：[C,FII,ARI,NRI,R,R,R,R]； 未携带ARI/NRI指示信息的SDAP头可以表示为：[D,FII,R,R,R,R,R,R]。即如图6i示例的又一个SDAP头的结构示意图，ARI和NRI的指示位均可以复用。控制信息还可以是ARI和NRI之外的其他控制信息。图6j与图6i的区别在于，Oct1中还可包含流标识的内容。
在又一个实现方式中，SDAP头包括FII和下行/上行指示位(D/U)，若FII指示包含流标识，则SDAP头还包含流标识。这样，若是下行传输，则SDAP头可以表示为：[D,FII,ARI,NRI,R,R,R,R]；若是上行传输，则SDAP头可以表示为：[U,FII,R,R,R,R,R,R]。即ARI和NRI的指示位均可以复用。这样可以节省SDAP头的开销，并便于进行前向兼容。
在又一个实现方式中，如前面描述的实施例中，SDAP头可以位于SDAP SDU之前；为了减少对PDCP层头压缩(Robust Header Compression，RoHC)的影响，SDAP头也可以加在SDAP SDU的末尾，如图6k示例的又一个SDAP头的结构示意图，SDAP头放置在SDAP SDU的末尾，FII指示位从后端对齐。
上述详细阐述了本发明实施例的方法，下面提供了本发明实施例的装置。
请参阅图7，图7为本发明实施例提供的一种通信设备的模块示意图，该通信设备7000可包括：处理器71和发送器72；其中：
处理器71，用于将数据流进行处理，其中，所述处理包括：将所述数据流添加流标识指示，所述流标识指示用于指示是否包括流标识；
发送器72，用于发送所述经过处理的数据流。
在一个实现方式中，所述处理具体包括在服务数据适配协议层协议数据单元SDAP PDU的头部或末尾添加所述流标识指示。
在另一个实现方式中，所述处理具体包括在分组数据映射协议PDCP头中添加所述流标识指示。
在又一个实现方式中，所述通信设备包括基站；
所述流标识指示还用于指示所述数据流中是否包含接入层数据流反射指示；
所述发送器72，还用于发送第一信令，其中，所述第一信令包括非接入层数据流反射指示NRI；
或者所述流标识指示还用于指示所述数据流中是否包含非接入层数据流反射指示；
所述发送器72，还用于发送第二信令，其中，所述第二信令包括所述接入层数据流反射指示。
在另一个实现方式中，所述通信设备包括基站；
所述发送器72，还用于通过无线资源控制信令发送接入层数据流反射指示；以及
所述发送器72，还用于转发来自核心网的非接入层数据流反射指示。
在又一个实现方式中，该通信设备7000还包括：接收器(未示出)；
所述接收器，用于接收所述数据流；
所述处理器，还用于获取所述流标识指示。
在又一个实现方式中，所述处理器，还用于去掉所述数据流中的所述SDAP PDU中的SDAP头。
在又一个实现方式中，所述SDAP头还包括流标识，所述流标识位于所述SDAP头的 第一字节和/或第二字节。
在又一个实现方式中，所述流标识指示还用于指示所述数据流中是否包含接入层数据流反射指示和非接入层数据流反射指示。
在又一个实现方式中，所述数据流中还包括数据信息/控制信息的指示。
具体可参见方法实施例中的描述，在此不再赘述。
根据本发明实施例提供一种通信设备，通过在数据流中添加流标识指示，流标识指示用于指示是否包含流标识，根据该流标识指示进行数据流的传输，从而完成了数据流的处理。
图8为本发明实施例提供的另一种通信设备的模块示意图，该通信设备8000包括接收器81和处理器82；其中：
接收器，用于接收数据流，所述数据流包括流标识指示，所述流标识指示用于指示是否包括流标识；
处理器，用于获取所述流标识指示。
在一个实现方式中，所述流标识指示位于服务数据适配协议层协议数据单元SDAP PDU的头部或末尾；或所述流标识指示位于分组数据映射协议PDCP头中。
在另一个实现方式中，所述处理器，还用于去掉所述SDAP PDU中的SDAP头。
在又一个实现方式中，所述SDAP头还包括流标识，所述流标识位于所述SDAP头的第一字节和/或第二字节。
在另一个实现方式中，所述流标识指示还用于指示所述数据流中是否包含接入层数据流反射指示和非接入层数据流反射指示。
在又一个实现方式中，所述数据流中还包括数据信息/控制信息的指示。
具体可参见方法实施例中的描述，在此不再赘述。
根据本发明实施例提供一种通信设备，通过在数据流中添加流标识指示，流标识指示用于指示是否包含流标识，根据该流标识指示进行数据流的传输，从而完成了数据流的处理。
本发明实施例还提供一种通信设备，该通信设备可以采用图9所示的硬件架构，例如，该通信设备可以是基站，也可以是终端设备。该通信设备可以包括接收器、发送器、存储器和处理器，所述接收器、发送器、存储器和处理器通过总线相互连接。
存储器包括但不限于是随机存储记忆体(Random Access Memory，RAM)、只读存储器(Read-Only Memory，ROM)、可擦除可编程只读存储器(Erasable Programmable Read Only Memory，EPROM)、或便携式只读存储器(Compact Disc Read-Only Memory，CD-ROM)，该存储器用于相关指令及数据。
接收器用于接收数据和/或信号，以及发送器用于发送数据和/或信号。发送器和接收器可以是独立的器件，也可以是一个整体的器件，例如收发器。
处理器可以包括是一个或多个处理器，例如包括一个或多个中央处理器(Central Processing Unit，CPU)，在处理器是一个CPU的情况下，该CPU可以是单核CPU，也可以是多核CPU。
存储器用于存储通信设备的程序代码和数据，可以为单独的器件或集成在处理器中。
上述各个器件可以集成在芯片中实现，例如集成在基带芯片中实现。
具体地，所述处理器执行以下操作：
将数据流进行处理，其中，所述处理包括：将所述数据流添加流标识指示，所述流标识指示用于指示是否包括流标识；
通过所述发送器发送所述经过处理的数据流。
在一个实现方式中，所述处理具体包括在服务数据适配协议层协议数据单元SDAP PDU的头部或末尾添加所述流标识指示。
在另一个实现方式中，所述处理具体包括在分组数据映射协议PDCP头中添加所述流标识指示。
在又一个实现方式中，所述通信设备包括基站；
所述流标识指示还用于指示所述数据流中是否包含接入层数据流反射指示；
通过所述发送器发送第一信令，其中，所述第一信令包括非接入层数据流反射指示；
或者所述流标识指示还用于指示所述数据流中是否包含非接入层数据流反射指示；
通过所述发送器发送第二信令，其中，所述第二信令包括所述接入层数据流反射指示。
在另一个实现方式中，所述通信设备包括基站；
通过所述发送器在无线资源控制信令中发送接入层数据流反射指示；以及
通过所述发送器转发来自核心网的非接入层数据流反射指示。
在又一个实现方式中，该处理器还用于执行以下操作：
通过所述接收器接收所述数据流；
获取所述流标识指示。
在又一个实现方式中，所述处理器执行所述通过所述接收器接收所述数据流之后，还执行以下操作：去掉所述数据流中的所述SDAP头。
在又一个实现方式中，所述SDAP头还包括流标识，所述流标识位于所述SDAP头的第一字节和/或第二字节。
在又一个实现方式中，所述流标识指示还用于指示所述数据流中是否包含接入层数据流反射指示和非接入层数据流反射指示。
在又一个实现方式中，所述数据流中还包括数据信息/控制信息的指示。
具体可参见方法实施例中的描述，在此不再赘述。
可以理解的是，图9仅仅示出了通信设备的简化设计。在实际应用中，通信设备还可以分别包含必要的其他元件，包含但不限于任意数量的收发器、处理器、控制器、存储器等，而所有可以实现本发明实施例的通信设备都在本发明的保护范围之内。
根据本发明实施例提供一种通信设备，通过在数据流中添加流标识指示，流标识指示用于指示是否包含流标识，根据该流标识指示进行数据流的传输，从而完成了数据流的处理。
本发明实施例还提供一种通信设备，该通信设备可以是上述通信系统中的通信设备，例如，可以是基站，也可以是终端设备。该通信设备可以采用图9所示的硬件架构。该通信设备可以包括接收器、发送器、存储器和处理器，所述接收器、发送器、存储器和处理器通过总线相互连接。
存储器包括但不限于是RAM、ROM、EPROM、CD-ROM，该存储器用于相关指令及数据。
接收器用于接收数据和/或信号，以及发送器用于发送数据和/或信号。发送器和接收器可以是独立的器件，也可以是一个整体的器件，例如收发器。
处理器可以包括是一个或多个处理器，例如包括一个或多个CPU，在处理器是一个CPU的情况下，该CPU可以是单核CPU，也可以是多核CPU。
存储器用于存储通信设备的程序代码和数据，可以为单独的器件或集成在处理器中。
上述各个器件可以集成在芯片中实现，例如集成在基带芯片中实现。
具体地，所述处理器执行以下操作：
通过所述接收器接收数据流，所述数据流包括流标识指示，所述流标识指示用于指示是否包括流标识；
获取所述流标识指示。
在一个实现方式中，所述流标识指示位于服务数据适配协议层协议数据单元SDAP PDU的头部或末尾；或所述流标识指示位于分组数据映射协议PDCP头中。
在另一个实现方式中，所述处理器还用于执行以下操作：去掉所述SDAP PDU中的SDAP头。
在又一个实现方式中，所述SDAP头还包括流标识，所述流标识位于所述SDAP头的第一字节和/或第二字节。
在又一个实现方式中，所述流标识指示还用于指示所述数据流中是否包含接入层数据流反射指示和非接入层数据流反射指示。
在又一个实现方式中，所述数据流中还包括数据信息/控制信息的指示。
具体可参见方法实施例中的描述，在此不再赘述。
可以理解的是，图9仅仅示出了通信设备的简化设计。在实际应用中，通信设备还可以分别包含必要的其他元件，包含但不限于任意数量的收发器、处理器、控制器、存储器等，而所有可以实现本发明的通信设备都在本发明的保护范围之内。
根据本发明实施例提供一种通信设备，通过在数据流中添加流标识指示，流标识指示用于指示是否包含流标识，根据该流标识指示进行数据流的传输，从而完成了数据流的处理。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组 件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本发明实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者通过所述计算机可读存储介质进行传输。所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘(Solid State Disk，SSD))等。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程，该流程可以由计算机程序来指令相关的硬件完成，该程序可存储于计算机可读取存储介质中，该程序在执行时，可包括如上述各方法实施例的流程。而前述的存储介质包括：ROM或随机存储记忆体RAM、磁碟或者光盘等各种可存储程序代码的介质。

Claims (26)

  1. 一种数据传输方法，其特征在于，包括：
    发送端设备将数据流进行处理，其中，所述处理包括：将所述数据流添加流标识指示，所述流标识指示用于指示是否包括流标识；
    所述发送端设备发送所述经过处理的数据流。
  2. 如权利要求1所述的方法，其特征在于，所述处理具体包括在服务数据适配协议层协议数据单元SDAP PDU的头部或末尾添加所述流标识指示。
  3. 如权利要求1所述的方法，其特征在于，所述处理具体包括在分组数据映射协议PDCP头中添加所述流标识指示。
  4. 如权利要求1至3任一项所述的方法，其特征在于，所述发送端设备包括基站；
    所述流标识指示还用于指示所述数据流中是否包含接入层数据流反射指示；
    所述方法还包括：所述基站发送第一信令，其中，所述第一信令包括非接入层数据流反射指示；
    或者所述流标识指示还用于指示所述数据流中是否包含非接入层数据流反射指示；
    所述方法还包括：所述基站发送第二信令，其中，所述第二信令包括接入层数据流反射指示。
  5. 如权利要求1至3任一项所述的方法，其特征在于，所述发送端设备包括基站；
    所述方法还包括：
    所述基站通过无线资源控制信令发送接入层数据流反射指示；以及
    所述基站转发来自核心网的非接入层数据流反射指示。
  6. 如权利要求2至5任一项所述的方法，其特征在于，还包括：
    所述发送端设备接收所述数据流；
    所述发送端设备获取所述流标识指示。
  7. 如权利要求6所述的方法，其特征在于，所述发送端设备接收所述数据流之后，所述方法还包括：
    所述发送端设备去掉所述SDAP PDU中的SDAP头。
  8. 一种数据传输方法，其特征在于，包括：
    接收端设备接收数据流，所述数据流包括流标识指示，所述流标识指示用于指示是否包括流标识；
    所述接收端设备获取所述流标识指示。
  9. 如权利要求8所述的方法，其特征在于，所述流标识指示位于服务数据适配协议层协议数据单元SDAP PDU的头部或末尾；或所述流标识指示位于分组数据映射协议PDCP头中。
  10. 如权利要求9所述的方法，其特征在于，所述接收端设备接收数据流之后，所述方法还包括：
    所述接收端设备去掉所述SDAP PDU中的SDAP头。
  11. 如权利要求2或9所述的方法，其特征在于，所述SDAP头还包括流标识，所述流标识位于所述SDAP头的第一字节和/或第二字节。
  12. 如权利要求1或8所述的方法，其特征在于，所述流标识指示还用于指示所述数据流中是否包含接入层数据流反射指示和非接入层数据流反射指示。
  13. 如权利要求1或8所述的方法，其特征在于，所述数据流中还包括数据信息/控制信息的指示。
  14. 一种通信设备，其特征在于，包括：
    处理器，用于将数据流进行处理，其中，所述处理包括：将所述数据流添加流标识指示，所述流标识指示用于指示是否包括流标识；
    发送器，用于发送所述经过处理的数据流。
  15. 如权利要求14所述的通信设备，其特征在于，所述处理具体包括在服务数据适配协议层协议数据单元SDAP PDU的头部或末尾添加所述流标识指示。
  16. 如权利要求14所述的通信设备，其特征在于，所述处理具体包括在分组数据映射协议PDCP头中添加所述流标识指示。
  17. 如权利要求14至16任一项所述的通信设备，其特征在于，所述通信设备包括基站；
    所述流标识指示还用于指示所述数据流中是否包含接入层数据流反射指示；
    所述发送器，还用于发送第一信令，其中，所述第一信令包括非接入层数据流反射指示；
    或者所述流标识指示还用于指示所述数据流中是否包含非接入层数据流反射指示；
    所述发送器，还用于发送第二信令，其中，所述第二信令包括所述接入层数据流反射指示。
  18. 如权利要求14至16任一项所述的通信设备，其特征在于，所述通信设备包括基站；
    所述发送器，还用于通过无线资源控制信令发送接入层数据流反射指示；以及
    所述发送器，还用于转发来自核心网的非接入层数据流反射指示。
  19. 如权利要求15至18任一项所述的通信设备，其特征在于，还包括：
    接收器，用于接收所述数据流；
    所述处理器，还用于获取所述流标识指示。
  20. 如权利要求19所述的通信设备，其特征在于，所述处理器，还用于去掉所述SDAP PDU中的SDAP头。
  21. 一种通信设备，其特征在于，包括：
    接收器，用于接收数据流，所述数据流包括流标识指示，所述流标识指示用于指示是否包括流标识；
    处理器，用于获取所述流标识指示。
  22. 如权利要求21所述的通信设备，其特征在于，所述流标识指示位于服务数据适配协议层协议数据单元SDAP PDU的头部或末尾；或所述流标识指示位于分组数据映射协议PDCP头中。
  23. 如权利要求22所述的方法，其特征在于，所述处理器，还用于去掉所述SDAP PDU中的SDAP头。
  24. 如权利要求15或22所述的通信设备，其特征在于，所述SDAP头还包括流标识，所述流标识位于所述SDAP头的第一字节和/或第二字节。
  25. 如权利要求14或21所述的通信设备，其特征在于，所述流标识指示还用于指示所述数据流中是否包含接入层数据流反射指示和非接入层数据流反射指示。
  26. 如权利要求14或21所述的通信设备，其特征在于，所述数据流中还包括数据信息/控制信息的指示。
PCT/CN2018/085514 2017-05-05 2018-05-03 数据传输方法及通信设备 WO2018202102A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP18794474.9A EP3611865B1 (en) 2017-05-05 2018-05-03 Data transmission method and communication device
US16/670,066 US11252095B2 (en) 2017-05-05 2019-10-31 Data transmission method and communications device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710313752.7 2017-05-05
CN201710313752.7A CN108809584B (zh) 2017-05-05 2017-05-05 数据传输方法及通信设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/670,066 Continuation US11252095B2 (en) 2017-05-05 2019-10-31 Data transmission method and communications device

Publications (1)

Publication Number Publication Date
WO2018202102A1 true WO2018202102A1 (zh) 2018-11-08

Family

ID=64016384

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/085514 WO2018202102A1 (zh) 2017-05-05 2018-05-03 数据传输方法及通信设备

Country Status (4)

Country Link
US (1) US11252095B2 (zh)
EP (1) EP3611865B1 (zh)
CN (1) CN108809584B (zh)
WO (1) WO2018202102A1 (zh)

Families Citing this family (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117354862A (zh) 2017-06-05 2024-01-05 三星电子株式会社 在下一代移动通信系统中配置pdcp设备和sdap设备的方法和装置
KR102359746B1 (ko) * 2017-06-05 2022-02-10 삼성전자 주식회사 차세대 이동통신 시스템에서 인액티브 모드 단말이 데이터를 전송하는 방법 및 장치
GB201715920D0 (en) * 2017-09-29 2017-11-15 Nec Corp Communication system
CN110351221B (zh) 2018-04-02 2020-07-17 维沃移动通信有限公司 配置数据流的方法和装置
KR20200076558A (ko) * 2018-12-19 2020-06-29 삼성전자주식회사 차세대 이동 통신 시스템에서 pdcp 계층 장치 기반 보안키 확인 방법 및 장치
WO2020130673A1 (ko) 2018-12-19 2020-06-25 삼성전자 주식회사 차세대 이동 통신 시스템에서 pdcp 계층 장치 기반 보안키 확인 방법 및 장치
CN111447650B (zh) * 2019-01-17 2021-11-19 中国移动通信有限公司研究院 一种数据前转的方法、设备及存储介质
CN110071935B (zh) * 2019-04-30 2021-03-30 重庆邮电大学 一种5g系统中终端组装sdap头的实现方法
CN113381843B (zh) * 2020-02-25 2023-09-08 中国移动通信有限公司研究院 一种数据传输方法、终端及基站
CN113395239A (zh) * 2020-03-12 2021-09-14 中国移动通信有限公司研究院 数据传输方法、装置、相关设备及存储介质
CN114125950A (zh) * 2020-08-11 2022-03-01 中国移动通信有限公司研究院 数据传输方法及设备
CN116648933A (zh) * 2020-12-24 2023-08-25 华为技术有限公司 无线通信网络中的感测系统、方法和装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102480468A (zh) * 2010-11-25 2012-05-30 中国移动通信集团公司 一种数据流传输方法、装置及系统
US20130021933A1 (en) * 2011-07-21 2013-01-24 Movik Networks RAN Analytics, Control And Tuning Via Multi-Protocol, Multi-Domain, And Multi-RAT Analysis
CN103581033A (zh) * 2012-07-27 2014-02-12 重庆重邮信科通信技术有限公司 数据流处理的方法及设备

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101867882B (zh) * 2009-04-14 2015-10-21 中兴通讯股份有限公司 消息发送及消息反馈预处理方法
TWI651950B (zh) * 2016-07-07 2019-02-21 財團法人工業技術研究院 無線接取網路之服務區分方法、無線網路系統及無線接取網路存取點
KR20180050192A (ko) * 2016-11-04 2018-05-14 삼성전자주식회사 차세대 이동 통신 시스템을 지원하기 위한 mac 서브 헤더의 구조와 이를 적용하는 방법 및 장치
US10993136B2 (en) * 2017-02-01 2021-04-27 Lg Electronics Inc. Method for performing reflective quality of service (QoS) in wireless communication system and a device therefor
CN110447260B (zh) * 2017-03-23 2023-05-16 三星电子株式会社 无线通信系统中的基站和终端以及由其执行的方法
WO2018196102A1 (zh) * 2017-04-27 2018-11-01 北京小米移动软件有限公司 信息传递方法、装置及计算机可读存储介质

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102480468A (zh) * 2010-11-25 2012-05-30 中国移动通信集团公司 一种数据流传输方法、装置及系统
US20130021933A1 (en) * 2011-07-21 2013-01-24 Movik Networks RAN Analytics, Control And Tuning Via Multi-Protocol, Multi-Domain, And Multi-RAT Analysis
CN103581033A (zh) * 2012-07-27 2014-02-12 重庆重邮信科通信技术有限公司 数据流处理的方法及设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3611865A4

Also Published As

Publication number Publication date
EP3611865A4 (en) 2020-04-01
EP3611865B1 (en) 2021-07-28
US20210006498A9 (en) 2021-01-07
CN108809584B (zh) 2021-05-18
EP3611865A1 (en) 2020-02-19
US20200067843A1 (en) 2020-02-27
CN108809584A (zh) 2018-11-13
US11252095B2 (en) 2022-02-15

Similar Documents

Publication Publication Date Title
WO2018202102A1 (zh) 数据传输方法及通信设备
US11405773B2 (en) Method and device for relay transmission
US10785824B2 (en) Information processing method and related apparatus
WO2017166138A1 (zh) 中继传输的方法和装置
TWI657708B (zh) 用於新型無線電系統的分段與級聯方法及使用者設備
WO2019149248A1 (zh) 通信的方法和装置
CN110505714B (zh) 多链接通信方法、设备和终端
US10764961B2 (en) Relay transmission method and device
KR20180125450A (ko) 중계 전송 방법과 장치, 및 중계 단말 장비
CN111448817B (zh) 一种提供ue能力以支持承载上的安全保护的方法和装置
CN108432338A (zh) 一种数据传输系统、方法和装置
JP2019514249A (ja) データユニットを送信する方法及び装置
CN110636580A (zh) 一种切换方法及装置
WO2015081553A1 (zh) 传输数据的方法、装置和系统
US11510129B2 (en) Relay transmission method and relay node
WO2021179453A1 (zh) 信号处理方法、接入网设备及多制式接入网设备
WO2020125753A1 (en) Uplink data compression in mobile communications
US11228667B2 (en) Base station, method, and device for data transmission
WO2019237315A1 (zh) 一种控制安全功能的方法及装置、网络设备、终端设备
WO2018145292A1 (zh) 通信方法、装置和系统
CN109155956A (zh) 一种数据传输方法、装置及系统
WO2022089210A1 (zh) 数据处理方法及设备
WO2023123515A1 (zh) 数据处理方法、终端设备和网络设备
KR20100082698A (ko) 다중화 ｍａｃ 헤더를 이용한 효율적인 데이터 전송방법 및장치
TW201815113A (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: 18794474

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2018794474

Country of ref document: EP

Effective date: 20191115