WO2018223965A1 - 数据传输方法、数据发送端、数据接收端、数据传输系统及计算机可读存储介质 - Google Patents

数据传输方法、数据发送端、数据接收端、数据传输系统及计算机可读存储介质 Download PDF

Info

Publication number
WO2018223965A1
WO2018223965A1 PCT/CN2018/089979 CN2018089979W WO2018223965A1 WO 2018223965 A1 WO2018223965 A1 WO 2018223965A1 CN 2018089979 W CN2018089979 W CN 2018089979W WO 2018223965 A1 WO2018223965 A1 WO 2018223965A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
entity
identifier
sdap
sdap entity
Prior art date
Application number
PCT/CN2018/089979
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 US16/620,378 priority Critical patent/US11323912B2/en
Priority to EP18813941.4A priority patent/EP3637844B1/en
Priority to EP21186025.9A priority patent/EP3913967B1/en
Priority to ES18813941T priority patent/ES2899395T3/es
Publication of WO2018223965A1 publication Critical patent/WO2018223965A1/zh
Priority to US17/687,238 priority patent/US11665581B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0273—Traffic management, e.g. flow control or congestion control adapting protocols for flow control or congestion control to wireless environment, e.g. adapting transmission control protocol [TCP]
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
    • H04W28/065—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information using assembly or disassembly of packets
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • 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
    • H04W28/0263—Traffic management, e.g. flow control or congestion control per individual bearer or channel involving mapping traffic to individual bearers or channels, e.g. traffic flow template [TFT]
    • 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/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
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels
    • 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
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/08—Upper layer protocols

Definitions

  • the present disclosure relates to the field of communications technologies, and in particular, to a data transmission method, related device, and system.
  • the 5G system introduces a network-side indication mechanism of Quality-of-Service (QoS), it is necessary to add QoS indication information of the IP data flow of the terminal in the process of transmitting uplink and downlink data (such as flow). ID), and the protocol layer is located above the Packet Data Convergence Protocol (PDCP) layer.
  • QoS Quality-of-Service
  • different data may correspond to different network slices, and one network slice may include multiple session units (for example, PDU sessions), and one session unit may include multiple data streams ( Flow). Therefore, how to implement the interaction between the high-level entity, the Service Data Adaptation Protocol (SDAP) entity and the PDCP entity becomes an urgent problem to be solved.
  • SDAP Service Data Adaptation Protocol
  • an embodiment of the present disclosure provides a data transmission method, which is applied to a data sending end, and includes:
  • the high-level entity sends the data packet to the corresponding SDAP entity according to at least one of a network slice identifier, a SDAP identifier, a data flow identifier, and a session identifier.
  • the SDAP entity adds a data flow identifier to the data packet, and sends the data packet to the PDCP entity corresponding to the DRB according to the correspondence between the SDAP entity and the Data Radio Bearer (DRB).
  • DRB Data Radio Bearer
  • the embodiment of the present disclosure further provides a data transmission method, which is applied to a data receiving end, and includes:
  • the PDCP entity receives the data packet from the data sending end, and sends the data packet to the corresponding SDAP entity according to the data flow identifier carried by the data packet;
  • the SDAP entity forwards the data packet to an application protocol layer or forwards the data packet to a corresponding network slice, data stream, and session unit.
  • an embodiment of the present disclosure further provides a data sending end, including:
  • a first sending module configured to send, by the upper layer entity, the data packet to the corresponding SDAP entity according to at least one of a network slice identifier, a SDAP identifier, a data flow identifier, and a session identifier;
  • a second sending module configured to send the data flow identifier to the SDAP entity, and send the data packet to the PDCP entity corresponding to the DRB according to the correspondence between the SDAP entity and the data bearer DRB.
  • an embodiment of the present disclosure further provides a data receiving end, including:
  • a receiving module configured to receive, by the PDCP entity, a data packet from the data sending end, and send the data packet to the corresponding SDAP entity according to the data flow identifier carried by the data packet;
  • a forwarding module configured to: forward, by the SDAP entity, the data packet to an application protocol layer, or forward the data packet to a corresponding network slice, a data stream, and a session unit.
  • an embodiment of the present disclosure further provides a data sending end, including: a processor, a memory, a network interface, and a user interface, where the processor, the memory, the network interface, and the user interface pass a bus
  • the system is coupled together, and the processor is configured to read a program in the memory, and perform the steps in the data transmission method on the data transmitting end side provided by the embodiment of the present disclosure.
  • an embodiment of the present disclosure further provides a data receiving end, including: a processor, a memory, a network interface, and a user interface, where the processor, the memory, the network interface, and the user interface pass through a bus
  • the system is coupled together, and the processor is configured to read a program in the memory, and perform the steps in the data transmission method on the data receiving end side provided by the embodiment of the present disclosure.
  • an embodiment of the present disclosure further provides a data transmission system, including a data sending end and a data receiving end provided by the embodiments of the present disclosure.
  • an embodiment of the present disclosure further provides a computer readable storage medium, where the data transfer program is stored on a computer readable storage medium, and the data transfer program is executed by a processor to implement the embodiment of the present disclosure.
  • the embodiment of the present disclosure further provides a computer readable storage medium, where the data transfer program is stored on the computer readable storage medium, and the data transfer program is executed by the processor to implement the embodiment of the present disclosure.
  • FIG. 1 is a structural diagram of a data transmission system to which an embodiment of the present disclosure is applied;
  • FIG. 2 is a flowchart of a data transmission method according to an embodiment of the present disclosure
  • FIG. 3 is a flowchart of another data processing method according to an embodiment of the present disclosure.
  • FIG. 4 is a schematic diagram of transmission of a data stream according to an embodiment of the present disclosure.
  • FIG. 5 is a schematic diagram of another data stream transmission according to an embodiment of the present disclosure.
  • FIG. 6 is a schematic diagram of another data stream transmission according to an embodiment of the present disclosure.
  • FIG. 7 is a schematic diagram of another data stream transmission according to an embodiment of the present disclosure.
  • FIG. 8 is a schematic diagram of another data stream transmission according to an embodiment of the present disclosure.
  • FIG. 9 is a flowchart of another data transmission method according to an embodiment of the present disclosure.
  • FIG. 10 is a flowchart of another data transmission method according to an embodiment of the present disclosure.
  • FIG. 11 is a flowchart of a data processing method according to an embodiment of the present disclosure.
  • FIG. 12 is a flowchart of another data processing method according to an embodiment of the present disclosure.
  • FIG. 13 is a flowchart of another data processing method according to an embodiment of the present disclosure.
  • FIG. 14 is a structural diagram of a data sending end according to an embodiment of the present disclosure.
  • FIG. 15 is a structural diagram of another data sending end according to an embodiment of the present disclosure.
  • 16 is a structural diagram of another data transmitting end according to an embodiment of the present disclosure.
  • 17 is a structural diagram of another data transmitting end according to an embodiment of the present disclosure.
  • FIG. 18 is a structural diagram of a data receiving end according to an embodiment of the present disclosure.
  • FIG. 19 is a structural diagram of another data receiving end according to an embodiment of the present disclosure.
  • FIG. 20 is a structural diagram of a data processing apparatus according to an embodiment of the present disclosure.
  • FIG. 21 is a structural diagram of another data processing apparatus according to an embodiment of the present disclosure.
  • FIG. 22 is a structural diagram of another data processing apparatus according to an embodiment of the present disclosure.
  • FIG. 23 is a structural diagram of another data processing apparatus according to an embodiment of the present disclosure.
  • FIG. 24 is a structural diagram of another data transmitting end according to an embodiment of the present disclosure.
  • 25 is a structural diagram of another data receiving end according to an embodiment of the present disclosure.
  • FIG. 26 is a structural diagram of another data processing apparatus according to an embodiment of the present disclosure.
  • FIG. 1 is a structural diagram of a data transmission system applicable to an embodiment of the present disclosure.
  • the data transmission end 11 and the data receiving end 12 are included.
  • the data transmitting end 11 may be a user terminal. It can also be called User Equipment (UE).
  • UE User Equipment
  • it can be a mobile phone, a Tablet Personal Computer, a Laptop Computer, a personal digital assistant (PDA), and a mobile Internet.
  • PDA personal digital assistant
  • a terminal device such as a mobile Internet device (MID) or a wearable device, or may be a network side device, for example, a Transmission Reception Point (TRP), or may be a base station, and the base station may be The macro station, such as an LTE eNB, a 5G NR NB, etc.; the data transmitting end 11 may also be an access point (AP).
  • MID mobile Internet device
  • TRP Transmission Reception Point
  • the macro station such as an LTE eNB, a 5G NR NB, etc.
  • the data transmitting end 11 may also be an access point (AP).
  • AP access point
  • the specific type of the data sending end 11 is not limited in the embodiment of the present disclosure, wherein the drawing is exemplified by the data sending end 11 as a user terminal.
  • the data receiving end 12 may be a UE, for example, a terminal side device such as a mobile phone, a tablet computer, a laptop computer, a PDA, a MID, or a wearable device, or may be a network side device, such as a TRP, or may be a base station.
  • the base station may be a macro station, such as an LTE eNB, a 5G NR NB, etc.; the data receiving end 12 may also be an AP. It should be noted that the specific type of the data receiving end 12 is not limited in the embodiment of the present disclosure. The figure is exemplified by the data receiving end 12 as a network side device.
  • FIG. 2 is a flowchart of a data transmission method according to an embodiment of the present disclosure. The method is applied to a data sending end, as shown in FIG. 2, and includes the following steps:
  • Step 201 The high-level entity sends the data packet to the corresponding SDAP entity according to at least one of a network slice identifier, a SDAP identifier, a data flow identifier, and a session identifier.
  • the network slice identifier may be used to identify a network slice to which the data packet belongs, and the network slice may include multiple session units (eg, PDU sessions), and one session unit may include multiple data flows.
  • the data flow identifier may be used to identify the data flow to which the data packet belongs, and the session identifier may be used to identify a session unit corresponding to the data flow to which the data packet belongs.
  • the corresponding SDAP identifier is determined according to the network slice identifier, the data flow identifier, or the session identifier of the data packet, and the data is sent to the corresponding SDAP entity.
  • Step 202 The SDAP entity adds a data flow identifier to the data packet, and sends the data packet to a PDCP entity corresponding to the DRB according to the correspondence between the SDAP entity and the DRB.
  • the corresponding relationship between the foregoing SDAP entity and the DRB may be preset. After adding the data flow identifier in the data packet, the identifier of the corresponding data stream may be added in the data packet, and the data flow identifier of the data packet may be according to the network. The default configuration is added.
  • the PDCP entity corresponding to the DRB may be pre-configured, for example, one DRB corresponds to one PDCP entity, or multiple DRBs correspond to the same PDCP entity.
  • the foregoing data packet may be a TCP/IP data packet.
  • the high-level entity sends the data packet to the corresponding SDAP entity according to at least one of a network slice identifier, a SDAP identifier, a data flow identifier, and a session identifier; the SDAP entity adds a data stream to the data packet. And sending, according to the correspondence between the SDAP entity and the DRB, the data packet to the PDCP entity corresponding to the DRB. Thereby, the interaction between the high-level entity, the SDAP entity and the PDCP entity is realized.
  • FIG. 3 is a flowchart of another data transmission method according to an embodiment of the present disclosure. The method is applied to a data sending end. As shown in FIG. 3, the method includes the following steps:
  • Step 301 Establish a SDAP entity according to a network configuration or a pre-agreed configuration information in advance.
  • the configuration information includes at least one of the following: a network slice identifier, a data bearer identifier, a data flow identifier, a session identifier, and association relationship indication information.
  • the association relationship indication information may indicate a correspondence between the foregoing SDAP entity and other entities, so that after receiving the configuration information, the step 301 may establish a corresponding SDAP entity.
  • Step 302 Instruct the corresponding relationship information of the SDAP entity to the high-layer entity by using the SDAP entity.
  • the correspondence information includes at least one of the following: a network slice identifier, a data bearer identifier, a data stream identifier, a session identifier, and a SDAP identifier.
  • the foregoing correspondence information may be used to indicate a correspondence between the SDAP entities, for example, a correspondence between the SDAP entity and other entities, and may also indicate a relationship between the network slice identifier, the data bearer identifier, the data flow identifier, and the session identifier.
  • the foregoing high-level entity may be located on an entity above the SDAP layer, for example, a non-access stratum (NAS) layer entity.
  • NAS non-access stratum
  • Step 303 The high-level entity sends the data packet to the corresponding SDAP entity according to at least one of a network slice identifier, a SDAP identifier, a data flow identifier, and a session identifier.
  • the corresponding SDAP identifier is determined according to the network slice identifier, the data flow identifier, or the session identifier of the data packet, and the data is sent to the corresponding SDAP entity.
  • Step 304 The SDAP entity adds a data flow identifier to the data packet, and sends the data packet to the PDCP entity corresponding to the DRB according to the correspondence between the SDAP entity and the DRB.
  • association relationship indication information includes any one of the following:
  • the correspondence between the data stream and the PDCP entity may be pre-configured, one PDCP entity may correspond to one or more data flows, and one PDCP entity may correspond to one data bearer, or one SDAP. Corresponding to a data bearer.
  • one SDAP entity may be corresponding to one PDU session.
  • multiple data streams included in one PDU session are sent to the PDCP entity corresponding to each data stream through one SDAP.
  • one SDAP entity may be corresponding to one PDCP entity.
  • a data flow corresponding to one PDCP entity is sent to a PDCP entity corresponding to each data stream through one SDAP.
  • one SDAP entity may be corresponding to one MAC entity.
  • the data flows of multiple PDU sessions corresponding to one MAC entity are sent to each data flow through the same SDAP entity.
  • the corresponding PDCP entity is sent to the Radio Link Control (RLC) entity through the PDCP and finally sent to the MAC entity.
  • RLC Radio Link Control
  • one SDAP entity may be corresponding to one terminal.
  • the data flows of multiple PDU sessions corresponding to multiple MAC entities of one terminal are sent to the same SDAP entity.
  • the PDCP entity corresponding to each data stream is sent to the RLC entity through the PDCP and finally sent to the MAC entity of the terminal.
  • the configuration information when the association relationship indication information indicates that one SDAP entity corresponds to one MAC entity, the configuration information further includes a MAC identifier.
  • the association relationship indication information indicates that one SDAP entity corresponds to one session unit, that one SDAP entity corresponds to one PDCP entity, that one SDAP entity corresponds to one MAC entity, or one SDAP entity is indicated.
  • the correspondence relationship information further includes the association relationship indication information.
  • the association relationship indication information indicates that one SDAP entity corresponds to one session unit, one SDAP entity corresponds to one PDCP entity, one SDAP entity corresponds to one MAC entity, or one SDAP is indicated.
  • the association relationship indication information is sent to the high-layer entity by using the corresponding relationship information, so that the high-level entity can determine whether to provide the auxiliary information of the data packet by using the association indication information, so that the SDAP can accurately transmit the data packet. Improve data transfer performance.
  • the method further includes:
  • the high-level entity provides auxiliary information of the data packet, and the auxiliary information includes a data flow identifier.
  • the data stream identifier is provided, so that the SDAP can be accurately added with the corresponding data stream identifier to improve data transmission performance.
  • the method further includes:
  • the high-level entity provides auxiliary information of the data packet, and the auxiliary information includes at least one of the following: a data flow identifier, a network slice identifier, and a session identifier.
  • the data flow identifier, the network slice identifier, and the session identifier are provided, so that the SDAP can be accurately added.
  • the SDAP entity is established in advance according to the network configuration or the pre-agreed configuration information, where the configuration information includes at least one of the following: a network slice identifier, a data bearer identifier, a data flow identifier, a session identifier, and an association relationship indication information;
  • the SDAP entity indicates the correspondence relationship information of the SDAP entity to the upper layer entity, where the correspondence relationship information includes at least one of the following: a network slice identifier, a data bearer identifier, a data flow identifier, a session identifier, and a SDAP identifier high-level entity; Corresponding relationship between the slice identifier, the SDAP identifier, the data flow identifier, and the session identifier, and sending the data packet to the corresponding SDAP entity; the SDAP entity adds a data flow identifier to the data packet, and according to the SDAP entity and the DRB Corresponding relationship, the data packet is sent to a PDCP entity corresponding to the DRB.
  • FIG. 9 is a flowchart of another data transmission method according to an embodiment of the present disclosure. The method is applied to a data receiving end. As shown in FIG. 9, the method includes:
  • Step 901 The PDCP entity receives the data packet from the data sending end, and sends the data packet to the corresponding SDAP entity according to the data flow identifier carried by the data packet.
  • the corresponding SDAP entity may be a SDAP entity corresponding to the data flow identifier.
  • Step 902 The SDAP entity forwards the data packet to an application protocol layer, or forwards the data packet to a corresponding network slice, data stream, and session unit.
  • the SDAP entity forwards the data packet to the application protocol layer, and when the data receiving end is the network side device, the SDAP entity forwards the data packet to the corresponding Network slices, data streams, and session units.
  • the PDCP entity receives the data packet from the data sending end, and sends the data packet to the corresponding SDAP entity according to the data flow identifier carried by the data packet; the SDAP entity forwards the data packet to the application protocol.
  • the layer or, forwards the data packet to a corresponding network slice, data stream, and session unit. Thereby the interaction between the SDAP entity and the PDCP entity is achieved.
  • FIG. 10 is a flowchart of another data transmission method according to an embodiment of the present disclosure. The method is applied to a data receiving end, as shown in FIG.
  • Step 1001 Establish a SDAP entity according to the configuration information of the network configuration or the protocol.
  • the configuration information includes at least one of the following: a network slice identifier, a data bearer identifier, a data flow identifier, a session identifier, and association relationship indication information.
  • Step 1002 The corresponding relationship information of the SDAP entity is indicated by the SDAP entity to a high-level entity, where the corresponding relationship information includes at least one of the following: a network slice identifier, a data bearer identifier, a data flow identifier, a session identifier, and a SDAP identifier.
  • Step 1003 The PDCP entity receives the data packet from the data sending end, and sends the data packet to the corresponding SDAP entity according to the data flow identifier carried by the data packet.
  • the corresponding SDAP entity may be a SDAP entity corresponding to the data flow identifier.
  • Step 1004 The SDAP entity forwards the data packet to an application protocol layer, or forwards the data packet to a corresponding network slice, data stream, and session unit.
  • the SDAP entity forwards the data packet to a corresponding network slice, a data stream, and a session unit, including:
  • the SDAP entity forwards the data packet to a corresponding network slice, data stream, and session unit according to at least one of a network slice identifier, a SDAP identifier, a data flow identifier, and a session identifier.
  • the data packet can be accurately sent to the corresponding network slice, data stream, and session unit according to the foregoing correspondence to improve data transmission performance.
  • association relationship indication information includes any one of the following:
  • association relationship indication information For the above-mentioned association relationship indication information, reference may be made to the corresponding description of the embodiment shown in FIG. 3, which is not described herein, and the same beneficial effects can be achieved.
  • the configuration information when the association relationship indication information indicates that one SDAP entity corresponds to one MAC entity, the configuration information further includes a MAC identifier.
  • the association relationship indication information indicates that one SDAP entity corresponds to one session unit, that one SDAP entity corresponds to one PDCP entity, that one SDAP entity corresponds to one MAC entity, or one SDAP entity is indicated.
  • the correspondence relationship information further includes the association relationship indication information.
  • the SDAP entity is established in advance according to the network configuration or the pre-agreed configuration information, where the configuration information includes at least one of the following: a network slice identifier, a data bearer identifier, a data flow identifier, a session identifier, and an association relationship indication information;
  • the SDAP entity indicates the corresponding relationship information of the SDAP entity to the high-level entity, where the corresponding relationship information includes at least one of the following: a network slice identifier, a data bearer identifier, a data flow identifier, a session identifier, and a SDAP identifier high-level entity;
  • Receiving a data packet from the data sending end sending the data packet to a corresponding SDAP entity according to the data flow identifier carried by the data packet; the SDAP entity forwarding the data packet to an application protocol layer, or The packet is forwarded to the corresponding network slice, data stream, and session unit.
  • the SDAP entity can be flexibly established to improve the overall performance of the data
  • FIG. 11 is a flowchart of a data processing method according to an embodiment of the present disclosure. As shown in FIG. 11, the method includes the following steps:
  • Step 1101 Establish a SDAP entity according to the configuration information of the network configuration or the protocol.
  • the configuration information includes at least one of the following: a network slice identifier, a data bearer identifier, a data flow identifier, a session identifier, and association relationship indication information.
  • the network slice identifier is used to identify a network slice, and the network slice may include multiple session units (eg, PDU sessions), and one session unit may include multiple data flows.
  • the data bearer identifier may be used to identify the DRB, and the data bearer may correspond to the PDCP.
  • the association relationship indication information is used to indicate the correspondence between the foregoing SDAP entity and other entities, so that after receiving the configuration information, step 201 may establish a corresponding SDAP entity.
  • Step 1102 Instruct the mapping relationship information of the SDAP entity to the upper layer entity by using the SDAP entity.
  • the foregoing correspondence information may be used to indicate a correspondence between the SDAP entities, for example, a correspondence between the SDAP entity and other entities, and may also indicate a relationship between the network slice identifier, the data bearer identifier, the data flow identifier, and the session identifier.
  • the above high-level entity may be located on an entity above the SDAP layer, for example, a NAS layer entity.
  • Step 1103 Perform data transmission between the high-level entity, the SDAP entity, and the PDCP entity based on the correspondence information.
  • the data transmission between the high-level entity, the SDAP entity, and the packet data convergence protocol (PDCP entity) based on the correspondence information may be the correspondence between entities or entities and data indicated by the correspondence information.
  • the high-level entity SDAP entity and the packet data convergence protocol PDCP entity perform data transmission. And the data transmission can be sending data or receiving data.
  • the method can be applied to the data receiving end or the data transmitting end in the system shown in FIG. 1 .
  • the SDAP entity is established in advance according to the configuration information of the network configuration or the protocol, and the configuration information includes at least one of the following: a network slice identifier, a data bearer identifier, a data flow identifier, a session identifier, and an association relationship indication information;
  • the SDAP entity indicates the correspondence relationship information of the SDAP entity to the upper layer entity; and performs data transmission between the high layer entity, the SDAP entity, and the packet data convergence protocol PDCP entity based on the correspondence relationship information.
  • the interaction between the high-level entity, the SDAP entity and the PDCP entity is realized.
  • FIG. 12 is a flowchart of another data processing method according to an embodiment of the present disclosure. As shown in FIG. 12, the method includes the following steps:
  • Step 1201 Establish a SDAP entity according to the configuration information of the network configuration or the protocol.
  • the configuration information includes at least one of the following: a network slice identifier, a data bearer identifier, a data flow identifier, a session identifier, and association relationship indication information.
  • association relationship indication information includes any one of the following:
  • the correspondence between the data stream and the PDCP entity may be pre-configured, one PDCP entity may correspond to one or more data flows, and one PDCP entity may correspond to one data bearer, or one SDAP. Corresponding to a data bearer.
  • one SDAP entity may be corresponding to one PDU session.
  • multiple data streams included in one PDU session are sent to the PDCP entity corresponding to each data stream through one SDAP.
  • one SDAP entity may be corresponding to one PDCP entity.
  • a data flow corresponding to one PDCP entity is sent to a PDCP entity corresponding to each data stream through one SDAP.
  • one SDAP entity may be corresponding to one MAC entity.
  • the data flows of multiple PDU sessions corresponding to one MAC entity are sent to each data flow through the same SDAP entity.
  • the corresponding PDCP entity is sent to the RLC entity through the PDCP and finally sent to the MAC entity.
  • one SDAP entity may be corresponding to one terminal.
  • the data flows of multiple PDU sessions corresponding to multiple MAC entities of one terminal are sent to the same SDAP entity.
  • the PDCP entity corresponding to each data stream is sent to the RLC entity through the PDCP and finally sent to the MAC entity of the terminal.
  • Step 1202 Instruct the mapping relationship information of the SDAP entity to the high-layer entity by using the SDAP entity.
  • the configuration information when the association relationship indication information indicates that one SDAP entity corresponds to one MAC entity, the configuration information further includes a MAC identifier.
  • the foregoing correspondence information includes at least one of the following: a network slice identifier, a data bearer identifier, a data stream identifier, a session identifier, and a SDAP identifier.
  • the network slice identifier, the data bearer identifier, the data stream identifier, the session identifier, and the SDAP identifier may explicitly indicate a correspondence relationship between the network slice identifier, the data bearer identifier, the data flow identifier, the session identifier, and the SDAP identifier, thereby When transmitting, it can be accurately transmitted through the corresponding entity to improve data transmission performance.
  • Step 1203 The high-layer entity determines, according to at least one of a network slice identifier, a SDAP identifier, a data flow identifier, and a session identifier, a target SDAP entity corresponding to the target data packet to be sent.
  • the step 1203 may be performed when the foregoing method can be applied to the data sending end, for example, a terminal or a network side device.
  • the target data packet may be a data packet in a certain data flow, so that the target SDAP entity corresponding to the target data may be determined by using the foregoing correspondence.
  • the corresponding data packet may be determined by the data stream of the target data packet; for example, one SDAP entity corresponds to one session unit, and may be determined by the session corresponding to the target data packet.
  • Corresponding SDAP entity when one SDAP entity corresponds to one PDCP entity, the corresponding SDAP entity may be determined by the PDCP entity corresponding to the data flow corresponding to the target data packet; for example, indicating that one SDAP entity corresponds to one MAC The entity may determine the corresponding SDAP entity by using the data stream corresponding to the target data packet to the MAC corresponding to the PDU session; for example, indicating that one SDAP entity corresponds to one terminal, and the terminal corresponding to the target data packet can determine the corresponding SDAP. entity.
  • Step 1204 The high-level entity sends the target data packet to the target SDAP entity.
  • step 304 can send the target data packet to the SDAP entity.
  • the sent data packet may provide one or more auxiliary information as follows:
  • Data flow identifier session identifier, SDAP identifier, DRB identifier, PDCP identifier, and MAC identifier.
  • Step 1205 The target SDAP entity forwards the target data packet to the target PDCP entity corresponding to the data bearer according to the corresponding relationship between the SDAP entity and the DRB, after adding the data flow identifier to the target data packet.
  • the corresponding relationship between the foregoing SDAP entity and the DRB may be preset, and the identifier of the corresponding data stream may be added to the target data packet after the data flow identifier is added to the target data packet. And the data flow identifier of the target data packet may be added according to the network configuration.
  • the target data packet may be a TCP/IP data packet.
  • the high-level entity provides auxiliary information of the sent target data packet.
  • the auxiliary information includes a data flow identifier.
  • the data flow identifier can be sent to the SDAP entity, so that the SDAP can be accurately added with the corresponding data flow identifier to improve data transmission performance.
  • the high-level entity provides auxiliary information of the sent target data packet, where
  • the auxiliary information includes at least one of the following: a data flow identifier, a network slice identifier, and a session identifier.
  • the data stream identifier, the network slice identifier, and the session identifier may be sent to the SDAP entity, so that the SDAP may be accurately added with the corresponding data stream identifier, and the network segment identifier and the session identifier may be accurately transmitted to improve the Data transfer performance.
  • data can be accurately transmitted between the upper layer entity, the SDAP entity, and the PDCP through the foregoing steps, thereby improving the transmission performance of the data transmitting end.
  • FIG. 13 is a flowchart of another data processing method according to an embodiment of the present disclosure. As shown in FIG. 13, the method includes the following steps:
  • Step 1301 Establish a SDAP entity according to the configuration information of the network configuration or the protocol.
  • the configuration information includes at least one of the following: a network slice identifier, a data bearer identifier, a data flow identifier, a session identifier, and association relationship indication information.
  • association relationship indication information includes any one of the following:
  • Step 1302 Instruct the mapping relationship information of the SDAP entity to the upper layer entity by using the SDAP entity.
  • the configuration information when the association relationship indication information indicates that one SDAP entity corresponds to one MAC entity, the configuration information further includes a MAC identifier.
  • the foregoing correspondence information includes at least one of the following: a network slice identifier, a data bearer identifier, a data stream identifier, a session identifier, and a SDAP identifier.
  • the network slice identifier, the data bearer identifier, the data stream identifier, the session identifier, and the SDAP identifier may explicitly indicate a correspondence relationship between the network slice identifier, the data bearer identifier, the data flow identifier, the session identifier, and the SDAP identifier, thereby When transmitting, it can be accurately transmitted through the corresponding entity to improve data transmission performance.
  • Step 1303 The PDCP entity receives the target data packet sent by the sending end.
  • the step 1303 may be performed when the foregoing method is applied to the receiving end, for example, a terminal or a network side device.
  • the target data packet may be the target data packet in the embodiment shown in FIG. 12, and details are not described herein, and the target data packet carries the data flow identifier.
  • Step 1304 The PDCP entity forwards the target data packet to the corresponding target SDAP entity according to the data flow identifier carried by the target data packet.
  • the corresponding target SDAP may be determined by using the association relationship indication information.
  • the method further includes :
  • the target SDAP entity forwards the received target data packet to a corresponding network slice, data stream, and session unit.
  • the target SDAP entity forwards the received data packet to an application protocol layer.
  • the terminal can forward the data packet to the application protocol layer through the SDAP entity.
  • data can be accurately received between the SDAP entity and the PDCP through the foregoing steps, thereby improving the receiving performance of the data receiving end.
  • FIG. 14 is a structural diagram of a data sending end according to an embodiment of the present disclosure. As shown in FIG. 14, the data sending end 1400 includes:
  • the first sending module 1401 is configured to send, by the upper layer entity, the data packet to the corresponding SDAP entity according to at least one of a network slice identifier, a SDAP identifier, a data flow identifier, and a session identifier.
  • the second sending module 1402 is configured to allow the SDAP entity to add a data flow identifier to the data packet, and send the data packet to a PDCP entity corresponding to the DRB according to a correspondence between the SDAP entity and the data bearer DRB.
  • the data sending end further includes:
  • the establishing module 1403 is configured to establish a SDAP entity according to the network configuration or the pre-agreed configuration information, where the configuration information includes at least one of the following: a network slice identifier, a data bearer identifier, a data flow identifier, a session identifier, and an association relationship indication information;
  • the indication module 1404 is configured to indicate, by using the SDAP entity, the correspondence relationship information of the SDAP entity to the upper layer entity, where the correspondence relationship information includes at least one of the following: a network slice identifier, a data bearer identifier, a data stream identifier, a session identifier, and SDAP logo.
  • association relationship indication information includes any one of the following:
  • the configuration information when the association relationship indication information indicates that one SDAP entity corresponds to one MAC entity, the configuration information further includes a MAC identifier.
  • the association relationship indication information indicates that one SDAP entity corresponds to one session unit, that one SDAP entity corresponds to one PDCP entity, that one SDAP entity corresponds to one MAC entity, or one SDAP entity is indicated.
  • the correspondence relationship information further includes the association relationship indication information.
  • the data sending end 1400 further includes:
  • the first providing module 1405 is configured to provide the high-level entity with auxiliary information of the data packet, where the auxiliary information includes a data flow identifier.
  • the data sending end 1400 further includes:
  • the second providing module 1406 is configured to provide the high-level entity with auxiliary information of the data packet, where the auxiliary information includes at least one of the following: a data flow identifier, a network slice identifier, and a session identifier.
  • the data sending end 1400 may be the data sending end of any of the method embodiments in the embodiments of the present disclosure, and any implementation manner of the data sending end in the method embodiment of the disclosure may be used. It is implemented by the foregoing data sending end 1400 in this embodiment, and achieves the same beneficial effects, and details are not described herein again.
  • FIG. 18 is a structural diagram of a data receiving end according to an embodiment of the present disclosure. As shown in FIG. 18, the data receiving end 1800 includes:
  • the receiving module 1801 is configured to receive, by the PDCP entity, a data packet from the data sending end, and send the data packet to the corresponding SDAP entity according to the data flow identifier carried by the data packet;
  • the forwarding module 1802 is configured to forward, by the SDAP entity, the data packet to an application protocol layer, or forward the data packet to a corresponding network slice, a data stream, and a session unit.
  • the forwarding module 1802 is configured to: forward, by the SDAP entity, the data packet to a corresponding network slice according to at least one of a network slice identifier, a SDAP identifier, a data flow identifier, and a session identifier. Data stream and session unit.
  • the data receiving end 1800 further includes:
  • the establishing module 1803 is configured to establish a SDAP entity according to the configuration information of the network configuration or the protocol, where the configuration information includes at least one of the following: a network slice identifier, a data bearer identifier, a data flow identifier, a session identifier, and an association relationship indication information;
  • the indication module 1804 is configured to indicate, by using the SDAP entity, the correspondence relationship information of the SDAP entity to the upper layer entity, where the correspondence relationship information includes at least one of the following: a network slice identifier, a data bearer identifier, a data flow identifier, a session identifier, and SDAP logo.
  • association relationship indication information includes any one of the following:
  • the configuration information when the association relationship indication information indicates that one SDAP entity corresponds to one MAC entity, the configuration information further includes a MAC identifier.
  • the association relationship indication information indicates that one SDAP entity corresponds to one session unit, that one SDAP entity corresponds to one PDCP entity, that one SDAP entity corresponds to one MAC entity, or one SDAP entity is indicated.
  • the correspondence relationship information further includes the association relationship indication information.
  • the data receiving end 1800 may be the data receiving end of any of the method embodiments in the embodiments of the present disclosure, and any implementation manner of the data receiving end in the method embodiment of the disclosure may be used. It is implemented by the above-mentioned data receiving end 1800 in this embodiment, and achieves the same beneficial effects, and details are not described herein again.
  • FIG. 20 is a structural diagram of a data processing apparatus according to an embodiment of the present disclosure. As shown in FIG. 20, the data processing apparatus 2000 includes:
  • the establishing module 2001 is configured to establish a SDAP entity according to the configuration information of the network configuration or the protocol, where the configuration information includes at least one of the following: a network slice identifier, a data bearer identifier, a data flow identifier, a session identifier, and an association relationship indication information;
  • the indication module 2002 is configured to indicate, by using the SDAP entity, correspondence information of the SDAP entity to a high-level entity;
  • the transmission module 2003 is configured to perform data transmission between the high-layer entity, the SDAP entity, and the PDCP entity based on the correspondence relationship information.
  • association relationship indication information includes any one of the following:
  • the configuration information when the association relationship indication information indicates that one SDAP entity corresponds to one MAC entity, the configuration information further includes a MAC identifier.
  • the correspondence information includes at least one of the following: a network slice identifier, a data bearer identifier, a data stream identifier, a session identifier, and a SDAP identifier.
  • the transmitting module 2003 includes:
  • the first determining sub-module 20031 is configured to determine, by the high-layer entity, the target SDAP entity corresponding to the target data packet to be sent according to at least one of a network slice identifier, a SDAP identifier, a data flow identifier, and a session identifier.
  • a sending submodule 20032 configured to send, by the upper layer entity, the target data packet to the target SDAP entity;
  • the first forwarding sub-module 20033 is configured to send, by the target SDAP entity, a target packet data convergence protocol PDCP corresponding to the data bearer according to the correspondence between the SDAP entity and the data bearer DRB, after adding the data flow identifier to the target data packet.
  • the entity forwards the target packet.
  • the high-level entity provides auxiliary information of the sent target data packet.
  • the auxiliary information includes a data flow identifier.
  • the high-level entity provides auxiliary information of the sent target data packet, where
  • the auxiliary information includes at least one of the following: a data flow identifier, a network slice identifier, and a session identifier.
  • the transmission module 2003 includes:
  • a receiving submodule 20034 configured to receive, by the PDCP entity, a target data packet sent by the sending end;
  • the second forwarding module 20035 is configured to forward, by the PDCP entity, the target data packet to the corresponding target service data adaptation protocol SDAP entity according to the data flow identifier carried by the target data packet.
  • the data processing device 2000 further includes:
  • the forwarding module 2004 is configured to forward, by the target SDAP entity, the received target data packet to a corresponding network slice, a data stream, and a session unit.
  • the target SDAP entity forwards the received data packet to an application protocol layer.
  • the data processing device 2000 implements any implementation manner of the data processing method provided by the embodiment of the present disclosure, and achieves the same beneficial effects, and details are not described herein again.
  • FIG. 24 is a structural diagram of a data transmitting end of an application according to an embodiment of the present disclosure.
  • the data transmitting end 2400 includes: at least one processor 2401, a memory 2402, at least one network interface 2404, and a user interface 2403.
  • the various components in data transmitting end 2400 are coupled together by a bus system 2405.
  • the bus system 2405 is used to implement connection communication between these components.
  • the bus system 2405 includes a power bus, a control bus, and a status signal bus in addition to the data bus.
  • various buses are labeled as bus system 2405 in FIG.
  • the user interface 2403 may include a display, a keyboard, or a pointing device (eg, a mouse, a track ball, a touch pad, or a touch screen, etc.).
  • a pointing device eg, a mouse, a track ball, a touch pad, or a touch screen, etc.
  • the memory 2402 in the embodiments of the present disclosure may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory may be a read-only memory (ROM), a programmable read only memory (PROM), an erasable programmable read only memory (Erasable PROM, EPROM), or an electric Erase programmable read only memory (EEPROM) or flash memory.
  • the volatile memory can be a Random Access Memory (RAM) that acts as an external cache.
  • RAM Random Access Memory
  • many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (Synchronous DRAM).
  • SDRAM Double Data Rate Synchronous Dynamic Random Access Memory
  • DDRSDRAM Double Data Rate Synchronous Dynamic Random Access Memory
  • ESDRAM Enhanced Synchronous Dynamic Random Access Memory
  • SDRAM Synchronous Connection Dynamic Random Access Memory
  • DRRAM direct memory bus random access memory
  • the memory 2402 stores the following elements, executable modules or data structures, or a subset thereof, or their extended set: an operating system 24021 and an application 24022.
  • the operating system 24021 includes various system programs, such as a framework layer, a core library layer, a driver layer, and the like, for implementing various basic services and processing hardware-based tasks.
  • the application 24022 includes various applications, such as a Media Player, a Browser, etc., for implementing various application services.
  • a program implementing the method of the embodiments of the present disclosure may be included in the application 24022.
  • the processor 2401 by calling the program or instruction stored in the memory 2402, specifically, the program or instruction stored in the application program 24022, the processor 2401 is configured to:
  • the high-level entity sends the data packet to the corresponding SDAP entity according to at least one of a network slice identifier, a SDAP identifier, a data flow identifier, and a session identifier.
  • the SDAP entity adds a data flow identifier to the data packet, and sends the data packet to a PDCP entity corresponding to the DRB according to the correspondence between the SDAP entity and the DRB.
  • the method disclosed in the above embodiments of the present disclosure may be applied to the processor 2401 or implemented by the processor 2401.
  • the processor 2401 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the foregoing method may be completed by an integrated logic circuit of hardware in the processor 2401 or an instruction in a form of software.
  • the processor 2401 may be a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or the like. Programmable logic devices, discrete gates or transistor logic devices, discrete hardware components.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the steps of the method disclosed in connection with the embodiments of the present disclosure may be directly implemented by the hardware decoding processor, or may be performed by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like.
  • the storage medium is located in the memory 2402, and the processor 2401 reads the information in the memory 2402 and completes the steps of the above method in combination with its hardware.
  • the embodiments described herein can be implemented in hardware, software, firmware, middleware, microcode, or a combination thereof.
  • the processing unit can be implemented in one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processing (DSP), Digital Signal Processing Equipment (DSP Device, DSPD), programmable Programmable Logic Device (PLD), Field-Programmable Gate Array (FPGA), general purpose processor, controller, microcontroller, microprocessor, other for performing the functions described herein In an electronic unit or a combination thereof.
  • ASICs Application Specific Integrated Circuits
  • DSP Digital Signal Processing
  • DSP Device Digital Signal Processing Equipment
  • PLD programmable Programmable Logic Device
  • FPGA Field-Programmable Gate Array
  • the techniques described herein can be implemented by modules (eg, procedures, functions, and so on) that perform the functions described herein.
  • the software code can be stored in memory and executed by the processor.
  • the memory can be implemented in the processor or external to the processor.
  • the processor 2401 is further configured to:
  • the configuration information includes at least one of the following: a network slice identifier, a data bearer identifier, a data flow identifier, a session identifier, and an association relationship indication information;
  • the corresponding relationship information includes at least one of the following: a network slice identifier, a data bearer identifier, a data stream identifier, a session identifier, and a SDAP identifier.
  • association relationship indication information includes any one of the following:
  • the configuration information when the association relationship indication information indicates that one SDAP entity corresponds to one MAC entity, the configuration information further includes a MAC identifier.
  • the association relationship indication information indicates that one SDAP entity corresponds to one session unit, that one SDAP entity corresponds to one PDCP entity, that one SDAP entity corresponds to one MAC entity, or one SDAP entity is indicated.
  • the correspondence relationship information further includes the association relationship indication information.
  • the processor 2401 is further configured to:
  • the high-level entity provides auxiliary information of the data packet, and the auxiliary information includes a data flow identifier.
  • the processor 2401 is further configured to:
  • the high-level entity provides auxiliary information of the data packet, and the auxiliary information includes at least one of the following: a data flow identifier, a network slice identifier, and a session identifier.
  • the foregoing data sending end 2400 implements any implementation manner of the data transmission method provided by the embodiment of the present disclosure, and achieves the same beneficial effects, and details are not described herein again.
  • FIG. 25 is a structural diagram of a data receiving end of an application according to an embodiment of the present disclosure.
  • the data receiving end 2500 includes: at least one processor 2501, a memory 2502, at least one network interface 2504, and a user interface 2503.
  • the various components in data sink 2500 are coupled together by bus system 2505.
  • bus system 2505 is used to implement connection communication between these components.
  • the bus system 2505 includes a power bus, a control bus, and a status signal bus in addition to the data bus.
  • various buses are labeled as bus system 2505 in FIG.
  • the user interface 2503 may include a display, a keyboard, or a pointing device (eg, a mouse, a track ball, a touch pad, or a touch screen, etc.).
  • a pointing device eg, a mouse, a track ball, a touch pad, or a touch screen, etc.
  • the memory 2502 in the embodiments of the present disclosure may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory may be a read-only memory (ROM), a programmable read only memory (PROM), an erasable programmable read only memory (Erasable PROM, EPROM), or an electric Erase programmable read only memory (EEPROM) or flash memory.
  • the volatile memory can be a Random Access Memory (RAM) that acts as an external cache.
  • RAM Random Access Memory
  • many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (Synchronous DRAM).
  • SDRAM Double Data Rate Synchronous Dynamic Random Access Memory
  • DDRSDRAM Double Data Rate Synchronous Dynamic Random Access Memory
  • ESDRAM Enhanced Synchronous Dynamic Random Access Memory
  • SDRAM Synchronous Connection Dynamic Random Access Memory
  • DRRAM direct memory bus random access memory
  • the memory 2502 stores elements, executable modules or data structures, or a subset thereof, or their extended set: an operating system 25021 and an application 25022.
  • the operating system 25021 includes various system programs, such as a framework layer, a core library layer, a driver layer, and the like, for implementing various basic services and processing hardware-based tasks.
  • the application 25022 includes various applications, such as a media player (Media Player), a browser (Browser), etc., for implementing various application services.
  • a program implementing the method of the embodiments of the present disclosure may be included in the application 25022.
  • the processor 2501 by calling the program or instruction stored in the memory 2502, specifically, the program or instruction stored in the application 25022, the processor 2501 is configured to:
  • the SDAP entity forwards the data packet to an application protocol layer or forwards the data packet to a corresponding network slice, data stream, and session unit.
  • the method disclosed in the above embodiments of the present disclosure may be applied to the processor 2501 or implemented by the processor 2501.
  • the processor 2501 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the foregoing method may be completed by an integrated logic circuit of hardware in the processor 2501 or an instruction in a form of software.
  • the processor 2501 may be a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a Field Programmable Gate Array (FPGA), or the like. Programmable logic devices, discrete gates or transistor logic devices, discrete hardware components.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA Field Programmable Gate Array
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the steps of the method disclosed in connection with the embodiments of the present disclosure may be directly implemented by the hardware decoding processor, or may be performed by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like.
  • the storage medium is located in the memory 2502, and the processor 2501 reads the information in the memory 2502 and performs the steps of the above method in combination with its hardware.
  • the embodiments described herein can be implemented in hardware, software, firmware, middleware, microcode, or a combination thereof.
  • the processing unit can be implemented in one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processing (DSP), Digital Signal Processing Equipment (DSP Device, DSPD), programmable Programmable Logic Device (PLD), Field-Programmable Gate Array (FPGA), general purpose processor, controller, microcontroller, microprocessor, other for performing the functions described herein In an electronic unit or a combination thereof.
  • ASICs Application Specific Integrated Circuits
  • DSP Digital Signal Processing
  • DSP Device Digital Signal Processing Equipment
  • PLD programmable Programmable Logic Device
  • FPGA Field-Programmable Gate Array
  • the techniques described herein can be implemented by modules (eg, procedures, functions, and so on) that perform the functions described herein.
  • the software code can be stored in memory and executed by the processor.
  • the memory can be implemented in the processor or external to the processor.
  • the SDAP entity executed by the processor 2501 forwards the data packet to a corresponding network slice, a data stream, and a session unit, including:
  • the SDAP entity forwards the data packet to a corresponding network slice, data stream, and session unit according to at least one of a network slice identifier, a SDAP identifier, a data flow identifier, and a session identifier.
  • processor 2501 is further configured to:
  • the configuration information includes at least one of the following: a network slice identifier, a data bearer identifier, a data flow identifier, a session identifier, and an association relationship indication information;
  • the corresponding relationship information includes at least one of the following: a network slice identifier, a data bearer identifier, a data stream identifier, a session identifier, and a SDAP identifier.
  • association relationship indication information includes any one of the following:
  • the configuration information when the association relationship indication information indicates that one SDAP entity corresponds to one MAC entity, the configuration information further includes a MAC identifier.
  • the association relationship indication information indicates that one SDAP entity corresponds to one session unit, that one SDAP entity corresponds to one PDCP entity, that one SDAP entity corresponds to one MAC entity, or one SDAP entity is indicated.
  • the correspondence relationship information further includes the association relationship indication information.
  • the foregoing data receiving end 2500 implements any implementation manner of the data transmission method provided by the embodiment of the present disclosure, and achieves the same beneficial effects, and details are not described herein again.
  • FIG. 26 is a structural diagram of a data processing apparatus according to an embodiment of the present disclosure.
  • the data processing apparatus 2600 includes: at least one processor 2601, a memory 2602, at least one network interface 2604, and a user interface 2603. .
  • the various components in data processing device 2600 are coupled together by a bus system 2605.
  • the bus system 2605 is used to implement connection communication between these components.
  • the bus system 2605 includes a power bus, a control bus, and a status signal bus in addition to the data bus.
  • various buses are labeled as bus system 2605 in FIG.
  • the user interface 2603 may include a display, a keyboard, or a pointing device (eg, a mouse, a track ball, a touch pad, or a touch screen, etc.).
  • a pointing device eg, a mouse, a track ball, a touch pad, or a touch screen, etc.
  • the memory 2602 in the embodiments of the present disclosure may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory may be a read-only memory (ROM), a programmable read only memory (PROM), an erasable programmable read only memory (Erasable PROM, EPROM), or an electric Erase programmable read only memory (EEPROM) or flash memory.
  • the volatile memory can be a Random Access Memory (RAM) that acts as an external cache.
  • RAM Random Access Memory
  • many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (Synchronous DRAM).
  • SDRAM Double Data Rate Synchronous Dynamic Random Access Memory
  • DDRSDRAM Double Data Rate Synchronous Dynamic Random Access Memory
  • ESDRAM Enhanced Synchronous Dynamic Random Access Memory
  • SDRAM Synchronous Connection Dynamic Random Access Memory
  • DRRAM direct memory bus random access memory
  • the memory 2602 stores elements, executable modules or data structures, or a subset thereof, or their extended set: an operating system 26021 and an application 26022.
  • the operating system 26021 includes various system programs, such as a framework layer, a core library layer, a driver layer, and the like, for implementing various basic services and processing hardware-based tasks.
  • the application program 26022 includes various applications, such as a media player (Media Player), a browser (Browser), etc., for implementing various application services.
  • a program implementing the method of the embodiments of the present disclosure may be included in the application 26022.
  • the processor 2601 by calling the program or instruction stored in the memory 2602, specifically, the program or instruction stored in the application program 26022, the processor 2601 is configured to:
  • the configuration information includes at least one of the following: a network slice identifier, a data bearer identifier, a data flow identifier, a session identifier, and an association relationship indication information;
  • Data transmission is performed between the high layer entity, the SDAP entity, and the PDCP entity based on the correspondence relationship information.
  • the method disclosed in the above embodiments of the present disclosure may be applied to the processor 2601 or implemented by the processor 2601.
  • the processor 2601 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the foregoing method may be completed by an integrated logic circuit of hardware in the processor 2601 or an instruction in a form of software.
  • the processor 2601 may be a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a Field Programmable Gate Array (FPGA), or the like. Programmable logic devices, discrete gates or transistor logic devices, discrete hardware components.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA Field Programmable Gate Array
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the steps of the method disclosed in connection with the embodiments of the present disclosure may be directly implemented by the hardware decoding processor, or may be performed by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like.
  • the storage medium is located in the memory 2602, and the processor 2601 reads the information in the memory 2602 and performs the steps of the above method in combination with its hardware.
  • the embodiments described herein can be implemented in hardware, software, firmware, middleware, microcode, or a combination thereof.
  • the processing unit can be implemented in one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processing (DSP), Digital Signal Processing Equipment (DSP Device, DSPD), programmable Programmable Logic Device (PLD), Field-Programmable Gate Array (FPGA), general purpose processor, controller, microcontroller, microprocessor, other for performing the functions described herein In an electronic unit or a combination thereof.
  • ASICs Application Specific Integrated Circuits
  • DSP Digital Signal Processing
  • DSP Device Digital Signal Processing Equipment
  • PLD programmable Programmable Logic Device
  • FPGA Field-Programmable Gate Array
  • the techniques described herein can be implemented by modules (eg, procedures, functions, and so on) that perform the functions described herein.
  • the software code can be stored in memory and executed by the processor.
  • the memory can be implemented in the processor or external to the processor.
  • association relationship indication information includes any one of the following:
  • the configuration information when the association relationship indication information indicates that one SDAP entity corresponds to one MAC entity, the configuration information further includes a MAC identifier.
  • the correspondence information includes at least one of the following: a network slice identifier, a data bearer identifier, a data stream identifier, a session identifier, and a SDAP identifier.
  • the step of performing, by the processor 2601, performing data transmission between the high-layer entity, the SDAP entity, and the packet data convergence protocol (PDCP entity) based on the corresponding relationship information includes: :
  • the high-level entity determines, according to at least one of a network slice identifier, a SDAP identifier, a data flow identifier, and a session identifier, a target SDAP entity corresponding to the target data packet to be sent;
  • the high-level entity sends the target data packet to the target SDAP entity
  • the target SDAP entity forwards the target data packet to the target PDCP entity corresponding to the data bearer after adding the data flow identifier to the target data packet according to the corresponding relationship between the SDAP entity and the data bearer DRB.
  • the high-level entity provides auxiliary information of the sent target data packet.
  • the auxiliary information includes a data flow identifier.
  • the high-level entity provides auxiliary information of the sent target data packet, where
  • the auxiliary information includes at least one of the following: a data flow identifier, a network slice identifier, and a session identifier.
  • the performing, by the processor 2601, the data transmission between the high-layer entity, the SDAP entity, and the PDCP entity based on the correspondence information includes:
  • the PDCP entity receives the target data packet sent by the sending end
  • the PDCP entity forwards the target data packet to the corresponding target SDAP entity according to the data flow identifier carried by the target data packet.
  • the processor 2601 is further configured to:
  • the target SDAP entity forwards the received target data packet to a corresponding network slice, data stream, and session unit.
  • the target SDAP entity forwards the received data packet to an application protocol layer.
  • the foregoing data processing device 2600 implements any implementation manner of the data processing method provided by the embodiment of the present disclosure, and achieves the same beneficial effects, and details are not described herein again.
  • an embodiment of the present disclosure further provides a computer readable storage medium, where the data transfer program is stored on a computer readable storage medium, and the data transfer program is executed by a processor to implement the embodiment of the present disclosure.
  • the embodiment of the present disclosure further provides a computer readable storage medium, where the data transfer program is stored on the computer readable storage medium, and the data transfer program is executed by the processor to implement the embodiment of the present disclosure.
  • the disclosed apparatus and method 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 objectives of the embodiments of the present disclosure.
  • each functional unit in various embodiments of the present disclosure 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 functions may be stored in a computer readable storage medium if implemented in the form of a software functional unit and sold or used as a standalone product. Based on such understanding, the portion of the technical solution of the present disclosure that contributes in essence or to the prior art or the portion of the technical solution may be embodied in the form of a software product stored in a storage medium, including The instructions are used to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present disclosure.
  • the foregoing storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a ROM, a RAM, a magnetic disk, or an optical disk.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Communication Control (AREA)

Abstract

本公开提供一种数据传输方法、相关设备及系统，该方法包括：高层实体根据网络切片标识、SDAP标识、数据流标识和会话标识中的至少一项，将数据包发送给对应的SDAP实体；所述SDAP实体在所述数据包中添加数据流标识，并根据SDAP实体与DRB的对应关系，向DRB对应的PDCP实体发送所述数据包。

Description

数据传输方法、数据发送端、数据接收端、数据传输系统及计算机可读存储介质
相关申请的交叉引用
本申请主张在2017年6月8日在中国提交的中国专利申请号No.201710431213.3的优先权，其全部内容通过引用包含于此。
技术领域
本公开涉及通信技术领域，尤其涉及一种数据传输方法、相关设备及系统。
背景技术
众所周知，由于5G系统引入了服务质量(Quality-of-Service，QoS)的网络侧指示机制，因此需要在上行和下行数据的发送过程中都需要加入终端的IP数据流的QoS指示信息(如flow ID)，而该协议层位于包数据汇聚协议(Packet Data Convergence Protocol，PDCP)层之上。
然而在5G的QoS控制中，不同的数据可以对应不同网络切片(Slice)，1个网络切片中可以包含多个会话单元(例如，PDU session)，1个会话单元中可以包含多个数据流(flow)。因此，如何实现高层实体、业务数据适配协议(Service Data Adaptation Protocol，SDAP)实体和PDCP实体之间的交互成为了亟需解决的问题。
发明内容
第一方面，本公开实施例提供了一种数据传输方法，应用于数据发送端，包括：
高层实体根据网络切片标识、SDAP标识、数据流标识和会话标识中的至少一项，将数据包发送给对应的SDAP实体；
所述SDAP实体在所述数据包中添加数据流标识，并根据SDAP实体与数据承载(Data Radio Bearer，DRB)的对应关系，向DRB对应的PDCP实 体发送所述数据包。
第二方面，本公开实施例还提供了一种数据传输方法，应用于数据接收端，包括：
PDCP实体接收来自数据发送端的数据包，根据所述数据包携带的数据流标识，向对应的SDAP实体发送所述数据包；
所述SDAP实体将所述数据包转发至应用协议层，或者，将所述数据包转发至对应的网络切片、数据流和会话单元。
第三方面，本公开实施例还提供了一种数据发送端，包括：
第一发送模块，用于供高层实体根据网络切片标识、SDAP标识、数据流标识和会话标识中的至少一项，将数据包发送给对应的SDAP实体；
第二发送模块，用于供所述SDAP实体在所述数据包中添加数据流标识，并根据SDAP实体与数据承载DRB的对应关系，向DRB对应的PDCP实体发送所述数据包。
第四方面，本公开实施例还提供了一种数据接收端，包括：
接收模块，用于供PDCP实体接收来自数据发送端的数据包，根据所述数据包携带的数据流标识，向对应的SDAP实体发送所述数据包；
转发模块，用于供所述SDAP实体将所述数据包转发至应用协议层，或者，将所述数据包转发至对应的网络切片、数据流和会话单元。
第五方面，本公开实施例还提供了一种数据发送端，包括：处理器、存储器、网络接口和用户接口，所述处理器、所述存储器、所述网络接口和所述用户接口通过总线系统耦合在一起，所述处理器用于读取所述存储器中的程序，执行本公开实施例提供的数据发送端侧的数据传输方法中的步骤。
第六方面，本公开实施例还提供了一种数据接收端，包括：处理器、存储器、网络接口和用户接口，所述处理器、所述存储器、所述网络接口和所述用户接口通过总线系统耦合在一起，所述处理器用于读取所述存储器中的程序，执行本公开实施例提供的数据接收端侧的数据传输方法中的步骤。
第七方面，本公开实施例还提供了一种数据传输系统，包括本公开实施例提供的数据发送端和数据接收端。
第八方面，本公开实施例还提供了一种计算机可读存储介质，所述计算 机可读存储介质上存储有数据传输程序，所述数据传输程序被处理器执行时实现本公开实施例提供的数据发送端侧的数据传输方法的步骤。
第九方面，本公开实施例还提供了一种计算机可读存储介质，所述计算机可读存储介质上存储有数据传输程序，所述数据传输程序被处理器执行时实现本公开实施例提供的数据接收端侧的的数据传输方法的步骤。
附图说明
为了更清楚地说明本公开实施例的技术方案，下面将对本公开实施例描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本公开的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获得其他的附图。
图1是本公开实施例应用的一种数据传输系统的结构图；
图2是本公开实施例提供的一种数据传输方法的流程图；
图3是本公开实施例提供的另一种数据处理方法的流程图；
图4是本公开实施例提供的一种数据流的传输示意图；
图5是本公开实施例提供的另一种数据流的传输示意图；
图6是本公开实施例提供的另一种数据流的传输示意图；
图7是本公开实施例提供的另一种数据流的传输示意图；
图8是本公开实施例提供的另一种数据流的传输示意图；
图9是本公开实施例提供的另一种数据传输方法的流程图；
图10是本公开实施例提供的另一种数据传输方法的流程图；
图11是本公开实施例提供的一种数据处理方法的流程图；
图12是本公开实施例提供的另一种数据处理方法的流程图；
图13是本公开实施例提供的另一种数据处理方法的流程图；
图14是本公开实施例提供的一种数据发送端的结构图；
图15是本公开实施例提供的另一种数据发送端的结构图；
图16是本公开实施例提供的另一种数据发送端的结构图；
图17是本公开实施例提供的另一种数据发送端的结构图；
图18是本公开实施例提供的一种数据接收端的结构图；
图19是本公开实施例提供的另一种数据接收端的结构图；
图20是本公开实施例提供的一种数据处理装置的结构图；
图21是本公开实施例提供的另一种数据处理装置的结构图；
图22是本公开实施例提供的另一种数据处理装置的结构图；
图23是本公开实施例提供的另一种数据处理装置的结构图；
图24是本公开实施例提供的另一种数据发送端的结构图；
图25是本公开实施例提供的另一种数据接收端的结构图；
图26是本公开实施例提供的另一种数据处理装置的结构图。
具体实施方式
下面将结合本公开实施例中的附图，对本公开实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本公开一部分实施例，而不是全部的实施例。基于本公开中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本公开保护的范围。
参见图1，图1是本公开实施例可应用的一种数据传输系统的结构图，如图1所示，包括数据发送端11和数据接收端12，其中，数据发送端11可以是用户终端，又可称作用户设备(User Equipment，UE)，例如：可以是手机、平板电脑(Tablet Personal Computer)、膝上型电脑(Laptop Computer)、个人数字助理(personal digital assistant，PDA)、移动上网装置(Mobile Internet Device，MID)或可穿戴式设备(Wearable Device)等终端侧设备，或者可以是网络侧设备，例如：传输接收点(Transmission Reception Point，TRP)，或者可以是基站，基站可以是宏站，如LTE eNB、5G NR NB等；数据发送端11也可以是接入点(Access Point，AP)。需要说明的是，在本公开实施例中并不限定数据发送端11的具体类型，其中附图以数据发送端11为用户终端进行举例。数据接收端12可以是UE，例如：可以是手机、平板电脑、膝上型电脑、PDA、MID或可穿戴式设备等终端侧设备，或者可以是网络侧设备，例如：TRP，或者可以是基站，基站可以是宏站，如LTE eNB、5G NR NB等；数据接收端12也可以是AP。需要说明的是，在本公开实施例中并不限定数据接收端12的具体类型。其中附图以数据接收端12为网络侧设备进行 举例。
需要说明的是，在本公开实施例中并不限定数据发送端11和数据接收端12的具体类型，数据发送端11和数据接收端12的具体功能将通过以下多个实施例进行具体描述。
参见图2，图2是本公开实施例提供的一种数据传输方法的流程图，该方法应用于数据发送端，如图2所示，包括以下步骤：
步骤201、高层实体根据网络切片标识、SDAP标识、数据流标识和会话标识中的至少一项，将数据包发送给对应的SDAP实体。
其中，上述网络切片标识可以用于标识上述数据包归属的网络切片，且网络切片可以包括多个会话单元(例如，PDU session)，而一个会话单元可以包括多个数据流(flow)。而数据流标识可以用于标识上述数据包归属的数据流，上述会话标识可以用于标识上述数据包归属的数据流对应的会话单元。该步骤中，可以是根据数据包的网络切片标识、数据流标识或者会话标识，确定对应的SDAP标识，进而将该数据发送给对应的SDAP实体。
步骤202、所述SDAP实体在所述数据包中添加数据流标识，并根据SDAP实体与DRB的对应关系，向DRB对应的PDCP实体发送所述数据包。
其中，上述SDAP实体与DRB的对应关系可以是预先设置好的，上述数据包中添加数据流标识后可以是在数据包添加对应数据流的标识，而数据包的数据流标识可以是根据网络的预设配置的进行添加的。而DRB对应的PDCP实体可以是预先配置的，例如：一个DRB对应一个PDCP实体，或者多个DRB对应同一个PDCP实体等。
另外，本公开实施例中，上述数据包可以是TCP/IP数据包。
本实施例中，高层实体根据网络切片标识、SDAP标识、数据流标识和会话标识中的至少一项，将数据包发送给对应的SDAP实体；所述SDAP实体在所述数据包中添加数据流标识，并根据SDAP实体与DRB的对应关系，向DRB对应的PDCP实体发送所述数据包。从而实现了高层实体、SDAP实体和PDCP实体之间的交互。
参见图3，图3是本公开实施例提供的另一种数据传输方法的流程图，该方法应用于数据发送端，如图3所示，包括以下步骤：
步骤301、预先根据网络配置或预先约定的配置信息建立SDAP实体。
其中，所述配置信息包括以下至少一项：网络切片标识、数据承载标识、数据流标识、会话标识和关联关系指示信息。
其中，上述关联关系指示信息可以指示上述SDAP实体与其他实体之间的对应关系，从而步骤301在接收到上述配置信息后，可以建立相应的SDAP实体。
步骤302、通过所述SDAP实体向高层实体指示所述SDAP实体的对应关系信息。
其中，所述对应关系信息包括以下至少一项：网络切片标识、数据承载标识、数据流标识、会话标识和SDAP标识。
其中，上述对应关系信息可以用于指示SDAP实体的对应关系，例如：SDAP实体与其他实体的对应关系，以及还可以指示上述网络切片标识、数据承载标识、数据流标识和会话标识之间的关系。另外，上述高层实体可以位于SDAP层之上的实体，例如：非接入层(Non-access stratum，NAS)层实体。
步骤303、高层实体根据网络切片标识、SDAP标识、数据流标识和会话标识中的至少一项，将数据包发送给对应的SDAP实体。
该步骤中，可以是根据数据包的网络切片标识、数据流标识或者会话标识，确定对应的SDAP标识，进而将该数据发送给对应的SDAP实体。
步骤304、所述SDAP实体在所述数据包中添加数据流标识，并根据SDAP实体与DRB的对应关系，向DRB对应的PDCP实体发送所述数据包。
可选的，所述关联关系指示信息包括以下任一种：
指示1个SDAP实体对应1个数据流(flow)；
指示1个SDAP实体对应1个会话单元(例如，PDU session)；
指示1个SDAP实体对应1个PDCP实体；
指示1个SDAP实体对应1个媒体接入控制(Medium Access Control，MAC)实体；
指示1个SDAP实体对应1个终端。
该实施方式中，可以实现建立为每个数据流(flow)建立一个SDAP实 体，例如：如图4所示，不同数据流通过不同的SDAP发送至对应的PDCP实体。
需要说明的是，本公开实施例中，数据流与PDCP实体的对应关系可以是预先配置的，一个PDCP实体可以对应一个或者多个数据流，且一个PDCP实体可以对应一个数据承载，或者一个SDAP对应一个数据承载。
另外，上述实施方式中，还可以实现1个SDAP实体对应1个PDU session，例如：图5所示，一个PDU session包括的多个数据流通过一个SDAP发送至各数据流对应的PDCP实体。
另外，上述实施方式中，还可以实现1个SDAP实体对应1个PDCP实体，例如：图6所示，一个PDCP实体对应的数据流通过一个SDAP发送至各数据流对应的PDCP实体。
另外，上述实施方式中，还可以实现1个SDAP实体对应1个MAC实体，例如：图7所示，一个MAC实体对应的多个PDU session的数据流均通过同一个SDAP实体发送至各数据流对应的PDCP实体，并经过PDCP发送至无线链路层控制(Radio Link Control，RLC)实体，最后发送给MAC实体。
且，上述实施方式中，还可以实现1个SDAP实体对应1个终端，例如：图8所示，一个终端的多个MAC实体对应的多个PDU session的数据流均通过同一个SDAP实体发送至各数据流对应的PDCP实体，并经过PDCP发送至RLC实体，最后发送给该终端的MAC实体。
可选的，当所述关联关系指示信息为指示1个SDAP实体对应1个MAC实体时，所述配置信息还包括MAC标识。
该实施方式中，可以实现当1个SDAP实体对应1个MAC实体时，通过上述MAC标识指示对应的MAC实体。
可选的，当所述关联关系指示信息为指示1个SDAP实体对应1个会话单元、指示1个SDAP实体对应1个PDCP实体、指示1个SDAP实体对应1个MAC实体或指示1个SDAP实体对应1个终端时，所述对应关系信息还包括所述关联关系指示信息。
该实施方式中，可以实现在关联关系指示信息为指示1个SDAP实体对应1个会话单元、指示1个SDAP实体对应1个PDCP实体、指示1个SDAP 实体对应1个MAC实体或指示1个SDAP实体对应1个终端时，通过上述对应关系信息向高层实体发送上述关联关系指示信息，从而高层实体可以通过该关联指示信息决定是否提供数据包的辅助信息，以让SDAP准确地传输数据包，以提高数据传输性能。
例如：当所述关联关系指示信息为指示1个SDAP实体对应1个会话单元或指示1个SDAP实体对应1个PDCP实体时，所述方法还包括：
所述高层实体提供所述数据包的辅助信息，所述辅助信息包括数据流标识。
这样可以实现在1个SDAP实体对应1个会话单元或1个SDAP实体对应1个PDCP实体时，提供数据流标识，从而可以准确地让SDAP添加相应的数据流标识，以提高数据传输性能。
又例如：当所述关联关系指示信息为指示1个SDAP实体对应1个MAC实体或指示1个SDAP实体对应1个终端时，所述方法还包括：
所述高层实体提供所述数据包的辅助信息，所述辅助信息包括以下至少一项：数据流标识、网络切片标识和会话标识。
该实施方式中，可以实现在1个SDAP实体对应1个MAC实体或指示1个SDAP实体对应1个终端时，提供数据流标识、网络切片标识和会话标识，从而可以准确地让SDAP添加相应的数据流标识，以及根据网络切片标识和会话标识进行准确的传输，以提高数据传输性能。
本实施例中，预先根据网络配置或预先约定的配置信息建立SDAP实体，所述配置信息包括以下至少一项：网络切片标识、数据承载标识、数据流标识、会话标识和关联关系指示信息；通过所述SDAP实体向高层实体指示所述SDAP实体的对应关系信息，所述对应关系信息包括以下至少一项：网络切片标识、数据承载标识、数据流标识、会话标识和SDAP标识高层实体；根据网络切片标识、SDAP标识、数据流标识和会话标识之间的对应关系，将数据包发送给对应的SDAP实体；所述SDAP实体在所述数据包中添加数据流标识，并根据SDAP实体与DRB的对应关系，向DRB对应的PDCP实体发送所述数据包。这样可以灵活建立SDAP实体，以提高数据发送端的整体性能，且还实现了高层实体、SDAP实体和PDCP实体之间的交互。
请参见图9，图9是本公开实施例提供的另一种数据传输方法的流程图该方法应用于数据接收端，如图9所示，包括：
步骤901、PDCP实体接收来自数据发送端的数据包，根据所述数据包携带的数据流标识，向对应的SDAP实体发送所述数据包；
其中，上述对应的SDAP实体可以是上述数据流标识对应的SDAP实体。
步骤902、所述SDAP实体将所述数据包转发至应用协议层，或者，将所述数据包转发至对应的网络切片、数据流和会话单元。
其中，步骤902中可以数据接收端为用户终端时，SDAP实体将所述数据包转发至应用协议层，而数据接收端为网络侧设备时，所述SDAP实体将所述数据包转发至对应的网络切片、数据流和会话单元。
本实施例中，PDCP实体接收来自数据发送端的数据包，根据所述数据包携带的数据流标识，向对应的SDAP实体发送所述数据包；所述SDAP实体将所述数据包转发至应用协议层，或者，将所述数据包转发至对应的网络切片、数据流和会话单元。从而实现了SDAP实体和PDCP实体之间的交互。
请参见图10，图10是本公开实施例提供的另一种数据传输方法的流程图该方法应用于数据接收端，如图10所示，包括：
步骤1001、预先根据网络配置或协议约定的配置信息建立SDAP实体，所述配置信息包括以下至少一项：网络切片标识、数据承载标识、数据流标识、会话标识和关联关系指示信息。
其中，上述建立SDAP实体可以参考图3所示的实施例的相应说明，此处不作赘述，且可以达到相同的有益效果。
步骤1002、通过所述SDAP实体向高层实体指示所述SDAP实体的对应关系信息，所述对应关系信息包括以下至少一项：网络切片标识、数据承载标识、数据流标识、会话标识和SDAP标识。
其中，上述SDAP实体的对应关系信息可以参考图3所示的实施例的相应说明，此处不作赘述，且可以达到相同的有益效果。
步骤1003、PDCP实体接收来自数据发送端的数据包，根据所述数据包携带的数据流标识，向对应的SDAP实体发送所述数据包；
其中，上述对应的SDAP实体可以是上述数据流标识对应的SDAP实体。
步骤1004、所述SDAP实体将所述数据包转发至应用协议层，或者，将所述数据包转发至对应的网络切片、数据流和会话单元。
可选的，所述SDAP实体将所述数据包转发至对应的网络切片、数据流和会话单元，包括：
所述SDAP实体根据网络切片标识、SDAP标识、数据流标识和会话标识中的至少一项，将所述数据包转发至对应的网络切片、数据流和会话单元。
该实施方式中，可以实现根据上述对应关系准确地将数据包发至对应的网络切片、数据流和会话单元，以提高数据传输性能。
可选的，所述关联关系指示信息包括以下任一种：
指示1个SDAP实体对应1个数据流；
指示1个SDAP实体对应1个会话单元；
指示1个SDAP实体对应1个PDCP实体；
指示1个SDAP实体对应1个MAC实体；
指示1个SDAP实体对应1个终端。
其中，上述关联关系指示信息可以参考图3所示的实施例的相应说明，此处不作赘述，且可以达到相同的有益效果。
可选的，当所述关联关系指示信息为指示1个SDAP实体对应1个MAC实体时，所述配置信息还包括MAC标识。
其中，上述配置信息可以参考图3所示的实施例的相应说明，此处不作赘述，且可以达到相同的有益效果。
可选的，当所述关联关系指示信息为指示1个SDAP实体对应1个会话单元、指示1个SDAP实体对应1个PDCP实体、指示1个SDAP实体对应1个MAC实体或指示1个SDAP实体对应1个终端时，所述对应关系信息还包括所述关联关系指示信息。
其中，上述对应关系信息可以参考图3所示的实施例的相应说明，此处不作赘述，且可以达到相同的有益效果。
本实施例中，预先根据网络配置或预先约定的配置信息建立SDAP实体，所述配置信息包括以下至少一项：网络切片标识、数据承载标识、数据流标识、会话标识和关联关系指示信息；通过所述SDAP实体向高层实体指示所 述SDAP实体的对应关系信息，所述对应关系信息包括以下至少一项：网络切片标识、数据承载标识、数据流标识、会话标识和SDAP标识高层实体；PDCP实体接收来自数据发送端的数据包，根据所述数据包携带的数据流标识，向对应的SDAP实体发送所述数据包；所述SDAP实体将所述数据包转发至应用协议层，或者，将所述数据包转发至对应的网络切片、数据流和会话单元。这样可以灵活建立SDAP实体，以提高数据发送端的整体性能，且还实现了SDAP实体和PDCP实体之间的交互。
参见图11，图11是本公开实施例提供的一种数据处理方法的流程图，如图11所示，包括以下步骤：
步骤1101、预先根据网络配置或协议约定的配置信息建立SDAP实体，所述配置信息包括以下至少一项：网络切片标识、数据承载标识、数据流标识、会话标识和关联关系指示信息。
其中，上述网络切片标识用于标识网络切片，且网络切片可以包括多个会话单元(例如，PDU session)，而一个会话单元可以包括多个数据流(flow)。而上述数据承载标识可以用于标识DRB，且该数据承载可以与PDCP对应。而上述关联关系指示信息用于指示上述SDAP实体与其他实体之间的对应关系，从而步骤201在接收到上述配置信息后，可以建立相应的SDAP实体。
步骤1102、通过所述SDAP实体向高层实体指示所述SDAP实体的对应关系信息。
其中，上述对应关系信息可以用于指示SDAP实体的对应关系，例如：SDAP实体与其他实体的对应关系，以及还可以指示上述网络切片标识、数据承载标识、数据流标识和会话标识之间的关系。另外，上述高层实体可以位于SDAP层之上的实体，例如：NAS层实体。
步骤1103、基于所述对应关系信息在所述高层实体、SDAP实体和PDCP实体之间进行数据传输。
上述基于所述对应关系信息在所述高层实体、SDAP实体和包数据汇聚协议PDCP实体之间进行数据传输，可以是按照上述对应关系信息指示的实体之间或者实体与数据之间对应关系，在上述高层实体SDAP实体和包数据汇聚协议PDCP实体之间进行数据传输。且该数据传输可以是发送数据或者 接收数据。
需要说明的是，本方法可以应用于图1所示的系统中的数据接收端或者数据发送端。
本实施例，预先根据网络配置或协议约定的配置信息建立SDAP实体，所述配置信息包括以下至少一项：网络切片标识、数据承载标识、数据流标识、会话标识和关联关系指示信息；通过所述SDAP实体向高层实体指示所述SDAP实体的对应关系信息；基于所述对应关系信息在所述高层实体、SDAP实体和包数据汇聚协议PDCP实体之间进行数据传输。从而实现了高层实体、SDAP实体和PDCP实体之间的交互。
参见图12，图12是本公开实施例提供的另一种数据处理方法的流程图，如图12所示，包括以下步骤：
步骤1201、预先根据网络配置或协议约定的配置信息建立SDAP实体，所述配置信息包括以下至少一项：网络切片标识、数据承载标识、数据流标识、会话标识和关联关系指示信息。
可选的，所述关联关系指示信息包括以下任一种：
指示1个SDAP实体对应1个数据流；
指示1个SDAP实体对应1个会话单元；
指示1个SDAP实体对应1个PDCP实体；
指示1个SDAP实体对应1个MAC实体；
指示1个SDAP实体对应1个终端。
该实施方式中，可以实现建立为每个数据流(flow)建立一个SDAP实体，例如：如图4所示，不同数据流通过不同的SDAP发送至对应的PDCP实体。
需要说明的是，本公开实施例中，数据流与PDCP实体的对应关系可以是预先配置的，一个PDCP实体可以对应一个或者多个数据流，且一个PDCP实体可以对应一个数据承载，或者一个SDAP对应一个数据承载。
另外，上述实施方式中，还可以实现1个SDAP实体对应1个PDU session，例如：图5所示，一个PDU session包括的多个数据流通过一个SDAP发送至各数据流对应的PDCP实体。
另外，上述实施方式中，还可以实现1个SDAP实体对应1个PDCP实体，例如：图6所示，一个PDCP实体对应的数据流通过一个SDAP发送至各数据流对应的PDCP实体。
另外，上述实施方式中，还可以实现1个SDAP实体对应1个MAC实体，例如：图7所示，一个MAC实体对应的多个PDU session的数据流均通过同一个SDAP实体发送至各数据流对应的PDCP实体，并经过PDCP发送至RLC实体，最后发送给MAC实体。
且，上述实施方式中，还可以实现1个SDAP实体对应1个终端，例如：图8所示，一个终端的多个MAC实体对应的多个PDU session的数据流均通过同一个SDAP实体发送至各数据流对应的PDCP实体，并经过PDCP发送至RLC实体，最后发送给该终端的MAC实体。
步骤1202、通过所述SDAP实体向高层实体指示所述SDAP实体的对应关系信息。
可选的，当所述关联关系指示信息为指示1个SDAP实体对应1个MAC实体时，所述配置信息还包括MAC标识。
该实施方式中，可以实现当1个SDAP实体对应1个MAC实体时，通过上述MAC标识指示对应的MAC实体。
可选的，上述对应关系信息包括以下至少一项：网络切片标识、数据承载标识、数据流标识、会话标识和SDAP标识。
通过上述网络切片标识、数据承载标识、数据流标识、会话标识和SDAP标识可以明确地指示网络切片标识、数据承载标识、数据流标识、会话标识和SDAP标识之间的对应的关系，从而在数据传输时，可以准确地通过相应的实体进行传输，以提高数据传输性能。
步骤1203、高层实体根据网络切片标识、SDAP标识、数据流标识和会话标识中的至少一项，确定待发送的目标数据包对应的目标SDAP实体。
其中，步骤1203可以是上述方法可以应用于数据发送端时执行的，例如：终端或者网络侧设备。
其中，上述目标数据包可以是某一数据流中的数据包，从而通过上述对应关系，可以确定目标数据对应的目标SDAP实体。例如：1个SDAP实体 对应1个数据流时，通过该目标数据包的数据流可以确定对应的SDAP实体；又例如：1个SDAP实体对应1个会话单元，可以通过目标数据包对应的会话确定对应的SDAP实体；又例如：1个SDAP实体对应1个PDCP实体时，可以通过目标数据包对应的数据流对应的PDCP实体确定对应的SDAP实体；又例如：指示1个SDAP实体对应1个MAC实体时，可以通过目标数据包对应的数据流对PDU session对应的MAC确定对应的SDAP实体；又例如：指示1个SDAP实体对应1个终端，通过该目标数据包对应的终端可以确定对应的SDAP实体。
步骤1204、高层实体向所述目标SDAP实体发送所述目标数据包。
当目标SDAP实体确定后，步骤304可以将目标数据包发送给该SDAP实体。可选的，高层实体向所述目标SDAP实体发送所述目标数据包时，对发送的数据包可以提供如下一项或者多项辅助信息：
数据流标识、会话标识、SDAP标识、DRB标识、PDCP标识和MAC标识。
步骤1205、所述目标SDAP实体根据SDAP实体与DRB的对应关系，在所述目标数据包中添加数据流标识后，向数据承载对应的目标PDCP实体转发目标数据包。
其中，上述SDAP实体与DRB的对应关系可以是预先设置好的，而上述目标数据包中添加数据流标识后可以是在目标数据包添加对应数据流的标识。且目标数据包的数据流标识可以是根据网络配置的进行添加的。
另外，本公开实施例中，上述目标数据包可以是TCP/IP数据包。
可选的，当所述关联关系指示信息为指示1个SDAP实体对应1个会话单元或指示1个SDAP实体对应1个PDCP实体时，所述高层实体提供发送的目标数据包的辅助信息，所述辅助信息包括数据流标识。
该实施方式中，可以实现向SDAP实体发送数据流标识，从而可以准确地让SDAP添加相应的数据流标识，以提高数据传输性能。
可选的，当所述关联关系指示信息为指示1个SDAP实体对应1个MAC实体或指示1个SDAP实体对应1个终端时，所述高层实体提供发送的目标数据包的辅助信息，所述辅助信息包括以下至少一项：数据流标识、网络切 片标识和会话标识。
该实施方式中，可以实现向SDAP实体发送数据流标识、网络切片标识和会话标识，从而可以准确地让SDAP添加相应的数据流标识，以及根据网络切片标识和会话标识进行准确的传输，以提高数据传输性能。
本实施例中，通过上述步骤可以实现准确地在高层实体、SDAP实体和PDCP之间进行数据的发送，从而提高数据发送端的发送性能。
参见图13，图13是本公开实施例提供的另一种数据处理方法的流程图，如图13所示，包括以下步骤：
步骤1301、预先根据网络配置或协议约定的配置信息建立SDAP实体，所述配置信息包括以下至少一项：网络切片标识、数据承载标识、数据流标识、会话标识和关联关系指示信息。
可选的，所述关联关系指示信息包括以下任一种：
指示1个SDAP实体对应1个数据流；
指示1个SDAP实体对应1个会话单元(PDU session)；
指示1个SDAP实体对应1个PDCP实体；
指示1个SDAP实体对应1个MAC实体；
指示1个SDAP实体对应1个终端。
其中，关于上述关联关系指示信息可以参见图12所示的实施例的相应说明，此处不作赘述。
步骤1302、通过所述SDAP实体向高层实体指示所述SDAP实体的对应关系信息。
可选的，当所述关联关系指示信息为指示1个SDAP实体对应1个MAC实体时，所述配置信息还包括MAC标识。
该实施方式中，可以实现当1个SDAP实体对应1个MAC实体时，通过上述MAC标识指示对应的MAC实体。
可选的，上述对应关系信息包括以下至少一项：网络切片标识、数据承载标识、数据流标识、会话标识和SDAP标识。
通过上述网络切片标识、数据承载标识、数据流标识、会话标识和SDAP标识可以明确地指示网络切片标识、数据承载标识、数据流标识、会话标识 和SDAP标识之间的对应的关系，从而在数据传输时，可以准确地通过相应的实体进行传输，以提高数据传输性能。
步骤1303、PDCP实体接收发送端发送的目标数据包。
其中，步骤1303可以是上述方法应用于接收端时执行的，例如：终端或者网络侧设备。
其中，上述目标数据包可以是图12所示的实施例中的目标数据包，对此不作赘述，且该目标数据包携带有数据流标识。
步骤1304、PDCP实体根据所述目标数据包携带的数据流标识，向对应的目标SDAP实体转发所述目标数据包。
其中，上述对应的目标SDAP可以通过上述关联关系指示信息进行确定。
可选的，当上述方法应用于接收端，且该接收端为网络侧设备时，所述向对应的目标业务数据适配协议SDAP实体转发所述目标数据包的步骤之后，所述方法还包括：
所述目标SDAP实体将接收到的目标数据包转发至对应的网络切片、数据流和会话单元。
该实施方式中，还可以实现将目标数据包发送至对应的网络切片、数据流和会话单元。
可选的，当上述方法应用于接收端，且该接收端为终端时，所述目标SDAP实体将接收到的数据包转发至应用协议层。
该实施方式中，可以实现终端通过SDAP实体将数据包转发到应用协议层。
本实施例中，通过上述步骤可以实现准确地在SDAP实体和PDCP之间进行数据的接收，从而提高数据接收端的接收性能。
请参见图14，图14是本公开实施例提供的一种数据发送端的结构图，如图14所示，数据发送端1400包括：
第一发送模块1401，用于供高层实体根据网络切片标识、SDAP标识、数据流标识和会话标识中的至少一项，将数据包发送给对应的SDAP实体；
第二发送模块1402，用于供所述SDAP实体在所述数据包中添加数据流标识，并根据SDAP实体与数据承载DRB的对应关系，向DRB对应的PDCP 实体发送所述数据包。
可选的，如图15所示，所述数据发送端还包括：
建立模块1403，用于预先根据网络配置或预先约定的配置信息建立SDAP实体，所述配置信息包括以下至少一项：网络切片标识、数据承载标识、数据流标识、会话标识和关联关系指示信息；
指示模块1404，用于通过所述SDAP实体向高层实体指示所述SDAP实体的对应关系信息，所述对应关系信息包括以下至少一项：网络切片标识、数据承载标识、数据流标识、会话标识和SDAP标识。
可选的，所述关联关系指示信息包括以下任一种：
指示1个SDAP实体对应1个数据流；
指示1个SDAP实体对应1个会话单元；
指示1个SDAP实体对应1个PDCP实体；
指示1个SDAP实体对应1个MAC实体；
指示1个SDAP实体对应1个终端。
可选的，当所述关联关系指示信息为指示1个SDAP实体对应1个MAC实体时，所述配置信息还包括MAC标识。
可选的，当所述关联关系指示信息为指示1个SDAP实体对应1个会话单元、指示1个SDAP实体对应1个PDCP实体、指示1个SDAP实体对应1个MAC实体或指示1个SDAP实体对应1个终端时，所述对应关系信息还包括所述关联关系指示信息。
可选的，当所述关联关系指示信息为指示1个SDAP实体对应1个会话单元或指示1个SDAP实体对应1个PDCP实体时，如图16所示，所述数据发送端1400还包括：
第一提供模块1405，用于供所述高层实体提供所述数据包的辅助信息，所述辅助信息包括数据流标识。
可选的，当所述关联关系指示信息为指示1个SDAP实体对应1个MAC实体或指示1个SDAP实体对应1个终端时，如图17所示，所述数据发送端1400还包括：
第二提供模块1406，用于供所述高层实体提供所述数据包的辅助信息， 所述辅助信息包括以下至少一项：数据流标识、网络切片标识和会话标识。
需要说明的是，本实施例中上述数据发送端1400可以是本公开实施例中方法实施例中任意实施方式的数据发送端，本公开实施例中方法实施例中数据发送端的任意实施方式都可以被本实施例中的上述数据发送端1400所实现，以及达到相同的有益效果，此处不再赘述。
请参见图18，图18是本公开实施例提供的一种数据接收端的结构图，如图18所示，数据接收端1800包括：
接收模块1801，用于供PDCP实体接收来自数据发送端的数据包，根据所述数据包携带的数据流标识，向对应的SDAP实体发送所述数据包；
转发模块1802，用于供所述SDAP实体将所述数据包转发至应用协议层，或者，将所述数据包转发至对应的网络切片、数据流和会话单元。
可选的，所述转发模块1802，具体用于供所述SDAP实体根据网络切片标识、SDAP标识、数据流标识和会话标识中的至少一项，将所述数据包转发至对应的网络切片、数据流和会话单元。
可选的，如图19所示，数据接收端1800还包括：
建立模块1803，用于预先根据网络配置或协议约定的配置信息建立SDAP实体，所述配置信息包括以下至少一项：网络切片标识、数据承载标识、数据流标识、会话标识和关联关系指示信息；
指示模块1804，用于通过所述SDAP实体向高层实体指示所述SDAP实体的对应关系信息，所述对应关系信息包括以下至少一项：网络切片标识、数据承载标识、数据流标识、会话标识和SDAP标识。
可选的，所述关联关系指示信息包括以下任一种：
指示1个SDAP实体对应1个数据流；
指示1个SDAP实体对应1个会话单元；
指示1个SDAP实体对应1个PDCP实体；
指示1个SDAP实体对应1个MAC实体；
指示1个SDAP实体对应1个终端。
可选的，当所述关联关系指示信息为指示1个SDAP实体对应1个MAC实体时，所述配置信息还包括MAC标识。
可选的，当所述关联关系指示信息为指示1个SDAP实体对应1个会话单元、指示1个SDAP实体对应1个PDCP实体、指示1个SDAP实体对应1个MAC实体或指示1个SDAP实体对应1个终端时，所述对应关系信息还包括所述关联关系指示信息。
需要说明的是，本实施例中上述数据接收端1800可以是本公开实施例中方法实施例中任意实施方式的数据接收端，本公开实施例中方法实施例中数据接收端的任意实施方式都可以被本实施例中的上述数据接收端1800所实现，以及达到相同的有益效果，此处不再赘述。
参见图20，图20是本公开实施例提供的一种数据处理装置的结构图，如图20所示，数据处理装置2000包括：
建立模块2001，用于预先根据网络配置或协议约定的配置信息建立SDAP实体，所述配置信息包括以下至少一项：网络切片标识、数据承载标识、数据流标识、会话标识和关联关系指示信息；
指示模块2002，用于通过所述SDAP实体向高层实体指示所述SDAP实体的对应关系信息；
传输模块2003，用于基于所述对应关系信息在所述高层实体、SDAP实体和PDCP实体之间进行数据传输。
可选的，所述关联关系指示信息包括以下任一种：
指示1个SDAP实体对应1个数据流；
指示1个SDAP实体对应1个会话单元；
指示1个SDAP实体对应1个PDCP实体；
指示1个SDAP实体对应1个MAC实体；
指示1个SDAP实体对应1个终端。
可选的，当所述关联关系指示信息为指示1个SDAP实体对应1个MAC实体时，所述配置信息还包括MAC标识。
可选的，所述对应关系信息包括以下至少一项：网络切片标识、数据承载标识、数据流标识、会话标识和SDAP标识。
可选的，当所述数据处理装置2000应用于发送端时，如图21所示，所述传输模块2003包括：
第一确定子模块20031，用于供高层实体根据网络切片标识、SDAP标识、数据流标识和会话标识中的至少一项，确定待发送的目标数据包对应的目标SDAP实体；
发送子模块20032，用于供高层实体向所述目标SDAP实体发送所述目标数据包；
第一转发子模块20033，用于供所述目标SDAP实体根据SDAP实体与数据承载DRB的对应关系，在所述目标数据包中添加数据流标识后，向数据承载对应的目标包数据汇聚协议PDCP实体转发目标数据包。
可选的，当所述关联关系指示信息为指示1个SDAP实体对应1个会话单元或指示1个SDAP实体对应1个PDCP实体时，所述高层实体提供发送的目标数据包的辅助信息，所述辅助信息包括数据流标识。
可选的，当所述关联关系指示信息为指示1个SDAP实体对应1个MAC实体或指示1个SDAP实体对应1个终端时，所述高层实体提供发送的目标数据包的辅助信息，所述辅助信息包括以下至少一项：数据流标识、网络切片标识和会话标识。
可选的，当所述数据处理装置2000应用于接收端时，如图22所示，所述传输模块2003包括：
接收子模块20034，用于供PDCP实体接收发送端发送的目标数据包；
第二转发模块20035，用于供PDCP实体根据所述目标数据包携带的数据流标识，向对应的目标业务数据适配协议SDAP实体转发所述目标数据包。
可选的，当所述接收端为网络侧设备时，如图23所示，所述数据处理装置2000还包括：
转发模块2004，用于供所述目标SDAP实体将接收到的目标数据包转发至对应的网络切片、数据流和会话单元。
可选的，当所述接收端为终端时，所述目标SDAP实体将接收到的数据包转发至应用协议层。
需要说明的是，本实施例中上述数据处理装置2000实现本公开实施例提供的数据处理方法的任一实施方式，且达到相同的有益效果，此处不再赘述。
参见图24，图24是本公开实施例应用的数据发送端的结构图，如图24 所示，数据发送端2400包括：至少一个处理器2401、存储器2402、至少一个网络接口2404和用户接口2403。数据发送端2400中的各个组件通过总线系统2405耦合在一起。可理解，总线系统2405用于实现这些组件之间的连接通信。总线系统2405除包括数据总线之外，还包括电源总线、控制总线和状态信号总线。但是为了清楚说明起见，在图24中将各种总线都标为总线系统2405。
其中，用户接口2403可以包括显示器、键盘或者点击设备(例如，鼠标，轨迹球(track ball)、触感板或者触摸屏等。
可以理解，本公开实施例中的存储器2402可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(Random Access Memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(Static RAM，SRAM)、动态随机存取存储器(Dynamic RAM，DRAM)、同步动态随机存取存储器(Synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM，DDRSDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(Synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM，DRRAM)。本文描述的系统和方法的存储器2402旨在包括但不限于这些和任意其它适合类型的存储器。
在一些实施方式中，存储器2402存储了如下的元素，可执行模块或者数据结构，或者他们的子集，或者他们的扩展集：操作系统24021和应用程序24022。
其中，操作系统24021，包含各种系统程序，例如框架层、核心库层、驱动层等，用于实现各种基础业务以及处理基于硬件的任务。应用程序24022，包含各种应用程序，例如媒体播放器(Media Player)、浏览器(Browser)等，用 于实现各种应用业务。实现本公开实施例方法的程序可以包含在应用程序24022中。
在本公开实施例中，通过调用存储器2402存储的程序或指令，具体的，可以是应用程序24022中存储的程序或指令，处理器2401用于：
供高层实体根据网络切片标识、SDAP标识、数据流标识和会话标识中的至少一项，将数据包发送给对应的SDAP实体；
所述SDAP实体在所述数据包中添加数据流标识，并根据SDAP实体与DRB的对应关系，向DRB对应的PDCP实体发送所述数据包。
上述本公开实施例揭示的方法可以应用于处理器2401中，或者由处理器2401实现。处理器2401可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法的各步骤可以通过处理器2401中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器2401可以是通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现成可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本公开实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本公开实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器2402，处理器2401读取存储器2402中的信息，结合其硬件完成上述方法的步骤。
可以理解的是，本文描述的这些实施例可以用硬件、软件、固件、中间件、微码或其组合来实现。对于硬件实现，处理单元可以实现在一个或多个专用集成电路(Application Specific Integrated Circuits，ASIC)、数字信号处理器(Digital Signal Processing，DSP)、数字信号处理设备(DSP Device，DSPD)、可编程逻辑设备(Programmable Logic Device，PLD)、现场可编程门阵列(Field-Programmable Gate Array，FPGA)、通用处理器、控制器、微控制器、微处理器、用于执行本申请所述功能的其它电子单元或其组合中。
对于软件实现，可通过执行本文所述功能的模块(例如过程、函数等)来实现本文所述的技术。软件代码可存储在存储器中并通过处理器执行。存储器可以在处理器中或在处理器外部实现。
可选的，所述高层实体根据网络切片标识、SDAP标识、数据流标识和会话标识中的至少一项，将数据包发送给对应的SDAP实体之前，处理器2401还用于：
预先根据网络配置或预先约定的配置信息建立SDAP实体，所述配置信息包括以下至少一项：网络切片标识、数据承载标识、数据流标识、会话标识和关联关系指示信息；
通过所述SDAP实体向高层实体指示所述SDAP实体的对应关系信息，所述对应关系信息包括以下至少一项：网络切片标识、数据承载标识、数据流标识、会话标识和SDAP标识。
可选的，所述关联关系指示信息包括以下任一种：
指示1个SDAP实体对应1个数据流；
指示1个SDAP实体对应1个会话单元；
指示1个SDAP实体对应1个PDCP实体；
指示1个SDAP实体对应1个MAC实体；
指示1个SDAP实体对应1个终端。
可选的，当所述关联关系指示信息为指示1个SDAP实体对应1个MAC实体时，所述配置信息还包括MAC标识。
可选的，当所述关联关系指示信息为指示1个SDAP实体对应1个会话单元、指示1个SDAP实体对应1个PDCP实体、指示1个SDAP实体对应1个MAC实体或指示1个SDAP实体对应1个终端时，所述对应关系信息还包括所述关联关系指示信息。
可选的，当所述关联关系指示信息为指示1个SDAP实体对应1个会话单元或指示1个SDAP实体对应1个PDCP实体时，处理器2401还用于：
供所述高层实体提供所述数据包的辅助信息，所述辅助信息包括数据流标识。
可选的，当所述关联关系指示信息为指示1个SDAP实体对应1个MAC 实体或指示1个SDAP实体对应1个终端时，处理器2401还用于：
供所述高层实体提供所述数据包的辅助信息，所述辅助信息包括以下至少一项：数据流标识、网络切片标识和会话标识。
需要说明的是，本实施例中上述数据发送端2400实现本公开实施例提供的数据传输方法的任一实施方式，且达到相同的有益效果，此处不再赘述。
参见图25，图25是本公开实施例应用的数据接收端的结构图，如图25所示，数据接收端2500包括：至少一个处理器2501、存储器2502、至少一个网络接口2504和用户接口2503。数据接收端2500中的各个组件通过总线系统2505耦合在一起。可理解，总线系统2505用于实现这些组件之间的连接通信。总线系统2505除包括数据总线之外，还包括电源总线、控制总线和状态信号总线。但是为了清楚说明起见，在图25中将各种总线都标为总线系统2505。
其中，用户接口2503可以包括显示器、键盘或者点击设备(例如，鼠标，轨迹球(track ball)、触感板或者触摸屏等。
可以理解，本公开实施例中的存储器2502可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(Random Access Memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(Static RAM，SRAM)、动态随机存取存储器(Dynamic RAM，DRAM)、同步动态随机存取存储器(Synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM，DDRSDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(Synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM，DRRAM)。本文描述的系统和方法的存储器2502旨在包括但不限于这些和任意其它适合类型的存储器。
在一些实施方式中，存储器2502存储了如下的元素，可执行模块或者数据结构，或者他们的子集，或者他们的扩展集：操作系统25021和应用程序25022。
其中，操作系统25021，包含各种系统程序，例如框架层、核心库层、驱动层等，用于实现各种基础业务以及处理基于硬件的任务。应用程序25022，包含各种应用程序，例如媒体播放器(Media Player)、浏览器(Browser)等，用于实现各种应用业务。实现本公开实施例方法的程序可以包含在应用程序25022中。
在本公开实施例中，通过调用存储器2502存储的程序或指令，具体的，可以是应用程序25022中存储的程序或指令，处理器2501用于：
供PDCP实体接收来自数据发送端的数据包，根据所述数据包携带的数据流标识，向对应的SDAP实体发送所述数据包；
所述SDAP实体将所述数据包转发至应用协议层，或者，将所述数据包转发至对应的网络切片、数据流和会话单元。
上述本公开实施例揭示的方法可以应用于处理器2501中，或者由处理器2501实现。处理器2501可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法的各步骤可以通过处理器2501中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器2501可以是通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现成可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本公开实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本公开实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器2502，处理器2501读取存储器2502中的信息，结合其硬件完成上述方法的步骤。
可以理解的是，本文描述的这些实施例可以用硬件、软件、固件、中间 件、微码或其组合来实现。对于硬件实现，处理单元可以实现在一个或多个专用集成电路(Application Specific Integrated Circuits，ASIC)、数字信号处理器(Digital Signal Processing，DSP)、数字信号处理设备(DSP Device，DSPD)、可编程逻辑设备(Programmable Logic Device，PLD)、现场可编程门阵列(Field-Programmable Gate Array，FPGA)、通用处理器、控制器、微控制器、微处理器、用于执行本申请所述功能的其它电子单元或其组合中。
对于软件实现，可通过执行本文所述功能的模块(例如过程、函数等)来实现本文所述的技术。软件代码可存储在存储器中并通过处理器执行。存储器可以在处理器中或在处理器外部实现。
可选的，处理器2501执行的所述SDAP实体将所述数据包转发至对应的网络切片、数据流和会话单元，包括：
所述SDAP实体根据网络切片标识、SDAP标识、数据流标识和会话标识中的至少一项，将所述数据包转发至对应的网络切片、数据流和会话单元。
可选的，处理器2501还用于：
预先根据网络配置或协议约定的配置信息建立SDAP实体，所述配置信息包括以下至少一项：网络切片标识、数据承载标识、数据流标识、会话标识和关联关系指示信息；
通过所述SDAP实体向高层实体指示所述SDAP实体的对应关系信息，所述对应关系信息包括以下至少一项：网络切片标识、数据承载标识、数据流标识、会话标识和SDAP标识。
可选的，所述关联关系指示信息包括以下任一种：
指示1个SDAP实体对应1个数据流；
指示1个SDAP实体对应1个会话单元；
指示1个SDAP实体对应1个PDCP实体；
指示1个SDAP实体对应1个MAC实体；
指示1个SDAP实体对应1个终端。
可选的，当所述关联关系指示信息为指示1个SDAP实体对应1个MAC实体时，所述配置信息还包括MAC标识。
可选的，当所述关联关系指示信息为指示1个SDAP实体对应1个会话 单元、指示1个SDAP实体对应1个PDCP实体、指示1个SDAP实体对应1个MAC实体或指示1个SDAP实体对应1个终端时，所述对应关系信息还包括所述关联关系指示信息。
需要说明的是，本实施例中上述数据接收端2500实现本公开实施例提供的数据传输方法的任一实施方式，且达到相同的有益效果，此处不再赘述。
参见图26，图26是本公开实施例应用的数据处理装置的结构图，如图26所示，数据处理装置2600包括：至少一个处理器2601、存储器2602、至少一个网络接口2604和用户接口2603。数据处理装置2600中的各个组件通过总线系统2605耦合在一起。可理解，总线系统2605用于实现这些组件之间的连接通信。总线系统2605除包括数据总线之外，还包括电源总线、控制总线和状态信号总线。但是为了清楚说明起见，在图26中将各种总线都标为总线系统2605。
其中，用户接口2603可以包括显示器、键盘或者点击设备(例如，鼠标，轨迹球(track ball)、触感板或者触摸屏等。
可以理解，本公开实施例中的存储器2602可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(Random Access Memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(Static RAM，SRAM)、动态随机存取存储器(Dynamic RAM，DRAM)、同步动态随机存取存储器(Synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM，DDRSDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(Synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM，DRRAM)。本文描述的系统和方法的存储器2602旨在包括但不限于这些和任意其它适合类型的存储器。
在一些实施方式中，存储器2602存储了如下的元素，可执行模块或者数据结构，或者他们的子集，或者他们的扩展集：操作系统26021和应用程序26022。
其中，操作系统26021，包含各种系统程序，例如框架层、核心库层、驱动层等，用于实现各种基础业务以及处理基于硬件的任务。应用程序26022，包含各种应用程序，例如媒体播放器(Media Player)、浏览器(Browser)等，用于实现各种应用业务。实现本公开实施例方法的程序可以包含在应用程序26022中。
在本公开实施例中，通过调用存储器2602存储的程序或指令，具体的，可以是应用程序26022中存储的程序或指令，处理器2601用于：
预先根据网络配置或协议约定的配置信息建立SDAP实体，所述配置信息包括以下至少一项：网络切片标识、数据承载标识、数据流标识、会话标识和关联关系指示信息；
通过所述SDAP实体向高层实体指示所述SDAP实体的对应关系信息；
基于所述对应关系信息在所述高层实体、SDAP实体和PDCP实体之间进行数据传输。
上述本公开实施例揭示的方法可以应用于处理器2601中，或者由处理器2601实现。处理器2601可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法的各步骤可以通过处理器2601中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器2601可以是通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现成可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本公开实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本公开实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器2602，处 理器2601读取存储器2602中的信息，结合其硬件完成上述方法的步骤。
可以理解的是，本文描述的这些实施例可以用硬件、软件、固件、中间件、微码或其组合来实现。对于硬件实现，处理单元可以实现在一个或多个专用集成电路(Application Specific Integrated Circuits，ASIC)、数字信号处理器(Digital Signal Processing，DSP)、数字信号处理设备(DSP Device，DSPD)、可编程逻辑设备(Programmable Logic Device，PLD)、现场可编程门阵列(Field-Programmable Gate Array，FPGA)、通用处理器、控制器、微控制器、微处理器、用于执行本申请所述功能的其它电子单元或其组合中。
对于软件实现，可通过执行本文所述功能的模块(例如过程、函数等)来实现本文所述的技术。软件代码可存储在存储器中并通过处理器执行。存储器可以在处理器中或在处理器外部实现。
可选的，所述关联关系指示信息包括以下任一种：
指示1个SDAP实体对应1个数据流；
指示1个SDAP实体对应1个会话单元；
指示1个SDAP实体对应1个PDCP实体；
指示1个SDAP实体对应1个MAC实体；
指示1个SDAP实体对应1个终端。
可选的，当所述关联关系指示信息为指示1个SDAP实体对应1个MAC实体时，所述配置信息还包括MAC标识。
可选的，所述对应关系信息包括以下至少一项：网络切片标识、数据承载标识、数据流标识、会话标识和SDAP标识。
可选的，当所述数据处理方法应用于发送端时，处理器2601执行的基于所述对应关系信息在所述高层实体、SDAP实体和包数据汇聚协议PDCP实体之间进行数据传输的步骤包括：
高层实体根据网络切片标识、SDAP标识、数据流标识和会话标识中的至少一项，确定待发送的目标数据包对应的目标SDAP实体；
高层实体向所述目标SDAP实体发送所述目标数据包；
所述目标SDAP实体根据SDAP实体与数据承载DRB的对应关系，在所述目标数据包中添加数据流标识后，向数据承载对应的目标PDCP实体转发 目标数据包。
可选的，当所述关联关系指示信息为指示1个SDAP实体对应1个会话单元或指示1个SDAP实体对应1个PDCP实体时，所述高层实体提供发送的目标数据包的辅助信息，所述辅助信息包括数据流标识。
可选的，当所述关联关系指示信息为指示1个SDAP实体对应1个MAC实体或指示1个SDAP实体对应1个终端时，所述高层实体提供发送的目标数据包的辅助信息，所述辅助信息包括以下至少一项：数据流标识、网络切片标识和会话标识。
可选的，当所述数据处理方法应用于接收端时，处理器2601执行的基于所述对应关系信息在所述高层实体、SDAP实体和PDCP实体之间进行数据传输的步骤包括：
PDCP实体接收发送端发送的目标数据包；
PDCP实体根据所述目标数据包携带的数据流标识，向对应的目标SDAP实体转发所述目标数据包。
可选的，当所述接收端为网络侧设备时，所述向对应的目标业务数据适配协议SDAP实体转发所述目标数据包的步骤之后，处理器2601还用于：
供所述目标SDAP实体将接收到的目标数据包转发至对应的网络切片、数据流和会话单元。
可选的，当所述接收端为终端时，所述目标SDAP实体将接收到的数据包转发至应用协议层。
需要说明的是，本实施例中上述数据处理装置2600实现本公开实施例提供的数据处理方法的任一实施方式，且达到相同的有益效果，此处不再赘述。
第八方面，本公开实施例还提供了一种计算机可读存储介质，所述计算机可读存储介质上存储有数据传输程序，所述数据传输程序被处理器执行时实现本公开实施例提供的数据发送端侧的数据传输方法的步骤。
第九方面，本公开实施例还提供了一种计算机可读存储介质，所述计算机可读存储介质上存储有数据传输程序，所述数据传输程序被处理器执行时实现本公开实施例提供的数据接收端侧的的数据传输方法的步骤。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各 示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本公开的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的实施例中，应该理解到，所揭露的装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本公开实施例方案的目的。
另外，在本公开各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本公开的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本公开各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、ROM、RAM、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本公开的具体实施方式，但本公开的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本公开揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本公开的保护范围之内。因此，本公开的保护范围应以权利要求的保护范围为准。

Claims (31)

  1. 一种数据传输方法，应用于数据发送端，包括：
    高层实体根据网络切片标识、业务数据适配协议SDAP标识、数据流标识和会话标识中的至少一项，将数据包发送给对应的SDAP实体；
    所述SDAP实体在所述数据包中添加所述数据流标识；以及
    根据所述SDAP实体与数据承载DRB的对应关系，向DRB对应的PDCP实体发送所述数据包。
  2. 根据权利要求1所述的方法，其中，所述高层实体根据网络切片标识、SDAP标识、数据流标识和会话标识中的至少一项，将数据包发送给对应的SDAP实体之前，所述方法还包括：
    预先根据网络配置或预先约定的配置信息建立所述SDAP实体，所述配置信息包括以下至少一项：网络切片标识、数据承载标识、数据流标识、会话标识和关联关系指示信息；
    通过所述SDAP实体向所述高层实体指示所述SDAP实体的对应关系信息，所述对应关系信息包括以下至少一项：网络切片标识、数据承载标识、数据流标识、会话标识和SDAP标识。
  3. 根据权利要求2所述的数据传输方法，其中，所述关联关系指示信息包括以下任一种：
    指示1个SDAP实体对应1个数据流；
    指示1个SDAP实体对应1个会话单元；
    指示1个SDAP实体对应1个PDCP实体；
    指示1个SDAP实体对应1个媒体接入控制MAC实体；
    指示1个SDAP实体对应1个终端。
  4. 根据权利要求3所述的方法，其中，当所述关联关系指示信息为指示1个SDAP实体对应1个MAC实体时，所述配置信息还包括MAC标识。
  5. 根据权利要求3所述的方法，其中，当所述关联关系指示信息为指示1个SDAP实体对应1个会话单元、指示1个SDAP实体对应1个PDCP实体、指示1个SDAP实体对应1个MAC实体或指示1个SDAP实体对应1 个终端时，所述对应关系信息还包括所述关联关系指示信息。
  6. 根据权利要求5所述的方法，其中，当所述关联关系指示信息为指示1个SDAP实体对应1个会话单元或指示1个SDAP实体对应1个PDCP实体时，所述方法还包括：
    所述高层实体提供所述数据包的辅助信息，所述辅助信息包括数据流标识。
  7. 根据权利要求5所述的方法，其中，当所述关联关系指示信息为指示1个SDAP实体对应1个MAC实体或指示1个SDAP实体对应1个终端时，所述方法还包括：
    所述高层实体提供所述数据包的辅助信息，所述辅助信息包括以下至少一项：数据流标识、网络切片标识和会话标识。
  8. 一种数据传输方法，应用于数据接收端，包括：
    PDCP实体接收来自数据发送端的数据包，根据所述数据包携带的数据流标识，向对应的SDAP实体发送所述数据包；
    所述SDAP实体将所述数据包转发至应用协议层，或者，将所述数据包转发至对应的网络切片、数据流和会话单元。
  9. 根据权利要求8所述的方法，其中，所述SDAP实体将所述数据包转发至对应的网络切片、数据流和会话单元，包括：
    所述SDAP实体根据网络切片标识、SDAP标识、数据流标识和会话标识中的至少一项，将所述数据包转发至对应的网络切片、数据流和会话单元。
  10. 根据权利要求8所述的方法，还包括：
    预先根据网络配置或协议约定的配置信息建立SDAP实体，所述配置信息包括以下至少一项：网络切片标识、数据承载标识、数据流标识、会话标识和关联关系指示信息；
    通过所述SDAP实体向高层实体指示所述SDAP实体的对应关系信息，所述对应关系信息包括以下至少一项：网络切片标识、数据承载标识、数据流标识、会话标识和SDAP标识。
  11. 根据权利要求10所述的数据传输方法，其中，所述关联关系指示信息包括以下任一种：
    指示1个SDAP实体对应1个数据流；
    指示1个SDAP实体对应1个会话单元；
    指示1个SDAP实体对应1个PDCP实体；
    指示1个SDAP实体对应1个MAC实体；
    指示1个SDAP实体对应1个终端。
  12. 根据权利要求11所述的方法，其中，当所述关联关系指示信息为指示1个SDAP实体对应1个MAC实体时，所述配置信息还包括MAC标识。
  13. 根据权利要求11所述的方法，其中，当所述关联关系指示信息为指示1个SDAP实体对应1个会话单元、指示1个SDAP实体对应1个PDCP实体、指示1个SDAP实体对应1个MAC实体或指示1个SDAP实体对应1个终端时，所述对应关系信息还包括所述关联关系指示信息。
  14. 一种数据发送端，包括：
    第一发送模块，用于供高层实体根据网络切片标识、SDAP标识、数据流标识和会话标识中的至少一项，将数据包发送给对应的SDAP实体；
    第二发送模块，用于供所述SDAP实体在所述数据包中添加数据流标识，并根据SDAP实体与数据承载DRB的对应关系，向DRB对应的PDCP实体发送所述数据包。
  15. 根据权利要求14所述的数据发送端，其中，所述数据发送端还包括：
    建立模块，用于预先根据网络配置或预先约定的配置信息建立SDAP实体，所述配置信息包括以下至少一项：网络切片标识、数据承载标识、数据流标识、会话标识和关联关系指示信息；
    指示模块，用于通过所述SDAP实体向高层实体指示所述SDAP实体的对应关系信息，所述对应关系信息包括以下至少一项：网络切片标识、数据承载标识、数据流标识、会话标识和SDAP标识。
  16. 根据权利要求15所述的数据传输数据发送端，其中，所述关联关系指示信息包括以下任一种：
    指示1个SDAP实体对应1个数据流；
    指示1个SDAP实体对应1个会话单元；
    指示1个SDAP实体对应1个PDCP实体；
    指示1个SDAP实体对应1个MAC实体；
    指示1个SDAP实体对应1个终端。
  17. 根据权利要求16所述的数据发送端，其中，当所述关联关系指示信息为指示1个SDAP实体对应1个MAC实体时，所述配置信息还包括MAC标识。
  18. 根据权利要求16所述的数据发送端，其中，当所述关联关系指示信息为指示1个SDAP实体对应1个会话单元、指示1个SDAP实体对应1个PDCP实体、指示1个SDAP实体对应1个MAC实体或指示1个SDAP实体对应1个终端时，所述对应关系信息还包括所述关联关系指示信息。
  19. 根据权利要求18所述的数据发送端，其中，当所述关联关系指示信息为指示1个SDAP实体对应1个会话单元或指示1个SDAP实体对应1个PDCP实体时，所述数据发送端还包括：
    第一提供模块，用于供所述高层实体提供所述数据包的辅助信息，所述辅助信息包括数据流标识。
  20. 根据权利要求18所述的数据发送端，其中，当所述关联关系指示信息为指示1个SDAP实体对应1个MAC实体或指示1个SDAP实体对应1个终端时，所述数据发送端还包括：
    第二提供模块，用于供所述高层实体提供所述数据包的辅助信息，所述辅助信息包括以下至少一项：数据流标识、网络切片标识和会话标识。
  21. 一种数据接收端，包括：
    接收模块，用于供PDCP实体接收来自数据发送端的数据包，根据所述数据包携带的数据流标识，向对应的SDAP实体发送所述数据包；
    转发模块，用于供所述SDAP实体将所述数据包转发至应用协议层，或者，将所述数据包转发至对应的网络切片、数据流和会话单元。
  22. 根据权利要求21所述的数据接收端，其中，所述转发模块，具体用于供所述SDAP实体根据网络切片标识、SDAP标识、数据流标识和会话标识中的至少一项，将所述数据包转发至对应的网络切片、数据流和会话单元。
  23. 根据权利要求21所述的数据接收端，还包括：
    建立模块，用于预先根据网络配置或协议约定的配置信息建立SDAP实 体，所述配置信息包括以下至少一项：网络切片标识、数据承载标识、数据流标识、会话标识和关联关系指示信息；
    指示模块，用于通过所述SDAP实体向高层实体指示所述SDAP实体的对应关系信息，所述对应关系信息包括以下至少一项：网络切片标识、数据承载标识、数据流标识、会话标识和SDAP标识。
  24. 根据权利要求23所述的数据传输数据接收端，其中，所述关联关系指示信息包括以下任一种：
    指示1个SDAP实体对应1个数据流；
    指示1个SDAP实体对应1个会话单元；
    指示1个SDAP实体对应1个PDCP实体；
    指示1个SDAP实体对应1个MAC实体；
    指示1个SDAP实体对应1个终端。
  25. 根据权利要求24所述的数据接收端，其中，当所述关联关系指示信息为指示1个SDAP实体对应1个MAC实体时，所述配置信息还包括MAC标识。
  26. 根据权利要求24所述的数据接收端，其中，当所述关联关系指示信息为指示1个SDAP实体对应1个会话单元、指示1个SDAP实体对应1个PDCP实体、指示1个SDAP实体对应1个MAC实体或指示1个SDAP实体对应1个终端时，所述对应关系信息还包括所述关联关系指示信息。
  27. 一种数据发送端，包括：处理器、存储器、网络接口和用户接口，所述处理器、所述存储器、所述网络接口和所述用户接口通过总线系统耦合在一起，所述处理器用于读取所述存储器中的程序，执行如权利要求1至7中任一项所述的数据传输方法中的步骤。
  28. 一种数据接收端，包括：处理器、存储器、网络接口和用户接口，所述处理器、所述存储器、所述网络接口和所述用户接口通过总线系统耦合在一起，所述处理器用于读取所述存储器中的程序，执行如权利要求8至13中任一项所述的数据传输方法中的步骤。
  29. 一种数据传输系统，包括如权利要求14至20中任一项所述数据发送端和如权利要求21至26中任一项所述数据接收端；或者包括如权利要求 27所述数据发送端和如权利要求28所述数据接收端。
  30. 一种计算机可读存储介质，其中，所述计算机可读存储介质上存储有数据传输程序，所述数据传输程序被处理器执行时实现如权利要求1至7中任一项所述的数据传输方法的步骤。
  31. 一种计算机可读存储介质，其中，所述计算机可读存储介质上存储有数据传输程序，所述数据传输程序被处理器执行时实现如权利要求8至13中任一项所述的数据传输方法的步骤。
PCT/CN2018/089979 2017-06-08 2018-06-05 数据传输方法、数据发送端、数据接收端、数据传输系统及计算机可读存储介质 WO2018223965A1 (zh)

Priority Applications (5)

Application Number Priority Date Filing Date Title
US16/620,378 US11323912B2 (en) 2017-06-08 2018-06-05 Data transmission method, data transmitting end, data receiving end, data transmission system and computer readable storage medium
EP18813941.4A EP3637844B1 (en) 2017-06-08 2018-06-05 Data transmission methods, data transmitting end, data receiving end, data transmission system and computer-readable storage media
EP21186025.9A EP3913967B1 (en) 2017-06-08 2018-06-05 Data transmission method, data transmitting ends and computer readable storage medium
ES18813941T ES2899395T3 (es) 2017-06-08 2018-06-05 Métodos de transmisión de datos, extremo de transmisión de datos, extremo de recepción de datos, sistema de transmisión de datos y medio de almacenamiento legible por ordenador
US17/687,238 US11665581B2 (en) 2017-06-08 2022-03-04 Data transmission method, data transmitting end, data receiving end, data transmission system and computer readable storage medium

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710431213.3A CN109041119B9 (zh) 2017-06-08 2017-06-08 一种数据传输方法、相关设备及系统
CN201710431213.3 2017-06-08

Related Child Applications (2)

Application Number Title Priority Date Filing Date
US16/620,378 A-371-Of-International US11323912B2 (en) 2017-06-08 2018-06-05 Data transmission method, data transmitting end, data receiving end, data transmission system and computer readable storage medium
US17/687,238 Continuation US11665581B2 (en) 2017-06-08 2022-03-04 Data transmission method, data transmitting end, data receiving end, data transmission system and computer readable storage medium

Publications (1)

Publication Number Publication Date
WO2018223965A1 true WO2018223965A1 (zh) 2018-12-13

Family

ID=64566818

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/089979 WO2018223965A1 (zh) 2017-06-08 2018-06-05 数据传输方法、数据发送端、数据接收端、数据传输系统及计算机可读存储介质

Country Status (7)

Country Link
US (2) US11323912B2 (zh)
EP (2) EP3913967B1 (zh)
CN (1) CN109041119B9 (zh)
ES (2) ES2899395T3 (zh)
HU (1) HUE056963T2 (zh)
PT (1) PT3637844T (zh)
WO (1) WO2018223965A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020125521A1 (zh) * 2018-12-20 2020-06-25 华为技术有限公司 控制网络拥塞的方法、装置及系统

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109041119B9 (zh) * 2017-06-08 2020-07-03 维沃移动通信有限公司 一种数据传输方法、相关设备及系统
CN111447650B (zh) * 2019-01-17 2021-11-19 中国移动通信有限公司研究院 一种数据前转的方法、设备及存储介质
CN111278060B (zh) * 2019-01-18 2023-10-24 维沃移动通信有限公司 一种以太帧传输方法和相关设备
CN111585723B (zh) * 2019-02-15 2022-05-13 华为技术有限公司 一种辅助信息及其传递的方法和装置
CN112055423B (zh) 2019-06-06 2022-09-02 华为技术有限公司 一种通信方法及相关设备
US11212850B2 (en) * 2019-06-19 2021-12-28 Cisco Technology, Inc. Network slice support of respective transport protocols
CN116249157A (zh) * 2019-07-02 2023-06-09 大唐移动通信设备有限公司 一种业务数据适配层实体的管理方法、发送端及接收端
CN115442300A (zh) * 2021-06-04 2022-12-06 华为技术有限公司 报文转发方法、装置及通信网络
CN113726838B (zh) * 2021-06-17 2023-09-19 武汉理工数字传播工程有限公司 文件传输方法、装置、设备及存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102404789A (zh) * 2010-09-15 2012-04-04 华为技术有限公司 数据包处理方法、设备及系统
WO2013174422A1 (en) * 2012-05-23 2013-11-28 Nokia Siemens Networks Oy Methods, computer program products and apparatuses enabling symmetric bearer enforcement
US20160338130A1 (en) * 2014-01-17 2016-11-17 Lg Electronics Inc. Bearer setup method and apparatus in wireless communication system supporting dual connectivity

Family Cites Families (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101212404B (zh) 2006-12-27 2011-04-06 大唐移动通信设备有限公司 鲁棒头压缩分组数据传输的方法及系统
EP3180938A1 (en) 2014-08-15 2017-06-21 Telefonaktiebolaget LM Ericsson (publ) Rohc optimizations for burst losses
WO2017220151A1 (en) * 2016-06-23 2017-12-28 Huawei Technologies Co., Ltd. Access node, control device and method thereof
CN107770807B (zh) * 2016-08-15 2024-03-15 华为技术有限公司 一种数据处理方法及装置
WO2018128452A1 (en) * 2017-01-06 2018-07-12 Lg Electronics Inc. Method for transmitting lossless data packet based on quality of service (qos) framework in wireless communication system and a device therefor
US11115855B2 (en) * 2017-01-13 2021-09-07 Lg Electronics Inc. Method for transmitting UL packet based on quality of service (QoS) flow in wireless communication system and a device therefor
US10432761B2 (en) * 2017-01-18 2019-10-01 Qualcomm Incorporated Techniques for handling internet protocol flows in a layer 2 architecture of a wireless device
JP2020507976A (ja) * 2017-02-01 2020-03-12 エルジー エレクトロニクス インコーポレイティド 無線通信システムにおいて反映式サービス品質（ＱｏＳ）を行うための方法及びそのための装置
CN110352610B (zh) * 2017-03-01 2023-05-05 Lg电子株式会社 在无线通信系统中发送tcp ack分组的方法及其装置
EP3606116B1 (en) * 2017-03-20 2021-12-01 LG Electronics Inc. Method for interaction between layers in wireless communication system and apparatus therefor
KR102284374B1 (ko) * 2017-03-22 2021-08-02 엘지전자 주식회사 무선 통신 시스템에서 상이한 tti 길이들에서 mac ce를 전송하기 위한 방법 및 이를 위한 장치
KR102265907B1 (ko) * 2017-03-22 2021-06-16 엘지전자 주식회사 무선 통신 시스템에서 서비스 품질 (QoS) 구조 기반으로 상향링크 패킷을 전송하는 방법 및 이를 위한 장치
EP3603178B1 (en) * 2017-03-23 2024-10-02 Nokia Technologies Oy Quality of service flow relocation
CN108924876B (zh) * 2017-03-24 2024-05-10 华为技术有限公司 数据传输方法、接入网设备、终端及通信系统
US10980077B2 (en) * 2017-04-01 2021-04-13 Lg Electronics Inc. Method for performing MCG recovery in dual connectivity in wireless communication system and a device therefor
CN109274474B (zh) * 2017-05-05 2019-11-19 华为技术有限公司 一种基于反转服务流特性的通信方法及装置
KR102359746B1 (ko) * 2017-06-05 2022-02-10 삼성전자 주식회사 차세대 이동통신 시스템에서 인액티브 모드 단말이 데이터를 전송하는 방법 및 장치
CN109041119B9 (zh) * 2017-06-08 2020-07-03 维沃移动通信有限公司 一种数据传输方法、相关设备及系统
CN109151915B (zh) * 2017-06-16 2023-11-17 夏普株式会社 用于数据分组递送的方法、用户设备和基站
KR102629306B1 (ko) * 2018-05-21 2024-01-25 삼성전자 주식회사 차세대 이동통신 시스템에서 sdap 제어 pdu를 구분해서 처리하는 방법 및 장치

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102404789A (zh) * 2010-09-15 2012-04-04 华为技术有限公司 数据包处理方法、设备及系统
WO2013174422A1 (en) * 2012-05-23 2013-11-28 Nokia Siemens Networks Oy Methods, computer program products and apparatuses enabling symmetric bearer enforcement
US20160338130A1 (en) * 2014-01-17 2016-11-17 Lg Electronics Inc. Bearer setup method and apparatus in wireless communication system supporting dual connectivity

Non-Patent Citations (1)

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

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020125521A1 (zh) * 2018-12-20 2020-06-25 华为技术有限公司 控制网络拥塞的方法、装置及系统
US11431637B2 (en) 2018-12-20 2022-08-30 Huawei Technologies Co., Ltd. Network congestion control method, apparatus, and system

Also Published As

Publication number Publication date
CN109041119B (zh) 2020-06-02
US11665581B2 (en) 2023-05-30
EP3913967A1 (en) 2021-11-24
HUE056963T2 (hu) 2022-04-28
EP3637844A4 (en) 2020-06-17
US11323912B2 (en) 2022-05-03
ES2899395T3 (es) 2022-03-11
EP3913967B1 (en) 2022-12-07
PT3637844T (pt) 2021-11-19
ES2935209T3 (es) 2023-03-02
US20220191732A1 (en) 2022-06-16
US20210084526A1 (en) 2021-03-18
EP3637844A1 (en) 2020-04-15
CN109041119A (zh) 2018-12-18
EP3637844B1 (en) 2021-10-06
CN109041119B9 (zh) 2020-07-03

Similar Documents

Publication Publication Date Title
WO2018223965A1 (zh) 数据传输方法、数据发送端、数据接收端、数据传输系统及计算机可读存储介质
WO2018224013A1 (zh) 波束失败处理方法、终端及网络设备
WO2019005307A1 (en) CONFIGURABLE BEAM FAILURE EVENT DESIGN
US11140546B2 (en) Security processing method and related device
EP3920491B1 (en) Service processing method, device and computer readable storage medium
KR20150110103A (ko) 전송 경로 최적화를 위한 컨텐츠 서버 간 핸드오버 방법 및 장치
WO2018233512A1 (zh) 指示方法、基站和增强型移动宽带用户设备
US20180242146A1 (en) Apparatuses and methods for avoiding location exposure
JP2020532888A (ja) データ伝送方法、端末機器及びネットワーク機器
WO2017152360A1 (zh) 一种为无线承载进行安全配置方法和设备
WO2018195943A1 (zh) 用于拥塞处理的方法和设备
US11588860B2 (en) Flexible selection of security features in mobile networks
WO2020233496A1 (zh) 安全会话方法和装置
WO2019019057A1 (zh) 无线通信方法、终端设备和网络设备
WO2022174802A1 (zh) 密钥更新的方法和装置
WO2018210134A1 (zh) 随机接入的方法、终端、源基站和目标基站
WO2019192464A1 (zh) 配置数据流的方法和装置
WO2020147602A1 (zh) 一种认证方法、装置和系统
WO2021087729A1 (zh) 一种指示解压缩对象的方法及装置、通信设备
JP2022511577A (ja) 無線通信及び機器
WO2019095295A1 (zh) 用于传输数据的方法、终端设备和会话管理功能smf设备
US11968728B2 (en) Method of configuring service data adaptation protocol entity and device
WO2019028824A1 (zh) 用于传输数据的方法、终端设备和网络设备
WO2016161551A1 (zh) 用于多流汇聚的方法和装置
WO2020124540A1 (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: 18813941

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

Country of ref document: EP

Effective date: 20200108